DOCSIS terms: Errored Second: Any 1 second interval containing at least one bit error. Extended Subsplit: A frequency division scheme that allows bidirectional traffic on a single coaxial cable. Reverse path signals come to the head-end from 5 to 42 MHz. Forward path signals go from the head-end from 50 to 54 MHz to the upper frequency limit. High Frequency: Refers to the entire subsplit (5 - 30 MHz) and extended subsplit (5 - 42 MHz) band used in reverse channel communications over the cable television network. Micro-reflections: Echoes in the forward transmission path due to departures from ideal amplitude and phase characteristics. Mini-slot: An integer multiple of 6.25-microsecond increments. MSO: Multiple System Operator Quadrative Amplitude Modulation (QAM): A method of modulating digital signals onto a radio-frequency carrier signal involving both amplitude and phase coding. Quadrature Phase-Shift Keying (QPSK): A method of modulating digital signals onto a radio-frequency carrier signal using four phase states to code two digital bits. Service Flow: A MAC layer transport service which: (X) Provides unidirectional transport of packets from the upper layer service entity to the RF; (X) Shapes, polices, and prioritizes traffic according to QoS traffic parameters defined for the Flow. System Clock Period: The period of the 10.24 MHz system clock, nominally 97.65625 ns. ------------------------------------------------------------------------------------------------------------------------------ The SNMPv3 protocol has been selected as the communication protocol for management of data-over-cable services and _MUST_ be implemented. Although SNMPv3 offers advantages, many management systems may not be capable of supporting SNMPv3 agents; therefore, support for SNMPv1 and SNMPv2c is also required and _MUST_ be implemented. The cable modem _MUST_ provide read-only access to the following MIB objects: (X) docsIfDownChannelFrequency (X) docsIfDownChannelPower (X) docsIfCmStatusValue (X) docsDevServerBootState (x) docsDevEventTable The cable modem _MAY_ provide read-only access to the following MIB objects: (X) sysDescr (X) sysUptime (X) ifTable (X) ifXtable (X) docsIfUpChannelFrequency (X) docsIfSigQSignalQualityTable (X) docsIfCmCmtsAddress (X) docsIfCmStatusTxPower (X) docsDevSwCurrentVers The cable modem _MUST NOT_ reveal: (X) CoS and QoS service flow information (X) configuration file contents (X) Secure Software Download information (X) Key authentication and encryption material (X) SNMP management and control (X) DOCSIS functional module statistics and configuration (X) Network provisioning hosts and servers IP addresses The cable modem _MUST_ include at least the hardware version, Boot ROM image version, vendor name, software version, and model number in the sysDescr object (from RFC 3418). The CM _MUST_ support docsDevSwCurrentVers MIB object and the object _MUST_ contain the same softawre revision information as shows in the software information included in the sysDescr object. The format of the specific information contained in the sysDescr _MUST_ be as follows: Hardware Version: HW_REV: Vendor Name: VENDOR: Boot ROM: BOOTR: Software Version: SW_REV: Model Number: MODEL: 7.3 Protocol Filters: The CM _MUST_ implement LLC, SNMP Access, 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, IPX, NetBIOS, and AppleTalk). The IP protocol filter entries can be used to restrict upstream or downstream traffic based on source and destination IP addresses, transport-layer protocols (such as TCP, UDP, and ICMP), and source and destination TCP/UDP port numbers. 7.3.5 IP Filter The object docsDevFilterIPDefault _MUST_ apply to all CM interfaces. DOCSIS 2.0-compliant CMs _MUST_ support a MINIMUM of 16 IP filters. 7.4.2.1 Local Event Logging A CM _MUST_ maintain local log events in both local-volatile storage and local non-volatile storage. A CMTS _MUST_ maintain local-log events in local-volatile storage or local non-volatile storage or both. The cable device event log _MUST_ be organized as a cyclic buffer with a MINIMUM of ten (10) entries, and _MAY_ persist across reboots. The event log table _MUST_ be accessible through the docsDevEventTable [RFC 2669] by the cable device (CM or CMTS). Event recording must conform to the requirements of [RFC 2669]. Event descriptions must appear in English and must not be longer than 255 characters, which is the maximum defined for SnmpAdminString. Events are identical if their EventIds are identical. For identical events occurring consecutively, the CM _MAY_ choose to store only a single event. In such a case, the event description recorded _MUST_ reflect the most recent event. The EventId digit is a 32-bit unsigned integer. EventIds ranging from 0 to (2^31 - 1) are reserved by DOCSIS. The EventIds ranging from 2^31 to (2^32 - 1) _MUST_ be used as vendor-specific EventIds using the following format: (X) Bit 31 is set to indicate vendor-specific event (X) Bits 30 - 16 contain the lower 15 bits of the vendor's SNMP enterprise number (X) Bits 15 - 0 are used by the vendor to number events. 7.6 Coexistance When a DOCSIS 2.0-compliant CM is connected to a 2.0 CMTS, it can operate in DOCSIS 2.0, 1.1, or 1.0 mode. When a DOCSIS 2.0-compliant CM is connected to a 1.1 CMTS, it can operate in DOCSIS 1.1 or 1.0 mode. When a DOCSIS 2.0-compliant CM is connected to a 1.0 CMTS, it operate in DOCSIS 1.0 mode. 9.1 SNMP Access via CMCI SNMP access from the CMCI before and after completing the CMTS registration process, _MUST_ comply with the access requirements specified in Section 5.2. The CM _MUST_ support SNMP access through the following IP addresses: (X) The CM DHCP-acquired IP _MUST_ accept an SNMP request from CMCI only after completing registration. (X) The CM _MUST_ support 192.168.100.1 as the well-known diagnostic IP address accessible only from the CMCI interfaces regardless of the registration state. The well-known diagnostic IP address, 192.168.100.1, _MUST_ be supported on all physical interfaces associated with the CMCI (e.g., USB, 10BaseT, etc). SNMP requests coming from the CATV interface targeting the well-known IP _MUST_ be DROPPED by the CM. 9.2 Console Access An exteranl cable modem _MUST NOT_ allow access to the CM functions via a console port. In this specification, a console port is defined as a communication path, either hardware or software, that allows a user to issue commands to modify the configuration or operational status of the CM. Access to the external CM _MUST_ only be allowed using DOCSIS 2.0-defined RF interfaces and operator-controlled SNMP access via the CMCI. 9.3 CM Diagnostic Capabilities The CM _MAY_ have a diagnostic interface for debugging and troubleshooting purposes. The interface _MUST_ be limited by default to the requirements described in Section 5.2 a) before and after registration, and _SHOULD_ be disabled by default after registration has been completed. Additional controls _MAY_ be provided that will enable the MSO to alter or customize the diagnostic interface, such as via the configuration process or alter management by the MSO through the setting of a proprietary MIB. 9.4 Protocol Filtering The CM _MUST_ be capable of filtering all broadcast traffic from the host CPE, with the exception of DHCP and ARP packets. This filtering function must adhere to Section 7.3. All ICMP type packets _MUST_ be forwarded from the CMCI interface to the RF upstream interface. The CMCI _MUST_ also adhere to the data forwarding rules defined in [DOCSIS 5]. 10 CM Operational Status Visualization DOCSIS 2.0-compliant CM is _RECOMMENDED_ to support a standard front-panel LEDs that presents straightforward information about the registration state of the CM to facilitate efficient customer support operations. 10.1 CM LEDs Requirements and Operation The LEDs on a DOCSIS 2.0 compliant CM _SHOULD_ have three states; 1) unlit, 2) flash, 3) lit solid. A 'flash' LED _SHOULD_ turn on and off with a 50% duty cycle at a frequency not less than 2 cycles per second. The LEDs will light sequentially, following the normal CM boot-up procedure, as specified in the DOCSIS RF1 specification. In this way, the installer can detect a failure that prevents the CM from becoming operational. DOCSIS 2.0 compliant CMs are _RECOMMENDED_ to have a minimum of five LEDs visible on the outside case divided into three functional groups: (X) BOX: It _SHOULD_ have 1 LED labelled as POWER. (X) DOCSIS: This group has LEDs for the DOCSIS interface. It _SHOULD_ have 3 LEDs labelled as DS, US, and ONLINE. (X) CPE: The group has the LINK LED indication. It _SHOULD_ have a minimum of 1 LED labelled as LINK. DOCSIS 2.0 CMs _MAY_ have multiple LEDs in the CPE group to represent individual CPE interfaces types and paramters. Those LEDs _MAY_ be labelled according to their associated interface type. There is no specific requirement for labelling the functional groups, moreover, the LEDs in the DOCSIS group _SHOULD_ be in the order DS, US, and ONLINE, from left to right, or top to bottom, as appropriate for the orientation of the device. As well, the overall LED distribution _SHOULD_ intend to be in the order POWER, DS, US, ONLINE, and LINK. The _RECOMMENDED_ LEDs indicate the following steps are in progress, or have completed successfully by the CM: (X) Power on and optionally any proprietary CM self-test (X) DOCSIS Downstream Scanning and Sync (X) DOCSIS Upstream Channel Selection and Ranging (X) Becoming operational (X) Data link and activity 10.1.1 Power and self test When the CM is turned on, the _RECOMMENDED_ LEDs, or at least the DOCSIS group LEDs (DS, US, ONLINE) _SHOULD_ 'flash' while the CM performs the system initialization of the Operational System, CM application load, and any proprietary self-tests. Following the successful completion of the steps above, the _RECOMMENDED_ LEDs, or at least the DOCSIS group LEDs, _SHOULD_ show "lit solid" for one second and then only the POWER LED _SHOULD_ remain "lit solid." The LINK LED _MAY_ also be "lit solid" if a CPE device is properly connnected. If the system initialization, described above, results in a failure, the _RECOMMENDED_ LEDs, or at least the DOCSIS group LEDs _SHOULD_ continue to 'flash'. 10.1.2 Scanning and Synchronization to Downstream DS: The DS LED _SHOULD_ 'flash' as the CM scans for a Downstream DOCSIS channel. The DS LED _SHOULD_ go to "lit solid" when the CM MAC layer has already synchronized, as defined in [DOCSIS 5] Section 9.2.1. Whenever the CM is scanning for a downstream channel and attempting to sychronize to a downstream channel, the DS LED _SHOULD_ 'flash' and the US and ONLINE LEDs _SHOULD_ be 'unlit.' 10.1.3 DOCSIS Upstream obtaining parameters US: After the DS LED goes "lit solid", the US LED _SHOULD_ 'flash' and the ONLINE LED _SHOULD_ be 'unlit', while the CM is obtaining upstream parameters and performing initial ranging. When the CM completes a successful initial Ranging, the US LED _SHOULD_ go "lit solid". 10.1.4 Becoming operational ONLINE: After the US LED goes "lit solid", the ONLINE LED _SHOULD_ 'flash' while the CM continues the process to become operational. When the CM is operational, the ONLINE LED _SHOULD_ be "lit solid". Operational is defined according to [DOCSIS 5], Figure 9-1, CM initialization overview. If at any point there is a failure in the registration process that causes the CM to not become operational (ranging, DHCP, configuration, file download, registration, Baseline Privacy initialization, etc), the ONLINE LED _SHOULD_ continue to 'flash'. If the CM becomes operational and the CM configuration file has the Network Access Control Object (NACO) set to off, the ONLINE LED _SHOULD_ be 'unlit', while DS and US LEDs _SHOULD_ 'flash'.