Table of Contents
Advertisement
PROBLEMS FIXED
The following problems were discovered in Release 2.0 of the CMTS and
corrected.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
305472-B Rev 02
An Internal inconsistency in the upstream scheduler caused the CMTS
to reset when the cable interface admin status was cycled from down to
up on a plant with more than 200 CMs.
The frequency status table for Ingress Avoidance displayed
frequencies, as in use, though upstream interfaces were disabled.
With Ingress Avoidance, changing a carrier path from one channel
group to another channel group could cause an invalid configuration.
The CMTS would continuously reset when its provisioning file was
greater than 8192 bytes. The maximum size of a provisioning file is
now 40960 bytes.
The CMTS did not record the modems IP address in
docsIfCmtsCmStatusIPAddress when the IP address was not in the
"modem IPaddress" parameter of the Registration Request.
The "modems" command could cause the CMTS to reset when access
was denied to a modem.
Enabling Ingress Avoidance did not force all upstreams in a channel
group to be within the valid frequency range.
Metric status values were not being reset when Ingress Avoidance
forced a change due to channel groups.
Provisioning of Ingress Avoidance Frequency Control Table and
Profile Table could cause an SNMP set error when Frequency Status is
available.
An SNMP get-next on lcPhyIndex of the proprietary MIB with a large
index value was not working properly.
Attempts to set docsIfUpChanel ModulationProfile from the Command
Line Interface failed.
Ethernet Error statistics were incorrect when running full-duplex.
Release Notes
1-7
Advertisement
Table of Contents
