Instruction/ maintenance manual of the product 3700-A2-GB20-10 Paradyne
Go to page of 120
AREA CODE CHANGE Please note that the area code for Paradyne Corporation in Largo, Florida has changed from 813 to 727. For any Paradyne telephone number that appears in this manual with an 813 area code, dial 727 instead.
COMSPHERE 6700 SERIES NETWORK MANAGEMENT SYSTEM SNMP PROXY AGENT FEA TURE USER’S GUIDE Document No. 6700-A2-GB20-10.
A Issue 2 December 1996 COMSPHERE 6700 Series Network Management System SNMP Proxy Agent Featur e User ’s Guide 6700-A2-GB20-10 Issue 2 (December 1996) Changes and enhancements to the product and to the information herein will be documented and issued as a new release.
i Issue 2 December 1996 Preface Related Documents v . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering Information vi . . . . . . . . . . . . . . . . . . . . . 1 Overview What is SNMP? 1-1 . . . . . . . . .
ii Issue 2 December 1996 3 Management Information Bases MIB-II Support 3-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MIB-II System Group Overview 3-2 . . . . . . . . . . . . MIB-II Interface Group Overview 3-2 .
iii Issue 2 December 1996 Figures 1 Overview 1-1 Sample SNMP Network T opology 1-3 . . . . . . . . . . 2 Installation 2-1 Welcome Window 2-5 . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Product Information Window 2-6 . . . . . . . .
iv Issue 2 December 1996 T ables 2 Installation 2-1 Supported Network Adapter Boards 2-2 . . . . . . . . 3 Management Information Bases 3-1 MIB Browser Output T able 3-2 . . . . . . . . . . . . . . . . 3-2 Primary Alert T raps 3-8 . . . . .
v Issue 2 December 1996 P reface This guide describes how to install and use the COMSPHERE r 6700 Series Network Management System (NMS) SNMP Proxy Agent feature.
Preface vi Issue 2 December 1996 3910-A2-GN32 COMSPHERE 3900 Series Modems, Models 3910 and 391 1, Point–to–Point/Multipoint, Installation and Operation Manual 6700-A2-GB21 COMSPHERE 6700 Series N.
1-1 Issue 2 December 1996 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.
Overview 1-2 Issue 2 December 1996 Software Description The SNMP Proxy Agent feature includes NetManage Enhanced Windows TCP/IP (NEWT t ) software, which supports transmission of SNMP messages across Ethernet r , T oken Ring, FDDI, SLIP , and PPP interfaces.
Overview 1-3 Issue 2 December 1996 Integrated TCP/IP , UDP/IP , and SNMP Protocol support Concurrent Ethernet, T oken Ring, FDDI, SLIP , and PPP interface support Sample SNMP Network T opology Figure 1-1 shows a sample SNMP network topology . Figure 1-1.
Overview 1-4 Issue 2 December 1996 SNMP Proxy Agent Featur e Package Contents The SNMP Proxy Agent feature package includes the following: SNMP feature software on one 3 1/2 ″ disk COMSPHERE.
2-1 Issue 2 December 1996 Installation 2 Hardware and Softwar e Requirements The SNMP Proxy Agent feature has the same hardware and software requirements as the basic single-user NMS. Refer to the Hardware Description and Software Description sections of the COMSPHERE 6700 Series Network Management System User ’s Guide for details.
Installation 2-2 Issue 2 December 1996 T able 2-1. Supported Network Adapter Boards (1 of 2) Interface V endor Model Ethernet 3COM 3C501 Ether Link 3C503 Ether Link II 3C505 Ether Link Plus 3C507 Ethe.
Installation 2-3 Issue 2 December 1996 T able 2-1. Supported Network Adapter Boards (2 of 2) Interface Model V endor Ethernet Xircom (Continued) All PE3 Models Other (NDIS Driver Required) T oken Ring.
Installation 2-4 Issue 2 December 1996 SNMP Feature Installation and Configuration Information General Where to install the software (c:pcnms): Network Interface Name (Ethernet0): Network Interface T ype (Ethernet): Workstation Internet Address of Workstation (192.
Installation 2-5 Issue 2 December 1996 Installing the SNMP Proxy Agent Feature T o 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 .
Installation 2-6 Issue 2 December 1996 6. Choose Continue . The Product Information window appears, as shown in Figure 2-2. Figure 2-2. Pr oduct Information Window 7. Choose Ye s . The Destination Directory window appears, as shown in Figure 2-3. Figure 2-3.
Installation 2-7 Issue 2 December 1996 9. Choose Continue . The Confirmation window appears, as shown in Figure 2-4. Figure 2-4. Confirmation W indow 10. Choose Install to confirm the installation of the NMS software into the specified directory . The Completion status window appears, as shown in Figure 2-5.
Installation 2-8 Issue 2 December 1996 Figure 2-6. Installation Completed! W indow 1 1. 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.
3-1 Issue 2 December 1996 Management Information Bases 3 MIB-II Support 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. This support is provided by the NEWT component.
Management Information Bases 3-2 Issue 2 December 1996 MIB-II System Group Overview The MIB-II system group contains system description information. Y ou may customize the sysContact , sysName , and sysLocation text. For further details, refer to the NEWT TCP/IP for Windows Installation and User ’ s Guide.
Management Information Bases 3-3 Issue 2 December 1996 COMSPHERE 6700 Series NMS Enterprise MIBs Four new enterprise Management Information Base (MIB) definitions are introduced with SNMP Proxy Agent Release 1.
Management Information Bases 3-4 Issue 2 December 1996 Figure 3-1. SMI Defined Object Identifier Pr efix T ree The COMSPHERE 6700 NMS and Device MIBs are defined in the appendices.
Management Information Bases 3-5 Issue 2 December 1996 COMSPHERE 6700 NMS MIB Overview The NMS MIB administers the 6700 Series NMS. The following groups are defined in the NMS MIB.
Management Information Bases 3-6 Issue 2 December 1996 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.
Management Information Bases 3-7 Issue 2 December 1996 SNMP T raps Overview COMSPHERE 6700 NMS alerts may be exported to authorized SNMP managers as SNMP traps. T raps are forwarded for any event that makes it through the COMSPHERE 6700 Series NMS’s alert filter .
Management Information Bases 3-8 Issue 2 December 1996 NOTE: The state of a device’s primary alerts can also be read from devStatusAlert . T able 3-2.
Management Information Bases 3-9 Issue 2 December 1996 T able 3-2. Primary Alert T raps (2 of 2) 3900 3800 3600 Primary Alert T raps T rap 21 T ributary Timeout D 22 Dial T one D 23 Redundant Power Supply D 32 No Response D D D T able 3-3 identifies which system security event traps apply to the specific devices.
Management Information Bases 3-10 Issue 2 December 1996 T able 3-3. System Security Event T raps (2 of 2) 3900 3800 3600 System Security Event T raps T rap 11 2 Invalid Access Time D D 11 3 User Login.
Management Information Bases 3-1 1 Issue 2 December 1996 T able 3-4. Primary Alert Clear Notifications (2 of 2) 3900 3800 3600 Primary Alert T raps T rap 213 Primary Channel Interrupted Cleared D D 21.
Management Information Bases 3-12 Issue 2 December 1996 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.
A-1 Issue 2 December 1996 MIB Definition A NMS6700-MIB DEFINITIONS ::= BEGIN –– T itle: COMSPHERE 6700 NMS MIB for Customer Network Management –– Copyright (C) 1996, Paradyne. All rights reserved. –– –– This file may be freely copied and distributed as –– long as no changes are made to it.
MIB Definition A-2 Issue 2 December 1996 –– –– NMS MIB Groups –– nmsAdmin OBJECT IDENTIFIER ::= { nms 1 }–– administration nmsSystem OBJECT IDENTIFIER ::= { nms 2 }–– system identi.
MIB Definition A-3 Issue 2 December 1996 –– NMS Administration Group (nms 1) –– NMS Information nmsAdminName OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”Name of the 6700 NMS.” ::= { nmsAdmin 1 } nmsAdminLocation OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
MIB Definition A-4 Issue 2 December 1996 access to all objects in the COMSPHERE 6700 NMS MIB. An exception applies with the nmsAdminNmsW riteCommunity object for which the read community provides no access.” ::= { nmsAdmin 5 } nmsAdminNmsW riteCommunity OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
MIB Definition A-5 Issue 2 December 1996 –– NMS System Group (nms 2) –– T ime of Day nmsSystemT ime OBJECT -TYPE SYNT AX DateAndT ime ACCESS read-only ST A TUS mandatory DESCRIPTION ”Specifies the date and time in RFC 1514 DateAndT ime format.
MIB Definition A-6 Issue 2 December 1996 –– Layout of one entry in nmsSystemFeatureT able. NmsSystemFeatureEntry ::= SEQUENCE { nmsSystemFeatureIndex INTEGER, nmsSystemFeatureName DisplayString, n.
MIB Definition A-7 Issue 2 December 1996 ::= { nmsSystemFeatureEntry 3 } –– Serial Number nmsSystemFeatureSerial OBJECT -TYPE SYNT AX DisplayString (SIZE (0..25)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Serial number of system product or feature.
MIB Definition A-8 Issue 2 December 1996 –– NMS Device Group (nms 3) nmsDevices OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”The number of devices configured in the 6700 nms network. This is also the number of entries in nmsDeviceT able.
MIB Definition A-9 Issue 2 December 1996 ”This object is the row index of the nmsDevice table. Note that a device’ s index in the table may change as devices are added or removed from the 6700 nms network, thus this index should not be used as a device ID.
MIB Definition A-10 Issue 2 December 1996 DESCRIPTION ”An entry in the manager table. Entries are indexed by IP Address.” INDEX { nmsManagerAddress } ::= { nmsManagerT able 1 } –– Layout of one entry in nmsManagerT able.
MIB Definition A-1 1 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”This object is the NMS manager name. The manager name must be unique in the table. If a set operation is performed for a non-existing instance (i.e., index is a new IP address), a new table entry for the specified IP address will be created.
MIB Definition A-12 Issue 2 December 1996 nmsManagerLocation OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”T ext string describing manager location.” ::= { nmsManagerEntry 5 } –– Contact1 nmsManagerContact1 OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
MIB Definition A-13 Issue 2 December 1996 –– NMS T est Group (nms 5) –– T extual Convention for T est Result V alidity Indicator T estResultV alidity ::= INTEGER { valid-final(1), valid-interm.
MIB Definition A-14 Issue 2 December 1996 nmsT estEntry OBJECT -TYPE SYNT AX NmsT estEntry ACCESS not-accessible ST A TUS mandatory DESCRIPTION ”An entry in the nms test table.
MIB Definition A-15 Issue 2 December 1996 –– Layout of one entry in nmsT estT able. NmsT estEntry ::= SEQUENCE { nmsT estIndex INTEGER, nmsT estDeviceName DisplayString, nmsT estT ype INTEGER, nms.
MIB Definition A-16 Issue 2 December 1996 nmsT estRemoteT otalBlocks INTEGER, nmsT estRemoteErrorBlocksV alidity T estResultV alidity , nmsT estRemoteErrorBlocks INTEGER, nmsT estTimeOutsV alidity T e.
MIB Definition A-17 Issue 2 December 1996 SYNT AX INTEGER { self-test(1), local-loop(2), rem-digital-loop(3), loc-digital-loop(4), dte-loop(5), bert(6), local-loop-bert(7), rdl-bert(8), digital-test(9), end-to-end-test(10), abort(1 1) } ACCESS read-write ST A TUS mandatory DESCRIPTION ”This object is the test type.
MIB Definition A-18 Issue 2 December 1996 SYNT AX INTEGER ACCESS read-write ST A TUS mandatory DESCRIPTION ”T est duration in seconds (or blocks). Only applicable for the following test types: bert, local-loop-bert, rdl-bert, digital-test, end-to-end-test.
MIB Definition A-19 Issue 2 December 1996 ::= { nmsT estEntry 6 } –– –– T est Status –– nmsT estStatus OBJECT -TYPE SYNT AX INTEGER { idle(1), testMode(2), testRunning(3), testAborted(4), testFailed(5) } ACCESS read-only ST A TUS mandatory DESCRIPTION ”T est status.
MIB Definition A-20 Issue 2 December 1996 nmsT estLocalT otalSeconds OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”T otal seconds for local device. (For 3600 model type devices, this variable is also called elapsed seconds.
MIB Definition A-21 Issue 2 December 1996 –– Local Error Blocks (Bits for 3600 DSU) nmsT estLocalErrorBlocksV alidity OBJECT -TYPE SYNT AX T estResultV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the nmsT estLocalErrorBlocks test result object.
MIB Definition A-22 Issue 2 December 1996 DESCRIPTION ”V alidity of the nmsT estRemoteErrorSeconds test result object.” ::= { nmsT estEntry 18 } nmsT estRemoteErrorSeconds OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Errored seconds elapsed for the remote device.
MIB Definition A-23 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”Remote Error blocks (actually Bits). Not used for 3800 and 3900 model type devices.
MIB Definition A-24 Issue 2 December 1996 –– Entry Status nmsT estEntryStatus OBJECT -TYPE SYNT AX INTEGER { valid(1), createRequest(2), underCreation(3), invalid(4) } ACCESS read-write ST A TUS mandatory DESCRIPTION ”The status of this nmsT estT able entry .
B-1 Issue 2 December 1996 Device Enterprise MIB Definition B NMS6700-DEV -MIB DEFINITIONS ::= BEGIN –– T itle: COMSPHERE 6700 Device MIB for Customer Network Management –– –– Copyright (C) 1996, Paradyne. All rights reserved. –– –– This file may be freely copied and distributed as –– long as no changes are made to it.
Device Enterprise MIB Definition B-2 Issue 2 December 1996 –– –– Enterprise Identification for COMSPHERE 6700 Device MIB –– dev OBJECT IDENTIFIER ::= { nms-6700 2 } –– Device MIB –.
Device Enterprise MIB Definition B-3 Issue 2 December 1996 –– Device Administration Group (dev 1) devAdminName OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Device name. This is the name used by the COMSPHERE 6700 NMS to identify the device.
Device Enterprise MIB Definition B-4 Issue 2 December 1996 devAdminCabinet OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Device cabinet name used by COMSPHERE 6700 NMS.” ::= { devAdmin 5 } devAdminCarrier OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
Device Enterprise MIB Definition B-5 Issue 2 December 1996 ”Device contact string #2.” ::= { devAdmin 10 } devAdminComment OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
Device Enterprise MIB Definition B-6 Issue 2 December 1996 multi point option is installed.” ::= { devAdmin 14 } devAdminTdmOption OBJECT -TYPE SYNT AX INTEGER { tdm-installed(1), tdm-not-installed(2) } ACCESS read-only ST A TUS mandatory DESCRIPTION ”A value of tdm-installed(1) indicates that a time division multiplexer option is installed.
Device Enterprise MIB Definition B-7 Issue 2 December 1996 –– Device Identity Group (dev 2) devIdentityModel OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Model number .” ::= { devIdentity 1 } devIdentityLineSpeed OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
Device Enterprise MIB Definition B-8 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”Access module (if applicable, otherwise length is zero).” ::= { devIdentity 6 } devIdentityRestoralOption OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
Device Enterprise MIB Definition B-9 Issue 2 December 1996 devIdentityOption1 OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Option 1 (if applicable, otherwise length is zero).” ::= { devIdentity 12 } devIdentityOption2 OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
Device Enterprise MIB Definition B-10 Issue 2 December 1996 ”Option 6 (if applicable, otherwise length is zero).” ::= { devIdentity 17 }.
Device Enterprise MIB Definition B-1 1 Issue 2 December 1996 –– Device Status Group (dev 3) devStatusConnectedDevice OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”The device name of the connected device.
Device Enterprise MIB Definition B-12 Issue 2 December 1996 service-line(15), non-answering-modem(16), short-holding-time-modem(17), sub-tree-truncation(18), tdm-failure-good-apl(19), trib-timeout(20), dial-tone(21), redundant-power(22), no-response(31)” ::= { devStatus 3 } devStatusAlertDesc OBJECT -TYPE SYNT AX DisplayString (SIZE (0.
Device Enterprise MIB Definition B-13 Issue 2 December 1996 devStatusSpeed OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”The current data rate of the device, in bits per second. A value of zero indicates that the device is training.
Device Enterprise MIB Definition B-14 Issue 2 December 1996 ”Indicates the polling state of the device in the network.” ::= { devStatus 9 }.
Device Enterprise MIB Definition B-15 Issue 2 December 1996 –– Circuit Quality Group (dev 4) –– T ype Definition for Circuit Quality V alidity indicators –– V alidity is not-used(6) if not supported by device type.
Device Enterprise MIB Definition B-16 Issue 2 December 1996 ”V alidity of the devCirQualMeanSquareError object.” ::= { devCirQual 3 } devCirQualMeanSquareError OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Mean squared error .
Device Enterprise MIB Definition B-17 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”1004 Hz loss.” ::= { devCirQual 8 } –– Signal to Noise Ratio devCirQualSignalT oNoiseV alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualSignalT oNoise object.
Device Enterprise MIB Definition B-18 Issue 2 December 1996 –– Phase Jitter 20–300 Hz devCirQualPhaseJitter300V alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualPhaseJitter300 object.
Device Enterprise MIB Definition B-19 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualNegativeAttenuation object.” ::= { devCirQual 17 } devCirQualNegativeAttenuation OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Negative attenuation.
Device Enterprise MIB Definition B-20 Issue 2 December 1996 SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Frequency offset. Units are (Hz * 10).
Device Enterprise MIB Definition B-21 Issue 2 December 1996 DESCRIPTION ”Retrains. Integer value represents the number of retrain events during the last 15 minutes.
Device Enterprise MIB Definition B-22 Issue 2 December 1996 –– Phase Hits devCirQualPhaseHitsV alidity OBJECT -TYPE SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualPhaseHits object.
Device Enterprise MIB Definition B-23 Issue 2 December 1996 ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualDropouts object.” ::= { devCirQual 35 } devCirQualDropouts OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Dropouts.
Device Enterprise MIB Definition B-24 Issue 2 December 1996 SYNT AX CirQualV alidity ACCESS read-only ST A TUS mandatory DESCRIPTION ”V alidity of the devCirQualNearEndEcho object.” ::= { devCirQual 39 } devCirQualNearEndEcho OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Near end echo.
Device Enterprise MIB Definition B-25 Issue 2 December 1996 ::= { devCirQual 43 } devCirQualFarEndDelay OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Far end delay . Units are in milliseconds. Possible range 0 to 4095 ms.
Device Enterprise MIB Definition B-26 Issue 2 December 1996 –– EIA Status Group (dev 5) –– T extual Convention for EIA Status Integer EIAStatus ::= INTEGER { off(1), on(2), unsupported-lead(3).
Device Enterprise MIB Definition B-27 Issue 2 December 1996 –– Layout of one entry in devEIAStatusT able. DevEIAStatusEntry ::= SEQUENCE { devEIAStatusIndex INTEGER, devEIAStatusCode OCTET STRING,.
Device Enterprise MIB Definition B-28 Issue 2 December 1996 devEIAStatusACR EIAStatus, devEIAStatusDSC EIAStatus, devEIAStatusPND EIAStatus } devEIAStatusIndex OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”The index of the entry in the devEIAStatusT able.
Device Enterprise MIB Definition B-29 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”TD.” ::= { devEIAStatusEntry 4 } devEIAStatusRD OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”RD.
Device Enterprise MIB Definition B-30 Issue 2 December 1996 devEIAStatusTM OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”TM.” ::= { devEIAStatusEntry 10 } devEIAStatusDRI OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”DRI.
Device Enterprise MIB Definition B-31 Issue 2 December 1996 ”LL.” ::= { devEIAStatusEntry 15 } devEIAStatusRL OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”RL.” ::= { devEIAStatusEntry 16 } devEIAStatusRI OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”RI.
Device Enterprise MIB Definition B-32 Issue 2 December 1996 ACCESS read-only ST A TUS mandatory DESCRIPTION ”ACR.” ::= { devEIAStatusEntry 21 } devEIAStatusDSC OBJECT -TYPE SYNT AX EIAStatus ACCESS read-only ST A TUS mandatory DESCRIPTION ”DSC.
Device Enterprise MIB Definition B-33 Issue 2 December 1996 –– External Leads Group (dev 6) –– T extual Convention for External Lead objects ExternalLead ::= INTEGER { lead-off(1), lead-on(2) } devExtLeadsOutPin12 OBJECT -TYPE SYNT AX ExternalLead ACCESS read-write ST A TUS mandatory DESCRIPTION ”RS-232 output pin 12 (port 1).
Device Enterprise MIB Definition B-34 Issue 2 December 1996 –– Command Group (dev 7) –– Dial an Entered or Stored Number devCommandDial OBJECT -TYPE SYNT AX DisplayString (SIZE (0..40)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”Setting this attribute will cause the modem to dial the entered number .
Device Enterprise MIB Definition B-35 Issue 2 December 1996 ”Setting this attribute to busy(1) will cause the device to busy out the attached analog phone line. Setting this attribute to clear(2) will cause the device to unbusy the analog phone line.
Device Enterprise MIB Definition B-36 Issue 2 December 1996 devCommandReset OBJECT -TYPE SYNT AX INTEGER { software(1), hardware(2), unknown(3) } ACCESS read-write ST A TUS mandatory DESCRIPTION ”Invoke a software(1) or hardware(2) reset of the device.
C-1 Issue 2 December 1996 Enterprise T rap Definitions C NMS6700-TRAP DEFINITIONS ::= BEGIN –– T itle: COMSPHERE 6700 T rap Definitions –– Copyright (C) 1996, Paradyne. All rights reserved. –– –– This file may be freely copied and distributed as –– long as no changes are made to it.
Enterprise T rap Definitions C-2 Issue 2 December 1996 –– Primary Alerts (1 – 32) deviceFailure TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device failure (major).” ::= 1 configChangeNotify TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Configuration change notify .
Enterprise T rap Definitions C-3 Issue 2 December 1996 streamingT erminal TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Streaming terminal (major).” ::= 8 accessSecurity TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Access security alarm (major).” ::= 9 dialBackup TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Dial backup active for APL.
Enterprise T rap Definitions C-4 Issue 2 December 1996 ENTERPRISE devOid DESCRIPTION ”Make busy mode.” ::= 15 serviceLine TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Service line.” ::= 16 nonAnsweringModem TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Non-answering modem.
Enterprise T rap Definitions C-5 Issue 2 December 1996 DESCRIPTION ”Dial tone.” ::= 22 redundantPowerSupply TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Redundant power supply .” ::= 23 noResponse TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”No response from the device.
Enterprise T rap Definitions C-6 Issue 2 December 1996 –– System Events (101 – 1 17) vfLoginOk TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”VF login OK. The calling party entered a correct VF (DTMF) password.” ::= 101 userLoginOk TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”User Login OK.
Enterprise T rap Definitions C-7 Issue 2 December 1996 vfLoginRejected–PasswordT imeout TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”VF Login Rejected – Password T imeout. The calling party failed to enter a VF (DTMF) password within the allotted time.
Enterprise T rap Definitions C-8 Issue 2 December 1996 userLoginHack TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”User Login Hack – Multiple Sequential Password Retries. The password retry pattern indicates a hacker is attempting to defeat login security .
Enterprise T rap Definitions C-9 Issue 2 December 1996 –– Primary Alert Clear Notifications (201 – 232) deviceFailureClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device failure cleared.” ::= 201 configChangeNotifyClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Configuration change notify cleared.
Enterprise T rap Definitions C-10 Issue 2 December 1996 streamingT erminalClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Streaming terminal cleared.” ::= 208 accessSecurityClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Access security alarm cleared.
Enterprise T rap Definitions C-1 1 Issue 2 December 1996 ”Make busy mode cleared.” ::= 215 serviceLineClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Service line mode cleared.” ::= 216 nonAnsweringModemClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Non-answering modem cleared.
Enterprise T rap Definitions C-12 Issue 2 December 1996 redundantPowerSupplyClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Redundant power supply cleared.” ::= 223 noResponseClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”No response from the device cleared.
D-1 Issue 2 December 1996 Enterprise Common MIB Definitions D A TTP-ENTERPRISES DEFINITIONS ::= BEGIN IMPOR TS enterprises, IpAddress FROM RFC1 155-SMI OBJECT -TYPE FROM RFC-1212 DisplayString FROM RFC1213-MIB; –– –– Copyright (C) 1996, Paradyne.
Enterprise Common MIB Definitions D-2 Issue 2 December 1996 paradyne-products OBJECT IDENTIFIER ::= { att-products 14 } attp-cellRelay-products OBJECT IDENTIFIER ::= { paradyne-products 1 } attp-31XX-.
Enterprise Common MIB Definitions D-3 Issue 2 December 1996 devIdentityCustAssignedID OBJECT -TYPE SYNT AX DisplayString (SIZE (0..15)) ACCESS read-write ST A TUS mandatory DESCRIPTION ”Device identifier assigned by the customer . Used for display in ASCII interfaces.
Enterprise Common MIB Definitions D-4 Issue 2 December 1996 ::= { devIdentity 6 } devIdentityHWRevEntry OBJECT -TYPE SYNT AX DevIdentityHWRevEntry ACCESS not-accessible ST A TUS mandatory DESCRIPTION ”An entry in the hardware revision table.
Enterprise Common MIB Definitions D-5 Issue 2 December 1996 SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Number of software revision entries in table.
Enterprise Common MIB Definitions D-6 Issue 2 December 1996 DESCRIPTION ”Software Revision table index.” ::= { devIdentitySWRevEntry 1 } devIdentitySWRevNumber OBJECT -TYPE SYNT AX DisplayString (SIZE (1..16)) ACCESS read-only ST A TUS mandatory DESCRIPTION ”Software revision number for the CCA software module.
Enterprise Common MIB Definitions D-7 Issue 2 December 1996 ”Self-test results. Self-test (or power-up test) results summarizes the test results of each CCA, where each CCA test result is separated by a semi-colon. Refer to device-specific user documentation for a complete description of the self test codes and messages.
Enterprise Common MIB Definitions D-8 Issue 2 December 1996 devFrontPanelCursorRow OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”Front panel cursor row (zero origin).
Enterprise Common MIB Definitions D-9 Issue 2 December 1996 ST A TUS mandatory DESCRIPTION ”A row entry in front panel display table.” INDEX { devFrontPanelDisplayRowIndex } ::= { devFrontPanelDis.
Enterprise Common MIB Definitions D-10 Issue 2 December 1996 ACCESS read-only ST A TUS mandatory DESCRIPTION ”Indicates who owns the front panel at this time. If the status is free, then a keyPress set will successfully update the front panel and the status will change to nms.
Enterprise Common MIB Definitions D-1 1 Issue 2 December 1996 The value returned on a GET is undefined.” ::= { adminFrontPanel 4 } –– –– Call Directory –– devCallDir OBJECT IDENTIFIER ::.
Enterprise Common MIB Definitions D-12 Issue 2 December 1996 devCallDirPurpose INTEGER, devCallDirId DisplayString, devCallDirPhoneNumber DisplayString } devCallDirIndex OBJECT -TYPE SYNT AX INTEGER ACCESS read-only ST A TUS mandatory DESCRIPTION ”A unique value for each call directory .
Enterprise Common MIB Definitions D-13 Issue 2 December 1996 DESCRIPTION ”Call directory phone number .” ::= { devCallDirEntry 4 } END.
IN-1 Issue 2 December 1996 C Call Directory MIB, 3-6 COMSPHERE 6700 Series NMS Enterprise MIBs, 3-3 D Device MIB, 3-5 device traps, 3-7 DOS MIB, 3-6 F Front Panel MIB, 3-6 H hardware r.
Index IN-2 Issue 2 December 1996 S SNMP community views, 3-1 1 overview , 1-1 sample network topology , 1-3 SNMP traps, 3-7 SNMP Proxy Agent feature list, 1-2 overview , 1-1 package contents, 1-4 soft.
An important point after buying a device Paradyne 3700-A2-GB20-10 (or even before the purchase) is to read its user manual. We should do this for several simple reasons:
If you have not bought Paradyne 3700-A2-GB20-10 yet, this is a good time to familiarize yourself with the basic data on the product. First of all view first pages of the manual, you can find above. You should find there the most important technical data Paradyne 3700-A2-GB20-10 - thus you can check whether the hardware meets your expectations. When delving into next pages of the user manual, Paradyne 3700-A2-GB20-10 you will learn all the available features of the product, as well as information on its operation. The information that you get Paradyne 3700-A2-GB20-10 will certainly help you make a decision on the purchase.
If you already are a holder of Paradyne 3700-A2-GB20-10, but have not read the manual yet, you should do it for the reasons described above. You will learn then if you properly used the available features, and whether you have not made any mistakes, which can shorten the lifetime Paradyne 3700-A2-GB20-10.
However, one of the most important roles played by the user manual is to help in solving problems with Paradyne 3700-A2-GB20-10. Almost always you will find there Troubleshooting, which are the most frequently occurring failures and malfunctions of the device Paradyne 3700-A2-GB20-10 along with tips on how to solve them. Even if you fail to solve the problem, the manual will show you a further procedure – contact to the customer service center or the nearest service center
