support.dasanzhone.comsupport.dasanzhone.com/support/manuals/docs/98/... · 9820-A2-GB20-00 March...

FrameSaver � SLV 9820USER’S GUIDE

Document No. 9820-A2-GB20-00

March 1999

A 9820-A2-GB20-00March 1999

Copyright � 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 formor by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without theexpress 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 specificallydisclaims any implied warranties of merchantability or fitness for a particular purpose. Further, Paradyne Corporationreserves the right to revise this publication and to make changes from time to time in the contents hereof withoutobligation 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 newrelease to this manual.

Warranty, Sales, Service, and Training Information

Contact your local sales representative, service representative, or distributor directly for any help needed. Foradditional information concerning warranty, sales, service, repair, installation, documentation, training, distributorlocations, or Paradyne worldwide office locations, use one of the following methods:

� Internet: Visit the Paradyne World Wide Web site at www.paradyne.com . (Be sure to register your warranty there. Select Service & Support →Warranty Registration.)

� 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] . Includethe number and title of this document in your correspondence. Please include your name and phone number if youare willing to provide additional clarification.

Trademarks

All products and services mentioned herein are the trademarks, service marks, registered trademarks or registeredservice marks of their respective owners.

Patent Notification

FrameSaver SLV products are protected by U.S. Patents: 5,550,700 and 5,654,966. Other patents are pending.

i9820-A2-GB20-00 March 1999

Contents

About This Guide� Purpose and Intended Audience xi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Document Organization xi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Conventions Used xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Product-Related Documents xiv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 About the FrameSaver SLV Solution� Overview 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� The FrameSaver SLV 9820 and 9820-C 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . .

� The OpenLane Management Solution 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OpenLane DCE Manager 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OpenLane Performance Wizard 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� NetScout Manager Plus 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� FrameSaver SLV Unit Features 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� SNMP Management Capabilities 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Management Control� End User Management Overview 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Service Provider Management Overview 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . .

� Managing the FrameSaver Unit 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Configuring Local Management Control 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Management PVC Between the Router and Unit Via the User Data Port 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a Separate Management Link Via the COM Port 2-6. . . . . . . . .

Configuring an External Device (Connected to the COM Port) 2-7. . . . .

� Configuring End-to-End Management Control 2-8. . . . . . . . . . . . . . . . . . . . . . .

Management Control Using PVC Multiplexing (EDLCI) 2-8. . . . . . . . . . .

Management Control Using a Dedicated PVC 2-9. . . . . . . . . . . . . . . . . . .

Transparent Remote Management Control Using RFC 1490 Routers 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

ii 9820-A2-GB20-00March 1999

3 Typical Applications� SLV Frame Relay Monitoring 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Multinational Frame Relay Solution 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� SLV Frame Relay Access 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� PVC Multiplexing Application 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Using Auto-Configuration 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Back-to-Back Operation 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 User Interface� Interfaces to the FrameSaver SLV 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FrameSaver Unit’s Faceplate 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Menu-Driven User Interface 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Management 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Menu Hierarchy 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Main Menu Screen 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Screen Format Types 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� What Affects Screen Displays 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Screen Work Areas 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Navigating the Screens 4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Keyboard Keys 4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Screen Function Keys 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Using the Menu-Driven User Interface 4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selecting from a Menu 4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selecting a Field 4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Making Input Selections 4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Switching Between Screen Work Areas 4-8. . . . . . . . . . . . . . . . . . . . . . . .

Contents

iii9820-A2-GB20-00 March 1999

5 Using the OpenLane NMS� The OpenLane Advantage 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using an OpenLane NMS Application 5-2. . . . . . . . . . . . . . . . . . . . . . . . . .

� Installation and Setup of DCE Manager 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . .

� 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Viewing OpenLane Performance Wizard Graphs 5-10. . . . . . . . . . . . . . . . . . . .

Frame Relay Access Channel Aggregated Summary 5-11. . . . . . . . . . . . .

Frame Relay Physical Link Integrity 5-13. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Port Diagnostics 5-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PVC Throughput 5-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frame Relay DLCI Congestion 5-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PVC Data Delivery Analysis 5-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Creating OpenLane Service Level Management Reports 5-22. . . . . . . . . . . . .

Web Browsers Supported 5-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation and Setup of SLM Reports 5-23. . . . . . . . . . . . . . . . . . . . . . . . .

Displaying the Log-in Screen 5-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reports Administration 5-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Viewing Reports 5-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

iv 9820-A2-GB20-00March 1999

6 Using NetScout Manager Plus� The NetScout Advantage 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using a NetScout Manager Plus NMS Application 6-2. . . . . . . . . . . . . . .

� Installing NetScout Manager Plus 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Configuring NetScout Manager Plus 6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Before You Get Started 6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding FrameSaver SLV Units to the NetScout Manager Plus Network 6-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying Domains and Groups 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Correcting Domains and Groups 6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding SLV Alarms Using a Template 6-8. . . . . . . . . . . . . . . . . . . . . . . . . .

Editing Alarms 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding SLV Alarms Manually 6-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating History Files 6-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing the User-Defined History Files 6-15. . . . . . . . . . . . . . . . . . . . . . . .

Monitoring a DLCI’s History Data 6-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Monitoring the Agent Using NetScout Manager Plus 6-19. . . . . . . . . . . . .

Statistical Windows Supported 6-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

v9820-A2-GB20-00 March 1999

7 Using Concord’s Network Health� Network Health Compatibility 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Features 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using Concord’s Network Health NMS Application 7-2. . . . . . . . . . . . . . .

� Installation and Setup of Network Health 7-3. . . . . . . . . . . . . . . . . . . . . . . . . . .

Discovering FrameSaver Elements 7-4. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring the Discovered Elements 7-5. . . . . . . . . . . . . . . . . . . . . . . . . .

Grouping Elements for Reports 7-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Generating Reports for a Group 7-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Viewing Network Health Charts and Tables 7-8. . . . . . . . . . . . . . . . . . . . . . . . .

About Service Level Reports 7-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About the At-a-Glance Reports 7-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About Trend Reports 7-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Printed Reports 7-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Reports Applicable to FrameSaver SLV Units 7-17. . . . . . . . . . . . . . . . . . . . . . .

Exceptions Reports 7-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Summary Report 7-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Leaders Summary Report 7-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Elements Summary Report 7-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Supplemental Report 7-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Executive Service Level Report 7-29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IT Manager Service Level Report 7-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Customer Service Level Report 7-33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

At-a-Glance Reports 7-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Trend Reports 7-40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 Setup� Considerations When Setting Up 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Selecting a Management Interface 8-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Minimal Configuration Before Deploying Remote Units 8-2. . . . . . . . . . .

� Entering System Identification 8-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Setting the System Date and Time 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Setting Up Logins 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Configuring the FrameSaver Unit 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration Option Areas 8-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Accessing and Displaying Configuration Options 8-6. . . . . . . . . . . . . . . .

Changing Configuration Options 8-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Saving Configuration Options 8-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Setting Up Auto-Configuration 8-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing the Frame Relay Discovery Mode 8-9. . . . . . . . . . . . . . . . . . . .

Contents

vi 9820-A2-GB20-00March 1999

9 Configuration Options� Configuring System Options 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring System Frame Relay and LMI Options 9-2. . . . . . . . . . . . . .

Configuring Service Level Verification Options 9-4. . . . . . . . . . . . . . . . . . .

Configuring General System Options 9-5. . . . . . . . . . . . . . . . . . . . . . . . . . .

� Setting Up Each Physical Interface 9-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring the Network Data Port Physical Options 9-6. . . . . . . . . . . . .

Configuring User Data Port Physical Options 9-8. . . . . . . . . . . . . . . . . . . .

� Configuring Frame Relay LMI for the Unit 9-10. . . . . . . . . . . . . . . . . . . . . . . . . .

� Configuring DLCI Records for Each Interface 9-13. . . . . . . . . . . . . . . . . . . . . . .

� Configuring PVC Connections 9-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Setting Up Management and Communication Options 9-20. . . . . . . . . . . . . . .

Configuring Node IP Information 9-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring Management PVCs 9-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring General SNMP Management 9-27. . . . . . . . . . . . . . . . . . . . . . .

Configuring Telnet and/or FTP Session Support 9-28. . . . . . . . . . . . . . . . .

Configuring SNMP NMS Security 9-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring SNMP Traps and Trap Dial-Out 9-32. . . . . . . . . . . . . . . . . . . . .

Configuring the Communication Port 9-38. . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring the COM Port to Support an External Modem 9-43. . . . . . . .

10 Security and Logins� Limiting Access 10-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Controlling Asynchronous Terminal Access 10-2. . . . . . . . . . . . . . . . . . . . . . . . .

� Controlling Telnet Access 10-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Controlling FTP Access 10-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Controlling External COM Port Device Access 10-5. . . . . . . . . . . . . . . . . . . . . .

� Controlling SNMP Access 10-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Disabling SNMP Access 10-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assigning SNMP Community Names and Access Levels 10-7. . . . . . . . .

Limiting SNMP Access Through IP Addresses 10-8. . . . . . . . . . . . . . . . . .

� Creating a Login 10-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Modifying a Login 10-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Deleting a Login 10-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

vii9820-A2-GB20-00 March 1999

11 Displaying System Information� Displaying Unit Identification 11-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Displaying LEDs and Control Leads 11-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FrameSaver 9820 LEDs 11-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LED Descriptions 11-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Statuses 11-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System and Test Status Messages 11-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Self-Test Results Messages 11-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Health and Status Messages 11-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Status Messages 11-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Device Messages 11-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Network LMI-Reported DLCIs Status 11-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� PVC Connection Status 11-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Performance Statistics 11-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Types of Statistics Collected 11-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying Statistical Information 11-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining Whether a Statistic Is Incrementing 11-18. . . . . . . . . . . . . . . . .

� Service Level Verification Performance Statistics 11-19. . . . . . . . . . . . . . . . . . . .

� DLCI Performance Statistics 11-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Frame Relay Performance Statistics 11-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12 Operation and Maintenance� Accessing the Unit 12-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging In 12-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging Out 12-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting a Session 12-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Ending a Session 12-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Monitoring the Unit 12-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Viewing LEDs and Control Lead Status via theMenu-Driven User Interface 12-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Viewing Alarm and Status Messages 12-5. . . . . . . . . . . . . . . . . . . . . . . . . . .

� Maintaining Modem Call Directories 12-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying or Changing Modem Call Directories 12-6. . . . . . . . . . . . . . . . .

� FTP File Transfers 12-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Determining Whether a Download Is Completed 12-8. . . . . . . . . . . . . . . . .

Performing a Software Upgrade 12-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing Software 12-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transferring SLV Statistics to an NMS 12-11. . . . . . . . . . . . . . . . . . . . . . . . . .

� Downloading MIBs and SNMP Traps 12-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

viii 9820-A2-GB20-00March 1999

� Resetting the FrameSaver Unit 12-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Resetting the Unit from the Control Menu 12-12. . . . . . . . . . . . . . . . . . . . . . .

Resetting the Unit By Cycling the Power 12-12. . . . . . . . . . . . . . . . . . . . . . . .

Restoring Communication with a Misconfigured Unit 12-13. . . . . . . . . . . . .

� Setting Up Units for Back-to-Back Operation 12-14. . . . . . . . . . . . . . . . . . . . . . . .

Changing Operating Mode 12-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13 Troubleshooting� Troubleshooting Features 13-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Problem Indicators 13-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

LEDs 13-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarms 13-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Supported SNMP Traps 13-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Troubleshooting Tables 13-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FrameSaver Device Problems 13-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Frame Relay PVC Problems 13-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Tests Available 13-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Test Timeout 13-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Starting and Stopping a Test 13-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Aborting All Tests 13-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Determining Test Status and Results 13-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� PVC Tests 13-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network or Port (Internal) PVC Loopback 13-12. . . . . . . . . . . . . . . . . . . . . .

Send Pattern 13-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Monitor Pattern 13-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connectivity 13-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Physical Tests 13-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DTE Loopback 13-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� IP Ping Test 13-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Lamp Test 13-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

ix9820-A2-GB20-00 March 1999

A Menu Hierarchy� Menus A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B IP Addressing� Selecting an IP Addressing Scheme B-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Mixing Private and Public Addressing on the Same Network B-2. . . . . . . . . .

Service Provider Example B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preferred Method B-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� IP Addressing Scheme Examples B-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Direct PVCs to Remote FrameSaver Units B-5. . . . . . . . . . . . . . . . . . . . . .

Routing to Remote FrameSaver Units on the Same Subnet B-6. . . . . . .

Routing to Remote FrameSaver Units Using Different Subnets B-7. . . .

Routing to Remote FrameSaver Units Using Routers B-8. . . . . . . . . . . . .

Assigning IP Addresses and Subnet Masks B-10. . . . . . . . . . . . . . . . . . . . .

C Standards Compliance for SNMP Traps� Trap: warmStart C-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Trap: authenticationFailure C-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Traps: linkUp and linkDown C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Variable-Bindings: linkUp and linkDown C-4. . . . . . . . . . . . . . . . . . . . . . . .

� Traps: enterprise-Specific C-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Variable-Bindings: enterprise-Specific C-7. . . . . . . . . . . . . . . . . . . . . . . . . .

� Traps: RMON-Specific C-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Variable-Bindings: risingAlarm and fallingAlarm C-9. . . . . . . . . . . . . . . . . .

D RMON Alarm Defaults� RMON Alarm and Event Defaults D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Event Defaults D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rising Event Operation D-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Sync Port Physical Interface Alarm Defaults D-2. . . . . . . . . . . . .

Static Frame Relay Interface Alarm Defaults D-3. . . . . . . . . . . . . . . . . . . .

Dynamic Frame Relay Interface Alarm Defaults D-5. . . . . . . . . . . . . . . . .

DLCI Alarm Defaults – Paradyne Area D-6. . . . . . . . . . . . . . . . . . . . . . . . .

Static DLCI Alarm Defaults – NetScout Area D-7. . . . . . . . . . . . . . . . . . . .

Dynamic DLCI Alarm Defaults – NetScout Area D-8. . . . . . . . . . . . . . . . .

Contents

x 9820-A2-GB20-00March 1999

E Cables, Connectors, and Pin Assignments� Rear Panel E-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� COM Port Connector E-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

COM Port-to-Terminal Cable (3100-F2-540) E-2. . . . . . . . . . . . . . . . . . . . .

LAN Adapter Converter and Cable E-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EIA-232-D Crossover Cable (9008-F1-550) E-4. . . . . . . . . . . . . . . . . . . . .

� User and Network Data Port Connectors E-8. . . . . . . . . . . . . . . . . . . . . . . . . . .

X.21 Network Cable E-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

X.21 DTE Adapter Cable E-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

V.35 Network Cable E-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

V.35 DTE Adapter E-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EIA-530 Straight-through Cable (9008-F1-523) E-13. . . . . . . . . . . . . . . . . .

F Technical Specifications

G Equipment List� Equipment G-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

� Cables G-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary

Index

xi9820-A2-GB20-00 March 1999

About This Guide

Purpose and Intended Audience

This document contains information needed to properly set up, configure, andverify operation of the FrameSaver 9820, a frame relay monitor unit with ServiceLevel Verifier (SLV) functionality designed for international and multinationalapplications. It is intended for system designers, engineers, administrators, andoperators.

You must be familiar with the functional operation of digital data communicationsequipment and frame relay networks.

Document Organization

Section Description

Chapter 1 About the FrameSaver SLV Solution. Describes elementsof the FrameSaver SLV solution, as well as the features of9820 service level verifier units. A list of supported SNMPMIBs is also included.

Chapter 2 Management Control. Describes how you establish amanagement link and configure end-to-end managementcontrol.

Chapter 3 Typical Applications. Shows typical applications of theFrameSaver SLV unit in a frame relay network.

Chapter 4 User Interface. Shows how to navigate the user interface.

Chapter 5 Using the OpenLane NMS. Identifies the key features ofOpenLane NMS applications and describes setup andapplicable windows. Also includes service-levelmanagement reports information.

Chapter 6 Using NetScout Manager Plus. Identifies the key featuresof the NetScout Manager Plus application and theminimum hardware and software required to run theapplications. Also, describes setup and related windows.

About This Guide

xii 9820-A2-GB20-00March 1999

Section Description

Chapter 7 Using Concord’s Network Health. Identifies the keyfeatures of the Network Health NMS application and theminimum hardware and software required to run theapplications. Also, describes setup and related windows.

Chapter 8 Setup. Provides instructions for setting up the unit,including how to enter identity information and set up thedate and time on the screens.

Chapter 9 Configuration Options. Provides instructions for configuringthe unit, along with full descriptions of each option andpossible settings.

Chapter 10 Security and Logins. Provides procedures for controllingaccess to the FrameSaver SLV and setting up logins.

Chapter 11 Displaying System Information. Provides procedures todisplay unit identification information, and to display andinterpret status and statistical information.

Chapter 12 Operation and Maintenance. Provides information forstartup and monitoring the unit, dialing out to send SNMPtraps, maintaining call directories, downloading, andresetting the FrameSaver unit.

Chapter 13 Troubleshooting. Provides troubleshooting and testprocedures.

Appendix A Menu Hierarchy. Contains a graphical representation ofhow the user interface screens are organized.

Appendix B IP Addressing. Provides guidelines for selecting an IPaddressing scheme and shows examples of typicalschemes with subnet masks assigned.

Appendix C Standards Compliance for SNMP Traps. Describes theunit’s compliance with SNMP format standards and with itsspecial operational trap features.

Appendix D RMON Alarm Defaults. Describes the RMON-specific userhistory groups, and alarm and event defaults.

Appendix E Cables, Connectors, and Pin Assignments. Identifiescables used with the access unit and provides pinassignments for them, along with those of theconnectors/interfaces.

About This Guide

xiii9820-A2-GB20-00 March 1999

Section Description

Appendix F Technical Specifications.

Appendix G Equipment List.

Glossary Defines acronyms and terms used in this manual.

Index Lists key terms, acronyms, concepts, and sections.

Conventions Used

Convention Used When Used

Italic To indicate variable information (e.g.,DLCI nnnn).

Menu sequence: To provide an abbreviated method for indicatingthe selections to be made from a menu orselections from within a menu beforeperforming a procedural step.

For example,Main Menu→Status→System and Test Statusindicates that you should select Status fromthe Main Menu, then select System and TestStatus.

(Path:) To provide a check point that coincides with themenu path shown at the top of the screen.Always shown within parentheses so you canverify that you are referencing the correct table(e.g., Path: main/config/alarm).

Brackets [ ] To indicate multiple selection choices whenmore than one selection is available(e.g., Performance Statistics→Status→[Network/Port-1]).

Text highlighted in red To indicate a hyperlink to additional information.Click on the highlighted text (e.g., clicking onPerformance Statistics in Chapter 11 takes youdirectly to the Performance Statistics section inChapter 11, Displaying System Information.

About This Guide

xiv 9820-A2-GB20-00March 1999

Product-Related Documents

Document Number Document Title

Paradyne FrameSaver Documentation:

9000-A2-GK42 FrameSaver Standalone Unit Installation InstructionsSupplement

9820-A2-GL10 FrameSaver SLV 9820 Quick Reference

9820-A2-GN10 FrameSaver SLV 9820 Standalone UnitInstallation Instructions

Paradyne OpenLane NMS Documentation:

7700-A2-GB23 OpenLane DCE Manager for HP OpenView forWindows User’s Guide

7800-A2-GB26 OpenLane DCE Manager User’s Guide

7800-A2-GB28 OpenLane Performance Wizard User’s Guide

NetScout Documentation:

2930-170 NetScout Probe User Guide

2930-610 NetScout Manager/Plus User Guide

2930-620 NetScout Manager/Plus & NetScout ServerAdministrator 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 atwww.paradyne.com . Select Library →Technical Manuals.

To request a paper copy of this manual:

� Within the U.S.A., call 1-800-PARADYNE (1-800-727-2396)

� Outside the U.S.A., call 1-727-530-8623

1-19820-A2-GB20-00 March 1999

About the FrameSaver SLVSolution

1Overview

FrameSaver� SLV (Service Level Verifier) 9820 and 9820-C units add SLVfunctionality and intelligence to international locations when frame relay accessis provided via a separate network termination unit (NTU). For multinationalapplications, teaming international SLV units with North American-basedFrameSaver SLV units provides a complete global frame relay managementsolution.

International units have all the award-winning frame-aware diagnostics andQuality-of-Service (QoS) features that are common to all FrameSaver SLV units.The tools provided by FrameSaver SLV units allow customers and serviceproviders to monitor, diagnose, and fully manage their frame relay networks todeliver consistently higher levels of service.

Embedded with NetScout’s market-leading RMON (remote monitoring) probingtechnology, and supported by state of the art applications and reporting tools, theFrameSaver SLV solution delivers the industry’s most powerful frame relayoffering.

The FrameSaver SLV solution consists of the following elements:

� FrameSaver SLV units

— FrameSaver SLV 9820-C units for E1 sites, monitoring up to 120 PVCs(Permanent Virtual Circuits).

— FrameSaver SLV 9820 units for 64/128 kbps sites, monitoring up to8 PVCs.

� OpenLane� management solution

— DCE Manager application

— Performance Wizard application

� NetScout Manager Plus application

Optional standalone NetScout Probes can be used at sites where full 7-layermonitoring, an unlimited number of protocols, and advanced frame captureand decode capabilities are desired.

About the FrameSaver SLV Solution

1-2 9820-A2-GB20-00March 1999

FrameSaver SLV units provide the industry’s most accurate measurements ofservice level parameters, physical and logical PVC monitoring and diagnostics,Layers 1 through 3 monitoring, and full support of standards-based SNMP(Simple Network Management Protocol) and RMON (Remote Monitoring) forintegration and interoperability with third party management systems like ConcordNetwork Health.

The OpenLane management solution provides frame relay network visibility,control, nondisruptive diagnostics, and real-time and historical reporting tools forverification of SLAs (Service Level Agreements).

The NetScout Manager Plus application provides support for FrameSaver trafficand protocol analysis with expert frame capture and decode capabilities, anddisplays for protocol distribution and top talkers. If a NetScout Probe is installed, itprovides monitoring and protocol analysis for Layers 2 through 7. Combined withNetScout Manager Plus, capacity planning using baselining and trend reporting,as well as application analysis and utilization, are provided.

In the sections that follow, the features and benefits of each element of theFrameSaver SLV solution are discussed.

For additional information:

� See Chapter 3, Typical Applications, to see how to implement theFrameSaver SLV solution in your network.

� See Chapter 5, Using the OpenLane NMS, for OpenLane reports and otherinformation.

� See Chapter 6, Using NetScout Manager Plus, for additional NetScoutPerformance Plus information.

� See Chapter 7, Using Concord’s Network Health, for Network Health reportsthat apply to FrameSaver SLV units and additional information.

The FrameSaver SLV 9820 and 9820-C

The FrameSaver SLV units collect and store physical, frame relay, and protocolstatistics that can be accessed real time for troubleshooting, or retrieved on anetwork-wide basis at a scheduled time for historical report processing. Theseunits have unique PVC multiplexing capability, referred to as embedded DLCIs(EDLCIs), that permits multiple data streams to share a single PVC. This reducesboth customer and service provider costs.

See FrameSaver SLV Unit Features on page 1-5 for more about theFrameSaver SLV element of the solution.


1-39820-A2-GB20-00 March 1999

The OpenLane Management Solution

FrameSaver SLV units are managed by Paradyne’s preeminent OpenLanenetwork management solution for Unix or Windows-based systems. TheOpenLane solution consists of the following applications:

� DCE Manager

� Performance Wizard

OpenLane DCE Manager

This application is a powerful management system that runs from anHP OpenView console, and provides a real-time view of network and devicestatuses.

Some of its features include:

� Plug-and-play device discovery, full awareness of PVCs, and database-levelintegration into HP OpenView.

� Device identification and access to detailed health and status, alarms, tests,etc., information.

� Level 1 and 2 physical and logical frame relay monitoring and diagnostics(loopbacks).

� Enhanced SNMP trap processing to ensure that network trap icons reflect thealarm on the device.

� Real-time graphical representations of the device and all its interfaces.

� Device configuration.

� Telnet access to devices.

OpenLane Performance Wizard

OpenLane Performance Wizard is an advanced performance monitoringapplication that provides real-time and historical data collection for determiningnetwork performance and service level verification. This application gathersnetwork performance data from a FrameSaver SLV unit’s user-history collectionbuckets to provide an accurate view of network traffic at any time.

Some of its features include:

� Java-based, for operating system flexibility (it runs on UNIX or Windows).

� Real-time graphical displays of service level verification parameters – latency,availability, and frame delivery ratios (which includes the ability to reportaccurate measurements of dropped frames transmitted above or within CIR(Committed Information Rate).

Real-time displays include PVC throughput, data delivery analysis, transmitburst analysis, frame size distribution, physical link performance, networkutilization, diagnostics, and congestion data.


1-4 9820-A2-GB20-00March 1999

� Web-based daily, weekly, and monthly reports designed to verify frame relayservice level agreements.

� Automatic end-to-end PVC discovery and configuration to eliminate orminimize manual configuration and operator intervention.

� Enhanced navigation, with the intuitive standard folder concept (automaticallycreates folders that group devices) for network partitioning and circuit nameidentification, and search utilities for finding devices by their name.

� Enhanced diagnostic capabilities, with loopback and PVC testing.

OpenLane Performance Wizard also provides a direct link to the NetScoutManager Plus application. See Chapter 5, Using the OpenLane NMS, foradditional information.

NetScout Manager Plus

This application supports FrameSaver SLV units and NetScout Probes withcomplete LAN and WAN traffic analysis and monitoring functions. NetScoutManager Plus provides the following features for FrameSaver SLV units:

� Configurable thresholds for RMON 1 alarms and events.

� Performance monitoring using collected RMON 2 data.

— Protocol Directory and Distribution functionality allows FrameSaver SLVunits to measure up to eleven network-layer protocols and report theamount of traffic generated by each.

— IP Top Talkers and Listeners reporting identifies the devices usingnetwork bandwidth. The network’s top six users are identified.

— User history buckets to collect performance statistics from FrameSaverSLV units. Up to 900 samples can be stored in 15-minute buckets, with96 buckets in a 24-hour period, for up to five days worth of data.

See FrameSaver SLV Unit Features on page 1-5 for information about theFrameSaver SLV element of the solution.


1-59820-A2-GB20-00 March 1999

FrameSaver SLV Unit Features

The FrameSaver SLV product is a single, standards-based frame relaymonitoring solution that provides the following features:

� Service Level Verification. Provides a new set of service level verificationfeatures, often referred to as Quality of Service (or QoS) features:

— Ability to configure actual service level agreement parameters andthresholds.

— Intelligent verification tools for determining whether service levelagreements are being met, and for determining whether the network orthe customer’s data is the cause when they are being missed.

— Independent performance verification across the frame relay networkbased upon delay, or latency, throughput, and availability.

— Ability to collect accurate and detailed information about frame relaynetwork performance.

� TruePut Technology. Using Frame Delivery Ratios (FDR) and Data DeliveryRatios (DDR), FrameSaver units provide a method for precisely measuringthroughput, both within and above CIR. This proprietary method eliminatesinaccuracies due to averaging.

Delivery ratio features include:

— Frame Delivery Ratio within CIR (FDRc).

— Frame Delivery Ratio exceeding CIR (FDRe).

— Data Delivery Ratio within CIR (DDRc).

— Data Delivery Ratio exceeding CIR (DDRe).

— Total FDR for all frames transmitted.

— Total DDR for all bytes transmitted.

These ratios, available through OpenLane Performance Wizard’s SLVReports, are calculated by dividing the frames or bytes delivered (actuallyreceived by the far-end device) by the frames or bytes offered (sent).

� Frame Relay Aware. Provides support for diagnostic and networkmanagement features over the frame relay network, which:

— Supports multiple PVCs on an interface.

— Provides monitoring of CIRs on a per-PVC basis.

— Supports the LMIs (Local Management Interfaces) – Annex-A, Annex-D,and Standard UNI (User Network Interface) management protocol.

— Provides unique nondisruptive diagnostic capabilities.

— Supports inband management channels over the frame relay networkusing dedicated PVCs.


1-6 9820-A2-GB20-00March 1999

— Multiplexes management PVCs with user data PVCs using a patentedmultiplexing technique called embedded DLCIs (EDLCIs).

— Multiplexes multiple PVCs going to the same location, aggregating themonto a single network PVC using a patented multiplexing technique calledembedded DLCIs (EDLCIs).

� Router-Independence. Unique diagnostics, performance monitoring,PVC-based in-band network management, and SNMP connectivity is notdependent upon external routers, cables, or LAN adapters. As a result,you can:

— Get the network set up and running sooner.

— Stay in service longer.

— Return to service faster when there is an outage.

— Allow remote troubleshooting over the Internet.

During installation, this allows the integrity of the network endpoints to beverified before connecting the routers and DLCIs can be fully tested beforerunning production data.

� Inverse ARP and Standard RIP Support. Provides Inverse ARP (AddressResolution Protocol) support to the router connected to the user data port, ora dedicated PVC through the network so the frame relay router at one end ofa management PVC can acquire the IP address of the FrameSaver unit atthe other end of the PVC.

Setting a FrameSaver unit’s management PVC RIP (Routing InformationProtocol) option to Standard_out permits frame relay routers to automaticallylearn the routes to all FrameSaver units connected to this unit so the routesdo not have to be entered manually.

See Appendix B, IP Addressing, for additional information.

� Auto-Configuration . Provides automatic configuration to simplify the task ofconfiguring the FrameSaver unit.

Feature Description Benefit

Frame RelayDiscovery

Internal DLCI and PVCConfiguration – For each DLCIdiscovered and coming from thenetwork, the FrameSaver unitautomatically creates acorresponding port DLCI, thencreates a PVC that connects thetwo DLCIs within the unit.

Installation and setup costsare reduced since less timeand effort is required toconfigure the unit.

PVC Multiplexing – Using thedefault FR Discovery method(1MPort), a management DLCIis multiplexed with a user dataDLCI, turning two networkaccess points into one as itmoves through the network overa single PVC.

Network costs may beconsiderably reducedby consolidating twoindependent sources ontoa single PVC, saving aPVC charge.


1-79820-A2-GB20-00 March 1999

� Multiple Management Paths. Provides multiple communication methods forsending/receiving management data:

— Between the network management system and FrameSaver unit.

— Between the FrameSaver unit and a router or internet device through theCOM port.

— Using inband management on either the network or user data port toallow management via a dedicated network or user data port PVC, or amultiplexed network PVC.

SNMP (Simple Network Management Protocol) management is via anexternal SNMP management system using industry-standard andproduct-specific MIB (Management Information Base) objects.

Local management is through the COM (communications) port for anasynchronous terminal or NMS connection, and through a management PVCconnection configured for the user data port.

Remote management is achieved out-of-band using an external modem, orthrough a management PVC connection configured for the network data port.See Chapter 2, Management Control, for additional management information.

� Configuration Upload/Download and Software Download Capability.Provides quick, cost-effective software upgrades, and quick transfer ofconfiguration options to and from nodes using a standard file transfer protocol(FTP). Software and configuration download can occur through anymanagement link while the unit is running (in as short a time as 30 seconds).

Two software loads can be stored. See FTP File Transfers in Chapter 12,Operation and Maintenance, for additional information.

� IP Connectivity. Supports connectivity within an IP (Internet Protocol)network for up to 300 IP routes. Using the management paths describedearlier, provides IP routing for SNMP, Telnet, and file transfer protocol (FTP)message connectivity without requiring direct connections.

� Standards-Based Protocol Support. Supports two link-layer protocols forconnection to an external SNMP manager or network device via the COMport, and the three standard LMI protocols for communication over the framerelay interface.

Protocols Supported Description

Link-Layer Protocols Point-to-Point Protocol (PPP)

Serial Line Internet Protocol (SLIP)

Frame Relay LMI Protocols Standard

Annex-A – Specified by Q.933, Annex A

Annex-D – Specified by ANSI T1.617, Annex D

Routing Protocols Inverse ARP – Specified by RFC 2390

Standard RIP, Version 1 – Specified byRFC 1058


1-8 9820-A2-GB20-00March 1999

� Menu-Driven User Interface. Provides an easy to use, menu-driveninterface to locally or remotely configure, manage, maintain, and access theFrameSaver unit’s extensive diagnostic capability. The menu-driven userinterface is accessed using an async (or other VT100-compatible) terminal,PC terminal emulation, modem, or Telnet session.

� Two Customer-Specified Configuration Storage Areas. Allows quickswitching of the FrameSaver unit’s configuration. See Configuration OptionAreas in Chapter 8, Setup, for additional information.

� Data Port Rates. FrameSaver SLV units support the following interface rates:

Feature FrameSaver SLV Rates

Data Rates Network Data Port –

� 64 kbps and 128 kbps for remote site unit

� 64 kbps to 2048 kbps for central site unit

User Data Port – automatically set to the same rate usedat the network data port

COM Port:

� Asynchronous – 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and115.2 kbps

Standard Interfaces Network and User Data Port – EIA-530A, V.35, X.21

COM Port – EIA-232/V.24

� Maximum PVCs, EDLCIs, and Management PVCs. The number of remotesites and PVCs that can be created for each FrameSaver SLV unit issummarized in the following table:

Feature

Central-SiteFrameSaverSLV 9820-C

Remote-SiteFrameSaverSLV 9820

Monitored PVCs 120 8

Configurable DLCIs 242 18

Management Links 122 10

Monitored Network DLCIs 121 9


1-99820-A2-GB20-00 March 1999

� Extensive Monitoring Capability. Provides status information to help youkeep track of and evaluate the unit’s and network’s operation:

Via the . . . FrameSaver SLV Unit . . .

Status menu Provides information for:

� System and test status

� LMI-reported DLCI statuses for each interface

� Source and destination PVC (permanent virtual circuit)connection status for each interface

Performance Statistics

(See User HistoryStatistics Gathering)

Provides statistical data collection for:

� Physical interfaces

� Frame relay

LEDs

(faceplate, ordisplayed via theuser interface)

Provides unit and interface status for:

� Network data port

� User data port

See Statuses in Chapter 11, Displaying System Information, for additionalstatus information, and Displaying LEDs and Control Leads for LEDinformation.

� User-Selectable Ranges for Frame and Burst Sizes . Providesconfigurability for statistical data collection to increase measurement andplanning accuracy. This feature is only provided by Paradyne at this time.

Using OpenLane DCE Manager, upper and lower limits are set for eachbucket’s size, or range. Based upon these limits, data is deposited into theappropriate bucket. A bucket is all the data collected for a specified range.The data accumulated in these buckets is used for graphs and reports, andcan be used to trigger an alarm. Smaller buckets provide greater granularityacross a particular measurement range for troubleshooting problems.

� User History Statistics Gathering. Provides a complete view of the networkand user data port’s performance through the statistical data collected andassists when trying to determine the duration of a condition or event. In thisapplication, a bucket contains all the data gathered for a specified interval.Using NetScout Manager Plus, you can reconfigure the number of userhistory buckets to better fit your management needs.

Two default user history bucket intervals are used for collecting statistics:15 minutes and one day. Using these default settings, the FrameSaver unitcan collect, display, and store 24 hours of 15-minute buckets (96 buckets)and five 24-hour buckets simultaneously, providing up to five days of dailystatistical totals.


1-10 9820-A2-GB20-00March 1999

FrameSaver SLV Performance Statistics

SLV Statistics (Network DLCI):1, 2

� Far End DLCI

� Far End IP Address

� Inbound Dropped Frames

� Inbound Dropped Characters

� Dropped SLV Responses

� Average Round Trip Latency

� Maximum Round Trip Latency

DLCI Statistics (Network and User Data Port): 3

� DLCI Up Since and Up Time

� Tx and Rx Characters

� Tx and Rx Frames

� Tx and Rx Frames Within andExceeding CIR

� Tx and Rx Frames with DE

� Tx and Rx BECN Frames

� Rx FECN Frames

� Inactive Seconds 2

� Tx Frames Dropped 4

� Protocol Octets 2

� IP Top Talkers and Listeners 2, 4

� Tx Frames Dropped Above CIR 4

� Tx Frames Offered Above CIR 4

� Total Frames Offered 4

Frame Relay Statistics (Network and User Data Port): 3

� Frame Relay Link– Frames and Characters Sent and

Received– FECNs and BECNs Received– LMI Unavailable Seconds– All DLCIs, plus LMI Tx and Rx

Octets 2

– Total Tx and Rx Errors 2

– Total Rx CRC Errors 2

� Frame Relay Errors– Total Errors– Invalid Rx Frames– Short and Long Rx Frames– Invalid and Unknown DLCIs– Unknown Errors

� Frame Relay LMI– LMI Protocol– Status Message Received– Total LMI Errors– Number of Inactives

� Frame Relay HDLC Errors– Rx and Tx Total Errors– Rx and Tx Total Discards– Rx Overruns– Tx Underruns– Rx Non-octet Frames– Rx CRC Errors

1 Available through Telnet or the menu-driven user interface.2 Available through SNMP.3 RMON2 User History Group stores some of this information.4 Available on the Network interface only.

See Performance Statistics in Chapter 11, Displaying System Information, foradditional statistical information.


1-119820-A2-GB20-00 March 1999

� Extensive Testing Capability. Provides a variety of tests to diagnose device,network, and PVC problems, not just identify them. These diagnostic toolsfeature:

— Selectable RMON 2 buckets to control granularity of the data collected.

— Instantaneous and accurate burst and dropped packets analysis basedupon actual data, not averaging.

— Continuous background latency testing, run without interfering withnormal operation.

— Unique nondisruptive frame relay diagnostics, sent independent from therouter to facilitate troubleshooting and testing a DLCI before using it torun production traffic.

— Detailed information that helps determine the reason for missed SLAs,not simply alerting you to the existence of network problems.

— Local/remote line speed reporting to identify rate mismatches when thephysical limitations of the remote unit cannot handle the amount of trafficbeing transmitted.

— Information that helps operators understand the relationship betweennetwork alarms and SLA parameters being measured so they can betterprioritize corrective action, and avert system downtime and costs.

Diagnostic tests that can be selected include the following:

FrameSaver SLV Tests

PVC Tests

Network and User Data Port DLCI Tests:1

� PVC Loopback

� Send and Monitor Pattern

� Connectivity

Physical Tests

User Data Port Physical Tests:

� DTE Loopback

IP Ping (Verifies an operational end-to-end path.)

Lamp Test (For testing faceplate LEDs.)

Self-test – Automatically performed each time the FrameSaver unit is powered-onor reset. (Verifies that the unit’s internal components are operational.)

1 These tests are nondisruptive between FrameSaver units using multiplexedDLCIs.

You can perform all the same tests except for the IP Ping test and Self-test byusing SNMP MIB test commands when using the OpenLane DCE Manageras the user interface.

See Tests Available in Chapter 13, Troubleshooting, for additional testinginformation.


1-12 9820-A2-GB20-00March 1999

� Security. Provides multiple levels of security, which prevents unauthorizedaccess to the unit. Security can be controlled by:

Action How Controlled

Disabling any form ofremote access to the unit

Disable:

� SNMP Management – General SNMPManagement options

� Telnet Session – Telnet and FTP Session options

� FTP Session – Telnet and FTP Session options

� External Modem Commands – Disable Dial-InAccess

Requiring logins

(Applies to the terminal,Telnet and FTP.)

Combinations of a Login ID and password, andaccess levels.

Selectable access levels:

� Read only (Level-3)

� Limited access (Level-2)

� Full access (Level-1)

Specifying a communityname and access type

(Applies to SNMP only.)

SNMP Management must be enabled, which is thedefault setting – General SNMP Managementoptions.

� Enter Community Name 1 and 2

� Set Name 1 and 2 Access

Specifying selected NMSIP addresses andaccess type

SNMP Management must be enabled, which is thedefault setting – General SNMP Managementoptions.

Plus the following SNMP NMS Security options:

� Enable NMS IP Validation

� Enter the NMS IP Address

� Set the Access Type

See Chapter 10, Security and Logins, for additional information.


1-139820-A2-GB20-00 March 1999

SNMP Management Capabilities

The FrameSaver unit supports the SNMP Version 1, and has the capability ofbeing managed by any industry-standard SNMP manager and accessed byexternal SNMP managers using SNMP protocol.

The following MIBs are supported:

MIB Description

MIB II(RFC 1213 and RFC 1573)

Defines the general objects for use with a networkmanagement protocol in TCP/IP internets and providesgeneral information about the FrameSaver unit.

Frame Relay DTEs MIB(RFC 2115)

Defines objects for supporting the frame relay networkdata port.

RS-232-Like MIB(RFC 1659)

Defines objects for managing RS-232-type interfaces(e.g., V.35, RS-422, RS-423, etc.).

Frame Relay Service MIB(RFC 1604)

Defines objects for supporting the frame relay user dataport, and for supporting the network user data port whenthe FrameSaver unit is configured for back-to-backoperation (see Setting Up Units for Back-to-BackOperation in Chapter 12, Operation and Maintenance).

Enterprise MIB Supports execution of PVC tests, the display of DLCIconnections, and allows the entire contents of oneconfiguration area to be copied into another configurationarea.

RMON Version 1 MIB(RFC 1757)

Supports the following groups from RMON Version 1(RFC 1757):

� Ethernet Statistics Group (rmon 1) allows previousNetScout Manager Plus features to work.

� Alarm Group (rmon 3) for specifying alarms and theirbehavior.

� Event Group (rmon 9) for permitting event configurationand provide limited history of those events.

RMON Version 2 MIB(RFC 2021)

Supports the following groups from RMON Version 2(RFC 2021):

� Protocol Directory (rmon 11) and Distribution (rmon 12)Groups for displaying network-layer protocols on a perDLCI basis.

� Network Level Host Group (rmon 14) for monitoringnetwork-level host information.

� User History Group (rmon 18) for collection of statisticaldata.

Download Paradyne MIBs from our World Wide Web site atwww.paradyne.com . Select Service & Support → MIBs.


1-14 9820-A2-GB20-00March 1999

This page intentionally left blank.

2-19820-A2-GB20-00 March 1999

Management Control

2This chapter contains customer end user and service provider managementoverviews, followed by the steps needed to provide local and remotemanagement connectivity to the FrameSaver unit.

You need to select and configure:

� A method of local management connectivity for FrameSaver units.

� A method for end-to-end management connectivity across the network.

� An IP addressing scheme that fits the local and end-to-end managementconnectivity methods.

Examples illustrating various network configurations are included in each section.

� End User Management Overview on page 2-2.

� Service Provider Management Overview on page 2-3.

� Managing the FrameSaver Unit on page 2-4.

� Configuring Local Management Control on page 2-4.

� Configuring End-to-End Management Control on page 2-8.

Management Control

2-2 9820-A2-GB20-00March 1999

End User Management Overview

The optimal method for managing an end-user network is shown in the examplebelow. Using this method saves PVC charges because management data ismultiplexed with user data using a single PVC.

By accessing the remote units in-band, the remote units are notrouter-dependent, so trouble isolation is easier when there are LAN outages.

FrameRelayRouter

FrameSaverUnit

99-16281

FrameRelay

Network

FrameRelayRouter

FrameSaverUnit

CustomerNMS

FrameRelayRouter

FrameSaverUnit

CentralSite

CustomerBranch 1

CustomerBranch 2

PVCs ContainingMultiplexedManagementEDLCIs andUser Data

Physical Connection

PVC Connection (Using EDLCIs)

PVC Connection (Using Standard DLCIs)

Standard Local PVC

NTU

NTU

NTU

For details configuring in-band management links to the central and remote siteFrameSaver units, see Configuring Management PVCs in Chapter 9,Configuration Options.

Management Control

2-39820-A2-GB20-00 March 1999

Service Provider Management Overview

In the service provider example below, the service provider’s management data ismultiplexed with the user data using EDLCIs traveling between the customer’scentral site and the customer branches.

A dedicated PVC is configured from the customer’s central site to the serviceprovider’s network control center, so the customer’s entire network can bemanaged from the service provider’s network operation/control center using asingle PVC. This dedicated PVC carries only management data; no user data iscarried.

FrameRelayRouter

FrameSaverUnit

99-16280

NetworkControlCenter

FrameRelayRouter

FrameSaverUnit

CustomerNMS

FrameRelayRouter

FrameSaverUnit

CentralSite

CustomerBranch 1

ServiceProvider

NMS

CustomerBranch 2

FrameRelaySwitch

FrameRelaySwitch

FrameRelaySwitch

FrameRelaySwitch

Physical Connection

PVC Connection (Using EDLCIs)

PVC Connection (Using Standard Non-multiplexed DLCI)

NTU

NTU

NTU

The service provider’s diagnostic capabilities are greatly enhanced using thistopology. Service provider troubleshooting and management of the customer’snetwork is completely independent of the customer’s routers. PVC Loopbacksand Pattern tests can be performed without disrupting user data.

Management Control

2-4 9820-A2-GB20-00March 1999

Managing the FrameSaver Unit

Local management is accomplished through the following methods:

� User data port configured with a frame relay management PVC, with therouter providing RFC 1490 or Cisco encapsulation of the IP traffic.

� COM port configured as a terminal for access to the menu-driven userinterface using a VT-100 async terminal or compatible terminal or PC.

� COM port connected to the manager or router for an IP management linkusing either PPP or SLIP as the link layer.

� COM port connected to an external LAN adapter for Ethernet connectivity foran IP management link.

Remote management is accomplished via the following methods:

� Merging or multiplexing management data with user data, and transferringthe information over a specified network PVC.

� Dedicated frame relay PVC between FrameSaver units at each end of thecircuit for in-band management. This is required when communicating withnon-FrameSaver equipment.

� Management PVCs configured between the user data port andRFC 1490-compliant or Cisco encapsulation routers at one or both ends ofthe circuit to route management and user data through the same port to therouters.

� External modems connected to FrameSaver unit COM port and the NMS forout-of-band management.

Configuring Local Management Control

Local management methods are typically used at the central site or at largeregional sites, where the FrameSaver unit is colocated with the NMS. This isillustrated in the End User Management Overview, page 2-2.

When managing the FrameSaver unit locally, you can establish a managementlink by:

� Creating a Management PVC Between the Router and Unit Via the UserData Port on page 2-5.

� Creating a Separate Management Link Via the COM Port on page 2-6.

� Configuring an External Device (Connected to the COM Port) on page 2-7.

Management Control

2-59820-A2-GB20-00 March 1999

Creating a Management PVC Between the Router and UnitVia the User Data Port

The following configuration shows the management connection using anRFC 1490-compliant or Cisco frame relay IP router connected to the FrameSaverunit’s user data port.

As shown below, in-band management is accomplished through the dedicatedPVC between the frame relay router or FRAD and the FrameSaver unit.

99-16289

Frame RelayRFC 1490IP Router

WAN Link

FrameSaver Unit

FrameRelay

NetworkDCEPort

NetworkPort

UserData Port

• 2 Configured PVCs – 1 for Management Data – 1 for User Data• 1 Cable

Physical Connection

PVC Connection

Management DataUser Data

NTU

In this configuration, the FrameSaver unit depends on the router for managementconnectivity. User data PVCs share the same port as the management PVC. Noadditional cables need to be purchased.

The FrameSaver unit provides Inverse ARP and Standard RIP Version 1 supportfor the router being used for management. Using these features, which is thepreferred method, the router can automatically learn the IP address of allFrameSaver units at the other end of a management PVC so these routes do nothave 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 toensure that management traffic destined for the remote site units is routed to thecentral site FrameSaver unit. Once traffic gets to the central site FrameSaverunit, it is rerouted to the appropriate remote site FrameSaver units.

For remote FrameSaver 9x24 units running a software release prior to 1.2, andfor all remote FrameSaver 9120 and 9620 units, the central site FrameSaver unitwill 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 bereached.

See the Primary Link RIP option in Table 9-10, Management PVC Options, inChapter 9, Configuration Options, for additional Inverse ARP and Standard RIPinformation.

Management Control

2-6 9820-A2-GB20-00March 1999

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 belowshows a management link connected to the COM port for local access to anon-RFC 1490 router. The router must have an asynchronous interface runningPPP or SLIP link-layer protocol.

When the COM port is configured as the IP management link, the menu-drivenuser interface is accessible via Telnet. Once the interface is configured, itoperates 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 adaptercan be connected to the COM port to provide Ethernet connectivity.

99-16290

Frame RelayRouter or

Terminal Server(Non-RFC 1490)

WAN Link

FrameSaverUnit

FrameRelay

NetworkAUXPort

NetworkPort

COMPort

• 2 Cables – 1 for Management Data – 1 for User Data

User Data

Management Data

DCEPort

UserDataPort NTU

Physical Connection

PVC Connection

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 optionmust be disabled (set to None).

See Table 9-15, Communication Port Options, in Chapter 9, ConfigurationOptions, for information about the Communication Port options. See Table 9-12,Telnet and FTP Session Options for information about the Telnet options.

Management Control

2-79820-A2-GB20-00 March 1999

Configuring an External Device (Connected to the COM Port)

The FrameSaver unit can be managed remotely by connecting an external devicelike a modem or PAD (packet assembly/disassembly) facility to the COM port. Astandard EIA-232-D crossover cable is used.

99-16286

VT100 Emulationand Telnet or

NMS using SNMP

SNMPNMS

WAN Link

ExternalModem

FrameRelay

Network

PSTN

Async orVT100

Terminal

-or-

SimpleASCII

InterfaceFrameSaverUnit

COMPort

ExternalModem

EIA-232-DCrossoverCable

Using this out-of-band example, configure call processing using the ExternalModem (on Com Port) configuration options, selected from the Management andCommunication menu.

Menu selection sequence:

Main Menu → Configuration →Management and Communication →External Modem (on Com Port)

See Table 9-16, External Modem (on Com Port) Options, in Chapter 9,Configuration Options, for information about these options.

If connecting to an external device like an SNMP NMS management station or aLAN adapter, configure the Communication Port options Port Use to Net Link,then Link Protocol for PPP.

Menu selection sequence:

Main Menu →Configuration →Management and Communication →Communication Port

See Table 9-15, Communication Port Options, in Chapter 9, ConfigurationOptions, for information about these options.

Management Control

2-8 9820-A2-GB20-00March 1999

Configuring End-to-End Management Control

End-to-end management control methods are typically used for accessing remotesite units that are not colocated with the NMS. When managing the FrameSaverunit remotely, you can establish a management link across the network in one ofthree ways. You can:

� Use a shared PVC (embedded DLCI).

� Use a dedicated PVC.

� Use RFC 1490 routers for transparent management control.

Management Control Using PVC Multiplexing (EDLCI)

This is the preferred method for accessing remote site units that are notco-located with the NMS.

In the configuration below, the FrameSaver unit’s management data ismultiplexed with user data onto a single PVC, sharing the same PVC – sourceDLCI 20 to destination DLCI 60. There is one configured PVC through thenetwork – a shared PVC for management and user data.

99-16293

DLCI 20

FrameSaverUnit A

FrameRelay

Network

FramerSaver Unit B

DLCI 60

FrameRelayRouter Physical Connection

PVC Connection(Using Shared PVC)

FrameRelayRouter

Management andUser Data

ManagementData

UserData

NTUNTU

Using the Inverse ARP and Standard RIP features, the preferred method, therouter can automatically learn the IP address of all FrameSaver units at the otherend of a management PVC. If not using these features, map or subinterfacestatements must be added to the central site router to ensure that managementtraffic is routed appropriately.

If desired, higher priority may be given to DLCIs carrying user data. Whenconfiguring an embedded DLCI (EDLCI) for management data, the DE (discardeligible) bit may be set. When there is traffic congestion, the network first discardsthe management data since they are already marked discard eligible.


Management Control

2-99820-A2-GB20-00 March 1999

Management Control Using a Dedicated PVC

Management control through a dedicated PVC is typically used by serviceproviders to provide a single point of access (i.e., a standard, nonmultiplexedPVC), usually to the customer’s central site unit, to manage the customer’snetwork. See Service Provider Management Overview on page 2-3 for a typicalservice provider configuration.

Nonmultiplexed DLCIs must be used when in-band management communicationis desired between any non-FrameSaver unit and a FrameSaver unit.

99-16282

DLCI 60

FrameSaverUnit A

Physical Connection

PVC Connection(Using Dedicated PVC)

FrameRelay

Network

DLCI 20

Non-FrameSaverUnit B

FrameRelayRouter

ManagementData

NetworkOperation

CenterRouter

CentralSite

RemoteSite

NTUNTU

As shown in the example, in-band management is accomplished through thededicated PVC between the two units. Management data for non-FrameSaverUnit B (at the remote site) goes to FrameSaver Unit A first (at the central site) ,which then routes it into the dedicated PVC between the two units. Onlymanagement data is carried over the PVC – source DLCI 60 to destinationDLCI 20.

Using the Inverse ARP and Standard RIP features, the preferred method, theNOC router can automatically learn the IP address of the FrameSaver unit at theother end of a management PVC. If not using these features to access remotesites, or for older FrameSaver 9x24 (pre-1.2) or 9120 and 9620 units, map orsubinterface statements for those units must be added to the central site routerfor management traffic to be routed to the central site FrameSaver unit so it canbe rerouted to the appropriate remote site FrameSaver units.


Management Control

2-10 9820-A2-GB20-00March 1999

Transparent Remote Management Control Using RFC 1490 Routers

FrameSaver unit A can be managed locally via in-band management channelsusing a frame relay PVC that is configured on its user data port. When managingthe FrameSaver unit B remotely, FrameSaver unit A does not route IP traffic toFrameSaver unit B. Instead, IP traffic is transparently passed throughFrameSaver unit B as part of user data. The router then routes the managementdata back to FrameSaver unit B on the dedicated management PVC configuredbetween the router and the user data port of the FrameSaver unit.

The configuration below shows both local and remote management across thenetwork. Management data is being routed from frame relay Router A to IPRouter B, then being redirected by the router to FrameSaver Unit B. Bothmanagement and user data are carried over the same PVC; a separate,dedicated management PVC is not required.

FrameRelay

Network

98-16221

SNMP NMS

FrameRelay

RFC 1490Router A

FrameSaverUnit B

WANLink

FrameRelay

RFC 1490Router B

WANLink

FrameSaverUnit A

VT100Emulation

and Telnet orNMS using

SNMP

1 Cable2 PVCs

1 Cable1 PVC

1 PVC

Physical Connection PVC Connection

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 routerfailure.

3-19820-A2-GB20-00 March 1999

Typical Applications

3SLV Frame Relay Monitoring

FrameSaver 9820 endpoints provide SLV intelligence and visibility forinternational NTU-terminated lines. Typical applications include:

� FrameSaver SLV 9820-C unit at the central site, where E1 access speeds arerequired.

� FrameSaver SLV 9820 units at the remote sites, where 64/128 kbps accessspeeds are required.

The SLV (Service Level Verifier) application shown below provides RMON(remote monitoring) capability at the central and remote sites.

FrameRelayRouter

FrameSaver9820-C

Unit

99-16266

FrameRelay

Network

FrameRelayRouter

RemoteSites

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

Paradyne OpenLaneand NetScout

NMS Applications

CentralSite

NTU

NTU

NTU

NTU


3-2 9820-A2-GB20-00March 1999

When the FrameSaver unit detects a failure, the unit proactively notifies themanagement station so the management station can actively monitor networkconditions.

With FrameSaver SLV units in a network, the service provider can offer itscustomers the following services:

� Higher quality service

� Quick installation

� Quick problem resolution

� SLAs backed by accurate (not averaged) measurements

� Web-based reporting

Multinational Frame Relay Solution

For multinational applications, teaming FrameSaver 9820-C and 9820 units withNorth 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 diagnosticand service-level verification features in their frame relay networks, and theyrealize that these same features are needed at their international locations aswell if the company is to continue expanding globally.

The illustration below shows a multinational application.

99-16285

NorthAmerican

FrameRelay

Network

North AmericanLocation

FrameRelayRouter

World-WideLocation

FrameSaverSLV 9820-C

Unit

FrameRelayRouter

FrameSaverSLV 9820

Unit

NTU

NTU

FrameRelayRouter

FrameSaverSLV 9124

Unit

FrameRelayRouter

FrameSaverSLV 9128

Unit

World-WideFrameRelay

Network

CustomerNMS


3-39820-A2-GB20-00 March 1999

SLV Frame Relay Access

Typical RMON applications include a:

� FrameSaver SLV unit with RMON capability at the central site using aFrameSaver SLV 9820-C unit and FrameSaver SLV units with RMONcapability at the remote sites using FrameSaver SLV 9820 units, or

� FrameSaver SLV 9820-C unit and a NetScout RMON probe at the central siteand FrameSaver 9820 units at all remote sites.

The SLV application shown below provides RMON capability at the central siteand remote sites. This capability provides Physical, Frame Relay, and Networklayer protocol statistical buckets for remote troubleshooting and frame relay SLVmonitoring.

FrameRelayRouter

FrameSaver9820-C

Unit

99-16266

FrameRelay

Network

FrameRelayRouter

RemoteSites

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

Paradyne OpenLaneand NetScout

NMS Applications

CentralSite

NTU

NTU

NTU

NTU

When the FrameSaver unit detects a failure, the unit proactively notifies themanagement station so the management station can actively monitor networkconditions.


3-4 9820-A2-GB20-00March 1999

OpenLane Performance Wizard provides service providers or commercial endusers and their customers with SLV reports through the World Wide Web. TheNOC’s (network operation center’s) OpenLane management system must haveaccess to the frame relay network so the system needs to be inside the networkservice provider’s protective firewall. The SLV Reports Web server, which isoutside the firewall, enables communication with the customer Web browser andauthenticates customer logins for access to SLV data. This is shown in theexample below.

FrameRelayRouter

FrameSaver9820-C

Unit

99-16267

Frame RelayNetwork

FrameRelayRouter

RemoteSites

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

WebBrowser

CentralSite

SLV ReportsWeb Server

FrameRelaySwitch

FrameRelaySwitch

NOC NMSwith OpenLanePerformance

Wizard Application

NOC = Network Operation Center

NTU

NTU

NTU

NTU

Firewall

Customer access to SLV data is through a standard Netscape or Microsoft Webbrowser. The customer’s profile, which contains the login information andspecifies the device IP addresses that the customer is authorized to view,prevents unauthorized access to the SLV data. The customer enters the URL forthe customer’s subdirectory, enters the appropriate login, and selects a report.

See Creating OpenLane Service Level Management Reports in Chapter 5, Usingthe OpenLane NMS, for information about these reports.


3-59820-A2-GB20-00 March 1999

If LAN or application layer probing or packet capture capability is desired, aNetScout probe can be used with a FrameSaver 9820-C at the central site.

In the example below, a FrameSaver 9820-C is connected to NetScout’s probe,which is using NetScout’s NMS application to provide full Layer 1–7 probecapability at the central or regional site.

FrameRelayRouter

FrameSaver9820-C

Unit

99-16268

NetScoutProbe

FrameRelay

Network

FrameRelayRouter

RemoteSites

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

FrameRelayRouter

FrameSaver9820Unit

NetScoutNMS

Application

CentralSite

NTU

NTU

NTU

NTU

Diagnostic and statistical information is continuously collected every 15 minutesfor 24 hours by the FrameSaver SLV units, with daily totals for up to 5 days. Thisinformation continues to be collected, even when frequent communication withthe management station is not possible or desired due to bandwidth restrictionsor network outages. As a result, the NMS application does not have to usenetworking bandwidth and CPU time to repeatedly query the remote FrameSaverunit for information, reducing network load and maximizing use of the informationcollected.

FrameSaver units can also respond to multiple managers, and each managercan pick and choose from the information collected, selecting and collecting onlythe information that is important to them through internal thresholds in theNetScout NMS.


3-6 9820-A2-GB20-00March 1999

PVC Multiplexing Application

When FrameSaver units are at each end of the circuit, the FrameSaver unitprovides the ability to multiplex data of multiple DLCIs onto a single networkDLCI. This feature is referred to as PVC multiplexing. PVC multiplexing allowsPVC diagnostic tests to be run without disrupting data, and uses the followingnetwork configuration.

FrameRelayRouter

FrameRelay

Network

FrameSaverUnit

FrameSaverUnit

99-16283

FR FR FR FR

PVCs ContainMultiplexed

ManagementEDLCIs andUser Data FR = Frame Relay

Physical Connection

PVC Connection

FrameRelayRouter

ManagementData

UserData

NTU NTU

SNMPNMS

ManagementData

The example shows frame relay data coming in over Port-1, with the framesbeing multiplexed onto a single network connection.

This sharing of PVCs (i.e., multiplexing user DLCIs with managementdata/frames with user data/frames) is a proprietary method that is patented.When using this method:

� The first EDLCI, EDLCI 0, is used for the Port-1 data, and no overhead isassociated with the multiplexing for EDLCI 0. Subsequent DLCIs have twobytes of overhead associated with them.

� A diagnostic EDLCI, which is transparent to the user, is also created on eachmultiplexed DLCI on the network data port. This allows nondisruptive PVCdiagnostic tests to be run, as well as end-to-end communication of networklatency, topology, and data delivery information.

� A management EDLCI, EDLCI 2, is created to route management datathrough the network data port. This allows for nondisruptive multiplexing ofmanagement data with user data and provides router-independentmanagement of remote units.

To use this feature, the network DLCI Type must be Multiplexed.


3-79820-A2-GB20-00 March 1999

Using Auto-Configuration

When the Frame Relay Discovery feature is used, DLCI configuration and PVCconnection occur automatically. Based upon the network LMI status responsemessage, the FrameSaver unit “discovers” network DLCIs and captures thenetwork’s CIR (committed information rate), provided the network switch supportsthis feature (e.g., Stratacom switch DLCI, plus CIR). Network and Port interfaceDLCIs with the same number are created and connected automatically.

All automatically configured network DLCIs are multiplexed, allowing for thecreation of a management diagnostic EDLCI (embedded DLCI) being created.When management data is multiplexed with user data, two EDLCIs are createdfrom the network DLCI, one matching DLCI for user data on Port-1, and anotherone for management (Mgmt) information.

PVCs configured to non-Paradyne units should not be multiplexed because onlyFrameSaver models currently support PVC multiplexing and PVC diagnostics.However, when the unit at the other end is not a FrameSaver unit, PVCdiagnostic tests and SLV communication between FrameSaver units aredisruptive to user data.

The following illustrations show the DLCI records and PVC connections createdwhen a particular Frame Relay Discovery Mode is selected. The tables show theautomatic configuration that takes place within the FrameSaver unit.

Refer to Setting Up Auto-Configuration in Chapter 8, Setup, for additionalinformation.

This example shows the 1-port management application (1MPort).

FrameRelay

Network

99-16287

FrameSaver Unit

DLCI 201

Port 1

Network Sideof LMI

User Sideof LMI

DLCI 201

DTE

Network Port

Physical Connection

PVC Connection

Contains 2 EDLCIs: – User Data Port – Management (Mgmt)

Mgmt 201 NTU

FR DiscoveryMode Selection

SourceInterface

SourceDLCI

DestinationInterface/Link

DestinationDLCI

DestinationEDLCI

One port withManagement

Port-1 DLCI 201 Network DLCI 201 EDLCI 0Management(1MPort) Internal Mgmt201 EDLCI 2


3-8 9820-A2-GB20-00March 1999

The following example shows the 1-port, nonmanagement configuration (1Port).

FrameRelay

Network

99-16288

FrameSaver Unit

DLCI 201

Port 1

Network Sideof LMI

User Sideof LMI

DLCI 201

DTE

Network Port

Physical Connection

PVC Connection

Contains 1 EDLCI: – User Data Port

NTU

FR DiscoveryMode Selection

SourceInterface

SourceDLCI

DestinationInterface/Link

DestinationDLCI

DestinationEDLCI

One port withNo Management(1Port)

Port-1 DLCI 201 Network DLCI 201 EDLCI 0

Back-to-Back Operation

Back-to-back operation can be achieved by connecting two FrameSaver unitstogether, with no frame relay switches in the path, as in a test bench setup or forpoint-to-point configuration using a leased line. This configuration is useful forprivate frame relay networks, or for demonstrations when a frame relay circuit isnot available.

This configuration is shown in the illustration below.

99-16331

FrameSaverUnit

FrameRelayRouter

FrameSaverUnit

FrameRelayRouter

(CSU/DSU)NTU

(CSU/DSU)NTU

Leased LineNetwork or

Crossover Cable

DTE DCE DCE DTE

Using this feature, only one FrameSaver unit must be configured forBack-to-Back operation so it presents the network side of the UNI to the otherunit. 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 12, Operation andMaintenance, for additional information.

4-19820-A2-GB20-00 March 1999

User Interface

4Interfaces to the FrameSaver SLV

Your interfaces to the FrameSaver SLV unit are the front panel LEDs, themenu-driven user interface, and SNMP (simple network management protocol)network management. These interfaces provide feedback and status for theFrameSaver unit.

This chapter tells you how to set up and navigate the menu-driven user interface.

FrameSaver Unit’s Faceplate

The unit’s faceplate includes a number of LEDs (light-emitting diodes). SeeDisplaying LED and Control Leads in Chapter 11, Displaying System Information,for an understanding of what each LED indicates.

Menu-Driven User Interface

Access to the easy to use, menu-driven interface is provided through an async(asynchronous or other VT100-compatible) terminal, PC terminal emulation, or aTelnet session.

Network Management

Acting as an SNMP agent, the FrameSaver unit supports external managementby an SNMP manager via industry-standard and enterprise-specific managementinformation base (MIB) objects.

Refer to SNMP Management Capabilities in Chapter 1, About the FrameSaverSLV, for supported MIB objects.

User Interface

4-2 9820-A2-GB20-00March 1999

Menu Hierarchy

The menu hierarchy represents the organization of the FrameSaver unit’s menusand screens. Refer to Appendix A, Menu Hierarchy, for a pictorial view.

Main Menu Screen

Entry to all of the FrameSaver unit’s tasks begins at the Main Menu screen, whichhas five menus or branches.

Select . . . To . . .

Status View diagnostic tests, interfaces, PVC connections, andstatistics. Also, to display LEDs and access unit identityinformation.

View diagnostic tests, interfaces, PVC connections, andstatistics.

Test Select and cancel test for the FrameSaver unit’s interfaces.

Configuration Display and edit the configuration options.

Auto-Configuration Configure basic access unit setup automatically based upon aselected application.

Automatically populate network and data port DLCIconfiguration options with numeric settings.

Control Control the user interface for call directories, device naming,login administration, and selecting software releases.

Initiate a power-on reset of the FrameSaver unit.

NOTE:The login’s access level appears at the top of the screen unless no securityhas been set up.

User Interface

4-39820-A2-GB20-00 March 1999

Screen Format Types

Three types of screen formats are available on the async (asynchronous)terminal.

Use screen format . . . To . . .

Menu selection Display a list of available functions for user selection.(Refer to the Quick Reference or Appendix A for a pictorialview of the menu hierarchy.)

Input Add or change information on a screen.

Underlines in the field value or selection indicate an input oredit field.

Display Display configuration information and results fromperformance and system-specific tests.

No underlines in the field value or selection indicates adisplay-only field.

What Affects Screen Displays

What appears on the screens depends on:

� Current configuration – How your network is currently configured.

� Security access level – The security level set by the system administratorfor each user.

� Data selection criteria – What you entered in previous screens.

User Interface

4-4 9820-A2-GB20-00March 1999

Screen Work Areas

There are two user work areas:

� Screen area – Where you input information into fields.

� Function keys area – Where you perform specific screen functions.

Below is a sample async (asynchronous) terminal interface screen.

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

main/config/data ports/physical PARADYNE 9820Device Name: Node A 01/26/1999 23:32

DATA PORT PHYSICAL OPTIONS

Port Type: X.21Invert Transmit Clock DisableMonitor RTS (Control): Enable

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––Ctrl-a to access these functions, ESC for previous menu M ainMenu E xitSaveE530, V.35, X.21

Menu Path

ScreenArea

DeviceName

Model Number

Date and Time

FunctionKeys Area

Message Area

Screen Format Description

Menu Path Menu selections made to reach the current screen.

Device Name Customer-assigned identification of the FrameSaverunit.

9820 FrameSaver unit’s model number.

Screen Area Selection, display, and input fields for monitoring andmaintaining the FrameSaver unit.

Function Keys Area Specific functions that can be performed by pressinga specified key, then pressing Enter.

Message Area System-related information and valid settings forinput fields in the lower left corner.

System and Test Status messages in the lower rightcorner.

User Interface

4-59820-A2-GB20-00 March 1999

Navigating the Screens

You can navigate the screens by:

� Using keyboard keys.

� Switching between the two screen work areas using function keys.

Keyboard Keys

Use the following keyboard keys to navigate within the screen area:

Press . . . To . . .

Ctrl-a Move cursor between the screen area and thescreen 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 thelast 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 thesame screen.

Down Arrow or Ctrl-d Move cursor down one field within a column onthe same screen.

Right Arrow or Ctrl-f Move cursor one character to the right if in editmode.

Left Arrow or Ctrl-b Move cursor one character to the left if in editmode.

Ctrl-l Redraw the screen display, clearing informationtyped in but not yet entered.

Enter (Return) Accept entry or display valid options on the lastrow of the screen when pressed before enteringdata or after entering invalid data.

User Interface

4-6 9820-A2-GB20-00March 1999

Screen Function Keys

All screen function keys (located in the lower part of the screen; see the exampleon page 4-4) operate the same way (upper- or lowercase) throughout thescreens.

These keys use the following conventions:

Select . . .For the screenfunction . . . And press Enter to . . .

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 lete Delete data.

S or s Save Save information.

R or r Refresh Update screen with current information.

V or v PVCs Display PVC statistics for the selected interface.

C or c ClrStats Clear network performance statistics and refresh thescreen.

U or u PgUp Display the previous page.

D or d PgDn Display the next page.

User Interface

4-79820-A2-GB20-00 March 1999

Using the Menu-Driven User Interface

This section leads you through the basic operations of using the interface.

Selecting from a Menu

You select from a menu to get subsequent menus or screens so you can performdesired tasks.

� Procedure

To make a menu selection:

1. Tab or press the arrow keys to position the cursor on a menu selection. Eachmenu selection is highlighted as you press the key to move the cursor fromposition to position.

2. Press Enter. The selected menu or screen appears.

3. Continue Steps 1 and 2 until you reach the screen you want.

Refer to Appendix A, Menu Hierarchy, for a pictorial guide through menuselections.

Selecting a Field

Once you reach the desired menu or screen, select a field to view or change, orto issue a command. Press the Tab or right arrow key to select a field within amenu. The current setting or value appears to the right of the field.

Example:To change the test duration time from 10 minutes to 15 minutes:

Main Menu →Configuration →Load Configuration From: →CurrentConfiguration →General, Tab to the Test Duration (min) field, enter 15,then press Enter.

Example:To add or delete a login, select Control from the Main Menu, select AdministerLogins from the Control menu, then type n (New) or l (Delete) and press Enter.

Main Menu →Control →Administer Logins → [New/Delete]

User Interface

4-8 9820-A2-GB20-00March 1999

Making Input Selections

You can enter information into a field in one of several ways. Once the field isselected, you can:

� Manually type in (enter) the field value or command.

Example:Entering bjk as a user’s Login ID on the Administer Logins screen ( from theControl menu/branch).

� Type in the first letter(s) of a field value or command, using the FrameSaverunit’s character-matching feature.

Example:When configuring the communication port, with the RIP configurationoption/field selected (possible settings include None, Proprietary, andStandard_out), typing p or P displays Proprietary as the selection.

When a configuration option/field has multiple selections starting with thesame letter(s), the first value starting with the letter(s) entered are displayed.

� Switch from the screen area to the function keys area and select or enter thedesignated function key. See Switching Between Screen Work Areas belowfor an example.

If a field is blank and the System Messages and Field Values screen areadisplays valid selections, press the spacebar; the first valid setting for the fieldappears. Continue pressing the spacebar to scroll through other possiblesettings.

Switching Between Screen Work Areas

Using Ctrl-a allows you to switch between the screen area and function keys area(see page 4-4).

� Procedure

To access and use 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 thedesired function key.

Example:To save a configuration option change, type s or S (Save).

3. Press Enter. The function is performed.

4. To return to the screen area, press Ctrl-a again.

5-19820-A2-GB20-00 March 1999

Using the OpenLane NMS

5This chapter includes:

� OpenLane Management features.

� Installation and Setup of the OpenLane DCE Manager and PerformanceWizard on page 5-2.

� Viewing OpenLane Performance Wizard Graphs specific to FrameSaver SLVdata collection and display on page 5-10.

� Creating OpenLane Service Level Management Reports on page 5-22.

The OpenLane Advantage

OpenLane Management features:

� Nondisruptive tests from OpenLane NMSs

� Layers 1, 2 and 3 monitoring

� Real-time and historical focus

� 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

� Service level accounting and quality of service verification

� Web-based service level management reports


5-2 9820-A2-GB20-00March 1999

Using an OpenLane NMS Application

For additional information about accessing and managing the FrameSaver SLVunit through OpenLane DCE Manager and OpenLane Performance Wizard, andfor hardware and software requirements necessary to support these applicationsrefer to the:

� OpenLane DCE Manager User’s Guide to help you set up and configuredevices and their interfaces; and monitor, operate, and perform diagnostictesting using the Unix-based management application.

� OpenLane DCE Manager for HP OpenView for Windows User’s Guide tohelp you set up and configure devices and their interfaces; and monitor,operate, and perform diagnostic testing using the Windows-basedmanagement application.

� OpenLane Performance Wizard User’s Guide to query devices for both realtime and historical data, and to display graphs.

Installation and Setup of DCE Manager

OpenLane DCE Manager (Version 4.2.2 or higher) is used in conjunction with HPOpenView or NetView, and if performance graphs are wanted, used withOpenLane Performance Wizard, as well.

When adding FrameSaver SLV units to your network, follow the proceduresprovided in the appropriate DCE Manager User’s Guide:

� Install the OpenLane DCE Manager for Unix or Windows software and openthe application as specified in the applicable User’s Guide.

� Use the Autodiscovery feature to discover the new FrameSaver SLV units.

Refer to the appropriate User’s Guide for installation and setup, and informationabout accessing and managing the FrameSaver SLV unit through OpenLaneDCE Manager:

� OpenLane DCE Manager User’s Guide

� OpenLane DCE Manager for HP OpenView for Windows User’s Guide

Installation and Setup of Performance Wizard

Performance Wizard (Version 4.1 or higher) can be used alone, or it can beinvoked from an HP OpenView or NetView window. To use this application:

� Install the OpenLane Performance Wizard software and open the application.

� Add frame relay agents to the Navigation Wizard, unless using DCEManager.

� Set up historical data collection.


5-39820-A2-GB20-00 March 1999

Installing and Starting OpenLane Performance Wizard

Installation instructions are located in the OpenLane Performance WizardUser’s Guide. Open the application by following the instructions contained inGetting Started with the Performance Wizard. Depending upon your platform, seeone of the following procedures:

� Installing on Solaris, HP-UX, and AIX

� Installing on Windows NT or Windows 95

The OpenLane Navigation Wizard window opens. This window has threecolumns of information:

� End Point – Shows the devices in the network and their interfaces.

� Connection – Shows the PVC connections.

� Historical Collection – Shows whether historical data is being collected forthe interface or PVC.

Based upon the item that is highlighted, appropriate graph selection buttonsappear near the bottom of the window. Once a graph window is open, othergraphs 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 iconand the status message says Historical Daemon Running . If the HistoricalDaemon is not running, a red circle with a slash through it overlays the icon.


5-4 9820-A2-GB20-00March 1999

Adding FrameSaver SLV Units to Your Network

Use either one of these procedures to add FrameSaver SLV units to yournetwork.

� Procedure

To add an SLV unit from HP OpenView or NetView:

1. Use the HP OpenView or NetView autodiscovery feature to create submapsand discover an SLV unit.

2. Click on the submap containing the SLV unit, then click on the icon forthe unit.

3. Use the following HP OpenView menu selection sequence to accessNavigation Wizard:

Windows: Control →Performance Wizard →Navigation Wizard

Unix: Performance →Performance Wizard →Navigation Wizard

The OpenLane Navigation Wizard window opens so you can change or verifythe Community Name and view the graphs.

Refer to your DCE Manager User’s Guide for additional information.

� Procedure

To add an SLV unit from Navigation Wizard:

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 IPaddress or IP hostname appears in the Navigation Wizard device displayarea.

Refer to Populating the Device Display Area in Using the Navigation Wizardof the OpenLane Performance Wizard User’s Guide for additionalinformation.


5-59820-A2-GB20-00 March 1999

Setting Up for Collection of Historical Data

See the sample Navigation Wizard window on page 5-3. OK appears under theHistorical Collection column. In this example, historical data is being collected forperformance statistics on the Network Data Port of the 135.90.153.3 device.

� 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 usedfor each of the graphical views.

4. Click on the Active box for the graphical views wanted so a checkmarkappears in the box.

5. Select the Test button to verify that the data collection parameters arecorrect. OK should appear in the message area.

6. Select the OK button. The Edit Historical Collection dialog box closes, and anOK appears under the Historical Collection column for the interface or PVCselected, and for the device.

7. Click on Action at the menu bar, and select Start Historical Daemon if it is notcurrently running. Check the lower right corner of the Navigation Wizardwindow to see whether Historical Daemon is running (see the example onpage 5-3).


5-6 9820-A2-GB20-00March 1999

Accessing NetScout Manager Plus

A direct link to the NetScout Manager Plus application is provided by OpenLanePerformance 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 theleft side of the window).

Applicable icons appear on the right side of the main window.

Refer to Launching NSM in the NetScout Manager/Plus & NetScout ServerAdministrator Guide for information about how to start reports.


5-79820-A2-GB20-00 March 1999

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 Navigation Wizard, select a device’s DLCI so it is highlighted.

2. Click the right mouse button and select Connection... from the menu. TheEdit Connection dialog box opens, with the network collapsed.

3. Expand the remote network device in the device display area so that itsDLCIs are shown.

4. Select the appropriate DLCI so it is highlighted.

The selected DLCI numbers appear in the Connection Name field for bothends of the connection, which can be edited for a more meaningful name.

5. Select the Connect button. The Edit Connection dialog box closes and thePVC appears under the Connection column for the devices at both ends ofthe connection.

Repeat the procedure until all Port-1 DLCI connections have been defined.


5-8 9820-A2-GB20-00March 1999

Setting Frame and Burst Ranges

You can configure frame size and burst upper limits to:

� Match service level agreement parameters.

� Identify problem areas.

� Display the Frame Burst Breakdown graph.

� Assist in troubleshooting.

� Match the site’s traffic patterns.

� Procedure

To set frame and burst range parameters:

1. From Navigation Wizard, 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 theBurst Ranges tab in the background.

3. Select the Burst Ranges tab to bring it to the forefront if you want to set BurstRange Upper Limits.

The procedure for setting the frame size and burst upper limits is the same.


5-99820-A2-GB20-00 March 1999

4. Select a row in the box below the Frame Size Range Upper Limit (Octets) orBurst Range Upper Limit (Octets) heading so it is highlighted, and theselected value appears in the Edit box.

NOTE:If you change frame size ranges, the frame size distribution cannot bedisplayed by the NetScout Manager. Performance Wizard isrecommended 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 RangeUpper 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 thehighest 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 UpperLimits.

Getting Error Messages

Error messages may appear in the messages area at the bottom of the window toindicate when there is a problem (e.g., Unable to set table. SNMPError: No such name ). When this type of error occurs, you need toresynchronize with the FrameSaver unit.

� Procedure

To resynchronize:

1. Leave the current view and return to the Navigation Wizard main window.

2. Select Device Sync... from the File menu.

3. Return to the view where the error message appeared. The error messageshould be gone.

If the error message is not cleared, see the OpenLane Performance WizardUser’s Guide, or the Help feature, for additional information.


5-10 9820-A2-GB20-00March 1999

Viewing OpenLane Performance Wizard Graphs

The following OpenLane Performance Wizard graphs support FrameSaver SLVunits, integrating the new service level verifier capability provided by FrameSaverSLV units into Navigation Wizard:

� Frame Relay Access Channel Aggregated Summary – Capacity,Throughput, and Heaviest Users – Output

� Frame Relay Physical Link Integrity – Throughput, Errored Frames, LMISignaling Errors, and Unknown Protocol Frames

� Data Port Diagnostics – Currently under construction.

� PVC Throughput – Transmit and Receive

� Frame Relay DLCI Congestion – Capacity, Throughput, and Congestion

� PVC Data Delivery Analysis – Transmit Bit Burst Analysis As % CIR, RoundTrip Network Latency, End-to-End Data Delivery Success, and TransmitFrame Size Distribution

Status and error messages appear in the messages area at the bottom ofPerformance Wizard windows. If an error message appears, try andresynchronize with the FrameSaver unit.

The following sections show and discuss the frame relay windows that can beaccessed when monitoring a FrameSaver SLV unit.

Refer to the OpenLane Performance Wizard User’s Guide, or the Help feature,for additional information.


5-119820-A2-GB20-00 March 1999

Frame Relay Access Channel Aggregated Summary

For a complete view of an interface’s traffic, this graph summary brings togetherthe information needed to determine how well an interface’s, or link’s, capability isbeing utilized.

Correlate the time at which a problem occurred to the following graphs.

� Capacity – Shows what percent of the physical link is being used. Ameasurement is provided for both incoming and outgoing data. Thepercentage is based upon line speed.

� Throughput – Shows the actual volume of data in kilobits per second forboth incoming and outgoing data over a physical link. The line speed is alsoshown so you can easily see when the link’s physical capacity is about to beexceeded.


5-12 9820-A2-GB20-00March 1999

� Heaviest Users – Output – Shows which DLCIs are generating the mosttraffic over the frame relay link. Up to three high-volume DLCIs can beshown.

This information can be viewed in two forms:

— Graph – The data shown for each DLCI is a percent of the line speedover time. Up to three high-volume DLCIs can be shown.

— Pie Chart – The data shown for each DLCI is a percent of the total outputper the most recent snapshot.

NOTE:Position the cursor over a particular DLCI within the graph and press theright 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 isalso shown.

If errors occurred when transmitted data bursts exceeded line capacity, looking atthe Heaviest Users should indicate the DLCI(s) most responsible for the problem.Once identified, PVCs generating the greatest amount of traffic can be examinedfurther.

� Procedure

To immediately launch PVC graphs:

1. From within a Heaviest Users graph or pie chart, position the cursor over aDLCI segment.

2. Press the right mouse button to display the menu.

3. Select either the PVC Throughput or PVC Congestion graph, or PVC Analysisif viewing the aggregated summary for the network interface. See one of thefollowing:

— PVC Throughput for end-to-end connectivity between units at both endsof the PVC, and to see the types of errors that are being recorded byeach unit.

— PVC Congestion for if the PVC is exceeding its contracted committedinformation rate (CIR) and whether it is causing network congestion.

— PVC Analysis for a more complete view of network traffic. Only appearsfor a network interface.


5-139820-A2-GB20-00 March 1999

Frame Relay Physical Link Integrity

Use this grouping of graphs to relate actual throughput on the frame relay link tothe types of errors that are occurring. It can also be used to verify that thenetwork is operational and traffic is flowing normally.


� Throughput – Shows the actual volume of data in frames per second forboth incoming and outgoing data over a physical link. The line speed is alsoshown so you can easily see when the link’s physical capacity is about to beexceeded.

� Errored Frames – Shows a count of errored or discarded frames over aphysical link for both incoming and outgoing data.

� 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 errorsreceived on the link.


5-14 9820-A2-GB20-00March 1999

If Frame Relay for Data Port 1 was selected, compare LMI Signaling ProtocolErrors against the Unknown Protocol Frames graph to see how many of the LMIerrors were due to wrong protocol being used.

See Frame Relay Performance Statistics in Chapter 11, Displaying SystemInformation, for additional information.

Data Port Diagnostics

This window is still under construction.

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. Thelines 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 thedevice.

Link Status next to each device indicate the link’s current status. Each device isidentified using a connection name, DLCI name, and DLCI number.

The Throughput graphs for each device shows the input and/or output for eachdevice. Lines are shown for CIR, physical link speed, and input and output in bitsper second.


5-159820-A2-GB20-00 March 1999

Variables that could appear in the panes below each graph include:

Variable Displayed Indication

Frames Sent above CIR Number of transmitted frames that exceeded thecontracted CIR.

Frames Sent within CIR Number of transmitted frames that compliedwith CIR.

Frames Sent marked DE Transmit data on a management PVC is markeddiscard eligible, so the network can discard thelower-priority frame when there is congestion.

Frames discarded by the network Number of transmitted frames that weredropped.

Bytes Sent above CIR Number of transmitted bytes over the contractedCIR.

Bytes Sent within CIR Number of transmitted bytes within or under thecontracted 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, warningthat outbound frames may encounter congestionand 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 thatinbound frames may encounter congestion andmay be dropped.

FECNs seconds Duration over which FECNs were received.

Congested seconds Duration over which BECNs and FECNs werereceived.

BECNs and FECNs indicate network congestion issues. Frames marked DEindicate that the DLCI is partly responsible for the network congestion; the DLCIhas exceeded its contracted CIR.

When congestion is detected on the network, select the Congestion button underthe menu bar to verify whether the DLCI is the cause for the problem.

See Chapter 11, Displaying System Information, for additional information onthese types of errors.


5-16 9820-A2-GB20-00March 1999

Frame Relay DLCI Congestion

Although used primarily for capacity planning and CIR negotiations, this group ofgraphs can be used to assess whether a DLCI is contributing to networkcongestion.


5-179820-A2-GB20-00 March 1999


� Capacity – Shows how a DLCI’s capacity is being used for both incomingand outgoing data. When the DLCI’s allocated bandwidth is underutilized, it istime to renegotiate CIR and excess burst size agreements.

The DLCI’s capacity is calculated based upon its data rate and CIR, which isprovided in two graph views:

— % of Port Speed Capacity – Shows capacity calculated based upon theFrameSaver unit’s data rate.

— % of CIR Capacity – Shows capacity calculated based upon theFrameSaver unit’s CIR.

Compare how CIR and Line Speed on the graphs compare to the CIR andLine Speed that had been configured, seen near the top of the window. Thepercentages calculated are based upon those values.

When zero CIR has been configured, the speed of the link’s capacity is usedin the calculations instead of the speed of the DLCI’s allocated capacity.

These graphs are used primarily for capacity planning or in CIR negotiations.

� Throughput – Shows the actual volume of data in kilobits per second forboth incoming and outgoing data over a frame relay PVC. Throughput onlyappears when the port is connected to the frame relay network. CIR is alsoshown so you can easily see when CIR is being exceeded.

When the DLCI is exceeding CIR, trying to deliver more data than wascontracted for, check the Round Trip Network Latency and End-to-End DataDelivery graphs on the PVC Data Delivery Analysis window to verify that theDLCI is the cause of apparent network problems.

� Congestion – Helps determine the degree of traffic congestion on thenetwork, and the reason some frames may have been discarded by thenetwork.

The number of BECNs counted over time are shown. The network sendsBECNs as a warning that outbound frames may encounter congestion andmay 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 onlydifference should be the scale values along the left side of each graph, basedupon the measurement being shown.


5-18 9820-A2-GB20-00March 1999

PVC Data Delivery Analysis

For a more complete view of network traffic, this graph summary brings togetherthe information needed to determine the cause of frame relay lost packets and/orexcessive network latency. A patent is pending on this graphical report.

Network service providers can use this screen to help determine whether theirnetwork or the customer’s data was the cause for a missed service levelagreement (SLA).

You can view the Transmit Burst Analysis As % CIR and End-to-End DataDelivery Success graphs in either Bits or Frames by changing the radio buttonselection. In this example, the Frames radio button was selected.

� If Bits is selected, the Transmit Burst Analysis As % CIR graph is measuredin Total Mbps Tx, and the End-to-End Data Delivery Success graph ismeasured in Total Kbps Tx.

� If Frames is selected, both the Transmit Burst Analysis As % CIR andEnd-to-End Data Delivery Success graphs are measured in Total Frames Tx.


5-199820-A2-GB20-00 March 1999

In most cases, transmission characteristics of the customer’s data rather than thenetwork is the cause of apparent network problems. This summary allows you todetermine the following:

� Overutilization of the network, trying to deliver amounts of data well over CIR.

� Data frames that are too large or small.

� More packets are being sent than the receiving node can receive due todifferences in physical circuit capacity.

Any of these will cause the network switch’s egress queue to fill, increasinglatency and data loss.


� Transmit Bit Burst Analysis As % CIR – Shows network utilization burstingdetails to aid in determining the cause of frame relay lost packets and/orexcessive network latency. Tx Bit Burst Analysis is measured in megabits andshows the exact distribution of transmitted data in relation to the DLCI’s CIRand excess burst size.

The color displayed indicates whether the DLCI is or is coming close toexceeding its purchased CIR and excess burst size.

Color % of CIR Indication

Blue Less than orequal to 99%

Packets are within CIR.

Gold 100–199% Packets are at or over CIR.

Pink 200–299% Packets are two times greater than thecontracted CIR.

Aqua 300–399% Packets are three times greater than thecontracted CIR.

Yellow More than 399% Packets are four times greater than thecontracted CIR.

When zero CIR has been configured, the percentage breakdowns are basedon link speed instead of CIR.

If utilization is consistently under 50% of CIR, the CIR contracted for shouldbe downgraded. If over 100%, the DLCI may be ready for its CIR to beupgraded.

When a DLCI is overutilizing the network, compare the Tx Bit Burst Analysisgraph 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.


5-20 9820-A2-GB20-00March 1999

� Round Trip Network Latency – Shows how fast the network is movingtraffic. Latency is the amount of time it takes a frame relay frame to travelfrom one CPE end point to another and back. The times at which an averageof the frame relay frames are calculated is shown along the bottom, while thedelay is shown in milliseconds.

Any excessive spikes or increases in latency should be investigated further. Itcould indicate a network problem, or it could indicate that the DLCI isoversubscribed, exceeding CIR, and is sending frames that are filling up thenetwork switch’s egress queue, delaying network traffic.

To determine the exact cause of the delay, compare the Round Trip NetworkLatency graph against the following graphs to determine the cause:

— Transmit Bit Burst Analysis As % CIR to see distribution of transmitteddata in relation to the DLCI’s CIR.

— Transmit Frame Size Distribution to see the size of the packets that weretransmitted.

� End-to-End Data Delivery Success – Shows the exact number of bits thatwere successfully delivered, as well as those that did not get delivered to theend point node for a selected DLCI.

Data Delivery Success is measured in kilobits over time. The color displayedindicates 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 followinggraphs to determine the cause:

— Transmit Bit Burst Analysis As % CIR to see distribution of transmitteddata in relation to the DLCI’s CIR.

— Transmit Frame Size Distribution to see the size of the packets that weretransmitted.


5-219820-A2-GB20-00 March 1999

� Transmit Frame Size Distribution – Various service level agreementparameters may be based on frame size, which may contribute to latencyand frames being lost. This graph shows the size of the packets beingtransmitted, so you can compare frame size to your service level agreement.

Transmit Frame Size Distribution is measured over time in percent of alltransmitted 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.


5-22 9820-A2-GB20-00March 1999

Creating OpenLaneService Level Management Reports

Service Level Management (SLM) Reports, a segment of OpenLanePerformance Wizard, provides FrameSaver SLV network administrators with away of offering SLV Reports to their customers via the World Wide Web. Throughsecurely partitioned access, customers can create, view, and print SLV Reportspertaining to their portion of the network. Performance data is gathered from allFrameSaver SLV RMON-2 user history buckets at configurable polling intervalsand made available for the SLV Reports.

These reports include a summary of overall network performance, as well asdetailed statistics on a per PVC basis. They measure network latency, availability,and frame delivery success rate (throughput). Using proprietary TruePuttechnology, the reports provide accurate (not averaged) SLA verification becausethroughput within CIR as well as throughput above CIR is measured. Reports arealso available for physical inventory of the network’s device names, locations,serials numbers, DLCIs, and port speeds.

Once all devices have been added to the OpenLane Navigation Wizard database,FrameSaver SLV units can be polled in real time for troubleshooting andperformance monitoring. Based upon the configured intervals for user historydata collection, FrameSaver SLV data can be collected and retrieved forafter-hours report generation.

Web Browsers Supported

Users interact with the system via a Web browser. The following browsers arerecommended:

� Netscape Communicator 4.04 or higher

� Microsoft Internet Explorer 4.0

Service level management SLV Reports have been tested with the Apache Webserver, although other Web servers may work as well, including Web servers thatuse Secure Socket Layer (SSL) for data encryption. Be aware that encryptiongreatly slows system throughput. If the Apache Web server is not installed, referto the Apache Web site at www.apache.org for installation instructions.


5-239820-A2-GB20-00 March 1999

Installation and Setup of SLM Reports

Refer to the OpenLane Performance Wizard User’s Guide for installation andoperation instructions for the Performance Wizard, and follow the instructionsapplicable 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 andcustomers via the Web. You define the URL to access the SLV Reports, based onwhere 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 followingscreens differ, depending on whether you are

� Administering customer profiles and data collection as the networkadministrator, or

� Viewing selected reports as a customer.

Enter your customer ID. In the resulting pop-up window, enter your User ID orenter as an administrator, then your Password.

Reports Administration

As the network administrator, you have the ability to perform the followingfunctions:

� Create, modify and delete customer profiles. Customer profiles containinformation such as the customer’s name, account number, address(including e-mail), phone number, a contact name, and any additionalcomments. Customer profiles also contain the customer’s access level(either reports-only or administrative). Via customer profiles, you determinewhich Web server users have access to what FrameSaver SLV devices forthe SLV Reports.

� Modify authorized user logins. Determine which Web server users areauthorized to log in as the customer listed in the profile.

� Modify assigned devices. Determine which FrameSaver SLV devices in thenetwork the customer listed in the profile can access.

� Administer data collection. Enable data collection on devices that havealready been added to the OpenLane Navigation Wizard database. For datacollection, a 12-hour window is recommended. Any data collection errorscausing a delay of over 24 hours will result in a loss of data.


5-24 9820-A2-GB20-00March 1999

Viewing Reports

As a Web user with a customer profile defined by your network administrator, youhave 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-upwindow, the FrameSaver SLV Reports window displays, giving you theopportunity to select one of the reports.

For specific information on an SLV Report, refer to the SLM Reports online Help,which contains detailed information consisting of a description and typical usesfor each report. An example is also provided to show how a company could usethe information provided by this powerful tool.

6-19820-A2-GB20-00 March 1999

Using NetScout Manager Plus

6This chapter includes:

� Significant features of NetScout Manager Plus.

� Installation and setup of NetScout Manager Plus software.

� Configuration of NetScout Manager Plus.

Release 5.5 or higher of the NetScout Manager Plus software providesFrameSaver SLV-specific support.

The NetScout Advantage

NetScout Manager Plus features:

� Large central site location: Layers 2 through 7 monitoringRemote Probe location: Layers 1 through 3 monitoring

� RMON1 and RMON2 customization

� Flexible, customized, drill-down tool set

� Historical and real time analysis and reporting

� LAN, WAN, and switched LAN support

� Protocol analysis

� Threshold alarming

� Web access

� Familiar interface (almost identical to both Motif and Windows environments)

� Integrates with other management systems

See the sections that follow to make sure you have the necessary hardware andsoftware to support this application.

For the latest hardware requirements, see the NetScout Manager Plus Set Up &Installation Guide. For the latest software requirements, see the NetScoutManager/Plus & NetScout Server Administrator Guide.


6-2 9820-A2-GB20-00March 1999

Using a NetScout Manager Plus NMS Application

For additional information about accessing and managing the FrameSaver SLVunit through NetScout Manager Plus, refer to the:

� NetScout Manager/Plus User Guide to help you install the application,monitor traffic, and diagnose emerging problems on network segments.

� NetScout Manager/Plus & NetScout Server Administrator Guide to help youconfigure agents, remote servers, and report templates using the variousNetScout products.

� NetScout Probe User Guide to help you install and configure NetScout Probeon network segments you want to monitor, as shown in SLV Frame RelayAccess in Chapter 3, Typical Applications.

Installing NetScout Manager Plus

Installation instructions are located in the NetScout Manager/Plus & NetScoutServer Administrator Guide. Depending upon your platform, see either:

� Installing NSS/NSM/NSM+ Unix Version

� Installing NSS/NSM/NSM+ Windows Version


6-39820-A2-GB20-00 March 1999

Configuring NetScout Manager Plus

For the NetScout Manager Plus main window to appear, make sure yourenvironment is set up exactly as specified in your NetScout Readme file. You willneed to:

� Copy the OpenLane Performance Wizard directory to a user directory.

� Add frame relay agents to the NetScout Manager.

� Configure agent properties.

� Verify and correct domains and groups.

� Monitor the agent and DLCIs.

Before You Get Started

Before getting started, you need to copy some OpenLane Performance Wizarddirectories to a NetScout Manager Plus user directory. Performance Wizardprovides these directories as a starting point for loading new alarms and creatinghistory files. A template of alarms and values for configuring alarms and severaltemplates for creating history files specific to the FrameSaver unit are available.

The Performance Wizard paradyne directories include the following:

� Properties: paradyne.fsd file found in PerfWiz/netscout/alarms/directory

� Properties: paradyne.fst file found in PerfWiz/netscout/alarms/directory

� Alarms: slvtemplate.fct file found inPerfWiz/netscout/alarms/directory

� 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-8 and Creating HistoryFiles on page 6-13 for additional information.


6-4 9820-A2-GB20-00March 1999

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 theleft side of the window).

A list of configured frame relay agents appear in the list box below theName and IP Address headings. If this is a new NetScout Manager Plusinstallation, the list box below the selection bar is blank since no agents areconfigured yet.

3. Select the Admin radio button from the application selection bar (to the farright of the screen). Applicable configuration and administration icons appearin the box below the application bar.

4. Click on the Config Manager icon to open the Configuration Manager mainwindow.

5. Select the Add... button (down the center of the screen).

6. Minimally, enter the following:

— Agent name

— IP address

— Enter 4 for the frame relay logical interface to be monitored.

— Properties File: Select paradyne.

7. Select the OK button at the bottom of the screen to add the agent, discoverits DLCIs, and return to the Configuration Manager main window.

The frame relay agent just entered appears in the agent list box, with itsDLCIs 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 sureyou can communicate with the agent.

Refer to Adding Frame Relay Agents in the NetScout Manager/Plus & NetScoutServer Administrator Guide for additional information.


6-59820-A2-GB20-00 March 1999

Verifying Domains and Groups

� Procedure

1. From the NetScout Manager Plus main window, with the FrameRelay andAdmin radio buttons still selected, click on the Config Manager icon to openthe Configuration Manager main window.

2. Verify that only FrameSaver SLV-supported domains appear listed in theDomain 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 Groupcolumn.

— 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 theConfiguration Manager window.

If all these requirements are not met, a FrameSaver SLV-supported domainneeds to be added, or if an unsupported domain needs to be deleted, theProperties File must be edited.


6-6 9820-A2-GB20-00March 1999

Correcting Domains and Groups

Properties need to be edited when not using the Paradyne-provided file andwhen:

� An unsupported domain needs to be deleted.

� A missing domain needs to be added.

� Groups, Samples, Interval, and Logging are not configured as specified inStep 3 of Verifying Domains and Groups on page 6-5.

� Procedure

1. Select the the Property... button (down the center of the ConfigurationManager 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 domaindisappears 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 PropertyEditor window). The Edit Domain window opens.


6-79820-A2-GB20-00 March 1999

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 otherdomains.

Conversations (C) Protocols being used Disabled for all domains.

Logging Event logging Disabled for all domains andgroups.

5. Select the OK button (at the bottom of the screen) to apply the changes.

Refer to Configuring Domains in Properties Files in the NetScout Manager/Plus &NetScout Server Administrator Guide for additional information.


6-8 9820-A2-GB20-00March 1999

Adding SLV Alarms Using a Template

Once DLCIs have been discovered, SLV alarms should be configured andassigned to each DLCI. Paradyne provides a template for configuring alarms.DLCI alarms can be configured manually, but using the Paradyne alarm defaultstemplate 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 copiedand 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 allDLCIs 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-11.

NOTE:Perl must be installed in your system to use the eztrap utility in the procedurebelow. 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 Enter torun the eztrap utility to create alarm threshold values across all DLCIs for thecopied .fct file.

The message eztrap done appears when the .fct file is transferred.

3. From the NetScout Manager Plus main window, with the FrameRelay andAdmin radio buttons still selected, click on the Config Manager icon to openthe Configuration Manager main window (see the window on page 6-5).

4. Edit any alarm values that need to be changed.

5. Select the Install button (down the center of the Configuration Managermain window) to load alarms for the unit. This may take some time, soplease be patient.

See Editing Alarms on page 6-9 if any default settings need to be changed.


6-99820-A2-GB20-00 March 1999

Editing Alarms

� Procedure


2. Select the Custom radio button from the Properties File area (in the upperright of the window), then Property... (down the center of the screen).

The Custom Property Editor window opens.


6-10 9820-A2-GB20-00March 1999

3. Select a DLCI from the Trap list, and select the Edit... button (to the right ofthe list).

The Edit Trap window opens.

4. Edit any trap defaults that may be required. See Step 4 on page 6-12 for fieldsettings you may want to change.

5. Select the OK button (at the bottom of the screen) to apply your changes.The window closes and the Configuration Manager main window reappears.

6. Select the Install button (down the center of the Configuration Manager mainwindow) to apply your changes.

Refer to Editing Alarms in the NetScout Manager/Plus & NetScout ServerAdministrator Guide to change alarm thresholds.


6-119820-A2-GB20-00 March 1999

Adding SLV Alarms Manually

Once DLCIs have been discovered, SLV alarms should be defined and assignedto each DLCI.

When configuring alarms manually, every alarm must be configured for eachDLCI; that is, if there are eight alarms and 20 DLCIs, 160 trap configurationsmust be created (8 x 20). For this reason, it is recommended that the Paradynedefaults be used. Follow the procedure below to configure alarms manually.

To load Paradyne default settings for alarms, follow the procedure on page 6-8.

� Procedure


2. Select the Custom radio button from the Properties File area (in the upperright of the window), then Property... (down the center of the screen).

The Custom Property Editor window opens (see the window on page 6-9).

3. Select a DLCI from the Trap list, and select the Add... button (to the right ofthe list). The Add Trap window opens.


6-12 9820-A2-GB20-00March 1999

4. Click on the ... button to the right of indicated fields for a drop-down list fromwhich 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 The ifIndex for the frame relay logical interface is 1

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 Latency MIB variables should be Absolute; all others should be Delta.2 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 Configuring Alarms in the NetScout Manager/Plus & NetScout ServerAdministrator Guide for additional information.


6-139820-A2-GB20-00 March 1999

Creating History Files

Up to 14 additional user history tables can be created in the FrameSaver unit foreach 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 inNetScout Manager Plus to load a file that contains the OIDs (Object IDs) to bemonitored into the unit.

Paradyne provides several useful examples, including three files containing acomplete set of OIDs appropriate to the interface to be monitored: one for aDLCI, one for a frame relay link, and one containing system type OIDs. Any ofthese files can be used as a template when creating customized history filesspecific to the FrameSaver unit.

These files have a pdn*.udh (user-defined history) format and are found in thePerfWiz/netscout/userHistory directory. The userHistory files should bemoved to $NSHOME/usr so they can be used.

A separate *.udh file must be created and loaded for each DLCI or link that will bemonitored before a customized user history table can be loaded. Use a text editorto create these *.udh files by:

� Copying one of the interface-specific files (DLCI or link) and editing it usingone of the examples provided as a guide.

� Copying one of the examples provided and editing the extensions to fit theFrameSaver unit.

CAUTION:Two user history table files are already configured and installed in theunit, 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 besure your agent and DLCI lists are current. To rediscover agents and their DLCIs,select the Learn button on the NetScout Manager Plus main window (theFrameRelay and Admin radio buttons still selected).


6-14 9820-A2-GB20-00March 1999

� 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 userhistory table number.

3. Open the new file using a text editor.

The variables in the file are listed with their OIDs. The frame relay interfacenumber 101016002 must replace @IFN, and the DLCI number to bemonitored must replace @DLCI.

Example: frCircuitSentFrames Change “1.3.6.1.2.1.10.32.2.1.6.@IFN.@DLCI” to “1.3.6.1.2.1.10.32.2.1.6.101016002.301”

The only valid interface number for a FrameSaver 9820 or 9820-C is101016002.

4. Edit the new file, as needed.

Refer to Creating .UDH Files in Using Custom History of the NetScout ManagerPlus User Guide for additional information.


6-159820-A2-GB20-00 March 1999

Installing the User-Defined History Files

Once the user-defined history files have been created, the files need to beinstalled. History files are installed from the command-line prompt in NetScoutManager Plus. Should the FrameSaver unit be reset, these files will need to bereinstalled. The command used to install a new user history table is located in$NSHOME/bin.

CAUTION:Do not use user_history_table_1 or 2. UserHistory1 and UserHistory2are the default user history files used to keep SLV data for reports.Editing either of these files will destroy SLV reporting capability.

� Procedure

1. Type dvuhist -f agentname user_history_table_number confignumber_of_buckets interval download_file.udh to load user-defined historyfiles 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-definedhistory 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 UserHistory3on the History List.

See Step 5 in Monitoring a DLCI’s User History Data on page 6-17 to verify thatthe user-defined history files have been loaded.

Refer to Installing .UDH Files in Using Custom History of the NetScout ManagerPlus User Guide for additional information.


6-16 9820-A2-GB20-00March 1999

Monitoring a DLCI’s History Data

Once the monitoring variables have been defined, a problem DLCI canmonitored.

� Procedure

To monitor user history data:

1. From the NetScout Manager Plus main window, with the FrameRelay radiobutton 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 DLCIlist box (under the agent list box).

3. Highlight the DLCI to be monitored.

4. Click on the Custom History icon. The NetScout Custom History windowopens.

Adjust the size of the window so the entire report is shown.


6-179820-A2-GB20-00 March 1999

5. Select History List from the View menu. The History List window opens.

The newly defined user history variables should appear on this list.

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 maytake some time, so please be patient.

7. Select 2D or 3D Bar from the Format menu, if desired (3D Bar is shown).


6-18 9820-A2-GB20-00March 1999

Using the 2D or 3D Bar to view the user history data collected, you can clickon a particular bar and get an expanded view of the data.

8. Click anywhere on this window to return to the previous window view (seeStep 7 on page 6-17).

Refer to Launching User History and Understanding Custom History Display inUsing Custom History of the NetScout Manager Plus User Guide for additionalinformation.


6-199820-A2-GB20-00 March 1999

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 barare supported for FrameSaver SLV agents.

The procedure below describes how to monitor an agent’s traffic. The procedureis the same for protocol monitoring, but you may be prompted to select a DomainGroup as well as an agent or DLCI.

� Procedure

1. Select the Traffic radio button to monitor the newly added agent, or one of itsDLCIs.

2. Highlight an agent in the agent list box so that its DLCIs appear in the DLCIlist box (under the agent list box).

3. If you want to monitor one of the agent’s DLCIs, highlight the DLCI to bemonitored.

4. Click on an applicable icon. The selected graphical report should open.

Traffic icons that would be of particular interest are Traffic Monitor andDomain History. In the example below, the Domain History icon was selected,which is actually a real-time report.


6-20 9820-A2-GB20-00March 1999

NOTE:If Size Distribution is the selected View and distribution size has beenchanged via OpenLane Performance Wizard, the values shown for thedistribution 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 aresupported for FrameSaver units. For example, All Convs (conversations) andTopNConv icons appear when the Protocol radio button is selected, butconversations are not supported.

Of the icons that appear on the NetScout Manager Plus main window, thefollowing are supported:

Traffic Statistics Protocol Statistics

Traffic Monitor Protocol Monitor

Segment Zoom Protocol Zoom

Segment Details1 TopNTalkers

Domain History1 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 forFrameSaver 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 >1518statistics appear in the 1024..1518 bucket).

Conversations and Long-Term and Short-Term Histories are not supported in thisrelease. As a result, no data will appear on windows that include these panes.

7-19820-A2-GB20-00 March 1999

Using Concord’s Network Health

7Information concerning Concord Communication’s Network Health software as itrelates to FrameSaver SLV units is provided in this chapter. This chapterincludes:

� Significant features (listed on page 7-2) of Concord’s Network Healthsoftware.

� Installation and Setup of Network Health and reports on page 7-3.

� Viewing Network Health Charts and Tables on page 7-8.

Network Health Compatibility

Concord Communication’s Network Health is a family of Web-based softwareapplications that automate the collection, analysis, and reporting of criticalnetwork information.

The Network Health family of application solutions addresses performancemanagement at multiple levels of an enterprise network. Network Health includesa powerful and integrated relational database, and a graphical console andWeb-viewing system. It also has scheduling and grouping capabilities.

Network Health discovers and collects vital data from your network devices andIT infrastructure, then condenses critical information into graphical presentationsneeded to run your business. The result is a correlated, end-to-end view of yournetwork and IT infrastructure so that you can fully understand and measure theeffectiveness of your enterprise IT investment.


7-2 9820-A2-GB20-00March 1999

Features

Concord’s Network Health features:

� All device and layer monitoring

� RMON2 support

� Historical analysis and reporting

� A summarized view of your network, with individual element reports

� Service level and charge-back reports

� Capacity, load, baseline, and drill-down reports

� Automatic trend analysis and early warning of upcoming issues

� Web access, with zoom-in links for detailed views

� Easy interface that works with existing network management platforms

� Collection and storage of data for up to two years

� Web-based Traffic Accountant option for concise, easy-to-understandmanagement reports that relate network performance, growth trends, andcost directly to users and business units

See subsequent sections to make sure you have the necessary hardware andsoftware to support this application.

For the latest hardware and software requirements, see the Network HealthInstallation Guide or check Concord’s Web site at www.concord.com .

NOTE:Network Health has just released the first in a series of software modules thatintegrates FrameSaver SLV enhanced performance statistics into its reportingpackage (see the At-a-Glance report on page 7-38). To get this report, youneed Network Health R4.01 or higher.

Using Concord’s Network Health NMS Application

For additional information about installing, accessing, and managing theFrameSaver SLV unit through Concord’s Network Health, refer to:

� Network Health Installation Guide to help you install the application.

� Network Health User Guide to help you get started using the application.

� Network Health Reports Guide to help you understand and use Frame Relayreports.

� Network Health – Traffic Accountant Reports Guide to help you understandand use Traffic Accountant reports.


7-39820-A2-GB20-00 March 1999

Installation and Setup of Network Health

Refer to the Network Health Installation Guide for installation instructions, andfollow the instructions applicable to your network platform.

Before starting the installation:

� Verify the amount of disk and swap space required for your network.

� Make sure that your operating system is appropriately configured.

� Have user account information ready so you can access licensedapplications.

To use this application:

� Install the Concord Network Health software and open the application.

� Enter license information from the Network Health License Information formso specific Network Health applications can be used.

� Discover network elements, devices, and interfaces in the network.

� Configure the Network Health applications, then save them.

� Organize elements into groups for reporting purposes.

� Set up and run reports.

Each Network Health application provides a different set of functions, called amodule. Each module used requires a separate license to gain access to thosefeatures and functions. Make sure that you license the Poller application so youcan poll SLV units and collect data.

Setup and operation information is contained in the Network Health User Guide.The sections that follow address only the minimal procedural steps needed onceyou have access to the applications.

See the Network Health User and Reports Guides for additional startupinformation and a full discussion of the application’s features and how to usethem.


7-4 9820-A2-GB20-00March 1999

Discovering FrameSaver Elements

Once licenses are entered to provide access to the applications, the Discoverdialog box opens. Use this dialog box to search for SLV units in your network anddiscover their DLCIs. Saving the results creates definitions in the PollerConfiguration, which are used to poll the units.

IP addresses and the Community String (Community Names in the FrameSaverunit) must be entered so that Network Health can find the SLV units on thenetwork 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:

� Statistics elements – Provide counters and other gauges gathered aboutyour network for statistical and trend analysis.

� Conversation elements – Provide RMON2 and similar data gathered aboutnetwork traffic between nodes.

� Procedure

To find SLV unit 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 for the SLV units to be located, and the CommunityString (Community Name in the FrameSaver unit). Community String iscase-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 ofexisting elements updated when the discovery process is complete.Depending upon the number of units entered, it could take anywhere from afew 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 additionalinformation and how to schedule automatic element discovery updates to thedatabase.


7-59820-A2-GB20-00 March 1999

Configuring the Discovered Elements

Network Health sets the speed for discovered elements when it polls the unit forthe first time. For the FrameSaver SLV unit, the speed set would be the unit’sCIR. No additional configuration should be required. However, you should verifythat all appropriate information has been retrieved.

If a FrameSaver SLV unit does not have CIR configured, or configured correctly,Network Health sets the unit’s CIR to 0 kbps. For this reason, you shouldreconfigure the unit’s CIR before Network Health polls it. If 0 kbps is the speedsetting, you will need to edit the unit’s CIR from Network Health.

Additional information that can be edited includes:

� Element name

� Community string

� Polling status and rates

� SNMP index for the interface

� Agent type

� Desciption information

See Discovering Elements in the Network Health User Guide for additionalinformation.

� Procedure

To change the CIR for FrameSaver SLV unit elements from Network Health:

1. Select the Edit Before Saving button at the bottom of the Discoveringdialog box once the discovery process is completed.

The Poller Configuration window opens.

2. Double-click on the first element discovered. The Modify Element dialog boxopens.

3. In the Speed box, select the Override radio button and enter the CIR for theunit in the text box.

Letters k and m can be used as shortcuts (e.g., enter 56 k for 56,000 bitsper second, or 16 m for 16 Mbits per second).

4. Apply your changes:

— Select the Apply/Next button to save your change and bring up the nextelement to be edited. Continue until all newly discovered frame relayelements have been modified before selecting the OK button.

— Select the the OK button.

The Modify Element dialog box closes.


7-6 9820-A2-GB20-00March 1999

5. Select the OK button at the bottom of the Poller Configuration window.

The modified elements are saved to the database, and the units are polled.

Allow Network Health to continue polling for about a half an hour to allow timefor data to be gathered before running any reports.

Grouping Elements for Reports

Once the discovery process is completed and required changes are made, thenewly discovered elements (DLCIs) should be organized into a group for Healthreporting. Grouping makes for easier monitoring and management of similar nodetypes (e.g., all SLV elements). Once grouped, you can then run reports on allDLCIs 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 AddGroups 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 specificDLCIs, then select the left arrow button.

The highlighted DLCIs move from the Available Elements list to theGroup Members list.

5. Select the OK button when all appropriate DLCIs have been moved to theGroup Members list.

The Add Groups dialog box closes and the newly created group appears onthe Groups dialog box.

See Managing Groups and Group Lists in the Network Health Reports Guide foradditional information. It also tells you how to customize reports.


7-79820-A2-GB20-00 March 1999

Generating Reports for a Group

Once Network Health has had sufficient time to gather data from the polled DLCIsand the DLCIs have been grouped, you can start generating reports. Thefollowing are defined when specifying a report:

� Report to be run

� Group

� Daily, a specific day(s) of the week, weekly, or monthly report

� Destination of the report

NOTE:Not all reports can be ordered or scheduled on a monthly basis. See theNetwork Health Reports Guide to determine what reports can be generatedon 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 checkmark 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. Thewindow closes when the report screen comes up or the report is printed.

See Running Reports from the Console in the Network Health Reports Guide foradditional information. It also tells you how to schedule automatic reportgeneration.


7-8 9820-A2-GB20-00March 1999

Viewing Network Health Charts and Tables

Network Health already supports the service level verifier capability provided byNetScout probes and FrameSaver SLVs. The following frame relay reportssupport frame relay and SLV capability:

� Exceptions Reports – Provide summary and detail information that identifiesDLCIs with the highest incidence of errors, high bandwidth utilization, andtrends (see page 7-17).

� Summary Reports – Provide summary information for the network, volumeand error leaders, and DLCI traffic.

— Network Summary Report – Provides an overall view of the network (seepage 7-19).

— Leaders Summary Report – Identifies DLCIs having the highest volumeand errors (see page 7-22).

— Elements Summary Report – Compares DLCI traffic with volume and thebaseline, bandwidth utilization, and errors (see page 7-25).

� Supplemental Report – Shows DLCI availability and latency (seepage 7-27).

� Service Level Reports – Provide summary information for a group list for alonger reporting period than other reports.

— Executive Service Level Report – Provides service level information foran enterprise (see page 7-29).

— IT Manager Service Level Report – Provides service level information forvarious groups (see page 7-31).

— Customer Service Level Report – Provides service level information forcustomers (see page 7-33).


7-99820-A2-GB20-00 March 1999

� At-a-Glance Reports – Provides consolidated DLCI and networkperformance information onto a single page.

— At-a-Glance Report – Consolidates bandwidth utilization, network traffic,events occurring over the reporting period, and availability and latencylevels information (see page 7-36).

— Paradyne FrameSaver SLV Plus At-a-Glance Report – Consolidatestransmit burst analysis, network latency, dropped frames, frame sizedistribution, and availability information (see page 7-38).

� Trend Reports – Performs trend analysis on up to ten specified variables forDLCIs (see page 7-40).

Information is provided with each chart or table, generally referred to as a report.Click on the hyperlink (Explanation of ...), which explains what the chart isshowing, where the information comes from, etc.

When requesting frame relay summary reports, you must specify whether youwant the reports for the previous day or week.

� When previous day is specified, data summary charts for the day areprovided, with tables providing hourly details.

� When previous week is specified, data summary charts for the week areprovided, with tables providing daily details.

The sections that follow briefly describe key charts and tables used whenmonitoring the frame relay network and DLCIs. Refer to the Network HealthReports Guide for additional information about the charts and tables provided inthese reports, as well as other reports provided by Network Health.


7-10 9820-A2-GB20-00March 1999

About Service Level Reports

For long-term analysis and reporting, you will want to license the Service LevelReports application. This application analyzes data collected over months, or byquarters, and provides service level information about an enterprise, a region,department, or business process. Executive, IT Manager, and Customer ServiceLevel reports are provided.

Using these reports, you can measure service performance against goals andagreements. Ranges for service level goals can be set for up to five variables:availability, bandwidth, bytes, health exceptions, and latency. These ranges needto be set before reports are scheduled.

About the At-a-Glance Reports

At-a-Glance Reports consolidate various important DLCI and networkperformance indicators onto a single page. Up to ten DLCIs can be included in anAt-a-Glance Report.

Using the report on page 7-36, you can compare a DLCI’s volume with thenetwork’s performance over a specified period of time. Ranges for service levelgoals can be set for up to five variables: availability, bandwidth, bytes, healthexceptions, and latency. These ranges need to be set before reports arescheduled.

Using the report on page 7-38, all the enhanced network statistics that only aFrameSaver SLV unit can accurately collect is provided so you can truly monitorthe health of the frame relay network and see the effects of the customer’sutilization on network efficiency.

About Trend Reports

By specifying specific variables like bandwidth, trend analysis can be performedand shown on Trend Reports. Up to ten variables for a DLCI, or ten DLCIs on onevariable can be generated on a single trend report. Information can be presentedin a line graph, pie chart, bar chart, or table format. Any amount of time can bespecified for the reporting period.

These reports can help identify the reasons a DLCI has acquired a poor HealthIndex rating. See the Exceptions Report on page 7-17 for information aboutHealth 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-119820-A2-GB20-00 March 1999


7-12 9820-A2-GB20-00March 1999


7-139820-A2-GB20-00 March 1999


7-14 9820-A2-GB20-00March 1999


7-159820-A2-GB20-00 March 1999


7-16 9820-A2-GB20-00March 1999


7-179820-A2-GB20-00 March 1999

Reports Applicable to FrameSaver SLV Units

This section identifies the Network Health reports that apply to FrameSaver SLVunits, summarizes relevant information, and tells you how to use the reports.

Exceptions Reports

These reports identify those DLCIs that have exceeded a specified number ofaccumulated exception points.

The Exception Summary and Detail reports are explained below.

� Exception Summary Report – Lists DLCIs with the greatest number ofexception points beyond the specified minimum. The most critical DLCIs areat the top of the list. DLCIs can be listed more than once if more than oneproblem condition has been experienced.

The total number of exception occurrences and the type of condition causingthe DLCI to be added to this report are shown. Select the detail report foradditional information.

� Exceptions Detail – Shows additional information about the condition, likethe time at which the condition was occurring, or when threshold will bereached. A thumbnail Trend chart is also provided, tracking the condition’sbehavior.


7-18 9820-A2-GB20-00March 1999

Exception points are assigned based upon the DLCI’s Health Index rating, trendanalysis performed for each problem condition experienced, as well as when newerrors suddenly occur.

It is a good idea to run this report daily so that DLCIs having the most problemscan be attended to first. DLCIs contained on this report need immediate attention.

� The Health Index is the sum of grades assigned for all problem conditions,or variables, encountered by a DLCI. A grade is assigned for a DLCI basedupon the threshold ranges set for each variable and the period of time thatthe condition existed. The grades for all three problem conditions are addedtogether to form the Health Index rating for the DLCI. The higher the HealthIndex rating, the more exception points assigned. The lower the Health Indexrating, the healthier the DLCI.

The table below shows the default frame relay Health Index threshold ranges,and the grades assigned to each range.

VariableExcellentGrade = 0

GoodGrade = 2

FairGrade = 4

PoorGrade = 8

Utilization 0–100% 100–125% 125–150% over 150%

Congestion 0–1000 1000–3000 3000–5000 over 5000

Errors 0–1000 1000–3000 3000–5000 over 5000

� Trend analysis is performed on each exception condition to try andanticipate when the DLCI will reach threshold.

Steepness of the trend line is also evaluated to determine how quickly thatthreshold will be reached. Exception points are added accordingly. The closerthe threshold, the more exception points are assigned, and the higher theHealth Index rating.

See the Situations to Watch table on page 7-21 of the Network Summaryreport for additional information.

� Sudden new errors can occur after a DLCI has been error-free for aminimum of eight days, then suddenly has new errors that put it on thesereports.

If a DLCI is suddenly showing up on these reports, check whether any newequipment has been added to the network and whether it is configuredproperly. If its configuration is correct, the equipment could be faulty.

Exception reports can be customized. See Customizing the Exception Reports inthe Network Health Reports Guide.


7-199820-A2-GB20-00 March 1999

Network Summary Report

This set of charts and the table provides a summary of the frame relay network.


7-20 9820-A2-GB20-00March 1999

The charts and table contained in this report include:

� Total Network Volume by Week (or Day) – Shows network traffic on aweekly or daily basis, each bar representing a week or a day, dependingupon how the report is set up. If set up for:

— Previous day, up to 56 days may be shown.

— Previous week, up to 8 weeks may be shown.

The total volume of data passing through the network is in either bytes, usinga floating scale, or percentage of bandwidth utilization. As network dataaccumulates, regular patterns of network traffic emerge, which can be usedfor decision-making and capacity planning.

� Average Network Volume by Day – Averages network traffic for all DLCIsduring the baseline period on either a daily or weekly basis. The baselineperiod is a rolling span of time over which data is collected.

From the day a report is generated, current data is compared to the datacollected for the same hour and day going back to the beginning of thebaseline period (the default setting is six weeks). Results of calculations areshown in either bytes or percentage of bandwidth utilization. Bytes is thedefault setting, using a floating scale to report volume.

If the report is run for the:

— Previous day, each bar represents an hour.

— Previous week, each bar represents a day.

As network data accumulates, regular patterns of network traffic emerge.Use this report in conjunction with with the Total Network Volume by Weekchart for capacity planning.

If there are significant differences between the baseline and the calculatedaverage, use the Leaders Summary Report (see page 7-22) and theExceptions Reports (see page 7-17) to identify which DLCIs are havingproblems.

� Average Health Index by Day – Averages the Health Index grades forall DLCIs combined for a given day, providing a Health Index rating for thenetwork as a whole (see page 7-18 for Health Index information).

From the stack colors, you can determine the most prevalent exceptionconditions experienced.


7-219820-A2-GB20-00 March 1999

� Situations to Watch – Based upon the trend thresholds that have been set,this table predicts when a DLCI might run into trouble. Data from the baselineperiod is used to construct a trend line, which is compared against theprevious day’s data.

Up to ten DLCIs most likely to exceed, or closest to exceeding or reachingthe threshold, are listed. If the Situations to Watch supplemental report isrequested, all DLCIs will be printed on the report, not just the top ten.

Frame relay thresholds are shown in terms of variables, or exceptionconditions, being tracked. The table below shows the frame relay trendthresholds.

Variable Threshold

Utilization as a percentage of the overall bandwidth. 100

Congestion per one million frames. 1000

Errors per one million frames. 5000

Any DLCI within two weeks of reaching threshold should be investigated. Usethis report in conjunction with the Exceptions Reports to identify the problemand when it started.

At-a-Glance Reports (starting on page 7-36) or multi-variable Trend Report(see page 7-40) for the DLCI may be helpful, as well. These summary reportsprovide an overview of DLCI activity and the network’s health. Trendingprovides a historical context for planning and decision-making.

If the DLCI’s threshold has been exceeded or is close to being exceeded andits predicted daily average is high, but its actual daily average is belowthreshold, then no further investigation is needed. The problem has beenfixed.

For additional information about this report, see LAN/WAN Network SummaryReport in the Network Health Reports Guide.


7-22 9820-A2-GB20-00March 1999

Leaders Summary Report

The following chart and tables list the ten highest-volume DLCIs, which may alsohave a high Health Index rating. High traffic volume may be increasing latency,and the high Health Index rating indicates problems.


7-239820-A2-GB20-00 March 1999

The chart and tables contained in this report include:

� Volume Leaders – Shows the DLCIs that are processing the most data forthe previous day, in megabytes, or the percentage of bandwidth the DLCIused. Volume leaders are shown in both chart and table form, with the tableproviding more information.

Up to ten DLCIs can be shown. When there are more than ten DLCIs, youcan view them by running the Volume Leaders Supplemental report. Allhigh-volume DLCIs will be shown on the printed report.

Volume, Bandwidth, and the Health Index ratings are provided for allhigh-volume DLCIs. Average volume is compared to the calculated baselinefor volume. For Bandwidth and the Health Index ratings, an average value, aswell as a value for bandwidth utilization when processing was at its highest,are provided.

It is a good idea to run these reports daily so a norm can be established. Thesame DLCIs should appear on this report daily. Use this chart and table toalert you to possible problems. Things 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 Indexrating.

Use the Volume Change Leaders table to identify DLCI’s with suddenchanges in their traffic pattern.

� Health Index Leaders – Lists up to ten DLCIs having the highest HealthIndex rating for the day. DLCIs can be healthy and still appear on this table.However, if a DLCI’s Health Index rating is high, the condition causing theDLCI’s high rating will be shown.

Use this table to determine the possible cause for changes in a DLCI’s HealthIndex rating. Use the Health Index Change Leaders table to identify DLCIsthat are suddenly experiencing problem conditions.

If a DLCI is transmitting high volume and has a high Health Index rating, it couldhave errors. Check the Element Health Index chart description on the ElementSummary Report, page 7-25, to check for errors.


7-24 9820-A2-GB20-00March 1999

� Volume Change Leaders – Lists up to ten DLCIs having the greatest changein the amount of data transmitted between the day of the report and thebaseline average.

Normally high-volume DLCIs do not usually appear on this table. If they doappear, it could indicate a serious problem that could disrupt service. DLCIsthat suddenly appear on this table are usually experiencing outages, or mayhave just been brought online.

� Health Index Change Leaders – Lists up to ten DLCIs having the greatestchange in their Health Index rating between the day of the report and thebaseline average.

Use this table to determine the cause of the change.

For both Volume Change Leaders and Health Index Change Leaders:

� If the baseline value is a positive number, an increasing number of changesare occurring.

� If the baseline value is a negative number, the number of changes aredecreasing.

For additional DLCI information, see the Bandwidth Utilization chart on theElement Summary Report, page 7-25.


7-259820-A2-GB20-00 March 1999

Elements Summary Report

Use this report for DLCI detail information, which consists of three charts. All theDLCIs appear for comparison. Up to 25 DLCIs per page appear when the reportis printed.


7-26 9820-A2-GB20-00March 1999

Several views for these charts can be selected:

� In data

� Out data

� In and Out data (two bars appear for each DLCI)

� Max data (the direction of the highest volume of data)

� Total data (the default)

The charts contained in this report include:

� Element Volume vs Baseline by Week (or Day) – Displays the volume ofthe DLCIs in bytes (the default) or percentage of bandwidth utilization for thereporting period, either the previous day or the previous week.

Three baselines are shown: high, low, and average so you can view whenvolume was at its highest, lowest, or the average.

Use this chart to identify DLCIs with above or below average volume. Whenthere are any significant changes, investigate the cause. See the ReportsGuide for additional information.

� Bandwidth Utilization – Shows the amount of bandwidth a DLCI usedduring the report period in a percentage of allocated bandwidth. Using theheight of the bar and the color coding, you can determine the amount of timea DLCI spent in a particular bandwidth utilization range.

Possible problems that can be indicated:

— Under 50% utilization indicates you are paying for more bandwidth thanrequired. It is time to renegotiate CIR if this is a consistent pattern.

— Peaks to 100% or greater, check for high error rates. If high utilization isthe norm, it is time to negotiate for higher CIR.

� Element Health Index – Displays the Health Index rating for each DLCI.Based upon the height of each color-coded section, you can determine theproblem conditions which occurred over the reporting period.

See page 7-18 for additional Health Index information.


7-279820-A2-GB20-00 March 1999

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 ofthe service provided by the network.


7-28 9820-A2-GB20-00March 1999


� Availability – Shows the percentage of time that each DLCI was active. If theinterface status changes, or if a poll is missed, the application assumes thatthe DLCI was not available.

Use this chart to verify that DLCIs are operational, and if down, to determinehow long they have been down.

� Reachability – Shows whether the system could communicate with theDLCI; that is, whether the interface could be polled.

Missed polling can occur when there are network problems, or when theinterface is down. The application tries to reach the interface several times.If the unit does not respond, check the Statistics Polling Status window foradditional information which could point to the cause.

� Latency – Shows how fast the network is moving traffic. Network Healthsends one Ping with each IP address it polls, then averages the amount oftime it took to reach the end point and return. However, the method used bythe FrameSaver unit is more accurate since it follows the path of thecustomer data (see Latency Maximum/Average on the At-a-Glance report onpage 7-38). The times at which an average of the frames are calculated isshown along the bottom of the chart, while the delay is shown in milliseconds.


To determine the exact cause of the delay, see the Health Index and theElement Volume vs Baseline by Week (or Day) charts for the DLCI inquestion. In addition, the Element Summaries report will show problemconditions and the size of the packets sent. Packet size may be contributingto the latency.


7-299820-A2-GB20-00 March 1999

Executive Service Level Report

This report summarizes service level performance for an enterprise on a singlepage. Use this report to assess whether IT service levels are meeting availabilityand service goals.


7-30 9820-A2-GB20-00March 1999


� Availability Distribution for All Groups – Shows whether availability goalsand service level agreements are being met. Average daily availability iscompared to the goal that was set. When setting the goal, the highestavailability range possible should be set.

From the stack colors, you can determine the percentage of time on a givenday that the availability goal was not met. Green areas show where thenetwork availability goal was met.

� Latency Distribution for All Groups – Shows how well the network ismoving data. Average daily latency is compared to the goal that was set.When setting the goal, the lowest latency range permissible should be set.

Green areas show where the network latency goal was met. From the stackcolors, you can determine the percentage of each day that the latency goalwas not met.

� Bandwidth Distribution for All Groups – Shows the average bandwidthutilization of all DLCI groups. When setting the goal, the lowest bandwidthutilization range should be set.

From this chart, you can determine whether bandwidth utilization needs arerising. You may need to increase capacity.

� Daily Network Volume by Group – Shows which DLCIs in a group arecontributing the most to network traffic. Use this chart to help determinewhether the appropriate amount of CIR has been negotiated.

The maximum mark shows the highest volume recorded over the reportingperiod, the minimum mark shows the lowest volume, and the average markshows the average for any given day during the reporting period.

� Bandwidth Distribution by Group – Shows the average bandwidthutilization for a group of DLCIs.

Groups showing high utilization levels are in need of an upgrade. Use thischart to justify the need for additional bandwidth to improve service levels.

See LAN/WAN Executive Report in the Network Health Reports Guide foradditional information about this report.


7-319820-A2-GB20-00 March 1999

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 onindividual DLCIs within that group.


7-32 9820-A2-GB20-00March 1999

The charts and table contained in this report include:

� Network Volume for All Groups – Shows the average network volume on adaily basis for all groups for the reporting period. Average volume can beseen in relation to a calculated trend line showing whether volume isincreasing, decreasing, or is remaining constant.

Based upon trends, this chart is used primarily for capacity planning anddecisions.

� Bandwidth Distribution by Group – Shows the average bandwidthutilization for a group of DLCIs.

Groups showing high utilization levels are in need of an upgrade. Use thischart to justify the need for additional bandwidth to improve service levels.

� Daily Health Exceptions by Group – Shows the average number of Healthexceptions (potential utilization, congestion, and error problems) for a groupof DLCIs.

The maximum mark shows the highest number of Health exceptionsoccurring over the reporting period, the minimum mark shows the lowestnumber, and the average mark shows the average for the reporting period.

Use this chart to monitor groups having the most problems.

� Element Summary – Lists specified DLCIs, and allows you to rank the mostcritical ones.

You can monitor the following over the reporting period:

— Availability

— Bandwidth

— Peak Bandwidth

— Latency

This chart can be used when entering into service level agreements, as well.

See LAN/WAN IT Manager Report in the Network Health Reports Guide foradditional information about this report.


7-339820-A2-GB20-00 March 1999

Customer Service Level Report

Used to provide service level information to service customers, this report showsup to 25 DLCIs per page. It combines daily volume, daily Health exceptions,bandwidth distribution, average Health Index ratings and availability for eachDLCI onto a single page.

The report can be tailored to the needs of individual customers, and can helpthem determine optimum service levels needed based upon their own traffic data,as well as provide documented evidence for increasing CIR.

(The rest of this report is on the next page.)


7-34 9820-A2-GB20-00March 1999


� Daily Volume per Element – Shows how customer traffic is changing overtime. The maximum mark shows the highest traffic volume recorded over thereporting period, the minimum mark shows the lowest volume, and theaverage mark shows the average for any given day during the reportingperiod.

A trend line is also provided so the customer can see whether traffic volumeis increasing, decreasing, or remaining constant so they can plan for futureneeds.

� Daily Health Exceptions per Element – Shows the average number ofHealth exceptions (potential utilization, congestion, and error problems) foreach DLCI.

The maximum mark shows the highest number of Health exceptionsoccurring over the reporting period, the minimum mark shows the lowestnumber, and the average mark shows the average for the reporting period.

With this chart, the customer can monitor service quality. If the trend linestarts ascending, quality of service is declining.


7-359820-A2-GB20-00 March 1999

� Bandwidth Distribution – Shows average bandwidth utilization for eachDLCI in terms of the percentage of each day spent within a bandwidth range.

— Customers can use this chart to see when a DLCI’s allocated bandwidthis over- or underutilized, and renegotiate CIR as needed.

— Service providers can use this chart to model the optimum balancebetween service and price for the customer.

For additional bandwidth distribution information, see Bandwidth Utilizationfor the Elements Summary Report on page 7-26.

� Average Health Index – Shows each DLCI’s average Health Index rating forthe reporting period, and the conditions that contributed to the rating. Viewedin conjunction with the Bandwidth Distribution chart, it is easy to correlate therelationship between high utilization and poor service.

DLCIs are in the same order as in the Bandwidth Distribution chart. Thehigher the bar, the poorer the service. From the stack colors, customers candetermine the conditions contributing to poor service.

If Bandwidth Distribution shows that a DLCI is not exceeding CIR, but theDLCI’s Health Index rating high, the service provider is not delivering theadequate service.

See page 7-18 for additional Health Index information.

� Availability – Shows the percentage of time each DLCI has been up andrunning. The service level goal is also shown, which can vary between 90%and 100%. This report is used to verify delivery of the SLA guarantees.

DLCIs are in the same order as in the Bandwidth Distribution chart.

See page 7-28 for additional Availability information.

See LAN/WAN Service Customer Report in the Network Health Reports Guide foradditional information about this report.


7-36 9820-A2-GB20-00March 1999

At-a-Glance Reports

Network Health consolidates a frame relay circuit’s performance over a specifiedperiod onto single page summaries. At-a-Glance reports can be run for aspecified period of a day, an entire day, several days, a week, several weeks, ora month. You also can enter beginning and ending dates and times by selectingCustom when specifying the Time Range that the report is to cover.

In the At-a-Glance report below, a DLCI’s bandwidth utilization, traffic on thenetwork, events that occurred over the reporting period, and availability andlatency service levels are shown. Up to ten DLCIs can be included in the report,with Network Health producing a page for each DLCI that has been specified.


7-379820-A2-GB20-00 March 1999

Any gaps in this report indicate that not enough information has beenaccumulated over the specified time period for the missing performance indicatorto create the graph.


� Bandwidth In/Out – Shows total bandwidth, utilization as a percentage forboth incoming and outgoing data. For additional information, see theElements Summary Report on page 7-25.

� Bandwidth – Shows the DLCI’s volume the amount of time the DLCI isutilizing its allocated bandwidth. If over 70% utilization is being reached, itmay be time for an upgrade. For additional information, see the ElementsSummary Report on page 7-25.

� Bytes In and Out – Shows network volume in bytes per second in and bytesper second out. For additional information, see the Network Summary Reporton page 7-19.

� Frames In and Out – Shows network volume in frames per second in andframes per second out. For additional information, see the Network SummaryReport on page 7-19.

� FECN In and Out – Shows the number of Forward Explicit CongestionNotifications coming in or going out over the frame relay circuit in frames persecond.

� BECN In and Out – Shows the number of Backward Explicit CongestionNotifications coming in or going out over the frame relay circuit in frames persecond.

� DE Frames In and Out – Shows the number of frames marked DiscardEligible coming in or going out over the frame relay circuit in frames persecond.

� Availability – Shows the percent of time that the frame relay circuit was upand running. For additional information, see the Supplemental Report onpage 7-27.

� Latency – Shows the amount of time it takes a Ping on a frame relay circuitto reach a FrameSaver unit and return to the Network Health workstation. Foradditional information, see the Supplemental Report on page 7-27.

Use this report to compare the DLCI’s volume and utilization to the networkperformance indicators.


7-38 9820-A2-GB20-00March 1999

The At-a-Glance report below is the first Network Health report that integratesthe FrameSaver SLV’s unique monitoring capabilities into its reporting package.These graphs integrate FrameSaver SLV enhanced network statistics intoNetwork Health’s reporting.


7-399820-A2-GB20-00 March 1999


� Bytes In and Out – Shows network volume in bytes per second in and bytesper second out. For additional information, see the Network Summary Reporton page 7-19.

� Frames In and Out – Shows network volume in frames per second in andframes per second out. For additional information, see the Network SummaryReport on page 7-19.

� DLCI Up Time – Shows the percentage of time that a DLCI has been up andrunning. The time at which a problem started is shown as a dip in up time.

� Latency Maximum/Average – Shows how fast the network is moving trafficfollowing the path of the customer data, which is the amount of time it takes aframe to travel from one CPE endpoint to another and back. The times atwhich an average of the frames are calculated is shown along the bottom ofthe chart, while the delay is shown in milliseconds. The average latency iscompared to the maximum latency for this DLCI.


To determine the exact cause of the delay, see the Health Index and theElement Volume vs Baseline by Week (or Day) charts for the DLCI inquestion. In addition, the Element Summaries report will show problemconditions and the size of the packets sent. Packet size may be contributingto the latency. For additional information, see the Supplemental Report onpage 7-27.

� Burst Out Distribution – Shows network utilization bursting details to aid indetermining the cause of frame relay lost packets and/or excessive networklatency. Burst Out Distribution is measured in bytes per second and it showsthe exact distribution of transmitted data in relation to the DLCI’s CIR andexcess burst size.

From the stack colors and the amount of data sent, you can determine howthe DLCI is bursting, when the DLCI exceeded its purchased CIR, and byhow much. The higher the Burst Range, the more serious the problem.

� Network Frame Drops – Shows the number of frames dropped by thenetwork in the period of a second.

� Frames Out Size Distribution – Various service level agreement parametersmay be based on frame size, which may contribute to latency and framesbeing lost. This graph shows the size of the packets being transmitted, soyou can compare frame size to your service level agreement.

The transmitted Frame Size Distribution is measured over time as apercentage of all transmitted frames within each of the ranges shown.

� Link Up Time – Shows the percentage of time that the frame relay link hasbeen up and running. If the link goes down, you can determine when it wentdown.


7-40 9820-A2-GB20-00March 1999

Trend Reports

Variables other than bandwidth can be selected for a trend report (e.g., burstoctets); however, a bandwidth trend report (shown here) should be generatedwhen investigating problems that appear on:

� Exceptions Reports (see page 7-17)

� Health Reports (see page 7-11)

� Supplemental Report (see page 7-27)

You can specify total bandwidth (both incoming and outgoing data), only incomingdata bandwidth, or only outgoing data bandwidth. The trend report calculates thebandwidth for the data based upon the data rate and the amount of data in bytes.


7-419820-A2-GB20-00 March 1999

Up to ten variables for a single DLCI, or up to ten DLCIs for a single variable canbe included in a trend report. These reports can be generated for any time frame(i.e., a specific hour, several hours, a day, several days, a week, several weeks,or a month). You can also select the size of the data samples that will be used inthe report (i.e., hourly, daily, etc.).

These reports can present variable information as a line chart, bar chart, stackbar (standard or a percentage of the whole), pie chart, or table. If selecting a piechart, you should be generate the report for multiple variables or DLCIs since thepie shows the percentage each element/DLCI represents of the whole.

Use trend reports to view individual variables for DLCIs having a high HealthIndex rating to help locate which variable is causing a problem leading to aDLCI’s poor Health Index rating (see page 7-18 for Health Index information).

For additional information about trend reports, see LAN/WAN Trend Reports inthe Network Health Reports Guide.


7-42 9820-A2-GB20-00March 1999


8-19820-A2-GB20-00 March 1999

Setup

8Setup and configuration instructions are included in the FrameSaver SLV 9820Standalone Unit Installation Instructions. This chapter provides additionalinformation about the FrameSaver unit’s features and a detailed description of allthe configuration options available.

This chapter provides setup information for the following:

� Entering System Identification on page 8-3.

� Setting the System Date and Time on page 8-4.

� Configuring the FrameSaver Unit on page 8-4.

� Setting Up Auto-Configuration on page 8-8.

Login setup is in Chapter 10, Security and Logins.

Considerations When Setting Up

We recommend that you decide how to configure the FrameSaver unit beforeactually configuring it.

When setting up the FrameSaver unit, you need to:

� Determine where PVCs will be required in your network. Refer to Chapter 3,Typical Applications, for assistance.

� Determine whether you will be using the Auto-Configuration feature. Refer toSetting Up Auto-Configuration on page 8-8.

� Determine whether you want SNMP traps generated, and how you would likethem communicated to the management system.

Setup

8-2 9820-A2-GB20-00March 1999

� 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 FrameSaver unit and a router attached toits DTE port.

— Locally, through the COM port.

— Remotely, through dedicated or multiplexed PVCs.

— Remotely, from a remote terminal via a modem or Telnet connection.

� If managing the FrameSaver unit using an SNMP NMS or Telnet, select anIP addressing scheme. See Chapter 2, Management Control, for differentmanagement alternatives. See Appendix B, IP Addressing, for sample IPaddressing schemes.

Selecting a Management Interface

Select one of the following management interfaces:

� Asynchronous terminal access to the menu-driven user interface – Overthe FrameSaver unit’s COM port or modem connection for local configurationand control.

An asynchronous terminal is also required for initial setup to enable externalmanagement.

� Telnet access to the menu-driven user interface – Over the FrameSaverunit’s network or user data port through an in-band management channel(PVC), or over the COM port using a LAN adapter or modem.

� SNMP – Over the FrameSaver unit’s network or user data port through anin-band management channel (PVC), or over the COM port using a LANadapter or modem.

Minimal Configuration Before Deploying Remote Units

At a minimum, the following configuration options must be set before deploying aa FrameSaver unit to a remote site:

� Node IP Address

� Node Subnet Mask

See Configuring Node IP Information in Chapter 9, Configuration Options, forthese options.

Setup

8-39820-A2-GB20-00 March 1999

Entering System Identification

Use the Device Name screen to name the FrameSaver unit, and to change ordisplay the general SNMP system name, location, and contact for theFrameSaver unit.

� Procedure

1. Follow this menu selection sequence:

Main Menu →Control →Device Name

2. Place the cursor in the field (Tab to the field, or press the arrow keys) whereyou want to add or change information.

The following information is available for viewing. Use the right and left arrowkeys to scroll additional text into view.

If the selection is . . . Enter the . . .

Device Name Unique name for device identification of up to20 characters.

System Name SNMP system name; can be up to 255 characters.

System Location FrameSaver unit’s physical location; can be up to255 characters.

System Contact Name and how to contact the system person; can be up to255 characters.

NOTE:To clear existing information, place the cursor in the Clear field (Tab tothe Clear field) and press Enter.

3. Press Ctrl-a and Save your entries.

Setup

8-4 9820-A2-GB20-00March 1999

Setting the System Date and Time

Use the Date & Time screen to set the date and time for the system.

� Procedure


Main Menu →Control →Date & Time

2. Tab or press arrow keys to move the cursor to the field where you want toadd or change information.

NOTE:To clear existing information, move the cursor to the Clear field and pressEnter.

If the selection is . . . Enter the . . .

Date (mm/dd/yyyy) Date in month/day/year, in the format mm/dd/yyyy ormm-dd-yyyy.

Time (hh:mm) Time (24-hour clock) in the format hh:mm.


Setting Up Logins

See Chapter 10, Security and Logins, to set up and administer logins.

Configuring the FrameSaver Unit

Configuration option settings determine how the FrameSaver unit operates. Usethe FrameSaver unit’s Configuration menu to display or change configurationoption settings.

See Chapter 9, Configuration Options, when configuring the FrameSaver unit. Itcontains tables describing all configuration options and their possible settings.

Changing the Auto-Configuration setting can also change the FrameSaver unit’sconfiguration. See Setting Up Auto-Configuration on page 8-8 for additionalinformation.

Setup

8-59820-A2-GB20-00 March 1999

Configuration Option Areas

The FrameSaver unit arrives with configured factory default settings, which arelocated in the Factory Default configuration option area. You can find the defaultsettings for configuration options in the:

� Quick Reference

� Configuration option tables in Chapter 9

If the factory default settings do not support your network’s configuration, you cancustomize the configuration options to better suit your application.

To change configuration option settings, perform the following tasks:

� Access and display configuration options and their settings.

� Change the settings, as needed.

� Save the changes to one of three configuration option areas.

The FrameSaver unit offers four configuration option storage areas located in thefollowing areas:

Configuration Option Area Description

Current Configuration The currently active set of configuration options.

Customer Configuration 1 An alternate set of configuration options that thecustomer can set up and store for future use.

Customer Configuration 2 Another alternate set of configuration options that thecustomer can set up and store for future use.

Default Factory Configuration A read-only configuration area containing the factorydefault set of configuration options.

You can load and edit default factory configurationsettings, but you can only save those changes to theCurrent, Customer 1, or Customer 2 configurationoption areas.

The Current, Customer 1, and Customer 2 configurationoption areas are identical to the Default FactoryConfiguration 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 andrun tests.

— Security Access Level 3 users can only view configuration options; theycannot change configuration options or run tests.

Setup

8-6 9820-A2-GB20-00March 1999

Accessing and Displaying Configuration Options

To access and display configuration options, load (copy) the applicableconfiguration 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 editarea and the Configuration Edit/Display screen appears.

NOTE:Loading a configuration with many DLCIs from a unit’s CustomerConfiguration 1 or 2 option area may take time. Allow a minute or more forthe file to be loaded.

Changing Configuration Options

� Procedure

To change configuration option settings:

1. From the Configuration Edit/Display screen, select the configuration optionset you want to view or make changes to and press Enter.

2. Select the configuration options applicable to your network, and makeappropriate changes to the setting(s).

When creating new PVC connections or management PVCs, someconfiguration options will be blank. For a valid setting to appear, Tab to theconfiguration option and press the spacebar.

3. Repeat Steps 1 and 2 until all changes are complete.

Setup

8-79820-A2-GB20-00 March 1999

Saving Configuration Options

When all changes to the configuration options are complete, use the Savefunction key to save configuration option changes to either the Current,Customer 1, or Customer 2 Configuration areas.

� Procedure

To save the configuration options changes:

1. Press Ctrl-a to switch to the screen’s function keys area.

2. Type s to select the Save function and press Enter.

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 Save is complete, Command Complete appears in the message areaat the bottom of the screen.

NOTE:If you changed configuration options and try to exit the Configurationmenu without saving those changes, a Save Configuration screenappears requiring a Yes or No response to saving the changes.

I f you select . . . Then the . . .

No Main Menu screen appears. Changes are not saved.

Yes Save Configuration To screen appears. Choose aconfiguration option area to save to (e.g., CustomerConfiguration 1).

NOTE:There are other methods of changing configurations, like SNMP andauto-configuration. Since multiple sessions can be active at same time(two Telnet sessions or one Telnet session and one menu-driven userinterface session), the last change made overwrites any previous orcurrent changes made. For instance:

— Saving your configuration changes would cause configurationchanges made via another method to be lost.

— If you are making changes and someone else makes changes andsaves them, your changes would be lost.

Setup

8-8 9820-A2-GB20-00March 1999

Setting Up Auto-Configuration

The auto-configuration feature allows you to select a method of automaticconfiguration and connection of DLCIs within the FrameSaver unit.

When Frame Relay Discovery is selected, the FrameSaver unit “discovers”network DLCIs from the network LMI status response message (see theprocedure on page 8-10). It configures a network data port DLCI, required userdata port DLCI, and automatically connects them to create a PVC.

Automatically configured network DLCIs are multiplexed, and each automaticallyconfigured user data port DLCI carries the same DLCI Number as itscorresponding network DLCI. These are the same DLCI numbers that wouldhave been available had the FrameSaver unit not been inserted in the linkbetween your equipment and the network.

Frame Relay Discovery mode defaults to 1MPort (management DLCIsmultiplexed with user data DLCIs on Port), which creates two embedded DLCIs(EDLCIs) – one EDLCI for Port user data, and another EDLCI for managementdata. When LMI is active on the network data port and PVC status information(with provisioned DLCI numbers) is next received from the network, the systemautomatically saves the settings listed in the table on page 8-11 to the CurrentConfiguration area.

NOTE:Local Management PVCs (e.g., PVCs between a router and the FrameSaverunit’s user data port) must be configured manually.

Example of Auto-Configuration Screen

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

main/auto-configuration PARADYNE 9820Device Name: Node A 1/26/1998 23:32

AUTO-CONFIGURATION

Frame Relay Discovery Mode: 1MPort

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––Ctrl-a to access these functions, ESC for previous menu M ainMenu E xit S ave

Setup

8-99820-A2-GB20-00 March 1999

Changing the Frame Relay Discovery Mode

Configuration options set by discovery mode can be manually modified, refined,or deleted at any time using the Configuration menus. No previously discoveredand configured DLCIs or cross-connections will be removed unless authorized.Additional discovered DLCIs will be configured according to the current FrameRelay Discovery mode setting. Selecting or changing the setting will not affectIP Addresses or Subnet Masks.

If setting up a FrameSaver unit going to a remote site, only the unit’s NodeIP Address and Subnet Mask need to be preconfigured; the default 1MPortsetting automatically configures the unit.

If 1MPort is not the setting required for your application, change the FrameRelay Discovery mode before connecting the network cable or editing discoveredoption settings. Otherwise, the FrameSaver unit will start “discovering” DLCIs assoon as the unit powers up. To recover from this problem if it occurs:

I f . . . Then . . .

Any DLCIs or PVC connectionshave been configured manually

Select a “discovered” DLCI or PVC connection,and edit as needed using the Configuration menus.

Only a local management PVCbetween the router and theFrameSaver unit has beenconfigured

Select the desired Frame Relay Discovery mode,and Save.

Save causes the Delete All DLCIs and PVCConnections? prompt to appear.

� If Yes (y) is entered, clears all discovered andmanually configured DLCI records and PVCconnections, except for the management PVCbetween a data port and router. This is socommunication with the unit remains.

� If No (n) is entered, no previously discovered ormanually configured DLCIs or PVC connectionsare removed and newly discovered DLCIs willbe configured according to the new discoverymode.

NOTE:If non-FrameSaver units are at the other end of a PVC connection, PVCdiagnostic tests are disruptive to data. Only FrameSaver units currentlysupport PVC multiplexing and nondisruptive PVC diagnostics.

Setup

8-10 9820-A2-GB20-00March 1999

� Procedure

To select a Frame Relay Discovery mode:


Main Menu →Auto-Configuration →Frame Relay Discovery Mode

2. Select a Frame Relay Discovery mode:

Discovery Mode1 Application Description

1MPort

(default)

� Auto-configuration is enabled.

� A management DLCI is configured.

� A multiplexed network DLCI containing two EDLCIs isconfigured for Port-1 user data and for managementdata.

� A PVC connection is configured between the networkand user data port DLCIs.

1Port � Auto-configuration is enabled.

� No management DLCI is configured.

� A multiplexed network DLCI is configured for Port-1user data.

� A PVC connection is configured between the networkand port DLCIs.

NetOnly � Auto-configuration of a network DLCI only; no Port-1 orPVC connections are configured.

� No Port-1, PVC connection, or management DLCI isconfigured.

Disable � No frame relay discovery or automatic configurationtakes place.The FrameSaver unit will be configured manually.

1 See page 8-11 to see the auto-configuration that takes place.

3. Save your selection. Respond yes or no to the Delete All DLCIs andPVC Connections? prompt (see page 8-9).

4. Go to the Configuration menu and change any node-specific configurationoptions that may be needed.

Setup

8-119820-A2-GB20-00 March 1999

The following table shows the automatic configuration that occurs within theFrameSaver unit when a Frame Relay Discovery Mode is selected.

Automatic Configuration for Selected Frame Relay Discovery Mode (1 of 4)

If the mode selected is . . . Then setup configuration is . . .

Multiplexed Management:

� 1MPort

(For DLCI Record information,see Table 9-7, DLCI RecordsOptions.)

� DLCI Records :– Network: DLCI Number is automatically created

from the LMI status response message. ThisDLCI will contain multiple EDLCIs: one forPort-1 user data and one for management.Port-1: DLCI Number is automatically createdfor the user data port from the multiplexednetwork DLCI.Example:Network DLCI 1001 →Port-1 DLCI 1001

– Network: DLCI Type is set to Multiplexed.– Network: CIR (bps) is automatically determined

from LMI status update message if switchprovides this information. Otherwise, the portrate is configured.Port-1: CIR (bps) is set to the network DLCI’sCIR.

– Committed Burst Size Bc (Bits) is set to thenetwork DLCI’s CIR.

– Excess Burst Size Be (Bits) is set to the networkdata port rate minus the network DLCI’s CIR.

– DLCI Priority is set to High.

Setup

8-12 9820-A2-GB20-00March 1999



� 1MPort

(cont’d)

(For Management PVCinformation, see Table 9-10,Management PVC Options.)

� Management PVCs:1

– Name is automatically created from the networkDLCI as Mgmnnnn (nnnn being the discoveredmultiplexed network DLCI number).1

Example:Network DLCI 1001 →Port-1 DLCI 1001 andMgm1001

– Intf IP Address is taken from the Node IPAddress.1

– Intf Subnet Mask is taken from the Node SubnetMask.1

– Primary Link is set to Net1-FR1.– Primary DLCI is automatically created from the

network DLCI.– Primary EDLCI is set to 2 (management data).– Set DE is set to Enable.– RIP is set to Proprietary.

(For PVC Connectioninformation, see Table 9-8, PVCConnection Options.)

� PVC Connections:– Source Link set to Port-1.– Source DLCI – Port-1 DLCI is automatically

created.– Source EDLCI is left blank.– Primary Destination Link is set to Net1-FR1.– Primary Destination DLCI is the automatically

created network DLCI.– Primary Destination EDLCI is set to 0.

1 If the same DLCI/EDLCI combination already exists, no changes are made to theexisting management PVC.You may want to configure a unique Node IP Address and Subnet Mask, and create amanagement PVC for this address and subnet mask prior to Frame Relay Discovery.

Setup

8-139820-A2-GB20-00 March 1999



No Management:

� 1Port

(For DLCI Record information,see Table 9-7, DLCI RecordsOptions.)

� DLCI Records :– Network: DLCI Number is automatically created

from the LMI status response message.Port-1: DLCI Number is automatically createdfrom the network DLCI.Example:Network DLCI 1001 →Port-1 DLCI 1001

– Network: DLCI Type is set to Multiplexed.2

– Network: CIR (bps) is automatically determinedfrom LMI status update message if switchprovides this information. Otherwise, the portrate is configured.Port-1: CIR (bps) is set to the network DLCI’sCIR.




(For PVC Connectioninformation, see Table 9-8, PVCConnection Options.)

� PVC Connections:– Source Link set to Port-1.– Source DLCI is automatically created from the

LMI status response message.– Source EDLCI is left blank.– Primary Destination Link is set to Net1-FR1.– Primary Destination DLCI is automatically

created from the network/source DLCI.– Primary Destination EDLCI is set to 0

(Port-1 data).

2 When non-FrameSaver units are at the other end of the PVC connection, change thenetwork DLCI Type setting to Standard before sending data.

Setup

8-14 9820-A2-GB20-00March 1999



� NetOnly

(For DLCI Record information,see Table 9-7, DLCI RecordOptions.)

� Network DLCI Records:– DLCI Number is automatically created from the

LMI status response message.– DLCI Type is set to Multiplexed.2

– CIR (bps) is automatically determined from LMIstatus update message if switch provides thisinformation. Otherwise, the port rate isconfigured.




� No PVC connections are made within theFrameSaver unit. The user must manually createport and management DLCIs, then connect themto the DLCIs discovered on the network interface.

2 When non-FrameSaver units are at the other end of the PVC connection, change thenetwork DLCI Type setting to Standard before sending data.

9-19820-A2-GB20-00 March 1999

Configuration Options

9This chapter identifies how each set of configuration options is accessed,describes each option, and each option’s possible settings.

The following configuration option tables are included in this chapter:

� Table 9-1. System Frame Relay and LMI Options on page 9-2.

� Table 9-2. Service Level Verification Options on page 9-4.

� Table 9-3. General System Options on page 9-5.

� Table 9-4. Network Data Port Physical Options on page 9-6.

� Table 9-5. User Data Port Physical Options on page 9-8.

� Table 9-6. Frame Relay and LMI Options on page 9-10.

� Table 9-7. DLCI Records Options on page 9-16.

� Table 9-8. PVC Connection Options on page 9-19.

� Table 9-9. Node IP Options on page 9-21.

� Table 9-10. Management PVC Options on page 9-23.

� Table 9-11. General SNMP Management Options on page 9-27.

� Table 9-12. Telnet and FTP Session Options on page 9-28.

� Table 9-13. SNMP NMS Security Options on page 9-31.

� Table 9-14. SNMP Traps and Trap Dial-Out Options on page 9-34.

� Table 9-15. Communication Port Options on page 9-38.

� Table 9-16. External Modem (on Com Port) Options on page 9-43.


9-2 9820-A2-GB20-00March 1999

Configuring System Options

Select System to set the following options:

� Frame Relay and LMI Options, Table 9-1

� Service Level Verification Options, Table 9-2

� General System Options, Table 9-3, for user-initiated test time-out and testduration

Configuring System Frame Relay and LMI Options

Select Frame Relay and LMI to display or change the Frame Relay and LMIoptions for the system (see Table 9-1). Follow this menu selection sequence:

Main Menu →Configuration →System→Frame Relay and LMI

Table 9-1. System Frame Relay and LMI Options (1 of 2)

LMI Behavior

Possible Settings: Independent, Port-1_Follows_Net1-FR1,Net1-FR1_Follows_Port-1, Port-1_Codependent_with_Net1-FR1Default Setting: Independent

Configures the device to allow the state of the LMI to be passed from one interface toanother, determining how the FrameSaver unit will handle a change in the LMI state.Sometimes referred to as LMI pass-through.

Independent – Handles the LMI state of each interface separately so that the LMI stateof one interface has no effect on the LMI state of another interface. Provides LMISpoofing. This is the recommended setting for Network Service Providers (NSPs).

Port-1_Follows_Net1-FR1 – Brings LMI down on user data Port-1 when LMI on thenetwork data port goes down, disabling Port 1 and deasserting its control leads. WhenLMI on the network data port comes back up, Port-1 is reenabled and its control leadsare reasserted. The LMI state on Port-1 has no effect on the LMI state on the networkdata port. That is, Port-1’s LMI follows the network data port’s LMI. This setting is usefulif the router connected to Port-1 is used to initiate recovery when network failures aredetected.

Net1-FR1_Follows_Port-1 – Brings LMI down on the network data port when LMI onPort-1 goes down, disabling the network data port and deasserting its control leads.When LMI on Port-1 comes back up, the network data port is reenabled and its controlleads are reasserted. The LMI state on the network data port has no effect on the LMIstate on Port-1. That is, the network data port’s LMI follows Port-1’s LMI. Used at centralsites, this setting is useful when the remote site router on the other end of the PVCconnection can initiate recovery via a redundant central site when there is a catastrophiccentral-site LAN or router failure. Not recommended for NSPs.

Port-1_Codependent_with_Net1-FR1 – Brings LMI down on the network data portwhen LMI on user data Port-1 goes down (or LMI down on user data Port-1 when LMIon the network data port goes down), and allows LMI to come back up when LMI comesback on either port. That is, the LMI state for one interface is dependent on the other.Use this setting when backup will be performed by the router. It is not recommendedsince it makes fault isolation more difficult.


9-39820-A2-GB20-00 March 1999

Table 9-1. System Frame Relay and LMI Options (2 of 2)

LMI Error Event (N2)

Possible Settings: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10Default Setting: 3

Configures the N2 parameter which sets the number of errors that can occur on the LMIlink before reporting an error. Applies to both the user and network sides of the UNI.

1 – 10 – Specifies the number of errors that can occur on the LMI link (inclusive).

LMI Clearing Event (N3)


Configures the LMI-defined N3 parameter which sets the number of error-free messagesthat must be received before clearing an error event. Applies to both the user andnetwork sides of the UNI.

1 – 10 – Specifies the number of error-free messages that must be received (inclusive).

LMI Status Enquiry (N1)

Possible Settings: 1, 2, 3, 4, . . . 255Default Setting: 6

Configures the LMI-defined N1 parameter which sets the number of status enquirypolling cycles that the user side of the LMI initiates before a full status enquiry isinitiated. Applies only to the user side of the UNI.

1 – 255 – Specifies the number of status enquiry polling cycles that can be initiated(inclusive).

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 betweenthe initiation of status enquiry messages on the user side of the LMI. Applies only to theuser side of the UNI.

5 – 30 – Specifies the number of seconds between the initiation of status enquirymessages in increments of 5.

LMI Inbound Heartbeat (T2)


Configures the LMI-defined T2 parameter which sets the number of seconds betweenthe receipt of status enquiry messages on the network side of the LMI. Applies only tothe network side of the UNI.

5 – 30 – Specifies the number of seconds between the receipt of status enquirymessages in increments of 5.

LMI N4 Measurement Period (T3)

Possible Settings: 5, 10, 15, 20, 25, 30Default Setting: 20

Configures the LMI-defined T3 parameter, which is the interval time (in seconds) that theNetwork side of the LMI uses to measure the maximum status enquiry messagesreceived (N4) from the User side. Applies only when LMI Personality is set to NetworkSide of the UNI.

5 – 30 – Specifies the interval of time in increments of 5.


9-4 9820-A2-GB20-00March 1999

Configuring Service Level Verification Options

Select Service Level Verification to display or change the Service LevelVerification (SLV) System configuration options (see Table 9-2). Follow this menuselection sequence:

Main Menu →Configuration →System →Service Level Verification

Table 9-2. Service Level Verification Options

SLV Sample Interval (secs)

Possible Settings: 15 – 3600Default Setting: 60

Sets the inband communications interval between FrameSaver SLV units. Inbandcommunications are used to pass frames that calculate latency, as well as transmissionsuccess and other SLV information.

15 – 3600 – Sets the SLV Sample Interval (secs) period in seconds (inclusive).

SLV Delivery Ratio

Possible Settings: Enable, DisableDefault Setting: Disable

Determines whether communication of Frame and Data Delivery Ratios (FDR/DDR)between FrameSaver units is enabled. To use this capability, units at both ends of allPVCs must be FrameSaver SLV units. If some of the units are FrameSaver 9124s or9624s, 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. (Beaware that increasing bandwidth used for SLV communications reduces bandwidthavailable for user data).

Disable – Extra byte is not included.


9-59820-A2-GB20-00 March 1999

Configuring General System Options

Select General to display or change the general system configuration options(see Table 9-3). Follow this menu selection sequence:

Main Menu →Configuration →System →General

Table 9-3. General System Options

Test Timeout

Possible Settings: Enable, DisableDefault Setting: Enable

Determines whether or not loopback and pattern tests have a duration after which theyare terminated automatically.

Enable – All Loopback and Pattern tests have a timeout. This setting is recommendedwhen the FrameSaver unit is managed remotely through an in-band data stream. If theFrameSaver unit is accidently commanded to execute a disruptive test on the interfaceproviding the management access, control can be regained after the timeout expires,terminating the test.

Disable – Loopback and pattern tests must be manually terminated.

Test Duration (min)


Specifies the maximum duration of the tests.� Test Duration (min) only appears if Test Timeout is set to Enable.

1 – 120 – Sets the Test Timeout period in minutes (inclusive).

Setting Up Each Physical Interface

Configure physical characteristics using the following interface options:

� Network Data Port Physical Options, Table 9-4

� User Data Port Physical Options, Table 9-5


9-6 9820-A2-GB20-00March 1999

Configuring the Network Data Port Physical Options

Select Physical to display or change the physical configuration options for theport being used as the network interface (see Table 9-6) following this menuselection sequence:

Main Menu →Configuration →Network →Physical

The network data port physical interface acts as a DTE.

Table 9-4. Network Data Port Physical Options (1 of 2)

Port Type

Possible Settings: E530, V.35, X.21Default Setting: V.35

Selects the type of port to be used for the network data port.

E530 – The port is configured as an EIA-530A-compatible DTE. An EIA-530 compatibleDCE can be directly connected to the DB25 connector for this port on the rear of theFrameSaver unit.

V.35 – The port is configured as a V.35-compatible DTE. A V.35-compatible DCE can beconnected to the DB25 connector for this port using an adapter cable on the rear of theFrameSaver unit.

X.21 – The port is configured as a V.11/X.21-compatible DTE. A V.11/X.21-compatibleDCE can be connected to the DB25 connector for this port using an adapter cable onthe rear of the FrameSaver unit.

Port Rate (Kbps)

Possible Settings: For information only.

Displays the rate detected on the network data port. Valid rates are:FrameSaver 9820: 64 or 128 kbpsFrameSaver 9820-C: 64 – 2048 kbps, in increments of 64

If a DCE is not connected to the network data port, if the rate detected is less than64 kbps, or if the rate detected is greater than the highest port rate supported by theunit, then Auto-rating is shown as the unit continues looking for a valid rate. Noattempts to send data should be made until a valid port rate is displayed.

When a valid rate cannot be detected, a Clock Out of Range at Network orLOS at Network 1 Health and Status message is generated. See System andHealth Status Messages in Chapter 11, Displaying System Information, for additionalinformation.

Invert Internal Clock


Specifies whether the internal clock (used for timing data transmitted to the DCE) will bephase-inverted with respect to the clock received at the interface. This option is usefulwhen long cable lengths between the FrameSaver device and the DCE are causingerrors.

Enable – The internal clock used to transmit data to the DCE is phase inverted withrespect to the clock supplied by the DCE to this port.

Disable – The internal clock is not inverted (normal).


9-79820-A2-GB20-00 March 1999

Table 9-4. Network Data Port Physical Options (2 of 2)

Monitor DSR


Specifies whether the state of the DCE Ready (DSR) circuit on the network data portwill be used to determine when valid data communication is possible with the unit.When this condition is detected, an alarm is generated, LMI is declared down, and nofurther transfer of frame relay data can occur on this interface.

� Monitor DSR does not appear if Port Type is set to X.21 (the signal is assumed tobe asserted).

Enable – Interchange circuit CC (ITU/CCITT 107) – DSR is monitored to determinewhen valid data is being sent from the DCE.

Disable – DSR is not monitored. DSR is assumed to be asserted and data istransmitted, regardless of the actual state of the lead.

Monitor CTS


Specifies whether the state of the Clear to Send (CTS) circuit on the network data portwill be used to determine when valid data communication is possible with the unit.When this condition is detected, an alarm is generated, LMI is declared down, and nofurther transfer of frame relay data can occur on this interface.

� Monitor CTS does not appear if Port Type is set to X.21 (the signal is assumed tobe asserted).

Enable – Interchange circuit CB (ITU/CCITT 106) – CTS is monitored to determinewhether data should be transmitted to the DCE.

Disable – CTS is not monitored. CTS is assumed to be asserted and data istransmitted, regardless of the actual state of the lead.

Monitor RLSD (Indication)


Specifies whether the state of the Received Line Signal Detector (RLSD) circuit onthe network data port will be used to determine when valid data communication ispossible with the unit. When this condition is detected, an alarm is generated, LMI isdeclared down, and no further transfer of frame relay data can occur on this interface.

� If Port Type is set to X.21, the Indication interchange circuit is monitored insteadof RLSD.

Enable – Interchange circuit CF (ITU/CCITT 109) – RLSD is monitored to determinewhen valid data communication is possible with the DCE.

Disable – RLSD is not monitored. RLSD is assumed to be asserted and data istransmitted, regardless of the actual state of the lead.


9-8 9820-A2-GB20-00March 1999

Configuring User Data Port Physical Options

Select Physical to display or change the physical characteristics of the user dataport connected to the DTE (see Table 9-5).

Main Menu →Configuration →Data Ports →Physical

Table 9-5. User Data Port Physical Options (1 of 2)

Port Type

Possible Settings: E530, V.35, X.21Default Setting: V.35

Selects the type of port to be used for the user data port.

E530 – The port is an EIA-530A-compatible DCE. An EIA-530-compatible DTE can bedirectly connected to the DB25 connector.

V.35 – The port is a V.35-compatible DCE. A V.35-compatible DTE can be connected tothe DB25 connector by using an adapter cable.

X.21 – The port is a V.11/X.21-compatible DCE. A V.11/X.21-compatible DTE can beconnected to the DB25 connector by using an adapter cable.

Transmit Clock Source

Possible Settings: Internal, ExternalDefault Setting: Internal

Determines whether the DTE’s transmitted data is clocked into the FrameSaver unit byits internal transmit clock or by the external clock provided by the DTE.

� Transmit Clock Source does not appear when Port Type is set to X.21.

NOTE: Changing settings for this configuration option causes the FrameSaver unitto abort any physical port tests, including any DTE-initiated loopback tests.

Internal – The FrameSaver unit uses the interchange circuit DB (ITU 114) – TransmitSignal Element Timing (TXC) (DCE source) for timing the incoming data.

External – The DTE provides the clock for the transmitted data, and the FrameSaverunit uses the interchange circuit DA (ITU 113) – Transmit Signal Element Timing (XTXC)(DTE source) for timing the incoming data.

Invert Transmit Clock

Possible Settings: Auto, Enable, DisableDefault Setting: Auto

Specifies whether the phase relationship between the data received by the FrameSaverunit from the DTE (TXD) and the clock used to time this incoming data will be inverted inorder to minimize transmission errors.

Auto – Phase relationship is automatically adjusted to optimize data transmission fromthe DTE.

Enable – Phase relationship is inverted.

Disable – Phase relationship is normal; it is not inverted.


9-99820-A2-GB20-00 March 1999

Table 9-5. User Data Port Physical Options (2 of 2)

Port (DTE) Initiated Loopbacks

Possible Settings: Local , DisableDefault Setting: Disable

Allows a local external DTE Loopback to be started or stopped via the port’s attacheddata terminal equipment using the port’s interchange lead LL (ITU 141).

� Port (DTE) Initiated Loopbacks does not appear when Port Type is set to X.21.

Local – The DTE attached to the port controls the local external DTE Loopback.

Disable – The DTE attached to the port cannot control the local external DTELoopback.

Monitor DTR


Specifies whether the state of the DTE Ready (DTR) circuit on the user data port will beused to determine when valid data communication is not possible with the DTE. Whenthis condition is detected, an alarm is generated, LMI is declared down, and no furthertransfer of frame relay data can occur on this interface.

� Monitor DTR does not appear when Port Type is set to X.21.

Enable – Interchange circuit CD (ITU 108/1/2) – DTR is monitored to determinewhether data should be transmitted to the DTE.

Disable – DTR is not monitored. DTR is assumed to be asserted and data is beingtransmitted, regardless of the state of the lead.

Monitor RTS (Control)


Specifies whether the state of the Request To Send (RTS) circuits on the user data portwill be used to determine when valid data communication is not possible with the DTE.When this condition is detected, CTS is deasserted, LMI is declared down, and nofurther transfer of frame relay data can occur on this interface.

� If Port Type is set to X.21, RTS appears as Control.

Enable – Interchange circuit CA (ITU 105) – RTS is monitored to determine when validdata communication is possible with the DTE.

Disable – RTS is not monitored. RTS is assumed to be asserted and data is beingtransmitted, regardless of the state of the lead.


9-10 9820-A2-GB20-00March 1999

Configuring Frame Relay LMI for the Unit

Select Frame Relay from the selected Network or Data Ports menu. Based uponthe information about the local management interface (LMI) and assigned lineconditions supplied by the service provider, edit the Frame Relay configurationoptions (see Table 9-6).

Main Menu →Configuration → [Network/Data Ports] →Frame Relay

� Network Data Port

� User Data Port

Table 9-6. Frame Relay and LMI Options (1 of 3)

LMI Protocol

Possible Settings: Initialize_From_Net1FR1 , Initialize_From_Interface,Auto_On_LMI_Fail, Standard, Annex-A, Annex-DDefault Setting: User Data Port: Initialize_From_Net1FR1Network Data Port: Auto_On_LMI_Fail

Specifies either the LMI protocol supported on the frame relay interface or the discoverysource for the LMI protocol.

Initialize_From_Net1FR1 – The LMI type supported on this frame relay link will beconfigured to match the LMI protocol initially discovered on the primary Network framerelay link (Net1FR1). LMI Protocol is set to None internally, but once a protocol hasbecome active or is set on the primary Network link, the protocol will be set to the samevalue on this link (Standard, Annex-A or Annex-D). The protocol will not be updatedbased on changes to Net1FR1 after being set initially.

� Only appears for the user data port.

Initialize_From_Interface – The LMI type supported on this frame relay link will beconfigured to match the LMI protocol discovered from the attached Network line or DTEdevice. Once a protocol has become active, the protocol will be set to the protocoldiscovered (Standard, Annex-A or Annex-D) on the frame relay link. The protocol will notbe updated after being initially discovered. Frame relay links on the user data portdiscover the LMI protocol from an attached device via LMI status polls.

Auto_On_LMI_Fail – The LMI type supported on this frame relay link will be configuredto match the LMI protocol discovered from the attached Network line or the DTE devicewhenever an LMI Link Down failure occurs. This option is available for frame relay linkson the user data port and network data ports. Frame relay links on the user data portdiscover the LMI protocol from LMI status polls on attached DTE devices. Frame relaylinks on the network data port discover LMI protocol by sending polls to an attachedNetwork line and “listening” for correct poll response messages.

Standard – Supports Standard LMI and the Stratacom enhancements to theStandard LMI.

Annex-A – Supports LMI as specified by Q.933, Annex A.

Annex-D – Supports LMI as specified by ANSI T1.617, Annex D.


9-119820-A2-GB20-00 March 1999


LMI Parameters

Possible Settings: System , CustomDefault Setting: System

Allows you to use the system LMI options, or to set specific LMI options for thisinterface.

System – Use system LMI options (see Table 9-1, System Frame Relay and LMIOptions).

Custom – Use the following options in this table to configure LMI parameters.

LMI Error Event (N2)


Configures the LMI-defined N2 parameter which sets the number of errors that canoccur on the LMI link before reporting an error.

� LMI Error Event (N2) only appears when LMI Parameters is set to Custom.

1 – 10 – Specifies the number of errors that can occur on the LMI link (inclusive).

LMI Clearing Event (N3)


Configures the LMI-defined N3 parameter which sets the number of error-free messagesthat must be received before clearing an error event.

� LMI Clearing Event (N3) only appears when LMI Parameters is set to Custom.

1 – 10 – Specifies the number of error-free messages that must be received (inclusive).

LMI Status Enquiry (N1)

Possible Settings: 1, 2, 3, 4, . . . 255Default Setting: 6

Configures the LMI-defined N1 parameter which sets the number of status enquirypolling cycles that the user side of the LMI initiates before a full status enquiry isinitiated. Applies to and configured for the user side of the UNI only.

� LMI Status Enquiry (N1) only appears when LMI Parameters is set to Custom.

1 – 255 – Specifies the number of status enquiry polling cycles that can be initiated(inclusive).


9-12 9820-A2-GB20-00March 1999


LMI Heartbeat (T1)


Configures the LMI-defined T1 parameter which sets the number of seconds betweenthe initiation of status enquiry messages on the user side of the LMI. Applies to andconfigured for the user side of the UNI only.

� LMI Heartbeat (T1) only appears when LMI Parameters is set to Custom.

5 – 30 – Specifies the number of seconds between the initiation of status enquirymessages in increments of 5.

LMI Inbound Heartbeat (T2)


Configures the LMI-defined T2 parameter which sets the number of seconds betweenthe receipt of status enquiry messages on the network side of the LMI. Applies to andconfigured for the network side of the UNI only.

� LMI Inbound Heartbeat (T2) only appears when LMI Parameters is set to Custom.

5 – 30 – Specifies the number of seconds between the receipt of status enquirymessages in increments of 5.

LMI N4 Measurement Period (T3)

Possible Settings: 5, 10, 15, 20, 25, 30Default Setting: 20

Configures the LMI-defined T3 parameter which is the time interval (in seconds) that thenetwork side of the LMI uses to measure the maximum number of status enquirymessages received (N4) from the user side. Applies to and configured for the networkside of the UNI only.

� LMI N4 Measurement Period (T3) only appears when LMI Parameters is set toCustom.

5 – 30 – Specifies the interval of time in increments of 5.


9-139820-A2-GB20-00 March 1999

Configuring DLCI Records for Each Interface

If Auto-Configuration is not used, it is necessary to create DLCI records manuallyfor each interface. If you do use Auto-Configuration, then it may only benecessary to create a management DLCI between the FrameSaver unit and therouter attached to the user data port.

Configure the DLCI records for the following interfaces:

� Network Data Port

� User 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:

5. Select the desired DLCI records.

Main Menu →Configuration → [Network/Data Ports] →DLCI Records

6. 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 thedefault value settings.

NOTE:If the maximum number of DLCIs have already been defined, themessage No more DLCIs allowed appears.

7. Enter the DLCI number to be created.

8. Determine the DLCI type; that is, determine whether the DLCI will bemultiplexed. Do not multiplex a DLCI unless a FrameSaver device is at bothends of the connection. If desired, change DLCI Type to Multiplexed.

9. Press Crtl-a and Save the DLCI Record.


9-14 9820-A2-GB20-00March 1999

� Procedure

To change DLCI records:

1. Select the desired DLCI records.

Main Menu →Configuration → [Network/Data Ports] →DLCI Records

2. Select Modify and press Enter to change a DLCI record.

The message Modify DLCI record for DLCI Number? appears.

3. Select the DLCI record to be modified from the list of all DLCIs on the framerelay link and interface displayed. Then, press Enter.

The DLCI record entry screen displays with the fields initialized for theselected DLCI.

4. Make the desired changes.

5. Press Crtl-a and Save your changes.

If a connected network DLCI’s type is changed from Multiplexed to Standard, thefollowing prompt will appear if the DLCI is part of a connection: DLCI inConnection. Update DLCI usage as follows:

Select one of the following choices:

� Delete EDLCI Connections and Make a Mgmt Only PVC

If you choose this selection, the following actions occur. All of this is typicallydone by frame relay service providers so there is management connectivityfrom the network operation/control center (NOC or NCC):

— Resets any Trap Manager Destination (see Table 9-14, SNMP Traps andTrap Dial-Out Options), or Default Network Destination (see Table 9-9,Node IP Options) that is configured for a Management PVC with thisDLCI to the factory default setting.

— Deletes all PVC Connections (see Configuring PVC Connections onpage 9-18) and Management PVC Connections (see ConfiguringManagement PVCs on page 9-23) involving this DLCI as the source orprimary destination.

— Deletes all excess DLCIs (on the user data port) that were used only indeleted connections.

— Changes DLCI Type from Multiplexed to Standard for the selectedNetwork DLCI.

— Configures the Network DLCI as a Management PVC (see ConfiguringManagement PVCs on page 9-23).


9-159820-A2-GB20-00 March 1999

� Delete EDLCI Connections and Make a standard PVC to frame relay link ,DLCI nnnn

If you choose this selection, the following actions occur:

— Resets any Trap Manager Destination (see Table 9-14, SNMP Traps andTrap Dial-Out Options), or Default Network Destination (see Table 9-9,Node IP Options) that is configured for a Management PVC with thisDLCI to the factory default setting.

— Deletes all PVC Connections (see Configuring PVC Connections onpage 9-18) and Management PVC Connections (see ConfiguringManagement PVCs on page 9-23) involving this DLCI as the source orprimary destination.

— Deletes all excess DLCIs (other than frame relay link, DLCI nnnn) thatwere used only in deleted connections.

— Changes DLCI Type from Multiplexed to Standard for the selectedNetwork DLCI.

— Creates a standard PVC connection between this Network DLCI andframe relay link, DLCI nnnn (see Configuring PVC Connections onpage 9-18).

� Leave as Multiplexed DLCI

The DLCI Type remains unchanged. You must delete the DLCI connectionbefore 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 CopyFromfunction to create additional records, assigning a unique number to eachnew DLCI record.

Example: First DLCI numbered 16Second DLCI numbered 17

2. Select New, or the CopyFrom function, and press Enter.


9-16 9820-A2-GB20-00March 1999

Table 9-7. DLCI Records Options (1 of 2)

DLCI Number

Possible Settings: 16 – 1007Default Setting: Initially blank; no default.

Specifies the number for the DLCI in the DLCI record. The parameter determines whichDLCI record is used for transferring data on a particular frame relay interface. DLCInumbers range from 0 to 1023. However, the numbers 0 – 15 and 1008 – 1023 arereserved. Entry of an invalid number results in the error message Value Out ofRange (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.

– Changing settings for this configuration option causes the FrameSaverunit to abort any active frame relay tests.

16 – 1007 – Specifies the DLCI number (inclusive).

DLCI Type

Possible Settings: Standard, MultiplexedDefault Setting: Standard

Specifies whether the DLCI is standard or multiplexed. This field is read-only when theselected DLCI is a PVC or Management link connection and the DLCI Type is Standard.

� DLCI Type does not appear for the user data port.

Standard – Supports standard DLCIs as specified by the Frame Relay Standards. Usethis setting when a non-FrameSaver unit is at the other end.

Multiplexed – Enables multiplexing of multiple connections into a single DLCI. Allows asingle PVC through the frame relay network to carry multiple DLCIs as long as theseconnections are between the same two endpoints (proprietary). Do not selectMultiplexed unless there are FrameSaver units at both ends of the connection.

CIR (bps)

Possible Settings: 0 – maximum line rate on portDefault Setting: 64000

Determines the data rate for the DLCI that the network commits to accept and carrywithout discarding frames; the CIR in bits per second. Entry of an invalid rate causes theerror message Value Out of Range (0 – x) , where x = the maximum line rateavailable on the port.

Committed Burst Size Bc (Bits)

Possible Settings: CIR, OtherDefault Setting: CIR

Specifies the committed amount of transmitted data in bits that the network will acceptwithout discarding frames (Bc).

CIR – Specifies the CIR amount of data that will be accepted before frames arediscarded.

Other – Allows you to specify a rate other than the CIR in the Port Rate-Bc field. In thiscase, Tc is calculated according to I.370.


9-179820-A2-GB20-00 March 1999

Table 9-7. DLCI Records Options (2 of 2)

Bc

Possible Settings: 0 – maximum line rate on portDefault Setting: CIR rate

Allows you to display or change the committed burst size for the DLCI.� Bc only appears when Committed Burst Size is set to Other.

Excess Burst Size (Bits)

Possible Settings: This field is blank.Default Setting: There is no default setting.

Specifies the maximum amount of data in bits that the network may accept beyond theCIR without discarding frames.

Be

Possible Settings: 0 – maximum line rate on portDefault Setting: maximum port rate minus the default CIR

Allows you to display or change the excess burst size for the DLCI.

DLCI Priority

Possible Settings: Low, Medium, HighDefault Setting: Medium

Specifies the relative priority for data received on the DLCI from an attached device(also known as quality of service). All data on user data Port 1 is cut-through, as long asthere is no higher-priority data queued from another user port. The DLCI priority set foran interface applies to data coming into that interface. For example, the priority set forDLCIs on Port 1 applies to data coming into Port 1 from the attached equipment (suchas a router). This option has no effect when there is only one user data port.

� DLCI Priority is not available on the network data port.

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, HighDefault Setting: Medium

Specifies the relative priority for management traffic sent on management PVCstransmitted on this DLCI to the network.

� Outbound Management Priority 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.


9-18 9820-A2-GB20-00March 1999

Configuring PVC Connections

Select PVC Connections to display or change the configuration options for thePVC connections (see Table 9-8). DLCI records must have been configured forthe interface first. See Maximum PVCs, EDLCIs, and Management PVCs inChapter 1, About the FrameSaver SLV, for a table of the maximum number ofPVCs that you can configure.

� Procedure


Main Menu →Configuration →PVC Connections

The PVC Connection Table screen appears.

2. Select New or Modify from the PVC Connection Table screen to add orchange PVC connections between a source DLCI (link) and destination DLCI(link) on a frame relay interface.

3. When New is selected, the configuration option field is blank. Tab to the firstconfiguration option and press the spacebar. The first valid selection appearsin the field.

NOTE:Management links are not created using this screen. Go to theManagement PVC Entry screen:

Main Menu →Configuration →Management and Communication →Management PVCs


9-199820-A2-GB20-00 March 1999

Table 9-8. PVC Connection Options (1 of 2)

Source Link

Possible Settings: Port-1, NET1-FR1Default Setting: Initially blank; no default.

Specifies the frame relay interface that starts a PVC connection; the from end of afrom-to link. The only valid settings for this configuration option are frame relayinterfaces that have at least one DLCI or EDLCI defined that are not part of a PVCconnection or management link. For example, if Port-1 has no DLCIs defined, Port-1would not appear as a valid setting.

Port-1 – Specifies the user data port as the source link.

Net1-FR1 – Specifies the network data port as the source link.

Clear – Clears the Source Link and Source DLCI settings, and suppresses SourceEDLCI.

Source DLCI

Possible Settings: 16 – 1007 Default Setting: Initially blank; no default.

Specifies the source DLCI for a frame relay interface. The DLCI must be defined andcannot be part of a PVC connection or management link. For multiplexed DLCIs, at leastone 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 framerelay interface when a multiplexed DLCI record is selected as one end of a connection.

� Source EDLIC only appears if Source DLCI contains a multiplexed DLCI recordnumber.

0 – 62 – Specifies the EDLCI number (inclusive).

Primary Destination Link

Possible Setting: Net1-FR1Default Setting: Initially blank; no default.

Specifies the frame relay interface used as the primary destination link; the to end of afrom-to link. The only valid settings for this configuration option are frame relayinterfaces that have at least one DLCI or EDLCI defined which are not part of a PVCconnection or management link. For example, if the network data port has no DLCIsdefined, this interface would not appear as a valid setting.

Net1-FR1 – Specifies the network data port as the destination link.

Clear – Clears the Primary Destination Link and Primary Destination DLCI settings, andsuppresses Primary Destination EDLCI.


9-20 9820-A2-GB20-00March 1999

Table 9-8. PVC Connection Options (2 of 2)

Primary Destination DLCI


Specifies the primary destination DLCI for a frame relay interface. The DLCI must bedefined and cannot be part of a PVC connection or management link. For multiplexedDLCIs, 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 containsno value.


Primary Destination EDLCI


Specifies the primary destination Embedded Data Link Connection Identifier (EDLCI) fora frame relay interface when a multiplexed DLCI record is selected as one end of aconnection.

� Primary Destination EDLCI only appears if Source DLCI contains a multiplexedDLCI record number.


Setting Up Management and Communication Options

Select Management and Communication to display the Management andCommunications Options menu. The following Management and CommunicationOptions can be selected from the menu:

� Node IP Options, Table 9-9

� Management PVC Options, Table 9-10

� General SNMP Management Options, Table 9-11

� Telnet and FTP Sessions Options, Table 9-12

� SNMP NMS Security Options, Table 9-13

� SNMP Traps and Trap Dial-Out Options, Table 9-14

� Communication Port Options, Table 9-15

� External Modem (on Com Port) Options, Table 9-16


9-219820-A2-GB20-00 March 1999

Configuring Node IP Information

Select Node IP to display, add, or change the information necessary to supportIP communication network for the node (see Table 9-9).

Main Menu →Configuration →Management and Communication →Node IP

Table 9-9. Node IP Options (1 of 2)

Node IP Address

Possible Settings: 001.000.000.000 – 223.255.255.255, ClearDefault Setting: Clear (000.000.000.000)

Specifies the IP address needed to access the node. Since an IP address is not boundto 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 youcan view or edit. The first byte (i.e., nnn.255.255.255) can be any number from 001through 223, excluding 127. However, 000 is valid, representing a null address.Remaining bytes (i.e., 223.nnn.nnn.nnn) can be any number from 000 through 255.Leading zeros are required.

Clear – Clears Node IP Address and fills the address with zeros( i.e., 000.000.000.000).

Node Subnet Mask

Possible Settings: 000.000.000.000 – 255.255.255.255, ClearDefault Setting: 000.000.000.000

Specifies the subnet mask needed to access the node. Since the subnet mask is notbound 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 youcan view or edit.

Clear – Clears Node Subnet Mask and fills the address with zeros( i.e., 000.000.000.000). When the node’s subnet mask is all zeros, the IP protocolcreates 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.


9-22 9820-A2-GB20-00March 1999

Table 9-9. Node IP Options (2 of 2)

Default IP Destination

Possible Settings: None, COM, PVCnameDefault Setting: None

Specifies where a default IP destination or route is connected so that data without aspecifically defined PVC will have a route.

Examples: If the default IP network is connected to the communications port, you would selectCOM.

If the default IP network is connected to a far-end device over the management PVCnamed London (as defined by the Name configuration option (see Table 9-10,Management PVC Options), you would select the PVC name London.

NOTE: If the link to the IP destination selected as the default route becomesdisabled or down, the unrouteable data will be discarded. Make sure thatthe link selected is operational, and if that link goes down, change thedefault destination.

CAUTION: Use care when configuring a default route to an interface that has asubnet route configured at a remote end where the NMS, router, LANadapter, terminal server, etc. is connected. Communicating with anunknown 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 that the default destination is connected to the COM port. Onlyappears when Port Use is set to Net Link (see Table 9-15, Communication PortOptions).

PVCname – Specifies a name for the management PVC. Only appears when amanagement PVC name is defined for the node For example, when the network isconnected to a remote device located in the London office, London can be specified asthe PVC name, which is the link between the local FrameSaver unit and the one locatedin London. London would appear as one of the available selections.


9-239820-A2-GB20-00 March 1999

Configuring Management PVCs

Select Management PVCs to define in-band management links by:

� Adding or changing Management PVCs for the FrameSaver unit.

� Assigning the PVCs to the frame relay interface.

First, DLCI records must have been configured for the interface where theManagement PVC will reside. See Configuring DLCI Records for Each Interfaceon page 9-13.

� Procedure


Main Menu →Configuration →Management and Communication →Management PVCs

2. Select New or Modify from the Management PVCs screen to add or changeDLCI and EDLCI logical links. When you select New, the configuration optionfield is blank. When you select Modify, the values displayed for all fields arebased on the PVC ID that you specified.

See Table 9-10 for Management PVC configuration options.

Table 9-10. Management PVC Options (1 of 4)

Name

Possible Settings: ASCII text entryDefault Setting: Initially blank; no default.

Specifies a unique name for the management PVC as referenced on screens(e.g., London for the London office).

ASCII text entry – Where you enter a unique name for the management PVC(maximum length 8 characters).

Intf IP Address

Possible Settings: Node-IP-Address, Special (nnn.nnn.nnn.nnn)Default Setting: Node-IP-Address

Specifies the IP address needed to access the unit via this management PVC, providingconnectivity to an external IP network through the frame relay network.

Node-IP-Address – Uses the IP address contained in the Node IP Addressconfiguration option (see Table 9-9, Node IP Options).

Special (001.000.000.000 – 223.255.255.255) – Allows you to edit/display the IPaddress for the unit’s management PVC when the IP address is different for thisinterface. The first byte (i.e., nnn.255.255.255) can be any number from 001 through223, excluding 127. Remaining bytes (i.e., 223.nnn.nnn.nnn) can be any number from000 through 255. Leading zeros are required.


9-24 9820-A2-GB20-00March 1999


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 isproviding connectivity to an external IP network (through frame relay) that requires aspecific subnet mask for the interface.

Node-Subnet-Mask – Uses the Interface IP Subnet contained in the Node-SubnetMask configuration option (see Table 9-9, 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, orClass 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 subnetmask for the management PVC when the subnet mask is different for this interface. Atext field displays where you can enter the subnet mask for this unit’s managementPVC.

Set DE


Specifies whether frames (packets) sent on a management PVC have the DiscardEligible (DE) bit set. This bit is used by the network to prioritize which frames to discardfirst during periods of network congestion. This allows management traffic to be viewedas 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 isthe recommended setting, particularly for NSPs providing a managed network service.

Primary Link

Possible Settings: Net1-FR1, Port-1, ClearDefault Setting: Initially blank; no default.

Specifies the frame relay interface to use for this management PVC. The interfaceselected must have at least one DLCI (or DLCI with EDLCI) defined, which is not part ofa PVC connection or already assigned as a management PVC.

Net1-FR1 – Specifies the network data port as the source link for the connection.

Port-1 – Specifies the frame relay link on user data Port 1 as the destination link for theconnection.

Clear – Clears the link and the DLCI field, and suppresses the EDLCI field if the DLCIwas multiplexed.


9-259820-A2-GB20-00 March 1999


Primary DLCI


Specifies the DLCI number used for the management PVC after the frame relayinterface is selected.

The DLCI must be defined for the link (i.e., has a DLCI record), and it must not be partof a PVC connection or already assigned as a management PVC. For multiplexedDLCIs, 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 isselected for the frame relay link. EDLCIs identify individual connections withinmultiplexed 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 theprimary EDLCI for user data, which has a higher utilization rate than management data,with slightly less line overhead.

� Primary EDLCI does not appear if the DLCI field does not reference a multiplexedDLCI.

NOTE: Clearing the DLCI or changing it to a standard DLCI suppresses EDLCIfield.



9-26 9820-A2-GB20-00March 1999


Primary Link RIP

Possible Settings: None, Proprietary, Standard_outDefault Setting: Multiplexed DLCIs: ProprietaryNonmultiplexed DLCIs: Standard_out

Specifies which Routing Information Protocol (RIP) is used to enable routing ofmanagement between FrameSaver units.

None – Does not use a routing protocol.

Proprietary – Uses a proprietary variant of RIP version 1 to communicate routinginformation between FrameSaver units. A FrameSaver unit must be on the other end ofthe link. This is the factory default for management PVCs configured on multiplexedDLCIs (see Table 9-7, DLCI Records Options).

Standard_out – The device will send standard RIP messages to communicate routinginformation only about other FrameSaver SLV units in the network. This is the factorydefault for management PVCs configured on standard DLCIs.

NOTE: The router must be configured to receive RIP on the port connected to theFrameSaver unit for 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:– Create a Standard DLCI for the user data port (see Configuring DLCI

Records for Each Interface on page 9-13).– Change it to a Management PVC (see Configuring Management PVCs

on page 9-23).– Make sure that Node IP Information has been set up (see Configuring

Node IP Information on page 9-9).– Set Primary Link RIP to Standard_Out.


9-279820-A2-GB20-00 March 1999

Configuring General SNMP Management

Select General SNMP Management to add, change, or delete the informationneeded to allow the FrameSaver unit to be managed as an SNMP agent by theNMS supporting the SNMP protocols.

Main Menu →Configuration →Management and Communication →General SNMP Management

See Table 9-11 for General SNMP Management configuration options.

Table 9-11. General SNMP Management Options (1 of 2)

SNMP Management


Determines whether the FrameSaver unit can be managed as an SNMP agent by anSNMP-compatible NMS.

Enable – Can be managed as an SNMP agent.

Disable – Cannot be managed as an SNMP agent. The FrameSaver unit will notrespond to SNMP messages nor send SNMP traps.

Community Name 1

Possible Settings: ASCII text entry, ClearDefault Setting: Public in ASCII text field

Specifies the first of two names that are allowed to access the objects in theFrameSaver unit’s MIB. The community name must be supplied by an external SNMPmanager whenever the manager tries to access an object in the MIB.

ASCII text entry – Adds to or changes Community Name 1 (maximum 255 characters).

Clear – Clears Community Name 1.

Name 1 Access

Possible Settings: Read, Read/WriteDefault Setting: Read

Specifies the type of access allowed to the objects in the MIB. This is the type of accessallowed for external SNMP managers accessing MIB objects using Community Name 1.

Read – Allows read-only access (SNMP Get command). This includes all objectsspecified 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

Possible Settings: ASCII text entry, ClearDefault Setting: Clear

Specifies the second of two names that are allowed to access the objects in theFrameSaver unit’s MIB. The community name must be supplied by an external SNMPmanager whenever the manager tries to access an object in the MIB.

ASCII text entry – Adds to or changes Community Name 2 (maximum 255 characters).

Clear – Clears Community Name 2.


9-28 9820-A2-GB20-00March 1999

Table 9-11. General SNMP Management Options (2 of 2)

Name 2 Access


Specifies the type of access allowed to the objects in the MIB. This is the type of accessallowed for external SNMP managers accessing MIB objects using Community Name 2.

Read – Allows read-only access (SNMP Get command). This includes all objectsspecified 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 a Telnet or download session.Telnet configuration options control whether a Telnet session is allowed throughan interconnected IP network and the access security applicable to the session(see Table 9-12). Two Telnet sessions can be active at a time.

Main Menu →Configuration →Management and Communication →Telnet and FTP Session

Table 9-12. Telnet and FTP Session Options (1 of 3)

Telnet Session


Specifies whether the FrameSaver unit will respond to a session request from a Telnetclient on an interconnected IP network.

Enable – Allows Telnet sessions between the FrameSaver unit 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 toaccess the menu-driven user interface via a Telnet session. If required, the login used isthe same login used for an menu-driven user interface session.

Enable – Requires a login to access a Telnet session.

Disable – Does not require a login.


9-299820-A2-GB20-00 March 1999


Session Access Level

Possible Settings: Level-1, Level-2, Level-3Default Setting: Level-1

Specifies the highest security level allowed when accessing the menu-driven userinterface via a Telnet session. If a login is required for the session, the effective accesslevel is determined by the user’s access level. When a login is not required, the effectiveaccess level is determined by this option.

Level-1 – Allows Telnet or FTP access by users with Login ID access levels of 1, 2, and3, with the capability to view system information, change configuration options, and runtests. This is the highest access level allowed. Use this setting when downloading files.

CAUTION: Before changing session access level to Level-2 or 3, make sure that thePort Access Level for the communication port is set to Level-1 and atleast one Login ID is set to Level-1. Otherwise, access will be lost. If thisoccurs, you must reset the unit to the factory defaults and begin theconfiguration process again. A reset is required if the CommunicationPort’s Port Use option is set to Net Link (see Table 9-3, General SystemOptions).

Level-2 – Allows Telnet access by users with Login ID access levels of 1, 2, and 3, withthe capability to view system information and run tests only; they cannot changeconfiguration options.

Level-3 – Allows Telnet access by users with Login ID access levels of 1, 2, and 3, withthe capability to view system information only; they cannot change configuration optionsor run tests.

NOTE: The effective access level is always the lowest one assigned to either thesession or the user. For example, if the Session Access Level assigned isLevel-2, but the User Access Level is Level-3, then only level-3 access willbe permitted for the session.

Inactivity Timeout


Determines whether a Telnet session is disconnected after a specified time of keyboardinactivity.

NOTE: Changing this setting does not affect the current session; it changes allsubsequent sessions.

Enable – Terminates Telnet session after the specified time of inactivity.

Disable – Does not terminate Telnet session during inactivity.

Disconnect Time (Minutes)


Determines the amount of keyboard inactive time before disconnecting a user session.� Disconnect Time (Minutes) does not appear if Inactivity Timeout is set to Disable.


1 – 60 – Sets the time from 1 to 60 minutes (inclusive).


9-30 9820-A2-GB20-00March 1999


FTP Session


Determines whether the FrameSaver unit responds as a server when an FTP (filetransfer protocol) client on an interconnected IP network requests an FTP session. Mustbe enabled when downloading files.

Enable – Allows an FTP session between the FrameSaver unit and an FTP client.

Disable – Does not allow an FTP session.

FTP Login Required


Determines whether a user ID and password are required for an FTP session. Ifrequired, the login used is the same login used for an menu-driven user interfacesession.

Enable – User is prompted for a user ID and password.

Disable – User is not prompted for a user ID and password.

FTP Max Receive Rate (kbps)

Possible Settings: FrameSaver 9820: 1 – 128FrameSaver 9820-C: 1 – 2048Default Setting: Maximum management rate supported by the unit.

Determines the maximum receive rate of file transfer to the FrameSaver unit. This optionallows new software to be downloaded using selected bandwidth without interfering withnormal operation. Using this option, new software can be downloaded quickly using thedefault settings, or at a slower rate over an extended period of time by selecting a slowerspeed. Based upon TCP flow control, the FTP server in the FrameSaver unit throttlesbandwidth to match this setting.

To see whether a download has completed, check the Identity screen (selected from theStatus menu). In the Alternate Software Revision field, a software revision numberappears if the file transfer is complete. If In Progress appears, the file is still beingtransferred. If Invalid appears, no download has occurred.

1 – 128 – Sets the download line speed from 1 kilobits per second to the full networkdata port rate of 128 kbps for the FrameSaver 9820.

1 – 2048 – Sets the download line speed from 1 kilobits per second to the full networkdata port rate of 2048 kbps for the FrameSaver 9820-C.


9-319820-A2-GB20-00 March 1999

Configuring SNMP NMS Security

Select SNMP NMS Security to display, add, or change the SNMP securityconfiguration options for the FrameSaver unit. A table is displayed consisting ofthe network management systems identified by IP address that are allowed toaccess the FrameSaver unit by SNMP.

Main Menu →Configuration →Management and Communication →SNMP NMS Security

See Table 9-13 for SNMP NMS Security configuration options.

Table 9-13. SNMP NMS Security Options (1 of 2)

NMS IP Validation


Specifies whether security checks are performed on the IP address of SNMPmanagement systems attempting to access the node. Allows access only if IP addressof the sending manager is listed on the SNMP NMS Security Options screen.

Enable – Performs security checks.

Disable – Does not perform security checks.

Number of Managers


Specifies the number of SNMP management systems that are authorized to sendSNMP messages to the FrameSaver unit. An IP address must be configured for eachmanagement system allowed to send messages. Configure IP addresses in the NMS nIP Address configuration option.

1 – 10 – Specifies the number of authorized SNMP managers.

NMS n IP Address


Specifies the IP address that identifies SNMP manager(s) authorized to send SNMPmessages to the FrameSaver unit. If an SNMP message is received from the NMSwhose IP address does not match an address contained in this field, access is deniedand 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 level.

001.000.000.000 – 223.255.255.255 – Adds to or changes the NMS IP address. Thefirst byte (i.e., nnn.255.255.255) can be any number from 001 through 223, excluding127. Remaining bytes (i.e., 223.nnn.nnn.nnn) can be any number from 000 through 255.Leading zeros are required.

Clear – Clears the NMS IP address and fills the address with zeros( i.e., 000.000.000.000).


9-32 9820-A2-GB20-00March 1999

Table 9-13. SNMP NMS Security Options (2 of 2)

Access Type


Specifies the access allowed for an authorized NMS when IP address validation isperformed. If the IP address for the NMS sending an SNMP message is on the list ofallowed managers, this configuration option determines the type of access allowed forthat manager.

Read – Allows read-only access (SNMP Get command) to the MIB objects. Thisincludes 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 MIBobjects. 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 SNMP trap configurationoptions for the FrameSaver unit.

Main Menu →Configuration →Management and Communication →SNMP Traps

To configure the FrameSaver unit for SNMP traps you must set:

� The number of SNMP managers that are to receive SNMP traps from theFrameSaver unit.

� An IP address for each SNMP manager specified.

� The type of SNMP traps to be sent from the FrameSaver unit.

Use the SNMP Trap Options screen to configure the necessary configurationoptions needed to support the SNMP traps. Select and set the followingconfiguration options, as appropriate (see Table 9-14).


9-339820-A2-GB20-00 March 1999

See Appendix C, Standards Compliance for SNMP Traps, for trap formatstandards and special trap features, including RMON-specific traps. SeeAppendix D, RMON Alarm Defaults, for the default settings that will generateRMON-specific SNMP traps.

NOTE:Be sure to choose an operational link for the default. Should the default linkbecome disabled, unrouteable traps will be discarded.

To . . . Set the configuration option . . .

Enable sending of SNMP trapmessages

SNMP Traps to Enable.

Specify the number of SNMPmanagers that will receive SNMP trapmessages from the FrameSaver unit

Number of SNMP Managers to the desirednumber (maximum of 6) of SNMPmanagers to receive SNMP traps.

Specify an IP address for each SNMPmanager specified in the Number ofSNMP Managers configuration option

NMS n IP Address to the IP address thatidentifies each SNMP manager(s) indicatedin the Number of SNMP Managersconfiguration option.

Specify the network destination forthe Trap Manager

Destination to one of the following:DefaultCOMPVCname

Select the type of SNMP trapmessages to be sent from theFrameSaver unit

� General Traps to enable or disablewarmStart and authenticationFailuretraps.

� Enterprise Specific Traps to enable ordisable enterpriseSpecific traps.

� Link Traps to enable or disable linkDownand linkUp traps.

� Link and DLCI Traps Interfaces to specifywhich interfaces will generate linkDown,linkUp and enterpriseSpecific traps.

� RMON traps


9-34 9820-A2-GB20-00March 1999

Table 9-14. SNMP Traps and Trap Dial-Out Options (1 of 4)

SNMP Traps


Determines whether the FrameSaver unit sends trap messages to the currentlyconfigured SNMP trap manager(s).

Enable – Sends trap messages.

Disable – Does not send trap messages.

Number of Trap Managers


Specifies the number of SNMP management systems that will receive SNMP trapmessages from the FrameSaver unit. An NMS IP Address must be configured in theNMS n IP Address configuration option for each trap manager to receive trapmessages.

1 – 6 – Specifies the number of trap managers (inclusive).

NMS n IP Address


Specifies the IP address that identifies the SNMP manager(s) to receive SNMP traps.� NMS n IP Address 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 IP address for the trapmanager. The first byte (i.e., nnn.255.255.255) can be any number from 001 through223, excluding 127. Remaining bytes (i.e., 255.nnn.nnn.nnn) can be any number from000 through 255. Leading zeros are required.

Clear – Clears the IP address and fills the address with zeros ( i.e., 000.000.000.000).

Destination

Possible Settings: Default, COM, PVCnameDefault Setting: Default

Specifies the network destination for the Trap Manager number configuration option.� Destination appears for each trap manager specified in the Number of Trap

Managers configuration option.

Default – Uses the default network.

COM – Uses the COM port. This selection only appears if the Communication Port Useconfiguration option is set to Net Link.

PVCname – The management linkname (name of the logical managementcommunication link). This selection only appears when at least one logical managementcommunication link name is defined for the node.


9-359820-A2-GB20-00 March 1999


General Traps

Possible Settings: Disable, Warm, AuthFail, BothDefault Setting: Both

Determines whether SNMP trap messages for warmStart and/or authenticationFailureevents are sent to the currently configured trap manager(s).

Disable – Does not send trap messages for warmStart or authenticationFailure events.

Warm – Sends trap messages for warmStart events.

AuthFail – Sends trap messages for authenticationFailure events.

Both – Sends trap messages for both warmStart and authenticationFailure events.

Enterprise Specific Traps


Determines whether trap messages for enterpriseSpecific events are sent to thecurrently configured trap manager(s).

Enable – Sends trap messages for enterpriseSpecific events.

Disable – Does not send trap messages for enterpriseSpecific events.

Link Traps

Possible Settings: Disable, Up, Down, BothDefault Setting: Both

Determines whether SNMP linkDown or linkUp traps are sent to the currently configuredtrap manager(s). A linkDown trap indicates that the FrameSaver unit recognizes afailure in one of the communication interfaces. A linkUp trap indicates that theFrameSaver unit recognizes one of its communication interfaces is active.

Use the Link Traps Interface and the DLCI Traps on Interface configuration options tospecify which interface will monitor linkUp and linkDown traps messages.

Disable – Does not send linkDown or linkUp trap messages.

Up – Sends trap messages for linkUp events.

Down – Sends trap messages for linkDown events.

Both – Sends trap messages for linkUp and linkDown events.

Link Traps Interfaces

Possible Settings: Network, Ports, AllDefault Setting: All

Specifies which interface monitors and generates linkUp, linkDown, andenterpriseSpecific trap messages. These traps are not supported on the COM port.

Network – Generates trap messages for linkUp, linkDown, and enterpriseSpecificevents on the network data port only.

Ports – Generates trap messages for linkUp, linkDown, and enterpriseSpecific eventson user data port only.

All – Generates trap messages for linkUp and enterpriseSpecific events on the networkand user data ports.


9-36 9820-A2-GB20-00March 1999


DLCI Traps on Interfaces

Possible Settings: Network, Ports, AllDefault Setting: All

Specifies which interface will monitor and generate linkUp and linkDown trap messagesfor individual DLCIs. These traps are not supported on the COM port.

Network – Generates trap messages for linkUp and linkDown events on DLCIs for thenetwork data port only.

Ports – Generates trap messages for linkUp and linkDown events on DLCIs for theuser data port only.

All – Generates trap messages for linkUp and linkDown events on all interfaces.

RMON Traps


Specifies whether remote monitoring traps are sent to the currently configured trapmanager(s). RMON traps are typically sent as a result of the Alarms and Events Groupsof 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.

Trap Dial-Out


Controls whether SNMP trap messages initiate a call automatically. If the call cannot becompleted 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.

Enable – Automatically calls the phone number contained in the Control menu’s ModemCall Directories, Directory Number A (Alarm).

Disable – For traps, where the COM port-connected modem has not completed theconnection, holds the messages.

Trap Disconnect


Determines whether the COM port-connected modem disconnects after the SNMP trapmessage has been sent. This configuration option only applies to modem connectionsinitiated as a result of sending the SNMP trap message.

Enable – Disconnects the call after sending an SNMP trap message(s).

Disable – Does not disconnect the call and holds the line until it is disconnectedmanually or by the remote modem. This allows the NMS to poll the FrameSaver unit formore information after receiving an SNMP trap.


9-379820-A2-GB20-00 March 1999


Call Retry


Controls whether an incomplete call (busy, no answer, etc.) is retried when an SNMPtrap message is sent to the modem connected to the COM port.

Enable – Attempts to retry the call, up to one time per SNMP trap message, with adelay between the retry. The delay is specified by the Dial-Out Delay Time (Min)configuration option.

If an alternate dial-out directory is specified (see Alternate Dial-Out Directory), the alarmdirectory’s telephone number is called first. If the call cannot be completed, then thealternate directory’s telephone number is called (see the Control menu’s Modem CallDirectories).

Disable – Does not retry an incomplete call.

Dial-Out Delay TIme (Min)


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 – Sets the number of minutes for the delay between call retry attempts(inclusive).

Alternate Dial-Out Directory

Possible Settings: None, 1 – 5Default Setting: None

Specifies whether an incomplete call (busy, or no answer, etc.) resulting from an attemptto send an SNMP trap message is retried using an alternate telephone number. Up to5 alternate call directories can be set up, but only one at a time can be used.

When Call Retry on Trap Dial-Out is enabled, the alarm directory’s telephone number iscalled first. If the call cannot be completed after one additional try, then the specifiedalternate 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 callcannot be completed using the telephone number in the alarm directory (DirectoryNumber A in the Control menu’s Modem Call Directories), inclusive.


9-38 9820-A2-GB20-00March 1999

Configuring the Communication Port

Select Communication Port to display or change the communication portconfiguration options (see Table 9-15).


Table 9-15. Communication Port Options (1 of 5)

Port Use

Possible Settings: Terminal, Net LinkDefault Setting: Terminal

Assigns a specific use to the COM port.

NOTE: If the Default IP Destination is set to COM (see Table 9-9, Node IP Options)and you change Port Use to Terminal, the Default IP Destination is forced toNone.

Terminal – The COM port is used for the asynchronous terminal connection.

Net Link – The COM port is the network communications link to the IP network orIP device port.

NOTE: If the COM port is configured for Net Link and it is used to connect to anexternal modem, there is a potential security risk of an unauthorized usergaining access to the NMS or other devices on the LAN for which thisdevice has routing table entries.

Data Rate (Kbps)

Possible Settings: 9.6, 14.4, 19.2, 28.8, 38.4, 57.6, 115.2Default Setting: 19.2

Specifies the rate for the COM port in kilobits per second.

9.6 – 115.2 kbps

Character Length

Possible Settings: 7, 8Default Setting: 8

Specifies the number of bits needed to represent one character.

NOTE: Character length defaults to 8 and cannot be changed if Port Use is set toNet Link.

7 – Sets the character length to seven bits.

8 – Sets the character length to eight bits. Use this setting if using the COM port as thenetwork communication link.


9-399820-A2-GB20-00 March 1999


Parity

Possible Settings: None, Even, OddDefault Setting: None

Provides a method of checking the accuracy of binary numbers for the COM port. Aparity bit is added to the data to make the “1” bits of each character add up to either anodd 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 as specified by this configuration option.

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

Possible Settings: 1, 2Default 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 Default Setting: Disable

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.

Login Required


Determines whether a user ID and password (referred to as the login) is required inorder to log on to the asynchronous terminal connected to the COM port.

� Login Required only appears if Port Use is set to Terminal.

Enable – Requires a login to access the menu-driven user interface.

Disable – Does not requires a login.


9-40 9820-A2-GB20-00March 1999


Port Access Level

Possible Settings: Level-1, Level-2, Level-3Default Setting: Level-1

Specifies level of user access privilege for an asynchronous terminal connected to theCOM port. If a login is required for the port, the effective access level is determined bythe user’s access level. When a login is not required, the effective access level isdetermined by this option.

� Port Access Level only appears if Port Use is set to Terminal.

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.

CAUTION: Before changing the communication port’s access level to Level-2 or 3,make sure that the Telnet Session Access Level is set top Level-1 and atleast one Login ID is set to Level-1. Otherwise, access will be lost. If thisoccurs, you must reset the unit to the factory defaults and begin theconfiguration process again.

Level-2 – Allows limited access and control of the device. The user can monitor andperform diagnostics, display status and configuration option information.

Level-3 – Allows limited access with monitoring control only. The user can monitor anddisplay status and configuration screens only.

NOTE: The effective access level is always the lowest one assigned to either theport 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 bepermitted for the port.

Inactivity Timeout


Determines whether a user session is disconnected after a specified time of inactivity(no keyboard activity).

� Inactivity Timeout only appears if Port Use is set to Terminal.


Enable – Disconnects user session after the specified time of inactivity.

Disable – Does not disconnect user session.


9-419820-A2-GB20-00 March 1999


Disconnect Time (Minutes)


Determines the amount of lapsed time before disconnecting a user session in minutes.� Disconnect Time (Minutes) only appears if Port Use is set to Terminal.


1 – 60 – Sets the time from 1 to 60 minutes (inclusive).

IP Address


Specifies the IP address needed to access the unit. Only in effect when the COM port isconfigured as a network communication link (Port Use option is set to Net Link, seeTable 9-15).

� IP Address only appears if Port Use is set to Net Link.

001.000.000.000 – 223.255.255.255 – Shows the IP address for the COM port, whichyou can view or edit. The first byte (i.e., nnn.255.255.255) can be any number from 001through 223, excluding 127. Remaining bytes (i.e., 223.nnn.nnn.nnn) can be anynumber from 000 through 255. Leading zeros are required.

Clear – Clears the IP address for the COM port and fills the address with zeros( i.e., 000.000.000.000).

Subnet Mask


Specifies the subnet mask needed to access the unit. Only in effect when the COM portis configured as a network communication link (Port Use option is set to Net Link, seeTable 9-15, Communication Port Options).

� Subnet Mask only appears if Port Use is set to Net Link.

000.000.000.000 – 255.255.255.255 – Shows the subnet mask for the COM port, whichyou can view or edit.

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 createsa 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.


9-42 9820-A2-GB20-00March 1999


Link Protocol

Possible Settings: PPP, SLIPDefault Setting: PPP

Specifies the link-layer protocol to be used. Only in effect when the COM port isconfigured as a network communication link (Port Use option is set to Net Link, seeTable 9-15, Communication Port Options).

� Link Protocol only appears if Port Use is set to Net Link.

PPP – Point-to-Point Protocol.

SLIP – Serial-Line Internet Protocol.

RIP

Possible Settings: None, Proprietary, Standard_outDefault Setting: None

Specifies which Routing Information Protocol (RIP) is used to enable routing ofmanagement data between devices.

� RIP only appears if Port Use is set to Net Link.

None – No routing is used. Use this setting when the device connected to the COM portis not a 9000 Series or 31xx Series device.

Proprietary – A proprietary variant of RIP version 1 is used to communicate routinginformation only between devices to enable routing of IP traffic. Use this setting whenthe FrameSaver unit is connected to another 9000 Series or 31xx Series device throughthe COM port.

Standard_out – The device will send standard RIP messages to communicate routinginformation about other FrameSaver units in the network. Standard RIP messagesreceived on this link are ignored.

NOTE: The router must be configured to receive RIP on the port connected to theCOM 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 IPInformation has been set up (see Configuring Node IP Information onpage 9-9).


9-439820-A2-GB20-00 March 1999

Configuring the COM Port to Support an External Modem

Select External Modem (on Com Port) to display or change the configurationoptions that control call processing for an external device attached to the COMport (see Table 9-16).

Main Menu →Configuration →Management and Communication →External Modem (on Com Port)

NOTE:A standard EIA-232 crossover cable is required when connecting an externalmodem to the FrameSaver unit’s COM Port. See Standard EIA-232-DCrossover Cable in Appendix E, Cables, Connectors, and Pin Assignments,for cable pin assignments.

Table 9-16. External Modem (on Com Port) Options (1 of 2)

External Modem Commands

Possible Settings: Disable, ATDefault Setting: Disable

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 theexternal device. All AT command strings will end with a carriage return (hex 0x0D) and aline feed (hex 0x0A).

CAUTION: Do not use this setting if you have an async terminal connected to theCOM port.

Dial-In Access


Controls whether external devices can dial-in to the FrameSaver unit through the COMport (based on the Port Use option setting).

� Dial-In Access does not appear if External Modem Commands is disabled.

Enable – Answers incoming calls and establishes connection to the remote terminal orIP network.

Disable – Does not answer incoming calls.


9-44 9820-A2-GB20-00March 1999

Table 9-16. External Modem (on Com Port) Options (2 of 2)

Alternate IP Address


Specifies the Alternate IP Address for the COM port when the alternate phone directoryis used. If this configuration option is not configured (i.e., it is zero), the COM port’sprimary IP Address is used when the alternate telephone directory is used.

� Alternate IP Address only appears if External Modem Commands is set to AT.� Only in effect when the COM port is configured as a network communication link

(Port Use is set to Net Link, see Table 9-15, Communication Port Options).

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 numberfrom 001 through 223, excluding 127. Remaining bytes (i.e., 223.nnn.nnn.nnn) can beany number from 000 through 255. Leading zeros are required.

Clear – Clears the Alternate IP Address for the COM port and fills the address withzeros ( i.e., 000.000.000.000).

Alternate Subnet Mask


Specifies the Alternate Subnet Mask for the COM port when the alternate phonedirectory is used.

� Alternate Subnet Mask only appears if External Modem Commands is set to AT.� Only in effect when the COM port is configured as a network communication link

(Port Use is set to Net Link, see Table 9-15, Communication Port Options).

000.000.000.000 – 255.255.255.255 – Shows the subnet mask for the COM port, whichyou can view or edit.

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 createsa 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.

10-19820-A2-GB20-00 March 1999

Security and Logins

10This chapter provides information about the following:

� Limiting Access on page 10-1.

� Controlling Asynchronous Terminal Access on page 10-2.

� Controlling Telnet Access on page 10-3.

� Controlling FTP Access on page 10-4.

� Controlling External COM Port Device Access on page 10-5.

� Controlling SNMP Access on page 10-6.

� Creating a Login on page 10-10.

� Deleting a Login on page 10-11.

Limiting Access

The FrameSaver unit provides access security through the following:

� Asynchronous (async) terminal

� Telnet

� FTP

� External devices

� SNMP

Up to two direct or Telnet sessions can be active at any given time; that is, youcan have two simultaneous Telnet sessions, or one Telnet session and one activeasync terminal session, or two simultaneous async terminal sessions.

Security and Logins

10-2 9820-A2-GB20-00March 1999

Controlling Asynchronous Terminal Access

The FrameSaver unit provides the following methods for limiting direct access tothe asynchronous user interface on the communication (COM) port:

� Requiring a login.

� Assigning an access level to the port.

See Configuring the Communication Port in Chapter 9, Configuration Options, formore information about communication port configuration options.

� Procedure

To limit COM port access to the async user interface:



The Communication Port Options screen appears.

2. Select and set the following configuration options, as appropriate:


Require a login Login Required to Enable.

NOTE: User ID and password combinationsmust be defined. See Creating a Login onpage 10-10.

Limit the effective access level toLevel-3 or Level-2

Port Access Level to Level-2 or Level-3.

NOTE: Regardless of a user’s login accesslevel, a user cannot operate at a level higherthan the access level specified for the port(e.g., if a user has a Level-1 login and Level-2port access has been set, the Level-1 usercan only operate as a Level-2 user).

If you are going to allow Level-1 users toconfigure the unit, keep the access at Level-1.

NOTE:See Resetting the FrameSaver Unit in Chapter 12, Operation andMaintenance, should you inadvertently be locked out.

3. Press Ctrl-a and Save your changes.

See Configuring the Communication Port in Chapter 9, Configuration Options, formore information about communication port configuration options.

Security and Logins

10-39820-A2-GB20-00 March 1999

Controlling Telnet Access

The FrameSaver unit provides the following methods for limiting access througha Telnet session:

� Disabling Telnet access completely.

� Requiring a user ID or password to login.

� Assigning an access level for Telnet sessions.

� Procedure

To limit access through a Telnet Session:


Main Menu →Configuration →Management and Communication →Telnet and FTP Sessions

The Telnet and FTP Session Options screen appears.

2. Select and set the following configuration options, as appropriate.


Disable Telnet Telnet Session to Disable.



Assign an access level Session Access Level to Level-2 or Level-3.

NOTE: Regardless of a user’s login accesslevel, a user cannot operate at a level higherthan the access level specified for the Telnetsession (e.g., if a user has a Level-1 login andLevel-2 telnet access has been set, theLevel-1 user can only operate as a Level-2user).

If you are going to allow users to configure theunit, keep the access at Level-1.


See Configuring Telnet and/or FTP Session Support in Chapter 9, ConfigurationOptions, for more information about communication port configuration options.

Security and Logins

10-4 9820-A2-GB20-00March 1999

Controlling FTP Access

The FrameSaver unit provides the following methods for limiting access througha FTP session:

� Disabling FTP access completely.

� Requiring a user ID or password to login.

� Bandwidth of FTP.

� Procedure

To limit access through a FTP Session:


Main Menu →Configuration →Management and Communication →Telnet and FTP Sessions

The Telnet and FTP Session Options screen appears.



Disable FTP FTP Session to Disable.



If you want to allow users to configure the unitor perform file transfers, including downloads,keep the access at Level-1.

Level-1 access is required to downloadsoftware to the unit, or to upload or downloadconfiguration files. Level-3 is sufficient forNMS access for SLV historical information.

Limit bandwidth for FTP FTP Max Receive Rate to a rate less than thenetwork line speed, typically less than orequal to the CIR.

This method is not recommended if SLVreports are desired since FTP is required togenerate the reports.


See Configuring Telnet and/or FTP Session Support in Chapter 9, ConfigurationOptions, for more information about setting FTP options.

Security and Logins

10-59820-A2-GB20-00 March 1999

Controlling External COM Port Device Access

The FrameSaver unit allows you to control whether dial-in access for an externaldevice (modem) is allowed on the communication port. Use the External DeviceOptions screen to set the necessary configuration options to allow dial-in accessthrough the COM port.

� Procedure

To control dial-in access:


Main Menu →Configuration →User Interface →External Device (Com Port)

The External Device Options screen appears.

2. Enable the Dial-In Access configuration option.

This option only appears when the External Device Commands option is setto AT or Other.


See Configuring the COM Port to Support an External Device in Chapter 9,Configuration Options, for more information about external device communicationport configuration options.

Security and Logins

10-6 9820-A2-GB20-00March 1999

Controlling SNMP Access

The FrameSaver unit supports SNMP Version 1, which only provides limitedsecurity through the use of community names. There are three methods forlimiting SNMP access:

� Disabling SNMP access.

� Assigning SNMP community names and access type.

� Assigning IP addresses of NMSs that can access the FrameSaver unit.

Disabling SNMP Access

The General SNMP Options screen provides the configuration option to disableSNMP access to the unit. When this configuration option is disabled, theFrameSaver unit will not respond to any SNMP messages.

� Procedure

To disable SNMP access:



The General SNMP Options screen appears.

2. Set SNMP Management to Disable.


See Configuring SNMP Management in Chapter 9, Configuration Options, formore information about General SNMP Management configuration options.

Security and Logins

10-79820-A2-GB20-00 March 1999

Assigning SNMP Community Names and Access Levels

The General SNMP Options screen provides the configuration options that allowthe FrameSaver unit to be managed by an SNMP manager supporting the SNMPprotocol. Use this screen to:

� Assign the SNMP community names that are allowed to access theFrameSaver unit’s Management Information Base (MIB).

� 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:



The General SNMP Management Options screen appears.



Assign SNMP community names Community Name 1 and Community Name 2to a community name text, up to 255characters in length.

Assign the type of access allowedfor the SNMP community names

Name 1 Access and Name 2 Access to Reador Read/Write.


See Configuring SNMP Management in Chapter 9, Configuration Options, formore information about General SNMP Management configuration options.

Security and Logins

10-8 9820-A2-GB20-00March 1999

Limiting SNMP Access Through IP Addresses

The FrameSaver unit provides an additional level of security by:

� Limiting the IP addresses of the NMSs that can access the FrameSaver unit.

� Performing validation checks on the IP address of SNMP managementsystems attempting to access the FrameSaver unit.

� Specifying the access allowed for the authorized NMS when IP addressvalidation is performed.

The SNMP NMS Security Options screen provides the configuration options thatdetermine whether security checking is performed on the IP address of SNMPmanagement systems attempting to communicate with the unit.

Make sure that SNMP Management is set to Enable.

Menu selection sequence:Main Menu →Configuration →Management and Communication →General SNMP Management → SNMP Management: Enable

See Configuring SNMP Management in Chapter 9, Configuration Options, formore information about SNMP management configuration options.

Security and Logins

10-99820-A2-GB20-00 March 1999

� Procedure

To limit SNMP access through IP addresses:


Main Menu →Configuration →Management and Communication →SNMP NMS Security

The SNMP NMS Security Options screen appears.



Enable IP address checking NMS IP Validation to Enable.

Specify the number (between 1and 10) of SNMP managementsystems that are authorized tosend SNMP messages to theFrameSaver unit

Number of Managers to the desirednumber.

Specify the IP address(es) thatidentifies the SNMP manager(s)authorized to send SNMPmessages to the FrameSaver unit

NMS n IP Address to the appropriateIP address.

Specify the access allowed for anauthorized NMS when IP addressvalidates is performed

Access Level to Read or Read/Write.


See Configuring SNMP NMS Security in Chapter 9, Configuration Options, formore information about SNMP NMS Security configuration options.

Security and Logins

10-10 9820-A2-GB20-00March 1999

Creating a Login

A login ID and password is required if security is enabled.* You can define acombination of six login/passwords. Each login must be unique and have aspecified access level.

� Procedure

To create a login ID and password:


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 characters.

Re-enter password Password again to verify that you entered thecorrect password into the device.

Access Level Access level: 1, 2, or 3.

� Level-1 – User can add, change, anddisplay configuration options, save, andperform device testing.

� Level-2 – User can monitor and performdiagnostics, display status andconfiguration option information.

� Level-3 – User can only monitor anddisplay status and configuration screens.

Note: Make sure at least one login is setup forLevel-1 access or you may be inadvertentlylocked out.

NOTE:See Resetting the FrameSaver Unit in Chapter 12, Operation andMaintenance, should you inadvertently be locked out.


When Save is complete, Command Complete appears at the bottom of thescreen and the cursor is repositioned at the Login ID field, ready for anotherentry.

See Configuring SNMP NMS Security in Chapter 9, Configuration Options, formore information about security configuration options.

* Security is enabled by the Communication Port’s Login Required option. For a Telnet or FTP session, the Telnet orFTP Session’s Telnet Login Required or FTP Login Required option is also enabled.

Security and Logins

10-119820-A2-GB20-00 March 1999

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:


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/recordsuntil you find the one to be deleted.

4. Once the correct record is displayed, select Delete and press Enter.

5. Press Ctrl-a and Save your deletion.

When the deletion is complete, Command Complete appears at the bottomof the screen. 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.

Security and Logins

10-12 9820-A2-GB20-00March 1999


11-19820-A2-GB20-00 March 1999

Displaying System Information

11This chapter includes the following information:

� Displaying Unit Identification on page 11-2.

� Displaying LED and Control Leads on page 11-3.

� Statuses:

— Self-Test Results Messages on page 11-5.

— Health and Status Messages on page 11-6.

— Test Status Messages on page 11-9.

— Device Messages on page 11-10.

— Network LMI-Reported DLCIs Status on page 11-15.

— PVC Connection Status on page 11-16.

� Performance Statistics:

— Service Level Verification performance Statistics on page 11-19.

— DLCI Performance Statistics on page 11-20.

— Frame Relay Performance Statistics on page 11-21.


11-2 9820-A2-GB20-00March 1999

Displaying Unit Identification

Use the Identity screen to view identification information about the system andthe FrameSaver unit. This information is useful if you are purchasing additional orreplacement units and/or making firmware upgrades.

� Procedure

To view identity information for the system:

1. Use the following menu selection sequence, pressing Enter after eachselection:

Main Menu →Status → Identity

2. The following system information is available for viewing. Use the right (→)and left (←) arrow keys to scroll additional text into view.

View this field . . . To find the . . .

System Name Domain name for the SNMP-managed node.

System Contact Contact person for this SNMP-managed node.

System Location Physical location for this SNMP-managed node.

NAM

NAM Type The type of FrameSaver unit installed, referred to as a networkaccess module, or NAM (e.g., DP FR NAM).

Serial Number FrameSaver unit’s 7-character serial number.

CurrentSoftware Revision

Software version currently being used by the FrameSaver unit.Format nn.nn.nn consists of a 6-digit number that representsthe major and minor revision levels.

AlternateSoftware Revision

Software version that has been downloaded into theFrameSaver unit, but has not yet been implemented. Formatis the same as for the Current Software Revision.

� If the flash memory is currently being downloaded,In Progress displays.

� If no download has occurred or the download was notsuccessful, Invalid displays.

Hardware Revision FrameSaver unit’s hardware version. Format nnnn-nnxconsists of a 4-digit number, followed by 2 digits and1 alphabetic character.


11-39820-A2-GB20-00 March 1999

Displaying LEDs and Control Leads

Use the following menu selection to display and monitor LEDs and control leads.This feature is useful when monitoring remote units or troubleshooting controllead problems:

Main Menu →Status →Display LEDs and Control Leads

� Inverse video of the LED indicates that the LED is on.

� Normal video indicates that the LED is off.

FrameSaver 9820 LEDs

The FrameSaver 9820 unit’s faceplate includes LEDs ( light-emitting diodes)that provide status on the FrameSaver unit, its network data port, and its userdata port. The faceplate shown is a remote FrameSaver 9820.

99-16201a

OK ALM TSTOK OK

9820

NETWORK PORTFrameSaverTM SLVFrameSaverTM SLV

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

main/status/leds PARADYNE 9820Device Name: Node A 1/26/1998 23:32

DISPLAY LEDS & CONTROL LEADS

DP FR NAM

GENERAL NETWORK1 Port-1 OK OK OK Alarm TXD TXD Test RXD RXD

RLSD(Ind) DTRDSR RTS(Control)CTS TM

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– ESC for previous menu M ainMenu E xit

Refresh


11-4 9820-A2-GB20-00March 1999

LED Descriptions

Table 11-1 describes what the LEDs indicate.

Table 11-1. General LEDs

Label Indication Color What It Means

OK 1 Power andOperationalStatus

Green ON – FrameSaver unit has power and is operational.

OFF – FrameSaver unit is in a power-up self-test, or there is a failure.

ALM OperationalAlarm (Fail )

Red ON – FrameSaver unit has just been reset, or an error or fault has been detected.

Error/fault/alarm conditions:

� Clock out of Range

� Loss of Signal (LOS)

� Device Fail

� Self-Test Failed

� LMI Down

� DLCI Down

� Network Communication Link Down

� CTS Down

� DTR Down

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.

Network Data Port LED

OK OperationalStatus

Green ON – The interchange circuits for the portare in the correct state to transmit andreceive data.

OFF – The port is idle. Occurs if the port isconfigured to monitor DSR, CTS, orRLSD and the leads are not asserted,or TM is asserted on the DCE, or.avalid clock signal cannot be detectedon the port.

User Data Port LED

OK OperationalStatus

Green ON – The interchange circuits for the portare in the correct state to transmit andreceive data.

OFF – The port is idle. Occurs if the port isconfigured to monitor DTR and/or RTSand the lead(s) is not asserted.


11-59820-A2-GB20-00 March 1999

Statuses

Status information is useful when monitoring the FrameSaver unit. Use the Statusmenu to display information concerning:

� System and Test Status – Health and Status, Self-Test Results, Test Status

� Network LMI Reported DLCIs – DLCIs, Status, and CIR (Kbps)

� PVC Connection Status – Source and Destination Links, DLCIs, EDLCIs, andconnection status

NOTE:Status messages contained in the following sections are inalphabetical order.

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 tables describe the System and Test Status Messages:

� Table 11-2. Self-Test Results Messages

� Table 11-3. Health and Status Messages

� Table 11-4. Test Status Messages

Self-Test Results Messages

These self-test result messages appear in the Self-Test Results field at the top ofthe System and Test Status screen.

Table 11-2. Self-Test Results Messages

Message What It Indicates What To Do

Failure xxxxxxxx An internal failure occurred(xxxxxxxx represents an8-digit hexadecimal failurecode for use by servicepersonnel).

1. Record the failure code.

2. Reset the unit.

3. Contact your servicerepresentative.

Passed No problems were foundduring power-up or reset.

No action needed.


11-6 9820-A2-GB20-00March 1999

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 thebottom of the screen (right corner).

Table 11-3. Health and Status Messages (1 of 3)


Auto-ConfigurationActive

Auto-Configuration featureis active, which allowsautomatic configuration andcross-connection of DLCIsas they are reported by thenetwork LMI.

No action needed unless youwant to disable this feature.

Back-to-Back Mode isActive

The operating mode hasbeen configured forback-to-back(Control →ChangeOperating Mode).

The FrameSaver unit canbe connected to anotherFrameSaver unit without aframe relay switch betweenthem.

See Back-to-BackOperation in Chapter 3,Typical Applications, for anillustration.

No action needed unless youwant to disable this feature.

This feature is useful for productdemonstrations or for apoint-to-point configuration usinga leased line.

CTS down to Port-1Device

The Port-1 CTS controllead on the FrameSaverunit is off.

Check DTR and RTS fromPort-1.

Device Fail yyyyyyyy An internal error has beendetected by the operatingsoftware.

1. Provide the displayed 8-digitfailure code (yyyyyyyy) to yourservice representative.

2. Clear the Device Failmessage.

Main Menu →Control →Clear Device Fail


11-79820-A2-GB20-00 March 1999


Message What To DoWhat It Indicates

DLCI nnnn Down,frame relay link 1, 2

The DLCI for the specifiedframe relay link is down.

Verify that the network LMI is up.If it is, contact network provider.

DTR down from Port-1Device

The DTR control lead onthe device connected toPort-n is disasserted.

Examine the attached DTE andcable connected to theFrameSaver unit’s port.

1. Check that the Port-1 cable issecurely attached at bothends.

2. Check the status of theattached equipment.

Clock Out of Range atNetwork

A valid port rate cannot bedetected because the:

� Unit is auto-rating on thenetwork data port, tryingto detect a valid portrate.

� Rate detected is greaterthan the highest port ratesupported by the unit.– FrameSaver 9820

rates: 64 or 128 kbps– FrameSaver 9820-C

rates: 64 – 2048 kbpsin 64 kbps increments

If the message continues toappear:

1. Confirm that there is a validclock on the cable.

2. Manually configure the NTUfor a rate supported by theFrameSaver unit.

3. If necessary, replace theFrameSaver unit with a higherspeed FrameSaver unitcapable of supporting the NTUclock rate.

1 nnnn indicates a DLCI number of 16 through 1007;2 frame relay link is one of the following:

– Net1-FR1. The frame relay link specified for the network data port, Network 1.

– Port-1. The frame relay link associated with the user data port.


11-8 9820-A2-GB20-00March 1999



LMI Down, frame relaylink 2

The Local ManagementInterface is down for thespecified frame relay link.

For the Network Data Port:

1. If LMI was never up, verifythat the LMI Protocol settingreflects the LMI type beingused.

2. Verify that Frame RelayPerformance Statistics showLMI frames being transmitted.

If all of the above have beenverified and the physical link isnot in Alarm, contact networkprovider.

For User Data Port:

1. Check that the DTE cable issecurely attached at bothends.

2. Verify that Transmit ClockSource and Invert TransmitClock options are properlyconfigured.

3. Verify that Frame RelayPerformance Statistics showLMI frames being received. Ifno frames are being received:– Check the attached device.– Verify that the LMI Protocol

setting reflects the LMI typebeing used.

LOS at Network 1 A Loss of Signal (LOS)condition is detected on thenetwork data port. Eitherthe control leads on thenetwork data port aredeasserted, the TM lead isasserted, or no clock isdetected from the NTU.

1. Network cable problem.

2. NTU or network facilityproblem.

1. Check that the network cableis securely attached at bothends.

2. Contact your network provider.

Network Com LinkDown

The communication link forthe COM port is down, andthe COM port is configuredfor Net Link.

Check the router connected tothe COM port.

2 frame relay link is one of the following:– Net1-FR1. The frame relay link specified for the network data port, Network 1.



11-99820-A2-GB20-00 March 1999

Test Status Messages

These test messages appear in the right column of the System and Test Statusscreen.

You have the option of allowing the test to continue or aborting the test. Refer toChapter 13, Troubleshooting, for more information on tests, including how to startand stop them.

Table 11-4. Test Status Messages

Message What It Indicates

DTE External LB Active, Port-1 An external DTE Loopback is running on thespecified port.

DTE Initiated Ext. LB Active, Port-1 DTE has initiated an external DTE Loopback onthe specified port.

FCC Test Active Should never see this message.

Lamp Test Active The Lamp Test is active, causing the LEDs on thefaceplate to flash on and off.

Monitor Pttn Active, DLCI nnnn,frame_relay_link 1, 2

FrameSaver unit is monitoring a test pattern on thespecified DLCI on the specified frame relay link.

No Test Active No tests are currently running.

PVC Loopback Active, DLCI nnnn,frame_relay_link 1, 2

FrameSaver unit is monitoring the selected testpattern on the specified DLCI for the interface.

Send Pttn Active, DLCI nnnn,frame_relay_link 1, 2

FrameSaver unit is monitoring the selected testpattern on the specified DLCI for the interface.

1 nnnn indicates a DLCI number of 16 through 1007.2 frame_relay_link is one of the following:

– Net1-FR1. The frame relay link specified by for the network data port, Network 1.



11-10 9820-A2-GB20-00March 1999

Device Messages

These messages appear in the messages area at the bottom of the screens.All device messages are listed in alphabetical order.

Table 11-5. Device Messages (1 of 5)


Access level is n ,Read-only.

User’s access level is 2or 3; user is not authorizedto change configurations.

No action needed.

Already Active Test selected is alreadyrunning.

� Allow test to continue.

� Select another test.

� Stop the test.

Blank EntriesRemoved

New had been selectedfrom the Administer Loginsscreen, no entry was made,then Save was selected.

� No action needed.

� Reenter the Login ID,Password, and Access Level.

Cannot delete TrapManager

Delete was selected fromthe Management PVCsOptions screen, but thePVC had been defined as atrap destination.

No action needed, or configureanother path for traps and tryagain.

Command Complete Configuration has beensaved or all tests havebeen aborted.

No action needed.

Connection Refused

(Seen at an FTPterminal.)

Two menu-driven userinterface sessions arealready in use when aTelnet session wasattempted.

Wait and try again.

Destination NotUnique

Destination entered isalready being used.

Enter another destinationindicator.

DLCI in connection.Delete connection first

User tried to delete a DLCIthat was part of aconnection.

� No action needed, or

� Delete the connection, thendelete the DLCI.

Duplicate DLCINumber

DLCI number entered is notunique for the frame relaylink.

No action needed; previouscontents of the DLCI numberfield is restored.

File Transfer Complete


A file transfer wasperformed successfully.

Switch to the newly downloadedsoftware.

See Changing Software inChapter 12, Operation andMaintenance.


11-119820-A2-GB20-00 March 1999



File Transfer Failed –Invalid file


A file transfer wasattempted, but it was notsuccessful.

� Try again, making sure youtype the filename correctly.

� Exit the FTP session, ordownload another file.See Changing Software inChapter 12, Operation andMaintenance.

Invalid Character (x ) A non-valid printable ASCIIcharacter has beenentered.

Reenter information using validcharacters.

Invalid date: must bemm/dd/yyyy

A non-valid date wasentered on the Data & Timescreen.

Reenter the date in themonth/day/4-digit year format.

Invalid date and/ortime

A non-valid date or timewas entered on the Data &Time screen. The datedoes not exist (e.g.,February 29th).

Reenter the date in themonth/day/4-digit year format.

Invalid time: must behh:mm

A non-valid system timewas entered on the Data &Time screen.

Reenter the time in thehour:minutes format.

Invalid – AlreadyActive

A test was already inprogress when it wasselected.

No action needed.

Invalid Password Login is required and anincorrect password wasentered; access is denied.

� Try again.

� Contact your systemadministrator to verify yourpassword.

Invalid TestCombination

A conflicting loopback orpattern test was in progresswhen Start was selected tostart another test, or wasactive on the same oranother interface whenStart was selected.

� Wait until other test ends andmessage clears.

� Cancel all tests from the Testscreen (Path: main/ test ).

� Stop the test from the samescreen the test was startedfrom.

Limit of six Login IDsreached

An attempt to enter a newlogin ID was made, and thelimit of six login/passwordcombinations has beenreached.

� Delete another login/passwordcombination.

� Reenter the new login ID.


11-12 9820-A2-GB20-00March 1999



Limit of Mgmt PVCsreached

New was selected from thePVC Connection Table andthe maximum number ofmanagement PVCs hasalready been created.

� Do not create themanagement PVC.

� Delete another managementPVC, and try again.

Limit of PVCConnections reached

New was selected from thePVC Connection Table andthe maximum number ofPVCs has already beencreated.

� Do not create the PVCconnection.

� Delete another PVCconnection, and try again.

Name Must be Unique Name entered for amanagement PVC hasbeen used previously.

Enter another 4-character namefor the logical/management link.

No Destination LinkDLCIs Available

New was selected from thePVC Connection Table, buteven though DLCIs areavailable to form aconnection, no DLCIs areavailable on the networklink, which is a suitablePVC Destination.

Configure additional DLCIs forthe network link and try again.

No DLCIs available forconnection

New was selected from thePVC Connection Table, butall configured DLCIs havebeen connected.

No action needed, or configuremore DLCIs and try again.

No DLCIs available forconnection

New was selected from theManagement PVCs optionscreen, but all Link/DLCIpairs have been connected.

Configure more network and/orPort-1 Links/DLCIs pairs and tryagain.

No DLCIs Available forMgmt PVC

New was selected from theManagement PVCs optionscreen, but all configuredDLCIs have beenconnected.

Configure more network and/orPort-1 DLCIs and try again.

No DLCIs Defined DLCI Records was selectedfrom an interface’sConfiguration Edit/Displaymenu, and no DLCIRecords have been createdfor this interface.

Select New and create a DLCIrecord.


11-139820-A2-GB20-00 March 1999



No more DLCIsallowed

New or CopyFrom wasselected from an interface’sDLCI Records configurationscreen, and the maximumnumber of DLCI Recordshad already been reached.

Delete a DLCI, then create thenew DLCI Record.

No PrimaryDestination LinkDLCIs Available

New or Modify wasselected from the PVCConnection Table, but eventhough DLCIs are availableto form a connection, noDLCIs are available on thenetwork link, which is asuitable Primary PVCDestination.

Configure additional DLCIs forthe network link and try again.

If a network DLCI has beenentered as a Source DLCI:

1. Change the Source DLCI to auser data port DLCI.

2. Enter the network DLCI as thePVC’s Primary Destination.

No Security Recordsto Delete

Delete was selected fromthe Administer Loginscreen, and no securityrecords had been defined.

� No action needed.

� Enter a security record.

Password MatchingError – Re-enterPassword

Password entered in theRe-enter Password field ofthe Administer Loginsscreen does not matchwhat was entered in thePassword field.

� Try again.

� Contact your systemadministrator to verify yourpassword.

Permission Denied


A file transfer wasattempted, but the:

� User did not haveLevel 1 security.

� Wrong file was specifiedwhen the put commandwas entered.

� User attempted toupload a program filefrom the unit.

� See your system administratorto get your security levelchanged.

� Try again, entering the correctfile with the put command.

� Enter the put commandinstead of a get command;you can only transfer files tothe unit, not from it.See Performing a SoftwareUpgrade in Chapter 12,Operation and Maintenance.


11-14 9820-A2-GB20-00March 1999



Please Wait Command takes longerthan 5 seconds.

Wait until message clears.

Resetting Device,Please Wait ...

Yes (or y) was entered inthe Reset COM Port usagefield of the System Pausedmenu.

No action needed.

Test Active No higher priority healthand status messages exist,and a test is running.

� Contact service provider if testinitiated by the network.

� Wait until the test ends andmessage clears.

� Cancel all tests from the Testscreen (Path: main/test ).

� Stop the test from the samescreen the test was startedfrom.

User Interface Alreadyin Use

Two Telnet sessions arealready in use when anattempt to access themenu-driven user interfacethrough the COM port ismade.

IP addresses and logins ofthe users currentlyaccessing the interface arealso provided.

� Wait and try again.

� Contact one of the IP addressuser and request that theylogoff.

User Interface Idle Previously active session isnow closed/ended, andaccess via the COM port isnow available.

Log onto the FrameSaver unit.

Session has been endeddue to timeout.

No action needed.

Value Out of Range CIR entered for the DLCI isa number greater than themaximum allowed.

Enter a valid CIR (0 – 2048000).

Excess Burst Size enteredfor the DLCI is a numbergreater than the maximumallowed.

Enter a valid Excess Burst Size(0 – 2048000).

DLCI Number entered isless than 16 or greater than1007.

Enter a valid number(16 – 1007).


11-159820-A2-GB20-00 March 1999

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 theswitch) for each DLCI, whether the DLCI is configured or not. An asteriskidentifies each DLCI contained in the device configuration. Data and LMI statusreceived on DLCIs that are not configured are passed transparently through theFrameSaver unit between the network data port and the user data port withoutmonitoring of DLCI traffic or demultiplexing/multiplexing management diagnosticsor user data. Data received on DLCIs that are not configured on other frame relaylinks is discarded.

Table 11-6. Network LMI-Reported DLCIs Status

Field Status What It Indicates

DLCI 16 through 1007 Identifies the Local ManagementInterface-reported DLCI numbersassigned to the selected interface – theidentifying number assigned to the pathbetween two frame relay FrameSaverunits’ ports.

DLCI statuses are listed in ascendingorder ( i.e., lowest number first ).

Status ActiveInactiveDeleted 1

New1

LMI-reported status of the DLCI:

� Whether the DLCI is active (capableof carrying data) in the frame relaynetwork,

� Whether it is inactive,

� Whether it has been deleted by theframe relay network, or

� Whether it has been created by theframe relay network.

CIR (bps) 0 – 2048000 Displays the committed information ratereported by the Stratacom switch. CIRinformation only appears in this columnwhen LMI Protocol is set to Standard.

If blank, the switch does not support thisfeature.

1 Appears for 10 seconds only, before the network changes Deleted to Inactive andNew to Active .


11-16 9820-A2-GB20-00March 1999

PVC Connection Status

PVC connection statuses are selected from the Status menu. Only PVCconnections with Source DLCIs configured to be Active are shown.

Follow this menu-selection sequence:

Main Menu →Status →PVC Connection Status

Table 11-7. PVC Connection Status

Field Status What It Indicates

— No PVC Connections. PVC connections have yet to bedefined.

Link Net1-FR1

MgmtPVCName

Identifies the cross-connection ofDLCIs configured for theFrameSaver unit.

� Source/destination is frame relaylink 1 on Network 1

� Virtual circuit is a managementlink 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 aDLCI.

EDLCI 0 to 62 For multiplexed DLCIs only.

Identifies an individual link/connection embedded within aDLCI.

Status Active 1

InactiveIdentifies whether the physicalinterfaces, LMIs, and DLCIs are allenabled and active for this PVCconnection.

1 For the circuit to be active, both Source and Destination Statuses must be Active.


11-179820-A2-GB20-00 March 1999

Example of PVC Connection Status Screen

ÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎÎ

main/status/connections PARADYNE 9820Device Name: Node A 01/26/1998 23:32

Page 1 of 2PVC CONNECTION STATUS

Source Primary Destination Link DLCI EDLCI Link DLCI EDLCI Status

Port-1 201 Net1-FR1 300 1 Active Port-1 202 Net1-FR1 1001 4 Active Port-1 100 Net1-FR1 1001 2 Active Port-1 204 Net1-FR1 1001 5 Active Mgmt PVC Dunedin Net1-FR1 1001 3 Active Port-1 206 Net1-FR1 1001 Active Port-1 207 Net1-FR1 1001 Active Port-1 208 Net1-FR1 500 Active Port-1 209 Net1-FR1 502 Inactive Port-1 210 Net1-FR1 504 Inactive

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––ESC for previous menu M ainMenu E xit

Refresh PgU p PgDn

Performance Statistics

Use the Performance Statistics menu to display statistical information for aselected interface. Statistical information is useful when trying to determine theseverity and frequency or duration of a condition.

Types of Statistics Collected

The following performance statistics are collected:

� Service Level Verification (SLV)

� DLCI

� Frame relay link


11-18 9820-A2-GB20-00March 1999

Displaying Statistical Information

� Procedure

To display performance statistics:

1. Use the following menu selection sequence:

Main Menu →Status →Performance Statistics

2. Select the type of information you want to view(e.g., Performance Statistics →Service Level Verification).

3. Statistics for the lowest configured multiplexed DLCI for the primary networkframe relay link appear.

The sections that follow provide information about the statistical metrics collected.

Determining Whether a Statistic Is Incrementing

When you want to observe and estimate the frequency or duration of a specificcondition (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 beginningvalue).

2. Press r for Refresh to see if it changes.

3. If the statistic is incrementing, record the ending value and the amount oftime between the beginning and ending values.

Continue to Refresh the screen until you have a sense of how serious theproblem might be.


11-199820-A2-GB20-00 March 1999

Service Level Verification Performance Statistics

These statistics appear when Service Level Verification is selected from thePerformance Statistics menu.

Follow this menu selection sequence:

Main Menu →Status →Performance Statistics → Service Level Verification

The following statistics only appear for the network data port and only if DLCIsare multiplexed (see DLCI Type option in Table 9-7, DLCI Records Options).

Table 11-8. Service Level Verification Performance Statistics

Statistic What It Indicates

Far End DLCI Number of the multiplexed DLCI at the other end of theconnection.

None is displayed if the FrameSaver unit has notcommunicated with the other end.

Inbound DroppedFrames

Number of frames transmitted by the far-end unit that weredropped in transit.

This count continues to accumulate until the maximum countvalue has been reached, then the count is reset and starts toaccumulate dropped frames again.

Dropped SLVResponses

The number of SLV inband sample packets sent that did notreceive a response.

Far End IP Addr IP Address of the unit at the other end of the multiplexed DLCIconnection.

None is displayed if the FrameSaver unit has notcommunicated with the other end, or if the unit at the other endof the multiplexed DLCI does not have an IP Addressconfigured.

Inbound DroppedCharacters

Number of bytes transmitted by the far-end unit that weredropped in transit.

This count continues to accumulate until the maximum countvalue has been reached, then the count is reset and starts toaccumulate dropped characters again.

Avg RdTrip Latency Average round trip latency, measured in milliseconds, betweenthe FrameSaver unit and the unit at the other end of themultiplexed DLCI connection. Average round trip latency ismeasured every SLV sampling interval and the average iscomputed over the previous 15 sampling intervals.

Unknown is displayed if communication with the far-end unitover the last five minutes has not been successful.

Max RdTrip Latency Same as average (Avg RdTrip Latency), but storing themaximum number of milliseconds over the sampling intervalinstead.

Unknown is displayed if communication with the far-end unitover the last 15 sampling intervals has not been successful.


11-20 9820-A2-GB20-00March 1999

DLCI Performance Statistics

These statistics appear when DLCI is selected from the Performance Statisticsmenu.


Main Menu →Status →Performance Statistics → DLCI

Table 11-9. DLCI Performance Statistics (1 of 2)


DLCI Up Since 1 Date and time that the DLCI was last declared Active after aperiod 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 theFrameSaver unit discovered that the DLCI was active in thenetwork.

DLCI Up Time 1 Days, hours, minutes, and seconds since the DLCI was lastdeclared Active after a period of inactivity. Down is displayed ifthe DLCI is inactive.

If the DLCI was Down, this is the amount of time since theDLCI recovered.

If the DLCI was never Down, this is the amount of time sincethe FrameSaver unit discovered that the DLCI was active inthe network.

Tx/Rx Characters Number of data octets (8-bit bytes) sent/received for theselected DLCI on the interface.

Tx /Rx Frames Number of frames sent/received for the DLCI on the interface.

Tx /Rx FramesWithin CIR

Number of frames sent/received for the DLCI on the interfacethat are within the committed information rate that had beenconfigured.

Tx/Rx FramesExceed CIR

Number of frames sent/received for the DLCI on the interfacethat exceed the committed information rate that had beenconfigured.

Tx/Rx FramesWith DE

Number of frames sent/received for the DLCI on the interfacethat have the discard eligible bit set.

Tx BECN Frames Number of Backward Explicit Congestion Notifications(BECNs) sent over the interface.

The network sends BECNs to notify users of data trafficcongestion in the opposite direction of the frame carrying theBECN indicator.

1 Appears only for the network data port.


11-219820-A2-GB20-00 March 1999

Table 11-9. DLCI Performance Statistics (2 of 2)


Rx BECN Frames Number of Backward Explicit Congestion Notificationsreceived over the interface.

The network receives BECNs to notify users of data trafficcongestion in the opposite direction of the frame carrying theBECN 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 trafficcongestion in the same direction of the frame carrying theFECN indicator.

Frame Relay Performance Statistics

These statistics appear when Frame Relay is selected from the PerformanceStatistics menu.


Main Menu →Status →Performance Statistics →Frame Relay

Table 11-10. Frame Relay Performance Statistics (1 of 3)


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 (8-bit bytes) sent over the interface.

Characters Received Number of data octets (8-bit 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 trafficcongestion in the same direction of the frame carrying theFECN indicator.

BECNs Received Number of Backward Explicit Congestion Notifications(BECNs) received over the interface.

The network sends BECNs to notify users of data trafficcongestion in the opposite direction of the frame carrying theBECN indicator.


11-22 9820-A2-GB20-00March 1999



Frame Relay Errors

Total Errors Number of total frame relay errors, excluding LMI errors. Shortframes, long frames, invalid DLCIs, unknown DLCIs, andunknown errors are included in this total.

Indicates that there may be a non-frame relay device on theother end of the link, or the units at either the far end or bothends of the link may be configured incorrectly.

Invalid Rx Frames Number of invalid frames received over the Network or Port-1interface.

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-1interface that were less than 5-octets ( five 8-bit bytes) inlength.

There may be a non-frame relay device on the other end ofthe link.

Long Rx Frames Number of frames received over the Network or Port-1interface that were more than 8192-octets in length.

The device on the far end of the link may be configuredincorrectly.

Invalid DLCI Number of frames received over the interface that wereaddressed to DLCIs outside the valid range; that is, a numberless than 16 or greater than 1007.

The device on the far end of the circuit may have beenconfigured incorrectly, or the DLCIs configured for theFrameSaver unit may not match the DLCIs supplied by theservice provider.

Unknown DLCI Number of frames received over the interface that wereaddressed to unknown DLCIs.

The DLCI may not have been configured, or it has beenconfigured to be Inactive.

Indicates that the FrameSaver units or devices at both oreither end of the circuit have been configured incorrectly.

Unknown Error Number of frames received over the interface that do not fallinto one of the other statistic categories.

Indicates that the error is not one that the unit can recognize.


11-239820-A2-GB20-00 March 1999



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, andsequence errors are included in this total.

Network problems.

Number of Inactives Number of times the LMI has declared the frame relay linkInactive.

Network problems.

Frame Relay HDLC Errors

Rx Total Errors Number of receiver errors on the interface. The following areincluded in this count:

� Receive invalid frames (short frames, long frames, invalidDLCIs, unknown DLCIs, and unknown errors)

� Rx Total Discards

� Receive errors (non-octet aligned frames, frames with CRCerrors, and Rx Overruns)

Rx Total Discards Number of receiver discards on the interface. The following areincluded in this count:

� Resource errors

� Rx Overruns

� Frames received when the link was down

� Inactive and disconnected DLCIs

� Inactive destination DLCIs

� Unknown EDLCIs

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, includingtransmits discards and transmit overruns.

Tx Total Discards Total number of transmit discards on the interface, includingunderrun flushes.

Tx Underruns Number of transmitter underruns (too few bits) on theinterface.


11-24 9820-A2-GB20-00March 1999


12-19820-A2-GB20-00 March 1999

Operation and Maintenance

12This section provides instructions for:

� Accessing the Unit

� Monitoring the Unit on page 12-5.

� Maintaining Modem Call Directories on page 12-6.

� FTP File Transfers on page 12-7.

� Downloading MIBs and SNMP Traps on page 12-11.

� Resetting the FrameSaver Unit on page 12-12.

� Setting Up Units for Back-to-Back Operation on page 12-14.

Accessing the Unit

If security requiring logins has been set up, follow the instructions in Logging Inand Logging Out.

Otherwise, follow the instructions in Starting a Session and Ending a Session.


12-2 9820-A2-GB20-00March 1999

Logging In

When there is no contention for the menu-driven user interface and a login isrequired, you are presented with the Login screen. Up to 10 characters can beentered in the Login ID and Password fields. Valid characters include all printableASCII characters.

� Procedure

To log in:

1. Enter your assigned login ID, and press Enter.

2. Enter your password, and press Enter.

An asterisk (*) appears in the password field for each character entered.

If the Login ID/Passwordcombination is . . . Then the . . .

Valid Main Menu appears. Begin your session.

Invalid Message, Invalid Password , is displayed online 24, and the Login screen is redisplayed.

If an invalid Login ID/Password combination isentered 3 consecutive times:

– A Telnet session is closed.– The User Interface Idle screen appears for a

directly-connected terminal.– An external modem is disconnected.– An SNMP trap is generated.

Access is denied. See your system administrator toverify your login (Login ID/Password combination).

Logging Out

When a login is required and a timeout occurs, you are automatically logged out.You will be prompted for your login next time you try to use the interface.

You can also end a session using the function keys area of the menu-driven userinterface.

� Procedure

To log out using the screen function area:

1. Press Ctrl-a to switch from the screen area to the function keys area.

2. Type e (Exit) and press Enter. The session is ended.


12-39820-A2-GB20-00 March 1999

Starting a Session

Depending on how your network is configured, you can start a session using oneof the following methods:

� Telnet session through an in-band management channel through the framerelay network.

� Telnet session through a local in-band management channel configured onthe user data port between the FrameSaver unit and the router.

� Dialing in through an external modem to the COM port.

� Direct terminal connection over the COM port.

� Telnet session over the COM port.

� Procedure

Upon beginning a session, the menu-driven user interface is blank. To activate:

1. Press Enter.

2. One of the following occurs:

I f . . . Then . . . What to Do

Security is disabled The Main Menu screenappears.

Begin your session.

Security is enabled You are prompted for alogin ID and password(see Logging In onpage 12-2).

Enter your ID and password.

If Invalid Passwordappears, see DeviceMessages in Chapter 11,Displaying SystemInformation.

Attempting to access theunit through Telnet andtwo menu-driven userinterface sessions arealready active

The messageConnectionrefused: appears.(FrameSaver unit allowsonly two connections ata time.)

Wait and try again.

See Device Messages inChapter 11, DisplayingSystem Information, foradditional information.

Attempting direct accessthrough the COM portand two menu-drivenuser interface sessionsare already active

The message UserInterface AlreadyIn Use appears withboth active user IPaddresses shown.


12-4 9820-A2-GB20-00March 1999

Ending a Session

Use the Exit function key from any screen to terminate the session.

� Procedure

To end a session:

1. Press Ctrl-a and Exit the screen. The session is terminated; the terminal isdisconnected.

2. If ending a configuration editing session, the Save Configuration screenappears with the Save Changes? prompt.

If you select . . . Then . . .

No The session is terminated without the configurationoption changes being saved.

Yes The Save Configuration To screen appears.

Select a configuration option area to save yourchanges to (Current, Customer 1, or Customer 2), andpress Return.

Configuration option changes are saved and thesession is terminated.


12-59820-A2-GB20-00 March 1999

Monitoring the Unit

The FrameSaver unit offers indicators to alert you of possible problems:

� LEDs and Control Leads

� Alarms

� SNMP Traps

Viewing LEDs and Control Lead Status via theMenu-Driven User Interface

You can monitor the same conditions monitored by the faceplate LEDs, as well asselected control lead status, using the following menu selection sequence:

Main Menu →Status →Display LEDs and Control Leads

This feature is especially useful when monitoring a remote FrameSaver unit.

See Displaying LEDs and Control Leads in Chapter 11, Displaying SystemInformation, for display, faceplate, and LED information.

Viewing Alarm and Status Messages

You can view alarm messages via the:

� Health and Status column of the System and Test Status screen.


� Messages on Line 24 of the menu-driven user interface screen.

See System and Test Status Messages in Chapter 11, Displaying SystemInformation, or Chapter 13, Troubleshooting, for additional information.

See Chapter 13, Troubleshooting, for more information on alarms.


12-6 9820-A2-GB20-00March 1999

Maintaining Modem Call Directories

Modem Call Directories are used to dial a remote device for management via anexternal modem.

See Entering Modem Directory Phone Numbers in Chapter 8, Setup, to set upmodem 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 alternatedirectory) and press Enter.

— Press the spacebar to cycle through various directories until the desireddirectory 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 enteredwhen 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 newphone number, or delete a phone number.


CAUTION:Failure to save additions or changes to Modem Call Directories willresult in your changes being lost.


12-79820-A2-GB20-00 March 1999

FTP File Transfers

The FrameSaver unit supports a standard File Transfer Protocol (FTP) serverover Transmission Control Protocol (TCP) to allow software upgrades, copyingconfigurations, and SLV statistics gathering. A complete binary image of theconfiguration files can be copied to a host to provide a backup. To use thisfeature, the unit must be configured to support Telnet and FTP Sessions.

Using this feature, you can transfer configuration files to/from a FrameSaver unitnode, program files to a FrameSaver unit node, and User History data from aFrameSaver unit node through a user data port or the network data port using amanagement PVC, or through the COM port.

Be aware of the following rules when doing a file transfer:

� You must have Access Level 1 permission to use the put and getcommands. However, you can retrieve the data file for the user historyreports regardless of access level.

� You cannot put a configuration file to the factory.cfg or current.cfg filesunder the system directory. Configuration files should be put to a customerfile (cust1.cfg or cust2.cfg), then loaded into the downloaded unit’s CurrentConfiguration via the menu-driven user interface.

� You can only put a NAM program file (nam.ocd) into a FrameSaver unit. Youcannot upload a NAM program file from the FrameSaver unit.

� Before putting a download file, you must use the bin binary command toplace the data connection in binary transfer mode.

� When transferring SLV user history information to the NMS, you can only geta uhbcfull.dat file. It is recommended that you use the NMS application to getthis information (see Transferring SLV Statistics to an NMS on page 12-11).

FrameSaver SLV units provide an additional feature that allows new software tobe downloaded in the background, using the selected bandwidth and withoutinterfering with normal operation. Downloads can be performed quickly, using thefull line speed, or at a slower rate over an extended period of time.

You initiate an FTP session to a FrameSaver unit node in the same way as youwould initiate an FTP to any other IP-addressable device.

NOTE:Loading a configuration with many DLCIs from a unit’s CustomerConfiguration 1 or 2 option area into its Current Configuration area may taketime. Allow a minute or more for the downloaded file to be put into the unit’scurrently active configuration.


12-8 9820-A2-GB20-00March 1999

� Procedure

To initiate an FTP session:

1. Start the FTP client program on your host. For example, on a Unix host,type ftp , followed by the FrameSaver unit’s IP address.

2. If a login and password are required (see Creating a Login in Chapter 10,Security and Logins), you are prompted to enter them. If not, press Enter.

The FTP prompt appears.

The starting directory is the root directory ( / ). Use standard FTP commandsduring the FTP session, as well as the following remote FTP commands.

Command Definition

cd directory Change the current directory on the FrameSaver unit node tothe 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 FrameSaver unitnode to the local directory on the host (for configuration filesonly).

remotehelp[command]

Print the meaning of the command. If no argument is given, alist 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 thecurrent directory of the FrameSaver unit node. If file2 is notspecified, the file will be named file1 on the FrameSaver unitnode.

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 FrameSaver unitnode.

bin Places the FTP session in binary-transfer mode.

Determining Whether a Download Is Completed

To see whether a download has completed, check the Identity screen (selectedfrom the Status menu). Check Alternate Software Rev. under the NAM Identitycolumn.

� If a software revision number appears, the file transfer is complete.

� If In Progress appears, the file is still being transferred.

� If Invalid appears, no download has occurred or the download was notsuccessful.


12-99820-A2-GB20-00 March 1999

Performing a Software Upgrade

If you need to upgrade the FrameSaver unit’s program code, you must transferthe upgrade of the nam.ocd file in the system memory directory using the putcommand.

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 theupgrade, 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) tothe nam.ocd file to start the upgrade.

If the message displayed is . . . Then . . .

nam.ocd: File Transfer Complete The download was successful. The file isloaded into system memory.

nam.ocd: File Transfer Failed –Invalid file

The file is not valid for this FrameSaver unit.

A different Rxxxxxx.ocd file will need to bedownloaded. Repeat the step or end theFTP session.

NOTE:During the download, a series of hash marks (#) appear. When the hashmarks stop appearing, there is a pause of about 30 seconds before thenam.ocd: File Transfer Complete message appears. Please bepatient. Do not exit from FTP at this time.

See Changing Software on page 12-10 to activate the newly downloadedsoftware.


12-10 9820-A2-GB20-00March 1999

Changing Software

Once a software upgrade is downloaded, it needs to be activated. Whenactivated, the unit resets, then executes the downloaded software. With thisfeature, 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 softwareversion and the new release that was just transferred.

If the download failed, Invalid appears in the Alternate Release fieldinstead of the new release number. Repeat the procedure on page 12-9,Performing a Software Upgrade, if this occurs.

2. Type w and press Enter to select Switch&Reset. The Are you sure?prompt appears.

3. Type y (Yes) and press Enter. The FrameSaver unit resets and beginsinstalling the newly transferred software.

4. Verify that the new software release was successfully installed as the CurrentSoftware Revision.

Main Menu →Status → Identity

NOTE:If someone opens a Telnet session and accesses the unit’s Identity(identification) screen while the FrameSaver unit is downloadingsoftware, the In Progress . . . message appears in theAlternate Software Revision field.

See Displaying Unit Identification in Chapter 11, Displaying SystemInformation, to see what is included in the unit’s Identity.


12-119820-A2-GB20-00 March 1999

Transferring SLV Statistics to an NMS

FrameSaver SLV user history statistics can be uploaded to an NMS using FTP,which is faster than other methods. The rate at which the user history data file istransferred is the rate set by the FTP MaxReceive Rate (Kbps) option (see theFTP Max Receive Rate (Kbps) configuration option in Table 9-12, Telnet and FTPSession Options).

NOTE:Using your NMS application to FTP and view statistics is recommended sincethe data file is not in user-readable format.

� Procedure

To retrieve FrameSaver SLV statistics:

1. Initiate an FTP session to the device you want to retrieve SLV statistics from.

2. Type bin to enter binary transfer mode.

3. Type cd data to change to the data directory.

4. Perform a get of the uhbcfull.dat file to start the data transfer. Once thedevice’s uhbcfull.dat file is successfully transferred, the messageuhbcfull.dat: File Transfer Complete displays.

5. Close the FTP session.

The FrameSaver unit’s SLV statistics are now available for reporting.

Downloading MIBs and SNMP Traps

Paradyne standard and enterprise MIBs are available from the Paradyne WorldWide 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 NMSapplication software. Refer to your browser or NMS manual for additionaldownload information.


12-12 9820-A2-GB20-00March 1999

Resetting the FrameSaver Unit

You can reset the FrameSaver unit in one of four ways:

� Reset it from the Control menu.

� Cycle the power.

� Reset the configuration options for the COM port, or reload the factory defaultsettings.

� Set the appropriate MIB object from NMS (see your NMS documentation).

The FrameSaver 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 unit, recycling power.

� Procedure

To reset the FrameSaver unit from the Control menu:

1. From the Main Menu screen, select Control and press Enter. The Controlmenu appears.

2. Select Reset Device and press Enter. The Are You Sure? promptappears.

3. Type y (Yes) and press Enter. The FrameSaver unit reinitializes itself,performing a device self-test.

Resetting the Unit By Cycling the Power

Disconnecting, then reconnecting the power cord resets the FrameSaver unit.


12-139820-A2-GB20-00 March 1999

Restoring Communication with a Misconfigured Unit

Misconfiguring the FrameSaver unit could render the menu-driven user interfaceinaccessible. If this occurs, connectivity to the unit can be restored via a directlyconnected async terminal.

Two methods can be used to restore access to the menu-driven user interface:

� Reset COM Port – Allows you to reset the configuration options related toCOM port usage, which includes disabling External Modem Commands. Thiscauses a reset of the FrameSaver unit and a Device Self-Test to beperformed. No security-related configuration options are changed.

� Reload Factory Defaults – Allows you to reload the Default FactoryConfiguration into the Current Configuration, which resets all configurationand control settings. This method is also useful when the user’s password(s)have been forgotten.

CAUTION:This causes the current configuration to be destroyed and aDevice Self-Test to be performed.

� Procedure

To reset COM port settings:

1. Configure the async terminal to operate at 19.2 kbps, using character lengthof 8 bits, with one stop-bit, and no parity. In addition, set the async terminal’sFlow Control to None.

2. Reset the FrameSaver unit, hold the Enter key down until the System Pausedscreen appears. (See Resetting the FrameSaver Unit on page 12-12 forvarious methods of resetting the unit.)

3. Tab to the desired option, and type y (Yes) at one of the prompts.

If selecting . . . Then the following takes place . . .

Reset COM Port usage � Port Use is set to Terminal so the asyncterminal can be used.

� Data Rate (Kbps), Character Length, Stop Bits,Parity are reset to the factory default settingsas described in Step 1.

� External Modem Commands is set to Disable.

� FrameSaver unit resets itself.

Reload Factory Defaults � All configuration and control settings are resetto the Default Factory Configuration settings.

� FrameSaver unit resets itself.

If no selection is made within 30 seconds, or No (n) is entered, theFrameSaver unit resets itself without making any configuration changes.

Once the FrameSaver unit resets itself, connectivity is restored and the MainMenu screen appears.


12-14 9820-A2-GB20-00March 1999

Setting Up Units for Back-to-Back Operation

Using this special feature, you can set up two FrameSaver units that areconnected back-to-back without frame relay switches between them, as in a testbench setup.

This configuration is shown in the illustration below.

99-16331

FrameSaverUnit

FrameRelayRouter

FrameSaverUnit

FrameRelayRouter

(CSU/DSU)NTU

(CSU/DSU)NTU

Leased LineNetwork or

Crossover Cable

DTE DCE DCE DTE


12-159820-A2-GB20-00 March 1999

Changing Operating Mode

When setting up back-to-back operation:

� One FrameSaver unit must be configured for Standard operation, which isthe setting for normal operation.

� One FrameSaver unit must be configured for Back-to-Back operation so itpresents the network side of the UNI.

The operating mode must be changed for only one of the FrameSaver units.

� Procedure

To set up back-to-back operation:

1. On the unit that will be configured for Back-to-Back Operating Mode,manually configure DLCIs; DLCIs should be configured before connecting thetwo units.

2. On one FrameSaver 9820 only , select:

Main Menu →Control →Change Operating Mode

The Change Operating Mode screen appears, with two modes:

Operating Mode Prompt

Back-to-Back The network data port will be configured toemulate a network switch. Are you sure?

Standard The network data port will be configured forstandard operation. Are you sure?

3. Select Back-to-Back Operation, and type y (Yes) at the prompt.

4. Press Ctrl-a and Save the change.

� Procedure

To return the units to normal operation:

1. On the FrameSaver unit that was set for Back-to-Back operation, change theOperating Mode back to Standard.

2. Type y (Yes) at the prompt and press Enter.

3. Press Ctrl-a and Save the change.

The FrameSaver units can now be connected to a standard frame relaynetwork.


12-16 9820-A2-GB20-00March 1999


13-19820-A2-GB20-00 March 1999

Troubleshooting

13This chapter includes the following:

� Troubleshooting Features and ways of identifying when there is a problem.

� Problem Indicators on page 13-2.

� Troubleshooting Tables on page 13-4.

� Tests Available on page 13-7.

� Test Timeout feature on page 13-8.

� Starting and Stopping a Test on page 13-9.

� Aborting All Tests on page 13-10.

� Determining Test Status and Results on page 13-10.

� PVC Tests on page 13-10.

� Physical Tests on page 13-14.

� IP Ping Test on page 13-15.

� Lamp Test on page 13-17.

Troubleshooting Features

The FrameSaver unit can:

� Detect and report faults

� Perform diagnostic tests

� Monitor statistics

Statistics are collected to help you determine how long a problem has existed.See Performance Statistics in Chapter 11, Displaying System Information.

These features ensure that your FrameSaver unit is giving you optimumperformance within your network.

Troubleshooting

13-2 9820-A2-GB20-00March 1999

Problem Indicators

The FrameSaver unit offers a number of indicators to alert you to possibleproblems:

� LEDs

� Alarms

� SNMP Traps

When monitoring the system, the System and Test Status screen can alsoindicate that there is a problem.


See System and Test Status Messages in Chapter 11, Displaying SystemInformation, for statuses and what you should do when you see one of thesemessages.

LEDs

FrameSaver faceplates have LEDs (Light Emitting Diodes) that provide statuson the:

� FrameSaver unit operation


� User data port

You can view LED information on the Display LEDs screen, selected from theStatus menu.

See Displaying LEDs and Control Leads in Chapter 11, Displaying SystemInformation, to see FrameSaver faceplates and Display LEDs and Control Leadsscreens, and to interpret the LEDs and determine whether there is a problem.

Troubleshooting

13-39820-A2-GB20-00 March 1999

Alarms

The FrameSaver unit monitors alarm conditions occurring on the:


� User data port

� Frame relay LMIs

� Frame relay DLCIs

See Monitoring the Unit in Chapter 12, Operation and Maintenance, for additionalinformation.

Supported SNMP Traps

The FrameSaver unit supports the following traps:

� warm-start

� authentication-failure

� link-up

� link-down

� enterprise-specific (those specific to this FrameSaver unit)

� RMON-specific

See Appendix C, Standards Compliance for SNMP Traps, for more informationon traps. See Monitoring the Unit in Chapter 12, Operation and Maintenance, foradditional information.

Troubleshooting

13-4 9820-A2-GB20-00March 1999

Troubleshooting Tables

The FrameSaver unit is designed to provide you with many years of trouble-freeservice. If a problem occurs, however, refer to the appropriate table in thefollowing sections for possible solutions.

FrameSaver Device Problems

Table 13-1. FrameSaver Device Problem (1 of 2)

Symptom Possible Cause Solutions

No power, or the LEDsare not lit.

The power cord is notsecurely plugged into thewall receptacle to rearpanel connection.

Check that the power cord issecurely attached at both ends.

The wall receptacle has nopower.

� Check the wall receptaclepower by plugging in someequipment that is known to beworking.

� Check the circuit breaker.

� Verify that your site is not onan energy managementprogram.

Power-Up Self-Testfails. Only Alarm LEDis on after power-up.

The FrameSaver unit hasdetected an internalhardware failure.

� Reset the FrameSaver unitand try again.

� Contact your servicerepresentative.

� Return the FrameSaver unit tothe factory (refer to Warranty,Sales, and Service Informationon page A of this document).

Cannot access theFrameSaver unit orthe menu-driven userinterface.

Login or password isincorrect, COM port ismisconfigured, or theFrameSaver unit isotherwise configured so itprevents access.

� Reset the FrameSaver unit(see RestoringCommunication with aMisconfigured Unit inChapter 12, Operation andMaintenance).


Troubleshooting

13-59820-A2-GB20-00 March 1999

Table 13-1. FrameSaver Device Problem (2 of 2)

Symptom SolutionsPossible Cause

Device Fail appearson the System andTest Status screenunder Self-Testresults.

The FrameSaver unitdetects an internalhardware failure.

� Record the 8-digit code fromthe System and Test Statusscreen.

� Reset the FrameSaver unitand try again.


An LED appearsdysfunctional.

LED is burned out. Run the Lamp Test. If the LED inquestion does not flash with theother LEDs, then contact yourservice representative.

Not receiving data. Network cable loose orbroken.

Network is down.

� Reconnect or repair the cable.

� Call the network serviceprovider.

Receiving data errorson a multiplexed DLCI,but frame relay isokay.

FR Discovery is being usedfor automatic DLCI andPVC configuration

Change the DLCI Type for eachnetwork DLCI from Multiplexed toStandard, turning offmultiplexing.

The equipment at the other endis not frame relay RFC 1490-compliant or the unit at one endof the PVC does not support theData Delivery Ratio feature.

Troubleshooting

13-6 9820-A2-GB20-00March 1999

Frame Relay PVC Problems

Table 13-2. Frame Relay PVC Problems

Symptom Possible Cause Solutions

No receipt ortransmission of data.

Cross Connection of theDLCIs are configuredincorrectly.

Verify the PVC connections,DLCIs, and CIRs agree withthose of the service provider bychecking the network-discoveredDLCIs.

DLCI is inactive on theframe relay network.

� Verify that the DLCI(s) isactive on the PVC ConnectionStatus screen. If the DLCI(s)is not active, contact theservice provider.

� Verify the LMI Reported DLCIfield on the Interface Statusscreen.

DTE is configuredincorrectly.

Check the DTE’s configuration.

LMI is not configuredproperly for the DTE ornetwork.

Configure LMI characteristics tomatch those of the DTE ornetwork.

LMI link is inactive. Verify that the LMI link is activeon the network; the Status MsgReceived counter on the NetworkFrame Relay PerformanceStatistics screen increments.

Losing Data. CIR and Excess Burst Sizeare inadequate for thethroughput required.

Verify the configured NetworkPVC settings, then increase thesettings, as needed, or decreasethroughput on the PVC.

Frame relay network isexperiencing problems.

Run PVC Loopback and Patterntests to isolate the problem, thencontact the service provider.

Out of Syncmessage.

If Monitor Pattern wasselected, it means the testpattern generator andreceiver have not yetsynchronized.

If the message persists, itmeans that 5 packets out of25 are missing or are out ofsequence.

� Verify that the FrameSaverunit at the other end isconfigured to Send Pattern.Correct unit configurations.

� Check the line’s error rate –the physical line quality.Contact service provider.

Troubleshooting

13-79820-A2-GB20-00 March 1999

Tests Available

The Test menu allows you to run loopbacks and test patterns on the FrameSaverunit, and to test the front panel LEDs. It is available to users with a securityaccess level of 1 or 2.

To access . . . Select . . .

PVC Tests 1

PVC tests for the network data port Network PVC Tests

PVC tests for the user data port Data Port PVC Tests

Data Port Physical Tests

Physical tests for the user data port Data Port Physical Test

Other Tests

IP Ping test IP Ping

Lamp Test for LEDs Lamp Test

1 PVC Tests menu selections are suppressed when no PVCs have been defined for the interface.

The following tests can be run on a PVC:

� Network or Port (Internal) PVC Loopback on page 13-12.

� Send Pattern and Monitor Pattern on page 13-13.

� Connectivity on page 13-14.

PVC tests only appear on the Test menu when PVCs have been configured forthe interface.

The following test can be run on the physical data port:

� DTE Loopback on page 13-14.

Additional tests include the following:

� IP Ping Test on page 13-15.

� Lamp Test on page 13-17.

Troubleshooting

13-8 9820-A2-GB20-00March 1999

Test Timeout

A Test Timeout feature is available to automatically terminate a test (as opposedto manually terminating a test) after it has been running a specified period oftime.

It is recommended that this feature be used when the FrameSaver unit isremotely managed through an inband data stream (PVC). If a test is accidentlycommanded to execute on the interface providing management access, control isregained when the specified time period expires, automatically terminating thetest.

To use this feature, enable the Test Timeout configuration option, and set aduration for the test to run in the Test Duration (min) configuration option (seeConfiguring General System Options in Chapter 9, Configuration Options).

NOTE:These configuration options do not pertain to tests commanded by the DTE,like a DTE-initiated External Loopback.

Troubleshooting

13-99820-A2-GB20-00 March 1999

Starting and Stopping a Test

Use this procedure to start, monitor, or abort specific tests. To abort all activetests on all interfaces, see Aborting All Tests on page 13-10.

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 test:


Main Menu →Test

2. Select an interface to be tested (Network or Data Port PVC Tests, or DataPort Physical Tests) and press Enter.

The selected test screen appears. Start appears in the Command column.Inactive appears in the Status column.

3. 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 availabletest. Start is highlighted.

4. 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 toActive.

5. Press Enter to stop the test.

Start reappears and the status of the test changes back to Inactive.

6. View the length of time that the test has been running in the Result column.

Troubleshooting

13-10 9820-A2-GB20-00March 1999

Aborting All Tests

Use the Abort All Tests selection from the Test menu to abort all tests running onall interfaces, with exception to DTE-initiated loopbacks. To abort individual teststhat are active, see Starting and Stopping a Test on page 13-9.

� Procedure

To abort all tests on all interfaces:


Main Menu →Test

2. Select Abort All Tests and press Enter.

Command Complete appears when all tests on all interfaces have beenstopped.

NOTE:Abort All Tests does not interrupt DTE-initiated loopbacks.

Determining Test Status and Results

Current test status and results are available on the:

� Test screen from which you execute the test (Results column)

� System and Test Status screen

� NMS

� Test LED

Troubleshooting

13-119820-A2-GB20-00 March 1999

PVC Tests

PVC tests can be run on the following interfaces for the requested DLCI:


� User data port

Loopback, and send/monitor pattern tests are available for each interface on theselected DLCI. FrameSaver units should be at each end of the circuit. If aPVC Loopback is started at one end of the circuit, the other end can send andmonitor pattern tests.

CAUTION:PVC tests between FrameSaver units on a multiplexed DLCI arenondisruptive to data so data can be sent while a test is running.If the device at one end of the circuit is not a FrameSaver unit,these tests will disrupt data.

NOTE:Errors encountered during these tests may be caused by mismatched CIRsin the two FrameSaver units. If errors are detected, verify the CIRconfiguration and retest.

Troubleshooting

13-12 9820-A2-GB20-00March 1999

Network or Port (Internal) PVC Loopback

The Network/Port PVC Loopback (Internal) loops frames back to the selectedinterface on a per-PVC basis. This test logically (not physically) loops backframes from one FrameSaver unit node through the frame relay PVC to the sameFrameSaver unit node.

Main Menu →Test → [Network PVC Tests/Data Port PVC Tests] →PVC Loopback

If the selected DLCI is . . . Then the PVC Loopback is . . .

Standard Disruptive to data.

Proprietary, multiplexed Nondisruptive to data.

98-16186

DTE

NetworkPVC #x

Network PVC Loopback

PVC #x

PVC #x

DTE

Network

98-16187

Port PVC Loopback

PVC #x

Troubleshooting

13-139820-A2-GB20-00 March 1999

Send Pattern

This test sends frames filled with a hexadecimal 55 test pattern and sequencenumber over the selected interface on a per-DLCI basis.

Main Menu →Test → [Network PVC Tests/Data Port PVC Tests] →Send Pattern

If the selectedDLCI is configured as . . . Then . . .

And the defaultRate (Kbps) setting is . . .

Standard (Disruptive) appearsafter Test

100% of CIR

Multiplexed (Non-Disruptive) appearsafter 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 hexadecimal test pattern and checkssequence numbers using a proprietary method. To view the test results, see thePVC Tests DLCI screen.

Main Menu →Test → [Network PVC Tests/Data Port PVC Tests] →Monitor Pattern

The current number of sequence and data errors are shown under the Resultcolumn when the FrameSaver unit is in sync. An Out of Sync messageappears 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.

Connectivity

The Connectivity test is only available for multiplexed DLCIs.

Connectivity is a proprietary method that determines whether the FrameSaverunit node at the other end of the frame relay PVC is active. This test stopsautomatically and can only be executed for multiplexed PVCs.

Main Menu →Test → [Network PVC Tests/Data Port PVC Tests] →Connectivity

Selecting Connectivity sends a frame to the FrameSaver unit at the other end ofthe PVC. A RndTrip Time(ms) message appears in the Result column when aresponse is received within 5 seconds, indicating that the FrameSaver unit at theremote end is alive (operational and connected), and the round trip (RT) time isshown in milliseconds (ms), with a resolution of 1 ms. If a response is notreceived within 5 seconds, No Response appears in the Result column.

Troubleshooting

13-14 9820-A2-GB20-00March 1999

Physical Tests

Physical Tests can be commanded for the user data port.

CAUTION:You should not run these tests with frame relay equipment attached;you must disconnect the frame relay equipment and use external testequipment.

DTE Loopback

The DTE external Loopback (DTLB) test loops the received signal on a user dataport back to the DTE. Use this test for isolating problems on the user data port.

An attached device or test equipment must generate data to be looped back.

99-16284

NetworkPort

UserDataPort

DTLB

CAUTION:DTE Loopback will affect the operation of the frame relay PVCsassigned to the user data port. Any IP data being sent while this testis active will be disrupted.

To start and stop a DTE Loopback, follow this menu selection sequence:

Main Menu →Test →Data Port Physical Tests

View the length of time that the test has been running in the Result column.

Troubleshooting

13-159820-A2-GB20-00 March 1999

IP Ping Test

An IP Ping test can be run to test connectivity between the FrameSaver unit andany FrameSaver unit, router, or NMS to which it has a route.

Times when you might want to run an IP Ping test are:

� To test connectivity between the FrameSaver unit and any FrameSaver unitin the network to verify that the path is operational. Select Procedure 1 toPing any far-end FrameSaver unit.

� To verify the entire path between a newly-installed remote-site FrameSaverunit and the central-site NMS. During a remote-site installation, an IP Pingtest is typically run from the remote-site to Ping the NMS at the central site.The remote FrameSaver unit must have SNMP trap managers configured,and one of those trap managers must be the central-site NMS. SelectProcedure 2 on page 13-16 to Ping the NMS at the central site.

� To test the path to the NMS trap managers during installation of thecentral-site FrameSaver unit. The remote FrameSaver unit must haveconfigured the SNMP trap managers to be sent the Ping. Select Procedure 2on page 13-16 to Ping the SNMP trap managers.

� Procedure 1

To Ping any far-end FrameSaver unit:

1. Select the IP Ping test.

Main Menu →Test → IP Ping

2. Enter the IP Address of the device the Ping is being sent to, then select Start.

NOTE:If the FrameSaver unit has just initialized, or the far-end unit has justinitialized, it may take about a minute for the units to learn the routes viathe proprietary RIP.

3. Verify the results of the IP Ping test.

— While the test is running, In Progress . . . is displayed in theStatus field.

— When the test is finished, Alive. Latency = nn ms should appear asthe Status (nn being the amount of time the test took in milliseconds).

If any other message is displayed, additional testing will be required.

Troubleshooting

13-16 9820-A2-GB20-00March 1999

� Procedure 2

To Ping the NMS at the central site:

1. Verify that the central-site NMS has the FrameSaver unit’s IP address in itsrouting table so it can communicate with the FrameSaver unit.

2. Verify that the central-site NMS’s router has the FrameSaver unit’s IPaddress in its routing table so it can communicate with the FrameSaver unit.

3. Verify that the central-site NMS has been configured as an SNMP TrapManager if the router is to route data, so a route has been configured withinthe FrameSaver unit.

Main Menu →Configuration →Management and Communication →SNMP Traps

Or, for a local DLCI between the central-site FrameSaver unit and its router,verify that a Default IP Destination route has been configured.

Main Menu →Configuration →Management and Communication →Node IP →Default IP Destination

Configure both SNMP Traps and a Default IP Destination when PVCMultiplexing 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 theStatus field.

— When the test is finished, Alive. Latency = nn ms should appear asthe Status (nn being the amount of time the test took in milliseconds).

If any other message is displayed, additional testing will be required.

Troubleshooting

13-179820-A2-GB20-00 March 1999

Lamp Test

The FrameSaver unit supports a Lamp Test to verify that all LEDs are lighting andfunctioning properly. All LEDs flash or blink on and off at the same time every 1/2second during execution of the test. When the test is stopped, the LEDs arerestored to their normal condition.

If the Test Timeout configuration option is enabled and a Test Duration is set, theLamp Test stops when the test duration expires.

See Configuring General System Options in Chapter 9, Configuration Options, toconfigure the unit to stop the test automatically.

Troubleshooting

13-18 9820-A2-GB20-00March 1999


A-19820-A2-GB20-00 March 1999

Menu Hierarchy

AMenus

The following is a graphical representation of the FrameSaver SLV unit’s menuorganization.

Menu Hierarchy

A-2 9820-A2-GB20-00March 1999

98-16240a

Menu Hierarchy

MAIN MENU Status Test Configuration Auto-Configuration Control

StatusSystem and Test StatusLMI Reported DLCIsPVC Connection StatusPerformance StatisticsDisplay LEDs and Control LeadsIdentity

Identity –System andNam• System Name, Contact and Location

• Serial Number

• Current and Alternate Software Revisions

• Hardware Revision

Network LMIReportedDLCIs• DLCI• Status• CIR (bps)

PVC ConnectionStatus• Source Link, DLCI, EDLCI

• Primary Destination Link, DLCI, EDLCI, Status


PVC Tests(DLCI Number, Test,Command, Status,and Result)• PVC Loopback• Send Pattern• Monitor Pattern• Connectivity

TestNetwork PVC TestsData Port PVC TestsData Port Physical TestsIP PingLamp TestAbort All Tests

IP Ping• IP Address• Status

Data PortPhysical Tests• DTE Loopback

PerformanceStatistics• Service Level Verification• DLCI• Frame Relay

System andTest Status• Health and Status• Self-Test Results• Test Status

Menu Hierarchy

A-39820-A2-GB20-00 March 1999


Auto-Configuration• FR Discovery

98-16240b


Device Name• Device Name• System Name, Location, Contact

ControlModem Call DirectoriesDevice NameDate & TimeAdminister LoginsChange Operating ModeSelect Software ReleaseClear Device FailDisconnect ModemReset Device

Administer Logins• Login ID• Password• Access Level

New

Login Entry

LoadConfiguration

from:ConfigurationEdit/DisplaySystemNetworkData PortsPVC ConnectionsManagement and Communication

Network andData Ports• Physical• Frame Relay• DLCI Records


System• Frame Relay and LMI• Service Level Verification• General

PVC ConnectionTable• Source Link, DLCI, EDLCI• Primary Destination Link, DLCI, EDLCI

New or Modify

PVC ConnectionEntry

Management andCommunication Options• Node IP• Management PVCs• General SNMP Management• Telnet and FTP Session• SNMP NMS Security• SNMP Traps• Communication Port• External Modem

New or Modify

ManagementPVC Entry

Menu Hierarchy

A-4 9820-A2-GB20-00March 1999


B-19820-A2-GB20-00 March 1999

IP Addressing

BSelecting an IP Addressing Scheme

You can select from many IP addressing schemes to provide SNMP NMSconnectivity. When selecting a scheme, keep the following in mind:

� Because connection to remote devices is through PVCs, if desired, you canassign IP addresses and subnet masks to each PVC individually.

� Assign IP addresses on a per-interface or FrameSaver unit basis.

� Although routing information is automatically passed between interconnectedFrameSaver units from the network side, make sure to set a route to thesubnet(s) in the NMS’s or local router’s routing table.

The gateway to subnet(s) is through the FrameSaver unit connected to:

— A router’s, terminal server’s, or NMS’s direct PPP (point-to-pointprotocol) or SLIP’s ( link-layer protocol for IP traffic) serial connection, or

— The router’s DTE port using a local PVC, or

— The LAN (using a LAN adapter).

� Be aware that each FrameSaver unit’s routing table supports a maximum of300 routes, even though a single route is all that is needed to reach everydevice on a subnet.

� Have a default route set only for devices directly connected to the NMS’sCOM port.

� Allow any legal host address for a given subnet; the address choice withinthe subnet is not important to the unit, but it should be selected in conjunctionwith all IP addressing for the subnet.

NOTE:When dealing with IP addressing, your Information Systems (IS) departmentneeds to be involved since they typically dictate the IP addressing schemeused in an organization.

IP Addressing

B-2 9820-A2-GB20-00March 1999

Mixing Private and Public Addressingon the Same Network

When customers are connected to the internet, IP addresses are limited to thenumber of IP addresses they own. Using FrameSaver units, private addressingcan be used for your network without taking away from the customer’s pool ofIP addresses.

The illustration below shows this scheme of public and private IP addressing,which is like having two networks in one.

FrameRelayRouter

135.18.2.1

98-16224

Frame RelayNetwork

FrameRelayRouter

135.18.2.2

FrameRelayRouter

135.18.2.3

NMS

Physical ConnectionPVC Connection

EDLCI 200

EDLCI 210

EDLCI 200DLCI 200

DLCI 210

EDLCI 210

DLCI 900

DLCI 200

DLCI 210

Both networks share the near-to-far-end customer-ordered DLCIs (200 and 210)so that data and management data use FrameSaver EDLCIs (embedded DLCIs).Management of the far-end devices is performed via EDLCIs. FrameSaverEDLCIs enhance standard DLCIs, creating a communication path within acommunication path.

Using the FrameSaver RIP feature, far-end FrameSaver units can be identifiedautomatically and reported to the management station via DLCI 900. DLCI 900 isnot propagated to the network by the router. The DLCI terminates in theFrameSaver unit and is only used for management.

IP Addressing

B-39820-A2-GB20-00 March 1999

Service Provider Example

Total management can be performed by service providers using both private andpublic IP addressing. A standard CSU/DSU can be used by the network operationcenter (NOC) NMS. This requires two dedicated DLCIs.

FrameRelayRouter

135.18.2.1

98-16225

Frame RelayNetwork Frame

RelayRouter

135.18.2.2

FrameRelayRouter

135.18.2.3

NMS


EDLCI 200

EDLCI 210

EDLCI 200DLCI 200

DLCI 210

EDLCI 210

DLCI 909

DLCI 200

DLCI 210

DLCI 908

DLCI 909

DLCI 910

IntegratedServicesCenter

DLC

I 909

DLC

I 910

In this illustration, two dedicated DLCIs are required. One DLCI (909) is requiredfor router management between the NOC and the central site FrameSaver unit’srouter. Another dedicated DLCI (910) is required for managing the FrameSaverunit itself. Using private addresses ensures that the router will not pass DLCItraffic to the network so the PVC is reserved for management traffic only. Noticethat the DLCI for the unit (910) terminates in the FrameSaver unit and is notpassed to the router.

The only other requirement is that there is a separate DLCI for each remoteFrameSaver unit.

IP Addressing

B-4 9820-A2-GB20-00March 1999

Preferred Method

Instead of having one PVC for the router (DLCI 909) and another for theFrameSaver unit (DLCI 910), management of the network can be accomplishedusing only the router PVC when the NOC uses a FrameSaver unit, which has itsown IP address, as seen in the illustration below.

Simply create a PVC between the NOC and the router, then let the FrameSaverunit automatically discover the DLCI and convert it to an EDLCI via itsAuto-Configuration feature. This solution eliminates the need for two DLCIs percentral-site FrameSaver unit-router set. The management PVC would be sharedby both the FrameSaver unit and the router.

FrameRelayRouter

135.18.2.2

98-16226

Frame RelayNetwork Frame

RelayRouter

135.18.2.3

FrameRelayRouter

135.18.2.4

NMS


EDLCI 200

EDLCI 210

EDLCI 200DLCI 200

DLCI 210

EDLCI 210DLCI 909

DLCI 200

DLCI 210

DLCI 908EDLCI 909

NetworkOperation

Center

DLC

I 909/910

135.18.2.1

Whether automatically discovering DLCIs or manually configuring DLCIs, a localmanagement PVC must be created between each FrameSaver unit and its routerif management through a back door is desired. Using private addresses, therouter will not pass the DLCI to the network so the PVC is reserved formanagement only.

Management through a back door can be accomplished via a dial line to therouter. Should the network fail, communication with both the router and theFrameSaver unit would be maintained.

IP Addressing

B-59820-A2-GB20-00 March 1999

IP Addressing Scheme Examples

The following examples describe some typical network scenarios; they are notthe only scenarios that can be used. The subnet mask shown for eachFrameSaver unit is 255.255.255.0.

Direct PVCs to Remote FrameSaver Units

In this example, FrameSaver unit A is connected to:

� The NMS at the central site

� Each remote FrameSaver unit through a management PVC

The illustration below shows three separate management PVCs, one for eachremote FrameSaver unit.

FrameRelay

Network

135.18.2.17

98-16217

135.18.2.18

135.18.2.26

Subnet 135.18.2.0

A

B

C

D

135.18.40.1

Ethernet

DLCI 201IP Address: 135.18.40.3

135.18.2.1

Subnet 135.18.40.0

SNMP NMS


DLCI 50

DLCI 60

DLCI 70

DLCI 21

DLCI 20

DLCI 22

FrameRelayRouter

IP Addressing

B-6 9820-A2-GB20-00March 1999

Routing to Remote FrameSaver Units on the Same Subnet



� Remote FrameSaver units through management PVCs

The illustration below shows two management PVCs at the central site, withFrameSaver units B and C connected through one management PVC.

FrameRelay

Network

135.18.2.17

98-16218

135.18.2.18

135.18.2.26

Subnet 135.18.2.0

A

B

C

D

135.18.40.1

Ethernet

IP Address: 135.18.40.3

135.18.2.1

Subnet 135.18.40.0

SNMP NMS


FrameRelayRouter

IP Addressing

B-79820-A2-GB20-00 March 1999

Routing to Remote FrameSaver Units Using Different Subnets



� Two remote FrameSaver units through management PVCs

The illustration below shows two management PVCs, with FrameSaver units Band C connected through one management PVC. By configuring a different IPaddress and subnet for each management PVC:

� FrameSaver units B and C share a subnet: 135.18.3.0

� FrameSaver units A and B share a different subnet: 135.18.2.0

� FrameSaver units A and D share yet another subnet: 135.18.4.0

FrameRelay

Network

135.18.2.2

98-16219

135.18.3.2

135.18.4.26

Subnet 135.18.2.0

A

B

C

D

135.18.40.1

Ethernet

COM PortIP Address: 135.18.40.3

135.18.4.1

Subnet 135.18.4.0

SNMP NMS

135.18.3.3

Subnet 135.18.3.0

135.18.2.1

Subnet 135.18.40.0*


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

*

FrameRelayRouter

IP Addressing

B-8 9820-A2-GB20-00March 1999

Routing to Remote FrameSaver Units Using Routers

In the following examples, the FrameSaver unit at the central site is connected to:

� A router ( instead of a LAN connection)

� The router is connected to the NMS

� The router’s additional serial or AUX port connection is not used formanagement

� No additional network PVCs are required

In the following examples, data is not routed by the FrameSaver units, andmanagement PVCs are not configured between them. Instead, management datafor the remote FrameSaver units is routed through the routers, with managementPVCs configured between the routers and FrameSaver units. Connection is viathe existing DTE cable, between the router’s DTE interface and the T1access unit.

In the following examples, data is not routed by the FrameSaver units, andmanagement PVCs are not configured between them. Instead, management datafor the remote FrameSaver units is routed through the routers, with managementPVCs configured between the routers and FrameSaver units. Connection is viathe existing DTE cable, between the router’s DTE interface and the access unit.

The illustration below shows all FrameSaver units on the same subnet, and allrouters on the same subnet.

FrameRelay

Network

135.18.3.2

97-14989-01

Subnet 135.18.3.0

A

B

C

135.18.1.2

135.18.3.1

SNMP NMS

Subnet 135.18.2.0

Subnet 135.18.1.0

FR Router:135.18.1.1



135.18.3.3


FR = Frame Relay Physical Connection

PVC Connection

IP Addressing

B-99820-A2-GB20-00 March 1999

The following illustration is a more complex example in which each FrameSaverunit is on its own subnet, having a subnet mask of FF.FF.FF.00. This subnet isindependent of the subnet on the LAN supported by the local router.

FrameRelay

Network

135.18.5.2

97-14914-01

Subnet 135.18.5.0

A

B

C

135.18.1.2

135.18.4.2

SNMP NMS

Subnet135.18.2.0

Subnet 135.18.1.0



Subnet 135.18.4.0



135.18.6.2

Subnet 135.18.6.0


COMPort

COMPort

Subnet135.18.3.0


COMPort

Physical Connection

PVC ConnectionFR = Frame Relay

IP Addressing

B-10 9820-A2-GB20-00March 1999

Assigning IP Addresses and Subnet Masks

Once you select an IP scheme, assign an address (or addresses) to theaccess unit.

� If one IP address is wanted for the FrameSaver unit, set node IP address andsubnet mask.

� If an IP address is wanted for each interface, assign a separate IP addressand subnet mask to each interface.

I f using . . . Then . . .

COM port as amanagement interface

Assign the node IP address and subnet mask or theCOM port IP address and subnet mask.

Menu selection sequence:Main Menu →Configuration →Management andCommunication →Communication Protocol

COM port connected to anexternal modem

Configure an IP address and subnet mask to dial out trapsusing the alarm directory.

Menu selection sequence:Main Menu →Configuration →Alarm

Or, configure the IP address and subnet mask.

Menu selection sequence:Main Menu →Configuration →Management andCommunication →Communication Protocol

Management PVC as amanagement interface

Assign IP addresses and subnet masks to each PVC, orto the node IP address if only one IP address per unit isdesired.

Menu selection sequence:Main Menu →Configuration →Management andCommunication →Logical Communication Links

C-19820-A2-GB20-00 March 1999

Standards Compliance forSNMP Traps

CThis appendix describes the FrameSaver unit’s compliance with SNMP formatstandards and with its special operational trap features.

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 thefollowing format:

‘DLCI $dlciNumber of $ifName frame relay link “$linkName”.’

— $dlciNumber is the DLCI number. DLCI $dlciNumber only appears whena DLCI is associated with the trap.

— $linkName is the name given to the link. Frame relay $linkName onlyappears 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 FrameSaver unit supports the following traps:

� warmStart on page C-2.

� authenticationFailure on page C-2.

� linkUp and linkDown on page C-2.

� enterprise-Specific on page C-6.

� RMON-Specific on page C-9.

These traps are listed in alphabetical order within each table.

Standards Compliance for SNMP Traps

C-2 9820-A2-GB20-00March 1999

Trap: warmStart

This trap indicates that the FrameSaver unit has been reset as a result of a resetcommand or a power disruption.

Table C-1. warmStart Trap

Trap What It Indicates Possible Cause

warmStart FrameSaver unit has justreinitialized and stabilizeditself.

� Reset command sent.

� Power disruption.

St iVariable-Bindings

String: ‘Unit reset.’

devLastTrapString(devHealthAndStatus.mib)

Trap: authenticationFailure

Table C-2. authenticationFailure Trap


authenticationFailure Access to the FrameSaverunit was attempted andfailed.

� SNMP protocol message notproperly authenticated.

� Three unsuccessful attemptswere made to enter a correctlogin user ID/passwordcombination.

� IP Address security is enabledand a message was receivedfrom the SNMP Managerwhose address was not on thelost of approved managers.

String: ‘Unauthorized access attempted.’

Variable-Bindings

devLastTrapString(devHealthAndStatus.mib)


C-39820-A2-GB20-00 March 1999

Traps: linkUp and linkDown

These traps are supported on the synchronous data ports – Physical sublayerinterfaces.

Table C-3. linkUp and linkDown Traps


linkDown A failure in one of thecommunication interfaceshas occurred.

A failure in one of thecommunication interfaces hasoccurred.

linkUp One of the failedcommunication interfaces isup and operational.

One of the failed communicationinterfaces is up and operational.


C-4 9820-A2-GB20-00March 1999

Variable-Bindings: linkUp and linkDown

These variable-bindings support the linkUp and linkDown traps and conditions foreach interface.

Table C-4. linkUp and linkDown Variable-Bindings (1 of 2)

Interface Variable-Bindings Possible Cause

Physical Sublayer – Represented by the entry in the MIB II Interfaces Table.

SynchronousData Port

(Supported by themedia-specificRS232-like MIB.)

� ifIndex (RFC 1573)

� ifAdminStatus(RFC 1573)

� ifOperStatus (RFC 1573)

� devLastTrapString(devHealthAndStatus.-mib)

� linkDown – One or more alarmconditions are active on theport.Alarm conditions include:– DTR 1

– RTS 2

– RLSD 3

– ‘ ’ – Not DTR, RTS, orRLSD, but link is down.

String: ‘$ifString $alarmString down.’(e.g., ‘Sync Data Port S01P1DTR and RTS down.’ )

� linkUp – No alarms on theport.String: ‘$ifString up.’

(Supported throughifIndex – RFC 1573.)





� linkDown – One or more alarmconditions are active on theinterface.

Strings: ‘$ifString down.’ No alarmsexist on the link.

‘$ifString administrativelyshutdown.’ (Due to anintentional shutdown.)

� linkUp – No alarms on theinterface.String: ‘$ifString up.’

1 The DTR alarm condition will only generate a linkUp/ linkDown trap if the DTEsupports the DTR lead state.

2 The RTS alarm condition will only generate a linkUp/ linkDown trap if the DTEsupports the RTS lead state.

3 The RLSD alarm condition will only generate a linkUp/ linkDown trap if the DTEsupports the RLSD lead state.


C-59820-A2-GB20-00 March 1999

Table C-4. linkUp and linkDown Variable-Bindings (2 of 2)

Interface Possible CauseVariable-Bindings

Logical Link Sublayer – Represented by the entry in the MIB II Interfaces Table.

Service Side of theFrame Relay UNI

(Supported by themedia-specific FrameRelay Services MIB.)





� linkDown – LMI is down for theLMI Protocol configured,4 orFrame Relay link is disabled.

Strings: ‘$ifString down.’ No alarmsexist on the link due to LMI.

‘$ifString LMI down.’ Noalarms exist on the link.


� linkUp – LMI is up or FrameRelay link is enabled.String: ‘$ifString up.’

DTE Side of theFrame Relay UNI

(Supported by themedia-specific FrameRelay DTE’s MIB.)





� linkDown – LMI is down for theLMI Protocol configured,4 orFrame Relay link is disabled.Strings: ‘$ifString LMI down.’


� linkUp – LMI is up or FrameRelay link is enabled.String: ‘$ifString up.’

4 If the LMI Protocol is not configured, a linkUp/ linkDown trap is based solely uponwhether the interface is enabled or disabled.


C-6 9820-A2-GB20-00March 1999

Traps: enterprise-Specific

These traps indicate that an enterprise-specific event has occurred. Supportedenterprise-specific traps include the following, listed in alphabetical order:

Table C-5. enterprise-Specific Traps


enterpriseCIR-Change(115)

CIR has changed due tothe LMI report.

LMI Protocol is set to Standardand the network’s CIR changed.

enterpriseConfig-Change(6)

Configuration has beenchanged via the async userinterface or an SNMPManager after 60 secondshas elapsed withoutanother change.

Configuration has been changedvia the async user interface or anSNMP Manager fromdevLastTrapString(devHealthAndStatus.mib).

enterpriseDevice-Fail(3)

An internal device failure.

The variable binding for thistrap is devHealthandStatus.

Operating software has detectedan internal device failure.

enterpriseDLCI-Down(11)

The DLCI for an interfacesupporting one side of theUNI is down.

DLCI is down.

enterpriseDLCIUp(12) The DLCI for an interfacesupporting one side of theUNI is up.

DLCI is up again.

enterpriseLinkSpeed-Change(114)

The speed of the framerelay link has changed.

Link speed has changed due tothe auto-rate algorithm.

enterpriseRMON-ResetToDefault(13)

All RMON-related optionchanges have been reset totheir default values.

Default Factory Configurationsettings have been reloaded,returning RMON-related optionsto their original settings.

enterpriseSelfTest-Fail(2)

A hardware failure. Unit has completed(re)initialization and a hardwarefailure was detected.

enterpriseTest-Start(5)

A test is running. At least one test has beenstarted on an interface or virtualcircuit.

enterpriseTest-Stop(105)

All tests have been halted. All tests have been halted on aninterface or virtual circuit.


C-79820-A2-GB20-00 March 1999

Variable-Bindings: enterprise-Specific

Table C-6. enterprise-Specific Variable-Bindings (1 of 2)

Trap Variable-Bindings Possible Cause

enterpriseCIR-Change(115)

� devFrExtDlciIfIndex(devFrExt.mib)

� devFrExtDlciDlci(devFrExt.mib)

� devFrExtDlciCIR(devFrExt.mib)


LMI Protocol is set to Standardand the network’s CIR changed.

String: ‘CIR on $ifString changed to$CIR bps.’

enterpriseConfig-Change(6)


Configuration has been changedvia the async user interface or anSNMP Manager fromdevLastTrapString(devHealthAndStatus.mib).

String: ‘Device configuration change.’

enterpriseDevice-Fail(3)

� devLastTrapString(devHealthAndStatus.-mib is the internal failurenumber.)

An internal device failure wasdetected.

String: ‘Device fail with error codexxxxxxxx.’

enterpriseDLCI-Down(11)



� devLastTrapString(devHealthAndStatus.-mib.)

DLCI Status is set to Inactive; theDLCI is down.

Strings: ‘$ifString down.’ (Due to LMI orphysical failure.)

‘$ifString administrativelyshutdown.’ (Due to an intentionalshutdown.)

enterpriseDLCIUp(12) DLCI Status is set to Active;DLCI is up again.

String: ‘$ifString up.’


C-8 9820-A2-GB20-00March 1999

Table C-6. enterprise-Specific Variable-Bindings (2 of 2)

Trap Possible CauseVariable-Bindings

enterpriseLinkSpeed-Change(114)


� ifSpeed (RFC 1573)

� devLastTrapString(devHealthAndStatus.-mib.)

Link speed has changed due tothe auto-rate algorithm.

String: ‘Speed of $ifName changed to$ifSpeed bps.’

enterpriseRMON-ResetToDefault(13)


Default Factory Configurationsettings have been reloaded,returning RMON-related optionsto their original settings.

String: ‘RMON database reset todefaults.’

enterpriseSelfTest-Fail(2)


Unit has completed(re)initialization and a hardwarefailure was detected.

String: ‘Selftest failed: $s.’ ($s is thecontents of devSelfTestResult.)

enterpriseTest-Start(5)

For physical interfaces andframe relay links:


� .0.0 (placeholder)

� devLastTrapString(devHealthAndStatus.-mib

For virtual circuits (DLCIs):

At least one test has beenstarted on an interface or virtualcircuit.

String: ‘$testString test startedon$ifString.’ (e.g., ‘DTE ExternalLoopback test started on SyncData Port S01P1.’)

enterpriseTest-Stop(105)

For virtual circuits (DLCIs):



� devLastTrapString(devHealthAndStatus.-mib

All tests have been halted on aninterface or virtual circuit.

String: ‘$testString test startedon$ifString.’ (e.g., ‘DTE ExternalLoopback test stopped on SyncData Port S01P1.’)


C-99820-A2-GB20-00 March 1999

Traps: RMON-Specific

Two traps are defined to support the Alarm and Events Groups of RMON, whichare shown below with their variable-bindings.

See in Appendix D, RMON Alarm Defaults, for the default values that willgenerate RMON-specific traps.

Variable-Bindings: risingAlarm and fallingAlarm

Table C-7. risingAlarm and fallingAlarm Variable-Bindings

Trap Variable-Bindings Possible Cause

risingAlarm � alarmIndex (RFC 1757)

� alarmVariable(RFC 1757)

� alarmSampleType(RFC 1757)

� alarmValue (RFC 1757)

� alarmRisingThreshold(RFC 1757)


Object being monitored has risenabove the set threshold.

String: ‘Change in $variableName$typeString threshold of$alarmRisingThreshold by$(alarmValue –AlarmRisingThreshold.’(e.g., ‘Octets received on SyncData Port S01P1 frame relayrose to threshold of 1.’)

fallingAlarm � alarmIndex (RFC 1757)

� alarmVariable(RFC 1757)

� alarmSampleType(RFC 1757)

� alarmValue (RFC 1757)

� alarmFallingThreshold(RFC 1757)


Object being monitored hasfallen below the set threshold.

String: ‘Change in $variableName$typeString threshold of$alarmRisingThreshold by$(alarmValue –AlarmRisingThreshold.’(e.g., ‘Octets received on SyncData Port S01P1 frame relayrose to threshold of 1.’)


C-10 9820-A2-GB20-00March 1999


D-19820-A2-GB20-00 March 1999

RMON Alarm Defaults

DRMON Alarm and Event Defaults

The FrameSaver unit supports automatic generation of RMON alarm and eventinformation. Each alarm sets an SNMP variable to monitor. When the thresholdset 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 unit, there is noneed to define multiple events for each alarm type, so only the following twoevents 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 defaultalarm is set by the FrameSaver unit, shows the alarm and event types, theinterval used when generating alarms, and thresholds.

� Network Sync Port Physical Interface Alarm Defaults on page D-2.

� Static Frame Relay Interface Alarm Defaults on page D-3.

� Dynamic Frame Relay Interface Alarm Defaults on page D-5.

� DLCI Alarm Defaults – Paradyne Area on page D-6.

� Static DLCI Alarm Defaults – NetScout Area on page D-7.

� Dynamic DLCI Alarm Defaults – NetScout Area on page D-8.

See Appendix C, Standards Compliance for SNMP Traps, for information abouthow traps work, and Traps: RMON-Specific for traps specific to remotemonitoring.

RMON Alarm Defaults

D-2 9820-A2-GB20-00March 1999

Rising Event Operation

If a rising threshold is crossed during the interval shown in a table (e.g., framesdropped by the network), the event is armed and an alarm is generated at theend of the interval. Only one alarm per event per interval is generated. The alarmcondition persists until the event has been disarmed (reset).

The event is disarmed when a falling threshold has been crossed and the risingthreshold has not been crossed during an interval, allowing the event to return toits original disarmed state.

Network Sync Port Physical Interface Alarm Defaults

These alarms only apply to the FrameSaver unit’s network data port interface.They are created during RMON initialization and put into the Paradyne-definedalarm area.

Table D-1. Network Sync Port Physical Interface Alarm Defaults

ItemSampleType 1 MIB/Tag/OID 2 Interval

EventType

RisingThresholdDefault

FallingThresholdDefault

UnavailableSeconds

D MIB: devSyncPortStats.mib(RFC 1406)

Tag: devSyncPortStatsUASs

OID: .1.1.3.6.1.4.1.1795.2.24.-2.6.6.5.1.1.2.101003002

900 secs(15 mins)

Rising 1 1

1 D = Delta. Indicates that the calculated difference between the current value and the previous value is containedin the MIB.

RMON Alarm Defaults

D-39820-A2-GB20-00 March 1999

Static Frame Relay Interface Alarm Defaults

These alarms apply to the FrameSaver unit’s frame relay interfaces. They arecreated during RMON initialization.

Table D-2. Static Frame Relay Interface Alarm Defaults (1 of 2)


EventType



Invalid Frames D MIB: devfrext.mib (E)

Tag: devFrExtLinkRxIlFrames

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.18.I

900 secs(15 mins)

Rising 1 1

Short Frames D MIB: devfrext.mib (E)

Tag: devFrExtLinkRxShort

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.6.I

900 secs(15 mins)

Rising 1 1

Long Frames D MIB: devfrext.mib (E)

Tag: devFrExtLinkRxLong

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.7.I

900 secs(15 mins)

Rising 1 1

Rx Discards D MIB: devfrext.mib (E)

Tag: devFrExtLinkRxDiscards

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.15.I

900 secs(15 mins)

Rising 1 1

Tx Discards D MIB: devfrext.mib (E)

Tag: devFrExtLinkTxDiscards

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.14.I

900 secs(15 mins)

Rising 1 1

Rx Total Errors D MIB: devfrext.mib (E)

Tag: devFrExtLinkTotRxErrs

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.20.I

900 secs(15 mins)

Rising 1 1

Tx Total Errors D MIB: devfrext.mib (E)

Tag: devFrExtLinkTotTxErrs

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.19.I

900 secs(15 mins)

Rising 1 1


2 I in the OID = Interface ID of the frame relay link.

RMON Alarm Defaults

D-4 9820-A2-GB20-00March 1999

Table D-2. Static Frame Relay Interface Alarm Defaults (2 of 2)

Item



EventTypeIntervalMIB/Tag/OID 2

SampleType 1

Rx Overruns D MIB: devfrext.mib (E)

Tag: devFrExtLinkRxOverruns

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.28.I

900 secs(15 mins)

Rising 1 1

Tx Underruns D MIB: devfrext.mib (E)

Tag: devFrExtLinkTx-Underruns

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.29.I

900 secs(15 mins)

Rising 1 1

Rx Nonoctet Aligns D MIB: devfrext.mib (E)

Tag: devFrExtLinkRx-NonOctet

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.16.I

900 secs(15 mins)

Rising 1 1

Rx CRC Errors D MIB: devfrext.mib (E)

Tag: devFrExtLinkRxCrcErrs

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.17.I

900 secs(15 mins)

Rising 1 1

Total LMI Errors D MIB: devfrext.mib (E)

Tag: devFrExtLinkTotal-LMIErrs

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.7.1.32.I

900 secs(15 mins)

Rising 1 1



RMON Alarm Defaults

D-59820-A2-GB20-00 March 1999

Dynamic Frame Relay Interface Alarm Defaults

These alarms apply to the FrameSaver unit’s frame relay interfaces. They arecreated during RMON initialization, and will change if the interface’s line speedchanges.

Table D-3. Dynamic Frame Relay Interface Alarm Defaults


EventType



Rx Utilization D MIB: MIB II (RFC 1573)

Tag: ifInOctets

OID: .1.3.6.1.2.1.2.2.1.10.I

60 secs(1 min)

Rising 70% of linkcapability

65% of linkcapability

Tx Utilization D MIB: MIB II (RFC 1573)

Tag: ifOutOctets

OID: .1.3.6.1.2.1.2.2.1.16.I

60 secs(1 min)





RMON Alarm Defaults

D-6 9820-A2-GB20-00March 1999

DLCI Alarm Defaults – Paradyne Area

These alarms apply to DLCIs on the network interface. They are created eitherduring RMON initialization or when a DLCI is created, and put into theParadyne-defined alarm area.

Table D-4. DLCI Alarm Defaults – Paradyne Area


EventType



DLCI InactiveSeconds

D MIB: devfrext.mib (E)

Tag: devFrExtDlciStsInactive-Secs

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.2.1.2.I.D

900 secs(15 mins)

Rising 1 1

Missing LatencyResponses


Tag: devFrExtDlciMissedSLVs

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.1.1.23.I.D

900 secs(15 mins)

Rising 5 5

Rx FECNs D MIB: FT DTE MIB (RFC 2115)

Tag: frCircuitReceivedFECNs

OID: .1.3.6.1.2.1.10.32.2.1.5.I.D

60 secs(1 min)

Rising 1 1

Rx BECNs D MIB: FT DTE MIB (RFC 2115)

Tag: frCircuitReceivedBECNs

OID: .1.3.6.1.2.1.10.32.2.1.4.I.D

60 secs(1 min)

Rising 1 1

Congested Seconds D MIB: devfrext.mib (E)

Tag: devFrExtDlciSts-CongestedSecs

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.2.1.6.I.D

60 secs(1 min)

Rising 5 5

Frames Dropped byNetwork


Tag: frFrExtDlciNetDropFr

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.1.1.20.I.D

900 secs(15 mins)

Rising 1 1

1 D = Delta. Indicates that the calculated difference between the current value and the previous value is containedin 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.

RMON Alarm Defaults

D-79820-A2-GB20-00 March 1999

Static DLCI Alarm Defaults – NetScout Area

These alarms apply to DLCIs on the network interface. They are created eitherduring RMON initialization or when a DLCI is created, and put into theNetScout-defined alarm area.

The thresholds for these alarms can be edited using NetScout Manager Plus sothey 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


EventType



Current Latency A MIB: devfrext.mib (E)

Tag: devFrExtLatencyLatest

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.3.1.7.I.D

60 secs(1 min)

Rising Must beconfigured.

0

Average Latency A MIB: devfrext.mib (E)

Tag: devFrExtLatencyAvg

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.3.1.5.I.D

900 secs(15 mins)


0

Frames Received D MIB: FT DTE MIB (RFC 2115)

Tag: frCircuitReceivedFrames

OID: .1.3.6.1.2.1.10.32.2.1.8.I.D

60 secs(1 min)


0

Frames Sent D MIB: FT DTE MIB (RFC 2115)

Tag: frCircuitSentFrames

OID: .1.3.6.1.2.1.10.32.2.1.6.I.D

60 secs(1 min)


0

Tx FramesExceeding CIR


Tag: devFrExtDlciTxFrOutCIR

OID: .1.3.6.1.4.1.1795.2.24.2.6.9. 4.1.1.17.I.D

60 secs(1 min)


0

Tx CIR Utilization D MIB: FT DTE MIB (RFC 2115)

Tag: frCircuitSentOctets

OID: .1.3.6.1.2.1.10.32.2.1.7.I.D

60 secs(1 min)


0



RMON Alarm Defaults

D-8 9820-A2-GB20-00March 1999

Dynamic DLCI Alarm Defaults – NetScout Area

These alarms apply to DLCIs on the network interface. They are created eitherduring RMON initialization or when a DLCI is created, and put into theNetScout-defined alarm area. They will be reconfigured if the interface’s linespeed changes.

Table D-6. Dynamic DLCI Alarm Defaults – NetScout Area


EventType



Rx DLCI LinkUtilization

D MIB: FT DTE MIB (RFC 2115)

Tag: frCircuitReceivedOctets

OID: .1.3.6.1.2.1.10.32.2.1.9.I.D

60 secs.(1 min)



Tx DLCI LinkUtilization

D MIB: FT DTE MIB (RFC 2115)

Tag: frCircuitSentOctets

OID: .1.3.6.1.2.1.10.32.2.1.7.I.D

60 secs.(1 min)





E-19820-A2-GB20-00 March 1999

Cables, Connectors, andPin Assignments

EThis appendix shows the FrameSaver unit rear panels, and pin assignments forthe connectors/interfaces and cables.

NOTE:In the pin assignment tables of this appendix, if the pin number is not shown,it is not being used.

Rear Panel

The following illustration shows the FrameSaver 9820 and 9820-C unit’srear panel.

98-16189

Cables, Connectors, and Pin Assignments

E-2 9820-A2-GB20-00March 1999

COM Port Connector

The following table shows the signals and pin assignments for the DB25communication port connector.

Signal Direction Pin #

Shield — 1

Transmit Data (TXD) To COM port ( In) 2

Received Data (RXD) From COM port (Out ) 3

Request to Send (RTS) To COM port ( In) 4

Carrier Detect (CD) From COM port (Out ) 5, 6, 8

Signal Ground (SG) To/From COM port 7

Data Terminal Ready (DTR) To COM port ( In) 20

COM Port-to-Terminal Cable (3100-F2-540)

Order this cable when connecting the COM port to an asynchronous terminal;it does not come with the FrameSaver unit. The following shows thepin assignments from the COM port to the terminal interface.

1

2

3

4

5

6

7

8

496-14910

COM PortNon-Keyed8-Position

Modular Plug

Tx Clock

Rx Data

Ground

Tx Data

DTR

CD

RTS

Rx Clock

15

3

7

2

20

8

5

6

4

17

Rx Data

Ground

Tx Data

DTR

CD

CTS

DSR

RTS

DTEDB25 Plug


E-39820-A2-GB20-00 March 1999

LAN Adapter Converter and Cable

The following shows the pin assignments for the:

� DB25 plug-to-modular jack converter between the COM port and the8-conductor LAN Adapter cable and

� Custom 8-conductor cable (with modular plugs on both ends) between theconverter and the LAN Adapter (3100-F2-910).

Unused

DTR

Tx Data

Signal Ground

Rx Data

CTS

Frame Ground

Unused

Plug toModular Jack

Plug toLAN Adapter

98-16214

1

2

3

4

5

6

7

8

1

2

3

4

5

6

7

8

Tx Clock

Rx Data

Signal Ground

Tx Data

DTR

CD

RTS

Rx Clock

Com Port(DB25 Plug)

8-PositionModular Jack

15

3

7

2

20

8

4

17

1

2

3

4

5

6

7

8

Plug-to-ModularJack Converter Cable


E-4 9820-A2-GB20-00March 1999

Standard EIA-232 Crossover Cable (4951-035F)

A standard EIA-232 crossover cable can be used to connect the COM port to anexternal modem. This is an EIA-232 plug-to EIA-232 plug (DB25-to-DB25) cable.The external modem must be configured so it is compatible with the FrameSaverunit. See page E-5 to configure an external modem.

Pin 1

Pin 14

Pin 13

Pin 25

Pin 1

Pin 14

Pin 13

Pin 25

P2Plug

Chassis Ground

TXD

RXD

RTS

DSR

Signal Ground

CD (RLSD)

RXC

DTR

XTXC

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

Pin

99-16332

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

P1

Chassis Ground

TXD

RXD

RTS

DSR

Signal Ground

CD (RLSD)

RXC

DTR

XTXC

Pin P2

P1Plug


E-59820-A2-GB20-00 March 1999

� Procedure

To configure an external modem:

1. Disconnect the async terminal from the standard cable. See page E-2 for anillustration of the COM Port connection.

2. Reconnect the crossover cable to the external modem.

3. Enable auto-answer on your modem, and configure it to use the followingLSD, DSR, CTS, RTS, and DTR control leads.

See the table below for AT D0 command strings. Use the following commandstring:

AT &C0 &D2 &S0 &R1 \D0 S0=1

AT Command String To configure the modem to . . .

&C0 Force LSD on.

&D2 Drop the connection when the unit drops DTR.

&S0 Force DSR on.

&R1 Ignore RTS.

\D0 Force CTS on.

S0=1 Automatically answer incoming calls.


E-6 9820-A2-GB20-00March 1999

User and Network Data Port Connectors

The following table provides the pin assignments for the EIA-530A connector tothe DTE or NTU.

SignalCircuitMnemonic

ITU/CCITT # Direction

25-PinPin #

Shield — — — 1

Transmit Data (TXD) BA 103 To DCE 2 (A)14 (B)

Received Data (RXD) BB 104 From DCE 3 (A)16 (B)

Request to Send (RTS) CA 105 To DCE 4 (A)19 (B)

Clear to Send (CTS) 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 To/FromDCE

7

Received Line Signal Detector(RLSD or LSD)

CF 109 From DCE 8 (A)10 (B)

Transmit Signal ElementTiming (TXC – DTE Source)

DA 113 To DCE 11 (B)24 (A)

Transmit Signal ElementTiming (TXC – DCE Source)

DB 114 From DCE 12 (B)15 (A)

Received Signal ElementTiming (RXC – DCE Source)

DD 115 From DCE 17 (A)9 (B)

Local Loopback (LL) LL 141 To DCE 18

Data Terminal (or DTE)Ready (DTR)

CD 108/1, /2 To DCE 20

Test Mode Indicator (TM) TM 142 From DCE 25

NOTE:The user data port has a DCE personality, while the network data port has aDTE personality.


E-79820-A2-GB20-00 March 1999

X.21 Network Cable

This cable is used to connect the network data port to an NTU with an X.21interface. It is a 25-position EIA-530A-to-15-pin X.21 (DB25-to-X.21) cable.

This cable (Part No. 035-0384-1031) is part of the X.21 Cable Kit (Feature No.9008-F1-521).

99-16303

The following table provides the pin assignments for the DB25-to-X.21 networkcable.

SignalITU/CCITT #

25-PinSocketPin # Direction

15-PinPlugPin #

Transmit Data (TXD) 103 2 (A)14 (B)

To DCE 2 (A)9 (B)

Received Data (RXD) 104 3 (A)16 (B)

From DCE 4 (A)11 (B)

Request to Send (RTS) 105 4 (A)19 (B)

To DCE 3 (A)10 (B)

Signal Ground/Common (SG) 102 7 — 8

Data Channel Received LineSignal Detector (RLSD or LSD)

109 8 (A)10 (B)


Transmit Signal Element/Terminal Timing (TT) —DTE Source

113 24 (A)11 (B)

To DCE 7 (A)14 (B)

Received Signal Element Timing(RXC) — DCE Source

115 17 (A)4 (B)



E-8 9820-A2-GB20-00March 1999

X.21 DTE Adapter Cable

This adapter is used to connect the user data port to a DTE with an X.21 cable.It is a 25-pin EIA-530A-to-15-pin X.21 (DB25-to-X.21) adapter cable.

This cable (Part No. 035-0302-0131) is part of the X.21 Cable Kit (Feature No.9008-F1-521).

98-15883

The following table provides the pin assignments for the DB25-to-X.21 adaptercable.

SignalITU/CCITT #

25-Pin Plug Pin # Direction

15-Pin SocketPin #


To DCE 2 (A)9 (B)




115 17 (A)9 (B)


Request to Send (RTS) 105 4 (A)19 (B)

To DCE 3 (A)10 (B)


109 8 (A)10 (B)



113 24 (A)11 (B)

To DCE 7 (A)14 (B)



E-99820-A2-GB20-00 March 1999

V.35 Network Cable

This cable is used to connect the network data port to an NTU with a V.35interface. It is a 25-position EIA-530A-to-34-pin V.35 (DB25-to-V.35) cable.

This cable (Part No. 035-0383-1031) is part of the V.35 Cable Kit (Feature No.9008-F1-522).

99-16302


E-10 9820-A2-GB20-00March 1999

The following table provides the pin assignments for the DB25-to-V.35 networkcable.

SignalITU/CCITT #

25-PinSocketPin # Direction

34-PinPlugPin #


To DCE P (A)S (B)


From DCE R (A)T (B)

Transmit Signal Element Timing(TXC) — DCE Source

114 15 (A)12 (B)

From DCE Y (A)AA (B)


115 17 (A)9 (B)

From DCE V (A)X (B)


113 24 (A)11 (B)

To DCE U (A)W (B)

Request to Send (RTS) 105 4 To DCE C

Clear to Send (CTS) 106 5 From DCE D

Data Terminal (or DTE) Ready(DTR)

108/1, /2 20 To DCE H


109 8 From DCE F

Loopback/Maintenance (RL) 140 21 To DCE N

Local Loopback (LL) 141 18 To DCE L

Test Mode Indicator (TM) 142 25 From DCE NN

Data Set (or DCE) Ready (DSR) 107 6 From DCE E

Signal Ground/Common (SG) 102 7, 23 — B


E-119820-A2-GB20-00 March 1999

V.35 DTE Adapter

This adapter is used to connect the user data port to a DTE with an V.35 cable.It is a 25-pin EIA-530A-to-34-position V.35 (DB25-to-V.35) adapter.

This adapter (Part No. 002-0095-0031) is part of the V.35 Cable Kit (Feature No.9008-F1-522).

99-16294


E-12 9820-A2-GB20-00March 1999

The following table provides the pin assignments for the DB25-to-V.35 adapter.

SignalITU/CCITT #

25-PinPlugPin # Direction

34-PinSocketPin #

Shield — 1 — A


To DCE P (A)S (B)


From DCE R (A)T (B)


114 15 (A)12 (B)

From DCE Y (A)AA (B)


115 17 (A)9 (B)

From DCE V (A)X (B)

Request to Send (RTS) 105 4 To DCE C

Clear to Send (CTS) 106 5 From DCE D


108/1, /2 20 To DCE H


109 8 From DCE F

Data Set (or DCE) Ready (DSR) 107 6 From DCE E

Signal Ground/Common (SG) 102 7 — B

Loopback/Maintenance (RL) 140 21 To DCE N

Local Loopback (LL) 141 18 To DCE L

Signal Ground/Common (SG) 102 23 — B


113 24 (A)11 (B)

To DCE U (A)W (B)


E-139820-A2-GB20-00 March 1999

EIA-530 Straight-through Cable (9008-F1-523)

A standard straight-through cable is used to connect the network data port to theNTU or the user data port to a DTE when the Port Type is E530 (EIA-530A). It isa 25-pin EIA-530A-to-25-pin EIA-530A (DB25-to-DB25) cable.

99-16304


E-14 9820-A2-GB20-00March 1999

The following table provides the pin assignments for the DB25-to-DB25straight-through cable.

SignalITU/CCITT #

25-PinPlugPin # Direction

25-PinSocketPin #

Shield — 1 — A


To DCE 2 (A)14 (B)



Request to Send (RTS) 105 4, 19 To DCE 4, 19

Clear to Send (CTS) 106 5, 13 From DCE 5, 13

Data Set (or DCE) Ready (DSR) 107 6 From DCE 6


108/1, /2 20 To DCE 20



109 8, 10 From DCE 8, 10


114 15 (A)12 (B)



115 17 (A)9 (B)


Local Loopback (LL) 141 18 To DCE 18

Loopback/Maintenance (RL) 140 21 To DCE 21


113 24 (A)11 (B)

To DCE 24 (A)11 (B)

Test Mode Indicator (TM) 142 25 From DCE 25

22 From DCE 22


F-19820-A2-GB20-00 March 1999

Technical Specifications

FStandalone FrameSaver Unit Technical Specifications (1 of 2)

Specification Criteria

Approvals

EMC

Network

ICE

Safety

Class A, ICES-003, CISPR22

CTR1, CTR2

73/23/EEC, 89/336/EEC, 91/263/EEC

CSA 950, EN 60950, AS 3260

Physical Environment

Operating temperature

Storage temperature

Relative humidity

Shock and vibration

32°F to 122°F (0°C to 50°C)

–4°F to 158°F (–20°C to 70°C)

5% to 85% (noncondensing)

Withstands normal shipping and handling

Power

Input

Output

100 – 240 Vac, 50/60 Hz, 0.7A

12 Vdc, 2.5A, 1.0A minimum

Power Consumptionand Dissipation

4.8 watts, 100 mA at 100 Vac Result: 16.38 Btu per hour

5.0 watts, 90 mA at 120 VacResult: 17.06 Btu per hour

5.6 watts, 60 mA at 240 VacResult: 19.11 Btu per hour

Technical Specifications

F-2 9820-A2-GB20-00March 1999

Standalone FrameSaver Unit Technical Specifications (2 of 2)

Specification Criteria

Weight 2.59 lbs. (1.18 kg)

Physical Dimensions

Height

Width

Depth

2.9 inches (7.4 cm)

8.5 inches (21.6 cm)

12.5 inches (31.8 cm)

COM Port

Data rates

DB25 connector

9.6, 14.4, 19.2, 28.8, 38.4, 57.6, and 115.2 kbps

Network Data Port

Data rates

25-position (DB25) subminiature connectorSelectable EIA-530, V.35, X.21

FrameSaver 9820: 64 kbps and 128 kbps(auto-detected)

FrameSaver 9820-C: 64–2048 kbps in 64 kbpsincrements (auto-detected)

User Data Port

Data rates

25-position (DB25) subminiature connectorSelectable EIA-530, V.35, X.21

Automatically set to same values as the Networkinterface

G-19820-A2-GB20-00 March 1999

Equipment List

GEquipment

See page G-2 for cables you can order.

DescriptionModel/FeatureNumber

FrameSaver SLV Units

FrameSaver SLV 9820 Remote Site unit for up to 8 PVCsIncludes Standalone Housing, Universal 100–240 Vac PowerSupply, Power Cord, Installation Instructions, and QuickReference.1

9820-A1-443-nnn 2

FrameSaver SLV 9820-C Central Site unit for up to 120 PVCsIncludes Standalone Housing, Universal 100–240 Vac PowerSupply, Power Cord, Installation Instructions, and QuickReference.1

9820-A1-444-nnn 2

Power Supply

100 –240 Vac Power Supply (Universal Power Supply) 9001-F1-040

Optional Features

Wall Mounting Kit 9001-F1-891

User Documentation/Manual

FrameSaver SLV 9820 User’s Guide (Paper Manual) 9820-M1-001

1 The User’s Guide is available online via Paradyne’s World Wide Web site.2 The country code is shown as nnn. Contact your Paradyne sales office for the

correct number.

Equipment List

G-2 9820-A2-GB20-00March 1999

DescriptionModel/FeatureNumber

NMS Products

FrameSaver Management Package for WindowsIncludes OpenLane DCE Manager 2.1, OpenLane PerformanceWizard 4.1.1, and NetScout Manager Plus 5.5.1 for Windows.

7700-P1-001

FrameSaver Management Package for Unix Includes OpenLane DCE Manager 4.2, OpenLane PerformanceWizard 4.1.1, and NetScout Manager Plus 5.5.1 for Unix.

7800-P1-001

NetScout Server

For Unix or Windows NT 9190

NetScout WebCast

For Unix

For Windows NT

9145

9150

Cables

This table lists cables you can order.

Description Part NumberModel/FeatureNumber

COM Port-to-Terminal Cable(14 feet – 4.3 meters)

035-0314-1431 3100-F2-540

COM Port-to-LAN Adapter Cable(14 feet – 4.3 meters)

035-0315-1431 3100-F2-910

X.21 Cable Kit, which includes a:

X.21 Network Cable (10 feet – 3 meters)

X.21 DTE Adapter Cable, EIA-530A-to-X.21 (1 foot – .3 meters)

035-0384-1031

035-0302-0131

9008-F1-521

V.35 Cable Kit, which includes a:

V.35 Network Cable (10 feet – 3 meters)

V.35 DTE Adapter, EIA-530A-to-V.35

035-0383-1031

002-0095-0031

9008-F1-522

EIA-530 Straight-Through Cable, DB25-to-DB25 (10 feet/3 meters)

035-0385-1031 9008-F1-523

Standard EIA-232 Crossover Cable,DB25-to-DB25 (15 feet/4.6 meters)

035-0222-1531 4951-035F

GL-19820-A2-GB20-00 March 1999

Glossary

A software program housed within a device to provide SNMP functionality. Each SNMPagent stores management information and responds to the manager’s request for thisinformation.

A single bit stream that combines two or more bit streams.

Address Resolution Protocol. Part of the TCP/IP suite, ARP dynamically links an IPaddress with a physical hardware address.

American Standard Code for Information Interchange. The standard for data transmissionover telephone lines. A 7-bit code establishes compatibility between data services. TheASCII code consists of 32 control characters (nondisplayed) and 96 displayed characters.

Asynchronous terminal. A terminal such as the VT100 used for controlling computingdevices.

A data transmission that is synchronized by a transmission start bit at the beginning ofa character (five to eight bits) and one or more stop bits at the end.

A group of commands, issued from an asynchronous DTE, that allow control of the modemwhile in Command mode. All commands must begin with the characters AT and end with acarriage return.

Asynchronous Transfer Mode. A high-bandwidth, low-delay, connection-oriented switchingand multiplexing technique using fixed-size cells. Uses cell-switching rather than framerelay technology.

An SNMP trap that indicates that the device has received an SNMP protocol message thathas not been properly authenticated.

The mode in which the device automatically determines the asynchronous DTE data rate.

The mode in which the access unit forces automatic redetermination of the line rate assoon as a valid network signal is detected.

A FrameSaver feature that simplifies configuration. The FrameSaver unit creates networkand port interface DLCIs that match DLCIs identified in an LMI response message, thenconnects the network interface DLCIs with the port DLCIs.

American Wire Gauge. An indication of wire size. The heavier the gauge, the lower theAWG number, and the lower the impedance.

Backward Explicit Congestion Notification. A bit set and forwarded by the network to notifyusers of data traffic congestion, sent in the opposite direction of the frame carrying theBECN indicator or bit. Outbound frames may encounter congestion and be dropped.

Cluster Controller. A device that handles remote communications for multiple async (orother VT100-compatible) terminals or workstations.

Circuit Card Assembly. A printed circuit board to which separate components are attached.

Consultative Committee on International Telegraphy and Telephony. An advisorycommittee established by the United Nations to recommend communications standardsand policies. It was renamed ITU in March 1993.

Carrier Detect. A signal indicating that energy exists on the transmission circuit.Associated with Pin 8 on an EIA-232 interface.

agent

aggregate

ARP

ASCII

async terminal

asynchronous

AT command set

ATM

authentication-Failure trap

autobaud

autobaud mode

auto-configuration

AWG

BECN

CC

CCA

CCITT

CD

Glossary

GL-2 9820-A2-GB20-00March 1999

A bidirectional DS0, voice, or data path, for electrical transmission between two or morepoints. Also called a circuit, line, link, path, or facility.

Committed Information Rate. Less than or equal to the access rate, the CIR is used by theservice provider for rate enforcement when the network allocates bandwidth. When ratesexceed the CIR, frames may be discarded.

Communications port. A computer’s serial communications port used to transmit to andreceive data from a DCE. The DCE connects directly to this port.

Device software that sets specific operating parameters for the unit. Sometimes referred toas straps.

Customer Premises Equipment. Terminal equipment on the service user’s side of thetelecommunications network interface.

Cyclic Redundancy Check. A mathematical method of confirming the integrity of receiveddigital data.

Canadian Standards Association.

Controlled Slip Seconds. A period in which a frame was added or deleted because of avariance in timing.

Clear To Send. A signal indicating that the device is ready for the DTE to transmit data.Usually occurs in response to Request To Send (RTS).

Data Carrier Detect. A signal passed from a local modem to a local DTE when the modemhas received an acceptable carrier signal over the phone line (also known as RLSD,received line carrier detect).

Data Communications Equipment. The equipment that provides the functions required toestablish, maintain, and end a connection. It also provides the signal conversion requiredfor communication between the DTE and the network.

Data Delivery Ratio. The number of bytes delivered divided by the number of bytesoffered; that is, the number of bytes actually received by the far-end device divided by thenumber of bytes sent. Used to determine the amount of data dropped by the network.

Discard Eligibility. Part of the frame header that marks a frame for low priority if there iscongestion on the network. If congestion occurs, DE frames are the first to be discarded bythe network.

The end point of a PVC connection, comprising a designated port, DLCI, and EDLCI.

Data Link Connection Identifier. The virtual circuit number corresponding to a particularconnection between two destinations. This number is used as part of the frame relayheader. The total number of DLCIs between endpoints make up the PVC. DLCIs are alocal means of identifying a PVC.

Canadian Department of Communication.

Data Set Ready. An EIA-lead standard for V.24 circuit CC, ITU 107; an output signal(DCE-to-DTE).

Data Service Unit. Data communications equipment that provides timing, signalregeneration, and an interface between the DTE and the digital network. A subrateDSU/CSU is normally referred to as a DSU.

Data Terminal Equipment. The equipment, such as a computer or terminal, that providesdata in the form of digital signals for transmission.

Data Terminal Ready. An EIA-lead standard for V.24 circuit CD, ITU 108; an input signal(DTE-to-DCE).

channel

CIR

COM port

configuration option

CPE

CRC

CSA

CSS

CTS

DCD

DCE

DDR

DE

destination

DLCI

DOC

DSR

DSU

DTE

DTR

Glossary

GL-39820-A2-GB20-00 March 1999

Embedded Data Link Connection Identifier. Use when multiplexing user data on a singleDLCI (comparable to having multiple DLCIs on an interface being routed to a single DLCIon the network side). EDLCIs use a proprietary method to multiplex DLCIs that have beenselected as one end of a connection. An EDLCI is a number between 0 and 62, and itidentifies the individual connection within a multiplexed DLCI.

Electronic Industries Association. This organization provides standards for the datacommunications industry to ensure uniformity of interface between DTEs and DCEs.

Protocol-created control information that is added to the data or frame which has beenbroken into blocks or packets. The DTE constructs control packets and encapsulates userdata within those packets.

MIB objects unique to a specific company’s devices.

ElectroStatic Discharge. An undesirable discharge of static electricity that can damageequipment and degrade electrical circuitry.

Federal Communications Commission. The Board of Commissioners that regulates allelectrical communications that originate in the United States.

Frame Delivery Ratio. The number of frames delivered divided by the number of framesoffered; that is, the number of frames actually received by the far-end device divided bythe number of frames sent. Used to determine the number of frames dropped by thenetwork.

Forward Explicit Congestion Notification. A bit set and forwarded by the network to notifyusers of data traffic congestion, sent in the same direction of the frame carrying the BECNindicator or bit. Inbound frames may encounter congestion and be dropped.

Front-End Processor. A communications computer associated with a host computer thatmanages the lines and routing of data through the network.

Frame Relay Assembler/Disassembler. The equivalent of an X.25 PAD, a FRAD connectsnon-frame relay devices to the frame relay network. It also provides encapsulation andtranslation capability.

Frame Relay Aggregation. This capability statistically multiplexes packet streams onto asingle frame relay connection.

One identifiable group of bits that includes a sequence of bits for control, framing, etc.

A high-speed connection-oriented packet switching WAN protocol using variable-lengthframes.

The DLCI identifier contained within the frame relay packet.

The ability to route frame relay frames based on the source port and frame relay header(DLCI). The header contains a DLCI identifier that distinguishes the port for which the datais intended.

Frame Relay Aware. Said of a unit that can read the frame relay header and route the datainternally to the correct port.

File Transfer Protocol. A TCP/IP standard protocol that allows a user on one host toaccess and transfer files to and from another host over a network, provided that the clientsupplies a login identifier and password to the server.

High-Level Data Link Control. A communications protocol defined by the InternationalStandards Organization (ISO).

A shared boundary between functional units.

EDLCI

EIA

encapsulated

Enterprise MIB

ESD

FCC

FDR

FECN

FEPFEP

FRAD

FRAG

frame

frame relay

frame relay headerframe relay header

frame relay switching

FRAW

FTP

HDLC

interface

Glossary

GL-4 9820-A2-GB20-00March 1999

Inverse Address Resolution Protocol (InARP). A protocol that permits a frame relay routerat one end of a (management) PVC to acquire the IP address of the device at the otherend of the PVC via the PVC’s associated DLCI.

Internet Protocol. An open networking protocol used for internet packet delivery.

Internet Protocol address. The address assigned to an internet host.

Internetwork Packet Exchange. A LAN communications protocol used to move databetween server and workstation programs running on different network nodes.

International Telecommunications Union. The telecommunications agency of the UnitedNations, established to provide standardized communications procedures and practices.Before March 1993 it was called CCITT.

Local Area Network. A privately owned and administered data communications networklimited to a small geographic area.

A loopback that is maintained until a specific release code is detected. A latching loopbackcan only be initiated or terminated by the 64 kbps clear channel network service provider.

Time it takes to transfer data from its source to its destination.

Light Emitting Diode. A light or status indicator that glows in response to the presence of acertain condition (e.g., an alarm).

Local Loopback. A diagnostic test in which data is looped through data communicationsequipment from the DTE interface and back to the DTE.

Line LoopBack. A test in which the received signal on the network interface is looped backto the network without change.

Local Management Interface. The standard set of procedures and messages that managea PVC linking two DTEs. It is a common standard for link-management signaling(information exchange).

A diagnostic procedure that sends a test message back to its origination point. Used totest various portions of a data link in order to isolate an equipment or data line problem.

Loss of Signal. A digital line condition where there are no pulses.

Line Signal Detect. An EIA-lead standard for V.24 circuit CF, ITU 109; an output signal(DCE-to-DTE).

Line Termination Unit. The control unit on the network end of a link. (The NTU is on thecustomer premises end.)

A network configuration where each node has a path to every other node.

Management Information Base. A database of managed objects used by SNMP to providenetwork management information and device control.

A method for interleaving several access channels onto a single circuit for transmissionover the network.

Network Access Module. It is a type of CCA that accesses or acts as an interface with thenetwork.

Network Control Center. An operator-controlled command facility or application thatmonitors and controls network operation. Sometimes called a NOC.

Network Management System. A computer system used for monitoring and controllingnetwork devices.

Network Operation Center. Same as an NCC.

inverse ARP

IP

IP address

IPX

ITU

LAN

latching loopback

latency

LED

LL

LLB

LMI

loopback

LOS

LSD

LTU

mesh network

MIB

multiplexing

NAM

NCC

NMS

NOC

Glossary

GL-59820-A2-GB20-00 March 1999

A loopback that is not maintained unless network loopback codes are interspersed with thetest data. A non-latching loopback can only be initiated or terminated by the networkservice provider.

Network Termination Unit. The unit on the customer premises end of a link. (The LTU is onthe network end.)

Open Systems Interconnection. The seven-layer architecture of data communicationprotocols developed by ISO and ITU.

Packet Assembly and Disassembly. The term PAD is used extensively in X.25 networks;however, it can apply to any packet-switched network, such as frame relay.

Packet InterNet Groper. Used for testing and debugging networks, PING sends an echopacket to the specified host, waits for a response, then reports the results of its operation.Used as a verb, to PING means to use the program to verify the accessibility of a device.

Point-to-Point Protocol. A protocol for packet transmission over serial links, specified byInternet RFC 1661.

Specialized agent software designed to gather a wide variety of statistical informationabout network operation. The probe gathers the information, and the agent (theFrameSaver SLV unit) stores the statistical information locally.

A set of rules that determines the behavior of devices in achieving and maintainingcommunication.

Public Switched Telephone Network. A network shared among many users who can usetelephones to establish connections between two points. Also known as dial network.

Permanent Virtual Circuit. This is the DSU’s in-band management channel that supportsremote management via a Telnet connection. It is the logical link, identified by a DLCI,used for routing frames over the network from their source to their destination.

A patented method for multiplexing the data of multiple DLCIs onto a single DLCI to sharea single PVC connection.

A circuit that accepts data signals from a transmitter.

Standard of multiprotocol interconnect over frame relay. The encapsulation method forcarrying network interconnect traffic over a frame relay backbone; it also covers bothbridging and routing.

Routing Information Protocol. A protocol for exchanging routing information.

Received Line Signal Detect. A signal from the DCE that can be monitored by the DTE ona data port to determine when valid data is being received from the connected DCE.

Remote MONitoring. A management standard that was developed to provide trafficstatistics and analysis for comprehensive network fault diagnosis, planning, andperformance tuning.

Remote MONitoring, Version 1 (RFC 1757). This is the MIB that supports Alarm and EventGroups, which controls events that trigger SNMP traps. Remote and proactive monitoringand troubleshooting of traffic problems is possible through the statistical data collected.

Remote MONitoring, Version 2 (RFC 2021). This is the MIB Group that supports UserHistory Collection. Proactive monitoring and troubleshooting, performance optimization,and resource planning is possible through the SLV performance statistic collected.

A device that connects LANs by dynamically routing data according to destination andavailable routes.

Request to Send. An EIA-lead standard for V.24 circuit CA, ITU 105; an input signal(DTE-to-DCE).

nonlatching loopback

NTU

OSI

PAD

PING

PPP

probe

protocol

PSTN

PVC

PVC multiplexing

receiver

RFC 1490-compliant

RIP

RLSD

RMON

RMON1

RMON2

router

RTS

Glossary

GL-6 9820-A2-GB20-00March 1999

Received Clock. An EIA-lead standard for V.24 circuit DD, ITU 115; an output signal(DCE-to-DTE).

Received Data. An EIA-lead standard for V.24 circuit BB, ITU 104; an output signal(DCE-to-DTE).

Synchronous Data Link Control. An IBM standard data link protocol.

Service Level Agreement. A contract between a frame relay service provider and acustomer in which the service provider guarantees a certain level or quality of service tothe customer. Level of service is defined by a set of measurable parameters, each havingthresholds that are negotiated by the service provider and customer.

Serial Line Internet Protocol. Protocol for serial operation on an internet.

Simple Network Management Protocol. Protocol for open networking management.

Message sent by the customer’s frame relay equipment to maintain its user-network keepalive process, and requesting a status from the network. Network responds to each statusenquiry frame.

Concurrent, such as a data transmission synchronized by a time signal that accompaniesthe data.

Transmission Control Protocol. An Internet standard transport layer protocol defined inSTD 7, RFC 793. It is connection-oriented and stream-oriented.

Virtual terminal protocol in the Internet suite of protocols. Allows the user of one hostcomputer to log into a remote host computer and interact as a normal terminal user of theremote host.

Amount of data, or the number of data units per units of time, that pass through thenetwork when it is operating a peak capacity.

Test Mode. An EIA-lead standard for V.24 circuit TM, ITU 142; an output signal(DCE-to-DTE).

A circuit capable of generating, modulating, and sending a signal for communication,control, and other purposes.

Transmit Clock. An EIA-lead standard for V.24 circuit DB, ITU 114; an output signal(DCE-to-DTE).

Transmit Data. An EIA-lead standard for V.24 circuit BA, ITU 103; an input signal(DTE-to-DCE).

Underwriter’s Laboratories, Inc. An organization which promotes product safety.

User-Network Interface. The interface of a frame relay end user and a frame relay switch,or a frame relay switch and a public carrier.

Volts alternating current.

A logical link/connection or packet-switching mechanism established between two devicesat the start of transmission.

Wide Area Network. A network that spans a large geographic area.

RXC

RXD

SDLC

SLA

SLIP

SNMP

status enquiry

synchronous

TCP

Telnet

throughput

TM

transmitter

TXC

TXD

UL

UNI

Vac

virtual circuit

WAN

IN-19820-A2-GB20-00 March 1999

Index

Numbers1MPort, auto configuration, 8-111Port, auto configuration, 8-1355 hexadecimal, test pattern, 13-13

Aaborting tests, 13-10Access

Dial-In, 9-43Name, 9-27to user interface, resetting/restoring, 12-13Type, 9-32

Access Level, 10-9, 10-10assigning, 10-7Port, 9-40security, 4-3Session, 9-29

accessing NetScout Manager Plus, 5-6adding

DLCI records, 9-15SLV units to network, 5-4, 7-4

aggregated summary, 5-11Alarm

(Fail), 11-4adding manually, 6-11editing, 6-9LED is lit, 13-4RMON defaults, D-1using template, 6-8viewing messages, 12-5

alarms, 13-3ALM, LED, 11-4Alternate

Dial-Out Directory, 9-37IP Address, 9-44software revision, 11-2Subnet Mask, 9-44

Annex A and D, LMI Protocol, 9-10application, using the unit in your network, 3-1ARP, inverse, 1-6

assigningcommunity names and access levels, 10-7IP addresses and subnet masks, B-10

async terminal, interface, 4-4AT commands, 9-43At-a-Glance report, 7-10, 7-36authentificationFailure trap, C-2Auto-Configuration, 1-6, 3-7, 4-2

Active, 11-6setting up, 8-8

Auto-rating, 9-6, 11-7availability, 7-28, 7-35, 7-37

distribution for all groups, 7-30LMI and PVC, 1-5

averageHealth Index, 7-20, 7-35network volume, 7-20

Bback door access when locked out, 12-13back-to-back, Mode Active, 11-6back-to-back operation, 3-8, 12-14Backspace, 4-5bandwidth

distribution, 7-30, 7-32, 7-35in and out, 7-37utilization, 7-26

baseline, 7-24element/DLCI volume vs, 7-26period, 7-20

Bc, 9-17Be, 9-17BECN, 5-15, 7-37blank, field value, 4-8branches/menus, 4-2bucket, 1-9burst

analysis, 5-19distribution, 7-39ranges, 5-8

bytes, in and out, 7-37, 7-39

Index

IN-2 9820-A2-GB20-00March 1999

Ccall directories, modem, 12-6Call Retry, 9-37capacity, 5-11, 5-17change leaders, 7-24changing

auto-configuration, 8-9configuration options, 8-6domains and groups, 6-6FR Discovery mode, 8-9modem call directory numbers, 12-6operating mode, 12-15software release, 12-10

Character, Length, 9-38character, matching, 4-8CIR (bps), 9-16Clearing

Event, LMI, 9-3, 9-11existing information, 8-3, 8-4

ClockInvert Transmit, 9-8out of range, 11-7Out of Range at Network, message, 9-6Source, Transmit, 9-8

COM port, 1-7, 9-22, 9-34, 9-43configuring an external device, 2-7connector, E-2creating a separate management link, 2-6

combining private and public addressing on samenetwork, B-2

Committed Burst Size Bc (Bits), 9-16Committed Information Rate (CIR), 9-16Communication, Port, user interface options, 9-38Community Name, 9-27

assigning, 10-7Concord, 1-2Concord Network Health, compatibility, 7-1Configuration

Auto, Active, 11-6customer storage areas, 1-8displaying and changing options, 8-6menu/branch, 4-2option areas, 8-5saving options, 8-7tables, 8-5upload/download, 1-7

configuringadded SLV units/elements, 7-5end-to-end management control, 2-8

external device, 2-7local management, 2-4management DLCI, 2-5NetScout Manager Plus, 6-3the unit, 8-4

congestion, 5-17DLCI, 5-16

connectivity, 13-13IP, 1-7

Controlkeys, 4-5Leads, Ignore, 9-39menu/branch, 4-2

controllingasync terminal access, 10-2external device access, 10-5FTP access, 10-4SNMP access, 10-6Telnet access, 10-3

conversation elements, 7-4copyrights, ACRC, 11-23creating

a login, 10-10a separate management link, 2-6additional DLCI records, 9-15new PVC connections/management links, 8-6PVC connections, 5-7user history files, 6-13

crossover cable, EIA-232, E-4CTS down to Port Device, 11-6current software revision, 11-2customer service level report, 7-33customer-specified storage areas, 1-8

DData

Delivery Ratio (DDR), 1-5Link Control Identifier (DLCI), 9-25Port

Diagnostics, 5-14physical options, 9-8

port rates, 1-8Rate (Kbps), 9-38selection criteria, 4-3

Index

IN-39820-A2-GB20-00 March 1999

Data Port, network interface options, 9-6Date & Time setting, 8-4DB25, COM Port, connector, E-2DB25-to-DB25

crossover cable, E-4straight-through cable, E-13, E-14

DB25-to-V.35DTE adapter, E-11, E-12network cable, E-10V.35 network cable, E-9

DB25-to-X.21adapter cable, E-8network cable, E-7

DCE Managerinstallation and setup, 5-2NMS support, 1-3

DDR, 1-5DE

frames in and out, 7-37Set, 9-24

Default IP Destination, 9-22Delete key, 4-5deleting

a login, 10-11modem call directory phone number, 12-6

deliveryPVC analysis, 5-18success, 5-20

Destination, 9-34Default IP, 9-22DLCI, 9-20EDLCI, 9-20Link, 9-19

detail exception report, 7-17determining

test status/results, 13-10whether statistic is incrementing, 11-18

DeviceFail, 11-4, 11-6messages, 11-10troubleshooting problems, 13-4

Diagnostics, data port graph, 5-14Dial-In Access, 9-43Dial-Out

Delay Time (Min), 9-37Directory, 9-37options, 9-32Trap, 9-36

DirectoryAlternate Dial-Out, 9-37displaying and changing numbers, 12-6maintaining modem, 12-6

disabling, SNMP access, 10-6Discard Eligible (DE), 9-24Disconnect, Time (Minutes), 9-29, 9-41discovering elements/DLCIs, 7-4Discovery, frame relay (FR), 8-8, 8-9displaying

configuration options, 8-6identity information, 11-2LEDs, 11-3, 12-5modem call directory numbers, 12-6statistical information, 11-18

distributionavailability and latency, 7-30bandwidth, 7-30, 7-32, 7-35frame size, 7-39

DLCI, 9-25congestion, 5-16Destination, 9-20Down, 11-7element Health Index, 7-26element summary, 7-32element volume vs. baseline, 7-26elements summary report, 7-25Health Index exceptions, 7-34interface status, 11-15monitored, 1-8monitoring user history, 6-16Number, 9-16Priority, 9-17Records, 9-13Source, 9-19statistics, 11-20total number, 1-8Traps on Interfaces, 9-36Type, 9-16up time, 7-39

domains and groupscorrecting, 6-6verifying, 6-5

download, 12-9capability, 1-7

Index

IN-4 9820-A2-GB20-00March 1999

downloadingdetermining when completed, 12-8MIBs and SNMP traps, 1-13, 12-11SLV alarms, 6-8software, 12-7user history file, 6-13

dropped frames, 7-39DTE

configuring port using a management DLCI, 2-5Loopback, 13-14MIB, 1-13port-initiated loopbacks, 9-9

DTLB, 13-14DTR

down from Port-1 Device, 11-7Ignore Control Leads, 9-39

EEDLCI, 1-2, 1-6, 3-7, 9-25

Destination, 9-20management using PVC multiplexing, 2-8Source, 9-19

EIA-232, crossover cable, E-4EIA-530A

connector, E-6straight-through cable, E-13to-V.35

DTE adapter, E-11network cable, E-9

to-X.21adapter cable, E-8network cable, E-7

elements/DLCIs, 7-4summary, 7-32summary report, 7-25

Embedded Data Link Connection Identifier (EDLCI),9-19, 9-20, 9-25

end-to-end data delivery success, 5-20ending a session, 12-4Enter (Return) key, 4-5entering, Identity information, 8-3Enterprise

MIB, 1-13Specific Traps, 9-33, 9-35, C-6

equipment list, G-1Error

Event, LMI, 9-3, 9-11messages, 5-9

errored, frames, 5-13Errors

frame relay statistics, 11-22LMI signaling, 5-13

Esc key, 4-5even parity, 9-39exception points, 7-17exceptions report, 7-17

situations to watch, 7-21summary and detail, 7-17

Excess Burst Size (Bits), 9-17executive service level report, 7-29External

Deviceconfiguring, 2-7controlling access, 10-5

Modem(on Com Port) options, 9-43Commands, 9-43

Transmit Clock, 9-8

Ffaceplates, 4-1

9126, 11-3FDR, 1-5features, 1-5FECN, 5-15, 7-37field is blank/empty, 4-8file transfer, 12-7FTP (file transfer protocol), 9-30

Session, 9-30Frame

Delivery Ratio (FDR), 1-5size distribution, 5-21

Frame RelayDiscovery, 8-8, 8-9DTE, MIB, 1-13monitoring, 3-1multinational application, 3-2options, 9-10service MIB, 1-13statistics, 11-21troubleshooting PVC problems, 13-6

frames, 9-24in and out, 7-37, 7-39setting the range, 5-8size distribution, 7-39

Index

IN-59820-A2-GB20-00 March 1999

FTP, 1-7, 12-7file transfers, 12-7initiating a session, 12-7limiting access, 10-4Login Required, 9-30Max Receive Rate (kbps), 9-30Session, 10-4

function keys, 4-4, 4-6

GGeneral

LEDs, 11-4options, 9-5SNMP management, options, 9-27Traps, 9-33, 9-35

generating reports, 7-7graphs, Performance Wizard, 5-10grouping elements for reports, 7-6

Hhardware, requirements, 6-1, 7-2hardware revision, NAM, 11-2HDLC errors, frame relay statistics, 11-23Health and Status, messages, 11-6Health Index, 7-18

average, 7-20, 7-35change leaders, 7-24element/DLCI, 7-26exceptions, 7-32, 7-34leaders, 7-23

heaviest users – output, 5-12highlighted text, hyperlink to more information, xiiihistory

adding files, 6-13installing files, 6-15monitoring DLCI, 6-16

hyperlink to more information, highlighted text, xiii

IIdentity

displaying, 11-2entering information, 8-3

Ignore Control Leads, 9-39Inactivity Timeout, 9-29, 9-40installation and setup

DCE Manager, 5-2Network Health, 7-3Performance Wizard, 5-2SLM Reports, 5-23

installingNetScout Manager Plus and graphs, 6-2Network Health, 7-3Performance Wizard, 5-3user history files, 6-15

interfaceasync terminal/user, 4-4menu-driven, 1-8

Internal, Transmit Clock, 9-8international, application, 3-2Inverse ARP, 1-6, 2-5, 2-8, 2-9Invert Internal Clock, 9-6Invert Transmit Clock, 9-8IP

connectivity, 1-7node information, 9-21Ping test, 13-15Validation, NMS, 9-31

IP Address, 9-23, 9-41, 9-44NMS number, 9-31, 9-34Node, 9-21

IP addressingassigning addresses and subnet masks, B-10direct PVCs to remote units, B-5limiting SNMP access, 10-8mixing private and public addressing on same

network, B-2scheme examples, B-5selecting a scheme, B-1

IT manager service level report, 7-31

Kkeys

keyboard, 4-5screen function, 4-4, 4-6

LLamp Test, 1-11, 11-9, 13-17LAN, adapter and cable, E-3LAN/WAN Health Report, 7-11latency, 1-5, 5-20, 7-28, 7-37

distribution, 7-30maximum and average, 7-39round trip, 5-20

launching graphs, 5-12leaders

change, 7-24Health Index, 7-23summary report, 7-22volume, 7-23

Index

IN-6 9820-A2-GB20-00March 1999

LEDs, 4-1, 13-2, 13-49820 faceplate and screen, 11-3descriptions, 11-4displaying, 11-3viewing, 12-5

limitingasync terminal access, 10-2FTP access, 10-4SNMP access, 10-6

through IP addresses, 10-8Telnet access, 10-3

LinkDestination, 9-19frame relay statistics, 11-21Protocol, 9-42Source, 9-19Traps, 9-35Traps Interfaces, 9-35up time, 7-39

link-layer protocols, 1-7linkUp and linkDown

events, 9-35traps, C-3

LMIand PVC availability, 1-5Behavior, 9-2Clearing Event (N3), 9-3, 9-11Down, 11-8Error Event (N2), 9-3, 9-11frame relay statistics, 11-23Heartbeat (T1), 9-3, 9-12Inbound Heartbeat (T2), 9-3, 9-12N4 Measurement Period (T3), 9-3, 9-12Parameters, 9-11pass-through, 9-2Protocol, 9-10protocol, 1-7signaling errors, 5-13Status Enquiry (N1), 9-3, 9-11

localexternal DTE loopback, 9-9management, 1-7

locked out, 10-2, 10-10, 12-13logging in and out, 12-2Login

creating, 10-10ID, 10-10modifying and deleting, 10-11Required, 9-28, 9-39, 10-2, 10-3, 10-4

logins, 10-1Loopback

DTE, 13-14Port (DTE) Initiated, 9-9PVC, 13-12

LOSat Network, 9-6, 11-8LED, 11-4

MMain Menu, screen/branch, 4-2maintaining, modem directories, 12-6maintenance, 12-1making input selections, 4-8Management

and Communication, options, 9-20configuring end-to-end control, 2-8control and IP addressing, 2-1creating a separate link, 2-6General SNMP, options, 9-27links, total number dedicated, 1-8local and remote, 1-7network, user interface, 4-1paths, 1-7PVCs, 9-23selecting interface, 8-2service provider, 2-3SNMP, 1-7, 1-13, 9-27using a dedicated DLCI, 2-9using PVC multiplexing (EDLCI), 2-8using RFC 1490 routers, 2-10

managing FrameSaver unit, 2-4Menu, structure, A-1menu

branches, 4-2path, 4-4selecting from, 4-7

menu-driven user interface, 1-8, 4-1messages

Device, 11-10Health and Status, 11-6Self-Test Results, 11-5system, 4-4System and Test Status, 11-5Test Status, 11-9viewing alarm and status, 12-5

Index

IN-79820-A2-GB20-00 March 1999

MIBdownloading, 1-13, 12-11objects, test commands, 1-11support, 1-13

minimal remote configuration, 8-2mixing private and public addressing on same network,

B-2mManagement, overview, 2-2Mode

changing Operating, demos, 12-15Test, 11-4

model number, 4-4modifying, a login, 10-11Monitor

DTR, 9-9test pattern, 13-13

Monitor CTS, 9-7Monitor DSR, 9-7Monitor RTS, 9-9monitoring, 1-9

DLCI history data, 6-16FrameSaver unit, 11-5LEDs, 11-3using NetScout Manager Plus, 6-19

multinational, application, 3-2Multiplexed

DLCI, 9-19, 9-20, 9-25DLCI Type, 9-16PVCs, 13-13

multiplexing, applications, 3-6

NN1, LMI Status Enquiry, 9-3, 9-11N2, LMI Error Event, 9-3, 9-11N3, LMI Clearing Event, 9-3, 9-11Name, 9-23

1 or 2 Access, 10-7Access, 9-27, 9-28Community, 9-27

navigating the screens, 4-5Navigation Wizard, historical data collection, 5-5NCC (network control center), 2-3, 9-14Net Link, Port Use, 9-38NetOnly, 8-10

auto configuration, 8-14NetScout

Manager Plus, from Performance Wizard, 5-6NMS solution, 6-1NMS support, 1-1

NetScout Manager Plus, NMS support, 1-4Network

Com Link Down, 11-8data port, LED, 11-4data port connector, E-6DLCI records, options, 9-13dropped frames, 7-39Health (Concord) compatibility, 7-1latency, 1-5Management, 4-1mixing private and public addressing on same

network, B-2physical options, 9-6PVC Loopback, 13-12volume, 7-20, 7-30, 7-32

Network Health, installation and setup, 7-3NMS

IP Address, 9-31, 9-34, 10-9IP Validation, 9-31, 10-9OpenLane management solution, 1-3SNMP security, options, 9-31

NOC (network operation center), 2-3, 3-4, 9-14Node

IP Address, 9-21Subnet Mask, 9-21

Node IP, configuration option tables, 9-21NSP, 9-2NTU, 1-1Number of

Managers, 9-31, 10-9Trap Managers, 9-34

Oodd parity, 9-39OID (object identification), user history file, 6-13OK, LED, 11-4OpenLane

graphs, 5-10NMS solutions, 5-1NMS support, 1-3

operatingchanging mode for demos, 12-15the unit, 12-1

organization of this document, xiOut of Sync, message, 13-6, 13-13Outbound Management Priority, 9-17

Index

IN-8 9820-A2-GB20-00March 1999

Ppackets, 9-24Parity, 9-39Password, 10-10patents, Apattern, send/monitor, 13-13performance statistics, 11-17Performance Wizard

copying directory, 6-3graphs, 5-10installation and setup, 5-2NMS support, 1-3

physicaldata port options, 9-8tests, 13-14

pin assignmentsCOM Port, EIA-232 connector, E-2COM port

to-LAN cables, E-3to-terminal, E-2

crossover cable, EIA-232, E-4DB25-to-DB25, straight-through cable, E-14EIA-530A connector, E-6V.35 DTE adapter, E-12V.35 network cable, E-10X.21 DTE adapter cable, E-8X.21 network cable, E-7

Ping test, 13-15point-to-point (PPP), protocol, 1-7Port

(DTE) Initiated Loopbacks, 9-9Access Level, 9-40, 10-2communication, options, 9-38PVC Loopback, 13-12Use, 9-38

Port Rate, 9-6Port Type, 9-6, 9-8PPP, 9-42

protocol, 1-7Primary Destination

DLCI, 9-20EDLCI, 9-20Link, 9-19

Primary Frame Relay Link, 9-24Primary Link RIP, 9-26printed reports, 7-10product-related documents, xivProprietary, RIP, 9-26, 9-42

Protocoladdress resolution, 1-6Link, 9-42link-layer, 1-7LMI, 9-10Point-to-Point (PPP), 9-42routing, 1-7Routing Information (RIP), 9-26, 9-42Serial Line, IP (SLIP), 9-42Simple Network Management (SNMP), 9-27support, 1-7

PVCavailability, 1-5connections, 9-18

creating, 5-7total number, 1-8

data delivery analysis, 5-18Management, 9-23

total number dedicated, 1-8multiplexing, 2-8, 3-6name, 9-22, 9-34Network Loopback, 13-12tests, 1-11, 13-11throughput, 5-14troubleshooting problems, 13-6

QQoS, 1-1, 1-5quality of service, 1-1, 1-5, 9-17Quick Reference, 8-5

Rranges, setting frame and burst, 5-8rates, 1-8ratios, FDR and DDR, 1-5reachability, 7-28rear panel, E-1remote

management, 1-7units

minimal configuration, 8-2on same subnet, B-6using different subnets, B-7using direct PVCs, B-5using routers, B-8

Index

IN-99820-A2-GB20-00 March 1999

reportsNetwork Health, 7-8Performance Wizard, 5-10SLV, 3-4

resettingthe access unit, COM port, 12-13the unit, 12-12unit default configuration options, 12-13

restoring communication with a misconfigured unit,12-13

restoring user interface access, 12-13retrieving statistics, 12-11Return (Enter) key, 4-5revision, software and hardware, 11-2RFC 1213 and 1573, 1-13RFC 1315, 1-13RFC 1490, routers, for transparent management, 2-10RFC 1604, 1-13RFC 1659, 1-13RFC 1757, 1-13RFC 2021, 1-13right arrow key, 4-5RIP, 9-42RMON

alarm and event defaults, D-1Specific Traps, C-9Traps, 9-36Version 1, MIB, 1-13Version 2, MIB, 1-13

round trip network latency, 5-20router-independence, 1-6, 9-2Routing

Information Protocol (RIP), 9-42on same subnet, B-6protocols, 1-7using different subnets, B-7using routers, B-8

RS-232-like MIB, 1-13running reports, 7-7

SSampling, SLV Inband and Interval, 9-4saving configuration options, 8-7screen

area, 4-4format types, 4-3function keys, 4-6function keys area, 4-4how to navigate, 4-5

scrolling through valid selections, 4-8security, 1-12, 4-3, 8-5, 10-1, 12-3

SNMP NMS, options, 9-31selecting

a field, 4-7an IP addressing scheme, B-1from a menu, 4-7management interface, 8-2

Self-Test Results messages, 11-5Send, test pattern, 13-13serial line internet protocol (SLIP), 1-7serial number, NAM, 11-2Service, Aservice level

agreement, 1-2, 1-5customer report, 7-33executive report, 7-29IT manager report, 7-31reports, 7-10verification, statistics, 11-19verifier (SLV), 1-1

service provider management control, 2-3Session

Access Level, 9-29, 10-3ending, 12-4starting, 12-3

Set DE, 9-24setting

date and time, 8-4frame and burst ranges, 5-8

setting upauto-configuration, 8-8considerations when, 8-1historical data collection, 5-5management configuration, 8-2

situations to watch table, 7-21SLA, 1-2, 1-5, 5-18SLIP, 9-42

protocol, 1-7SLM Reports, 5-1

creating, 5-22installation and setup, 5-23

SLV(service level verifier), 1-1

feature summaries, 1-5Delivery Ratio, 9-4frame relay

access, 3-3monitoring, 3-1

options, 9-4reports, 3-4

installation and setup, 5-23Sample Interval (secs), 9-4

Index

IN-10 9820-A2-GB20-00March 1999

SNMPassigning community names/access levels, 10-7limiting access, 10-6, 10-8Management, 1-7, 1-13, 9-27, 10-6MIB, object test commands, 1-11NMS security, options, 9-31Number of Managers, 9-31Traps, 9-32

downloading, 12-11standards compliance, C-1supported, 13-3

softwarechanging, 12-10download, 1-7downloading, 12-7requirements, 6-1, 7-2revision, NAM, 11-2

SourceDLCI, 9-19EDLCI, 9-19Link, 9-19

Spacebar, 4-5specifications, technical, F-1standards compliance, SNMP traps, C-1starting

a session, 12-3a test, 13-9graphs, 5-12Performance Wizard, 5-3

statistics, 1-9, 11-17displaying, 11-18elements, 7-4uploading to an NMS, 12-11

StatusEnquiry, LMI, 9-3, 9-11information, 11-5LED, 11-4menu/branch, 4-2PVC connection, 11-16viewing messages, 12-5

Stop Bits, 9-39stopping a test, 13-9Subnet

assigning IP addresses and masks, B-10routing using different, B-7routing using same, B-6

Subnet Mask, 9-24, 9-41, 9-44Node, 9-21

suggestions, user documentation, Asummary

aggregated, 5-11element/DLCI, 7-32element/DLCI report, 7-25exception report, 7-17leaders report, 7-22network report, 7-19

supplemental report, 7-27switching

between screen areas, 4-8to new software, 12-10

Systemand test status messages, 11-5entering Identity, 8-3Frame Relay and LMI, options, 9-2messages, 4-4Name, Contact, and Location, 11-2options, 9-2

TT1, LMI Heartbeat, 9-3, 9-12T2, LMI Inbound Heartbeat, 9-3, 9-12T3, LMI N4 Measurement Period, 9-3, 9-12Tab key, 4-5TCP, 12-7technical specifications, F-1Telnet

limiting access, 10-3Session, 10-3

user interface options, 9-28Terminal, Port Use, 9-38Test

menu/branch, 4-2Mode, 11-4Status messages, 11-9

Tests, 1-11aborting, 13-10available, 13-7determining status and results, 13-10DTE Loopback, 13-14Duration, 9-5IP Ping, 13-15Lamp, 13-17MIB object commands, 1-11physical, 13-14PVC, 13-11PVC Loopback, 13-12starting or stopping, 13-9test pattern, 13-13Timeout, 9-5, 13-8

Index

IN-119820-A2-GB20-00 March 1999

throughput, 1-5, 5-11, 5-13, 5-14, 5-17time, setting, 8-4Timeout

Inactivity, 9-29, 9-40Test, 13-8

total network volume, 7-20trademarks, ATraining, Atransfering statistics to an NMS, 12-11transmit

bit burst analysis, 5-19frame size distribution, 5-21

Transmit ClockInvert, 9-8Source, 9-8

transparent remote management control, 2-10Trap

Dial-Out, 9-36Disconnect, 9-36Managers, Number of, 9-34

TrapsauthentificationFailure, C-2DLCI, 9-36Enterprise Specific, 9-35, C-6General, 9-35Link, 9-35Link Interfaces, 9-35linkUp and linkDown, C-3RMON, 9-36RMON Specific, C-9SNMP and dial-out, options, 9-32standards compliance, C-1supported, 13-3warmStart, C-2

Trendanalysis, 7-18report, 7-10, 7-40

troubleshooting, 13-1device problems, 13-4frame relay PVC problems, 13-6

TruePut, 1-5TST, LED, 11-4Type, Access, 9-32typical applications, 3-1

UUNI, 9-3unit, managing, 2-4upgrade, 12-9

performing, 12-9upload/download capability, 1-7uploading statistics to an NMS, 12-11user data port

connector, E-6LED, 11-4

user historyadding files, 6-13installing files, 6-15monitoring DLCI, 6-16statistics gathering, 1-9

user interface, 1-8, 4-1cannot be accessed, 13-4communication port, options, 9-38external modem (on Com port), options, 9-43resetting/restoring access, 12-13Telnet session, 9-28viewing alarms and LEDs, 12-5

user-defined history, 6-13utilization, bandwidth, 7-26

VV.35, cable kit, E-9, E-11valid, modem directory characters, 12-6Value Out of Range message, 9-16variable-bindings, C-4, C-7, C-9viewing

alarm messages, 12-5alarms and LEDs via user interface, 12-5LEDs, 11-3Network Health charts and tables, 7-8Performance Wizard graphs, 5-10

volumechange leaders, 7-24leaders, 7-23network, 7-20, 7-30, 7-32per element/DLCI, 7-34vs. baseline, 7-26

Index

IN-12 9820-A2-GB20-00March 1999

WWAN Health Report, 7-11warmStart

events, General Traps, 9-35trap, C-2

warranty, Aweb browsers, 5-22Web-site, access to documentation, xiv

XX.21, cable kit, E-7, E-8

support.dasanzhone.comsupport.dasanzhone.com/support/manuals/docs/98/... · 9820-A2-GB20-00 March...

Documents

Transcript of support.dasanzhone.comsupport.dasanzhone.com/support/manuals/docs/98/... · 9820-A2-GB20-00 March...