Network Working Group K. McCloghrie
Request for Comments: 2513 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: 2513 Cisco Systems, Inc.
Category: Standards Track J. Heinanen
Telia Finland, Inc.
W. Greene
MCI Telecommunications Corp.
A. Prasad
Cisco Systems, Inc.
February 1999
Managed Objects for Controlling the Collection and Storage of Accounting Information for Connection-Oriented Networks
用于控制面向连接网络的记帐信息的收集和存储的托管对象
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 .................................................... 2
2 The SNMP Network Management Framework ........................... 2
3 Overview ........................................................ 3
3.1 Operational Model ............................................. 3
3.2 Selection of Accounting Data .................................. 5
3.3 Format of Collection File ..................................... 6
4 Definitions ..................................................... 9
5 Acknowledgements ................................................25
6 References ......................................................25
7 Security Considerations .........................................27
8 IANA Considerations .............................................27
9 Authors' Addresses ..............................................28
10 Full Copyright Statement .......................................29
1 Introduction .................................................... 2
2 The SNMP Network Management Framework ........................... 2
3 Overview ........................................................ 3
3.1 Operational Model ............................................. 3
3.2 Selection of Accounting Data .................................. 5
3.3 Format of Collection File ..................................... 6
4 Definitions ..................................................... 9
5 Acknowledgements ................................................25
6 References ......................................................25
7 Security Considerations .........................................27
8 IANA Considerations .............................................27
9 Authors' Addresses ..............................................28
10 Full Copyright Statement .......................................29
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for controlling the collection and storage of accounting information for connection-oriented networks such as ATM. The accounting data is collected into files for later retrieval via a file transfer protocol. For information on data which can be collected for ATM networks, see [19].
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于控制面向连接的网络（如ATM）的记帐信息的收集和存储的托管对象。会计数据被收集到文件中，以便以后通过文件传输协议检索。有关可为ATM网络收集的数据的信息，请参见[19]。
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 some connection-oriented network environments, there is a need for the network administrator to be able to collect accounting data on the usage of bandwidth/resources by connections (e.g., ATM connections) within the network. Data collection should be available for switched virtual connections (SVCs and SVPs), and permanent virtual connections (PVCs and PVPs), including soft-permanent virtual connections (SPVCCs and SPVPCs). This need exists for ATM networks, and may well exist for other connection-oriented networks, such as Frame Relay.
在某些面向连接的网络环境中，网络管理员需要能够通过网络内的连接（例如ATM连接）收集有关带宽/资源使用情况的记帐数据。数据采集应可用于交换虚拟连接（SVC和SVP）和永久虚拟连接（PVC和PVP），包括软永久虚拟连接（SPVCC和SPVPC）。这种需求存在于ATM网络中，也可能存在于其他面向连接的网络中，如帧中继。
The potential quantity of such accounting information is such that it is not, in general, feasible to retrieve the information via SNMP. A better method is to store the collected accounting information in a file which can be subsequently retrieved via a file transfer protocol.
此类会计信息的潜在数量通常无法通过SNMP检索信息。更好的方法是将收集的会计信息存储在一个文件中，该文件随后可以通过文件传输协议进行检索。
It is, however, appropriate to provide management control of the selection and collection of such accounting data via SNMP. This memo describes a MIB module which provides such control in a manner independent of the type of network. One or more other documents provide definitions of particular items of accounting data which can be selected; for example, a particular set of data items which can be collected for ATM networks is specified in [19].
但是，通过SNMP提供对选择和收集此类会计数据的管理控制是合适的。本备忘录描述了以独立于网络类型的方式提供此类控制的MIB模块。一个或多个其他文件提供可选择的特定会计数据项的定义；例如，在[19]中规定了可以为ATM网络收集的一组特定数据项。
The requirement is for switches (e.g., ATM switches) to collect data concerning the connections which are routed across some subset of their interfaces (e.g., ATM UNI and/or NNI interfaces). The collected data is stored into one or more "files". The use of multiple files allows, for example, the data collected for PVCs to be different from that collected for SVCs.
要求交换机（如ATM交换机）收集有关连接的数据，这些连接通过其接口的某些子集（如ATM UNI和/或NNI接口）路由。收集的数据存储在一个或多个“文件”中。例如，使用多个文件可以使为PVC收集的数据与为SVC收集的数据不同。
In order to retrieve the data currently being stored in a file, the administrator instructs the switch to terminate the collection of data into that file, and start collecting data into a new file.
为了检索当前存储在文件中的数据，管理员指示交换机终止向该文件中收集数据，并开始向新文件中收集数据。
After this operation, the data in the old file is available for retrieval via file transfer.
执行此操作后，旧文件中的数据可通过文件传输进行检索。
A collection file is defined to have a maximum size. When the size of the file currently being collected exceeds a threshold percentage of that maximum size, an SNMP notification (e.g., a trap) can be optionally generated. An SNMP notification might also be generated if the file reaches its maximum size.
集合文件定义为具有最大大小。当当前正在收集的文件的大小超过该最大大小的阈值百分比时，可以选择生成SNMP通知（例如陷阱）。如果文件达到最大大小，也可能会生成SNMP通知。
The accounting data collected for each connection consists of a set of objects and their values. The set of objects and their values are collected on one or more of the following occasions:
为每个连接收集的记帐数据由一组对象及其值组成。在以下一种或多种情况下收集对象集及其值：
(1) on the release (termination) of a connection optionally including failed connection attempts;
(1) 在连接释放（终止）时（可选地包括失败的连接尝试）；
(2) for each active connection (having a particular minimum age) on a periodic basis;
(2) 定期针对每个活动连接（具有特定的最小使用年限）；
(3) for each active connection (having a particular minimum age) when so commanded by a management application.
(3) 当管理应用程序如此命令时，每个活动连接（具有特定的最小使用年限）。
While collecting data to be stored in a particular file, the same set of objects is collected for each connection on each occasion. Having the same set of objects stored on each occasion allows the optimization of storing only the values of those objects. This results in a significantly smaller file size, since it allows the names of the objects to be stored once and only once at the beginning of the file, rather than having to store every value as a (name, value) pair.
在收集要存储在特定文件中的数据时，每次都会为每个连接收集相同的对象集。在每次存储相同的对象集时，允许优化仅存储这些对象的值。这将导致文件大小大大减小，因为它允许对象的名称在文件开头存储一次且仅存储一次，而不必将每个值存储为（名称、值）对。
Two modes of agent behaviour are allowed on the event of a file reaching its maximum size:
当文件达到最大大小时，允许两种代理行为模式：
(1) management application in control:
(1) 控制中的管理应用：
The agent does not automatically swap to a new file; rather, it discards newly collected data until the management application subsequently instructs it to swap to a new file. Before swapping to a new file, the name of the file into which data is currently being collected is an implementation issue of no concern to an NM application; after swapping to a new file, the name of the file available for retrieval is as specified by the controlling MIB objects. This behaviour allows the application to know exactly how many files need to be retrieved and their names without having to perform any type of file directory operation, but also results in the possibility that data will be discarded if the application does not instruct the agent to swap
代理不会自动切换到新文件；相反，它会丢弃新收集的数据，直到管理应用程序随后指示它交换到新文件。在切换到新文件之前，当前正在收集数据的文件的名称是NM应用程序不关心的实现问题；切换到新文件后，可供检索的文件名由控制MIB对象指定。此行为允许应用程序准确地知道需要检索的文件数量及其名称，而无需执行任何类型的文件目录操作，但如果应用程序不指示代理交换，也可能导致数据被丢弃
within the required time frame.
在规定的时间范围内。
(2) agent automatically swaps to new file:
(2) 代理自动交换到新文件：
The agent terminates collection into the current (full) file, and begins collecting data into a new version of the same base file name. This behaviour aims to avoid loss of data by assuming that additional storage space is actually available to create a new version of the file. To support this behaviour, files are named using suffixes, such that when the current version of the file becomes full, the agent begins collecting data into a file with the same base file-name but with an incremented (or otherwise modified) suffix. This requires the application to perform file directory operations prior to retrieving completed files in order to know how many and which suffixes have been used.
代理终止对当前（完整）文件的收集，并开始将数据收集到相同基本文件名的新版本中。此行为的目的是通过假设实际有额外的存储空间可用于创建文件的新版本来避免数据丢失。为了支持这种行为，文件使用后缀命名，这样当文件的当前版本变满时，代理开始将数据收集到具有相同基本文件名但后缀递增（或以其他方式修改）的文件中。这要求应用程序在检索完成的文件之前执行文件目录操作，以便知道使用了多少后缀以及哪些后缀。
With either behaviour, any completed file must be an integral number of connection records (see below). When a file reaches its maximum size, collection into that file is terminated either immediately before or immediately after storing the whole of the current connection record into the file. The former causes the file to be just less than its maximum size, and the latter causes the file to be just greater than its maximum size.
无论是哪种行为，任何完整的文件都必须是连接记录的整数（见下文）。当文件达到最大大小时，在将整个当前连接记录存储到该文件之前或之后立即终止对该文件的收集。前者导致文件刚好小于其最大大小，后者导致文件刚好大于其最大大小。
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:
将要收集的会计数据项指定为一组对象。管理员可以通过指定一个或多个（子树、列表）元组来选择包含在此类集合中的对象，其中要收集的对象集合是每个元组指定的子集的并集：
'subtree' specifies an 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作为单个附加子标识符附加到子树而命名的对象。
The rationale for defining each subset as a (subtree,list) tuple is that one and only one OBJECT IDENTIFIER and one OCTET STRING is needed to define the subset of objects. This simplifies the MIB mechanisms needed for selection: an NM application needs to create only one conceptual row in a MIB table for each subset (rather than needing to create a conceptual row in a table for each and every
将每个子集定义为（子树，列表）元组的基本原理是，定义对象子集只需要一个且只有一个对象标识符和一个八进制字符串。这简化了选择所需的MIB机制：NM应用程序只需要在MIB表中为每个子集创建一个概念行（而不需要在表中为每个子集创建一个概念行）
object in the set).
对象（在集合中）。
The number of tuples supported by a particular switch is an implementation choice. One possibility is to support two (subtree, list) tuples so that one such tuple can specify a standard 'subtree' (e.g., the atmAcctngDataObjects subtree defined in [19]), and the second tuple can specify an enterprise-specific 'subtree'; this would allow the selected set of objects to be the union of a set of standard objects and a set of enterprise-defined objects.
特定交换机支持的元组数是一种实现选择。一种可能性是支持两个（子树，列表）元组，以便其中一个元组可以指定标准的“子树”（例如，在[19]中定义的ATMACTNGDataObjects子树），第二个元组可以指定特定于企业的“子树”；这将允许所选对象集成为一组标准对象和一组企业定义对象的并集。
A collection file generated by this process contains the values of MIB objects defined using the SMIv2. The standard way to encode the values of SNMP MIB objects in a device-independent manner is through the use of ASN.1's Basic Encoding Rules (BER) [18]. Thus, the standard format of an accounting file is defined here using the same adapted subset of ASN.1 [17] as the SMIv2.
此进程生成的集合文件包含使用SMIv2定义的MIB对象的值。以独立于设备的方式对SNMP MIB对象的值进行编码的标准方法是使用ASN.1的基本编码规则（BER）[18]。因此，这里使用与SMIv2相同的ASN.1[17]的调整子集定义了会计文件的标准格式。
The file consists of a set of header information followed by a sequence of zero or more collection records. The header information identifies (via sysName [16]) the switch which collected the data, the date and time at which the collection in to this file started, and the sequence of one or more (subtree, list) tuples identifying the objects whose values are contained in each connection record. The header information also includes a textual description of the data contained in the file.
该文件由一组标题信息和一系列零或多个收集记录组成。标题信息标识（通过sysName[16]）收集数据的开关、开始收集此文件的日期和时间，以及标识每个连接记录中包含其值的对象的一个或多个（子树、列表）元组的序列。标题信息还包括文件中包含的数据的文本描述。
Each connection record contains a sequence of values for each identified tuple, in the same order as the tuples are identified in the header information. For each tuple, the sequence of values are in ascending order of the sub-identifier which identifies them within the subtree.
每个连接记录包含每个已标识元组的一系列值，其顺序与在头信息中标识元组的顺序相同。对于每个元组，值序列按子标识符的升序排列，子标识符在子树中标识它们。
Formally, an accounting file is an ASN.1 value with the following syntax:
在形式上，记帐文件是ASN.1值，具有以下语法：
File ::=
[1]
IMPLICIT SEQUENCE {
-- header information
sysName -- name of the switch
DisplayString,
File ::=
[1]
IMPLICIT SEQUENCE {
-- header information
sysName -- name of the switch
DisplayString,
description -- textual description of the collection DisplayString,
description--集合DisplayString的文本描述，
startTime -- start time of the collection
startTime--集合的开始时间
DateAndTime,
日期和时间，
SEQUENCE OF { -- sequence of (subtree, list) tuples
SEQUENCE {
subtree
OBJECT IDENTIFIER,
list
OCTET STRING
}
}
-- sequence of connection records
SEQUENCE OF {
-- each record containing a sequence
SEQUENCE OF { -- per identified tuple
SEQUENCE OF { -- sequence of (subtree, list) tuples
SEQUENCE {
subtree
OBJECT IDENTIFIER,
list
OCTET STRING
}
}
-- sequence of connection records
SEQUENCE OF {
-- each record containing a sequence
SEQUENCE OF { -- per identified tuple
SEQUENCE OF { -- each per-tuple sequence containing
value -- a sequence of object values
ObjectSyntax
}
}
}
}
SEQUENCE OF { -- each per-tuple sequence containing
value -- a sequence of object values
ObjectSyntax
}
}
}
}
where:
哪里：
(1) the value of the sysName component is that of the sysName object in the System group [16].
(1) sysName组件的值是系统组[16]中sysName对象的值。
(2) each (subtree, list) specifies the set of objects contained in that tuple's sequence within each and every connection record.
(2) 每个（子树，列表）指定每个连接记录中该元组序列中包含的对象集。
(3) the tuples' sequences within each connection record occur in the same order as the (subtree, list) tuples occur in the header information.
(3) 每个连接记录中的元组序列的出现顺序与头信息中的（子树，列表）元组的出现顺序相同。
(4) the object values within each connection record occur in the same order as they are represented by the bits in the corresponding list value.
(4) 每个连接记录中的对象值的出现顺序与它们由相应列表值中的位表示的顺序相同。
(5) ObjectSyntax is defined by the SMIv2 [5].
(5) ObjectSyntax由SMIv2定义[5]。
(6) One particular category of object values deserves special attention: an object defined to hold the checksum value of an accounting record (e.g., atmAcctngRecordCrc16, defined in [19]). An object in this category will generally have a SYNTAX of a fixed-length OCTET STRING, and have its value initialized to the string of all zeros when composing the accounting record containing it, with the location of these zeros being saved.
(6) 有一类特定的对象值值得特别注意：一个定义为保存会计记录校验和值的对象（例如，ATMACTNGRecordCRC16，定义见[19]）。此类别中的对象通常具有固定长度的八进制字符串的语法，在编写包含该对象的会计记录时，将其值初始化为全零字符串，并保存这些零的位置。
Once the record is generated, the checksum is calculated over the whole connection record (including the starting SEQUENCE OF and the trailing end-of-contents octets, if used), and then the zeros are overwritten (at the saved location) by the calculated value of the checksum.
生成记录后，将在整个连接记录上计算校验和（包括内容八位字节的起始序列和结尾，如果使用），然后通过校验和的计算值覆盖零（在保存的位置）。
The encoding of the above syntax using the Basic Encoding Rules is the same as defined by the SNMPv2 [10], with the following exception:
使用基本编码规则对上述语法进行的编码与SNMPv2[10]定义的相同，但以下情况除外：
- when encoding the length field for a structured type, i.e., a SEQUENCE or SEQUENCE OF, the indefinite form encoding is permitted.
- 当编码结构化类型的长度字段时，即，一个或多个的序列，允许不定格式编码。
For example, the file containing the data:
例如，包含以下数据的文件：
[1] IMPLICIT SEQUENCE a1 80 OCTET STRING 04 09 73 77 69 74 63 68 2d 31 32 OCTET STRING 04 0a 41 63 63 6f 75 6e 74 69 6e 67 OCTET STRING 04 08 07 cc 07 14 10 05 00 00 SEQUENCE OF 30 0e SEQUENCE 30 0c OBJECT IDENTIFIER 06 07 2b 06 01 03 7f 01 01 OCTET STRING 04 01 c0 SEQUENCE OF 30 80 SEQUENCE OF 30 08 SEQUENCE OF 30 06 INTEGER 02 01 00 INTEGER 02 01 21 SEQUENCE OF 30 08 SEQUENCE OF 30 06 INTEGER 02 01 00 INTEGER 02 01 22 end-of-contents 00 00 end-of-contents 00 00
[1] 隐式序列a1 80八位字符串04 09 73 77 69 74 63 68 2d 31 32八位字符串04 0a 41 63 6f 75 6e 74 69 6e 67八位字符串04 08 07 cc 07 14 10 05 00 30 0e序列30 0c对象标识符06 07 2b 06 01 01 03 7f 01 01八位字符串04 01 c0 30 80序列30 08 30 06整数02 01 00整数02 01 2130 08序列30 06整数02 01 00整数02 01 22内容结束00 00内容结束00 00
contains two connection records, each containing one tuple listing two (integer) data items in a (fictitious) subtree: 1.3.6.1.3.127.1.1. Its header indicates it's for "switch-12", with description "Accounting", and was collected at 16:05:00 on 20 July 1996.
包含两个连接记录，每个记录包含一个元组，列出（虚拟）子树中的两个（整数）数据项：1.3.6.1.3.127.1.1。其标题表示其用于“开关-12”，并带有“会计”说明，于1996年7月20日16:05:00收集。
As well as the standard format defined above, the MIB allows other enterprise-specific formats to be used.
除了上面定义的标准格式外，MIB还允许使用其他特定于企业的格式。
ACCOUNTING-CONTROL-MIB DEFINITIONS ::= BEGIN
ACCOUNTING-CONTROL-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, TestAndIncr, DisplayString, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF ifIndex FROM IF-MIB;
从SNMPv2 SMI文本约定导入模块标识、对象类型、通知类型、mib-2、整数32，从IF-mib导入SNMPv2 TC模块符合性、对象组、通知组，从SNMPv2 CONF ifIndex导入行状态、TestAndIncr、DisplayString、TruthValue；
accountingControlMIB MODULE-IDENTITY
LAST-UPDATED "9809281000Z"
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"
DESCRIPTION
"The MIB module for managing the collection and storage of
accounting information for connections in a connection-
oriented network such as ATM."
::= { mib-2 60 }
accountingControlMIB MODULE-IDENTITY
LAST-UPDATED "9809281000Z"
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"
DESCRIPTION
"The MIB module for managing the collection and storage of
accounting information for connections in a connection-
oriented network such as ATM."
::= { mib-2 60 }
acctngMIBObjects OBJECT IDENTIFIER ::= { accountingControlMIB 1 }
acctngMIBObjects OBJECT IDENTIFIER ::= { accountingControlMIB 1 }
acctngSelectionControl OBJECT IDENTIFIER ::= { acctngMIBObjects 1 }
acctngFileControl OBJECT IDENTIFIER ::= { acctngMIBObjects 2 }
acctngInterfaceControl OBJECT IDENTIFIER ::= { acctngMIBObjects 3 }
acctngTrapControl OBJECT IDENTIFIER ::= { acctngMIBObjects 4 }
acctngSelectionControl OBJECT IDENTIFIER ::= { acctngMIBObjects 1 }
acctngFileControl OBJECT IDENTIFIER ::= { acctngMIBObjects 2 }
acctngInterfaceControl OBJECT IDENTIFIER ::= { acctngMIBObjects 3 }
acctngTrapControl OBJECT IDENTIFIER ::= { acctngMIBObjects 4 }
-- Textual Conventions
--文本约定
DataCollectionSubtree ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The subtree component of a (subtree, list) tuple. Such a
(subtree, list) tuple defines a set of objects and their
values to be collected as accounting data for a connection.
The subtree specifies a single OBJECT IDENTIFIER value such
that each object in the set is named by the subtree value
DataCollectionSubtree ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The subtree component of a (subtree, list) tuple. Such a
(subtree, list) tuple defines a set of objects and their
values to be collected as accounting data for a connection.
The subtree specifies a single OBJECT IDENTIFIER value such
that each object in the set is named by the subtree value
appended with a single additional sub-identifier." SYNTAX OBJECT IDENTIFIER
附加了一个附加的子标识符。“语法对象标识符
DataCollectionList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The list component of a (subtree, list) tuple. Such a
(subtree, list) tuple defines a set of objects and their
values to be collected as accounting data for a connection.
The subtree specifies a single OBJECT IDENTIFIER value such
that each object in the set is named by the subtree value
appended with a single additional sub-identifier. The list
specifies a set of data items, where the presence of an item
in the list indicates that the item is (to be) present in
the data collected for a connection; the absence of an item
from the list indicates that the item is not (to be) present
in the data collected for a connection. Each data item is
represented by an integer which when appended (as as
additional sub-identifier) to the OBJECT IDENTIFIER value of
the subtree identified by the tuple, is the name of an
object defining that data item (its description and its
syntax).
DataCollectionList ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The list component of a (subtree, list) tuple. Such a
(subtree, list) tuple defines a set of objects and their
values to be collected as accounting data for a connection.
The subtree specifies a single OBJECT IDENTIFIER value such
that each object in the set is named by the subtree value
appended with a single additional sub-identifier. The list
specifies a set of data items, where the presence of an item
in the list indicates that the item is (to be) present in
the data collected for a connection; the absence of an item
from the list indicates that the item is not (to be) present
in the data collected for a connection. Each data item is
represented by an integer which when appended (as as
additional sub-identifier) to the OBJECT IDENTIFIER value of
the subtree identified by the tuple, is the name of an
object defining that data item (its description and its
syntax).
The list is specified as an OCTET STRING in which each data item is represented by a single bit, where data items 1 through 8 are represented by the bits in the first octet, data items 9 through 16 by the bits in the second octet, etc. In each octet, the lowest numbered data item is represented by the most significant bit, and the highest numbered data item by the least significant bit. A data item is present in the list when its bit is set, and absent when its bit is reset. If the length of an OCTET STRING value is too short to represent one or more data items defined in a subtree, then those data items are absent from the set identified by the tuple of that subtree and that OCTET STRING value." SYNTAX OCTET STRING (SIZE(0..8))
该列表被指定为八位字符串，其中每个数据项由单个位表示，其中数据项1至8由第一个八位中的位表示，数据项9至16由第二个八位中的位表示，等等。在每个八位中，编号最低的数据项由最高有效位表示，以及以最低有效位表示的编号最高的数据项。数据项在其位被设置时出现在列表中，在其位被重置时不存在。如果八进制字符串值的长度太短，无法表示子树中定义的一个或多个数据项，则这些数据项不在由该子树的元组和该八进制字符串值标识的集合中。“语法八进制字符串（大小（0..8））
FileIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An arbitrary integer value identifying a file into which
accounting data is being collected."
SYNTAX Integer32 (1..65535)
FileIndex ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An arbitrary integer value identifying a file into which
accounting data is being collected."
SYNTAX Integer32 (1..65535)
-- The Accounting Information Selection table
--会计信息选择表
acctngSelectionTable OBJECT-TYPE SYNTAX SEQUENCE OF AcctngSelectionEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of accounting information selection entries.
acctngSelectionTable AcctngSelectionEntry MAX-ACCESS的对象类型语法序列不可访问状态当前说明“会计信息选择项列表。
Note that additions, modifications and deletions of entries
in this table can occur at any time, but such changes only
take effect on the next occasion when collection begins into
a new file. Thus, between modification and the next 'swap',
the content of this table does not reflect the current
selection."
::= { acctngSelectionControl 1 }
Note that additions, modifications and deletions of entries
in this table can occur at any time, but such changes only
take effect on the next occasion when collection begins into
a new file. Thus, between modification and the next 'swap',
the content of this table does not reflect the current
selection."
::= { acctngSelectionControl 1 }
acctngSelectionEntry OBJECT-TYPE
SYNTAX AcctngSelectionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry identifying an (subtree, list) tuple used to
select a set of accounting information which is to be
collected."
INDEX { acctngSelectionIndex }
::= { acctngSelectionTable 1 }
acctngSelectionEntry OBJECT-TYPE
SYNTAX AcctngSelectionEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry identifying an (subtree, list) tuple used to
select a set of accounting information which is to be
collected."
INDEX { acctngSelectionIndex }
::= { acctngSelectionTable 1 }
AcctngSelectionEntry ::=
SEQUENCE {
acctngSelectionIndex Integer32,
acctngSelectionSubtree DataCollectionSubtree,
acctngSelectionList DataCollectionList,
acctngSelectionFile FileIndex,
acctngSelectionType BITS,
acctngSelectionRowStatus RowStatus
}
AcctngSelectionEntry ::=
SEQUENCE {
acctngSelectionIndex Integer32,
acctngSelectionSubtree DataCollectionSubtree,
acctngSelectionList DataCollectionList,
acctngSelectionFile FileIndex,
acctngSelectionType BITS,
acctngSelectionRowStatus RowStatus
}
acctngSelectionIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer value which uniquely identifies a
tuple stored in this table. This value is required to be
the permanent 'handle' for an entry in this table for as
long as that entry exists, including across restarts and
power outages."
::= { acctngSelectionEntry 1 }
acctngSelectionIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer value which uniquely identifies a
tuple stored in this table. This value is required to be
the permanent 'handle' for an entry in this table for as
long as that entry exists, including across restarts and
power outages."
::= { acctngSelectionEntry 1 }
acctngSelectionSubtree OBJECT-TYPE
SYNTAX DataCollectionSubtree
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The combination of acctngSelectionSubtree and
acctngSelectionList specifies one (subtree, list) tuple
which is to be collected."
::= { acctngSelectionEntry 2 }
acctngSelectionSubtree OBJECT-TYPE
SYNTAX DataCollectionSubtree
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The combination of acctngSelectionSubtree and
acctngSelectionList specifies one (subtree, list) tuple
which is to be collected."
::= { acctngSelectionEntry 2 }
acctngSelectionList OBJECT-TYPE
SYNTAX DataCollectionList
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The combination of acctngSelectionSubtree and
acctngSelectionList specifies one (subtree, list) tuple
which is to be collected."
::= { acctngSelectionEntry 3 }
acctngSelectionList OBJECT-TYPE
SYNTAX DataCollectionList
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The combination of acctngSelectionSubtree and
acctngSelectionList specifies one (subtree, list) tuple
which is to be collected."
::= { acctngSelectionEntry 3 }
acctngSelectionFile OBJECT-TYPE
SYNTAX FileIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of the file into which the accounting
information identified by this entry is to be stored. If
there is no conceptual row in the acctngFileTable for which
the value of acctngFileIndex has the same value as this
object, then the information selected by this entry is not
collected."
::= { acctngSelectionEntry 4 }
acctngSelectionFile OBJECT-TYPE
SYNTAX FileIndex
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of the file into which the accounting
information identified by this entry is to be stored. If
there is no conceptual row in the acctngFileTable for which
the value of acctngFileIndex has the same value as this
object, then the information selected by this entry is not
collected."
::= { acctngSelectionEntry 4 }
acctngSelectionType OBJECT-TYPE SYNTAX BITS { svcIncoming(0), svcOutgoing(1), svpIncoming(2), svpOutgoing(3), pvc(4), pvp(5), spvcOriginator(6), spvcTarget(7), spvpOriginator(8), spvpTarget(9) } MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the types of connections for which the
acctngSelectionType对象类型语法位{SVCONNECTION（0）、SVCONNECTION（1）、svpIncoming（2）、svpOutgoing（3）、pvc（4）、pvp（5）、spvcOriginator（6）、spvcTarget（7）、spvpOriginator（8）、spvpTarget（9）}MAX-ACCESS read create STATUS current DESCRIPTION”指示
information selected by this entry are to be collected."
DEFVAL { { svcIncoming, svcOutgoing,
svpIncoming, svpOutgoing } }
::= { acctngSelectionEntry 5 }
information selected by this entry are to be collected."
DEFVAL { { svcIncoming, svcOutgoing,
svpIncoming, svpOutgoing } }
::= { acctngSelectionEntry 5 }
acctngSelectionRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row. An agent may refuse to create new conceptual rows and/or modify existing conceptual rows, if such creation/modification would cause multiple rows to have the same values of acctngSelectionSubtree and acctngSelectionList.
acctngSelectionRowStatus对象类型语法RowStatus MAX-ACCESS读取创建状态当前描述“此概念行的状态。代理可能会拒绝创建新的概念行和/或修改现有概念行，如果此类创建/修改会导致多行具有相同的acctngSelectionSubtree和acctngSelectionList值。
A conceptual row can not have the status of 'active' until values have been assigned to the acctngSelectionSubtree, acctngSelectionList and acctngSelectionFile columnar objects within that row.
在将值分配给该行中的acctngSelectionSubtree、acctngSelectionList和acctngSelectionFile列对象之前，概念行的状态不能为“活动”。
An agent must not refuse to change the values of the
acctngSelectionSubtree, acctngSelectionList and
acctngSelectionFile columnar objects within a conceptual row
even while that row's status is 'active'. Similarly, an
agent must not refuse to destroy an existing conceptual row
while the file referenced by that row's instance of
acctngSelectionFile is in active use, i.e., while the
corresponding instance of acctngFileRowStatus has the value
'active'. However, such changes only take effect upon the
next occasion when collection begins into a new (version of
the) file."
::= { acctngSelectionEntry 6 }
An agent must not refuse to change the values of the
acctngSelectionSubtree, acctngSelectionList and
acctngSelectionFile columnar objects within a conceptual row
even while that row's status is 'active'. Similarly, an
agent must not refuse to destroy an existing conceptual row
while the file referenced by that row's instance of
acctngSelectionFile is in active use, i.e., while the
corresponding instance of acctngFileRowStatus has the value
'active'. However, such changes only take effect upon the
next occasion when collection begins into a new (version of
the) file."
::= { acctngSelectionEntry 6 }
-- The Accounting File table
--会计档案表
acctngFileTable OBJECT-TYPE
SYNTAX SEQUENCE OF AcctngFileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of files into which accounting information is to be
stored."
::= { acctngFileControl 1 }
acctngFileTable OBJECT-TYPE
SYNTAX SEQUENCE OF AcctngFileEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of files into which accounting information is to be
stored."
::= { acctngFileControl 1 }
acctngFileEntry OBJECT-TYPE SYNTAX AcctngFileEntry MAX-ACCESS not-accessible
acctngFileEntry对象类型语法acctngFileEntry MAX-ACCESS不可访问
STATUS current
DESCRIPTION
"An entry identifying a file into which accounting
information is to be collected."
INDEX { acctngFileIndex }
::= { acctngFileTable 1 }
STATUS current
DESCRIPTION
"An entry identifying a file into which accounting
information is to be collected."
INDEX { acctngFileIndex }
::= { acctngFileTable 1 }
AcctngFileEntry ::=
SEQUENCE {
acctngFileIndex FileIndex,
acctngFileName DisplayString,
acctngFileNameSuffix DisplayString,
acctngFileDescription DisplayString,
acctngFileCommand INTEGER,
acctngFileMaximumSize Integer32,
acctngFileCurrentSize Integer32,
acctngFileFormat INTEGER,
acctngFileCollectMode BITS,
acctngFileCollectFailedAttempts BITS,
acctngFileInterval Integer32,
acctngFileMinAge Integer32,
acctngFileRowStatus RowStatus
}
AcctngFileEntry ::=
SEQUENCE {
acctngFileIndex FileIndex,
acctngFileName DisplayString,
acctngFileNameSuffix DisplayString,
acctngFileDescription DisplayString,
acctngFileCommand INTEGER,
acctngFileMaximumSize Integer32,
acctngFileCurrentSize Integer32,
acctngFileFormat INTEGER,
acctngFileCollectMode BITS,
acctngFileCollectFailedAttempts BITS,
acctngFileInterval Integer32,
acctngFileMinAge Integer32,
acctngFileRowStatus RowStatus
}
acctngFileIndex OBJECT-TYPE
SYNTAX FileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value identifying a file into which accounting
data is to be stored. This value is required to be the
permanent 'handle' for an entry in this table for as long as
that entry exists, including across restarts and power
outages."
::= { acctngFileEntry 1 }
acctngFileIndex OBJECT-TYPE
SYNTAX FileIndex
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unique value identifying a file into which accounting
data is to be stored. This value is required to be the
permanent 'handle' for an entry in this table for as long as
that entry exists, including across restarts and power
outages."
::= { acctngFileEntry 1 }
acctngFileName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The name of the file into which accounting data is to be stored. If files are named using suffixes, then the name of the current file is the concatenation of acctngFileName and acctngFileNameSuffix.
acctngFileName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..32)) MAX-ACCESS read-create STATUS current DESCRIPTION "The name of the file into which accounting data is to be stored. If files are named using suffixes, then the name of the current file is the concatenation of acctngFileName and acctngFileNameSuffix.translate error, please retry
An agent will respond with an error (e.g., 'wrongValue') to a management set operation which attempts to modify the
代理将以错误（例如“错误值”）响应管理集操作，该操作试图修改
value of this object to the same value as already held by another instance of acctngFileName. An agent will also respond with an error (e.g., 'wrongValue') if the new value is invalid for use as a file name on the local file system (e.g., many file systems do not support white space embedded in file names).
此对象的值与acctngFileName的另一个实例已持有的值相同。如果新值不能用作本地文件系统上的文件名（例如，许多文件系统不支持文件名中嵌入空格），则代理也会响应错误（例如，“错误值”）。
The value of this object can not be modified while the
corresponding instance of acctngFileRowStatus is 'active'."
::= { acctngFileEntry 2 }
The value of this object can not be modified while the
corresponding instance of acctngFileRowStatus is 'active'."
::= { acctngFileEntry 2 }
acctngFileNameSuffix OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The suffix, if any, of the name of a file into which
accounting data is currently being stored. If suffixes are
not used, then the value of this object is the zero-length
string. Note that if a separator, such as a period, is used
in appending the suffix to the file name, then that
separator appears as the first character of this value."
::= { acctngFileEntry 3 }
acctngFileNameSuffix OBJECT-TYPE
SYNTAX DisplayString (SIZE(0..8))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The suffix, if any, of the name of a file into which
accounting data is currently being stored. If suffixes are
not used, then the value of this object is the zero-length
string. Note that if a separator, such as a period, is used
in appending the suffix to the file name, then that
separator appears as the first character of this value."
::= { acctngFileEntry 3 }
acctngFileDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The textual description of the accounting data which will
be stored (on the next occasion) when header information is
stored in the file. The value of this object may be
modified at any time."
DEFVAL { "" }
::= { acctngFileEntry 4 }
acctngFileDescription OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The textual description of the accounting data which will
be stored (on the next occasion) when header information is
stored in the file. The value of this object may be
modified at any time."
DEFVAL { "" }
::= { acctngFileEntry 4 }
acctngFileCommand OBJECT-TYPE
SYNTAX INTEGER {
-- the following two values are states:
-- they may be read but not written
idle(1),
cmdInProgress(2),
-- the following two values are actions:
-- they may be written, but are never read
swapToNewFile(3),
collectNow(4)
}
MAX-ACCESS read-create
acctngFileCommand OBJECT-TYPE
SYNTAX INTEGER {
-- the following two values are states:
-- they may be read but not written
idle(1),
cmdInProgress(2),
-- the following two values are actions:
-- they may be written, but are never read
swapToNewFile(3),
collectNow(4)
}
MAX-ACCESS read-create
STATUS current DESCRIPTION "A control object for the collection of accounting data. When read the value is either 'idle' or 'cmdInProgress'. Writing a value is only allowed when the current value is 'idle'. When a value is successfully written, the value changes to 'cmdInProgress' until completion of the action, at which time the value reverts to 'idle'. Actions are invoked by writing the following values:
状态当前描述“用于收集会计数据的控制对象。读取时，值为“idle”或“cmdInProgress”。仅当当前值为“空闲”时才允许写入值。成功写入值后，该值将更改为“cmdInProgress”，直到操作完成，此时该值将恢复为“idle”。通过写入以下值来调用操作：
'swapToNewFile' - the collection of data into the current file is terminated, and collection continues into a new (version of the) file.
“swapToNewFile”-终止对当前文件的数据收集，并继续收集到新的（版本的）文件中。
'collectNow' - the agent creates and stores a connection
record into the current file for each active
connection having a type matching
acctngSelectionType and an age greater than
acctngFileMinAge."
DEFVAL { idle }
::= { acctngFileEntry 5 }
'collectNow' - the agent creates and stores a connection
record into the current file for each active
connection having a type matching
acctngSelectionType and an age greater than
acctngFileMinAge."
DEFVAL { idle }
::= { acctngFileEntry 5 }
acctngFileMaximumSize OBJECT-TYPE SYNTAX Integer32 (100..2147483647) UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum size of the file (including header information). When the file of collected data reaches this size, either the agent automatically swaps to a new version (i.e., a new value acctngFileNameSuffix) of the file, or new records are discarded. Since a file must contain an integral number of connection records, the actual maximum size of the file may be just less OR Just greater than the value of this object.
acctngFileMaximumSize对象类型语法整数32（100..2147483647）单位“字节”MAX-ACCESS read create STATUS current DESCRIPTION“文件的最大大小（包括头信息）。当收集的数据文件达到此大小时，代理会自动切换到新版本（即新值acctngFileNameSuffix）由于文件必须包含整数个连接记录，因此文件的实际最大大小可能略小于或略大于此对象的值。
The value of this object can not be modified while the
corresponding instance of acctngFileRowStatus is 'active'.
The largest value of the maximum file size in some agents
will be less than 2147483647 bytes."
DEFVAL { 5000000 }
::= { acctngFileEntry 6 }
The value of this object can not be modified while the
corresponding instance of acctngFileRowStatus is 'active'.
The largest value of the maximum file size in some agents
will be less than 2147483647 bytes."
DEFVAL { 5000000 }
::= { acctngFileEntry 6 }
acctngFileCurrentSize OBJECT-TYPE SYNTAX Integer32 (0..2147483647) UNITS "bytes" MAX-ACCESS read-only
acctngFileCurrentSize对象类型语法整数32（0..2147483647）单位“字节”最大访问只读
STATUS current
DESCRIPTION
"The current size of the file into which data is currently
being collected, including header information."
::= { acctngFileEntry 7 }
STATUS current
DESCRIPTION
"The current size of the file into which data is currently
being collected, including header information."
::= { acctngFileEntry 7 }
acctngFileFormat OBJECT-TYPE
SYNTAX INTEGER { other(1), ber(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of the format in which the accounting data is
to be stored in the file. If the value is modified, the new
value takes effect after the next 'swap' to a new file. The
value ber(2) indicates the standard format."
DEFVAL { ber }
::= { acctngFileEntry 8 }
acctngFileFormat OBJECT-TYPE
SYNTAX INTEGER { other(1), ber(2) }
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"An indication of the format in which the accounting data is
to be stored in the file. If the value is modified, the new
value takes effect after the next 'swap' to a new file. The
value ber(2) indicates the standard format."
DEFVAL { ber }
::= { acctngFileEntry 8 }
acctngFileCollectMode OBJECT-TYPE SYNTAX BITS { onRelease(0), periodically(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "An indication of when accounting data is to be written into this file. Note that in addition to the occasions indicated by the value of this object, an agent always writes information on appropriate connections to the file when the corresponding instance of acctngFileCommand is set to 'collectNow'.
acctngFileCollectMode对象类型语法位{onRelease（0），periodic（1）}MAX-ACCESS read create STATUS当前描述“会计数据何时写入此文件的指示。请注意，除了此对象的值指示的情况外，当acctngFileCommand的相应实例设置为“collectNow”时，代理始终会将有关适当连接的信息写入文件。
- 'onRelease' - whenever a connection (or possibly, connection attempt) is terminated, either through a Release message or through management removal, information on that connection is written.
- “onRelease”-无论何时通过释放消息或管理删除终止连接（或可能是连接尝试），都会写入有关该连接的信息。
- 'periodically' - information on appropriate connections is written on the expiry of a periodic timer,
- “定期”-在定期计时器到期时写入有关适当连接的信息，
This value may be modified at any time."
DEFVAL { { onRelease } }
::= { acctngFileEntry 9 }
This value may be modified at any time."
DEFVAL { { onRelease } }
::= { acctngFileEntry 9 }
acctngFileCollectFailedAttempts OBJECT-TYPE SYNTAX BITS { soft(0), regular(1) } MAX-ACCESS read-create STATUS current DESCRIPTION "An indication of whether connection data is to be collected
ACCTNGFILeCollectedFailedAttempts对象类型语法位{soft（0），regular（1）}MAX-ACCESS read create STATUS current DESCRIPTION“是否收集连接数据的指示
for failed connection attempts when the value of the corresponding instance of acctngFileCollectMode includes 'onRelease'. The individual values have the following meaning:
当acctngFileCollectMode的对应实例的值包括“onRelease”时，用于失败的连接尝试。单个值具有以下含义：
'soft' - indicates that connection data is to be collected for failed Soft PVCs/PVPs which originate or terminate at the relevant interface.
“软”-表示将为在相关接口处发起或终止的故障软PVC/PVP收集连接数据。
'regular' - indicates that connection data is to be collected for failed SVCs, including Soft PVCs/PVPs not originating or terminating at the relevant interface.
“常规”-表示将为发生故障的SVC收集连接数据，包括不在相关接口发起或终止的软PVC/PVP。
This value may be modified at any time."
DEFVAL { { soft, regular } }
::= { acctngFileEntry 10 }
This value may be modified at any time."
DEFVAL { { soft, regular } }
::= { acctngFileEntry 10 }
acctngFileInterval OBJECT-TYPE
SYNTAX Integer32 (60..86400)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of seconds between the periodic collections of
accounting data when the value of the corresponding instance
of acctngFileCollectMode includes 'periodically'. Some
agents may impose restrictions on the range of this
interval. This value may be modified at any time."
DEFVAL { 3600 }
::= { acctngFileEntry 11 }
acctngFileInterval OBJECT-TYPE
SYNTAX Integer32 (60..86400)
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The number of seconds between the periodic collections of
accounting data when the value of the corresponding instance
of acctngFileCollectMode includes 'periodically'. Some
agents may impose restrictions on the range of this
interval. This value may be modified at any time."
DEFVAL { 3600 }
::= { acctngFileEntry 11 }
acctngFileMinAge OBJECT-TYPE SYNTAX Integer32 (60..86400) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The minimum age of a connection, as used to determine the set of connections for which data is to be collected at the periodic intervals and/or when acctngFileCommand is set to 'collectNow'. The age of a connection is the elapsed time since it was last installed.
acctngFileMinAge对象类型语法整数32（60..86400）单位“秒”最大访问读取创建状态当前描述“连接的最短期限，用于确定定期收集数据的连接集和/或当ACCTNGFILEMAND设置为“collectNow”时。连接期限是自上次安装以来经过的时间。
When the periodic interval expires for a file or when acctngFileCommand is set to 'collectNow', accounting data is collected and stored in the file for each connection having a type matching acctngSelectionType and whose age at that time is greater than the value of acctngFileMinAge
当文件的周期间隔到期时，或者当acctngFileCommand设置为“collectNow”时，将为具有与acctngSelectionType匹配的类型且其时间段大于acctngFileMinAge值的每个连接收集记帐数据并将其存储在文件中
associated with the file. This value may be modified at any
time."
DEFVAL { 3600 }
::= { acctngFileEntry 12 }
associated with the file. This value may be modified at any
time."
DEFVAL { 3600 }
::= { acctngFileEntry 12 }
acctngFileRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this conceptual row.
acctngFileRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此概念行的状态。
This object can not be set to 'active' until a value has
been assigned to the corresponding instance of
acctngFileName. Collection of data into the file does not
begin until this object has the value 'active' and one or
more (active) instances of acctngSelectionFile refer to it.
If this value is modified after a collection has begun,
collection into this file terminates and a new (or new
version of the) file is immediately made ready for future
collection (as if acctngFileCommand had been set to
'swapToNewFile'), but collection into the new (or new
version of the) file does not begin until the value is
subsequently set back to active."
::= { acctngFileEntry 13 }
This object can not be set to 'active' until a value has
been assigned to the corresponding instance of
acctngFileName. Collection of data into the file does not
begin until this object has the value 'active' and one or
more (active) instances of acctngSelectionFile refer to it.
If this value is modified after a collection has begun,
collection into this file terminates and a new (or new
version of the) file is immediately made ready for future
collection (as if acctngFileCommand had been set to
'swapToNewFile'), but collection into the new (or new
version of the) file does not begin until the value is
subsequently set back to active."
::= { acctngFileEntry 13 }
-- Overall Control
--总体控制
acctngAdminStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "A control object to indicate the administratively desired state of the collection of accounting records across all interfaces.
acctngAdminStatus对象类型语法整数{enabled（1），disabled（2）}MAX-ACCESS read-write STATUS current DESCRIPTION“一个控制对象，用于指示跨所有接口的记帐记录集合的管理所需状态。
Modifying the value of acctngAdminStatus to 'disabled' does
not remove or change the current configuration as
represented by the active rows in the acctngSelectionTable,
acctngFileTable and acctngInterfaceTable tables."
::= { acctngInterfaceControl 1 }
Modifying the value of acctngAdminStatus to 'disabled' does
not remove or change the current configuration as
represented by the active rows in the acctngSelectionTable,
acctngFileTable and acctngInterfaceTable tables."
::= { acctngInterfaceControl 1 }
acctngOperStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2) } MAX-ACCESS read-only STATUS current DESCRIPTION
acctngOperStatus对象类型语法整数{已启用（1），已禁用（2）}MAX-ACCESS只读状态当前说明
"A status object to indicate the operational state of the collection of accounting records across all interfaces.
“一个状态对象，用于指示跨所有接口的会计记录集合的操作状态。
When the value of acctngAdminStatus is modified to be 'enabled', the value of this object will change to 'enabled' providing it is possible to begin collecting accounting records.
当acctngAdminStatus的值修改为“已启用”时，如果可以开始收集会计记录，则此对象的值将更改为“已启用”。
When the value of acctngAdminStatus is modified to be
'disabled', the value of this object will change to
'disabled' as soon as the collection of accounting records
has terminated."
::= { acctngInterfaceControl 2 }
When the value of acctngAdminStatus is modified to be
'disabled', the value of this object will change to
'disabled' as soon as the collection of accounting records
has terminated."
::= { acctngInterfaceControl 2 }
acctngProtection OBJECT-TYPE SYNTAX TestAndIncr MAX-ACCESS read-write STATUS current DESCRIPTION "A control object to protect against duplication of control commands. Over some transport/network protocols, it is possible for SNMP messages to get duplicated. Such duplication, if it occurred at just the wrong time could cause serious disruption to the collection and retrieval of accounting data, e.g., if a SNMP message setting acctngFileCommand to 'swapToNewFile' were to be duplicated, a whole file of accounting data could be lost.
acctngProtection对象类型语法测试INCR MAX-ACCESS读写状态当前说明“用于防止控制命令重复的控制对象。在某些传输/网络协议上，SNMP消息可能会被复制。这种复制如果发生在错误的时间，可能会对会计数据的收集和检索造成严重中断，例如，如果要复制将ACCTNGFILECOMAND设置为“swapToNewFile”的SNMP消息，则整个会计数据文件可能会丢失。
To protect against such duplication, a management
application should retrieve the value of this object, and
include in the Set operation needing protection, a variable
binding which sets this object to the retrieved value."
::= { acctngInterfaceControl 3 }
To protect against such duplication, a management
application should retrieve the value of this object, and
include in the Set operation needing protection, a variable
binding which sets this object to the retrieved value."
::= { acctngInterfaceControl 3 }
acctngAgentMode OBJECT-TYPE SYNTAX INTEGER { swapOnCommand(1), swapOnFull(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of the behaviour mode of the agent when a file becomes full:
acctngAgentMode对象类型语法整数{swapOnCommand（1），swapOnFull（2）}MAX-ACCESS只读状态当前描述“文件已满时代理行为模式的指示：
'swapOnCommand' - the agent does not automatically swap to a new file; rather, it discards newly collected data until a management application subsequently instructs it to swap to a new file.
“swapOnCommand”-代理不会自动切换到新文件；相反，它会丢弃新收集的数据，直到管理应用程序随后指示它交换到新文件。
'swapOnFull' - the agent terminates collection into the
“swapOnFull”-代理将集合终止到
current file as and when that file becomes full."
::= { acctngInterfaceControl 4 }
current file as and when that file becomes full."
::= { acctngInterfaceControl 4 }
-- Per-interface control table
--每个接口控制表
acctngInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF AcctngInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table controlling the collection of accounting data on
specific interfaces of the switch."
::= { acctngInterfaceControl 5 }
acctngInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF AcctngInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table controlling the collection of accounting data on
specific interfaces of the switch."
::= { acctngInterfaceControl 5 }
acctngInterfaceEntry OBJECT-TYPE
SYNTAX AcctngInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry which controls whether accounting data is to be
collected on an interface. The types of interfaces which
are represented in this table is implementation-specific."
INDEX { ifIndex }
::= { acctngInterfaceTable 1 }
acctngInterfaceEntry OBJECT-TYPE
SYNTAX AcctngInterfaceEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry which controls whether accounting data is to be
collected on an interface. The types of interfaces which
are represented in this table is implementation-specific."
INDEX { ifIndex }
::= { acctngInterfaceTable 1 }
AcctngInterfaceEntry ::=
SEQUENCE {
acctngInterfaceEnable TruthValue
}
AcctngInterfaceEntry ::=
SEQUENCE {
acctngInterfaceEnable TruthValue
}
acctngInterfaceEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the collection of accounting data is
enabled on this interface."
::= { acctngInterfaceEntry 1 }
acctngInterfaceEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates whether the collection of accounting data is
enabled on this interface."
::= { acctngInterfaceEntry 1 }
-- Objects for controlling the use of Notifications
--用于控制通知使用的对象
acctngControlTrapThreshold OBJECT-TYPE SYNTAX INTEGER (0..99) MAX-ACCESS read-write STATUS current DESCRIPTION "A percentage of the maximum file size at which a 'nearly-
acctngControlTrapThreshold对象类型语法整数（0..99）MAX-ACCESS读写状态当前描述“接近-
full' trap is generated. The value of 0 indicates that no
'nearly-full' trap is to be generated."
::= { acctngTrapControl 1 }
full' trap is generated. The value of 0 indicates that no
'nearly-full' trap is to be generated."
::= { acctngTrapControl 1 }
acctngControlTrapEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An indication of whether the acctngFileNearlyFull and
acctngFileFull traps are enabled."
::= { acctngTrapControl 2 }
acctngControlTrapEnable OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"An indication of whether the acctngFileNearlyFull and
acctngFileFull traps are enabled."
::= { acctngTrapControl 2 }
-- notifications
--通知
acctngNotifications OBJECT IDENTIFIER ::= { accountingControlMIB 2 }
acctngNotifications OBJECT IDENTIFIER ::= { accountingControlMIB 2 }
acctngNotifyPrefix OBJECT IDENTIFIER ::= { acctngNotifications 0 }
acctngNotifyPrefix OBJECT IDENTIFIER ::= { acctngNotifications 0 }
acctngFileNearlyFull NOTIFICATION-TYPE
OBJECTS { acctngFileName,
acctngFileMaximumSize,
acctngControlTrapThreshold,
acctngFileNameSuffix }
STATUS current
DESCRIPTION
"An indication that the size of the file into which
accounting information is currently being collected has
exceeded the threshold percentage of its maximum file size.
This notification is generated only at the time of the
transition from not-exceeding to exceeding."
::= { acctngNotifyPrefix 1 }
acctngFileNearlyFull NOTIFICATION-TYPE
OBJECTS { acctngFileName,
acctngFileMaximumSize,
acctngControlTrapThreshold,
acctngFileNameSuffix }
STATUS current
DESCRIPTION
"An indication that the size of the file into which
accounting information is currently being collected has
exceeded the threshold percentage of its maximum file size.
This notification is generated only at the time of the
transition from not-exceeding to exceeding."
::= { acctngNotifyPrefix 1 }
acctngFileFull NOTIFICATION-TYPE OBJECTS { acctngFileName, acctngFileMaximumSize, acctngFileNameSuffix } STATUS current DESCRIPTION "An indication that the size of the file into which accounting information is currently being collected has transistioned to its maximum file size. This notification is generated (for all values of acctngAgentMode) at the time of the transition from not-full to full. If acctngAgentMode has the value 'swapOnCommand', it is also generated periodically thereafter until such time as collection of
acctngFileFull NOTIFICATION-TYPE对象{acctngFileName，acctngFileMaximumSize，acctngFileNameSuffix}状态当前描述“表示当前收集会计信息的文件大小已转换为其最大文件大小。生成此通知（针对AcctngEntMode的所有值）在从“未满”转换为“满”时。如果acctngAgentMode具有值“swapOnCommand”，则此后还会定期生成该值，直到
data is no longer inhibited by the file full condition."
::= { acctngNotifyPrefix 2 }
data is no longer inhibited by the file full condition."
::= { acctngNotifyPrefix 2 }
-- conformance information
--一致性信息
acctngConformance OBJECT IDENTIFIER ::= { accountingControlMIB 3 }
acctngGroups OBJECT IDENTIFIER ::= { acctngConformance 1 }
acctngCompliances OBJECT IDENTIFIER ::= { acctngConformance 2 }
acctngConformance OBJECT IDENTIFIER ::= { accountingControlMIB 3 }
acctngGroups OBJECT IDENTIFIER ::= { acctngConformance 1 }
acctngCompliances OBJECT IDENTIFIER ::= { acctngConformance 2 }
acctngCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for switches which implement the Accounting Control MIB."
acctngCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“实施会计控制MIB的交换机的符合性声明”
MODULE -- this module MANDATORY-GROUPS { acctngBasicGroup, acctngNotificationsGroup }
MODULE--此模块为必填组{acctngBasicGroup，acctngNotificationsGroup}
OBJECT acctngSelectionType SYNTAX BITS { svcIncoming(0), svcOutgoing(1) } DESCRIPTION "The minimal requirement is collection for SVCs."
对象acctngSelectionType语法位{svcIncoming（0），SVCouting（1）}说明“SVC的最低要求是集合。”
OBJECT acctngSelectionRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象acctngSelectionRowStatus MIN-ACCESS只读说明“不需要写访问权限。”
OBJECT acctngFileName MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象acctngFileName MIN-ACCESS只读说明“不需要写访问。”
OBJECT acctngFileCommand MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象ACCTNGFILECOMAND MIN-ACCESS只读说明“不需要写访问。”
OBJECT acctngFileFormat SYNTAX INTEGER { ber(2) } MIN-ACCESS read-only DESCRIPTION "Only the standard format is required, and write access is not required."
对象acctngFileFormat语法整数{ber（2）}MIN-ACCESS只读说明“只需要标准格式，不需要写访问。”
OBJECT acctngFileMaximumSize MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象acctngFileMaximumSize最小访问只读描述“不需要写访问。”
OBJECT acctngFileCollectMode SYNTAX BITS { onRelease(0) }
对象acctngFileCollectMode语法位{onRelease（0）}
MIN-ACCESS read-only DESCRIPTION "The minimal requirement is for collection on connection release."
MIN-ACCESS只读说明“最低要求是在连接释放时收集。”
OBJECT acctngFileInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象acctngFileInterval MIN-ACCESS只读描述“不需要写访问。”
OBJECT acctngFileCollectFailedAttempts MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象ACCTNGFILeCollectedFailedAttempts最小访问只读描述“不需要写访问。”
OBJECT acctngFileRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象acctngFileRowStatus MIN-ACCESS只读说明“不需要写访问。”
::= { acctngCompliances 1 }
::= { acctngCompliances 1 }
-- units of conformance
--一致性单位
acctngBasicGroup OBJECT-GROUP
OBJECTS { acctngSelectionSubtree, acctngSelectionList,
acctngSelectionFile, acctngSelectionType,
acctngSelectionRowStatus, acctngFileName,
acctngFileNameSuffix, acctngFileDescription,
acctngFileCommand, acctngFileMaximumSize,
acctngFileCurrentSize, acctngFileRowStatus,
acctngFileFormat, acctngFileCollectMode,
acctngFileCollectFailedAttempts, acctngFileInterval,
acctngFileMinAge,
acctngAdminStatus, acctngOperStatus,
acctngProtection, acctngAgentMode,
acctngInterfaceEnable,
acctngControlTrapThreshold,
acctngControlTrapEnable
}
STATUS current
DESCRIPTION
"A collection of objects providing control of the basic
collection of accounting data for connection-oriented
networks."
::= { acctngGroups 1 }
acctngBasicGroup OBJECT-GROUP
OBJECTS { acctngSelectionSubtree, acctngSelectionList,
acctngSelectionFile, acctngSelectionType,
acctngSelectionRowStatus, acctngFileName,
acctngFileNameSuffix, acctngFileDescription,
acctngFileCommand, acctngFileMaximumSize,
acctngFileCurrentSize, acctngFileRowStatus,
acctngFileFormat, acctngFileCollectMode,
acctngFileCollectFailedAttempts, acctngFileInterval,
acctngFileMinAge,
acctngAdminStatus, acctngOperStatus,
acctngProtection, acctngAgentMode,
acctngInterfaceEnable,
acctngControlTrapThreshold,
acctngControlTrapEnable
}
STATUS current
DESCRIPTION
"A collection of objects providing control of the basic
collection of accounting data for connection-oriented
networks."
::= { acctngGroups 1 }
acctngNotificationsGroup NOTIFICATION-GROUP NOTIFICATIONS { acctngFileNearlyFull, acctngFileFull } STATUS current DESCRIPTION
acctngNotificationsGroup NOTIFICATION-GROUP NOTIFICATION{acctngFileNearlyFull，acctngFileFull}状态当前描述
"The notifications of events relating to controlling the
collection of accounting data."
::= { acctngGroups 2 }
"The notifications of events relating to controlling the
collection of accounting data."
::= { acctngGroups 2 }
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] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Management Information Base for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1907, January 1996.
[16] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息库”，RFC 1907，1996年1月。
[17] Information processing systems - Open Systems Interconnection, "Specification of Abstract Syntax Notation One (ASN.1)", International Organization for Standardization, Internation Standard 8824, December 1987.
[17] 信息处理系统.开放系统互连，“抽象语法符号1规范（ASN.1）”，国际标准化组织，国际标准88241987年12月。
[18] Information processing systems - Open Systems Interconnection, "Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1)", International Organization for Standardization, Internation Standard 8825, December 1987.
[18] 信息处理系统.开放系统互连，“抽象语法符号1（ASN.1）基本编码规则规范”，国际标准化组织，国际标准8825，1987年12月。
[19] McCloghrie, K., Heinanen, J., Greene, W. and A. Prasad, "Accounting Information for ATM Networks", RFC 2512, February 1999.
[19] McCloghrie，K.，Heinanen，J.，Greene，W.和A.Prasad，“ATM网络的会计信息”，RFC 25112999年2月。
[20] Noto, M., Spiegel, E., and K. Tesink, "Definitions of Textual Conventions and OBJECT-IDENTITIES for ATM Management", RFC 2514, February 1999.
[20] Noto，M.，Spiegel，E.，和K.Tesink，“ATM管理的文本约定和对象标识的定义”，RFC 2514，1999年2月。
The MIB defined in this memo controls and monitors the collection of accounting data. Care should be taken to prohibit unauthorized access to this control capability in order to prevent the disruption of data collection, possibly with fraudulent intent. Example of such disruption are disabling the collection of data, or causing the wrong set of data items to be collected.
本备忘录中定义的MIB控制和监控会计数据的收集。应注意禁止未经授权访问此控制功能，以防止数据收集中断，可能是出于欺诈目的。此类中断的示例包括禁用数据收集，或导致收集错误的数据项集。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
SNMPv1本身不是一个安全的环境。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB中的对象。
It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2274 [12] and the View-based Access Control Model RFC 2275 [15] is recommended.
建议实施者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC 2274[12]和基于视图的访问控制模型RFC 2275[15]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
然后，客户/用户有责任确保授予对此MIB实例访问权限的SNMP实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
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: 408 525-7209 EMail: aprasad@cisco.com
电话：408 525-7209电子邮件：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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。