ONEVISION DCE MANAGER FOR HP...

ONEVISIONDCE MANAGER FOR

HP OPENVIEWAPPLICATION GUIDE

Document No. 7800-A2-GB21-20

January 1997

DCE Manager for HP OpenView

A January 1997 7800-A2-GB21-20

OneVisionDCE Manager for HP OpenViewApplication Guide7800-A2-GB21-20

3rd Edition (January 1997)

Changes and enhancements to the product and to the information herein will be documented and issued as a new release.

Warranty, Sales, and Service Information

Contact your sales or service representative directly for any help needed. For additional information concerning warranty, sales,service, repair, installation, documentation, or training, use one of the following methods:

• Via the Internet: Visit the Paradyne World Wide Web site at http://www.paradyne.com

• Via Telephone: Call our automated call system to receive current information via fax or to speak with a company representative.

— Within the U.S.A., call 1-800-870-2221— International, call 727-530-2340

Trademarks

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

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

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

Printed on recycled paper

i7800-A2-GB21-20 January 1997

Table of Contents

Preface

Objectives and Reader Assumptions vii. . . . . . . . . . . . . . . . . . . . . . . . . . . How to Use This Manual viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Conventions ix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documents ix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference Documents x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1. Getting Started

Overview 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents of Package 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Information Base Files (MIBs) 1-5. . . . . . . . . . . . . . . . . . . . Installing the DCE Manager 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing the DCE Manager 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCE Manager Functions 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rear-Panel Display 1-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Help 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2. Discovering Devices

Overview 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering 3100 Series Devices 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering 6700 Series Proxied Devices 2-4. . . . . . . . . . . . . . . . . . . . . . . Notes on Using PPP 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trap Handling and Alarm Propagation 2-8. . . . . . . . . . . . . . . . . . . . . . . . . Dial-Backup Module Addressing 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Symbols 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3. Monitoring Health and Status

Overview 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Health and Status of 3100 Series Devices 3-1. . . . . . . . . . . . . . . Checking Health and Status of Proxied Devices 3-12. . . . . . . . . . . . . . . . . .


ii January 1997 7800-A2-GB21-20

4. Displaying and Setting Configuration

Overview 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying and Setting the 3100 Series Device Configuration 4-2. . . . . . . Displaying and Setting the NMS and Proxied Device Configuration4-10. .

5. Using Loopback Modes and Pattern Tests

Overview 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running Tests on 3100 Series Devices 5-1. . . . . . . . . . . . . . . . . . . . . . . . . Running Tests on Proxied Devices 5-6. . . . . . . . . . . . . . . . . . . . . . . . . . . .

6. Troubleshooting

Overview 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting 3100 Series Devices 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting a 6700 Series NMS or Proxy Devices 6-13. . . . . . . . . . . .

Appendices

A. Dialog MIB Values A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary

Index

Table of Contents

iii7800-A2-GB21-20 January 1997

List of Figures

Figure Page

1-1 DCE Manager Network Environment 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 MIB Tree 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 HP OpenView Menu Selections Specific to the DCE Manager 1-10. . . . . . . . . . . . . . 1-4 Functions Related to the Device 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Functions Related to a Device Interface 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 3164 Device Rear-Panel Display 1-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 3165 Device Rear-Panel Display 1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 3151 and 3161 Rear-Panel Display 1-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 3151 Rear-Panel Display 1-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Object Hierarchy 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 DCE Manager 3100 Series Device Symbols 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 DCE Manager 6700 Series Object Symbols 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Network T1 Performance Statistics Graph 3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Channel Configuration Dialog 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 Front Panel Emulator 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Refresh Dialog Box 4-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Use of LLB and Pattern Test 6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Line Loopback (LLB) 6-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Payload Loopback (PLB) 6-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 DLB Loopback 6-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 RLB Loopback 6-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Data Channel Loopback (DCLB) – V.54, Loop 2 6-9. . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Data Terminal Loopback (DTLB) – V.54, Loop 3 6-9. . . . . . . . . . . . . . . . . . . . . . . . . 6-8 Pattern Test – Testing One End of a Circuit 6-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Pattern Test – Testing Both Ends of a Circuit 6-11. . . . . . . . . . . . . . . . . . . . . . . . . . . .


iv January 1997 7800-A2-GB21-20

List of Tables

Table Page

1-1 Summary of Functions for Managing 3100 Series Devices 1-13. . . . . . . . . . . . . . . . . 1-2 Summary of Functions for Managing 6700 Series NMS and

6700 Series Proxied Devices 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 HP OpenView Status Colors Supported by 3100 Series Devices 3-2. . . . . . . . . . . . . 3-2 Device Summary Health and Status Dialog 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Network T1 Health and Status 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 DTE T1 Health and Status Dialog 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 Data Ports 1–4 Health and Status Dialog 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 Network T1 Performance Statistics Dialog 3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 HP OpenView Status Colors Supported by Proxied Devices 3-12. . . . . . . . . . . . . . . . 3-8 Proxied Device Health & Status 3-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 Proxied Device Circuit Quality Validity 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 Proxied Device Circuit Quality Table 3-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 Proxied Device EIA Status Display 3-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 Proxied Device External Leads Display 3-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 3100 Series Device Identity Dialog 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 3100 Series Device Channel Configuration 4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Copy Device Configuration Area Dialog 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 Network T1 Configuration Dialog 4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 DTE T1 Configuration 4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Data Ports 1–4 Configuration Dialog 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 NMS Administration Display 4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 NMS System Features Display 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Elements of the Front Panel Emulator 4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 Identity Display 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 Proxied Device Call Directory Display 4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 Proxied Device Commands 4-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 Command List 4-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 6700 Proxy Device Admin Display 4-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 Network T1 Loopback Modes and Pattern Tests 5-3. . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 DTE T1 Loopback Modes 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Data Ports 1–4 Loopback Modes and Pattern Tests 5-5. . . . . . . . . . . . . . . . . . . . . . . . 5-4 Proxied Device Loopback Modes and Pattern Tests 5-6. . . . . . . . . . . . . . . . . . . . . . . 5-5 Supported Loopback Modes and Tests 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Proxied Device Test Display 5-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 3100 Series Device Troubleshooting Table 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 3100 Series Device Traps 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Troubleshooting 3100 Series Device Traps 6-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Proxied Device Troubleshooting Table 6-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Proxied Device Primary Alert Traps 6-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Proxied Device System Security Event Traps 6-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Proxied Device Primary Alert Clear Notifications 6-18. . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

v7800-A2-GB21-20 January 1997

Table Page

6-8 Troubleshooting Proxied Device Traps 6-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 3100 Series Device Identity A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Network T1 Health and Status Dialog A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 DTE T1 Health and Status Dialog A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 Data Ports 1–4 Health and Status Dialog A-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Network T1 Performance Statistics Dialog A-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6 3100 Series Device Channel Configuration A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7 3100 Series Device User Configuration A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8 Network T1 Configuration A-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9 DTE T1 Configuration A-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10 Data Ports 1–4 Configuration A-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11 Network T1 Loopback Modes and Pattern Tests A-9. . . . . . . . . . . . . . . . . . . . . . . . . . A-12 DTE T1 Loopback Modes A-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13 Data Ports 1–4 Loopback Modes and Pattern Tests A-10. . . . . . . . . . . . . . . . . . . . . . . . A-14 Device Health and Status Display A-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15 Device Call Directory Display A-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16 Device Identity Display A-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17 System Features Display A-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18 NMS Administration Display A-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-19 Device Administration Display A-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-20 Proxy Device Circuit Quality Dialog (read-only) A-15. . . . . . . . . . . . . . . . . . . . . . . . . A-21 Device Commands A-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-22 Proxy Device EIA Status Dialog (read-only) A-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23 Proxy Device External Leads Dialog (read-only) A-18. . . . . . . . . . . . . . . . . . . . . . . . . A-24 Loopback Modes and Pattern Tests A-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-25 Device Test Display A-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vii7800-A2-GB21-20 January 1997

Preface

Objectives and Reader AssumptionsThe OneVision� DCE Manager for HP OpenView� Release 2.1 is a collection of tools that runswithin the Hewlett-Packard�OpenView network management system. The DCE Managerenhances your ability to manage the ACCULINK� 3100 Series devices and, through theCOMSPHERE� 6700 Series Network Management System SNMP Proxy Agent Feature, theCOMSPHERE 3550, 3600, 3800, and 3900 Series devices. This manual describes how to installand use the DCE Manager. It assumes that you are familiar with

• Features and functions of 3100 Series CSUs and DSU/CSUs, specifically as defined inManagement Information Base (MIB) II, DS1/E1 MIB, RS-232-Like MIB, ATTDCE MIB,and Generic-Interface Extension MIB

• Features and functions of the 3550 Series DSUs, 3600 Series DSUs, 3800 Series modems,and 3900 Series modems, specifically as defined in the COMSPHERE 6700 Series NMSand Device MIBs

• Features and functions of Hewlett-Packard (HP) OpenView

• Administration of HP workstations or Sun� workstations, including networking andPoint-to-Point Protocol (PPP) support

The documents listed at the end of this section will help you become familiar with these topics.


viii January 1997 7800-A2-GB21-20

How to Use This ManualThe manual has the following sections:

• Chapter 1, Getting Started, describes the

— product’s features

— hardware and software system requirements

— contents of the product package

— MIBs relevant to the DCE Manager

— installation and deinstallation of the product

— functions of the DCE Manager

— 3100 Series device rear-panel display

— help facilities

• Chapter 2, Discovering Devices, describes how the DCE Manager works with HPOpenView to discover 3100 Series and proxied devices.

• Chapter 3, Monitoring Health and Status, describes how to use the DCE Manager todetermine the identity of devices and evaluate their performance.

• Chapter 4, Displaying and Setting Configuration, describes how to use the DCE Managerto check and set selected MIB variables of 3100 Series and proxied devices.

• Chapter 5, Using Loopback Modes and Pattern Tests, describes how to set loopbackmodes and send/monitor pattern tests to check the integrity and performance of devices.

• Chapter 6, Troubleshooting, demonstrates how to use loopback modes and pattern tests toisolate a problem to a device or the line. The chapter also lists the traps that the devicesgenerate.

• Appendix A, Dialog MIB Values, identifies the MIB values used to generate the values thatappear in the DCE Manager’s displays.

You should first read Chapter 1 in order to install the product and become familiar with itscapabilities. Following that, read Chapter 2 to understand the issues related to discovery. You canthen choose the chapters relevant to your needs.

Preface

ix7800-A2-GB21-20 January 1997

Documentation ConventionsThe following conventions are used throughout this document.

Typeface

This typeface indicates an HP OpenView Windows menu selection. The arrow (–>) indicates asub-menu item, as in Monitor–>OneVision Device Mgmt: DCE Manager–>EIA Status.

This typeface indicates a command that you enter via the keyboard.

This typeface indicates a filename or pathname. It also indicates a field name or value in a display.

Variable Information in Tables

Variable information appears within angle brackets, as in <model number>.

Keyboard Instructions

Keyboard entry is indicated as follows:

TYPE: followed by the information to be typed in

PRESS: followed by a key to be pressed – usually the Enter key

Related DocumentsContact your sales representative for additional product documentation.

3150-A2-GB21 ACCULINK 315x Channel Service Unit Operator’s Guide

3160-A2-GB21 ACCULINK 316x Data Service Unit/Channel Service Unit Operator’sGuide

3550-A2-GB20 COMSPHERE 3550 Series Data Service Units, Models 3550 and 3551,User’s Guide

3610-A2-GB91 COMSPHERE 3600 Series Data Service Units, Models 3610 and 3611,Operator’s Guide

3810-A2-GB91 COMSPHERE 3800 Series Modems, Models 3810, 3811, and 3820,User’s Guide

3910-A2-GN32 COMSPHERE 3900 Series Modems, Models 3910 and 3911,Point-to-Point/Multipoint, Installation and Operation Manual

6700-A2-GB20 COMSPHERE 6700 Series Network Management System SNMP ProxyAgent Feature User’s Guide

6700-A2-GB22 COMSPHERE 6700 Series Network Management System NetworkConfiguration Guide


x January 1997 7800-A2-GB21-20

6700-A2-GY31 COMSPHERE 6700 Series Network Management System User’s Guide

HP Installation Guide for HP OpenView NNM, HP OpenView SNMP Management Platform, HPOpenView Distributed Management Platforms HP OpenView Installation Guide

HP OpenView Network Node Manager User’s Guide

HP OpenView Network Node Manager Administrator’s Reference

HP OpenView Windows User’s Guide

Morning Star PPP User’s Guide

Reference DocumentsBaker, F., Watt, J., Definitions of Managed Objects for the DS1 and E1 Interface Types. RFC 1406, January 1993

McCloghrie, K., Extension to the Generic-Interface MIB. RFC 1229, May 1991

McCloghrie, K., Rose, M.T., Management Information Base for Network Management ofTCP/IP-based Internets. RFC 1156, March 1991

Simpson, W., The Point-to-Point Protocol (PPP). RFC 1331, May 1992

Stewart, B., Definitions of Managed Objects for RS-232-like Hardware Devices. RFC 1317, April 1992.

1-17800-A2-GB21-20 January 1997

Getting StartedOverview 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Features 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hardware Requirements 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Requirements 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents of Package 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management Information Base Files (MIBs) 1-5. . . . . . . . . . . . . . . . . . . . . . . . . Installing the DCE Manager 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HP Systems 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun Systems 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Removing the DCE Manager 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DCE Manager Functions 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Functions Available through the Menu Bar 1-10. . . . . . . . . . . . . . . . . . . . . . . . Functions Available through the Right-hand Mouse Button 1-11. . . . . . . . . . . Functions Available through the UNIX Command Line 1-12. . . . . . . . . . . . . . Summary of Functions 1-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rear-Panel Display 1-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rear-Panel Status Colors 1-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Status 1-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Redoing Layout 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing Interface Labels 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Help 1-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OverviewThe OneVision DCE Manager for HP OpenView helps you manage ACCULINK 3100 Seriesdevices and the COMSPHERE 3550, 3600, 3800, and 3900 Series devices, as well as theCOMSPHERE 6700 Series Network Management System (NMS). The DCE Manager runs inconjunction with the HP OpenView Simple Network Management Protocol (SNMP) ManagementPlatform and the HP OpenView Network Node Manager, both of which use HP OpenViewWindows as a graphical interface.

The ACCULINK 3100 Series devices include the 316x Data Service Unit (DSU)/Channel ServiceUnit (CSU) and the 315x CSU. These devices support SNMP directly.

The 355x DSUs, 36xx DSUs, 38xx modems, 39xx modems support SNMP indirectly through theCOMSPHERE 6700 Series Network Management System SNMP Proxy Agent Feature softwareproduct as illustrated in Figure 1-1. These devices are referred to in this document as “proxieddevices.”

Note in Figure 1-1 that you can use the DCE Manager to manage the 6700 Series NMS as well asthe devices.

1


1-2 January 1997 7800-A2-GB21-20

SNMP Manager Running HP OpenView

LAN - TCP/IP

495-14590-01

Ethernet, Token Ring, or FDDI

SLIP or PPP

Asynchronous Serial

COMSPHERE 6700 Series NMSRunning 6700 Series NMSSNMP Proxy Agent Feature

COMSPHERE 3550 Series DSUsCOMSPHERE 3600 Series DSUsCOMSPHERE 3800 Series ModemsCOMSPHERE 3900 Series Modems

COMSPHERE 6700 Series NMSRunning 6700 Series NMSSNMP Proxy Agent Feature

COMSPHERE 3550 Series DSUsCOMSPHERE 3600 Series DSUsCOMSPHERE 3800 Series ModemsCOMSPHERE 3900 Series Modems

COMSPHERE 3610

Paradyne

COMSPHERE 3610

Paradyne

COMSPHERE 3610

Paradyne

Modem

Modem

COMSPHERE 3610

Paradyne

COMSPHERE 3610

Paradyne

COMSPHERE 3610

Paradyne

COMSPHERE 3610

Paradyne

COMSPHERE 3610

Paradyne

SLIP or PPP

Paradyne

Paradyne

ACCULINK 3100Series DSU/CSUs

ACCULINK 3100Series DSU/CSUs

Modem

SLIP or PPP

SLIP or PPP

3000Series Carrier

Figure 1-1. DCE Manager Network Environment

Features

The DCE Manager enhances your ability to manage the 3100 Series devices by providing thesefeatures:

• Dialogs that present MIB-based health and status and configuration information ineasy-to-read formats

• Dialogs that enable you to easily set selected MIB variables

• Test menus that enable you to conveniently initiate tests, the results of which you can use totroubleshoot devices

• Performance monitor that graphically displays information about the operation of theNetwork T1 interface

• Rear-panel display that enables you to determine the health and status of a device interfaceas well as check configuration parameters

Getting Started

1-37800-A2-GB21-20 January 1997

The DCE Manager enhances your ability to manage the 3550, 3600, 3800, and 3900 Series proxieddevices by providing these features:

• Dialogs that present MIB-based health and status and configuration information ineasy-to-read formats

• Dialogs that enable you easily set selected MIB variables

• Access to selected dialogs from the UNIX command line

• Test menus that enable you to conveniently initiate tests, the results of which you can use totroubleshoot devices

• Command menu that enables you to send these commands to a device:

— dial number

— disconnect call

— disconnect service

— set busy state

— clear busy state

— switch to dial backup

— switch to dial standby

— switch to leased line

— switch to service line

— enable device

— disable device

— send message to front panel

— software device reset

— hardware device reset

• Front-panel emulator that enables you to manage a 3800 or 3900 Series device as if youwere using its front panel

The DCE Manager enhances your ability to manage the 6700 Series NMS by providing thesefeatures:

• Dialog that displays MIB-based system features information

• Dialog that displays MIB-based administration information and enables you to set selectedMIB variables


1-4 January 1997 7800-A2-GB21-20

System RequirementsBecause the DCE Manager runs under HP OpenView on HP and Sun systems, the hardware andsoftware requirements are basically those of HP OpenView. However, there are some additionalthings you need to consider, as described in the following sections. Refer to the individual devicemanuals for information on connecting devices to the network.

Hardware Requirements

The DCE Manager requires 35 Mb of hard disk space.

Software Requirements

The DCE Manager requires the following software:

• HP OpenView SNMP Management Platform, Release 3.31

• HP OpenView Network Node Manager, Release 3.31

• COMSPHERE 6700 Network Management System SNMP Proxy Agent Feature,Release 1.0 or higher (needed only if you want to manage 3550, 3600, 3800, or 3900 Seriesdevices)

• Point-to-Point Protocol (PPP) communication software (e.g., Morning Star� PPP,Release 1.4) if you want to manage a 3100 Series device or connect to a 6700 Series NMSvia a dial-up or direct serial connection

Contents of PackageThe product package contains these components:

• OneVision DCE Manager for HP OpenView Release 2.1 on multiple 3.5″ disks for Sun systems or one 4 mm Digital Data Storage (DDS) tape for HP systems.

• OneVision DCE Manager for HP OpenView Application Guide.

• Software license agreement. The software license is an important document that contains theproduct serial number needed for the operation of the DCE Manager (as described in thenext section). This serial number is requested when you place a call for support. Pleaseretain this license for future reference.

• Release notes (copied to your hard disk during installation as described in the next section).

Getting Started

1-57800-A2-GB21-20 January 1997

Management Information Base Files (MIBs)The installation process copies to your hard disk all the MIBs needed for management of thesupported devices. These MIBs are available when you start HP OpenView. You do not need tomanually load them from within HP OpenView. These MIBs are loaded:

• MIB II (RFC 1213)

• Generic-Interface Extension MIB (RFC 1229)

• RS-232-Like MIB (RFC 1317)

• DS1/E1 MIB (RFC 1406)

• NMS6700 MIB

• ATTDCE MIB

In Figure 1-2, the dashed boxes show the branches of the MIB tree that are relevant to the DCEManager.

iso (1)

org (3)

dod (6)

internet (1)

mgmt (2)

mib-2 (1)

experimental (3)private (4)

enterprises (1)

att-2 (74)

att-mgmt (2)att-products (1)

paradyneNMS-products (13)

nms-6700-products (2)

paradyneNMS (23)

nms-6700 (5)

attp-frontPanel (1)devOid (2) nms (1) dev (2)

494-14591-01

attp-callDir (3)

paradyne (24)

attp-common (2)

Enterprise Traps Enterprise MIBS

netmanage (233)generic-interface (12)

transmission (10)

ds1 (18) rs232 (33)

31xx-traps (2)

paradyne-products (14)

attp-devConfigArea (7)

Figure 1-2. MIB Tree


1-6 January 1997 7800-A2-GB21-20

Installing the DCE ManagerTo copy the product files from the distribution media to your management system’s hard disk,follow the procedures described in the following sections.

HP Systems

To install the DCE Manager on HP systems, follow the steps below. (Refer to your HP OpenViewdocumentation for detailed descriptions of HP OpenView commands.) To abort the installationprocess, use the UNIX interrupt key (e.g., Control-D or Delete).

1. Log in as root.

2. Ensure that the HP OpenView products SNMP Management Platform (SNMPRUN) andNetwork Node Manager (NNMGR) are installed. You can check that they are installed byusing the HP OpenView command ovverify .

3. Terminate any HP OpenView Windows (ovw) processes using the command appropriate tothe process. You can check that no ovw processes are running by using the followingUNIX� command:

ps –el | grep ovw

4. Ensure that files related to previous versions of the product are removed from your harddisk. You can check for existing files by using the HP OpenView command ovverify .Use this command if any files are found:

ovremove -p CNMP-3100

If you have the software version release 2.0, refer to the section titled Removing the DCEManager later in this chapter for file removal.

5. Ensure that there is at least 35 Mb available in the /usr/OV directory on your hard disk.You can check for available space by using the following UNIX command:

bdf /usr/OV

If you do not have 35 Mb available, refer to the HP OpenView Installation Guide forinstructions on acquiring the needed space. After acquiring the space, continue theinstallation process at Step 6.

6. TYPE: cd /usr/OV/bin

7. Insert the DCE Manager product distribution tape.

8. TYPE: ovinstall –p ATTDCE –– –s /dev/rmt/0m

9. If you want to manage 3100 Series devices:

TYPE: ovinstall –p ATT3100 –– –s /dev/rmt/0m

10. If you want to manage devices through the COMSPHERE 6700 Series NMS SNMP ProxyAgent Feature (i.e., 3550, 3600, 3800, and 3900 Series devices):

TYPE: ovinstall –p ATT6700 –– –s /dev/rmt/0m

Getting Started

1-77800-A2-GB21-20 January 1997

11. To register the media serial number of the DCE Manager:

TYPE: attDCESerial

12. When prompted:

TYPE: <the serial number listed on your software license agreement>

The product serial number is needed for operation of the DCE Manager. This serial numberis requested when you place a call for support.

PRESS:Return

(After installation, you can use the Help–>Index–>Applications menu selection to displaythe serial number.)

13. Eject the tape and store it in a safe place.

14. Check /tmp/update.log for errors. Consult HP documentation if any errors are found.

15. Read the following release notes files in /usr/OV/ReleaseNotes:

attDCE/attDCEr2.rn

att3100/att3100r2.rn (if you installed ATT3100)


16. Exit from root.

Sun Systems

To install the DCE Manager on Sun systems, follow the steps below. (Refer to your HP OpenViewdocumentation for detailed descriptions of HP OpenView commands.) To abort the installationprocess, use the UNIX interrupt key (e.g., Control-D or Delete).

1. Log in as root.

2. Ensure that the HP OpenView products SNMP Management Platform (SNMPRUN) andNetwork Node Manager (NNMGR) are installed. You can check that they are installed byusing the HP OpenView command ovverify .

3. Ensure that files related to previous versions of the product are removed from your harddisk. You can check for existing files by using the HP OpenView command ovverify .Use this command if any files are found:

ovremove -p CNMP-3100

If you have the software version release 2.0, refer to the section titled Removing the DCEManager later in this chapter for file removal.

4. Terminate any HP OpenView Windows (ovw) processes using the command appropriate tothe process. You can check that no ovw processes are running by using the followingUNIX command:

ps –ax | grep ovw


1-8 January 1997 7800-A2-GB21-20

5. Ensure that there is at least 35 Mb available in the /usr/OV directory on your hard disk.You can check for available space by using the following UNIX command:

df /usr/OV

If you do not have 35 Mb available, refer to the HP OpenView Installation Guide forinstructions on acquiring the needed space. After acquiring the space, continue theinstallation process at Step 6.

6. Create a directory in a path other than /usr with at least 35 Mb available. (This is atemporary directory that is only needed for the installation process.) For example:

TYPE: mkdir /tmp/tempdir

7. TYPE: cd < path of directory created in Step 6>

8. Insert the first DCE Manager product diskette.

9. TYPE: bar xvf /dev/rfd0

10. Insert the remaining diskettes as prompted.

11. When the bar command is completed:

TYPE: uncompress attDCE *


13. TYPE: ovinstall –p ATTDCE –– –d < path of directory created inStep 6>/attDCE

14. If you want to manage 3100 Series devices:

TYPE: ovinstall –p ATT3100 –– –d < path of directory created inStep 6>/attDCE

15. If you want to manage devices through the COMSPHERE 6700 Series NMS SNMP ProxyAgent Feature (i.e., 3550, 3600, 3800, and 3900 Series devices):

TYPE: ovinstall –p ATT6700 –– –d < path of directory created inStep 6>/attDCE

16. To register the media serial number of the DCE Manager:

TYPE: attDCESerial

17. When prompted:

TYPE: <the serial number listed on your software license agreement>

The product serial number is needed for operation of the DCE Manager. This serial numberis requested when you place a call for support.

PRESS:Return

(After installation, you can use the Help–>Index–>Applications menu selection to displaythe serial number.)

Getting Started

1-97800-A2-GB21-20 January 1997

18. TYPE: rm -r <directory created in Step 6>

19. Eject the final diskette.

20. Store the diskettes in a safe place.

21. Check /tmp/update.log for errors. Consult HP documentation if any errors are found.

22. Read the following release notes files in /usr/OV/ReleaseNotes:

attDCE/attDCEr2.rn



23. Exit from root.

Removing the DCE ManagerIf you need to remove the DCE Manager product files from your hard disk for any reason, followthese steps:

1. Log in as root.


3. Execute the following commands in the specified order:

TYPE: ovremove -p ATT3100

TYPE: ovremove -p ATT6700

TYPE: ovremove -p ATTDCE

4. Exit from root.

A running report of the process appears, concluding with a message that informs you when theprocess is complete.

DCE Manager FunctionsUse these methods to access the functions of the DCE Manager:

• Menu bar of HP OpenView – enables you to access all of the functions related to the proxieddevices, as well as the test, performance, and rear-panel display functions related to the 3100 Series devices

• Right-hand mouse button – enables you to access functions related to the management of3100 Series devices

• UNIX command line – enables you to access selected functions related to the proxieddevices

The sections that follow discuss these methods in detail.


1-10 January 1997 7800-A2-GB21-20

Functions Available through the Menu Bar

Figure 1-3 shows the HP OpenView Windows menu selections specific to the DCE Manager.

Monitor

OneVision Device Mgmt

Rear Panel (8)Open

Update Status

Redo Layout

Performance Statistics Graph (9)

Circuit Quality Table (16)

EIA Status (17)

External Leads (18)

DCE Manager

OneVision Device Mgmt

Device Commands (21)

Dial Number

Disconnect Call

Set Busy

Identity (15)

Call Directory (20)

Admin (12 or 14)

Discover Proxied NMS (11)

Front Panel: Open (22)

DCE Manager

System Features (13)

Clear Busy

Switch to

Dial Standby

Leased Line

Service Line

Enable Device

Disable Device

Software Device Reset

Hardware Device Reset

Send Message

OneVision Device MgmtDCE Manager

Remote Loopback (10 or 23)

Loopback (10 or 23)

Patterns (10 or 23)

Start Digital Loopback

Start Digital Loopback w/ BERT

Send L LB Up Code

Send LLB Down Code

Send V.54 Up Code

Send V.54 Down Code

Send FT1 Up Code

Send FT1 Down Code

Abort Loopback

Start L ine LoopbackStart P ayload Loopback

Start R epeater Loopback

Start Data C hannel Loopback

Start Data T erminal Loopback

Abort M onitor

Abort S end

Monitor 51 1 Pattern

Monitor QR SS Pattern

Send 1-in-8 Pattern

Send 511 Pattern

Send QRSS Pattern

Start Digital Test

Start End-to-End Test

Start Loopback

Start Digital Loopback

Start DTE Loopback

Start Loopback w/ BERT

Send BERT

Self Test (25)

Health and Status (19)

Dial Backup

Disconnect Service

Abort Front Panel Test (24)

Administer D iagnose

Legend:

Start D TE Loopback

� Items in bold apply to 3100 Series devices. Items not in bold apply to the 6700 Series proxied NMS and devices.

� Numbers next to the menu items reference a description of the selections in Table 1-1 or Table 1-2.

� Underlined characters show the menu mnemonics. Refer to the HP OpenView User’s Guide for information on their use.

Note that the tests related to 3100 Series devices under the Diagnosemenu item require that you open the rear-panel display and select an interface symbol.

Figure 1-3. HP OpenView Menu Selections Specific to the DCE Manager

Getting Started

1-117800-A2-GB21-20 January 1997

Functions Available through the Right-Hand Mouse Button

To access functions related to a 3100 Series device as a whole:

1. Position the mouse cursor over a device symbol as it appears on an HP OpenViewWindows submap.

2. Press the right-hand mouse button and select Describe/Modify Object.

Figure 1-4 shows the functions available to you. (Note that the Channel Configuration function isonly applicable to 316x devices.) The Copy Device Configuration Area is only applicable to 316xdevices with Release 2.8 firmware. The numbers next to the menu selections reference descriptionsof the selections in Table 1-1.

Object Attributes

Health & Status (2)

Identity (1)

Channel Configuration (3)

Copy Device Configuration Area (4)

Figure 1-4. Functions Related to the Device

To access functions related to a 3100 Series device interface:

1. Select a device by clicking on a device symbol as it appears on an HP OpenView Windowssubmap.

2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager: RearPanel–>Open to display the rear panel.

3. Position the mouse cursor over desired interface symbol: Network T1, DTE T1, or DataPorts 1–4.



1-12 January 1997 7800-A2-GB21-20

Figure 1-5 shows the functions available to you. (Note that the Performance Statistics function isonly available for the Network T1 interface.) The numbers next to the menu selections referencedescriptions of the selections in Table 1-1.

Object Attributes

Configuration (6)

Health & Status (5)

Performance Statistics (7)

Figure 1-5. Functions Related to a Device Interface

Functions Available through the UNIX Command Line

You can use the UNIX command line to access the displays related to the following 6700 SeriesNMS and proxied device functions:

• NMS Administration (12)

• Health and Status (19)

• Call Directory (20)

• Device Commands (21)

• Front Panel Emulator (22)

• Device Tests (23, 24, 25)

The numbers reference descriptions of the functions in Table 1-2. These descriptions identifywhere you can find the syntax for the commands.

You can also access these functions through the menu bar. See Figure 1-3.

Getting Started

1-137800-A2-GB21-20 January 1997

Summary of Functions

Table 1-1 summarizes the functions used to manage the 3100 Series devices. Table 1-2 summarizesthe functions related to the 6700 Series NMS as well as the 3550, 3600, 3800, and 3900 Seriesproxied devices. Refer to the individual chapters for detailed explanations of the functions. (SeeDevice Symbols in Chapter 2 for a depiction of the device symbols referenced in Table 1-1 andTable 1-2.)

The numbers in the first column reference the menu selections shown in Figures 1-3. 1-4, and 1-5.

Table 1-1(1 of 3)

Summary of Functions for Managing 3100 Series Devices

RefNo. Function Specifics How to Execute the Function

1 Display device IdentityDialog and set selectedMIB values

Reports general information about adevice (model number, up time, address,etc.) and enables you to set Contact,Name, and Location MIB values. Someinformation is read-only; other informationis read-write.

See Identity Dialog in Chapter 4.

1. Position the mouse cursor over adevice symbol as it appears on an HPOpenView Windows submap.

2. Press the right-hand mouse buttonand select Describe/Modify Object.

3. Double-click Identity (att3100) in theObject Attribute list box.

2 Display device Healthand Status Dialog

Reports whether the Network T1, DTET1, and Data Ports 1–4 interfaces are up,down, in test, or disabled.

Displays whether the COM and MODEMports are up or down.

See Device Summary Health and StatusDialog in Chapter 3.

1. Access the Describe/Modify Objectselection window as described inReference Number 1, Steps 1–2.

2. Double-click Health & Status(att3100) in the Object Attribute listbox.

3 Display device ChannelConfiguration Dialog

Reports the channel assignments of theNetwork T1 and DTE T1 interfaces.

Note that the Channel ConfigurationDialog is only available for 316x devices.

See Displaying Channel ConfigurationDialog in Chapter 4.


2. Double-click Channel Configuration inthe Object Attribute list box.

4 Copy DeviceConfiguration Area Dialog

Displays one of eleven different deviceconfiguration combinations that can beset by the user.

See Copy Device Configuration AreaDialog in Chapter 4.


2. Double-click Copy DeviceConfiguration Area in the ObjectAttribute list box.


1-14 January 1997 7800-A2-GB21-20

Table 1-1(2 of 3)


RefNo. How to Execute the FunctionSpecificsFunction

5 Display interface Healthand Status Dialog for aselected interface:Network T1, DTE T1, orData Ports 1–4

Reports test information (including testsstatus, results, and codes) and generaloperational status information.

See Network T1 Dialog, DTE T1 Dialog,or Data Ports Dialog in Chapter 3.

1. Display the rear panel as described inReference Number 4.

2. Position the mouse cursor over adesired interface symbol.

3. Press the right-hand mouse buttonand select Describe/Modify Object.

4. Double-click Health & Status(att3100) in the Object Attribute listbox.

6 Display interfaceConfiguration Dialog for aselected interface:Network T1, DTE T1, orData Ports 1–4

Reports configuration information,including interface type, speed, clocksource, etc. Some information isread-only; other information is read-write.

See Network T1 Dialog, DTE T1 Dialog,or Data Ports Dialog in Chapter 4.


2. Double-click Configuration (att3100)in the Object Attribute list box.

7 Display tabularPerformance StatisticsDialog for the Network T1interface

Reports performance statistics (such asSeverely Errored Seconds and BurstyErrored Seconds) related to the NetworkT1 interface.

See Displaying Network T1 PerformanceStatistics Table in Chapter 3.


2. Double-click Performance Statistics(att3100) in the Object Attribute listbox.

8 Display Rear Panel Displays a graphical representation of a3100 Series device rear panel.

See Rear-Panel Display in this chapter.

1. Select a device by clicking on adevice symbol as it appears on an HPOpenView Windows submap.

2. Use the menu selection Monitor–>OneVision Device Mgmt: DCEManager–>Rear Panel–>Open todisplay the rear panel.

Getting Started

1-157800-A2-GB21-20 January 1997

Table 1-1(3 of 3)



9 Display PerformanceStatistics Graph for theNetwork T1 interface

Graphs performance statistics (such asSeverely Errored Seconds andUnavailable Seconds) related to theNetwork T1 interface.

See Displaying Network T1 PerformanceStatistics Graph in Chapter 3.

1. Display the rear panel as described inReference Number 4.

2. Select the Network T1 interface byclicking on the interface symbol.

3. Select Monitor–>OneVision DeviceMgmt: DCE Manager–> PerformanceStatistics Graph.

10 Set loopback modes andsend/monitor patterntests on a selectedinterface: Network T1,DTE T1, or Data Ports 1–4

Initiates a variety of device loopbackmodes and pattern tests.

See Network T1 Loopback Modes andPattern Tests, DTE T1, Loopback Modes,or Data Ports Loopback Modes andPattern Tests in Chapter 5.

1. Select a device by clicking on adevice symbol as it appears on an HPOpenView Windows submap.

2. Use the menu selection Monitor–>OneVision Device Mgmt: DCEManager: Rear Panel–>Open todisplay the rear panel.

3. Select the desired interface (NetworkT1, DTE T1, or Data Ports 1–4) byclicking on the interface symbol.

4. Select Diagnose–>OneVision DeviceMgmt: DCE Manager–> <pattern testor loopback mode>.


1-16 January 1997 7800-A2-GB21-20

Table 1-2(1 of 3)

Summary of Functions for Managing 6700 Series NMS and 6700 Series Proxied Devices

RefNo. Function Specifics How to Execute the Function

11 Discover Proxied NMS Causes HP OpenView to discoverproxied 6700 Series NMS.

See Manual Discovery andManagement of 6700 Series ProxyAgent Object in Chapter 2.

1. Select the NetManage by clicking on itssymbol as it appears on an HP OpenViewWindows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCEManager–>Discover Proxied NMS.

12 Display NMSadministration informationabout the 6700 SeriesNMS

Reports configuration informationsuch as NMS Name, Location,Read Community Name, and WriteCommunity Name. Someinformation is read-only; otherinformation is read-write.

See NMS Administration Display inChapter 4.

1. Select the 6700 Series NMS SNMP ProxyAgent by clicking on its symbol as it appearson an HP OpenView Windows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Admin.

This function is also accessible through the UNIXcommand line as explained in NMSAdministration Display in Chapter 4.

13 Display NMS systemfeatures informationabout the 6700 SeriesNMS

Reports configuration informationrelated to features installed on theNMS.

See NMS System Features Displayin Chapter 4.

1. Select the 6700 Series NMS SNMP ProxyAgent symbol as it appears on an HPOpenView Windows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>System Features.

14 Display deviceadministration information

Reports configuration informationsuch as Device Name, DeviceAddress, and Model Type.

See Device Administration Displayin Chapter 4.

1. Select a device by clicking on a devicesymbol as it appears on an HP OpenViewWindows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Admin.

15 Display device identityinformation

Reports configuration informationsuch as Model, Line Speed, andSerial Number.

See Identity Display in Chapter 4.


2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Identity.

16 Display device circuitquality information in atabular format

Reports health and statusinformation about the circuit suchas Receive Level, Signal to Noise,and Gain Hits.

See Circuit Quality Table inChapter 3.


2. Use the menu selection Monitor–>OneVisionDevice Mgmt: DCE Manager–>Circuit QualityTable.

17 Display device EIA statusinformation

Reports the state of the EIA linessuch as DTR, TD, and RD.

See EIA Status Display in Chapter 3.


2. Use the menu selection Monitor–>OneVisionDevice Mgmt: DCE Manager–>EIA Status.

Getting Started

1-177800-A2-GB21-20 January 1997

Table 1-2(2 of 3)



18 Display device externalleads information

Reports the state of the externalleads Pins 12, 13, 19, and 23.

See External Leads Display inChapter 3.


2. Use the menu selection Monitor–>OneVisionDevice Mgmt: DCE Manager–>ExternalLeads.

19 Display device health andstatus

Reports health and statusinformation such as Connect Time,Alerts, and State.

See Health and Status Display inChapter 3.


2. Use the menu selection Monitor–>OneVisionDevice Mgmt: DCE Manager–>Health andStatus.

This function is also accessible through the UNIXcommand line as explained in Health and StatusDisplay in Chapter 3.

20 Display call directoryinformation of a device

Reports configuration informationrelated to a device’s call directory.Some information is read-only;other information is read-write.

See Call Directory Display inChapter 4.


2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Call Directory.

This function is also accessible through the UNIXcommand line as explained in Call DirectoryDisplay in Chapter 4.

21 Issue a command to adevice

Enables you to send a command toa device such as Dial, DisconnectCall, and Switch to Leased.

See Command Menu in Chapter 4.


2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Device Commands–> < list of commands>.

This function is also accessible through the UNIXcommand line as explained in Command Menuin Chapter 4.

22 Manage a device usingthe front-panel emulator

Enables you to monitor andconfigure a device as if you wereusing the front panel of the device

See Front Panel Emulator inChapter 4.


2. Select Administer–>OneVision Device Mgmt:DCE Manager–>Front Panel: Open.


1-18 January 1997 7800-A2-GB21-20

Table 1-2(3 of 3)



23 Set loopback modes andsend/monitor patterntests for a device

Initiates a variety of deviceloopback modes and pattern tests.

See Running Tests on ProxiedDevices in Chapter 5.


2. Select Diagnose–>OneVision Device Mgmt:DCE Manager–> <pattern test or loopbackmode>.

This function is also accessible through the UNIXcommand line as explained in Running Tests onProxied Devices in Chapter 5.

24 Abort a test started froma device front panel

Abort tests started by a device’sfront panel.

See Aborting Tests Started fromthe Front Panel in Chapter 5.


2. Select Diagnose–>OneVision DeviceMgmt–>DCE Manager–>Abort Front PanelTest.

This function is also accessible through the UNIXcommand line as explained in Aborting TestsStarted from the Front Panel in Chapter 5.

25 Run a device self-test Initiates a device’s self-test.

See Running Tests on ProxiedDevices in Chapter 5.


2. Select Diagnose–>OneVision DeviceMgmt–>DCE Manager–>Self Test.

This function is also accessible through the UNIXcommand line as explained in Running Tests onProxied Devices in Chapter 5.

Getting Started

1-197800-A2-GB21-20 January 1997

Rear-Panel Display

NOTE

The rear-panel display is available for 3100 Series devices only.

For the DCE Manager to manage 3100 Series devices correctly, theHP OpenView map must be read-write.

The rear-panel display shown in Figure 1-6 represents the rear panel of a 3164 device (the other3100 Series devices, Figures 1-7, 1-8, and 1-9 have displays that match the appearance of their rearpanels). You display the rear panel by clicking on the 31xx device symbol to select it and thenselecting Monitor–>OneVision Device Mgmt: DCE Manager: Rear Panel–>Open from the HPOpenView menu. (See Figure 2-3 in Chapter 2 for a depiction of the device symbol.) From the rearpanel, you can display health and status, configuration, and performance dialogs for the variousinterfaces. You can also set loopback modes and run pattern tests on the interfaces.

POWER AUX PORT COM PORT MODEM DTE NETWORK

494-14437-01

NECCLASS 2

INPUT

AUX PORT OR COM PORT MUST NOT BE CONNECTED TO PSTN OR T1 NETWORKCAUTION:

CLOCK IN

PORT 3 PORT 4

PORT 2PORT 1

COM PORT MODEM NETWORK

PORT 3

PORT 1 PORT 2

PORT 4

DTE

Figure 1-6. 3164 Device Rear-Panel Display


1-20 January 1997 7800-A2-GB21-20

495-14674

PORT 1 COM PORT MODEM NETWORK

PORT 1 COM PORT MODEMPOWER NETWORK

CAUTION: COM PORT MUST NOT BE CONNECTED TO THE T1 NETWORK

NECCLASS 2

INPUT


495-14675

NETWORK T1

DTE

PORT2/COM PORT

PORT 1

COM PORT

NETWORK

DTE

PORT 1


NOTE

The 3161 rear panel display may be represented differently if thereare more than one 3161 devices configured in the carrier.

Getting Started

1-217800-A2-GB21-20 January 1997

495-14715

NETWORK T1

DTE

PORT2/COM PORT

PORT 1

COM PORT

NETWORK

DTE


NOTE

The 3151 rear panel display may be represented differently if thereare more than one 3151 devices configured in the carrier.

Rear-Panel Status Colors

In addition to displaying dialogs and running tests for the various interfaces, you can use therear-panel status colors to see at a glance the status of the various interfaces. Refer to Table 3-1.

Updating Status

There are situations when the rear panel does not reflect the current state of the interfaces. Forexample, when a test is initiated at a device’s front panel, the color of the symbol representing theinterface being tested does not change to salmon.

To force an update of the status of a 3100 Series device and its interfaces:

1. Click on the device or one of its rear-panel interface symbol.

2. Select Monitor–>OneVision Device Mgmt: DCE Manager–> Rear Panel–>Update Status.


1-22 January 1997 7800-A2-GB21-20

Redoing Layout

The rear-panel display is an HP OpenView submap and should not be altered (except for changinginterface labels). If you inadvertently alter the display: select Monitor–>OneVision Device Mgmt:DCE Manager: Rear Panel–>Redo Layout to reposition the interface symbols and backgroundgraphic.

Changing Interface Labels

To change the default labels provided with the various interfaces on the rear panel:

1. Select a device by clicking on a device symbol as it appears on an HP OpenView Windowssubmap.

2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager: RearPanel–>Open to display the rear panel.

3. Position the mouse cursor over the desired interface symbol: Network T1, DTE T1, DataPorts 1–4, COM, or Modem.

4. Press the right-hand mouse button and select Describe/Modify Symbol.

5. Type in the new label in the selected field.

6. Click OK.

HelpHelp information is available from the rear-panel display, front-panel display, and the status,configuration, and help displays. A Misc help button is available on selected displays related to theproxied devices. This button describes the features related to those displays.

The menu selections Help–>Index–>Tasks and Help–>Index–>Functions also provide informationabout the operation of the DCE Manager. The menu selection Help–>Index–>Tasks–>Troubleshooting 3100 Series Devices and Help–>Index–>Tasks–>Troubleshooting 6700 Series Proxied Devices provide the information contained in Chapter 6, Troubleshooting.

2-17800-A2-GB21-20 January 1997

Discovering DevicesOverview 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discovering 3100 Series Devices 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Network Configuration and 3100 Series Devices 2-2. . . . . . . . . . . . . . . . . . . 3100 Series Device Configuration 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Methods for Discovering and Managing 3100 Series Devices 2-2. . . . . . . . .

Discovering 6700 Series Proxied Devices 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . Network Configuration and 6700 Series Proxied Devices 2-4. . . . . . . . . . . . 6700 Series NMS Device Profiles 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6700 Series NMS SNMP Proxy Agent Configuration 2-4. . . . . . . . . . . . . . . 6700 Series Proxied Device Configuration 2-4. . . . . . . . . . . . . . . . . . . . . . . . Methods for Discovering and Managing 6700 Series Proxied Devices2-5. .

Notes on Using PPP 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trap Handling and Alarm Propagation 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dial-Backup Module Addressing 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Symbols 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OverviewThis chapter describes the steps you need to take to discover and manage the 3100 Series and 6700 Series proxied devices supported by the DCE Manager. The first part of the chapter discusses3100 Series devices; the second part discusses proxied devices.

Discovering 3100 Series DevicesFor the DCE Manager to discover and manage 3100 Series devices, do the following:

• Configure the network so that HP OpenView can communicate with a device over a director dial-up connection

• Configure your 3100 Series devices so that they can communicate with the managementsystem running HP OpenView

Also, you may need to issue HP OpenView commands so that discovery can take place.

The sections that follow discuss these step in detail.

NOTE

For the DCE Manager to manage 3100 Series devices correctly, theHP OpenView map must be read-write.

2


2-2 January 1997 7800-A2-GB21-20

Network Configuration and 3100 Series Devices

HP OpenView can establish a management link to 3100 Series devices over a LAN (via a router orLAN adapter), a leased line, or a dial-up connection. The DCE Manager provides no direct supportfor link establishment or disconnection. It is your responsibility to provide the hardware andsoftware that enables HP OpenView to communicate with the devices over the various link types.

Discovery and management of devices is straightforward over LAN and leased-line connections.Once you have the necessary hardware and software in place and configured, HP OpenViewdiscovers the devices and maintains a continual diagnostic link to them (see the sections thatfollow for information on configuration and discovery). Dial-up connections are more problematicbecause you may need to manually configure the PPP software with a large number of phonenumbers. Also, dialing a large number of devices may take a long time. Additionally, you shouldbe aware that if you only dial a device on an as-needed basis, the device appears on the map in anunknown state (color blue) during those times when no connection exists. See Notes on UsingPPP.

3100 Series Device Configuration

The DCE Manager does not enable you to configure a 3100 Series from scratch. Before HPOpenView can discover any 3100 Series device, an operator at the device site must do someconfiguration using the device’s front panel. The individual device manuals provide detailedinformation on device configuration.

The following is a list of some of the front panel configuration options that you need to consider:

• gen

• trap

• alarm

• user

Methods for Discovering and Managing 3100 Series Devices

The following sections discuss how 3100 Series devices are discovered over direct and dial-upconnections.

Discovery over a Direct Connection

A 3100 Series device is automatically discovered in two ways:

• As a result of the standard HP OpenView object discovery process

• As a result of a device sending a trap to the HP OpenView management system

If the IP address of a discovered device makes the device a member of a managed subnet (as aresult of a matching subnet mask), the device symbol appears on the submap in a managed state. Ifa device is not part of a managed subnet, its symbol appears in an unmanaged state (color tan).

Discovering Devices

2-37800-A2-GB21-20 January 1997

If you add a device to the network between HP OpenView’s discovery polling cycle, you can forcediscovery by issuing one of the following commands:

• From the UNIX command line,

TYPE: ping <IP address>

Where: IP address is the Internet address of the device

• From the HP OpenView menu, select Diagnose–>Network Connectivity–>Ping (supplyingthe Internet address of the device)

(To change the rate of discovery polling, use the menu selection Options–>Topology/StatusPolling: IP.)

After a device has been discovered and managed, the color of the device symbol changesdepending on the status of its device interfaces. If all the interfaces are green (operational), thedevice symbol remains green. If an interface is in an error state, the device symbol takes on thecolor of the interface with severest error state. If HP OpenView loses contact with an operationaldevice, the device symbol turns blue and the line connecting the symbol to the bus turns red. (Note,however, that the interface symbol colors on the rear-panel display always reflect the last knownstates.)

Discovery over a Dial-Up Connection

To discover a 3100 Series device over a dial-up connection:

1. Configure your PPP software to support a dial-up connection.

2. Establish a connection.

3. Issue one of following commands:



Where: IP address is the Internet address of the device

• From the HP OpenView menu, select Diagnose–>Network Connectivity–>Ping(supplying the Internet address of the device).

A 3100 Series device can also be discovered if the device sends a trap to the HP OpenViewmanagement system. Refer to your device manual for information on configuring a device to sendtraps to an NMS (HP OpenView).

You can configure a device so that it is automatically discovered on start-up by configuring it tosend a warmStart trap to the HP OpenView management system.

NOTE

Ensure that either the device or the PPP software is configured toterminate the connection after the trap has been sent (normally thedefault setting). This is an important point because you couldinadvertently incur large connection charges if the connectionremains up after the device has sent the trap information. See Noteson Using PPP.


2-4 January 1997 7800-A2-GB21-20

Discovering 6700 Series Proxied DevicesFor the DCE Manager to discover and manage a proxied device, do the following:

• Configure the network so that HP OpenView can communicate with the COMSPHERE6700 Series NMS SNMP Proxy Agent over a direct or dial-up connection

• Create device profiles on the 6700 Series NMS

• Configure the COMSPHERE 6700 Series NMS SNMP Proxy Agent

• Configure your devices so that they can communicate with the management system runningHP OpenView through the COMSPHERE 6700 Series NMS SNMP Proxy Agent

Also, you may need to issue HP OpenView commands so that discovery can take place.

The sections that follow discuss these steps in detail.

Network Configuration and 6700 Series Proxied Devices

HP OpenView can establish a management link to a system running the 6700 Series NMS SNMPProxy Agent over a LAN (via a router or LAN adapter), a leased line, or a dial-up connection. TheDCE Manager provides no direct support for link establishment or disestablishment. It is yourresponsibility to provide the hardware and software that enables HP OpenView to communicatewith the proxy agent.

6700 Series NMS Device Profiles

To have devices managed by the 6700 Series NMS (and in turn by HP OpenView), create profilesfor the devices using 6700 Series NMS menu selections. The COMSPHERE 6700 Series NetworkManagement System User’s Guide describes how to create device profiles.

6700 Series NMS SNMP Proxy Agent Configuration

To have your HP OpenView management system manage proxied devices, register your HP OpenView system with the 6700 Series NMS SNMP Proxy Agent. Enter the appropriate information on the screen displayed by the proxy agent’s menu selectionConfiguration–>SNMP–>Authorized Managers.

6700 Series Proxied Device Configuration

As with the 3100 Series devices, the DCE Manager does not enable you to configure a proxieddevice from scratch. Before HP OpenView can discover any proxied device, an operator at thedevice site must do some configuration using the device’s front panel. The individual devicemanuals provide detailed information on device configuration. Refer to the COMSPHERE 6700 Series Network Management System User’s Guide for a description of the deviceconfiguration options related to network management.

Discovering Devices

2-57800-A2-GB21-20 January 1997

Methods for Discovering and Managing 6700 Series Proxied Devices

Unlike 3100 Series devices, proxied devices are not automatically discovered. Discovery andmanagement of proxied devices require that objects ‘‘above” them are discovered and managed.There are four HP OpenView submap objects (represented by symbols) related to the managementof proxied device. As Figure 2-1 illustrates, the objects exist in a hierarchy.

NetManage Symbol.

Double-click on NetManage symbolto display 6700 Series NMS ProxyAgent symbol.

6700 Series NMS Proxy Agent Symbol.

Double-click on 6700 Series NMS ProxyAgent symbol to display the ControlChannel symbol.

Control Channel Symbol.

Double-click on Control Channelsymbol to display the proxied devicesymbols.

Symbol for a 3800 Series device.

Figure 2-1. Object Hierarchy


2-6 January 1997 7800-A2-GB21-20

Standard Discovery and Management

The standard discovery process discovers NetManage� (TCP/IP software) running on a PC. If theprocess also finds a 6700 Series NMS SNMP Proxy Agent installed on the PC, the process changesthe PC symbol (i.e., HP OpenView computer symbol) to a NetManage symbol and places a proxyagent symbol on the NetManage node submap.

NOTE

If the community names of the 6700 Series SNMP Proxy Agent arenot public or null, you must use the Options–>SNMP Configurationdialog to define the community names for the proxied agent objects.(The names to be changed are identified on the SNMPConfiguration dialog with the phrase CHANGE_THIS_STRING.)

Initially, the proxy agent objects are not managed. Further, none of the underlying objects arediscovered. In order to discover and manage the underlying Control Channel and proxied deviceobjects:

1. Select the proxy agent object.

2. Choose the menu selection Options–>Manage Objects.

After a proxied device has been discovered and managed, the color of the device symbol changesdepending on its status. For symbols to reflect the status of the objects below them, set thePropagate Most Critical parameter using the HP OpenView menu selectionFile–>Describe/Modify Map.

Manual Discovery and Management of the NetManage Object

To discover and manage a NetManage object and its subobjects without using the standarddiscovery process (because, for example, you installed NetManage on a management system afterthe system had already been discovered):

1. Select the HP OpenView computer object representing the system where NetManage isinstalled by clicking on its symbol (a square).

2. Choose the menu item Edit–>Delete–>From All Submaps.

3. Issue one of following commands:



Where: IP address is the Internet address of the system where NetManage is installed

• From the HP OpenView menu, select Diagnose–>Network Connectivity–>Ping(supplying the Internet address of the system where NetManage is installed).

Discovering Devices

2-77800-A2-GB21-20 January 1997

4. Double-click on the newly discovered NetManage symbol.

5. Select the proxy agent object by clicking on its symbol.

6. Choose the menu item Options–>Manage Objects.

Manual Discovery and Management of the 6700 Series Proxy Agent Object

To discover and manage a proxy agent object and its subobjects without using the standarddiscovery process (because, for example, you installed a proxy agent on a management systemafter the system had already been discovered):

1. Select the NetManage symbol of the system where the proxy agent is installed.

2. Choose the menu item Administer–>OneVision Device Mgmt: DCE Manager–>DiscoverProxied NMS.

3. Double-click on the NetManage symbol.


5. Choose the menu item Options–>Manage Objects.

Notes about the Discovery of 6700 Series Proxied Devices

Proxied devices are only discovered if device profiles are created for them on the 6700 SeriesNMS. After creating or deleting a device profile, follow these steps to update your submaps:


2. Choose the menu item Option–>Unmanaged Objects.

3. Choose the menu item Option–>Manage Objects.

The procedure above also rediscovers a proxied device if you have deleted its symbol from asubmap. To ensure that your submaps are up to date, do not add or delete objects from yoursubmap. Instead, add or delete devices profiles on the 6700 Series NMS and then follow theprocedure described above.


2-8 January 1997 7800-A2-GB21-20

Notes on Using PPPIf you use PPP as a dial-up management link to 3100 Series devices, it is recommended that youuse the HP OpenView menu selection Options–>SNMP Configurations to do the following on aper-device basis:

• Decrease the polling rate (Polling) so that connections are not established and brokenfrequently. Perhaps you would only want to connect to a device to access its status on anhourly or daily basis, rather than on the default 5-minute basis.

• Increase the timeout rate (Timeout) to 60 seconds to provide time for the connection to beestablished.

• Set the retry rate (Retry) to 0 to minimize connection charges.

Additionally, ensure that either the device or the PPP software is configured to terminate theconnection after the trap has been sent (normally the default setting). This is an important point.You could inadvertently incur large connection charges if the connection remains up after thedevice has sent the trap information.

Trap Handling and Alarm PropagationA trap received from a 3100 Series or proxied device causes an update to the HP OpenView EventLog. Refer to Chapter 6 for a description of the traps issued by 3100 Series and proxied devices.The receipt of a trap is indicated by a status color change in the HP OpenView Event Categorieswindow.

An Event Log entry contains the following information:

• Severity of the event (normal: green; warning: cyan; minor: yellow; major: orange; orcritical: red)

• Date and time of the event

• Name of the network element where the event originated

• Description of the event

Traps from any proxied device not discovered by HP OpenView cause an error message to beplaced in the nettl system log.

To have the NetManage, proxy agent, and control channel objects reflect the status color of theobjects below them, set the Propagate Most Critical parameter using the HP OpenView menuselection File–>Describe/Modify Map.

Discovering Devices

2-97800-A2-GB21-20 January 1997

Dial-Backup Module Addressing

A dial-backup module (DBM) contained within another device is separately manageable by theDCE Manager. The DBM has its own map symbol (see Device Symbols) and for managementpurposes can be treated as a separate device.

Device SymbolsFigure 2-2 shows the symbols that represent 3100 Series devices. The symbols are members of theHP OpenView symbol class Net Device.

Figure 2-2. DCE Manager 3100 Series Device Symbols


2-10 January 1997 7800-A2-GB21-20

Figure 2-3 shows the symbols that represent NetManage, the 6700 Series NMS SNMP ProxyAgent, the control channels, and the proxied devices (standalone and carrier models) as they aredisplayed on the HP OpenView submaps. The NetManage object is a member of the HP OpenViewsymbol class Computer. The proxy agent object is a member of the symbol class Software. Thecontrol channel object is a member of the symbol class Network. A device object is a member ofthe symbol class Net Device.

NetManage Symbol

6700 Series NMSProxy Agent Symbol

Control ChannelSymbol

Device Symbols

Figure 2-3. DCE Manager 6700 Series Object Symbols

3-17800-A2-GB21-20 January 1997

Monitoring Health and StatusOverview 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Health and Status of 3100 Series Devices 3-1. . . . . . . . . . . . . . . . . . .

Evaluating Status Colors 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Summary Health and Status Dialog (Network T1, DTE T1,

Data, COM, MODEM Ports) 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network T1 Dialog 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTE T1 Dialog 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Ports Dialog 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network T1 Performance Statistics 3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Checking Health and Status of Proxied Devices 3-12. . . . . . . . . . . . . . . . . . . . . . Evaluating Status Colors 3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health and Status Display 3-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Circuit Quality Table 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EIA Status Display 3-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External Leads Display 3-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OverviewThe DCE Manager enables you to check the general characteristics of 3100 Series and 6700 Seriesproxied devices as well as performance and health and status information. The first part of thechapter discusses 3100 Series devices; the second part discusses proxied devices.

Checking Health and Status of 3100 Series DevicesThe following sections describe how to interpret the colors of a 3100 Series device and interfacesymbols and how to access and interpret the dialogs that describe the health and status of thedevice as a whole and its individual interfaces.

NOTE

To update the information reported by a health and status dialog,you must close and then re-open the dialog.

3


3-2 January 1997 7800-A2-GB21-20

Evaluating Status Colors

You can quickly evaluate the status of the 3100 Series device by noting the color of the devicesymbol. You can evaluate the status of an individual interface by displaying a 3100 Series devicerear panel (Monitor–>OneVision Device Mgmt: DCE Manager–>Rear Panel–>Open). Table 3-1describes the colors and their meaning.

Table 3-1HP OpenView Status Colors

Supported by 3100 Series Devices

Color* Meaning

Blue Status information unavailable

Red Alarm (critical) or disabled

Salmon In test

Green No alarm (normal)

Tan Unmanaged

*The color of a device or interface symbol reflects the last known state.

Monitoring Health and Status

3-37800-A2-GB21-20 January 1997

Device Summary Health and Status Dialog (Network T1, DTE T1, Data, COM, MODEM Ports)

The read-only Summary Health and Status Dialog provides the status of the three principalcommunication interfaces: Network T1, DTE T1, and Data Ports 1–4 (if existent). It also providesthe COM port and the MODEM port, as described in Table 3-2. (Appendix A identifies the MIBobject used to generate the dialog.) To access the dialog:

1. Position the mouse cursor over a 3100 Series device symbol as it appears on an HPOpenView Windows submap.


3. Double-click Health and Status (att3100) in the Object Attributes list box.

Table 3-2Device Summary Health and Status Dialog

Field Definition Possible Value

Network T1 Operational Status: Up state: no alarm conditions exist

Down state: an alarm condition exists

Testing state: a test is active on the interface

Up

Down

Testing

DTE T1 Operational Status: Up state: no alarm conditions exist and the interface is enabled

Down state: an alarm condition exists and the interface isdisabled


Up

Down

Testing

Port 1–4 Operational Status: Up state: the port is assigned to a T1 interface and both CTSand DSR are On

Down state: the port is unassigned or CTS or DSR is Off


Up

Down

Testing

COM Port Operational Status: Up and Down states: based on the current state of the link layerwhen the port is configured as the SNMP management link.Otherwise, the interface is in the Up state.

UpDown

MODEM Port Operational Status: Up and Down states: based on the current state of the link layerwhen the port is configured as the SNMP management link.Otherwise, the interface is in the Up state when a modem isconnected and in the Down state when a modem is notconnected.

UpDown


3-4 January 1997 7800-A2-GB21-20

Network T1 Dialog

The read-only Network T1 Health and Status Dialog provides the status of the Network T1interface, as described in Table 3-3. (Appendix A identifies the MIB objects used to generate thedialog.) To access the dialog:

1. Select a device by clicking on a 3100 Series device symbol as it appears on anHP OpenView Windows submap.

2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager–>RearPanel–>Open to display the rear panel.

3. Position the mouse cursor over the Network T1 interface symbol.



Table 3-3(1 of 2)

Network T1 Health and Status

Field Definitions Possible Value(s)

Operational Status: Up state: no alarm conditions exist

Down state: an alarm condition exists


Up

Down

Testing

Line Status:No alarms: no alarms present

Loss of Signal: a Loss of Signal condition has existed for morethan 2.5 seconds

Loss of Frame: an Out of Frame condition has existed for morethan 2.5 seconds

Yellow Alarm: a Yellow Alarm signal is being received

Alarm Indication Signal: an Alarm Indication Signal is beingreceived

Excessive Error Rate: an Excessive Error Rate has been detected

(one or more)No Alarms

Loss of Signal

Loss of Frame

Yellow Alarm

Alarm Indication Signal

Excessive Error Rate

Loopback Status: No Loopback Active: the interface is not in the loopback state

Line Loopback Active: a Line Loopback is active

Payload Loopback Active: a Payload Loopback is active

No Loopback Active

Line Loopback Active

Payload Loopback Active


3-57800-A2-GB21-20 January 1997

Table 3-3(2 of 2)

Network T1 Health and Status

Field Possible Value(s)Definitions

Send Code Status: No Code Active: interface is sending normal or looped data

Sending 1–8 Pattern: interface is sending an 1–8 Pattern

Sending QRSS Pattern: interface is sending a QRSS Pattern

No Code Active

Sending 1–8 Pattern

Sending QRSS Pattern

Monitor Status: No Monitoring Active: interface is not monitoring a pattern

Monitoring QRSS Pattern: interface is monitoring a QRSS Pattern

No Monitoring Active

Monitoring QRSS Pattern

Test Result: None: no test currently active

Test in Progress: a test is in progress

Test Not Supported: a requested test is not supported

Unable to Run Test: the requested test cannot run because of thestate of the device

None

Test In Progress

Test Not Supported

Unable To Run Test

Test Code: None: no information beyond that reported by Test Resultsavailable

In Sync And No Bit Errors: no errors have been detected in aQRSS pattern

In Sync With Bit Errors: errors have been detected in a QRSSpattern

Not In Sync: device could not synchronize on the requestedpattern

None

In Sync And No Bit Errors

In Sync With Bit Errors

Not In Sync


3-6 January 1997 7800-A2-GB21-20

DTE T1 Dialog

The read-only DTE T1 Health and Status Dialog provides the status of the DTE T1 interface, asdescribed in Table 3-4. Because the 3165 has no DTE Port, this dialog is not available for thatdevice. (Appendix A identifies the MIB objects used to generate the dialog.) To access the dialog:



3. Position the mouse cursor over the DTE T1 interface symbol.



Table 3-4DTE T1 Health and Status Dialog

Field Definitions Possible Value(s)

Operational Status: Up state: no alarm conditions exist and the interface is enabled

Down state: an alarm condition exists and the interface is disabled


Up

Down

Testing

Line Status:No alarms: no alarms present

Loss of Signal: a Loss of Signal condition has existed for morethan 2.5 seconds

Loss of Frame: an Out of Frame condition has existed for morethan 2.5 seconds

Yellow Alarm: a Yellow Alarm signal is being received

Alarm Indication Signal: an Alarm Indication Signal is beingreceived

(one or more)No Alarms

Loss of Signal

Loss of Frame

Yellow Alarm

Alarm Indication Signal

Loopback Status: No Loopback Active: the interface is not in the loopback state

Line Loopback Active: a Line Loopback is active

DTE Loopback Active: a DTE Loopback is active

No Loopback Active

Repeater Loopback Active

DTE Loopback Active


3-77800-A2-GB21-20 January 1997

Data Ports Dialog

The read-only Data Ports Health and Status Dialog provides the status of the Data Ports 1–4, asdescribed in Table 3-5. (The number of ports depends on the model of your device. Because the3150/3151 has no data ports, this dialog is not available for that device.) (Appendix A identifiesthe MIB objects used to generate the dialog.) To access the dialog:



3. Position the mouse cursor over one of the Data Port interface symbols.



Table 3-5(1 of 2)

Data Ports 1 –4 Health and Status Dialog

Field Definitions Possible Value

Operational Status: Up state: the port is assigned to a T1 interface and both CTS andDSR are On

Down state: the port is unassigned or CTS or DSR is Off


Up

Down

Testing

Test Status: None Active: interface is not in loopback mode nor monitoring apattern

Data Channel Loopback Active: a Data Channel Loopback isactive

Data Terminal Loopback Active: a Data Terminal Loopback isactive

Sending QRSS Pattern: interface is sending a QRSS Pattern

Sending 511 Pattern: interface is sending a 511 Pattern

Monitoring QRSS Pattern: interface is monitoring a QRSS Pattern

Monitoring 511 Pattern: interface is monitoring a 511 Pattern

None Active

Data Channel LoopbackActive

Data Terminal LoopbackActive

Sending QRSS Pattern

Sending 511 Pattern

Monitoring QRSS Pattern

Monitoring 511 Pattern

Test Result: None: no test currently active

Test in Progress: a test is in progress

Test Not Supported: a requested test is not supported

Unable to Run Test: the requested test cannot run because of thestate of the device

None

Test In Progress

Test Not Supported

Unable To Run Test


3-8 January 1997 7800-A2-GB21-20

Table 3-5(2 of 2)

Data Ports 1 –4 Health and Status Dialog

Field Possible ValueDefinitions

Test Code: None: no information beyond that reported by Test Resultsavailable

In Sync And No Bit Errors: no errors have been detected in apattern

In Sync With Bit Errors: errors have been detected in a pattern

Not In Sync: device could not synchronize on the requestedpattern

None

In Sync And No Bit Errors

In Sync With Bit Errors

Not In Sync

DTR: On: DTR signal is On

Off: DTR signal is Off

On

Off

CTS: On: CTS signal is On

Off: CTS signal is Off

On

Off

RTS: On: RTS signal is On

Off: RTS signal is Off

On

Off

DSR: On: DSR signal is On

Off: DSR signal is Off

On

Off


3-97800-A2-GB21-20 January 1997

Network T1 Performance Statistics

Network T1 performance statistics are provided in the form of a table or a graph.

Displaying Network T1 Performance Statistics Table

The read-only Network T1 Performance Statistics Dialog provides information about the operationof the Network T1 interface, as described in Table 3-6. Note that the fields displayed by the dialogvary depending on the device type. For example, the 3150 device does not report Controlled SlipSeconds (Cntrl Slip Seconds). (Appendix A identifies the MIB objects used to generate thedialog.)

The performance statistics are gathered by the 3100 Series device in 15-minute units or intervals.Up to 96 intervals are collected (96 x 15-minute intervals equals 24 hours).

Note that the information reported by the Network T1 Performance Statistics Dialog is containedwithin the device itself and is not stored in any HP OpenView database. It is important also torealize that the line statistics being collected for the Network T1 interface represent only the past24 hours of operation, and that information related to operation before then is not available.

To access the performance statistics:

1. Select a device by clicking on 3100 Series device symbol as it appears on an HP OpenViewWindows submap.




5. Double-click Performance Statistics (att3100) in the Object Attributes list box.

6. Choose, if desired, a beginning and ending range of 15-minute intervals to be displayed.

7. Click Verify.


3-10 January 1997 7800-A2-GB21-20

Table 3-6Network T1 Performance Statistics Dialog

Field Definitions Possible Values

Time Elapsed: Time in seconds since statistics began to be gathered <number>

Valid Intervals: Number of valid intervals that have been gathered <number between 1 and 96>

Current Interval:

Errored Seconds

Sev Err Seconds

Unavail Seconds

Cntrl Slip Seconds

Bursty ErroredSeconds

Current interval: interval that is being reported

Errored Seconds: a second with one or more ESF error events(one or more CRC6 error events or OOFs)

Severely Errored Seconds: a second with 320 or more CRC6error events or one or more OOFs occurring

Unavailable Seconds: 1-second intervals when service isunavailable

Controlled Slip Seconds: a period in which a frame was addedor deleted because of a variance in timing

Bursty Errored Seconds: a second in which more than one, butless than 320 CRC6 error events, have occurred

<number of current interval>

<number>

<number>

<number>

<number>

<number>

Beginning Interval Number, which you input, that represents the beginning of therange of 15-minute intervals to be displayed in the 15-MinuteInterval window

<number>

Ending Interval Number, which you input, that represents the end of the rangeof 15-minute intervals to be displayed in the 15-Minute Intervalwindow

<number>

15 Minute-Interval:Interval numberErrored SecondsSev Err SecondsUnavail SecondsCntrl Slip SecondsBursty ErroredSeconds

Number of intervalSee definitions above

<number between 1 and 96><number><number><number><number><number><number>

Total: 24 HoursErrored SecondsSev Err SecondsUnavail SecondsCntrl Slip SecondsBursty ErroredSeconds

See definitions above <number><number><number><number><number><number>


3-117800-A2-GB21-20 January 1997

Displaying the Network T1 Performance Statistics Graph

The Network T1 Performance Statistics Graph provides the same information as in the fields of theNetwork T1 Performance Statistics Dialog: i.e., Unavailable Seconds, Controlled Slip Seconds(not applicable for 3150/3151 devices), Bursty Errored Seconds, Severely Errored Seconds, andErrored Seconds. However, the information is provided in a graph — a line corresponding to eachfield element of the dialog, as Figure 3-1 illustrates. (The graph is generated using xnmgraph,which comes packaged with HP OpenView. Refer to HP OpenView documentation for adescription of xnmgraph.)

The current 24 hours worth of 15-minute intervals are plotted on the graphs. The displays are notupdated as new intervals of data are available. You must close and reopen the PerformanceStatistics Graph to get the most current data.

220

200

180

160

140

120

100

80

60

40

20

0

16:56:39 21:30:24 02:04:09 06:37:54 11:11:39 15:15:24

Seconds

Severely Errored SecondsErrored Seconds

Unavailable SecondsControl Slip SecondsBursty Errored Seconds

495-14594-01

Figure 3-1. Network T1 Performance Statistics Graph


3-12 January 1997 7800-A2-GB21-20

To access the Network T1 Performance Statistics Graph display:

1. Select a device by clicking on 3100 Series device symbol as it appears on an HP OpenViewWindows submap.


3. Select the Network T1 interface by clicking on the interface symbol.

4. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager–>PerformanceStatistics Graph to display the graph. The selection name of the device is displayed in thetitle bar.

Checking Health and Status of Proxied DevicesThe following sections describe how to interpret the status colors related to the COMSPHERE6700 Series NMS and its proxied devices, and how to access and interpret the dialogs that describetheir health and status.

Evaluating Status Colors

You can quickly evaluate the status of a 6700 Series NMS or proxied device by noting its symbolcolor. Table 3-7 describes the colors and their meaning.

Table 3-7(1 of 2)

HP OpenView Status Colors Supported by Proxied Devices

Color Meaning

Blue Status information unavailable

Red One of the following alarms has been received:• Device Fail• Out Of Threshold• Facility Alarm• External Alarm• Streaming Terminal• Non-Answering Modem• Short Holding Time Modem• No Response

Salmon In test

Green No alarm (normal)


3-137800-A2-GB21-20 January 1997

Table 3-7(2 of 2)

HP OpenView Status Colors Supported by Proxied Devices

Color Meaning

Yellow One of the following alarms has been received:• Configuration Change Notify• Make Busy Mode• Service Line• Sub-tree Truncation• TDM Failure; Good APL• Trib Timeout• Dial Tone• Redundant Power

Orange One of the following alarms has been received:• Access Security• Dial Backup Active• DTE Alarm• Subnormal Speed• Primary Channel Interrupt• Firmware Downloading

Dark brown Disabled

Tan Unmanaged

NOTE

For a NetManage, proxy agent, or control channel symbol to reflectthe status color of its subobjects, set the Propagate Most Criticalparameter using the HP OpenView menu selection File–>Describe/Modify Map.

Health and Status Display

The read-only Proxied Device Health and Status Display provides status information about aproxied device, as described in Table 3-8. (Appendix A identifies the MIB objects used to generatethe display.)

Note that if N/A is displayed in a field, the information is unavailable.

After the status has been displayed, update the information by clicking the Refresh button. To exitthe display, click the Cancel button.

Any errors that prevent a task (such as communicating to the COMSPHERE 6700 Series NMSSNMP Proxy Agent) from completing are logged in the HP OpenView Log database (nettl). Anyerrors returned by the proxy agent are displayed in the status region of the display.


3-14 January 1997 7800-A2-GB21-20

Accessing the Display from the Menu

To access the display from the menu:

1. Select a device by clicking on a proxied device symbol as it appears on an HP OpenViewWindows submap.

2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager–>Health andStatus to access the display. The selection name of the device is displayed in the title bar.

Accessing the Display from the Command Line

To access the display from the UNIX command line:

TYPE: /usr/OV/bin/att6700Status –target < selection name>

Where: selection name is the selection name of the device

Table 3-8(1 of 2)

Proxied Device Health & Status


Connected Device: The device name of the connected device <15 characters>

Connect Time: Connect time in days:hours:minutes:seconds <number>

Device State: Current state of the device • Idle or Leased• Ring Indicate• Answering• Talk Mode• Off Hook• Dialing• Remote Ringing• On Line• Dial Backup• Dial Standby

Speed (bps): Current data rate of the device in bits persecond

<number>

Control/Trib: Indicates the position of the device in thenetwork

• Local Control• Remote Control• Tributary• Other

Line Configuration: Indicates the configured mode of the device • Leased• Dial


3-157800-A2-GB21-20 January 1997

Table 3-8(2 of 2)

Proxied Device Health & Status

Field Possible ValuesDefinitions

Polling State: Indicates the polling state of the device • Active• Inactive• Inventory• Suspended

Alerts: Current alerts for the device (one or more)• Device Fail• Config Change Notify• Test Mode• Disabled• Out of Threshold• Facility Alarm• External Alarm• Streaming Terminal• Access Security• Dial Backup Active• DTE Alarm• Subnormal Speed• Primary Channel Interrupt• Firmware Downloading• Make Busy Mode• Service Line• Non-answering Modem• Short Holding Time Modem• Sub-tree Truncation• TDM Failure; good APL• Trib Timeout• Dial Tone• Redundant Power• No Response


3-16 January 1997 7800-A2-GB21-20

Circuit Quality Table

The read-only Circuit Quality Table is a Network Node Manager Application Builder applicationthat provides the operating characteristics of the data circuit being used by the device, as describedlater in Table 3-10. (Appendix A identifies the MIB objects used to generate the display.)

NOTE

Circuit quality information is not available for 3550 or 3600 Seriesdevices without the dBM option.

Note that if no value is displayed in a field, the information has not been configured in the device.

After the status has been displayed, update the information by clicking the Restart button. To exitthe display, click the Close button.

Any errors that prevent a task (such as communicating to the COMSPHERE 6700 Series NMSSNMP Proxy Agent) from completing are logged in the HP OpenView Log database (nettl). Anyerrors returned by the proxy agent are displayed in the status region of the display.


2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager–>CircuitQuality Table to display the table. The selection name of the device is displayed in the titlebar.

Because certain devices may not return certain circuit quality values, it is important to check theValidity of the values returned as described in Table 3-9.

Table 3-9Proxied Device Circuit Quality Validity

Field Possible Values

Validity:See the fields in Table 3-10 for the specificvalidity field (e.g., Receive Level Validity).

• Valid• Valid greater than• Valid less than• Not valid for modulation mode• Not valid for multipoint mode• Not available yet• Count overflow• Not used

Note that warning and alarm ranges begin at the next higher number than that shown.


3-177800-A2-GB21-20 January 1997

Table 3-10(1 of 3)

Proxied Device Circuit Quality Table

Field/Definition UnitsLowest

PossibleValue

WarningRange

AlarmRange

HighestPossible

Value

Receive Level Validity: See Table 3-9

Receive LevelThe actual strength of the received signal.

dBm x 10 –50 –40 –10 0

Signal to Noise Validity: See Table 3-9

Signal to NoiseThe ratio of the amplitude of the signalplus the noise to the amplitude of thenoise.

dB x 10 0 24 n/a 40

Phase Jitter 20–300 Hz Validity: See Table 3-9

Phase Jitter 20–300 HzThe amount of phase difference(out-of-phase) between the transmittedcarrier signal and the received carriersignal.

degrees x 10 0 5 n/a 45

Frequency Offset Validity: See Table 3-9

Frequency OffsetThe difference between the transmittedcarrier frequency and the received carrierfrequency.

Hz x 10 –20 –5 5 20

Non-linear Distortion Validity: See Table 3-9

Non-linear DistortionThe portion of the channel output that isnonlinear in relation to the input signal.Harmonic and intermodulation distortionwould cause this kind of distortion.

Negative tenthsof dB

–40 n/a –30 0

Retrains Validity: See Table 3-9

RetrainsThe number of retransmissions during theprevious 15 minutes.

Number of retrainevents during thelast 15 minutes

0 n/a 0 255


3-18 January 1997 7800-A2-GB21-20

Table 3-10(2 of 3)


Field/DefinitionHighestPossible

Value

AlarmRange

WarningRange

LowestPossible

ValueUnits

Gain Hits Validity: See Table 3-9

Gain HitsA gain hit is a 3 dB change lasting morethan 4 milliseconds.

Number of gain hitevents during thelast 15 minutes

0 n/a 0 255

Phase Hits Validity: See Table 3-9

Phase HitsA phase hit is a phase change to a1004 Hz test signal greater than20 degrees.

Number of phasehit events duringthe last 15 minutes.

0 n/a 0 255

Impulse Noise Validity: See Table 3-9

Impulse NoiseAn impulse hit is a voltage surge of within6 dB of the normal carrier level lastingmore than 4 milliseconds.

Number of impulsenoise events duringthe last 15 minutes.

0 n/a 0 255

Dropouts Validity: See Table 3-9

DropoutsA dropout is a normal carrier leveldecrease greater than 12 dB lasting morethan 4 milliseconds.

Number of dropoutevents during thelast 15 minutes

0 n/a 0 255

Line Quality Validity: See Table 3-9

Line QualityA number used to indicate the quality ofthe signal.Note: If the signal quality is set to “no

signal,” no other impairments are displayed.

1: good2: fair3: poor4: no signal

0 n/a 2 4

Near End Echo Validity: dB x 10 See Table 3-9

Near End EchoThe ratio between the transmit signal andthe receiver near end echo of the signal.

dB x 10 –40 n/a –27 0


3-197800-A2-GB21-20 January 1997

Table 3-10(3 of 3)


Field/DefinitionHighestPossible

Value

AlarmRange

WarningRange

LowestPossible

ValueUnits

Far End Echo Validity: See Table 3-9

Far End EchoThe transmit signal and the echo from thefar end of the signal.

dB x 10 –40 n/a –27 0

Far End Delay Validity: See Table 3-9

Far End DelayThe roundtrip delay of the far end echo.

Milliseconds 0 n/a 100 4095

Echo Frequency Offset Validity: See Table 3-9

Echo Frequency OffsetThe frequency offset of the far end echo.

Tenths of Hz –20 –5 5 20


3-20 January 1997 7800-A2-GB21-20

EIA Status Display

The read-only EIA Status Display is a Network Node Manager Application Builder applicationthat provides status information about the EIA leads of the ports of a proxied device, as describedin Table 3-11. (Appendix A identifies the MIB objects used to generate the display.)


To access the display:


2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager–>EIA Statusto access the display. The selection name of the device is displayed in the title bar.

Table 3-11Proxied Device EIA Status Display


Port: Port number of the device <number>

DTRTDRDDSRRTSCTSDCDTMDRIPIN13PIN19DRSLLRLRIDPRDLOCRQACRDSCPND

EIA signals Off, On, Unsupported Lead, or Lead Changing


3-217800-A2-GB21-20 January 1997

External Leads Display

The read-only External Leads Display is a Network Node Manager Application Builder applicationthat provides status information about the external leads of a proxied device, as described inTable 3-12. (Appendix A identifies the MIB objects used to generate the display.)

NOTE

The External Leads Display is not available for 3800 and 3900 Series devices within carriers. Also, this display only returnsinformation if the circuit is active.




2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager–>ExternalLeads to access the display. The selection name of the device is displayed in the title bar.

Table 3-12Proxied Device External Leads Display


Output A Pin 12 for 3550 and 3600 Series devicesPin 16 for 3800 and 3900 Series devices

Lead Off or Lead On

Output B Pin 13 for all devices

Input A Pin 19 for all devices

Input B Pin 14 for 3800 and 3900 Series Devices

4-17800-A2-GB21-20 January 1997

Displaying and SettingConfiguration

Overview 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying and Setting the 3100 Series Device Configuration 4-2. . . . . . . . . . .

Characteristics of Enroll Dialogs 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identity Dialog 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Channel Configuration Dialog 4-4. . . . . . . . . . . . . . . . . . . . . . . . Copy Device Configuration Area 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Interface Configuration Dialogs 4-7. . . . . . . . . . . . . . . . . . . . . . .

Displaying and Setting the NMS and Proxied Device Configuration 4-10. . . . . . NMS Administration Display 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NMS System Features Display 4-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Front Panel Emulator 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identity Display 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Directory Display 4-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Menu 4-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Administration Display 4-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OverviewThe DCE Manager enables you to display and set selected configuration parameters (MIBvariables) of 3100 Series devices and proxied devices. You can also display configurationinformation about the COMSPHERE 6700 Series NMS. Additionally, you can use a front panelemulator to configure a proxy device as if you were using the device’s front panel. The first part ofthe chapter discusses the configuration of 3100 Series devices; the second part discusses theconfiguration of the 6700 Series proxy agent and proxied devices.

Be aware that although you can only set selected MIB variables via the DCE Manager, you can setany read-write MIB variable using the HP OpenView MIB Browser utility (Monitor–> MIBValues:Browse MIB: SNMP). All the MIBs necessary to manage the 3100 Series devices, proxyagent, and proxied devices are loaded automatically as part of the installation of the DCE Manager.See Figure 1-2 in Chapter 1 for a illustration of the MIB tree.

4


4-2 January 1997 7800-A2-GB21-20

Displaying and Setting the 3100 Series Device ConfigurationThe DCE Manager uses HP OpenView enroll dialogs to present configuration information about3100 Series devices as a whole and about its individual interfaces (Network T1, DTE T1, and dataports). You can change some of this information. The information that you can change is indicatedby read-write access in the tables.

Characteristics of Enroll Dialogs

The following characteristics apply to enroll dialogs:

• To update the information reported by a dialog, close and then re-open the dialog.

• When you select a field to change, a list of values is displayed. Note that Unset is not a validentry.

• To apply your configuration change, click the Verify button and then click the Cancel buttonto close the dialog.

NOTE

Before you attempt to set configuration values for 3100 Seriesdevices, ensure that the Write Community Name matches that ofthe device. It does not match by default. You can set the WriteCommunity Name by using the HP OpenView menu selectionOptions–>SNMP Configuration.

Identity Dialog

The Identity Dialog provides general information about a device, as described in Table 4-1. Notethat the fields displayed by the dialog vary depending on the device type. For example, the 3150device has no data ports, so that field is absent. Also, the 3151 and 3165 device have only oneHardware CCA, so the Hardware CCA2 field will not display. (Appendix A identifies the MIBobjects used to generate the dialog.) To access the Identity Dialog:

1. Position the mouse cursor over a device symbol as it appears on an HP OpenViewWindows submap.


3. Double-click Identity (att3100) in the Object Attributes list box.

Displaying and Setting Configuration

4-37800-A2-GB21-20 January 1997

Table 4-13100 Series Device Identity Dialog

Field Description Access

IP Hostname Internet name (assigned by HP OpenView) read

Description: Description read

Model: Model number read

Software Release: Software release number read

Hardware CCA1: Hardware revision number of the Hardware Circuit Card Assembly 1

read

Hardware CCA2: Hardware revision number of the Hardware Circuit Card Assembly 2

read

Serial Number: Serial number read

Up Time: Time in hundredths of a second since the network managementsubsystem contained in the device was re-initialized

read

Contact: Information about the contact person for the device

Note that 127 characters is the maximum valid size for this field

read-write

Name: Name assigned by device administrator


read-write

Location: Physical location of the device


read-write

Network T1 Description: Description of the interface, including the CAA number for the CSUboard

read

DTE T1 Description: Description of the interface, including the CAA number for the CSUboard

read

Data Port 1–4 Description: Description of the interface, including the CAA number for the DSUboard

read

COM Description: Description of the interface, including the CAA number for the CSUboard

read

MODEM Description: Description of the interface, including the CAA number for the CSUboard

read


4-4 January 1997 7800-A2-GB21-20

Displaying Channel Configuration Dialog

The read-only Channel Configuration Dialog displays the channel assignment of Network T1 andDTE T1 channels. Figure 4-1 illustrates the Channel Configuration Dialog. Table 4-2 describes itscontents. The DTE T1 channels do not display for a 3165 device.

Figure 4-1. Channel Configuration Dialog


4-57800-A2-GB21-20 January 1997

To access the screen for a selected device:

1. Select a device by clicking on a 3100 Series device symbol as it appears on an OpenViewWindows submap.

2. Click the right-hand mouse button and select Describe/Modify Object.

3. Double-click Channel Configuration (att3100) in the Object Attributes list box.

Table 4-2 shows the information relevant to the dialog.

Table 4-23100 Series Device Channel Configuration

Field Description

Network T1 Channels: 1 2 3...22 23 24 List of channel assignments, where P1 is port 1, P2 is port 2, etc. See notebelow.

DTE T1 Channels: 1 2 3...22 23 24 List of channel assignments, where P1 is port 1, P2 is port 2, etc. See notebelow.

NOTE

Although channel connections between the DTE and Network T1ports may exist, the DCE Manager cannot determine the actualNetwork T1 and DTE channel assignments. Therefore, Nx’s andDx’s appear in the display. For example, in Figure�4-1, Nx’s indicatethat while the DTE channels D1–D5 are assigned to Network ports,the actual Network channel positions are unknown. Portassignments are known and displayed.


4-6 January 1997 7800-A2-GB21-20

Copy Device Configuration Area Dialog

The read-only Copy Device Configuration Area Dialog displays up to eleven possibleconfiguration combinations. To access the User Configuration Dialog:



3. Double-click Copy Device Configuration Area (att3100) in the Object Attributes list box.

Upon opening the Copy Device Configuration Area Dialog, the following warning messagedisplays:

WARNING

Copying device configuration information into the Active areamay result in setting a NULL IP Address into the device. If thisoccurs, the address must be reset from the device’s frontpanel. Be absolutely sure you want to do this.


Table 4-3Copy Device Configuration Area Dialog

Field Definitions Possible Values Access

Copy DeviceConfiguration Area:

Copies the entire contents of one configuration areainto another configuration area. The Factory 1 andFactory 2 areas can be copied from but cannot becopied into.

Active to Customer 1Active to Customer 2Customer 1 to ActiveCustomer 1 to Customer 2Customer 2 to ActiveCustomer 2 to Customer 1Factory 1 ActiveFactory 1 to Customer 1Factory 1 to Customer 2FActory 2 to ActiveFactory 2 to Customer 1Factory 2 to Customer 2

read/write


4-77800-A2-GB21-20 January 1997

Displaying Interface Configuration Dialogs

The following sections describe the dialogs that provide configuration information for theindividual interfaces: Network T1, DTE T1, and Data Ports.

Network T1 Dialog

The Network T1 Configuration Dialog provides configuration information about the Network T1interface, as described in Table 4-4. To access the Network T1 Dialog:





5. Double-click Configuration (att3100) in the Object Attributes list box.


Table 4-4Network T1 Configuration Dialog


Interface Type: Identifies the type of interface based on thephysical/link protocol immediately below the networklayer

T1-carrier read

Speed (bps): Current configured data rate 1,544,000 bps read

Framing: Corresponds to the NET Framing configuration option ESFD4

read-write

Circuit Identifier: Transmission vendor’s circuit identifier. (Note that thisfield does not appear if not supported by the devicefirmware.)

<string> read-write

Line Coding: Corresponds to the NET Coding configuration options B8ZSAMI

read-write

Signal Mode: Specifies whether Robbed Bit Signaling is in use NoneRobbed Bit

read

Tx Clock Source: Timing source for the transmit clock Loop TimingLocal TimingThrough Timing

read

Facilities Data Link: Specifies how the Facilities Data Link is being used (one or both)ANSI-T1-403ATT-54016

read


4-8 January 1997 7800-A2-GB21-20

DTE T1 Dialog

The DTE T1 Configuration Dialog provides configuration information about the DTE T1 interface,as described in Table 4-5. (Appendix A identifies the MIB objects used to generate the dialog.) Toaccess the DTE T1 Dialog:



3. Position the mouse cursor over the DTE T1 interface symbol.




Table 4-5DTE T1 Configuration


Interface Type: Identifies the type of interface based on thephysical/link protocol immediately below the networklayer

T1-carrier read

Speed (bps): Current configured data rate 1,544,000 bps read

Framing: Corresponds to the DTE Framing configuration option ESFD4

read-write

Line Coding: Corresponds to the DTE Coding configuration option B8ZSAMI

read-write

Signal Mode: Specifies whether Robbed Bit Signaling is in use NoneRobbed Bit

read

Tx Clock Source: Timing source for the transmit clock Loop TimingLocal TimingThrough Timing

read

Facilities Data Link: Specifies how the Facilities Data Link is being used None read


4-97800-A2-GB21-20 January 1997

Data Ports Dialog

The Data Ports Configuration Dialog provides configuration information about the data ports, asdescribed in Table 4-6. (The number of ports depends on the model of your device. Because the3150/3151 has no data ports, this dialog is not available for that device.) (Appendix A identifiesthe MIB objects used to generate the dialog.) To access the Data Ports Dialog:



3. Position the mouse cursor over one of the Data Port interface symbols.



Table 4-6 shows the information relevant to the display.

Table 4-6Data Ports 1–4 Configuration Dialog


Interface Type: Identifies the type of interface based on the physical/link protocol immediately below the network layer.

Point-To-Point-Serial read

Speed: Current configured data rate for the port when theport is allocated to one of the T1 interfaces. If theport is not allocated, the data rate is 0.

<speed in bps> read

Port Type: Port hardware type. EIA-530A/RS449V.35

read

Clock Source: Clock source for the port. InternalExternal

read-write


4-10 January 1997 7800-A2-GB21-20

Displaying and Setting the NMS and Proxied DeviceConfiguration

This section describes the configuration information related to the the COMSPHERE 6700 SeriesNMS and the proxied devices (managed through the COMSPHERE 6700 Series NMS SNMPProxy Agent).

NMS Administration Display

The NMS Administration Display provides information about the 6700 Series NMS, as describedin Table 4-7. (Appendix A identifies the MIB objects used to generate the display.)

Note that if no value is displayed in a field, the information has not been configured.

After the status has been displayed, you can update the information by clicking the Restart button.To exit the display, click the Close button.

Any errors that prevent a task (such as communicating to the COMSPHERE 6700 Series NMSSNMP Proxy Agent) from completing are logged in the HP OpenView Log database (nettl).Critical errors are also shown in a pop-up display.



1. Select a 6700 Series NMS SNMP Proxy Agent symbol as it appears on an HP OpenViewWindows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Admin toaccess the display. The selection name of the device is displayed in the title bar.



TYPE: /usr/OV/bin/att6700NMSAdmn –target < selection name> –config/usr/OV/att/att6700/NMSAdmin.res



4-117800-A2-GB21-20 January 1997

Changing a Configuration Value

To change a configurable value:

1. On the input line of a read-write field, type in your value.

2. Click the Apply button to apply the change and leave the display open, or click the OKbutton to apply the change and close the display.

To see any real-time updates that have been made to the information from another NMS station,press the Refresh button.

Table 4-7NMS Administration Display

Field Definitions Access

NMS Name: Name of 6700 Series NMS read

Location: Physical location of the 6700 Series NMS <40 characters>

(This information is configured on the 6700 Series NMS using theWorkstation–>Administration menu selection of the NetworkConfiguration utility.)

read-write

Contact 1: Contact person for the 6700 Series NMS <40 characters>


read-write

Contact 2: Contact person for the 6700 Series NMS <40 characters>


read-write

Read Community: Read community name of the 6700 Series NMS read

Base Read Community: Base read community name of the 6700 Series NMS. Concatenatedwith the proxied device name to form the proxied device address(myNMSmydevice)

read

Base Write Community: Base write community name of the 6700 Series NMS. Concatenatedwith the proxied device name to form the proxied device address(myNMSmydevice)

read


4-12 January 1997 7800-A2-GB21-20

NMS System Features Display

The read-only NMS System Features Display is a Network Node Manager Application Builderapplication that provides the system features of a COMSPHERE 6700 Series NMS, as described inTable 4-8. (Appendix A identifies the MIB objects used to generate the display.)

Note that if no value is displayed in a field, the information has not been configured.



1. Select a device by clicking on a proxy device symbol as it appears on an HP OpenViewWindows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>SystemFeatures to access the display. The selection name of the device is displayed in the title bar.

Table 4-8NMS System Features Display

Field Definitions

Name Name of the feature installed on the 6700 Series NMS

Version Version of the feature

Serial Number Serial number of the feature


4-137800-A2-GB21-20 January 1997

Front Panel Emulator

The Front Panel Emulator emulates the operation of the front panel of 3800 and 3900 Seriesproxied devices. Detailed descriptions of the operation of the device front panels are provided bythe device manuals. Figure 4-2 shows the emulator display.

Figure 4-2. Front Panel Emulator

NOTE

If the front panel emulator of the COMSPHERE 6700 Series NMS isopen, you cannot open the front panel emulator of the DCEManager.


4-14 January 1997 7800-A2-GB21-20

Starting the Front Panel Emulator from the Menu


1. Select a 3800 or 3900 Series proxied device symbol as it appears on an HP OpenViewWindows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>FrontPanel:Open.

Starting the Front Panel Emulator from the Command Line


TYPE: /usr/OV/bin/attDCEFrntPnl –target < selection name> –config/usr/OV/attDCE/FrontPanel.res

Where: selection name is the selection name of the device, which is checked to ensurethat the DCE Manager can communicate with the device it represents and that thedevice supports the Front Panel MIB.

The selection name of the device is displayed in the title bar, as shown in Figure 4-2.

On successful start-up, the DCE Manager queries the device to determine what strings arecurrently displayed on the local front panel and then sets those text lines in the emulator window.

Operating the Front Panel Emulator

The Front Panel Emulator operates exactly as the actual front panel of a device, with the additionof the demand Refresh button. The front-panel display contains the elements described in Table 4-9.

Table 4-9Elements of the Front Panel Emulator

Elements Definitions

Text Window Contains the text that is displayed on the front panel LCD. When appropriate, a cursor, shown asan underscore, is displayed directly under the active character.

Moves you up the menu tree one level.

Moves you to the top of the current sub-menu.

Moves you one node to the left in the menu tree; this arrow is also used for moving the textcursor one character to the left, when appropriate.

Moves you one node to the right in the menu tree; this arrow is also used for moving the textcursor one character to the right, when appropriate.

F1, F2, F3 Selects the menu item directly above the button.

Refresh Causes the DCE Manager to immediately query the device for the current text window value.


4-157800-A2-GB21-20 January 1997

There is a delay between the time you click a button and when you receive a response from thedevice. During this period, a busy cursor is displayed and Processing is displayed in the statusarea. The emulator accepts no user input during this time.

Using Options Menu–>Set Refresh Rate

The menu selection Options Menu–>Set Refresh Rate displays a dialog box that enables you tomodify how often the DCE Manager polls the device for updates to the display strings (seeFigure 4-3). When the dialog box is displayed, it shows the current refresh setting. Each time theDCE Manager is started the refresh interval defaults to 3 minutes.

While the refresh dialog box is active, you cannot perform any other actions on the front paneldisplay.

Figure 4-3. Refresh Dialog Box

Use the slider to set your desired refresh interval by either clicking on it with the mouse andmoving it or using the left and right arrows on the keyboard. The range of the refresh interval is 1to 60 minutes.

Setting the refresh interval to 0 minutes causes the emulator to turn off automatic refreshing.Thereafter, the emulator refreshes the display only when you click the Refresh button or one of thefront panel buttons. (Note that while the emulator updates the display strings each time you selecteither the Refresh button or one of the front panel buttons, this does not restart the refresh interval.For example, if the interval is 10 minutes and after 5 minutes you select F1, the emulator updatesthe string immediately after the F1 action is performed. Subsequently, the emulator updates thescreen 5 minutes later when the refresh interval expires.)

Click the OK button to set the refresh interval. When you select a refresh rate other than 0, theemulator immediately queries the device for the current string. Click the Cancel button to close thewindow without making any changes


4-16 January 1997 7800-A2-GB21-20

Identity Display

The read-only device Identity Display is a Network Node Manager Application Builder applicationthat provides information about the identity of a proxied device, as described in Table 4-10.(Appendix A identifies the MIB objects used to generate the display.)





2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Identity toaccess the display.

Table 4-10Identity Display

Field Definitions

Model: Alphanumeric number that identifies the device.

Line Speed: Data rate of the device.

Software Version: Software/firmware version residing in the device.

Serial Number: Serial number of the device.

Application Module ID: ID identifying the application module.

Access Module ID: ID identifying the access module.

Restoral Option: The type of restoration that the device uses for backup. Refer to the appropriate device user’sguide for valid restoration features.

Configuration: The current configuration options of the device; for example: DDD, 2-wire APL, 4-wire APL.

International Strap: The current international option.

Hardware Part Number The Paradyne assigned hardware part number.

Software Part Number The Paradyne assigned software part number.

Option 1: Optional Features currently installed in the device. Refer to the appropriate device user’sguide for valid features.

Option 2: Additional option installed.






4-177800-A2-GB21-20 January 1997

Call Directory Display

The Call Directory Display provides information about the phone numbers in the proxy device’scall directory as described in Table 4-11. (Appendix A identifies the MIB objects used to generatethe display.) The Call Directory Display is not available for 3550 and 3600 Series devices withoutthe DBM option.



Any errors that prevent a task (such as communicating to the COMSPHERE 6700 Series NMSSNMP Proxy Agent) from completing are logged in the HP OpenView Log database (nettl).Critical errors are also shown in a pop-up display.

Table 4-11Proxied Device Call Directory Display

Field Definition Possible Values Access

ID: A unique identifier for the entry in the directory <15 character string> read

Phone Number: Phone number to be stored in the device calldirectory

<40 character string> read-write

Purpose: Purpose of the phone number OtherAlarm TrapDial BackupUnknown

read


4-18 January 1997 7800-A2-GB21-20




2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>CallDirectory to access the display. The selection name of the device is displayed in the titlebar.



TYPE: /usr/OV/bin/attDCECallDir –target < selection name> –config/usr/OV/att/attDCE/CallDir.res


Changing a Configuration Value

To change a configurable value:

1. On the input line of a read-write field, type in your value.

2. Click the Apply button to apply the change and leave the display open.Click the OK buttonto apply the change and close the display.

To see any real-time updates that have been made to the information from another NMS station,press the Refresh button.


4-197800-A2-GB21-20 January 1997

Command Menu

Table 4-12 defines the commands that you can send to a proxied device.

Table 4-12Proxied Device Commands

Command Definition

Clear Busy Causes the device to “unbusy” the analog line

Set Busy Causes the device to set to busy the attached analog line

Dial Number Causes modem to dial supplied number

Disconnect Call Causes current call to be disconnected

Disconnect Service Causes service to be disconnected

Disable Device Disables the device

Enable Device Enables the device

Hardware Device Reset Invokes a hardware reset of the device

Software Device Reset Invokes a software reset of the device

Send Message Sends a message string of up to 16 characters to the device’sfront-panel display

Switch to Dial Backup Causes the device to switch the service mode to dial backup

Switch to Dial Standby Causes the device to switch the service mode to dial standby

Switch to Leased Line Causes the device to switch the service mode to leased line

Switch to Service Line Causes the device to switch the service mode to service line


4-20 January 1997 7800-A2-GB21-20

Table 4-13 shows which devices support which commands.

Table 4-13Command List

Menu Selection3550 and

3600 SeriesDevices

3800Series

Devices

3900Series

Devices

Clear Busy � �

Set Busy � �

Dial Number � � �

Disconnect Call � � �

Disconnect Service � �

Disable Device � leased-line devices

Enable Device � leased-line devices

Hardware Device Reset � � �

Software Device Reset � � �

Send Message �

Switch to Dial Backup � � �

Switch to Dial Standby � � �

Switch to Leased Line � � �

Switch to Service Line � �


4-217800-A2-GB21-20 January 1997


To send a command from the menu:

1. Select a proxy device symbol as it appears on an HP OpenView Windows submap.

2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Command–><command name> to select a command.



TYPE: /usr/OV/bin/att6700DevCmd <command name> –target<selection name>

Where: command name is one of the following:

• SetBusy

• ClearBusy

• Dial

• DisconnectCall

• DisconnectService

• Disable

• Enable

• HardReset

• SoftReset

• SendMessage

• SwitchDialBackup

• SwitchDialStandby

• SwitchLeased

• SwitchServiceLine


Inputting Information

Two of the commands – Dial and Send Message – require you to input information. After you havesupplied a phone number and message respectively in the provided displays, click the Applybutton to apply the change and leave the display open. Click the OK button to apply the changeand close the display.


4-22 January 1997 7800-A2-GB21-20

Device Administration Display

The read-only Device Administration Display is a Network Node Manager Application Builderapplication that provides administrative information about a proxied device, as described inTable 4-14. (Appendix A identifies the MIB objects used to generate the display.)





2. Use the menu selection Administer–>OneVision Device Mgmt: DCE Manager–>Admin toaccess the display. The selection name of the device is displayed in the title bar.

Table 4-146700 Proxy Device Admin Display

Field Definitions

Device Name: Name used by the 6700 Series NMS to identify the device

Device Address: Address of the device in the ADP network (the network used by the6700 Series NMS to access the device)

Model Type: dial: 3800 Series dial modemsapl: 3900 Series leased-line modemsdsu: 3550 and 3600 Series DSUsdbm: 3600 Series Dial Backup Modules

Site: Device site name used by the 6700 Series NMS

Cabinet: Device cabinet name used by the 6700 Series NMS

Carrier: Carrier name

Carrier Slot: Device carrier slot number

Circuit Name: Device circuit name

Contact 1: Contact person for the device

Contact 2: Contact person for the device

Comment: Device comment string

DbmOption: Dial backup module option installed

MsdOption: Modem-sharing device option installed

McmpOption: Multichannel multipoint option installed

TdmOption: Time-division multiplexer option installed

5-17800-A2-GB21-20 January 1997

Using Loopback Modes andPattern Tests

Overview 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running Tests on 3100 Series Devices 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Displaying the Test Menus 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Whether a Test Is Running 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Pattern Test Results 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network T1 Loopback Modes and Pattern Tests 5-3. . . . . . . . . . . . . . . . . . . . DTE T1 Loopback Modes 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Ports Loopback Modes and Pattern Tests 5-5. . . . . . . . . . . . . . . . . . . . .

Running Tests on Proxied Devices 5-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the Test Display from the Menu 5-8. . . . . . . . . . . . . . . . . . . . . . . . Accessing the Test Display from the Command Line 5-8. . . . . . . . . . . . . . . . Checking the Test Results 5-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborting Tests Started from the Front Panel 5-10. . . . . . . . . . . . . . . . . . . . . . .

OverviewThe DCE Manager enables you to put 3100 Series and proxied devices in loopback mode andsend/monitor pattern tests. (You also can put proxied devices in self-test mode.) The pattern testscheck the integrity and performance of the devices and, to some extent, the network. The first partof the chapter discusses tests for the 3100 Series devices; the second part discusses the test for theproxied devices.

Refer to Chapter 6, Troubleshooting, for an explanation of how to use the loopback modes andpattern tests to isolate problems to a device or the network.

Running Tests on 3100 Series DevicesBefore you set loopback modes or run pattern tests on the 3100 Series devices, ensure that theWrite Community Name matches that of the device on which you want perform the action. It doesnot match by default. You can set the Write Community Name by using the HP OpenView menuselection Options–>SNMP Configuration.

5


5-2 January 1997 7800-A2-GB21-20

Displaying the Test Menus

To display the menus from which you can set loopback modes or send/monitor pattern tests:


2. Use the menu selection Monitor–>OneVision Device Mgmt: DCE Manager–> RearPanel–>Open to display the rear panel.

3. Select an interface by clicking on the interface symbol representing the one you want totest: Network T1, DTE T1, or Data Ports 1–4.

4. Use the menu selection Diagnose–>OneVision Device Mgmt: DCE Manager–>loopbackmodes or pattern tests. (Loopback modes or pattern tests inappropriate for the device youhave selected are grayed out.)

Checking Whether a Test Is Running

The DCE Manager enables you to check whether a test is in progress for an interface. To do this,use the appropriate health and status dialog (Chapter 3) or check the color of the interface symbol.It is salmon colored if a test is in progress. Use Monitor–>OneVision Device Mgmt: DCEManager–>Rear Panel–>Update Status to ensure that the rear panel reflects the current state ofthe interface.

Checking the Pattern Test Results

The DCE Manager enables the Network T1 and Data Port interfaces to continuously monitor theintegrity of data patterns sent to them by other devices. The result of a pattern test is reported in theTest Code field of the Network T1 or Data Ports health and status dialog (described in Chapter 3).The possible values are In Sync (device is operational), In Sync With Bit Errors (device ismarginal), or Not in Sync (device is down).

To check the result of a specific test, display the appropriate health and status dialog:

1. Select a device by clicking on a 3100 Series device symbol as it appears on an HPOpenView Windows submap.


3. Position the mouse cursor over the interface symbol that represents the interface that youwant to check.


5. Double-click Health and Status (att-3100) in the Object Attributes list box.

Using Loopback Modes and Pattern Tests

5-37800-A2-GB21-20 January 1997

Network T1 Loopback Modes and Pattern Tests

Table 5-1 shows the loopback modes and pattern tests available for the Network T1 interface. SeeUsing Loopback Modes and Pattern Tests in Chapter 6 for a description of how to use loopbackmodes and pattern tests to troubleshoot a device. (Appendix A identifies the MIB objects that areset when you select loopback modes and pattern tests.)

Table 5-1Network T1 Loopback Modes and Pattern Tests

Menu Item Function of Loopback Mode or Pattern Test

Remote Loopback –> Send LLBUp Code

Sends the line loopback up code from the selected device to the remote DSU/CSUfor a period of 10 seconds.

Remote Loopback –> Send LLBDown Code

Sends the line loopback down code from the selected device to the remoteDSU/CSU for a period of 10 seconds.

Loopback –> Abort Loopback Aborts active loopback tests on the selected device.

Loopback –> Start Line Loopback Loops the received signal on the selected network interface back to the networkwithout the signal passing through the framing circuitry of the DSU/CSU. The signalis looped on the network side of the DSU/CSU (see Figure 6-2 in Chapter 6).

Loopback –> Start PayloadLoopback

Loops the received signal on the selected network interface back to the networkafter the signal has passed through the framing circuitry of the DSU/CSU. Thesignal is looped on the DTE side of the DSU/CSU (see Figure 6-3 in Chapter 6).

Patterns –> Abort Send Aborts active send test pattern tests on the selected device.

Patterns –> Send QRSS Pattern Sends a QRSS test pattern out of the selected network interface.

Patterns –> Send 1 in 8 Pattern Sends a 1-in-8 pattern out of the network interface.

Patterns –> Abort Monitor Aborts active monitor test pattern tests on the selected device.

Patterns –> Monitor QRSS Pattern Monitors a QRSS test pattern received on the selected network interface.


5-4 January 1997 7800-A2-GB21-20

DTE T1 Loopback Modes

Table 5-2 shows the loopback modes available for the DTE T1 interface. See Using LoopbackModes and Pattern Tests in Chapter 6 for a description of how to use loopback modes and patterntests to troubleshoot a device. (Appendix A identifies the MIB objects that are set when you selectloopback modes.)

Table 5-2DTE T1 Loopback Modes

Menu Item Function of Test

Loopback –> Abort Aborts active loopback tests on selected device.

Loopback –> Start DTE Loopback Loops the received signal on the selected DTE T1 interface back to the DTE withoutthe signal passing through the framing circuitry of the DSU/CSU (see Figure 6-4 inChapter 6).

Loopback –> Start RepeaterLoopback

Loops the received signal(s) from the data ports and selected DTE T1 back to thedata and DTE ports after the signal(s) has passed through the framing circuitry (seeFigure 6-5 in Chapter 6).


5-57800-A2-GB21-20 January 1997

Data Ports Loopback Modes and Pattern Tests

Table 5-3 shows the loopback modes and pattern tests available for the Data Ports interfaces. (Thenumber of ports depends on the model of your device. Because the 3150 has no data ports, thisdialog is not available for that device.) See Using Loopback Modes and Pattern Tests in Chapter 6for a description of how to use loopback modes and pattern tests to troubleshoot a device.(Appendix A identifies the MIB objects that are set when you select loopback modes and patterntests.)

Table 5-3Data Ports 1–4 Loopback Modes and Pattern Tests

Menu Item Function

Remote Loopback –> Send V.54 Up Code Sends the V.54 activation sequence from the selected device to theremote DSU/CSU to initiate a V.54 Loop 2 (DCLB).

Remote Loopback –> Send V.54 Down Code Sends the V.54 deactivation sequence from the selected device to theremote DSU/CSU to terminate a V.54 Loop.

Remote Loopback –> Send FT1 Up Code Sends the ANSI T1.403 (Annex B) activation sequence from theselected device to the remote DSU/CSU to initiate a DCLB on theremote device.

Remote Loopback –> Send FT1 Down Code Sends the ANSI T1.403 (Annex B) deactivation sequence from theselected device to the remote DSU/CSU to terminate a DCLB on theremote device.

Loopback –> Abort Aborts active loopback tests on the selected device.

Loopback –> Start Data Channel Loopback Loops the data for the selected synchronous data port back to thenetwork interface after the information has passed all the way throughthe DSU/CSU; that is, just before it is sent to the customer equipment,either through the Network T1 or DTE T1 interface (see Figure 6-6 inChapter 6).

Loopback –> Start Data Terminal Loopback Loops the data for the selected synchronous data port back to the portjust before it is combined with the rest of the T1 data stream (seeFigure 6-7 in Chapter 6).

Patterns –> Abort Send Aborts active send test pattern tests on the selected device.

Patterns –> Send QRSS Pattern Sends a QRSS test pattern on the channels allocated to the selecteddata port.

Patterns –> Send 511 Pattern Sends a 511 test pattern on the channels allocated to the selected dataport.

Patterns –> Abort Monitor Aborts active monitor test pattern tests on the selected device

Patterns –>Monitor QRSS Pattern Monitors a QRSS test pattern received on the channels allocated to theselected data port.

Patterns –>Monitor 511 Pattern Monitors a 511 test pattern received on the channels allocated to theselected data port.


5-6 January 1997 7800-A2-GB21-20

Running Tests on Proxied DevicesTable 5-4 describes the self-test, loopback modes, and pattern tests available for proxied devices.Table 5-5 shows the devices (and their characteristics) that support the loopback modes and tests.

Refer to Chapter 6, Troubleshooting, for an explanation of how to use the loopback modes andpattern tests in troubleshooting devices and links.

Table 5-4Proxied Device Loopback Modes and Pattern Tests

Loopback ModeTest Description

Self-Test Runs a device’s self-test. Possible results are Test Passed or Test Failed . Refer to the deviceuser documentation for a detailed description of the self-test.

Loopback This loopback mode puts the selected device into analog loopback mode; that is, it connects thelocal analog receiver to the local analog transmitter. For modems, this is a CCITT V.54 Loop 3.

Loopback BERT This combination of loopback mode and pattern test puts the selected device in an analogloopback mode and causes a BERT pattern to be transmitted and received while it monitors forerrors.

Digital Loopback This loopback mode puts the selected device into digital loopback mode; that is, it connects thelocal digital receiver to the local digital transmitter. This loopback mode is useful if the remotedevice is incapable of initiating a remote digital loopback.

Remote DigitalLoopback

This loopback mode puts the selected remote device (the device with which the local device iscommunicating) into digital loopback mode; that is, it connects the remote digital receiver to theremote digital transmitter. A remote device must be connected to the device that issues this test inorder for it to run. For modems, this is a CCITT V.54 Loop 2.

Remote DigitalLoopback BERT

This combination of loopback mode and pattern test puts the selected remote device (the devicewith which the local device is communicating) in a digital loopback mode and causes a BERTpattern to be transmitted and received while it monitors for errors. A remote device must beconnected to the device that issues this test in order for it to run.

BERT (Bit Error RateTest)

This test causes the selected device to transmit a BERT pattern and monitor the loopbackedpattern for errors. A remote device must be connected and it must be looping back the BERTpattern.

DTE Loopback This loopback mode loops a DSU data port back to the DTE/DCE interface on a per-port basiswithout affecting the operation of the remaining ports.

Digital Test This test checks a pair of DSUs or DBMs and the circuit between them. A bit pattern is loopedthrough one tributary device and back to the control device, which checks the received data forerrors.

Select a local and a remote device on the HP OpenView submap before attempting to run thistest. (Select the local device by clicking on the local device symbol and then select the remotedevice by clicking on the remote device symbol while holding down the Control key.)

End-to-End Test This test simultaneously transmits, receives, and tests for the BERT pattern on a pair ofleased-line devices or connected dial modems. A remote device must be connected before thistest can run.

Select a local and a remote device on the HP OpenView submap before attempting to run thistest. (Select the local device by clicking on the local device symbol and then select the remotedevice by clicking on the remote device symbol while holding down the Control key.)


5-77800-A2-GB21-20 January 1997

Table 5-5Supported Loopback Modes and Tests

Test3550 and

3600 SeriesDevices

3800 Seriesand 3980Devices

3900 SeriesDevices

Can Only beIssued from a

Control Device

Time DivisionMultiplexing

FeatureRequired

Self-Test � � �

Loopback � � �

Loopback BERT � � �

Digital Loopback � � �

Remote Digital Loopback � � �

Remote Digital LoopbackBERT

�

BERT (Bit Error RateTest)

� � �

DTE Loopback �

Digital Test � � �

End-to-End Test � � � �

NOTE

Some tests require that specific device configuration parameters beset. So, although a test menu option may be enabled, it may not bepossible for the test to run. Refer to the device documentation fordetails on testing options.


5-8 January 1997 7800-A2-GB21-20

Accessing the Test Display from the Menu

To use the menu to access the displays from which you can set loopback modes or start patterntests:

1. Select a single proxied device symbol as it appears on an HP OpenView Windows submapif you intend to run any tests other than the Digital Test or End-to-End test. Select two(local and remote) device symbols if you intend to run the Digital or End-to-End test.

2. Use the menu selection Diagnose–>OneVision Device Mgmt: DCE Manager–>loopbackmode or pattern test. (Loopback modes or pattern tests inappropriate for the device(s) youhave selected are grayed out.) A test display appears, as described in Table 5-6.

3. Enter in the display the duration you want for the test and the number of the port on whichyou want the test to take place.

4. Click the Apply button to begin the test.

Clicking the Cancel button terminates the test and closes the display window.

NOTE

A device can only have one test running at any time.

Accessing the Test Display from the Command Line

To use the UNIX command line to access the displays from which you can set loopback modes orstart tests:

TYPE: /usr/OV/bin/att6700DevTest <test name> –target<selection name>

Where: test name is one of the following (described in Table 5-4):

• SelfTest – device self-test

• LB – loopback

• LBBERT – loopback BERT

• DigitalLB – digital loopback

• RDL – remote digital loopback

• RDLBERT – remote digital loopback BERT

• SendBERT – send BERT pattern

• DTELB – DTE loopback

• DigitalTest – digital test

• EndToEndTest – end-to-end test

• Abort – abort test started from the NMS front panel; see Aborting TestsStarted from the Front Panel



5-97800-A2-GB21-20 January 1997

Checking the Test Results

Test results are displayed automatically as they become available. The DCE Manager periodicallypolls for test results. You can manually request an update by pressing the Refresh button.

While a test is running, the proxied device health and status display (described in Chapter 3) showsTest Mode in its Alert field and the status color of the device symbol is salmon.

Table 5-6 shows the information displayed by the test display. Note that Table 5-6 shows all thefields related to proxied device testing. The displays for individual devices will be a subset of thesefields.

Table 5-6(1 of 2)

Proxied Device Test Display

Field Description

3550and3600

SeriesDevices

3800Series

Devices

3900Series

Devices

Device Name: Name of the device to test � � �

Remote Name: Name of the remote device to test. Only applicable forthe Digital Test and End-to-End Test.

� � �

Duration: Test duration in seconds � � �

Port Number: Port number being tested. Only applicable to multiportdevices and only supported for following tests:

• Remote Digital Loopback• Digital Loopback• DTE Loopback• BERT• Loopback BERT• Remote Digital Loopback BERT• Digital Test• End-To-End Test

� � �

Test Type: • Remote Digital Loopback• Self-Test• Loopback• Remote Digital Loopback• Digital Loopback• DTE Loopback• BERT• Loopback BERT• Remote Digital Loopback BERT• Digital Test• End-To-End Test

� � �


5-10 January 1997 7800-A2-GB21-20

Table 5-6(2 of 2)

Proxied Device Test Display

Field3900

SeriesDevices

3800Series

Devices

3550and3600

SeriesDevices

Description

Test Status: • Test Passed• Test Failed• Test Mode• Test Running• Test Aborted

� � �

Elapsed/TotalSeconds:

Total elapsed seconds that the test has been running � � �

Error Seconds: Count of the seconds in which an error has occurred � �

Total Bits/Blocks: Total bits/blocks tested � � �

Error Bits/Blocks: Count of the errored bits/blocks that have occurred � � �

Remote Elapsed/To-tal Seconds:

Total elapsed seconds that the test has been runningon the remote device

� � �

Remote ErrorSeconds:

Count of the seconds in which an error has occurredon the remote device

� �

Remote Total Bits/Blocks:

Total bits/blocks tested on the remote device � �

Remote Error Bits/Blocks:

Count of the errored bits/blocks that have occurred onthe remote device

�

Timeouts: Count of timeouts �

Aborting Tests Started from the Front Panel

You can abort tests started from a device’s front panel by using the menu selectionDiagnose–>OneVision Device Mgmt –>DCE Manager–>Abort Front Panel Test. Note that thismenu selection does not apply to tests started from the Front-Panel Emulator or other managementsystems.

6-17800-A2-GB21-20 January 1997

TroubleshootingOverview 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting 3100 Series Devices 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3100 Series Devices Troubleshooting Table 6-2. . . . . . . . . . . . . . . . . . . . . . . Problem with Management Link 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problem with Support Ports: COM and MODEM 6-5. . . . . . . . . . . . . . . . . . Problem with Device or Line 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Loopback Modes and Pattern Tests 6-6. . . . . . . . . . . . . . . . . . . . . . . . 3100 Series Device Traps 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting a 6700 Series NMS or Proxy Devices 6-13. . . . . . . . . . . . . . . . . 6700 Series NMS and Proxy Devices Troubleshooting Table 6-13. . . . . . . . . Troubleshooting Proxied Device Trap s 6-15. . . . . . . . . . . . . . . . . . . . . . . . . . Problem with Connection to 6700 Series NMS SNMP Proxy

Agent System 6-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking Line Quality 6-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problem with EIA or External Leads 6-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . Using Proxy Device Loopbacks and Pattern Tests 6-21. . . . . . . . . . . . . . . . . .

OverviewThis chapter identifies the types of problems that you may encounter with 3100 Series and proxieddevices. The chapter describes how you can use the loopback modes and pattern tests of the DCEManager to isolate the problem to the device or the line. The chapter also lists the traps that thedevices issue and what you can do when you receive one. The first part of the chapter discusses3100 Series devices; the second part discusses proxied devices.

The information contained in this chapter is available online through the menu selectionsHelp–>Index–>Tasks–>Troubleshooting 3100 Series Devices andHelp–>Index–>Tasks–>Troubleshooting 6700 Series Proxied Devices.

NOTE

HP OpenView classifies all application alerts (such as results fromaborting a loopback or pattern test or selecting Monitor–>OneVisionDevice Mgmt–>DCE Manager–>Rear Panel–>Update) as minoralerts (displayed as yellow in the HP OpenView Event Categorieswindow). The true severity is recorded in the Message portion of theHP OpenView Event Browser display.

6


6-2 January 1997 7800-A2-GB21-20

Troubleshooting 3100 Series DevicesThe following sections discuss how to use the functions of the DCE Manager to troubleshoot the3100 Series devices. Refer to the individual device manuals for more specific troubleshootinginformation.

3100 Series Devices Troubleshooting Table

Table 6-1 lists the ways you are notified of a problem with a 3100 Series device, the types of errorsor performance degradation that cause the notifications, and where to go to diagnose or isolate theproblem.

Table 6-1(1 of 3)

3100 Series Device Troubleshooting Table

Notification Problem Go To Section(s):

HP OpenView submap displays a 3100 Seriesdevice symbol in blue.

Connection between managementsystem and device has been lost.

Problem withManagement Link

and

Problem with SupportPorts: COM andMODEM

HP OpenView submap displays a 3100 Seriesdevice symbol in red.

One of the device interfaces is in analarm state.

Problem with Device orLine

The HP OpenView Event Categories display reportsthat a trap has been received.

If the trap is linkDown , indicating that one of theinterfaces is not functioning, the rear panel (Figure 1-6 in Chapter 1) displays the interfacesymbol in red, and the HP OpenView submapdisplays the device symbol in red.

Device has sent one of the followingtraps to the management system:

• AuthenticationFailure

• linkDown

• enterpriseClockFail(1)

• enterpriseSelfTestFail(2)

• enterpriseDeviceFail(3)

Traps

COM Port

The Operational Status field of the Device SummaryHealth and Status Dialog reports the COM interfaceas down .

Also, the rear panel displays the COM interfacesymbol in red.

Also, the HP OpenView submap displays the devicesymbol in red.

COM Port is in an alarm state. Problem with SupportPorts: COM andMODEM

Troubleshooting

6-37800-A2-GB21-20 January 1997

Table 6-1(2 of 3)


Notification Go To Section(s):Problem

MODEM Port

The Operational Status field of Device SummaryHealth and Status Dialog reports the MODEMinterface as down .

Also, the rear panel displays the MODEM interfacesymbol in red.


MODEM Port is in an alarm state. Problem with SupportPorts: COM andMODEM

Network T1 Interface

The Operational Status fields of the DeviceSummary Health and Status Dialog and the NetworkT1 Health and Status Dialog report the Network T1interface as down .

Also, the rear panel displays the Network T1interface symbol in red.


Network T1 interface is in an alarmstate.


The Line Status field of the Network T1 Health andStatus Dialog reports a problem.

Also, the rear panel displays the interface symbol inred.

Network T1 interface has experiencedone of the following:

• Loss of Signal

• Loss of Frame

• Yellow Alarm

• Alarm Indication Signal

• Excessive Error Rate


The Network T1 Performance Statistics dialog orgraph (Table 1-3) reports errors.

Network T1 interface experiences ahigh rate of performance-related errors:

• Errored Seconds

• Severely Errored Seconds

• Unavailable Seconds

• Controlled Slip Seconds

• Bursty Errored Seconds


The Test Code field of the Network T1 Health andStatus Dialog reports the test result No Sync or InSync with Bit Errors .

Pattern test monitor run on the NetworkT1 interface has failed.



6-4 January 1997 7800-A2-GB21-20

Table 6-1(3 of 3)


Notification Go To Section(s):Problem

DTE T1 Interface

The Operational Status fields of the DeviceSummary Health and Status Dialog and the DTE T1Health and Status Dialog report the interface asdown .

The rear panel displays the interface symbol in red.

HP OpenView submap displays the device symbolin red.

DTE T1 interface is in an alarm state. Problem with Device orLine

The line status field of the DTE T1 Health andStatus Dialog reports a problem.

The rear panel displays the interface symbol in red.

DTE T1 interfaces has experiencedone of the following:

• Loss of Signal

• Loss of Frame

• Yellow Alarm

• Alarm Indication Signal


Data Ports 1–4 Interface

The Operational Status fields of the DeviceSummary Health and Status Dialog and the DataPorts 1–4 Health and Status Dialog report theinterface as down .

The rear panel displays the Data Ports interfacesymbol in red.

HP OpenView submap displays the device symbolin red.

Data Ports 1–4 interface is in an alarmstate.


The Test Code field of the Data Ports 1–4 Healthand Status Dialog reports the test result No Sync orIn Sync with Bit Errors .

Pattern test monitor run on the DataPorts 1–4 interface has failed.


Troubleshooting

6-57800-A2-GB21-20 January 1997

Problem with Management Link

You can manage a 3100 Series device from HP OpenView through an Ethernet, leased-line, ordial-up connection. If the management connection is lost to a functional (green) device, the 3100 Series device symbol that appears on the HP OpenView submap turns blue and the lineconnected to it turns red. The colors of the interface symbols on the rear panel display correspondto their last known states. Note that an unknown (blue) state may be the norm if you are managinga device only periodically over a dial-up connection.

One possible reason for the loss of the management connection is a failure in the 3100 Seriesdevice. The individual device manuals provide a troubleshooting section that describes how todiagnose problems. The device manuals also describe how to run the device self-test. See alsoProblem with Support Ports: COM and MODEM.

Problem with Support Ports: COM and MODEM

The COM and MODEM interfaces of a 3100 Series device can be used to remotely manage adevice. If one of these interfaces is being used by HP OpenView to manage a 3100 Series deviceand that interface fails, the management link is lost, and the device symbol that appears on the HPOpenView submap turns blue and the line connected to the symbol turns red. If a COM orMODEM interface not being used to manage a device through HP OpenView fails, the devicesends a trap and the problem is reported to you in three ways:

• The operational status field of the Summary Health and Status Dialog (described in Chapter 3) reports the interface as down.

• The rear panel displays the COM or MODEM interface symbol in red.

• HP OpenView submap displays the device symbol in red.

The individual device manuals provide a troubleshooting section that describes how to diagnoseproblems. The device manuals also describe how to run the device self-test.

Problem with Device or Line

When the DCE Manager detects that one of the 3100 Series device interfaces is in a down (oralarm) state, the interface symbol on the rear-panel display turns red as does the device symbol thatappears on the HP OpenView submap. When the Network T1, DTE T1, or Data Ports 1–4interface is down, this state is reflected in the Operational Status field of the appropriate health andstatus dialog, as described in Chapter 3. The DCE Manager enables you to put these interfaces inloopback mode and run pattern tests to help you isolate the problem.

When you are notified of a problem with a particular interface, you should try to determinewhether the problem is the result of a failure of the device that reported the problem, a failure ofthe line, or a failure of a remote device. The sections that follow describe how you can use theloopback modes in combination with the pattern tests to do this. If you isolate a failure to a3100 Series device, you may want to run the device self-test, as described in the troubleshootingsection of the device manual. If you isolate a failure to the network or to a non-3100 Series device,you can take other corrective action (which is outside the scope of this manual).


6-6 January 1997 7800-A2-GB21-20


Loopback Modes

This section describes the loopback modes supported by 3100 Series devices that you can use introubleshooting.

Note that while an interface is in loopback mode, the other ports send all 1’s.

Line Loopback

The Line Loopback (LLB) mode loops the information received on the Network T1 interface backto the network as close to the network interface as possible. When used with a pattern test, thisloopback mode is useful for determining whether the problem is with the sending device or the T1facility. Figure 6-1 illustrates how you can use the LLB in conjunction with a pattern test (seePattern Tests) to isolate a problem. (Note that although 3100 Series devices are used in theexamples that follow, the loopback modes and pattern tests are defined in MIBs and so any devicethat supports the appropriate MIBs is able to go into loopback mode and send/monitor patterntests.)

In Figure 6-1, Device A is sending a known QRSS pattern out the Network T1 interface. (Device Asends a QRSS pattern when you select Diagnose–>OneVision: Device Mgmt: DCEManager–>Patterns–>Send QRSS Pattern.)

Device B is in LLB mode returning the pattern. (Device B is put in LLB mode locally or bysending it an LLB Up Code from Device A; see Network T1 Loopback Modes and Pattern Tests inChapter 5).

Device A monitors the returned information for errors. (Device A is put in monitor mode byselecting Diagnose–>OneVision: Device Mgmt: DCE Manager–>Patterns–>Monitor QRSSPattern). If Device A detects an error, it reports the error in the Network T1 Health and StatusDialog by setting the Test Code field to In Sync With Bit Errors (device is marginal) or Not inSync (device is down).

If Device A detects an error, the likelihood is that the problem is in the T1 facility and not withinany internal circuitry of Device A because it was able to send and monitor the pattern data. If thereare no errors reported, you can run the Payload Loopback test described in the next section todetermine whether the problem is caused by the CSU circuitry of remote device, Device B in ourexample. See Payload Loopback.

3100 Series DeviceSending/Monitoring

a QRSS Pattern

T1NETWORK

3100 SeriesDevice

in Loopback

DEVICE A DEVICE B

ÎÎÎÎÎÎ

Figure 6-1. Use of LLB and Pattern Test

Troubleshooting

6-77800-A2-GB21-20 January 1997

Payload Loopback

The Payload Loopback (PLB) mode loops the information received on the Network T1 networkinterface back to the network after it has passed through the receive and transmit framing section(i.e., the CSU) of the DSU/CSU. This loopback is useful for determining whether the problem iswith the T1 facility or in the circuitry of the remote 3100 Series device. Building on the exampleused in the previous section, if Device A does not detect an error as a result of a LLB test, but doesdetect an error as a result of a PLB test, the likelihood is that the error is in Device B. CompareFigure 6-2 and Figure 6-3.

LLB

DCEPort 1

DCEPort 2

CSU DSU

Network T1 DTE T1Interface Interface

Figure 6-2. Line Loopback (LLB)

DCEPort 1

DCEPort 2

CSU DSU

Network T1 DTE T1Interface PLB Interface

Figure 6-3. Payload Loopback (PLB)


6-8 January 1997 7800-A2-GB21-20

DTE Loopback

The DTE Loopback (DLB) performs an equivalent function on the DTE T1 interface that the LLBdoes on the Network T1 interface (see Figure 6-4). It is useful for isolating problems on the DTET1 line. For the DLB, a DTE device or test equipment must generate data to be looped back.

DCEPort 1

DCEPort 2

CSU DSU

Network T1 DTE T1Interface DLB

Interface

Figure 6-4. DLB Loopback

Repeater Loopback

The Repeater Loopback (RLB) performs an equivalent function to the PLB on the Network T1interface (see Figure 6-5). The exception is that the RLB loops the entire T1 data stream, whichincludes the data on the DTE T1 interface as well as the synchronous data ports. The RLB is usefulfor ensuring that all of the customer’s information is correct up to the point it is sent out theNetwork T1 interface (which helps indicate that the DSU/CSU is operational). For the RLB, aDTE device or test equipment must generate data to be looped back.

DCEPort 1

DCEPort 2

CSU DSU

Network T1 DTE T1Interface InterfaceRLB

Figure 6-5. RLB Loopback

Troubleshooting

6-97800-A2-GB21-20 January 1997

Data Channel Loopback

The Data Channel Loopback (DCLB) loops the data for a particular synchronous data port back tothe network interface after the information has passed all the way through the DSU/CSU (i.e., justbefore it is sent to the customer’s equipment, either through the Network T1 interface or the DTET1 interface, see Figure 6-6). It is useful for verifying the end-to-end integrity of a circuit for aparticular port.

DCEPort 1

DCEPort 2

CSU DSU


DCLB DCLB

Figure 6-6. Data Channel Loopback (DCLB) – V.54, Loop 2

Data Terminal Loopback

The Data Terminal Loopback (DTLB) loops the data for a particular synchronous data port back tothe port just before it is combined with the rest of the T1 data stream (see Figure 6-7). It is usefulfor both isolating errors to the DTE equipment connected to the DSU/CSU and ensuring that thedata for the port is being received/transmitted correctly by the DSU/CSU.

DCEPort 1

DCEPort 2

CSU DSU


Figure 6-7. Data Terminal Loopback (DTLB) – V.54, Loop 3

As described in the test menus of Chapter 5, Using Loopback Modes and Pattern Tests, the remoteloopback Send V.54 Up Code and Send FT1 Up Code put a remote device in loopback mode, andSend V.54 Down Code and Send FT1 Down Code take a remote device out of loopback mode. Youcan use these codes in troubleshooting, as described in Pattern Tests.


6-10 January 1997 7800-A2-GB21-20

Use of the Loopback Up Codes and Down Codes

The remote loopback up codes (which put a remote device in loopback mode) and down codes(which take a remote device out of loopback mode) are in-band codes that allow remote control ofa device. The loopback modes, as well as the pattern tests, are defined in MIBs, and so any devicethat supports the appropriate MIBs is able to go into loopback mode and send/monitor pattern tests.The LLB up code invokes a LLB in the remote unit while the LLB down code terminates theremote LLB. The Send V.54 Up/Down and FT1 Up/Down perform a similar function, but are onlysent on the DS0s associated with a particular data port and will control the remote operation of theDCLB Loopback.

The up and down codes are useful for performing tests from one end of a circuit. The followingexample illustrates the use of the codes. You would:

1. Send an LLB Up Code from the local 3100 Series device to a remote DSU/CSU. Theremote DSU/CSU goes into line loopback.

2. Send a QRSS pattern test from the local 3100 Series device. The remote DSU/CSU willreturn the QRSS pattern (because it is in loopback mode).

3. Start a monitor QRSS pattern test in the local 3100 Series device and monitor the result todetermine whether the circuit is operational (In Sync ), marginal (In Sync With BitErrors ), or completely down (Not in Sync). (The Network T1 Health and Status Dialogdescribed in Chapter 3 reports the results of the pattern test.)

4. Terminate sending and monitoring the QRSS pattern tests.

5. Send LLB Down Code from the local 3100 Series device to the remote DSU/CSU. RemoteDSU/CSU terminates the line loopback.

Pattern Tests

This section describes how you can send and monitor pattern tests and how you can use the tests introubleshooting.

Troubleshooting

6-117800-A2-GB21-20 January 1997

QRSS, 511, and 1-in-8 Patterns

The pattern tests (both QRSS and 511) enable a 3100 Series device either to send or monitor aknown bit pattern. These tests generate industry-standard, MIB-defined bit patterns that can beused to determine whether information is being correctly transmitted across a circuit. Thesepatterns can be sent by the Network T1 and Data Ports interfaces. Chapter 5, Using LoopbackModes and Pattern Tests, describes how to send and monitor patterns.

You can send a 1-in-8 pattern out of the Network T1 Interface, but you cannot monitor it. The1-in-8 pattern is a low-density bit test so that errors of the sort that would be detected by a 1-in-8pattern will likely appear in the line status fields of the Network T1 Health and Status Dialog or inthe Network T1 Performance Statistics Dialog (Chapter 3).

As Figures 6-8 and 6-9 illustrate, you can use a pattern test alone to test both ends of a circuit oruse a combination of a pattern test and a loopback to test one end of a circuit. Figure 6-8 shows aconfiguration that tests the sending circuitry and the network. Figure 6-9 shows a configurationthat tests the sending circuitry, the network, and the receiving circuitry.

DSU/CSUSending a QRSS

Test Pattern

T1NETWORK

DSU/CSUMonitoring a QRSS

Test Pattern

DEVICE A DEVICE B

Figure 6-8. Pattern Test – Testing One End of a Circuit

DSU/CSUSending/Monitoring

a QRSS TestPattern

T1NETWORK

DSU/CSUin Loopback(LLB or PLB)

DEVICE A DEVICE B

ÎÎÎÎ

Figure 6-9. Pattern Test – Testing Both Ends of a Circuit


6-12 January 1997 7800-A2-GB21-20

3100 Series Device Traps

A 3100 Series device can send the traps listed in Table 6-2 to the HP OpenView managementsystem. For this to occur, configure the device to send traps. If you manage the device through adial-up connection, set your management system modem to auto-answer. Refer to the devicemanual for instructions on configuring a device so that it sends traps to an appropriate trapmanager, in this case, HP OpenView.

When a connection is established as a result of an incoming trap, ensure that either the device orthe PPP software is configured to terminate the connection after the trap has been sent (normallythe default setting). This is an important point. You could inadvertently incur large connectioncharges.

Table 6-23100 Series Device Traps

General Traps

Trap Definition

warmStart This trap signifies that the unit has just reinitialized itself. It is sent afterthe unit has been reset, either because of a reset command or as theresult of a power disruption.

AuthenticationFailure This trap signifies that the unit is the addressee of a SNMP protocolmessage that is not properly authenticated.

Enterprise Specific Traps

Trap Definition

enterpriseClockFail(1) This trap signifies that a failure of the currently configured master clocksource for the DSU/CSU has been detected.

enterpriseSelfTestFail(2) This trap signifies that a hardware failure of the unit was detected aspart of the unit’s self-test.

enterpriseDeviceFail(3) This trap signifies that an internal device failure has been detected bythe operating software for the unit.

Link Traps

Trap Definition

linkUp This trap signifies that the unit recognizes that one of communicationinterfaces has come up.

linkDown This trap signifies that the unit recognizes a failure in one of thecommunication interfaces.

Troubleshooting

6-137800-A2-GB21-20 January 1997

Table 6-3 suggests some possible actions to take if you a receive a trap that indicates a problemwith a 3100 Series device.

Table 6-3Troubleshooting 3100 Series Device Traps

Trap Action

AuthenticationFailure Check that you are using the correct community name.

enterpriseClockFail(1) Check the T1 facility by running the pattern tests described in thepreceding sections.

enterpriseSelfTestFail(2) Refer to the device manual to determine the exact nature of the failure.

enterpriseDeviceFail(3) Contact your service representative.

linkDown Check the T1 facility by running the pattern tests described in thepreceding sections.

Troubleshooting a 6700 Series NMS or Proxy DevicesThe following sections discuss how to use the functions of the DCE Manager to troubleshoot the6700 Series NMS and proxied devices. Refer to the COMSPHERE 6700 Series NetworkManagement System User’s Guide and the individual device manuals for more specifictroubleshooting information.

6700 Series NMS and Proxy Devices Troubleshooting Table

Table 6-4 lists the ways you are notified of a problem with a 6700 Series NMS or proxied device,the types of errors or performance degradation that cause the notifications, and where to go todiagnose or isolate the problem.


6-14 January 1997 7800-A2-GB21-20

Table 6-4Proxied Device Troubleshooting Table

Notification Problem Go To Section(s):

HP OpenView submap displays a 6700Series proxy agent symbol in blue.

Connection between HP OpenView andsystem running the 6700 Series NMSSNMP Proxy Agent has been lost.

Problem with Connection to6700 Series NMS SNMPProxy Agent System

The HP OpenView Events Categoriesdisplay trap log file has recorded a trapissued by a proxied device.

Device has sent one of the following trapsto the management system:

• Device Fail

• Out of Threshold

• Facility Alarm

• External Alarm

• Streaming Terminal

• DTE Alarm

• Sub-normal Speed

• Primary Channel Interrupt

• Non-answering Modem

• Short Holding Time Modem

• Sub-tree Truncation

• TDM Failure; good APL

• Trib Timeout

• No Response

Troubleshooting ProxiedDevice Traps

The proxied device symbol is red. The device is in an alarm state. Troubleshooting ProxiedDevice Traps

Circuit Quality Table reports poor circuitquality.

Poor line conditions. Checking Line Quality

EIA Status or External Leads info is bad. Device failure. Problem with EIA or ExternalLeads

Test results displayed by the ProxiedDevice Test Display report errors.

Failure related to the local device, lineconditions, or a remote device.

Using Proxy DeviceLoopbacks and Pattern Tests

Troubleshooting

6-157800-A2-GB21-20 January 1997

Troubleshooting Proxied Device Traps

The COMSPHERE 6700 Series NMS SNMP Proxy Agent sends the traps listed inTables 6-5—6-7 to the HP OpenView management system on behalf of proxied devices. For this tooccur, configure the proxy agent to send traps. If you manage the device through a dial-upconnection, set your management system modem to auto-answer. Refer to the COMSPHERE 6700 Series Network Management System User’s Guide for instructions on configuring a device sothat it sends traps to an appropriate trap manager, in this case, HP OpenView. Refer to your modemdocumentation for information on configuring your modem so that it automatically answersincoming calls.

The Primary Alert Traps listed in Table 6-5 are the only traps that indicate a problem with thefunctioning of the device. The others involve security and clear status. Table 6-8 describes thelikely cause of Primary Alert Traps and the actions you can take when you receive one.

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Table 6-5(1 of 2)

Proxied Device Primary Alert TrapsÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

TrapNumber

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Primary Alert Traps

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

3550 and 3600Series Devices


3800 SeriesDevices


3900 Series DevicesÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁ

1

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Device Failure

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�


�


2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Configuration Change Notify ÁÁÁÁÁÁÁÁÁÁÁÁ

� ÁÁÁÁÁÁÁÁÁÁÁÁ


�


3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Test ModeÁÁÁÁÁÁÁÁÁÁÁÁ

�ÁÁÁÁÁÁÁÁÁÁÁÁ


�

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

DisabledÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�


�



Out of Threshold/VF Threshold Exceeded ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Facility Alarm ÁÁÁÁÁÁÁÁÁÁÁÁ



�



External AlarmÁÁÁÁÁÁÁÁÁÁÁÁ

�

ÁÁÁÁÁÁÁÁÁÁÁÁ

�


�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


Streaming TerminalÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�


�



Access Security ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Dial Backup Active for APL ÁÁÁÁÁÁÁÁÁÁÁÁ



�



DTE AlarmÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�




Sub-normal Operating SpeedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�


�



Primary Channel Interrupted ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Firmware DownloadingÁÁÁÁÁÁÁÁÁÁÁÁ



�



Make Busy ModeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�


�



Service Line ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Non-answering Modem ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Short Holding Time ModemÁÁÁÁÁÁÁÁÁÁÁÁ



�



Sub Tree TruncationÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�



�


6-16 January 1997 7800-A2-GB21-20

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Table 6-5(2 of 2)

Proxied Device Primary Alert Traps


3900 Series Devices


3800 SeriesDevices


3550 and 3600Series Devices


Primary Alert TrapsÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

TrapNumber



TDM Failure/Good APL Line ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Tributary TimeoutÁÁÁÁÁÁÁÁÁÁÁÁ


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ



Dial ToneÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁ23 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Redundant Power Supply ÁÁÁÁÁÁÁÁÁÁÁÁ




No Response ÁÁÁÁÁÁÁÁÁÁÁÁ



�

Troubleshooting

6-177800-A2-GB21-20 January 1997

Table 6-6 lists the System Security Event traps.

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Table 6-6Proxied Device System Security Event Traps

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

TrapNumber


System Security Event Traps


3550 and 3600 Series

Devices

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

3800 SeriesDevices


3900 SeriesDevices



VF Login OK ÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�



User Login OK ÁÁÁÁÁÁÁÁÁÁÁÁ



�



User Login Rejected – Retry FailedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�



104


User Login Rejected – Password Timeout



�


�



User Login Aborted – Line Disconnected ÁÁÁÁÁÁÁÁÁÁÁÁ



�



VF Login Rejected – Password InvalidÁÁÁÁÁÁÁÁÁÁÁÁ



�



VF Login Rejected – Password TimeoutÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�


�



VF Login Aborted – Line Disconnected ÁÁÁÁÁÁÁÁÁÁÁÁ



�



User Login OK – Multiple Password Retries ÁÁÁÁÁÁÁÁÁÁÁÁ



�



User ID and Password Combination InvalidÁÁÁÁÁÁÁÁÁÁÁÁ



�



Invalid User ID – Password Valid for DeviceÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�


�



Invalid Access Time ÁÁÁÁÁÁÁÁÁÁÁÁ



�


113 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

User Login Hack – Multiple Sequential PasswordRetries



�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�



Device Security Table Invalid ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Security Download FailedÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�

ÁÁÁÁÁÁÁÁÁÁÁÁ�ÁÁÁÁÁ



Front Panel ModificationÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�


�


6-18 January 1997 7800-A2-GB21-20

Table 6-7 lists the Primary Alert Clear Notifications.

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Table 6-7Proxied Device Primary Alert Clear Notifications

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

TrapNumber


Primary Alert Clear Notifications


3550 and 3600 Series

Devices

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

3800 SeriesDevices


3900 SeriesDevices



Streaming Terminal Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ

� ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�



Device Failure Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ

�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�



Configuration Change Notify ClearedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�



203


Test Mode Cleared


�


�


�



Disabled Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Out of Threshold/VF Threshold ExceededCleared


�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�



Facility Alarm ClearedÁÁÁÁÁÁÁÁÁÁÁÁ



�



External Alarm ClearedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�



209


Access Security Cleared



�


�



Dial Backup Active for APL Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ



�



DTE Alarm ClearedÁÁÁÁÁÁÁÁÁÁÁÁ



�



Sub-normal Operating Speed ClearedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�


�



Primary Channel Interrupted Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Firmware Downloading Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Make Busy Mode ClearedÁÁÁÁÁÁÁÁÁÁÁÁ

ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�

ÁÁÁÁÁÁÁÁÁÁÁÁ�ÁÁÁÁÁ



Service Line ClearedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


�


�



Non-answering Modem Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Short Holding Time Modem Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ



�



Sub Tree Truncation ClearedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�




220


TDM Failure Cleared/Good APL Line Cleared


�


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ�ÁÁÁÁÁ



Tributary Timeout ClearedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ


Dial Tone Cleared ÁÁÁÁÁÁÁÁÁÁÁÁ



ÁÁÁÁÁ223ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

Redundant Power Supply ClearedÁÁÁÁÁÁÁÁÁÁÁÁ





No Response ClearedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ

�


�


�

Troubleshooting

6-197800-A2-GB21-20 January 1997

Table 6-8 suggests some actions to take if you a receive a Primary Alert Trap that indicates aproblem with a proxied device.

Table 6-8Troubleshooting Proxied Device Traps

Trap Action

Device Failure The device failed its self-test. A serious failure has occurred in the hardware or firmware.Contact your service representative.

Out of Threshold/VFThreshold Exceeded

One or more of the analog parameter thresholds have been exceeded. The probablecause is poor line conditions or improper threshold settings. Thresholds may be setthrough the device front panel as described in the individual device manuals. SeeChecking Circuit Quality.

Facility Alarm A severe data transport problem has occurred due to poor line conditions. No signal or avery poor signal is being received. See Checking Circuit Quality.

External Alarm An alarm has been detected on the alarm lead. Troubleshoot whatever has sent the alarm.

Streaming Terminal The modem is in a antistreaming condition. The RTS input to the modem was held ON fora period exceeding the time selected by the RTS Antistream configuration option. SeeProblem with EIA or External Leads.

DTE Alarm One or more of the DTE signals are in alarm mode. See Problem with EIA or ExternalLeads.

Sub-normal OperatingSpeed

Due to poor line conditions, the modem’s transmit rate is below the configured rate. SeeChecking Circuit Quality.

Primary Channel Interrupted The primary channel is being used for diagnostics or other device related functions ortests. It is not currently available to carry user data. Retry after the tests have concluded.

Non-answering Modem The modem is in a non-answering mode. Reconfigure if this is not the desiredconfiguration.

Short Holding-time Modem The modem’s dial hold time has been shortened. Reconfigure if this is not the desiredconfiguration.

Sub-Tree Truncation Downstream health and status information has been truncated because it overflowedsystem limits. There is a large amount of health and status information in the subnetwork.This information can be recovered by sending device health and status commands tospecific modems.

TDM Failure The TDM has failed a self-check or is disabled. Check configuration options. If configuredcorrectly, the cause is a hardware problem. Contact your service representative.

Tributary Timeout The tributary device is not responding to diagnostic polls. The device is powered off, hasfailed, or may have had its diagnostic address changed. Another possible cause is thatcircuit quality is poor. Check the operational status and configuration of the device. Checkcircuit quality as described in Circuit Quality Table in Chapter 3.

No Response The device is not responding to diagnostic polls or commands. The device is powered off,has failed, or may have had its diagnostic address changed. Check the operational statusand configuration of the device. Check cabling/connection to Network ManagementSystem.


6-20 January 1997 7800-A2-GB21-20

Problem with Connection to 6700 Series NMS SNMP Proxy Agent System

Your HP OpenView management system can be connected to a system running the 6700 SeriesNMS SNMP Proxy Agent through an Ethernet (using a router or LAN adapter), leased-line, ordial-up connection. If this management connection is lost, the proxy agent symbol that appears onthe HP OpenView submap turns from green to blue and the line connected to it turns red. Thisoccurs either because there is a problem with the connection between HP OpenView and the proxyagent, or because there is a problem with the proxy agent software itself. Check the connection byusing the HP OpenView menu selection Diagnose–>Network Connectivity–>Demand Poll. If thepoll is unsuccessful, check the integrity of your communication hardware and software; also checkthe status of the machine running the proxy agent. If the poll is successful, check that the proxyagent is still operating correctly.

Checking Circuit Quality

If the Circuit Quality Table display (described in Chapter 3) indicates poor circuit quality or youreceive a Primary Alert Trap related to circuit quality (Out of Threshold, Facility Alarm,Sub-normal Operating Speed), check the integrity of your data link service. If the data link appearsto be operating properly, determine that the problem is not in the local device or remote device byperforming local and remote loopback tests (described in Using Proxy Device Loopbacks andPattern Tests. If a problem appears in the local device, run the device’s self-test (as described inChapter 5) to further isolate the problem.

Circuit quality may be improved by lowering a device’s operating speed and threshold settings.

Problem with EIA or External Leads

If the EIA Status or External Leads displays (described in Chapter 3) indicate an improper signalstate or you receive a Primary Alert Trap related to signal states (Streaming Terminal or DTEAlarm), perform a device self-test to isolate the problem.

Troubleshooting

6-217800-A2-GB21-20 January 1997

Using Proxy Device Loopbacks and Pattern Tests

The loopback modes and pattern tests for the proxied devices perform essentially the samefunctions as do the loopback modes and pattern tests for the 3100 Series devices. They enable youto test the internal circuitry of a local device and use remote loopbacks and pattern tests to test theintegrity of remote devices and lines. One significant difference is that the Digital Test andEnd-to-End Test for proxied devices combine a loopback mode and pattern test into a singleoperation, whereas for 3100 Series devices you must set the loopback mode and then issue apattern test in separate steps.

Table 5-4 in Chapter 5 provides a description of the loopback modes and pattern tests. Refer to theCOMSPHERE 6700 Series Network Management System User’s Guide for a more completeexplanation of the tests.

A-17800-A2-GB21-20 January 1997

Dialog MIB ValuesOverview A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3100 Series Devices Dialogs A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Rear-Panel Status Colors A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identity Dialog A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Summary Dialog A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network T1 Health and Status Dialog A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . DTE T1 Health and Status Dialog A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Ports Health and Status Dialog A-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network T1 Performance Statistics Dialog A-5. . . . . . . . . . . . . . . . . . . . . . . . Channel Configuration Dialog A-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy Device Configuration Area Dialog A-6. . . . . . . . . . . . . . . . . . . . . . . . . Network T1 Configuration Dialog A-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DTE T1 Configuration Dialog A-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Ports Configuration Dialog A-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network T1 Loopback Modes and Pattern Tests A-9. . . . . . . . . . . . . . . . . . . . DTE T1 Loopback Modes A-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Ports Loopback Modes and Pattern Tests A-10. . . . . . . . . . . . . . . . . . . . .

Proxied Device and Proxied NMS Dialogs A-11. . . . . . . . . . . . . . . . . . . . . . . . . . Device Health and Status Display A-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Call Directory Display A-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Identity Display A-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NMS System Features Display A-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NMS Administration Display A-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Administration Display A-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Circuit Quality A-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Commands A-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device EIA Status Display A-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device External Leads Display A-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Loopback Modes and Pattern Tests A-19. . . . . . . . . . . . . . . . . . . . . . . . Device Test Display A-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OverviewThis appendix lists the MIB objects that the DCE Manager uses to generate the fields that appearin its dialogs and displays. The first part of the chapter discusses the dialogs of 3100 Seriesdevices; the second part discusses the displays of the proxy agent and proxied devices.

3100 Series Devices DialogsThis sections describes the MIB objects related to 3100 Series devices that the DCE Manager readsand writes using the SNMP Get and Set commands.

Rear-Panel Status Colors

The MIB II Interface Group object ifOperStatus is used to generate the rear-panel status colors (seeChapter 1).

A


A-2 January 1997 7800-A2-GB21-20

Identity Dialog

Table A-1 shows the MIB objects used to generate the Identity Dialog (see Chapter 4).

Table A-13100 Series Device Identity

Field MIB Object MIB

Description: sysDescr MIB II – System Group

Model: sysDescr MIB II – System Group

Software Release: sysDescr MIB II – System Group

Hardware CCA1: sysDescr MIB II – System Group

Hardware CCA2: sysDescr MIB II – System Group

Serial Number: sysDescr MIB II – System Group

Up Time: sysUpTime MIB II – System Group

Contact: sysContact MIB II – System Group

Name: sysName MIB II – System Group

Hostname: HP OpenView generated n/a

Location: sysLocation MIB II – System Group

Network T1 Description: ifDescr (of Network T1 interface) MIB II – Interface Group

DTE T1 Description: ifDescr (of DTE T1 interface) MIB II – Interface Group

Port <n> Description: ifDescr (of Port <n> interface) MIB II – Interface Group

COM Description: ifDescr (of COM interface) MIB II – Interface Group

MODEM Description: ifDescr (of MODEM interface) MIB II – Interface Group

Device Summary Dialog

The MIB object ifOperStatus is used to generate the fields of the device summary Health andStatus Dialog (see Chapter 3).

Dialog MIB Values

A-37800-A2-GB21-20 January 1997

Network T1 Health and Status Dialog

Table A-2 shows the MIB objects used to generate the Network T1 Health and Status Dialog (seeChapter 3).

Table A-2Network T1 Health and Status Dialog


Operational Status: ifOperStatus MIB II – Interface Group

Line Status: dsx1LineStatus DS1/E1 MIB – Near End Group

Loopback Status: dsx1LoopbackConfig DS1/E1 MIB – Near End Group

Send Code Status: dsx1SendCode DS1/E1 MIB – Near End Group

Monitor Status: ifExtnsTestType Generic Interface MIB Extension – Generic Interface Test Table

Test Result: ifExtnsTestResult Generic Interface MIB Extension – Generic Interface Test Table

Test Code: ifExtnsTestCode Generic Interface MIB Extension – Generic Interface Test Table

DTE T1 Health and Status Dialog

Table A-3 shows the MIB objects used to generate the DTE T1 Health and Status Dialog (seeChapter 3).

Table A-3DTE T1 Health and Status Dialog


Operational Status: ifOperStatus MIB II – System Group

Line Status: dsx1LineStatus DS1/E1 MIB – Near End

Loopback Status: dsx1LoopbackConfig DS1/E1 MIB – Near End Group


A-4 January 1997 7800-A2-GB21-20

Data Ports Health and Status Dialog

Table A-4 shows the MIB objects used to generate the Data Ports Health and Status Dialog (seeChapter 3).

Table A-4Data Ports 1–4 Health and Status Dialog


Operational Status: ifOperStatus MIB II – System Group

Test Status: ifExtnsTestType Generic Interface MIB Extension – Generic Interface Test Table

Test Result: ifExtnsTestResult Generic Interface MIB Extension – Generic Interface Test Table

Test Code: ifExtnsTestCode Generic Interface MIB Extension – Generic Interface Test Table

DTR: rs232InSigState(rs232InSigName == dtr)

RS 232-like MIB – Input Signal Table

CTS: rs232OutSigState(rs232OutSigName == cts)

RS 232-like MIB – Output Signal Table

RTS: rs232InSigState(rs232InSigName == rts)


DSR: rs232OutSigState(rs232OutSigName == dsr)


Dialog MIB Values

A-57800-A2-GB21-20 January 1997

Network T1 Performance Statistics Dialog

Table A-5 shows the MIB objects used to generate the Network T1 Performance Statistics Dialog(see Chapter 3).

Table A-5Network T1 Performance Statistics Dialog


Time Elapsed: dsx1TimeElapsed DS1/E1 MIB – Near End Group

Valid Intervals: dsx1ValidIntervals DS1/E1 MIB – Near End Group

Current Interval:Errored SecondsSev Err SecondsUnavail SecondsCntrl Slip SecondsBursty SecondsBursty Errored Seconds

dsx1CurrentESsdsx1CurrentSESsdsx1CurrentUASsdsx1CurrentCSSsdsx1CurrentBESsdsx1CurrentBESs

DS1/E1 MIB – Near End Group

Beginning Interval dsx1IntervalNumber = 1–96 DS1/E1 MIB – Near End Group

Ending Interval dsx1IntervalNumber = 1–96 DS1/E1 MIB – Near End Group

15 Min Interval:Interval numberErrored SecondsSev Err SecondsUnavail SecondsCntrl Slip SecondsBursty SecondsBursty Errored Seconds

dsx1IntervalNumber = 1–96dsx1IntervalESsdsx1IntervalSESsdsx1IntervalUASsdsx1IntervalCSSsdsx1IntervalBESsdsx1IntervalBESs


Total: 24 HoursErrored SecondsSev Err SecondsUnavail SecondsCntrl Slip SecondsBursty SecondsBursty Errored Seconds

dsx1CurrentESsdsx1CurrentSESsdsx1CurrentUASsdsx1CurrentCSSsdsx1CurrentBESsdsx1CurrentBESs



A-6 January 1997 7800-A2-GB21-20

Channel Configuration Dialog

Table A-6 shows the MIB objects used to generate the Channel Configuration Dialog(see Chapter 4).

Table A-63100 Series Device Channel Configuration


Network T1 Channels:1 2 3. . .22 23 24

dsx1FracTable(for T1 interface)

DS1/E1 MIB – Fractional Group

DTE T1 Channels:1 2 3. . .22 23 24

dsx1FracTable(for DTE T1 interface)

DS1/E1 MIB – Fractional Group

Copy Device Configuration Area Dialog

Table A-7 shows the MIB objects used to generate the Copy Device Configuration Area Dialog(see Chapter 4).

Table A-73100 Series Device User Configuration


User Configuration: devConfigAreaCopy ATTDCE MIB

Dialog MIB Values

A-77800-A2-GB21-20 January 1997

Network T1 Configuration Dialog

Table A-8 shows the MIB objects used to generate the Network T1 Configuration Dialog (seeChapter 4).

Table A-8Network T1 Configuration


Interface Type: ifType MIB II – Interface Group

Speed (bps): ifSpeed MIB II – Interface Group

Framing: dsx1LineType DS1/E1 MIB – Near End Group

Line Coding: dsx1LineCoding DS1/E1 MIB – Near End Group

Circuit: dsx1CircuitIdentifier DS1/E1 MIB – Near End Group

Signal Mode: dsx1SignalMode DS1/E1 MIB – Near End Group

Tx Clock Source: dsx1TransmitClockSource DS1/E1 MIB – Near End Group

Facilities Data Link: dsx1Fdl DS1/E1 MIB – Near End Group

DTE T1 Configuration Dialog

Table A-9 shows the MIB objects used to generate the DTE T1 Configuration Dialog (see Chapter 4).

Table A-9DTE T1 Configuration




Framing: dsx1LineType DS1/E1 MIB – Near End Group

Line Coding: dsx1LineCoding DS1/E1 MIB – Near End Group

Signal Mode: dsx1SignalMode DS1/E1 MIB – Near End Group

Tx Clock Source: dsx1TransmitClockSource DS1/E1 MIB – Near End Group

Facilities Data Link: dsx1Fdl DS1/E1 MIB – Near End Group


A-8 January 1997 7800-A2-GB21-20

Data Ports Configuration Dialog

Table A-10 shows the MIB objects used to generate the Data Ports Configuration Dialog (seeChapter 4).

Table A-10Data Ports 1–4 Configuration




Port Type: rs232PortType RS 232-like MIB – Generic Port Table

Clock Source: rs232SyncPortClockSource RS 232-like MIB – Synchronous Port Table

Dialog MIB Values

A-97800-A2-GB21-20 January 1997

Network T1 Loopback Modes and Pattern Tests

Table A-11 shows the MIB objects that are set when you select loopback modes and pattern tests(see Chapter 5).

Table A-11Network T1 Loopback Modes and Pattern Tests

Menu ItemSet dsx1SendCode(DS1/E1 MIB – Near

End Group) to:

Setdsx1LoopbackConfig(DS1/E1 MIB – Near

End Group) to:

Set ifExtnsTestType(Generic Interface

MIB – GenericInterface Test

Table) to:

Remote Loopback –> Send LLBUp Code

dsx1SendLineCode

Remote Loopback –> Send LLBDown Code

dsx1SendResetCode

Loopback –> Abort dsx1NoLoop

Loopback –> Start LineLoopback

dsx1LineLoop

Loopback –> Start PayloadLoopback

dsx1PayloadLoop

Patterns –> Abort Send dsx1SendNoCode

Patterns –> Send QRSSPattern

dsx1SendQRS

Patterns –> Send 1 in 8 dsx1SendOtherTestPattern

Patterns –> Abort Monitor noTest

Patterns –> Monitor QRSSPattern

testMonQRSS


A-10 January 1997 7800-A2-GB21-20

DTE T1 Loopback Modes

Table A-12 shows the MIB objects that are set when you select a loopback mode (see Chapter 5).

Table A-12DTE T1 Loopback Modes

Menu Item Set dsx1LoopbackConfig (DS1/E1 MIB – Near End Group) to:

Loopback –> Abort dsx1Noloop

Loopback –> Start DTE Loopback dsx1LineLoop

Loopback –> Start Repeater Loopback dsx1PayloadLoop

Data Ports Loopback Modes and Pattern Tests

Table A-13 shows the MIB objects that are set when you select loopback modes and pattern tests(see Chapter 5).

Table A-13Data Ports 1–4 Loopback Modes and Pattern Tests

Menu Item Set ifExtnsTestType (Generic Interface MIB – Generic Interface Test Table) to:

Remote Loopback –> Send V.54 Up Code testSendV54Up

Remote Loopback –> Send V.54 Down Code testSendV54Down

Remote Loopback –> Send FT1 Up Code testSendFT1Up

Remote Loopback –> Send FT1 Down Code testSendFT1Down

Loopback –> Abort noTest

Loopback –> Start Data Channel Loopback testFullDuplexLoopBack

Loopback –> Start Data Terminal Loopback testLoopDTLB

Patterns –> Abort Send noTest

Patterns –> Send QRSS Pattern testSendQRSS

Patterns –> Send 511 Pattern testSend511

Patterns –> Abort Monitor noTest

Patterns –> Monitor QRSS Pattern testMonQRSS

Patterns –> Monitor 511 Pattern testMon511

Dialog MIB Values

A-117800-A2-GB21-20 January 1997

Proxied Device and Proxied NMS DialogsThis section describes the 6700 Series NMS SNMP Proxy Agent MIB objects that the DCEManager reads and writes using the SNMP Get and Set commands.

Device Health and Status Display

Table A-14 shows the MIB objects used to generate the Device Health and Status Display (seeChapter 3).

Table A-14Device Health and Status Display

Field 6700 Series Device MIB – Status Group

Connected Device: devStatusConnectedDevice

Connect Time: devStatusConnectTime

Alerts: devStatusAlert

State: devStatusState

Speed (bps): devStatusSpeed

Control–Trib: devStatusCtrlTrib

Config Type: devStatusConfigType

Polling State: devStatusPollingState

Device Call Directory Display

Table A-15 shows the MIB objects used to generate the Device Call Directory Display (seeChapter 4).

Table A-15Device Call Directory Display

Field 6700 Series Device MIB – Call Directory Group

Table: IndexPurposeIDPhone Number

devCallDirIndexdevCallDirPurposedevCallDirIddevCallDirPhoneNumber

<repeat the above for the next entry>


A-12 January 1997 7800-A2-GB21-20

Device Identity Display

Table A-16 shows the MIB objects used to generate the Device Identity Display (see Chapter 3).

Table A-16Device Identity Display

Field 6700 Series Device MIB – Identity Group

Model: devIdentityModel

Line Speed: devIdentityLineSpeed

Software Version: devIdentitySoftwareVersion

Serial Number: devIdentitySerialNumber

Application Module ID: devIdentityApplMoudleID

Access Module ID: devIdentityAccessModule

Restoral Option: devIdentityRestoralOption

Configuration: devIdentityConfiguration

International Strap: devIdentityInternationalStrap

Hardware Part Number devIdentityHwPartNumber

Software Part Number devIdentitySwPartNumber

Option 1: devIdentityOption1






Dialog MIB Values

A-137800-A2-GB21-20 January 1997

NMS System Features Display

Table A-17 shows the MIB objects used to generate the System Features Display (see Chapter 3).

Table A-17System Features Display

Field 6700 Series NMS MIB – System Features Group

IndexNameVersionSerial Number

nmsSystemFeatureIndexnmsSystemFeatureNamenmsSystemFeatureVersionnmsSystemFeatureSerial

<repeat the above for the next feature>

NMS Administration Display

Table A-18 shows the MIB objects used to generate the NMS Administration Display (seeChapter 3).

Table A-18NMS Administration Display

Display Label 6700 Series NMS MIB – Administration Group

NMS Name: nmsAdminName

Location: nmsAdminLocation

Contact 1: nmsAdminContact1

Contact 2: nmsAdminContact2

Read Community: nmsAdminReadCommunity

Base Read Community: nmsAdminBaseReadCommunity

Base Write Community: nmsAdminBaseWriteCommunity


A-14 January 1997 7800-A2-GB21-20

Device Administration Display

Table A-19 shows the MIB objects used to generate the Proxied Device Administration Display(see Chapter 4).

Table A-19Device Administration Display

Field 6700 Series Device MIB – Administration Group

Device Name: devAdminName

Device Address: devAdminAdpAddress

Model Type: devAdminModelType

Site: devAdminSite

Cabinet: devAdminCabinet

Carrier: devAdminCarrier

Carrier Slot: devAdminCarrierSlot

Circuit Name: devAdminCircuitName

Contact 1: devAdminContact1

Contact 2: devAdminContact2

Comment: devAdminComment

DbmOption: Dial backup module option installed

MsdOption: Modem-sharing device option installed

McmpOption: Multichannel multipoint option installed

TdmOption: Time-division multiplexer option installed

Dialog MIB Values

A-157800-A2-GB21-20 January 1997

Device Circuit Quality

Table A-20 show the MIB objects used to generate the device Circuit Quality Table (seeChapter 3).

Table A-20(1 of 2)

Proxy Device Circuit Quality Dialog (read-only)

Field 6700 Series Device MIB – Circuit Quality Group

Receive Level Validity: devCirQualReceiveLevelValidity

Receive Level: devCirQualReceiveLevel

Signal to Noise Validity: devCirQualSignalToNoiseValidity

Signal to Noise: devCirQualSignalToNoise

Phase Jitter 20–300 Hz Validity: devCirQualPhaseJitter300Validity

Phase Jitter 20–300 Hz: devCirQualPhaseJitter300

Frequency Offset Validity: devCirQualFrequencyOffsetValidity

Frequency Offset: devCirQualFrequencyOffset

Non-linear Distortion Validity: devCirQualNonLinearDistortionValidity

Non-linear Distortion: devCirQualNonLinearDistortion

Retrains Validity: devCirQualRetrainsValidity

Retrains: devCirQualRetrains

Gain Hits Validity: devCirQualgainHitsValidity

Gain Hits: devCirQualGainHits

Phase Hits Validity: devCirQualPhaseHitsValidity

Phase Hits: devCirQualPhaseHits

Impulse Noise Validity: devCirQualImpulseNoiseValidity

Impulse Noise: devCirQualImpulseNoise

Dropouts Validity: devCirQualDropoutsValidity

Dropouts: devCirQualDropouts

Line Quality Validity: devCirQualLineQualityValidity

Line Quality: devCirQualLineQuality

Near End Echo Validity: devCirQualNearEndEchoValidity

Near End Echo: devCirQualNearEndEcho


A-16 January 1997 7800-A2-GB21-20

Table A-20(2 of 2)

Proxy Device Circuit Quality Dialog (read-only)

Field 6700 Series Device MIB – Circuit Quality Group

Far End Echo Validity: devCirQualFarEndEchoValidity

Far End Echo: devCirQualFarEndEcho

Far End Delay Validity: devCirQualFarEndDelayValidity

Far End Delay: devCirQualFarEndDelay

Echo Frequency Offset Validity: devCirQualEchoFreqOffsetValidity

Echo Frequency Offset: devCirQualEchoFreqOffset

Dialog MIB Values

A-177800-A2-GB21-20 January 1997

Device Commands

Table A-21 shows the MIB objects used to generate the device commands (see Chapter 4).

Table A-21Device Commands

Field 6700 Series Device MIB – Command Group

Clear Busy devCommandBusy = clear-busy

Set Busy devCommandBusy = set-busy

Dial Number devCommandDial = <number>

Disconnect Call devCommandDisconnect = disconnect-call

Disconnect Service devCommandDisconnect = disconnect-service

Disable Device devCommandEnable = disable-device

Enable Device devCommandEnable = enable-device

Hardware Device Reset devCommandResetDevice = reset-device

Software Device Reset devCommandResetDevice = reset-device

Send Message devCommandMessage = <message>

Switch to Dial Backup devCommandSwitchTo = dial-backup

Switch to Dial Standby devCommandSwitchTo = dial-standby

Switch to Leased Line devCommandSwitchTo = leased

Switch to Service Line devCommandSwitchTo = service-line


A-18 January 1997 7800-A2-GB21-20

Device EIA Status Display

Table A-22 shows the MIB objects used to generate the Device EIA Status Display (seeChapter 3).

Table A-22Proxy Device EIA Status Dialog (read-only)

Field 6700 Series Device MIB – EIA Status Group

Port:DTRTDRDDSRRTSCTSDCDTMDRIPIN13PIN19DRSLLRLRIDPRDLOCRQACRDSCPND

devEIAStatusIndexdevEIAStatusDTRdevEIAStatusTDdevEIAStatusRDdevEIAStatusDSRdevEIAStatusRTSdevEIAStatusCTSdevEIAStatusDCSdevEIAStatusTMdevEIAStatusDRIdevEIAStatusPIN13devEIAStatusPIN19devEIAStatusDRSdevEIAStatusLLdevEIAStatusRLdevEIAStatusRIdevEIAStatusDPRdevEIAStatusDLOdevEIAStatusCRQdevEIAStatusACRdevEIAStatusDSCdevEIAStatusPND

Device External Leads Display

Table A-23 shows the MIB objects used to generate the Device External Leads Display (seeChapter 3).

Table A-23Proxy Device External Leads Dialog (read-only)

Field 6700 Series Device MIB – EIA Status Group

Out Pin 12Out Pin 13In Pin 19In Pin 23

devExtLeadsOutPin12devExtLeadsOutPin13devExtLeadsInPin19devExtLeadsInPin23

Dialog MIB Values

A-197800-A2-GB21-20 January 1997

Device Loopback Modes and Pattern Tests

Table A-24 shows the MIB objects used to generate the loopback modes and pattern tests forproxied devices (see Chapter 5).

Table A-24Loopback Modes and Pattern Tests

Menu ItemSet nmsTestType (6700 Series

NMS MIB – Test Group) to:

Self Test self-test

Proxied Device –>Local Loopback local-loop

Proxied Device –>Remote Digital Loopback rem-digital-loop

Local Digital Loopback loc-digital-loop

DTE Loopback dte-loop

BERT bert

Local Loopback BERT local-loop-bert

Remote Digital Loopback BERT rdl-bert

Digital Test digital-test

End To End Test end-to-end-test

Abort Test abort


A-20 January 1997 7800-A2-GB21-20

Device Test Display

Table A-25 shows the MIB objects used to generate the Device Test Display (see Chapter 5).

Table A-25Device Test Display

Field 6700 Series NMS MIB – Test Group

Device Name: nmsTestDeviceName

Remote Name: nmsTestRemoteName

Duration: nmsTestDuration

Port Number: nmsTestPortNumber

Test Type: nmsTestType

Test Status: nmsTestStatus

Total Seconds Validity: nmsTestTotalSecondsValidity

Total Seconds: nmsTestTotalSeconds

Error Seconds Validity: nmsTestErrorSecondsValidity

Error Seconds: nmsTestErrorSeconds

Glossary-17800-A2-GB21-20 January 1997

Glossary

Alert A device reported condition that meets or exceeds the alert criteria defined in the alertconfiguration.

AMI Alternate Mark Inversion. A line encoding technique and a bipolar return-to-zero signal.

ANSI American National Standards Institute.

ANSI-T1-403 ANSI specification that defines T1 operation.

APL Analog Private Line. See Facility Alarm.

ASCII This code (American Standard Code for Information Interchange) is a 7-bit code whichestablishes compatibility between data services. ASCII is the standard for datatransmission over telephone lines. The ASCII code consists of 32 control characters(nondisplayed) and 96 displayed characters.

asynchronoustransmission

A data transmission that is synchronized by a transmission start bit at the beginning of acharacter (five to eight bits) and one or more stop bits at the end.

ATT-54016 AT&T specification that defines T1 operation.

baud A unit of signaling speed that is equal to the number of symbols per second. This is notnecessarily the same as bits per second, although the terms are frequently interchanged.

BER Basic Error Rate. Number of errors over a given period.

BERT Bit Error Rate Test. See Pattern Test.

BES Bursty Error Seconds. A second in which more than one, but less than 320 CRC6 errorevents, have occurred.

B8ZS Bipolar 8 Zero Substitution. Encoding scheme for transmitting clear channel signals overa T1 line.

bit A contraction of binary digit. A bit, which is the smallest unit of information, representsthe choice between a one or a zero (sometimes called mark or space).

bps Bits per second. Indicates the speed at which bits are transmitted across a dataconnection.

buffer A storage device used to compensate for differences in the data flow rate whentransmitting data from one device to another.


Glossary-2 January 1997 7800-A2-GB21-20

busied out One of a device’s operational states. When a device is in the busy out (or make busy)state, it will not be able to answer calls. If the busied out device is on a rotary, the rotarywill skip the device when servicing incoming calls. A device that has its dial line busiedout may switch to the service line for further use.

byte A sequence of successive bits (usually eight) handled as a unit in data transmission.

carrier A carrier is a rack with 17 slots; one control slot (for a Shared Diagnostic Unit) and 16 device slots.

CCA Circuit Card Assembly. Identifies circuit cards in a device.

CCITT An advisory committee (Consultative Committee on International Telephone andTelegraph) established by the United Nations to recommend communications standardsand policies.

CCITT V.54 CCITT standard for local and remote diagnostic loopback tests.

control A term used to describe a device that can issue tests and commands to other devices onthe same circuit.

control channel The diagnostic communications link to network devices.

CNMP Common Network Management Platform. Used to identify HP OpenView elements thatrelate to the ACCULINK 3100 Series products.

CRC Cyclic Redundancy Check. A method of error detection.

CSS Controlled Slip Seconds. A period in which a frame was added or deleted because of avariance in timing.

CSU Channel Service Unit. Protects the T1 line from damage and regenerates the T1 signal.

dB Decibel.

dBm Decibel referred to one milliwatt.

DCE The equipment (Data Communications Equipment or Data Circuit TerminatingEquipment) that provides the functions required to establish, maintain, and end aconnection. This equipment also provides the signal conversion required forcommunication between the DTE and the telephone line.

DCLB Data Channel Loopback. Loopback mode that loops the data for a particular synchronousdata port back to the network interface after the information has passed all the waythrough the DSU/CSU.

D4 The transmission standard that specifies 12 frames as a superframe that is used for frame synchronization and to locate signaling bits.

dial A device operating on a Public Switched Telephone Network (PSTN) line and requiringa dialing method and protocol to conduct data transmission.

dial backup One of a device’s operational states that indicates a dial/leased device is using a dial linerather than a leased line to complete its communication.

Glossary


dial standby One of a lease line device’s operational states. The Dial Standby mode allows the deviceto switch back to leased-line operation while still maintaining the dial line.

dialog An HP OpenView window that displays status or configuration information about anobject.

DLB DTE Loopback. Loopback mode that loops the information received on the DTE T1network interface back to the network as close to the network interface as possible.

DSU Data Service Unit. Data communications equipment which transmits digital data over aprivate line. Also used for limited distance communications over the PSTN when ahigh-speed modem is not needed.

DS0 Digital Signal level 0. A signal of worldwide standard speed for PCM digital voicechannels running at 64 kbps.

DS1 Digital Signal level 1. A signal of 1.544 Mbps in North America.

DSX-1 Digital Signal Cross Connect level 1. An interconnection point for terminals,multiplexers and transmission facilities.

DTE The equipment (Data Terminal Equipment), such as a computer or terminal, thatprovides data in the form of digital signals.

DTLB Data Terminal Loopback. Loopback mode that loops the data for a particularsynchronous data port back to the port just before it is combined with the rest of the T1data stream.

EER Excessive Error Rate. Declared if more than 1,535 CRC6 errors are detected in a tensecond period.

EGP Exterior Gateway Protocol. Protocol that distributes routing information to the routersthat connect autonomous systems.

EIA Electronic Industries Association. This organization provides standards for the datacommunications industry.

EIA-530A/RS449 V.35 An Electronic Industries Association’s standard defining an interface.

ES Errored Second. A second with one or more ESF error events (one or more CRC6 errorevents or OOFs).

ESF Extended Superframe. The T1 transmission standard that specifies 24 frames as anextended superframe to be used for frame synchronization and to locate signaling bits.

facility A leased or dial transmission path.

facility alarm An alert that NMS displays indicating that the device has detected an abnormal conditionon the facility (line) that could cause data errors. The facility alarm only applies to leasedor Analog Private Line (APL) devices.

FDL Facility Data Link. The selected bits in the ESF format that are used for control,monitoring and testing.



511 A random bit test 511 bytes in length.

FT1 Fractional Timing 1. ANSI standard for DCLB tests.

ICMP Internet Control Management Protocol. Internet protocol that allows for the generation oferror messages, tests packets, and informational messages related to IP.

idle One of a dial line device’s operational states that indicates an installed device is notcurrently in use.

IP Internet Protocol. Open networking protocol standard.

LAN adapter A device that allows a serial device to be connected to a LAN.

leased A device operating on a private line where no dialing is necessary to make theconnection. A dial device can be configured to run on a leased line. A local leased linedevice can be switched over to dial mode while attached to a leased line.

LLB Line Loopback. Loopback mode that loops the information received on the T1 networkinterface back to the network as close to the network interface as possible.

LOF Loss of Frame. Occurs when a DS1 terminal is unable to synchronize on the DS1 signalfor some interval (nominally 2 1/2 seconds).

LOFC Loss of Frame Count. A count of the number of LOFs declared.

loopback test Any test that verifies a device’s integrity by connecting the device’s output to thedevice’s input, then checks the received signal for errors.

LOS Loss of Signal. The T1 line condition where there are no pulses.

make busy A condition indicating that the device is holding the dial line busy to prevent receivingcalls.

NMS Network Management System. A set of diagnostic and configuration management toolsfor a data communication network, consisting of software programs and dedicatedcomputer hardware.

OOF An error condition in which two out of four synchronization bits are in error.

1-in-8 pattern Low-density pattern used in testing (7 zeros and 1 one).

out of threshold One or more of the analog parameter thresholds has been exceeded. The probable causeis poor line conditions or improper threshold settings. Thresholds may be set throughNMS commands.

pattern test A local test causing the device to transmit and monitor for a test pattern. This testdisrupts the transmission of primary data.

phase jitter A rapid or repeated shifting of the relative phase of a signal resulting in unwanteddistortion.

Glossary


PLB Payload Loopback. Loopback mode that loops the information received on the T1network interface back to the network after it has passed through receive and transmitframing section.

PPP Point-to-Point Protocol. Serial protocol used for operation in a TCP/IP network.

PRM Performance Report Messages. Messages indicating the current state of a T1 line asspecified by ANSI-T1-403.

QRSS Quasi-Random Signal. A test pattern simulating a random pattern of digital ones andzeros used to simulate normal transmission.

RBS Robbed Bit Signaling. Signaling used for voice-call processing over a T1 line.

remote loopback A test that sends a signal to the remote device to test the local device, the remote device,and the circuit between them.

RLB Repeater Loopback. Loopback mode that loops the entire data stream (DTE T1 and dataports information) back to the DTE T1 interface.

SES Severely Errored Seconds. A second with 320 or more CRC6 error events or one or moreOOFs occurring.

6700 Series NetworkManagement System

A Paradyne automated network management system that allows an operator to monitornetwork conditions, analyze problems, and take restorative measures from a singlepersonal computer (PC) workstation.

6700 Series NetworkManagement SystemSNMP Proxy AgentFeature

The COMSPHERE 6700 Series Network Management System SNMP Proxy AgentFeature provides the capability for any device managed by a 6700 Series NetworkManagement System to also be monitored and controlled by an SNMP networkmanagement system, such as HP OpenView.

SLIP Serial Link Internet Protocol. Protocol for serial operation in an Internet network.

SNMP Simple Network Management Protocol. Open networking management protocol.

streaming terminal The modem is in an antistreaming condition. The RTS input to the modem was held ONfor a period exceeding the time selected by the RTS antistream configuration option.

Sub-normal OperatingSpeed

A condition indicating the leased or Analog Private Line (APL) device is operating at aspeed below normal.

Sub-tree Truncation Downstream health and status information has been truncated due overflowed systemlimits with large amounts of health and status information in the subnetwork. Recoverthis information by sending device health and status commands to specific modems.

synchronous transmission Data transmission that is synchronized by timing signals. Characters are sent at a fixedrate. This type of transmission is more efficient than asynchronous transmission.

T1 AT&T term for a digital carrier facility used to transmit a DS1 formatted digital signal at1.544 megabits per second.

TCP Transmission Control Protocol.



TDM Time Division Multiplexer. A device that enables the simultaneous transmissions ofmultiple independent data streams into a single high-speed data stream bysimultaneously sampling the independent data streams and combining these samples toform the high-speed stream.

tributary A term used to describe a device that receives commands from other devices in thenetwork.

tributary timeout This indicates that the control DSU has not received a health and status update from thetributary DSU within the specified time.

trellis-coded modulation A modulation scheme developed by Paradyne which uses Forward Error Correction formultipoint and high-speed point-to-point applications.

UAS Unavailable Seconds. A count of 1-second intervals when service is unavailable.

UDP User Datagram Protocol. An Internet protocol that adds a level of reliability andmultiplexing.

V.54 CCITT standard for DCLB tests.

Yellow Alarm An outgoing signal transmitted when a DS1 terminal has determined that it has lost theincoming signal.

Index-17800-A2-GB21-20 January 1997

Index

Ccommunity name, write, 4-2, 5-1COMSPHERE 6700 Series NMS, 1-1, 2-4, 4-1COMSPHERE 6700 Series NMS Proxy Agent, vii, 1-1,

1-4, 2-4

DData Ports, 6-4DCE Manager

features, 1-2, 1-3functions

functions available through menu bar, 1-10functions available through right-hand mousebutton, 1-11functions available through UNIX command line,

1-12summary, 1-9

hardware requirements, 1-4installation

HP systems, 1-6Sun systems, 1-7

overview, vii, 1-1removing the files

HP systems, 1-9Sun systems, 1-9

software requirements, 1-4system requirements, 1-4

device3100 Series

3150 CSU, 1-1316x DSU, 1-1channel configuration, 4-4COM port, 1-19, 3-3configuration, 4-2Data Ports, 3-7, 4-9Data Ports configuration, 4-9Data Ports interface, 1-19, 5-5Data Ports interfaces, 3-3Data Ports loopback modes and pattern tests, 5-5DTE T1 configuration, 4-8DTE T1 interface, 1-19, 3-3, 3-6, 4-8, 5-4DTE T1 loopback modes, 5-4health and status, 3-1, 3-3, 3-4, 3-6, 3-7identity, 4-2interfaces. See individual interface (Network T1,

etc.)MIB definitions, A-1MODEM port, 1-19, 3-3Network T1 configuration, 4-7Network T1 interface, 1-19, 3-3, 3-4, 3-9, 3-11,

4-7, 5-3Network T1 loopback modes and pattern tests,

5-3Network T1 Performance Statistics Graph, 3-11Network T1 Performance Statistics Table, 3-9rear-panel display, 1-19status colors, 3-2tests, 5-1traps, 6-12troubleshooting, 6-2

configuration, 4-1


Index-2 January 1997 7800-A2-GB21-20

discovery, 2-43100 Series devices, 2-1

models3100 Series. See device3550 Series. See device3600 Series. See device3800 Series. See device3900 Series. See device

proxied3550 Series, 1-13600 Series, 1-13800 Series, 1-13900 Series, 1-1abort front panel test, 5-10call directory, 4-17Circuit Quality Table, 3-16commands, 4-19configuration, 4-10device administration, 4-22dial-backup modules (DBM), 2-9EIA status, 3-20External Leads status, 3-21front panel emulator, 4-13health and status, 3-1, 3-12, 3-13identity, 4-16MIB definitions, A-11NMS administration, 4-10NMS system features, 4-12status colors, 3-12tests, 5-6traps, 6-15troubleshooting, 6-13

rear-panel display, status colors, 2-3symbols, 2-9

dial-backup modules. See Device, proxied, dial-backupmodem (DBM)

documentation conventions, ixdocuments

ordering, xreference, xrelated, ix

DTE T1 interface, 6-4

FFront Panel Emulator. See device, proxied, Front Panel

Emulator

Hhelp, 1-22Hewlett-Packard

Network Node Manager, 1-1, 1-4OpenView, map permissions, 2-1OpenView Windows, 1-1SNMP Management Platform, 1-1, 1-4workstations, vii

Lloopback modes

abort, 5-3overview, 5-1troubleshooting, 6-1

MManagement Information Base (MIB)

setting variables, 4-1supported MIBs, viitree, 1-5

Morning Star PPP, 1-4

NNetwork Node Manager. See Hewlett-Packard, Network

Node ManagerNetwork T1 interface, 6-3

OOpenView Windows. See Hewlett-Packard, OpenView

Windows

Ppattern tests

checking result, 5-9overview, 5-1troubleshooting, 6-1

Point-to-Point Protocol (PPP), vii, 1-4, 2-3, 2-8

Rrear-panel display

3151 device, 1-213161 device, 1-203164 device, 1-193165 device, 1-20

Index

Index-37800-A2-GB21-20 January 1997

SSimple Network Management Protocol (SNMP), 1-1SNMP. See Simple Network Management ProtocolSNMP Management Platform. See Hewlett-Packard,

SNMP Management PlatformSun, workstations, vii

Ttests. See device, 3100 or proxiedtraps

handling, 2-8troubleshooting, 6-13

troubleshooting, 1-3, 6-1–6-21Data Ports, 6-4DTE T1 interface, 6-4Network T1 interface, 6-3traps, 6-13

Date post:	12-Jul-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times