Network Working Group N. Freed
Request for Comments: 2248 Innosoft
Obsoletes: 1565 S. Kille
Category: Standards Track ISODE Consortium
January 1998
Network Working Group N. Freed
Request for Comments: 2248 Innosoft
Obsoletes: 1565 S. Kille
Category: Standards Track ISODE Consortium
January 1998
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 (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
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 the Host Resources MIB at present; development of an additional application MIB is currently underway in the IETF.
此MIB不尝试提供用于管理网络服务应用程序运行的一台或多台主机的设施，也不提供用于监视提供网络服务以外的应用程序的设施。主机资源和一般应用监控目前由主机资源MIB处理；IETF目前正在开发另一个应用程序MIB。
1 Introduction ............................................... 1
2 Table of Contents .......................................... 2
3 The SNMPv2 Network Management Framework .................... 2
3.1 Object Definitions ....................................... 3
4 Rationale for having a Network Services Monitoring MIB ..... 3
4.1 General Relationship to Other MIBs ....................... 4
4.2 Restriction of Scope ..................................... 4
4.3 Configuration Information ................................ 4
5 Application Objects ........................................ 5
6 Definitions ................................................ 5
7 Changes made since RFC 1565 ................................ 16
8 Acknowledgements ........................................... 16
9 References ................................................. 16
10 Security Considerations ................................... 17
11 Author and Chair Addresses ................................ 18
12 Full Copyright Statement .................................. 19
1 Introduction ............................................... 1
2 Table of Contents .......................................... 2
3 The SNMPv2 Network Management Framework .................... 2
3.1 Object Definitions ....................................... 3
4 Rationale for having a Network Services Monitoring MIB ..... 3
4.1 General Relationship to Other MIBs ....................... 4
4.2 Restriction of Scope ..................................... 4
4.3 Configuration Information ................................ 4
5 Application Objects ........................................ 5
6 Definitions ................................................ 5
7 Changes made since RFC 1565 ................................ 16
8 Acknowledgements ........................................... 16
9 References ................................................. 16
10 Security Considerations ................................... 17
11 Author and Chair Addresses ................................ 18
12 Full Copyright Statement .................................. 19
The SNMPv2 Network Management Framework consists of seven major components. They are:
SNMPv2网络管理框架由七个主要组件组成。他们是：
o RFC 1902 [1] which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management.
o RFC 1902[1]定义了SMI，即用于描述和命名对象以进行管理的机制。
o RFC 1903 [2] defines textual conventions for SNMPv2.
o RFC 1903[2]定义了SNMPv2的文本约定。
o RFC 1904 [3] defines conformance statements for SNMPv2.
o RFC 1904[3]定义了SNMPv2的一致性声明。
o RFC 1905 [4] defines transport mappings for SNMPv2.
o RFC 1905[4]定义了SNMPv2的传输映射。
o RFC 1906 [5] defines the protocol operations used for network access to managed objects.
o RFC 1906[5]定义了用于对受管对象进行网络访问的协议操作。
o RFC 1907 [6] defines the Management Information Base for SNMPv2.
o RFC 1907[6]定义了SNMPv2的管理信息库。
o RFC 1908 [7] specifies coexistance between SNMP and SNMPv2.
o RFC 1908[7]规定了SNMP和SNMPv2之间的共存性。
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
该框架允许为实验和评估目的定义新对象。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的抽象语法表示法1（ASN.1）的子集定义的。特别是，每个对象类型都由一个对象标识符命名，这是一个管理分配的名称。对象类型与对象实例一起用于唯一标识对象的特定实例化。为了方便起见，我们经常使用一个称为描述符的文本字符串来引用对象类型。
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 accomodated. 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 DisplayString, TimeStamp, TEXTUAL-CONVENTION FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
从SNMPv2 SMI DisplayString中导入对象类型、计数器32、仪表32、模块标识、mib-2，从SNMPv2 TC MODULE-COMPLIANCE中导入时间戳、文本约定，从SNMPv2 CONF中导入对象组；
application MODULE-IDENTITY LAST-UPDATED "9708170000Z" ORGANIZATION "IETF Mail and Directory Management Working Group" CONTACT-INFO " Ned Freed
应用模块标识最后更新的“970870000Z”组织“IETF邮件和目录管理工作组”联系人信息
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 "9311280000Z"
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 "9311280000Z"
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
STATUS current
DESCRIPTION
"A Distinguished Name represented in accordance with
RFC 1779 [8]."
SYNTAX DisplayString
DistinguishedName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A Distinguished Name represented in accordance with
RFC 1779 [8]."
SYNTAX DisplayString
-- Uniform Resource Locators are stored in URLStrings.
--统一资源定位器存储在URL字符串中。
URLString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A Uniform Resource Locator represented in accordance
with RFC 1738 [10]."
SYNTAX DisplayString
URLString ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A Uniform Resource Locator represented in accordance
with RFC 1738 [10]."
SYNTAX DisplayString
-- 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
applEntry对象类型语法applEntry MAX-ACCESS不可访问状态当前描述
"An entry associated with a single network service
application."
INDEX {applIndex}
::= {applTable 1}
"An entry associated with a single network service
application."
INDEX {applIndex}
::= {applTable 1}
ApplEntry ::= SEQUENCE {
applIndex
INTEGER,
applName
DisplayString,
applDirectoryName
DistinguishedName,
applVersion
DisplayString,
applUptime
TimeStamp,
applOperStatus
INTEGER,
applLastChange
TimeStamp,
applInboundAssociations
Gauge32,
applOutboundAssociations
Gauge32,
applAccumulatedInboundAssociations
Counter32,
applAccumulatedOutboundAssociations
Counter32,
applLastInboundActivity
TimeStamp,
applLastOutboundActivity
TimeStamp,
applRejectedInboundAssociations
Counter32,
applFailedOutboundAssociations
Counter32,
applDescription
DisplayString,
applURL
URLString
}
ApplEntry ::= SEQUENCE {
applIndex
INTEGER,
applName
DisplayString,
applDirectoryName
DistinguishedName,
applVersion
DisplayString,
applUptime
TimeStamp,
applOperStatus
INTEGER,
applLastChange
TimeStamp,
applInboundAssociations
Gauge32,
applOutboundAssociations
Gauge32,
applAccumulatedInboundAssociations
Counter32,
applAccumulatedOutboundAssociations
Counter32,
applLastInboundActivity
TimeStamp,
applLastOutboundActivity
TimeStamp,
applRejectedInboundAssociations
Counter32,
applFailedOutboundAssociations
Counter32,
applDescription
DisplayString,
applURL
URLString
}
applIndex OBJECT-TYPE SYNTAX INTEGER (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "An index to uniquely identify the network service
applIndex对象类型语法整数（1..2147483647）MAX-ACCESS not ACCESS STATUS current DESCRIPTION“唯一标识网络服务的索引
application. This attribute is the index used for lexicographic ordering of the table."
应用此属性是用于表的词典排序的索引。”
::= {applEntry 1}
::= {applEntry 1}
applName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name the network service application chooses to be
known by."
::= {applEntry 2}
applName OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name the network service application chooses to be
known by."
::= {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 DisplayString
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}
applVersion OBJECT-TYPE
SYNTAX DisplayString
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}
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
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 accomodated. '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}
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 accomodated. '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 assocation occurs when a another application successfully connects to this one."
applInboundAssociations对象类型语法量表32 MAX-ACCESS只读状态当前描述“网络服务应用程序的当前关联数，它是响应程序。当另一个应用程序成功连接到此应用程序时，将发生入站关联。”
::= {applEntry 8}
::= {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
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}
applAccumulatedInboundAssociations 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 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
applLastOutboundActivity对象类型语法时间戳MAX-ACCESS只读状态当前描述“此应用程序上次运行时的系统正常运行时间值
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}
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
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}
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
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 DisplayString
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 DisplayString
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
applURL对象类型语法URLString MAX-ACCESS只读状态当前描述“指向应用程序描述的URL。此信息旨在识别和描述
the application in a status display."
::= {applEntry 17}
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
associations."
::= {application 2}
assocTable OBJECT-TYPE
SYNTAX SEQUENCE OF AssocEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table holding a set of all active application
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
DisplayString,
assocApplicationProtocol
OBJECT IDENTIFIER,
assocApplicationType
INTEGER,
assocDuration
TimeStamp
}
AssocEntry ::= SEQUENCE {
assocIndex
INTEGER,
assocRemoteApplication
DisplayString,
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
AssociIndex对象类型语法整数（1..2147483647）MAX-ACCESS不可访问状态当前描述“唯一标识网络服务应用程序的每个关联的索引。此属性是
used for lexicographic ordering of the table. Note that the
table is also indexed by the applIndex."
::= {assocEntry 1}
used for lexicographic ordering of the table. Note that the
table is also indexed by the applIndex."
::= {assocEntry 1}
assocRemoteApplication OBJECT-TYPE
SYNTAX DisplayString
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 1327 [9] syntax
'mta in globalid' should be used. Note, however, that not
all connections an MTA are necessarily to another MTA."
::= {assocEntry 2}
assocRemoteApplication OBJECT-TYPE
SYNTAX DisplayString
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 1327 [9] syntax
'mta in globalid' should be used. Note, however, that not
all connections an MTA 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, the IANA
maintains a registry of the OIDs which correspond to
well-known applications. If the application protocol is
not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID 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."
::= {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, the IANA
maintains a registry of the OIDs which correspond to
well-known applications. If the application protocol is
not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID 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."
::= {assocEntry 3}
assocApplicationType OBJECT-TYPE
SYNTAX INTEGER {
ua-initiator(1),
ua-responder(2),
peer-initiator(3),
peer-responder(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
assocApplicationType OBJECT-TYPE
SYNTAX INTEGER {
ua-initiator(1),
ua-responder(2),
peer-initiator(3),
peer-responder(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}
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."
::= {assocEntry 5}
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."
::= {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 current
DESCRIPTION
"The compliance statement for SNMPv2 entities
which implement the Network Services Monitoring MIB
for basic monitoring of network service applications."
MODULE -- this module
MANDATORY-GROUPS {applGroup}
::= {applCompliances 1}
applCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities
which implement the Network Services Monitoring MIB
for basic monitoring of network service applications."
MODULE -- this module
MANDATORY-GROUPS {applGroup}
::= {applCompliances 1}
assocCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the Network Services Monitoring MIB for basic
monitoring of network service applications and their
associations."
MODULE -- this module
MANDATORY-GROUPS {applGroup, assocGroup}
::= {applCompliances 2}
assocCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for SNMPv2 entities which
implement the Network Services Monitoring MIB for basic
monitoring of network service applications and their
associations."
MODULE -- this module
MANDATORY-GROUPS {applGroup, assocGroup}
::= {applCompliances 2}
-- Units of conformance
--一致性单位
applGroup OBJECT-GROUP
OBJECTS {
applName, 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."
::= {applGroups 1}
applGroup OBJECT-GROUP
OBJECTS {
applName, 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."
::= {applGroups 1}
assocGroup OBJECT-GROUP
OBJECTS {
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations."
::= {applGroups 2}
assocGroup OBJECT-GROUP
OBJECTS {
assocRemoteApplication, assocApplicationProtocol,
assocApplicationType, assocDuration}
STATUS current
DESCRIPTION
"A collection of objects providing basic monitoring of
network service applications' associations."
::= {applGroups 2}
-- 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
终止
The only changes made to this document since it was issued as RFC 1565 [11] are the following:
自本文件作为RFC 1565[11]发布以来，对其进行的唯一更改如下：
(1) applDescription and applURL fields have been added. These fields are intended to identify and describe the application.
(1) 已添加applDescription和applURL字段。这些字段用于识别和描述应用程序。
(2) A number of DESCRIPTION fields have been reworded, hopefully making them clearer.
(2) 许多描述字段已重新编写，希望能使它们更清晰。
(3) The new "quiescing" state has been added to applOperStatus.
(3) 新的“静止”状态已添加到applOperStatus。
(4) The prose about "dynamic single threaded processes" has been removed -- it was simply too confusing.
(4) 关于“动态单线程进程”的文章被删除了——它太令人困惑了。
(5) Various RFC references have been updated to refer to more recent versions.
(5) 各种RFC参考已经更新，以参考更新的版本。
(6) The MIB has been renamed from APPLICATION-MIB to NETWORK-SERVICES-MIB. This was done because an application MIB is now under development within the IETF that provides very different functionality from this MIB.
(6) MIB已从APPLICATION-MIB重命名为NETWORK-SERVICES-MIB。之所以这样做，是因为IETF中正在开发一个应用程序MIB，该MIB提供了与此MIB截然不同的功能。
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 [11] that have led to the present document.
本文档是邮件和目录管理（MADMAN）工作组的产品。它基于S.Kille、T.Lenggenhager、D.Partain和W.Yeong设计的早期MIB。电子邮件协会的TSC委员会有助于对RFC 1565[11]提供反馈并提出改进建议，从而形成本文件。
[1] 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.
[1] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息结构”，RFC 1902，1996年1月。
[2] 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.
[2] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的文本约定”，RFC 1903，1996年1月。
[3] 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.
[3] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的一致性声明”，RFC 1904，1996年1月。
[4] 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.
[4] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[5] 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.
[5] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[6] 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.
[6] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的管理信息库”，RFC 1907，1996年1月。
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Coexistence between Version 1 and Version 2 of the Internet-standard Network Management Framework", RFC 1908, January 1996.
[7] SNMPv2工作组，Case，J.，McCloghrie，K.，Rose，M.，和S.Waldbusser，“互联网标准网络管理框架第1版和第2版之间的共存”，RFC 1908，1996年1月。
[8] Kille, S., "A String Representation of Distinguished Names", RFC 1779, March 1995.
[8] Kille，S.，“可分辨名称的字符串表示法”，RFC 1779，1995年3月。
[9] Kille, S., "Mapping between X.400(1988) / ISO 10021 and RFC 822", RFC 1327, May 1992.
[9] Kille，S.，“X.400（1988）/ISO 10021和RFC 822之间的映射”，RFC 1327，1992年5月。
[10] Berners-Lee, T., Masinter, L. and M. McCahill, Uniform Resource Locators (URL)", RFC 1738, December 1994.
[10] Berners Lee，T.，Masinter，L.和M.McCahill，统一资源定位器（URL）”，RFC 17381994年12月。
[11] Freed, N., and S. Kille, "Network Services Monitoring MIB", RFC 1565, January 1994.
[11] Freed，N.和S.Kille，“网络服务监控MIB”，RFC 15651994年1月。
This MIB does not offer write access, and as such cannot be used to actively attack a system. However, this MIB does provide passive information about the existance, 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确实提供了有关给定主机上应用程序的存在、类型和配置的被动信息，这些信息可能表明存在某种漏洞。最后，MIB提供的有关网络使用情况的信息可用于分析网络流量模式。
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 ISODE Consortium The Dome, The Square Richmond TW9 1DT UK
Steve Kille，疯子工作组主席ISODE Consortium The Dome，英国里士满TW9 1DT广场
Phone: +44 181 332 9091
EMail: S.Kille@isode.com
Phone: +44 181 332 9091
EMail: S.Kille@isode.com
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。