Accounting Information for ATM Networks
Extracted elements (24)
All objects in this MIB have MAX-ACCESS of not-accessible because they are not intended to be read or written via SNMP directly; instead they define the syntax and semantics of data fields representable within a (subtree, list) accounting tuple as specified by RFC 2513.
The (subtree, list) tuple mechanism allows administrators to select arbitrary subsets of accounting data objects: the subtree OID is fixed as atmAcctngDataObjects, and the list OCTET STRING has bit N set to include the object with sub-identifier N, enabling flexible per-deployment accounting configuration.
The MIB is specified as SMIv2-compliant; a semantically equivalent SMIv1 MIB can be produced via translation, except that Counter64 objects (e.g., cell counters) cannot be translated and must be omitted, and some machine-readable SMIv2 information becomes textual descriptions.
If the local SNMP agent supports the object ifName, the value of atmAcctngIfName must be identical to that of ifName in the conceptual row of the ifTable corresponding to this interface.
atmAcctngCallingParty and atmAcctngCalledParty record the ATM addresses of the calling and called parties; the zero-length string is used when unknown (e.g., for a PVC).
atmAcctngCallingPartySubAddress and atmAcctngCalledPartySubAddress (AtmAddr) record the sub-addresses of the calling and called parties; zero-length string when absent or unknown.
atmAcctngCallReference is an OCTET STRING of size 0..3 containing the Q.2931 call reference value; zero-length string when unknown (e.g., PVC).
atmAcctngCastType indicates whether the ATM connection is point-to-point (p2p) or point-to-multipoint (p2mp).
atmAcctngCollectMode records why the accounting data was collected: onRelease(1), periodically(2), or onCommand(3).
atmAcctngConnectionType identifies the ATM connection type as one of: pvc(1), pvp(2), svcIncoming(3), svcOutgoing(4), svpIncoming(5), svpOutgoing(6), spvcInitiator(7), spvcTarget(8), spvpInitiator(9), or spvpTarget(10).
atmAcctngIfAlias provides the non-volatile 'alias' name for the interface as set by a network manager; unlike ifIndex, its value is retained across agent reboots.
atmAcctngIfName provides a textual name for the interface on which data was collected; if the agent supports ifName, this value MUST be identical to the corresponding ifName in the ifTable.
atmAcctngRecordCrc16 is a 2-octet CRC-16 (ISO 3309/ITU X.25) checksum over the entire accounting record; it is computed by initializing the field to '0000'H, generating the record, then overwriting with the computed checksum.
atmAcctngReleaseCause (Integer32) records the Q.2931 Release message cause code when data was collected due to SVC release; it is zero for all other collection modes.
atmAcctngServiceCategory identifies the ATM service category for the connection: other(1), cbr(2), vbrRt(3), vbrNrt(4), abr(5), ubr(6), or unknown(7).
atmAcctngStartTime and atmAcctngCollectionTime record the DateAndTime at which the connection was established and at which the accounting data was collected, respectively.
atmAcctngTransmittedCells and atmAcctngReceivedCells are Counter64 objects counting all cells (including OAM cells) transmitted and received by the switch on the connection.
atmAcctngTransmittedClp0Cells and atmAcctngReceivedClp0Cells are Counter64 objects counting cells with CLP=0 (including OAM cells) transmitted and received on the connection.
atmAcctngVpi and atmAcctngVci record the VPI (range 0..4095) and VCI (range 0..65535) used for the ATM connection being accounted.
Each traffic descriptor direction has five parameter objects (Param1..Param5, INTEGER 0..2147483647) whose interpretation depends on the corresponding TrafficDescriptorType OID.
The ATM-ACCOUNTING-INFORMATION-MIB module is assigned OID { mib-2 59 } and defines a subtree (atmAcctngDataObjects) under which all ATM accounting data objects are defined, selectable via (subtree, list) tuples as specified in RFC 2513.
Traffic descriptor objects (atmAcctngTransmitTrafficDescriptorType and atmAcctngReceiveTrafficDescriptorType) are OBJECT IDENTIFIERs referencing the traffic descriptor type as defined in RFC 1695 for each direction.
IANA assigned OID { mib-2 59 } to the ATM-ACCOUNTING-INFORMATION-MIB module (atmAccountingInformationMIB) prior to publication of this RFC.
The MIB objects are only accessible through collected accounting files, not directly via SNMP. After collection, accounting data must be protected against modification or unauthorized deletion to preserve billing and audit integrity.