All MIBs › CISCO-ATM2-MIB
Organization: Cisco Systems, Inc.
Last Updated: 1998-03-04
Category: ATM
Description: Provides enhanced ATM interface monitoring with additional Cisco-specific ATM MIB extensions.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is CISCO-ATM2-MIB?
CISCO-ATM2-MIB is a Cisco-specific supplement to the standard ATM-MIB, adapted from a portion of the ATOMMIB supplemental MIB, in the ATM networking technology area. Because no sample objects were provided, its precise object set can't be enumerated here, but as an ATM-MIB extension it would be expected to expose additional interface, VC/VP, and cell-layer statistics and configuration beyond what the base ATM-MIB defines. Such extensions are typically used to monitor ATM interface hardware and software status, for example additional cell counters, interface operational state, or physical-layer alarm conditions not covered by the base standard. It explicitly depends on and extends the IETF ATM-MIB (and draws from the ATOMMIB supplemental MIB), making it usable only in conjunction with that base standard. It is deployed on Cisco routers and switches equipped with ATM interfaces requiring finer-grained monitoring than the base ATM-MIB provides. Engineers can download the CISCO-ATM2-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-ATM2-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Cisco routers with ATM interfaces
- Cisco ATM switches
Monitoring Examples
No sample objects were supplied for this module, so specific table or object names cannot be confirmed here; typically an ATM-MIB supplement of this kind would add per-interface or per-VC extension tables (following an atmIf/atmVcl-style naming pattern) for additional cell-layer counters or alarm status. An admin would normally poll such extension tables alongside the base ATM-MIB's interface and VCL tables to get a fuller picture of ATM interface health. Without concrete object names in hand, any further detail would be speculative rather than grounded.
What Can Be Monitored
- ATM interface status (extension to base ATM-MIB)
- additional ATM cell-layer statistics
- ATM physical-layer alarm conditions
This MIB depends on
Related MIBs
Imported Objects
From ATM-MIB
| atmInterfaceConfEntry | OBJECT-TYPE |
From CISCO-SMI
| ciscoExperiment | OBJECT-IDENTITY |
From IF-MIB
| ifIndex | OBJECT-TYPE |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ciscoAtm2MIB | 1.3.6.1.4.1.9.10.23 | This MIB Module is a supplement to the ATM-MIB [1]. It is an adaptation of a portion of the ATOMMIB supplemental MIB. | ||
| ciscoatm2MIBObjects | 1.3.6.1.4.1.9.10.23.1 | |||
| ciscoatmSigStatTable | 1.3.6.1.4.1.9.10.23.1.1 | not-accessible | This table contains ATM interface signalling monitoring , one entry per ATM signalling interface. | |
| ciscoatmSigStatEntry | 1.3.6.1.4.1.9.10.23.1.1.1 | not-accessible | This list contains signalling statistics variables. | |
| C32 ciscoatmSigSSCOPConEvents | 1.3.6.1.4.1.9.10.23.1.1.1.5 | Counter32 | read-only | SSCOP Connection Events Counter. This counter counts the sum of the following errors: 1) SSCOP Connection Disconnect Counter The abnormal occurrence of this event is characterized by the expiry of Timer_NO_RESPONSE. (This event is communicated to the layer management with MAA-ERROR code P. See ITU-T Q.2110 [13].) 2) SSCOP Connection Initiation Failure This condition indicates the inability to establish an SSCOP connection. This event occurs whenever the number of expiries of the connection control timer (Timer_CC) exceeds the MaxCC or upon receipt of a connection reject message BGREJ PDU. (This event is communicated to layer management with MAA-ERROR code O. See ITU-T Q.2110.) 3) SSCOP Connection Re-Establ/Resynch This event occurs upon receipt of a BGN PDU or RESYNC PDU. |
| C32 ciscoatmSigSSCOPErrdPdus | 1.3.6.1.4.1.9.10.23.1.1.1.6 | Counter32 | read-only | SSCOP Errored PDUs Counter. This counter counts the sum of the following errors: 1) Invalid PDUs. These are defined in SSCOP and consist of PDUs with incorrect length (MAA-ERROR code U), undefined PDU type code or not 32-bit aligned. 2) PDUs that result in MAA error codes and are discarded See Errors A-M and Q-T defined in ITU-T Q.2110 [13]. |
| C32 ciscoatmSigDetectSetupAttempts | 1.3.6.1.4.1.9.10.23.1.1.1.7 | Counter32 | read-only | Call Setup Attempts Counter. This counter counts the number of call setup attempts(both successful and unsuccessful) detected on this interface. |
| C32 ciscoatmSigEmitSetupAttempts | 1.3.6.1.4.1.9.10.23.1.1.1.8 | Counter32 | read-only | Call Setup Attempts Counter. This counter counts the number of call setup attempts(both successful and unsuccessful) transmitted on this interface. |
| C32 ciscoatmSigDetectUnavailRoutes | 1.3.6.1.4.1.9.10.23.1.1.1.9 | Counter32 | read-only | Number of Route Unavailability detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 1 unallocated (unassigned) number 2 no route to specified transit network 3 no route to destination 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigEmitUnavailRoutes | 1.3.6.1.4.1.9.10.23.1.1.1.10 | Counter32 | read-only | Number of Route Unavailability transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 1 unallocated (unassigned) number 2 no route to specified transit network 3 no route to destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigDetectUnavailResrcs | 1.3.6.1.4.1.9.10.23.1.1.1.11 | Counter32 | read-only | Number of Resource Unavailability detected on this interfrace. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 35 requested VPCI/VCI not available 37 user cell rate not available (UNI3.1 only) 38 network out of order 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available (UNI3.0 only) 58 bearer capability not presently available 63 Service or option not available, unspecified 92 too many pending add party requests NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigEmitUnavailResrcs | 1.3.6.1.4.1.9.10.23.1.1.1.12 | Counter32 | read-only | Number of Resource Unavailability transmitted from this interfrace. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 35 requested VPCI/VCI not available 37 user cell rate not available (UNI3.1 only) 38 network out of order 41 temporary failure 45 no VPCI/VCI available 47 resource unavailable, unspecified 49 Quality of Service unavailable 51 user cell rate not available (UNI3.0 only) 58 bearer capability not presently available 63 Service or option not available, unspecified 92 too many pending add party requests NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigDetectCldPtyEvents | 1.3.6.1.4.1.9.10.23.1.1.1.13 | Counter32 | read-only | Number of Called Party Responsible For Unsuccessful Call detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line id restriction (CLIR) 27 destination out of order 31 normal, unspecified 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure. |
| C32 ciscoatmSigEmitCldPtyEvents | 1.3.6.1.4.1.9.10.23.1.1.1.14 | Counter32 | read-only | Number of Called Party Responsible For Unsuccessful Call transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 17 user busy 18 no user responding 21 call rejected 22 number changed 23 user rejects all calls with calling line id restriction (CLIR) 27 destination out of order 31 normal, unspecified 88 incompatible destination NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. Note: Cause Value #30 'response to STATUS ENQUIRY' was not included in this memo since it did not apply to a hard failure. |
| C32 ciscoatmSigDetectMsgErrors | 1.3.6.1.4.1.9.10.23.1.1.1.15 | Counter32 | read-only | Number of Incorrect Messages detected on this interface. The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted, that contain any of the Cause values listed below. - Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: 1. Message with invalid protocol discriminator 2. Message with errors in the call reference I.E. - Bits 5-8 of the first octet not equal to '0000' - Bits 1-4 of the first octet indicating a length other than 3 octets - RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress - SETUP message received with call reference flag incorrectly set to 1 - SETUP message received with a call reference for a call that is already active or in progress. 3. Message too short The following cause values are monitored by this counter (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigEmitMsgErrors | 1.3.6.1.4.1.9.10.23.1.1.1.16 | Counter32 | read-only | Number of Incorrect Messages detected on this interface. The Incorrect Messages Counter reflects any sort of incorrect information in a message. This includes: - RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and STATUS messages transmitted or received, that contain any of the Cause values listed below. - Ignored messages. These messages are dropped because the message was so damaged that it could not be further processed. A list of dropped messages is compiled below: 1. Message with invalid protocol discriminator 2. Message with errors in the call reference I.E. - Bits 5-8 of the first octet not equal to '0000' - Bits 1-4 of the first octet indicating a length other than 3 octets - RELEASE COMPLETE message received with a call reference that does not relate to a call active or in progress - SETUP message received with call reference flag incorrectly set to 1 - SETUP message received with a call reference for a call that is already active or in progress. 3. Message too short The following cause values are monitored by this counter (Note: These cause values apply to both UNI3.0 and UNI3.1 unless otherwise stated): Cause Value Meaning 10 VPCI/VCI unacceptable (UNI3.0 only) 36 VPCI/VCI assignment failure (UNI3.1 only) 81 invalid call reference value 82 identified channel does not exist 89 invalid endpoint reference 96 mandatory information element is missing 97 message type non-existent or not implemented 99 information element non-existent or not implemented 100 invalid information element contents 101 message not compatible with call state 104 incorrect message length 111 protocol error, unspecified NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigDetectClgPtyEvents | 1.3.6.1.4.1.9.10.23.1.1.1.17 | Counter32 | read-only | Number of Calling Party Events detected on this interface. This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is received (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 28 invalid number format (address incomplete) 43 access information discarded 57 bearer capability not authorized 65 bearer capability not implemented 73 unsupported combination of traffic parameters 78 AAL parameters cannot be supported (UNI3.1 only) 91 invalid transit network selection 93 AAL parameters cannot be supported (UNI3.0 only) NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigEmitClgPtyEvents | 1.3.6.1.4.1.9.10.23.1.1.1.18 | Counter32 | read-only | Number of Calling Party Events transmitted from this interface. This counter monitors error events that occur due to the originating user doing something wrong. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE mesg for the same call), ADD PARTY REJECT, or STATUS message that contains one of the following cause code values is transmitted (Note: These cause values apply to both UNI3.0 and UNI3.1): Cause Value Meaning 28 invalid number format (address incomplete) 43 access information discarded 57 bearer capability not authorized 65 bearer capability not implemented 73 unsupported combination of traffic parameters 78 AAL parameters cannot be supported (UNI3.1 only) 91 invalid transit network selection 93 AAL parameters cannot be supported (UNI3.0 only) NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigDetectTimerExpireds | 1.3.6.1.4.1.9.10.23.1.1.1.19 | Counter32 | read-only | Number of Timer Expiries detected on this interface. The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The conditions for incrementing this counter are: - Expiry of any network timer - Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, 'recovery on timer expiry'. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigEmitTimerExpireds | 1.3.6.1.4.1.9.10.23.1.1.1.20 | Counter32 | read-only | Number of Timer Expiries transmitted from this interface. The Timer Expiries Counter provides a count of network timer expiries, and to some extent, host or switch timer expiries. The conditions for incrementing this counter are: - Expiry of any network timer - Receipt of a RELEASE or RELEASE COMPLETE message with Cause #102, 'recovery on timer expiry'. NOTE: For this counter, RELEASE COMPLETE messages that are a reply to a previous RELEASE message and contain the same cause value, are redundant (for counting purposes) and should not be counted. |
| C32 ciscoatmSigDetectRestarts | 1.3.6.1.4.1.9.10.23.1.1.1.21 | Counter32 | read-only | Number of Restart Activity errors detected on this interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when receiving a RESTART message. |
| C32 ciscoatmSigEmitRestarts | 1.3.6.1.4.1.9.10.23.1.1.1.22 | Counter32 | read-only | Number of Restart Activity errors transmitted from this interface. The Restart Activity Counter provides a count of host, switch, or network restart activity. This counter is incremented when transmitting a RESTART message. |
| C32 ciscoatmSigInEstabls | 1.3.6.1.4.1.9.10.23.1.1.1.23 | Counter32 | read-only | Number of SVC VCCs established at this signalling entity for incoming connections. |
| C32 ciscoatmSigOutEstabls | 1.3.6.1.4.1.9.10.23.1.1.1.24 | Counter32 | read-only | Number of SVC VCCs established at this signalling entity for outgoing connections. |
| ciscoatmSigSupportTable | 1.3.6.1.4.1.9.10.23.1.2 | not-accessible | This table contains ATM local interface configuration parameters, one entry per ATM signalling interface. | |
| ciscoatmSigSupportEntry | 1.3.6.1.4.1.9.10.23.1.2.1 | not-accessible | This list contains signalling configuration parameters and state variables. | |
| INT ciscoatmSigSupportClgPtyNumDel | 1.3.6.1.4.1.9.10.23.1.2.1.1 | INTEGER | read-write | This object indicates whether the Calling Party Number Information Element is transferred to the called party address. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| INT ciscoatmSigSupportClgPtySubAddr | 1.3.6.1.4.1.9.10.23.1.2.1.2 | INTEGER | read-write | This object indicates whether to accept and transfer the Calling Party Subaddress Information Element from the calling party to the called party. Calling party subaddress information shall only be transferred to the called party if calling party number delivery is enabled (i.e., atmSigSupportClgPtyNumDel = 'enabled(1)'. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| INT ciscoatmSigSupportCldPtySubAddr | 1.3.6.1.4.1.9.10.23.1.2.1.3 | INTEGER | read-write | This object indicates whether to accept, transfer, and deliver the Called Party Subaddress Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| INT ciscoatmSigSupportHiLyrInfo | 1.3.6.1.4.1.9.10.23.1.2.1.4 | INTEGER | read-write | This object indicates whether to accept, transfer, and deliver the Broadband High Layer Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| INT ciscoatmSigSupportLoLyrInfo | 1.3.6.1.4.1.9.10.23.1.2.1.5 | INTEGER | read-write | This object indicates whether to accept, transfer, and deliver the Broadband Low Layer Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| INT ciscoatmSigSupportBlliRepeatInd | 1.3.6.1.4.1.9.10.23.1.2.1.6 | INTEGER | read-write | This object indicates whether to accept, transfer, and deliver the Broadband Repeat Indicator with two or three instances of the Broadband Low Layer Information Element for low layer information selection from the calling party to the called party. This object shall only be transferred if atmSigSupportLoLyrInfo = 'enabled(1)'. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| INT ciscoatmSigSupportAALInfo | 1.3.6.1.4.1.9.10.23.1.2.1.7 | INTEGER | read-write | This object indicates whether to accept, transfer, and deliver the ATM Adaptation Layer Parameters Information Element from the calling party to the called party. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| INT ciscoatmSigSupportUnknownIe | 1.3.6.1.4.1.9.10.23.1.2.1.8 | INTEGER | read-write | This object indicates whether to accept, transfer, and deliver the unknown Information Element from the calling party to the called party, when the IE instruction field flag is set to zero.When the IE action flag is set to one, the IE action indicator should be followed regardless of this configuration. The value of this object can be: - enabled(1) This Information Element is transferred to the called party - disabled(2) This Information Element is NOT transferred to the called party. |
| ciscoatmInterfaceExtTable | 1.3.6.1.4.1.9.10.23.1.3 | not-accessible | This table contains ATM interface configuration not defined in the atmInterfaceConfTable from the ATM-MIB. This table has information on the VPI/VCI range. | |
| ciscoatmInterfaceExtEntry | 1.3.6.1.4.1.9.10.23.1.3.1 | not-accessible | An entry extends the atmInterfaceConfEntry defined in ATM-MIB. Each entry corresponds to an ATM interface. | |
| INT ciscoatmInterfaceConfMaxSvpcVpi | 1.3.6.1.4.1.9.10.23.1.3.1.16 | INTEGER | read-write | The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual path connections. |
| INT ciscoatmInterfaceCurrentMaxSvpcVpi | 1.3.6.1.4.1.9.10.23.1.3.1.17 | INTEGER | read-only | The maximum VPI that the signalling stack on the ATM interface may currently allocate to switched virtual path connections. This value is the minimum of ciscoatmInterfaceConfMaxSvpcVpi, and the ciscoatmInterfaceConfMaxSvpcVpi of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the maximum VPI that can be allocated to SVPCs on the interface, then the value of this object must equal ciscoatmInterfaceConfMaxSvpcVpi. |
| INT ciscoatmInterfaceConfMaxSvccVpi | 1.3.6.1.4.1.9.10.23.1.3.1.18 | INTEGER | read-write | The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual channel connections. |
| INT ciscoatmInterfaceCurrentMaxSvccVpi | 1.3.6.1.4.1.9.10.23.1.3.1.19 | INTEGER | read-only | The maximum VPI that the signalling stack on the ATM interface may currently allocate to switched virtual channel connections. This value is the minimum of ciscoatmInterfaceConfMaxSvccVpi, and the ciscoatmInterfaceConfMaxSvccVpi of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the maximum VPI that can be allocated to SVCCs on the interface, then the value of this object must equal ciscoatmInterfaceConfMaxSvccVpi. |
| INT ciscoatmInterfaceConfMinSvccVci | 1.3.6.1.4.1.9.10.23.1.3.1.20 | INTEGER | read-write | The minimum VCI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual channel connections. |
| INT ciscoatmInterfaceCurrentMinSvccVci | 1.3.6.1.4.1.9.10.23.1.3.1.21 | INTEGER | read-only | The minimum VCI that the signalling stack on the ATM interface may currently allocate to switched virtual channel connections. This value is the maximum of ciscoatmInterfaceConfMinSvccVci, and the ciscoatmInterfaceConfMinSvccVci of the interface's UNI/NNI peer. If the interface does not negotiate with its peer to determine the minimum VCI that can be allocated to SVCCs on the interface, then the value of this object must equal ciscoatmInterfaceConfMinSvccVci. |
| ciscoatm2MIBConformance | 1.3.6.1.4.1.9.10.23.3 | |||
| ciscoatm2MIBGroups | 1.3.6.1.4.1.9.10.23.3.1 | |||
| ciscoAtmSwitchServcHostGroup | 1.3.6.1.4.1.9.10.23.3.1.1 | A collection of objects providing information for a Switch/Service/Host that implements ATM interfaces. | ||
| ciscoAtmSwitchServcGroup | 1.3.6.1.4.1.9.10.23.3.1.3 | A collection of objects providing information for a Switch/Service that implements ATM interfaces. | ||
| ciscoAtmSwitchServcHostGroup2 | 1.3.6.1.4.1.9.10.23.3.1.4 | A collection of objects providing information regarding VPI/VCI range for SVCCs and SVPCs for a Switch/Service/Host that implements ATM interfaces. | ||
| ciscoatm2MIBCompliances | 1.3.6.1.4.1.9.10.23.3.2 | |||
| ciscoatm2MIBCompliance | 1.3.6.1.4.1.9.10.23.3.2.1 | The compliance statement for SNMP entities which represent ATM interfaces. The compliance statements are used to determine if a particular group or object applies to hosts, networks/switches, or both. | ||
| ciscoatm2MIBCompliance2 | 1.3.6.1.4.1.9.10.23.3.2.2 | The compliance statement for SNMP entities which represent ATM interfaces. The compliance statements are used to determine if a particular group or object applies to hosts, networks/switches, or both. |
RFC description
Cisco ATM2 supplemental MIB providing ATM interface signaling statistics, VPI/VCI range management, and signaling support information.
Start monitoring Cisco routers/switches with ATM interfaces with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.