Copyright 2000-2009 Motorola Inc.

_________________________________________________________________________________________

SB5100/SB5100E
Customer Release Notes
September 2, 2009

Platform

Release

SB5100
SB5100E

Revision #

SB5100-2.3.9.0-GA-00
SB5100E-2.3.9.0-GA-00

Date

Author

1
2
3
4
5

12/16/2005
01/31/2007
07/02/2008
07/23/2008
12/02/2008

Rich DiBenedetto
Rich DiBenedetto
Rich DiBenedetto
Rich DiBenedetto
Rich DiBenedetto

6
7

02/16/2009
09/02/2009

Rich DiBenedetto
Rich DiBenedetto

Description
Entered Customer Release Notes for SB5100(E)-2.3.3.0-SCM00
Entered Customer Release Notes for SB5100(E)-2.3.6.0-SCM00
Entered Customer Release Notes for SB5100(E)-2.3.7.0-GA-00
Entered Customer Release Notes for SB5100(E)-2.3.7.1-GA-00
Entered Customer Release Notes for SB5100(E)-2.3.7.2-GA-00
<Limited EuroDOCSIS Release>

9/9/2009

Entered Customer Release Notes for SB5100(E)-2.3.8.0-GA-00

Entered Customer Release Notes for SB5100(E)-2.3.9.0-GA-00

MGBI - Motorola General Business Information

Page 1 of 5

Copyright 2000-2009 Motorola Inc.

_________________________________________________________________________________________

Software Release Information

Product

SB5100, SB5100E

Software Versions

SB5100-2.3.9.0-GA-00
SB5100E-2.3.9.0-GA-00

Release Date

09/02/2009

Description of changes
for this release:

Fixes:
The SB5100(E) was sending a UDP Packet out to Port 65000 during boot up
with a payload of 20202020.... (cqvds00016061)

Description of changes
for this release:
SB5100-2.3.8.0-GA-00
SB5100E-2.3.8.0-GA-00
<Released 09/16/2009 for
General Availability>

Description of changes
for this release:
SB5100-2.3.7.2-GA-00
SB5100E-2.3.7.2-GA-00
<Limited Release on
12/02/2008 for Field Test
Only>

Description of changes
for this release:
SB5100-2.3.7.1-GA-00
SB5100E-2.3.7.1-GA-00

9/9/2009

The SB5100(E) Must Support Custom Frequency List Options.

(cqvds00009211)
The SB5100(E) now supports a list of 16 custom frequencies that can be
configured via SNMP.
The SB5100(E) shall retain the Custom Frequency List across power
cycle and reset to defaults via the GUI.
The Custom Frequency List can be cleared by reset to defaults through
the cmResetToDefaults MIB.

Fixes:
CPE fails to respond to IP ping after DCC with init-tech 0 on Cisco vXR and
BSR 64000 CMTS. (cqvds00012006)
The SB5100(E) now enables the data path back as soon it sends the DCC-REQ,
without waiting for a DCC-ACK.

Requirement to Disable Log/Syslog/CLI Messages if a Set-Top Box DSG DCD

Message is Seen by the CM. (cqvds00011906)
The CM will now ignore Set-Top Box DSG DCD Messages.

Fixes:
The SB5100 Could Get Stuck in init(o) State After Loosing its RF Signal and
Not Fully Recover Without a Power Reset. (cqvds00011799)
The failure was caused by the CM getting a T4 timeout before it completed
registration and moved to an operational state, causing the CM to initialize the
MAC only. However, in some cases, initializing the MAC is not enough to correct
the issue and a full reboot is required. Changes were made to perform a full
reboot on T4 regardless of the operational state if
cmConfigFullResetOnT4=true.

The SURFboard SB5100 Looses its Upstream Connection After a DCC, when
BPI+ is Enabled. (cqvds00010419)
Enhanced the management and processing of DSX messages.

The IfLastChange MIB Object always reports 0. (cqvds00009388)

The IfLastchange value should now reflect the uptime of the RF interface.

Requirement to Disable Log/Syslog/CLI Messages if a DOCSIS 3.0 MDD MAC

Frame is Seen by the CM. (cqvds00009427)
The CM will now ignore DOCSIS 3.0 MAC Messages.

Issue:
The expanded hacker communities have advanced their technique and now are
capable of enabling the SB5100 Factory MIB, extracting the appropriate certificates
required for BPI+, modifying/duplicatiing the CM MAC address as well as the

MGBI - Motorola General Business Information

Page 2 of 5

Copyright 2000-2009 Motorola Inc.

_________________________________________________________________________________________
<Released 07/23/2007 for
General Availability>

accompanying certificates to match the cloned cable modems.

Fixes:
The Following Modifications Have Been Made to the SB5100(E) to Aid in
Thwarting This Effort As Well As Enhancing Operator Notification
o
Disable a "once undocumented rework" that enabled SNMP access to the
Factory MIB.
o
If someone tries to access a CM via the Factory MIB, a trap with the CMs
HFC MAC address will be sent to a Syslog Server during the registration
process to indicate an unauthorized access attempt has occurred. In addition,
a critical system event will be logged to the CM docsDevEventTable and log
page.
A trap will be sent each time the CM comes up online, for three
times.

Description of changes
for this release:
SB5100-2.3.7.0-GA-00
SB5100E-2.3.7.0-GA-00
<Released 01/31/2007 for
General Availability>

Fixes:
SB5100(E) Hangs at init(o) After a Change of Downstream Frequencies
(CR 8902)
The SB5100(E) will no longer get stuck at init(o) after changing Downstream
Frequencies when a large number of TLV11s exist in the CM configuration file,
exceeding the limits of the modems Flash. This fix removes the need to recover
the modem with a "Factory Reset to Defaults".

SB5100(E) Supports Acquisition of New HRC Channel Plan Frequencies

(CR 7932)
Added support to channel scanning algorithm to enable the acquisition of new
HRC frequencies used by some MSOs.
SB5100(E) Experienced a Steady Drop in Upstream MER Over Time When
Passing Data Continuously (CR 6916)
The SB5100(E) now has enhanced equalization adjustments so that if the
previous number of EQ taps is different than the newly requested number of taps,
the SB5100(E) will pad/truncate the existing values, aligning the main tap to allow
proper equalization across the spectrum.
Enhancement Request:

SB5100(E) Now Returns the Model Number and Model Name via sysObjectID
(CR 8658)
To enhance consistency across products the SB5100(E) will now return the
Model Number/Model Name via a sysObjectID SNMP Query.

Notes:

9/9/2009

SB5100(E) Release 2.3.7.0-GA-00 File Size Differences

The 2.3.7.0-GA-00-NOSH image will now show as a smaller file size. The
SB5100(E) build process for creating the NOSH builds was changed so that the
NOSH image no longer has links to the Diagnostic Shell version of firmware.
Even through the serial port was disabled, etc. the NOSH code was using
excessive amounts of memory, causing some of the observed problems with
larger config files.

MGBI - Motorola General Business Information

Page 3 of 5

Copyright 2000-2009 Motorola Inc.

_________________________________________________________________________________________
Description of changes
for this release:
SB5100-2.3.6.0-SCM00
SB5100E-2.3.6.0-SCM00
<Released 01/31/2007 for
General Availability>

Fixes:
The SB5100(E) Scans Downstreams Instead of Additional Upstreams After a
DHCP Failure. (SCR2277)
The SB5100(E) will no longer immediately look for the next DS after failing DHCP
on a particular Upstream (US). Instead, it will try the next US based on the UCDs
received from the locked Downstream (DS). If no additional US channels are
present, or they also fail DHCP, then the SB5100(E) will scan for the next
available DS.

DOCSIS 2.0 Support for TLV41. (SCR2283)

Added support for the new DOCSIS 2.0 TLV41 (Downstream Channel List)
feature.

The SB5100(E) Rejects Config Files > 4K Bytes with BOOTR ver. 2150 and
2.3.3.0 code. (SCR2243)
Customers reported that after upgrading to firmware release 2.3.3.0 the
SB5100(E) would fail to load configuration files that previously worked. The
failures were noted to happen on files larger than 4K Bytes. Diagnostic modem
captures showed that the config file was rejected because of "low memory".

After an RF Issue Caused a Cable Modem Reset, the Cable Modem Was
Unable To Load the Config File Due to Low Memory. (SCR2269)
Customers reported that after a large-scale power outage, when the SB5100(E)
modems attempted to come back online, they rejected the config file (previously
loaded). Modems required a power on reset to come back online (using same
config file). Diagnostic modem captures showed that the config file was rejected
because of "low memory".

Supports Setting of ToS Bits via Config File. (SCR2216)

The CM Filter Policy table pointed to a wrong filter policy. This release changes
the processing so that the Filter Policy table points directly to the TOS Policy
table (docsDevFilterTosTable). All the IP packets now have the ToS Bits enabled
when the ToS bit is set from the config file.

Changed cmConfigFullResetOnT4 to True by Default (SCR2177)

Setting this default value to true will force the SB5100(E) to reboot upon receiving
a T4 instead of just reinitializing the MAC. Customers have the ability to change it
back to a disabled state via SNMP or Config file.

NACO LEDs Now Return to Proper State After A Failed Firmware Upgrade.
(SCR2233)
Changed the LEDs to return to the same state they were in prior to the download
being initiated.

9/9/2009

MGBI - Motorola General Business Information

Page 4 of 5

Copyright 2000-2009 Motorola Inc.

_________________________________________________________________________________________
Description of changes
for this release:
SB5100-2.3.3.0-SCM00
SB5100E-2.3.3.0-SCM00
<Released 12/16/2005 for
General Availability>

Fixes:
The SB5100(E) Will Stay In Standby Mode After UCC. (SCR2198)
Fixed a bug that allowed the SB5100(E) to leave standby mode if a UCC was
received while in standby mode. After completing the UCC, the SB5100(E) LEDs
were as follows: Power: On, Send: On, Receive: Off, Standby: On. The Standby
LED is lit throughout the transition.

Although the Standby LED is on, the modem is no longer in Standby mode and
allows traffic to pass normally. SNMP polls also show the Standby Status as
true.
Multicast Promiscuous Mode Now Working Properly w/BPI+. (SCR2219)
When the cmCfgMulticastPromiscuous OID was set to true and the SB5100(E)
was operational using DOCSIS 1.1 with BPI+, the SB5100(E) did not pass
Multicast Packets for RIPv2 Announcements. The SB5100(E) now passes
Multicast Packets for RIPv2 Announcements without any further interaction with
the cmCfgMulticastPromiscuous OID.
Fixed Problem Where SB5100(E) Would Be Stuck in a dhcp(0) Loop.
(SCR2202 and SCR2204)
The SB5100(E) could get stuck in dhcp(o) loop due to loss of IP connectivity
when attached to the Motorola BSR 64000 CMTS. The root cause of the lockup
was a jumbo packet (2066 bytes) being sent by the CMTS to the CM. This
caused the HMAC to chain Buffer Descriptors (BD) for the Packet Descriptors
(PD), since the DMA buffer can only hold 1536 bytes. Without enhanced
chaining support, the firmware and hardware buffers get out of sync, leading to
an eventual deadlock.
Additionally, we discovered a similar problem when dealing with multiple headeronly packets, the firmware could only handle a single header-only packet.

Enhancements:

Added Ability to Change Ethernet Interface Settings. These New MIB Objects
Allow the SB5100(E) Ethernet Interface to be Configured to Support 10/100
Mbits, and Full/Half Duplex. Added These New MIB Objects to the Config MIB.
(SCR2212)
Added these new MIB objects to the config MIB:
o cmConfigEtherAutoNegotiation (READ-WRITE)
o cmConfigEtherStatsDuplex
(READ-WRITE)
o cmConfigEtherSpeed
(READ-WRITE)
o cmConfigEtherOperStatus
(READ ONLY)
When cmConfigEtherAutoNegotiation is true, cmConfigEtherStasDuplex and
cmConfigEtherSpeed are READ ONLY

Added a New DHCP MIB Object (cmDhcpUnicastTrafficOnly). (SCR2170)

Setting this OID to true(1) and rebooting the modem will clear the Broadcast
bit in the DHCP 'flags' field to ensure that DHCP packets destined to the CM are
Unicast only.

9/9/2009

MGBI - Motorola General Business Information

Page 5 of 5