Network Working Group B. Aboba
Request for Comments: 2620 G. Zorn
Category: Informational Microsoft
June 1999
Network Working Group B. Aboba
Request for Comments: 2620 G. Zorn
Category: Informational Microsoft
June 1999
RADIUS Accounting Client MIB
RADIUS记帐客户端MIB
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。本备忘录未规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Abstract
摘要
This memo defines a set of extensions which instrument RADIUS accounting client functions. These extensions represent a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Using these extensions IP-based management stations can manage RADIUS accounting clients.
此备忘录定义了一组用于instrument RADIUS accounting客户端功能的扩展。这些扩展代表管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。使用这些扩展，基于IP的管理站可以管理RADIUS记帐客户端。
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 managing RADIUS accounting clients.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于管理RADIUS记帐客户端的托管对象。
Today a wide range of network devices, including routers and NASes, act as RADIUS accounting clients in order to provide accounting services. As a result, the effective management of RADIUS accounting clients is of considerable importance.
今天，包括路由器和NASE在内的各种网络设备充当RADIUS记帐客户端，以提供记帐服务。因此，RADIUS会计客户的有效管理具有相当重要的意义。
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [1].
o RFC 2571[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
o 为管理目的描述和命名对象和事件的机制。此管理信息结构（SMI）的第一个版本称为SMIv1，如中所述
STD 15, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7].
标准15，RFC 1155[2]，标准16，RFC 1212[3]和RFC 1215[4]。第二个版本称为SMIv2，在STD 58、RFC 2578[5]、RFC 2579[6]和RFC 2580[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 2572 [11] and RFC 2574 [12].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[8]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[9]和RFC 1906[10]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[10]、RFC 2572[11]和RFC 2574[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 2573 [14] and the view-based access control mechanism described in RFC 2575 [15].
o RFC 2573[14]中描述的一组基本应用程序和RFC 2575[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 poduced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (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的语义。
The RADIUS accounting protocol, described in [16], distinguishes between the client function and the server function. In RADIUS accounting, clients send Accounting-Requests, and servers reply with Accounting-Responses. Typically NAS devices implement the client function, and thus would be expected to implement the RADIUS accounting client MIB, while RADIUS accounting servers implement the server function, and thus would be expected to implement the RADIUS accounting server MIB.
[16]中描述的RADIUS记帐协议区分了客户端功能和服务器功能。在RADIUS记帐中，客户端发送记帐请求，服务器用记帐响应进行答复。通常，NAS设备实现客户端功能，因此预期将实现RADIUS记帐客户端MIB，而RADIUS记帐服务器实现服务器功能，因此预期将实现RADIUS记帐服务器MIB。
However, it is possible for a RADIUS accounting entity to perform both client and server functions. For example, a RADIUS proxy may act as a server to one or more RADIUS accounting clients, while simultaneously acting as an accounting client to one or more accounting servers. In such situations, it is expected that RADIUS entities combining client and server functionality will support both the client and server MIBs.
但是，RADIUS记帐实体可以同时执行客户端和服务器功能。例如，RADIUS代理可以充当一个或多个RADIUS记帐客户端的服务器，同时充当一个或多个记帐服务器的记帐客户端。在这种情况下，结合客户端和服务器功能的RADIUS实体预计将同时支持客户端和服务器MIB。
This MIB module contains two scalars as well as a single table:
此MIB模块包含两个标量和一个表：
(1) the RADIUS Accounting Server Table contains one row for each RADIUS server that the client shares a secret with.
(1) RADIUS Accounting Server表包含客户端共享机密的每个RADIUS服务器的一行。
Each entry in the RADIUS Accounting Server Table includes thirteen columns presenting a view of the activity of the RADIUS client.
RADIUS Accounting Server表中的每个条目包括十三列，表示RADIUS客户端活动的视图。
RADIUS-ACC-CLIENT-MIB DEFINITIONS ::= BEGIN
RADIUS-ACC-CLIENT-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Counter32, Integer32, Gauge32, IpAddress, TimeTicks, mib-2 FROM SNMPv2-SMI SnmpAdminString FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
从SNMPv2 SMI导入模块标识、对象类型、对象标识、计数器32、整数32、仪表32、IpAddress、TimeTicks、mib-2从SNMP-FRAMEWORK-mib MODULE-COMPLIANCE导入SNMPv2 SMI SNMPAdministring从SNMPv2 CONF导入对象组；
radiusAccClientMIB MODULE-IDENTITY LAST-UPDATED "9906110000Z" -- 11 Jun 1999 ORGANIZATION "IETF RADIUS Working Group." CONTACT-INFO " Bernard Aboba Microsoft One Microsoft Way Redmond, WA 98052 US
radiusAccClientMIB模块标识最后一次更新“9906100000Z”--1999年6月11日组织“IETF RADIUS工作组”。联系方式“Bernard Aboba Microsoft One Microsoft Way Redmond，WA 98052美国
Phone: +1 425 936 6605
EMail: bernarda@microsoft.com"
DESCRIPTION
"The MIB module for entities implementing the client side of
the Remote Access Dialin User Service (RADIUS) accounting
protocol."
REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2620"
::= { radiusAccounting 2 }
Phone: +1 425 936 6605
EMail: bernarda@microsoft.com"
DESCRIPTION
"The MIB module for entities implementing the client side of
the Remote Access Dialin User Service (RADIUS) accounting
protocol."
REVISION "9906110000Z" -- 11 Jun 1999
DESCRIPTION "Initial version as published in RFC 2620"
::= { radiusAccounting 2 }
radiusMIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { mib-2 67 }
radiusMIB OBJECT-IDENTITY
STATUS current
DESCRIPTION
"The OID assigned to RADIUS MIB work by the IANA."
::= { mib-2 67 }
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
radiusAccounting OBJECT IDENTIFIER ::= {radiusMIB 2}
radiusAccClientMIBObjects OBJECT IDENTIFIER ::=
{ radiusAccClientMIB 1 }
radiusAccClientMIBObjects OBJECT IDENTIFIER ::=
{ radiusAccClientMIB 1 }
radiusAccClient OBJECT IDENTIFIER ::= { radiusAccClientMIBObjects 1 }
radiusAccClient OBJECT IDENTIFIER ::= { radiusAccClientMIBObjects 1 }
radiusAccClientInvalidServerAddresses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response packets
received from unknown addresses."
::= { radiusAccClient 1 }
radiusAccClientInvalidServerAddresses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response packets
received from unknown addresses."
::= { radiusAccClient 1 }
radiusAccClientIdentifier OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-Identifier of the RADIUS accounting client. This
is not necessarily the same as sysName in MIB II."
::= { radiusAccClient 2 }
radiusAccClientIdentifier OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The NAS-Identifier of the RADIUS accounting client. This
is not necessarily the same as sysName in MIB II."
::= { radiusAccClient 2 }
radiusAccServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccServerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the RADIUS accounting
servers with which the client shares a secret."
::= { radiusAccClient 3 }
radiusAccServerTable OBJECT-TYPE
SYNTAX SEQUENCE OF RadiusAccServerEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the RADIUS accounting
servers with which the client shares a secret."
::= { radiusAccClient 3 }
radiusAccServerEntry OBJECT-TYPE SYNTAX RadiusAccServerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry (conceptual row) representing a RADIUS accounting server with which the client shares a secret." INDEX { radiusAccServerIndex }
radiusAccServerEntry对象类型语法radiusAccServerEntry MAX-ACCESS不可访问状态当前描述“表示客户端与之共享机密的RADIUS记帐服务器的条目（概念行）。”索引{radiusAccServerIndex}
::= { radiusAccServerTable 1 }
::= { radiusAccServerTable 1 }
RadiusAccServerEntry ::= SEQUENCE {
radiusAccServerIndex Integer32,
radiusAccServerAddress IpAddress,
radiusAccClientServerPortNumber Integer32,
radiusAccClientRoundTripTime TimeTicks,
radiusAccClientRequests Counter32,
radiusAccClientRetransmissions Counter32,
radiusAccClientResponses Counter32,
radiusAccClientMalformedResponses Counter32,
radiusAccClientBadAuthenticators Counter32,
radiusAccClientPendingRequests Gauge32,
radiusAccClientTimeouts Counter32,
radiusAccClientUnknownTypes Counter32,
radiusAccClientPacketsDropped Counter32
}
RadiusAccServerEntry ::= SEQUENCE {
radiusAccServerIndex Integer32,
radiusAccServerAddress IpAddress,
radiusAccClientServerPortNumber Integer32,
radiusAccClientRoundTripTime TimeTicks,
radiusAccClientRequests Counter32,
radiusAccClientRetransmissions Counter32,
radiusAccClientResponses Counter32,
radiusAccClientMalformedResponses Counter32,
radiusAccClientBadAuthenticators Counter32,
radiusAccClientPendingRequests Gauge32,
radiusAccClientTimeouts Counter32,
radiusAccClientUnknownTypes Counter32,
radiusAccClientPacketsDropped Counter32
}
radiusAccServerIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A number uniquely identifying each RADIUS
Accounting server with which this client
communicates."
::= { radiusAccServerEntry 1 }
radiusAccServerIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A number uniquely identifying each RADIUS
Accounting server with which this client
communicates."
::= { radiusAccServerEntry 1 }
radiusAccServerAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the RADIUS accounting server
referred to in this table entry."
::= { radiusAccServerEntry 2 }
radiusAccServerAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The IP address of the RADIUS accounting server
referred to in this table entry."
::= { radiusAccServerEntry 2 }
radiusAccClientServerPortNumber OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UDP port the client is using to send requests to
this server."
::= { radiusAccServerEntry 3 }
radiusAccClientServerPortNumber OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The UDP port the client is using to send requests to
this server."
::= { radiusAccServerEntry 3 }
radiusAccClientRoundTripTime OBJECT-TYPE SYNTAX TimeTicks
radiusAccClientRoundTripTime对象类型语法时间标记
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time interval between the most recent
Accounting-Response and the Accounting-Request that
matched it from this RADIUS accounting server."
::= { radiusAccServerEntry 4 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time interval between the most recent
Accounting-Response and the Accounting-Request that
matched it from this RADIUS accounting server."
::= { radiusAccServerEntry 4 }
-- Request/Response statistics
--
-- Requests = Responses + PendingRequests + ClientTimeouts
--
-- Responses - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received
-- Request/Response statistics
--
-- Requests = Responses + PendingRequests + ClientTimeouts
--
-- Responses - MalformedResponses - BadAuthenticators -
-- UnknownTypes - PacketsDropped = Successfully received
radiusAccClientRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent. This does not include retransmissions."
::= { radiusAccServerEntry 5 }
radiusAccClientRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent. This does not include retransmissions."
::= { radiusAccServerEntry 5 }
radiusAccClientRetransmissions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
retransmitted to this RADIUS accounting server.
Retransmissions include retries where the
Identifier and Acct-Delay have been updated, as
well as those in which they remain the same."
::= { radiusAccServerEntry 6 }
radiusAccClientRetransmissions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
retransmitted to this RADIUS accounting server.
Retransmissions include retries where the
Identifier and Acct-Delay have been updated, as
well as those in which they remain the same."
::= { radiusAccServerEntry 6 }
radiusAccClientResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets received on the
accounting port from this server."
::= { radiusAccServerEntry 7 }
radiusAccClientResponses OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets received on the
accounting port from this server."
::= { radiusAccServerEntry 7 }
radiusAccClientMalformedResponses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only
RadiusaccClientMalformedResponse对象类型语法计数器32 MAX-ACCESS只读
STATUS current
DESCRIPTION
"The number of malformed RADIUS Accounting-Response
packets received from this server. Malformed packets
include packets with an invalid length. Bad
authenticators and unknown types are not included as
malformed accounting responses."
::= { radiusAccServerEntry 8 }
STATUS current
DESCRIPTION
"The number of malformed RADIUS Accounting-Response
packets received from this server. Malformed packets
include packets with an invalid length. Bad
authenticators and unknown types are not included as
malformed accounting responses."
::= { radiusAccServerEntry 8 }
radiusAccClientBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response
packets which contained invalid authenticators
received from this server."
::= { radiusAccServerEntry 9 }
radiusAccClientBadAuthenticators OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Response
packets which contained invalid authenticators
received from this server."
::= { radiusAccServerEntry 9 }
radiusAccClientPendingRequests OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent to this server that have not yet timed out or
received a response. This variable is incremented when an
Accounting-Request is sent and decremented due to
receipt of an Accounting-Response, a timeout or
a retransmission."
::= { radiusAccServerEntry 10 }
radiusAccClientPendingRequests OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS Accounting-Request packets
sent to this server that have not yet timed out or
received a response. This variable is incremented when an
Accounting-Request is sent and decremented due to
receipt of an Accounting-Response, a timeout or
a retransmission."
::= { radiusAccServerEntry 10 }
radiusAccClientTimeouts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of accounting timeouts to this server.
After a timeout the client may retry to the same
server, send to a different server, or give up.
A retry to the same server is counted as a
retransmit as well as a timeout. A send to a different
server is counted as an Accounting-Request as well as
a timeout."
::= { radiusAccServerEntry 11 }
radiusAccClientTimeouts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of accounting timeouts to this server.
After a timeout the client may retry to the same
server, send to a different server, or give up.
A retry to the same server is counted as a
retransmit as well as a timeout. A send to a different
server is counted as an Accounting-Request as well as
a timeout."
::= { radiusAccServerEntry 11 }
radiusAccClientUnknownTypes OBJECT-TYPE SYNTAX Counter32
radiusAccClientUnknownTypes对象类型语法计数器32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets of unknown type which
were received from this server on the accounting port."
::= { radiusAccServerEntry 12 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets of unknown type which
were received from this server on the accounting port."
::= { radiusAccServerEntry 12 }
radiusAccClientPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets which were received from
this server on the accounting port and dropped for some
other reason."
::= { radiusAccServerEntry 13 }
radiusAccClientPacketsDropped OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of RADIUS packets which were received from
this server on the accounting port and dropped for some
other reason."
::= { radiusAccServerEntry 13 }
-- conformance information
--一致性信息
radiusAccClientMIBConformance
OBJECT IDENTIFIER ::= { radiusAccClientMIB 2 }
radiusAccClientMIBCompliances
OBJECT IDENTIFIER ::= { radiusAccClientMIBConformance 1 }
radiusAccClientMIBGroups
OBJECT IDENTIFIER ::= { radiusAccClientMIBConformance 2 }
radiusAccClientMIBConformance
OBJECT IDENTIFIER ::= { radiusAccClientMIB 2 }
radiusAccClientMIBCompliances
OBJECT IDENTIFIER ::= { radiusAccClientMIBConformance 1 }
radiusAccClientMIBGroups
OBJECT IDENTIFIER ::= { radiusAccClientMIBConformance 2 }
-- compliance statements
--合规声明
radiusAccClientMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for accounting clients implementing the RADIUS Accounting Client MIB." MODULE -- this module MANDATORY-GROUPS { radiusAccClientMIBGroup }
RADIUSACCCLIENTMIB COMPLIANCE MODULE-COMPLIANCE STATUS当前描述“用于实现RADIUS会计客户端MIB的会计客户端的符合性声明。”模块--此模块为必填项-GROUPS{radiusAccClientMIBGroup}
::= { radiusAccClientMIBCompliances 1 }
::= { radiusAccClientMIBCompliances 1 }
-- units of conformance
--一致性单位
radiusAccClientMIBGroup OBJECT-GROUP OBJECTS { radiusAccClientIdentifier, radiusAccClientInvalidServerAddresses, radiusAccServerAddress, radiusAccClientServerPortNumber, radiusAccClientRoundTripTime, radiusAccClientRequests,
radiusAccClientMIBGroup对象组对象{radiusAccClientIdentifier，RadiusaccClientInvalidServerAddresss，radiusAccServerAddress，radiusAccClientServerPortNumber，radiusAccClientRoundTripTime，radiusAccClientRequests，
radiusAccClientRetransmissions,
radiusAccClientResponses,
radiusAccClientMalformedResponses,
radiusAccClientBadAuthenticators,
radiusAccClientPendingRequests,
radiusAccClientTimeouts,
radiusAccClientUnknownTypes,
radiusAccClientPacketsDropped
}
STATUS current
DESCRIPTION
"The basic collection of objects providing management of
RADIUS Accounting Clients."
::= { radiusAccClientMIBGroups 1 }
radiusAccClientRetransmissions,
radiusAccClientResponses,
radiusAccClientMalformedResponses,
radiusAccClientBadAuthenticators,
radiusAccClientPendingRequests,
radiusAccClientTimeouts,
radiusAccClientUnknownTypes,
radiusAccClientPacketsDropped
}
STATUS current
DESCRIPTION
"The basic collection of objects providing management of
RADIUS Accounting Clients."
::= { radiusAccClientMIBGroups 1 }
END
终止
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[1] Harrington，D.，Presuhn，R.，和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[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, Performance Systems International, March 1991.
[4] Rose，M.“定义用于SNMP的陷阱的约定”，RFC 1215，性能系统国际，1991年3月。
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[5] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[6] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[7] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[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] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] 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] 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 2572, April 1999.
[11] Case，J.，Harrington D.，Presohn R.，和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model for Version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版基于用户的安全模型”，RFC 2574，1999年4月。
[13] 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] Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC 2573, April 1999.
[14] Levi，D.，Meyer，P.，和B.Stewart，“SNMP应用”，RFC2573，1999年4月。
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[15] Wijnen，B.，Presuhn，R.，和K.McCloghrie，“简单网络管理协议（SNMP）基于视图的访问控制模型”，RFC2575，1999年4月。
[16] Rigney, C., "RADIUS Accounting", RFC 2139, April 1997.
[16] 里格尼，C.，“半径会计”，RFC 21391997年4月。
There are no management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB is implemented correctly, then there is no risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET opertions.
此MIB中未定义具有读写和/或读创建MAX-ACCESS子句的管理对象。因此，如果此MIB正确实现，则入侵者不会通过直接SNMP集操作更改或创建此MIB的任何管理对象。
There are a number of managed objects in this MIB that may contain sensitive information. These are:
此MIB中有许多托管对象可能包含敏感信息。这些是：
radiusAccServerAddress This can be used to determine the address of the RADIUS accounting server with which the client is communicating. This information could be useful in mounting an attack on the acounting server, which may contain sensitive financial data.
radiusAccServerAddress可用于确定客户端与之通信的RADIUS记帐服务器的地址。此信息有助于对可能包含敏感财务数据的会计服务器发起攻击。
radiusAccClientServerPortNumber This can be used to determine the port number on which the RADIUS accounting client is sending. This information could be useful in impersonating the client in order to send fraudulent data to the accounting server.
radiusAccClientServerPortNumber可用于确定RADIUS记帐客户端正在发送的端口号。此信息可用于模拟客户端，以便向记帐服务器发送欺诈数据。
It is thus important to control even GET access to these objects and possibly to even encrypt the values of these object when sending them over the network via SNMP. Not all versions of SNMP provide features for such a secure environment.
因此，在通过SNMP通过网络发送这些对象时，控制甚至访问这些对象，甚至可能加密这些对象的值，这一点非常重要。并非所有版本的SNMP都为这种安全环境提供功能。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), 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 2574 [12] and the View-based Access Control Model RFC 2575 [15] is recommended. Using these security features, customer/users can give access to the objects only to those principals (users) that have legitimate rights to GET or SET (change/create/delete) them.
建议实施者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC 2574[12]和基于视图的访问控制模型RFC 2575[15]。使用这些安全功能，客户/用户只能将对象的访问权限授予那些具有获取或设置（更改/创建/删除）对象的合法权限的主体（用户）。
The authors acknowledge the contributions of the RADIUS Working Group in the development of this MIB. Thanks to Narendra Gidwani of Microsoft, Allan C. Rubens of MERIT, Carl Rigney of Livingston and Peter Heitman of American Internet Corporation for useful discussions of this problem space.
作者感谢RADIUS工作组在MIB开发中的贡献。感谢微软公司的纳伦德拉·吉德瓦尼（Narendra Gidwani）、梅里特公司的艾伦·鲁本斯（Allan C.Rubens）、利文斯顿公司的卡尔·里格尼（Carl Rigney）和美国互联网公司的彼得·海特曼（Peter Heitman）对这个问题空间进行了有益的讨论。
Bernard Aboba Microsoft Corporation One Microsoft Way Redmond, WA 98052
伯纳德·阿博巴（Bernard Aboba）微软公司华盛顿州雷德蒙微软大道一号，邮编：98052
Phone: 425-936-6605 EMail: bernarda@microsoft.com
电话：425-936-6605电子邮件：bernarda@microsoft.com
Glen Zorn Microsoft Corporation One Microsoft Way Redmond, WA 98052
格伦·佐恩微软公司华盛顿州雷德蒙微软大道一号，邮编：98052
Phone: 425-703-1559 EMail: glennz@microsoft.com
电话：425-703-1559电子邮件：glennz@microsoft.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 implmentation 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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。