cancel
Showing results for 
Search instead for 
Did you mean: 

FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

RogersMargaret
Community Manager (Retired)
Community Manager (Retired)

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.

4,921 REPLIES 4,921

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@JohnyR did you switch modems to the CODA-4582 and if so, was that in the Thursday afternoon gap?  If you did switch modems, what was the original modem model?

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial


@JohnyR wrote:

@RogersDave Will the DOCSIS 3.1 rollout help with node congestion? I've been experiencing serious node congestion over the past year. Screenshots below are to my node.

 

 


The DOCSIS 3.1 rollout will effectively alleviate network congestion on downlink. If network congestion is on the upstream, then it will require the DOCSIS 3.1 rollout for upstream (which is happening later) or node segmentation.

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

JohnyR
I plan to stick around

@Datalink Yup, exactly right. The gap was when I went to go switch over from the Rocket (3552) to the CODA. All those pink dots you see after the CODA install was me trying to figure out why I was getting 20mbps down. The next small gap was me going to the store to replace the CODA for another CODA. As expected, switching these modems did nothing for my speed. Although, the next morning my speeds did greatly improve from 20 to around 300 down -- I'm not sure what had changed.

 

@RogersDave Thanks for the information. Should I wait for the roll out or should I submit a ticket for node congestion? What's the likelyhood that one of the reps will actually believe me and take a look at it?

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Patrick9591
I plan to stick around

Hello @RogersDave,

Have you got a chance to take a look at my modem?

 

Patrick

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Modem has restarted multiple times, 5 times yesterday and twice today. Currently have the CGN3ACSMR on firmware 4.5.8.22. Already requested a firmware update last tuesday (December 13) but it still has not been pushed. Here are my signal levels and error reports. 


screencapture-192-168-0-1-index-html-1482281888992.png

1 12/21/16 01:18:55 82000600 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2 12/21/16 01:20:51 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
3 12/21/16 01:20:58 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
4 12/21/16 01:21:58 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
5 12/21/16 01:22:05 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
6 12/21/16 01:23:12 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
7 12/21/16 01:23:17 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
8 01/01/70 00:02:35 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
9 01/01/70 00:02:40 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
10 01/01/70 00:03:57 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
11 01/01/70 00:04:01 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
12 01/01/70 00:02:27 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
13 01/01/70 00:02:33 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
14 01/01/70 00:03:50 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
15 01/01/70 00:04:02 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
16 01/01/70 00:05:03 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
17 01/01/70 00:05:12 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
18 01/01/70 00:06:47 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
19 01/01/70 00:07:00 82000900 warning B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
20 01/01/70 00:07:11 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

RyzenFX
I'm a reliable contributor

@RogersDave

 

After experiencing speed degredation issues on Ports 1 and 2, I switched to port 3, rebooted the modem, and speeds went back to normal. Could there be a shielding issue? 

 

Judging from the graphs from the rogers speed test, the ports may have not been shielded properly, seen from the fluctuations in the upload and download speed. Aswell, the modem ports closest to the bottom of the modem, which is farthest away from the attennas at the top show more consistent results; there are less fluctuations in download and upload speeds, and a straighter line can be seen from speed test below.

 

(Test ran on port 3 of the CODA-4582)

port3_12_20_test.png

 

 

 

 

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@RogersDave @Killacammy same issue.  Wired speedtests seem to to cap at about 88meg down.  Used to be over 700meg down.  Get over 250down over 5g.

 

My guess is that modem/router is reading wired connection to be 10/100 not 10/100/1000.  Using same cables rated 5e as on my 3552.

 

On the positive side, my upload speeds have gone up from about 30meg to 40 and the levels are much better.

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Fixed my own issue - DO NOT USE PORT 1.

 

Confirmed that Port 1 - goes green just 10/100.

 

Moving to Port 4, I get yellow connection and much better results.  877 down, ping ms.

 

 

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

JohnBeaudin
I'm a senior contributor

@User105

 

877 down and how much ping ms?

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

NorthGraves
I plan to stick around

"Fixed my own issue - DO NOT USE PORT 1.

 

Confirmed that Port 1 - goes green just 10/100.

 

Moving to Port 4, I get yellow connection and much better results.  877 down, ping ms."

 

FWIW, using exactly port 1.

940 down.

Also, using two CAT-7 cables, certified up to 10 Gb/sec: one from switch to router, and the second one from router to port 1 of the CODA-4582.

 

Bought here:

http://www.ebay.ca/itm/Dulcet-Inimitable-Cat-7-RJ45-Shielded-LAN-Network-Ethernet-Cable-Internet-Cor...

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial


@SimplePanda wrote:

@RogersDave - Having done a bit of testing it appears this new modem still suffers from the IPSec performance issues of the previous devices.

 

Site A: Gigabit Ignite connection at my house (new Hitron D3.1 gateway in bridge mode to a Ubiquiti Networks EdgeRouter).

Site B: 100Mbps Beanfield connection (symmetric FTTP) behind a Juniper SRX.

 

Copying files from the office (Beanfield) to the house (Rogers):

 

If I copy something over SSH = 100Mbps (saturates the Beanfield upstream).

If I copy something over IPsec / UDP (NAT-T) = 25Mbps, maximum.

 

Previously the poor IPSec performance was IPv6 / ESP based (same 25Mbps speed limit).

 

Do you still think this is a Hitron firmware issue?


On the Puma 6, this limitation was a chipset issue which I'm still hoping will get resolved. It just keeps being de-prioritized because we are trying to address latency.

 

On the Puma 7, I can't say for sure. It will have to be carefully tested but that will come in January.

 

Dave

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial


@Killacammy wrote:

@RogersDave have you noticed anything with mine?  The fact that I can only get 11mbps while wired vs 30 mbps via 5g makes absolutely  no sense to me and the speeds have yet to improve at all.  I have switched wires and still nothing.


In both cases, these are very slow speeds and I suspect you are impacted by the 2.4 GHz issue.

 

I can have a look and suggest further action if you send me your MAC address via private message.

 

Dave

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

jseller
I plan to stick around

Hi,

 

I noticed that when someone includes a screenshot of their upstream and downstream signal parameters the signal strength is almost always positive. I checked mine and they are all negative. Is this a problem? 

 

I am on a gigabit internet but my speed never goes more than 550Mbps on a wired connection when I had my previous modem.  I tested today and I only got 104.17 Mbps down and 29.70 Mbps up using the new modem.

 

Modem is at least 6 feet away from the router, I'm connected through port 3 and Wifi on the modem is disabled.

 

http://www.speedtest.net/my-result/5900543977

 

I can't even use the Rogers Speed Check. I get a 'Latency Test Error'.

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1615000000256QAM-1.6001140.366
2561000000256QAM-1.700238.983
3567000000256QAM-2.300338.983
4573000000256QAM-2.700438.983
5579000000256QAM-2.600538.983
6585000000256QAM-2.400640.366
7591000000256QAM-2.100738.983
8597000000256QAM-1.300840.366
9603000000256QAM-1.900940.366
10609000000256QAM-1.9001040.366
11555000000256QAM-2.100138.983
12621000000256QAM-2.2001238.983
13633000000256QAM-1.9001338.983
14639000000256QAM-1.3001440.366
15645000000256QAM-0.8001540.366
16651000000256QAM-0.4001640.366
17657000000256QAM-0.9001740.366
18663000000256QAM-0.9001840.366
19669000000256QAM-1.0001938.983
20675000000256QAM-1.3002038.983
21681000000256QAM-0.7002140.366
22687000000256QAM-0.6002240.366
23693000000256QAM-0.8002340.366
24699000000256QAM-1.2002440.366
25705000000256QAM-2.1002538.983
26711000000256QAM-2.9002638.983
27717000000256QAM-2.6002738.983
28723000000256QAM-2.9002838.605
29825000000256QAM-2.2002938.605
30831000000256QAM-1.8003040.366
31837000000256QAM-2.1003138.983
32843000000256QAM-2.8003238.983
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K275600000YESYESYES-1.599998
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
130596000ATDMA - 64QAM34.25016400000
238596000ATDMA - 64QAM37.50033200000
323700000ATDMA - 64QAM33.00026400000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.00004K

 

 

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

dmbcanda
I plan to stick around

@RogersDave

 

Not too sure what is going on, but I am getting either socket errors or the following speeds this afternoon.   Have rebooted twice, have not had a problem all week: EDIT:  Noticed two Rogers trucks at the end of street running a temp line to someones house, would that affect me?

 

Coda-4582 12.21.16..JPG

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

RyzenFX
I'm a reliable contributor

After a couple of days testing modem ports 1, 2, and 3 on the CODA-4582, I have concluded that all 3 ports are effected by the 2.4GHz issue. Switching to any of those ports (in my case) has not seemed to fix the issue, however rebooting the modem has temporarily  fixed the issue. We pretty much have to wait for a implementation by Rogers and Hitron in order to fix this problem. 

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

What happens when disabaling 2.4 does it fix it ?

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

@eddiethefunnyon wrote:

After a couple of days testing modem ports 1, 2, and 3 on the CODA-4582, I have concluded that all 3 ports are effected by the 2.4GHz issue. Switching to any of those ports (in my case) has not seemed to fix the issue, however rebooting the modem has temporarily  fixed the issue. We pretty much have to wait for a implementation by Rogers and Hitron in order to fix this problem. 


There are 2 distincts issues affecting some modems. Some modems are affected by one of the two while others are affected by both.

 

For the Ethernet port problem, the problem is that ports (especially port 1) negociates at 100M instead of Gigabit. This is not linked to the 2.4 GHz issue.

 

I checked your modem and will contact you in private with additional tests.

 

Dave

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

I have a new issue for ya'll.

When I tried pluggin my laptop in the LAN ports it would connect and link at 1.0GB/s, but never get an ip address. Doesn't matter which LAN port on the modem I use, window would show linked at 1.0GB/s, but no ip address/internet access. I had 2 devices connected to the LAN port, my NAS, PS4, and I added the laptop trying to connect. I even tried unplugging all LAN devices, and only having the laptop, but same issue on all ports. So I thought maybe something is wrong with my laptop, but I plugged it into my work lan and everything worked perfect.

 

So today I had to unplug the modem and plug it back in, so it reboot. Now my PS4 is doing the same thing as the laptop! It connects, but cannot get an IP address! I've tried factroy reset, reboot multiple times, etc. This isn't a hardware issue, because just like with the laptop I tried every LAN port, and the devices show a link at 1GB/s, but the DHCP server in the CODA wont hand out IP address's. 

 

Anyone else experiece this issue? I of course also suffer from the super slow speeds (10mb/s) and a DOCSIS LOG full if Sync Errors if I use 2.4Ghz with 20/40mhz Channel Width. If I select 20Mhz Channel width my speeds are fine and no SYNC Errors. 

 

I'm really hoping we get some non Alpha firmware so I can use my internet. 

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Killacammy
I plan to stick around

@RogersDave wrote:

@Killacammy wrote:

@RogersDave have you noticed anything with mine?  The fact that I can only get 11mbps while wired vs 30 mbps via 5g makes absolutely  no sense to me and the speeds have yet to improve at all.  I have switched wires and still nothing.


In both cases, these are very slow speeds and I suspect you are impacted by the 2.4 GHz issue.

 

I can have a look and suggest further action if you send me your MAC address via private message.

 

Dave


Hey Dave,

I sent it a week or so ago.  Did you not get it?

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

14N
I plan to stick around

Hi @RogersDave 

I just exchanged my preivious modem with the CODA few hours ago.

I can connect in the internet and everything is fine if the modem is not in bridge mode.

With my previous modem, it was in bridge mode and my router was working fine.

But with the CODA, if I put it in bridge mode, my router cannot get an IP in the Rogers dhcp server thus no internet connection. My router is TP-Link Archer AC2600.

 

Internet speed is just the same as the previous modem. My only average speed is 200mbps never over 400mbps, most of the time even I'm on gigabit plan it's just below 200mbps. I still have pending ticket regarding the speed and latest update on the status was on September.

 

Also, do I automatically get the beta firmware upgrade for the CODA since I signed up for the previous one?

 

Thanks

Re: FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

NBomb
I plan to stick around

Just got a reboot and 2.0.10.14 pushed to my CODA. Eager to hear what's new, but I don't seem to notice any change in performance.