Network Working Group R. Woundy
Request for Comments: 4639 Comcast Cable
Obsoletes: 2669 K. Marez
Category: Standards Track Motorola
December 2006
Network Working Group R. Woundy
Request for Comments: 4639 Comcast Cable
Obsoletes: 2669 K. Marez
Category: Standards Track Motorola
December 2006
Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems
符合数据传输电缆服务接口规范（DOCSIS）的电缆调制解调器和电缆调制解调器终端系统的电缆设备管理信息库
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 IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
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 Data Over Cable Service Interface Specification (DOCSIS)-compliant Cable Modems and Cable Modem Termination Systems.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了一组基本的托管对象，用于基于简单网络管理协议（SNMP）的电缆服务接口规范（DOCSIS）兼容的电缆调制解调器和电缆调制解调器终端系统数据管理。
This memo obsoletes RFC 2669.
本备忘录废除RFC 2669。
Table of Contents
目录
1. The Internet-Standard Management Framework ......................3
2. Glossary ........................................................3
2.1. CATV .......................................................3
2.2. CM or Cable Modem ..........................................3
2.3. CMTS or Cable Modem Termination System .....................3
2.4. DOCSIS or Data-Over-Cable Service Interface Specification ..3
2.5. Downstream .................................................4
2.6. Head-End ...................................................4
2.7. Media Access Control (MAC) Packet ..........................4
2.8. RF .........................................................4
2.9. Simple Network Management Protocol (SNMP) ..................4
2.10. Upstream ..................................................4
3. Introduction ....................................................4
3.1. Structure of the MIB .......................................5
3.1.1. IMPORTed MIB Modules and REFERENCE Clauses ..........6
3.1.2. Persistence Model for Cable Modems ..................6
3.1.3. IPv4 Compliance .....................................6
3.2. Management Requirements ....................................7
3.2.1. Handling of Software Upgrades .......................7
3.2.2. Events and Notifications ............................8
3.2.3. Notification Throttling .............................8
3.2.3.1. Notification Rate Throttling ...............8
3.2.3.2. Limiting the Notification Rate .............9
3.3. Protocol Filters ...........................................9
3.3.1. Inbound LLC Filters: docsDevFilterLLCTable .........10
3.3.2. Special Filters ....................................11
3.3.2.1. IP Spoofing Filters:
docsDevCpeTable, docsDevCpeInetTable ......11
3.3.2.2. SNMP Access Filters:
docsDevNmAccessTable ......................11
3.3.3. IP Filtering: docsDevFilterIpTable .................12
3.3.4. Outbound LLC Filters ...............................13
4. Definitions ....................................................13
5. Acknowledgements ...............................................78
5.1. Revision Descriptions .....................................78
6. Security Considerations ........................................79
7. IANA Considerations ............................................82
8. References .....................................................83
8.1. Normative References ......................................83
8.2. Informative References ....................................85
1. The Internet-Standard Management Framework ......................3
2. Glossary ........................................................3
2.1. CATV .......................................................3
2.2. CM or Cable Modem ..........................................3
2.3. CMTS or Cable Modem Termination System .....................3
2.4. DOCSIS or Data-Over-Cable Service Interface Specification ..3
2.5. Downstream .................................................4
2.6. Head-End ...................................................4
2.7. Media Access Control (MAC) Packet ..........................4
2.8. RF .........................................................4
2.9. Simple Network Management Protocol (SNMP) ..................4
2.10. Upstream ..................................................4
3. Introduction ....................................................4
3.1. Structure of the MIB .......................................5
3.1.1. IMPORTed MIB Modules and REFERENCE Clauses ..........6
3.1.2. Persistence Model for Cable Modems ..................6
3.1.3. IPv4 Compliance .....................................6
3.2. Management Requirements ....................................7
3.2.1. Handling of Software Upgrades .......................7
3.2.2. Events and Notifications ............................8
3.2.3. Notification Throttling .............................8
3.2.3.1. Notification Rate Throttling ...............8
3.2.3.2. Limiting the Notification Rate .............9
3.3. Protocol Filters ...........................................9
3.3.1. Inbound LLC Filters: docsDevFilterLLCTable .........10
3.3.2. Special Filters ....................................11
3.3.2.1. IP Spoofing Filters:
docsDevCpeTable, docsDevCpeInetTable ......11
3.3.2.2. SNMP Access Filters:
docsDevNmAccessTable ......................11
3.3.3. IP Filtering: docsDevFilterIpTable .................12
3.3.4. Outbound LLC Filters ...............................13
4. Definitions ....................................................13
5. Acknowledgements ...............................................78
5.1. Revision Descriptions .....................................78
6. Security Considerations ........................................79
7. IANA Considerations ............................................82
8. References .....................................................83
8.1. Normative References ......................................83
8.2. Informative References ....................................85
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 terms in this document are derived either from normal cable system usage, or from the documents associated with the Data-Over-Cable Service Interface Specification (DOCSIS) process.
本文件中的术语来源于正常电缆系统使用，或来源于与电缆数据服务接口规范（DOCSIS）流程相关的文件。
Originally "Community Antenna Television", now used to refer to any cable or hybrid fiber and cable system used to deliver video signals to a community.
最初是“社区天线电视”，现在用来指用于向社区传送视频信号的任何有线或混合光纤和有线系统。
A CM acts as a "slave" station in a DOCSIS-compliant cable data system.
CM充当DOCSIS兼容电缆数据系统中的“从”站。
A generic term covering a cable bridge or cable router in a head-end. A CMTS acts as the master station in a DOCSIS-compliant cable data system. It is the only station that transmits downstream, and it controls the scheduling of upstream transmissions by its associated CMs.
涵盖前端电缆桥架或电缆路由器的通用术语。CMTS充当DOCSIS兼容电缆数据系统中的主站。它是唯一一个下行传输的站点，并且它通过其相关的CMs控制上行传输的调度。
A term referring to the ITU-T Recommendation J.112 [ITU-T_J.112], Annex B, standard for cable modem systems. [RFI1.0] [RFI1.1] [RFI2.0]
指ITU-T建议J.112[ITU-T_J.112]，附录B，电缆调制解调器系统标准的术语。[RFI1.0][RFI1.1][RFI2.0]
The direction from the head-end towards the subscriber.
从前端到用户的方向。
The origination point in most cable systems of the subscriber video signals. Generally, also the location of the CMTS equipment.
在大多数有线电视系统中，用户视频信号的起始点。一般来说，还包括CMTS设备的位置。
A DOCSIS Packet Data Unit.
DOCSIS分组数据单元。
Radio Frequency.
无线电频率
Protocol used for network access to Management Information Base (MIB) objects. The three most commonly used versions are Version 1 (SNMPv1), Version 2 (SNMPv2c), and Version 3 (SNMPv3).
用于网络访问管理信息库（MIB）对象的协议。三个最常用的版本是版本1（SNMPv1）、版本2（SNMPv2c）和版本3（SNMPv3）。
The direction from the subscriber towards the head-end.
从用户到前端的方向。
This MIB module provides a set of objects required for the management of DOCSIS-compliant Cable Modems (CM) and Cable Modem Termination Systems (CMTS). The specification is derived from the DOCSIS Radio Frequency Interface specification [RFI1.0]. Please note that the DOCSIS 1.0 standard only required that Cable Modems implement SNMPv1 and to process Internet Protocol Version 4 (IPv4) customer traffic. Design choices in the original version of this MIB module reflected those requirements. DOCSIS 1.1 [RFI1.1] and DOCSIS 2.0 [RFI2.0] require support for SNMPv3, as well as for SNMPv1 and SNMPv2c, and the changes in this MIB module over the previous proposed standard version reflect those additional requirements.
该MIB模块提供了管理符合DOCSIS的电缆调制解调器（CM）和电缆调制解调器终端系统（CMT）所需的一组对象。本规范源自DOCSIS射频接口规范[RFI1.0]。请注意，DOCSIS 1.0标准仅要求电缆调制解调器实现SNMPv1并处理Internet协议版本4（IPv4）客户流量。这些MIB的选择反映在最初的MIB设计版本中。DOCSIS 1.1[RFI1.1]和DOCSIS 2.0[RFI2.0]需要对SNMPv3以及SNMPv1和SNMPv2c的支持，与先前提议的标准版本相比，此MIB模块中的更改反映了这些附加要求。
Future versions of DOCSIS, starting with DOCSIS 3.0 [MULPI3.0], are expected to require support for the Internet Protocol Version 6 (IPv6) as both a Customer Premise Equipment (CPE) protocol and one supported by the network elements of the DOCSIS CMTS/CM system.
从DOCSIS 3.0[MULPI3.0]开始，DOCSIS的未来版本预计需要对互联网协议版本6（IPv6）的支持，作为客户前提设备（CPE）协议和DOCSIS CMTS/CM系统网元支持的协议。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
This MIB module is structured into seven components. A component contains one or more MIB groups related by deprecation or logical extension.
该MIB模块由七个组件组成。组件包含一个或多个通过弃用或逻辑扩展相关的MIB组。
o The docsDevBaseGroup extends the MIB-II 'system' group of RFC3418 [RFC3418] with objects needed for cable device system management. Related to this group is the docsDevBaseIgmpGroup (enabling Internet Group Management Protocol (IGMP) status and control) and the docsDevBaseMaxCpeGroup (managing the maximum number of CPEs permitted access through the cable modem).
o docsDevBaseGroup使用电缆设备系统管理所需的对象扩展RFC3418[RFC3418]的MIB-II“系统”组。与此组相关的是docsDevBaseIgmpGroup（启用Internet组管理协议（IGMP）状态和控制）和docsDevBaseMaxCpeGroup（管理通过电缆调制解调器允许访问的最大CPE数）。
o The docsDevNmAccessGroup and the docsDevNmAccessExtGroup provide a minimum level of SNMP access security (see Section 2.7 of [OSSI1.0], Section 2 of [OSSI1.1], and Section 5 of [OSSI2.0]). With the completion of the SNMP coexistence document, RFC 3584 [RFC3584], these groups have been deprecated in this version of the MIB.
o docsDevNmAccessGroup和docsDevNmAccessExtGroup提供最低级别的SNMP访问安全性（请参见[OSI1.0]第2.7节、[OSI1.1]第2节和[OSI2.0]第5节）。随着SNMP共存文档RFC 3584[RFC3584]的完成，这些组在本版本的MIB中已被弃用。
o The docsDevSoftwareGroup, updated by the docsDevSoftwareGroupV2, provides information for network-downloadable software upgrades. See "Handling of Software Upgrades", below.
o docsDevSoftwareGroupV2更新的docsDevSoftwareGroupV2提供了网络下载软件升级的信息。请参阅下面的“软件升级的处理”。
o The docsDevServerGroup, updated by the docsDevServerGroupV2, provides information about the progress of the interaction between the CM or CMTS and various provisioning servers.
o 由docsDevServerGroupV2更新的docsDevServerGroup提供了有关CM或CMT与各种供应服务器之间交互进度的信息。
o The docsDevEventGroup, updated by the docsDevEventGroupV2, provides control and logging for event reporting. With the addition of the SNMP Notification MIB, RFC 3413 [RFC3413], and Notification Log MIB, RFC 3014 [RFC3014], which cover event reporting, the objects in this MIB module have been modified to allow for the usage of these RFCs.
o docsDevEventGroup由docsDevEventGroup V2更新，为事件报告提供控制和日志记录。随着SNMP通知MIB RFC 3413[RFC3413]和通知日志MIB RFC 3014[RFC3014]的添加（涉及事件报告），此MIB模块中的对象已被修改，以允许使用这些RFC。
o The docsDevFilterGroup configures filters at the link layer and IP layer for bridged data traffic. This group has been deprecated in this version of the MIB in favor of the docsDevFilterLLCGroup, and by groups from the Differentiated Services MIB [RFC3289] -- specifically, the groups representing the Data Path, Classifier, and Actions tables from that MIB.
o docsDevFilterGroup在链路层和IP层为桥接数据流量配置过滤器。在这个版本的MIB中，该组已被弃用，取而代之的是docsDevFilterLLCGroup，以及来自Differentied Services MIB[RFC3289]的组，具体来说，这些组表示来自该MIB的数据路径、分类器和操作表。
o The docsDevCpeGroup, updated by the docsDevInetCpeGroup, provides control over which IP addresses may be used by CPEs (e.g., PCs) serviced by a given cable modem. This provides anti-spoofing control at the point of origin for a large cable modem system. This group is separate from docsDevFilter, primarily as this group is only implemented on the Cable Modem (CM) and MUST NOT be implemented on the Cable Modem Termination System (CMTS).
o docsDevCpeGroup由docsDevInetCpeGroup更新，用于控制由给定电缆调制解调器提供服务的CPE（如PC）可以使用哪些IP地址。这为大型电缆调制解调器系统在原点提供了反欺骗控制。此组与docsDevFilter分开，主要是因为此组仅在电缆调制解调器（CM）上实现，不得在电缆调制解调器终端系统（CMTS）上实现。
This MIB module IMPORTs definitions normatively from the following MIB modules, beyond [RFC2578], [RFC2579], and [RFC2580]: INET-ADDRESS-MIB [RFC4001], SNMP-FRAMEWORK-MIB [RFC3411], IF-MIB [RFC2863], RMON2-MIB [RFC4502], and DIFFSERV-MIB [RFC3289].
此MIB模块从[RFC2578]、[RFC2579]和[RFC2580]之外的下列MIB模块标准化导入定义：INET-ADDRESS-MIB[RFC4001]、SNMP-FRAMEWORK-MIB[RFC3411]、IF-MIB[RFC2863]、RMON2-MIB[RFC4502]和DIFFSERV-MIB[RFC3289]。
This MIB module also includes DESCRIPTION and REFERENCE clauses that normatively refer to [RFC868], [RFC3617], [RFI1.0], [RFI1.1], [RFI2.0], [OSSI1.1], and [OSSI2.0].
该MIB模块还包括规范性引用[RFC868]、[RFC3617]、[RFI1.0]、[RFI1.1]、[RFI2.0]、[OSI1.1]和[OSI2.0]的描述和参考条款。
Most of the tables in this MIB module (e.g., docsDevNmAccessTable, docsDevFilterLLCTable) are specified not to let objects persist across reboots.
此MIB模块中的大多数表（例如Docsdevnmaccestable、docsDevFilterLLCTable）都被指定为不允许对象在重新启动期间持久化。
The expectation (and current operational practice) is that upon reboot, these tables are cleared and repopulated from the DOCSIS configuration file supplied by the cable operator. This approach enables a cable modem to adapt to the current cable operator's environment, which in turn enables cable modem portability across different cable operators.
预期（和当前操作实践）是，重新启动后，这些表将从电缆运营商提供的DOCSIS配置文件中清除并重新填充。这种方法使电缆调制解调器能够适应当前电缆运营商的环境，从而使电缆调制解调器能够跨不同的电缆运营商进行移植。
A notable exception to the persistence model is docsDevEventTable, since it is useful to maintain a record of events across reboots for debugging purposes.
持久性模型的一个显著的例外是docsdeventtable，因为为了调试的目的，在重新启动时维护事件记录非常有用。
Please note that the compliance statements in this version of the MIB module require support only for IPv4 addresses. That is because the current versions of the DOCSIS protocols (1.0, 1.1, and 2.0) are not IPv6 capable. Although support for IPv6 will require changes to the DOCSIS protocols, it is expected that the only changes needed to the MIB module itself will be the addition of new compliance statements that mandate support for IPv6 addresses.
请注意，此版本的MIB模块中的符合性声明仅要求支持IPv4地址。这是因为DOCSIS协议的当前版本（1.0、1.1和2.0）不支持IPv6。尽管对IPv6的支持需要对DOCSIS协议进行更改，但预计MIB模块本身所需的唯一更改将是添加新的法规遵从性声明，强制支持IPv6地址。
The Cable Modem software upgrade process is documented in [RFI1.0]. From a network management station, the operator
电缆调制解调器软件升级过程记录在[RFI1.0]中。从网络管理站，操作员
o sets docsDevSwServer to the address of the Trivial File Transfer Protocol (TFTP) server for software upgrades;
o 将docsDevSwServer设置为用于软件升级的普通文件传输协议（TFTP）服务器的地址；
o sets docsDevSwFilename to the file pathname of the software upgrade image; and
o 将docsDevSwFilename设置为软件升级映像的文件路径名；和
o sets docsDevSwAdminStatus to upgrade-from-mgt.
o 将docsDevSwAdminStatus设置为从mgt升级。
Although DOCSIS only specifies the implementation of the TFTP protocol [RFC1350] for file transfers, other functional entities embedded within the cable device (particularly a PacketCable Multimedia Terminal Adapter [MTA-PROV]) specify the optional implementation of the Hyper Text Transfer Protocol (HTTP) [RFC1945] and [RFC2616] for file transfers. The value of the docsDevSwServerTransportProtocol object determines which protocol is used for SNMP-initiated software upgrade.
尽管DOCSIS仅规定了文件传输的TFTP协议[RFC1350]的实现，但嵌入电缆设备中的其他功能实体（特别是PacketCable多媒体终端适配器[MTA-PROV]）规定了超文本传输协议（HTTP）[RFC1945]和[RFC2616]的可选实现用于文件传输。docsDevSwServerTransportProtocol对象的值确定用于SNMP启动的软件升级的协议。
One reason for the SNMP-initiated upgrade is to allow loading of a temporary software image (e.g., special diagnostic software) that differs from the software normally used on that device without changing the provisioning database.
SNMP启动升级的一个原因是允许加载与该设备上通常使用的软件不同的临时软件映像（例如，特殊诊断软件），而无需更改配置数据库。
Note that software upgrades should not be accepted blindly by the cable device. The cable device may refuse an upgrade if
请注意，电缆设备不应盲目接受软件升级。如果出现以下情况，电缆设备可能会拒绝升级：
o the download is incomplete;
o 下载不完整；
o the file contents are incomplete or damaged; or
o 文件内容不完整或损坏；或
o the software is not intended for that hardware device (this may include the case of a feature set that has not been purchased for this device).
o 软件不适用于该硬件设备（这可能包括尚未为此设备购买的功能集的情况）。
A cable device that implements the code verification mechanisms of [BPIPLUS] verifies the source and integrity of the downloaded image by validating one or more Code Verification Signatures that are bundled within the software upgrade.
实现[BPIPLUS]代码验证机制的电缆设备通过验证捆绑在软件升级中的一个或多个代码验证签名来验证下载映像的源代码和完整性。
This MIB module provides control facilities for reporting events through syslog [RFC3164], notifications (traps and informs), and non-volatile logging. Additional controls allow the agent to use the SNMP Notification MIB [RFC3413] and Notification Log MIB [RFC3014] for event notification.
该MIB模块提供了通过syslog[RFC3164]、通知（陷阱和通知）和非易失性日志记录报告事件的控制设施。其他控件允许代理使用SNMP通知MIB[RFC3413]和通知日志MIB[RFC3014]进行事件通知。
The conventions for event reporting are outside the scope of this document. The definition and coding of common DOCSIS notifications can be found in [RFC4547].
事件报告的约定不在本文件的范围内。常见DOCSIS通知的定义和编码见[RFC4547]。
The CM and CMTS MUST provide support for notification message throttling as described below. The network operator can employ notification rate throttling or notification limiting by manipulating the appropriate MIB variables.
CM和CMT必须提供如下所述的通知消息限制支持。网络运营商可以通过操纵适当的MIB变量来采用通知速率限制或通知限制。
Network operators may employ either of two rate control methods. In the first method, the device ceases to send notifications when the rate exceeds the specified maximum message rate. It resumes sending notifications only if reactivated by a network management station request.
网络运营商可采用两种速率控制方法之一。在第一种方法中，当速率超过指定的最大消息速率时，设备停止发送通知。仅当网络管理站请求重新激活时，它才恢复发送通知。
In the second method, the device resumes sending notifications when the rate falls below the specified maximum message rate.
在第二种方法中，当速率低于指定的最大消息速率时，设备恢复发送通知。
The network operator configures the specified maximum message rate by setting the measurement interval (in seconds), and the maximum number of notifications to be transmitted within the measurement interval. The operator can query the operational throttling state (to determine whether notifications are enabled or blocked by throttling) of the device, as well as query and set the administrative throttling state (to manage the rate control method) of the device.
网络运营商通过设置测量间隔（以秒为单位）和在测量间隔内传输的最大通知数来配置指定的最大消息速率。操作员可以查询设备的操作节流状态（确定是通过节流启用还是阻止通知），也可以查询和设置设备的管理节流状态（管理速率控制方法）。
Network operators may wish to limit the number of notifications sent by a device over a specified time period. The device ceases to send notifications when the number of notifications exceeds the specified threshold. It resumes sending notifications only when the measurement interval has passed.
网络运营商可能希望限制设备在指定时间段内发送的通知数量。当通知数超过指定阈值时，设备停止发送通知。它仅在测量间隔已过时才恢复发送通知。
The network operator defines the maximum number of notifications he is willing to handle and sets the measurement interval to a large number (in hundredths of a second). For this case, the administrative throttling state is set to stop at a threshold that is the maximum number of notifications.
网络运营商定义他愿意处理的最大通知数量，并将测量间隔设置为一个较大的数字（百分之一秒）。对于这种情况，管理限制状态设置为在最大通知数的阈值处停止。
See "Techniques for Managing Asynchronously Generated Alerts" [RFC1224] for additional technical motivations.
有关其他技术动机，请参阅“管理异步生成警报的技术”[RFC1224]。
The Cable Device MIB provides objects for both Link Layer Control (LLC) and IP protocol filters. The LLC protocol filter entries can be used to limit CM forwarding to a restricted set of network-layer protocols (such as IP, Internetwork Packet Exchange (IPX), Network Basic Input/Output System (NetBIOS), and Appletalk).
电缆设备MIB为链路层控制（LLC）和IP协议过滤器提供对象。LLC协议筛选器条目可用于将CM转发限制为一组受限的网络层协议（如IP、网络间数据包交换（IPX）、网络基本输入/输出系统（NetBIOS）和Appletalk）。
The IP protocol filter entries can be used to restrict upstream or downstream traffic according to source and destination IP addresses, transport-layer protocols (such as Transport Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Control Message Protocol (ICMP)), and source and destination TCP/UDP port numbers.
IP协议筛选器条目可用于根据源和目标IP地址、传输层协议（如传输控制协议（TCP）、用户数据报协议（UDP）和Internet控制消息协议（ICMP））以及源和目标TCP/UDP端口号限制上游或下游流量。
In general, a cable modem applies filters (or, more properly, classifiers) in an order appropriate to the layering model. Specifically, the inbound MAC (or LLC) layer filters are applied first, then the "special" filters, then the IP layer inbound filters, then the IP layer outbound filters, and then any final LLC outbound filters.
通常，电缆调制解调器按照适合分层模型的顺序应用过滤器（或者更恰当地说，分类器）。具体来说，首先应用入站MAC（或LLC）层过滤器，然后是“特殊”过滤器，然后是IP层入站过滤器，然后是IP层出站过滤器，然后是任何最终的LLC出站过滤器。
*****************
* LLC Filter In *
*****************
|
v
*******************
* Special Filters *
* | *
* V *
* ************ *
* * IP Spoof * *
* ************ *
* | *
* v *
* *************** *
* * SNMP Access * *
* *************** *
* | *
*******************
|
v
****************
* IP Filter In *
****************
|
v
*****************
* IP Filter Out *
*****************
|
v
******************
* LLC Filter Out *
******************
*****************
* LLC Filter In *
*****************
|
v
*******************
* Special Filters *
* | *
* V *
* ************ *
* * IP Spoof * *
* ************ *
* | *
* v *
* *************** *
* * SNMP Access * *
* *************** *
* | *
*******************
|
v
****************
* IP Filter In *
****************
|
v
*****************
* IP Filter Out *
*****************
|
v
******************
* LLC Filter Out *
******************
The inbound LLC (or MAC or level-2) filters are contained in the docsDevFilterLLCTable and are applied to level-2 frames entering the cable modem from either the RF MAC interface or from one of the CPE interfaces (physical or logical). These filters are used to prohibit the processing and forwarding of certain types of level-2 traffic that may be disruptive to the network. The filters, as currently specified, can be set to cause the modem either to drop frames that match at least one filter, or to process a frame that matches at least one filter. Some examples of possible configurations would be to permit only IP (and ARP) traffic, or to drop NetBIOS traffic.
入站LLC（或MAC或2级）过滤器包含在DocsdevFilterllc表中，并应用于从RF MAC接口或其中一个CPE接口（物理或逻辑）进入电缆调制解调器的2级帧。这些筛选器用于禁止处理和转发可能中断网络的某些类型的2级流量。当前指定的筛选器可以设置为使调制解调器丢弃至少与一个筛选器匹配的帧，或处理至少与一个筛选器匹配的帧。一些可能的配置示例是只允许IP（和ARP）流量，或放弃NetBIOS流量。
Special filters are applied after the packet is accepted from the MAC layer by the IP module, but before any other processing is done. They are filters that apply only to a very specific class of traffic.
在IP模块从MAC层接受数据包之后，但在完成任何其他处理之前，应用特殊过滤器。它们是仅适用于非常特定类别流量的过滤器。
IP spoofing filters are applied to packets entering the modem from one of the CPE interfaces and are intended to prevent a subscriber from stealing or misusing IP addresses that were not assigned to the subscriber. If the filters are active (enabled), the source address of the IP packet must match at least one IP address in one of these two tables (docsDevCpeTable or docsDevCpeInetTable), or it is discarded without further processing.
IP欺骗过滤器应用于从CPE接口之一进入调制解调器的数据包，旨在防止订户窃取或误用未分配给订户的IP地址。如果筛选器处于活动状态（已启用），则IP数据包的源地址必须至少与这两个表（docsDevCpeTable或docsDevCpeInetTable）中的一个表中的一个IP地址匹配，否则将在不进行进一步处理的情况下丢弃。
To prevent potential implementation ambiguity, the device consults the docsDevCpeTable for the IP packet source address before consulting the docsDevCpeInetTable.
为了防止潜在的实现歧义，设备在查阅DOCSDEVCPEINETABLE之前先查阅DOCSDEVCETABLE以获取IP数据包源地址。
The table can be automatically populated where the first N different IP addresses seen from the CPE side of the cable modem are used to populate the table automatically. The spoofing filters are specified in the docsDevCpeTable and the docsDevCpeInetTable, and the policy for automatically creating filters in those tables is controlled by docsDevCpeEnroll and docsDevMaxCpe, as well as by the network management agent.
当从电缆调制解调器的CPE侧看到的前N个不同IP地址用于自动填充表格时，可以自动填充表格。欺骗筛选器在docsDevCpeTable和DocsdevcPeineTable中指定，在这些表中自动创建筛选器的策略由DocsdevcPeanRoll和docsDevMaxCpe以及网络管理代理控制。
Similar IP spoofing filter controls are defined for CMTS implementation in the Subscriber Management MIB [RFC4036].
在订户管理MIB[RFC4036]中为CMTS实现定义了类似的IP欺骗筛选器控件。
The SNMP access filters are applied to SNMP packets entering from any interface and destined for the cable modem. If the packets enter from a CPE interface, the SNMP filters are applied after the IP spoofing filters. The filters only apply to SNMPv1 or SNMPv2c traffic and are not consulted for SNMPv3 traffic (and need not be implemented by a v3-only agent). SNMPv3 access control is specified in the User Security Model MIB, in [RFC3414].
SNMP访问筛选器应用于从任何接口进入并发送到电缆调制解调器的SNMP数据包。如果数据包从CPE接口进入，则在IP欺骗过滤器之后应用SNMP过滤器。这些过滤器仅适用于SNMPv1或SNMPv2c流量，不适用于SNMPv3流量（并且不需要仅由v3代理实现）。SNMPv3访问控制在[RFC3414]中的用户安全模型MIB中指定。
With the completion of the SNMP coexistence document, RFC 3584 [RFC3584], docsDevNmAccess table has been deprecated in this version of the MIB. See the body of the MIB for the description of how agents should handle the interaction between RFC 3584 MIBs and this MIB.
随着SNMP共存文档RFC 3584[RFC3584]的完成，DOCSDEVNMACESS表在该版本的MIB中已被弃用。有关代理应如何处理RFC3584 MIB与此MIB之间的交互的描述，请参见MIB正文。
The IP Filtering table acts as a classifier table. Each row in the table describes a template against which IP packets are compared. The template includes source and destination addresses (and their associated masks), upper level protocol (e.g., TCP, UDP), source and destination port ranges, and Terms of Service (ToS) values. A row also contains interface and traffic direction match values that have to be considered in combination. All columns of a particular row must match the appropriate fields in the packet and must match the interface and direction items for the packet to result in a match to the packet.
IP筛选表充当分类器表。表中的每一行都描述了一个用于比较IP数据包的模板。该模板包括源和目标地址（及其相关掩码）、上层协议（例如TCP、UDP）、源和目标端口范围以及服务条款（ToS）值。行还包含必须结合考虑的接口和交通方向匹配值。特定行的所有列必须与数据包中的相应字段匹配，并且必须与数据包的接口和方向项匹配，才能与数据包匹配。
When classifying a packet, each table is scanned, beginning with the lowest number filter. If the agent finds a match, it applies the group of policies specified. If the matched filter has the continue bit set, the agent continues the scan possibly matching additional filters and applying additional policies. For example, this allows the agent to take one set of actions for the 24.0.16/255.255.255.0 group and one set of actions for telnet packets to/from 24.0.16.30, and these sets of actions may not be mutually exclusive.
对数据包进行分类时，将扫描每个表，从数字最少的过滤器开始。如果代理找到匹配项，它将应用指定的策略组。如果匹配的筛选器设置了continue位，则代理将继续扫描，可能会匹配其他筛选器并应用其他策略。例如，这允许代理对24.0.16/255.255.255.0组执行一组操作，对从24.0.16.30到24.0.16.30的telnet数据包执行一组操作，并且这些操作可能不是相互排斥的。
Once a packet is matched, one of three actions happen according to the setting of docsDevFilterIpControl in the row. The packet may be dropped, in which case no further processing is required. The packet may be accepted, and processing of the packet continues. Lastly, the packet may have a set of policy actions applied to it. If docsDevFilterIpContinue is set to true, scanning of the table continues and additional matches may result.
匹配数据包后，根据行中docsDevFilterIpControl的设置，将执行三个操作之一。包可能被丢弃，在这种情况下，不需要进一步处理。可以接受分组，并且分组的处理继续。最后，数据包可以应用一组策略操作。如果docsDevFilterIpContinue设置为true，则表的扫描将继续，并可能导致其他匹配。
When a packet matches and docsDevFilterIpControl in the filter matched is set to 'policy', the value of docsDevFilterIpPolicyId is used as a selector into the docsDevFilterPolicyTable. The first level of indirection may result in zero or more actions being taken according to the match. The docsDevFilterPolicyTable is scanned in row order, and all rows where docsDevFilterPolicyId equals docsDevFilterIpPolicyId have the action specified by the docsDevFilterPolicyValue 'executed'.
当数据包匹配且匹配的筛选器中的docsDevFilterIpControl设置为“策略”时，docsDevFilterIpPolicyId的值将用作docsDevFilterPolicyTable中的选择器。第一级间接寻址可能导致根据匹配执行零个或多个操作。docsDevFilterPolicyTable按行顺序扫描，docsDevFilterPolicyId等于docsDevFilterIpPolicyId的所有行都具有docsDevFilterPolicyValue“已执行”指定的操作。
For an example of the use of these IP Filtering MIB tables, see [RFC2669].
有关使用这些IP筛选MIB表的示例，请参阅[RFC2669]。
The IP Filtering table and related tables have been deprecated in this version of the MIB in favor of the Data Path, Classifier, and Action tables from the Differentiated Services MIB [RFC3289]. See the body of the MIB for the description of how agents should handle the interaction between RFC 3289 MIBs and this MIB module.
在这个版本的MIB中，IP筛选表和相关表已被弃用，取而代之的是来自区分服务MIB的数据路径、分类器和操作表[RFC3289]。有关代理应如何处理RFC 3289 MIB与此MIB模块之间的交互的描述，请参见MIB正文。
Lastly, any outbound LLC filters are applied to the packet just prior to its being emitted on the appropriate interface. This MIB module does not specify any outbound LLC filters, but section 3 of the DOCSIS Quality of Service (QoS) MIB, [RFC4323], includes outbound LLC filtering requirements.
最后，任何出站LLC过滤器都将在数据包在适当接口上发出之前应用于该数据包。此MIB模块未指定任何出站LLC过滤器，但DOCSIS服务质量（QoS）MIB[RFC4323]第3节包括出站LLC过滤要求。
DOCS-CABLE-DEVICE-MIB DEFINITIONS ::= BEGIN
DOCS-CABLE-DEVICE-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, IpAddress, Unsigned32, Counter32, Integer32, zeroDotZero, mib-2 FROM SNMPv2-SMI -- RFC 2578 RowStatus, RowPointer, DateAndTime, TruthValue, StorageType FROM SNMPv2-TC -- RFC 2579 InetAddressType, InetAddress FROM INET-ADDRESS-MIB -- RFC 4001 OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF -- RFC 2580 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC 3411 InterfaceIndexOrZero FROM IF-MIB -- RFC 2863 ZeroBasedCounter32 FROM RMON2-MIB -- RFC 4502 diffServMIBDataPathGroup, diffServMIBClfrGroup, diffServMIBClfrElementGroup, diffServMIBMultiFieldClfrGroup, diffServMIBActionGroup, diffServMIBDscpMarkActGroup, diffServMIBCounterGroup, diffServMIBAlgDropGroup,
从SNMPv2 SMI中导入MODULE-IDENTITY、OBJECT-TYPE、IpAddress、Unsigned32、Counter32、Integer32、zeroDotZero、mib-2--从SNMPv2 TC中导入RFC 2578 RowStatus、RowPointer、DateAndTime、TruthValue、StorageType--从INET-ADDRESS-mib中导入RFC 2579 InetAddressType、InetAddress--RFC 4001 OBJECT-GROUP，SNMPv2 CONF中的模块遵从性--从SNMP-FRAMEWORK-MIB中的RFC 2580 SNMPAdminInstalling--从IF-MIB中的RFC 3411 InterfaceIndexOrZero--从RMON2-MIB中的RFC 2863 ZeroBasedCounter32--RFC 4502 diffServMIBDataPathGroup、DiffServMibClfGroup、diffServMIBClfrElementGroup、diffServMIBMultiFieldClfrGroup、diffServMIBActionGroup、，DiffServMibDscMarkActGroup、diffServMIBCounterGroup、diffServMIBAlgDropGroup、，
diffServDataPathStatus, diffServClfrStatus, diffServClfrElementStatus, diffServMultiFieldClfrAddrType, diffServMultiFieldClfrSrcAddr, diffServMultiFieldClfrDstAddr, diffServAlgDropStatus, diffServDataPathStorage, diffServClfrStorage, diffServClfrElementStorage, diffServMultiFieldClfrStorage, diffServActionStorage, diffServCountActStorage, diffServAlgDropStorage, diffServAlgDropType FROM DIFFSERV-MIB; -- RFC 3289
diffServDataPathStatus、diffServClfrStatus、DiffServClfRlementStatus、DiffServMultiFieldClfrRaddRtype、DiffServMultiFieldClfrSrcAddress、DiffServMultiFieldClfrDsrdStadRddr、diffServAlgDropStatus、diffServDataPathStorage、diffServClfrStorage、DiffServClfRlementStorage、diffServMultiFieldClfrStorage、diffServCountActStorage、，diffServAlgDropStorage，来自DIFFSERV-MIB的diffServAlgDropType；——RFC 3289
docsDev MODULE-IDENTITY LAST-UPDATED "200612200000Z" -- December 20, 2006 ORGANIZATION "IETF IP over Cable Data Network Working Group" CONTACT-INFO " Rich Woundy Postal: Comcast Cable 27 Industrial Avenue Chelmsford, MA 01824 U.S.A. Phone: +1 978 244 4010 E-mail: richard_woundy@cable.comcast.com
docsDev MODULE-IDENTITY上次更新的“200612200000Z”-2006年12月20日组织“IETF IP over Cable Data Network工作组”联系方式“Rich Woundy Postal:康卡斯特有线电视27号美国马萨诸塞州切姆斯福德工业大道01824电话：+1 978 244 4010电子邮件：richard_woundy@cable.comcast.com
Kevin Marez Postal: Motorola Corporation 6450 Sequence Drive San Diego, CA 92121 U.S.A. Phone: +1 858 404 3785 E-mail: kevin.marez@motorola.com
Kevin Marez邮政：摩托罗拉公司6450 Sequence Drive San Diego，CA 92121美国电话：+1 858 404 3785电子邮件：Kevin。marez@motorola.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-chairs: Richard Woundy,
richard_woundy@cable.comcast.com
Jean-Francois Mule,
jf.mule@cablelabs.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-chairs: Richard Woundy,
richard_woundy@cable.comcast.com
Jean-Francois Mule,
jf.mule@cablelabs.com"
DESCRIPTION "This is the MIB Module for DOCSIS-compliant cable modems
描述“这是用于DOCSIS兼容电缆调制解调器的MIB模块
and cable-modem termination systems.
和电缆调制解调器终端系统。
Copyright (C) The IETF Trust (2006). This version of this MIB module was published in RFC 4639; for full legal notices see the RFC itself."
版权所有（C）IETF信托基金（2006年）。该MIB模块的此版本发布在RFC 4639中；有关完整的法律通知，请参见RFC本身。”
REVISION "200612200000Z" -- December 20, 2006 DESCRIPTION "Second version, published as RFC 4639.
修订版“200612200000Z”-2006年12月20日描述“第二版，作为RFC 4639出版。
Modifications to this MIB module since RFC 2669 include: - Deprecation of the docsDevFilter group in favor of the DiffServ MIB groups, to enable support for IPv6 filtering and DiffServ Code Point (DSCP) marking. - Deprecation of the docsDevCpeGroup in favor of the docsDevCpeInetGroup, to enable support of IPv6. - Addition of various InetAddress objects to enable support of IPv6. - Deprecation of docsDevNmAccessTable in favor of SNMP Coexistence and SNMPv3 -- yet adding docsDevNmAccessTrapVersion and clarifying docsDevNmAccessIp for current use of this table, - Addition of docsDevIgmpModeControl for management and control of the IGMP mode of operation, - Addition of docsDevMaxCpe for management of the maxmium number of CPEs permitted access through a cable modem, - Addition of docsDevSwServerTransportProtocol, and modifications to docsDevSoftware object DESCRIPTIONS, to enable software downloads via either TFTP or HTTP, - Replacement of docsDevEvThrottleInhibited with docsDevEvThrottleThresholdExceeded to simplify event threshold management, - Modification of docsDevEvReporting to enable local logging to the internal volatile log, and not to the internal non-volatile log, - Modification of the compliance statement to make the docsDevCpe objects optional - Created placeholders for two OIDs in the docsDevFilterPolicyTable that were never used - Modified the DESCRIPTION of docsDevSwServerTransportProtocol and docsDevSwServerAddressType to address the dependence between each object - Added a reference to docsDevServerConfigTftpAddress - Clarified the scope of notifications that are covered by docsDevEvThrottleThreshold - Clarified an error condition that could occur when
自RFC 2669以来对该MIB模块的修改包括：-弃用docsDevFilter组以支持区分服务MIB组，以支持IPv6过滤和区分服务代码点（DSCP）标记。-不赞成docsDevCpeGroup而赞成docsDevCpeInetGroup，以支持IPv6。-添加各种InetAddress对象以支持IPv6。-不赞成使用DOCSDEVNMACCESS table以支持SNMP共存和SNMPv3——但增加了DOCSDEVNMACCESS TRAPVersion并澄清了当前使用该表的DOCSDEVNMACCESS IP——增加了用于管理和控制IGMP操作模式的DOCSDEVIGMMODEControl，-添加docsDevMaxCpe，用于管理通过电缆调制解调器允许访问的最大数量的CPE，-添加DocsDevServerTransportProtocol，并修改docsDevSoftware对象描述，以便通过TFTP或HTTP下载软件，-用DOCSDEVEVTHROTTLETHRESHOLDED替换DOCSDEVEVTHROTTLETHRESHOLDEXCEED以简化事件阈值管理，-修改DOCSDEVEVRREPORTING以允许本地记录到内部易失性日志，而不是内部非易失性日志，-修改合规性声明以使docsDevCpe对象可选-为docsDevFilterPolicyTable中从未使用过的两个OID创建占位符-修改docsdevswerserverTransportProtocol和docsdevswerserverAddressType的描述以解决每个对象之间的依赖性-添加对docsDevServerConfigTftpAddress-澄清了DocsDevThrottleThreshold所涵盖的通知范围-澄清了当
doing a SET to docsDevEvReporting - Defined each of the enumerated types for both docsDevEvLevel and docsDevEvPriority - Added UNITS clause to docsDevFilterLLCMatches, docsDevFilterIpMatches, docsDevMaxCpe, docsDevEvThrottleThreshold and docsDevEvCounts. - Added REFERENCE clause to docsDevFilterIpProtocol - Modified DESCRIPTION of docsDevCpeInetAddr to be more protocol-neutral - Removed the enumerated value (1) from both docsDevCpeInetSource and docsDevCpeSource - Covered additional read-write and read-create objects in the Security Considerations section - Modified the default value of docsDevNmAccessIpMask to be consistent with OSSI specification - Modified the SYNTAX of docsDevNmAccessCommunity and docsDevNmAccessInterfaces in the Conformance Statement section - Added SYNTAX clause to docsDevEvReporting in the Conformance Statement section - Modified SYNTAX clause of docsDevEvReporting to move new enumerated type to byte boundary - Added references to DOCSIS 2.0 specifications to multiple objects - Clarified non-persistency across reboots for all tables - Clarified functionality of docsDevSw objects as they relate to docsDevSwOperStatus - Clarified enumerated types (9) and (10) for docsDevServerBootState - Defined the state of unknown(0) for the following objects: docsDevServerDhcpAddressType, docsDevServerTimeAddressType, docsDevServerConfigTftpAddressType and docsDevServerConfigTftpAddressType - Modified the value in docsDevFilterIpDaddr to be consistent with the SYNTAX - Specified which rows could be modified in an active row for docsDevFilterPolicyStatus - Defined the term 'manually' in docsDevCpeEnroll - Clarified the description for docsDevFilterTosOrMask - Covered the case of a non-existent row for docsDevFilterPolicyPtr - Added DEFVAL clauses for multiple objects - Replaced docsDevNotification OBJECT IDENTIFIER with docsDevNotifications to address possible compatibility issues
设置docsDevEvReporting-为docsDevEvLevel和docsDevEvPriority定义了每个枚举类型-将UNITS子句添加到DocsDevFilterlCmatches、docsDevFilterIpMatches、docsDevMaxCpe、DocsDeveVthRottletThreshold和docsDevEvCounts中。-在DocsdevFilteriProtocol中添加了REFERENCE子句-将docsDevCpeInetAddr的描述修改为更加协议中立-删除了枚举值（1）从docsDevCpeInetSource和docsDevCpeSource-在安全注意事项部分介绍了其他读写和读创建对象-修改了docsDevNmAccessIpMask的默认值以与OSI规范一致-修改了一致性中docsDevNmAccessCommunity和Docsdevnmaccess接口的语法语句部分-在一致性语句部分向DocsDevReporting添加语法子句-修改DocsDevReporting的语法子句以将新枚举类型移动到字节边界-向多个对象添加对DOCSIS 2.0规范的引用-澄清所有表在重新启动时的非持久性-澄清docsDevSw对象与docsDevSwOperStatus相关-澄清了docsDevServerBootState的枚举类型（9）和（10）-为以下对象定义了未知（0）状态：DOCSDEVSERVERDHCPADDRESTYPE、docsDevServerTimeAddressType、，docsDevServerConfigTftpAddressType和docsDevServerConfigTftpAddressType-修改DocsDevFilterIPAddr中的值以与语法一致-指定可以在docsDevFilterPolicyStatus的活动行中修改哪些行-在DocsDevcPenroll中定义术语“手动”-澄清了DocsDevFilterToSormak的说明-介绍了docsDevFilterPolicyPtr不存在行的情况-为多个对象添加了DEFVAL子句-用docsDevNotification替换docsDevNotification对象标识符以解决可能的兼容性问题
- Added support for the usage of RFC 3413 and RFC 3014 as event notification mechanisms - Removed docsDevFilterPolicyObsoleteGroup - Added stdInterface(9) type to docsDevEvReporting to support the usage of RFC3413 and RFC3014 - Modified DESCRIPTION for docsDevMaxCpe"
- 添加了对使用RFC 3413和RFC 3014作为事件通知机制的支持-删除了docsDevFilterPolicyObsoleteGroup-将stdInterface（9）类型添加到DocsdevReporting以支持使用RFC3413和RFC3014-修改了docsDevMaxCpe的说明”
REVISION "199908190000Z" DESCRIPTION "Initial version, published as RFC 2669."
修订版“199908190000Z”说明“初始版本，作为RFC 2669出版。”
::= { mib-2 69 }
::= { mib-2 69 }
docsDevMIBObjects OBJECT IDENTIFIER ::= { docsDev 1 }
docsDevMIBObjects OBJECT IDENTIFIER ::= { docsDev 1 }
docsDevBase OBJECT IDENTIFIER ::= { docsDevMIBObjects 1 }
docsDevBase OBJECT IDENTIFIER ::= { docsDevMIBObjects 1 }
--
-- For the following object, there is no concept in the
-- RFI specification corresponding to a backup CMTS. The
-- enumeration is provided here in case someone is able
-- to define such a role or device.
--
--
-- For the following object, there is no concept in the
-- RFI specification corresponding to a backup CMTS. The
-- enumeration is provided here in case someone is able
-- to define such a role or device.
--
docsDevRole OBJECT-TYPE
SYNTAX INTEGER {
cm(1),
cmtsActive(2),
cmtsBackup(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the current role of this device. cm(1) is a
Cable Modem, cmtsActive(2) is a Cable Modem Termination
System that is controlling the system of cable modems,
and cmtsBackup(3) is a CMTS that is currently connected
but is not controlling the system (not currently used).
docsDevRole OBJECT-TYPE
SYNTAX INTEGER {
cm(1),
cmtsActive(2),
cmtsBackup(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Defines the current role of this device. cm(1) is a
Cable Modem, cmtsActive(2) is a Cable Modem Termination
System that is controlling the system of cable modems,
and cmtsBackup(3) is a CMTS that is currently connected
but is not controlling the system (not currently used).
In general, if this device is a 'cm', its role will not
change during operation or between reboots. If the
device is a 'cmts' it may change between cmtsActive and
cmtsBackup and back again during normal operation. NB:
At this time, the DOCSIS standards do not support the
concept of a backup CMTS, but cmtsBackup is included for
completeness."
::= { docsDevBase 1 }
In general, if this device is a 'cm', its role will not
change during operation or between reboots. If the
device is a 'cmts' it may change between cmtsActive and
cmtsBackup and back again during normal operation. NB:
At this time, the DOCSIS standards do not support the
concept of a backup CMTS, but cmtsBackup is included for
completeness."
::= { docsDevBase 1 }
docsDevDateTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-write STATUS current DESCRIPTION "The current date and time, with time zone information (if known).
docsDevDateTime对象类型语法DateAndTime MAX-ACCESS读写状态current DESCRIPTION“当前日期和时间，以及时区信息（如果已知）。
If the real data and time cannot be determined, this
shall represent elapsed time from boot relative to
the standard epoch '1970-1-1,0:0:0.0'. In other
words, if this agent has been up for 3 minutes and
not been able to determine what the actual date and
time are, this object will return the value
'1970-1-1,0:03:0.0'."
::= { docsDevBase 2 }
If the real data and time cannot be determined, this
shall represent elapsed time from boot relative to
the standard epoch '1970-1-1,0:0:0.0'. In other
words, if this agent has been up for 3 minutes and
not been able to determine what the actual date and
time are, this object will return the value
'1970-1-1,0:03:0.0'."
::= { docsDevBase 2 }
docsDevResetNow OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to true(1) causes the device to
reset. Reading this object always returns false(2)."
::= { docsDevBase 3 }
docsDevResetNow OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to true(1) causes the device to
reset. Reading this object always returns false(2)."
::= { docsDevBase 3 }
docsDevSerialNumber OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The manufacturer's serial number for this device."
::= { docsDevBase 4 }
docsDevSerialNumber OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The manufacturer's serial number for this device."
::= { docsDevBase 4 }
docsDevSTPControl OBJECT-TYPE
SYNTAX INTEGER {
stEnabled(1),
noStFilterBpdu(2),
noStPassBpdu(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls operation of the spanning tree
protocol (as distinguished from transparent bridging).
docsDevSTPControl OBJECT-TYPE
SYNTAX INTEGER {
stEnabled(1),
noStFilterBpdu(2),
noStPassBpdu(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls operation of the spanning tree
protocol (as distinguished from transparent bridging).
If set to stEnabled(1), then the spanning tree protocol is enabled, subject to bridging constraints.
如果设置为stEnabled（1），则根据桥接约束启用生成树协议。
If noStFilterBpdu(2), then spanning tree is not active, and Bridge PDUs received are discarded.
如果为noStFilterBpdu（2），则生成树不处于活动状态，接收到的网桥PDU将被丢弃。
If noStPassBpdu(3), then spanning tree is not active, and Bridge PDUs are transparently forwarded.
如果是noStPassBpdu（3），则生成树不活动，网桥PDU透明转发。
Note that a device need not implement all of these
options, but that noStFilterBpdu(2) is required."
DEFVAL { noStFilterBpdu }
::= { docsDevBase 5 }
Note that a device need not implement all of these
options, but that noStFilterBpdu(2) is required."
DEFVAL { noStFilterBpdu }
::= { docsDevBase 5 }
docsDevIgmpModeControl OBJECT-TYPE
SYNTAX INTEGER {
passive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls the IGMP mode of operation for
the CM or CMTS. In passive mode, the device forwards
IGMP between interfaces as based on knowledge of
Multicast Session activity on the subscriber side
interface and the rules defined in the DOCSIS RFI
specification. In active mode, the device terminates
at and initiates IGMP through its interfaces as based
on the knowledge of Multicast Session activity on the
subscriber side interface."
REFERENCE
"DOCSIS RFI 1.1 Specification, Section 3.3.1. and
DOCSIS RFI 2.0 Specification, Section 5.3.1."
DEFVAL { passive }
::= { docsDevBase 6 }
docsDevIgmpModeControl OBJECT-TYPE
SYNTAX INTEGER {
passive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls the IGMP mode of operation for
the CM or CMTS. In passive mode, the device forwards
IGMP between interfaces as based on knowledge of
Multicast Session activity on the subscriber side
interface and the rules defined in the DOCSIS RFI
specification. In active mode, the device terminates
at and initiates IGMP through its interfaces as based
on the knowledge of Multicast Session activity on the
subscriber side interface."
REFERENCE
"DOCSIS RFI 1.1 Specification, Section 3.3.1. and
DOCSIS RFI 2.0 Specification, Section 5.3.1."
DEFVAL { passive }
::= { docsDevBase 6 }
docsDevMaxCpe OBJECT-TYPE SYNTAX Unsigned32 (0..255) UNITS "CPEs" MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of CPEs that can be granted access through a CM during a CM epoch. This value can be obtained from the CM configuration file; however, it may be adjusted by the CM according to hardware or software limitations that have been imposed on the implementation." REFERENCE "DOCSIS RFI 1.0 Specification, Appendix C.7.20., and
docsDevMaxCpe对象类型语法无符号32（0..255）单元“CPEs”最大访问只读状态当前说明“在CM期间，可通过CM授予访问权限的最大CPE数。该值可从CM配置文件中获得；但是，构型管理可根据对实施施加的硬件或软件限制对其进行调整。“参考”DOCSIS RFI 1.0规范，附录C.7.20，和
DOCSIS RFI 1.1 Specification, Appendix C.1.1.7. and
DOCSIS RFI 2.0 Specification, Appendix C.1.1.7."
::= { docsDevBase 7 }
DOCSIS RFI 1.1 Specification, Appendix C.1.1.7. and
DOCSIS RFI 2.0 Specification, Appendix C.1.1.7."
::= { docsDevBase 7 }
--
-- The following table provides one level of security for access
-- to the device by network management stations.
-- Note that access is also constrained by the
-- community strings and any vendor-specific security.
--
--
-- The following table provides one level of security for access
-- to the device by network management stations.
-- Note that access is also constrained by the
-- community strings and any vendor-specific security.
--
docsDevNmAccessTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevNmAccessEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This table controls access to SNMP objects by network management stations. If the table is empty, access to SNMP objects is unrestricted. The objects in this table MUST NOT persist across reboots. The objects in this table are only accessible from cable devices that are not capable of operating in SNMP Coexistence mode (RFC 3584) or in SNMPv3 mode (RFC 3410). See the conformance section for details. Note that some devices are required by other specifications (e.g., the DOCSIS OSSIv1.1 specification) to support the legacy SNMPv1/v2c docsDevNmAccess mode for backward compatibility.
docsDevNmAccessTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevNmAccessEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This table controls access to SNMP objects by network management stations. If the table is empty, access to SNMP objects is unrestricted. The objects in this table MUST NOT persist across reboots. The objects in this table are only accessible from cable devices that are not capable of operating in SNMP Coexistence mode (RFC 3584) or in SNMPv3 mode (RFC 3410). See the conformance section for details. Note that some devices are required by other specifications (e.g., the DOCSIS OSSIv1.1 specification) to support the legacy SNMPv1/v2c docsDevNmAccess mode for backward compatibility.translate error, please retry
This table is deprecated. Instead, use the SNMP
coexistence MIBs from RFC 3584, the TARGET and
NOTIFICATION MIBs from RFC 3413, and
the View-Based Access Control Model (VACM) MIBs for
all SNMP protocol versions from RFC 3415."
::= { docsDevMIBObjects 2 }
This table is deprecated. Instead, use the SNMP
coexistence MIBs from RFC 3584, the TARGET and
NOTIFICATION MIBs from RFC 3413, and
the View-Based Access Control Model (VACM) MIBs for
all SNMP protocol versions from RFC 3415."
::= { docsDevMIBObjects 2 }
docsDevNmAccessEntry OBJECT-TYPE SYNTAX DocsDevNmAccessEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "An entry describing access to SNMP objects by a particular network management station. An entry in this table is not readable unless the management station has read-write permission (either implicit if the table is empty, or explicit through an entry in this table). Entries are ordered by docsDevNmAccessIndex. The first
docsDevNmAccessEntry对象类型语法docsDevNmAccessEntry MAX-ACCESS不可访问状态不推荐的描述“描述特定网络管理站访问SNMP对象的条目。除非管理站具有读写权限，否则此表中的条目不可读（如果表为空，则为隐式，或者通过此表中的条目显式）。条目按docsDevNmAccessIndex排序。第一个
matching entry (e.g., matching IP address and community
string) is used to derive access."
INDEX { docsDevNmAccessIndex }
::= { docsDevNmAccessTable 1 }
matching entry (e.g., matching IP address and community
string) is used to derive access."
INDEX { docsDevNmAccessIndex }
::= { docsDevNmAccessTable 1 }
DocsDevNmAccessEntry ::= SEQUENCE {
docsDevNmAccessIndex Integer32,
docsDevNmAccessIp IpAddress,
docsDevNmAccessIpMask IpAddress,
docsDevNmAccessCommunity OCTET STRING,
docsDevNmAccessControl INTEGER,
docsDevNmAccessInterfaces OCTET STRING,
docsDevNmAccessStatus RowStatus,
docsDevNmAccessTrapVersion INTEGER
}
DocsDevNmAccessEntry ::= SEQUENCE {
docsDevNmAccessIndex Integer32,
docsDevNmAccessIp IpAddress,
docsDevNmAccessIpMask IpAddress,
docsDevNmAccessCommunity OCTET STRING,
docsDevNmAccessControl INTEGER,
docsDevNmAccessInterfaces OCTET STRING,
docsDevNmAccessStatus RowStatus,
docsDevNmAccessTrapVersion INTEGER
}
docsDevNmAccessIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"Index used to order the application of access
entries."
::= { docsDevNmAccessEntry 1 }
docsDevNmAccessIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"Index used to order the application of access
entries."
::= { docsDevNmAccessEntry 1 }
docsDevNmAccessIp OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The IP address (or subnet) of the network management
station. The address 0.0.0.0 is defined to mean
any Network Management Station (NMS). If traps are
enabled for this entry, then the value must be the
address of a specific device. Implementations MAY
recognize 255.255.255.255 as equivalent to 0.0.0.0."
DEFVAL { '00000000'h }
::= { docsDevNmAccessEntry 2 }
docsDevNmAccessIp OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The IP address (or subnet) of the network management
station. The address 0.0.0.0 is defined to mean
any Network Management Station (NMS). If traps are
enabled for this entry, then the value must be the
address of a specific device. Implementations MAY
recognize 255.255.255.255 as equivalent to 0.0.0.0."
DEFVAL { '00000000'h }
::= { docsDevNmAccessEntry 2 }
docsDevNmAccessIpMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The IP subnet mask of the network management stations. If traps are enabled for this entry, then the value must be 0.0.0.0. Implementations MAY recognize 255.255.255.255 as equivalent to 0.0.0.0."
docsDevNmAccessIpMask对象类型语法IpAddress MAX-ACCESS read create STATUS Disprecated DESCRIPTION“网络管理站的IP子网掩码。如果为此项启用陷阱，则该值必须为0.0.0.0。实现可能会将255.255.255.255识别为等同于0.0.0.0。”
DEFVAL { '00000000'h }
::= { docsDevNmAccessEntry 3 }
DEFVAL { '00000000'h }
::= { docsDevNmAccessEntry 3 }
docsDevNmAccessCommunity OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The community string to be matched for access by this
entry. If set to a zero-length string, then any
community string will match. When read, this object
SHOULD return a zero-length string."
DEFVAL { "public" }
::= { docsDevNmAccessEntry 4 }
docsDevNmAccessCommunity OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The community string to be matched for access by this
entry. If set to a zero-length string, then any
community string will match. When read, this object
SHOULD return a zero-length string."
DEFVAL { "public" }
::= { docsDevNmAccessEntry 4 }
docsDevNmAccessControl OBJECT-TYPE
SYNTAX INTEGER {
none(1),
read(2),
readWrite(3),
roWithTraps(4),
rwWithTraps(5),
trapsOnly(6)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Specifies the type of access allowed to this NMS.
Setting this object to none(1) causes the table entry
to be destroyed. Read(2) allows access by 'get' and
'get-next' PDUs. ReadWrite(3) allows access by 'set' as
well. RoWithtraps(4), rwWithTraps(5), and trapsOnly(6)
control distribution of Trap PDUs transmitted by this
device."
DEFVAL { read }
::= { docsDevNmAccessEntry 5 }
docsDevNmAccessControl OBJECT-TYPE
SYNTAX INTEGER {
none(1),
read(2),
readWrite(3),
roWithTraps(4),
rwWithTraps(5),
trapsOnly(6)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Specifies the type of access allowed to this NMS.
Setting this object to none(1) causes the table entry
to be destroyed. Read(2) allows access by 'get' and
'get-next' PDUs. ReadWrite(3) allows access by 'set' as
well. RoWithtraps(4), rwWithTraps(5), and trapsOnly(6)
control distribution of Trap PDUs transmitted by this
device."
DEFVAL { read }
::= { docsDevNmAccessEntry 5 }
-- The syntax of the following object was copied from RFC 1493,
-- dot1dStaticAllowedToGoTo.
-- The syntax of the following object was copied from RFC 1493,
-- dot1dStaticAllowedToGoTo.
docsDevNmAccessInterfaces OBJECT-TYPE SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Specifies the set of interfaces from which requests from this NMS will be accepted. Each octet within the value of this object specifies a set of eight
docsDevNmAccessInterfaces对象类型语法八位字节字符串（大小（1..32））MAX-ACCESS read create STATUS deprecated DESCRIPTION“指定接收来自此NMS的请求的接口集。此对象值中的每个八位字节指定一组八位字节
interfaces, the first octet specifying ports 1 through 8, the second octet specifying interfaces 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered interface, and the least significant bit represents the highest numbered interface. Thus, each interface is represented by a single bit within the value of this object. If that bit has a value of '1' then that interface is included in the set.
接口，第一个八位字节指定端口1到8，第二个八位字节指定接口9到16，等等。在每个八位字节中，最高有效位表示编号最低的接口，最低有效位表示编号最高的接口。因此，每个接口由该对象值内的一个位表示。如果该位的值为“1”，则该接口包含在集合中。
Note that entries in this table apply only to link-layer interfaces (e.g., Ethernet and CATV MAC). Bits representing upstream and downstream channel interfaces MUST NOT be set to '1'.
请注意，此表中的条目仅适用于链路层接口（例如，以太网和CATV MAC）。代表上游和下游信道接口的位不得设置为“1”。
Note that if bits corresponding to non-existing interfaces are set, the result is implementation specific.
注意，如果设置了与不存在的接口相对应的位，则结果是特定于实现的。
Note that according to the DOCSIS OSSIv1.1 specification, when ifIndex '1' is included in the set, then this row applies to all CPE (customer-facing) interfaces.
请注意，根据DOCSIS OSSIv1.1规范，当ifIndex“1”包含在集合中时，该行适用于所有CPE（面向客户）接口。
The size of this object is the minimum required to
represent all configured interfaces for this device."
::= { docsDevNmAccessEntry 6 }
The size of this object is the minimum required to
represent all configured interfaces for this device."
::= { docsDevNmAccessEntry 6 }
docsDevNmAccessStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS deprecated DESCRIPTION "Controls and reflects the status of rows in this table. Rows in this table may be created by either the create-and-go or create-and-wait paradigm. There is no restriction on changing values in a row of this table while the row is active.
docsDevNmAccessStatus对象类型语法RowStatus MAX-ACCESS read create STATUS deprecated DESCRIPTION“控制并反映此表中行的状态。此表中的行可以通过“创建并执行”或“创建并等待”范例创建。当行处于活动状态时，对更改此表中行的值没有任何限制。
The following objects MUST have valid values before this
object can be set to active: docsDevNmAccessIp,
docsDevNmAccessStatus, docsDevNmAccessIpMask,
docsDevNmAccessCommunity, docsDevNmAccessControl, and
docsDevNmAccessInterfaces."
::= { docsDevNmAccessEntry 7 }
The following objects MUST have valid values before this
object can be set to active: docsDevNmAccessIp,
docsDevNmAccessStatus, docsDevNmAccessIpMask,
docsDevNmAccessCommunity, docsDevNmAccessControl, and
docsDevNmAccessInterfaces."
::= { docsDevNmAccessEntry 7 }
docsDevNmAccessTrapVersion OBJECT-TYPE SYNTAX INTEGER {
docsDevNmAccessTrapVersion对象类型语法整数{
disableSNMPv2trap(1),
enableSNMPv2trap(2)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Specifies the TRAP version that is sent to this NMS.
Setting this object to disableSNMPv2trap (1) causes the
trap in SNMPv1 format to be sent to a particular NMS.
Setting this object to enableSNMPv2trap (2) causes the
trap in SNMPv2 format be sent to a particular NMS."
DEFVAL { disableSNMPv2trap }
::= { docsDevNmAccessEntry 8 }
disableSNMPv2trap(1),
enableSNMPv2trap(2)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Specifies the TRAP version that is sent to this NMS.
Setting this object to disableSNMPv2trap (1) causes the
trap in SNMPv1 format to be sent to a particular NMS.
Setting this object to enableSNMPv2trap (2) causes the
trap in SNMPv2 format be sent to a particular NMS."
DEFVAL { disableSNMPv2trap }
::= { docsDevNmAccessEntry 8 }
--
-- The following group describes control objects used for downloading
-- firmware to a cable device. Procedures for software download are
-- described in Section 3.2.1 of the RFC containing this MIB module.
--
--
-- The following group describes control objects used for downloading
-- firmware to a cable device. Procedures for software download are
-- described in Section 3.2.1 of the RFC containing this MIB module.
--
docsDevSoftware OBJECT IDENTIFIER ::= { docsDevMIBObjects 3 }
docsDevSoftware OBJECT IDENTIFIER ::= { docsDevMIBObjects 3 }
docsDevSwServer OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The address of the TFTP server used for software upgrades. If the TFTP server is unknown or is a non-IPv4 address, return 0.0.0.0.
docsDevSwServer对象类型语法IpAddress MAX-ACCESS读写状态已弃用说明“用于软件升级的TFTP服务器的地址。如果TFTP服务器未知或是非IPv4地址，请返回0.0.0。
This object is deprecated. See docsDevSwServerAddress
for its replacement. This object will have its value
modified, given a valid SET to docsDevSwServerAddress."
::= { docsDevSoftware 1 }
This object is deprecated. See docsDevSwServerAddress
for its replacement. This object will have its value
modified, given a valid SET to docsDevSwServerAddress."
::= { docsDevSoftware 1 }
docsDevSwFilename OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..64)) MAX-ACCESS read-write STATUS current DESCRIPTION "The filename of the software image to be downloaded via TFTP, or the abs_path (as defined in RFC 2616) of the software image to be downloaded via HTTP.
docsDevSwFilename对象类型语法SnmpAdminString（大小（0..64））MAX-ACCESS读写状态当前描述“通过TFTP下载的软件映像的文件名，或通过HTTP下载的软件映像的abs_路径（如RFC 2616中定义的）。
Unless set via SNMP, this is the filename or abs_path specified by the provisioning server during the boot process that corresponds to the software version that
除非通过SNMP设置，否则这是在引导过程中由配置服务器指定的文件名或abs_路径，对应于所使用的软件版本
is desired for this device.
此设备需要的是。
If unknown, the value of this object is the zero-length
string."
::= { docsDevSoftware 2 }
If unknown, the value of this object is the zero-length
string."
::= { docsDevSoftware 2 }
docsDevSwAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
upgradeFromMgt(1),
allowProvisioningUpgrade(2),
ignoreProvisioningUpgrade(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If set to upgradeFromMgt(1), the device will initiate a
TFTP or HTTP software image download. After
successfully receiving an image, the device will set
its state to ignoreProvisioningUpgrade(3) and reboot.
If the download process is interrupted (e.g., by a reset
or power failure), the device will load the previous
image and, after re-initialization, continue to attempt
loading the image specified in docsDevSwFilename.
docsDevSwAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
upgradeFromMgt(1),
allowProvisioningUpgrade(2),
ignoreProvisioningUpgrade(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If set to upgradeFromMgt(1), the device will initiate a
TFTP or HTTP software image download. After
successfully receiving an image, the device will set
its state to ignoreProvisioningUpgrade(3) and reboot.
If the download process is interrupted (e.g., by a reset
or power failure), the device will load the previous
image and, after re-initialization, continue to attempt
loading the image specified in docsDevSwFilename.
If set to allowProvisioningUpgrade(2), the device will use the software version information supplied by the provisioning server when next rebooting (this does not cause a reboot).
如果设置为allowProvisioningUpgrade（2），设备将在下次重新启动时使用配置服务器提供的软件版本信息（这不会导致重新启动）。
When set to ignoreProvisioningUpgrade(3), the device will disregard software image upgrade information from the provisioning server.
当设置为ignoreProvisioningUpgrade（3）时，设备将忽略来自设置服务器的软件映像升级信息。
Note that reading this object can return
upgradeFromMgt(1). This indicates that a software
download is currently in progress, and that the device
will reboot after successfully receiving an image."
DEFVAL { allowProvisioningUpgrade }
::= { docsDevSoftware 3 }
Note that reading this object can return
upgradeFromMgt(1). This indicates that a software
download is currently in progress, and that the device
will reboot after successfully receiving an image."
DEFVAL { allowProvisioningUpgrade }
::= { docsDevSoftware 3 }
docsDevSwOperStatus OBJECT-TYPE
SYNTAX INTEGER {
inProgress(1),
completeFromProvisioning(2),
completeFromMgt(3),
failed(4),
other(5)
}
docsDevSwOperStatus OBJECT-TYPE
SYNTAX INTEGER {
inProgress(1),
completeFromProvisioning(2),
completeFromMgt(3),
failed(4),
other(5)
}
MAX-ACCESS read-only STATUS current DESCRIPTION "InProgress(1) indicates that a TFTP or HTTP download is underway, either as a result of a version mismatch at provisioning or as a result of a upgradeFromMgt request. No other docsDevSw* objects can be modified in this state.
进程（1）中的MAX-ACCESS只读状态当前描述“表示TFTP或HTTP下载正在进行，这可能是由于设置时版本不匹配或升级FromMgt请求造成的。在此状态下不能修改任何其他docsDevSw*对象。
CompleteFromProvisioning(2) indicates that the last software upgrade was a result of version mismatch at provisioning.
CompleteFromProvisioning（2）表示上一次软件升级是由于配置时版本不匹配造成的。
CompleteFromMgt(3) indicates that the last software upgrade was a result of setting docsDevSwAdminStatus to upgradeFromMgt.
CompleteFromMgt（3）表示上一次软件升级是将docsDevSwAdminStatus设置为从MGT升级的结果。
Failed(4) indicates that the last attempted download
failed, ordinarily due to TFTP or HTTP timeout."
REFERENCE
"DOCSIS RFI 1.0 Specification, Section 8.2., and
DOCSIS RFI 1.1 Specification, Section 10.1. and
DOCSIS RFI 2.0 Specification, Section 12.1."
::= { docsDevSoftware 4 }
Failed(4) indicates that the last attempted download
failed, ordinarily due to TFTP or HTTP timeout."
REFERENCE
"DOCSIS RFI 1.0 Specification, Section 8.2., and
DOCSIS RFI 1.1 Specification, Section 10.1. and
DOCSIS RFI 2.0 Specification, Section 12.1."
::= { docsDevSoftware 4 }
docsDevSwCurrentVers OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The software version currently operating in this device.
This string's syntax is that used by the
individual vendor to identify software versions.
For a CM, this string will describe the current
software load. For a CMTS, this object SHOULD contain
a human-readable representation either of the vendor
specific designation of the software for the chassis,
or of the software for the control processor. If
neither of these is applicable, the value MUST be a
zero-length string."
::= { docsDevSoftware 5 }
docsDevSwCurrentVers OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The software version currently operating in this device.
This string's syntax is that used by the
individual vendor to identify software versions.
For a CM, this string will describe the current
software load. For a CMTS, this object SHOULD contain
a human-readable representation either of the vendor
specific designation of the software for the chassis,
or of the software for the control processor. If
neither of these is applicable, the value MUST be a
zero-length string."
::= { docsDevSoftware 5 }
docsDevSwServerAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-write STATUS current DESCRIPTION "The type of address of the TFTP or HTTP server used for
docsDevSwServerAddressType对象类型语法InetAddressType MAX-ACCESS读写状态当前描述“用于
software upgrades.
软件升级。
If docsDevSwServerTransportProtocol is currently set to
tftp(1), attempting to set this object to dns(16) MUST
result in an error."
::= { docsDevSoftware 6 }
If docsDevSwServerTransportProtocol is currently set to
tftp(1), attempting to set this object to dns(16) MUST
result in an error."
::= { docsDevSoftware 6 }
docsDevSwServerAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION "The address of the TFTP or HTTP server used for software upgrades.
docsDevSwServerAddress对象类型语法InetAddress MAX-ACCESS读写状态当前描述“用于软件升级的TFTP或HTTP服务器的地址。
If the TFTP/HTTP server is unknown, return the zero-length address string (see the TextualConvention).
如果TFTP/HTTP服务器未知，则返回长度为零的地址字符串（请参阅textualconversion）。
If docsDevSwServer is also implemented in this agent,
this object is tied to it. A set of this object to an
IPv4 address will result in also setting the value of
docsDevSwServer to that address. If this object is set
to an IPv6 address, docsDevSwServer is set to 0.0.0.0.
If docsDevSwServer is set, this object is also set to
that value. Note that if both are set in the same
action, the order of which one sets the other is
undefined."
::= { docsDevSoftware 7 }
If docsDevSwServer is also implemented in this agent,
this object is tied to it. A set of this object to an
IPv4 address will result in also setting the value of
docsDevSwServer to that address. If this object is set
to an IPv6 address, docsDevSwServer is set to 0.0.0.0.
If docsDevSwServer is set, this object is also set to
that value. Note that if both are set in the same
action, the order of which one sets the other is
undefined."
::= { docsDevSoftware 7 }
docsDevSwServerTransportProtocol OBJECT-TYPE
SYNTAX INTEGER {
tftp(1),
http(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the transport protocol (TFTP or
HTTP) to be used for software upgrades.
docsDevSwServerTransportProtocol OBJECT-TYPE
SYNTAX INTEGER {
tftp(1),
http(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object specifies the transport protocol (TFTP or
HTTP) to be used for software upgrades.
If the value of this object is tftp(1), then the cable device uses TFTP (RFC 1350) read request packets to download the docsDevSwFilename from the docsDevSwServerAddress in octet mode.
如果此对象的值为tftp（1），则电缆设备使用tftp（RFC 1350）读取请求数据包以八位字节模式从docsDevSwServerAddress下载docsDevSwFilename。
If the value of this object is http(2), then the cable device uses HTTP 1.0 (RFC 1945) or HTTP 1.1 (RFC 2616) GET requests sent to host docsDevSwServerAddress to
如果此对象的值为http（2），则有线设备将使用http 1.0（RFC 1945）或http 1.1（RFC 2616）获取发送到主机docsdevsServerAddress的请求
download the software image from path docsDevSwFilename.
从路径docsDevSwFilename下载软件映像。
If docsDevSwServerAddressType is currently set to
dns(16), attempting to set this object to tftp(1) MUST
result in an error."
DEFVAL { tftp }
::= { docsDevSoftware 8 }
If docsDevSwServerAddressType is currently set to
dns(16), attempting to set this object to tftp(1) MUST
result in an error."
DEFVAL { tftp }
::= { docsDevSoftware 8 }
--
-- The following group describes server access and parameters used
-- for initial provisioning and bootstrapping.
--
--
-- The following group describes server access and parameters used
-- for initial provisioning and bootstrapping.
--
docsDevServer OBJECT IDENTIFIER ::= { docsDevMIBObjects 4 }
docsDevServer OBJECT IDENTIFIER ::= { docsDevMIBObjects 4 }
docsDevServerBootState OBJECT-TYPE
SYNTAX INTEGER {
operational(1),
disabled(2),
waitingForDhcpOffer(3),
waitingForDhcpResponse(4),
waitingForTimeServer(5),
waitingForTftp(6),
refusedByCmts(7),
forwardingDenied(8),
other(9),
unknown(10)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If operational(1), the device has completed loading and
processing of configuration parameters, and the CMTS has
completed the Registration exchange.
docsDevServerBootState OBJECT-TYPE
SYNTAX INTEGER {
operational(1),
disabled(2),
waitingForDhcpOffer(3),
waitingForDhcpResponse(4),
waitingForTimeServer(5),
waitingForTftp(6),
refusedByCmts(7),
forwardingDenied(8),
other(9),
unknown(10)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If operational(1), the device has completed loading and
processing of configuration parameters, and the CMTS has
completed the Registration exchange.
If disabled(2), then the device was administratively disabled, possibly by being refused network access in the configuration file.
如果禁用（2），则设备被管理禁用，可能是由于配置文件中的网络访问被拒绝。
If waitingForDhcpOffer(3), then a Dynamic Host Configuration Protocol (DHCP) Discover has been transmitted, and no offer has yet been received.
如果waitingForDhcpOffer（3），则已传输动态主机配置协议（DHCP）发现，并且尚未收到任何报价。
If waitingForDhcpResponse(4), then a DHCP Request has been transmitted, and no response has yet been received.
如果waitingForDhcpResponse（4），则已发送DHCP请求，并且尚未收到响应。
If waitingForTimeServer(5), then a Time Request has been transmitted, and no response has yet been received.
如果waitingForTimeServer（5），则发送了时间请求，但尚未收到响应。
If waitingForTftp(6), then a request to the TFTP parameter server has been made, and no response received.
如果waitingForTftp（6），则已向TFTP参数服务器发出请求，但未收到响应。
If refusedByCmts(7), then the Registration Request/Response exchange with the CMTS failed.
如果CMTS拒绝（7），则与CMTS的注册请求/响应交换失败。
If forwardingDenied(8), then the registration process was completed, but the network access option in the received configuration file prohibits forwarding.
如果forwardingDenied（8），则注册过程已完成，但收到的配置文件中的网络访问选项禁止转发。
If other(9), then the registration process reached a point that does not fall into one of the above categories.
如果是其他（9），则注册过程不属于上述类别之一。
If unknown(10), then the device has not yet begun the
registration process or is in some other indeterminate
state."
REFERENCE
"DOCSIS RFI 1.0 Specification, Figure 7-1, and
DOCSIS RFI 1.1 Specification, Figure 9-1 and
DOCSIS RFI 2.0 Specification, Figure 11-1."
::= { docsDevServer 1 }
If unknown(10), then the device has not yet begun the
registration process or is in some other indeterminate
state."
REFERENCE
"DOCSIS RFI 1.0 Specification, Figure 7-1, and
DOCSIS RFI 1.1 Specification, Figure 9-1 and
DOCSIS RFI 2.0 Specification, Figure 11-1."
::= { docsDevServer 1 }
docsDevServerDhcp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the DHCP server that assigned an IP address to this device. Returns 0.0.0.0 if DHCP is not used for IP address assignment, or if this agent is not assigned an IPv4 address.
docsDevServerDhcp对象类型语法IpAddress MAX-ACCESS只读状态不推荐使用说明“为该设备分配IP地址的DHCP服务器的IP地址。如果DHCP未用于IP地址分配，或者此代理未分配IPv4地址，则返回0.0.0。
This object is deprecated and is replaced by
docsDevServerDhcpAddress."
::= { docsDevServer 2 }
This object is deprecated and is replaced by
docsDevServerDhcpAddress."
::= { docsDevServer 2 }
docsDevServerTime OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the Time server (RFC 0868). Returns 0.0.0.0 if the time server IP address is unknown, or if the time server is not an IPv4 server.
docsDevServerTime对象类型语法IpAddress MAX-ACCESS只读状态不推荐使用说明“时间服务器（RFC 0868）的IP地址。如果时间服务器IP地址未知，或者时间服务器不是IPv4服务器，则返回0.0.0。
This object is deprecated and is replaced by
此对象已弃用，替换为
docsDevServerTimeAddress."
::= { docsDevServer 3 }
docsDevServerTimeAddress."
::= { docsDevServer 3 }
docsDevServerTftp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The IP address of the TFTP server responsible for downloading provisioning and configuration parameters to this device. Returns 0.0.0.0 if the TFTP server address is unknown or is not an IPv4 address.
docsDevServerTftp对象类型语法IpAddress MAX-ACCESS只读状态不推荐使用说明“负责将配置和配置参数下载到此设备的TFTP服务器的IP地址。如果TFTP服务器地址未知或不是IPv4地址，则返回0.0.0。
This object is deprecated and is replaced by
docsDevServerConfigTftpAddress."
::= { docsDevServer 4 }
This object is deprecated and is replaced by
docsDevServerConfigTftpAddress."
::= { docsDevServer 4 }
docsDevServerConfigFile OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the device configuration file read from
the TFTP server. Returns a zero-length string if
the configuration file name is unknown."
::= { docsDevServer 5 }
docsDevServerConfigFile OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The name of the device configuration file read from
the TFTP server. Returns a zero-length string if
the configuration file name is unknown."
::= { docsDevServer 5 }
docsDevServerDhcpAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address of docsDevServerDhcpAddress. If
DHCP was not used, this value should return
unknown(0)."
::= { docsDevServer 6 }
docsDevServerDhcpAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address of docsDevServerDhcpAddress. If
DHCP was not used, this value should return
unknown(0)."
::= { docsDevServer 6 }
docsDevServerDhcpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The internet address of the DHCP server that assigned
an IP address to this device. Returns the zero length
octet string if DHCP was not used for IP address
assignment."
::= { docsDevServer 7 }
docsDevServerDhcpAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The internet address of the DHCP server that assigned
an IP address to this device. Returns the zero length
octet string if DHCP was not used for IP address
assignment."
::= { docsDevServer 7 }
docsDevServerTimeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address of docsDevServerTimeAddress. If
no time server exists, this value should return
unknown(0)."
::= { docsDevServer 8 }
docsDevServerTimeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address of docsDevServerTimeAddress. If
no time server exists, this value should return
unknown(0)."
::= { docsDevServer 8 }
docsDevServerTimeAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The Internet address of the RFC 868 Time server, as provided by DHCP option 4.
docsDevServerTimeAddress对象类型语法InetAddress MAX-ACCESS只读状态当前描述“由DHCP选项4提供的RFC 868时间服务器的Internet地址。
Note that if multiple values are provided to the CM in DHCP option 4, the value of this MIB object MUST be the Time server address from which the Time of Day reference was acquired as based on the DOCSIS RFI specification. During the period of time where the Time of Day have not been acquired, the Time server address reported by the CM may report the first address value in the DHCP option value or the last server address the CM attempted to get the Time of day value.
请注意，如果在DHCP选项4中向CM提供多个值，则此MIB对象的值必须是根据DOCSIS RFI规范获取时间参考的时间服务器地址。在尚未获取当日时间的时间段内，CM报告的时间服务器地址可能会报告DHCP选项值中的第一个地址值或CM试图获取当日时间值的最后一个服务器地址。
Returns the zero-length octet string if the time server
IP address is not provisioned."
REFERENCE
"DOCSIS RFI 1.1 Specification, Section 9.2.7. and
DOCSIS RFI 2.0 Specification, Section 11.2.7."
::= { docsDevServer 9 }
Returns the zero-length octet string if the time server
IP address is not provisioned."
REFERENCE
"DOCSIS RFI 1.1 Specification, Section 9.2.7. and
DOCSIS RFI 2.0 Specification, Section 11.2.7."
::= { docsDevServer 9 }
docsDevServerConfigTftpAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address of docsDevServerConfigTftpAddress.
If no TFTP server exists, this value should return
unknown(0)."
::= { docsDevServer 10 }
docsDevServerConfigTftpAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of address of docsDevServerConfigTftpAddress.
If no TFTP server exists, this value should return
unknown(0)."
::= { docsDevServer 10 }
docsDevServerConfigTftpAddress OBJECT-TYPE SYNTAX InetAddress
docsDevServerConfigTftpAddress对象类型语法
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The internet address of the TFTP server responsible for
downloading provisioning and configuration parameters
to this device. Returns the zero-length octet string if
the config server address is unknown. There are certain
security risks that are involved with using TFTP."
REFERENCE
"RFC 3617, Section 5"
::= { docsDevServer 11 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The internet address of the TFTP server responsible for
downloading provisioning and configuration parameters
to this device. Returns the zero-length octet string if
the config server address is unknown. There are certain
security risks that are involved with using TFTP."
REFERENCE
"RFC 3617, Section 5"
::= { docsDevServer 11 }
-- -- Event Reporting --
----事件报告--
docsDevEvent OBJECT IDENTIFIER ::= { docsDevMIBObjects 5 }
docsDevEvent OBJECT IDENTIFIER ::= { docsDevMIBObjects 5 }
docsDevEvControl OBJECT-TYPE
SYNTAX INTEGER {
resetLog(1),
useDefaultReporting(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to resetLog(1) empties the event
log. All data is deleted. Setting it to
useDefaultReporting(2) returns all event priorities to
their factory-default reporting. Reading this object
always returns useDefaultReporting(2)."
::= { docsDevEvent 1 }
docsDevEvControl OBJECT-TYPE
SYNTAX INTEGER {
resetLog(1),
useDefaultReporting(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to resetLog(1) empties the event
log. All data is deleted. Setting it to
useDefaultReporting(2) returns all event priorities to
their factory-default reporting. Reading this object
always returns useDefaultReporting(2)."
::= { docsDevEvent 1 }
docsDevEvSyslog OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The IP address of the Syslog server. If 0.0.0.0, either syslog transmission is inhibited, or the Syslog server address is not an IPv4 address.
docsDevEvSyslog对象类型语法IpAddress MAX-ACCESS读写状态已弃用描述“Syslog服务器的IP地址。如果为0.0.0.0，则Syslog传输被禁止，或者Syslog服务器地址不是IPv4地址。
This object is deprecated and is replaced by
docsDevEvSyslogAddress."
::= { docsDevEvent 2 }
This object is deprecated and is replaced by
docsDevEvSyslogAddress."
::= { docsDevEvent 2 }
docsDevEvThrottleAdminStatus OBJECT-TYPE
docsDevEvThrottleAdminStatus对象类型
SYNTAX INTEGER {
unconstrained(1),
maintainBelowThreshold(2),
stopAtThreshold(3),
inhibited(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Controls the transmission of traps and syslog messages
with respect to the trap pacing threshold.
SYNTAX INTEGER {
unconstrained(1),
maintainBelowThreshold(2),
stopAtThreshold(3),
inhibited(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Controls the transmission of traps and syslog messages
with respect to the trap pacing threshold.
unconstrained(1) causes traps and syslog messages to be transmitted without regard to the threshold settings.
无约束（1）导致陷阱和系统日志消息在不考虑阈值设置的情况下传输。
maintainBelowThreshold(2) causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold.
如果陷阱数量超过阈值，maintainBelowThreshold（2）会导致陷阱传输和系统日志消息被抑制。
stopAtThreshold(3) causes trap transmission to cease at the threshold and not to resume until directed to do so.
stopAtThreshold（3）导致陷阱传输在阈值处停止，并且在指示恢复之前不会恢复。
inhibited(4) causes all trap transmission and syslog messages to be suppressed.
抑制（4）导致所有陷阱传输和系统日志消息被抑制。
A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event.
对于阈值计数，单个事件始终被视为单个事件。也就是说，同时导致陷阱和系统日志消息的事件仍然被视为单个事件。
Writing to this object resets the thresholding state."
DEFVAL { unconstrained }
::= { docsDevEvent 3 }
Writing to this object resets the thresholding state."
DEFVAL { unconstrained }
::= { docsDevEvent 3 }
docsDevEvThrottleInhibited OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS deprecated DESCRIPTION "If true(1), trap and syslog transmission is currently inhibited due to thresholds and/or the current setting of docsDevEvThrottleAdminStatus. In addition, this is true(1) when transmission is inhibited because no syslog (docsDevEvSyslog) or trap (docsDevNmAccessEntry) destinations have been set.
docsDevEvThrottleInhibited对象类型语法TruthValue MAX-ACCESS只读状态不推荐使用说明“如果为true（1），陷阱和系统日志传输当前由于阈值和/或docsDevEvThrottleAdminStatus的当前设置而被禁止。此外，如果传输因无系统日志（docsDevEvSyslog）而被禁止，则为true（1）或陷阱（docsDevNmAccessEntry）目标已设置。
This object is deprecated and is replaced by docsDevEvThrottleThresholdExceeded."
此对象已弃用，并被DocsDevevthRottletThresholdExceed替换。“
::= { docsDevEvent 4 }
::= { docsDevEvent 4 }
docsDevEvThrottleThreshold OBJECT-TYPE SYNTAX Unsigned32 UNITS "events" MAX-ACCESS read-write STATUS current DESCRIPTION "Number of events per docsDevEvThrottleInterval permitted before throttling is to occur.
docsDevEvThrottleThreshold对象类型语法未签名32个单位“事件”最大访问读写状态当前描述“在发生节流之前，每个docsDevEvThrottleInterval允许的事件数。
A single event, whether the notification could result in messages transmitted using syslog, SNMP, or both protocols, and regardless of the number of destinations, (including zero) is always treated as a single event for threshold counting. For example, an event causing both a trap and a syslog message is still treated as a single event.
对于单个事件，无论通知是否会导致使用syslog、SNMP或这两种协议传输消息，也不管目的地的数量如何（包括零），都始终被视为阈值计数的单个事件。例如，导致陷阱和系统日志消息的事件仍然被视为单个事件。
All system notifications that occur within the device
should be taken into consideration when calculating
and monitoring the threshold."
DEFVAL { 0 }
::= { docsDevEvent 5 }
All system notifications that occur within the device
should be taken into consideration when calculating
and monitoring the threshold."
DEFVAL { 0 }
::= { docsDevEvent 5 }
docsDevEvThrottleInterval OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The interval over which docsDevEvThrottleThreshold
applies."
DEFVAL { 1 }
::= { docsDevEvent 6 }
docsDevEvThrottleInterval OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
UNITS "seconds"
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The interval over which docsDevEvThrottleThreshold
applies."
DEFVAL { 1 }
::= { docsDevEvent 6 }
--
-- The following table controls the reporting of the various classes
-- of events.
--
--
-- The following table controls the reporting of the various classes
-- of events.
--
docsDevEvControlTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevEvControlEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table allows control of the reporting of event classes. For each event priority, a combination of
DocsDevEvControlEntry的DocsDevEvControlEntry MAX-ACCESS不可访问状态当前说明“此表允许控制事件类的报告。对于每个事件优先级
logging and reporting mechanisms may be chosen. The
mapping of event types to priorities is
vendor dependent. Vendors may also choose to allow
the user to control that mapping through proprietary
means. Table entries MUST persist across reboots for
CMTS devices and MUST NOT persist across reboots for CM
devices."
::= { docsDevEvent 7 }
logging and reporting mechanisms may be chosen. The
mapping of event types to priorities is
vendor dependent. Vendors may also choose to allow
the user to control that mapping through proprietary
means. Table entries MUST persist across reboots for
CMTS devices and MUST NOT persist across reboots for CM
devices."
::= { docsDevEvent 7 }
docsDevEvControlEntry OBJECT-TYPE
SYNTAX DocsDevEvControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Allows configuration of the reporting mechanisms for a
particular event priority."
INDEX { docsDevEvPriority }
::= { docsDevEvControlTable 1 }
docsDevEvControlEntry OBJECT-TYPE
SYNTAX DocsDevEvControlEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Allows configuration of the reporting mechanisms for a
particular event priority."
INDEX { docsDevEvPriority }
::= { docsDevEvControlTable 1 }
DocsDevEvControlEntry ::= SEQUENCE {
docsDevEvPriority INTEGER,
docsDevEvReporting BITS
}
DocsDevEvControlEntry ::= SEQUENCE {
docsDevEvPriority INTEGER,
docsDevEvReporting BITS
}
docsDevEvPriority OBJECT-TYPE
SYNTAX INTEGER {
emergency(1),
alert(2),
critical(3),
error(4),
warning(5),
notice(6),
information(7),
debug(8)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The priority level that is controlled by this
entry. These are ordered from most (emergency) to least
(debug) critical. Each event with a CM or CMTS has a
particular priority level associated with it (as defined
by the vendor).
docsDevEvPriority OBJECT-TYPE
SYNTAX INTEGER {
emergency(1),
alert(2),
critical(3),
error(4),
warning(5),
notice(6),
information(7),
debug(8)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The priority level that is controlled by this
entry. These are ordered from most (emergency) to least
(debug) critical. Each event with a CM or CMTS has a
particular priority level associated with it (as defined
by the vendor).
emergency(1) events indicate vendor-specific fatal hardware or software errors that prevent normal system operation.
紧急（1）事件表示供应商特定的致命硬件或软件错误，这些错误会妨碍系统正常运行。
alert(2) events indicate a serious failure that causes the reporting system to reboot but is not caused by hardware or software malfunctioning.
警报（2）事件表示导致报告系统重新启动的严重故障，但不是由硬件或软件故障引起的。
critical(3) events indicate a serious failure that requires attention and prevents the device from transmitting data but that could be recovered without rebooting the system.
严重（3）事件表示严重故障，需要注意并阻止设备传输数据，但无需重新启动系统即可恢复。
error(4) and warning(5) events indicate that a failure occurred that could interrupt the normal data flow but that does not cause the device to re-register.
错误（4）和警告（5）事件表明发生了可能中断正常数据流但不会导致设备重新注册的故障。
notice(6) and information(7) events indicate a milestone or checkpoint in normal operation that could be of particular importance for troubleshooting.
注意（6）和信息（7）事件表示正常运行中的里程碑或检查点，这可能对故障排除特别重要。
debug(8) events are reserved for vendor-specific events.
调试（8）事件是为特定于供应商的事件保留的。
During normal operation, no event more
critical than notice(6) should be generated. Events
between warning and emergency should be generated at
appropriate levels of problems (e.g., emergency when the
box is about to crash)."
::= { docsDevEvControlEntry 1 }
During normal operation, no event more
critical than notice(6) should be generated. Events
between warning and emergency should be generated at
appropriate levels of problems (e.g., emergency when the
box is about to crash)."
::= { docsDevEvControlEntry 1 }
docsDevEvReporting OBJECT-TYPE
SYNTAX BITS {
local(0),
traps(1),
syslog(2),
-- The following are extensions to the original set of
-- labels. The extensions start at an octet boundary.
-- So for bits 3 - 7, one MUST set them to zero on send
-- and one MUST ignore them on receipt.
localVolatile(8),
stdInterface(9)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Defines the action to be taken on occurrence of this
event class. Implementations may not necessarily
support all options for all event classes but at
minimum must allow traps and syslogging to be
disabled.
docsDevEvReporting OBJECT-TYPE
SYNTAX BITS {
local(0),
traps(1),
syslog(2),
-- The following are extensions to the original set of
-- labels. The extensions start at an octet boundary.
-- So for bits 3 - 7, one MUST set them to zero on send
-- and one MUST ignore them on receipt.
localVolatile(8),
stdInterface(9)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Defines the action to be taken on occurrence of this
event class. Implementations may not necessarily
support all options for all event classes but at
minimum must allow traps and syslogging to be
disabled.
If the local(0) bit is set, then log to the internal
log and update non-volatile store, for backward
compatibility with the original RFC 2669 definition.
If the traps(1) bit is set, then generate
an SNMP trap; if the syslog(2) bit is set, then
send a syslog message (assuming that the syslog address
is set). If the localVolatile(8) bit is set, then
log to the internal log without updating non-volatile
store. If the stdInterface(9) bit is set, then the
agent ignores all other bits except the local(0),
syslog(2), and localVolatile(8) bits. Setting the
stdInterface(9) bit indicates that RFC3413 and
RFC3014 are being used to control event reporting
mechanisms."
::= { docsDevEvControlEntry 2 }
If the local(0) bit is set, then log to the internal
log and update non-volatile store, for backward
compatibility with the original RFC 2669 definition.
If the traps(1) bit is set, then generate
an SNMP trap; if the syslog(2) bit is set, then
send a syslog message (assuming that the syslog address
is set). If the localVolatile(8) bit is set, then
log to the internal log without updating non-volatile
store. If the stdInterface(9) bit is set, then the
agent ignores all other bits except the local(0),
syslog(2), and localVolatile(8) bits. Setting the
stdInterface(9) bit indicates that RFC3413 and
RFC3014 are being used to control event reporting
mechanisms."
::= { docsDevEvControlEntry 2 }
docsDevEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF DocsDevEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Contains a log of network and device events that may be
of interest in fault isolation and troubleshooting.
If the local(0) bit is set in docsDevEvReporting,
entries in this table MUST persist across reboots."
::= { docsDevEvent 8 }
docsDevEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF DocsDevEventEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Contains a log of network and device events that may be
of interest in fault isolation and troubleshooting.
If the local(0) bit is set in docsDevEvReporting,
entries in this table MUST persist across reboots."
::= { docsDevEvent 8 }
docsDevEventEntry OBJECT-TYPE SYNTAX DocsDevEventEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describes a network or device event that may be of interest in fault isolation and troubleshooting. Multiple sequential identical events are represented by incrementing docsDevEvCounts and setting docsDevEvLastTime to the current time rather than creating multiple rows.
DOCSDEVEVENTERY对象类型语法DOCSDEVEVENTERY MAX-ACCESS不可访问状态当前描述“描述可能与故障隔离和故障排除有关的网络或设备事件。多个顺序相同的事件通过递增docsDevEvCounts并将docsDevEvLastTime设置为当前时间而不是创建多行来表示。
Entries are created with the first occurrence of an
event. docsDevEvControl can be used to clear the
table. Individual events cannot be deleted."
INDEX { docsDevEvIndex }
::= { docsDevEventTable 1 }
Entries are created with the first occurrence of an
event. docsDevEvControl can be used to clear the
table. Individual events cannot be deleted."
INDEX { docsDevEvIndex }
::= { docsDevEventTable 1 }
DocsDevEventEntry ::= SEQUENCE {
docsDevEvIndex Integer32,
docsDevEvFirstTime DateAndTime,
DocsDevEventEntry ::= SEQUENCE {
docsDevEvIndex Integer32,
docsDevEvFirstTime DateAndTime,
docsDevEvLastTime DateAndTime, docsDevEvCounts Counter32, docsDevEvLevel INTEGER, docsDevEvId Unsigned32, docsDevEvText SnmpAdminString }
docsDevEvLastTime日期和时间，docsDevEvCounts计数器32，docsDevEvLevel整数，docsDevEvId无符号32，docsDevEvText snmpadmin}
docsDevEvIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Provides relative ordering of the objects in the event
log. This object will always increase except when
(a) the log is reset via docsDevEvControl,
(b) the device reboots and does not implement
non-volatile storage for this log, or (c) it reaches
the value 2^31. The next entry for all the above
cases is 1."
::= { docsDevEventEntry 1 }
docsDevEvIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Provides relative ordering of the objects in the event
log. This object will always increase except when
(a) the log is reset via docsDevEvControl,
(b) the device reboots and does not implement
non-volatile storage for this log, or (c) it reaches
the value 2^31. The next entry for all the above
cases is 1."
::= { docsDevEventEntry 1 }
docsDevEvFirstTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of docsDevDateTime at the time this entry was
created."
::= { docsDevEventEntry 2 }
docsDevEvFirstTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of docsDevDateTime at the time this entry was
created."
::= { docsDevEventEntry 2 }
docsDevEvLastTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"When an entry reports only one event, this object will
have the same value as the corresponding instance of
docsDevEvFirstTime. When an entry reports multiple
events, this object will record the value that
docsDevDateTime had when the most recent event for this
entry occurred."
::= { docsDevEventEntry 3 }
docsDevEvLastTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"When an entry reports only one event, this object will
have the same value as the corresponding instance of
docsDevEvFirstTime. When an entry reports multiple
events, this object will record the value that
docsDevDateTime had when the most recent event for this
entry occurred."
::= { docsDevEventEntry 3 }
-- This object was renamed from docsDevEvCount to meet naming
-- requirements for Counter32
docsDevEvCounts OBJECT-TYPE
SYNTAX Counter32
UNITS "events"
-- This object was renamed from docsDevEvCount to meet naming
-- requirements for Counter32
docsDevEvCounts OBJECT-TYPE
SYNTAX Counter32
UNITS "events"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of consecutive event instances reported by
this entry. This starts at 1 with the creation of this
row and increments by 1 for each subsequent duplicate
event."
::= { docsDevEventEntry 4 }
docsDevEvLevel OBJECT-TYPE
SYNTAX INTEGER {
emergency(1),
alert(2),
critical(3),
error(4),
warning(5),
notice(6),
information(7),
debug(8)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The priority level of this event, as defined by the
vendor. These are ordered from most serious (emergency)
to least serious (debug).
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of consecutive event instances reported by
this entry. This starts at 1 with the creation of this
row and increments by 1 for each subsequent duplicate
event."
::= { docsDevEventEntry 4 }
docsDevEvLevel OBJECT-TYPE
SYNTAX INTEGER {
emergency(1),
alert(2),
critical(3),
error(4),
warning(5),
notice(6),
information(7),
debug(8)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The priority level of this event, as defined by the
vendor. These are ordered from most serious (emergency)
to least serious (debug).
emergency(1) events indicate vendor-specific fatal hardware or software errors that prevent normal system operation.
紧急（1）事件表示供应商特定的致命硬件或软件错误，这些错误会妨碍系统正常运行。
alert(2) events indicate a serious failure that causes the reporting system to reboot but that is not caused by hardware or software malfunctioning.
警报（2）事件表示导致报告系统重新启动但并非由硬件或软件故障引起的严重故障。
critical(3) events indicate a serious failure that requires attention and prevents the device from transmitting data but that could be recovered without rebooting the system.
严重（3）事件表示严重故障，需要注意并阻止设备传输数据，但无需重新启动系统即可恢复。
error(4) and warning(5) events indicate that a failure occurred that could interrupt the normal data flow but that does not cause the device to re-register.
错误（4）和警告（5）事件表明发生了可能中断正常数据流但不会导致设备重新注册的故障。
notice(6) and information(7) events indicate a milestone or checkpoint in normal operation that could be of particular importance for troubleshooting.
注意（6）和信息（7）事件表示正常运行中的里程碑或检查点，这可能对故障排除特别重要。
debug(8) events are reserved for vendor-specific
调试（8）事件保留给特定于供应商的
events.
事件。
During normal operation, no event more
critical than notice(6) should be generated. Events
between warning and emergency should be generated at
appropriate levels of problems (e.g., emergency when the
box is about to crash)."
::= { docsDevEventEntry 5 }
During normal operation, no event more
critical than notice(6) should be generated. Events
between warning and emergency should be generated at
appropriate levels of problems (e.g., emergency when the
box is about to crash)."
::= { docsDevEventEntry 5 }
--
-- It is strongly recommended that implementors follow the CableLabs
-- enumerations for docsDevEvId, per the DOCSIS OSSIv1.1 spec
-- and follow-on specifications.
--
--
-- It is strongly recommended that implementors follow the CableLabs
-- enumerations for docsDevEvId, per the DOCSIS OSSIv1.1 spec
-- and follow-on specifications.
--
docsDevEvId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For this product, uniquely identifies the type of event
that is reported by this entry."
REFERENCE
"DOCSIS OSSI 1.1 Specification, Appendix H and
DOCSIS OSSI 2.0 Specification, Annex D."
::= { docsDevEventEntry 6 }
docsDevEvId OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"For this product, uniquely identifies the type of event
that is reported by this entry."
REFERENCE
"DOCSIS OSSI 1.1 Specification, Appendix H and
DOCSIS OSSI 2.0 Specification, Annex D."
::= { docsDevEventEntry 6 }
docsDevEvText OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Provides a human-readable description of the event,
including all relevant context (interface numbers,
etc.)."
::= { docsDevEventEntry 7 }
docsDevEvText OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Provides a human-readable description of the event,
including all relevant context (interface numbers,
etc.)."
::= { docsDevEventEntry 7 }
docsDevEvSyslogAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The type of address of docsDevEvSyslogAddress. If
no syslog server exists, this value should return
unknown(0)."
DEFVAL { unknown }
::= { docsDevEvent 9 }
docsDevEvSyslogAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The type of address of docsDevEvSyslogAddress. If
no syslog server exists, this value should return
unknown(0)."
DEFVAL { unknown }
::= { docsDevEvent 9 }
docsDevEvSyslogAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION "The Internet address of the Syslog server, as provided by DHCP option 7 or set via SNMP management. If the address of the server is set to the zero-length string, the 0.0.0.0 IPv4 address, or the 0: IPv6 address, Syslog transmission is inhibited.
docsDevEvSyslogAddress对象类型语法InetAddress MAX-ACCESS读写状态当前说明“系统日志服务器的Internet地址，由DHCP选项7提供或通过SNMP管理设置。如果服务器地址设置为零长度字符串、0.0.0.0 IPv4地址或0:IPv6地址，则系统日志传输将被禁止。
Note that if multiple values are provided to the CM in DHCP option 7, the value of this MIB object MUST be the first Syslog server address received.
请注意，如果在DHCP选项7中向CM提供多个值，则此MIB对象的值必须是收到的第一个Syslog服务器地址。
By default at agent boot, this object returns the zero
length string."
::= { docsDevEvent 10 }
By default at agent boot, this object returns the zero
length string."
::= { docsDevEvent 10 }
docsDevEvThrottleThresholdExceeded OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If true(1), trap and syslog transmission is currently
inhibited due to exceeding the trap/syslog event
threshold in the current interval."
::= { docsDevEvent 11 }
docsDevEvThrottleThresholdExceeded OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If true(1), trap and syslog transmission is currently
inhibited due to exceeding the trap/syslog event
threshold in the current interval."
::= { docsDevEvent 11 }
-- -- Link Level Control Filtering --
----链路级控制过滤--
docsDevFilter OBJECT IDENTIFIER ::= { docsDevMIBObjects 6 }
docsDevFilter OBJECT IDENTIFIER ::= { docsDevMIBObjects 6 }
docsDevFilterLLCUnmatchedAction OBJECT-TYPE
SYNTAX INTEGER {
discard(1),
accept(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"LLC (Link Level Control) filters can be defined on an
inclusive or exclusive basis: CMs can be configured to
forward only packets matching a set of layer three
protocols, or to drop packets matching a set of layer
three protocols. Typical use of these filters is to
docsDevFilterLLCUnmatchedAction OBJECT-TYPE
SYNTAX INTEGER {
discard(1),
accept(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"LLC (Link Level Control) filters can be defined on an
inclusive or exclusive basis: CMs can be configured to
forward only packets matching a set of layer three
protocols, or to drop packets matching a set of layer
three protocols. Typical use of these filters is to
filter out possibly harmful (given the context of a large metropolitan LAN) protocols.
过滤掉可能有害的（考虑到大型城域局域网的环境）协议。
If set to discard(1), any L2 packet that does not match
at least one filter in the docsDevFilterLLCTable will be
discarded. If set to accept(2), any L2 packet that
does not match at least one filter in the
docsDevFilterLLCTable will be accepted for further
processing (e.g., bridging). In other words, if the
packet does not match an entry in the table, it takes
this action; if it does match an entry in the table, it
takes the opposite of this action."
DEFVAL { accept }
::= { docsDevFilter 1 }
If set to discard(1), any L2 packet that does not match
at least one filter in the docsDevFilterLLCTable will be
discarded. If set to accept(2), any L2 packet that
does not match at least one filter in the
docsDevFilterLLCTable will be accepted for further
processing (e.g., bridging). In other words, if the
packet does not match an entry in the table, it takes
this action; if it does match an entry in the table, it
takes the opposite of this action."
DEFVAL { accept }
::= { docsDevFilter 1 }
docsDevFilterLLCTable OBJECT-TYPE
SYNTAX SEQUENCE OF DocsDevFilterLLCEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of filters to apply to (bridged) LLC
traffic. The filters in this table are applied to
incoming traffic on the appropriate interface(s) prior
to any further processing (e.g., before the packet
is handed off for level 3 processing, or for bridging).
The specific action taken when no filter is matched is
controlled by docsDevFilterLLCUnmatchedAction. Table
entries MUST NOT persist across reboots for any device."
::= { docsDevFilter 2 }
docsDevFilterLLCTable OBJECT-TYPE
SYNTAX SEQUENCE OF DocsDevFilterLLCEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A list of filters to apply to (bridged) LLC
traffic. The filters in this table are applied to
incoming traffic on the appropriate interface(s) prior
to any further processing (e.g., before the packet
is handed off for level 3 processing, or for bridging).
The specific action taken when no filter is matched is
controlled by docsDevFilterLLCUnmatchedAction. Table
entries MUST NOT persist across reboots for any device."
::= { docsDevFilter 2 }
docsDevFilterLLCEntry OBJECT-TYPE
SYNTAX DocsDevFilterLLCEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Describes a single filter to apply to (bridged) LLC
traffic received on a specified interface. "
INDEX { docsDevFilterLLCIndex }
::= { docsDevFilterLLCTable 1 }
docsDevFilterLLCEntry OBJECT-TYPE
SYNTAX DocsDevFilterLLCEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Describes a single filter to apply to (bridged) LLC
traffic received on a specified interface. "
INDEX { docsDevFilterLLCIndex }
::= { docsDevFilterLLCTable 1 }
DocsDevFilterLLCEntry ::= SEQUENCE {
docsDevFilterLLCIndex Integer32,
docsDevFilterLLCStatus RowStatus,
docsDevFilterLLCIfIndex InterfaceIndexOrZero,
docsDevFilterLLCProtocolType INTEGER,
docsDevFilterLLCProtocol Integer32,
docsDevFilterLLCMatches Counter32
}
DocsDevFilterLLCEntry ::= SEQUENCE {
docsDevFilterLLCIndex Integer32,
docsDevFilterLLCStatus RowStatus,
docsDevFilterLLCIfIndex InterfaceIndexOrZero,
docsDevFilterLLCProtocolType INTEGER,
docsDevFilterLLCProtocol Integer32,
docsDevFilterLLCMatches Counter32
}
docsDevFilterLLCIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index used for the identification of filters (note that
LLC filter order is irrelevant)."
::= { docsDevFilterLLCEntry 1 }
docsDevFilterLLCStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Controls and reflects the status of rows in this
table. There is no restriction on changing any of the
associated columns for this row while this object is set
to active.
docsDevFilterLLCIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index used for the identification of filters (note that
LLC filter order is irrelevant)."
::= { docsDevFilterLLCEntry 1 }
docsDevFilterLLCStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Controls and reflects the status of rows in this
table. There is no restriction on changing any of the
associated columns for this row while this object is set
to active.
Specifying only this object (with the
appropriate index) on a CM is sufficient to create a
filter row that matches all inbound packets on the
ethernet interface and results in the packets being
discarded. docsDevFilterLLCIfIndex (at least) must be
specified on a CMTS to create a row."
::= { docsDevFilterLLCEntry 2}
Specifying only this object (with the
appropriate index) on a CM is sufficient to create a
filter row that matches all inbound packets on the
ethernet interface and results in the packets being
discarded. docsDevFilterLLCIfIndex (at least) must be
specified on a CMTS to create a row."
::= { docsDevFilterLLCEntry 2}
docsDevFilterLLCIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another network interface. If the value is zero, the filter applies to all interfaces. In Cable Modems, the default value is the customer side interface(s). In CMTSs, this object has to be specified to create a row in this table.
DocsdevFilterlCifindex对象类型语法接口IndexorZero MAX-ACCESS读取创建状态当前描述“应用此筛选器的输入界面。该值对应于CATV MAC或其他网络接口的ifIndex。如果该值为零，则过滤器将应用于所有接口。在电缆调制解调器中，默认值是客户端接口。在CMTSs中，必须指定此对象才能在此表中创建行。
Note that according to the DOCSIS OSSIv1.1
specification, ifIndex '1' in the CM means that this
row applies to all Cable Modem-to-CPE Interfaces
(CMCI)."
REFERENCE
"DOCSIS OSSI 1.1 Specification, Section 3.3.4.1. and
DOCSIS OSSI 2.0 Specification, Section 6.3.4.1."
::= { docsDevFilterLLCEntry 3 }
Note that according to the DOCSIS OSSIv1.1
specification, ifIndex '1' in the CM means that this
row applies to all Cable Modem-to-CPE Interfaces
(CMCI)."
REFERENCE
"DOCSIS OSSI 1.1 Specification, Section 3.3.4.1. and
DOCSIS OSSI 2.0 Specification, Section 6.3.4.1."
::= { docsDevFilterLLCEntry 3 }
docsDevFilterLLCProtocolType OBJECT-TYPE
SYNTAX INTEGER {
ethertype(1),
dsap(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The format of the value in docsDevFilterLLCProtocol:
either a two-byte Ethernet Ethertype, or a one-byte
802.2 Service Access Point (SAP) value. ethertype(1)
also applies to Standard Network Access Protocol
(SNAP) encapsulated frames."
DEFVAL { ethertype }
::= { docsDevFilterLLCEntry 4 }
docsDevFilterLLCProtocolType OBJECT-TYPE
SYNTAX INTEGER {
ethertype(1),
dsap(2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The format of the value in docsDevFilterLLCProtocol:
either a two-byte Ethernet Ethertype, or a one-byte
802.2 Service Access Point (SAP) value. ethertype(1)
also applies to Standard Network Access Protocol
(SNAP) encapsulated frames."
DEFVAL { ethertype }
::= { docsDevFilterLLCEntry 4 }
docsDevFilterLLCProtocol OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The layer-three protocol for which this filter applies.
The protocol value format depends on
docsDevFilterLLCProtocolType. Note that for SNAP
frames, ethertype filtering is performed rather than
Destination Service Access Point (DSAP) =0xAA."
DEFVAL { 0 }
::= { docsDevFilterLLCEntry 5 }
docsDevFilterLLCProtocol OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The layer-three protocol for which this filter applies.
The protocol value format depends on
docsDevFilterLLCProtocolType. Note that for SNAP
frames, ethertype filtering is performed rather than
Destination Service Access Point (DSAP) =0xAA."
DEFVAL { 0 }
::= { docsDevFilterLLCEntry 5 }
docsDevFilterLLCMatches OBJECT-TYPE
SYNTAX Counter32
UNITS "matches"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Counts the number of times this filter was matched."
::= { docsDevFilterLLCEntry 6 }
docsDevFilterLLCMatches OBJECT-TYPE
SYNTAX Counter32
UNITS "matches"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Counts the number of times this filter was matched."
::= { docsDevFilterLLCEntry 6 }
-- -- IPv4 Filtering --
----IPv4过滤--
docsDevFilterIpDefault OBJECT-TYPE
SYNTAX INTEGER {
discard(1),
accept(2)
}
MAX-ACCESS read-write
docsDevFilterIpDefault OBJECT-TYPE
SYNTAX INTEGER {
discard(1),
accept(2)
}
MAX-ACCESS read-write
STATUS deprecated DESCRIPTION "The default behavior for (bridged) packets that do not match IP filters (or Internet filters, if implemented) is defined by docsDevFilterIpDefault.
STATUS deprecated DESCRIPTION“与IP筛选器（或Internet筛选器，如果已实现）不匹配的（桥接）数据包的默认行为由docsDevFilterIpDefault定义。
If set to discard(1), all packets not matching an IP
filter in docsDevFilterIpTable will be discarded. If
set to accept(2), all packets not matching an IP filter
or an Internet filter will be accepted for further
processing (e.g., bridging)."
DEFVAL { accept }
::= { docsDevFilter 3 }
If set to discard(1), all packets not matching an IP
filter in docsDevFilterIpTable will be discarded. If
set to accept(2), all packets not matching an IP filter
or an Internet filter will be accepted for further
processing (e.g., bridging)."
DEFVAL { accept }
::= { docsDevFilter 3 }
docsDevFilterIpTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterIpEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "An ordered list of filters or classifiers to apply to IP traffic. Filter application is ordered by the filter index, rather than by a best match algorithm (note that this implies that the filter table may have gaps in the index values). Packets that match no filters will have policy 0 in the docsDevFilterPolicyTable applied to them, if it exists. Otherwise, Packets that match no filters are discarded or forwarded according to the setting of docsDevFilterIpDefault.
docsDevFilterIpTable对象类型DocsDevFilterIpEntry MAX-ACCESS的语法序列不可访问状态不推荐的描述“应用于IP流量的筛选器或分类器的有序列表。筛选器应用程序按筛选器索引排序，而不是按最佳匹配算法排序（请注意，这意味着筛选器表可能在索引值中存在间隙）。不匹配筛选器的数据包将在docsDevFilterPolicyTable中应用策略0（如果存在）。否则，将根据docsDevFilterIpDefault的设置丢弃或转发不匹配筛选器的数据包。
Any IP packet can theoretically match multiple rows of this table. When considering a packet, the table is scanned in row index order (e.g., filter 10 is checked before filter 20). If the packet matches that filter (which means that it matches ALL criteria for that row), actions appropriate to docsDevFilterIpControl and docsDevFilterPolicyId are taken. If the packet was discarded processing is complete. If docsDevFilterIpContinue is set to true, the filter comparison continues with the next row in the table, looking for additional matches.
理论上，任何IP数据包都可以匹配此表的多行。当考虑分组时，以行索引顺序扫描表（例如，在过滤器20之前检查过滤器10）。如果数据包与该筛选器匹配（这意味着它与该行的所有条件匹配），则将采取适用于docsDevFilterIpControl和docsDevFilterPolicyId的操作。如果数据包被丢弃，则处理完成。如果docsDevFilterIpContinue设置为true，则过滤器比较将继续与表中的下一行进行，以查找其他匹配项。
If the packet matches no filter in the table, the packet is accepted or dropped for further processing according to the setting of docsDevFilterIpDefault. If the packet is accepted, the actions specified by policy group 0 (e.g., the rows in docsDevFilterPolicyTable that have a value of 0 for docsDevFilterPolicyId) are taken, if that policy
如果数据包与表中的任何筛选器都不匹配，则会根据docsDevFilterIpDefault的设置接受或丢弃该数据包以进行进一步处理。如果接受数据包，则执行策略组0指定的操作（例如，docsDevFilterPolicyTable中docsDevFilterPolicyId值为0的行），如果该策略
group exists.
团体存在。
Logically, this table is consulted twice during the processing of any IP packet: once upon its acceptance from the L2 entity, and once upon its transmission to the L2 entity. In actuality, for cable modems, IP filtering is generally the only IP processing done for transit traffic. This means that inbound and outbound filtering can generally be done at the same time with one pass through the filter table.
从逻辑上讲，在处理任何IP数据包的过程中，该表会被查阅两次：一次是在从L2实体接收数据包时，一次是在传输到L2实体时。实际上，对于电缆调制解调器，IP过滤通常是对传输流量进行的唯一IP处理。这意味着入站和出站筛选通常可以通过筛选表一次同时完成。
The objects in this table are only accessible from cable devices that are not operating in DiffServ MIB mode (RFC 3289). See the conformance section for details.
此表中的对象只能从未在DiffServ MIB模式（RFC 3289）下运行的电缆设备访问。有关详细信息，请参阅一致性部分。
Note that some devices are required by other specifications (e.g., the DOCSIS OSSIv1.1 specification) to support the legacy SNMPv1/v2c docsDevFilter mode for backward compatibility.
请注意，其他规范（如DOCSIS OSSIv1.1规范）要求某些设备支持传统SNMPv1/v2c docsDevFilter模式以实现向后兼容性。
Table entries MUST NOT persist across reboots for any device.
对于任何设备，表项在重新启动期间都不能持久存在。
This table is deprecated. Instead, use the DiffServ MIB
from RFC 3289."
::= { docsDevFilter 4 }
This table is deprecated. Instead, use the DiffServ MIB
from RFC 3289."
::= { docsDevFilter 4 }
docsDevFilterIpEntry OBJECT-TYPE SYNTAX DocsDevFilterIpEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "Describes a filter to apply to IP traffic received on a specified interface. All identity objects in this table (e.g., source and destination address/mask, protocol, source/dest port, TOS/mask, interface and direction) must match their respective fields in the packet for any given filter to match.
docsDevFilterIpEntry对象类型语法docsDevFilterIpEntry MAX-ACCESS not accessible STATUS deprecated DESCRIPTION“描述应用于指定接口上接收的IP流量的筛选器。此表中的所有标识对象（例如，源和目标地址/掩码、协议、源/目标端口、TOS/掩码、接口和方向）必须匹配数据包中各自的字段，才能匹配任何给定的筛选器。
To create an entry in this table, docsDevFilterIpIfIndex
must be specified."
INDEX { docsDevFilterIpIndex }
::= { docsDevFilterIpTable 1 }
To create an entry in this table, docsDevFilterIpIfIndex
must be specified."
INDEX { docsDevFilterIpIndex }
::= { docsDevFilterIpTable 1 }
DocsDevFilterIpEntry ::= SEQUENCE {
docsDevFilterIpIndex Integer32,
docsDevFilterIpStatus RowStatus,
docsDevFilterIpControl INTEGER,
DocsDevFilterIpEntry ::= SEQUENCE {
docsDevFilterIpIndex Integer32,
docsDevFilterIpStatus RowStatus,
docsDevFilterIpControl INTEGER,
docsDevFilterIpIfIndex InterfaceIndexOrZero, docsDevFilterIpDirection INTEGER, docsDevFilterIpBroadcast TruthValue, docsDevFilterIpSaddr IpAddress, docsDevFilterIpSmask IpAddress, docsDevFilterIpDaddr IpAddress, docsDevFilterIpDmask IpAddress, docsDevFilterIpProtocol Integer32, docsDevFilterIpSourcePortLow Integer32, docsDevFilterIpSourcePortHigh Integer32, docsDevFilterIpDestPortLow Integer32, docsDevFilterIpDestPortHigh Integer32, docsDevFilterIpMatches ZeroBasedCounter32, docsDevFilterIpTos OCTET STRING, docsDevFilterIpTosMask OCTET STRING, docsDevFilterIpContinue TruthValue, docsDevFilterIpPolicyId Integer32 }
DOCSDEVFILTERIPFINFINDEX接口索引为零，DOCSDEVFILTERIPDIRECT INTEGER，docsDevFilterIpBroadcast TruthValue，docsDevFilterIpSaddr IpAddress，docsDevFilterIpDaddr IpAddress，DOCSDEVFILTERIPDROSK IpAddress，docsDevFilterIpProtocol Integer32，DOCSDEVFILTERIPSOURCEPTLOW Integer32，DOCSDEVFILTERIPSOURCE高整数32、DOCSDEVFILTERIPDESTPORT低整数32、DOCSDEVFILTERIPDESTPORT高整数32、DOCSDEVFILTERIPMAPMATCHES ZeroBasedCounter32、docsDevFilterIpTos八位字符串、DOCSDEVFILTERIPTOSSMAK八位字符串、docsDevFilterIpContinue TRUTH值、docsDevFilterIpPolicyId整数32}
docsDevFilterIpIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"Index used to order the application of filters.
The filter with the lowest index is always applied
first."
::= { docsDevFilterIpEntry 1 }
docsDevFilterIpIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"Index used to order the application of filters.
The filter with the lowest index is always applied
first."
::= { docsDevFilterIpEntry 1 }
docsDevFilterIpStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Controls and reflects the status of rows in this
table. Specifying only this object (with the
appropriate index) on a CM is sufficient to create a
filter row that matches all inbound packets on the
ethernet interface and results in the packets being
discarded. docsDevFilterIpIfIndex (at least) must be
specified on a CMTS to create a row. Creation of the
rows may be done via either create-and-wait or
create-and-go, but the filter is not applied until this
object is set to (or changes to) active. There is no
restriction in changing any object in a row while this
object is set to active."
::= { docsDevFilterIpEntry 2 }
docsDevFilterIpStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Controls and reflects the status of rows in this
table. Specifying only this object (with the
appropriate index) on a CM is sufficient to create a
filter row that matches all inbound packets on the
ethernet interface and results in the packets being
discarded. docsDevFilterIpIfIndex (at least) must be
specified on a CMTS to create a row. Creation of the
rows may be done via either create-and-wait or
create-and-go, but the filter is not applied until this
object is set to (or changes to) active. There is no
restriction in changing any object in a row while this
object is set to active."
::= { docsDevFilterIpEntry 2 }
docsDevFilterIpControl OBJECT-TYPE
SYNTAX INTEGER {
discard(1),
accept(2),
policy(3)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"If set to discard(1), all packets matching this filter
will be discarded, and scanning of the remainder of the
filter list will be aborted. If set to accept(2), all
packets matching this filter will be accepted for
further processing (e.g., bridging). If
docsDevFilterIpContinue is set to true, see if there
are other matches; otherwise, done. If set to
policy (3), execute the policy entries
matched by docsDevFilterIpPolicyId in
docsDevFilterPolicyTable.
docsDevFilterIpControl OBJECT-TYPE
SYNTAX INTEGER {
discard(1),
accept(2),
policy(3)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"If set to discard(1), all packets matching this filter
will be discarded, and scanning of the remainder of the
filter list will be aborted. If set to accept(2), all
packets matching this filter will be accepted for
further processing (e.g., bridging). If
docsDevFilterIpContinue is set to true, see if there
are other matches; otherwise, done. If set to
policy (3), execute the policy entries
matched by docsDevFilterIpPolicyId in
docsDevFilterPolicyTable.
If docsDevFilterIpContinue is set to true, continue
scanning the table for other matches; otherwise, done."
DEFVAL { discard }
::= { docsDevFilterIpEntry 3 }
If docsDevFilterIpContinue is set to true, continue
scanning the table for other matches; otherwise, done."
DEFVAL { discard }
::= { docsDevFilterIpEntry 3 }
docsDevFilterIpIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS deprecated DESCRIPTION "The entry interface to which this filter applies. The value corresponds to ifIndex for either a CATV MAC or another interface. If the value is zero, the filter applies to all interfaces. Default value in CMs is the index of the customer-side (e.g., ethernet) interface(s). In CMTSes, this object MUST be specified to create a row in this table.
docsDevFilterIpIfIndex对象类型语法接口INDEXORZERO MAX-ACCESS读取创建状态不推荐的说明“应用此筛选器的输入界面。该值对应于CATV MAC或其他接口的ifIndex。如果该值为零，则过滤器将应用于所有接口。CMs中的默认值是客户端（如以太网）接口的索引。在CMTSes中，必须指定此对象才能在此表中创建行。
Note that according to the DOCSIS OSSIv1.1
specification, ifIndex '1' in the Cable Modem means
that this row applies to all CMCI (customer-facing)
interfaces."
REFERENCE
"DOCSIS OSSI 1.1 Specification, Section 3.3.4.1. and
DOCSIS OSSI 2.0 Specification, Section 6.3.4.1."
::= { docsDevFilterIpEntry 4 }
Note that according to the DOCSIS OSSIv1.1
specification, ifIndex '1' in the Cable Modem means
that this row applies to all CMCI (customer-facing)
interfaces."
REFERENCE
"DOCSIS OSSI 1.1 Specification, Section 3.3.4.1. and
DOCSIS OSSI 2.0 Specification, Section 6.3.4.1."
::= { docsDevFilterIpEntry 4 }
docsDevFilterIpDirection OBJECT-TYPE
docsDevFilterIpDirection对象类型
SYNTAX INTEGER {
inbound(1),
outbound(2),
both(3)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Determines whether the filter is applied to inbound(1)
traffic, outbound(2) traffic, or traffic in both(3)
directions."
DEFVAL { inbound }
::= { docsDevFilterIpEntry 5 }
SYNTAX INTEGER {
inbound(1),
outbound(2),
both(3)
}
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Determines whether the filter is applied to inbound(1)
traffic, outbound(2) traffic, or traffic in both(3)
directions."
DEFVAL { inbound }
::= { docsDevFilterIpEntry 5 }
docsDevFilterIpBroadcast OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"If set to true(1), the filter only applies to multicast
and broadcast traffic. If set to false(2), the filter
applies to all traffic."
DEFVAL { false }
::= { docsDevFilterIpEntry 6 }
docsDevFilterIpBroadcast OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"If set to true(1), the filter only applies to multicast
and broadcast traffic. If set to false(2), the filter
applies to all traffic."
DEFVAL { false }
::= { docsDevFilterIpEntry 6 }
docsDevFilterIpSaddr OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The source IP address, or portion thereof, that is to be
matched for this filter. The source address is first
masked (ANDed) against docsDevFilterIpSmask before
being compared to this value. A value of 0 for this
object and 0 for the mask matches all IP addresses."
DEFVAL { '00000000'h }
::= { docsDevFilterIpEntry 7 }
docsDevFilterIpSaddr OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The source IP address, or portion thereof, that is to be
matched for this filter. The source address is first
masked (ANDed) against docsDevFilterIpSmask before
being compared to this value. A value of 0 for this
object and 0 for the mask matches all IP addresses."
DEFVAL { '00000000'h }
::= { docsDevFilterIpEntry 7 }
docsDevFilterIpSmask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS deprecated DESCRIPTION "A bit mask that is to be applied to the source address prior to matching. This mask is not necessarily the same as a subnet mask, but 1s bits must be leftmost and contiguous." DEFVAL { '00000000'h }
docsDevFilterIpSmask对象类型语法IpAddress MAX-ACCESS read create STATUS deprecated DESCRIPTION“在匹配之前应用于源地址的位掩码。此掩码不一定与子网掩码相同，但1s位必须是最左边且连续的。“DEFVAL{'00000000'h}”
::= { docsDevFilterIpEntry 8 }
::= { docsDevFilterIpEntry 8 }
docsDevFilterIpDaddr OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The destination IP address, or portion thereof, that is
to be matched for this filter. The destination address
is first masked (ANDed) against docsDevFilterIpDmask
before being compared to this value. A value of
00000000 for this object and 00000000 for the mask
matches all IP addresses."
DEFVAL { '00000000'h }
::= { docsDevFilterIpEntry 9 }
docsDevFilterIpDaddr OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The destination IP address, or portion thereof, that is
to be matched for this filter. The destination address
is first masked (ANDed) against docsDevFilterIpDmask
before being compared to this value. A value of
00000000 for this object and 00000000 for the mask
matches all IP addresses."
DEFVAL { '00000000'h }
::= { docsDevFilterIpEntry 9 }
docsDevFilterIpDmask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"A bit mask that is to be applied to the destination
address prior to matching. This mask is not necessarily
the same as a subnet mask, but 1s bits MUST be leftmost
and contiguous."
DEFVAL { '00000000'h }
::= { docsDevFilterIpEntry 10 }
docsDevFilterIpDmask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"A bit mask that is to be applied to the destination
address prior to matching. This mask is not necessarily
the same as a subnet mask, but 1s bits MUST be leftmost
and contiguous."
DEFVAL { '00000000'h }
::= { docsDevFilterIpEntry 10 }
docsDevFilterIpProtocol OBJECT-TYPE
SYNTAX Integer32 (0..256)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The IP protocol value that is to be matched. For
example, icmp is 1, tcp is 6, and udp is 17. A value of
256 matches ANY protocol."
REFERENCE "www.iana.org/assignments/protocol-numbers"
DEFVAL { 256 }
::= { docsDevFilterIpEntry 11 }
docsDevFilterIpProtocol OBJECT-TYPE
SYNTAX Integer32 (0..256)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The IP protocol value that is to be matched. For
example, icmp is 1, tcp is 6, and udp is 17. A value of
256 matches ANY protocol."
REFERENCE "www.iana.org/assignments/protocol-numbers"
DEFVAL { 256 }
::= { docsDevFilterIpEntry 11 }
docsDevFilterIpSourcePortLow OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-create STATUS deprecated DESCRIPTION "This is the inclusive lower bound of the transport-layer source port range that is to be matched. If the IP protocol of the packet is neither UDP nor TCP, this
docsDevFilterIpSourcePortLow对象类型语法整数32（0..65535）MAX-ACCESS read create STATUS DISCREATED DESCRIPTION“这是要匹配的传输层源端口范围的包含下限。如果数据包的IP协议既不是UDP也不是TCP，则此
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 0 }
::= { docsDevFilterIpEntry 12 }
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 0 }
::= { docsDevFilterIpEntry 12 }
docsDevFilterIpSourcePortHigh OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the inclusive upper bound of the transport-layer
source port range that is to be matched. If the IP
protocol of the packet is neither UDP nor TCP, this
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 65535 }
::= { docsDevFilterIpEntry 13 }
docsDevFilterIpSourcePortHigh OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the inclusive upper bound of the transport-layer
source port range that is to be matched. If the IP
protocol of the packet is neither UDP nor TCP, this
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 65535 }
::= { docsDevFilterIpEntry 13 }
docsDevFilterIpDestPortLow OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the inclusive lower bound of the transport-layer
destination port range that is to be matched. If the IP
protocol of the packet is neither UDP nor TCP, this
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 0 }
::= { docsDevFilterIpEntry 14 }
docsDevFilterIpDestPortLow OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the inclusive lower bound of the transport-layer
destination port range that is to be matched. If the IP
protocol of the packet is neither UDP nor TCP, this
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 0 }
::= { docsDevFilterIpEntry 14 }
docsDevFilterIpDestPortHigh OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the inclusive upper bound of the transport-layer
destination port range that is to be matched. If the IP
protocol of the packet is neither UDP nor TCP, this
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 65535 }
::= { docsDevFilterIpEntry 15 }
docsDevFilterIpDestPortHigh OBJECT-TYPE
SYNTAX Integer32 (0..65535)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the inclusive upper bound of the transport-layer
destination port range that is to be matched. If the IP
protocol of the packet is neither UDP nor TCP, this
object is ignored during matching."
REFERENCE "www.iana.org/assignments/port-numbers"
DEFVAL { 65535 }
::= { docsDevFilterIpEntry 15 }
docsDevFilterIpMatches OBJECT-TYPE SYNTAX ZeroBasedCounter32 UNITS "matches" MAX-ACCESS read-only
docsDevFilterIpMatches对象类型语法ZeroBasedCounter32单元“匹配”MAX-ACCESS只读
STATUS deprecated
DESCRIPTION
"Counts the number of times this filter was matched.
This object is initialized to 0 at boot, or at row
creation, and is reset only upon reboot."
::= { docsDevFilterIpEntry 16 }
STATUS deprecated
DESCRIPTION
"Counts the number of times this filter was matched.
This object is initialized to 0 at boot, or at row
creation, and is reset only upon reboot."
::= { docsDevFilterIpEntry 16 }
docsDevFilterIpTos OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the value to be matched to the packet's
TOS (Type of Service) value (after the TOS value
is ANDed with docsDevFilterIpTosMask). A value for this
object of 0 and a mask of 0 matches all TOS values."
DEFVAL { '00'h }
::= { docsDevFilterIpEntry 17 }
docsDevFilterIpTos OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This is the value to be matched to the packet's
TOS (Type of Service) value (after the TOS value
is ANDed with docsDevFilterIpTosMask). A value for this
object of 0 and a mask of 0 matches all TOS values."
DEFVAL { '00'h }
::= { docsDevFilterIpEntry 17 }
docsDevFilterIpTosMask OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The mask to be applied to the packet's TOS value before
matching."
DEFVAL { '00'h }
::= { docsDevFilterIpEntry 18 }
docsDevFilterIpTosMask OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The mask to be applied to the packet's TOS value before
matching."
DEFVAL { '00'h }
::= { docsDevFilterIpEntry 18 }
docsDevFilterIpContinue OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"If this value is set to true and docsDevFilterIpControl
is anything but discard (1), continue scanning and
applying policies. See Section 3.3.3 for more
details."
DEFVAL { false }
::= { docsDevFilterIpEntry 19 }
docsDevFilterIpContinue OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"If this value is set to true and docsDevFilterIpControl
is anything but discard (1), continue scanning and
applying policies. See Section 3.3.3 for more
details."
DEFVAL { false }
::= { docsDevFilterIpEntry 19 }
docsDevFilterIpPolicyId OBJECT-TYPE SYNTAX Integer32 (0..2147483647) MAX-ACCESS read-create STATUS deprecated DESCRIPTION "This object points to an entry in docsDevFilterPolicyTable. If docsDevFilterIpControl
docsdevfilterpolicyid对象类型语法整数32（0..2147483647）MAX-ACCESS read create STATUS deprecated DESCRIPTION“此对象指向docsDevFilterPolicyTable中的一个条目。如果docsdevfilterpcontrol
is set to policy (3), execute all matching policies
in docsDevFilterPolicyTable. If no matching policy
exists, treat as if docsDevFilterIpControl were set
to accept (1). If this object is set to the value of
0, there is no matching policy, and
docsDevFilterPolicyTable MUST NOT be consulted."
DEFVAL { 0 }
::= { docsDevFilterIpEntry 20 }
is set to policy (3), execute all matching policies
in docsDevFilterPolicyTable. If no matching policy
exists, treat as if docsDevFilterIpControl were set
to accept (1). If this object is set to the value of
0, there is no matching policy, and
docsDevFilterPolicyTable MUST NOT be consulted."
DEFVAL { 0 }
::= { docsDevFilterIpEntry 20 }
-- -- Policy Mapping Table --
----策略映射表--
docsDevFilterPolicyTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterPolicyEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A Table that maps between a policy group ID and a set of pointers to policies to be applied. All rows with the same docsDevFilterPolicyId are part of the same group of policy pointers and are applied in the order in this table. docsDevFilterPolicyTable exists to allow multiple policy actions (referenced by policy pointers) to be applied to any given classified packet. The policy actions are applied in index order. For example:
docsDevFilterPolicyTable DocsDevFilterPolicyEntry的对象类型语法序列MAX-ACCESS不可访问状态不推荐使用的说明“在策略组ID和一组指向要应用的策略的指针之间映射的表。具有相同docsDevFilterPolicyId的所有行都是同一组策略指针的一部分，并按此表中的顺序应用。docsDevFilterPolicyTable允许对任何给定的分类数据包应用多个策略操作（由策略指针引用）。策略操作按索引顺序应用。例如：
Index ID Type Action 1 1 TOS 1 9 5 TOS 1 12 1 IPSEC 3
索引ID类型操作1 TOS 19 5 TOS 1 12 1 IPSEC 3
This says that a packet that matches a filter with policy id 1 first has TOS policy 1 applied (which might set the TOS bits to enable a higher priority) and next has the IPSEC policy 3 applied (which may result in the packets being dumped into a secure VPN to a remote encryptor).
这表示匹配策略id为1的筛选器的数据包首先应用TOS策略1（这可能会设置TOS位以启用更高的优先级），然后应用IPSEC策略3（这可能会导致数据包转储到远程加密机的安全VPN中）。
Policy ID 0 is reserved for default actions and is applied only to packets that match no filters in docsDevFilterIpTable.
策略ID 0保留用于默认操作，并且仅应用于docsDevFilterIpTable中不匹配筛选器的数据包。
Table entries MUST NOT persist across reboots for any device.
对于任何设备，表项在重新启动期间都不能持久存在。
This table is deprecated. Instead, use the DiffServ MIB
此表已弃用。相反，使用DiffServ MIB
from RFC 3289."
::= { docsDevFilter 5 }
from RFC 3289."
::= { docsDevFilter 5 }
docsDevFilterPolicyEntry OBJECT-TYPE
SYNTAX DocsDevFilterPolicyEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"An entry in the docsDevFilterPolicyTable. Entries are
created by Network Management. To create an entry,
docsDevFilterPolicyId MUST be specified."
INDEX { docsDevFilterPolicyIndex }
::= { docsDevFilterPolicyTable 1 }
docsDevFilterPolicyEntry OBJECT-TYPE
SYNTAX DocsDevFilterPolicyEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"An entry in the docsDevFilterPolicyTable. Entries are
created by Network Management. To create an entry,
docsDevFilterPolicyId MUST be specified."
INDEX { docsDevFilterPolicyIndex }
::= { docsDevFilterPolicyTable 1 }
DocsDevFilterPolicyEntry ::= SEQUENCE {
docsDevFilterPolicyIndex Integer32,
docsDevFilterPolicyId Integer32,
-- docsDevFilterPolicyType INTEGER,
-- docsDevFilterPolicyAction Integer32,
docsDevFilterPolicyStatus RowStatus,
docsDevFilterPolicyPtr RowPointer
}
DocsDevFilterPolicyEntry ::= SEQUENCE {
docsDevFilterPolicyIndex Integer32,
docsDevFilterPolicyId Integer32,
-- docsDevFilterPolicyType INTEGER,
-- docsDevFilterPolicyAction Integer32,
docsDevFilterPolicyStatus RowStatus,
docsDevFilterPolicyPtr RowPointer
}
docsDevFilterPolicyIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION "Index value for the table."
::= { docsDevFilterPolicyEntry 1 }
docsDevFilterPolicyIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION "Index value for the table."
::= { docsDevFilterPolicyEntry 1 }
docsDevFilterPolicyId OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Policy ID for this entry. If a policy ID can apply to
multiple rows of this table, all relevant policies are
executed. Policy 0 (if populated) is applied to all
packets that do not match any of the filters. N.B. If
docsDevFilterIpPolicyId is set to 0, it DOES NOT match
policy 0 of this table."
::= { docsDevFilterPolicyEntry 2 }
docsDevFilterPolicyId OBJECT-TYPE
SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Policy ID for this entry. If a policy ID can apply to
multiple rows of this table, all relevant policies are
executed. Policy 0 (if populated) is applied to all
packets that do not match any of the filters. N.B. If
docsDevFilterIpPolicyId is set to 0, it DOES NOT match
policy 0 of this table."
::= { docsDevFilterPolicyEntry 2 }
-- The following two objects were removed and never used; however,
-- to preserve OID numbering, they are simply commented out to
-- to ensure that they are not used again.
-- docsDevFilterPolicyType ::= { docsDevFilterPolicyEntry 3 }
-- docsDevFilterPolicyAction ::= { docsDevFilterPolicyEntry 4 }
-- The following two objects were removed and never used; however,
-- to preserve OID numbering, they are simply commented out to
-- to ensure that they are not used again.
-- docsDevFilterPolicyType ::= { docsDevFilterPolicyEntry 3 }
-- docsDevFilterPolicyAction ::= { docsDevFilterPolicyEntry 4 }
docsDevFilterPolicyStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Object used to create an entry in this table. There is
no restriction in changing any object in a row while
this object is set to active.
The following object MUST have a valid value before this
object can be set to active: docsDevFilterPolicyPtr."
::= { docsDevFilterPolicyEntry 5 }
docsDevFilterPolicyStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Object used to create an entry in this table. There is
no restriction in changing any object in a row while
this object is set to active.
The following object MUST have a valid value before this
object can be set to active: docsDevFilterPolicyPtr."
::= { docsDevFilterPolicyEntry 5 }
docsDevFilterPolicyPtr OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS deprecated DESCRIPTION "This object points to a row in an applicable filter policy table. Currently, the only standard policy table is docsDevFilterTosTable.
docsDevFilterPolicyPtr对象类型语法RowPointer MAX-ACCESS read create STATUS deprecated DESCRIPTION“此对象指向适用筛选器策略表中的一行。当前，唯一的标准策略表是docsDevFilterTosTable。
Per the textual convention, this object points to the first accessible object in the row; e.g., to point to a row in docsDevFilterTosTable with an index of 21, the value of this object would be the object identifier docsDevTosStatus.21.
根据文本约定，此对象指向行中的第一个可访问对象；e、 例如，要指向docsDevFilterTosTable中索引为21的行，此对象的值将是对象标识符docsDevTosStatus.21。
Vendors are recommended to adhere to the same convention when adding vendor-specific policy table extensions.
建议供应商在添加特定于供应商的策略表扩展时遵守相同的约定。
If this pointer references an empty or non-existent row, then no policy action is taken.
如果此指针引用空行或不存在行，则不执行任何策略操作。
The default upon row creation is a null pointer that
results in no policy action being taken."
DEFVAL { zeroDotZero }
::= { docsDevFilterPolicyEntry 6 }
The default upon row creation is a null pointer that
results in no policy action being taken."
DEFVAL { zeroDotZero }
::= { docsDevFilterPolicyEntry 6 }
-- -- TOS Policy action table --
----TOS策略操作表--
docsDevFilterTosTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevFilterTosEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "Table used to describe Type of Service (TOS) bits
docsDevFilterTosTable对象类型DocsDevFilterTosEntry MAX-ACCESS的语法序列不可访问状态不推荐的描述“用于描述服务类型（TOS）位的表
processing.
处理。
This table is an adjunct to the docsDevFilterIpTable and the docsDevFilterPolicy table. Entries in the latter table can point to specific rows in this (and other) tables and cause specific actions to be taken. This table permits the manipulation of the value of the Type of Service bits in the IP header of the matched packet as follows:
此表是docsDevFilterPolicy表和docsDevFilterPolicy表的附件。后一个表中的条目可以指向此（和其他）表中的特定行，并导致执行特定操作。此表允许对匹配数据包的IP报头中服务位类型的值进行如下操作：
Set the tosBits of the packet to (tosBits & docsDevFilterTosAndMask) | docsDevFilterTosOrMask
将数据包的tosBits设置为（tosBits&docsDevFilterTosAndMask）| docsDevFilterTosOrMask
This construct allows you to do a clear and set of all the TOS bits in a flexible manner.
此结构允许您以灵活的方式对所有TOS位进行清晰和完整的设置。
Table entries MUST NOT persist across reboots for any device.
对于任何设备，表项在重新启动期间都不能持久存在。
This table is deprecated. Instead, use the DiffServ MIB
from RFC 3289."
::= { docsDevFilter 6 }
This table is deprecated. Instead, use the DiffServ MIB
from RFC 3289."
::= { docsDevFilter 6 }
docsDevFilterTosEntry OBJECT-TYPE
SYNTAX DocsDevFilterTosEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"A TOS policy entry."
INDEX { docsDevFilterTosIndex }
::= { docsDevFilterTosTable 1 }
docsDevFilterTosEntry OBJECT-TYPE
SYNTAX DocsDevFilterTosEntry
MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION
"A TOS policy entry."
INDEX { docsDevFilterTosIndex }
::= { docsDevFilterTosTable 1 }
DocsDevFilterTosEntry ::= SEQUENCE {
docsDevFilterTosIndex Integer32,
docsDevFilterTosStatus RowStatus,
docsDevFilterTosAndMask OCTET STRING,
docsDevFilterTosOrMask OCTET STRING
}
DocsDevFilterTosEntry ::= SEQUENCE {
docsDevFilterTosIndex Integer32,
docsDevFilterTosStatus RowStatus,
docsDevFilterTosAndMask OCTET STRING,
docsDevFilterTosOrMask OCTET STRING
}
docsDevFilterTosIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "The unique index for this row. There are no ordering requirements for this table, and any valid index may be specified."
docsDevFilterTosIndex对象类型语法整数32（1..2147483647）MAX-ACCESS不可访问状态不推荐说明“此行的唯一索引。此表没有排序要求，可以指定任何有效索引。”
::= { docsDevFilterTosEntry 1 }
::= { docsDevFilterTosEntry 1 }
docsDevFilterTosStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The object used to create and delete entries in this
table. A row created by specifying just this object
results in a row that specifies no change to the TOS
bits. A row may be created using either the
create-and-go or create-and-wait paradigms. There is
no restriction on the ability to change values in this
row while the row is active."
::= { docsDevFilterTosEntry 2 }
docsDevFilterTosStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"The object used to create and delete entries in this
table. A row created by specifying just this object
results in a row that specifies no change to the TOS
bits. A row may be created using either the
create-and-go or create-and-wait paradigms. There is
no restriction on the ability to change values in this
row while the row is active."
::= { docsDevFilterTosEntry 2 }
docsDevFilterTosAndMask OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This value is bitwise ANDed with the matched packet's
TOS bits."
DEFVAL { 'ff'h }
::= { docsDevFilterTosEntry 3 }
docsDevFilterTosAndMask OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This value is bitwise ANDed with the matched packet's
TOS bits."
DEFVAL { 'ff'h }
::= { docsDevFilterTosEntry 3 }
docsDevFilterTosOrMask OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This value is bitwise ORed with the result from the
AND procedure (tosBits & docsDevFilterTosAndMask).
The result then replaces the packet's TOS bits."
DEFVAL { '00'h }
::= { docsDevFilterTosEntry 4 }
docsDevFilterTosOrMask OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"This value is bitwise ORed with the result from the
AND procedure (tosBits & docsDevFilterTosAndMask).
The result then replaces the packet's TOS bits."
DEFVAL { '00'h }
::= { docsDevFilterTosEntry 4 }
--
-- CPE IP Management and anti-spoofing group. Only implemented on
-- Cable Modems.
--
--
-- CPE IP Management and anti-spoofing group. Only implemented on
-- Cable Modems.
--
docsDevCpe OBJECT IDENTIFIER ::= { docsDevMIBObjects 7 }
docsDevCpe OBJECT IDENTIFIER ::= { docsDevMIBObjects 7 }
docsDevCpeEnroll OBJECT-TYPE SYNTAX INTEGER { none(1), any(2)
DocsdevcRoll对象类型语法整数{none（1），any（2）
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls the population of
docsDevFilterCpeTable.
If set to none, the filters must be set manually
by a network management action (either configuration
or SNMP set).
If set to any, the CM wiretaps the packets originating
from the ethernet and enrolls up to docsDevCpeIpMax
addresses as based on the source IPv4 or v6 addresses of
those packets."
DEFVAL { any }
::= { docsDevCpe 1 }
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls the population of
docsDevFilterCpeTable.
If set to none, the filters must be set manually
by a network management action (either configuration
or SNMP set).
If set to any, the CM wiretaps the packets originating
from the ethernet and enrolls up to docsDevCpeIpMax
addresses as based on the source IPv4 or v6 addresses of
those packets."
DEFVAL { any }
::= { docsDevCpe 1 }
docsDevCpeIpMax OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls the maximum number of CPEs allowed
to be learned behind this device. If set to zero, any
number of CPEs may connect up to the maximum permitted
for the device.
If set to -1, no filtering is done on CPE source
addresses, and no entries are made in the
docsDevFilterCpeTable via learning. If an attempt is
made to set this to a number greater than that
permitted for the device, it is set to that maximum."
DEFVAL { -1 }
::= { docsDevCpe 2 }
docsDevCpeIpMax OBJECT-TYPE
SYNTAX Integer32 (-1..2147483647)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This object controls the maximum number of CPEs allowed
to be learned behind this device. If set to zero, any
number of CPEs may connect up to the maximum permitted
for the device.
If set to -1, no filtering is done on CPE source
addresses, and no entries are made in the
docsDevFilterCpeTable via learning. If an attempt is
made to set this to a number greater than that
permitted for the device, it is set to that maximum."
DEFVAL { -1 }
::= { docsDevCpe 2 }
docsDevCpeTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevCpeEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This table lists the IPv4 addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. Table entries MUST NOT persist across reboots for any device.
docsDevCpeTable对象类型DocsdevcPeantry MAX-ACCESS的语法序列不可访问状态不推荐的描述“此表列出了看到（或允许）的IPv4地址作为来自此设备上的客户接口的数据包中的源地址。此外，此表可以通过正常的行创建机制提供CPE允许的特定地址。任何设备的表项不得在重新启动期间保持不变。
N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of
注意：管理操作可以在此表和文档中添加超过
docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to add learned addresses automatically.
docsDevCpeIpMax。docsDevCpeIpMax仅限制CM自动添加学习地址的能力。
This table is deprecated and is replaced by
docsDevCpeInetTable."
::= { docsDevCpe 3 }
This table is deprecated and is replaced by
docsDevCpeInetTable."
::= { docsDevCpe 3 }
docsDevCpeEntry OBJECT-TYPE SYNTAX DocsDevCpeEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "An entry in the docsDevFilterCpeTable. There is one entry for each IPv4 CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored; otherwise, upon receipt of an IP packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table but docsDevCpeEnroll is set to any and the sum of the table sizes of docsDevCpeTable and docsDevCpeInetTable is less than docsDevCpeIpMax, the address is added to the table, and packet processing continues. Otherwise, the packet is dropped.
DOCSDEVCPENDTRY对象类型语法DOCSDEVCPENDTRY MAX-ACCESS不可访问状态不推荐的说明“DocsdevFiltercTable中的条目。看到或配置的每个IPv4 CPE都有一个条目。如果docsDevCpeIpMax设置为-1，则忽略此表；否则，在从CM的客户接口接收到IP数据包后，将根据此表检查源IP地址。如果地址在表中，则数据包处理将继续。如果地址不在表中，但DocsdevcPeanRoll设置为any，并且docsDevCpeTable和docsDevCpeInetTable的表大小之和小于docsDevCpeIpMax，则将地址添加到表中，并继续数据包处理。否则，数据包将被丢弃。
The filtering actions specified by this table occur
after any LLC filtering (docsDevFilterLLCTable), but
prior to any IP filtering (docsDevFilterIpTable,
docsDevNmAccessTable)."
INDEX { docsDevCpeIp }
::= {docsDevCpeTable 1 }
The filtering actions specified by this table occur
after any LLC filtering (docsDevFilterLLCTable), but
prior to any IP filtering (docsDevFilterIpTable,
docsDevNmAccessTable)."
INDEX { docsDevCpeIp }
::= {docsDevCpeTable 1 }
DocsDevCpeEntry ::= SEQUENCE {
docsDevCpeIp IpAddress,
docsDevCpeSource INTEGER,
docsDevCpeStatus RowStatus
}
DocsDevCpeEntry ::= SEQUENCE {
docsDevCpeIp IpAddress,
docsDevCpeSource INTEGER,
docsDevCpeStatus RowStatus
}
docsDevCpeIp OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "The IPv4 address to which this entry applies.
docsDevCpeIp对象类型语法IpAddress MAX-ACCESS不可访问状态不推荐的说明“此项适用的IPv4地址。
N.B. Attempts to set all zeros or all ones address values MUST be rejected."
注意：必须拒绝设置所有0或1地址值的尝试。”
::= { docsDevCpeEntry 1 }
::= { docsDevCpeEntry 1 }
docsDevCpeSource OBJECT-TYPE
SYNTAX INTEGER {
other(1),
manual(2),
learned(3)
}
docsDevCpeSource OBJECT-TYPE
SYNTAX INTEGER {
other(1),
manual(2),
learned(3)
}
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"This object describes how this entry was created. If
the value is manual(2), this row was created by a
network management action (either configuration or
SNMP set). If set to learned(3), then it was found via
looking at the source IPv4 address of a received packet.
The value other(1) is used for any entries that do not
meet manual(2) or learned(3) criteria."
::= { docsDevCpeEntry 2 }
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION
"This object describes how this entry was created. If
the value is manual(2), this row was created by a
network management action (either configuration or
SNMP set). If set to learned(3), then it was found via
looking at the source IPv4 address of a received packet.
The value other(1) is used for any entries that do not
meet manual(2) or learned(3) criteria."
::= { docsDevCpeEntry 2 }
docsDevCpeStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Standard object to manipulate rows. To create a row in
this table, one only needs to specify this object.
Management stations SHOULD use the create-and-go
mechanism for creating rows in this table."
::= { docsDevCpeEntry 3 }
docsDevCpeStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS deprecated
DESCRIPTION
"Standard object to manipulate rows. To create a row in
this table, one only needs to specify this object.
Management stations SHOULD use the create-and-go
mechanism for creating rows in this table."
::= { docsDevCpeEntry 3 }
--
-- Internet CPE Management and anti spoofing group, for support of
-- non-IPv4 CPEs.
--
--
-- Internet CPE Management and anti spoofing group, for support of
-- non-IPv4 CPEs.
--
docsDevCpeInetTable OBJECT-TYPE SYNTAX SEQUENCE OF DocsDevCpeInetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table lists the IP addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms.
docsdevcpeinetable对象类型docsdevcpeinetry的语法序列MAX-ACCESS不可访问状态当前描述“此表列出了看到（或允许）的IP地址作为来自此设备上的客户接口的数据包中的源地址。此外，此表可以通过正常的行创建机制提供CPE允许的特定地址。
N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to add learned addresses automatically.
注意：管理操作可以在此表和docsDevCpeIpTable中添加超过docsDevCpeIpMax值的条目。docsDevCpeIpMax仅限制CM自动添加学习地址的能力。
Table entries MUST NOT persist across reboots for any device.
对于任何设备，表项在重新启动期间都不能持久存在。
This table exactly mirrors docsDevCpeTable and applies
to IPv4 and IPv6 addresses."
::= { docsDevCpe 4 }
This table exactly mirrors docsDevCpeTable and applies
to IPv4 and IPv6 addresses."
::= { docsDevCpe 4 }
docsDevCpeInetEntry OBJECT-TYPE SYNTAX DocsDevCpeInetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the docsDevFilterCpeInetTable. There is one entry for each IP CPE seen or provisioned. If docsDevCpeIpMax is set to -1, this table is ignored; otherwise, upon receipt of an IP packet from the customer interface of the CM, the source IP address is checked against this table. If the address is in the table, packet processing continues. If the address is not in the table but docsDevCpeEnroll is set to any and the sum of the table sizes for docsDevCpeTable and docsDevCpeInetTable is less than docsDevCpeIpMax, the address is added to the table, and packet processing continues. Otherwise, the packet is dropped.
docsDevCpeInetEntry对象类型语法docsDevCpeInetEntry MAX-ACCESS不可访问状态当前说明“docsDevFilterCpeInetTable中的条目。看到或配置的每个IP CPE都有一个条目。如果docsDevCpeIpMax设置为-1，则忽略此表；否则，在从CM的客户接口接收到IP数据包后，将根据此表检查源IP地址。如果地址在表中，则数据包处理将继续。如果地址不在表中，但DocsdevcPeanRoll设置为any，并且docsDevCpeTable和docsDevCpeInetTable的表大小之和小于docsDevCpeIpMax，则将地址添加到表中，并继续数据包处理。否则，数据包将被丢弃。
The filtering actions specified by this table occur after any LLC filtering (docsDevFilterLLCTable), but prior to any IP filtering (docsDevFilterIpTable, docsDevNmAccessTable).
此表指定的筛选操作发生在任何LLC筛选（docsDevFilterLLCTable）之后，但在任何IP筛选（docsDevFilterIpTable、Docsdevnmaccestable）之前。
When an agent (cable modem) restarts, then all
dynamically created rows are lost."
INDEX { docsDevCpeInetType, docsDevCpeInetAddr }
::= { docsDevCpeInetTable 1 }
When an agent (cable modem) restarts, then all
dynamically created rows are lost."
INDEX { docsDevCpeInetType, docsDevCpeInetAddr }
::= { docsDevCpeInetTable 1 }
DocsDevCpeInetEntry ::= SEQUENCE {
docsDevCpeInetType InetAddressType,
docsDevCpeInetAddr InetAddress,
docsDevCpeInetSource INTEGER,
docsDevCpeInetRowStatus RowStatus
}
DocsDevCpeInetEntry ::= SEQUENCE {
docsDevCpeInetType InetAddressType,
docsDevCpeInetAddr InetAddress,
docsDevCpeInetSource INTEGER,
docsDevCpeInetRowStatus RowStatus
}
docsDevCpeInetType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The type of internet address of docsDevCpeInetAddr."
::= { docsDevCpeInetEntry 1 }
docsDevCpeInetType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The type of internet address of docsDevCpeInetAddr."
::= { docsDevCpeInetEntry 1 }
docsDevCpeInetAddr OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Internet address to which this entry applies.
docsDevCpeInetAddr对象类型语法InetAddress MAX-ACCESS不可访问状态当前描述“此条目适用的Internet地址。
Implementors need to be aware that if the size of
docsDevCpeInetAddr exceeds 114 octets OIDs of
instances of columns in this row will have more
than 128 sub-identifiers and cannot be accessed
using SNMPv1, SNMPv2c, or SNMPv3. Only unicast
address are allowed for this object."
::= { docsDevCpeInetEntry 2 }
Implementors need to be aware that if the size of
docsDevCpeInetAddr exceeds 114 octets OIDs of
instances of columns in this row will have more
than 128 sub-identifiers and cannot be accessed
using SNMPv1, SNMPv2c, or SNMPv3. Only unicast
address are allowed for this object."
::= { docsDevCpeInetEntry 2 }
docsDevCpeInetSource OBJECT-TYPE
SYNTAX INTEGER {
manual(2),
learned(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes how this entry was created. If
the value is manual(2), this row was created by a
network management action (either configuration or
SNMP set). If set to learned(3), then it was found
via looking at the source IP address of a received
packet."
::= { docsDevCpeInetEntry 3 }
docsDevCpeInetSource OBJECT-TYPE
SYNTAX INTEGER {
manual(2),
learned(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object describes how this entry was created. If
the value is manual(2), this row was created by a
network management action (either configuration or
SNMP set). If set to learned(3), then it was found
via looking at the source IP address of a received
packet."
::= { docsDevCpeInetEntry 3 }
docsDevCpeInetRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "Standard object to manipulate rows. To create a row in this table, one only needs to specify this object. Management stations SHOULD use the create-and-go mechanism for creating rows in this table."
docsDevCpeInetRowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“用于操作行的标准对象。若要在此表中创建行，只需指定此对象。管理工作站应使用create and go机制来创建此表中的行。”
::= { docsDevCpeInetEntry 4 }
::= { docsDevCpeInetEntry 4 }
-- -- Placeholder for notifications/traps. --
----通知/陷阱的占位符--
-- erroneous, DO NOT USE docsDevNotification
docsDevNotification OBJECT IDENTIFIER ::= { docsDev 2 }
-- erroneous, DO NOT USE docsDevNotification
-- erroneous, DO NOT USE docsDevNotification
docsDevNotification OBJECT IDENTIFIER ::= { docsDev 2 }
-- erroneous, DO NOT USE docsDevNotification
docsDevNotifications OBJECT IDENTIFIER ::= { docsDev 0 }
docsDevNotifications OBJECT IDENTIFIER ::= { docsDev 0 }
-- -- RFC 2669 Conformance definitions --
----RFC 2669一致性定义--
docsDevConformance OBJECT IDENTIFIER ::= { docsDev 3 }
docsDevGroups OBJECT IDENTIFIER ::= { docsDevConformance 1 }
docsDevCompliances OBJECT IDENTIFIER ::= { docsDevConformance 2 }
docsDevConformance OBJECT IDENTIFIER ::= { docsDev 3 }
docsDevGroups OBJECT IDENTIFIER ::= { docsDevConformance 1 }
docsDevCompliances OBJECT IDENTIFIER ::= { docsDevConformance 2 }
docsDevBasicCompliance MODULE-COMPLIANCE STATUS deprecated DESCRIPTION "The RFC 2669 compliance statement for MCNS/DOCSIS Cable Modems and Cable Modem Termination Systems."
docsDevBasicCompliance MODULE-COMPLIANCE STATUS不推荐使用说明“MCN/DOCSIS电缆调制解调器和电缆调制解调器终端系统的RFC 2669符合性声明”
MODULE -- docsDev
模块——docsDev
-- conditionally mandatory groups
--条件强制群
GROUP docsDevBaseGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems."
GROUP docsDevBaseGroup DESCRIPTION“在电缆调制解调器中为必填项，在电缆调制解调器终端系统中为可选项。”
GROUP docsDevEventGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems."
组文档DeveventGroup DESCRIPTION“在电缆调制解调器中必须，在电缆调制解调器终端系统中可选。”
GROUP docsDevFilterGroup DESCRIPTION "Mandatory in Cable Modems, optional in Cable Modem Termination Systems."
组文档devfiltergroup DESCRIPTION“在电缆调制解调器中必须，在电缆调制解调器终端系统中可选。”
GROUP docsDevNmAccessGroup
组docsDevNmAccessGroup
DESCRIPTION "This group is only implemented in devices that do not implement the SNMPv3 User Security Model. It SHOULD NOT be implemented by devices that conform to SNMPv3.
DESCRIPTION“此组仅在未实现SNMPv3用户安全模型的设备中实现。不应由符合SNMPv3的设备实现。
For devices that do not implement SNMPv3 or later, this group is Mandatory in Cable Modems and is optional in Cable Modem Termination Systems."
对于未实现SNMPv3或更高版本的设备，此组在电缆调制解调器中是必需的，在电缆调制解调器终端系统中是可选的。”
GROUP docsDevServerGroup DESCRIPTION "This group is implemented only in Cable Modems, and is not implemented in Cable Modem Termination Systems."
GROUP docsDevServerGroup DESCRIPTION“此组仅在电缆调制解调器中实现，而不在电缆调制解调器终端系统中实现。”
GROUP docsDevSoftwareGroup DESCRIPTION "This group is Mandatory in Cable Modems and optional in Cable Modem Termination Systems."
GROUP docsDevSoftwareGroup DESCRIPTION“此组在电缆调制解调器中是必需的，在电缆调制解调器终端系统中是可选的。”
GROUP docsDevCpeGroup DESCRIPTION "This group is Mandatory in Cable Modems, and is not implemented in Cable Modem Termination Systems."
GROUP docsDevCpeGroup DESCRIPTION“此组在电缆调制解调器中是必需的，在电缆调制解调器终端系统中不实施。”
OBJECT docsDevSTPControl MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support noStFilterBpdu(2)."
对象docsDevSTPControl MIN-ACCESS只读说明“将此对象实现为只读符合要求。设备只需支持noStFilterBpdu（2）。”
OBJECT docsDevNmAccessIp DESCRIPTION "It is compliant to recognize the IP address 255.255.255.255 as referring to any NMS."
对象docsDevNmAccessIp DESCRIPTION“将IP地址255.255.255.255识别为引用任何NMS是符合要求的。”
OBJECT docsDevEvReporting
MIN-ACCESS read-only
DESCRIPTION
"It is compliant to implement this object as read-only.
Devices need only support local(0). An agent need not
enforce that trap or syslog logging be accompanied
by local(0) or localVolatile(3) logging."
::= { docsDevCompliances 1 }
OBJECT docsDevEvReporting
MIN-ACCESS read-only
DESCRIPTION
"It is compliant to implement this object as read-only.
Devices need only support local(0). An agent need not
enforce that trap or syslog logging be accompanied
by local(0) or localVolatile(3) logging."
::= { docsDevCompliances 1 }
docsDevBaseGroup OBJECT-GROUP OBJECTS { docsDevRole, docsDevDateTime,
docsDevBaseGroup对象组对象{docsDevRole，docsDevDateTime，
docsDevResetNow,
docsDevSerialNumber,
docsDevSTPControl
}
STATUS current
DESCRIPTION
"A collection of objects providing device status and
control."
::= { docsDevGroups 1 }
docsDevResetNow,
docsDevSerialNumber,
docsDevSTPControl
}
STATUS current
DESCRIPTION
"A collection of objects providing device status and
control."
::= { docsDevGroups 1 }
docsDevNmAccessGroup OBJECT-GROUP
OBJECTS {
docsDevNmAccessIp,
docsDevNmAccessIpMask,
docsDevNmAccessCommunity,
docsDevNmAccessControl,
docsDevNmAccessInterfaces,
docsDevNmAccessStatus
}
STATUS deprecated
DESCRIPTION
"A collection of objects for controlling access to SNMP
objects on cable devices.
docsDevNmAccessGroup OBJECT-GROUP
OBJECTS {
docsDevNmAccessIp,
docsDevNmAccessIpMask,
docsDevNmAccessCommunity,
docsDevNmAccessControl,
docsDevNmAccessInterfaces,
docsDevNmAccessStatus
}
STATUS deprecated
DESCRIPTION
"A collection of objects for controlling access to SNMP
objects on cable devices.
This group has been deprecated because all the
objects have been deprecated in favor of SNMPv3 and
Coexistence MIBs."
::= { docsDevGroups 2 }
This group has been deprecated because all the
objects have been deprecated in favor of SNMPv3 and
Coexistence MIBs."
::= { docsDevGroups 2 }
docsDevSoftwareGroup OBJECT-GROUP
OBJECTS {
docsDevSwServer,
docsDevSwFilename,
docsDevSwAdminStatus,
docsDevSwOperStatus,
docsDevSwCurrentVers
}
STATUS deprecated
DESCRIPTION
"A collection of objects for controlling software
downloads.
docsDevSoftwareGroup OBJECT-GROUP
OBJECTS {
docsDevSwServer,
docsDevSwFilename,
docsDevSwAdminStatus,
docsDevSwOperStatus,
docsDevSwCurrentVers
}
STATUS deprecated
DESCRIPTION
"A collection of objects for controlling software
downloads.
This group has been deprecated and replaced by docsDevSoftwareGroupV2. Object docsDevSwServer has been replaced by docsDevSwServerAddressType and docsDevSwServerAddress, and docsDevSwServerTransportProtocol has been added to support TFTP and HTTP firmware downloads."
此组已被弃用，并由docsDevSoftwareGroupV2取代。对象DocsDevServerAddressType和DocsDevServerAddress已替换为DocsDevServerServer，并且添加了DocsDevServerTransportProtocol以支持TFTP和HTTP固件下载。”
::= { docsDevGroups 3 }
::= { docsDevGroups 3 }
docsDevServerGroup OBJECT-GROUP
OBJECTS {
docsDevServerBootState,
docsDevServerDhcp,
docsDevServerTime,
docsDevServerTftp,
docsDevServerConfigFile
}
STATUS deprecated
DESCRIPTION
"A collection of objects providing status about server
provisioning.
docsDevServerGroup OBJECT-GROUP
OBJECTS {
docsDevServerBootState,
docsDevServerDhcp,
docsDevServerTime,
docsDevServerTftp,
docsDevServerConfigFile
}
STATUS deprecated
DESCRIPTION
"A collection of objects providing status about server
provisioning.
This group has been deprecated and replaced by
docsDevServerGroupV2. The objects docsDevServerDhcp,
docsDevServerTime, and docsDevServerTftp have
been replaced by docsDevServerDhcpAddressType,
docsDevServerDhcpAddress, docsDevServerTimeAddressType,
docsDevServerTimeAddress,
docsDevServerConfigTftpAddressType, and
docsDevServerConfigTftpAddress."
::= { docsDevGroups 4 }
This group has been deprecated and replaced by
docsDevServerGroupV2. The objects docsDevServerDhcp,
docsDevServerTime, and docsDevServerTftp have
been replaced by docsDevServerDhcpAddressType,
docsDevServerDhcpAddress, docsDevServerTimeAddressType,
docsDevServerTimeAddress,
docsDevServerConfigTftpAddressType, and
docsDevServerConfigTftpAddress."
::= { docsDevGroups 4 }
docsDevEventGroup OBJECT-GROUP
OBJECTS {
docsDevEvControl,
docsDevEvSyslog,
docsDevEvThrottleAdminStatus,
docsDevEvThrottleInhibited,
docsDevEvThrottleThreshold,
docsDevEvThrottleInterval,
docsDevEvReporting,
docsDevEvFirstTime,
docsDevEvLastTime,
docsDevEvCounts,
docsDevEvLevel,
docsDevEvId,
docsDevEvText
}
STATUS deprecated
DESCRIPTION
"A collection of objects used to control and monitor
events.
docsDevEventGroup OBJECT-GROUP
OBJECTS {
docsDevEvControl,
docsDevEvSyslog,
docsDevEvThrottleAdminStatus,
docsDevEvThrottleInhibited,
docsDevEvThrottleThreshold,
docsDevEvThrottleInterval,
docsDevEvReporting,
docsDevEvFirstTime,
docsDevEvLastTime,
docsDevEvCounts,
docsDevEvLevel,
docsDevEvId,
docsDevEvText
}
STATUS deprecated
DESCRIPTION
"A collection of objects used to control and monitor
events.
This group has been deprecated and replaced by docsDevEventGroupV2. The object docsDevEvSyslog has
此组已被弃用，并由docsDevEventGroupV2替换。对象docsDevEvSyslog具有
been replaced by docsDevEvSyslogAddressType and
docsDevEvSyslogAddress, and docsDevEvThrottleInhibited
has been replaced by
docsDevEvThrottleThresholdExceeded."
::= { docsDevGroups 5 }
been replaced by docsDevEvSyslogAddressType and
docsDevEvSyslogAddress, and docsDevEvThrottleInhibited
has been replaced by
docsDevEvThrottleThresholdExceeded."
::= { docsDevGroups 5 }
docsDevFilterGroup OBJECT-GROUP
OBJECTS {
docsDevFilterLLCUnmatchedAction,
docsDevFilterIpDefault,
docsDevFilterLLCStatus,
docsDevFilterLLCIfIndex,
docsDevFilterLLCProtocolType,
docsDevFilterLLCProtocol,
docsDevFilterLLCMatches,
docsDevFilterIpControl,
docsDevFilterIpIfIndex,
docsDevFilterIpStatus,
docsDevFilterIpDirection,
docsDevFilterIpBroadcast,
docsDevFilterIpSaddr,
docsDevFilterIpSmask,
docsDevFilterIpDaddr,
docsDevFilterIpDmask,
docsDevFilterIpProtocol,
docsDevFilterIpSourcePortLow,
docsDevFilterIpSourcePortHigh,
docsDevFilterIpDestPortLow,
docsDevFilterIpDestPortHigh,
docsDevFilterIpMatches,
docsDevFilterIpTos,
docsDevFilterIpTosMask,
docsDevFilterIpContinue,
docsDevFilterIpPolicyId,
docsDevFilterPolicyId,
docsDevFilterPolicyStatus,
docsDevFilterPolicyPtr,
docsDevFilterTosStatus,
docsDevFilterTosAndMask,
docsDevFilterTosOrMask
}
STATUS deprecated
DESCRIPTION
"A collection of objects to specify filters at the link
layer and IPv4 layer.
docsDevFilterGroup OBJECT-GROUP
OBJECTS {
docsDevFilterLLCUnmatchedAction,
docsDevFilterIpDefault,
docsDevFilterLLCStatus,
docsDevFilterLLCIfIndex,
docsDevFilterLLCProtocolType,
docsDevFilterLLCProtocol,
docsDevFilterLLCMatches,
docsDevFilterIpControl,
docsDevFilterIpIfIndex,
docsDevFilterIpStatus,
docsDevFilterIpDirection,
docsDevFilterIpBroadcast,
docsDevFilterIpSaddr,
docsDevFilterIpSmask,
docsDevFilterIpDaddr,
docsDevFilterIpDmask,
docsDevFilterIpProtocol,
docsDevFilterIpSourcePortLow,
docsDevFilterIpSourcePortHigh,
docsDevFilterIpDestPortLow,
docsDevFilterIpDestPortHigh,
docsDevFilterIpMatches,
docsDevFilterIpTos,
docsDevFilterIpTosMask,
docsDevFilterIpContinue,
docsDevFilterIpPolicyId,
docsDevFilterPolicyId,
docsDevFilterPolicyStatus,
docsDevFilterPolicyPtr,
docsDevFilterTosStatus,
docsDevFilterTosAndMask,
docsDevFilterTosOrMask
}
STATUS deprecated
DESCRIPTION
"A collection of objects to specify filters at the link
layer and IPv4 layer.
This group has been deprecated and replaced by various groups from the DiffServ MIB."
此组已被弃用，并由DiffServ MIB中的各种组替换。”
::= { docsDevGroups 6 }
::= { docsDevGroups 6 }
docsDevCpeGroup OBJECT-GROUP
OBJECTS {
docsDevCpeEnroll,
docsDevCpeIpMax,
docsDevCpeSource,
docsDevCpeStatus
}
STATUS deprecated
DESCRIPTION
"A collection of objects used to control the number
and specific values of IPv4 addresses allowed for
associated Customer Premises Equipment (CPE).
docsDevCpeGroup OBJECT-GROUP
OBJECTS {
docsDevCpeEnroll,
docsDevCpeIpMax,
docsDevCpeSource,
docsDevCpeStatus
}
STATUS deprecated
DESCRIPTION
"A collection of objects used to control the number
and specific values of IPv4 addresses allowed for
associated Customer Premises Equipment (CPE).
This group has been deprecated and replaced by
docsDevInetCpeGroup. The object docsDevCpeSource has
been replaced by docsDevCpeInetSource, and
docsDevCpeStatus has been replaced by
docsDevCpeInetRowStatus."
::= { docsDevGroups 7 }
This group has been deprecated and replaced by
docsDevInetCpeGroup. The object docsDevCpeSource has
been replaced by docsDevCpeInetSource, and
docsDevCpeStatus has been replaced by
docsDevCpeInetRowStatus."
::= { docsDevGroups 7 }
-- -- RFC 4639 Conformance definitions --
----RFC 4639一致性定义--
docsDevGroupsV2 OBJECT IDENTIFIER ::= { docsDevConformance 3 }
docsDevCompliancesV2 OBJECT IDENTIFIER ::= { docsDevConformance 4 }
docsDevGroupsV2 OBJECT IDENTIFIER ::= { docsDevConformance 3 }
docsDevCompliancesV2 OBJECT IDENTIFIER ::= { docsDevConformance 4 }
docsDevCmCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for DOCSIS Cable Modems.
DOCSDVCMCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“DOCSIS电缆调制解调器的符合性声明。
This compliance statement applies to implementations of DOCSIS versions that are not IPv6 capable."
本合规性声明适用于不支持IPv6的DOCSIS版本的实施。”
MODULE DIFFSERV-MIB -- RFC 3289
模块DIFFSERV-MIB——RFC 3289
MANDATORY-GROUPS { diffServMIBDataPathGroup, diffServMIBClfrGroup, diffServMIBClfrElementGroup, diffServMIBMultiFieldClfrGroup, diffServMIBActionGroup, diffServMIBDscpMarkActGroup, diffServMIBCounterGroup, diffServMIBAlgDropGroup
必填组{diffServMIBDataPathGroup，diffServMIBClfrGroup，DiffServMibClfRementGroup，DiffServMibMultiFieldCfRgroup，diffServMIBActionGroup，DiffServMibDscMarkactGroup，diffServMIBCounterGroup，diffServMIBAlgDropGroup
}
}
OBJECT diffServDataPathStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServDataPathStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServClfrStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServClfrStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServClfrElementStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServClfrElementStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServMultiFieldClfrAddrType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象diffServMultiFieldClfrAddrType语法InetAddressType{ipv4（1）}说明“仅支持ipv4地址才需要实现。”
OBJECT diffServMultiFieldClfrSrcAddr SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象DiffServMultiFieldCfRsrCddr语法InetAddress（大小（4））说明“实现仅需要支持IPv4地址。”
OBJECT diffServMultiFieldClfrDstAddr SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象diffServMultiFieldClfrDstAddr语法InetAddress（大小（4））说明“实现仅需要支持IPv4地址。”
OBJECT diffServAlgDropStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServAlgDropStatus -- same as RFC 3289
SYNTAX RowStatus { active(1) }
WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
DESCRIPTION
"Support for createAndWait and notInService is not
required."
OBJECT diffServDataPathStorage SYNTAX StorageType { volatile(2) } DESCRIPTION "An implementation is only required to support volatile storage."
对象diffServDataPathStorage语法StorageType{volatile（2）}说明“只有支持volatile存储才需要实现。”
OBJECT diffServClfrStorage SYNTAX StorageType { volatile(2) } DESCRIPTION "An implementation is only required to support volatile storage."
对象diffServClfrStorage语法StorageType{volatile（2）}说明“仅需要实现来支持volatile存储。”
OBJECT diffServClfrElementStorage SYNTAX StorageType { volatile(2) } DESCRIPTION "An implementation is only required to support volatile storage."
对象diffServClfrElementStorage语法StorageType{volatile（2）}说明“只有支持volatile存储才需要实现。”
OBJECT diffServMultiFieldClfrStorage SYNTAX StorageType { volatile(2) } DESCRIPTION "An implementation is only required to support volatile storage."
对象diffServMultiFieldClfrStorage语法StorageType{volatile（2）}说明“仅需要实现来支持volatile存储。”
OBJECT diffServActionStorage SYNTAX StorageType { volatile(2) } DESCRIPTION "An implementation is only required to support volatile storage."
对象DiffServeActionStorage语法StorageType{volatile（2）}说明“只有支持volatile存储才需要实现。”
OBJECT diffServCountActStorage SYNTAX StorageType { volatile(2) } DESCRIPTION "An implementation is only required to support volatile storage."
对象diffServCountActStorage语法StorageType{volatile（2）}说明“只有支持volatile存储才需要实现。”
OBJECT diffServAlgDropStorage SYNTAX StorageType { volatile(2) } DESCRIPTION "An implementation is only required to support volatile storage."
对象diffServAlgDropStorage语法StorageType{volatile（2）}说明“仅需要实现来支持volatile存储。”
OBJECT diffServAlgDropType SYNTAX INTEGER { alwaysDrop(5) } DESCRIPTION "This object is only used to provide packet filtering. Implementations need not support other values of this enumeration."
对象diffServAlgDropType语法整数{alwaysDrop（5）}说明“此对象仅用于提供数据包筛选。实现不需要支持此枚举的其他值。”
MODULE -- docsDev
模块——docsDev
MANDATORY-GROUPS {
docsDevBaseGroup,
docsDevBaseIgmpGroup,
docsDevBaseMaxCpeGroup,
docsDevSoftwareGroupV2,
docsDevServerGroupV2,
docsDevEventGroupV2,
docsDevFilterLLCGroup
}
MANDATORY-GROUPS {
docsDevBaseGroup,
docsDevBaseIgmpGroup,
docsDevBaseMaxCpeGroup,
docsDevSoftwareGroupV2,
docsDevServerGroupV2,
docsDevEventGroupV2,
docsDevFilterLLCGroup
}
-- conditionally mandatory groups
--条件强制群
GROUP docsDevInetCpeGroup DESCRIPTION "This group is optional in Cable Modems."
组docsDevInetCpeGroup DESCRIPTION“此组在电缆调制解调器中是可选的。”
OBJECT docsDevDateTime MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only."
对象docsDevDateTime MIN-ACCESS只读说明“将此对象实现为只读符合要求。”
OBJECT docsDevSTPControl SYNTAX INTEGER { noStFilterBpdu(2) } MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support noStFilterBpdu(2)."
对象docsDevSTPControl语法整数{noStFilterBpdu（2）}MIN-ACCESS只读说明“将此对象实现为只读是符合的。设备只需要支持noStFilterBpdu（2）。”
OBJECT docsDevIgmpModeControl SYNTAX INTEGER { passive(1) } MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support passive(1)."
OBJECT docsDevIgmpModeControl语法整数{passive（1）}MIN-ACCESS只读说明“将此对象实现为只读是符合的。设备只需要支持passive（1）。”
OBJECT docsDevSwServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevSwServerAddressType语法InetAddressType{ipv4（1）}说明“仅支持ipv4地址才需要实现。”
OBJECT docsDevSwServerAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsdevswerserverAddress语法InetAddress（大小（4））说明“仅支持IPv4地址才需要实现。”
OBJECT docsDevServerDhcpAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevServerDhcpAddressType语法InetAddressType{ipv4（1）}说明“实现仅需要支持ipv4地址。”
OBJECT docsDevServerDhcpAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevServerDhcpAddress语法InetAddress（大小（4））说明“仅支持IPv4地址才需要实现。”
OBJECT docsDevServerTimeAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevServerTimeAddressType语法InetAddressType{ipv4（1）}说明“仅支持ipv4地址才需要实现。”
OBJECT docsDevServerTimeAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevServerTimeAddress语法InetAddress（大小（4））说明“实现仅需要支持IPv4地址。”
OBJECT docsDevServerConfigTftpAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevServerConfigTftpAddressType语法InetAddressType{ipv4（1）}说明“实现仅需要支持ipv4地址。”
OBJECT docsDevServerConfigTftpAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevServerConfigTftpAddress语法InetAddress（大小（4））说明“实现仅需要支持IPv4地址。”
OBJECT docsDevEvReporting MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support local(0)."
对象docsDevEvReporting MIN-ACCESS只读说明“将此对象实现为只读符合要求。设备只需支持本地（0）。”
OBJECT docsDevEvSyslogAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevEvSyslogAddressType语法InetAddressType{ipv4（1）}说明“实现仅需要支持ipv4地址。”
OBJECT docsDevEvSyslogAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevEvSyslogAddress语法InetAddress（大小（4））说明“实现仅需要支持IPv4地址。”
OBJECT docsDevSwServerTransportProtocol SYNTAX INTEGER { tftp(1) } DESCRIPTION "An implementation is only required to support TFTP software image downloads."
对象docsDevSwServerTransportProtocol语法整数{tftp（1）}说明“仅支持tftp软件映像下载才需要实现。”
::= { docsDevCompliancesV2 1 }
::= { docsDevCompliancesV2 1 }
docsDevCmtsCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for DOCSIS Cable Modem Termination Systems.
DOCSDVCMTS符合性模块-符合性状态当前说明“DOCSIS电缆调制解调器终端系统的符合性声明。
This compliance statement applies to implementations of DOCSIS versions that are not IPv6 capable."
本合规性声明适用于不支持IPv6的DOCSIS版本的实施。”
MODULE -- docsDev
模块——docsDev
-- conditionally mandatory groups
--条件强制群
GROUP docsDevBaseGroup DESCRIPTION "Optional in Cable Modem Termination Systems."
组docsDevBaseGroup DESCRIPTION“电缆调制解调器终端系统中可选。”
GROUP docsDevBaseIgmpGroup DESCRIPTION "Optional in Cable Modem Termination Systems."
组docsDevBaseIgmpGroup DESCRIPTION“电缆调制解调器终端系统中可选。”
GROUP docsDevBaseMaxCpeGroup DESCRIPTION "This group MUST NOT be implemented in Cable Modem Termination Systems."
组docsDevBaseMaxCpeGroup DESCRIPTION“此组不能在电缆调制解调器终端系统中实现。”
GROUP docsDevSoftwareGroupV2 DESCRIPTION "Optional in Cable Modem Termination Systems."
GROUP docsDevSoftwareGroupV2说明“电缆调制解调器终端系统中可选。”
GROUP docsDevServerGroupV2 DESCRIPTION "This group MUST NOT be implemented in Cable Modem Termination Systems."
GROUP docsDevServerGroupV2 DESCRIPTION“此组不能在电缆调制解调器终端系统中实现。”
GROUP docsDevEventGroupV2 DESCRIPTION "Optional in Cable Modem Termination Systems."
组文档DeveventGroupv2说明“电缆调制解调器终端系统中可选。”
GROUP docsDevFilterLLCGroup DESCRIPTION "This group MUST NOT be implemented in Cable Modem Termination Systems. See the Subscriber Management MIB for similar CMTS capability."
GROUP docsDevFilterLLCGroup DESCRIPTION“此组不能在电缆调制解调器终端系统中实现。有关类似的CMTS功能，请参阅订户管理MIB。”
GROUP docsDevInetCpeGroup DESCRIPTION "This group MUST NOT be implemented in Cable Modem Termination Systems. See the Subscriber Management MIB for similar CMTS capability."
组docsDevInetCpeGroup DESCRIPTION“此组不能在电缆调制解调器终端系统中实现。有关类似的CMTS功能，请参阅订户管理MIB。”
OBJECT docsDevDateTime MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only."
对象docsDevDateTime MIN-ACCESS只读说明“将此对象实现为只读符合要求。”
OBJECT docsDevSTPControl SYNTAX INTEGER { noStFilterBpdu(2) } MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support noStFilterBpdu(2)."
对象docsDevSTPControl语法整数{noStFilterBpdu（2）}MIN-ACCESS只读说明“将此对象实现为只读是符合的。设备只需要支持noStFilterBpdu（2）。”
OBJECT docsDevIgmpModeControl SYNTAX INTEGER { passive(1) } MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support passive(1)."
OBJECT docsDevIgmpModeControl语法整数{passive（1）}MIN-ACCESS只读说明“将此对象实现为只读是符合的。设备只需要支持passive（1）。”
OBJECT docsDevSwServerAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevSwServerAddressType语法InetAddressType{ipv4（1）}说明“仅支持ipv4地址才需要实现。”
OBJECT docsDevSwServerAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsdevswerserverAddress语法InetAddress（大小（4））说明“仅支持IPv4地址才需要实现。”
OBJECT docsDevEvReporting
对象docsDevEvReporting
MIN-ACCESS read-only DESCRIPTION "It is compliant to implement this object as read-only. Devices need only support local(0)."
MIN-ACCESS只读说明“将此对象实现为只读符合要求。设备只需支持本地（0）。”
OBJECT docsDevEvSyslogAddressType SYNTAX InetAddressType { ipv4(1) } DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevEvSyslogAddressType语法InetAddressType{ipv4（1）}说明“实现仅需要支持ipv4地址。”
OBJECT docsDevEvSyslogAddress SYNTAX InetAddress (SIZE(4)) DESCRIPTION "An implementation is only required to support IPv4 addresses."
对象docsDevEvSyslogAddress语法InetAddress（大小（4））说明“实现仅需要支持IPv4地址。”
OBJECT docsDevSwServerTransportProtocol SYNTAX INTEGER { tftp(1) } DESCRIPTION "An implementation is only required to support TFTP software image downloads."
对象docsDevSwServerTransportProtocol语法整数{tftp（1）}说明“仅支持tftp软件映像下载才需要实现。”
::= { docsDevCompliancesV2 2 }
::= { docsDevCompliancesV2 2 }
docsDevBaseIgmpGroup OBJECT-GROUP
OBJECTS {
docsDevIgmpModeControl
}
STATUS current
DESCRIPTION
"An object providing cable device IGMP status and
control."
::= { docsDevGroupsV2 1 }
docsDevBaseIgmpGroup OBJECT-GROUP
OBJECTS {
docsDevIgmpModeControl
}
STATUS current
DESCRIPTION
"An object providing cable device IGMP status and
control."
::= { docsDevGroupsV2 1 }
docsDevBaseMaxCpeGroup OBJECT-GROUP
OBJECTS {
docsDevMaxCpe
}
STATUS current
DESCRIPTION
"An object providing management of the maximum number of
CPEs permitted access through a cable modem."
::= { docsDevGroupsV2 2 }
docsDevBaseMaxCpeGroup OBJECT-GROUP
OBJECTS {
docsDevMaxCpe
}
STATUS current
DESCRIPTION
"An object providing management of the maximum number of
CPEs permitted access through a cable modem."
::= { docsDevGroupsV2 2 }
docsDevNmAccessExtGroup OBJECT-GROUP OBJECTS { docsDevNmAccessTrapVersion
docsdevnmaccestextgroup对象组对象{docsDevNmAccessTrapVersion
} STATUS deprecated DESCRIPTION "An object, in addition to the objects in docsDevNmAccessGroup, for controlling access to SNMP objects on cable devices.
}STATUS deprecated DESCRIPTION“除docsDevNmAccessGroup中的对象外，用于控制对电缆设备上SNMP对象的访问的对象。
This group is included in this MIB due to existing implementations of docsDevNmAccessTrapVersion in DOCSIS cable modems.
由于DOCSIS电缆调制解调器中的docsDevNmAccessTrapVersion的现有实现，该组包含在该MIB中。
This group has been deprecated because the object has
been deprecated in favor of SNMPv3 and Coexistence
MIBs."
::= { docsDevGroupsV2 3 }
This group has been deprecated because the object has
been deprecated in favor of SNMPv3 and Coexistence
MIBs."
::= { docsDevGroupsV2 3 }
docsDevSoftwareGroupV2 OBJECT-GROUP
OBJECTS {
docsDevSwFilename,
docsDevSwAdminStatus,
docsDevSwOperStatus,
docsDevSwCurrentVers,
docsDevSwServerAddressType,
docsDevSwServerAddress,
docsDevSwServerTransportProtocol
}
STATUS current
DESCRIPTION
"A collection of objects for controlling software
downloads. This group replaces docsDevSoftwareGroup."
::= { docsDevGroupsV2 4 }
docsDevSoftwareGroupV2 OBJECT-GROUP
OBJECTS {
docsDevSwFilename,
docsDevSwAdminStatus,
docsDevSwOperStatus,
docsDevSwCurrentVers,
docsDevSwServerAddressType,
docsDevSwServerAddress,
docsDevSwServerTransportProtocol
}
STATUS current
DESCRIPTION
"A collection of objects for controlling software
downloads. This group replaces docsDevSoftwareGroup."
::= { docsDevGroupsV2 4 }
docsDevServerGroupV2 OBJECT-GROUP
OBJECTS {
docsDevServerBootState,
docsDevServerDhcpAddressType,
docsDevServerDhcpAddress,
docsDevServerTimeAddressType,
docsDevServerTimeAddress,
docsDevServerConfigTftpAddressType,
docsDevServerConfigTftpAddress,
docsDevServerConfigFile
}
STATUS current
DESCRIPTION
"A collection of objects providing status about server
provisioning. This group replaces docsDevServerGroup."
::= { docsDevGroupsV2 5 }
docsDevServerGroupV2 OBJECT-GROUP
OBJECTS {
docsDevServerBootState,
docsDevServerDhcpAddressType,
docsDevServerDhcpAddress,
docsDevServerTimeAddressType,
docsDevServerTimeAddress,
docsDevServerConfigTftpAddressType,
docsDevServerConfigTftpAddress,
docsDevServerConfigFile
}
STATUS current
DESCRIPTION
"A collection of objects providing status about server
provisioning. This group replaces docsDevServerGroup."
::= { docsDevGroupsV2 5 }
docsDevEventGroupV2 OBJECT-GROUP
OBJECTS {
docsDevEvControl,
docsDevEvThrottleAdminStatus,
docsDevEvThrottleThreshold,
docsDevEvThrottleInterval,
docsDevEvReporting,
docsDevEvFirstTime,
docsDevEvLastTime,
docsDevEvCounts,
docsDevEvLevel,
docsDevEvId,
docsDevEvText,
docsDevEvSyslogAddressType,
docsDevEvSyslogAddress,
docsDevEvThrottleThresholdExceeded
}
STATUS current
DESCRIPTION
"A collection of objects used to control and monitor
events. This group replaces docsDevEventGroup.
The event reporting mechanism, and more specifically
docsDevEvReporting, can be used to take advantage of
the event reporting features of RFC3413 and RFC3014."
::= { docsDevGroupsV2 6 }
docsDevEventGroupV2 OBJECT-GROUP
OBJECTS {
docsDevEvControl,
docsDevEvThrottleAdminStatus,
docsDevEvThrottleThreshold,
docsDevEvThrottleInterval,
docsDevEvReporting,
docsDevEvFirstTime,
docsDevEvLastTime,
docsDevEvCounts,
docsDevEvLevel,
docsDevEvId,
docsDevEvText,
docsDevEvSyslogAddressType,
docsDevEvSyslogAddress,
docsDevEvThrottleThresholdExceeded
}
STATUS current
DESCRIPTION
"A collection of objects used to control and monitor
events. This group replaces docsDevEventGroup.
The event reporting mechanism, and more specifically
docsDevEvReporting, can be used to take advantage of
the event reporting features of RFC3413 and RFC3014."
::= { docsDevGroupsV2 6 }
docsDevFilterLLCGroup OBJECT-GROUP
OBJECTS {
docsDevFilterLLCUnmatchedAction,
docsDevFilterLLCStatus,
docsDevFilterLLCIfIndex,
docsDevFilterLLCProtocolType,
docsDevFilterLLCProtocol,
docsDevFilterLLCMatches
}
STATUS current
DESCRIPTION
"A collection of objects to specify link layer filters."
::= { docsDevGroupsV2 7 }
docsDevFilterLLCGroup OBJECT-GROUP
OBJECTS {
docsDevFilterLLCUnmatchedAction,
docsDevFilterLLCStatus,
docsDevFilterLLCIfIndex,
docsDevFilterLLCProtocolType,
docsDevFilterLLCProtocol,
docsDevFilterLLCMatches
}
STATUS current
DESCRIPTION
"A collection of objects to specify link layer filters."
::= { docsDevGroupsV2 7 }
docsDevInetCpeGroup OBJECT-GROUP
OBJECTS {
docsDevCpeEnroll,
docsDevCpeIpMax,
docsDevCpeInetSource,
docsDevCpeInetRowStatus
}
STATUS current
docsDevInetCpeGroup OBJECT-GROUP
OBJECTS {
docsDevCpeEnroll,
docsDevCpeIpMax,
docsDevCpeInetSource,
docsDevCpeInetRowStatus
}
STATUS current
DESCRIPTION
"A collection of objects used to control the number
and specific values of Internet (e.g., IPv4 and IPv6)
addresses allowed for associated Customer Premises
Equipment (CPE)."
::= { docsDevGroupsV2 8 }
DESCRIPTION
"A collection of objects used to control the number
and specific values of Internet (e.g., IPv4 and IPv6)
addresses allowed for associated Customer Premises
Equipment (CPE)."
::= { docsDevGroupsV2 8 }
END
终止
This document is a production of the IPCDN Working Group and is a revision of RFC 2669, "Cable Device Management Information Base for DOCSIS-Compliant Cable Modems and Cable Modem Termination Systems" [RFC2669]. Mike St. Johns and Guenter Roeck served well as the editors of previous versions of this MIB module.
本文件是IPCDN工作组的成果，是RFC 2669“符合DOCSIS标准的电缆调制解调器和电缆调制解调器终端系统的电缆设备管理信息库”[RFC2669]的修订版。Mike St.Johns和Guenter Roeck担任此MIB模块早期版本的编辑。
The editor specifically wishes to thank Howard Abramson, Eduardo Cardona, Andre Lejeune, Kevin Marez, Jean-Francois Mule, Greg Nakanishi, Pak Siripunkaw, Boris Tsekinovski, Randy Presuhn, Bert Wijnen, and Bill Yost for their contributions to this document.
编辑特别感谢霍华德·艾布拉姆森、爱德华多·卡多纳、安德烈·勒琼、凯文·马雷斯、让·弗朗索瓦·穆勒、格雷格·纳卡尼希、帕克·西里蓬考、鲍里斯·茨基诺夫斯基、兰迪·普雷森、伯特·维恩和比尔·约斯特对本文件的贡献。
This document contains the following revisions over RFC 2669:
本文件包含对RFC 2669的以下修订：
o All IPv4 address objects were either deprecated and replaced or mirrored with IPv6 objects, where appropriate, following the guidelines of RFC 4001 [RFC4001]. In particular, docsDevCpeInetTable was added, and the docsDevFilterGroup objects were deprecated in favor of the DiffServ MIB.
o 根据RFC 4001[RFC4001]的指导原则，所有IPv4地址对象都已弃用，并在适当情况下被替换或镜像为IPv6对象。特别是，添加了docsdevcpeinetable，并且不推荐使用docsDevFilterGroup对象，而支持DiffServ MIB。
o Objects that were obviated by SNMPv3 and the SNMP Coexistence MIBs have been deprecated; e.g., docsDevNmAccessTable.
o SNMPv3和SNMP共存MIB排除的对象已被弃用；e、 g.，Docsdevnmaccestable。
o A new object, docsDevIgmpModeControl, has been added to control passive versus active IGMP modem operation.
o 添加了一个新对象docsDevIgmpModeControl，用于控制被动与主动IGMP调制解调器的操作。
o A new object, docsDevMaxCpe, has been added to report the maximum number of CPEs granted network access across the CM.
o 添加了一个新对象docsDevMaxCpe，以报告在CM中允许网络访问的最大CPE数。
o A new object, docsDevSwServerTransportProtocol, has been added to docsDevSoftware, and other object DESCRIPTIONs have been modified, to enable the use of either TFTP or HTTP for software downloads to the device.
o docsDevSwServerTransportProtocol是一个新对象，已添加到docsDevSoftware中，并修改了其他对象描述，以允许使用TFTP或HTTP将软件下载到设备。
o A new object, docsDevEvThrottleThresholdExceeded, has been added to replace docsDevEvThrottleInhibited for simplification of event threshold management.
o 添加了一个新对象docsDevEvThrottleThresholdExceeded，以替换docsDevEvThrottleInhibited，以简化事件阈值管理。
o The docsDevEvReporting object has been modified to enable local logging to the internal volatile log, and not to the internal non-volatile log.
o docsDevEvReporting对象已修改为允许本地记录到内部易失性日志，而不是内部非易失性日志。
o Minor updates to the description text have been made to a number of objects to clarify their meaning.
o 对一些对象的描述文本进行了微小的更新，以澄清其含义。
o The compliance statements were updated to reflect current requirements (including making the docsDevCpe objects optional) and split between CM and CMTS devices.
o 合规性声明已更新，以反映当前的要求（包括使docsDevCpe对象成为可选对象），并在CM和CMTS设备之间进行拆分。
o Text was added to indicate support of the SNMP Notification MIB [RFC3413] and Notification Log MIB [RFC3014] modules.
o 添加的文本表示支持SNMP通知MIB[RFC3413]和通知日志MIB[RFC3014]模块。
This MIB module relates to a system that will provide metropolitan public internet access. As such, improper manipulation of the objects represented by this MIB module may result in denial of service to a large number of end-users. In addition, manipulation of docsDevNmAccessTable, docsDevFilterLLCTable, docsDevFilterIpTable, docsDevFilterInetTable, and the elements of the docsDevCpe and docsDevCpeInetTable groups may allow an end-user to increase his or her service levels, spoof his or her IP addresses, change the permitted management stations, or affect other end-users in either a positive or negative manner.
该MIB模块与提供城域公共互联网接入的系统相关。因此，对该MIB模块表示的对象的不当操作可能会导致大量最终用户拒绝服务。此外，操纵DocsdevMacAccessTable、DocsdevFilterlTable、docsDevFilterIpTable、DocsdevFilterNetTable以及docsDevCpe和DocsdevcPeineTable组的元素可能会允许最终用户提高其服务级别、伪造其IP地址、更改允许的管理站，或以积极或消极的方式影响其他最终用户。
It is recommended that the implementors prevent the "tiny fragment" and "overlapping fragment" attacks for the IP filtering tables in this MIB module, as discussed in [RFC1858] and [RFC3128]. Prevention of these attacks can be implemented with the following rules, when TCP source and/or destination port filtering is enabled:
如[RFC1858]和[RFC3128]中所述，建议实施者防止此MIB模块中IP筛选表的“微小片段”和“重叠片段”攻击。启用TCP源和/或目标端口筛选时，可以使用以下规则来防止这些攻击：
o Admit all packets with fragment offset >= 2.
o 允许碎片偏移量>=2的所有数据包。
o Discard all packets with fragment offset = 1, or with fragment offset = 0 AND fragment payload length < 16.
o 丢弃片段偏移量=1或片段偏移量=0且片段有效负载长度<16的所有数据包。
o Apply filtering rules to all packets with fragment offset = 0.
o 将筛选规则应用于片段偏移量为0的所有数据包。
This MIB module does not affect confidentiality of services on a cable modem system. [BPI] and [BPIPLUS] specify the implementation of the DOCSIS Baseline Privacy and Baseline Privacy Plus mechanisms for data transmission confidentiality.
此MIB模块不会影响电缆调制解调器系统上服务的机密性。[BPI]和[BPIPLUS]规定了DOCSIS基线隐私和基线隐私加数据传输保密机制的实施。
There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o The use of docsDevNmAccessTable to specify management stations is considered only limited protection and does not protect against attacks that spoof the management station's IP address. The use of stronger mechanisms, such as SNMPv3 security, should be considered, where possible. Specifically, SNMPv3 USM [RFC3414] and VACM [RFC3415] MUST be used with any v3 agent that implements this MIB module.
o 使用docsdevnmaccestable指定管理站仅被视为有限保护，不能防止欺骗管理站IP地址的攻击。在可能的情况下，应考虑使用更强大的机制，如SNMPv3安全性。具体而言，SNMPv3 USM[RFC3414]和VACM[RFC3415]必须与实现此MIB模块的任何v3代理一起使用。
o The CM may have its software changed by the actions of the management system using a combination of the following objects: docsDevSwServer, docsDevSwFilename, docsDevSwAdminStatus, docsDevSwServerAddressType, docsDevSwServerAddress, and docsDevSwServerTransportProtocol. An improper software download may result in substantial vulnerabilities and the loss of the ability of the management system to control the cable modem. A cable device SHOULD implement the code verification mechanisms of [BPIPLUS] to verify the source and integrity of downloaded software images.
o CM可能会通过管理系统的操作，使用以下对象的组合来更改其软件：docsDevSwServer、docsDevSwFilename、docsDevSwAdminStatus、docsDevSwServerAddressType、docsDevSwServerAddress和docsDevSwServerTransportProtocol。不正确的软件下载可能会导致严重的漏洞，并使管理系统失去控制电缆调制解调器的能力。电缆设备应实现[BPIPLUS]的代码验证机制，以验证下载的软件映像的源代码和完整性。
o The device may be reset by setting docsDevResetNow = true(1). This causes the device to reload its configuration files, as well as to eliminate all previous non-persistent network management settings. As such, this may provide a vector for attacking the system.
o 可通过设置DOCSDVRESETNOW=true（1）重置设备。这会导致设备重新加载其配置文件，并消除所有以前的非持久性网络管理设置。因此，这可能提供攻击系统的向量。
o Setting docsDevEvThrottleAdminStatus = unconstrained(1) (which is also the DEFVAL) may cause flooding of traps, which can disrupt network service. Additionally, docsDevThrottleThreshold and docsDevThrottleInterval could also be set to high values that may cause a disruption in service.
o 设置docsDevEvThrottleAdminStatus=unconstraint（1）（这也是deffal）可能会导致陷阱泛滥，从而中断网络服务。此外，docsDevThrottleThreshold和docsDevThrottleInterval也可以设置为可能导致服务中断的高值。
o Setting docsDevDateTime to an arbitrary (incorrect) value would merely cause the device to record incorrect timestamps on many events/actions that rely on this object for reporting.
o 将docsDevDateTime设置为任意（不正确）值只会导致设备在依赖此对象进行报告的许多事件/操作上记录不正确的时间戳。
o Setting docsDevEvControl to resetLog(1) will delete any event log history and could potentially impact debugging/troubleshooting efforts.
o 将docsDevEvControl设置为resetLog（1）将删除任何事件日志历史记录，并可能影响调试/故障排除工作。
o Setting docsDevEvSyslog.
o 正在设置docsDevEvSyslog。
o Setting docsDevEvReporting to enable syslog reporting, along with a redirect of the syslog server could allow access to sensitive information on network devices. Modifying docsDevEvSyslog, docsDevEvSyslogAddressType, or docsDevEvSyslogAddress could allow a redirect of sensitive information.
o 将docsDevEvReporting设置为启用系统日志报告，并重定向系统日志服务器，可允许访问网络设备上的敏感信息。修改docsDevEvSyslog、docsDevEvSyslogAddress类型或docsDevEvSyslogAddress可能允许重定向敏感信息。
o Setting docsDevFilterLLCnmatchedAction or docsDevFilterIpDefault could cause significant changes to default traffic filtering on a device.
o 设置docsdevfilterlcnmatchedaction或docsDevFilterIpDefault可能会对设备上的默认流量过滤造成重大更改。
o Setting docsDevCpeEnroll to any(2) could cause the docsDevFilterCPETable to be populated, which may not be the intended functionality.
o 将DocsdevcPenderRoll设置为任意（2）可能会导致填充DocsdevFiltercTable，这可能不是预期的功能。
o Setting docsDevCpeIpMax to a value other than that intended by the MSO may allow a user to provision more devices than the MSO would like.
o 将docsDevCpeIpMax设置为MSO预期之外的值可能会允许用户提供超出MSO希望的更多设备。
o Setting values in the docsDevNmAccess table can potentially introduce a mechanism for users to use a local NMS device and manipulate other settings in the CM or CMTS.
o DOCSDEVNMACESS表中的设置值可能会引入一种机制，供用户使用本地NMS设备并操作CM或CMT中的其他设置。
o Setting values in the docsDevFilterLLC and docsDevFilterIP tables can allow or deny access to certain devices that the MSO does not want.
o 在docsDevFilterLLC和docsDevFilterIP表中设置值可以允许或拒绝访问MSO不需要的某些设备。
o Setting docsDevCpeStatus and docsDevCpeInetRowStatus may allow users to provision more devices than were intended by the MSO, or to provision different ones.
o 设置DOCSDEVCPESTETUS和docsDevCpeInetRowStatus可能允许用户提供超过MSO预期的设备，或提供不同的设备。
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 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通过网络发送这些对象时，控制甚至访问这些对象，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o Rows from docsDevNmAccessTable may provide sufficient information for attackers to spoof management stations that have management access to the device.
o Docsdevnmaccestable中的行可能为攻击者提供足够的信息，以欺骗具有设备管理访问权限的管理站。
o The docsDevSwCurrentVers object may provide hints as to the software vulnerabilities of the cable device.
o docsDevSwCurrentVers对象可能会提供有关电缆设备软件漏洞的提示。
o The docsDevFilterLLCTable and docsDevFilterLLCTable may provide clues for attacking the cable device and other subscriber devices.
o docsDevFilterLLCTable和docsDevFilterLLCTable可能提供攻击有线设备和其他用户设备的线索。
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 indeed GET or SET (change/create/delete) them.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商有责任确保授予访问此MIB模块实例权限的SNMP实体正确配置为仅授予那些拥有合法权限来获取或设置（更改/创建/删除）对象的主体（用户）访问对象的权限。
The MIB module defined in this document uses the following IANA-assigned OBJECT IDENTIFIER values, recorded in the SMI Numbers registry:
本文档中定义的MIB模块使用以下IANA分配的对象标识符值，记录在SMI编号注册表中：
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
docsDevMIB { mib-2 69 }
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
docsDevMIB { mib-2 69 }
[BPI] SCTE Data Standards Subcommittee, "Data-Over-Cable Service Interface Specifications: DOCSIS 1.0 Baseline Privacy Interface Specification SCTE 22-2 2002", 2002, <http://www.scte.org/standards/>.
[BPI]SCTE数据标准小组委员会，“有线数据服务接口规范：DOCSIS 1.0基线隐私接口规范SCTE 22-2 2002”，2002年<http://www.scte.org/standards/>.
[BPIPLUS] CableLabs, "Data-Over-Cable Service Interface Specifications: Baseline Privacy Plus Interface Specification CM-SP-BPI+_I12-050812", August 2005, <http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[BPIPLUS]CableLabs，“有线数据服务接口规范：基线隐私加接口规范CM-SP-BPI+_I12-050812”，2005年8月<http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[ITU-T_J.112] ITU-T Recommendation J.112 (3/98), "Transmission Systems for Interactive Cable Television Services, J.112, International Telecommunications Union", March 1998, <http://www.itu.int/ITU-T/studygroups/com09/>.
[ITU-T_J.112]ITU-T建议J.112（3/98），“交互式有线电视服务的传输系统，J.112，国际电信联盟”，1998年3月<http://www.itu.int/ITU-T/studygroups/com09/>.
[MTA-PROV] CableLabs, "PacketCable(TM) 1.5 Specification: MTA Device Provisioning PKT-SP-PROV1.5-I02-050812", August 2005, <http://www.packetcable.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[MTA-PROV]CableLabs，“PacketCable（TM）1.5规范：MTA设备供应PKT-SP-PROV1.5-I02-050812”，2005年8月<http://www.packetcable.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[OSSI1.0] SCTE Data Standards Subcommittee, "Data-Over-Cable Service Interface Specification: DOCSIS 1.0 Operations Support System Interface (OSSI), SCTE 22-3 2002", 2002, <http://www.scte.org/standards/>.
[OSSI1.0]SCTE数据标准小组委员会，“有线数据服务接口规范：DOCSIS 1.0操作支持系统接口（OSSI）”，SCTE 22-3 2002<http://www.scte.org/standards/>.
[OSSI1.1] SCTE Data Standards Subcommittee, "DOCSIS 1.1 Part 3: Operations Support System Interface ANSI/SCTE 23-3 2005", 2005, <http://www.scte.org/standards/>.
[1.1]SCTE数据标准小组委员会，“DOCSIS 1.1第3部分：操作支持系统接口ANSI/SCTE 23-3 2005”，2005年<http://www.scte.org/standards/>.
[OSSI2.0] CableLabs, "Data-Over-Cable Service Interface Specifications: Operations Support System Interface Specification SP-OSSIv2.0-I09-050812", August 2005, <http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[OSSI2.0]CableLabs，“有线数据服务接口规范：运营支持系统接口规范SP-OSSIv2.0-I09-050812”，2005年8月<http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[RFC1350] Sollins, K., "The TFTP Protocol (Revision 2)", STD 33, RFC 1350, July 1992.
[RFC1350]Sollins，K.，“TFTP协议（修订版2）”，STD 33，RFC 1350，1992年7月。
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2", RFC 4502, May 2006.
[RFC4502]Waldbusser，S.，“远程网络监控管理信息库版本2”，RFC4502，2006年5月。
[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", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2616]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2616，1999年6月。
[RFC2669] St. Johns, M., "DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems", RFC 2669, August 1999.
[RFC2669]圣约翰，M.，“符合DOCSIS标准的电缆调制解调器和电缆调制解调器终端系统的DOCSIS电缆设备MIB电缆设备管理信息库”，RFC 2669，1999年8月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3014] Kavasseri, R., "Notification Log MIB", RFC 3014, November 2000.
[RFC3014]Kavasseri，R.，“通知日志MIB”，RFC30142000年11月。
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, May 2002.
[RFC3289]Baker，F.，Chan，K.和A.Smith，“差异化服务体系结构的管理信息库”，RFC 3289，2002年5月。
[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月。
[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月。
[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.，Presuhn，R.，和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，STD 62，RFC 3415，2002年12月。
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the Simple Network Management Protocol (SNMP)", STD 62, RFC 3418, December 2002.
[RFC3418]Presohn，R.，“简单网络管理协议（SNMP）的管理信息库（MIB）”，STD 62，RFC 3418，2002年12月。
[RFC3584] Frye, R., Levi, D., Routhier, S., and B. Wijnen, "Coexistence between Version 1, Version 2, and Version 3 of the Internet-standard Network Management Framework", BCP 74, RFC 3584, August 2003.
[RFC3584]Frye，R.，Levi，D.，Routhier，S.，和B.Wijnen，“互联网标准网络管理框架版本1，版本2和版本3之间的共存”，BCP 74，RFC 3584，2003年8月。
[RFC868] Postel, J. and K. Harrenstien, "Time Protocol", STD 26, RFC 868, May 1983.
[RFC868]Postel，J.和K.Harrenstien，“时间协议”，STD 26，RFC 868，1983年5月。
[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月。
[RFI1.0] SCTE Data Standards Subcommittee, "Data-Over-Cable Service Interface Specifications: DOCSIS 1.0 Radio Frequency Interface Specification SCTE 22-1 2002", 2002, <http://www.scte.org/standards/>.
[RFI1.0]SCTE数据标准小组委员会，“电缆数据服务接口规范：DOCSIS 1.0射频接口规范SCTE 22-1 2002”，2002年<http://www.scte.org/standards/>.
[RFI1.1] SCTE Data Standards Subcommittee, "DOCSIS 1.1 Part 1: Radio Frequency Interface ANSI/SCTE 23-1 2005", 2005, <http://www.scte.org/standards/>.
[RFI1.1]SCTE数据标准小组委员会，“DOCSIS 1.1第1部分：射频接口ANSI/SCTE 23-1 2005”，2005年<http://www.scte.org/standards/>.
[RFI2.0] CableLabs, "Data-Over-Cable Service Interface Specifications: Radio Frequency Interface Specification SP-RFI2.0-I11-060602", June 2006, <http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[RFI2.0]CableLabs，“电缆数据服务接口规范：射频接口规范SP-RFI2.0-I11-060602”，2006年6月<http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[RFC1858] Ziemba, G., Reed, D., and P. Traina, "Security Considerations r IP Fragment Filtering", RFC 1858, October 1995.
[RFC1858]Ziemba，G.，Reed，D.，和P.Trana，“IP片段过滤的安全考虑”，RFC 1858，1995年10月。
[RFC1945] Berners-Lee, T., Fielding, R., and H. Frystyk, "Hypertext Traner Protocol -- HTTP/1.0", RFC 1945, May 1996.
[RFC1945]Berners Lee，T.，Fielding，R.，和H.Frystyk，“超文本传输协议——HTTP/1.0”，RFC 1945，1996年5月。
[RFC3128] Miller, I., "Protection Against a Variant of the Tiny Fragment Attack (RFC 1858)", RFC 3128, June 2001.
[RFC3128]Miller，I.，“防止微小碎片攻击的变体（RFC 1858）”，RFC 31281001年6月。
[RFC3164] Lonvick, C., "The BSD Syslog Protocol", RFC 3164, August 2001.
[RFC3164]Lonvick，C.，“BSD系统日志协议”，RFC31642001年8月。
[RFC3617] Lear, E., "Uniform Resource Identifier (URI) Scheme and Applicbility Statement for the Trivial File Transfer Protocol (TFTP)", RFC 3617, October 2003.
[RFC3617]李尔，E.“普通文件传输协议（TFTP）的统一资源标识符（URI）方案和适用性声明”，RFC3617，2003年10月。
[RFC4547] Ahmad, A. and G. Nakanishi, "Event Notification Management Information Base for Data over Cable Service Interface Specifications (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems", RFC 4547, June 2006.
[RFC4547]Ahmad，A.和G.Nakanishi，“符合电缆服务接口规范（DOCSIS）的电缆调制解调器和电缆调制解调器终端系统的事件通知管理信息库”，RFC 4547，2006年6月。
[RFC1224] Steinberg, L., "Techniques for managing asynchronously generated alerts", RFC 1224, May 1991.
[RFC1224]Steinberg，L.“管理异步生成警报的技术”，RFC1224，1991年5月。
[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月。
[RFC4036] Sawyer, W., "Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management", RFC 4036, April 2005.
[RFC4036]Sawyer，W.“用户管理用电缆数据服务接口规范（DOCSIS）电缆调制解调器终端系统的管理信息库”，RFC 4036，2005年4月。
[RFC4323] Patrick, M. and W. Murwin, "Data Over Cable System Interface Specification Quality of Service Management Information Base (DOCSIS-QoS MIB)", RFC 4323, January 2006.
[RFC4323]Patrick，M.和W.Murwin，“电缆系统接口数据规范服务质量管理信息库（DOCSIS QoS MIB）”，RFC 43232006年1月。
[MULPI3.0] CableLabs, "Data-Over-Cable Service Interface Specifications: DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification CM-SP-MULPIv3.0-I01- 060804", August 2006, <http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
[MULPI3.0]CableLabs，“有线数据服务接口规范：DOCSIS 3.0 MAC和上层协议接口规范CM-SP-MULPIv3.0-I01-060804”，2006年8月<http://www.cablemodem.com/specifications/>, <http://www.cablelabs.com/specifications/archives/>.
Authors' Addresses
作者地址
Richard Woundy Comcast Cable 27 Industrial Avenue Chelmsford, MA 01824 USA
Richard Woundy Comcast电缆美国马萨诸塞州切姆斯福德工业大道27号01824
Phone: +1 978 244 4010
EMail: richard_woundy@cable.comcast.com
Phone: +1 978 244 4010
EMail: richard_woundy@cable.comcast.com
Kevin Marez Motorola Corporation 6450 Sequence Drive San Diego, CA 92121 USA
Kevin Marez摩托罗拉公司6450 Sequence Drive美国加利福尼亚州圣地亚哥92121
Phone: +1 858 404 3785
EMail: kevin.marez@motorola.com
Phone: +1 858 404 3785
EMail: kevin.marez@motorola.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST, AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。