Network Working Group A. Bierman
Request for Comments: 3434 K. McCloghrie
Category:Standards Track Cisco Systems, Inc.
December 2002
Network Working Group A. Bierman
Request for Comments: 3434 K. McCloghrie
Category:Standards Track Cisco Systems, Inc.
December 2002
Remote Monitoring MIB Extensions for High Capacity Alarms
用于高容量报警的远程监控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 (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for extending the alarm thresholding capabilities found in the Remote Monitoring (RMON) MIB (RFC 2819), to provide similar threshold monitoring of objects based on the Counter64 data type.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于扩展远程监控（RMON）MIB（RFC 2819）中的报警阈值功能的托管对象，以基于Counter64数据类型提供类似的对象阈值监控。
Table of Contents
目录
1 The Internet-Standard Management Framework ................... 2
2 Terms ........................................................ 2
3 Overview ..................................................... 2
3.1 Relationship to the Remote Monitoring MIBs ............... 3
4 MIB Structure ................................................ 4
4.1 MIB Group Overview ....................................... 4
4.1.1 High Capacity Alarm Control Group .................. 5
4.1.2 High Capacity Alarm Capabilities ................... 6
4.1.3 High Capacity Alarm Notifications .................. 6
5 Definitions .................................................. 6
6 Intellectual Property ........................................ 21
7 Acknowledgements ............................................. 21
8 Normative References ......................................... 21
9 Informative References ....................................... 22
1 The Internet-Standard Management Framework ................... 2
2 Terms ........................................................ 2
3 Overview ..................................................... 2
3.1 Relationship to the Remote Monitoring MIBs ............... 3
4 MIB Structure ................................................ 4
4.1 MIB Group Overview ....................................... 4
4.1.1 High Capacity Alarm Control Group .................. 5
4.1.2 High Capacity Alarm Capabilities ................... 6
4.1.3 High Capacity Alarm Notifications .................. 6
5 Definitions .................................................. 6
6 Intellectual Property ........................................ 21
7 Acknowledgements ............................................. 21
8 Normative References ......................................... 21
9 Informative References ....................................... 22
10 Security Considerations ..................................... 22
11 Authors' Addresses .......................................... 23
12 Full Copyright Statement .................................... 24
10 Security Considerations ..................................... 22
11 Authors' Addresses .......................................... 23
12 Full Copyright Statement .................................... 24
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 for a standardized way of providing the same type of alarm thresholding capabilities for Counter64 objects, as already exists for Counter32 objects. The RMON-1 alarmTable objects and RMON-1 notification types are specific to 32-bit objects, and cannot be used to properly monitor Counter64-based objects. Extensions to these existing constructs which explicitly support Counter64-based objects are needed. These extensions are completely independent of the existing RMON-1 alarm mechanisms.
需要一种标准化的方法为Counter64对象提供与Counter32对象相同类型的报警阈值功能。RMON-1 alarmTable对象和RMON-1通知类型特定于32位对象，无法用于正确监视基于计数器64的对象。需要对这些显式支持基于计数器64的对象的现有构造进行扩展。这些扩展完全独立于现有的RMON-1报警机制。
The usage of Counter64 objects is increasing. One of the causes for this increase is the increasing speeds of network interfaces; RFC 2863 [RFC2863] says:
Counter64对象的使用正在增加。这一增长的原因之一是网络接口速度的提高；RFC 2863[RFC2863]表示：
As the speed of network media increase, the minimum time in which a 32 bit counter will wrap decreases. For example, a 10Mbs stream of back-to-back, full-size packets causes ifInOctets to wrap in just over 57 minutes; at 100Mbs, the minimum wrap time is 5.7 minutes, and at 1Gbs, the minimum is 34 seconds. Requiring that interfaces be polled frequently enough not to miss a counter wrap is increasingly problematic.
随着网络媒体速度的增加，32位计数器的最小换行时间缩短。例如，一个10Mbs的背对背、全尺寸数据包流会导致IFinocts在57分钟内完成打包；100Mbs时，最小换行时间为5.7分钟，1Gbs时，最小换行时间为34秒。要求对接口进行足够频繁的轮询，以避免遗漏计数器包装，这一点越来越成问题。
and therefore requires:
因此需要：
For interfaces that operate at 20,000,000 (20 million) bits per second or less, 32-bit byte and packet counters MUST be supported. For interfaces that operate faster than 20,000,000 bits/second, and slower than 650,000,000 bits/second, 32-bit packet counters MUST be supported and 64-bit octet counters MUST be supported. For interfaces that operate at 650,000,000 bits/second or faster, 64-bit packet counters AND 64-bit octet counters MUST be supported.
对于每秒运行20000000（2000万）位或更少的接口，必须支持32位字节和数据包计数器。对于操作速度超过20000000位/秒、速度低于650000000位/秒的接口，必须支持32位数据包计数器，并且必须支持64位八位字节计数器。对于以650000000位/秒或更快速度运行的接口，必须支持64位数据包计数器和64位八位字节计数器。
Of the variables on which thresholds are set using RMON-1's alarmTable, two of the most popular are: ifInOctets and ifOutOctets. Thus, the increasing usage of the 64-bit versions: ifHCInOctets and ifHCOutOctets means that there is an increasing requirement to use RMON-1's thresholding capability for ifHCInOctets and ifHCOutOctets.
在使用RMON-1的alarmTable设置阈值的变量中，两个最流行的变量是：ifInOctets和ifOutOctets。因此，随着64位版本ifHCInOctets和ifHCOutOctets使用率的增加，对ifHCInOctets和ifHCOutOctets使用RMON-1阈值功能的要求也越来越高。
The RMON-1 Alarm Group is implemented not only by all RMON probes, but also by the SNMP agents in many other types of devices for the purpose of monitoring any of their (non-RMON) integer-valued MIB objects. The fact that it has been so widely implemented indicates its obvious value. Without this extension, that obvious value is becoming incomplete because of its lack of support for 64-bit integers. This extension is the easiest, simplest, and most compatible way for an implementation to overcome that lack of support.
RMON-1报警组不仅由所有RMON探测器实现，而且由许多其他类型设备中的SNMP代理实现，以监控其任何（非RMON）整数值MIB对象。它得到如此广泛的实施表明了其明显的价值。如果没有这个扩展，这个明显的值将变得不完整，因为它不支持64位整数。这个扩展是实现克服这种缺乏支持的最简单、最简单、最兼容的方法。
This MIB is intended to be implemented in Remote Monitoring (RMON) probes, which may also support the RMON-1 MIB [RFC2819]. Such probes may be stand-alone devices, or may be co-located with other networking devices (e.g., ethernet switches and repeaters).
该MIB拟在远程监控（RMON）探头中实现，该探头也可支持RMON-1 MIB[RFC2819]。此类探头可以是独立设备，或者可以与其他网络设备（例如，以太网交换机和中继器）位于同一位置。
The functionality of the High Capacity Alarm Group is a superset of RMON-1's Alarm Group. Thus, one day in the distant future, it is a possibility that RMON-1's Alarm Group will be deprecated in favor of this MIB's High Capacity Alarm Group. However, that day will not come before this document, or one of its successors, reaches the same standardization state as RMON-1.
高容量报警组的功能是RMON-1报警组的超集。因此，在遥远的将来的某一天，RMON-1的报警组有可能会被弃用，转而支持该MIB的高容量报警组。然而，在本文件或其后续文件之一达到与RMON-1相同的标准化状态之前，这一天不会到来。
Figure 1: HC-ALARM MIB Functional Structure
图1:HC-ALARM MIB功能结构
+---------------------------------------------+
| |
| (RMON-1) (HC-ALARM) |
| +-----------+ +-----------+ |
| | | | | |
| | alarm | | hcAlarm | |
| | Table | | Table | |
| | | | | |
| +-----------+ +-----------+ |
| | | |
| V (RMON-1) V |
| +----------------------------------+ |
| | | |
| | eventTable | |
| | | |
| +----------------------------------+ |
| | | |
| | | |
| V V |
| +---------------+ +----------------+ |
| | risingAlarm | | hcRisingAlarm | |
| | fallingAlarm | | hcFallingAlarm | |
| | Notifications | | Notifications | |
| +---------------+ +----------------+ |
| (RMON-1) (HC-ALARM) |
+---------------------------------------------+
+---------------------------------------------+
| |
| (RMON-1) (HC-ALARM) |
| +-----------+ +-----------+ |
| | | | | |
| | alarm | | hcAlarm | |
| | Table | | Table | |
| | | | | |
| +-----------+ +-----------+ |
| | | |
| V (RMON-1) V |
| +----------------------------------+ |
| | | |
| | eventTable | |
| | | |
| +----------------------------------+ |
| | | |
| | | |
| V V |
| +---------------+ +----------------+ |
| | risingAlarm | | hcRisingAlarm | |
| | fallingAlarm | | hcFallingAlarm | |
| | Notifications | | Notifications | |
| +---------------+ +----------------+ |
| (RMON-1) (HC-ALARM) |
+---------------------------------------------+
The HC-ALARM MIB contains three MIB groups:
HC-ALARM MIB包含三个MIB组：
- hcAlarmControlObjects group Controls the configuration of alarms for high capacity MIB object instances.
- hcAlarmControlObjects组控制高容量MIB对象实例的报警配置。
- hcAlarmCapabilities group Describes the high capacity alarm capabilities provided by the agent.
- hcAlarmCapabilities组描述了代理提供的高容量报警功能。
- hcAlarmNotifications group Provide new rising and falling threshold notifications for high capacity objects.
- hcAlarmNotifications组为高容量对象提供新的上升和下降阈值通知。
This group contains one table, which is used by a management station to configure high capacity alarm entries. To configure alarm thresholding for Counter64 or CounterBasedGauge64 objects, a management application must configure the hcAlarmTable in a manner similar to how RMON-1's alarmTable is configured.
此组包含一个表，管理站使用该表配置高容量报警条目。要为Counter64或CounterBasedGauge64对象配置报警阈值，管理应用程序必须以与RMON-1的alarmTable配置方式类似的方式配置hcAlarmTable。
Because the language in some of the DESCRIPTION clauses of objects in the alarmTable is specific to the alarmTable itself, their defined semantics do not allow them to be used for this MIB also. Therefore, the following objects are essentially cloned from the alarmTable to the hcAlarmTable:
由于alarmTable中对象的某些描述子句中的语言是特定于alarmTable本身的，因此它们定义的语义不允许将它们也用于此MIB。因此，以下对象基本上是从alarmTable克隆到hcAlarmTable的：
alarmTable hcAlarmTable
---------- ------------
alarmIndex hcAlarmIndex
alarmInterval hcAlarmInterval
alarmVariable hcAlarmVariable
alarmSampleType hcAlarmSampleType
alarmStartupAlarm hcAlarmStartupAlarm
alarmRisingEventIndex hcAlarmRisingEventIndex
alarmFallingEventIndex hcAlarmFallingEventIndex
alarmOwner hcAlarmOwner
alarmStatus hcAlarmStatus
alarmTable hcAlarmTable
---------- ------------
alarmIndex hcAlarmIndex
alarmInterval hcAlarmInterval
alarmVariable hcAlarmVariable
alarmSampleType hcAlarmSampleType
alarmStartupAlarm hcAlarmStartupAlarm
alarmRisingEventIndex hcAlarmRisingEventIndex
alarmFallingEventIndex hcAlarmFallingEventIndex
alarmOwner hcAlarmOwner
alarmStatus hcAlarmStatus
In addition, the following hcAlarmTable objects are used as high capacity values instead of the corresponding 32-bit version in the alarmTable.
此外，以下hcAlarmTable对象用作高容量值，而不是alarmTable中相应的32位版本。
alarmTable hcAlarmTable
---------- ------------
alarmValue hcAlarmAbsValue
hcAlarmValueStatus
alarmRisingThreshold hcAlarmRisingThreshAbsValueLo
hcAlarmRisingThreshAbsValueHi
hcAlarmRisingThresholdValStatus
alarmFallingThreshold hcAlarmFallingThreshAbsValueLo
hcAlarmFallingThreshAbsValueHi
hcAlarmFallingThresholdValStatus
alarmTable hcAlarmTable
---------- ------------
alarmValue hcAlarmAbsValue
hcAlarmValueStatus
alarmRisingThreshold hcAlarmRisingThreshAbsValueLo
hcAlarmRisingThreshAbsValueHi
hcAlarmRisingThresholdValStatus
alarmFallingThreshold hcAlarmFallingThreshAbsValueLo
hcAlarmFallingThreshAbsValueHi
hcAlarmFallingThresholdValStatus
Nevertheless, the hcAlarmTable does have a few differences from the alarmTable:
然而，hcAlarmTable与alarmTable确实有一些不同之处：
- Counter64 based objects are thresholded properly - an entry is not destroyed if the instance identified by the hcAlarmVariable is not available during a polling interval.
- 正确设置基于计数器64的对象的阈值-如果hcAlarmVariable标识的实例在轮询间隔期间不可用，则不会销毁条目。
- the RowStatus textual convention is used instead of EntryStatus for the hcAlarmStatus object. - the non-volatile storage of an HC alarm entry is explicitly controlled with a StorageType parameter. - a counter is provided to indicate the number of times the hcAlarmVariable object value could not be retrieved by the agent.
- hcAlarmStatus对象使用RowStatus文本约定代替EntryStatus。-HC报警条目的非易失性存储由StorageType参数明确控制。-提供一个计数器，指示代理无法检索hcAlarmVariable对象值的次数。
This group contains a single scalar object, called hcAlarmCapabilities. It describes the basic high capacity alarm features supported by the agent.
此组包含单个标量对象，称为hcAlarmCapabilities。它描述了代理支持的基本高容量报警功能。
This group contains two notifications, hcRisingAlarm and hcFallingAlarm. These are generated for high capacity alarms in the same manner and used to convey essentially the same information as RMON-1's risingAlarm and fallingAlarm notifications do for alarmTable-specified alarms.
此组包含两个通知：hcRisingAlarm和hcFallingAlarm。这些警报是以相同的方式为高容量警报生成的，用于传达与RMON-1的risingAlarm和fallingAlarm通知基本相同的信息，用于警报表指定的警报。
HC-ALARM-MIB DEFINITIONS ::= BEGIN
HC-ALARM-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, Counter32, Unsigned32 FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF RowStatus, VariablePointer, StorageType, TEXTUAL-CONVENTION FROM SNMPv2-TC CounterBasedGauge64 FROM HCNUM-TC rmon, OwnerString, rmonEventGroup FROM RMON-MIB;
从SNMPv2 SMI MODULE-COMPLIANCE导入MODULE-IDENTITY、OBJECT-TYPE、NOTIFICATION-TYPE、Integer32、Counter32、Unsigned32；从SNMPv2 CONF RowStatus导入OBJECT-GROUP、NOTIFICATION-GROUP；从HCNUM-TC rmon导入SNMPv2 TC CounterBasedGauge64；从rmon-MIB导入OwnerString、rmonEventGroup；
hcAlarmMIB MODULE-IDENTITY LAST-UPDATED "200212160000Z" ORGANIZATION "IETF RMONMIB Working Group" CONTACT-INFO " Andy Bierman Cisco Systems, Inc. Tel: +1 408 527-3711
hcAlarmMIB MODULE-IDENTITY上次更新的“200212160000Z”组织“IETF RMONMIB工作组”联系人信息“Andy Bierman Cisco Systems，Inc.电话：+1 408 527-3711
E-mail: abierman@cisco.com Postal: 170 West Tasman Drive San Jose, CA USA 95134
电邮：abierman@cisco.com邮政编码：美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编：95134
Keith McCloghrie Cisco Systems, Inc. Tel: +1 408 526-5260 E-mail: kzm@cisco.com Postal: 170 West Tasman Drive San Jose, CA USA 95134
Keith McCloghrie Cisco Systems，Inc.电话：+1 408 526-5260电子邮件：kzm@cisco.com邮政编码：美国加利福尼亚州圣何塞市西塔斯曼大道170号，邮编：95134
Send comments to <rmonmib@ietf.org> Mailing list subscription info: http://www.ietf.org/mailman/listinfo/rmonmib " DESCRIPTION "This module defines Remote Monitoring MIB extensions for High Capacity Alarms.
将评论发送到<rmonmib@ietf.org>邮件列表订阅信息：http://www.ietf.org/mailman/listinfo/rmonmib “说明”此模块定义了高容量报警的远程监控MIB扩展。
Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3434; see the RFC itself for full legal notices."
版权所有（C）互联网协会（2002年）。此版本的MIB模块是RFC 3434的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200212160000Z"
DESCRIPTION
"Initial version of the High Capacity Alarm MIB module.
This version published as RFC 3434."
::= { rmon 29 }
REVISION "200212160000Z"
DESCRIPTION
"Initial version of the High Capacity Alarm MIB module.
This version published as RFC 3434."
::= { rmon 29 }
hcAlarmObjects OBJECT IDENTIFIER ::= { hcAlarmMIB 1 }
hcAlarmNotifications OBJECT IDENTIFIER ::= { hcAlarmMIB 2 }
hcAlarmConformance OBJECT IDENTIFIER ::= { hcAlarmMIB 3 }
hcAlarmObjects OBJECT IDENTIFIER ::= { hcAlarmMIB 1 }
hcAlarmNotifications OBJECT IDENTIFIER ::= { hcAlarmMIB 2 }
hcAlarmConformance OBJECT IDENTIFIER ::= { hcAlarmMIB 3 }
hcAlarmControlObjects OBJECT IDENTIFIER ::= { hcAlarmObjects 1 }
hcAlarmCapabilitiesObjects OBJECT IDENTIFIER
::= { hcAlarmObjects 2 }
hcAlarmControlObjects OBJECT IDENTIFIER ::= { hcAlarmObjects 1 }
hcAlarmCapabilitiesObjects OBJECT IDENTIFIER
::= { hcAlarmObjects 2 }
-- -- Textual Conventions --
----文本约定--
HcValueStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type indicates the validity and sign of the data
in associated object instances which represent the absolute
value of a high capacity numeric quantity. Such an object
may be represented with one or more object instances. An
object of type HcValueStatus MUST be defined within the same
HcValueStatus ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This data type indicates the validity and sign of the data
in associated object instances which represent the absolute
value of a high capacity numeric quantity. Such an object
may be represented with one or more object instances. An
object of type HcValueStatus MUST be defined within the same
structure as the object(s) representing the high capacity absolute value.
结构作为表示高容量绝对值的对象。
If the associated object instance(s) representing the high capacity absolute value could not be accessed during the sampling interval, and is therefore invalid, then the associated HcValueStatus object will contain the value 'valueNotAvailable(1)'.
如果表示高容量绝对值的关联对象实例在采样间隔期间无法访问，因此无效，则关联的HcValueStatus对象将包含值“valueNotAvailable（1）”。
If the associated object instance(s) representing the high capacity absolute value are valid and actual value of the sample is greater than or equal to zero, then the associated HcValueStatus object will contain the value 'valuePositive(2)'.
如果表示高容量绝对值的关联对象实例有效且样本的实际值大于或等于零，则关联的HcValueStatus对象将包含值“ValuePosition（2）”。
If the associated object instance(s) representing the high
capacity absolute value are valid and the actual value of
the sample is less than zero, then the associated
HcValueStatus object will contain the value
'valueNegative(3)'. The associated absolute value should be
multiplied by -1 to obtain the true sample value."
SYNTAX INTEGER {
valueNotAvailable(1),
valuePositive(2),
valueNegative(3)
}
If the associated object instance(s) representing the high
capacity absolute value are valid and the actual value of
the sample is less than zero, then the associated
HcValueStatus object will contain the value
'valueNegative(3)'. The associated absolute value should be
multiplied by -1 to obtain the true sample value."
SYNTAX INTEGER {
valueNotAvailable(1),
valuePositive(2),
valueNegative(3)
}
-- -- High Capacity Alarm Table --
----大容量报警表--
hcAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF HcAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of entries for the configuration of high capacity
alarms."
::= { hcAlarmControlObjects 1 }
hcAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF HcAlarmEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of entries for the configuration of high capacity
alarms."
::= { hcAlarmControlObjects 1 }
hcAlarmEntry OBJECT-TYPE SYNTAX HcAlarmEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A conceptual row in the hcAlarmTable. Entries are usually created in this table by management application action, but may also be created by agent action as well."
hcAlarmEntry对象类型语法hcAlarmEntry MAX-ACCESS不可访问状态当前描述“hcAlarmTable中的概念行。此表中的条目通常由管理应用程序操作创建，但也可能由代理操作创建。”
INDEX { hcAlarmIndex }
::= { hcAlarmTable 1 }
INDEX { hcAlarmIndex }
::= { hcAlarmTable 1 }
HcAlarmEntry ::= SEQUENCE {
hcAlarmIndex Integer32,
hcAlarmInterval Integer32,
hcAlarmVariable VariablePointer,
hcAlarmSampleType INTEGER,
hcAlarmAbsValue CounterBasedGauge64,
hcAlarmValueStatus HcValueStatus,
hcAlarmStartupAlarm INTEGER,
hcAlarmRisingThreshAbsValueLo Unsigned32,
hcAlarmRisingThreshAbsValueHi Unsigned32,
hcAlarmRisingThresholdValStatus HcValueStatus,
hcAlarmFallingThreshAbsValueLo Unsigned32,
hcAlarmFallingThreshAbsValueHi Unsigned32,
hcAlarmFallingThresholdValStatus HcValueStatus,
hcAlarmRisingEventIndex Integer32,
hcAlarmFallingEventIndex Integer32,
hcAlarmValueFailedAttempts Counter32,
hcAlarmOwner OwnerString,
hcAlarmStorageType StorageType,
hcAlarmStatus RowStatus }
HcAlarmEntry ::= SEQUENCE {
hcAlarmIndex Integer32,
hcAlarmInterval Integer32,
hcAlarmVariable VariablePointer,
hcAlarmSampleType INTEGER,
hcAlarmAbsValue CounterBasedGauge64,
hcAlarmValueStatus HcValueStatus,
hcAlarmStartupAlarm INTEGER,
hcAlarmRisingThreshAbsValueLo Unsigned32,
hcAlarmRisingThreshAbsValueHi Unsigned32,
hcAlarmRisingThresholdValStatus HcValueStatus,
hcAlarmFallingThreshAbsValueLo Unsigned32,
hcAlarmFallingThreshAbsValueHi Unsigned32,
hcAlarmFallingThresholdValStatus HcValueStatus,
hcAlarmRisingEventIndex Integer32,
hcAlarmFallingEventIndex Integer32,
hcAlarmValueFailedAttempts Counter32,
hcAlarmOwner OwnerString,
hcAlarmStorageType StorageType,
hcAlarmStatus RowStatus }
hcAlarmIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer index value used to uniquely identify
this high capacity alarm entry."
::= { hcAlarmEntry 1 }
hcAlarmIndex OBJECT-TYPE
SYNTAX Integer32 (1..65535)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An arbitrary integer index value used to uniquely identify
this high capacity alarm entry."
::= { hcAlarmEntry 1 }
hcAlarmInterval OBJECT-TYPE SYNTAX Integer32 (1..2147483647) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this variable, care should be taken in the case of deltaValue sampling - the interval should be set short enough that the sampled variable is very unlikely to increase or decrease by more than 2^63 - 1 during a single sampling interval.
hcAlarmInterval对象类型语法整数32（1..2147483647）单位“秒”最大访问读取创建状态当前说明“对数据进行采样并与上升和下降阈值进行比较的间隔（秒）。设置此变量时，应注意deltaValue采样的情况-间隔应设置得足够短，以使采样变量在单个采样间隔内不太可能增加或减少2^63-1以上。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 2 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 2 }
hcAlarmVariable OBJECT-TYPE SYNTAX VariablePointer MAX-ACCESS read-create STATUS current DESCRIPTION "The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Integer32, Counter32, Counter64, Gauge, or TimeTicks) may be sampled.
hcAlarmVariable OBJECT-TYPE语法VariablePointer MAX-ACCESS read create STATUS current DESCRIPTION“要采样的特定变量的对象标识符。只能对解析为ASN.1整数基元类型（整数、整数32、计数器32、计数器64、仪表或时间刻度）的变量进行采样。
Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Because there is thus no acceptable means of restricting the read access that could be obtained through the alarm mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe.
由于SNMP访问控制完全根据MIB视图的内容进行阐述，因此不存在可以限制此对象的值以仅识别特定MIB视图中存在的那些对象的访问控制机制。由于没有可接受的方式限制通过报警机制获得的读取访问，因此探测器必须仅在对探测器上所有对象具有读取访问权限的视图中授予对此对象的写入访问权限。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 3 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 3 }
hcAlarmSampleType OBJECT-TYPE
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The method of sampling the selected variable and
calculating the value to be compared against the thresholds.
If the value of this object is absoluteValue(1), the value
of the selected variable will be compared directly with the
thresholds at the end of the sampling interval. If the
value of this object is deltaValue(2), the value of the
selected variable at the last sample will be subtracted from
the current value, and the difference compared with the
thresholds.
hcAlarmSampleType OBJECT-TYPE
SYNTAX INTEGER {
absoluteValue(1),
deltaValue(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The method of sampling the selected variable and
calculating the value to be compared against the thresholds.
If the value of this object is absoluteValue(1), the value
of the selected variable will be compared directly with the
thresholds at the end of the sampling interval. If the
value of this object is deltaValue(2), the value of the
selected variable at the last sample will be subtracted from
the current value, and the difference compared with the
thresholds.
If the associated hcAlarmVariable instance could not be obtained at the previous sample interval, then a delta
如果在上一个采样间隔无法获取关联的hcAlarmVariable实例，则会生成一个增量
sample is not possible, and the value of the associated hcAlarmValueStatus object for this interval will be valueNotAvailable(1).
无法进行采样，并且此间隔的关联hcAlarmValueStatus对象的值将为valueNotAvailable（1）。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 4 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 4 }
hcAlarmAbsValue OBJECT-TYPE SYNTAX CounterBasedGauge64 MAX-ACCESS read-only STATUS current DESCRIPTION "The absolute value (i.e., unsigned value) of the hcAlarmVariable statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed.
hcAlarmAbsValue对象类型语法CounterBasedGauge64 MAX-ACCESS只读状态current DESCRIPTION“上次采样期间hcAlarmVariable统计信息的绝对值（即无符号值）。当前采样期间的值在该期间完成后才可用。
To obtain the true value for this sampling interval, the associated instance of hcAlarmValueStatus must be checked, and the value of this object adjusted as necessary.
要获取此采样间隔的真实值，必须检查相关的hcAlarmValueStatus实例，并根据需要调整此对象的值。
If the MIB instance could not be accessed during the
sampling interval, then this object will have a value of
zero and the associated instance of hcAlarmValueStatus will
be set to 'valueNotAvailable(1)'."
::= { hcAlarmEntry 5 }
If the MIB instance could not be accessed during the
sampling interval, then this object will have a value of
zero and the associated instance of hcAlarmValueStatus will
be set to 'valueNotAvailable(1)'."
::= { hcAlarmEntry 5 }
hcAlarmValueStatus OBJECT-TYPE
SYNTAX HcValueStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the validity and sign of the data for
the hcAlarmAbsValue object, as described in the
HcValueStatus textual convention."
::= { hcAlarmEntry 6 }
hcAlarmValueStatus OBJECT-TYPE
SYNTAX HcValueStatus
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the validity and sign of the data for
the hcAlarmAbsValue object, as described in the
HcValueStatus textual convention."
::= { hcAlarmEntry 6 }
hcAlarmStartupAlarm OBJECT-TYPE
SYNTAX INTEGER {
risingAlarm(1),
fallingAlarm(2),
risingOrFallingAlarm(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The alarm that may be sent when this entry is first set to
hcAlarmStartupAlarm OBJECT-TYPE
SYNTAX INTEGER {
risingAlarm(1),
fallingAlarm(2),
risingOrFallingAlarm(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The alarm that may be sent when this entry is first set to
active. If the first sample after this entry becomes active is greater than or equal to the rising threshold and this object is equal to risingAlarm(1) or risingOrFallingAlarm(3), then a single rising alarm will be generated. If the first sample after this entry becomes valid is less than or equal to the falling threshold and this object is equal to fallingAlarm(2) or risingOrFallingAlarm(3), then a single falling alarm will be generated.
忙碌的如果此条目激活后的第一个样本大于或等于上升阈值，且该对象等于risingAlarm（1）或risingAlarm（3），则将生成单个上升报警。如果此条目生效后的第一个样本小于或等于下降阈值，且该对象等于下降报警（2）或上升报警（3），则将生成单个下降报警。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 7 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 7 }
hcAlarmRisingThreshAbsValueLo OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The lower 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmRisingThreshAbsValueHi and hcAlarmRisingThresholdValStatus objects, as follows:
hcAlarmRisingThreshAbsValueLo对象类型语法Unsigned32 MAX-ACCESS读取创建状态当前说明“采样统计的阈值绝对值的低32位。实际阈值由hcAlarmRisingThreshAbsValueHi和hcAlarmRisingThresholdValStatus对象的关联实例确定，如下所示：
ABS(threshold) = hcAlarmRisingThreshAbsValueLo +
(hcAlarmRisingThreshAbsValueHi * 2^^32)
ABS(threshold) = hcAlarmRisingThreshAbsValueLo +
(hcAlarmRisingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the rising threshold for this entry.
阈值的绝对值根据需要进行调整，如HcValueStatus文本约定中所述。这三个对象实例在概念上结合在一起，以表示此条目的上升阈值。
When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3).
当当前采样值大于或等于此阈值，且上次采样间隔的值小于此阈值时，将生成单个事件。如果此条目生效后的第一个样本大于或等于此阈值，并且关联的hcAlarmStartupAlarm等于risingAlarm（1）或RisingorAllingalarm（3），则也将生成单个事件。
After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the threshold identified by the hcAlarmFallingThreshAbsValueLo, hcAlarmFallingThreshAbsValueHi, and hcAlarmFallingThresholdValStatus objects.
生成上升事件后，在采样值低于此阈值并达到由hcAlarmFallingThreshAbsValueLo、hcAlarmFallingThreshAbsValueHi和hcAlarmFallingThresholdValStatus对象标识的阈值之前，不会生成另一个此类事件。
This object may not be modified if the associated hcAlarmStatus object is equal to active(1)."
如果关联的hcAlarmStatus对象等于active（1），则不能修改此对象。”
::= { hcAlarmEntry 8 }
::= { hcAlarmEntry 8 }
hcAlarmRisingThreshAbsValueHi OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The upper 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmRisingThreshAbsValueLo and hcAlarmRisingThresholdValStatus objects, as follows:
hcAlarmRisingThreshAbsValueHi对象类型语法Unsigned32 MAX-ACCESS读取创建状态当前说明“采样统计的阈值绝对值的上32位。实际阈值由hcAlarmRisingThreshAbsValueLo和hcAlarmRisingThresholdValStatus对象的关联实例确定，如下所示：
ABS(threshold) = hcAlarmRisingThreshAbsValueLo +
(hcAlarmRisingThreshAbsValueHi * 2^^32)
ABS(threshold) = hcAlarmRisingThreshAbsValueLo +
(hcAlarmRisingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the rising threshold for this entry.
阈值的绝对值根据需要进行调整，如HcValueStatus文本约定中所述。这三个对象实例在概念上结合在一起，以表示此条目的上升阈值。
When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3).
当当前采样值大于或等于此阈值，且上次采样间隔的值小于此阈值时，将生成单个事件。如果此条目生效后的第一个样本大于或等于此阈值，并且关联的hcAlarmStartupAlarm等于risingAlarm（1）或RisingorAllingalarm（3），则也将生成单个事件。
After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the threshold identified by the hcAlarmFallingThreshAbsValueLo, hcAlarmFallingThreshAbsValueHi, and hcAlarmFallingThresholdValStatus objects.
生成上升事件后，在采样值低于此阈值并达到由hcAlarmFallingThreshAbsValueLo、hcAlarmFallingThreshAbsValueHi和hcAlarmFallingThresholdValStatus对象标识的阈值之前，不会生成另一个此类事件。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 9 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 9 }
hcAlarmRisingThresholdValStatus OBJECT-TYPE SYNTAX HcValueStatus MAX-ACCESS read-create STATUS current
hcAlarmRisingThresholdValStatus对象类型语法HcValueStatus MAX-ACCESS读取创建状态当前
DESCRIPTION "This object indicates the sign of the data for the rising threshold, as defined by the hcAlarmRisingThresAbsValueLo and hcAlarmRisingThresAbsValueHi objects, as described in the HcValueStatus textual convention.
描述“此对象表示上升阈值的数据符号，如HcValueStatus文本约定中所述，由hcAlarmRisingThresAbsValueLo和hcAlarmRisingThresAbsValueHi对象定义。
The enumeration 'valueNotAvailable(1)' is not allowed, and the associated hcAlarmStatus object cannot be equal to 'active(1)' if this object is set to this value.
不允许枚举“valueNotAvailable（1）”，如果将此对象设置为此值，则关联的hcAlarmStatus对象不能等于“active（1）”。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 10 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 10 }
hcAlarmFallingThreshAbsValueLo OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The lower 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmFallingThreshAbsValueHi and hcAlarmFallingThresholdValStatus objects, as follows:
hcAlarmFallingThreshAbsValueLo对象类型语法Unsigned32 MAX-ACCESS读取创建状态当前说明“采样统计的阈值绝对值的低32位。实际阈值由hcAlarmFallingThreshAbsValueHi和hcAlarmFallingThresholdValStatus对象的关联实例确定，如下所示：
ABS(threshold) = hcAlarmFallingThreshAbsValueLo +
(hcAlarmFallingThreshAbsValueHi * 2^^32)
ABS(threshold) = hcAlarmFallingThreshAbsValueLo +
(hcAlarmFallingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the falling threshold for this entry.
阈值的绝对值根据需要进行调整，如HcValueStatus文本约定中所述。这三个对象实例在概念上组合在一起，以表示此条目的下降阈值。
When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3).
当当前采样值小于或等于此阈值，且上次采样间隔的值大于此阈值时，将生成单个事件。如果此条目生效后的第一个样本小于或等于此阈值，且相关的hcAlarmStartupAlarm等于fallingAlarm（2）或RisingorAllingAlarm（3），则也将生成单个事件。
After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the threshold identified by the hcAlarmRisingThreshAbsValueLo, hcAlarmRisingThreshAbsValueHi, and hcAlarmRisingThresholdValStatus objects.
生成下降事件后，在采样值上升到该阈值以上并达到由hcAlarmRisingThreshAbsValueLo、hcAlarmRisingThreshAbsValueHi和hcAlarmRisingThresholdValStatus对象标识的阈值之前，不会生成另一个此类事件。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 11 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 11 }
hcAlarmFallingThreshAbsValueHi OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "The upper 32 bits of the absolute value for threshold for the sampled statistic. The actual threshold value is determined by the associated instances of the hcAlarmFallingThreshAbsValueLo and hcAlarmFallingThresholdValStatus objects, as follows:
hcAlarmFallingThreshAbsValueHi对象类型语法Unsigned32 MAX-ACCESS读取创建状态当前说明“采样统计的阈值绝对值的上32位。实际阈值由hcAlarmFallingThreshAbsValueLo和hcAlarmFallingThresholdValStatus对象的关联实例确定，如下所示：
ABS(threshold) = hcAlarmFallingThreshAbsValueLo +
(hcAlarmFallingThreshAbsValueHi * 2^^32)
ABS(threshold) = hcAlarmFallingThreshAbsValueLo +
(hcAlarmFallingThreshAbsValueHi * 2^^32)
The absolute value of the threshold is adjusted as required, as described in the HcValueStatus textual convention. These three object instances are conceptually combined to represent the falling threshold for this entry.
阈值的绝对值根据需要进行调整，如HcValueStatus文本约定中所述。这三个对象实例在概念上组合在一起，以表示此条目的下降阈值。
When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated hcAlarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3).
当当前采样值小于或等于此阈值，且上次采样间隔的值大于此阈值时，将生成单个事件。如果此条目生效后的第一个样本小于或等于此阈值，且相关的hcAlarmStartupAlarm等于fallingAlarm（2）或RisingorAllingAlarm（3），则也将生成单个事件。
After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the threshold identified by the hcAlarmRisingThreshAbsValueLo, hcAlarmRisingThreshAbsValueHi, and hcAlarmRisingThresholdValStatus objects.
生成下降事件后，在采样值上升到该阈值以上并达到由hcAlarmRisingThreshAbsValueLo、hcAlarmRisingThreshAbsValueHi和hcAlarmRisingThresholdValStatus对象标识的阈值之前，不会生成另一个此类事件。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 12 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 12 }
hcAlarmFallingThresholdValStatus OBJECT-TYPE SYNTAX HcValueStatus MAX-ACCESS read-create STATUS current DESCRIPTION
hcAlarmFallingThresholdValStatus对象类型语法HcValueStatus MAX-ACCESS读取创建状态当前说明
"This object indicates the sign of the data for the falling threshold, as defined by the hcAlarmFallingThreshAbsValueLo and hcAlarmFallingThreshAbsValueHi objects, as described in the HcValueStatus textual convention.
“此对象表示下降阈值的数据符号，如HcValueStatus文本约定中所述，由hcAlarmFallingThreshAbsValueLo和hcAlarmFallingThreshAbsValueHi对象定义。
The enumeration 'valueNotAvailable(1)' is not allowed, and the associated hcAlarmStatus object cannot be equal to 'active(1)' if this object is set to this value.
不允许枚举“valueNotAvailable（1）”，如果将此对象设置为此值，则关联的hcAlarmStatus对象不能等于“active（1）”。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 13 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 13 }
hcAlarmRisingEventIndex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The index of the eventEntry that is used when a rising threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index.
hcAlarmRisingEventIndex对象类型语法整数32（0..65535）最大访问读取创建状态当前说明“超过上升阈值时使用的eventEntry索引。由该索引的特定值标识的eventEntry与由eventIndex对象的相同值标识的eventEntry相同。如果eventTable中没有相应的条目，则不存在关联。特别是，如果该值为零，则不会生成关联事件，因为零不是有效的事件索引。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 14 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 14 }
hcAlarmFallingEventIndex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "The index of the eventEntry that is used when a falling threshold is crossed. The eventEntry identified by a particular value of this index is the same as identified by the same value of the eventIndex object. If there is no corresponding entry in the eventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index.
hcAlarmFallingEventIndex对象类型语法整数32（0..65535）MAX-ACCESS读取创建状态当前说明“超过下降阈值时使用的eventEntry索引。由该索引的特定值标识的eventEntry与由eventIndex对象的相同值标识的eventEntry相同。如果eventTable中没有相应的条目，则不存在关联。特别是，如果该值为零，则不会生成关联事件，因为零不是有效的事件索引。
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 15 }
This object may not be modified if the associated
hcAlarmStatus object is equal to active(1)."
::= { hcAlarmEntry 15 }
hcAlarmValueFailedAttempts OBJECT-TYPE
hcAlarmValueFailedAttempts对象类型
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated hcAlarmVariable instance
was polled on behalf of this hcAlarmEntry, (while in the
active state) and the value was not available. This counter
may experience a discontinuity if the agent restarts,
indicated by the value of sysUpTime."
::= { hcAlarmEntry 16 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of times the associated hcAlarmVariable instance
was polled on behalf of this hcAlarmEntry, (while in the
active state) and the value was not available. This counter
may experience a discontinuity if the agent restarts,
indicated by the value of sysUpTime."
::= { hcAlarmEntry 16 }
hcAlarmOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { hcAlarmEntry 17 }
hcAlarmOwner OBJECT-TYPE
SYNTAX OwnerString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The entity that configured this entry and is therefore
using the resources assigned to it."
::= { hcAlarmEntry 17 }
hcAlarmStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of non-volatile storage configured for this entry.
If this object is equal to 'permanent(4)', then the
associated hcAlarmRisingEventIndex and
hcAlarmFallingEventIndex objects must be writable."
::= { hcAlarmEntry 18 }
hcAlarmStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The type of non-volatile storage configured for this entry.
If this object is equal to 'permanent(4)', then the
associated hcAlarmRisingEventIndex and
hcAlarmFallingEventIndex objects must be writable."
::= { hcAlarmEntry 18 }
hcAlarmStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of this row.
hcAlarmStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“此行的状态。
An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value, as described in the description clause for each writable object.
除非条目中的所有对象都具有适当的值（如每个可写对象的description子句中所述），否则条目不得处于活动状态。
The hcAlarmStatus object may be modified if the associated
instance of this object is equal to active(1),
notInService(2), or notReady(3). All other writable objects
may be modified if the associated instance of this object is
equal to notInService(2) or notReady(3)."
::= { hcAlarmEntry 19 }
The hcAlarmStatus object may be modified if the associated
instance of this object is equal to active(1),
notInService(2), or notReady(3). All other writable objects
may be modified if the associated instance of this object is
equal to notInService(2) or notReady(3)."
::= { hcAlarmEntry 19 }
-- -- Capabilities --
----能力--
hcAlarmCapabilities OBJECT-TYPE
SYNTAX BITS {
hcAlarmCreation(0),
hcAlarmNvStorage(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the high capacity alarm capabilities
supported by this agent.
hcAlarmCapabilities OBJECT-TYPE
SYNTAX BITS {
hcAlarmCreation(0),
hcAlarmNvStorage(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"An indication of the high capacity alarm capabilities
supported by this agent.
If the 'hcAlarmCreation' BIT is set, then this agent allows NMS applications to create entries in the hcAlarmTable.
如果设置了“hcAlarmCreation”位，则此代理允许NMS应用程序在hcAlarmTable中创建条目。
If the 'hcAlarmNvStorage' BIT is set, then this agent allows
entries in the hcAlarmTable which will be recreated after a
system restart, as controlled by the hcAlarmStorageType
object."
::= { hcAlarmCapabilitiesObjects 1 }
If the 'hcAlarmNvStorage' BIT is set, then this agent allows
entries in the hcAlarmTable which will be recreated after a
system restart, as controlled by the hcAlarmStorageType
object."
::= { hcAlarmCapabilitiesObjects 1 }
-- -- Notifications --
----通知--
hcAlarmNotifPrefix OBJECT IDENTIFIER
::= { hcAlarmNotifications 0 }
hcAlarmNotifPrefix OBJECT IDENTIFIER
::= { hcAlarmNotifications 0 }
hcRisingAlarm NOTIFICATION-TYPE OBJECTS { hcAlarmVariable, hcAlarmSampleType, hcAlarmAbsValue, hcAlarmValueStatus, hcAlarmRisingThreshAbsValueLo, hcAlarmRisingThreshAbsValueHi, hcAlarmRisingThresholdValStatus, hcAlarmRisingEventIndex } STATUS current DESCRIPTION "The SNMP notification that is generated when a high capacity alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps.
hcRisingAlarm通知类型对象{hcAlarmVariable，hcAlarmSampleType，hcAlarmAbsValue，hcAlarmValueStatus，hcAlarmRisingThreshAbsValueLo，hcAlarmRisingThreshAbsValueHi，hcAlarmRisingThresholdValStatus，hcAlarmRisingEventIndex}状态当前说明“当高容量警报条目超过其上升阈值并生成配置为发送SNMP陷阱的事件时生成的SNMP通知。
The hcAlarmEntry object instances identified in the OBJECTS
对象中标识的hcAlarmEntry对象实例
clause are from the entry that causes this notification to
be generated."
::= { hcAlarmNotifPrefix 1 }
clause are from the entry that causes this notification to
be generated."
::= { hcAlarmNotifPrefix 1 }
hcFallingAlarm NOTIFICATION-TYPE OBJECTS { hcAlarmVariable, hcAlarmSampleType, hcAlarmAbsValue, hcAlarmValueStatus, hcAlarmFallingThreshAbsValueLo, hcAlarmFallingThreshAbsValueHi, hcAlarmFallingThresholdValStatus, hcAlarmFallingEventIndex } STATUS current DESCRIPTION "The SNMP notification that is generated when a high capacity alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps.
HcAlarmingAlarm通知类型对象{hcAlarmVariable，hcAlarmSampleType，hcAlarmAbsValue，hcAlarmValueStatus，hcAlarmFallingThreshAbsValueLo，hcAlarmFallingThreshAbsValueHi，hcAlarmFallingThresholdValStatus，hcAlarmFallingEventIndex}状态当前说明“当高容量警报条目超过其下降阈值并生成配置为发送SNMP陷阱的事件时生成的SNMP通知。
The hcAlarmEntry object instances identified in the OBJECTS
clause are from the entry that causes this notification to
be generated."
::= { hcAlarmNotifPrefix 2 }
The hcAlarmEntry object instances identified in the OBJECTS
clause are from the entry that causes this notification to
be generated."
::= { hcAlarmNotifPrefix 2 }
-- -- Conformance Section --
----合规部分--
hcAlarmCompliances OBJECT IDENTIFIER ::= { hcAlarmConformance 1 }
hcAlarmGroups OBJECT IDENTIFIER ::= { hcAlarmConformance 2 }
hcAlarmCompliances OBJECT IDENTIFIER ::= { hcAlarmConformance 1 }
hcAlarmGroups OBJECT IDENTIFIER ::= { hcAlarmConformance 2 }
hcAlarmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the High
Capacity Alarm MIB."
MODULE -- this module
MANDATORY-GROUPS {
hcAlarmControlGroup,
hcAlarmCapabilitiesGroup,
hcAlarmNotificationsGroup
}
hcAlarmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the High
Capacity Alarm MIB."
MODULE -- this module
MANDATORY-GROUPS {
hcAlarmControlGroup,
hcAlarmCapabilitiesGroup,
hcAlarmNotificationsGroup
}
MODULE RMON-MIB MANDATORY-GROUPS { rmonEventGroup }
模块RMON-MIB强制组{rmonEventGroup}
::= { hcAlarmCompliances 1 }
::= { hcAlarmCompliances 1 }
-- Object Groups
--对象组
hcAlarmControlGroup OBJECT-GROUP
OBJECTS {
hcAlarmInterval,
hcAlarmVariable,
hcAlarmSampleType,
hcAlarmAbsValue,
hcAlarmValueStatus,
hcAlarmStartupAlarm,
hcAlarmRisingThreshAbsValueLo,
hcAlarmRisingThreshAbsValueHi,
hcAlarmRisingThresholdValStatus,
hcAlarmFallingThreshAbsValueLo,
hcAlarmFallingThreshAbsValueHi,
hcAlarmFallingThresholdValStatus,
hcAlarmRisingEventIndex,
hcAlarmFallingEventIndex,
hcAlarmValueFailedAttempts,
hcAlarmOwner,
hcAlarmStorageType,
hcAlarmStatus
}
STATUS current
DESCRIPTION
"A collection of objects used to configure entries for high
capacity alarm threshold monitoring purposes."
::= { hcAlarmGroups 1 }
hcAlarmControlGroup OBJECT-GROUP
OBJECTS {
hcAlarmInterval,
hcAlarmVariable,
hcAlarmSampleType,
hcAlarmAbsValue,
hcAlarmValueStatus,
hcAlarmStartupAlarm,
hcAlarmRisingThreshAbsValueLo,
hcAlarmRisingThreshAbsValueHi,
hcAlarmRisingThresholdValStatus,
hcAlarmFallingThreshAbsValueLo,
hcAlarmFallingThreshAbsValueHi,
hcAlarmFallingThresholdValStatus,
hcAlarmRisingEventIndex,
hcAlarmFallingEventIndex,
hcAlarmValueFailedAttempts,
hcAlarmOwner,
hcAlarmStorageType,
hcAlarmStatus
}
STATUS current
DESCRIPTION
"A collection of objects used to configure entries for high
capacity alarm threshold monitoring purposes."
::= { hcAlarmGroups 1 }
hcAlarmCapabilitiesGroup OBJECT-GROUP
OBJECTS {
hcAlarmCapabilities
}
STATUS current
DESCRIPTION
"A collection of objects used to indicate an agent's high
capacity alarm threshold monitoring capabilities."
::= { hcAlarmGroups 2 }
hcAlarmCapabilitiesGroup OBJECT-GROUP
OBJECTS {
hcAlarmCapabilities
}
STATUS current
DESCRIPTION
"A collection of objects used to indicate an agent's high
capacity alarm threshold monitoring capabilities."
::= { hcAlarmGroups 2 }
hcAlarmNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
hcRisingAlarm,
hcFallingAlarm
}
STATUS current
DESCRIPTION
"A collection of notifications to deliver information
related to a high capacity rising or falling threshold event
hcAlarmNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
hcRisingAlarm,
hcFallingAlarm
}
STATUS current
DESCRIPTION
"A collection of notifications to deliver information
related to a high capacity rising or falling threshold event
to a management application."
::= { hcAlarmGroups 3 }
to a management application."
::= { hcAlarmGroups 3 }
END
终止
The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
This memo is a product of the RMONMIB working group, and is based on existing alarmTable objects in the RMON-1 MIB module [RFC2819]. In order to maintain the RMON 'look-and-feel' and semantic consistency, some of Steve Waldbusser's text from [RFC2819] has been adapted for use in this MIB.
此备忘录是RMONMIB工作组的产品，基于RMON-1 MIB模块[RFC2819]中现有的alarmTable对象。为了保持RMON的“外观”和语义一致性，Steve Waldbusser在[RFC2819]中的一些文本已被改编用于此MIB。
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996.
[RFC2026]Bradner，S.，“互联网标准过程——第3版”，BCP 9，RFC 2026，1996年10月。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, STD 58, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，RFC 2580，STD 58，1999年4月。
[RFC2819] Waldbusser, S., "Remote Network Monitoring Management Information Base", STD 59, RFC 2819, May 2000.
[RFC2819]Waldbusser，S.，“远程网络监控管理信息库”，STD 59，RFC 2819，2000年5月。
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）版本3的基于用户的安全模型（USM）”，STD 62，RFC 3414，2002年12月。
[RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3415, December 2002.
[RFC3415]Wijnen，B.，Presohn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，STD 62，RFC 3415，2002年12月。
[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月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June, 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
There are a number of management objects defined in this MIB that have 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.
此MIB中定义了许多管理对象，它们的MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
There are a number of managed objects in this MIB that may contain sensitive information. These are:
此MIB中有许多托管对象可能包含敏感信息。这些是：
hcAlarmAbsValue hcAlarmValueStatus
hcAlarmAbsValue hcAlarmValueStatus
These objects are used together, and may expose the values of particular MIB instances, as identified by associated instances of the hcAlarmVariable object.
这些对象一起使用，并可能公开特定MIB实例的值，如hcAlarmVariable对象的关联实例所标识的。
hcAlarmVariable
hcAlarmVariable
This object identifies the object instance that the associated hcAlarmEntry will periodically sample. Because SNMP access control is articulated entirely in terms of the contents of MIB views, no access control mechanism exists that can restrict the value of this object to identify only those objects that exist in a particular MIB view. Thus, because there is no acceptable means of restricting the read access that could be obtained through the alarm mechanism, the probe must only grant write access to this object in those views that have read access to all objects on the probe.
此对象标识关联的hcAlarmEntry将定期采样的对象实例。由于SNMP访问控制完全根据MIB视图的内容进行阐述，因此不存在可以限制此对象的值以仅识别特定MIB视图中存在的那些对象的访问控制机制。因此，由于没有可接受的方式限制通过报警机制获得的读取访问，因此探测器必须仅在对探测器上的所有对象具有读取访问权限的视图中授予对此对象的写入访问权限。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
SNMPv1本身不是一个安全的环境。即使网络本身是安全的（例如通过使用IPSec），也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB中的对象。
It is recommended that the implementors consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model STD 62, RFC 3414 [RFC3414] and the View-based Access Control Model STD 62, RFC 3415 [RFC3415] is recommended.
建议执行者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型STD 62、RFC 3414[RFC3414]和基于视图的访问控制模型STD 62、RFC 3415[RFC3415]。
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 only the objects, and to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
然后，客户/用户有责任确保授予访问此MIB实例权限的SNMP实体正确配置为仅授予访问对象的权限，以及授予确实具有获取或设置（更改/创建/删除）对象的合法权限的主体（用户）的权限。
Andy Bierman Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA 95134 Phone: +1 408-527-3711 EMail: abierman@cisco.com
Andy Bierman Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号95134电话：+1 408-527-3711电子邮件：abierman@cisco.com
Keith McCloghrie Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA 95134 Phone: +1 408-526-5260 EMail: kzm@cisco.com
Keith McCloghrie Cisco Systems，Inc.美国加利福尼亚州圣何塞西塔斯曼大道170号95134电话：+1 408-526-5260电子邮件：kzm@cisco.com
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
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编辑功能的资金目前由互联网协会提供。