Paradyne COMSPHERE 6700 SERIES User manual

Brand: Paradyne

Model: COMSPHERE 6700 SERIES

Category: Software

Type: User manual

COMSPHERE

6700 SERIES NETWORK

MANAGEMENT SYSTEM

SNMP PROXY AGENT FEATURE

USER’S GUIDE

Document No. 6700-A2-GB20-30

September 1998

Printed on recycled paper

6700-A2-GB20-30

September 1998

Printed in U.S.A.

Notice

This publication is protected by federal copyright law. No part of this publication may be copied or distributed,

transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form

or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the

express written permission of Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773.

Paradyne Corporation makes no representation or warranties with respect to the contents hereof and specifically

disclaims any implied warranties of merchantability or fitness for a particular purpose. Further, Paradyne Corporation

reserves the right to revise this publication and to make changes from time to time in the contents hereof without

obligation of Paradyne Corporation to notify any person of such revision or changes.

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

release to this manual.

Warranty, Sales, and Service Information

Contact your local sales representative, service representative, or distributor directly for any help needed. For

additional information concerning warranty, sales, service, repair, installation, documentation, training, distributor

locations, or Paradyne worldwide office locations, use one of the following methods:

 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

— Outside the U.S.A., call 1-727-530-2340

Document Feedback

We welcome your comments and suggestions about this document. Please mail them to Technical Publications,

Paradyne Corporation, 8545 126th Ave. N., Largo, FL 33773, or send e-mail to [email protected]. Include

the number and title of this document in your correspondence. Please include your name and phone number if you

are willing to provide additional clarification.

Trademarks

All products and services mentioned herein are the trademarks, service marks, registered trademarks or registered

service marks of their respective owners.

6700-A2-GB20-30

September 1998

Contents

About This Guide

 Document Purpose and Intended Audience iii. . . . . . . . . . . . . . . . . . . . . . . . .

 Document Summary iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 Product-Related Documents iv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 SNMP Proxy Agent Overview

 What is SNMP? 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 What is the SNMP Proxy Agent Feature? 1-1. . . . . . . . . . . . . . . . . . . . . . . . . .

Feature List 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Software Description 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 SNMP Proxy Agent Feature Package Contents 1-2. . . . . . . . . . . . . . . . . . . . .

 SNMP Network Topology 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 Proxy Agent Interface 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 SNMP Proxy Agent Installation

 Hardware and Software Requirements 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing for Installation and Configuration 2-1. . . . . . . . . . . . . . . . . . . . .

 Installing the SNMP Proxy Agent Feature 2-2. . . . . . . . . . . . . . . . . . . . . . . . . .

Configuring the SNMP Proxy Agent Feature for TCP/IP Networks 2-4. .

 SNMP Community Views 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Community Name Example 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Troubleshooting SNMP Request Timeouts 2-6. . . . . . . . . . . . . . . . . . . . . .

3 Traps and Report Formats

 SNMP Traps Overview 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Trap Messages 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 Traps OIDs 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mode 1 Traps 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mode 2 Traps 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NMS Events and Status 3-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents

6700-A2-GB20-30

September 1998

 File Formats 3-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm Filter Profile 3-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alarm History Report 3-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call Fault Report 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Call History Report 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Report 3-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A Enterprise Device MIBs

 Enterprise Device MIBs Overview A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Front Panel MIB Overview A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Call Directory MIB Overview A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Device Configuration MIB Overview A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . .

 MIB-II Support A-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

OID Prefix Tree A-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B NMS 6700 MIB Specifications

 NMS 6700 MIB Overview B-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 Action Request Tables B-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Action Request Setup Rules B-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Accessing the NMS 6700 MIB B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Action Request Setup Procedure B-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Test Table Setup B-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transaction Table Setup B-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transaction Table Setup Example B-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Report Table Setup B-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Report Table Setup Example B-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 NMS 6700 MIB Objects B-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

 Transaction Commands B-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C NMS Device MIB Specifications

 NMS Device MIB Overview C-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index

iii

6700-A2-GB20-30

September 1998

About This Guide

Document Purpose and Intended Audience

This guide describes how to install and use the COMSPHERE 6700 Series

Network Management System (NMS) SNMP Proxy Agent feature. It is assumed

that you have a basic understanding of COMSPHERE modems and data service

units (DSUs) and their operation, are knowledgeable about data communications,

and are familiar with Windows terminology and conventions.

Document Summary

Section Description

Chapter 1

SNMP Proxy Agent Overview.

Provides an introduction

to the SNMP Proxy Agent features and the Proxy

Agent Interface.

Chapter 2

SNMP Proxy Agent Installation.

Describes hardware

and software requirements and installation procedures.

Chapter 3

Traps and Report Formats.

Provides an overview of

SNMP traps with specific device traps actions.

Presents file formats for reports.

Appendix A

Enterprise Device MIBs.

Defines supported MIB

objects in the Paradyne Enterprise MIBs and standard

MIB-II support.

Appendix B

NMS 6700 MIB Specifications.

Provides MIB objects

and descriptions for the Enterprise NMS 6700 MIB with

details regarding table entries.

Appendix C

NMS Device MIB Specifications.

Provides MIB objects

and descriptions for the Enterprise NMS Device MIB

with details regarding table entries.

Glossary Refer to

COMSPHERE 6700 Series Network

Management System User’s Guide,

Document

Number 6700-A2-GY31.

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

alphabetical order.

About This Guide

6700-A2-GB20-30

September 1998

Product-Related Documents

Document Number Document Title

3000-A2-GA31

COMSPHERE 3000 Series Carrier, Installation

Manual

3610-A2-GB46

COMSPHERE 3600 Series Data Service Units,

Models 3610 and 3611, User’s Guide

3610-A2-GB48

COMSPHERE 3600 Series Data Service Units,

Models 3610 and 3611, Time Division Multiplexer,

Multichannel Multipoint, and Digital Bridge Options

Supplement

3610-A2-GB49

COMSPHERE 3600 Series Data Service Units,

Models 3610 and 3611, Dial Backup Module Options

Supplement

3810-A2-GB30

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-GB21

COMSPHERE 6700 Series Network Management

System Multiuser Feature User’s Guide

6700-A2-GB22

COMSPHERE 6700 Series Network Management

System Network Configuration Guide

6700-A2-GB23

COMSPHERE 6700 Series Network Management

System Remote Monitor Feature User’s Guide

6700-A2-GB41

COMSPHERE 6700 Series Network Management

System Security Manager Feature Supplement

6700-A2-GY31

COMSPHERE 6700 Series Network Management

System User’s Guide

7800-A2-GB24

Proxy Agent Interface for HP OpenView Application

Guide

7800-A2-GB26

OpenLane

DCE Manager User’s Guide

Contact your sales or service representative to order additional product

documentation.

Paradyne documents are also available on the World Wide Web at:

http://www.paradyne.com

Select

Service & Support

→

Technical Manuals

1-1

6700-A2-GB20-30

September 1998

SNMP Proxy Agent Overview

What is SNMP?

Simple Network Management Protocol (SNMP) is an Internet standard protocol

for managing TCP/IP devices.

Using SNMP, a network administrator can address queries and commands to

network nodes and devices. SNMP can be used to:

 Monitor network performance and status

 Control operational parameters

 Report, analyze, and isolate faults

Agents, managers, and Management Information Bases (MIBs) combine to

control network devices.

Agents collect management information and store in a database called the MIB.

The agent provides management information to an SNMP manager upon

request.

Non-TCP/IP devices can be managed with SNMP proxy agents.

What is the SNMP Proxy Agent Feature?

The COMSPHERE 6700 Series Network Management System SNMP Proxy

Agent feature provides the capability for any device managed by a COMSPHERE

6700 Series Network Management System (NMS) to also be monitored and

controlled by an SNMP network management system, such as HP OpenView.

SNMP Proxy Agent Overview

1-2

6700-A2-GB20-30

September 1998

Feature List

The SNMP Proxy Agent feature provides the following features:

 SNMP Proxy Agent for COMSPHERE devices using Enterprise MIBs

 SNMP Agent for COMSPHERE 6700 Series NMS using Enterprise MIBs

 SNMP Agent for MIB-II

 COMSPHERE 6700 Series NMS Alerts exported as SNMP Traps

 One IP address per COMSPHERE 6700 Series NMS

 Specific Community View Access for each managed device

Software Description

The SNMP Proxy Agent feature includes SNMP software, which supports

transmission of SNMP messages across any Winsock-compliant TCP/IP protocol

stack installed on the system.

COMSPHERE 6700 Series NMS Release 5.0 or higher is required to execute the

SNMP Proxy Agent feature. The SNMP Proxy Agent feature is a software

package that can be installed on top of COMSPHERE 6700 Series NMS

Release 5.0 or higher.

You can install the SNMP Proxy Agent feature in the following COMSPHERE

6700 Series NMS installations:

 Single user

 Multiuser server

SNMP Proxy Agent Feature Package Contents

The SNMP Proxy Agent feature package includes the following:

 SNMP feature software on one 3 1/2″ disk with a Software Abstract

 COMSPHERE 6700 MIBs on one 3 1/2″ disk with a Software Abstract

 One

COMSPHERE 6700 Series Network Management System SNMP Proxy

Agent Feature User’s Guide

(this manual)

SNMP Proxy Agent Overview

1-3

6700-A2-GB20-30

September 1998

SNMP Network Topology

The figure below shows a sample SNMP network topology.

SNMP Proxy Agent Overview

1-4

6700-A2-GB20-30

September 1998

Proxy Agent Interface

The Paradyne Proxy Agent Interface application for HP OpenView runs in

conjunction with DCE Manager. HP OpenView can establish a management link

to a system running the 6700 Series NMS SNMP Proxy Agent feature over a LAN

(via router or LAN adapter), leased line, or dial-up connection. The Proxy Agent

Interface application can be used to manage the 6700 Series NMS as well as the

devices.

The 3550 Series DSUs, 3610 Series DSUs, 3810 Series modems, and 39xx

Series modems support SNMP

indirectly

through the COMSPHERE 6700 Series

Network Management System SNMP Proxy Agent Feature software product as

illustrated below. These devices are referred to as proxied devices.

SNMP Manager

Running HP OpenView

LAN - TCP/IP

495-14590-01

Ethernet, Token Ring, or FDDI

SLIP

PPP

Asynchronous

Serial

COMSPHERE 6700 Series NMS

Running 6700 Series NMS

SNMP Proxy Agent Feature

COMSPHERE 3550 Series DSUs

COMSPHERE 3600 Series DSUs

COMSPHERE 3800 Series Modems

COMSPHERE 3900 Series Modems

COMSPHERE 6700 Series NMS

Running 6700 Series NMS

SNMP Proxy Agent Feature

COMSPHERE 3550 Series DSUs

COMSPHERE 3600 Series DSUs

COMSPHERE 3800 Series Modems

COMSPHERE 3900 Series Modems

COMSPHERE 3610

dyn

COMSPHERE 3610

dyn

COMSPHERE 3610

dyn

Modem

COMSPHERE 3610

dyn

COMSPHERE 3610

dyn

COMSPHERE 3610

dyn

COMSPHERE 3610

dyn

COMSPHERE 3610

dyn

SLIP

PPP

dyn

ACCULINK 3100

Series DSU/CSUs

ACCULINK 3100

Series DSU/CSUs

Modem

SLIP

PPP

SLIP

PPP

3000

Series Carrier

For additional information, refer to

Proxy Agent Interface for HP OpenView

Application Guide.

2-1

6700-A2-GB20-30

September 1998

SNMP Proxy Agent Installation

Hardware and Software Requirements

The SNMP Proxy Agent feature has the same hardware and software

requirements as the basic single-user NMS, except that the agent requires at

least 16 MB of RAM. Refer to the

Hardware Description

and

Software Description

sections in Chapter 1,

Introduction

, of the

COMSPHERE 6700 Series Network

Management System User’s Guide

for details.

Preparing for Installation and Configuration

Before installing and configuring the SNMP Proxy Agent feature, you need some

system and network information. A Winsock-compliant TCP/IP stack must be

installed on the PC, such as the one provided by Windows 95 and Windows NT.

SNMP Proxy Agent Installation

2-2

6700-A2-GB20-30

September 1998

Installing the SNMP Proxy Agent Feature

 Procedure

To install the SNMP Proxy Agent feature software, start from the Program

Manager window and perform the following steps:

1. Insert Disk #1 into Drive A. From the Program Manager window, choose File.

From the File menu, choose Run.

2. In the Command Line field, type A:\INSTALL.

3. Choose OK. The Welcome window appears.

4. Choose Continue. The Product Information window appears.

SNMP Proxy Agent Installation

2-3

6700-A2-GB20-30

September 1998

5. Choose Yes. The Destination Directory window appears.

The Destination Directory window allows you to place the NMS software into

a specific directory. A single directory within a single partition is required.

Enter a subdirectory location or choose the default setting C:\PCNMS.

6. Choose Continue. The Confirmation window appears.

7. Choose Install to confirm the installation of the NMS software into the

specified directory. The Completion status window appears.

This window displays a bar indicating the percentage of completion for the

current installation. In addition, the names of the files being installed appear

above the bar until the installation is complete.

SNMP Proxy Agent Installation

2-4

6700-A2-GB20-30

September 1998

8. The Trap Compatibility window appears. No is the default.

The 7800 DCE Manager trap types and format are available. To maintain

compatibility, select Yes if you are using the DCE Manager software also.

Choosing Yes results in Mode 1 for Release 1 and disables the traps new to

Release 2 and other new functionality, including filtering from the NMS Alarm

MIB.

9. The Installation Completed! window appears.

10. Choose OK.

Configuring the SNMP Proxy Agent Feature for TCP/IP Networks

After installation, use the Network Configuration application to customize your

configuration for TCP/IP networks. For details, refer to the

COMSPHERE

6700 Series Network Management System Network Configuration Guide

SNMP Proxy Agent Installation

2-5

6700-A2-GB20-30

September 1998

SNMP Community Views

Different read and write community views are used for the COMSPHERE 6700

NMS MIB and for each managed device under the COMSPHERE 6700 Device

MIB. Set up the community names for community views using the COMSPHERE

6700 Series NMS Network Configuration feature. Refer to the

COMSPHERE

6700 Series Network Management System Network Configuration Guide

NOTE:

The default community names are:

nmsAdminNmsReadCommunity = “public”

nmsAdminNmsWriteCommunity = “public”

nmsAdminBaseReadCommunity = “” (null)

nmsAdminBaseWriteCommunity = “” (null)

With the default settings, the community names for the devices are the

device names. Refer to Chapter 4,

Configuration,

in the

COMSPHERE 6700

Series Network Management System User’s Guide

The community names for the Device MIB are generated by appending the

desired device name to the appropriate base name. Consider the following rules

when creating community names:

 Community names should not be the prefix of a device name.

 Write community names can be used for both read and write.

 Device Call Directory MIB and Device Front Panel MIB both use the same

communities as the Device Configuration MIB. Refer to Appendix A,

Enterprise Device MIBs.

Community Name Example

To better understand the use of community names, consider the following

example. Using community name settings as follows:

 nmsAdminNmsReadCommunity = clear

 nmsAdminNmsWriteCommunity = orange

 nmsAdminBaseReadCommunity = teal

 nmsAdminBaseWriteCommunity = pink

The community name for Get requests to the NMS MIB can be either “clear” or

“orange.” The community name for Set requests to the NMS MIB must be

“orange.”

The Device MIB community name for Get requests to a device named “

modem1

”

in the Device MIB would be either “teal

modem1

” or “pink

modem1.

” The

community name for Set requests to the device would be “pink

modem1.

”

To access a Dial Backup Module (DBM) within a COMSPHERE 3600 Series

DSU, the suffix “.dbm” is appended to the device community name. For example,

the DBM for a device named “

DSU5

” would have a write community name of

“pink

DSU5.

dbm.”

SNMP Proxy Agent Installation

2-6

6700-A2-GB20-30

September 1998

Troubleshooting SNMP Request Timeouts

The following table includes most common causes of SNMP request timeouts.

Symptom

Solution

Community name is not valid. Use the Network Configuration application

SNMP/Community Names menu item to

determine the valid community names.

SNMP Manager is not authorized. Use the Network Configuration application

SNMP/Community Names menu item to add a

manager or change its access.

Timeout setting for SNMP

Manager is too short.

Allow at least 30 seconds (recommended

minimum). For tributary or tail circuit access,

60 seconds may be required.

6700 NMS is not running. Check the PC to ensure that the 6700 NMS is up

and running. For additional troubleshooting, refer

to the

COMSPHERE 6700 Series Network

Management User’s Guide

. Additional related

documents are listed in

Product-Related

Documentation

About This Guide

on page iv.

3-1

6700-A2-GB20-30

September 1998

Traps and Report Formats

SNMP Traps Overview

The COMSPHERE 6700 Series NMS supports several SNMP traps and reports.

COMSPHERE 6700 NMS alerts may be exported to authorized SNMP managers

as SNMP traps. Traps are forwarded for any event that makes it through the

COMSPHERE 6700 Series NMS’s alert filter.

All traps are enterprise specific, with an OBJECT IDENTIFIER (OID) specifying

the COMSPHERE 6700 Enterprise Device product.

Trap forwarding can be turned on/off for each SNMP manager in the authorized

manager list through the COMSPHERE 6700 Series NMS Network Configuration

feature or via SNMP. To do so, refer to the

COMSPHERE 6700 Series Network

Management System Network Configuration Guide

Traps may be:

 Configured to operate in Mode 1 or Mode 2.

— Use Mode 1 with Release 1 for compatibility with previous SNMP Proxy

Agent releases and with the DCE Manager Proxy Agent Interface (UNIX

platform).

— Use Mode 2 with Release 2 for additional traps, filtering, more

information, and serialization.

 Individually filtered for each manager through the NMS Alarm MIB group in

Mode 2 only.

Trap Messages

The COMSPHERE 6700 Device MIB variable bindings are dependent on the

specific trap and Trap Mode.

 Table 3-1, Mode 1 Traps

 Table 3-2, Mode 2 Traps

 Table 3-3, Mode 2 NMS Events and Status

Traps and Report Formats

3-2

6700-A2-GB20-30

September 1998

Traps OIDs

Traps are generated for alert conditions detected by the COMSPHERE 6700

Series NMS.

The Enterprise OBJECT IDENTIFIER (OID) used in device traps in Trap Mode 1

is the following:

iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

att-2(74) att-products(1) paradyneNMS-products(13)

nms-6700-products(2) att67 devOid(2)

For Trap Mode 2, the OBJECT IDENTIFIER (OID) varies depending on the

device type generating the trap.

For dial devices, the following OID is used:

iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

att-2(74) att-products(1) paradyneNMS-products(13)

nms-6700-products(2) att67 devOid(2) att67dialOid(1)

For APL devices, the following OID is used:

iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

att-2(74) att-products(1) paradyneNMS-products(13)

nms-6700-products(2) att67 devOid(2) att67aplOid(2)

For DSU devices, the following OID is used:

iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

att-2(74) att-products(1) paradyneNMS-products(13)

nms-6700-products(2) att67 devOid(2) att67dsuOid(3)

For the NMS system, the following OID is used:

iso(1) org(3) dod(6) internet(1) private(4) enterprises(1)

att-2(74) att-products(1) paradyneNMS-products(13)

nms-6700-products(2) att67nmsOid(1)

The community name used in device product traps is the Device Read

Community. This is formed by concatenating base read community with the

device name.

Mode 1 Traps

The following COMSPHERE 6700 Device MIB variable bindings are included in

each trap message.

 Device Name (devAdminName)

 Device Type (devAdminModelType)

 System Time (nmsSystemTime)

Traps and Report Formats

3-3

6700-A2-GB20-30

September 1998

Table 3-1 identifies Mode 1 traps that apply to all Paradyne devices (DSU, Dial,

and APL) and includes an alarm clearing actions column. Use Mode 1 traps for

compatibility with the Proxy Agent Interface application for DCE Manager.

Traps 101–117 are Dial Security alerts.

NOTE:

Trap numbers 1–32 are reserved for Primary Alerts. The state of a device’s

Primary Alerts can also be read from devStatusAlert.

Table 3-1. Mode 1 Traps (1 of 3)

Trap

Trap Description Alarm Clearing Actions

1 Device Failure Automatically clears when condition improves

2 Configuration Change Notify User must explicitly clear the alarm

3 Test Mode Automatically clears when condition improves

4 Disabled Automatically clears when condition improves

5 Out of Threshold/VF Threshold

Exceeded

Automatically clears when condition improves

6 Facility Alarm Automatically clears when condition improves

7 External Alarm Automatically clears when condition improves

8 Streaming Terminal Automatically clears when condition improves

9 Access Security Automatically clears when condition improves

10 TDM Failure/Dial Backup

Active for APL

Automatically clears when condition improves

11 DTE Alarm Automatically clears when condition improves

12 Sub-normal Operating Speed Automatically clears when condition improves

13 Primary Channel Interrupted Automatically clears when condition improves

14 Firmware Downloading Automatically clears when condition improves

15 Make Busy Mode Automatically clears when condition improves

16 Service Line Automatically clears when condition improves

17 Non-answering Modem Automatically clears when condition improves

18 Short Holding Time Modem Automatically clears when condition improves

19 Sub Tree Truncation Automatically clears when condition improves

20 TDM Failure/Good APL Line Automatically clears when condition improves

21 Tributary Timeout Automatically clears when condition improves

22 Dial Tone Test Automatically clears when condition improves

23 Redundant Power Supply Automatically clears when condition improves

Traps and Report Formats

3-4

6700-A2-GB20-30

September 1998

Table 3-1. Mode 1 Traps (2 of 3)

Trap Alarm Clearing ActionsTrap Description

32 No Response Automatically clears when condition improves

101 VF Login OK One-time event notification; no clearing needed

102 User Login OK One-time event notification; no clearing needed

103 User Login Rejected – Retry

Failed