FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

[RogersMargaret]

Hello Community,

We are currently offering our users an exclusive opportunity to participate in an upcoming trial of the new firmware for our Rocket Wi-Fi Modem (CGN3ACR, CGN3AMR and CGN3ACSMR) and Rocket Gigabit Wi-Fi Modem (CGN3552 and CODA-4582). For details of this program, please see this thread.

This thread will be used for feedback regarding the firmware.  We've invited @RogersSergio, @RogersSyd & @RogersBob from our Networking team to participate in this thread.  Your feedback is very valuable and will be used to enhance the firmware before it is released publicly.

Thank you for your continued feedback and support.

[soundwave80]

Ever since "upgrading " to the CODA my internet has been unstable and slow, the silver lining here is that Roger's usually brings out a new modem every 2-3 years, so hopefully the CODA will be retiring soon.

[pac_west227]

K,

I'm on the CODA 4582. The most recent f/w update was 36T5. Why was downgraded to 36T2 just a few days after 36T5 was installed?? Too many bugs I presume... 

[catalano11]

been having packet loss for 2 months now since CODA modem. no fix at all. noise issue in area still has not been fixed. There is no point of calling in and waiting for a fix, 5 techs to my home. What is the point of having internet at all and paying for the top quality internet if it dose not work at all. I have given up.

[RogersIan]

We are in the midst of testing new code for the CODA-4582, firmware version 36T6.

Testing is looking good so far and we look to be in a position to get it out to the community this week.

Updates:

Upgrades to backend telemetry – Improves device management

RogersIan

[zardoz99]

OK, what's going on? 

15	10/23/2018 06:45:13	69010100	notice	SW Download INIT - Via NMS
16	10/23/2018 06:45:41	69011100	notice	SW download Successful - Via NMS
17	10/23/2018 11:47:13	90000000	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18	10/23/2018 09:37:28	69010100	notice	SW Download INIT - Via NMS
19	10/23/2018 09:37:57	69011100	notice	SW download Successful - Via NMS
20	10/23/2018 14:39:35	90000000	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Clear

Software Version

2.0.10.36T5

[ashwinrajan]

I am on 4.5.8.39T5. My internet is going off and on from yesterday night onwards. I am wondering if you guys are doing some maintenance.. 

Weirdly my modem is only bonded to 2 upstream channels. and also getting so many critical error.

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	603000000	256QAM	2.700	9	40.366
2	579000000	256QAM	2.900	5	40.946
3	585000000	256QAM	3.100	6	40.366
4	591000000	256QAM	2.900	7	40.366
5	597000000	256QAM	2.600	8	40.366
6	303000000	256QAM	9.500	1	40.946
7	609000000	256QAM	2.800	10	38.983
8	615000000	256QAM	1.900	11	40.366
9	621000000	256QAM	1.900	12	39.397
10	633000000	256QAM	2.500	13	40.366
11	639000000	256QAM	2.200	14	38.983
12	645000000	256QAM	2.200	15	40.366
13	651000000	256QAM	2.000	16	38.983
14	657000000	256QAM	2.200	17	40.366
15	663000000	256QAM	2.500	18	40.366
16	669000000	256QAM	2.600	19	40.366
17	675000000	256QAM	2.600	20	40.366
18	681000000	256QAM	2.700	21	38.983
19	687000000	256QAM	2.800	22	40.366
20	693000000	256QAM	2.700	23	40.366
21	699000000	256QAM	2.800	24	40.366
22	705000000	256QAM	2.800	25	40.946
23	711000000	256QAM	2.800	26	38.983
24	717000000	256QAM	2.300	27	38.983

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	38596000	ATDMA - 64QAM	45.250	3	3200000
2	30596000	ATDMA - 64QAM	46.750	1	6400000

DOCSIS Logs

The DOCSIS event logs is shown here

No.	Time	Type	Priority	Event
1	10/23/18 17:00:17	90000000	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
2	10/23/18 17:00:18	73040100	notice	TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
3	10/23/18 17:00:28	82000500	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
4	10/23/18 17:00:29	82000300	critical	Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
5	10/23/18 17:00:29	82000600	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
6	10/23/18 17:00:29	85010200	warning	TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
7	10/23/18 17:00:40	82000500	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
8	10/23/18 17:00:41	82000300	critical	Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
9	10/23/18 17:00:41	82000600	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xxCMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
10	10/23/18 17:00:52	82000500	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
11	10/23/18 17:00:53	82000300	critical	Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
12	10/23/18 17:00:53	82000600	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
13	10/23/18 17:01:04	82000500	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
14	10/23/18 17:01:05	82000300	critical	Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
15	10/23/18 17:01:05	82000600	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
16	10/23/18 17:01:16	82000500	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
17	10/23/18 17:01:17	82000300	critical	Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
18	10/23/18 17:01:17	82000600	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
19	10/23/18 17:01:24	82000500	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;
20	10/23/18 17:13:54	82000400	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cb:ad;CM-QOS=1.1;CM-VER=3.0;

(Edited - Removed CM Mac Addresses - RogersTony)

[zardoz99]

And again?

15	10/23/2018 14:45:19	69010100	notice	SW Download INIT - Via NMS
16	10/23/2018 14:45:48	69011100	notice	SW download Successful - Via NMS
17	10/23/2018 19:47:26	90000000	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
18	10/23/2018 19:47:38	69010100	notice	SW Download INIT - Via NMS
19	10/23/2018 14:48:19	69011100	notice	SW download Successful - Via NMS
20	10/23/2018 19:50:01	90000000	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Clear

Still at

Software Version

2.0.10.36T5

[Triple_Helix]

---

@RogersIan wrote:

We are in the midst of testing new code for the CODA-4582, firmware version 36T6.

Testing is looking good so far and we look to be in a position to get it out to the community this week.

Updates:

Upgrades to backend telemetry – Improves device management

RogersIan

---

Well I got the 36T6 Firmware and now my Download speed is around 50 to 75Mbps Max so what is going on? Gigabit Plan here and never had this before with 36T5?

Software Version

2.0.10.36T6

[Datalink]

Reboot the modem.

[Triple_Helix]

---

@Datalink wrote:

Reboot the modem.

---

Yes I did twice and always do a second reboot after a new firmware. You mentioned it so many times so it's hard to miss.

[mcsandy]

On 36T6 speeds look as usual.

[Datalink]

@Triple_Helix Lol, ok, call me a nag!  But, you remembered.  Guess it works after all 🙂

Is the modem showing that its running in Docsis 3.1 mode?

[Triple_Helix]

---

@Datalink wrote:

@Triple_Helix Lol, ok, call me a nag!  But, you remembered.  Guess it works after all 🙂

Is the modem showing that its running in Docsis 3.1 mode?

---

Yea that's fine and just talked to support and they don't see anything wrong on there end and they suggested to get another modem??? He also did a factory reset and the 36T6 is still there?

Software Version

2.0.10.36T6

Downstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	591000000	256QAM	5.500	7	38.983
2	855000000	256QAM	5.100	3	35.084
3	861000000	256QAM	5.500	4	35.595
4	579000000	256QAM	4.700	5	37.636
5	585000000	256QAM	5.200	6	37.636
6	849000000	256QAM	5.300	2	35.084
7	597000000	256QAM	5.500	8	37.636
8	603000000	256QAM	5.600	9	38.605
9	609000000	256QAM	5.200	10	37.636
10	615000000	256QAM	5.500	11	37.636
11	621000000	256QAM	6.000	12	37.636
12	633000000	256QAM	6.000	13	37.636
13	639000000	256QAM	6.100	14	37.636
14	645000000	256QAM	6.500	15	37.356
15	651000000	256QAM	6.700	16	37.636
16	657000000	256QAM	6.700	17	37.636
17	663000000	256QAM	6.300	18	38.605
18	669000000	256QAM	6.200	19	37.636
19	675000000	256QAM	6.200	20	37.636
20	681000000	256QAM	6.500	21	37.636
21	687000000	256QAM	6.600	22	37.356
22	693000000	256QAM	7.100	23	37.636
23	699000000	256QAM	7.200	24	37.636
24	705000000	256QAM	6.900	25	37.636
25	711000000	256QAM	6.400	26	37.636
26	717000000	256QAM	5.600	27	37.356
27	723000000	256QAM	6.000	28	37.636
28	825000000	256QAM	6.000	29	35.595
29	831000000	256QAM	5.600	30	35.595
30	837000000	256QAM	5.400	31	35.084
31	843000000	256QAM	5.000	32	35.084
32	303000000	256QAM	-0.300	1	38.605

OFDM Downstream Overview

Receiver	FFT type	Subcarr 0 Frequency(MHz)	PLC locked	NCP locked	MDC1 locked	PLC power(dBmv)
0	4K	275600000	YES	YES	YES	0.799999
1	NA	NA	NO	NO	NO	NA

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	30596000	ATDMA - 64QAM	39.250	1	6400000
2	38596000	ATDMA - 64QAM	43.250	3	3200000
3	23700000	ATDMA - 64QAM	39.250	2	6400000

OFDM/OFDMA Overview

Channel Index	State	lin Digital Att	Digital Att	BW (sc's*fft)	Report Power	Report Power1_6	FFT Size
0	DISABLED	0.5000	0.0000	0.0000	-inf	-1.0000	4K
1	DISABLED	0.5000	0.0000	0.0000	-inf	-1.0000	4K

[Datalink]

@Triple_Helix, I wouldn't trade the modem in just yet.  I'd give @RogersIan or @RogersGordon a chance to have a look at it first, if you can wait for a day or two.  Can you call tech support back and ask the Customer Service Rep what the OFDM channel QAM number is at the present time?  I'm curious if that number has dropped significantly from its normal 1024 level.

[JohnBeaudin]

Feedback for CODA 36T6 modem.

It's been reliable so far, I didn't had to reboot the modem yet like I had to do every day with previous firmware.

Latency is also lower on speedtest.net 

 (Image Rejected due to personal IP address visible - RogersTony)

So far It's a lot better than the previous firmware.

[Triple_Helix]

---

@Datalink wrote:

@Triple_Helix, I wouldn't trade the modem in just yet.  I'd give @RogersIan or @RogersGordon a chance to have a look at it first, if you can wait for a day or two.  Can you call tech support back and ask the Customer Service Rep what the OFDM channel QAM number is at the present time?  I'm curious if that number has dropped significantly from its normal 1024 level.

---

It's back to normal as I tried my other laptop via Ethernet and the speeds were good so reinstalled my Ethernet adapter driver and all is back to normal. 

[JohnBeaudin]

I wonder how close we are from D3.1 upload now?

[blues_clues]

2.0.10.36T6

Observation: There is a noticeable 15 second GUI delay for data to return from the, "Basic/MoCA", settings tab.

[RogersGordon]

Hi @JohnBeaudin

The network teams have been testing OFDMA and working through the issues.

If all goes well we'll be looking to roll out enablement in 2019.

G

[JohnBeaudin]

@RogersGordon

That's great to hear, thank you!

[rjmaxim]

---

@mcsandy wrote:

On 36T6 speeds look as usual.

---

@mcsandy  If you are getting this on average.....that's great. I am on CODA 36T6 and average:

Down 450 Up 40.  Consistency is the real problem.....Up is good but down sucks when you're paying for 1000. If average was around 800 I would be happy. Below test results over last 30 days using 6 different hosts, including Rogers.