FEEDBACK - Rogers Rocket Wi-Fi Modem Firmware Trial

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
I Plan to Stick Around
Posts: 16

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

@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.

I Plan to Stick Around
Posts: 98

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

@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?

I Plan to Stick Around
Posts: 43

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

@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.

 

 

I Plan to Stick Around
Posts: 124

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

Since the weekend my speeds have gone back up to 300 mbps. I am fairly certain that this is the best I will get, whatever firmware I'm on now is what I want to stay at until official release for future firmware is released. With that said how do I opt out of testing beta firmware?
Resident Expert
Resident Expert
Posts: 6,052

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?



Network Architect
Network Architect
Posts: 611

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.

I Plan to Stick Around
Posts: 43

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

@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?

I Plan to Stick Around
Posts: 11

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

Hello @RogersDave,

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

 

Patrick

I'm Here A Lot
Posts: 7

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;

I'm a Reliable Contributor
Posts: 579

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

@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