Network Working Group K. McCloghrie
Request for Comments: 2512 Cisco Systems, Inc.
Category: Standards Track J. Heinanen
Telia Finland, Inc.
W. Greene
MCI Telecommunications Corp.
A. Prasad
Cisco Systems, Inc.
February 1999
Network Working Group K. McCloghrie
Request for Comments: 2512 Cisco Systems, Inc.
Category: Standards Track J. Heinanen
Telia Finland, Inc.
W. Greene
MCI Telecommunications Corp.
A. Prasad
Cisco Systems, Inc.
February 1999
Accounting Information for ATM Networks
ATM网络的会计信息
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Table of Contents
目录
1 Introduction ................................................... 1
2 The SNMP Network Management Framework .......................... 2
3 Overview ....................................................... 3
4 Definitions .................................................... 3
5 Acknowledgements ...............................................12
6 References .....................................................12
7 Security Considerations ........................................13
8 IANA Considerations ............................................13
9 Authors' Addresses .............................................14
10 Full Copyright Statement ......................................15
1 Introduction ................................................... 1
2 The SNMP Network Management Framework .......................... 2
3 Overview ....................................................... 3
4 Definitions .................................................... 3
5 Acknowledgements ...............................................12
6 References .....................................................12
7 Security Considerations ........................................13
8 IANA Considerations ............................................13
9 Authors' Addresses .............................................14
10 Full Copyright Statement ......................................15
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. A separate memo [16] defines managed objects, in a manner independent of the type of network, for controlling the selection, collection and storage of accounting information into files for later retrieval via a file transfer protocol. This memo defines a set of ATM-specific accounting information which can be collected for connections on ATM networks.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。单独的备忘录[16]以独立于网络类型的方式定义了托管对象，用于控制会计信息的选择、收集和存储到文件中，以便以后通过文件传输协议检索。此备忘录定义了一组ATM特定的会计信息，可收集这些信息用于ATM网络上的连接。
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2271 [1].
o RFC 2271[1]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[2]、STD 16、RFC 1212[3]和RFC 1215[4]中进行了描述。第二个版本称为SMIv2，在RFC 1902[5]、RFC 1903[6]和RFC 1904[7]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[8]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[9]和RFC 1906[10]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[10]、RFC 2272[11]和RFC 2274[12]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13].
o 访问管理信息的协议操作。STD 15、RFC 1157[8]中描述了第一组协议操作和相关PDU格式。RFC 1905[13]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2273 [14] and the view-based access control mechanism described in RFC 2275 [15].
o RFC 2273[14]中描述的一组基本应用程序和RFC 2275[15]中描述的基于视图的访问控制机制。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (e.g., use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（例如，使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
In [16], the items of accounting data to be collected are specified as a set of objects. Which objects are contained in such a set is selectable by an administrator through the specification of one or more (subtree, list) tuples, where the set of objects to be collected is the union of the subsets specified by each tuple:
在[16]中，将要收集的会计数据项指定为一组对象。管理员可以通过指定一个或多个（子树、列表）元组来选择包含在此类集合中的对象，其中要收集的对象集合是每个元组指定的子集的并集：
'subtree' specifies a OBJECT IDENTIFIER value such that every object in the subset is named by the subtree's value appended with a single additional sub-identifier.
“子树”指定一个对象标识符值，这样子集中的每个对象都由附加有单个附加子标识符的子树值命名。
'list' specifies an OCTET STRING value, such that if the N-th bit of the string's value is set then the the subset contains the object named by appending N as a single additional sub-identifier to the subtree.
“list”指定一个八进制字符串值，这样，如果设置了字符串值的第N位，则子集包含通过将N作为单个附加子标识符附加到子树而命名的对象。
This memo specifies such a subtree containing a set of objects defining items of accounting information which are applicable to ATM connections.
此备忘录指定了包含一组对象的子树，这些对象定义了适用于ATM连接的会计信息项。
Note that all of the objects defined here have a MAX-ACCESS clause of not-accessible, since their purpose is not to be read/written by SNMP, but rather, to be the syntax and semantics of the set of information which can be represented within a single (subtree, list) tuple.
请注意，此处定义的所有对象都有一个MAX-ACCESS子句not ACCESS，因为它们的目的不是由SNMP读/写，而是作为可以在单个（子树，列表）元组中表示的信息集的语法和语义。
ATM-ACCOUNTING-INFORMATION-MIB DEFINITIONS ::= BEGIN
ATM-ACCOUNTING-INFORMATION-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, mib-2, Integer32, Counter64 FROM SNMPv2-SMI DisplayString, DateAndTime FROM SNMPv2-TC AtmAddr FROM ATM-TC-MIB;
从SNMPv2 SMI显示字符串中导入模块标识、对象类型、对象标识、mib-2、整数32、计数器64，从ATM-TC-mib中导入SNMPv2 TC AtmAddr中的日期和时间；
atmAccountingInformationMIB MODULE-IDENTITY LAST-UPDATED "9611052000Z" ORGANIZATION "IETF AToM MIB Working Group" CONTACT-INFO " Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive, San Jose CA 95134-1706. Phone: +1 408 526 5260 Email: kzm@cisco.com"
ATMacCountingInformation MIB MODULE-IDENTITY上次更新的“9611052000Z”组织“IETF AToM MIB工作组”联系方式“Keith McCloghrie Cisco Systems，Inc.，地址：加利福尼亚州圣何塞市西塔斯曼大道170号95134-1706。电话：+1 408 526 5260电子邮件：kzm@cisco.com"
DESCRIPTION
"The MIB module for identifying items of accounting
information which are applicable to ATM connections."
::= { mib-2 59 }
DESCRIPTION
"The MIB module for identifying items of accounting
information which are applicable to ATM connections."
::= { mib-2 59 }
atmAcctngMIBObjects OBJECT IDENTIFIER ::=
{ atmAccountingInformationMIB 1 }
atmAcctngMIBObjects OBJECT IDENTIFIER ::=
{ atmAccountingInformationMIB 1 }
-- Definitions of objects for use in specifying ATM accounting
-- data to be collected
-- Definitions of objects for use in specifying ATM accounting
-- data to be collected
atmAcctngDataObjects OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identifier defines a subtree under which various
objects are defined such that a set of objects to be
collected as ATM accounting data can be specified as a
(subtree, list) tuple using this identifier as the subtree."
::= { atmAcctngMIBObjects 1 }
atmAcctngDataObjects OBJECT-IDENTITY
STATUS current
DESCRIPTION
"This identifier defines a subtree under which various
objects are defined such that a set of objects to be
collected as ATM accounting data can be specified as a
(subtree, list) tuple using this identifier as the subtree."
::= { atmAcctngMIBObjects 1 }
-- Objects defined under the atmAcctngDataObjects subtree
--
-- In each case the semantics of the object are interpreted with
-- respect to the creation/storage of an accounting record for a
-- particular connection on a particular interface.
-- Objects defined under the atmAcctngDataObjects subtree
--
-- In each case the semantics of the object are interpreted with
-- respect to the creation/storage of an accounting record for a
-- particular connection on a particular interface.
atmAcctngConnectionType OBJECT-TYPE
SYNTAX INTEGER { pvc(1),
pvp(2),
svcIncoming(3),
svcOutgoing(4),
svpIncoming(5),
svpOutgoing(6),
spvcInitiator(7),
spvcTarget(8),
spvpInitiator(9),
spvpTarget(10) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The type of connection."
::= { atmAcctngDataObjects 1 }
atmAcctngConnectionType OBJECT-TYPE
SYNTAX INTEGER { pvc(1),
pvp(2),
svcIncoming(3),
svcOutgoing(4),
svpIncoming(5),
svpOutgoing(6),
spvcInitiator(7),
spvcTarget(8),
spvpInitiator(9),
spvpTarget(10) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The type of connection."
::= { atmAcctngDataObjects 1 }
atmAcctngCastType OBJECT-TYPE SYNTAX INTEGER { p2p(1), p2mp(2) } MAX-ACCESS not-accessible
ATMACTNGCASTTYPE对象类型语法整数{p2p（1），p2mp（2）}MAX-ACCESS不可访问
STATUS current
DESCRIPTION
"An indication of whether the connection is point-to-point
or point-to-multipoint."
::= { atmAcctngDataObjects 2 }
STATUS current
DESCRIPTION
"An indication of whether the connection is point-to-point
or point-to-multipoint."
::= { atmAcctngDataObjects 2 }
atmAcctngIfName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A textual name for the interface on which the data for the
connection was collected. If the local SNMP agent supports
the object ifName, the value of this object must be
identical to that of ifName in the conceptual row of the
ifTable corresponding to this interface."
::= { atmAcctngDataObjects 3 }
atmAcctngIfName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A textual name for the interface on which the data for the
connection was collected. If the local SNMP agent supports
the object ifName, the value of this object must be
identical to that of ifName in the conceptual row of the
ifTable corresponding to this interface."
::= { atmAcctngDataObjects 3 }
atmAcctngIfAlias OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The 'alias' name for the interface as specified by a
network manager, e.g., via a management set operation to
modify the relevant instance of the ifAlias object. Note
that in contrast to ifIndex, ifAlias provides a non-volatile
'handle' for the interface, the value of which is retained
across agent reboots."
::= { atmAcctngDataObjects 4 }
atmAcctngIfAlias OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The 'alias' name for the interface as specified by a
network manager, e.g., via a management set operation to
modify the relevant instance of the ifAlias object. Note
that in contrast to ifIndex, ifAlias provides a non-volatile
'handle' for the interface, the value of which is retained
across agent reboots."
::= { atmAcctngDataObjects 4 }
atmAcctngVpi OBJECT-TYPE
SYNTAX INTEGER (0..4095)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VPI used for the connection."
::= { atmAcctngDataObjects 5 }
atmAcctngVpi OBJECT-TYPE
SYNTAX INTEGER (0..4095)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VPI used for the connection."
::= { atmAcctngDataObjects 5 }
atmAcctngVci OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VCI used for the connection."
::= { atmAcctngDataObjects 6 }
atmAcctngVci OBJECT-TYPE
SYNTAX INTEGER (0..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The VCI used for the connection."
::= { atmAcctngDataObjects 6 }
atmAcctngCallingParty OBJECT-TYPE
ATMACTNGCallingParty对象类型
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's calling party. If unknown (e.g., for a
PVC), then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 7 }
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's calling party. If unknown (e.g., for a
PVC), then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 7 }
atmAcctngCalledParty OBJECT-TYPE
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's called party. If unknown (e.g., for a
PVC), then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 8 }
atmAcctngCalledParty OBJECT-TYPE
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's called party. If unknown (e.g., for a
PVC), then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 8 }
atmAcctngCallReference OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..3))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's call reference value (e.g., from Q.2931).
If unknown (e.g., for a PVC), then the value of this object
is the zero-length string."
::= { atmAcctngDataObjects 9 }
atmAcctngCallReference OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..3))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's call reference value (e.g., from Q.2931).
If unknown (e.g., for a PVC), then the value of this object
is the zero-length string."
::= { atmAcctngDataObjects 9 }
atmAcctngStartTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The time when the connection was established."
::= { atmAcctngDataObjects 10 }
atmAcctngStartTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The time when the connection was established."
::= { atmAcctngDataObjects 10 }
atmAcctngCollectionTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The time at which the data in this record was collected."
::= { atmAcctngDataObjects 11 }
atmAcctngCollectionTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The time at which the data in this record was collected."
::= { atmAcctngDataObjects 11 }
atmAcctngCollectMode OBJECT-TYPE SYNTAX INTEGER { onRelease(1), periodically(2),
ATMACTNGCollectMode对象类型语法整数{onRelease（1），周期性（2），
onCommand(3) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The reason why this connection data was collected."
::= { atmAcctngDataObjects 12 }
onCommand(3) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The reason why this connection data was collected."
::= { atmAcctngDataObjects 12 }
atmAcctngReleaseCause OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"If the connection data was collected because of the release
of an SVC, then this is the cause code in the Release
message for the connection; otherwise, this object has the
value zero."
::= { atmAcctngDataObjects 13 }
atmAcctngReleaseCause OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"If the connection data was collected because of the release
of an SVC, then this is the cause code in the Release
message for the connection; otherwise, this object has the
value zero."
::= { atmAcctngDataObjects 13 }
atmAcctngServiceCategory OBJECT-TYPE
SYNTAX INTEGER { other(1), cbr(2), vbrRt(3), vbrNrt(4),
abr(5), ubr(6), unknown(7) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's service category."
::= { atmAcctngDataObjects 14 }
atmAcctngServiceCategory OBJECT-TYPE
SYNTAX INTEGER { other(1), cbr(2), vbrRt(3), vbrNrt(4),
abr(5), ubr(6), unknown(7) }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's service category."
::= { atmAcctngDataObjects 14 }
atmAcctngTransmittedCells OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The number of cells, including OAM cells, transmitted by
this switch on this connection."
::= { atmAcctngDataObjects 15 }
atmAcctngTransmittedCells OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The number of cells, including OAM cells, transmitted by
this switch on this connection."
::= { atmAcctngDataObjects 15 }
atmAcctngTransmittedClp0Cells OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The number of cells with CLP=0, including OAM cells,
transmitted by this switch on this connection."
::= { atmAcctngDataObjects 16 }
atmAcctngTransmittedClp0Cells OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The number of cells with CLP=0, including OAM cells,
transmitted by this switch on this connection."
::= { atmAcctngDataObjects 16 }
atmAcctngReceivedCells OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS not-accessible
ATMACTNGReceivedCells对象类型语法计数器64 MAX-ACCESS不可访问
STATUS current
DESCRIPTION
"The number of cells, including OAM cells, received by this
switch on this connection."
::= { atmAcctngDataObjects 17 }
STATUS current
DESCRIPTION
"The number of cells, including OAM cells, received by this
switch on this connection."
::= { atmAcctngDataObjects 17 }
atmAcctngReceivedClp0Cells OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The number of cells with CLP=0, including OAM cells,
received by this switch on this connection."
::= { atmAcctngDataObjects 18 }
atmAcctngReceivedClp0Cells OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The number of cells with CLP=0, including OAM cells,
received by this switch on this connection."
::= { atmAcctngDataObjects 18 }
atmAcctngTransmitTrafficDescriptorType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The traffic descriptor type (as defined in RFC 1695 and its
successors) in the direction in which the switch transmits
cells on the connection."
REFERENCE
"See atmTrafficDescriptorTypes in ATM-MIB.my in RFC 1695 and
its successors."
::= { atmAcctngDataObjects 19 }
atmAcctngTransmitTrafficDescriptorType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The traffic descriptor type (as defined in RFC 1695 and its
successors) in the direction in which the switch transmits
cells on the connection."
REFERENCE
"See atmTrafficDescriptorTypes in ATM-MIB.my in RFC 1695 and
its successors."
::= { atmAcctngDataObjects 19 }
atmAcctngTransmitTrafficDescriptorParam1 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The first traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 20 }
atmAcctngTransmitTrafficDescriptorParam1 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The first traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 20 }
atmAcctngTransmitTrafficDescriptorParam2 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The second traffic descriptor parameter in the direction in which this switch transmits cells on this connection. Interpretation of this parameter is dependent on the value of atmAcctngTransmitTrafficDescriptorType."
ATMACTNGTransmitTrafficDescriptorParam2对象类型语法整数（0..2147483647）MAX-ACCESS不可访问状态当前说明“此交换机在此连接上传输小区的方向上的第二个流量描述符参数。此参数的解释取决于ATMACTNGTransmitTrafficDescriptorType的值。”
::= { atmAcctngDataObjects 21 }
::= { atmAcctngDataObjects 21 }
atmAcctngTransmitTrafficDescriptorParam3 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The third traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 22 }
atmAcctngTransmitTrafficDescriptorParam3 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The third traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 22 }
atmAcctngTransmitTrafficDescriptorParam4 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The fourth traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 23 }
atmAcctngTransmitTrafficDescriptorParam4 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The fourth traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 23 }
atmAcctngTransmitTrafficDescriptorParam5 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The fifth traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 24 }
atmAcctngTransmitTrafficDescriptorParam5 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The fifth traffic descriptor parameter in the direction in
which this switch transmits cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngTransmitTrafficDescriptorType."
::= { atmAcctngDataObjects 24 }
atmAcctngReceiveTrafficDescriptorType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The traffic descriptor type (as defined in RFC 1695 and its
successors) in the direction in which this switch receives
cells on this connection."
REFERENCE
"See atmTrafficDescriptorTypes in ATM-MIB.my in RFC 1695 and
its successors."
::= { atmAcctngDataObjects 25 }
atmAcctngReceiveTrafficDescriptorType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The traffic descriptor type (as defined in RFC 1695 and its
successors) in the direction in which this switch receives
cells on this connection."
REFERENCE
"See atmTrafficDescriptorTypes in ATM-MIB.my in RFC 1695 and
its successors."
::= { atmAcctngDataObjects 25 }
atmAcctngReceiveTrafficDescriptorParam1 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The first traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 26 }
atmAcctngReceiveTrafficDescriptorParam1 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The first traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 26 }
atmAcctngReceiveTrafficDescriptorParam2 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The second traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 27 }
atmAcctngReceiveTrafficDescriptorParam2 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The second traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 27 }
atmAcctngReceiveTrafficDescriptorParam3 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The third traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 28 }
atmAcctngReceiveTrafficDescriptorParam3 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The third traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 28 }
atmAcctngReceiveTrafficDescriptorParam4 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The fourth traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 29 }
atmAcctngReceiveTrafficDescriptorParam4 OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The fourth traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 29 }
atmAcctngReceiveTrafficDescriptorParam5 OBJECT-TYPE SYNTAX INTEGER (0..2147483647) MAX-ACCESS not-accessible STATUS current
ATMACTNGReceiveTrafficDescriptor参数5对象类型语法整数（0..2147483647）最大访问不可访问状态当前
DESCRIPTION
"The fifth traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 30 }
DESCRIPTION
"The fifth traffic descriptor parameter in the direction in
which this switch receives cells on this connection.
Interpretation of this parameter is dependent on the value
of atmAcctngReceiveTrafficDescriptorType."
::= { atmAcctngDataObjects 30 }
atmAcctngCallingPartySubAddress OBJECT-TYPE
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's calling party sub-address. If the
connection has no calling party sub-address, or it's value
is unknown, then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 31 }
atmAcctngCallingPartySubAddress OBJECT-TYPE
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's calling party sub-address. If the
connection has no calling party sub-address, or it's value
is unknown, then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 31 }
atmAcctngCalledPartySubAddress OBJECT-TYPE
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's called party sub-address. If the
connection has no called party sub-address, or it's value is
unknown, then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 32 }
atmAcctngCalledPartySubAddress OBJECT-TYPE
SYNTAX AtmAddr
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The connection's called party sub-address. If the
connection has no called party sub-address, or it's value is
unknown, then the value of this object is the zero-length
string."
::= { atmAcctngDataObjects 32 }
atmAcctngRecordCrc16 OBJECT-TYPE SYNTAX OCTET STRING (SIZE(2)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The value of the CRC-16 checksum (as defined by ISO 3309 (HDLC) and/or ITU X.25) calculated over the accounting record containing this object.
ATMACTNGRecordCRC16对象类型语法八位字节字符串（大小（2））MAX-ACCESS不可访问状态当前描述“在包含此对象的记帐记录上计算的CRC-16校验和（由ISO 3309（HDLC）和/或ITU X.25定义）的值。
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum."
::= { atmAcctngDataObjects 33 }
While the mechanism for calculating/encoding the checksum
value is specific to the method of encoding the accounting
record, an accounting record containing this object is
typically generated by initializing the value of this object
to the all-zeros string ('0000'H), with the location of
these zeros being saved. After generating the record, the
checksum is calculated over the whole connection record and
then the all-zeros value is overwritten (at the saved
location) by the calculated value of the checksum."
::= { atmAcctngDataObjects 33 }
END
终止
The comments of the IETF's AToM MIB Working Group are acknowledged.
IETF的AToM MIB工作组的评论得到了认可。
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2271, January 1998.
[1] Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2271，1998年1月。
[2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[2] Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[3] Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[4] Rose，M.“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[5] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息结构”，RFC 1902，1996年1月。
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[6] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的文本约定”，RFC 1903，1996年1月。
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[7] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的一致性声明”，RFC 1904，1996年1月。
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[8] Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[10] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2272, January 1998.
[11] Case，J.，Harrington D.，Presuhn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 22721998年1月。
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2274, January 1998.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 22741998年1月。
[13] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[13] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2273, January 1998.
[14] Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC 22731998年1月。
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2275, January 1998.
[15] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 22751998年1月。
[16] McCloghrie, K., Heinanen, J., Greene, W. and A. Prasad, "Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks", RFC 2513, February 1999.
[16] McCloghrie，K.，Heinanen，J.，Greene，W.和A.Prasad，“用于控制面向连接网络会计信息收集和存储的托管对象”，RFC 2513，1999年2月。
[17] Noto, M., Spiegel, E. and K. Tesink, "Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999.
[17] Noto，M.，Spiegel，E.和K.Tesink，“ATM管理的文本约定和对象标识的定义”，RFC 2514，1999年2月。
This MIB module defines data items for potential use as accounting information. Each of these data items is only accessible through a collected accounting file. After being collected, the accounting data should be protected against modification or unauthorized deletion.
此MIB模块定义可能用作会计信息的数据项。这些数据项中的每一项都只能通过收集的会计文件进行访问。会计数据收集后，应保护其不被修改或未经授权删除。
Prior to publication of this memo as an RFC, IANA is requested to make a suitable OBJECT IDENTIFIER assignment.
在将本备忘录作为RFC发布之前，IANA需要进行适当的对象标识符分配。
Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive, San Jose CA 95134
基思·麦克洛赫里思科系统公司，地址：加利福尼亚州圣何塞市西塔斯曼大道170号，邮编：95134
Phone: +1 408 526 5260
EMail: kzm@cisco.com
Phone: +1 408 526 5260
EMail: kzm@cisco.com
Juha Heinanen Telia Finland, Inc. Myyrmaentie 2 01600 VANTAA Finland
Juha Heinanen Telia Finland，Inc.Myyrmaentie 2 01600 VANTAA Finland
Phone +358 303 944 808 EMail: jh@telia.fi
电话+358 303 944 808电子邮件：jh@telia.fi
Wedge Greene MCI Telecommunications Corporation 901 International Parkway Richardson, Texas 75081
德克萨斯州理查森国际大道901号韦奇格林MCI电信公司75081
Phone: 214-498-1232 or 972-729-1232 EMail: wedge.greene@mci.com
电话：214-498-1232或972-729-1232电子邮件：wedge。greene@mci.com
Anil Prasad Cisco Systems, Inc. 170 West Tasman Drive, San Jose CA 95134
安尼尔·普拉萨德思科系统公司，地址：加利福尼亚州圣何塞市西塔斯曼大道170号，邮编：95134
Phone: +1 408 525-7209
EMail: aprasad@cisco.com
Phone: +1 408 525-7209
EMail: aprasad@cisco.com
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。