Cox → [AZ] New Motorola MB8600 Firmware 8600-19.3.11

I own my own personal Motorola MB8600 cable modem and Cox just pushed new firmware version 8600-19.3.11 to it on 09/30/2020. My modem was previously using firmware version 8600-18.2.9 for over a year. When logging into the modem's webgui you will be prompted to change the username and password. There also has been some changes to the webui layout. The OFDM PLC channel still hasn't been fixed. So far working as expected. This is just FYI. I have yet to see any information about this firmware version.

The password change requirement is a CA state law. Expect to see that on nearly every device in some form or fashion.

When can we expect to see this firmware deployed in New England/Northeast region?

When can we expect to see this new firmware deployed in Southern California? I reached out to cox.help@cox.com and was told "I'm sorry that we are not able to push that firmware at this time."

Got another Motorola MB8600 firmware push to firmware version 8600-19.3.15. I think it have on January 12th, 2021. I live in Tucson Arizona and have yet hear about anyone else in my state or any other state having these new firmware updates. Below is the firmware sequence since I purchased this modem when it first came out.

8600-6.1.1.19 >>> 8600-18.2.9 >>> 8600-19.3.11 >>> 8600-19.3.15

Got another Motorola MB8600 firmware push to firmware version 8600-19.3.15. I think it happened on January 12th, 2021. I live in Tucson Arizona and have yet hear about anyone else in my state or any other state having these new firmware updates. Below is the firmware sequence since I purchased this modem when it first came out.

8600-6.1.1.19 >>> 8600-18.2.9 >>> 8600-19.3.11 >>> 8600-19.3.15

I'm still on 18.2.9 here

My firmware is at the newest level, 8600-19.3.15, however in checking that out, I saw the following info (MAC has been edited down)and was hoping one of the knowledgeable folk would be kind enough to translate into layman terms for me.

MB8600 Event Log
Tue Jan 26 2021 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=00;CMTS-MAC=00:38:df:09:1d:5b;CM-QOS=1.1;CM-VER=3.1;
00:24:36
Tue Jan 26 2021 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00;CMTS-MAC=00:38:df:09:1d:5b;CM-QOS=1.1;CM-VER=3.1;
00:24:36
Tue Jan 26 2021 Warning (5) Dynamic Range Window violation
00:24:36
Tue Jan 26 2021 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00;CMTS-MAC=00:38:df:09:1d:5b;CM-QOS=1.1;CM-VER=3.1;
00:24:36
Tue Jan 26 2021 Warning (5) Dynamic Range Window violation
00:24:36
Tue Jan 26 2021 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00;CMTS-MAC=00:38:df:09:1d:5b;CM-QOS=1.1;CM-VER=3.1;
00:24:36
Tue Jan 26 2021 Warning (5) Dynamic Range Window violation
00:24:36
Tue Jan 26 2021 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=00;CMTS-MAC=00:38:df:09:1d:5b;CM-QOS=1.1;CM-VER=3.1;
00:24:36
Tue Jan 26 2021 Warning (5) Dynamic Range Window violation
00:24:57
Tue Jan 26 2021 Warning (5) Unicast DSID PSN startup error
00:24:57
Tue Jan 26 2021 Notice (6) CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: �; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00;CMTS-MAC=00:38:df:09:1d:5b;CM-QOS=1.1;CM-VER=3.1;

This seems to be normal, and only happens upon modem starting up. It's something between the modem, and the CCAP(CMTS).

bchandler02 factory reseting your modem might trigger an update for you as I believe it did for me. Do a hard cable modem factory reset by usnig the following method:

Factory Reset:
Locate the RESET button on the back of your modem. Press the RESET button and hold it for 30 seconds before you release. After 30 seconds has passed, release the RESET button. This will clear all configuration in the product and pull a fresh connection from your Internet Service Provider.

Barron I get the same warning after a fresh cable modem reboot or completely disconnecting the power and it booting it back up.

factory reset is not required. Just a simple reboot.

What is the default login and password? Mine has one now and I don't know what it is.

Username: admin / Password: motorola

Didn't read the thread carefully enough. Mine is an Arris CM8200 so different model, different PW. New firmware though :P

Try this then for the Arris CM8200. Username: admin / Password: admin

MB8200 is similiar. Try what is shown here:

»arris.secure.force.com/c ··· r-Access

Nope

I think it's admin/modem serial number. I seen a post not to long ago about it.

Edit: last 8 digits of the serial

You can also try admin/password. At least that's what it is for the S33 so it should be the same for yours as well.

Try admin / motorola

That what it is. Thank

I see now there is a option to change the username and password, any opinions if safe to do so or just leave as is

the risk is that a website script "could" initiate a login and reset of the modem. It's fairly dubious that it would be worth it to denial of servicing a person like this, but its possible.

My MB8600 rebooted last night and this morning I was presented with the "Your password is incorrect" message when I attempted to logon. I cycled the power off and on and it would not connect to Cox. Did a hard reset (paper clip) then opened the modem logon page. Used "admin" and last eight digits of serial #. That took me the a password change page where I was forced to change the password. After that I saw the modem was finally connected to Cox. Firmware had updated to 8600-19.3.15 from 8600-18.2.9.

Any idea when the new firmware/software push will reach the East Cost? I've been on 18.2.9 for over a year.

Thank you for your time.

I think 19.3.15 started a few weeks ago. The entire nationwide rollout spans ~6-8 weeks so you should be soon.

Thank you!

02-09-2021
XFinity / Comcast just pushed New Motorola MB8600 Firmware 8600-19.3.15

400/25 speed here

I am on 19.3.15 here as well .. 300/30 tier.

I've had some strange behaviour with my SB8600 starting these past couple of weeks. I woke up this morning to no internet and it had the same root cause as the previous occurrence on 2/27. Even though I don't have Gigablast, I have LACP turned on in the modem settings and on the two ports on the 3560X switch. It works, and has worked, just fine for many months. However since this new version of code, there have been two times now where there has been no internet. Starting at 04:59 this morning the modem dropped both interfaces and brings them back online, this cycles over the next 40 minutes with the ports eventually going down and staying down because LACP is not enabled on the remote ports. I tried changing one port to non-LACP but could still not get back online or access the modem. Power cycling the modem restored full service. Not sure how to triage this, other than to disable LACP and go back to one port.

Mar  8 04:59:00 ciscosw 12991: 014775: Mar  8 11:58:59.893: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 04:59:07 ciscosw 12992: 014776: Mar  8 11:59:06.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 04:59:07 ciscosw 12993: 014777: Mar  8 11:59:06.092: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 04:59:07 ciscosw 12994: 014778: Mar  8 11:59:07.098: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 04:59:08 ciscosw 12995: 014779: Mar  8 11:59:07.409: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 04:59:14 ciscosw 12996: 014780: Mar  8 11:59:13.239: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 04:59:16 ciscosw 12997: 014781: Mar  8 11:59:15.738: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:03:20 ciscosw 12998: 014782: Mar  8 12:03:19.453: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:03:20 ciscosw 12999: 014783: Mar  8 12:03:20.468: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:03:22 ciscosw 13000: 014784: Mar  8 12:03:21.449: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:03:22 ciscosw 13001: 014785: Mar  8 12:03:21.474: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:04:42 ciscosw 13002: 014786: Mar  8 12:04:41.969: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:04:50 ciscosw 13003: 014787: Mar  8 12:04:49.091: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:04:50 ciscosw 13004: 014788: Mar  8 12:04:49.107: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:04:50 ciscosw 13005: 014789: Mar  8 12:04:49.233: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:04:50 ciscosw 13006: 014790: Mar  8 12:04:50.097: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:04:56 ciscosw 13007: 014791: Mar  8 12:04:55.852: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:05:00 ciscosw 13008: 014792: Mar  8 12:04:59.274: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:09:08 ciscosw 13009: 014793: Mar  8 12:09:07.183: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:09:09 ciscosw 13010: 014794: Mar  8 12:09:08.164: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:09:10 ciscosw 13011: 014795: Mar  8 12:09:09.028: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:09:10 ciscosw 13012: 014796: Mar  8 12:09:09.188: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:11:08 ciscosw 13013: 014797: Mar  8 12:11:07.404: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:11:15 ciscosw 13014: 014798: Mar  8 12:11:14.761: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:11:18 ciscosw 13015: 014799: Mar  8 12:11:17.177: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:11:18 ciscosw 13016: 014800: Mar  8 12:11:17.177: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:11:18 ciscosw 13017: 014801: Mar  8 12:11:18.208: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:11:25 ciscosw 13018: 014802: Mar  8 12:11:24.273: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:11:28 ciscosw 13019: 014803: Mar  8 12:11:27.310: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:11:38 ciscosw 13020: 014804: Mar  8 12:11:37.267: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:11:38 ciscosw 13021: 014805: Mar  8 12:11:37.418: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:11:39 ciscosw 13022: 014806: Mar  8 12:11:38.257: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:11:39 ciscosw 13023: 014807: Mar  8 12:11:39.272: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:13:10 ciscosw 13024: 014808: Mar  8 12:13:09.589: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:13:14 ciscosw 13025: 014809: Mar  8 12:13:13.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:13:14 ciscosw 13026: 014810: Mar  8 12:13:13.716: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:13:14 ciscosw 13027: 014811: Mar  8 12:13:14.714: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:13:18 ciscosw 13028: 014812: Mar  8 12:13:17.113: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:13:22 ciscosw 13029: 014813: Mar  8 12:13:21.467: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:18:06 ciscosw 13030: 014814: Mar  8 12:18:05.403: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:18:07 ciscosw 13031: 014815: Mar  8 12:18:06.401: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:18:08 ciscosw 13032: 014816: Mar  8 12:18:07.324: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:18:08 ciscosw 13033: 014817: Mar  8 12:18:07.416: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:19:31 ciscosw 13034: 014818: Mar  8 12:19:30.813: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:19:39 ciscosw 13035: 014819: Mar  8 12:19:38.262: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:19:39 ciscosw 13036: 014820: Mar  8 12:19:38.270: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:19:39 ciscosw 13037: 014821: Mar  8 12:19:38.589: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:19:39 ciscosw 13038: 014822: Mar  8 12:19:39.269: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:19:47 ciscosw 13039: 014823: Mar  8 12:19:46.139: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:19:49 ciscosw 13040: 014824: Mar  8 12:19:48.269: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:24:23 ciscosw 13041: 014825: Mar  8 12:24:22.551: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:24:23 ciscosw 13042: 014826: Mar  8 12:24:22.853: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:24:24 ciscosw 13043: 014827: Mar  8 12:24:23.549: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:24:24 ciscosw 13044: 014828: Mar  8 12:24:24.556: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:27:36 ciscosw 13045: 014829: Mar  8 12:27:35.239: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:27:38 ciscosw 13046: 014830: Mar  8 12:27:37.403: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:27:38 ciscosw 13047: 014831: Mar  8 12:27:37.412: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:27:38 ciscosw 13048: 014832: Mar  8 12:27:38.410: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:27:43 ciscosw 13049: 014833: Mar  8 12:27:42.462: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:27:45 ciscosw 13050: 014834: Mar  8 12:27:44.743: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:29:24 ciscosw 13051: 014835: Mar  8 12:29:23.960: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:29:25 ciscosw 13052: 014836: Mar  8 12:29:24.959: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:29:26 ciscosw 13053: 014837: Mar  8 12:29:25.823: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:29:26 ciscosw 13054: 014838: Mar  8 12:29:25.965: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:29:32 ciscosw 13055: 014839: Mar  8 12:29:31.803: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:29:32 ciscosw 13056: 014840: Mar  8 12:29:31.820: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:29:32 ciscosw 13057: 014841: Mar  8 12:29:31.820: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:29:33 ciscosw 13058: 014842: Mar  8 12:29:32.827: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:36:59 ciscosw 13059: 014843: Mar  8 12:36:58.566: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:36:59 ciscosw 13060: 014844: Mar  8 12:36:58.591: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:37:00 ciscosw 13061: 014845: Mar  8 12:36:59.564: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:37:00 ciscosw 13062: 014846: Mar  8 12:37:00.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:38:21 ciscosw 13063: 014847: Mar  8 12:38:20.042: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:38:21 ciscosw 13064: 014848: Mar  8 12:38:20.797: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:38:21 ciscosw 13065: 014849: Mar  8 12:38:20.813: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:38:22 ciscosw 13066: 014850: Mar  8 12:38:21.803: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:38:28 ciscosw 13067: 014851: Mar  8 12:38:27.826: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:38:28 ciscosw 13068: 014852: Mar  8 12:38:28.422: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:38:55 ciscosw 13069: 014853: Mar  8 12:38:54.149: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to up
Mar  8 05:38:55 ciscosw 13070: 014854: Mar  8 12:38:55.147: %LINK-3-UPDOWN: Interface Port-channel5, changed state to up
Mar  8 05:38:56 ciscosw 13071: 014855: Mar  8 12:38:55.885: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to up
Mar  8 05:38:56 ciscosw 13072: 014856: Mar  8 12:38:56.154: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to up
Mar  8 05:40:18 ciscosw 13073: 014857: Mar  8 12:40:17.017: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/47, changed state to down
Mar  8 05:40:24 ciscosw 13074: 014858: Mar  8 12:40:23.132: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/48, changed state to down
Mar  8 05:40:24 ciscosw 13075: 014859: Mar  8 12:40:23.141: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel5, changed state to down
Mar  8 05:40:24 ciscosw 13076: 014860: Mar  8 12:40:24.139: %LINK-3-UPDOWN: Interface Port-channel5, changed state to down
Mar  8 05:40:25 ciscosw 13077: 014861: Mar  8 12:40:24.239: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
Mar  8 05:40:32 ciscosw 13078: 014862: Mar  8 12:40:31.084: %EC-5-L3DONTBNDL2: Gi0/48 suspended: LACP currently not enabled on the remote port.
Mar  8 05:40:34 ciscosw 13079: 014863: Mar  8 12:40:33.945: %EC-5-L3DONTBNDL2: Gi0/47 suspended: LACP currently not enabled on the remote port.
 

I'll give the feedback to Zoom/Motorola.

I have not found LAG to be worth it. Technically it should be more resilient, but in function I've found it profoundly more sensitive. As Randy would say, its a no from me dog.