Summary of Contents for Paradyne COMSPHERE 6700 Series
Page 1
COMSPHERE 6700 SERIES NETWORK MANAGEMENT SYSTEM SNMP PROXY AGENT FEATURE USER’S GUIDE Document No. 6700-A2-GB20-30 September 1998...
Page 2
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 September 1998 6700-A2-GB20-30...
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.
3811, and 3820, User’s Guide COMSPHERE 3900 Series Modems, Models 3910 and 3911, Point-to-Point/Multipoint, Installation and Operation Manual 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...
What is the SNMP Proxy Agent Feature? The COMSPHERE 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. 6700-A2-GB20-30...
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.
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.
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.
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. September 1998 6700-A2-GB20-30...
Page 13
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. 6700-A2-GB20-30 SNMP Proxy Agent Installation September 1998...
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 . September 1998 6700-A2-GB20-30...
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 .
Allow at least 30 seconds (recommended minimum). For tributary or tail circuit access, 60 seconds may be required. 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 .
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 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)
Sub Tree Truncation TDM Failure/Good APL Line Tributary Timeout Dial Tone Test Redundant Power Supply 6700-A2-GB20-30 Alarm Clearing Actions Automatically clears when condition improves User must explicitly clear the alarm Automatically clears when condition improves Automatically clears when condition improves...
Page 20
One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification; no clearing needed September 1998 6700-A2-GB20-30...
Page 21
Tributary Timeout Cleared Dial Tone Test Cleared Redundant Power Supply Cleared No Response Cleared 6700-A2-GB20-30 Alarm Clearing Actions One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification; no clearing needed One-time event notification;...
Use Mode 2 traps when the Proxy Agent Interface application is not used. To use the Proxy Agent Interface application, refer to The following COMSPHERE 6700 NMS MIB variable bindings are included in each trap message. Trap Serial Number (nmsTempSerial)
Page 23
Out of Service Signal Noise Ratio Threshold Abnormal Station Code Phase Jitter Threshold Facility Alarm due to Bipolar Violations Frequency Offset Threshold CMI Detected Facility Alarm Non-linear Distortion Threshold 6700-A2-GB20-30 3600 DSU September 1998 Traps and Report Formats 3800 Dial 3900 APL...
Page 24
Port 2 LSD Alarm Port 2 Auto Stream Disabled Port 2 Disabled Port 3 Receive Data Alarm Port 3 Transmit Data Alarm Port 3 DTR Alarm Port 3 CTS Alarm Port 3 RTS Alarm 3600 DSU September 1998 3800 Dial 3900 APL 6700-A2-GB20-30...
Page 25
User ID and Password Combination Invalid Invalid User ID – Password Valid for Device Invalid Access Time User Login Hack – Multiple Sequential Password Retries Device Security Table Invalid 6700-A2-GB20-30 3600 DSU September 1998 Traps and Report Formats 3800 Dial 3900 APL...
Page 26
Short Holding Time Modem Cleared Sub Tree Truncation Cleared TDM Failure Cleared Good APL Line Cleared Tributary Timeout Cleared Dial Tone Test Cleared Redundant Power Supply Cleared No Response Cleared 3-10 3600 DSU September 1998 3800 Dial 3900 APL 6700-A2-GB20-30...
Page 27
Port 1 LSD Alarm Cleared Port 1 Auto Stream Disabled Cleared Port 1 Disabled Cleared Port 2 Receive Data Alarm Cleared Port 2 Transmit Data Alarm Cleared 6700-A2-GB20-30 3600 DSU September 1998 Traps and Report Formats 3800 Dial 3900 APL...
Page 28
Port 4 CTS Alarm Cleared Port 4 RTS Alarm Cleared Port 4 DSR Alarm Cleared Port 4 LSD Alarm Cleared Port 4 Auto Stream Disabled Cleared Port 4 Disabled Cleared 3-12 3600 DSU September 1998 3800 Dial 3900 APL 6700-A2-GB20-30...
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.
NMS MIB Objects, refer to Appendix B, Device MIB Objects, refer to Appendix C, 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.
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.
OID Prefix Tree The Structure of Management Information (SMI) defined object identifier prefix tree that includes the COMSPHERE 6700 Enterprise MIBs is shown below. paradyneNMS-products (13) nms-6700-products (2) att67nmsOid (1) att67dialOid (1) att67aplOid (2) att67dsuOid (3) * = Trap Mode 1...
Page 36
Contents of a front panel display row. (devFrontPanelDisplayEntry 2) For valid entries, refer to Chapter 4, Configuration , in the COMSPHERE 6700 Series Network Management System User’s Guide . Setting/Contents Supported as read/write. Supported as read-only. Supported as read-only.
Page 37
(devCallDirEntry 3) identifier. If this identifier is a number, then it may have the same value as devCallDirIndex. devCallDirPhoneNumber Call directory phone number. (devCallDirEntry 4 6700-A2-GB20-30 Setting/Contents Supported as read-only. Refer to devCallDirEntry for the number of entries. — Value ranges between 1 and the devCallDirEntry value.
Page 38
Supported as read/write. September 1998 6700-A2-GB20-30...
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, Objects , for details.
NMS 6700 MIB Specifications Action Request Tables Using the NMS 6700 MIB, the following action request tables can be created. The test, transaction, and report groups in the NMS 6700 MIB have tables that are used in a similar manner, very much like table usage for RMON. Refer to Table B-1, NMS 6700 MIB Objects, for object details.
Accessing the NMS 6700 MIB To access the NMS 6700 MIB to create a table, an NMS Manager must have read or read/write permission in the object nmsManagerAccess nmsManagerEntry3 An NMS Manager with permission to Set an entry status object to createRequest(2) can set up a table.
NMS 6700 MIB Specifications 6. After the action is completed, the NMS manager can get the appropriate object values in the table entry with the results. 7. After obtaining the results, the NMS manager will Set the object nms xxx EntryStatus to the value of invalid(4). This will release the table entry for use by other NMS managers.
IP address of the NMS manager requesting the Set. 3. Set the object nmsTransactionCommandString.2 to the value GET OPTION DTR Action. The option name must match exactly those found in the 6700 database or the command execution will fail. Valid option names and values can be obtained using the RANGE command.
NMS manager, but the file created still exists on the 6700 disk. NMS 6700 MIB Objects The NMS 6700 MIB contains Validity Object pairs. The first object indicates the validity of the second object in the pair. Table B-1. NMS 6700 MIB Objects (1 of 16)
Page 49
Table B-1. NMS 6700 MIB Objects (5 of 16) Object nmsTestType (nmsTestEntry 3) nmsTestDuration (nmsTestEntry 4) 6700-A2-GB20-30 Description This object is the test type. Applicable for the test types: bert(6) local-loop-bert(7) rdl-bert(8) digital-test(9) end-to-end-test(10) September 1998 NMS 6700 MIB Specifications Setting/Contents self-test(1) –...
Page 50
NMS 6700 MIB Specifications Table B-1. NMS 6700 MIB Objects (6 of 16) Object nmsTestPortNumber (nmsTestEntry 5) nmsTestRemoteName (nmsTestEntry 6) nmsTestStatus (nmsTestEntry 7) nmsTestLocalTotalSecondsValidity (nmsTestEntry 8) B-12 Description Port number. Only applicable to a multiport device for the following test...
Page 51
Table B-1. NMS 6700 MIB Objects (7 of 16) Object nmsTestLocalTotalSeconds (nmsTestEntry 9) nmsTestLocalErrorSecondsValidity (nmsTestEntry 10) nmsTestLocalErrorSeconds (nmsTestEntry 11) nmsTestLocalTotalBlocksValidity (nmsTestEntry 12) nmsTestLocalTotalBlocks (nmsTestEntry 13) nmsTestLocalErrorBlocksValidity (nmsTestEntry 14) nmsTestLocalErrorBlocks (nmsTestEntry 15) 6700-A2-GB20-30 Description Total seconds for local device. For the 3600 Series devices, this variable is also called elapsed seconds.
Page 52
NMS 6700 MIB Specifications Table B-1. NMS 6700 MIB Objects (8 of 16) Object nmsTestRemoteTotalSeconds Validity (nmsTestEntry 16) nmsTestRemoteTotalSeconds (nmsTestEntry 17) nmsTestRemoteErrorSeconds Validity (nmsTestEntry 18) nmsTestRemoteErrorSeconds (nmsTestEntry 19) nmsTestRemoteTotalBlocksValidity (nmsTestEntry 20) nmsTestRemoteTotalBlocks (nmsTestEntry 21) nmsTestRemoteErrorBlocksValidity (nmsTestEntry 22) B-14 Description Validity of the test result object nmsTestRemoteTotalSeconds.
Page 53
Table B-1. NMS 6700 MIB Objects (9 of 16) Object nmsTestRemoteErrorBlocks (nmsTestEntry 23) nmsTestTimeOutsValidity (nmsTestEntry 24) nmsTestTimeOuts (nmsTestEntry 25) nmsTestOwner (nmsTestEntry 26) nmsTestEntryStatus (nmsTestEntry 27) nmsTestNotify (nmsTestEntry 28) nmsTestErrorDesc (nmsTestEntry 29) nmsTransactionEntries (nmsTransaction 1) 6700-A2-GB20-30 Description Remote Error Bits. Not used for the 3800 and 3900 Series devices.
Page 56
NMS 6700 MIB Specifications Table B-1. NMS 6700 MIB Objects (12 of 16) Object nmsReportType (nmsReportEntry 3) nmsReportName (nmsReportEntry 4) nmsReportScope (nmsReportEntry 5) nmsReportStart (nmsReportEntry 6) nmsReportStop (nmsReportEntry 7) nmsReportStatus (nmsReportEntry 8) nmsReportErrorDesc (nmsReportEntry 9) B-18 Description The report type is selected via this object.
Page 57
Table B-1. NMS 6700 MIB Objects (13 of 16) Object nmsReportOwner (nmsReportEntry 10) nmsReportOwnerIpAddr (nmsReportEntry 11) nmsReportNotify (nmsReportEntry 12) nmsAlarmTable (nmsAlarm 1) nmsAlarmEntry (nmsAlarmTable 1) NmsAlarmRecipient (nmsAlarmEntry 1) nmsAlarmClass (nmsAlarmEntry 2) nmsAlarmNumber (nmsAlarmEntry 3) 6700-A2-GB20-30 Description Identifies the system or person that configured this entry and is therefore using the resources assigned to it.
Page 59
Table B-1. NMS 6700 MIB Objects (15 of 16) Object nmsErrorRecipient (nmsErrorEntry 1) nmsErrorRequestedId (nmsErrorEntry 2) nmsErrorType (nmsErrorEntry 3) nmsErrorDesc (nmsErrorEntry 4) nmsTempName1 (nmsTemp 1) nmsTempName2 (nmsTemp 2) 6700-A2-GB20-30 Description This object is the IP address of the NMS manager which received the error.
NMS 6700 MIB Specifications Table B-1. NMS 6700 MIB Objects (16 of 16) Object nmsTempIdentifier (nmsTemp 3) nmsTempString (nmsTemp 4) nmsTempSerial (nmsTemp 5) Transaction Commands Transaction commands are entered by writing (issuing a Set) to the transaction command string object, nmsTransactionCommandString, in an allocated transaction table entry.
Page 61
None, Even, Odd, Mark, Space Delete report with specified name from the SNMP\REPORT directory. Tests for existence of a file with specified name in the SNMP\REPORT directory. Response in the nmsTransactionResponseString is either EXISTS or NOT FOUND. September 1998 NMS 6700 MIB Specifications B-23...
Page 62
NMS 6700 MIB Specifications This page intentionally left blank. B-24 September 1998 6700-A2-GB20-30...
The NMS 6700 Device MIB contains the common device attributes. There is an instance of the Device MIB for each device in the 6700 network. Each device is identified by a unique Community String. SNMP management applications must use the Community Name to specify the device to access.
Page 67
Table C-1. NMS 6700 Device MIB Objects (4 of 17) Object devStatusAlert (devStatus 3) devStatusAlertDesc (devStatus 4) 6700-A2-GB20-30 Description Setting/Contents The current Alerts for the The Primary Alerts and their bit device. The bit position number positions are defined as follows:...
Page 68
NMS Device MIB Specifications Table C-1. NMS 6700 Device MIB Objects (5 of 17) Object devStatusState (devStatus 5) devStatusSpeed (devStatus 6) devStatusCtrlTrib (devStatus 7) devStatusConfigType (devStatus 8) devStatusPollingState (devStatus 9) devStatusLockingState (devStatus 10) devStatusLockingTask (devStatus 11) devStatusLockingIpAddress (devStatus 12) Description Setting/Contents The current state of the device.