ATM2-MIB: View SNMP OID List / Download MIB

Copyright (C) The Internet Society (2003). This version of this MIB module is part of RFC 3606; see the RFC itself for full legal notices. This MIB Module is a supplement to the ATM-MIB defined in RFC 2515.

The ATM SVPC Cross-Connect table. A bi-directional VP cross-connect between two switched VPLs is modeled as one entry in this table. A Soft PVPC cross-connect, between a soft permanent VPL and a switched VPL, is also modeled as one entry in this table.

An entry in the ATM SVPC Cross-Connect table. This entry is used to model a bi-directional ATM VP cross-connect between two VPLs.

A unique value to identify this SVPC cross-connect. For each VP associated with this cross-connect, the agent reports this cross-connect index value in the atmVplCrossConnectIdentifer attribute of the corresponding atmVplTable entries.

The value of this object is equal to the ifIndex value of the ATM interface port for this SVPC cross-connect. The term low implies that this ATM interface has the numerically lower ifIndex value than the other ATM interface identified in the same atmSvcVpCrossConnectEntry.

The value of this object is equal to the VPI value associated with the SVPC cross-connect at the ATM interface that is identified by atmSvcVpCrossConnectLowIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvpcVpi at the low ATM interface port.

The value of this object is equal to the ifIndex value of the ATM interface port for this SVC VP cross-connect. The term high implies that this ATM interface has the numerically higher ifIndex value than the other ATM interface identified in the same atmSvcVpCrossConnectEntry.

The value of this object is equal to the VPI value associated with the SVPC cross-connect at the ATM interface that is identified by atmSvcVpCrossConnectHighIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvpcVpi at the high ATM interface port.

The value of the sysUpTime object at the time this bi-directional SVPC cross-connect was created. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.

This object is used to delete rows in the atmSvcVpCrossConnectTable.

The ATM SVCC Cross-Connect table. A bi-directional VC cross-connect between two switched VCLs is modeled as one entry in this table. A Soft PVCC cross-connect, between a soft permanent VCL and a switched VCL, is also modeled as one entry in this table.

An entry in the ATM SVCC Cross-Connect table. This entry is used to model a bi-directional ATM VC cross-connect between two VCLs.

A unique value to identify this SVCC cross-connect. For each VP associated with this cross-connect, the agent reports this cross-connect index value in the atmVclCrossConnectIdentifier attribute of the corresponding atmVplTable entries.

The value of this object is equal to the ifIndex value of the ATM interface port for this SVCC cross-connect. The term low implies that this ATM interface has the numerically lower ifIndex value than the other ATM interface identified in the same atmSvcVcCrossConnectEntry.

The value of this object is equal to the VPI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectLowIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvccVpi at the low ATM interface port.

The value of this object is equal to the VCI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectLowIfIndex. The VCI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvccVci at the low ATM interface port.

The value of this object is equal to the ifIndex value for the ATM interface port for this SVCC cross-connect. The term high implies that this ATM interface has the numerically higher ifIndex value than the other ATM interface identified in the same atmSvcVcCrossConnectEntry.

The value of this object is equal to the VPI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectHighIfIndex. The VPI value cannot exceed the number supported by the atmInterfaceCurrentMaxSvccVpi at the high ATM interface port.

The value of this object is equal to the VCI value associated with the SVCC cross-connect at the ATM interface that is identified by atmSvcVcCrossConnectHighIfIndex. The VCI value cannot exceed the number supported by the atmInterfaceMaxVciBits at the high ATM interface port.

The value of the sysUpTime object at the time this bi-directional SVCC cross-connect was created. If the current state was entered prior to the last re-initialization of the agent, then this object contains a zero value.

This object is used to delete rows in the atmSvcVcCrossConnectTable.

This table contains ATM interface signalling statistics, one entry per ATM signalling interface.

This list contains signalling statistics variables.

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.) 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) equals or 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 RS PDU.

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 an incorrect length (MAA-ERROR code U), an undefined PDU type code, or that are not 32-bit aligned. 2) PDUs that result in MAA-ERROR codes and are discarded. See MAA-ERROR codes A-D, F-M, and Q-T defined in ITU-T Q.2110.

Call Setup Attempts Counter. This counter counts the number of call setup attempts (both successful and unsuccessful) detected on this interface.

Call Setup Attempts Counter. This counter counts the number of call setup attempts (both successful and unsuccessful) transmitted on this interface.

Number of Route Unavailability detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message 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 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.

Number of Route Unavailability transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message 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.

Number of Resource Unavailability detected on this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message 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.

Number of Resource Unavailability transmitted from this interface. This counter is incremented when a RELEASE, RELEASE COMPLETE (only when not preceded by a RELEASE message 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.

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 message 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 identification 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.

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 message 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 identification 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.

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.

Number of Incorrect Messages transmitted 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.

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 message 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.

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 message 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.

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.

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.

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.

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.

Number of SVCs established at this signalling entity for incoming connections.

Number of SVCs established at this signalling entity for outgoing connections.

This table contains ATM local interface configuration parameters, one entry per ATM signalling interface.

This list contains signalling configuration parameters and state variables.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

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's value should always be disabled(2) if the value of atmSigSupportLolyrInfo is disabled(2). 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. Enumeration: 'disabled': 2, 'enabled': 1.

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. Enumeration: 'disabled': 2, 'enabled': 1.

This parameter identifies the carrier to which intercarrier calls originated from this interface are routed when transit network selection information is not provided by the calling party. If a Carrier Identification Code (CIC) is used the parameter shall contain the CIC. For three-digit CICs, the first octet shall be '0' and the CIC is contained in the three following octets. If the preferred carrier feature is not supported the value is a zero-length string.

A table contains signalling capabilities of VCLs except the Traffic Descriptor. Traffic descriptors are described in the atmTrafficDescrParamTable.

Each entry in this table represents a set of signalling capabilities that can be applied to a VCL. There is no requirement for unique entries, except that the index must be unique.

The value of this object is used by the atmVclGenSigDescrIndex object in the atmVclGenTable to identify a row in this table.

The AAL type. The value of this object is set to other(1) when not defined. Enumeration: 'userDefined': 5, 'aal2': 6, 'aal1': 2, 'aal5': 4, 'other': 1, 'aal34': 3.

The SSCS type used by this entry. Enumeration: 'frameRelay': 4, 'null': 5, 'other': 1, 'nonassured': 3, 'assured': 2.

The Broadband high layer type. Enumeration: 'vendorSpecific': 5, 'other': 1, 'iso': 2, 'user': 3, 'hiProfile': 4.

The Broadband high layer information. When atmSigDescrParamBhliType is set to iso(2), the value of this object is a zero length string. When atmSigDescrParamBhliType is set to user(3), the value of this object is an octet string with length ranging from 0 to 8. When atmSigDescrParamBhliType is set to hiProfile(4), the value of this object is a length of 4 octet string containing user to user profile identifier. When atmSigDescrParamBhliType is set to vendorSpecific(5), the value of this object is a length of 7 octet string, where the most significant 3 octets consist of a globally- administered OUI, and the least significant 4 octets are the vender administered application OUI.

The Broadband bearer capability user plane connection configuration parameter. Enumeration: 'ptmp': 2, 'ptp': 1.

The Broadband low layer information, protocol type of layer 2. The value of this object is other(1) if layer 2 protocol is not used. Enumeration: 'userDef': 13, 'x25multilink': 5, 'x75slp': 11, 'hdlcAbm': 9, 'iso1745': 2, 'iso7776': 14, 'q921': 3, 'q922': 12, 'other': 1, 'iso88022': 10, 'hdlcNrm': 8, 'lapb': 6, 'hdlcArm': 7, 'x25linklayer': 4.

The Broadband low layer information, protocol type of layer 3. The value of this object is other(1) if layer 3 protocol is not used. Enumeration: 'userDef': 8, 'isoiec8208': 3, 'x25pkt': 2, 'isoiec8473': 5, 'tr9577': 7, 't70': 6, 'other': 1, 'x223iso8878': 4.

The default packet size defined in B-LLI. Enumeration: 's128': 5, 's4096': 10, 's2048': 9, 's512': 7, 's16': 2, 's256': 6, 's32': 3, 'other': 1, 's64': 4, 's1024': 8.

The SNAP ID used for Broadband low layer protocol layer 3. The value of this object is other(1) if atmSigDescrParamBlliLayer3 is set to other(1). Enumeration: 'false': 3, 'other': 1, 'true': 2.

The OUI/PID encoding for Broadband low layer protocol layer 3. The value of this object is a zero length string if atmSigDescrParamBlliLayer3 is set to other(1). When used, it is always 5 octets with the most significant octet as the OUI Octet 1 and the least significant octet as the PID Octet 2.

This object is used to create and delete rows in the atmSigDescrParamTable.

This table contains a list of ATM addresses that can be used for calls to and from a given interface by a switch or service. The ATM addresses are either registered by the endsystem via ILMI or statically configured. This table does not expose PNNI reachability information. ILMI registered addresses cannot be deleted using this table. This table only applies to switches and network services.

An entry in the ATM Interface Registered Address table.

An address registered for a given switch or service interface.

The type of address source for a given ATM Address. The value dynamic(3) is indicated when ILMI is used. Enumeration: 'dynamic': 3, 'other': 1, 'static': 2.

This object indicates the organizational scope for the referenced address. The information of the referenced address shall not be distributed outside the indicated scope. Refer to Annex 5.3 of ATM Forum UNI Signalling 4.0 for guidelines regarding the use of organizational scopes. This value cannot be configured for ILMI-registered addresses. The default values for organizational scope are localNetwork(1) for ATM group addresses, and global(15) for individual addresses. Enumeration: 'organizationMinusOne': 7, 'global': 15, 'sitePlusOne': 6, 'intraCommunity': 11, 'regional': 13, 'intraOrganization': 8, 'localNetwork': 1, 'organizationPlusOne': 9, 'localNetworkPlusOne': 2, 'siteMinusOne': 4, 'localNetworkPlusTwo': 3, 'intraSite': 5, 'interRegional': 14, 'communityMinusOne': 10, 'communityPlusOne': 12.

This object is used to create and delete rows in the atmIfRegisteredAddrTable. Rows created dynamically (e.g., ILMI- registered addresses) cannot be deleted using this object.

This table provides a mapping between the atmVclTable and the ATM called party/calling party address. This table can be used to retrieve the calling party and called party ATM address pair for a given VCL. Note that there can be more than one pair of calling party and called party ATM addresses for a VCL in a point to multi-point call.

Each entry in this table represents a binding between a VCL and an ATM address associated with this call. This ATM address can be either the called party address or the calling party address. There can be more than one pair of calling/called party ATM addresses associated with the VCL entry for point to multi-point calls. Objects atmVclAddrType, and atmVclAddrRowStatus are required during row creation.

An ATM address on one end of the VCL. For SVCs, the agent supplies the value of this object at creation time. For PVC VCL, the manager can supply the value of this object during or after the PVC VCL creation.

The type of ATM Address represented by the object atmVclAddrAddr. Choices are either the calling party ATM address or the called party ATM address. Enumeration: 'callingParty': 1, 'calledParty': 2.

This object is used to create or destroy an entry from this table. Note that the manager entity can only destroy the PVC VCLs.

This table provides an alternative way to retrieve the atmVclTable. This table can be used to retrieve the indexing to the atmVclTable by an ATM address.

Each entry in this table represents an entry in the atmVclTable of the ATM-MIB by its ATM address. The ATM address is either the calling or called party ATM address of the call. Entries in this table are read only. They show up when entries are created in the atmVclAddrTable.

The interface index of the ATM interface to which this VCL pertains. This object combined with the atmAddrVclVpi and atmAddrVclVci objects serves as an index to the atmVclTable.

The VPI value of the VCL. This object combined with the atmAddrVclAtmIfIndex and atmAddrVclVci objects serves as an index to the atmVclTable.

The VCI value of the VCL. This object combined with the atmAddrVclAtmIfIndex and atmAddrVclVpi objects serves as an index to the atmVclTable.

The type of ATM Address represented by the object atmVclAddrAddr. Choices are either calling party address or called party address. Enumeration: 'callingParty': 1, 'calledParty': 2.

This table contains all statistics counters per VPL. It is used to monitor the usage of the VPL in terms of incoming cells and outgoing cells.

Each entry in this table represents a VPL.

The total number of valid ATM cells received by this VPL including both CLP=0 and CLP=1 cells. The cells are counted prior to the application of the traffic policing.

The number of valid ATM cells received by this VPL with CLP=0. The cells are counted prior to the application of the traffic policing.

The total number of valid ATM cells discarded by the traffic policing entity. This includes cells originally received with CLP=0 and CLP=1.

The total number of valid ATM cells received with CLP=0 and discarded by the traffic policing entity.

The total number of valid ATM cells transmitted by this VPL. This includes both CLP=0 and CLP=1 cells.

The total number of valid ATM cells transmitted with CLP=0 by this VPL.

The total number of valid ATM cells tagged by the traffic policing entity from CLP=0 to CLP=1.

Indicates whether the VPL is an ATM Logical Port interface (ifType=80).

An entry with information about the ATM Logical Port interface.

Indicates whether the VPC at this VPL interface is an ATM Logical Port interface. Enumeration: 'notLogicalIf': 1, 'isLogicalIf': 2.

The ifTable index of the ATM logical port interface associated with this VPL. The distinguished value of zero indicates that the agent has not (yet) assigned such an ifTable Index. The zero value must be assigned by the agent if the value of atmVplLogicalPortDef is set to notLogicalIf, or if the VPL row is not active.

This table contains all statistics counters per VCL. It is used to monitor the usage of the VCL in terms of incoming cells and outgoing cells.

Each entry in this table represents a VCL.

The total number of valid ATM cells received by this VCL including both CLP=0 and CLP=1 cells. The cells are counted prior to the application of the traffic policing.

The number of valid ATM cells received by this VCL with CLP=0. The cells are counted prior to the application of the traffic policing.

The total number of valid ATM cells discarded by the traffic policing entity. This includes cells originally received with CLP=0 and CLP=1.

The total number of valid ATM cells received with CLP=0 and discarded by the traffic policing entity.

The total number of valid ATM cells transmitted by this VCL. This includes both CLP=0 and CLP=1 cells.

The total number of valid ATM cells transmitted with CLP=0 by this VCL.

The total number of valid ATM cells tagged by the traffic policing entity from CLP=0 to CLP=1.

This table provides a collection of objects providing AAL5 configuration and performance statistics of a VCL.

Each entry in this table represents an AAL5 VCL, and is indexed by ifIndex values of AAL5 interfaces and the associated VPI/VCI values.

The number of AAL5 CPCS PDUs received on the AAL5 VCC at the interface identified by the ifIndex.

The number of AAL5 CPCS PDUs transmitted on the AAL5 VCC at the interface identified by the ifIndex.

The number of octets contained in AAL5 CPCS PDUs received on the AAL5 VCC at the interface identified by the ifIndex.

The number of octets contained in AAL5 CPCS PDUs transmitted on the AAL5 VCC at the interface identified by the ifIndex.

General Information for each VC.

An entry with general information about the ATM VC.

The value of this object identifies the row in the ATM Signalling Descriptor Parameter Table which applies to this VCL.

This table contains ATM interface configuration and monitoring information not defined in the atmInterfaceConfTable from the ATM-MIB. This includes the type of connection setup procedures, ILMI information, and information on the VPI/VCI range.

An entry extends the atmInterfaceConfEntry defined in the ATM- MIB. Each entry corresponds to an ATM interface.

The type of connection setup procedures configured for the ATM interface. Setting this variable to a value of 'other' is not allowed.

The type of connection setup procedures currently being used on the interface. This may reflect a manually configured value for the interface type, or may be determined by other means such as auto-configuration. A value of `autoConfig' indicates that auto-configuration was requested but has not yet been completed.

The configured role of the managed entity as one side of the ATM interface. This value does not apply when the object atmIntfConfigType is set to `autoConfig', `atmfPnni1Dot0', or `atmfBici2Dot0'. Enumeration: 'other': 1, 'user': 2, 'network': 3.

The current role used by the managed entity to represent one side of the ATM interface. Enumeration: 'symmetric': 4, 'other': 1, 'user': 2, 'network': 3.

Indicates which components of ILMI are administratively enabled on this interface. If the 'ilmi' bit is not set, then no ILMI components are operational. ILMI components other than auto- configuration that are not represented in the value have their administrative status determined according to the 'ilmi' bit. The ILMI auto-configuration component is enabled/disabled by the atmIntfConfigType object. Bits: 'ilmiConnectivity': 2, 'ilmiAddressRegistration': 1, 'ilmiSigVccParamNegotiation': 4, 'ilmi': 0, 'ilmiPvcPvpMgmt': 3.

Indicates which components of ILMI are operational on this interface. Bits: 'ilmiConnectivity': 2, 'ilmiAddressRegistration': 1, 'ilmiSigVccParamNegotiation': 4, 'ilmi': 0, 'ilmiPvcPvpMgmt': 3.

Indicates the state of the ILMI Finite State Machine associated with this interface. Enumeration: 'configuring': 4, 'verifying': 9, 'registeringAddresses': 8, 'establishing': 3, 'retrievingAddresses': 7, 'stopped': 1, 'linkFailing': 2, 'retrievingNetworkPrefixes': 5, 'registeringNetworkPrefixes': 6.

The amount of time S between successive transmissions of ILMI messages on this interface for the purpose of detecting establishment of ILMI connectivity.

The amount of time T between successive transmissions of ILMI messages on this interface for the purpose of detecting loss of ILMI connectivity. The distinguished value zero disables ILMI connectivity procedures on this interface.

The number K of consecutive polls on this interface for which no ILMI response message is received before ILMI connectivity is declared lost.

Specifies whether this end of the interface is advertised in ILMI as a device of the `public' or `private' type. Enumeration: 'other': 1, 'public': 2, 'private': 3.

The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual path connections.

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 atmInterfaceConfMaxSvpcVpi, and the atmInterfaceMaxSvpcVpi 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 atmInterfaceConfMaxSvpcVpi.

The maximum VPI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual channel connections.

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 atmInterfaceConfMaxSvccVpi, and the atmInterfaceConfMaxSvccVpi 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 atmInterfaceConfMaxSvccVpi.

The minimum VCI that the signalling stack on the ATM interface is configured to support for allocation to switched virtual channel connections.

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 atmInterfaceConfMinSvccVci, and the atmInterfaceConfMinSvccVci 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 atmInterfaceConfMinSvccVci.

This object identifies the row in the atmTrafficDescrParamTable used during ILMI auto-configuration to specify the advertised signalling VCC traffic parameters for the receive direction. The traffic descriptor resulting from ILMI auto-configuration of the signalling VCC is indicated in the atmVclTable.

This object identifies the row in the atmTrafficDescrParamTable used during ILMI auto-configuration to specify the advertised signalling VCC traffic parameters for the transmit direction. The traffic descriptor resulting from ILMI auto-configuration of the signalling VCC is indicated in the atmVclTable.

The number of times the operational status of a PVPL or PVCL on this interface has gone down.

The current number of VPLs on this interface for which there is an active row in the atmVplTable having an atmVplConnKind value of `pvc' and an atmVplOperStatus with a value other than `up'.

The current number of VCLs on this interface for which there is an active row in the atmVclTable having an atmVclConnKind value of `pvc' and an atmVclOperStatus with a value other than `up'.

Allows the generation of traps in response to PVCL or PVPL failures on this interface.

The minimum interval between the sending of atmIntfPvcFailuresTrap notifications for this interface.

Number of setup failures. For root, this is the number of rejected setup requests and for leaf, this is the number of setup failure received.

Number of setup requests. For root, this includes both incoming setup request and root intiated setup requests.

This table contains a list of all the ATM network services known by this device. The characteristics of these services are made available through the ILMI, using the ILMI general-purpose service registry MIB. These services may be made available to all ATM interfaces (atmIlmiSrvcRegIndex = 0) or to some specific ATM interfaces only (atmIlmiSrvcRegIndex = ATM interface index).

Information about a single service provider that is available to the user-side of an adjacent device through the ILMI. Implementors need to be aware that if the size of the atmIlmiSrvcRegServiceID exceeds 112 sub-identifiers then OIDs of column instances in this table will have more than 128 sub- identifiers and cannot be accessed using SNMPv1, SNMPv2, or SNMPv3.

The ATM interface where the service defined in this entry can be made available to an ATM device attached to this interface. The value of 0 has a special meaning: when an ATM service is defined in an entry whose atmIlmiSrvcRegIndex is zero, the ATM service is available to ATM devices connected to any ATM interface. (default value(s)). When the user-side of an adjacent device queries the content of the ILMI service registry MIB (using the ILMI protocol), the local network-side responds with the ATM services defined in atmIlmiSrvcRegTable entries, provided that these entries are indexed by: - the corresponding ifIndex value (atmIlmiSrvcRegIndex equal to the ifIndex of the interface to which the adjacent device is connected) - zero (atmIlmiSrvcRegIndex=0).

This is the service identifier which uniquely identifies the type of service at the address provided in the table. The object identifiers for the LAN Emulation Configuration Server (LECS) and the ATM Name Server (ANS) are defined in the ATM Forum ILMI Service Registry MIB. The object identifiers for the ATMARP Server, the Multicast Address Resolution Server (MARS), and the NHRP Server (NHS) are defined in RFC 2601, RFC 2602, and RFC 2603, respectively.

An arbitrary integer to differentiate multiple rows containing different ATM addresses for the same service on the same interface. This number need NOT be the same as the corresponding ILMI atmfSrvcRegAddressIndex MIB object.

This is the full address of the service. The user-side of the adjacent device may use this address to establish a connection with the service.

An octet string used according to the value of atmIlmiSrvcRegServiceID.

This object is used to create or destroy an entry from this table.

A table specifying per-interface network prefix(es) supplied by the network side of the UNI during ILMI address registration. When no network prefixes are specified for a particular interface, one or more network prefixes based on the switch address(es) may be used for ILMI address registration.

Information about a single network prefix supplied by the network side of the UNI during ILMI address registration. Note that the index variable atmIlmiNetPrefixPrefix is a variable- length string, and as such the rule for variable-length strings in section 7.7 of RFC 2578 applies.

The network prefix specified for use in ILMI address registration.

Used to create, delete, activate and de-activate network prefixes used in ILMI address registration.

This table contains one or more ATM endsystem addresses on a per-switch basis. These addresses are used to identify the switch. When no ILMI network prefixes are configured for certain interfaces, network prefixes based on the switch address(es) may be used for ILMI address registration.

An entry in the ATM Switch Address table.

An arbitrary index used to enumerate the ATM endsystem addresses for this switch.

An ATM endsystem address or address prefix used to identify this switch. When no ESI or SEL field is specified, the switch may generate the ESI and SEL fields automatically to obtain a complete 20-byte ATM endsystem address.

Used to create, delete, activate, and de-activate addresses used to identify this switch.

This table contains one row per VP Cross-Connect represented in the atmVpCrossConnectTable.

Information about a particular ATM VP Cross-Connect. Each entry provides an two objects that name the Cross-Connect. One is assigned by the Service User and the other by the Service Provider.

This is a service user assigned textual representation of a VPC PVC.

This is a system supplied textual representation of VPC PVC. It is assigned by the service provider.

This table contains one row per VC Cross-Connect represented in the atmVcCrossConnectTable.

Information about a particular ATM VC Cross-Connect. Each entry provides an two objects that name the Cross-Connect. One is assigned by the Service User and the other by the Service Provider.

This is a service user assigned textual representation of a VCC PVC.

This is a system supplied textual representation of VCC PVC. It is assigned by the service provider.

A table indicating all VPLs for which there is an active row in the atmVplTable having an atmVplConnKind value of `pvc' and an atmVplOperStatus with a value other than `up'.

Each entry in this table represents a VPL for which the atmVplRowStatus is `active', the atmVplConnKind is `pvc', and the atmVplOperStatus is other than `up'.

The time at which this PVPL began to fail.

A table indicating all VCLs for which there is an active row in the atmVclTable having an atmVclConnKind value of `pvc' and an atmVclOperStatus with a value other than `up'.

Each entry in this table represents a VCL for which the atmVclRowStatus is `active', the atmVclConnKind is `pvc', and the atmVclOperStatus is other than `up'.

The time at which this PVCL began to fail.

A notification indicating that one or more PVPLs or PVCLs on this interface has failed since the last atmPvcFailuresTrap was sent. If this trap has not been sent for the last atmIntfPvcNotificationInterval, then it will be sent on the next increment of atmIntfPvcFailures.

A collection of objects providing information for a Switch/Service/Host that implements ATM interfaces.

A collection of objects providing information for a Switch/Service/Host that implements ATM VCL and VPL Statistics

A collection of objects providing information for a Switch/Service that implements ATM interfaces.

A collection of objects providing information for a Switch/Service that implements ATM signalling.

A collection of notifications providing information for a Switch/Service that implements ATM interfaces.

A collection of objects providing information for an ATM switch.

A collection of objects providing information for an ATM Network Service.

A collection of objects providing information for a Host that implements ATM interfaces.

A collection of objects providing information for a Host that implements ATM interfaces.

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. The Common group is defined as applicable to all three.