COMSPHERE 6700 SERIES NETWORK MANAGEMENT SYSTEM SNMP PROXY AGENT FEATURE

Transcription

1 COMSPHERE 6700 SERIES NETWORK MANAGEMENT SYSTEM SNMP PROXY AGENT FEATURE USER S GUIDE Document No A2-GB20-30 September 1998

2 Copyright 1998 Paradyne Corporation. All rights reserved. Printed in U.S.A. Notice This publication is protected by federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language in any form or by any means, electronic, mechanical, magnetic, manual or otherwise, or disclosed to third parties without the express written permission of Paradyne Corporation, th Ave. N., Largo, FL 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 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 Outside the U.S.A., call Document Feedback We welcome your comments and suggestions about this document. Please mail them to Technical Publications, Paradyne Corporation, th Ave. N., Largo, FL 33773, or send to userdoc@eng.paradyne.com. 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. Printed on recycled paper A September A2-GB20-30

3 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? What is the SNMP Proxy Agent Feature? Feature List Software Description SNMP Proxy Agent Feature Package Contents SNMP Network Topology Proxy Agent Interface SNMP Proxy Agent Installation Hardware and Software Requirements Preparing for Installation and Configuration Installing the SNMP Proxy Agent Feature Configuring the SNMP Proxy Agent Feature for TCP/IP Networks SNMP Community Views Community Name Example Troubleshooting SNMP Request Timeouts Traps and Report Formats SNMP Traps Overview Trap Messages Traps OIDs Mode 1 Traps Mode 2 Traps NMS Events and Status A2-GB20-30 September 1998 i

4 Contents File Formats Alarm Filter Profile Alarm History Report Call Fault Report Call History Report Device Report 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 ii September A2-GB20-30

5 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 Chapter 1 Chapter 2 Chapter 3 Appendix A Appendix B Appendix C Glossary Index Description SNMP Proxy Agent Overview. Provides an introduction to the SNMP Proxy Agent features and the Proxy Agent Interface. SNMP Proxy Agent Installation. Describes hardware and software requirements and installation procedures. Traps and Report Formats. Provides an overview of SNMP traps with specific device traps actions. Presents file formats for reports. Enterprise Device MIBs. Defines supported MIB objects in the Paradyne Enterprise MIBs and standard MIB-II support. NMS 6700 MIB Specifications. Provides MIB objects and descriptions for the Enterprise NMS 6700 MIB with details regarding table entries. NMS Device MIB Specifications. Provides MIB objects and descriptions for the Enterprise NMS Device MIB with details regarding table entries. Refer to COMSPHERE 6700 Series Network Management System User s Guide, Document Number 6700-A2-GY31. Lists key terms, acronyms, concepts, and sections in alphabetical order A2-GB20-30 September 1998 iii

6 About This Guide Product-Related Documents Document Number 3000-A2-GA A2-GB A2-GB A2-GB49 Document Title COMSPHERE 3000 Series Carrier, Installation Manual COMSPHERE 3600 Series Data Service Units, Models 3610 and 3611, User s Guide COMSPHERE 3600 Series Data Service Units, Models 3610 and 3611, Time Division Multiplexer, Multichannel Multipoint, and Digital Bridge Options Supplement 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-GB A2-GB A2-GB A2-GB A2-GY A2-GB A2-GB26 COMSPHERE 6700 Series Network Management System Multiuser Feature User s Guide COMSPHERE 6700 Series Network Management System Network Configuration Guide COMSPHERE 6700 Series Network Management System Remote Monitor Feature User s Guide COMSPHERE 6700 Series Network Management System Security Manager Feature Supplement COMSPHERE 6700 Series Network Management System User s Guide Proxy Agent Interface for HP OpenView Application Guide 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: Select Service & Support Technical Manuals iv September A2-GB20-30

7 SNMP Proxy Agent Overview 1 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 A2-GB20-30 September

8 SNMP Proxy Agent Overview 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) 1-2 September A2-GB20-30

9 SNMP Proxy Agent Overview SNMP Network Topology The figure below shows a sample SNMP network topology A2-GB20-30 September

10 Paradyne Paradyne Paradyne Paradyne Paradyne Paradyne COMSPHERE 3610 Paradyne Paradyne Paradyne Paradyne SNMP Proxy Agent Overview 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 SLIP or PPP 3000 Series Carrier SLIP or PPP Modem SLIP or PPP ACCULINK 3100 Series DSU/CSUs Modem SLIP or PPP Modem Asynchronous Serial Ethernet, Token Ring, or FDDI COMSPHERE 6700 Series NMS Running 6700 Series NMS SNMP Proxy Agent Feature COMSPHERE 3610 COMSPHERE 3610 COMSPHERE 3610 COMSPHERE 3550 Series DSUs COMSPHERE 3600 Series DSUs COMSPHERE 3800 Series Modems COMSPHERE 3900 Series Modems ACCULINK 3100 Series DSU/CSUs COMSPHERE 6700 Series NMS Running 6700 Series NMS SNMP Proxy Agent Feature COMSPHERE 3610 COMSPHERE 3610 COMSPHERE 3610 COMSPHERE 3610 COMSPHERE 3550 Series DSUs COMSPHERE 3600 Series DSUs COMSPHERE 3800 Series Modems COMSPHERE 3900 Series Modems For additional information, refer to Proxy Agent Interface for HP OpenView Application Guide. 1-4 September A2-GB20-30

11 SNMP Proxy Agent Installation 2 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 A2-GB20-30 September

12 SNMP Proxy Agent Installation 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. 2-2 September A2-GB20-30

13 SNMP Proxy Agent Installation 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 A2-GB20-30 September

14 SNMP Proxy Agent Installation 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. 2-4 September A2-GB20-30

15 SNMP Proxy Agent Installation 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 tealmodem1 or pinkmodem1. The community name for Set requests to the device would be pinkmodem1. 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 pinkdsu5.dbm A2-GB20-30 September

16 SNMP Proxy Agent Installation Troubleshooting SNMP Request Timeouts The following table includes most common causes of SNMP request timeouts. Symptom Community name is not valid. SNMP Manager is not authorized. Timeout setting for SNMP Manager is too short. Solution Use the Network Configuration application SNMP/Community Names menu item to determine the valid community names. Use the Network Configuration application SNMP/Community Names menu item to add a manager or change its access. Allow at least 30 seconds (recommended minimum). For tributary or tail circuit access, 60 seconds may be required 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 in About This Guide on page iv. 2-6 September A2-GB20-30

17 Traps and Report Formats 3 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 6700-A2-GB20-30 September

18 Traps and Report Formats 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) 3-2 September A2-GB20-30

19 Traps and Report Formats 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 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 Á Automatically clears when condition improves Exceeded Á 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 Á Automatically clears when condition improves Active for APL Á 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 6700-A2-GB20-30 September

20 Traps and Report Formats Table 3-1. Mode 1 Traps (2 of 3) Trap Trap Description Alarm Clearing Actions 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 One-time event notification; no clearing needed Failed Á 104 User Login Rejected One-time event notification; no clearing needed ÁÁ Password Timeout Á Á 105 User Login Aborted Line One-time event notification; no clearing needed Disconnected Á Á 106 VF Login Rejected Password One-time event notification; no clearing needed Invalid Á 107 VF Login Rejected Password Á One-time event notification; no clearing needed Timeout Á 108 VF Login Aborted Line Á One-time event notification; no clearing needed ÁÁ Disconnected Á 109 User Login OK Multiple Á One-time event notification; no clearing needed ÁÁ Password Retries Á 110 User ID and Password Á One-time event notification; no clearing needed Combination Invalid Á 111 Invalid User ID Password Á One-time event notification; no clearing needed Valid for Device Á 112 Invalid Access Time Á One-time event notification; no clearing needed 113 User Login Hack Multiple Á One-time event notification; no clearing needed Sequential Password Retries 114 Device Security Table Invalid Á One-time event notification; no clearing needed 116 Security Download Failed Á One-time event notification; no clearing needed Á 117 Front Panel Modification of One-time event notification; no clearing needed Security Options Á Á 201 Device Failure Cleared One-time event notification; no clearing needed Á 202 Configuration Change Notify One-time event notification; no clearing needed ÁÁ Cleared Á 203 Á Test Mode Cleared One-time event notification; no clearing needed Á 204 Device Disabled Cleared Á One-time event notification; no clearing needed 205 Threshold Exceeded Cleared Á One-time event notification; no clearing needed Á 206 Facility Alarm Cleared One-time event notification; no clearing needed Á 207 External Alarm Cleared One-time event notification; no clearing needed 3-4 September A2-GB20-30

21 Traps and Report Formats Table 3-1. Mode 1 Traps (3 of 3) Trap Trap Description Alarm Clearing Actions 208 Streaming Terminal Cleared Á One-time event notification; no clearing needed 209 Access Security Alarm Cleared Á One-time event notification; no clearing needed Á 210 TDM Failure/Dial Backup One-time event notification; no clearing needed Active for APL Cleared Á Á 211 DTE Alarm Cleared One-time event notification; no clearing needed Á 212 Sub-Normal Operating Speed One-time event notification; no clearing needed ÁÁ Cleared Á Á 213 Primary Channel Interrupted One-time event notification; no clearing needed Cleared Á Á 214 Firmware Downloading Cleared One-time event notification; no clearing needed Á 215 Make Busy Mode Cleared One-time event notification; no clearing needed 216 Service Line Cleared Á One-time event notification; no clearing needed 217 Non-answering Modem Á One-time event notification; no clearing needed ÁÁ Cleared Á 218 Short Holding Time Modem Á One-time event notification; no clearing needed ÁÁ Cleared Á 219 Sub Tree Truncation Cleared Á One-time event notification; no clearing needed 220 Good APL Line Cleared/TDM Á One-time event notification; no clearing needed Failure Cleared Á 221 Tributary Timeout Cleared Á One-time event notification; no clearing needed Á 222 Dial Tone Test Cleared One-time event notification; no clearing needed Á 223 Redundant Power Supply One-time event notification; no clearing needed Cleared Á 232 No Response Cleared One-time event notification; no clearing needed 6700-A2-GB20-30 September

22 Traps and Report Formats Mode 2 Traps Use Mode 2 traps when the Proxy Agent Interface application is not used. To use the Proxy Agent Interface application, refer to Mode 1 Traps on page 3-2. The following COMSPHERE 6700 NMS MIB variable bindings are included in each trap message. Trap Serial Number (nmstempserial) Device Name (nmstempname) System Time (nmssystemtime) Table 3-2 identifies Mode 2 (Enhanced Mode) traps that apply to all Paradyne devices (DSU, Dial, and APL). Not all devices produce all traps; refer to the device columns. Traps and are new with Release 2.0. Traps 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. Traps are Secondary Alerts with additional information on Primary Alerts (Traps 1 32). Alarm Clearing actions per Trap: Trap Alarm Clearing Action 1, 3 78 Automatically clears when condition improves 2 User must explicitly clear the alarm Automatically clears when condition improves Generates clear notification of corresponding Traps 1 78 when condition improves Table 3-2. Mode 2 Traps (1 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL Á 1 Device Failure ÁÁ Á 2 Configuration Change Notify 3 ÁÁ Test Mode Á 4 ÁÁ Disabled Á ÁÁ Á 5 Out of Threshold ÁÁ Á VF Threshold Exceeded 6 ÁÁ Facility Alarm Á 7 ÁÁ External Alarm Á 3-6 September A2-GB20-30

23 Traps and Report Formats Table 3-2. Mode 2 Traps (2 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 8 ÁÁ Streaming Terminal Á 9 ÁÁ Access Security Á ÁÁ Á 10 Dial Backup Active for APL ÁÁ Á 11 DTE Alarm Á 12 ÁÁ Sub-normal Operating Speed Á 13 ÁÁ Primary Channel Interrupted Á 14 ÁÁ Firmware Downloading Á Á 15 ÁÁ Make Busy Mode 16 ÁÁ Service Line Á ÁÁ Á 17 Non-answering Modem ÁÁ Á 18 Short Holding Time Modem ÁÁ Á 19 ÁÁ Sub Tree Truncation Á 20 ÁÁ TDM Failure Á ÁÁ Á Good APL Line ÁÁ Á 21 Tributary Timeout 22 ÁÁ Dial Tone Test Á 23 ÁÁ Redundant Power Supply Á ÁÁ Á 32 No Response ÁÁ Á 33 No Signal ÁÁ Receive Level High Threshold Á 34 ÁÁ Out of Frame Á ÁÁ Á Receive Level Low Threshold ÁÁ Á 35 Out of Service ÁÁ Signal Noise Ratio Threshold Á 36 ÁÁ Abnormal Station Code Á ÁÁ Á Phase Jitter Threshold ÁÁ Á 37 Á Facility Alarm due to Bipolar Violations ÁÁ Frequency Offset Threshold Á 38 ÁÁ CMI Detected Facility Alarm Á ÁÁ Á Non-linear Distortion Threshold 6700-A2-GB20-30 September

24 Traps and Report Formats Table 3-2. Mode 2 Traps (3 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 39 ÁÁ FDHP Sync Loss ÁÁ Retrain Threshold Á ÁÁ Á 40 External Alarm A ÁÁ Á Signal Quality Threshold 41 ÁÁ External Alarm B Á ÁÁ Near Echo Threshold Á ÁÁ Á 42 Far Echo Threshold ÁÁ Á 43 Port 1 Receive Data Alarm 44 ÁÁ Port 1 Transmit Data Alarm Á 45 ÁÁ Port 1 DTR Alarm Á ÁÁ Á 46 Port 1 CTS Alarm ÁÁ Á 47 ÁÁ Port 1 RTS Alarm ÁÁ 48 ÁÁ Port 1 DSR Alarm Á ÁÁ 49 Port 1 LSD Alarm Á ÁÁ ÁÁ 50 Port 1 Auto Stream Disabled ÁÁ Á 51 ÁÁ Port 1 Disabled Á 52 ÁÁ Port 2 Receive Data Alarm Á ÁÁ Á 53 Port 2 Transmit Data Alarm ÁÁ Á 54 Port 2 DTR Alarm 55 ÁÁ Port 2 CTS Alarm Á 56 ÁÁ Port 2 RTS Alarm Á ÁÁ Á 57 Port 2 DSR Alarm ÁÁ Á 58 ÁÁ Port 2 LSD Alarm ÁÁ 59 ÁÁ Port 2 Auto Stream Disabled Á 60 ÁÁ Port 2 Disabled Á 61 ÁÁ Port 3 Receive Data Alarm ÁÁ Á Á 62 ÁÁ Port 3 Transmit Data Alarm ÁÁ 63 ÁÁ Port 3 DTR Alarm Á ÁÁ Á 64 Port 3 CTS Alarm ÁÁ Á 65 Port 3 RTS Alarm 3-8 September A2-GB20-30

25 Traps and Report Formats Table 3-2. Mode 2 Traps (4 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 66 ÁÁ Port 3 DSR Alarm ÁÁ 67 ÁÁ Port 3 LSD Alarm Á ÁÁ Á 68 Port 3 Auto Stream Disabled ÁÁ Á 69 Port 3 Disabled 70 ÁÁ Port 4 Receive Data Alarm Á 71 ÁÁ Port 4 Transmit Data Alarm Á 72 ÁÁ Port 4 DTR Alarm ÁÁ Á Á 73 ÁÁ Port 4 CTS Alarm ÁÁ 74 ÁÁ Port 4 RTS Alarm Á ÁÁ Á 75 Port 4 DSR Alarm ÁÁ Á 76 Port 4 LSD Alarm ÁÁ Á 77 ÁÁ Port 4 Auto Stream Disabled Á 78 ÁÁ Port 4 Disabled Á ÁÁ Á 101 VF Login OK ÁÁ Á 102 User Login OK 103 ÁÁ User Login Rejected Retry Failed Á 104 ÁÁ User Login Rejected Password Á Á Timeout ÁÁ 105 ÁÁ User Login Aborted Line Disconnected Á ÁÁ Á 106 VF Login Rejected Password Invalid ÁÁ Á 107 VF Login Rejected Password Timeout 108 ÁÁ VF Login Aborted Line Disconnected Á 109 ÁÁ User Login OK Multiple Password Á Á Retries ÁÁ 110 ÁÁ User ID and Password Combination Á Á Invalid ÁÁ 111 ÁÁ Invalid User ID Password Valid for Á Device ÁÁ Á 112 ÁÁ Invalid Access Time Á 113 ÁÁ User Login Hack Multiple Sequential Á Á Password Retries ÁÁ 114 ÁÁ Device Security Table Invalid Á 6700-A2-GB20-30 September

26 Traps and Report Formats Table 3-2. Mode 2 Traps (5 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 116 ÁÁ Security Download Failed 117 ÁÁ Front Panel Modification of Security Á Á Options ÁÁ 201 ÁÁ Device Failure Cleared Á ÁÁ Á 202 Configuration Change Notify Cleared ÁÁ Á 203 Test Mode Cleared ÁÁ Á 204 ÁÁ Device Disabled Cleared Á 205 ÁÁ Threshold Exceeded Cleared Á ÁÁ Á VF Parameter Threshold Exceeded Á Cleared ÁÁ 206 Facility Alarm Cleared Á 207 ÁÁ External Alarm Cleared Á 208ÁÁ Streaming Terminal Cleared Á 209 ÁÁ Access Security Alarm Cleared Á ÁÁ Á 210 Dial Backup Active for APL Cleared ÁÁ Á 211 DTE Alarm Cleared ÁÁ Á 212 ÁÁ Sub-Normal Operating Speed Cleared Á 213 ÁÁ Primary Channel Interrupted Cleared Á ÁÁ Á 214 Firmware Downloading Cleared ÁÁ Á 215 Make Busy Mode Cleared 216 ÁÁ Service Line Cleared Á 217 ÁÁ Non-answering Cleared Á 218 ÁÁ Short Holding Time Modem Cleared Á Á 219ÁÁ Sub Tree Truncation Cleared 220 ÁÁ TDM Failure Cleared Á ÁÁ Good APL Line Cleared Á 221 ÁÁ Tributary Timeout Cleared ÁÁ Á 222ÁÁ Dial Tone Test Cleared 223 ÁÁ Redundant Power Supply Cleared Á ÁÁ Á 232 No Response Cleared 3-10 September A2-GB20-30

27 Traps and Report Formats Table 3-2. Mode 2 Traps (6 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 233 ÁÁ No Signal Cleared ÁÁ Receive Level High Threshold Cleared Á ÁÁ Á 234 Out of Frame Cleared ÁÁ Á Receive Level Low Threshold Cleared 235 ÁÁ Out of Service Cleared Á ÁÁ Signal Noise Ratio Threshold Cleared Á ÁÁ Á 236 Abnormal Station Code Cleared ÁÁ Á Phase Jitter Threshold Cleared 237 ÁÁ Facility Alarm Due to Bipolar Violations Á Cleared ÁÁ Á Á Frequency Offset Threshold Cleared ÁÁ 238 ÁÁ CMI Detected Facility Alarm Cleared Á ÁÁ Non-linear Distortion Threshold Cleared Á 239 ÁÁ FDHP Sync Loss Cleared ÁÁ Á Á Retrain Threshold Cleared ÁÁ 240 ÁÁ External Alarm A Cleared Á ÁÁ Signal Quality Threshold Cleared Á 241 ÁÁ External Alarm B Cleared ÁÁ Á Á Near Echo Threshold Cleared ÁÁ 242 ÁÁ Far Echo Threshold Cleared Á ÁÁ Á 243 Port 1 Receive Data Alarm Cleared ÁÁ ÁÁ 244 Port 1 Transmit Data Alarm Cleared ÁÁ Á 245 ÁÁ Port 1 DTR Alarm Cleared Á 246 ÁÁ Port 1 CTS Alarm Cleared Á ÁÁ Á 247 Port 1 RTS Alarm Cleared ÁÁ Á 248 Port 1 DSR Alarm Cleared 249 ÁÁ Port 1 LSD Alarm Cleared Á 250 ÁÁ Port 1 Auto Stream Disabled Cleared Á ÁÁ Á 251 Port 1 Disabled Cleared ÁÁ Á 252ÁÁ Port 2 Receive Data Alarm Cleared ÁÁ 253 ÁÁ Port 2 Transmit Data Alarm Cleared Á 6700-A2-GB20-30 September

28 Traps and Report Formats Table 3-2. Mode 2 Traps (7 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 254 ÁÁ Port 2 DTR Alarm Cleared ÁÁ 255 ÁÁ Port 2 CTS Alarm Cleared Á ÁÁ Á 256 Port 2 RTS Alarm Cleared ÁÁ Á 257 Port 2 DSR Alarm Cleared 258 ÁÁ Port 2 LSD Alarm Cleared Á 259 ÁÁ Port 2 Auto Stream Disabled Cleared Á 260 ÁÁ Port 2 Disabled Cleared ÁÁ Á Á 261ÁÁ Port 3 Receive Data Alarm Cleared ÁÁ 262 ÁÁ Port 3 Transmit Data Alarm Cleared Á ÁÁ Á 263 Port 3 DTR Alarm Cleared ÁÁ Á 264 Port 3 CTS Alarm Cleared ÁÁ Á 265 ÁÁ Port 3 RTS Alarm Cleared Á 266 ÁÁ Port 3 DSR Alarm Cleared Á ÁÁ Á 267 Port 3 LSD Alarm Cleared ÁÁ Á 268 Port 3 Auto Stream Disabled Cleared 269 ÁÁ Port 3 Disabled Cleared Á 270 ÁÁ Port 4 Receive Data Alarm Cleared Á ÁÁ Á 271 Port 4 Transmit Data Alarm Cleared ÁÁ Á 272ÁÁ Port 4 DTR Alarm Cleared ÁÁ 273 ÁÁ Port 4 CTS Alarm Cleared Á ÁÁ 274 Port 4 RTS Alarm Cleared Á ÁÁ ÁÁ 275 Port 4 DSR Alarm Cleared ÁÁ Á 276 ÁÁ Port 4 LSD Alarm Cleared Á 277 ÁÁ Port 4 Auto Stream Disabled Cleared Á ÁÁ Á 278 Port 4 Disabled Cleared 3-12 September A2-GB20-30

29 Traps and Report Formats NMS Events and Status Table 3-3 lists the Mode 2 NMS Traps status and variable bindings. Use Mode 2 traps when the Proxy Agent Interface application is not used. For actual Mode 2 Traps, refer to Table 3-2, Mode 2 Traps. Table 3-3. Mode 2 NMS Events and Status Trap Trap Message Alarm Clearing Action Á 301 Report Complete Success 1 One-time event notification; no clearing needed ÁÁ Á 302 Report Complete Failure 1 One-time event notification; no clearing needed ÁÁ Á 303 Command Complete Á One-time event notification; no clearing needed Success Á Command Complete Failure1 Á One-time event notification; no clearing needed 305 Test Complete Success 1 Á One-time event notification; no clearing needed Á 306 Test Complete Failure 1 One-time event notification; no clearing needed Á 307 Debug Informational 2 One-time event notification; no clearing needed ÁÁ Á 308 Debug Warning 2 Á One-time event notification; no clearing needed 309 Debug Severe Á 2 One-time event notification; no clearing needed Á 310 Hunt Group Saturation 3 Automatically clears when condition improves ÁÁ Á 311 Hunt Group Saturation One-time event notification; no clearing needed Cleared Á Low Disk Space 1 Automatically clears when condition improves ÁÁ Á 313 Low Disk Space Cleared 1 Á One-time event notification; no clearing needed 314 Device Added 3 Á One-time event notification; no clearing needed Á 315 Device Deleted 3 One-time event notification; no clearing needed ÁÁ Á 316 Device Renamed ÁÁ 4 One-time event notification; no clearing needed Á 317 Device Profile Modified 3 Á One-time event notification; no clearing needed 318 Device Unlock Forced Á 3 One-time event notification; no clearing needed Variable Bindings: 1 devmgrtraplastserialnbr, nmstempidentifier, and nmssystemtime 2 devmgrtraplastserialnbr, nmstempstring, and nmssystemtime 3 devmgrtraplastserialnbr, nmstempname1, and nmssystemtime 4 devmgrtraplastserialnbr, nmstempname1, nmssystemtime, and nmstempname A2-GB20-30 September

30 Traps and Report Formats File Formats Reports generated from the NMS Report MIB group are created in a subdirectory such as c:\pcnms\snmp\reports (assuming the default directory is used). Refer to Appendix B, NMS 6700 MIB Specifications. The report names are user-specified and are typically transferred to the SNMP Manager via FTP. All report files are generated using ASCII characters with one record per line. The date/time variable is formatted as: yyyymmdd hh:mm:ss Each field is delimited by a semicolon, and each entry is terminated by a carriage return and a linefeed. The types of reports that can be generated include: Alarm Filter Profile Alarm History Report Call Fault Report Call History Report Device Report Alarm Filter Profile Each SNMP manager can use a different filter profile. The files can be created at the 6700 NMS with a text editor or created remotely using the nmsalarm MIB. The alarm filter profile uses the standard Windows ini file conventions of section keys and key-value pairs. The default file is a straight text file. Enter a trap number and the action to be taken when a trap occurs. SNMP Proxy provides a file: \PCNMS\SNMP\CONFIG\DEFAULT.AFP 3-14 September A2-GB20-30

31 Traps and Report Formats Four sections are specified in the alarm filter profiles, one for each of the four Enterprise identifiers that are used in Enterprise traps (nms, dsu, dial, and apl). The following example illustrates the file organization used for alarm filter profiles. An action is assigned to each trap number using either the default value or an individual entry. The default value applies to all traps not specifically listed in this section and only the exceptions need to be individually entered in this file. [nms] default=s [dial] default=s 101=n 102=n [apl] default=s 101=l 102=l [dsu] default=s 101=b 102=l 103=n 104=s Value s l b n Definition Send Log Send and log Ignore Alarm History Report Record Format: date time;manager ipaddr;trap serial;device name;model family;specific trap Example: :06:00; ;100;3811-1/5;DIAL; A2-GB20-30 September

32 Traps and Report Formats Call Fault Report Record Format: device;start-date time;sample duration minutes; #calls-no-answer Example: /5; :32:00;30;2 Call History Report Record Format: loc device;rem device name;date time;duration;speed; disc reason;modem config;error control;dte speed Example: /5;3810-1/5/1; :48:00;00:00:12;19200; Rmt Cmnded Disc;DDD;MNP 5;38400 Device Report Record Format: device name;networkaddress;model type;model family;hunt group;site;cabinet;carrier;slot;circuitname;contact1; contact2 Example: /5;1/5;DIAL;3811;remotes;Middletown;MiddleCab; MiddleCar;5;1fd00123;Bob Smith;Frank Jones 3-16 September A2-GB20-30

33 Enterprise Device MIBs A Enterprise Device MIBs Overview Several Enterprise MIB definitions are included with SNMP Proxy Agent Release 2.0: Device Front Panel MIB Objects, refer to Table A-2 Device Call Directory MIB Objects, refer to Table A-3 Device Configuration MIB Objects, refer to Table A-4 NMS MIB Objects, refer to Appendix B, NMS 6700 MIB Specifications Device MIB Objects, refer to Appendix C, NMS Device MIB Specifications Refer to the COMSPHERE 6700 SNMP MIBs diskette for a full description of the COMSPHERE 6700 NMS MIBs. On this diskette, these objects are defined in the file ATTDCE.MIB. For additional installation information, refer to the readme.txt file on the COMSPHERE 6700 SNMP MIBs diskette. The MIB-II and Paradyne Enterprise MIBs are available online on the World Wide Web. Procedure To access the MIBs Download Page: 1. Access the Paradyne World Wide Web site: 2. Click on: Service & Support MIBs 6700 Proxy Agent 6700-A2-GB20-30 September 1998 A-1

34 Enterprise Device MIBs Device Front Panel MIB Overview The Front Panel MIB provides remote access to the front panel of a device and is accessed using the community procedures used for the 6700 Device MIB. Front panel keypress codes can be sent to the device in Set requests. The current front panel display can be retrieved with a Get request to the front panel display table. Refer to Table A-2, Device Front Panel MIB Objects. Device Call Directory MIB Overview The Call Directory MIB contains call directory data for a device and is accessed using the community procedures used for the 6700 Device MIB. The number of entries in a device s call directory table is dependent on the device type. Refer to Table A-3, Device Call Directory MIB Objects. Device Configuration MIB Overview MIB-II Support The Device Configuration MIB allows copying between the Active, Customer, and Factory configuration options areas and is accessed using the community procedures used for the 6700 Device MIB. If a device agent supports the Front Panel MIB, it must also support this group. Refer to Table A-4, Device Configuration MIB Objects. The SNMP Proxy Agent feature includes support for the standard Management Information Base (MIB-II) used with network management protocols in TCP/IP-based internets. Specific characteristics of the system and interface groups are noted in the following sections. The following MIB-II groups are supported as specified in RFC System Group Interface Group NOTE: Because this product is a proxy agent, the MIB-II information reflects the state of the TCP/IP interface in the workstation where the proxy is running. If a MIB-II variable is accessed for a proxied device, the MIB-II value for the proxy workstation is returned. A-2 September A2-GB20-30

35 Enterprise Device MIBs The MIB-II interface group contains information about TCP/IP interfaces. The MIB-II system group contains system description information. You can customize the text for syscontact, sysname, and syslocation. MIB browser output examples for the system group are presented in Table A-1. Table A-1. Object Descriptor MIB Browser Output Table Example sysdescr DOS 6.20 Windows 3.10 Enhanced Mode NetManage SNMP 4.00 sysobjectid NetManage, Inc. sysuptime 00:00:24.99 syscontact COMSPHERE 6700 NMS Administrator sysname Paradyne COMSPHERE 6700 syslocation COMSPHERE 6700 NMS Workstation sysservices 76 OID Prefix Tree The Structure of Management Information (SMI) defined object identifier prefix tree that includes the COMSPHERE 6700 Enterprise MIBs is shown below. iso (1) org (3) dod (6) internet (1) mgmt (2) mib-2 (1) private (4) experimental (3) enterprises (1) att-2 (74) netmanage (233) att-products (1) att-mgmt (2) paradynenms-products (13) paradynenms (23) paradyne (24) nms-6700-products (2) nms-6700 (5) attp-common (2) att67nmsoid (1) att67devoid (2)* nms (1) dev (2) attp-frontpanel (1) attp-calldir (3) attp-devconfig (7) Enterprise MIBs att67dialoid (1) att67aploid (2) att67dsuoid (3) Enterprise Traps * = Trap Mode A2-GB20-30 September 1998 A-3

36 Enterprise Device MIBs Table A-2. Device Front Panel MIB Objects Object Description Setting/Contents devfrontpanelkeypress (devfrontpanel 1) devfrontpanelcursordisplay (devfrontpanel 2) devfrontpanelcursorrow (devfrontpanel 3) devfrontpanelcursorcolumn (devfrontpanel 4) devfrontpaneldisplayrows (devfrontpanel 5) devfrontpaneldisplaycolumns (devfrontpanel 6) Front panel keypress. Any other value causes rejection of the Set request. On read, the value returned is noop(8). Front panel cursor display. CursorColumn and CursorRow are only valid when CursorDisplay is show(2). Front panel cursor row (blank). Front panel cursor column (blank). Number of front panel display rows in the devfrontpaneldisplaytable. Number of front panel display columns in the devfrontpaneldisplaytable. doubleup(1) up(2) left(3) right(4) f1(5) f2(6) f3(7) noop(8) Supported as read/write. hide(1) show(2) 2 rows Default 16 columns Default devfrontpaneldisplaytable (devfrontpanel 7) devfrontpaneldisplayentry (devfrontpaneldisplaytable 1) Contents of front panel display table. A row entry in the front panel display table. devfrontpaneldisplayrowindex (devfrontpaneldisplayentry 1) devfrontpaneldisplayrow (devfrontpaneldisplayentry 2) Index of entry in front panel display table (starts with zero). Contents of a front panel display row. For valid entries, refer to Chapter 4, Configuration, in the COMSPHERE 6700 Series Network Management System User s Guide. Non-ASCII characters that may appear: 0x04 Underscore 0x05 Solid block 0x12 Up/Down arrow 0x18 Up arrow 0x19 Down arrow 0x1A Right arrow 0x1B Left arrow 0x1C Inverse r 0x1D Left/right arrow A-4 September A2-GB20-30

37 Enterprise Device MIBs Table A-3. Device Call Directory MIB Objects Object Description Setting/Contents devcalldirentries (devcalldir 1) devcalldirtable (devcalldir 2) Number of directories in the call directory table. The device call directory table contains telephone numbers stored in a device s call directory. Refer to devcalldirentry for the number of entries. devcalldirentry (devcalldirtable 1) An entry in the call directory table. devcalldirindex (devcalldirentry 1) devcalldirpurpose (devcalldirentry 2) devcalldirid (devcalldirentry 3) devcalldirphonenumber (devcalldirentry 4) A unique value for each call directory. Call directory purpose. A textual string containing the call directory identifier. If this identifier is a number, then it may have the same value as devcalldirindex. Call directory phone number. Value ranges between 1 and the devcalldirentry value. other(1) None of the following. alarm-trap(2) dial-back-up(3) unknown(4) Default. Refer to the device document for valid characters A2-GB20-30 September 1998 A-5

38 Enterprise Device MIBs Table A-4. Device Configuration MIB Objects Object Description Setting/Contents devconfigareacopy (devconfigarea 1) This object is used to copy the entire contents of one configuration area into another configuration area. The supported number of factory configuration areas depends on the device model. The value read from this object is always noop(1). noop(1) active-to-customer1(2) active-to-customer2(3) customer1-to-active(4) customer1-to-customer2(5) customer2-to-active(6) customer2-to-customer1(7) factory1-to-active(8) factory1-to-customer1(9) factory1-to-customer2(10) factory2-to-active(11) factory2-to-customer1(12) factory2-to-customer2(13) factory3-to-active(14) factory3-to-customer1(15) factory3-to-customer2(16) factory4-to-active(17) factory4-to-customer1(18) factory4-to-customer2(19) factory5-to-active(20) factory5-to-customer1(21) factory5-to-customer2(22) factory6-to-active(23) factory6-to-customer1(24) factory6-to-customer2(25) factory7-to-active(26) factory7-to-customer1(27) factory7-to-customer2(28) factory8-to-active(29) factory8-to-customer1(30) factory8-to-customer2(31) factory9-to-active(32) factory9-to-customer1(33) factory9-to-customer2(34) Supported as read/write. A-6 September A2-GB20-30

39 NMS 6700 MIB Specifications B NMS 6700 MIB Overview The NMS 6700 MIB contains attributes of the 6700 NMS Enterprise MIB. The user can view and control the 6700 Series NMS via this MIB. The following groups are defined in the NMS 6700 MIB. Refer to Table B-1, NMS 6700 MIB Objects, for details. NMS Administration Group Displays the basic 6700 NMS location, contacts, and community name read/write setup. NMS System Group Identifies the 6700 NMS workstation. NMS Device Group Lists all 6700 devices and hunt groups. NMS Manager Group Identifies all NMS managers. NMS Test Group Allows an NMS manager to request a test be performed on a device or device pair. Refer to Action Request Tables. NMS Transaction Group Used to request that a command be executed. Refer to Action Request Tables. NMS Report Group Allows an NMS manager to request a report be set up and run. Refer to Action Request Tables. NMS Alarm Group Contains a list of actions to be taken, specific to each authorized NMS manager, when the respective trap condition occurs. NMS Error Group Lists the ten most recent SNMP errors for each NMS manager with error type. NMS Temporary Group Used to define variable bindings and type of objects contained in traps. Variable bindings in traps have OIDs. Refer to Traps OIDs in Chapter 3, Traps and Reports Formats A2-GB20-30 September 1998 B-1