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-20 December 1997

2 Copyright 1997 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 Avenue North, P.O. Box 2826, Largo, Florida 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 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 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 International, call 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 December A2-GB20-20

3 Contents About This Guide Document Purpose and Intended Audience iii Document Summary iii Product-Related Documents iv 1 Overview What is SNMP? What is the SNMP Proxy Agent Feature? Software Description Feature List Sample SNMP Network Topology SNMP Proxy Agent Feature Package Contents 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 Troubleshooting SNMP Request Timeouts A2-GB20-20 December 1997 i

4 Contents 3 Management Information Bases Access to MIBs MIB-II Support COMSPHERE 6700 Series NMS Enterprise MIBs OID Prefix Tree COMSPHERE 6700 NMS MIB Overview COMSPHERE 6700 Device MIB Overview Front Panel MIB Overview Call Directory MIB Overview Device Configuration MIB Overview SNMP Traps Overview Device Traps Mode 1 Traps Mode 2 Traps SNMP Community Views Community Name Example Transaction Commands File Formats Device Report Call History Report Call Fault Report Alarm History Report Alarm Filter Profile Index ii December A2-GB20-20

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 Glossary Index Description Overview. Provides an introduction to SNMP Proxy Agent feature. Installation. Describes hardware and software requirements and installation procedures. Management Information Bases. Provides MIB overviews and specific device traps actions. 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-20 December 1997 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-GY31 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 Security Manager Feature Supplement COMSPHERE 6700 Series Network Management System User s Guide Paradyne documents are available on the World Wide Web. Procedure To access Paradyne Product Technical Manuals: 1. Access the Paradyne World Wide Web site: 2. Click on: Service & Support Technical Manuals Contact your sales or service representative to order additional product documentation. iv December A2-GB20-20

7 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-20 December

8 Overview 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 the COMSPHERE 6700 Series NMS Release 5.0 or higher. You can install the SNMP Proxy Agent feature in any of the following COMSPHERE 6700 Series NMS installations: Single user Multiuser server Multiuser client 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 1-2 December A2-GB20-20

9 Overview Sample SNMP Network Topology Figure 1-1 shows a sample SNMP network topology. Figure 1-1. Sample SNMP Network Topology SNMP Proxy Agent Feature Package Contents The SNMP Proxy Agent feature package includes the following: SNMP feature software on one 3 1/2 disk COMSPHERE 6700 MIBs on one 3 1/2 disk One COMSPHERE 6700 Series Network Management System SNMP Proxy Agent Feature User s Guide (this manual) 6700-A2-GB20-20 December

10 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 Meg of RAM. Refer to the Hardware Description and Software Description sections 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-20 December

11 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. 2. From the Program Manager window, choose File. 3. From the File menu, choose Run. 4. In the Command Line field, type A:\INSTALL. 5. Choose OK. The Welcome window appears. 6. Choose Continue. The Product Information window appears. 2-2 December A2-GB20-20

12 Installation 7. 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. 8. Enter a subdirectory location or choose the default setting C:\PCNMS. 9. Choose Continue. The Confirmation window appears. 10. 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-20 December

13 Installation 11. The Installation Completed! window appears. 12. 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. 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. Then, check the NMS User s Guide and related documentation for troubleshooting. 2-4 December A2-GB20-20

14 3 Access to MIBs MIB-II Support The SNMP Proxy Agent MIBs are available on the COMSPHERE 6700 SNMP MIBs diskette shipped with this manual and on the World Wide Web. Refer to the COMSPHERE 6700 SNMP MIBs diskette for a full description of the COMSPHERE 6700 NMS MIBs. The MIB-II and Paradyne enterprise MIBs are available online on the World Wide Web. Procedure To access MIBs Download Page: 1. Access the Paradyne World Wide Web site: 2. Click on: Service & Support MIBs 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 A2-GB20-20 December

15 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 syslocation MIB browser output examples for the system group are presented in Table 3-1. Table 3-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 COMSPHERE 6700 Series NMS Enterprise MIBs Several new enterprise Management Information Base (MIB) definitions are introduced with SNMP Proxy Agent Release 2.0: COMSPHERE 6700 Device MIB Front Panel MIB Call Directory MIB Device Configuration MIB NOTE: For additional installation information, refer to the readme.txt file on the COMSPHERE 6700 SNMP MIBs diskette. Refer to the COMSPHERE 6700 SNMP MIBs diskette for a full description of the COMSPHERE 6700 NMS MIBs. 3-2 December A2-GB20-20

16 OID Prefix Tree Figure 3-1 shows the Structure of Management Information (SMI) defined object identifier prefix tree that includes the COMSPHERE 6700 Enterprise MIBs. 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 Figure 3-1. SMI Defined Object Identifier Prefix Tree 6700-A2-GB20-20 December

17 COMSPHERE 6700 NMS MIB Overview The NMS MIB administers the 6700 Series NMS. The following groups are defined in the NMS MIB. NMS Administration NMS System NMS Device NMS Manager NMS Test NMS Transaction NMS Report NMS Alarm NMS Error NMS Temporary COMSPHERE 6700 Device MIB Overview The Device MIB supports management of COMSPHERE 3600, 3800, and 3900 model-type devices attached to a COMSPHERE 6700 Series NMS. The device attributes and commands are defined in a device-independent manner that supports both modems and DSUs. The following groups are defined in the Device MIB. Device Administration Group Device Identity Group Device Status Group Device Circuit Quality Group Device EIA Status Group Device External Leads Group Device Command Group The SNMP Proxy Agent automatically provides a specific community name for each managed device. An SNMP management application must use the device specific community name to select which device to act upon. 3-4 December A2-GB20-20

18 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. 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. Device Configuration MIB Overview 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. SNMP Traps Overview 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: Individually filtered for each manager through the NMS Alarm MIB group. Configured to operate in Mode 1 or Mode 2. Use Mode 1 for compatibility with previous SNMP Proxy Agent releases and with the DCE Manager Proxy Agent Interface (UNIX platform). Use Mode 2 for additional traps, more information, and serialization A2-GB20-20 December

19 Device Traps Device traps are generated for device-related 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 NMS 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) 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. The COMSPHERE 6700 Device MIB variable bindings are dependent on the specific trap and Trap Mode. Refer to Tables 3-2, 3-3, and December A2-GB20-20

20 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) Table 3-2 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. 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-2. Mode 1 Traps (1 of 3) Trap Trap Description Alarm Clearing Actions 1 Á Device Failure ÁÁ Á 2 Configuration Change Notify User must explicitly clear the alarm Á 3 Test Mode Á 4 Á Disabled ÁÁ 5 Á Out of Threshold/VF Threshold ÁÁ Exceeded ÁÁ 6 Á Facility Alarm ÁÁ Á 7 External Alarm Á 8 Streaming Terminal Á 9 Á Access Security ÁÁ 10 Á TDM Failure/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 Á 6700-A2-GB20-20 December

21 Table 3-2. Mode 1 Traps (2 of 3) Trap Trap Description Alarm Clearing Actions 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 ÁÁ 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 ÁÁ 116 Á Security Download Failed ÁÁ 117 Á Front Panel Modification of ÁÁ Security Options ÁÁ 201 Á Device Failure Cleared ÁÁ 3-8 December A2-GB20-20

22 Table 3-2. Mode 1 Traps (3 of 3) Trap Trap Description Alarm Clearing Actions 202 Á Configuration Change Notify ÁÁ Cleared Á Á ÁÁ 203Á Test Mode Cleared ÁÁ 204 Á Device Disabled Cleared ÁÁ ÁÁ 205 Threshold Exceeded Cleared Á 206 Facility Alarm Cleared Á 207 Á External Alarm Cleared ÁÁ 208 Á Streaming Terminal Cleared ÁÁ ÁÁ 209 Access Security Alarm Cleared Á 210 TDM Failure/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 Modem Á Cleared ÁÁ 218 Á ÁÁ Short Holding Time Modem Á Cleared ÁÁ 219 Á Sub Tree Truncation Cleared ÁÁ 220 Á ÁÁ Good APL Line Cleared/TDM Á Failure Cleared ÁÁ Á ÁÁ 221 Tributary Timeout Cleared Á 222 Dial Tone Test Cleared Á 223 Á Redundant Power Supply ÁÁ Cleared ÁÁ 232 Á No Response Cleared ÁÁ 6700-A2-GB20-20 December

23 Mode 2 Traps Use Mode 2 traps when the Proxy Agent Interface application is not used. The following COMSPHERE 6700 Device MIB variable bindings are included in each trap message. Trap Serial Number (nmstempserial) Device Name (nmstempname) System Time (nmssystemtime) Table 3-3 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. Alarm Clearing actions per Trap: Trap Alarm Clearing Action 1, User must explicitly clear the alarm Table 3-3. 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 ÁÁ ÁÁ 8 Streaming Terminal ÁÁ Á ÁÁ 9 Access Security ÁÁ ÁÁ ÁÁ ÁÁ 10 Dial Backup Active for APL Á 11 DTE Alarm Á 12 Sub-normal Operating Speed ÁÁ Á ÁÁ 13 Primary Channel Interrupted 3-10 December A2-GB20-20

24 Table 3-3. Mode 2 Traps (2 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 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 39 FDHP Sync Loss ÁÁ ÁÁ Á Retrain Threshold 40 External Alarm A ÁÁ ÁÁ ÁÁ Signal Quality Threshold 41 External Alarm B ÁÁ ÁÁ ÁÁ Near Echo Threshold 6700-A2-GB20-20 December

25 Table 3-3. Mode 2 Traps (3 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 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 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 ÁÁ Á Á ÁÁ ÁÁ 3-12 December A2-GB20-20

26 Table 3-3. Mode 2 Traps (4 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 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 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 Á 6700-A2-GB20-20 December

27 Table 3-3. Mode 2 Traps (5 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 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 ÁÁ Á ÁÁ 233 No Signal Cleared ÁÁ Receive Level High Threshold Cleared Á Á Á ÁÁ ÁÁ 234 Out of Frame Cleared ÁÁ ÁÁ ÁÁ Receive Level Low Threshold Cleard 235 Out of Service Cleared ÁÁ Signal Noise Ratio Threshold Cleared Á Á Á ÁÁ ÁÁ 236 Abnormal Station Code Cleared ÁÁ ÁÁ ÁÁ Phase Jitter Threshold Cleared 3-14 December A2-GB20-20

28 Table 3-3. Mode 2 Traps (6 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 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 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 6700-A2-GB20-20 December

29 Table 3-3. Mode 2 Traps (7 of 7) Trap Trap Description 3600 DSU 3800 Dial 3900 APL 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-16 December A2-GB20-20

30 Table 3-4 lists the Mode 2 NMS Traps and variable bindings. Table 3-4. Mode 2 NMS Traps Trap Trap Message Alarm Clearing Action Á 301 Report Complete Success ÁÁ Á Á ÁÁ Report Complete Failure 1 Á 303Á Command Complete ÁÁ Success 1 ÁÁ 304Á Command Complete Failure 1 ÁÁ 305 Á Test Complete Success 1 ÁÁ 306 Á Test Complete Failure ÁÁ Á Á ÁÁ Debug Informational 2 Á 308Á Debug Warning 2 ÁÁ 309 Á Debug Severe 2 ÁÁ Á ÁÁ 310 Hunt Group Saturation 3 Á 311 Hunt Group Saturation Cleared ÁÁ Á 3 ÁÁ 312 Low Disk Space 1 Á 313Á Low Disk Space Cleared 1 ÁÁ 314 Á Device Added 3 ÁÁ Á ÁÁ 315 Device Deleted Á ÁÁ Device Renamed Á 4 ÁÁ 317 Á Device Profile Modified 3 ÁÁ 318 Á Device Unlock Forced 3 ÁÁ Variable Bindings: 1 devmgrtraplastserialnbr, nmstempidentifier, nmssystemtime 2 devmgrtraplastserialnbr, nmstempstring, nmssystemtime 3 devmgrtraplastserialnbr, nmstempname1, nmssystemtime 4 devmgrtraplastserialnbr, nmstempname1, nmssystemtime, nmstempname A2-GB20-20 December

31 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. To do so, 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. 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 reads and writes. Call Directory MIB and Front Panel MIB both use the same communities as the Device MIB. 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 pinkmodem December A2-GB20-20

32 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. Transaction Commands Transaction commands are entered by writing (issuing a Set) to the transaction command string object, nmstransactioncommandstring, in an allocated transaction table entry. Transaction commands are listed in Table 3-5. The syntax used in the Transaction commands table is: Symbol Translation < > Required entry [ ] Optional { } Either/or choice within brackets; one entry required Shown within brackets to represent either/or option NOTE: Transaction commands are not case-sensitive; however, their arguments may be. Table 3-5. Transaction Commands (1 of 2) Command Action Á LOCK <device> Locks device s front panel, call directory, Á options/thresholds, and tests. Á UNLOCK <device> Unlocks device from lock placed by LOCK Á command. FORCE <device> ÁÁ Forces a device to unlock, regardless of the Á lock owner. SET {OPTION THRESHOLD} ÁÁ Acts upon the scratch buffer. The scratch <option> = <value> [;<modifier>] ÁÁ buffer persists as long as the transaction table entry remains valid. Á UPLOAD {OPTION THRESHOLD} ÁÁ Transfers active option/threshold settings from <device> the device to the scratch buffer. Á DOWNLOAD {OPTION THRESHOLD} Transfers scratch buffer to active ÁÁ <device> option/threshold settings in the device. Á SAVE {OPTION THRESHOLD} Saves the scratch buffer to a disk file. ÁÁ <file name> Á LOAD {OPTION THRESHOLD} Loads the scratch buffer from a disk file. Á <file name> 6700-A2-GB20-20 December

33 Table 3-5. Transaction Commands (2 of 2) Command Action GET {OPTION THRESHOLD} ÁÁ Responds with value (and modifier) for the <option> specified option/threshold. Numbers are Á represented by ASCII numerals. Multiple Á fields are separated by semicolons. RANGE {OPTION THRESHOLD} ÁÁ Responds with option/threshold value range <device> [<option>] ÁÁ for the specified device based on device type. Á The range response occurs in nmstransactionresponsetable. Á The type of response is indicated in Á nmstransactionresponsestring Á {OPTIONS CHOICE INTEGER TEXT}. Á Range response format for response type OPTIONS (when option not specified): Á option1, option2, etc. Á Example option list for APL devices: Á Async/Sync Mode Á Async DTE Rate Á Async Number of Bits Á Async Parity Bit Á Async Stop Bits DTR Action Á DSR Control Á RTS Action Á CTS Control, etc. Á Range response format (when option is Á specified) for following response types: Á CHOICE: enum1, enum2, enum3, etc. Á INTEGER: low, high, inc, scale Á TEXT: minchrs (low), maxchrs (high) Á Example choice list for option Async Parity Bit: Á None, Even, Odd, Mark, Space Á DELETE REPORT <file name> Delete report with specified name from the Á SNMP\REPORT directory. Á EXIST REPORT <file name> Tests for existence of a file with specified Á name in the SNMP\REPORT directory. Á Response in the nmstransactionresponsestring is either Á EXISTS or NOT FOUND 3-20 December A2-GB20-20

34 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). 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 are: 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 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 Call Fault Report Record Format: device;start-date time;sample duration minutes; #calls-no-answer Example: /5; :32:00;30; A2-GB20-20 December

35 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;2 Alarm Filter Profile This method can be used in place of the Alarm MIB functions. 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 Four sections are specified, 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. [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 3-22 December A2-GB20-20

36 Index A alarm clearing, 3-7 filter profile, 3-22 history report, 3-22 C call fault report, 3-21 history report, 3-21 Call Directory MIB, 3-5 COMSPHERE 6700 Series NMS Enterprise MIBs, 3-2 D device MIB, 3-4 report, 3-21 traps, 3-6 F file formats, 3-21 front panel MIB, 3-5 H hardware requirements, 2-1 I installation, 2-1 M Management Information Bases Call Directory MIB, 3-5 Device MIB, 3-4 Front Panel MIB, 3-5 MIB II System Group, 3-2 NMS Enterprise MIBs, 3-2 NMS MIB, 3-4 online access, 3-1 mode 1 traps, 3-7 mode 2 traps, 3-17 N NMS MIB, 3-4 P package contents, 1-3 primary alerts, 3-7 product related documents, iv S SNMP community views, 3-18 overview, 1-1 Proxy Agent for TCP/IP, 2-4 request timeouts, 2-4 sample network topology, 1-3 SNMP Proxy Agent feature list, 1-2 overview, 1-1 package contents, 1-3 SNMP traps, 3-5 software requirements, A2-GB20-20 December 1997 IN-1

37 Index T Timeouts, SNMP requests, 2-4 transaction commands, 3-19 traps device, 3-6 mode 1, 3-7 mode 2, 3-17 SNMP, 3-5 Troubleshooting, 2-4 V variable bindings, 3-7 W World Wide Web online access to MIBs, 3-1 technical manuals access, iv IN-2 December A2-GB20-20