I've updated the firmware on hundreds of SB6121 without issue. In our most recent lot of cable modems there were a couple of modems that do not attempt to do the upgrade. I'm trying to upgrade to SB612X-1.0.5.2-SCM01-NOSH.
I used Wirehark to snoop on the DHCP traffic between a bad CM and my provisioning system. I compare this with the DHCP packets from a CM that does do the firmware upgrade and don't see any real difference.
I cannot open the web page on the CM that does not accept the firmware upgrade.
I did an SNMPwalk on both a good and a bad cable modem. I do see differences there. I post a few excerpts from the SNMPwalk below. (The first line is from a bad CM and the second line is from a good CM). The log entries from the bad CM appear below that (I've never noticed a "MIMO" error before).
Can anybody see what's wrong?
SNMPv2-MIB::sysDescr.0 = STRING: DOCSIS 3.0 Cable Modem<>
SNMPv2-MIB::sysDescr.0 = STRING: DOCSIS 3.0 Cable Modem<>
IF-MIB::ifDescr.3 = STRING: RF Downstream Interface 1
IF-MIB::ifDescr.3 = STRING: RF Downstream Interface
SNMPv2-SMI::transmission.127.1.1.1.1.6.3 = INTEGER: -23
SNMPv2-SMI::transmission.127.1.1.1.1.6.3 = INTEGER: 37
SNMPv2-SMI::transmission.127.1.2.2.1.2.2 = STRING: "Z00.0"
SNMPv2-SMI::transmission.127.1.2.2.1.2.2 = STRING: "R02.0"
SNMPv2-SMI::mib-2.69.1.3.2.0 = STRING: "578204-007-nosh-a.p7"
SNMPv2-SMI::mib-2.69.1.3.2.0 = STRING: "SB612X-1.0.5.2-SCM01-NOSH.NNDMN.p7"
SNMPv2-SMI::mib-2.69.1.3.5.0 = STRING: "SB612X-1.0.5.1-SCM00-NOSH"
SNMPv2-SMI::mib-2.69.1.3.5.0 = STRING: "SB612X-1.0.5.2-SCM01-NOSH"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.6 = STRING: "MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:05:5f:ea:dc:54;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.7 = STRING: "No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:05:5f:ea:dc:54;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.8 = STRING: "Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.9 = STRING: "MDD message timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.10 = STRING: "No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.11 = STRING: "Lost MDD Timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.12 = STRING: "MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.13 = STRING: "Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.14 = STRING: "MDD message timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.15 = STRING: "Lost MDD Timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.16 = STRING: "MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.17 = STRING: "Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.18 = STRING: "MDD message timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.19 = STRING: "Lost MDD Timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.20 = STRING: "MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.21 = STRING: "Cable Modem Reboot due to power reset ;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.22 = STRING: "MDD message timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.23 = STRING: "No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.24 = STRING: "Lost MDD Timeout;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
SNMPv2-SMI::mib-2.69.1.5.8.1.7.25 = STRING: "MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:14:cb:00;CMTS-MAC=00:0c:31:f5:9c:01;CM-QOS=1.1;CM-VER=3.0;"
"Cable Modem Reboot due to power reset " Have you tried a different power supply? or is that you rebooting the modem?
578204-007-nosh-a.p7
Is that the firmware that is loaded in the bad modem? Its not listed as a GA release on Moto's site - You may need to contact Motorola and see if there is another step to get rid of that firmware. I'll bet those weren't supposed to be shipped with that still in them. When we were weeding out the last of our 1.0 moto's I found a couple that had engineering releases still in them, they wouldn't take regular updates either.
Version SBTI-1.0.6.10-SCM00 is the latest version, btw. You should sign up for moto's digitalcm site
Thanx for the response.
That would be me power cycling the modem. The modem is stable and apart from the firmware issue, works well.
>> contact Motorola and see if there is another step to get rid of that firmware.
I think you're right. I'm stuck with a custom spin of the firmware. I will have to wait until the Purchasing Manager returns from vacation to see if we are in a position to contact Moto over this.
So far, I use my provisiong system (Incognito), to update the firmware. In the meantime I might try the SNMP method of changing firmware. I noticed that there are instruction somewhere on this forum.
The firt pair of SNMP responses got mangled while posting. I try again, replacing angle brackets with brackets.
SNMPv2-MIB::sysDescr.0 = STRING: DOCSIS 3.0 Cable Modem((HW_REV: 5.0; VENDOR: Motorola; BOOTR: PSPU-Boot(25CLK) 1.0.12.18m3; SW_REV: SB612X-1.0.5.1-SCM00-NOSH; MODEL: SB6121))
SNMPv2-MIB::sysDescr.0 = STRING: DOCSIS 3.0 Cable Modem((HW_REV: 5.0; VENDOR: Motorola; BOOTR: PSPU-Boot(25CLK) 1.0.12.18m3; SW_REV: SB612X-1.0.5.2-SCM01-NOSH; MODEL: SB6121))
How did you manage to get the snmpwalk? I keep getting Timeout errors.
snmpwalk -v 2c -c public 192.168.100.1
Timeout: No Response from 192.168.100.1