Network Working Group H. Lam
Request for Comments: 3878 Lucent Technologies
Category: Standards Track A. Huynh
Cetus Networks
D. Perkins
SNMPinfo
September 2004
Network Working Group H. Lam
Request for Comments: 3878 Lucent Technologies
Category: Standards Track A. Huynh
Cetus Networks
D. Perkins
SNMPinfo
September 2004
Alarm Reporting Control Management Information Base (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 (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for controlling the reporting of alarm conditions.
此备忘录定义了管理信息库（MIB）的一部分，用于基于TCP/IP的Internet中的网络管理协议。特别是，它定义了用于控制报警条件报告的对象。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 2
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. ARC MIB Overview . . . . . . . . . . . . . . . . . . . . . . . 2
4.1. Relationship between ARC mode and Alarm Reporting. . . . 4
5. ARC MIB Object Definitions . . . . . . . . . . . . . . . . . . 4
6. Security Considerations. . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . 15
9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15
10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 16
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 2
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 2
4. ARC MIB Overview . . . . . . . . . . . . . . . . . . . . . . . 2
4.1. Relationship between ARC mode and Alarm Reporting. . . . 4
5. ARC MIB Object Definitions . . . . . . . . . . . . . . . . . . 4
6. Security Considerations. . . . . . . . . . . . . . . . . . . . 13
7. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
8.1. Normative References . . . . . . . . . . . . . . . . . . 14
8.2. Informative References . . . . . . . . . . . . . . . . . 15
9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15
10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 16
The scope of this MIB is targeted for network operators responsible for managing the operations of network resources. This document defines an alarm reporting control (ARC) MIB module, which provides a mechanism for a manager to suppress or defer the reporting of alarm conditions based on the resource ID and alarm condition type.
此MIB的范围针对负责管理网络资源操作的网络运营商。本文档定义了报警报告控制（ARC）MIB模块，该模块为管理器提供了一种机制，用于根据资源ID和报警条件类型抑制或延迟报警条件的报告。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[RFC2119]中的说明进行解释。
There is a need to provide a mechanism for controlling the reporting of alarm conditions of resources in a network device. For example, (a) inhibiting the reporting of alarm conditions of a resource until the resource is problem-free, (b) inhibiting the reporting of alarm conditions of a resource for a specified time period, or (c) inhibiting the reporting of alarm conditions of a resource indefinitely until explicitly allowed by the managing system at a later time.
需要提供一种机制，用于控制网络设备中资源的报警条件的报告。例如，（a）禁止报告资源的警报条件，直到资源无问题为止，（b）禁止报告指定时间段内的资源警报条件，或（c）无限期禁止报告资源警报条件，直到管理系统在以后明确允许为止。
The alarm reporting control (ARC) feature provides an automatic in-service provisioning capability. It allows sufficient time for service setup, customer testing, and other maintenance activities in an "alarm-free" state. Once a resource is "problem-free", alarm reporting can be automatically or manually turned on (i.e., allowed).
报警报告控制（ARC）功能提供了自动在役供应功能。它允许在“无报警”状态下有足够的时间进行服务设置、客户测试和其他维护活动。一旦资源“无问题”，可以自动或手动打开报警报告（即允许）。
By putting a network resource in ARC mode, (i.e., in nalm, nalmTI, nalmQI, or nalmQICD states, as described in the MIB), the technicians and managing systems will not be flooded with unnecessary work items during operations activities such as service provisioning and network setup/teardown. This will reduce maintenance costs and improve the operation and maintenance of these systems. Putting a network resource in ARC mode shall not affect the availability of active alarm condition information for potential retrieval.
通过将网络资源置于ARC模式（即，如MIB中所述，处于nalm、nalmTI、nalmQI或nalmQICD状态），技术人员和管理系统在服务供应和网络设置/拆卸等操作活动期间不会被不必要的工作项淹没。这将降低维护成本，改善这些系统的运行和维护。将网络资源置于ARC模式不得影响活动报警条件信息的可用性，以供潜在检索。
ITU-T Recommendation M.3100 Amendment 3 [M.3100 Amd3] provides the business requirements, analysis, and design of the Alarm Reporting Control feature.
ITU-T建议M.3100修改件3[M.3100 Amd3]提供了报警报告控制功能的业务需求、分析和设计。
This document defines the MIB objects to support a subset of the ARC functions described in M.3100 Amd3. In particular, it defines a table that can be used to specify the ARC settings for the resources in a system.
本文档定义了MIB对象，以支持M.3100 Amd3中描述的ARC函数的子集。特别是，它定义了一个表，可用于指定系统中资源的弧设置。
Defined in M.3100 Amendment 3 [M.3100 Amd3], there are five ARC states: alm, nalm, nalmQI, nalmQICD and nalmTI. In the ARC MIB module, the arcState object is defined to model the M.3100 ARC states. Note that the state alm (alarm reporting is allowed) is not listed in the enumeration of the value of this object. However, this state is implicitly supported by the mib. Once a resource enters the normal reporting mode (i.e., into the alm state) for the specified alarm type, the corresponding row will be automatically deleted from the arc table. Also the manual setting of arcState to alm can be achieved through setting the RowStatus object to 'destroy'.
M.3100修正案3[M.3100 Amd3]中定义了五种电弧状态：alm、nalm、nalmQI、nalmQICD和nalmTI。在ARC MIB模块中，定义了ARCTATE对象以建模M.3100 ARC状态。请注意，此对象值的枚举中未列出状态alm（允许报警报告）。但是，mib隐式支持此状态。一旦资源进入指定报警类型的正常报告模式（即进入alm状态），相应的行将自动从arc表中删除。还可以通过将RowStatus对象设置为“destroy”来手动将arcState设置为alm。
The ARC MIB module defined in this document provides a way to control the reporting of alarm conditions. A set of applicable alarm conditions is defined in ITU-T Recommendation M.3100 [M.3100] and is named "probable causes". These probable causes (alarm conditions) have been included in the IANAItuProbableCause TC, which is defined in the IANA-ITU-ALARM-TC MIB module [RFC3877]. The IANA-ITU-ALARM-TC MIB module is maintained in the IANA web-site [ITUALARMTC]. [RFC3877].
本文档中定义的ARC MIB模块提供了一种控制报警条件报告的方法。ITU-T建议M.3100[M.3100]中定义了一组适用的报警条件，并将其命名为“可能原因”。这些可能的原因（报警条件）已包含在IANA-ITU-alarm-TC MIB模块[RFC3877]中定义的IAAITURBABLECAUSE TC中。IANA-ITU-ALARM-TC MIB模块保存在IANA网站[ITUARMTC]中。[RFC3877]。
The ARC MIB module defines an IANAItuProbableCauseOrZero TC which can take any value of IANAItuProbableCause or 0. The ARC MIB module further uses IANAItuProbableCauseOrZero to define the ARC settings for the managed resource in the network elements. Specification of objects for defining and storing alarms, including active and history alarms, standing and transient alarms, and alarm notifications are out of the scope of this document.
ARC MIB模块定义一个IAAITURBABLECAUSE或零TC，它可以取IAAITURBABLECAUSE或0的任何值。ARC MIB模块还使用IANAITUPBABLECAUSEORZERO为网元中的托管资源定义ARC设置。用于定义和存储报警（包括活动和历史报警、持续和瞬态报警以及报警通知）的对象规范不在本文件范围内。
When the ARC MIB module is used in a managed system, the following rules apply:
在托管系统中使用ARC MIB模块时，以下规则适用：
For alarm condition raised prior to entering ARC mode, reporting of alarm raised and alarm cleared will be sent as usual.
对于在进入ARC模式之前发出的报警条件，将一如既往地发送报警发出和报警清除的报告。
For alarm condition raised after entering ARC mode and also cleared before exiting ARC mode, no reporting of alarm raised will be sent and no reporting of alarm cleared will be sent.
对于在进入ARC模式后发出且在退出ARC模式前清除的报警条件，不会发送报警发出报告，也不会发送报警清除报告。
For alarm condition raised after entering ARC mode and not cleared when exiting ARC mode, the reporting of alarm raised will be deferred until the moment of exiting ARC mode. The reporting of alarm cleared will be sent as usual (i.e., at the time of alarm cleared).
对于进入ARC模式后发出的报警条件，以及退出ARC模式时未清除的报警条件，报警的报告将延迟到退出ARC模式的时刻。警报清除的报告将照常发送（即在警报清除时）。
Further details of the ARC function can be found in M.3100 Amd3 [M.3100 Amd3].
有关ARC功能的更多详细信息，请参见M.3100 Amd3[M.3100 Amd3]。
ARC-MIB DEFINITIONS ::= BEGIN
ARC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, RowStatus, StorageType
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ResourceId
FROM ALARM-MIB; -- [RFC3877]
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION, RowStatus, StorageType
FROM SNMPv2-TC -- [RFC2579]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
ResourceId
FROM ALARM-MIB; -- [RFC3877]
arcMibModule MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
arcMibModule MODULE-IDENTITY
LAST-UPDATED "200409090000Z" -- September 09, 2004
ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO
"WG EMail: disman@ietf.org
Subscribe: disman-request@ietf.org
http://www.ietf.org/html.charters/disman-charter.html
Chair: Randy Presuhn E-mail: randy_presuhn@mindspring.com
主席：Randy Presuhn电子邮件：Randy_presuhn@mindspring.com
Editor: Hing-Kam Lam Lucent Technologies, 4C-616 101 Crawfords Corner Road
编者：兴锦林朗讯科技有限公司，克劳福德角道101号4C-616
Holmdel, NJ 07733 USA Tel: +1 732 949 8338 E-mail: hklam@lucent.com"
美国新泽西州霍姆德尔07733电话：+1732 949 8338电子邮件：hklam@lucent.com"
DESCRIPTION "The MIB module describes the objects for controlling a resource in reporting alarm conditions that it detects.
DESCRIPTION“MIB模块描述用于在报告其检测到的报警条件时控制资源的对象。
Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC 3878; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2004年）。此版本的MIB模块是RFC 3878的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3878."
::={ mib-2 117 }
REVISION "200409090000Z" -- September 09, 2004
DESCRIPTION
"Initial version, published as RFC 3878."
::={ mib-2 117 }
------------------
-- TEXTUAL-CONVENTION
------------------
------------------
-- TEXTUAL-CONVENTION
------------------
IANAItuProbableCauseOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC can take any value of IANAItuProbableCause or 0.
IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC
module, which is maintained at the IANA web site and
published in the Alarm MIB document (see RFC 3877)."
REFERENCE
"IANA-ITU-ALARM-TC MIB module as maintained at the IANA web site.
The initial module was also published in RFC 3877."
--
SYNTAX INTEGER (0..2147483647)
IANAItuProbableCauseOrZero ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TC can take any value of IANAItuProbableCause or 0.
IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC
module, which is maintained at the IANA web site and
published in the Alarm MIB document (see RFC 3877)."
REFERENCE
"IANA-ITU-ALARM-TC MIB module as maintained at the IANA web site.
The initial module was also published in RFC 3877."
--
SYNTAX INTEGER (0..2147483647)
------------------
-- MIB Objects
------------------
------------------
-- MIB Objects
------------------
arcTimeIntervals OBJECT IDENTIFIER ::= { arcMibModule 1 }
arcObjects OBJECT IDENTIFIER ::= { arcMibModule 2 }
arcTimeIntervals OBJECT IDENTIFIER ::= { arcMibModule 1 }
arcObjects OBJECT IDENTIFIER ::= { arcMibModule 2 }
arcTITimeInterval OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION
ARCTITIMEInteval对象类型语法无符号32单位“秒”最大访问读写状态当前说明
"This variable indicates the time interval used for the nalmTI state, in units of second. It is a pre-defined length of time in which the resource will stay in the nalmTI state before transition into the alm state.
“此变量表示nalmTI状态使用的时间间隔，单位为秒。它是一个预定义的时间长度，资源在转换为alm状态之前将保持在nalmTI状态。”。
Instances of this object SHOULD persist across agent restarts."
::= { arcTimeIntervals 1 }
Instances of this object SHOULD persist across agent restarts."
::= { arcTimeIntervals 1 }
arcCDTimeInterval OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-write STATUS current DESCRIPTION "This variable indicates the time interval used for the nalmQICD state, in units of second. It is a pre-defined length of time in which the resource will stay in the nalmQICD state before transition into the alm state after it is problem-free.
arcCDTimeInterval对象类型语法无符号32单位“秒”最大访问读写状态当前说明“此变量表示nalmQICD状态使用的时间间隔，单位为秒。这是一个预定义的时间长度，在该时间长度内，资源将保持在nalmQICD状态，然后在无问题后转换为alm状态。
Instances of this object SHOULD persist across agent restarts."
::= { arcTimeIntervals 2 }
Instances of this object SHOULD persist across agent restarts."
::= { arcTimeIntervals 2 }
arcTable OBJECT-TYPE SYNTAX SEQUENCE OF ArcEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table of Alarm Reporting Control (ARC) settings on the system.
arcTable对象类型ArcEntry MAX-ACCESS的语法序列不可访问状态当前描述“系统上的报警报告控制（ARC）设置表。
Alarm Reporting Control is a feature that provides an automatic in-service provisioning capability. Alarm reporting is turned off on a per-resource basis for a selective set of potential alarm conditions to allow sufficient time for customer testing and other maintenance activities in an 'alarm free' state. Once a resource is ready for service, alarm reporting is automatically or manually turned on.
报警报告控制是一项功能，可提供自动在用供应功能。针对一组选择性的潜在报警条件，在每个资源的基础上关闭报警报告，以便在“无报警”状态下有足够的时间进行客户测试和其他维护活动。一旦资源准备好服务，报警报告将自动或手动打开。
Functional description and requirements of Alarm Reporting Control are defined in ITU-T Recommendation M.3100 Amendment 3 [M.3100 Amd3]."
警报报告控制的功能描述和要求在ITU-T建议M.3100修改件3[M.3100 Amd3]中定义。”
REFERENCE
"ITU Recommendation M.3100 Amendment 3, 'Generic Network
Information Model', January 2001."
::= { arcObjects 1 }
REFERENCE
"ITU Recommendation M.3100 Amendment 3, 'Generic Network
Information Model', January 2001."
::= { arcObjects 1 }
arcEntry OBJECT-TYPE SYNTAX ArcEntry
arcEntry对象类型语法arcEntry
MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row that contains information about an ARC setting of a resource in the system.
MAX-ACCESS not ACCESS STATUS current DESCRIPTION“包含系统中资源的ARC设置信息的概念行。
Implementation need to be aware that if the total size of arcIndex and arcNotificationId exceeds 114 sub-IDs, then OIDs of column instances in this table will have more than 128 sub-IDs and cannot be access using SNMPv1, SNMPv2c, or snmpv3."
实施需要注意，如果arcIndex和arcNotificationId的总大小超过114个子ID，则此表中列实例的OID将超过128个子ID，并且无法使用SNMPv1、SNMPv2c或snmpv3进行访问。”
INDEX { arcIndex, arcAlarmType, arcNotificationId }
::= { arcTable 1 }
INDEX { arcIndex, arcAlarmType, arcNotificationId }
::= { arcTable 1 }
ArcEntry ::=
SEQUENCE {
arcIndex ResourceId,
arcAlarmType IANAItuProbableCauseOrZero,
arcNotificationId OBJECT IDENTIFIER,
arcState INTEGER,
arcNalmTimeRemaining Unsigned32,
arcRowStatus RowStatus,
arcStorageType StorageType
}
ArcEntry ::=
SEQUENCE {
arcIndex ResourceId,
arcAlarmType IANAItuProbableCauseOrZero,
arcNotificationId OBJECT IDENTIFIER,
arcState INTEGER,
arcNalmTimeRemaining Unsigned32,
arcRowStatus RowStatus,
arcStorageType StorageType
}
arcIndex OBJECT-TYPE SYNTAX ResourceId MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object uniquely identifies a resource, which is under the arcState's control for the associated arcAlarmType.
arcIndex对象类型语法ResourceId MAX-ACCESS不可访问状态当前描述“此对象唯一标识一个资源，该资源受关联arcAlarmType的arcState控制。
For example, if the resource is an interface, this object will
point to an instance of interface, e.g., ifIndex.1."
::= { arcEntry 1 }
For example, if the resource is an interface, this object will
point to an instance of interface, e.g., ifIndex.1."
::= { arcEntry 1 }
arcAlarmType OBJECT-TYPE SYNTAX IANAItuProbableCauseOrZero MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object identifies the alarm condition type controlled by the arcState. It specifies the value 0 or a value of IANAItuProbableCause that is applicable to the resource. IANAItuProbableCause is defined in the IANA-ITU-ALARM-TC module in the Alarm MIB document.
arcAlarmType对象类型语法IANAITUPBABLECAUSEORZERO MAX-ACCESS不可访问状态当前描述“此对象标识由arcState控制的报警条件类型。它指定适用于资源的值0或IAAITURBABLECAUSE的值。IANAITU-ALARM-TC模块在报警MIB文档中定义了IANAITU-ALARM-TC。
The value of zero (0) implies any probable causes that are
applicable to the resource. Usually, the applicable probable
causes of a resource are specified in the resource-specific mib."
::= { arcEntry 2 }
The value of zero (0) implies any probable causes that are
applicable to the resource. Usually, the applicable probable
causes of a resource are specified in the resource-specific mib."
::= { arcEntry 2 }
arcNotificationId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object identifies the type of notification to be suppressed.
The notification type identified should be the one normally used
by the resource for reporting its alarms. When the value of 0.0 is
specified for this object, it implies all applicable notification
types."
::= { arcEntry 3 }
arcNotificationId OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object identifies the type of notification to be suppressed.
The notification type identified should be the one normally used
by the resource for reporting its alarms. When the value of 0.0 is
specified for this object, it implies all applicable notification
types."
::= { arcEntry 3 }
arcState OBJECT-TYPE
SYNTAX INTEGER {
nalm (1),
nalmQI (2),
nalmTI (3),
nalmQICD (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defined in M.3100 Amendment 3 [M.3100 Amd3], there are five
ARC states: alm, nalm, nalmQI, nalmQICD, and nalmTI.
arcState OBJECT-TYPE
SYNTAX INTEGER {
nalm (1),
nalmQI (2),
nalmTI (3),
nalmQICD (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Defined in M.3100 Amendment 3 [M.3100 Amd3], there are five
ARC states: alm, nalm, nalmQI, nalmQICD, and nalmTI.
alm: Alarm reporting is turned on (i.e., is allowed). nalm: Alarm reporting is turned off (i.e., not allowed). nalmQI: nalm - Qualified Inhibit. Alarm reporting is turned off until the managed entity is qualified problem-free for an optional persistence interval. Problem-free means that the condition corresponding to the specified alarm type is cleared. nalmQICD: nalmQI - Count down. This is a substate of nalmQI and performs the persistence timing countdown function after the managed entity is qualified problem-free. nalmTI: nalm - Timed Inhibit. Alarm reporting is turned off for a specified time interval.
alm：报警报告已打开（即允许）。nalm：报警报告已关闭（即不允许）。nalmQI:nalm-限定禁止。报警报告将关闭，直到受管实体在可选的持续时间间隔内没有问题。无问题表示与指定报警类型对应的条件已清除。nalmQICD:nalmQI-倒计时。这是nalmQI的一个子状态，在被管理实体合格且无问题后执行持久性计时倒计时功能。nalmTI:nalm-定时抑制。在指定的时间间隔内关闭报警报告。
alm may transition to nalm, nalmQI or nalmTI by management request.
alm可以通过管理请求转换为nalm、nalmQI或nalmTI。
nalm may transition to alm, nalmQI or nalmTI by management request.
nalm可以通过管理请求转换为alm、nalmQI或nalmTI。
nalmQI may transition to nalm or alm by management request.
nalmQI可以通过管理请求转换为nalm或alm。
nalmQI may transition to alm automatically if qualified problem-free (if nalmQICD is not supported) or if the CD timer expired (if nalmQICD is supported)
如果合格的无问题（如果不支持nalmQICD）或CD计时器过期（如果支持nalmQICD），则nalmQI可以自动转换为alm
nalmTI may transition to alm or nalm by management request.
nalmTI可根据管理层的要求转换为alm或nalm。
nalmTI may transition to alm automatically if the TI timer expired.
如果TI计时器过期，nalmTI可能会自动转换为alm。
Further details of ARC state transitions are defined in Figure 3 of M.3100 Amd3 [M.3100 Amd3].
M.3100 Amd3[M.3100 Amd3]的图3中定义了电弧状态转换的更多细节。
According to the requirements in M.3100 Amd3, a resource supporting the ARC feature shall support the alm state and at least one of the nalm, nalmTI, and nalmQI states. The nalmQICD state is an optional substate of nalmQI.
根据M.3100 Amd3中的要求，支持ARC功能的资源应支持alm状态以及至少一种nalm、nalmTI和nalmQI状态。nalmQICD状态是nalmQI的可选子状态。
The arcState object controls the alarm reporting state of a resource. Note that the state alm (alarm reporting is allowed) is not listed in the enumeration of the value of this object. However, this state is implicitly supported by the mib. Once a resource enters the normal reporting mode (i.e., in the alm state) for the specified alarm type, the corresponding row will be automatically deleted from the arc table. Also the manual setting of arcState to alm can be achieved through setting the RowStatus object to 'destroy'.
arcState对象控制资源的报警报告状态。请注意，此对象值的枚举中未列出状态alm（允许报警报告）。但是，mib隐式支持此状态。一旦资源进入指定报警类型的正常报告模式（即alm状态），相应的行将自动从arc表中删除。还可以通过将RowStatus对象设置为“destroy”来手动将arcState设置为alm。
The nalamQICD state is a transitional state from nalmQI to alm. It is optional depending on the resource type and the implementation of the resource. If it is supported, before the state transitions from nalmQI to alm, a count down period is activated for a duration set by the object arcNalmCDTimeInterval. When the time is up, the arcState transitions to alm."
nalamQICD状态是从nalmQI到alm的过渡状态。它是可选的，具体取决于资源类型和资源的实现。如果支持，则在状态从nalmQI转换为alm之前，将在对象ARCNALMCDTIMETERVAL设置的持续时间内激活一个倒计时周期。时间到后，arcState将转换为alm。“
::= { arcEntry 4 }
::= { arcEntry 4 }
arcNalmTimeRemaining OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the time remaining in the nalmTI state or the nalmQICD state, in units of second.
ARCNAMTIMESTAINING对象类型语法Unsigned32单位“秒”MAX-ACCESS read create STATUS current DESCRIPTION“此变量表示nalmTI状态或nalmQICD状态下的剩余时间，单位为秒。
At the moment the resource enters the nalmTI state, this variable will have the initial value equal to the value of
当资源进入nalmTI状态时，该变量的初始值将等于
arcNalmTITimeInterval and then starts decrementing as time goes by.
arcNalmTITimeInterval，然后随着时间的推移开始递减。
Similarly at the moment the resource enters the nalmQICD state, this variable will have the initial value equal to the value of arcNalmCDTimeInterval and then starts decrementing as time goes by.
类似地，在资源进入nalmQICD状态时，该变量的初始值将等于ArcNALMDCTimeInterval的值，然后随着时间的推移开始递减。
This variable is read-create and thus will allow the manager to write (extend or shorten), as needed, the remaining time when the resource is in the nalmTI or nalmQICD state.
此变量为read create，因此当资源处于nalmTI或nalmQICD状态时，管理器可以根据需要写入（扩展或缩短）剩余时间。
If this variable is supported and the resource is currently not in
the nalmTI nor nalmQICD state, the value of this variable shall
equal to zero."
::= { arcEntry 5 }
If this variable is supported and the resource is currently not in
the nalmTI nor nalmQICD state, the value of this variable shall
equal to zero."
::= { arcEntry 5 }
arcRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This columnar object is used for creating and deleting a conceptual row of the arcTable. It is used to create and delete an arc setting.
arcRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此列对象用于创建和删除arcTable的概念行。用于创建和删除arc设置。
Setting RowStatus to createAndGo or createAndWait implies creating a new ARC setting for the specified resource and alarm type. Setting RowStatus to destroy implies removing the ARC setting and thus has the effect of resuming normal reporting behaviour of the resource for the alarm type.
将RowStatus设置为createAndGo或createAndWait意味着为指定的资源和报警类型创建新的ARC设置。将RowStatus设置为destroy意味着删除ARC设置，从而恢复报警类型资源的正常报告行为。
Only the objects arcState, arcNalmTimeRemaining, and arcRowStatus
can be updated when a row is active. All the objects, except
arcNalmTimeRemaining, must be set before the row can be activated."
::= { arcEntry 6 }
Only the objects arcState, arcNalmTimeRemaining, and arcRowStatus
can be updated when a row is active. All the objects, except
arcNalmTimeRemaining, must be set before the row can be activated."
::= { arcEntry 6 }
arcStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this conceptual row. Conceptual rows having the value 'permanent' must allow write-access at a minimum to arcState. Note that arcState must allow change by management request. Therefore, no row can be created with 'readOnly'. If a set operation tries to set the value to 'readOnly', then an 'inconsistentValue' error must be returned." DEFVAL { nonVolatile }
arcStorageType对象类型语法StorageType MAX-ACCESS读取创建状态当前描述“此概念行的存储类型。值为“permanent”的概念行必须至少允许对arcState进行写访问。请注意，arcState必须允许按管理请求进行更改。因此，不能使用“readOnly”创建任何行。如果set操作试图将值设置为“readOnly”，则必须返回“inconsistentValue”错误。“deffal{nonVolatile}”
::= { arcEntry 7}
::= { arcEntry 7}
--------------------------
-- conformance information
--------------------------
--------------------------
-- conformance information
--------------------------
arcConformance OBJECT IDENTIFIER ::= { arcMibModule 3 }
arcConformance OBJECT IDENTIFIER ::= { arcMibModule 3 }
arcCompliances OBJECT IDENTIFIER ::= { arcConformance 1 }
arcCompliances OBJECT IDENTIFIER ::= { arcConformance 1 }
arcCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for systems supporting the ARC MIB module."
ARC合规模块-合规状态当前描述“支持ARC MIB模块的系统的合规声明”
MODULE -- this module
MANDATORY-GROUPS {
arcSettingGroup
}
MODULE -- this module
MANDATORY-GROUPS {
arcSettingGroup
}
OBJECT arcStorageType
WRITE-SYNTAX StorageType {
volatile(2),
nonVolatile(3),
permanent(4)
}
DESCRIPTION
"Support for value 'other' is not required.
The arcState object must allow change by management
request. Therefore, no row can be created with
'readOnly'."
OBJECT arcStorageType
WRITE-SYNTAX StorageType {
volatile(2),
nonVolatile(3),
permanent(4)
}
DESCRIPTION
"Support for value 'other' is not required.
The arcState object must allow change by management
request. Therefore, no row can be created with
'readOnly'."
GROUP arcTIGroup DESCRIPTION "This group is REQUIRED for ARC settings that provide the Time Inhibit (TI) function."
组arcTIGroup DESCRIPTION“提供时间禁止（TI）功能的ARC设置需要此组。”
GROUP arcQICDGroup DESCRIPTION "This group is REQUIRED for ARC settings that provide the Quality Inhibit (QI) Count Down (CD) function."
组arcQICDGroup DESCRIPTION“提供质量抑制（QI）倒计时（CD）功能的ARC设置需要此组。”
::= { arcCompliances 1 }
::= { arcCompliances 1 }
arcGroups OBJECT IDENTIFIER ::= { arcConformance 2 }
arcGroups OBJECT IDENTIFIER ::= { arcConformance 2 }
arcSettingGroup OBJECT-GROUP
OBJECTS {
arcState,
arcRowStatus,
arcStorageType
}
STATUS current
DESCRIPTION
"A collection of objects applicable to
basic ARC setting."
::= { arcGroups 1}
arcSettingGroup OBJECT-GROUP
OBJECTS {
arcState,
arcRowStatus,
arcStorageType
}
STATUS current
DESCRIPTION
"A collection of objects applicable to
basic ARC setting."
::= { arcGroups 1}
arcTIGroup OBJECT-GROUP
OBJECTS {
arcTITimeInterval,
arcNalmTimeRemaining
}
STATUS current
DESCRIPTION
"A collection of objects applicable to
ARC setting that support the Time Inhibit (TI)
function."
::= { arcGroups 2}
arcTIGroup OBJECT-GROUP
OBJECTS {
arcTITimeInterval,
arcNalmTimeRemaining
}
STATUS current
DESCRIPTION
"A collection of objects applicable to
ARC setting that support the Time Inhibit (TI)
function."
::= { arcGroups 2}
arcQICDGroup OBJECT-GROUP
OBJECTS {
arcCDTimeInterval,
arcNalmTimeRemaining
}
STATUS current
DESCRIPTION
"A collection of objects applicable to
ARC setting that support the Quality Inhibit (QI)
Count Down (CD) function."
::= { arcGroups 3}
arcQICDGroup OBJECT-GROUP
OBJECTS {
arcCDTimeInterval,
arcNalmTimeRemaining
}
STATUS current
DESCRIPTION
"A collection of objects applicable to
ARC setting that support the Quality Inhibit (QI)
Count Down (CD) function."
::= { arcGroups 3}
END
终止
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
arcTITimeInterval, arcCDTimeInterval, arcState, arcNalmTimeRemaining, arcRowStatus, arcStorageType.
ArcTitimInterval、ArcCD时间间隔、arcState、ArcNalmTime剩余、arcRowStatus、arcStorageType。
Setting these objects may have disruptive effects on network operation that range from omission of alarm notifications to flooding of unwanted alarm notifications from the network. The consequence of suppressing or deferring the reporting of an alarm can prevent the timely delivery of important diagnostic information, including information that can help identify an attack.
设置这些对象可能会对网络操作产生中断性影响，从忽略报警通知到网络中大量出现不需要的报警通知。抑制或延迟报警报告的后果可能会阻止重要诊断信息的及时传递，包括有助于识别攻击的信息。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
arcTITimeInterval, arcCDTimeInterval, arcState, arcNalmTimeRemaining, arcRowStatus, arcStorageType.
ArcTitimInterval、ArcCD时间间隔、arcState、ArcNalmTime剩余、arcRowStatus、arcStorageType。
Reading these objects will provide information about the setting which affects alarm notification generation.
读取这些对象将提供有关影响报警通知生成的设置的信息。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPSec), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPSec），也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module 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.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
The authors wish to thank Brian Teer and Sharon Chisholm for reviewing and commenting on this document.
作者希望感谢Brian Teer和Sharon Chisholm对本文件的审查和评论。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC3877] Chisholm, S. and D. Romascanu, "Alarm Management Information Base (MIB)", RFC 3877, September 2004.
[RFC3877]Chisholm，S.和D.Romascanu，“报警管理信息库（MIB）”，RFC 3877，2004年9月。
[ITUALARMTC] http://www.iana.org/assignments/ianaitualarmtc-mib
[ITUALARMTC] http://www.iana.org/assignments/ianaitualarmtc-mib
[M.3100] ITU Recommendation M.3100, "Generic Network Information Model", July 1995.
[M.3100]国际电联建议M.3100，“通用网络信息模型”，1995年7月。
[M.3100 Amd3] ITU Recommendation M.3100 Amendment 3, "Generic Network Information Model", January 2001.
[M.3100 Amd3]国际电联建议M.3100修正案3，“通用网络信息模型”，2001年1月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
Hing-Kam Lam Lucent Technologies 101 Crawfords Corner Road, Room 4C-616 Holmdel, NJ 07733 USA
兴锦林朗讯科技美国新泽西州霍姆代尔克劳福德角路101号4C-616室07733
Phone: +1 732-949-8338
EMail: hklam@lucent.com
Phone: +1 732-949-8338
EMail: hklam@lucent.com
An-ni Huynh Cetus Networks USA
美国安尼胡恩赛特斯网络公司
EMail: a_n_huynh@yahoo.com
EMail: a_n_huynh@yahoo.com
David T. Perkins 548 Quailbrook Ct San Jose, CA 95110 USA
David T.Perkins 548美国加利福尼亚州圣何塞奎尔布鲁克市，邮编95110
Phone: +1 408-394-8702
EMail: dperkins@snmpinfo.com
Phone: +1 408-394-8702
EMail: dperkins@snmpinfo.com
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。