Network Working Group S. Channabasappa
Request for Comments: 5428 CableLabs
Category: Standards Track W. De Ketelaere
tComLabs
E. Nechamkin
Broadcom Corp.
April 2009
Network Working Group S. Channabasappa
Request for Comments: 5428 CableLabs
Category: Standards Track W. De Ketelaere
tComLabs
E. Nechamkin
Broadcom Corp.
April 2009
Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices
PacketCable和IPCablecom兼容设备的管理事件管理信息库（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) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托在本文件出版之日生效的与IETF文件有关的法律规定的约束(http://trustee.ietf.org/license-info). 请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
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 defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of events that can be generated by PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了一组基本的托管对象，用于基于简单网络管理协议（SNMP）的事件管理，这些事件可以由符合PacketCable和IPCablecom的多媒体终端适配器设备生成。
Table of Contents
目录
1. The Internet-Standard Management Framework ......................2
2. Introduction ....................................................2
3. Terminology .....................................................3
3.1. PacketCable ................................................3
3.2. IPCablecom .................................................3
3.3. MTA ........................................................4
3.4. Endpoint ...................................................4
3.5. MSO ........................................................4
3.6. UDP ........................................................4
4. Overview ........................................................4
4.1. Structure of the MIB .......................................5
4.2. pktcEventControl ...........................................6
4.3. pktcEventThrottle ..........................................6
4.4. pktcEventStatus ............................................7
4.5. pktcEvent ..................................................7
4.6. pktcEventLog ...............................................7
4.7. pktcEventNotifications .....................................7
5. Relationship to Other MIB Modules ...............................7
5.1. MIB Modules Required for IMPORTS ...........................7
6. Definitions .....................................................8
7. IANA Considerations ............................................32
8. Security Considerations ........................................32
9. Acknowledgments ................................................34
10. Normative References ..........................................35
11. Informative References ........................................36
1. The Internet-Standard Management Framework ......................2
2. Introduction ....................................................2
3. Terminology .....................................................3
3.1. PacketCable ................................................3
3.2. IPCablecom .................................................3
3.3. MTA ........................................................4
3.4. Endpoint ...................................................4
3.5. MSO ........................................................4
3.6. UDP ........................................................4
4. Overview ........................................................4
4.1. Structure of the MIB .......................................5
4.2. pktcEventControl ...........................................6
4.3. pktcEventThrottle ..........................................6
4.4. pktcEventStatus ............................................7
4.5. pktcEvent ..................................................7
4.6. pktcEventLog ...............................................7
4.7. pktcEventNotifications .....................................7
5. Relationship to Other MIB Modules ...............................7
5.1. MIB Modules Required for IMPORTS ...........................7
6. Definitions .....................................................8
7. IANA Considerations ............................................32
8. Security Considerations ........................................32
9. Acknowledgments ................................................34
10. Normative References ..........................................35
11. Informative References ........................................36
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]所述。
A Multimedia Terminal Adapter (MTA) is used to deliver broadband Internet, data, and/or voice access jointly with telephony service to a subscriber's or customer's premises using a cable network
多媒体终端适配器（MTA）用于通过有线网络将宽带互联网、数据和/或语音接入与电话服务一起传送到用户或客户的场所
infrastructure. An MTA is normally installed at the subscriber's or customer's premises and is coupled to a multiple system operator (MSO) using a hybrid fiber coax (HFC) access network.
基础设施MTA通常安装在用户或客户的场所，并使用混合光纤同轴电缆（HFC）接入网络连接到多系统运营商（MSO）。
An MTA is provisioned by the MSO for broadband Internet, data, and/or voice service. For more information on MTA provisioning, refer to [PKT-SP-PROV] and [RFC4682]. MTA devices include one or more endpoints (e.g., telephone ports), which receive call signaling information to establish ring cadence, and codecs, which provide telephony service.
MSO为宽带互联网、数据和/或语音服务提供MTA。有关MTA配置的更多信息，请参阅[PKT-SP-PROV]和[RFC4682]。MTA设备包括一个或多个端点（例如，电话端口），它们接收呼叫信令信息以建立环频，以及提供电话服务的编解码器。
For more information on call signaling refer to, [PKT-SP-MGCP] and [RFC3435].
有关呼叫信令的更多信息，请参阅[PKT-SP-MGCP]和[RFC3435]。
For more information on codecs, refer to [PKT-SP-CODEC].
有关编解码器的更多信息，请参阅[PKT-SP-CODEC]。
Given the complexity of such systems, it is important that a suitable event management mechanism be defined to allow for effective management. This MIB module provides objects suitable for generation and management of events on the MTA.
鉴于此类系统的复杂性，必须定义适当的事件管理机制，以便进行有效管理。此MIB模块提供适合在MTA上生成和管理事件的对象。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。
The terms "MIB module" and "information module" are used interchangeably in this memo. As used here, both terms refer to any of the three types of information modules defined in Section 3 of RFC 2578 [RFC2578]. Some of the terms used in this memo are defined below. Some additional terms are also defined in the PacketCable(TM) Management Event Mechanism Specification [PKT-SP-MEM1.5] and the PacketCable MTA Device Provisioning Specification [PKT-SP-PROV].
术语“MIB模块”和“信息模块”在本备忘录中互换使用。此处使用的两个术语均指RFC 2578[RFC2578]第3节中定义的三种信息模块中的任何一种。本备忘录中使用的一些术语定义如下。PacketCable（TM）管理事件机制规范[PKT-SP-MEM1.5]和PacketCable MTA设备配置规范[PKT-SP-PROV]中还定义了一些附加术语。
PacketCable is a CableLabs-led initiative that is aimed at developing interoperable interface specifications for delivering advanced, real-time multimedia services over two-way cable plants.
PacketCable是由CableLabs牵头的一项计划，旨在制定可互操作的接口规范，以便通过双向电缆工厂提供先进的实时多媒体服务。
IPCablecom is an ITU Telecommunication Standardization Sector (ITU-T) project that includes architecture and a series of recommendations that enable the delivery of real-time services over the cable television networks using cable modems.
IPCablecom是国际电联电信标准化部门（ITU-T）的一个项目，该项目包括使用电缆调制解调器在有线电视网络上提供实时服务的体系结构和一系列建议。
A Multimedia Terminal Adapter (MTA) is a PacketCable- or IPCablecom-compliant device providing telephony services over a cable or hybrid system used to deliver video signals to a community. It contains an interface to endpoints, a network interface, codecs, and all signaling and encapsulation functions required for Voice over IP transport, call signaling, and Quality of Service signaling. An MTA can be an embedded or standalone device. An Embedded MTA (E-MTA) is an MTA device containing an embedded Data Over Cable Service Interface Specifications (DOCSIS) cable modem. A Standalone MTA (S-MTA) is an MTA device separated from the DOCSIS cable modem by a non-DOCSIS Media Access Control (MAC) interface (e.g., Ethernet, USB).
多媒体终端适配器（MTA）是一种与PacketCable或IPCablecom兼容的设备，通过用于向社区传送视频信号的电缆或混合系统提供电话服务。它包含端点接口、网络接口、编解码器以及IP语音传输、呼叫信令和服务质量信令所需的所有信令和封装功能。MTA可以是嵌入式或独立设备。嵌入式MTA（E-MTA）是一种MTA设备，包含嵌入式数据有线服务接口规范（DOCSIS）电缆调制解调器。独立MTA（S-MTA）是通过非DOCSIS介质访问控制（MAC）接口（如以太网、USB）与DOCSIS电缆调制解调器分离的MTA设备。
An endpoint or MTA endpoint is a standard RJ-11 telephony physical port located on the MTA and used for attaching the telephone device to the MTA.
端点或MTA端点是位于MTA上的标准RJ-11电话物理端口，用于将电话设备连接到MTA。
A Multi-System Operator is a cable company that operates many head-end locations in several cities.
多系统运营商是一家在多个城市运营多个前端位置的电缆公司。
A User Datagram Protocol is a connectionless protocol built upon Internet Protocol (IP), as per RFC 768 [RFC768].
根据RFC 768[RFC768]，用户数据报协议是建立在互联网协议（IP）基础上的无连接协议。
PacketCable, European Telecommunications Standards Institute (ETSI), and International Telecommunication Union Telecommunication Standardization Sector (ITU-T) IPCablecom-compliant Multimedia Terminal Adaptors (MTAs) are required to generate management events upon the occurrence of certain operational conditions (for instance, "AC power failure, MTA operational on battery power"). The complete set of conditions and the corresponding management events to be generated are specified in [PKT-SP-MEM1.5] (PacketCable), [ETSITS101909-22] (ETSI), and [ITU-T-J176] (ITU-T). In addition, the MTA manufacturer is allowed to specify vendor-specific management events. For example, vendor XYZ can specify "Memory read error, terminating process, code: XYZ123".
PacketCable、欧洲电信标准协会（ETSI）和国际电信联盟电信标准化部门（ITU-T）IPCablecom兼容的多媒体终端适配器（MTA）需要在出现某些操作条件时生成管理事件（例如，“交流电源故障，MTA在电池电源上运行”）。在[PKT-SP-MEM1.5]（打包电缆）、[ETSITS11909-22]（ETSI）和[ITU-T-J176]（ITU-T）中规定了要生成的整套条件和相应的管理事件。此外，允许MTA制造商指定特定于供应商的管理事件。例如，供应商XYZ可以指定“内存读取错误，终止进程，代码：XYZ123”。
When management events are generated, they can either be stored in a local log on the MTA or transmitted using two possible mechanisms: SNMP or syslog. This choice between storing and transmitting is required to be configurable and manageable by the management station for each management event (default values can be provided when the events are defined). This document proposes a MIB that can provide for configuration and management of such management events. A means to log the events is provided within the specified MIB module. For syslog as a transport, the necessary information (format, transport, etc.) is also specified. For SNMP as a transport, the MIB objects specified in the SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB as utilized, is specified in [RFC3413].
生成管理事件时，它们可以存储在MTA上的本地日志中，也可以使用两种可能的机制进行传输：SNMP或syslog。存储和传输之间的选择要求管理站对每个管理事件进行配置和管理（定义事件时可提供默认值）。本文档提出了一个MIB，可用于配置和管理此类管理事件。在指定的MIB模块中提供了记录事件的方法。对于作为传输的syslog，还指定了必要的信息（格式、传输等）。对于作为传输的SNMP，在[RFC3413]中指定了SNMP-TARGET-MIB和SNMP-NOTIFICATION-MIB中指定的MIB对象。
Further, each management event can be uniquely identified using the 'Organization ID' and 'Event ID'. The 'Organization ID' is the private enterprise number of the organization specifying the event (e.g., 4491 for CableLabs) and a unique identifier that identifies the event. The 'Event ID' is an identifier that uniquely identifies the event within the 'Organization ID' space. This document does not specify any management events. It only provides a mechanism to manage the storage and transmission of events.
此外，每个管理事件都可以使用“组织ID”和“事件ID”进行唯一标识。“Organization ID”是指定事件的组织的私有企业编号（例如，CableLabs为4491）和标识事件的唯一标识符。“事件ID”是唯一标识“组织ID”空间内事件的标识符。本文档未指定任何管理事件。它只提供一种机制来管理事件的存储和传输。
The EVENT MIB module specified in this document is intended to update the EVENT MIB modules from which it is partly derived:
本文档中指定的事件MIB模块旨在更新其部分派生的事件MIB模块：
- the PacketCable 1.5 Management Event MIB Specification [PKT-SP-EVEMIB1.5] and
- PacketCable 1.5管理事件MIB规范[PKT-SP-EVEMIB1.5]和
- the ITU-T IPCablecom management event mechanism MIB requirements [ITU-T-J176].
- ITU-T IPCablecom管理事件机制MIB要求[ITU-T-J176]。
Several normative and informative references are used to help define Management Event MIB objects. As a convention, wherever the requirements are equivalent at the time of the writing, the PacketCable reference is used. However, MTA implementations MUST refer to the corresponding specifications to ensure compliance.
一些规范性和信息性参考文件用于帮助定义管理事件MIB对象。作为惯例，只要在编写本报告时要求相同，就使用PacketCable参考。但是，MTA实施必须参考相应的规范以确保合规性。
The Management Event MIB module is identified by pktcIetfEventMib and is structured into the following sub-trees:
管理事件MIB模块由pktcIetfEventMib标识，并被构造为以下子树：
- pktcEventControl specifies the management information pertinent to control of the device's event generation capabilities.
- pktcEventControl指定与控制设备的事件生成功能相关的管理信息。
- pktcEventThrottle specifies the management information pertinent to throttling the transmission of management events using syslog or SNMP.
- pktcEventThrottle指定与使用syslog或SNMP限制管理事件传输相关的管理信息。
- pktcEventStatus specifies the management information for the device to report status information related to the generated events.
- pktcEventStatus指定设备的管理信息，以报告与生成的事件相关的状态信息。
- pktcEvents specifies the management information for the device to list all the events it is capable of generating.
- pktcEvents指定设备的管理信息，以列出其能够生成的所有事件。
- pktcEventLog specifies the management information for the device to store the generated events.
- pktcEventLog指定用于存储生成事件的设备的管理信息。
- pktcEventNotifications specifies the management information that defines the SNMP trap and inform messages.
- pktcEventNotifications指定定义SNMP陷阱和通知消息的管理信息。
The group of objects in this sub-tree provide for three important controls: ability to reset the event logs and event descriptions, syslog configuration, and event classes.
此子树中的对象组提供了三个重要控件：重置事件日志和事件描述的能力、系统日志配置和事件类。
Some highlights are as follows:
一些亮点如下：
pktcEventReset - this MIB object allows a management station to reset the event logs, the event descriptions, or both.
pktcEventReset—此MIB对象允许管理站重置事件日志和/或事件描述。
pktcEventSyslog - this group of MIB objects allows the management station to provide information for transmission of events to a syslog server, such as message formats and transport protocols.
pktcEventSyslog—这组MIB对象允许管理站提供将事件传输到syslog服务器的信息，例如消息格式和传输协议。
pktcEventClassTable - this MIB table allows for MTAs to classify the management events into different categories, termed 'event classes'. It then allows for common operations to be affected across all the events pertaining to a specific event class.
pktcEventClassTable—此MIB表允许MTA将管理事件分类为不同的类别，称为“事件类”。然后，它允许在与特定事件类相关的所有事件中影响公共操作。
As indicated earlier, the generated events can be stored locally or transmitted using SNMP, syslog, or both. However, the management stations receiving such events may wish to control the rate of transmission of such events. This event-throttling behavior is provided by the MIB objects in this sub-tree.
如前所述，生成的事件可以本地存储，也可以使用SNMP、syslog或两者进行传输。然而，接收此类事件的管理站可能希望控制此类事件的传输速率。此事件限制行为由此子树中的MIB对象提供。
Some highlights are as follows:
一些亮点如下：
pktcEventThrottleAdminStatus - this MIB object allows for transmissions to be unconstrained, maintained below threshold, stopped at the threshold, or inhibited.
pktcEventThrottleAdminStatus-此MIB对象允许传输不受限制、保持在阈值以下、在阈值处停止或禁止。
pktcEventThrottleThreshold - this MIB object specifies the throttle, i.e., the number of events over an interval that is considered to be the threshold.
pktcEventThrottleThreshold-此MIB对象指定限制，即在被视为阈值的时间间隔内的事件数。
pktcEventThrottleInterval - this MIB object specifies the interval over which the threshold is calculated.
pktcEventThrottleInterval-此MIB对象指定计算阈值的时间间隔。
This sub-tree is designed to provide status information related to event transmissions. It currently contains one MIB object, pktcEventTransmissionStatus, that allows a client to report the status of event transmissions.
此子树旨在提供与事件传输相关的状态信息。它当前包含一个MIB对象pktcEventTransmissionStatus，它允许客户端报告事件传输的状态。
This sub-tree is designed to provide a list of all the events that can be generated by an MTA and its associated descriptions. The MIB objects are grouped under the MIB table pktcEventTable.
此子树旨在提供MTA可以生成的所有事件及其相关描述的列表。MIB对象分组在MIB表pktcEventTable下。
This sub-tree is designed to allow the MTA to store all the events that are generated during its operation. The events are stored with information such as the time of the event, its description and related characteristics like severity levels.
此子树旨在允许MTA存储其操作期间生成的所有事件。事件与事件时间、描述和相关特征（如严重性级别）等信息一起存储。
This sub-tree specifies the notification information, i.e., when MTAs transmit messages using SNMP traps and informs. SNMP traps refer to the SNMPv2-Trap-PDU. SNMPv1 traps are disallowed.
此子树指定通知信息，即MTA使用SNMP陷阱和通知传输消息的时间。SNMP陷阱指的是SNMPv2陷阱PDU。不允许使用SNMPv1陷阱。
Some management objects defined in other MIB modules are applicable to an entity implementing this MIB. In particular, it is assumed that an entity implementing the PKTC-IETF-EVENT-MIB module will also implement the 'interfaces' group of the IF-MIB [RFC2863].
其他MIB模块中定义的某些管理对象适用于实现此MIB的实体。特别是，假设实现PKTC-IETF-EVENT-MIB模块的实体也将实现IF-MIB[RFC2863]的“接口”组。
The PKTC-IETF-EVENT-MIB MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], SNMPv2-TC [RFC2579], SNMP-FRAMEWORK-MIB [RFC3411], SNMPv2-CONF [RFC2580], IF-MIB [RFC2863], INET-ADDRESS-MIB [RFC4001], SNMP-TARGET-MIB [RFC3413], SNMP-NOTIFICATION-MIB [RFC3413], and the SYSLOG-TC-MIB [RFC5427].
PKTC-IETF-EVENT-MIB MIB模块从SNMPv2 SMI[RFC2578]、SNMPv2 TC[RFC2579]、SNMP-FRAMEWORK-MIB[RFC3411]、SNMPv2 CONF[RFC2580]、IF-MIB[RFC2863]、INET-ADDRESS-MIB[RFC4001]、SNMP-TARGET-MIB[RFC3413]、SNMP-NOTIFICATION-MIB[RFC3413]和SYSLOG-TC-MIB[RFC5427]导入对象。
PKTC-IETF-EVENT-MIB DEFINITIONS ::= BEGIN
PKTC-IETF-EVENT-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, NOTIFICATION-TYPE, mib-2 FROM SNMPv2-SMI
从SNMPv2 SMI导入模块标识、对象类型、未签名32、通知类型、mib-2
TruthValue, DateAndTime, TEXTUAL-CONVENTION FROM SNMPv2-TC SnmpAdminString FROM SNMP-FRAMEWORK-MIB OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF ifPhysAddress FROM IF-MIB InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB snmpTargetBasicGroup, snmpTargetResponseGroup FROM SNMP-TARGET-MIB snmpNotifyGroup, snmpNotifyFilterGroup FROM SNMP-NOTIFICATION-MIB SyslogSeverity, SyslogFacility FROM SYSLOG-TC-MIB;
TruthValue、DateAndTime、SNMPv2 TC中的文本约定SNMPAdmin从SNMP-FRAMEWORK-MIB对象组中安装、模块符合性、SNMPv2 CONF中的通知组ifPhysAddress从IF-MIB InetAddressType中删除、InetAddress从INET-ADDRESS-MIB snmpTargetBasicGroup中删除、snmpTargetResponseGroup从SNMP-TARGET-MIB snmpNotifyGroup中删除、，SNMP-NOTIFICATION-MIB SyslogSeverity中的snmpNotifyFilterGroup，SYSLOG-TC-MIB中的SyslogFacility；
pktcIetfEventMib MODULE-IDENTITY LAST-UPDATED "200903300000Z" -- 30 March 2009 ORGANIZATION "IETF IP over Cable Data Network Working Group" CONTACT-INFO "Sumanth Channabasappa Cable Television Laboratories, Inc. 858 Coal Creek Circle, Louisville, CO 80027, USA +1 303-661-3307 Sumanth@cablelabs.com
pktcIetfEventMib模块标识最新更新“20090330000Z”-2009年3月30日组织“IETF有线数据网络IP工作组”联系方式“Sumanth Channabasappa有线电视实验室有限公司，地址：美国科罗拉多州路易斯维尔Coal Creek Circle 858号，邮编：80027+1 303-661-3307Sumanth@cablelabs.com
Wim De Ketelaere tComLabs Gildestraat 8 9000 Gent, Belgium +32 9 269 22 90 deketelaere@tComLabs.com
Wim De Ketelaere tComLabs Gildestsaat 8 9000 Gent，比利时+32 9 269 22 90deketelaere@tComLabs.com
Eugene Nechamkin Broadcom Corporation 200 - 13711 International Place Richmond, BC, V6V 2Z8, Canada +1 604 233 8500 enechamkin@broadcom.com
Eugene Nechamkin Broadcom Corporation 200-13711加拿大不列颠哥伦比亚省里士满国际广场，V6V 2Z8+1 604 233 8500enechamkin@broadcom.com
IETF IPCDN Working Group
General Discussion: ipcdn@ietf.org
Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com
Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com"
IETF IPCDN Working Group
General Discussion: ipcdn@ietf.org
Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com
Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com"
DESCRIPTION "This MIB module specifies the basic management objects for managing events generated by the Multimedia Terminal Adapter devices compliant with the PacketCable and IPCablecom requirements.
DESCRIPTION“此MIB模块指定基本管理对象，用于管理符合PacketCable和IPCablecom要求的多媒体终端适配器设备生成的事件。
Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2009 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
在满足以下条件的情况下，允许以源代码和二进制格式重新分发和使用，无论是否修改：
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- 源代码的重新分发必须保留上述版权声明、此条件列表和以下免责声明。
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- 以二进制形式重新分发时，必须在分发时提供的文档和/或其他材料中复制上述版权声明、本条件列表和以下免责声明。
- Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission.
- 未经事先书面许可，不得使用互联网协会、IETF或IETF Trust的名称或特定贡献者的名称来认可或推广源自本软件的产品。
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
本软件由版权所有者和贡献者“按原样”提供，不承担任何明示或暗示的担保，包括但不限于适销性和特定用途适用性的暗示担保。在任何情况下，版权所有人或贡献者均不对任何直接、间接、偶然、特殊、惩戒性或后果性损害负责
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
（包括但不限于替代商品或服务的采购；使用、数据或利润的损失；或业务中断）无论是合同、严格责任还是因使用本软件而产生的侵权行为（包括疏忽或其他）而引起的任何责任理论，即使被告知可能发生此类损坏。
This version of this MIB module is part of RFC 5428; see the RFC itself for full legal notices."
此版本的MIB模块是RFC 5428的一部分；有关完整的法律通知，请参见RFC本身。”
REVISION "200903300000Z" -- 30 March 2009
修订版“20090330000Z”-2009年3月30日
DESCRIPTION "Initial version, published as RFC 5428."
说明“初始版本，发布为RFC 5428。”
::= { mib-2 182 }
::= { mib-2 182 }
SyslogSeverityMask ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention represents a bit mask representing
the severity of the syslog events that can be generated.
It corresponds to the various severity levels associated
with syslog messages, as specified in 'The Syslog Protocol',
[RFC5424].
SyslogSeverityMask ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention represents a bit mask representing
the severity of the syslog events that can be generated.
It corresponds to the various severity levels associated
with syslog messages, as specified in 'The Syslog Protocol',
[RFC5424].
emerg (0), - emergency; system is unusable alert (1), - action must be taken immediately crit (2), - critical condition err (3), - error condition warning (4), - warning condition notice (5), - normal but significant condition info (6), - informational message debug (7) - debug-level messages"
紧急情况（0），-紧急情况；系统不可用警报（1），-必须立即采取措施（2），-临界条件错误（3），-错误条件警告（4），-警告条件通知（5），-正常但重要的条件信息（6），-信息性消息调试（7）-调试级别消息”
SYNTAX BITS {
emerg(0),
alert(1),
crit(2),
err(3),
warning(4),
notice(5),
info(6),
debug(7)
}
SYNTAX BITS {
emerg(0),
alert(1),
crit(2),
err(3),
warning(4),
notice(5),
info(6),
debug(7)
}
--
--
pktcEventNotifications OBJECT IDENTIFIER ::= { pktcIetfEventMib 0 }
pktcEventMibObjects OBJECT IDENTIFIER ::= { pktcIetfEventMib 1 }
pktcEventConformance OBJECT IDENTIFIER ::= { pktcIetfEventMib 2 }
--
--
pktcEventControl OBJECT IDENTIFIER ::= { pktcEventMibObjects 1 }
pktcEventThrottle OBJECT IDENTIFIER ::= { pktcEventMibObjects 2 }
pktcEventStatus OBJECT IDENTIFIER ::= { pktcEventMibObjects 3 }
pktcEvents OBJECT IDENTIFIER ::= { pktcEventMibObjects 4 }
pktcEventLog OBJECT IDENTIFIER ::= { pktcEventMibObjects 5 }
--
--
pktcEventNotifications OBJECT IDENTIFIER ::= { pktcIetfEventMib 0 }
pktcEventMibObjects OBJECT IDENTIFIER ::= { pktcIetfEventMib 1 }
pktcEventConformance OBJECT IDENTIFIER ::= { pktcIetfEventMib 2 }
--
--
pktcEventControl OBJECT IDENTIFIER ::= { pktcEventMibObjects 1 }
pktcEventThrottle OBJECT IDENTIFIER ::= { pktcEventMibObjects 2 }
pktcEventStatus OBJECT IDENTIFIER ::= { pktcEventMibObjects 3 }
pktcEvents OBJECT IDENTIFIER ::= { pktcEventMibObjects 4 }
pktcEventLog OBJECT IDENTIFIER ::= { pktcEventMibObjects 5 }
---
-- Event Reporting control objects
---
pktcEventReset OBJECT-TYPE
SYNTAX BITS {
resetEventLogTable(0),
resetEventTable(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object allows a management station to
clear the local log of generated events, reset the
management event descriptions, or both.
---
-- Event Reporting control objects
---
pktcEventReset OBJECT-TYPE
SYNTAX BITS {
resetEventLogTable(0),
resetEventTable(1)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object allows a management station to
clear the local log of generated events, reset the
management event descriptions, or both.
MTAs generate management events. These events are stored in the MIB table pktcEventLogTable. If a management station needs to clear all the current entries (e.g., after a troubleshooting operation is complete), it can do so by setting the resetEventLogTable(0) bit to a value of '1'.
MTA生成管理事件。这些事件存储在MIB表pktcEventLogTable中。如果管理站需要清除所有当前条目（例如，在故障排除操作完成后），可以通过将resetEventLogTable（0）位设置为“1”值来完成。
The MTA is pre-configured with the events that it can generate. This is stored in the MIB table pktcEventTable. This table also contains the descriptions associated with these events. These descriptions can be modified by a management station. However, if the management station wishes to reset the descriptions to factory defaults, it can do so by setting the resetEventTable(1) bit to a value of '1'.
MTA预先配置了它可以生成的事件。这存储在MIB表pktcEventTable中。此表还包含与这些事件相关的说明。管理站可以修改这些说明。但是，如果管理站希望将描述重置为出厂默认值，则可以通过将resetEventTable（1）位设置为值“1”来实现。
The MTA actions are summarized below:
MTA行动总结如下：
Bit resetEventLogTable(0) set to a value of '1' - delete all entries in pktcEventLogTable;
位resetEventLogTable（0）设置为值“1”-删除pktcEventLogTable中的所有条目；
- reset the value of pktcEventLogIndex to '0'.
- 将PKTCEventLoginEx的值重置为“0”。
Bit resetEventTable(1) set to a value of '1' - reset the pktcEventTable to the factory default values.
位resetEventTable（1）设置为值“1”-将pktcEventTable重置为出厂默认值。
Bits resetEventLogTable(0) and resetEventTable(1) set to a value of '1' - perform the above actions as though they were performed individually (in any order).
位resetEventLogTable（0）和resetEventTable（1）设置为值“1”-执行上述操作，就好像它们是单独执行的（以任何顺序）。
Setting a reset bit to a value of '0' MUST NOT result in any action.
将重置位设置为值“0”不得导致任何操作。
The MTA MUST perform the above actions regardless of persistence (i.e., storage in non-volatile memory).
MTA必须执行上述操作，而不考虑持久性（即存储在非易失性内存中）。
The MTA MUST always return a value of '00' when this MIB object is read.
读取此MIB对象时，MTA必须始终返回值“00”。
A management station that resets tables using this MIB
object needs to be careful about the impact to other
management stations that may be reliant on the
information contained in the table(s) being reset. For
example, say management station A creates a specific set
of event descriptions in the event table
(pktcEventTable) for debugging purposes and expects any
generated events to report the modified descriptions. In
such a case, if another management station resets the
event table to factory defaults, any subsequent events
will not contain the modified descriptions expected by
management station A. Such multi-manager contentions are
not addressed within this MIB module. Thus, management
stations are RECOMMENDED to use this MIB object with
care and caution, and only when absolutely required."
::= { pktcEventControl 1 }
A management station that resets tables using this MIB
object needs to be careful about the impact to other
management stations that may be reliant on the
information contained in the table(s) being reset. For
example, say management station A creates a specific set
of event descriptions in the event table
(pktcEventTable) for debugging purposes and expects any
generated events to report the modified descriptions. In
such a case, if another management station resets the
event table to factory defaults, any subsequent events
will not contain the modified descriptions expected by
management station A. Such multi-manager contentions are
not addressed within this MIB module. Thus, management
stations are RECOMMENDED to use this MIB object with
care and caution, and only when absolutely required."
::= { pktcEventControl 1 }
---
-- syslog-specific MIB objects
---
---
-- syslog-specific MIB objects
---
pktcEventSyslog OBJECT IDENTIFIER ::= { pktcEventControl 2 }
pktcEventSyslog OBJECT IDENTIFIER ::= { pktcEventControl 2 }
pktcEventSyslogCapabilities OBJECT-TYPE SYNTAX BITS { formatBSDSyslog(0), formatSyslogProtocol(1), transportUDP(2),
pktcEventSyslogCapabilities对象类型语法位{formatBSDSyslog（0）、formatSyslogProtocol（1）、transportUDP（2），
transportTLS(3), transportBEEP(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB object contains the MTA capabilities for supporting the syslog protocol, specifically the message formats and the transport protocols.
transportTLS（3）、transportBEEP（4）}MAX-ACCESS只读状态当前描述“此MIB对象包含支持syslog协议的MTA功能，特别是消息格式和传输协议。
The BSD syslog message format is specified in [RFC3164] (formatBSDSyslog), and the IETF syslog protocol is specified in [RFC5424] (formatSyslogProtocol).
BSD系统日志消息格式在[RFC3164]（formatBSDSyslog）中指定，IETF系统日志协议在[RFC5424]（formatSyslogProtocol）中指定。
The MTA MUST set the appropriate protocol and
transport bits, based on implementation."
REFERENCE
"The BSD syslog Protocol, [RFC3164];
The Syslog Protocol, [RFC5424];
Transmission of Syslog Messages over UDP, [RFC5426];
TLS Transport Mapping for Syslog, [RFC5425];
Reliable Delivery for syslog, [RFC3195]."
::= { pktcEventSyslog 1 }
The MTA MUST set the appropriate protocol and
transport bits, based on implementation."
REFERENCE
"The BSD syslog Protocol, [RFC3164];
The Syslog Protocol, [RFC5424];
Transmission of Syslog Messages over UDP, [RFC5426];
TLS Transport Mapping for Syslog, [RFC5425];
Reliable Delivery for syslog, [RFC3195]."
::= { pktcEventSyslog 1 }
pktcEventSyslogAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object defines the Internet address type of
the syslog server specified by the MIB object
pktcEventSyslogAddress. A value of dns(16) is
disallowed since a non-resolvable DNS domain name
will leave the device without a syslog server to
which it can report events."
REFERENCE
"PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV]."
DEFVAL { ipv4 }
::= { pktcEventSyslog 2 }
pktcEventSyslogAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object defines the Internet address type of
the syslog server specified by the MIB object
pktcEventSyslogAddress. A value of dns(16) is
disallowed since a non-resolvable DNS domain name
will leave the device without a syslog server to
which it can report events."
REFERENCE
"PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV]."
DEFVAL { ipv4 }
::= { pktcEventSyslog 2 }
pktcEventSyslogAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION "This MIB object contains the IP address of the
pktcEventSyslogAddress对象类型语法InetAddress MAX-ACCESS读写状态当前描述“此MIB对象包含
syslog server to which the MTA can transmit a syslog message upon the generation of a management event. The type of address this object represents is defined by the MIB object pktDevEventSyslogAddressType.
系统日志服务器，MTA可在生成管理事件时向其传输系统日志消息。此对象表示的地址类型由MIB对象PKTDeventsyslogAddressType定义。
The format of the syslog message is specified by the
MIB object pktcEventSyslogMessageFormat."
REFERENCE
"PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV];
PacketCable Management Event Mechanism Specification,
[PKT-SP-MEM1.5];"
DEFVAL { "0.0.0.0" }
::= { pktcEventSyslog 3 }
The format of the syslog message is specified by the
MIB object pktcEventSyslogMessageFormat."
REFERENCE
"PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV];
PacketCable Management Event Mechanism Specification,
[PKT-SP-MEM1.5];"
DEFVAL { "0.0.0.0" }
::= { pktcEventSyslog 3 }
pktcEventSyslogMessageFormat OBJECT-TYPE
SYNTAX INTEGER {
formatBSDSyslog(1), -- The BSD syslog Protocol
formatSyslogProtocol(2) -- The syslog Protocol
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object contains the syslog message format to
be used for transmitting syslog messages to the server
contained in the MIB object pktcEventSyslogServer."
REFERENCE
"The BSD syslog Protocol, [RFC3164];
The Syslog Protocol, [RFC5424]."
DEFVAL { formatSyslogProtocol }
::= { pktcEventSyslog 4 }
pktcEventSyslogMessageFormat OBJECT-TYPE
SYNTAX INTEGER {
formatBSDSyslog(1), -- The BSD syslog Protocol
formatSyslogProtocol(2) -- The syslog Protocol
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object contains the syslog message format to
be used for transmitting syslog messages to the server
contained in the MIB object pktcEventSyslogServer."
REFERENCE
"The BSD syslog Protocol, [RFC3164];
The Syslog Protocol, [RFC5424]."
DEFVAL { formatSyslogProtocol }
::= { pktcEventSyslog 4 }
pktcEventSyslogTransport OBJECT-TYPE
SYNTAX INTEGER {
udp(1),-- Transmission of syslog messages over UDP
tls(2),-- TLS Transport Mapping for Syslog
beep(3)-- BEEP Transport Mapping for Syslog
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object specifies the transport to be
used to transmit syslog messages to the syslog
server contained in the MIB object
pktcEventSyslogAddress.
pktcEventSyslogTransport OBJECT-TYPE
SYNTAX INTEGER {
udp(1),-- Transmission of syslog messages over UDP
tls(2),-- TLS Transport Mapping for Syslog
beep(3)-- BEEP Transport Mapping for Syslog
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object specifies the transport to be
used to transmit syslog messages to the syslog
server contained in the MIB object
pktcEventSyslogAddress.
If the MTA does not support the transport specified in a SET operation, then the
如果MTA不支持集合操作中指定的传输，则
MTA MUST return an appropriate error
response, such as 'inconsistentValue'."
REFERENCE
"Transmission of Syslog messages over UDP, [RFC5426];
TLS Transport Mapping for Syslog, [RFC5425]."
DEFVAL {tls}
::= { pktcEventSyslog 5 }
MTA MUST return an appropriate error
response, such as 'inconsistentValue'."
REFERENCE
"Transmission of Syslog messages over UDP, [RFC5426];
TLS Transport Mapping for Syslog, [RFC5425]."
DEFVAL {tls}
::= { pktcEventSyslog 5 }
pktcEventSyslogPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object contains the port number of the
syslog server to which the syslog messages are to
be transmitted."
REFERENCE
"Transmission of Syslog Messages over UDP, [RFC5426];
TLS Transport Mapping for Syslog, [RFC5425]."
DEFVAL { 6514 }
::= { pktcEventSyslog 6 }
pktcEventSyslogPort OBJECT-TYPE
SYNTAX InetPortNumber
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object contains the port number of the
syslog server to which the syslog messages are to
be transmitted."
REFERENCE
"Transmission of Syslog Messages over UDP, [RFC5426];
TLS Transport Mapping for Syslog, [RFC5425]."
DEFVAL { 6514 }
::= { pktcEventSyslog 6 }
---
-- Event classes
---
---
-- Event classes
---
pktcEventClassTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcEventClassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB table allows for management events that can be
generated by an MTA to be classified into categories,
or 'event classes'. For example, all the configuration-
related events can be associated with an event class
titled 'configuration'. Such a classification allows
for a management station to affect changes on a common
group of events at once. Two operations are specified
on an event class: enabling or disabling of all the
events in an event class, and selective enabling or
disabling based on the severity level."
::= { pktcEventControl 3 }
pktcEventClassTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcEventClassEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB table allows for management events that can be
generated by an MTA to be classified into categories,
or 'event classes'. For example, all the configuration-
related events can be associated with an event class
titled 'configuration'. Such a classification allows
for a management station to affect changes on a common
group of events at once. Two operations are specified
on an event class: enabling or disabling of all the
events in an event class, and selective enabling or
disabling based on the severity level."
::= { pktcEventControl 3 }
pktcEventClassEntry OBJECT-TYPE SYNTAX PktcEventClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
pktcEventClassEntry对象类型语法pktcEventClassEntry MAX-ACCESS不可访问状态当前描述
"Each entry in this table specifies an event class, a grouping of events, as identified by the MTA manufacturer. Any event associated with an event class in this table MUST be specified in the pktcEventTable.
此表中的每个条目都指定一个事件类，一组由MTA制造商标识的事件。与此表中的事件类关联的任何事件都必须在pktcEventTable中指定。
The MTA MUST create one entry (index=100) for the event class titled 'generic'. This event class MUST contain all the events that are not contained in any other vendor-specified event classes.
MTA必须为标题为“generic”的事件类创建一个条目（索引=100）。此事件类必须包含任何其他供应商指定的事件类中未包含的所有事件。
A management station SHOULD NOT associate an event with multiple event classes. However, if an event is associated with multiple event classes, the MTA MUST give precedence to the event class with the lowest index. Thus, at a given point in time, only one event class is applicable for an event.
管理站不应将一个事件与多个事件类关联。但是，如果一个事件与多个事件类关联，MTA必须优先于索引最低的事件类。因此，在给定的时间点，只有一个事件类适用于一个事件。
The event table (pktcEventTable) provides the event class that affects the event. Whenever an event is generated, the MTA MUST verify the applicable event class entry to take any specified actions.
事件表（pktcEventTable）提供影响事件的事件类。每当生成事件时，MTA必须验证适用的事件类条目，以执行任何指定的操作。
Entries in this table persist across resets and
reboots."
INDEX { pktcEventClassIndex }
::= { pktcEventClassTable 1 }
Entries in this table persist across resets and
reboots."
INDEX { pktcEventClassIndex }
::= { pktcEventClassTable 1 }
PktcEventClassEntry::= SEQUENCE {
pktcEventClassIndex Unsigned32,
pktcEventClassName SnmpAdminString,
pktcEventClassStatus TruthValue,
pktcEventClassSeverity SyslogSeverityMask
}
PktcEventClassEntry::= SEQUENCE {
pktcEventClassIndex Unsigned32,
pktcEventClassName SnmpAdminString,
pktcEventClassStatus TruthValue,
pktcEventClassSeverity SyslogSeverityMask
}
pktcEventClassIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..100)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB object is an index into the event
class table. It is a locally meaningful
value."
::= { pktcEventClassEntry 1 }
pktcEventClassIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..100)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB object is an index into the event
class table. It is a locally meaningful
value."
::= { pktcEventClassEntry 1 }
pktcEventClassName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (1..100)) MAX-ACCESS read-only
pktcEventClassName对象类型语法SnmpAdminString（大小（1..100））MAX-ACCESS只读
STATUS current DESCRIPTION "This MIB object contains the name of the event class.
STATUS current DESCRIPTION“此MIB对象包含事件类的名称。
Vendors MAY define different event classes (e.g., DHCP, SNMP, DEBUG) to group together management events of a particular category.
供应商可以定义不同的事件类（例如DHCP、SNMP、调试），以将特定类别的管理事件组合在一起。
Event class names need to take into
consideration the SnmpAdminString definition
requirements, such as the use of control code
sequence CR LF to represent a newline."
::= { pktcEventClassEntry 2 }
Event class names need to take into
consideration the SnmpAdminString definition
requirements, such as the use of control code
sequence CR LF to represent a newline."
::= { pktcEventClassEntry 2 }
pktcEventClassStatus OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "This MIB object indicates if events belonging to the corresponding event class are enabled or disabled, for event reporting.
pktcEventClassStatus对象类型语法TruthValue MAX-ACCESS读写状态当前描述“此MIB对象指示是否为事件报告启用或禁用属于相应事件类的事件。
Setting this object to a value of 'true' enables reporting of all the events in the event class.
将此对象的值设置为“true”可以报告事件类中的所有事件。
When enabled, the means of reporting events is specified by the MIB object pktcEventReporting.
启用时，报告事件的方式由MIB对象pktcEventReporting指定。
Setting this object to a value of 'false' disables any event reporting, irrespective of the value of the MIB object pktcEventReporting for a specific event.
将此对象的值设置为“false”将禁用任何事件报告，而与特定事件的MIB对象pktcEventReporting的值无关。
The default value of this MIB object is vendor-
specific. However, the vendor SHOULD enable all
event categories defined by PacketCable or
IPCablecom by default."
::= { pktcEventClassEntry 3 }
The default value of this MIB object is vendor-
specific. However, the vendor SHOULD enable all
event categories defined by PacketCable or
IPCablecom by default."
::= { pktcEventClassEntry 3 }
pktcEventClassSeverity OBJECT-TYPE SYNTAX SyslogSeverityMask MAX-ACCESS read-write STATUS current DESCRIPTION "This MIB object defines the severity level of events belonging to a specific event class
pktcEventClassSeverity对象类型语法SyslogSeverityMask MAX-ACCESS读写状态当前描述“此MIB对象定义属于特定事件类的事件的严重性级别
that are enabled for event reporting.
为事件报告启用的。
This MIB object has no effect on the event reporting unless the MIB object pktcEventClassStatus is set to a value of 'true' (enabled), for the corresponding event class.
此MIB对象对事件报告没有影响，除非针对相应的事件类将MIB对象pktcEventClassStatus设置为“true”（已启用）的值。
Setting a bit within the mask to a value of '1' implies that events corresponding to that severity level MUST be reported as defined by the corresponding value of 'pktcEventReporting' for events in the event class.
将掩码内的位设置为值“1”意味着必须按照事件类中事件的“pktcEventReporting”对应值的定义报告与该严重性级别对应的事件。
Setting a bit to a value of '0' implies that events corresponding to that level MUST NOT be reported, irrespective of the corresponding value of 'pktcEventReporting' for events in the event class.
将位设置为值“0”意味着不得报告与该级别对应的事件，而与事件类中事件的“pktcEventReporting”对应值无关。
It is recommended that the bits corresponding
to emerg(0), alert(1), crit(2), and err(3)
be set to a value of '1' to ensure reporting of
events requiring immediate attention."
REFERENCE
"The Syslog Protocol, [RFC5424]."
::= { pktcEventClassEntry 4 }
It is recommended that the bits corresponding
to emerg(0), alert(1), crit(2), and err(3)
be set to a value of '1' to ensure reporting of
events requiring immediate attention."
REFERENCE
"The Syslog Protocol, [RFC5424]."
::= { pktcEventClassEntry 4 }
---
-- Event throttling control
---
---
-- Event throttling control
---
pktcEventThrottleAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
unconstrained(1),
maintainBelowThreshold(2),
stopAtThreshold(3),
inhibited(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object controls the throttling of the
transmitted messages upon generation of an event
(SNMP/syslog). It does not affect local logging
of events.
pktcEventThrottleAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
unconstrained(1),
maintainBelowThreshold(2),
stopAtThreshold(3),
inhibited(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object controls the throttling of the
transmitted messages upon generation of an event
(SNMP/syslog). It does not affect local logging
of events.
A value of unconstrained(1) causes event messages
值unconstrated（1）会导致事件消息
to be transmitted without regard to the threshold settings.
在不考虑阈值设置的情况下传输。
A value of maintainBelowThreshold(2) causes event messages to be suppressed if the number of transmissions would otherwise exceed the threshold specified by pktcEventThrottleThreshold over the interval specified by pktcEventThrottleInterval.
如果在pktcEventThrottleInterval指定的时间间隔内，传输次数将超过pktcEventThrottleThreshold指定的阈值，则值maintainBelowThreshold（2）将导致事件消息被抑制。
A value of stopAtThreshold(3) causes event message transmission to cease once the threshold specified by pktcEventThrottleThreshold (over the interval specified by pktcEventThrottleInterval) is reached. Event generation is resumed when the value of this MIB object is modified by a management station or when the device resets or reboots.
一旦达到pktcEventThrottleThreshold指定的阈值（在pktcEventThrottleInterval指定的间隔内），StopAttThreshold（3）的值将导致事件消息传输停止。当管理站修改此MIB对象的值或设备重置或重新启动时，将恢复事件生成。
A value of inhibited(4) causes all event message transmissions to be suppressed.
禁用（4）的值会导致所有事件消息传输被抑制。
An event causing both an SNMP and a syslog message is still treated as a single event.
导致SNMP和syslog消息的事件仍被视为单个事件。
Refer to MIB objects pktcEventThrottleThreshold and
pktcEventThrottleInterval for information on
throttling."
DEFVAL { unconstrained }
::= { pktcEventThrottle 1 }
Refer to MIB objects pktcEventThrottleThreshold and
pktcEventThrottleInterval for information on
throttling."
DEFVAL { unconstrained }
::= { pktcEventThrottle 1 }
pktcEventThrottleThreshold OBJECT-TYPE SYNTAX Unsigned32(0..1024) MAX-ACCESS read-write STATUS current DESCRIPTION "This MIB object contains the number of events per pktcEventThrottleInterval to be transmitted before throttling.
pktcEventThrottleThreshold对象类型语法Unsigned32（0..1024）MAX-ACCESS读写状态当前描述“此MIB对象包含每个pktcEventThrottleInterval在限制前要传输的事件数。
An event resulting in multiple actions (e.g., SNMP and syslog) is still treated as a single event."
导致多个操作（如SNMP和syslog）的事件仍被视为单个事件。”
DEFVAL { 2 }
::= { pktcEventThrottle 2 }
DEFVAL { 2 }
::= { pktcEventThrottle 2 }
pktcEventThrottleInterval OBJECT-TYPE SYNTAX Unsigned32(0..604800) UNITS "seconds" MAX-ACCESS read-write
pktcEventThrottleInterval对象类型语法无符号32（0..604800）单位“秒”最大访问读写
STATUS current
DESCRIPTION
"This MIB object contains the interval over which
the throttle threshold applies."
DEFVAL { 1 }
::= { pktcEventThrottle 3 }
STATUS current
DESCRIPTION
"This MIB object contains the interval over which
the throttle threshold applies."
DEFVAL { 1 }
::= { pktcEventThrottle 3 }
---
-- Reporting of transmission status
---
---
-- Reporting of transmission status
---
pktcEventTransmissionStatus OBJECT-TYPE
SYNTAX BITS {
syslogThrottled(0),
snmpThrottled(1),
validsyslogServerAbsent(2),
validSnmpManagerAbsent(3),
syslogTransmitError(4),
snmpTransmitError(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object reflects the status of the event
transmissions using syslog, SNMP, or both.
pktcEventTransmissionStatus OBJECT-TYPE
SYNTAX BITS {
syslogThrottled(0),
snmpThrottled(1),
validsyslogServerAbsent(2),
validSnmpManagerAbsent(3),
syslogTransmitError(4),
snmpTransmitError(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object reflects the status of the event
transmissions using syslog, SNMP, or both.
If a bit corresponding to a state is set to a value of: '1', it indicates that the state is true '0', it indicates that the state is false
如果与状态相对应的位设置为值“1”，则表示状态为真“0”，表示状态为假
If the MTA is not configured with a syslog server or an SNMP Manager, the corresponding 'throttling' and 'transmit error' bits MUST be set to a value of '0'. For example, if an SNMP Manager is not configured on the MTA, the bit corresponding to validSnmpManagerAbsent(3) is set to a value of '1', and the values of the bits corresponding to snmpThrottled(1) and snmpTransmitError(5) are set to a value of '0'.
如果MTA未配置syslog服务器或SNMP管理器，则相应的“节流”和“传输错误”位必须设置为值“0”。例如，如果未在MTA上配置SNMP管理器，则与ValidSmpManagerabSent（3）相对应的位设置为值“1”，与snmpThrottled（1）和snmpTransmitError（5）相对应的位设置为值“0”。
'Event throttling' is based on thresholds and the current setting of the MIB object pktcEventThrottleAdminStatus.
“事件限制”基于阈值和MIB对象pktcEventThrottleAdminStatus的当前设置。
'Server/Manager' indicators are based on the availability of valid syslog server/SNMP Managers.
“服务器/管理器”指示器基于有效的syslog服务器/SNMP管理器的可用性。
Transmit errors are reported when detected. If an MTA cannot detect an error situation, the value of the BIT will be set '0'.
检测到传输错误时会报告。如果MTA无法检测到错误情况，则位的值将设置为“0”。
It is to be noted that not all the conditions that are
indicated by this MIB object are detectable by all
devices, and when detected may not be accurate. It is
meant to provide a report of the status as determined
by the device during event transmissions."
::= { pktcEventStatus 1 }
It is to be noted that not all the conditions that are
indicated by this MIB object are detectable by all
devices, and when detected may not be accurate. It is
meant to provide a report of the status as determined
by the device during event transmissions."
::= { pktcEventStatus 1 }
---
-- Description of events
---
---
-- Description of events
---
pktcEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB table contains all possible management events
that can be generated by the device. This includes
PacketCable- and IPCablecom-defined events and
vendor-specific events."
::= { pktcEvents 1 }
pktcEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB table contains all possible management events
that can be generated by the device. This includes
PacketCable- and IPCablecom-defined events and
vendor-specific events."
::= { pktcEvents 1 }
pktcEventEntry OBJECT-TYPE
SYNTAX PktcEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created for each
event the MTA implementing this MIB is
capable of reporting. Entries in this table
are persisted across resets and reboots."
INDEX { pktcEventOrganization, pktcEventIdentifier }
::= { pktcEventTable 1 }
pktcEventEntry OBJECT-TYPE
SYNTAX PktcEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in this table is created for each
event the MTA implementing this MIB is
capable of reporting. Entries in this table
are persisted across resets and reboots."
INDEX { pktcEventOrganization, pktcEventIdentifier }
::= { pktcEventTable 1 }
PktcEventEntry::= SEQUENCE {
pktcEventOrganization Unsigned32,
pktcEventIdentifier Unsigned32,
pktcEventFacility SyslogFacility,
pktcEventSeverityLevel SyslogSeverity,
pktcEventReporting BITS,
pktcEventText SnmpAdminString,
pktcEventClass SnmpAdminString
}
PktcEventEntry::= SEQUENCE {
pktcEventOrganization Unsigned32,
pktcEventIdentifier Unsigned32,
pktcEventFacility SyslogFacility,
pktcEventSeverityLevel SyslogSeverity,
pktcEventReporting BITS,
pktcEventText SnmpAdminString,
pktcEventClass SnmpAdminString
}
pktcEventOrganization OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB object provides the IANA enterprise number of
the organization defining the event. Thus, all
PacketCable- or IPCablecom-defined events will contain
the PacketCable or IPCablecom IANA enterprise
number, and all vendor-specific events will contain
the IANA enterprise number of the defining
organization."
REFERENCE
"IANA Private Enterprise Number assignment,
[IANA-ENTERPRISE]."
::= { pktcEventEntry 1 }
pktcEventOrganization OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB object provides the IANA enterprise number of
the organization defining the event. Thus, all
PacketCable- or IPCablecom-defined events will contain
the PacketCable or IPCablecom IANA enterprise
number, and all vendor-specific events will contain
the IANA enterprise number of the defining
organization."
REFERENCE
"IANA Private Enterprise Number assignment,
[IANA-ENTERPRISE]."
::= { pktcEventEntry 1 }
pktcEventIdentifier OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB object contains the event identifier for the
corresponding event."
REFERENCE
"PacketCable Management Event Mechanism Specification,
[PKT-SP-MEM1.5];
PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV]."
::= { pktcEventEntry 2 }
pktcEventIdentifier OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB object contains the event identifier for the
corresponding event."
REFERENCE
"PacketCable Management Event Mechanism Specification,
[PKT-SP-MEM1.5];
PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV]."
::= { pktcEventEntry 2 }
pktcEventFacility OBJECT-TYPE
SYNTAX SyslogFacility
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object contains the facility
for the event.
For PacketCable, IPCablecom, or ETSI events,
this MUST be set to a value of local0(16)."
REFERENCE
"The Syslog Protocol, [RFC5424];
Textual Conventions for Syslog Management,
[RFC5427]."
::= { pktcEventEntry 3 }
pktcEventFacility OBJECT-TYPE
SYNTAX SyslogFacility
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object contains the facility
for the event.
For PacketCable, IPCablecom, or ETSI events,
this MUST be set to a value of local0(16)."
REFERENCE
"The Syslog Protocol, [RFC5424];
Textual Conventions for Syslog Management,
[RFC5427]."
::= { pktcEventEntry 3 }
pktcEventSeverityLevel OBJECT-TYPE SYNTAX SyslogSeverity
pktcEventSeverityLevel对象类型语法SyslogSeverity
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object contains the severity level that
is applicable to the specified event."
REFERENCE
"The Syslog Protocol, [RFC5424];
Textual Conventions for Syslog Management,
[RFC5427]."
::= { pktcEventEntry 4 }
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object contains the severity level that
is applicable to the specified event."
REFERENCE
"The Syslog Protocol, [RFC5424];
Textual Conventions for Syslog Management,
[RFC5427]."
::= { pktcEventEntry 4 }
pktcEventReporting OBJECT-TYPE
SYNTAX BITS {
local(0),
syslog(1),
snmpTrap(2),
snmpInform(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object defines the action to be taken on
occurrence of this event. Bit local(0) refers to local
logging of events; bit sylog(1) refers to the
transmission of events using syslog; bit snmpTrap(2)
refers to the transmission of events using SNMP Traps
(SNMPv2-Trap-PDU); and bit snmpInform(3) refers to the
transmission of events using SNMP INFORMs.
pktcEventReporting OBJECT-TYPE
SYNTAX BITS {
local(0),
syslog(1),
snmpTrap(2),
snmpInform(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object defines the action to be taken on
occurrence of this event. Bit local(0) refers to local
logging of events; bit sylog(1) refers to the
transmission of events using syslog; bit snmpTrap(2)
refers to the transmission of events using SNMP Traps
(SNMPv2-Trap-PDU); and bit snmpInform(3) refers to the
transmission of events using SNMP INFORMs.
Setting a bit to a value of '1' indicates that the corresponding action will be taken upon occurrence of this event. If none of the bits are set, then no action is taken upon occurrence of the event. The success of transmission using syslog and SNMP depends on the MTA configuration. For example, a valid syslog server address is required for syslog message transmission.
将位设置为值“1”表示将在发生此事件时采取相应的操作。如果未设置任何位，则在事件发生时不采取任何操作。使用syslog和SNMP传输的成功与否取决于MTA配置。例如，syslog消息传输需要有效的syslog服务器地址。
Specification of a management event does not necessarily include the actions to be taken upon its generation, i.e., it does not need to specify if a generated event needs to be transmitted via SNMP or syslog, or stored locally. Thus, certain default values are specified, based on the event's severity level specified by the MIB object pktcEventSeverityLevel, as follows: - If the severity level of an event is emerg(0), alert(1), crit(2), or err(3), set the bits for local(0), syslog(1), and snmpInform(3) to a value of '1' and set the remaining bits to a value of '0'.
管理事件的规范不一定包括生成事件时要采取的操作，即，它不需要指定生成的事件是否需要通过SNMP或syslog传输或本地存储。因此，根据MIB对象pktcEventSeverityLevel指定的事件严重性级别，指定某些默认值，如下：-如果事件的严重性级别为emerg（0）、alert（1）、crit（2）或err（3），则将本地（0）、系统日志（1）和SNMPInfo（3）的位设置为值“1”，将其余位设置为值“0”。
- For an event with any other severity level, set
the bits for local(0) and syslog(1) to a value
of '1' and set the rest of the bits to a value
of '0'."
::= { pktcEventEntry 5 }
- For an event with any other severity level, set
the bits for local(0) and syslog(1) to a value
of '1' and set the rest of the bits to a value
of '0'."
::= { pktcEventEntry 5 }
pktcEventText OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..127))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object provides a human-readable
description of the event. Descriptions need
to take into consideration the SnmpAdminString
definition requirements such as the use of
control code sequence CR LF to represent a
newline."
::= { pktcEventEntry 6 }
pktcEventText OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..127))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This MIB object provides a human-readable
description of the event. Descriptions need
to take into consideration the SnmpAdminString
definition requirements such as the use of
control code sequence CR LF to represent a
newline."
::= { pktcEventEntry 6 }
pktcEventClass OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..100)) MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB object represents the event class that affects the event. If an event is associated with only one event class, then its name (pktcEventClassName) is reported. If an event is associated with more than one event class, then the name of the event class with the lowest index in the event class table (pktcEventClassTable) is reported.
pktcEventClass对象类型语法SnmpAdminString（大小（0..100））MAX-ACCESS只读状态当前描述“此MIB对象表示影响事件的事件类。如果事件仅与一个事件类关联，则其名称（pktcEventClassName）报告。如果事件与多个事件类关联，则报告事件类表（pktcEventClassTable）中索引最低的事件类的名称。
See the MIB table pktcEventClassTable for a description of event classes and usage.
有关事件类和用法的说明，请参见MIB表pktcEventClassTable。
Descriptions need to take into consideration the
SnmpAdminString definition requirements, such as
the use of control code sequence CR LF to
represent a newline."
::= { pktcEventEntry 7 }
Descriptions need to take into consideration the
SnmpAdminString definition requirements, such as
the use of control code sequence CR LF to
represent a newline."
::= { pktcEventEntry 7 }
---
-- Log of generated events
---
---
-- Log of generated events
---
pktcEventLogTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcEventLogEntry
PktcEventLogEntry的pktcEventLogTable对象类型语法序列
MAX-ACCESS not-accessible STATUS current DESCRIPTION "This MIB table contains a log of the events generated by the MTA.
MAX-ACCESS不可访问状态当前描述“此MIB表包含MTA生成的事件日志。
A description of all the events that can be generated by the device can be obtained from the MIB table pktcEventTable.
可以从MIB表pktcEventTable中获取设备可以生成的所有事件的描述。
An MTA is not required to persist the contents of this
table across resets."
::= { pktcEventLog 1 }
An MTA is not required to persist the contents of this
table across resets."
::= { pktcEventLog 1 }
pktcEventLogEntry OBJECT-TYPE SYNTAX PktcEventLogEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry in this table describes an event that has occurred, indexed in the chronological order of generation. The details of the event are borrowed from the parameters associated with the corresponding event entry in pktcEventTable at the time of the event generation. While all entries created as such can be cleared using the MIB object pktcEventReset, the event entries themselves cannot be individually deleted."
pktcEventLogEntry对象类型语法pktcEventLogEntry MAX-ACCESS不可访问状态当前说明“此表中的每个条目都描述了已发生的事件，并按生成的时间顺序编制索引。事件的详细信息从生成事件时pktcEventTable中与相应事件项关联的参数中借用。虽然可以使用MIB对象pktcEventReset清除所有创建的条目，但不能单独删除事件条目本身。”
INDEX { pktcEventLogIndex }
::= { pktcEventLogTable 1 }
INDEX { pktcEventLogIndex }
::= { pktcEventLogTable 1 }
PktcEventLogEntry ::= SEQUENCE {
pktcEventLogIndex Unsigned32,
pktcEventLogTime DateAndTime,
pktcEventLogOrganization Unsigned32,
pktcEventLogIdentifier Unsigned32,
pktcEventLogText SnmpAdminString,
pktcEventLogEndpointName SnmpAdminString,
pktcEventLogType BITS,
pktcEventLogTargetInfo SnmpAdminString,
pktcEventLogCorrelationId Unsigned32,
pktcEventLogAdditionalInfo SnmpAdminString
}
PktcEventLogEntry ::= SEQUENCE {
pktcEventLogIndex Unsigned32,
pktcEventLogTime DateAndTime,
pktcEventLogOrganization Unsigned32,
pktcEventLogIdentifier Unsigned32,
pktcEventLogText SnmpAdminString,
pktcEventLogEndpointName SnmpAdminString,
pktcEventLogType BITS,
pktcEventLogTargetInfo SnmpAdminString,
pktcEventLogCorrelationId Unsigned32,
pktcEventLogAdditionalInfo SnmpAdminString
}
pktcEventLogIndex OBJECT-TYPE SYNTAX Unsigned32(1..4294967295) MAX-ACCESS not-accessible
pktcEventLogIndex对象类型语法Unsigned32（1..4294967295）MAX-ACCESS不可访问
STATUS current DESCRIPTION "This MIB object provides relative ordering of the objects in the event log.
STATUS current DESCRIPTION“此MIB对象提供事件日志中对象的相对顺序。
If the MTA implements non-volatile storage, then this object will always increase except when the MIB object reaches a value of 2^32-1.
如果MTA实现非易失性存储，则此对象将始终增加，除非MIB对象达到值2^32-1。
If the MTA does not implement non-volatile storage, then this object will always increase except when the MIB object reaches a value of 2^32-1 or the MTA is reset.
如果MTA未实现非易失性存储，则此对象将始终增加，除非MIB对象达到值2^32-1或MTA重置。
When the value reaches 2^32-1, or an MTA that does
not implement non-volatile storage is reset,
newer events will be stored starting with an index
value of '1' (cyclic rotation)."
::= { pktcEventLogEntry 1 }
When the value reaches 2^32-1, or an MTA that does
not implement non-volatile storage is reset,
newer events will be stored starting with an index
value of '1' (cyclic rotation)."
::= { pktcEventLogEntry 1 }
pktcEventLogTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object provides a human-readable description
of the date and time at which the event occurred.
The value of the date and time contained in this MIB
object SHOULD reflect the date and time used in the
syslog message resulting from the associated event,
if such a syslog message was transmitted."
::= { pktcEventLogEntry 2 }
pktcEventLogTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object provides a human-readable description
of the date and time at which the event occurred.
The value of the date and time contained in this MIB
object SHOULD reflect the date and time used in the
syslog message resulting from the associated event,
if such a syslog message was transmitted."
::= { pktcEventLogEntry 2 }
pktcEventLogOrganization OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object provides the IANA enterprise number of
the organization defining the event. Thus, all
PacketCable- or IPCablecom-defined events will contain
the CableLabs or IPCablecom IANA enterprise number, and
all vendor-specific events will contain the IANA
enterprise number of the defining organization."
::= { pktcEventLogEntry 3 }
pktcEventLogOrganization OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object provides the IANA enterprise number of
the organization defining the event. Thus, all
PacketCable- or IPCablecom-defined events will contain
the CableLabs or IPCablecom IANA enterprise number, and
all vendor-specific events will contain the IANA
enterprise number of the defining organization."
::= { pktcEventLogEntry 3 }
pktcEventLogIdentifier OBJECT-TYPE SYNTAX Unsigned32
PKTCEventLogiIdentifier对象类型语法Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object contains the event identifier for the
corresponding event."
::= { pktcEventLogEntry 4 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object contains the event identifier for the
corresponding event."
::= { pktcEventLogEntry 4 }
pktcEventLogText OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..127))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object contains the contents of
the MIB object pktcEventText, corresponding
to the event, at the moment of generation."
::= { pktcEventLogEntry 5 }
pktcEventLogText OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..127))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB object contains the contents of
the MIB object pktcEventText, corresponding
to the event, at the moment of generation."
::= { pktcEventLogEntry 5 }
pktcEventLogEndpointName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB object contains the unique identifier of the MTA endpoint that generated the corresponding event. If the generated event was not associated with any specific endpoint on the MTA, then this MIB object contains the MTA identifier.
pktcEventLogEndpointName对象类型语法SnmpAdminString（大小（0..255））MAX-ACCESS只读状态当前说明“此MIB对象包含生成相应事件的MTA终结点的唯一标识符。如果生成的事件未与MTA上的任何特定端点关联，则此MIB对象包含MTA标识符。
An MTA endpoint can be uniquely identified using a combination of the MTA identifier and the endpoint number. The MTA is identified via its Fully-Qualified Domain Name (FQDN) and the associated IP address at the given point in time.
MTA端点可以使用MTA标识符和端点编号的组合进行唯一标识。MTA通过其完全限定域名（FQDN）和给定时间点的关联IP地址进行标识。
The format of the value contained by this MIB object is as follows:
此MIB对象包含的值的格式如下：
aaln/n:<FQDN>/<IP>, when it identifies an endpoint, 'n' being the endpoint number; or, <FQDN>/<IP>, when it identifies an MTA.
aaln/n:<FQDN>/<IP>，当它标识端点时，“n”是端点号；或者，<FQDN>/<IP>，当它标识MTA时。
The value contained by this MIB object needs to observe
the SnmpAdminString definition requirements."
::= { pktcEventLogEntry 6 }
The value contained by this MIB object needs to observe
the SnmpAdminString definition requirements."
::= { pktcEventLogEntry 6 }
pktcEventLogType OBJECT-TYPE SYNTAX BITS {
pktcEventLogType对象类型语法位{
local(0), syslog(1), snmpTrap(2), snmpInform(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB object contains the type of actions taken by the MTA when the event indicated by the MIB object pktcEventLogIdentifier occurred.
local（0）、syslog（1）、snmpTrap（2）、snmpinfo（3）}MAX-ACCESS只读状态当前描述“此MIB对象包含发生MIB对象PKTCEventLogiIdentifier指示的事件时MTA采取的操作类型。
A bit with a value of '1' indicates the corresponding action was taken. Setting it to a value of '0' indicates that the corresponding action was not taken.
值为“1”的位表示已采取相应的操作。将其设置为值“0”表示未采取相应的操作。
An event may trigger one or more actions (e.g., syslog
and SNMP) or result only in a local log. An action may
also be prevented due to throttling, in which case it is
not reported by this MIB object."
::= { pktcEventLogEntry 7 }
An event may trigger one or more actions (e.g., syslog
and SNMP) or result only in a local log. An action may
also be prevented due to throttling, in which case it is
not reported by this MIB object."
::= { pktcEventLogEntry 7 }
pktcEventLogTargetInfo OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB object contains a comma-separated list of the actions taken for external notifications, along with the target IP address for the generated events. Locally stored events MUST NOT be recorded in this MIB object.
pktcEventLogTargetInfo对象类型语法SnmpAdminString（大小（0..255））MAX-ACCESS只读状态当前描述“此MIB对象包含一个逗号分隔的外部通知操作列表，以及生成事件的目标IP地址。本地存储的事件不得记录在此MIB对象中。
The syntax is as:
<action-1/IP>,<action-2/IP>,<action-3/IP>
The syntax is as:
<action-1/IP>,<action-2/IP>,<action-3/IP>
Where <action-n/IP> is to be denoted as follows:
For syslog events:
syslog/<IP address of the syslog server>
For SNMP traps:
snmpTrap/<IP address of the SNMP server>
For SNMP INFORMS:
snmpInform/<IP address of the SNMP server>
Where <action-n/IP> is to be denoted as follows:
For syslog events:
syslog/<IP address of the syslog server>
For SNMP traps:
snmpTrap/<IP address of the SNMP server>
For SNMP INFORMS:
snmpInform/<IP address of the SNMP server>
If there are multiple targets for the same type (SNMP traps sent to multiple IP addresses) or if there are multiple message types sent to the same IP (syslog and SNMP sent to the same IP address), they need to be reported individually.
如果同一类型有多个目标（SNMP陷阱发送到多个IP地址），或者如果有多个消息类型发送到同一IP（syslog和SNMP发送到同一IP地址），则需要分别报告它们。
It is to be noted that this MIB object may not be able to store all the data in some cases (e.g., multiple IPv6 addresses), in which case some actions may not be reported. In such cases, the MTA MUST present a value of '...' at the end of the value.
需要注意的是，在某些情况下（例如，多个IPv6地址），此MIB对象可能无法存储所有数据，在这种情况下，可能不会报告某些操作。在这种情况下，MTA必须在值的末尾提供值“…”。
Values contained by this MIB object need to observe the
SnmpAdminString definition requirements."
::= { pktcEventLogEntry 8 }
Values contained by this MIB object need to observe the
SnmpAdminString definition requirements."
::= { pktcEventLogEntry 8 }
pktcEventLogCorrelationId OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB object contains the correlation ID generated by the MTA during the initiation of the last provisioning flow, within or following which the event occurred.
pktcEventLogCorrelationId对象类型语法Unsigned32 MAX-ACCESS只读状态当前描述“此MIB对象包含MTA在上次设置流启动期间生成的相关ID，事件发生在该流内或之后。
Although a correlation ID once generated after MTA reset does not change until next MTA reset, the value of this object will differ for the events preserved across MTA resets in case of a persistent pktcEventLogTable.
虽然在MTA重置后生成的关联ID在下次MTA重置之前不会更改，但对于在持久性pktcEventLogTable的情况下跨MTA重置保留的事件，此对象的值将有所不同。
For more information on the generation of correlation
IDs, refer to the corresponding PacketCable/IPCablecom
Device Provisioning specifications."
REFERENCE
"PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV]."
::= { pktcEventLogEntry 9 }
For more information on the generation of correlation
IDs, refer to the corresponding PacketCable/IPCablecom
Device Provisioning specifications."
REFERENCE
"PacketCable MTA Device Provisioning Specification,
[PKT-SP-PROV]."
::= { pktcEventLogEntry 9 }
pktcEventLogAdditionalInfo OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..255)) MAX-ACCESS read-only STATUS current DESCRIPTION "This MIB object contains additional information in relation to the corresponding event that an MTA might wish to report, such as parameterized data or debugging information. The format is vendor-specific.
pktcEventLogAdditionalInfo对象类型语法SnmpAdminString（大小（0..255））MAX-ACCESS只读状态当前描述“此MIB对象包含与MTA可能希望报告的相应事件相关的附加信息，例如参数化数据或调试信息。格式特定于供应商。
If the MTA cannot provide any additional information for the particular event generated, it MUST populate this
如果MTA无法为生成的特定事件提供任何其他信息，则必须填充此
MIB object with a zero-length OCTET-STRING. Vendors
providing this information need to observe the
SnmpAdminString definition requirements, such as the
use of control code sequence CR LF for newline."
::= { pktcEventLogEntry 10 }
MIB object with a zero-length OCTET-STRING. Vendors
providing this information need to observe the
SnmpAdminString definition requirements, such as the
use of control code sequence CR LF for newline."
::= { pktcEventLogEntry 10 }
---
-- Notifications
---
---
-- Notifications
---
pktcEventNotification NOTIFICATION-TYPE
OBJECTS {
pktcEventLogTime,
pktcEventLogOrganization,
pktcEventLogIdentifier,
pktcEventLogEndpointName,
pktcEventLogCorrelationId,
ifPhysAddress
}
STATUS current
DESCRIPTION
"This Notification MIB object contains the contents for
event reporting.
pktcEventNotification NOTIFICATION-TYPE
OBJECTS {
pktcEventLogTime,
pktcEventLogOrganization,
pktcEventLogIdentifier,
pktcEventLogEndpointName,
pktcEventLogCorrelationId,
ifPhysAddress
}
STATUS current
DESCRIPTION
"This Notification MIB object contains the contents for
event reporting.
It contains the event log time, the organization
ID, the event identifier, the endpoint identifier, the
correlation ID, and the MTA's MAC address."
::= { pktcEventNotifications 1 }
It contains the event log time, the organization
ID, the event identifier, the endpoint identifier, the
correlation ID, and the MTA's MAC address."
::= { pktcEventNotifications 1 }
---
-- Conformance/Compliance
---
---
-- Conformance/Compliance
---
pktcEventCompliances OBJECT IDENTIFIER ::=
{ pktcEventConformance 1 }
pktcEventGroups OBJECT IDENTIFIER ::=
{ pktcEventConformance 2 }
pktcEventCompliances OBJECT IDENTIFIER ::=
{ pktcEventConformance 1 }
pktcEventGroups OBJECT IDENTIFIER ::=
{ pktcEventConformance 2 }
pktcEventBasicCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for devices that implement the event-reporting feature."
pktcEventBasicCompliance MODULE-COMPLIANCE STATUS当前描述“实现事件报告功能的设备的符合性声明”
MODULE --pktcIetfEventMib
模块——pktcIetfEventMib
MANDATORY-GROUPS { pktcEventGroup,
强制组{pktcEventGroup，
pktcEventNotificationGroup }
pktcEventNotificationGroup}
MODULE SNMP-TARGET-MIB
MANDATORY-GROUPS {
snmpTargetBasicGroup,
snmpTargetResponseGroup
}
MODULE SNMP-TARGET-MIB
MANDATORY-GROUPS {
snmpTargetBasicGroup,
snmpTargetResponseGroup
}
MODULE SNMP-NOTIFICATION-MIB
MANDATORY-GROUPS {
snmpNotifyGroup,
snmpNotifyFilterGroup
}
MODULE SNMP-NOTIFICATION-MIB
MANDATORY-GROUPS {
snmpNotifyGroup,
snmpNotifyFilterGroup
}
::= { pktcEventCompliances 3 }
::= { pktcEventCompliances 3 }
pktcEventGroup OBJECT-GROUP
OBJECTS {
pktcEventReset,
pktcEventSyslogCapabilities,
pktcEventSyslogAddressType,
pktcEventSyslogAddress,
pktcEventSyslogTransport,
pktcEventSyslogPort,
pktcEventSyslogMessageFormat,
pktcEventThrottleAdminStatus,
pktcEventThrottleThreshold,
pktcEventThrottleInterval,
pktcEventTransmissionStatus,
pktcEventFacility,
pktcEventSeverityLevel,
pktcEventReporting,
pktcEventText,
pktcEventLogTime,
pktcEventLogOrganization,
pktcEventLogIdentifier,
pktcEventLogText,
pktcEventLogEndpointName,
pktcEventLogType,
pktcEventLogTargetInfo,
pktcEventLogCorrelationId,
pktcEventLogAdditionalInfo,
pktcEventClass,
pktcEventClassName,
pktcEventClassStatus,
pktcEventClassSeverity
}
pktcEventGroup OBJECT-GROUP
OBJECTS {
pktcEventReset,
pktcEventSyslogCapabilities,
pktcEventSyslogAddressType,
pktcEventSyslogAddress,
pktcEventSyslogTransport,
pktcEventSyslogPort,
pktcEventSyslogMessageFormat,
pktcEventThrottleAdminStatus,
pktcEventThrottleThreshold,
pktcEventThrottleInterval,
pktcEventTransmissionStatus,
pktcEventFacility,
pktcEventSeverityLevel,
pktcEventReporting,
pktcEventText,
pktcEventLogTime,
pktcEventLogOrganization,
pktcEventLogIdentifier,
pktcEventLogText,
pktcEventLogEndpointName,
pktcEventLogType,
pktcEventLogTargetInfo,
pktcEventLogCorrelationId,
pktcEventLogAdditionalInfo,
pktcEventClass,
pktcEventClassName,
pktcEventClassStatus,
pktcEventClassSeverity
}
STATUS current
DESCRIPTION
"Group of MIB objects for PacketCable Management Event
MIB."
::= { pktcEventGroups 1 }
STATUS current
DESCRIPTION
"Group of MIB objects for PacketCable Management Event
MIB."
::= { pktcEventGroups 1 }
pktcEventNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { pktcEventNotification }
STATUS current
DESCRIPTION
"Group of MIB objects for notifications related to
change in status of the MTA Device."
::= { pktcEventGroups 2 }
END
pktcEventNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { pktcEventNotification }
STATUS current
DESCRIPTION
"Group of MIB objects for notifications related to
change in status of the MTA Device."
::= { pktcEventGroups 2 }
END
The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
本文档中的MIB模块使用SMI编号注册表中记录的以下IANA分配的对象标识符值：
Descriptor OBJECT IDENTIFIER Value
---------- -----------------------
pktcIetfEventMib { mib-2 182 }
Descriptor OBJECT IDENTIFIER Value
---------- -----------------------
pktcIetfEventMib { mib-2 182 }
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write. 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. Security threats include events unreported on errors, redirection of events (deliberately or otherwise) or minimized reporting of errors. Such threats can mask certain misconfiguration attempts and denial of service attacks that can be recognized and thwarted via event reporting.
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。安全威胁包括未报告错误的事件、事件重定向（有意或无意）或最小化错误报告。此类威胁可以掩盖某些错误配置尝试和拒绝服务攻击，这些攻击可以通过事件报告来识别和阻止。
MIB objects of significance include:
重要的MIB对象包括：
- those that control the event generation, the target syslog address for events and the reporting status, i.e.: pktcEventReset pktcEventSyslogAddressType pktcEventSyslogAddress pktcEventSyslogPort pktcEventSyslogMessageFormat pktcEventSyslogTransport pktcEventClassStatus
- 控制事件生成、事件的目标系统日志地址和报告状态的，即：pktcEventReset pktcEventSyslogAddressType pktcEventSyslogAddress pktcEventSyslogPort pktcEventSyslogMessageFormat pktcEventSyslogTransport pktcEventClassStatus
- those related to event classes, i.e.: pktcEventClassSeverity
- 与事件类相关的，即：pktcEventClassSeverity
- those related to throttling, i.e.: pktcEventThrottleAdminStatus pktcEventThrottleThreshold pktcEventThrottleInterval
- 与节流相关的，即：pktcEventThrottleAdminStatus pktcEventThrottleThreshold pktcEventThrottleInterval
- those related to the event reporting capabilities of an MTA, i.e: pktcEventSeverityLevel pktcEventReporting pktcEventText
- 与MTA的事件报告功能相关的，即：pktcEventSeverityLevel pktcEventReporting pktcEventText
The MIB object pktcEventReset deserves special mention since access to this MIB object can be used to disrupt event collection by management stations. For example, consider a management station that modifies the descriptions in the event table pktcEventTable. It would then expect management events generated by the MTA to reflect the modified values. A rogue management station that has access to the pktcEventReset can reset the event table, resulting in the management station not receiving events with the expected descriptions. Further, a rogue management station with access to pktcEventReset can also clear local logs, eliminating local logs of generated events for management stations that are not configured to receive syslog or SNMP messages. The same concerns apply when allowed management stations performing such operations are unaware of other management stations that may be reliant on the event table or the event log table for management or monitoring. This MIB module does not address such multi-manager contentions, and recommends that the MIB object pktcEventReset be used with caution.
MIB对象pktcEventReset值得特别提及，因为对该MIB对象的访问可用于中断管理站的事件收集。例如，考虑在事件表pktEvestTable中修改描述的管理站。然后，它将期望MTA生成的管理事件反映修改后的值。有权访问pktcEventReset的恶意管理站可以重置事件表，从而导致管理站无法接收具有预期描述的事件。此外，具有pktcEventReset访问权限的恶意管理站还可以清除本地日志，从而消除未配置为接收syslog或SNMP消息的管理站生成的事件的本地日志。当执行此类操作的允许管理站不知道其他管理站可能依赖事件表或事件日志表进行管理或监控时，同样的问题也适用。此MIB模块不处理此类多管理器冲突，建议谨慎使用MIB对象pktcEventReset。
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通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
pktcEventLogTable: This table contains the log of generated event messages. Read access to this table might reveal some specific information that should be kept confidential.
pktcEventLogTable：此表包含生成的事件消息的日志。对此表的读取访问可能会泄露一些应保密的特定信息。
pktcEventTransmissionStatus: This MIB object reveals the status of event transmission and MAY be sensitive in some environments.
pktcEventTransmissionStatus：此MIB对象显示事件传输的状态，在某些环境中可能很敏感。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB 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 perform GET or SET (change/create/delete) operations.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体正确配置为仅授予具有执行GET或SET（更改/创建/删除）操作合法权限的主体（用户）访问对象的权限。
The authors would like to thank the members of the IETF IP over Cable Data Network (IPCDN) working group and the CableLabs PacketCable Provisioning focus team for their contributions, comments, and suggestions.
作者要感谢IETF IP over Cable Data Network（IPCDN）工作组成员和CableLabs PacketCable Provisioning focus团队的贡献、评论和建议。
Special appreciation is extended to the following individuals (in alphabetical order): Dan Romascanu, David Harrington, Greg Nakanishi, Jean-Francois Mule, John Berg, Kevin Marez, Paul Duffy, Peter Bates, Randy Presuhn, Rich Woundy, Rick Vetter, Roy Spitzer, and Satish Kumar.
特别感谢以下个人（按字母顺序）：丹·罗马斯坎努、大卫·哈林顿、格雷格·纳卡尼希、让·弗朗索瓦·穆尔、约翰·伯格、凯文·马雷斯、保罗·达菲、彼得·贝茨、兰迪·普雷森、里奇·沃迪、里克·维特、罗伊·斯皮策和萨蒂什·库马尔。
The primary editor (Sumanth) wishes to acknowledge the MIB doctors David Harrington and Dan Romascanu, Lars Eggert and Pasi Eronen, as well as Rich Woundy for expert feedback and numerous suggestions to improve this document.
主要编辑（Sumanth）希望感谢MIB医生David Harrington和Dan Romascanu、Lars Eggert和Pasi Eronen，以及Rich Woundy提供专家反馈和许多改进本文件的建议。
[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月。
[PKT-SP-PROV] Packetcable MTA Device Provisioning Specification, PKT-SP-PROV-I11-050812.
[PKT-SP-PROV]打包电缆MTA设备供应规范，PKT-SP-PROV-I11-050812。
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002.
[RFC3413]Levi，D.，Meyer，P.，和B.Stewart，“简单网络管理协议（SNMP）应用”，STD 62，RFC 3413，2002年12月。
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, March 2009.
[RFC5424]Gerhards，R.，“系统日志协议”，RFC 54242009年3月。
[RFC5426] Okmianski, A., "Transmission of Syslog Messages over UDP", RFC 5426, March 2009.
[RFC5426]Okmianski，A.，“通过UDP传输系统日志消息”，RFC 5426，2009年3月。
[RFC5425] Miao, F., Ed., Ma, Y., Ed., and J. Salowey, Ed., "Transport Layer Security (TLS) Transport Mapping for Syslog", RFC 5425, March 2009.
[RFC5425]Miao，F.，Ed.，Ma，Y.，Ed.，和J.Salowey，Ed.，“系统日志的传输层安全（TLS）传输映射”，RFC 54252009年3月。
[RFC5427] Keeni, G., "Textual Conventions for Syslog Management", RFC 5427, March 2009.
[RFC5427]Keeni，G.“系统日志管理的文本约定”，RFC 5427，2009年3月。
[RFC3195] New, D. and M. Rose, "Reliable Delivery for syslog", RFC 3195, November 2001.
[RFC3195]New，D.和M.Rose，“系统日志的可靠交付”，RFC 31952001年11月。
[ITU-T-J176] IPCablecom Management Event Mechanism MIB, J.176, ITU-T, August 2002.
[ITU-T-J176]IPCablecom管理事件机制MIB，J.176，ITU-T，2002年8月。
[PKT-SP-EVEMIB1.5] PacketCable(TM) Management Event MIB Specification, PKT-SP-EVEMIB1.5-I02-050812, August, 2005.
[PKT-SP-EVEMIB1.5]PacketCable（TM）管理事件MIB规范，PKT-SP-EVEMIB1.5-I02-050812，2005年8月。
[PKT-SP-MEM1.5] PacketCable(TM) Management Event Mechanism Specification, PKT-SP-MEM1.5-I02-050812, August, 2005.
[PKT-SP-MEM1.5]PacketCable（TM）管理事件机制规范，PKT-SP-MEM1.5-I02-050812，2005年8月。
[ETSITS101909-22] ETSI TS 101 909-22, "Digital Broadband Cable Access to the Public Telecommunications Network", IP Multimedia Time Critical Services, Part 22, Management Event Messages.
[ETSITS101909-22]ETSI TS 101 909-22，“公共电信网络的数字宽带电缆接入”，IP多媒体时间关键业务，第22部分，管理事件消息。
[RFC768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980.
[RFC768]Postel，J.，“用户数据报协议”，STD 6，RFC 768，1980年8月。
[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月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, December 2002.
[RFC3411]Harrington，D.，Presohn，R.，和B.Wijnen，“描述简单网络管理协议（SNMP）管理框架的体系结构”，STD 62，RFC 3411，2002年12月。
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.
[RFC4001]Daniele，M.，Haberman，B.，Routhier，S.，和J.Schoenwaeld，“互联网网络地址的文本约定”，RFC 4001，2005年2月。
[IANA-ENTERPRISE] "IANA Private Enterprise Numbers",
http://www.iana.org/
[IANA-ENTERPRISE] "IANA Private Enterprise Numbers",
http://www.iana.org/
[RFC3164] Lonvick, C., "The BSD Syslog Protocol", RFC 3164, August 2001.
[RFC3164]Lonvick，C.，“BSD系统日志协议”，RFC31642001年8月。
[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月。
[PKT-SP-MGCP] Packetcable Network-Based Call Signaling Protocol Specification, PKT-SP-EC-MGCP-I11-050812.
[PKT-SP-MGCP]基于分组电缆网络的呼叫信令协议规范，PKT-SP-EC-MGCP-I11-050812。
[RFC3435] Andreasen, F. and B. Foster, "Media Gateway Control Protocol (MGCP) Version 1.0", RFC 3435, January 2003.
[RFC3435]Andreasen，F.和B.Foster，“媒体网关控制协议（MGCP）1.0版”，RFC 3435，2003年1月。
[RFC4682] Nechamkin, E. and J-F. Mule, "Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices", RFC 4682, December 2006.
[RFC4682]Nechamkin，E.和J-F.Mule，“PacketCable和IPCablecom兼容设备的多媒体终端适配器（MTA）管理信息库”，RFC 4682，2006年12月。
[PKT-SP-CODEC] Packetcable Audio/Video Codecs Specification, PKT-SP-CODEC-I06-050812.
[PKT-SP-CODEC]打包电缆音频/视频编解码器规范，PKT-SP-CODEC-I06-050812。
Authors' Addresses
作者地址
Sumanth Channabasappa Cable Television Laboratories, Inc. 858 Coal Creek Circle, Louisville, CO 80027, USA
Sumanth Channabasapa有线电视实验室有限公司，地址：美国科罗拉多州路易斯维尔Coal Creek Circle 858号，邮编：80027
Phone: +1 303-661-3307
EMail: Sumanth@cablelabs.com
Phone: +1 303-661-3307
EMail: Sumanth@cablelabs.com
Wim De Ketelaere tComLabs Gildestraat 8 9000 Gent, Belgium
Wim De Ketelaere tComLabs Gildestaat 8 9000，比利时
Phone: +32 9 269 22 90
EMail: deketelaere@tComLabs.com
Phone: +32 9 269 22 90
EMail: deketelaere@tComLabs.com
Eugene Nechamkin Broadcom Corporation 200 - 13711 International Place Richmond, BC, V6V 2Z8, Canada
Eugene Nechamkin Broadcom Corporation 200-13711加拿大不列颠哥伦比亚省里士满国际广场，V6V 2Z8
Phone: +1 604 233 8500
EMail: enechamkin@broadcom.com
Phone: +1 604 233 8500
EMail: enechamkin@broadcom.com