Network Working Group N. Freed
Request for Comments: 2788 Innosoft
Category: Standards Track S. Kille
Obsoletes: 2248 MessagingDirect Ltd.
March 2000
Network Working Group N. Freed
Request for Comments: 2788 Innosoft
Category: Standards Track S. Kille
Obsoletes: 2248 MessagingDirect Ltd.
March 2000
Network Services Monitoring MIB
网络服务监控MIB
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 (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Introduction
介绍
A networked application is a realization of some well-defined service on one or more host computers that is accessible via some network, uses some network for its internal operations, or both.
网络化应用程序是在一台或多台主机上实现某种定义明确的服务，这些主机可以通过某种网络访问，或使用某种网络进行内部操作，或两者兼而有之。
There are a wide range of networked applications for which it is appropriate to provide SNMP monitoring of their network usage. This includes applications using both TCP/IP and OSI networking. This document defines a MIB which contains the elements common to the monitoring of any network service application. This information includes a table of all monitorable network service applications, a count of the associations (connections) to each application, and basic information about the parameters and status of each application-related association.
有许多网络应用程序适合于提供对其网络使用情况的SNMP监控。这包括同时使用TCP/IP和OSI网络的应用程序。本文档定义了一个MIB，其中包含用于监视任何网络服务应用程序的通用元素。此信息包括所有可监控网络服务应用程序的表、每个应用程序的关联（连接）计数，以及每个应用程序相关关联的参数和状态的基本信息。
This MIB may be used on its own for any application, and for most simple applications this will suffice. This MIB is also designed to serve as a building block which can be used in conjunction with application-specific monitoring and management. Two examples of this are MIBs defining additional variables for monitoring a Message Transfer Agent (MTA) service or a Directory Service Agent (DSA) service. It is expected that further MIBs of this nature will be specified.
此MIB可以单独用于任何应用程序，对于大多数简单的应用程序，这就足够了。此MIB还被设计为一个构建块，可与特定于应用程序的监视和管理结合使用。这方面的两个示例是定义用于监视消息传输代理（MTA）服务或目录服务代理（DSA）服务的附加变量的MIB。预计将进一步指定这种性质的MIB。
This MIB does not attempt to provide facilities for management of the host or hosts the network service application runs on, nor does it provide facilities for monitoring applications that provide something other than a network service. Host resource and general application monitoring is handled by either the Host Resources MIB [1] or the application MIB [2].
此MIB不尝试提供用于管理网络服务应用程序运行的一台或多台主机的设施，也不提供用于监视提供网络服务以外的应用程序的设施。主机资源和一般应用程序监视由主机资源MIB[1]或应用程序MIB[2]处理。
Table of Contents
目录
1 The SNMP Network Management Framework ....................... 2
2 Rationale for having a Network Services Monitoring MIB ...... 3
1 General Relationship to Other MIBs ........................ 4
2 Restriction of Scope ...................................... 4
3 Configuration Information ................................. 5
3 Application Objects ......................................... 5
4 Definitions ................................................. 5
5 Changes made since RFC 2248 ................................. 18
6 Acknowledgements ............................................ 18
7 References .................................................. 19
8 Security Considerations ..................................... 20
9 Author and Chair Addresses .................................. 21
10 Full Copyright Statement .................................... 22
1 The SNMP Network Management Framework ....................... 2
2 Rationale for having a Network Services Monitoring MIB ...... 3
1 General Relationship to Other MIBs ........................ 4
2 Restriction of Scope ...................................... 4
3 Configuration Information ................................. 5
3 Application Objects ......................................... 5
4 Definitions ................................................. 5
5 Changes made since RFC 2248 ................................. 18
6 Acknowledgements ............................................ 18
7 References .................................................. 19
8 Security Considerations ..................................... 20
9 Author and Chair Addresses .................................. 21
10 Full Copyright Statement .................................... 22
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [3].
o RFC 2571[3]中描述的总体架构。
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 [4], STD 16, RFC 1212 [5] and RFC 1215 [6]. The second version, called SMIv2, is described in STD 58, RFC 2578 [7], STD 58, RFC 2579 [8] and STD 58, RFC 2580 [9].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[4]、STD 16、RFC 1212[5]和RFC 1215[6]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[7]、STD 58、RFC 2579[8]和STD 58、RFC 2580[9]中进行了描述。
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 [10]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [11] and RFC 1906 [12]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [12], RFC 2572 [13] and RFC 2574 [14].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[10]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[11]和RFC 1906[12]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[12]、RFC 2572[13]和RFC 2574[14]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [10]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [15].
o 访问管理信息的协议操作。STD 15、RFC 1157[10]中描述了第一组协议操作和相关PDU格式。RFC 1905[15]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [16] and the view-based access control mechanism described in RFC 2575 [17].
o RFC 2573[16]中描述的一组基本应用程序和RFC 2575[17]中描述的基于视图的访问控制机制。
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 (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的语义。
Much effort has been expended in developing tools to manage lower layer network facilities. However, relatively little work has been done on managing application layer entities. It is neither efficient nor reasonable to manage all aspects of application layer entities using only lower layer information. Moreover, the difficulty of managing application entities in this way increases dramatically as application entities become more complex.
在开发管理低层网络设施的工具方面已经花费了大量精力。然而，在管理应用层实体方面所做的工作相对较少。仅使用较低层的信息来管理应用层实体的所有方面既不高效也不合理。此外，随着应用程序实体变得越来越复杂，以这种方式管理应用程序实体的难度急剧增加。
This leads to a substantial need to monitor applications which provide network services, particularly distributed components such as MTAs and DSAs, by monitoring specific aspects of the application itself. Reasons to monitor such components include but are not limited to measuring load, detecting broken connectivity, isolating system failures, and locating congestion.
这就需要通过监视应用程序本身的特定方面来监视提供网络服务的应用程序，特别是分布式组件，如MTA和DSA。监控这些组件的原因包括但不限于测量负载、检测断开的连接、隔离系统故障和定位拥塞。
In order to manage network service applications effectively two requirements must be met:
为了有效地管理网络服务应用程序，必须满足两个要求：
(1) It must be possible to monitor a large number of components (typical for a large organization).
(1) 必须能够监控大量组件（大型组织的典型情况）。
(2) Application monitoring must be integrated into general network management.
(2) 应用程序监视必须集成到通用网络管理中。
This specification defines simple read-only access; this is sufficient to determine up/down status and provide an indication of a broad class of operational problems.
本规范定义了简单的只读访问；这足以确定上升/下降状态，并提供一系列操作问题的指示。
This MIB is intended to only provide facilities common to the monitoring of any network service application. It does not provide all the facilities necessary to monitor any specific application. Each specific type of network service application is expected to have a MIB of its own that makes use of these common facilities.
此MIB仅用于提供监控任何网络服务应用程序的公用设施。它没有提供监控任何特定应用所需的所有设施。每个特定类型的网络服务应用程序都应该有自己的MIB，利用这些公共设施。
The framework provided here is very minimal; there is a lot more that could be done. For example:
这里提供的框架非常小；还有很多事情可以做。例如：
(1) General network service application configuration monitoring and control.
(1) 通用网络服务应用程序配置监视和控制。
(2) Detailed examination and modification of individual entries in service-specific request queues.
(2) 详细检查和修改特定于服务的请求队列中的单个条目。
(3) Probing to determine the status of a specific request (e.g., the location of a mail message with a specific message-id).
(3) 探测以确定特定请求的状态（例如，具有特定邮件id的邮件的位置）。
(4) Requesting that certain actions be performed (e.g., forcing an immediate connection and transfer of pending messages to some specific system).
(4) 请求执行某些操作（例如，强制立即连接并将挂起的消息传输到某个特定系统）。
All these capabilities are both impressive and useful. However, these capabilities would require provisions for strict security checking. These capabilities would also mandate a much more complex design, with many characteristics likely to be fairly implementation-specific. As a result such facilities are likely to be both contentious and difficult to implement.
所有这些能力都是令人印象深刻和有用的。然而，这些能力需要提供严格的安全检查。这些功能还要求进行更复杂的设计，其中许多特性可能相当特定于实现。因此，此类设施可能既有争议，又难以实施。
This document religiously keeps things simple and focuses on the basic monitoring aspect of managing applications providing network services. The goal here is to provide a framework which is simple, useful, and widely implementable.
本文档非常简单，重点介绍管理提供网络服务的应用程序的基本监控方面。这里的目标是提供一个简单、有用且可广泛实现的框架。
This MIB attempts to provide information about the operational aspects of an application. Further information about the actual configuration of a given application may be kept in other places; the applDirectoryName or applURL may be used to point to places where such information is kept.
此MIB尝试提供有关应用程序操作方面的信息。关于给定应用程序的实际配置的进一步信息可以保存在其他地方；applDirectoryName或applURL可用于指向保存此类信息的位置。
This MIB defines a set of general purpose attributes which would be appropriate for a range of applications that provide network services. Both OSI and non-OSI services can be accommodated. Additional tables defined in extensions to this MIB provide attributes specific to specific network services.
此MIB定义了一组通用属性，适用于提供网络服务的一系列应用程序。可以容纳OSI和非OSI服务。此MIB扩展中定义的其他表提供特定于特定网络服务的属性。
A table is defined which will have one row for each operational network service application on the system. The only static information held on the application is its name. All other static information should be obtained from various directory services. The applDirectoryName is an external key, which allows an SNMP MIB entry to be cleanly related to the X.500 Directory. In SNMP terms, the applications are grouped in a table called applTable, which is indexed by an integer key applIndex.
定义了一个表，该表将为系统上的每个操作网络服务应用程序提供一行。应用程序上保存的唯一静态信息是其名称。所有其他静态信息都应该从各种目录服务中获得。applDirectoryName是一个外部键，它允许SNMP MIB条目与X.500目录完全相关。在SNMP术语中，应用程序分组在一个名为applTable的表中，该表由整数键applIndex索引。
The type of the application will be determined by one or both of:
应用程序的类型将由以下一项或两项决定：
(1) Additional MIB variables specific to the applications.
(1) 特定于应用程序的其他MIB变量。
(2) An association to the application of a specific protocol.
(2) 特定协议应用的关联。
NETWORK-SERVICES-MIB DEFINITIONS ::= BEGIN
NETWORK-SERVICES-MIB DEFINITIONS ::= BEGIN
IMPORTS OBJECT-TYPE, Counter32, Gauge32, MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI TimeStamp, TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
从SNMPv2 SMI时间戳导入对象类型、计数器32、仪表32、模块标识、mib-2，从SNMPv2 TC导入文本约定，从SNMPv2 CONF导入对象组，从SNMP-FRAMEWORK-mib导入对象组；
application MODULE-IDENTITY LAST-UPDATED "200003030000Z" ORGANIZATION "IETF Mail and Directory Management Working Group"
应用模块-IDENTITY最后更新的“2000003030000Z”组织“IETF邮件和目录管理工作组”
CONTACT-INFO " Ned Freed
联系人信息“Ned Freed”
Postal: Innosoft International, Inc. 1050 Lakes Drive West Covina, CA 91790 US
邮政：美国加利福尼亚州科维纳湖大道西1050号Innosoft国际公司，邮编：91790
Tel: +1 626 919 3600
Fax: +1 626 919 3614
Tel: +1 626 919 3600
Fax: +1 626 919 3614
E-Mail: ned.freed@innosoft.com"
DESCRIPTION
"The MIB module describing network service applications"
REVISION "200003030000Z"
DESCRIPTION
"This revision, published in RFC 2788, changes a number of
DisplayStrings to SnmpAdminStrings. Note that this change
is not strictly supported by SMIv2. However, the alternative
of deprecating the old objects and defining new objects
would have a more adverse impact on backward compatibility
and interoperability, given the particular semantics of
these objects. The defining reference for distinguished
names has also been updated from RFC 1779 to RFC 2253."
REVISION "199905120000Z"
DESCRIPTION
"This revision fixes a few small technical problems found
in previous versions, mostly in regards to the conformance
groups for different versions of this MIB. No changes have
been made to the objects this MIB defines since RFC 2248."
REVISION "199708170000Z"
DESCRIPTION
"This revision, published in RFC 2248, adds the
applDescription and applURL objects, adds the quiescing
state to the applOperStatus object and renames the MIB
from the APPLICATION-MIB to the NETWORK-SERVICE-MIB."
REVISION "199311280000Z"
DESCRIPTION
"The original version of this MIB was published in RFC 1565"
::= {mib-2 27}
E-Mail: ned.freed@innosoft.com"
DESCRIPTION
"The MIB module describing network service applications"
REVISION "200003030000Z"
DESCRIPTION
"This revision, published in RFC 2788, changes a number of
DisplayStrings to SnmpAdminStrings. Note that this change
is not strictly supported by SMIv2. However, the alternative
of deprecating the old objects and defining new objects
would have a more adverse impact on backward compatibility
and interoperability, given the particular semantics of
these objects. The defining reference for distinguished
names has also been updated from RFC 1779 to RFC 2253."
REVISION "199905120000Z"
DESCRIPTION
"This revision fixes a few small technical problems found
in previous versions, mostly in regards to the conformance
groups for different versions of this MIB. No changes have
been made to the objects this MIB defines since RFC 2248."
REVISION "199708170000Z"
DESCRIPTION
"This revision, published in RFC 2248, adds the
applDescription and applURL objects, adds the quiescing
state to the applOperStatus object and renames the MIB
from the APPLICATION-MIB to the NETWORK-SERVICE-MIB."
REVISION "199311280000Z"
DESCRIPTION
"The original version of this MIB was published in RFC 1565"
::= {mib-2 27}
-- Textual conventions
--文本约定
-- DistinguishedName is used to refer to objects in the
-- directory.
-- DistinguishedName is used to refer to objects in the
-- directory.
DistinguishedName ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
DistinguishedName ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current DESCRIPTION "A Distinguished Name represented in accordance with RFC 2253, presented in the UTF-8 charset defined in RFC 2279." SYNTAX OCTET STRING (SIZE (0..255))
状态当前描述“根据RFC 2253表示的可分辨名称，以RFC 2279中定义的UTF-8字符集表示。”语法八位字符串（大小（0..255））
-- Uniform Resource Locators are stored in URLStrings.
--统一资源定位器存储在URL字符串中。
URLString ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"A Uniform Resource Locator represented in accordance
with RFCs 1738 and 2368, presented in the NVT ASCII
charset defined in RFC 854."
SYNTAX OCTET STRING (SIZE (0..255))
URLString ::= TEXTUAL-CONVENTION
DISPLAY-HINT "255a"
STATUS current
DESCRIPTION
"A Uniform Resource Locator represented in accordance
with RFCs 1738 and 2368, presented in the NVT ASCII
charset defined in RFC 854."
SYNTAX OCTET STRING (SIZE (0..255))
-- The basic applTable contains a list of the application
-- entities.
-- The basic applTable contains a list of the application
-- entities.
applTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding objects which apply to all different
kinds of applications providing network services.
Each network service application capable of being
monitored should have a single entry in this table."
::= {application 1}
applTable OBJECT-TYPE
SYNTAX SEQUENCE OF ApplEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding objects which apply to all different
kinds of applications providing network services.
Each network service application capable of being
monitored should have a single entry in this table."
::= {application 1}
applEntry OBJECT-TYPE
SYNTAX ApplEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry associated with a single network service
application."
INDEX {applIndex}
::= {applTable 1}
applEntry OBJECT-TYPE
SYNTAX ApplEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry associated with a single network service
application."
INDEX {applIndex}
::= {applTable 1}
ApplEntry ::= SEQUENCE {
applIndex
INTEGER,
applName
SnmpAdminString,
applDirectoryName
ApplEntry ::= SEQUENCE {
applIndex
INTEGER,
applName
SnmpAdminString,
applDirectoryName
DistinguishedName, applVersion SnmpAdminString, applUptime TimeStamp, applOperStatus INTEGER, applLastChange TimeStamp, applInboundAssociations Gauge32, applOutboundAssociations Gauge32, applAccumulatedInboundAssociations Counter32, applAccumulatedOutboundAssociations Counter32, applLastInboundActivity TimeStamp, applLastOutboundActivity TimeStamp, applRejectedInboundAssociations Counter32, applFailedOutboundAssociations Counter32, applDescription SnmpAdminString, applURL URLString }
区分名称、applVersion SNMPAdminInstalling、applUptime时间戳、applOperStatus整数、applLastChange时间戳、applInboundAssociations量表32、applOutboundAssociations量表32、ApplAccumeratedBoundAssociations计数器32、applLastInboundActivity时间戳、applLastOutboundActivity时间戳、，applRejectedInboundAssociations计数器32，applFailedOutboundAssociations计数器32，applDescription SNMPAdministring，applURL URLString}
applIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index to uniquely identify the network service
application. This attribute is the index used for
lexicographic ordering of the table."
::= {applEntry 1}
applIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index to uniquely identify the network service
application. This attribute is the index used for
lexicographic ordering of the table."
::= {applEntry 1}
applName OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The name the network service application chooses to be known by."
applName对象类型语法SnmpAdminString MAX-ACCESS只读状态当前描述“网络服务应用程序选择的已知名称。”
::= {applEntry 2}
::= {applEntry 2}
applDirectoryName OBJECT-TYPE
SYNTAX DistinguishedName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Distinguished Name of the directory entry where
static information about this application is stored.
An empty string indicates that no information about
the application is available in the directory."
::= {applEntry 3}
applDirectoryName OBJECT-TYPE
SYNTAX DistinguishedName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Distinguished Name of the directory entry where
static information about this application is stored.
An empty string indicates that no information about
the application is available in the directory."
::= {applEntry 3}
applVersion OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The version of network service application software.
This field is usually defined by the vendor of the
network service application software."
::= {applEntry 4}
applUptime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the network service
application was last initialized. If the application was
last initialized prior to the last initialization of the
network management subsystem, then this object contains
a zero value."
::= {applEntry 5}
applVersion OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The version of network service application software.
This field is usually defined by the vendor of the
network service application software."
::= {applEntry 4}
applUptime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the network service
application was last initialized. If the application was
last initialized prior to the last initialization of the
network management subsystem, then this object contains
a zero value."
::= {applEntry 5}
applOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2),
halted(3),
congested(4),
restarting(5),
quiescing(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the operational status of the network service
application. 'down' indicates that the network service is
applOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1),
down(2),
halted(3),
congested(4),
restarting(5),
quiescing(6)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the operational status of the network service
application. 'down' indicates that the network service is
not available. 'up' indicates that the network service
is operational and available. 'halted' indicates that the
service is operational but not available. 'congested'
indicates that the service is operational but no additional
inbound associations can be accommodated. 'restarting'
indicates that the service is currently unavailable but is
in the process of restarting and will be available soon.
'quiescing' indicates that service is currently operational
but is in the process of shutting down. Additional inbound
associations may be rejected by applications in the
'quiescing' state."
::= {applEntry 6}
not available. 'up' indicates that the network service
is operational and available. 'halted' indicates that the
service is operational but not available. 'congested'
indicates that the service is operational but no additional
inbound associations can be accommodated. 'restarting'
indicates that the service is currently unavailable but is
in the process of restarting and will be available soon.
'quiescing' indicates that service is currently operational
but is in the process of shutting down. Additional inbound
associations may be rejected by applications in the
'quiescing' state."
::= {applEntry 6}
applLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the network service
application entered its current operational state. If
the current state was entered prior to the last
initialization of the local network management subsystem,
then this object contains a zero value."
::= {applEntry 7}
applLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time the network service
application entered its current operational state. If
the current state was entered prior to the last
initialization of the local network management subsystem,
then this object contains a zero value."
::= {applEntry 7}
applInboundAssociations OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of current associations to the network service
application, where it is the responder. An inbound
association occurs when another application successfully
connects to this one."
::= {applEntry 8}
applInboundAssociations OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of current associations to the network service
application, where it is the responder. An inbound
association occurs when another application successfully
connects to this one."
::= {applEntry 8}
applOutboundAssociations OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of current associations to the network service
application, where it is the initiator. An outbound
association occurs when this application successfully
connects to another one."
::= {applEntry 9}
applOutboundAssociations OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of current associations to the network service
application, where it is the initiator. An outbound
association occurs when this application successfully
connects to another one."
::= {applEntry 9}
applAccumulatedInboundAssociations OBJECT-TYPE
AppledBoundAssociations对象类型
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of associations to the application entity
since application initialization, where it was the responder."
::= {applEntry 10}
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of associations to the application entity
since application initialization, where it was the responder."
::= {applEntry 10}
applAccumulatedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of associations to the application entity
since application initialization, where it was the initiator."
::= {applEntry 11}
applAccumulatedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of associations to the application entity
since application initialization, where it was the initiator."
::= {applEntry 11}
applLastInboundActivity OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this application last
had an inbound association. If the last association
occurred prior to the last initialization of the network
subsystem, then this object contains a zero value."
::= {applEntry 12}
applLastInboundActivity OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this application last
had an inbound association. If the last association
occurred prior to the last initialization of the network
subsystem, then this object contains a zero value."
::= {applEntry 12}
applLastOutboundActivity OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this application last
had an outbound association. If the last association
occurred prior to the last initialization of the network
subsystem, then this object contains a zero value."
::= {applEntry 13}
applLastOutboundActivity OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this application last
had an outbound association. If the last association
occurred prior to the last initialization of the network
subsystem, then this object contains a zero value."
::= {applEntry 13}
applRejectedInboundAssociations OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The total number of inbound associations the application entity has rejected, since application initialization. Rejected associations are not counted in the accumulated association totals. Note that this only counts
applRejectedInboundAssociations对象类型语法计数器32 MAX-ACCESS只读状态当前描述“自应用程序初始化以来，应用程序实体已拒绝的入站关联总数。拒绝的关联不计入累计关联总数。请注意，这仅计算
associations the application entity has rejected itself;
it does not count rejections that occur at lower layers
of the network. Thus, this counter may not reflect the
true number of failed inbound associations."
::= {applEntry 14}
associations the application entity has rejected itself;
it does not count rejections that occur at lower layers
of the network. Thus, this counter may not reflect the
true number of failed inbound associations."
::= {applEntry 14}
applFailedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number associations where the application entity
is initiator and association establishment has failed,
since application initialization. Failed associations are
not counted in the accumulated association totals."
::= {applEntry 15}
applFailedOutboundAssociations OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number associations where the application entity
is initiator and association establishment has failed,
since application initialization. Failed associations are
not counted in the accumulated association totals."
::= {applEntry 15}
applDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A text description of the application. This information
is intended to identify and briefly describe the
application in a status display."
::= {applEntry 16}
applDescription OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A text description of the application. This information
is intended to identify and briefly describe the
application in a status display."
::= {applEntry 16}
applURL OBJECT-TYPE
SYNTAX URLString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A URL pointing to a description of the application.
This information is intended to identify and describe
the application in a status display."
::= {applEntry 17}
applURL OBJECT-TYPE
SYNTAX URLString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A URL pointing to a description of the application.
This information is intended to identify and describe
the application in a status display."
::= {applEntry 17}
-- The assocTable augments the information in the applTable
-- with information about associations. Note that two levels
-- of compliance are specified below, depending on whether
-- association monitoring is mandated.
-- The assocTable augments the information in the applTable
-- with information about associations. Note that two levels
-- of compliance are specified below, depending on whether
-- association monitoring is mandated.
assocTable OBJECT-TYPE SYNTAX SEQUENCE OF AssocEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table holding a set of all active application
assocTable对象类型语法序列AssocEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“包含一组所有活动应用程序的表
associations."
::= {application 2}
associations."
::= {application 2}
assocEntry OBJECT-TYPE
SYNTAX AssocEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry associated with an association for a network
service application."
INDEX {applIndex, assocIndex}
::= {assocTable 1}
assocEntry OBJECT-TYPE
SYNTAX AssocEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry associated with an association for a network
service application."
INDEX {applIndex, assocIndex}
::= {assocTable 1}
AssocEntry ::= SEQUENCE {
assocIndex
INTEGER,
assocRemoteApplication
SnmpAdminString,
assocApplicationProtocol
OBJECT IDENTIFIER,
assocApplicationType
INTEGER,
assocDuration
TimeStamp
}
AssocEntry ::= SEQUENCE {
assocIndex
INTEGER,
assocRemoteApplication
SnmpAdminString,
assocApplicationProtocol
OBJECT IDENTIFIER,
assocApplicationType
INTEGER,
assocDuration
TimeStamp
}
assocIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index to uniquely identify each association for a network
service application. This attribute is the index that is
used for lexicographic ordering of the table. Note that the
table is also indexed by the applIndex."
::= {assocEntry 1}
assocIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An index to uniquely identify each association for a network
service application. This attribute is the index that is
used for lexicographic ordering of the table. Note that the
table is also indexed by the applIndex."
::= {assocEntry 1}
assocRemoteApplication OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the system running remote network service application. For an IP-based application this should be either a domain name or IP address. For an OSI application it should be the string encoded distinguished name of the managed object. For X.400(1984) MTAs which do not have a Distinguished Name, the RFC 2156 syntax 'mta in
assocRemoteApplication对象类型语法SNMPAdministring MAX-ACCESS只读状态当前说明“运行远程网络服务应用程序的系统的名称。对于基于IP的应用程序，这应该是域名或IP地址。对于OSI应用程序，它应该是托管对象的字符串编码的可分辨名称。对于没有可分辨名称的X.400（1984）mta，RFC 2156语法“mta in”
globalid' used in X400-Received: fields can be used. Note,
however, that not all connections an MTA makes are
necessarily to another MTA."
::= {assocEntry 2}
globalid' used in X400-Received: fields can be used. Note,
however, that not all connections an MTA makes are
necessarily to another MTA."
::= {assocEntry 2}
assocApplicationProtocol OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An identification of the protocol being used for the
application. For an OSI Application, this will be the
Application Context. For Internet applications, OID
values of the form {applTCPProtoID port} or {applUDPProtoID
port} are used for TCP-based and UDP-based protocols,
respectively. In either case 'port' corresponds to the
primary port number being used by the protocol. The
usual IANA procedures may be used to register ports for
new protocols."
::= {assocEntry 3}
assocApplicationProtocol OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An identification of the protocol being used for the
application. For an OSI Application, this will be the
Application Context. For Internet applications, OID
values of the form {applTCPProtoID port} or {applUDPProtoID
port} are used for TCP-based and UDP-based protocols,
respectively. In either case 'port' corresponds to the
primary port number being used by the protocol. The
usual IANA procedures may be used to register ports for
new protocols."
::= {assocEntry 3}
assocApplicationType OBJECT-TYPE
SYNTAX INTEGER {
uainitiator(1),
uaresponder(2),
peerinitiator(3),
peerresponder(4)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This indicates whether the remote application is some type of
client making use of this network service (e.g., a Mail User
Agent) or a server acting as a peer. Also indicated is whether
the remote end initiated an incoming connection to the network
service or responded to an outgoing connection made by the
local application. MTAs and messaging gateways are
considered to be peers for the purposes of this variable."
::= {assocEntry 4}
assocApplicationType OBJECT-TYPE
SYNTAX INTEGER {
uainitiator(1),
uaresponder(2),
peerinitiator(3),
peerresponder(4)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This indicates whether the remote application is some type of
client making use of this network service (e.g., a Mail User
Agent) or a server acting as a peer. Also indicated is whether
the remote end initiated an incoming connection to the network
service or responded to an outgoing connection made by the
local application. MTAs and messaging gateways are
considered to be peers for the purposes of this variable."
::= {assocEntry 4}
assocDuration OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time this association was started. If this association started prior to the last initialization of the network subsystem, then this object contains a zero value."
assocDuration对象类型语法TimeStamp MAX-ACCESS只读状态当前描述“启动此关联时的sysUpTime值。如果此关联在网络子系统上次初始化之前启动，则此对象包含零值。”
::= {assocEntry 5}
::= {assocEntry 5}
-- Conformance information
--一致性信息
applConformance OBJECT IDENTIFIER ::= {application 3}
applConformance OBJECT IDENTIFIER ::= {application 3}
applGroups OBJECT IDENTIFIER ::= {applConformance 1}
applCompliances OBJECT IDENTIFIER ::= {applConformance 2}
applGroups OBJECT IDENTIFIER ::= {applConformance 1}
applCompliances OBJECT IDENTIFIER ::= {applConformance 2}
-- Compliance statements
--合规声明
applCompliance MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement for RFC 1565 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications.
This is the basic compliance statement for RFC 1565."
MODULE
MANDATORY-GROUPS {applRFC1565Group}
::= {applCompliances 1}
applCompliance MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement for RFC 1565 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications.
This is the basic compliance statement for RFC 1565."
MODULE
MANDATORY-GROUPS {applRFC1565Group}
::= {applCompliances 1}
assocCompliance MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement for RFC 1565 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications
and their associations."
MODULE
MANDATORY-GROUPS {applRFC1565Group, assocRFC1565Group}
::= {applCompliances 2}
assocCompliance MODULE-COMPLIANCE
STATUS obsolete
DESCRIPTION
"The compliance statement for RFC 1565 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications
and their associations."
MODULE
MANDATORY-GROUPS {applRFC1565Group, assocRFC1565Group}
::= {applCompliances 2}
applRFC2248Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for RFC 2248 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications."
MODULE
MANDATORY-GROUPS {applRFC2248Group}
::= {applCompliances 3}
applRFC2248Compliance MODULE-COMPLIANCE
STATUS deprecated
DESCRIPTION
"The compliance statement for RFC 2248 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications."
MODULE
MANDATORY-GROUPS {applRFC2248Group}
::= {applCompliances 3}
assocRFC2248Compliance MODULE-COMPLIANCE STATUS deprecated DESCRIPTION "The compliance statement for RFC 2248 implementations
ASSOCRFC2248合规性模块-合规性状态已弃用说明“RFC 2248实施的合规性声明
which support the Network Services Monitoring MIB for
basic monitoring of network service applications and
their associations."
MODULE
MANDATORY-GROUPS {applRFC2248Group, assocRFC2248Group}
::= {applCompliances 4}
which support the Network Services Monitoring MIB for
basic monitoring of network service applications and
their associations."
MODULE
MANDATORY-GROUPS {applRFC2248Group, assocRFC2248Group}
::= {applCompliances 4}
applRFC2788Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for RFC 2788 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications."
MODULE
MANDATORY-GROUPS {applRFC2788Group}
::= {applCompliances 5}
applRFC2788Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for RFC 2788 implementations
which support the Network Services Monitoring MIB
for basic monitoring of network service applications."
MODULE
MANDATORY-GROUPS {applRFC2788Group}
::= {applCompliances 5}
assocRFC2788Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for RFC 2788 implementations
which support the Network Services Monitoring MIB for
basic monitoring of network service applications and
their associations."
MODULE
MANDATORY-GROUPS {applRFC2788Group, assocRFC2788Group}
::= {applCompliances 6}
assocRFC2788Compliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for RFC 2788 implementations
which support the Network Services Monitoring MIB for
basic monitoring of network service applications and
their associations."
MODULE
MANDATORY-GROUPS {applRFC2788Group, assocRFC2788Group}
::= {applCompliances 6}
-- Units of conformance
--一致性单位
applRFC1565Group OBJECT-GROUP
OBJECTS {
applName, applVersion, applUptime, applOperStatus,
applLastChange, applInboundAssociations,
applOutboundAssociations, applAccumulatedInboundAssociations,
applAccumulatedOutboundAssociations, applLastInboundActivity,
applLastOutboundActivity, applRejectedInboundAssociations,
applFailedOutboundAssociations}
STATUS obsolete
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications. This is the original set
of such objects defined in RFC 1565."
::= {applGroups 7}
applRFC1565Group OBJECT-GROUP
OBJECTS {
applName, applVersion, applUptime, applOperStatus,
applLastChange, applInboundAssociations,
applOutboundAssociations, applAccumulatedInboundAssociations,
applAccumulatedOutboundAssociations, applLastInboundActivity,
applLastOutboundActivity, applRejectedInboundAssociations,
applFailedOutboundAssociations}
STATUS obsolete
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications. This is the original set
of such objects defined in RFC 1565."
::= {applGroups 7}
assocRFC1565Group OBJECT-GROUP OBJECTS {
ASSOCRFC1565组对象-组对象{
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS obsolete
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations. This is the
original set of such objects defined in RFC 1565."
::= {applGroups 2}
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS obsolete
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations. This is the
original set of such objects defined in RFC 1565."
::= {applGroups 2}
applRFC2248Group OBJECT-GROUP
OBJECTS {
applName, applVersion, applUptime, applOperStatus,
applLastChange, applInboundAssociations,
applOutboundAssociations, applAccumulatedInboundAssociations,
applAccumulatedOutboundAssociations, applLastInboundActivity,
applLastOutboundActivity, applRejectedInboundAssociations,
applFailedOutboundAssociations, applDescription, applURL}
STATUS deprecated
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications. This group was originally
defined in RFC 2248; note that applDirectoryName is
missing."
::= {applGroups 3}
applRFC2248Group OBJECT-GROUP
OBJECTS {
applName, applVersion, applUptime, applOperStatus,
applLastChange, applInboundAssociations,
applOutboundAssociations, applAccumulatedInboundAssociations,
applAccumulatedOutboundAssociations, applLastInboundActivity,
applLastOutboundActivity, applRejectedInboundAssociations,
applFailedOutboundAssociations, applDescription, applURL}
STATUS deprecated
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications. This group was originally
defined in RFC 2248; note that applDirectoryName is
missing."
::= {applGroups 3}
assocRFC2248Group OBJECT-GROUP
OBJECTS {
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS deprecated
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations. This group
was originally defined by RFC 2248."
::= {applGroups 4}
assocRFC2248Group OBJECT-GROUP
OBJECTS {
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS deprecated
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations. This group
was originally defined by RFC 2248."
::= {applGroups 4}
applRFC2788Group OBJECT-GROUP
OBJECTS {
applName, applDirectoryName, applVersion, applUptime,
applOperStatus, applLastChange, applInboundAssociations,
applOutboundAssociations, applAccumulatedInboundAssociations,
applAccumulatedOutboundAssociations, applLastInboundActivity,
applLastOutboundActivity, applRejectedInboundAssociations,
applFailedOutboundAssociations, applDescription, applURL}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications. This is the appropriate
applRFC2788Group OBJECT-GROUP
OBJECTS {
applName, applDirectoryName, applVersion, applUptime,
applOperStatus, applLastChange, applInboundAssociations,
applOutboundAssociations, applAccumulatedInboundAssociations,
applAccumulatedOutboundAssociations, applLastInboundActivity,
applLastOutboundActivity, applRejectedInboundAssociations,
applFailedOutboundAssociations, applDescription, applURL}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications. This is the appropriate
group for RFC 2788 -- it adds the applDirectoryName object
missing in RFC 2248."
::= {applGroups 5}
group for RFC 2788 -- it adds the applDirectoryName object
missing in RFC 2248."
::= {applGroups 5}
assocRFC2788Group OBJECT-GROUP
OBJECTS {
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations. This is
the appropriate group for RFC 2788."
::= {applGroups 6}
assocRFC2788Group OBJECT-GROUP
OBJECTS {
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations. This is
the appropriate group for RFC 2788."
::= {applGroups 6}
-- OIDs of the form {applTCPProtoID port} are intended to be used
-- for TCP-based protocols that don't have OIDs assigned by other
-- means. {applUDPProtoID port} serves the same purpose for
-- UDP-based protocols. In either case 'port' corresponds to
-- the primary port number being used by the protocol. For example,
-- assuming no other OID is assigned for SMTP, an OID of
-- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
-- protocol that uses port 25 as its primary port.
-- OIDs of the form {applTCPProtoID port} are intended to be used
-- for TCP-based protocols that don't have OIDs assigned by other
-- means. {applUDPProtoID port} serves the same purpose for
-- UDP-based protocols. In either case 'port' corresponds to
-- the primary port number being used by the protocol. For example,
-- assuming no other OID is assigned for SMTP, an OID of
-- {applTCPProtoID 25} could be used, since SMTP is a TCP-based
-- protocol that uses port 25 as its primary port.
applTCPProtoID OBJECT IDENTIFIER ::= {application 4}
applUDPProtoID OBJECT IDENTIFIER ::= {application 5}
applTCPProtoID OBJECT IDENTIFIER ::= {application 4}
applUDPProtoID OBJECT IDENTIFIER ::= {application 5}
END
终止
This revision corrects a few minor technical errors in the construction of the network services MIB in RFC 2248 [22]. In addition, the applName, applVersion, and applDescription fields have been changed from DisplayStrings to SnmpAdminStrings. The reference to RFC 1779 has also been updated to RFC 2253, which in turn adds the ability for distinguished names to be in the UTF-8 character set.
本次修订修正了RFC 2248[22]中网络服务MIB构造中的一些小技术错误。此外，applName、applVersion和applDescription字段已从DisplayString更改为SNMPAdminString。对RFC 1779的引用也已更新为RFC 2253，这反过来又增加了可分辨名称在UTF-8字符集中的能力。
This document is a product of the Mail and Directory Management (MADMAN) Working Group. It is based on an earlier MIB designed by S. Kille, T. Lenggenhager, D. Partain, and W. Yeong. The Electronic Mail Association's TSC committee was instrumental in providing feedback on and suggesting enhancements to RFC 1565 [23] that have led to the present document.
本文档是邮件和目录管理（MADMAN）工作组的产品。它基于S.Kille、T.Lenggenhager、D.Partain和W.Yeong设计的早期MIB。电子邮件协会的TSC委员会有助于对RFC 1565[23]提供反馈并提出改进建议，从而形成本文件。
[1] Grillo, P. and S. Waldbusser, "Host Resources MIB", RFC 1514, September 1993.
[1] Grillo，P.和S.Waldbusser，“主机资源MIB”，RFC 15141993年9月。
[2] Krupczak, C. and J. Saperia, "Definitions of System-Level Managed Objects for Applications", RFC 2287, February 1998.
[2] Krupczak，C.和J.Saperia，“应用程序系统级托管对象的定义”，RFC 2287，1998年2月。
[3] Wijnen, B., Harrington, D. and R. Presuhn, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[3] Wijnen，B.，Harrington，D.和R.Presuhn，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[4] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[4] Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[5] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[5] Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[6] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[6] Rose，M.“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[7] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[7] McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[8] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[8] McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[9] McCloghrie, K., Perkins, D. and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[9] McCloghrie，K.，Perkins，D.和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[10] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[10] Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[11] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[11] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[12] 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.
[12] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[13] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[13] Case，J.，Harrington D.，Presohn R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[14] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[14] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[15] 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.
[15] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[16] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[16] Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC2573，1999年4月。
[17] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[17] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC2575，1999年4月。
[18] Wahl, M., Kille, S. and T.Howes, "Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names", RFC 2253, December 1997.
[18] Wahl，M.，Kille，S.和T.Howes，“轻量级目录访问协议（v3）：可分辨名称的UTF-8字符串表示”，RFC 2253，1997年12月。
[19] Kille, S., "Mapping between X.400(1988) and RFC 822/MIME", RFC 2156, January 1998.
[19] Kille，S.，“X.400（1988）和RFC 822/MIME之间的映射”，RFC 2156，1998年1月。
[20] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[20] Berners Lee，T.，Masinter，L.和M.McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。
[21] Hoffman, P., Masinter, L. and J. Zawinski, "The mailto URL Scheme", RFC 2368, July 1998.
[21] Hoffman，P.，Masinter，L.和J.Zawinski，“邮件URL方案”，RFC 2368，1998年7月。
[22] Freed, N. and S. Kille, "Network Services Monitoring MIB", RFC 2248, January 1998.
[22] Freed，N.和S.Kille，“网络服务监控MIB”，RFC 2248，1998年1月。
[23] Freed, N. and Kille, "Network Services Monitoring MIB", RFC 1565, January 1994.
[23] Freed，N.和Kille，“网络服务监控MIB”，RFC15651994年1月。
[29] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD 8, RFC 854, RFC 855, May 1983.
[29] Postel，J.和J.Reynolds，“Telnet协议规范”，STD 8，RFC 854，RFC 855，1983年5月。
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 operations.
此MIB中未定义具有读写和/或读创建MAX-ACCESS子句的管理对象。因此，如果此MIB正确实现，则入侵者不会通过直接的SNMP集操作更改或创建此MIB的任何管理对象。
However, this MIB does provide passive information about the existence, type, and configuration of applications on a given host that could potentially indicate some sort of vulnerability. Finally, the information MIB provides about network usage could be used to analyze network traffic patterns.
但是，此MIB确实提供有关给定主机上应用程序的存在、类型和配置的被动信息，这些信息可能表示存在某种漏洞。最后，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 2574 [14] and the View-based Access Control Model RFC 2575 [17] is recommended.
建议实施者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC 2574[14]和基于视图的访问控制模型RFC 2575[17]。
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实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
Ned Freed Innosoft International, Inc. 1050 Lakes Drive West Covina, CA 91790 USA
Ned Freed Innosoft International，Inc.美国加利福尼亚州西科维纳湖大道1050号，邮编：91790
Phone: +1 626 919 3600
Fax: +1 626 919 3614
EMail: ned.freed@innosoft.com
Phone: +1 626 919 3600
Fax: +1 626 919 3614
EMail: ned.freed@innosoft.com
Steve Kille, MADMAN WG Chair MessagingDirect Ltd. The Dome, The Square Richmond TW9 1DT UK
Steve Kille，MADMAN工作组主席MessagingDirect Ltd.英国里士满TW9 1DT广场穹顶
Phone: +44 20 8332 9091
EMail: Steve.Kille@MessagingDirect.com
Phone: +44 20 8332 9091
EMail: Steve.Kille@MessagingDirect.com
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。