1. Manuals
  2. Brands
  3. Paradyne Manuals
  4. Network Hardware
  5. COMSPHERE 6700 Series
  6. User manual

Paradyne COMSPHERE 6700 Series User Manual

Network management system snmp proxy agent feature
Hide thumbs Also See for COMSPHERE 6700 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
You have accessed an older version
of a Paradyne product document.
Paradyne is no longer a subsidiary
of AT&T. Any reference to
AT&T Paradyne is amended to
read Paradyne Corporation.

Advertisement

Table of Contents
loading

Related Manuals for Paradyne COMSPHERE 6700 Series

Summary of Contents for Paradyne COMSPHERE 6700 Series

  • Page 1 You have accessed an older version of a Paradyne product document. Paradyne is no longer a subsidiary of AT&T. Any reference to AT&T Paradyne is amended to read Paradyne Corporation.
  • Page 2 6700-A2-GB20-00 P a r a dyn e Issue 1 September 1994 COMSPHERE 6700 Series Network Management System SNMP Proxy Agent Feature User’s Guide Printed on recycled paper...
  • Page 3 COMSPHERE 6700 Series Network Management System SNMP Proxy Agent Feature User’s Guide 6700-A2-GB20-00 Issue 1 (September 1994) Changes and enhancements to the product and to the information herein will be documented and issued as a new release. A Reader’s Comments form is provided at the front of this publication and your comments are appreciated.
  • Page 4 Trademarks Trademarks COMSPHERE is a registered trademark of AT&T. Ethernet is a registered trademark of Xerox Corporation. Hayes is a registered trademark of Hayes Microcomputer Products, Inc. Hewlett-Packard is a registered trademark of Hewlett-Packard Company. HP OpenView is a trademark of Hewlett-Packard Company. IBM is a registered trademark of International Business Machines Corporation.

  • Page 5: Table Of Contents

    Contents Preface Related Documents Ordering Information 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...
  • Page 6 MIB-II Support MIB-II System Group Overview MIB-II Interface Group Overview COMSPHERE 6700 Series NMS Enterprise MIBs COMSPHERE 6700 NMS MIB Overview COMSPHERE 6700 Device MIB Overview Front Panel MIB Overview Call Directory MIB Overview DOS, Windows, and Workstation MIBs SNMP Traps Overview...
  • Page 7 Figures Overview Sample SNMP Network Topology Installation Welcome Window Product Information Window Destination Directory Window Confirmation Window Completion Status Window Installation Completed! Window Management Information Bases SMI Defined Object Identifier Prefix Tree ...
  • Page 8 Tables Installation Supported Network Adapter Boards Management Information Bases MIB Browser Output Table Primary Alert Traps System Event Traps Primary Alert Clear Notifications Issue 1 September 1994 ......

  • Page 9: Preface

    Preface This guide describes how to install and use the COMSPHERE 6700 Series Network Management System (NMS) SNMP Proxy Agent feature. This manual assumes you have a basic understanding of COMSPHERE modems and data service units (DSUs) and their operation, are knowledgeable about data communications, and...

  • Page 10: Ordering Information

    Preface 6700-A2-GB21 COMSPHERE 6700 Series Network Management System Multiuser Feature User’s Guide COMSPHERE 6700 Series Network 6700-A2-GB22 Management System Network Configuration Guide COMSPHERE 6700 Series Network 6700-A2-GB41 Management System Security Manager Feature Supplement 6700-A2-GY31 COMSPHERE 6700 Series Network Management System User’s Guide...

  • Page 11: Overview

    What is the SNMP Proxy Agent Feature? The COMSPHERE 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...

  • Page 12: Software Description

    SNMP messages across Ethernet FDDI, SLIP, and PPP interfaces. The SNMP Proxy Agent feature is a software package that can be installed on top of the COMSPHERE 6700 Series NMS Release 4.0.0 or higher at any time. NOTE: COMSPHERE 6700 Series NMS Release 4.0.0 or higher...

  • Page 13: Sample Snmp Network Topology

    Overview Integrated TCP/IP, UDP/IP, and SNMP Protocol support Concurrent Ethernet, Token Ring, FDDI, SLIP, and PPP interface support Sample SNMP Network Topology Figure 1-1 shows a sample SNMP network topology. Figure 1-1. Sample SNMP Network Topology Issue 1 September 1994...

  • Page 14: Snmp Proxy Agent Feature Package Contents

    Package Contents The SNMP Proxy Agent feature package includes the following: SNMP feature software on one 3 1/2 disk COMSPHERE 6700 MIBs 3 1/2 disk One COMSPHERE 6700 Series Network Management System SNMP Proxy Agent Feature User’s Guide One COMSPHERE 6700 Series Network Management...

  • Page 15: Installation

    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. Supported Network Adapters To use the SNMP feature on Ethernet, Token Ring, or FDDI, you must install a supported network adapter board.
  • Page 16 Installation Table 2-1. Supported Network Adapter Boards (1 of 2) Interface Vendor Ethernet 3COM Allied Telesis Hewlett Packard Intel Novell/Excelan Racal InterLan Ungermann-Bass Western Digital Xircom Issue 1 September 1994 Model 3C501 Ether Link 3C503 Ether Link II 3C505 Ether Link Plus 3C507 Ether Link 16 3C509 Ether Link III 3C523 Ether Link/MC TP...

  • Page 17: Preparing For Installation And Configuration

    Installation Table 2-1. Supported Network Adapter Boards (2 of 2) Interface Vendor Ethernet Xircom (Continued) Other Token Ring Xircom Madge Proteon Raycone Other FDDI Preparing for Installation and Configuration Before installing and configuring the SNMP Proxy Agent feature, you need some system and network information. Use the following form to collect the necessary information before you start the installation process.
  • Page 18 Installation SNMP Feature Installation and Configuration Information General Where to install the software (c:\pcnms): Network Interface Name (Ethernet0): Network Interface Type (Ethernet): Workstation Internet Address of Workstation (192.0.2.2): Unique Node Name (Largo Bld. G): SNMP Manager Internet Address of Manager (192.0.2.8): Unique Manager Name (Help Desk1): LAN/Hardware Interface Adapter Vendor Name (Western Digital):...

  • Page 19: Installing The Snmp Proxy Agent Feature

    Installation Installing the SNMP Proxy Agent Feature 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.
  • Page 20 Installation 6. Choose Continue. The Product Information window appears, as shown in Figure 2-2. Figure 2-2. Product Information Window 7. Choose Yes. The Destination Directory window appears, as shown in Figure 2-3. Figure 2-3. Destination Directory Window The Destination Directory window allows you to place the NMS software into a specific directory.
  • Page 21 Installation 9. Choose Continue. The Confirmation window appears, as shown in Figure 2-4. Figure 2-4. Confirmation Window 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. Figure 2-5.

  • Page 22: Configuring The Snmp Proxy Agent Feature For Tcp/Ip Networks

    Agent Feature for TCP/IP Networks After installation, use the Network Configuration application to customize your configuration for TCP/IP networks. For details on doing so, refer to the COMSPHERE 6700 Series Network Management System Network Configuration Guide . Issue 1 September 1994...

  • Page 23: Management Information Bases

    Management Information Bases 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. The following MIB-II groups are supported as specified in RFC 1213. System Group Interface Group Address Translation Table Group...

  • Page 24: Mib-Ii System Group Overview

    80486 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 AT&T Paradyne COMSPHERE 6700 sysLocation COMSPHERE 6700 NMS Workstation sysServices MIB-II Interface Group Overview The MIB-II interface group contains information about TCP/IP interfaces configured within NEWT.

  • Page 25: Comsphere 6700 Series Nms Enterprise Mibs

    Call Directory MIB NOTE: For additional installation information, refer to the readme.txt file on the COMSPHERE 6700 SNMP MIBs diskette, Part No. 869-2745-0011. Figure 3-1 shows the Structure of Management Information (SMI) defined object identifier prefix tree that includes the COMSPHERE 6700 Enterprise MIBs.
  • Page 26 Management Information Bases Figure 3-1. SMI Defined Object Identifier Prefix Tree The COMSPHERE 6700 NMS and Device MIBs are defined in the appendices. Issue 1 September 1994...

  • Page 27: Comsphere 6700 Nms Mib Overview

    Management Information Bases COMSPHERE 6700 NMS MIB Overview The NMS MIB administers the 6700 Series NMS. The following groups are defined in the NMS MIB. NMS Administration Group NMS System Group NMS Device Group NMS Manager Group NMS Test Group Refer to Appendix A for a full description of the COMSPHERE 6700 NMS MIBs.

  • Page 28: Front Panel 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.

  • Page 29: Snmp Traps Overview

    Management Information Bases 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 specifying the COMSPHERE 6700 Enterprise Device product.
  • Page 30 Management Information Bases NOTE: The state of a device’s primary alerts can also be read from devStatusAlert. Table 3-2. Primary Alert Traps (1 of 2) Trap Primary Alert Traps Device Failure Configuration Change Notify Test Mode Disabled Out of Threshold/VF Threshold Exceeded Facility Alarm External Alarm...
  • Page 31 Management Information Bases Table 3-2. Primary Alert Traps (2 of 2) Trap Primary Alert Traps Tributary Timeout Dial Tone Redundant Power Supply No Response Table 3-3 identifies which system security event traps apply to the specific devices. Table 3-3. System Security Event Traps (1 of 2) Trap System Security Event Traps VF Login OK...
  • Page 32 Management Information Bases Table 3-3. System Security Event Traps (2 of 2) Trap System Security Event Traps Invalid Access Time User Login Hack - Multiple Sequential Password Retries Device Security Table Invalid Security Download Failed Front Panel Modification Table 3-4 lists the Primary Alert Clear Notifications. Table 3-4.

  • Page 33: Snmp Community Views

    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 .

  • Page 34: Community Name Example

    Management Information Bases 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.
  • Page 35 This file may be freely copied and distributed as –– long as no changes are made to it. –– The NMS MIB contains attributes of the 6700 NMS entity. –– The user can inspect and control the 6700 NMS via this MIB. IMPORTS IpAddress FROM RFC1155-SMI...
  • Page 36 OBJECT IDENTIFIER ::= { nms 1 }–– administration nmsSystem OBJECT IDENTIFIER ::= { nms 2 }–– system identity nmsDevice OBJECT IDENTIFIER ::= { nms 3 }–– 6700 devices nmsManager OBJECT IDENTIFIER ::= { nms 4 }–– SNMP managers nmsTest OBJECT IDENTIFIER ::= { nms 5 }–– Tests...
  • Page 37 ”Location of the 6700 NMS.” ::= { nmsAdmin 2 } nmsAdminContact1 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-write STATUS mandatory DESCRIPTION ”Contact 1 for the 6700 NMS.” ::= { nmsAdmin 3 } nmsAdminContact2 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-write STATUS mandatory DESCRIPTION ”Contact 2 for the 6700 NMS.”...
  • Page 38 MIB Definition access to all objects in the COMSPHERE 6700 NMS MIB. An exception applies with the nmsAdminNmsWriteCommunity object for which the read community provides no access.” ::= { nmsAdmin 5 } nmsAdminNmsWriteCommunity OBJECT-TYPE SYNTAX DisplayString (SIZE (0..32)) ACCESS read-only...
  • Page 39 ::= { nmsSystem 1 } –– Features nmsSystemFeatures OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Number of COMSPHERE 6700 NMS product or feature entries in nmsSystemFeatureTable.” ::= { nmsSystem 2 } nmsSystemFeatureTable OBJECT-TYPE SYNTAX SEQUENCE OF NmsSystemFeatureEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”The nms feature table contains a list of software...
  • Page 40 MIB Definition –– Layout of one entry in nmsSystemFeatureTable. NmsSystemFeatureEntry ::= SEQUENCE { nmsSystemFeatureIndex INTEGER, nmsSystemFeatureName DisplayString, nmsSystemFeatureVersion DisplayString, nmsSystemFeatureSerial DisplayString –– Index nmsSystemFeatureIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The index of the entry.” ::= { nmsSystemFeatureEntry 1 } ––...
  • Page 41 MIB Definition ::= { nmsSystemFeatureEntry 3 } –– Serial Number nmsSystemFeatureSerial OBJECT-TYPE SYNTAX DisplayString (SIZE (0..25)) ACCESS read-only STATUS mandatory DESCRIPTION ”Serial number of system product or feature. If feature has no serial number, this object contains a zero length string.”...
  • Page 42 OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The number of devices configured in the 6700 nms network. This is also the number of entries in nmsDeviceTable.” ::= { nmsDevice 1 } nmsDeviceTable OBJECT-TYPE SYNTAX SEQUENCE OF NmsDeviceEntry ACCESS not-accessible...
  • Page 43 ”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.”...
  • Page 44 MIB Definition DESCRIPTION ”An entry in the manager table. Entries are indexed by IP Address.” INDEX { nmsManagerAddress } ::= { nmsManagerTable 1 } –– Layout of one entry in nmsManagerTable. NmsManagerEntry ::= SEQUENCE { nmsManagerAddress IpAddress, nmsManagerName DisplayString, nmsManagerAccess INTEGER, nmsManagerTraps INTEGER,...
  • Page 45 MIB Definition STATUS 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.
  • Page 46 MIB Definition nmsManagerLocation OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-write STATUS mandatory DESCRIPTION ”Text string describing manager location.” ::= { nmsManagerEntry 5 } –– Contact1 nmsManagerContact1 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-write STATUS mandatory DESCRIPTION ”Text string describing manager contact 1.” ::= { nmsManagerEntry 6 } ––...
  • Page 47 ACCESS read-only STATUS mandatory DESCRIPTION ”The number of NMS Test table entries that are configured. This number is controlled by the following lines in the 6700 profile (default value is shown). [SNMP] NmsTestEntries=8” ::= { nmsTest 1 } –– Test Table...
  • Page 48 MIB Definition nmsTestEntry OBJECT-TYPE SYNTAX NmsTestEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”An entry in the nms test table.” INDEX { nmsTestIndex } ::= { nmsTestTable 1 } A-14 Issue 1 September 1994...
  • Page 49 MIB Definition –– Layout of one entry in nmsTestTable. NmsTestEntry ::= SEQUENCE { nmsTestIndex INTEGER, nmsTestDeviceName DisplayString, nmsTestType INTEGER, nmsTestDuration INTEGER, nmsTestPortNumber INTEGER, nmsTestRemoteName DisplayString, nmsTestStatus INTEGER, nmsTestLocalTotalSecondsValidity TestResultValidity, nmsTestLocalTotalSeconds INTEGER, nmsTestLocalErrorSecondsValidity TestResultValidity, nmsTestLocalErrorSeconds INTEGER, nmsTestLocalTotalBlocksValidity TestResultValidity, nmsTestLocalTotalBlocks INTEGER, nmsTestLocalErrorBlocksValidity TestResultValidity, nmsTestLocalErrorBlocks INTEGER,...
  • Page 50 MIB Definition nmsTestRemoteTotalBlocks INTEGER, nmsTestRemoteErrorBlocksValidity TestResultValidity, nmsTestRemoteErrorBlocks INTEGER, nmsTestTimeOutsValidity TestResultValidity, nmsTestTimeOuts INTEGER, nmsTestOwner DisplayString, nmsTestEntryStatus INTEGER –– Index nmsTestIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”This object is the test table entry index.” ::= { nmsTestEntry 1 } ––...
  • Page 51 MIB Definition SYNTAX 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(11) ACCESS read-write STATUS mandatory DESCRIPTION ”This object is the test type. Test type self-test(1) performs an internal self-test of the device. Test type local-loop(2) places the device into local loopback (for modems, this is a CCITT V.54 Loop 3).
  • Page 52 MIB Definition SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION ”Test duration in seconds (or blocks). Only applicable for the following test types: bert, local-loop-bert, rdl-bert, digital-test, end-to-end-test.” ::= { nmsTestEntry 4 } –– –– Port Number –– nmsTestPortNumber OBJECT-TYPE SYNTAX INTEGER { aggregate(1), port1(2), port2(3),...
  • Page 53 MIB Definition ::= { nmsTestEntry 6 } –– –– Test Status –– nmsTestStatus OBJECT-TYPE SYNTAX INTEGER { idle(1), testMode(2), testRunning(3), testAborted(4), testFailed(5) ACCESS read-only STATUS mandatory DESCRIPTION ”Test status. Status of idle(1) indicates that the device is not in test mode (from this control point);...
  • Page 54 MIB Definition nmsTestLocalTotalSeconds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Total seconds for local device. (For 3600 model type devices, this variable is also called elapsed seconds.)” ::= { nmsTestEntry 9 } –– Local Error Seconds nmsTestLocalErrorSecondsValidity OBJECT-TYPE SYNTAX TestResultValidity ACCESS read-only STATUS mandatory DESCRIPTION...
  • Page 55 MIB Definition –– Local Error Blocks (Bits for 3600 DSU) nmsTestLocalErrorBlocksValidity OBJECT-TYPE SYNTAX TestResultValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the nmsTestLocalErrorBlocks test result object.” ::= { nmsTestEntry 14 } nmsTestLocalErrorBlocks OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Error Blocks for 3800 and 3900 modems, or Local Error Blocks (actually Bits) for 3600 DSUs;...
  • Page 56 MIB Definition DESCRIPTION ”Validity of the nmsTestRemoteErrorSeconds test result object.” ::= { nmsTestEntry 18 } nmsTestRemoteErrorSeconds OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Errored seconds elapsed for the remote device. (The value is not used for 3600 model type devices.)” ::= { nmsTestEntry 19 } ––...
  • Page 57 MIB Definition STATUS mandatory DESCRIPTION ”Remote Error blocks (actually Bits). Not used for 3800 and 3900 model type devices.)” ::= { nmsTestEntry 23 } –– Time Outs nmsTestTimeOutsValidity OBJECT-TYPE SYNTAX TestResultValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the nmsTestTimeOuts test result object.” ::= { nmsTestEntry 24 } nmsTestTimeOuts OBJECT-TYPE SYNTAX INTEGER...
  • Page 58 MIB Definition –– Entry Status nmsTestEntryStatus OBJECT-TYPE SYNTAX INTEGER { valid(1), createRequest(2), underCreation(3), invalid(4) ACCESS read-write STATUS mandatory DESCRIPTION ”The status of this nmsTestTable entry. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry. If there is a test active when the entry is invalidated, the test will be aborted.
  • Page 59 –– The 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 ––...
  • Page 60 Device Enterprise MIB Definition –– –– Enterprise Identification for COMSPHERE 6700 Device MIB –– OBJECT IDENTIFIER ::= { nms-6700 2 } –– Device MIB –– Device MIB Groups devAdmin OBJECT IDENTIFIER ::= { dev 1 } –– administration devIdentity OBJECT IDENTIFIER ::= { dev 2 } –– device identity devStatus OBJECT IDENTIFIER ::= { dev 3 } ––...
  • Page 61 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only STATUS mandatory DESCRIPTION ”Device name. This is the name used by the COMSPHERE 6700 NMS to identify the device.” ::= { devAdmin 1 } devAdminAdpAddress OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only...
  • Page 62 Device Enterprise MIB Definition devAdminCabinet OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only STATUS mandatory DESCRIPTION ”Device cabinet name used by COMSPHERE 6700 NMS.” ::= { devAdmin 5 } devAdminCarrier OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only STATUS mandatory DESCRIPTION ”Device carrier name used by COMSPHERE 6700 NMS.”...
  • Page 63 Device Enterprise MIB Definition ”Device contact string #2.” ::= { devAdmin 10 } devAdminComment OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-only STATUS mandatory DESCRIPTION ”Device comment string.” ::= { devAdmin 11 } devAdminDbmOption OBJECT-TYPE SYNTAX INTEGER { dbm-installed(1), dbm-not-installed(2) ACCESS read-only STATUS mandatory DESCRIPTION ”A value of dbm-installed(1) indicates that a dial backup...
  • Page 64 Device Enterprise MIB Definition multi point option is installed.” ::= { devAdmin 14 } devAdminTdmOption OBJECT-TYPE SYNTAX INTEGER { tdm-installed(1), tdm-not-installed(2) ACCESS read-only STATUS mandatory DESCRIPTION ”A value of tdm-installed(1) indicates that a time division multiplexer option is installed.” ::= { devAdmin 15 } Issue 1 September 1994...
  • Page 65 Device Enterprise MIB Definition –– Device Identity Group (dev 2) devIdentityModel OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-only STATUS mandatory DESCRIPTION ”Model number.” ::= { devIdentity 1 } devIdentityLineSpeed OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-only STATUS mandatory DESCRIPTION ”Line speed.” ::= { devIdentity 2 } devIdentitySoftwareVersion OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40))
  • Page 66 Device Enterprise MIB Definition STATUS mandatory DESCRIPTION ”Access module (if applicable, otherwise length is zero).” ::= { devIdentity 6 } devIdentityRestoralOption OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-only STATUS mandatory DESCRIPTION ”Restoral option (if applicable, otherwise length is zero).” ::= { devIdentity 7 } devIdentityConfiguration OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-only...
  • Page 67 Device Enterprise MIB Definition devIdentityOption1 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-only STATUS mandatory DESCRIPTION ”Option 1 (if applicable, otherwise length is zero).” ::= { devIdentity 12 } devIdentityOption2 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-only STATUS mandatory DESCRIPTION ”Option 2 (if applicable, otherwise length is zero).” ::= { devIdentity 13 } devIdentityOption3 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40))
  • Page 68 Device Enterprise MIB Definition ”Option 6 (if applicable, otherwise length is zero).” ::= { devIdentity 17 } B-10 Issue 1 September 1994...
  • Page 69 Device Enterprise MIB Definition –– Device Status Group (dev 3) devStatusConnectedDevice OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-only STATUS mandatory DESCRIPTION ”The device name of the connected device. A zero length string will be returned if the information is unavailable.” ::= { devStatus 1 } devStatusConnectTime OBJECT-TYPE SYNTAX TimeTicks...
  • Page 70 Device Enterprise MIB Definition 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 SYNTAX DisplayString (SIZE (0..255)) ACCESS read-only STATUS mandatory DESCRIPTION ”Contains current Primary Alerts for the device, in text format, delimited by semicolons (;). The following abbreviations are used for the primary alerts: Fail, CfgChng, Test, Disab, Thresh, FacAlrm, ExtAlrm, StrTerm, AccSec, DialBkUp, DteAlrm, SubSpeed, PriChIr,...
  • Page 71 Device Enterprise MIB Definition devStatusSpeed OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The current data rate of the device, in bits per second. A value of zero indicates that the device is training.” ::= { devStatus 6 } devStatusCtrlTrib OBJECT-TYPE SYNTAX INTEGER { local-control(1), remote-control(2),...
  • Page 72 Device Enterprise MIB Definition ”Indicates the polling state of the device in the network.” ::= { devStatus 9 } B-14 Issue 1 September 1994...
  • Page 73 Device Enterprise MIB Definition –– Circuit Quality Group (dev 4) –– Type Definition for Circuit Quality Validity indicators –– Validity is not-used(6) if not supported by device type. CirQualValidity ::= INTEGER { valid(1), valid-greater-than(2), valid-less-than(3), not-valid-for-modulation-mode(4), not-valid-for-multipoint-mode(5), not-available-yet(6), count-overflow(7), not-used(8) ––...
  • Page 74 Device Enterprise MIB Definition ”Validity of the devCirQualMeanSquareError object.” ::= { devCirQual 3 } devCirQualMeanSquareError OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Mean squared error.” ::= { devCirQual 4 } –– Receive Level devCirQualReceiveLevelValidity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualReceiveLevel object.”...
  • Page 75 Device Enterprise MIB Definition STATUS mandatory DESCRIPTION ”1004 Hz loss.” ::= { devCirQual 8 } –– Signal to Noise Ratio devCirQualSignalToNoiseValidity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualSignalToNoise object.” ::= { devCirQual 9 } devCirQualSignalToNoise OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory...
  • Page 76 Device Enterprise MIB Definition –– Phase Jitter 20–300 Hz devCirQualPhaseJitter300Validity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualPhaseJitter300 object.” ::= { devCirQual 13 } devCirQualPhaseJitter300 OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Phase jitter 20–300 Hz. Units are (degrees * 10). Possible range 0.0 to 33 degrees.”...
  • Page 77 Device Enterprise MIB Definition STATUS mandatory DESCRIPTION ”Validity of the devCirQualNegativeAttenuation object.” ::= { devCirQual 17 } devCirQualNegativeAttenuation OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Negative attenuation.” ::= { devCirQual 18 } –– Envelope Delay devCirQualEnvelopeDelayValidity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION...
  • Page 78 Device Enterprise MIB Definition SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Frequency offset. Units are (Hz * 10). Possible range –51.1 to +51.1 Hz.” ::= { devCirQual 22 } –– Non Linear Distortion devCirQualNonLinearDistortionValidity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualNonLinearDistortion object.”...
  • Page 79 Device Enterprise MIB Definition DESCRIPTION ”Retrains. Integer value represents the number of retrain events during the last 15 minutes. Possible range is 0 to 4095.” ::= { devCirQual 26 } –– Blown Startups devCirQualBlownStartupsValidity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualBlownStartups object.”...
  • Page 80 Device Enterprise MIB Definition –– Phase Hits devCirQualPhaseHitsValidity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualPhaseHits object.” ::= { devCirQual 31 } devCirQualPhaseHits OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Phase hits. Integer value represents the number of phase hit events during the last 15 minutes.
  • Page 81 Device Enterprise MIB Definition ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualDropouts object.” ::= { devCirQual 35 } devCirQualDropouts OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Dropouts. Integer value represents the number of dropout events during the last 15 minutes. Possible range is 0 to 4095.”...
  • Page 82 Device Enterprise MIB Definition SYNTAX CirQualValidity ACCESS read-only STATUS mandatory DESCRIPTION ”Validity of the devCirQualNearEndEcho object.” ::= { devCirQual 39 } devCirQualNearEndEcho OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Near end echo. Units are (dB *10). Possible range 0.0 to –102.4 dB.” ::= { devCirQual 40 } ––...
  • Page 83 Device Enterprise MIB Definition ::= { devCirQual 43 } devCirQualFarEndDelay OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Far end delay. Units are in milliseconds. Possible range 0 to 4095 ms.” ::= { devCirQual 44 } –– Echo Frequency Offset devCirQualEchoFreqOffsetValidity OBJECT-TYPE SYNTAX CirQualValidity ACCESS read-only...
  • Page 84 Device Enterprise MIB Definition –– EIA Status Group (dev 5) –– Textual Convention for EIA Status Integer EIAStatus ::= INTEGER { off(1), on(2), unsupported-lead(3), lead-changing(4) –– Number of Ports (Number of Entries in EIA Status Table) devEIAStatusPorts OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION...
  • Page 85 Device Enterprise MIB Definition –– Layout of one entry in devEIAStatusTable. DevEIAStatusEntry ::= SEQUENCE { devEIAStatusIndex INTEGER, devEIAStatusCode OCTET STRING, devEIAStatusDTR EIAStatus, devEIAStatusTD EIAStatus, devEIAStatusRD EIAStatus, devEIAStatusDSR EIAStatus, devEIAStatusRTS EIAStatus, devEIAStatusCTS EIAStatus, devEIAStatusDCD EIAStatus, devEIAStatusTM EIAStatus, devEIAStatusDRI EIAStatus, devEIAStatusPIN13 EIAStatus, devEIAStatusPIN19 EIAStatus, devEIAStatusDRS...
  • Page 86 Device Enterprise MIB Definition devEIAStatusACR EIAStatus, devEIAStatusDSC EIAStatus, devEIAStatusPND EIAStatus devEIAStatusIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The index of the entry in the devEIAStatusTable. Note that the device hardware port number is used as the index. Port numbers start with 1 and increment monotonically up to number of ports in devEIAStatusPorts.”...
  • Page 87 Device Enterprise MIB Definition STATUS mandatory DESCRIPTION ”TD.” ::= { devEIAStatusEntry 4 } devEIAStatusRD OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”RD.” ::= { devEIAStatusEntry 5 } devEIAStatusDSR OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”DSR.” ::= { devEIAStatusEntry 6 } devEIAStatusRTS OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only...
  • Page 88 Device Enterprise MIB Definition devEIAStatusTM OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”TM.” ::= { devEIAStatusEntry 10 } devEIAStatusDRI OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”DRI.” ::= { devEIAStatusEntry 11 } devEIAStatusPIN13 OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”Pin13.”...
  • Page 89 Device Enterprise MIB Definition ”LL.” ::= { devEIAStatusEntry 15 } devEIAStatusRL OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”RL.” ::= { devEIAStatusEntry 16 } devEIAStatusRI OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”RI.” ::= { devEIAStatusEntry 17 } devEIAStatusDPR OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only...
  • Page 90 Device Enterprise MIB Definition ACCESS read-only STATUS mandatory DESCRIPTION ”ACR.” ::= { devEIAStatusEntry 21 } devEIAStatusDSC OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”DSC.” ::= { devEIAStatusEntry 22 } devEIAStatusPND OBJECT-TYPE SYNTAX EIAStatus ACCESS read-only STATUS mandatory DESCRIPTION ”PND.” ::= { devEIAStatusEntry 23 } B-32 Issue 1 September 1994...
  • Page 91 Device Enterprise MIB Definition –– External Leads Group (dev 6) –– Textual Convention for External Lead objects ExternalLead ::= INTEGER { lead-off(1), lead-on(2) devExtLeadsOutPin12 OBJECT-TYPE SYNTAX ExternalLead ACCESS read-write STATUS mandatory DESCRIPTION ”RS-232 output pin 12 (port 1).” ::= { devExtLeads 1 } devExtLeadsOutPin13 OBJECT-TYPE SYNTAX ExternalLead ACCESS read-write...
  • Page 92 Device Enterprise MIB Definition –– Command Group (dev 7) –– Dial an Entered or Stored Number devCommandDial OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-write STATUS mandatory DESCRIPTION ”Setting this attribute will cause the modem to dial the entered number. To dial a stored number, the string must begin with ’d’, followed by the call directory entry number.
  • Page 93 Device Enterprise MIB Definition ”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. This object will always return a value of unknown(3).
  • Page 94 Device Enterprise MIB Definition devCommandReset OBJECT-TYPE SYNTAX INTEGER { software(1), hardware(2), unknown(3) ACCESS read-write STATUS mandatory DESCRIPTION ”Invoke a software(1) or hardware(2) reset of the device. This object always returns a value of unknown(3).” ::= { devCommand 6 } –– Send Message to Front Panel devCommandMessage OBJECT-TYPE SYNTAX DisplayString (SIZE (0..16)) ACCESS read-write...
  • Page 95 IMPORTS TRAP-TYPE FROM RFC-1215 nms-6700-products FROM ATTP-ENTERPRISES; –– –– Enterprise Identification for COMSPHERE 6700 SNMP Proxy Agent Traps –– devOid OBJECT IDENTIFIER ::= { nms-6700-products 2 } –– Device OID –– –– NOTE: All of the traps are subject to filtering that ––...
  • Page 96 Enterprise Trap Definitions –– Primary Alerts (1 – 32) deviceFailure TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device failure (major).” ::= 1 configChangeNotify TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Configuration change notify.” ::= 2 testMode TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Test mode.” ::= 3 deviceDisabled TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device has been disabled.”...
  • Page 97 Enterprise Trap Definitions streamingTerminal 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.” ::= 10 dteAlarm TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”DTE alarm (minor).”...
  • Page 98 Enterprise Trap Definitions 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.” ::= 17 shortHoldingTimeModem TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Short holding time modem.” ::= 18 subTreeTruncation TRAP-TYPE ENTERPRISE devOid DESCRIPTION...
  • Page 99 Enterprise Trap Definitions 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.” ::= 32 Issue 1 September 1994...
  • Page 100 Enterprise Trap Definitions –– System Events (101 – 117) 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. The calling party entered a correct user password”...
  • Page 101 Enterprise Trap Definitions vfLoginRejected–PasswordTimeout TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”VF Login Rejected – Password Timeout. The calling party failed to enter a VF (DTMF) password within the allotted time.” ::= 107 vfLoginAborted–LineDisconnected TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”VF Login Aborted – Line Disconnected. The calling party disconnected before VF (DTMF) login completed.”...
  • Page 102 Enterprise Trap Definitions 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.” ::= 113 securityTableInvalid TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Device Security Table Invalid.” ::= 114 securityDownloadFailed TRAP-TYPE ENTERPRISE devOid...
  • Page 103 Enterprise Trap Definitions –– 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.” ::= 202 testModeClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Test mode cleared.” ::= 203 deviceDisabledClear TRAP-TYPE ENTERPRISE devOid...
  • Page 104 Enterprise Trap Definitions streamingTerminalClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Streaming terminal cleared.” ::= 208 accessSecurityClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Access security alarm cleared.” ::= 209 dialBackupClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Dial backup active for APL cleared.” ::= 210 dteAlarmClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”DTE alarm (minor).”...
  • Page 105 Enterprise Trap Definitions ”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.” ::= 217 shortHoldingTimeModemClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Short holding time modem cleared.” ::= 218 subTreeTruncationClear TRAP-TYPE ENTERPRISE devOid...
  • Page 106 Enterprise Trap Definitions redundantPowerSupplyClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”Redundant power supply cleared.” ::= 223 noResponseClear TRAP-TYPE ENTERPRISE devOid DESCRIPTION ”No response from the device cleared.” ::= 232 C-12 Issue 1 September 1994...
  • Page 107 OBJECT IDENTIFIER ::= { att-2 2 } –– –– The NMS/ATTP products subtrees are used for enterprise OIDs –– –– NMS products paradyneNMS-products nms-6700-products paradyneNMS-products 2 } –– ATTP products OBJECT IDENTIFIER ::= { att-products 13 } OBJECT IDENTIFIER ::= { Issue 1 September 1994...
  • Page 108 –– The NMS/ATTP mgmt subtrees are used for MIB objects –– –– NMS mgmt paradyneNMS OBJECT IDENTIFIER ::= { att-mgmt 23 } nms-6700 OBJECT IDENTIFIER ::= { paradyneNMS 5 } –– ATTP mgmt paradyne OBJECT IDENTIFIER ::= { att-mgmt 24 }...
  • Page 109 Enterprise Common MIB Definitions devIdentityCustAssignedID OBJECT-TYPE SYNTAX DisplayString (SIZE (0..15)) ACCESS read-write STATUS mandatory DESCRIPTION ”Device identifier assigned by the customer. Used for display in ASCII interfaces.” ::= { devIdentity 2 } devIdentitySlotID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Slot identifier for this device.
  • Page 110 Enterprise Common MIB Definitions ::= { devIdentity 6 } devIdentityHWRevEntry OBJECT-TYPE SYNTAX DevIdentityHWRevEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”An entry in the hardware revision table.” INDEX { devIdentityHWRevIndex } ::= { devIdentityHWRevTable 1 } –– –– Layout of one entry in the devIdentityHWRevTable ––...
  • Page 111 Enterprise Common MIB Definitions SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Number of software revision entries in table.” ::= { devIdentity 7 } devIdentitySWRevTable OBJECT-TYPE SYNTAX SEQUENCE OF DevIdentitySWRevEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”The software revision table contains the software revision for every CCA in the device with a unique software module.”...
  • Page 112 Enterprise Common MIB Definitions DESCRIPTION ”Software Revision table index.” ::= { devIdentitySWRevEntry 1 } devIdentitySWRevNumber OBJECT-TYPE SYNTAX DisplayString (SIZE (1..16)) ACCESS read-only STATUS mandatory DESCRIPTION ”Software revision number for the CCA software module.” ::= { devIdentitySWRevEntry 2 } devIdentitySWRevHWIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory...
  • Page 113 Enterprise Common MIB Definitions ”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.”...
  • Page 114 Enterprise Common MIB Definitions devFrontPanelCursorRow OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Front panel cursor row (zero origin).” ::= { devFrontPanel 3 } devFrontPanelCursorColumn OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Front panel cursor column (zero origin).” ::= { devFrontPanel 4 } devFrontPanelDisplayRows OBJECT-TYPE SYNTAX INTEGER ACCESS read-only...
  • Page 115 Enterprise Common MIB Definitions STATUS mandatory DESCRIPTION ”A row entry in front panel display table.” INDEX { devFrontPanelDisplayRowIndex } ::= { devFrontPanelDisplayTable 1 } DevFrontPanelDisplayEntry ::= SEQUENCE { devFrontPanelDisplayRowIndex INTEGER, devFrontPanelDisplayRow DisplayString devFrontPanelDisplayRowIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Index of entry in front panel display table (zero origin).”...
  • Page 116 Enterprise Common MIB Definitions ACCESS read-only STATUS 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. The agent is allowed to set the status back to free after a specified inter-keyPress timeout.”...
  • Page 117 Enterprise Common MIB Definitions The value returned on a GET is undefined.” ::= { adminFrontPanel 4 } –– –– Call Directory –– devCallDir OBJECT IDENTIFIER ::= { attp-callDir 1 } devCallDirEntries OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Number of directories in the call directory table.” ::= { devCallDir 1 } ––...
  • Page 118 If this identifier is a number, then it may have the same value as devCallDirIndex.” ::= { devCallDirEntry 3 } devCallDirPhoneNumber OBJECT-TYPE SYNTAX DisplayString (SIZE (0..40)) ACCESS read-write STATUS mandatory D-12 Issue 1 September 1994 –– none of the following –– 6700 default...
  • Page 119 Enterprise Common MIB Definitions DESCRIPTION ”Call directory phone number.” ::= { devCallDirEntry 4 } Issue 1 September 1994 D-13...
  • Page 120 Index Call Directory MIB, 3-6 COMSPHERE 6700 Series NMS Enterprise MIBs, 3-3 Device MIB, 3-5 device traps, 3-7 DOS MIB, 3-6 Front Panel MIB, 3-6 hardware requirements, 2-1 installation preparation, 2-3 procedure, 2-5 Management Information Bases Call Directory MIB, 3-6...
  • Page 121 Index SNMP community views, 3-11 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 software description, 1-2 software requirements, 2-1 supported network adapters, 2-2 system event traps, 3-9 IN-2 Issue 1 September 1994 topology, sample, 1-3 traps...

Table of Contents