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


@toolcubed wrote:
So your firmware was rolled back to .20? Strange. I can gladly report that after several days with .21, I have not experienced the issue with LAN ports shutting off. When I had the issue, it was daily for me, so this new firmware seems to be working well.

Yup, that was my experience too... until this morning. I'm guessing that the downgrade to .20 happened overnight... and boom, problem is back.

 

I reached out to @CommunityHelps ; I really hope someone can get me back to .21 today otherwise it's going to be a painful weekend (last weekend, one day I had to power cycle the modem FOUR TIMES)... 

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


@RogersDave wrote:

Hi VivienM

 

We have a system that ensures modems are running a current version of firmware. The system periodically checks all modems and performs upgrades/downgrades as required.

 

Normally when modems are running a special version of firmware, we have to exclude them from this system but as one of the first participants in this trial, your modem was missed.

 

I went ahead, initiated an upgrade back to 4.5.8.21T6 and have made sure your modem is being excluded from automatic downgrade.


@RogersDave, you are my hero. Modem just updated itself to 4.5.8.21 and my weekend is saved. Thank you so much! 

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

@VivienM  Glad to hear you've received the .21 update! Hopefully this helps resolve some of the issues you've been having. Since this is a trial version though, from time to time the internet may go down due to updates still being pushed to our modems which will require a factory reset.

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

Gurpreen
I've been here awhile
Guys, i have been noticing the LAN Port issue (every 48 hours) the LAN port is not functional and only a reboot fixes it. As per this thread 4.5.8.21T6 version is being tested to fix it.

I am willing to try it, can someone please tell me where the download link to this firmware is? and some of the steps on how to onboard this onto the modem?

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

cyco
I plan to stick around

You cannot download it yourself nor flash the modem yourself, it has to be done from the coax connection. 

 

You need to send an email to @CommunityHelps with the subject "Rogers Rocket Wi-Fi Modem Firmware Trial"

Regards,

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

Gurpreen
I've been here awhile
@RogersDave how do i get 4.5.8.21T6, i want to try this ASAP. Im experiencing the LAN port issue?

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

Gurpreen
I've been here awhile
Thanks, just sent @CommunityHelps a Private message with the subject you mentioned. Is that it? do i keep checking firmware on the GUI?

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

One of the mods will probably contact you if more info is required.  If not, later today, 4.5.8.21 will load.

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

cyco
I plan to stick around

I'm getting mine pushed right now! 😄

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

hiho
I'm a regular

just wondering if this new firmware upgrade is causing these issues that are worse then before the upgrade..

 

Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 615000000 256QAM -7.200 11 35.084
2 561000000 256QAM -7.800 2 35.084
3 567000000 256QAM -6.800 3 35.595
4 573000000 256QAM -6.200 4 35.780
5 579000000 256QAM -5.100 5 35.595
6 585000000 256QAM -4.500 6 35.780
7 591000000 256QAM -4.800 7 35.780
8 597000000 256QAM -5.200 8 35.595
9 603000000 256QAM -6.400 9 35.595
10 609000000 256QAM -7.000 10 35.595
11 555000000 256QAM -8.100 1 35.084
12 621000000 256QAM -8.000 12 34.926
13 633000000 256QAM -9.000 13 34.926
14 639000000 256QAM -8.700 14 34.484
15 645000000 256QAM -8.400 15 34.926
16 651000000 256QAM -8.100 16 34.926
17 657000000 256QAM -7.300 17 35.595
18 663000000 256QAM -7.200 18 35.780
19 669000000 256QAM -7.000 19 35.780
20 675000000 256QAM -7.000 20 35.780
21 681000000 256QAM -7.600 21 35.595
22 687000000 256QAM -7.800 22 35.595
23 693000000 256QAM -8.100 23 35.780
24 699000000 256QAM -8.300 24 35.595
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID BandWidth
1 23700000 ATDMA - 64QAM 39.750 2 6400000
2 38596000 ATDMA - 64QAM 45.000 3 3200000
3 30596000 ATDMA - 64QAM 41.750 1

6400000

 

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

cyco
I plan to stick around

My modem says it got partial service here, however my ping rates went down by quite a bit 🙂

 

 

         
         
         
         
         
         
         

 

Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 693000000 256QAM -0.400 30 38.983
2 609000000 256QAM 1.500 17 40.366
3 615000000 256QAM 1.400 18 40.946
4 621000000 256QAM 1.100 19 40.366
5 633000000 256QAM 1.300 20 40.366
6 639000000 256QAM 1.400 21 40.366
7 645000000 256QAM 1.200 22 40.366
8 651000000 256QAM 1.000 23 40.366
9 657000000 256QAM 0.800 24 40.366
10 663000000 256QAM 0.000 25 38.983
11 669000000 256QAM -0.600 26 38.983
12 675000000 256QAM -1.300 27 38.983
13 681000000 256QAM -1.600 28 40.366
14 687000000 256QAM -1.200 29 38.983
15 603000000 256QAM 1.400 16 40.366
16 699000000 256QAM 0.800 31 40.366
17 705000000 256QAM 1.400 32 34.484
18 711000000 256QAM 1.600 33 40.366
19 717000000 256QAM 1.700 34 40.366
20 723000000 256QAM 2.100 35 40.366
21 729000000 256QAM 2.100 36 40.946
22 735000000 256QAM 2.300 37 40.366
23 741000000 256QAM 2.500 38 40.366
24 747000000 256QAM 2.300 39 40.946
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID BandWidth
1 23700000 ATDMA - 16QAM 40.000 2 6400000
2 38596000 ATDMA - 16QAM 40.000 3 3200000
3 30596000 ATDMA - 16QAM 40.000 1 6400000

 

 

Does that seems right?

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

Triple_Helix
I plan to stick around

My 4.5.8.21 for CGN3ACSMR signals are very good in my area in Oshawa. I can't see why some would have any - 

1 693000000 256QAM -0.400 30 38.983

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1597000000256QAM8.300238.605
2591000000256QAM8.600138.605
3603000000256QAM8.500338.605
4609000000256QAM8.900438.983
5615000000256QAM9.700538.605
6621000000256QAM9.400638.983
7633000000256QAM7.600738.983
8639000000256QAM7.100838.605
9645000000256QAM6.600938.983
10651000000256QAM6.2001038.605
11657000000256QAM6.1001138.983
12663000000256QAM6.7001238.605
13669000000256QAM7.9001338.983
14675000000256QAM8.4001438.605
15681000000256QAM8.9001538.983
16687000000256QAM9.1001640.366
17693000000256QAM9.7001738.983
18699000000256QAM9.1001838.605
19705000000256QAM8.8001938.983
20711000000256QAM8.2002038.983
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandWidth
130596000ATDMA - 64QAM 39.50026400000
223700000ATDMA - 64QAM 40.25036400000
338596000ATDMA - 64QAM 40.75013200000

 

 

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

The problem isn't the data rate or successful single pings.  The problem is the latency that is showing up in applications and ingame.  If you look at the following ping test to the first node beyond my modem, you can see the second and forth pings, which are high time pings.

 

Pinging 99.239.32.1 with 32 bytes of data:

 

Reply from 99.239.32.1: bytes=32 time=28ms TTL=63
Reply from 99.239.32.1: bytes=32 time=199ms TTL=63
Reply from 99.239.32.1: bytes=32 time=12ms TTL=63
Reply from 99.239.32.1: bytes=32 time=118ms TTL=63
Reply from 99.239.32.1: bytes=32 time=12ms TTL=63

 

Ping statistics for 99.239.32.1:
Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 199ms, Average = 73ms

 

So, with just 5 pings, my average ping time is 73 ms.  In a few more pings, there will be another high time ping or equal or greater time.  My average ping time to the first node historically has been 10 ms.  Now, if I let this run long enough my average ping time will be 20 to 30 ms with visible high time pings.  Consider this, this is the first stop on the road to everywhere, and I'm seeing high return times from that node alone.  Fwiw, I'm not the only one to see this in an application or possibly in a game.  This is seen thru a CGNM-3552 with V4.5.8.21 running gigabit service out to a Casa CMTS.  Its an interesting combination, higher data rates and higher latency.  So something is up, so to speak.  

 

Here are some examples of graphed ping times out to the first node beyond my CGNM-3552:

 

http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3520iEE410A8BE2503DD0

 

 

http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3521i6C10342CB35F4AB4

 

From a couple of days earlier, showing the time distribution:

 

http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3469i5CD04FB9F4FE100B

 

http://communityforums.rogers.com/t5/media/gallerypage/user-id/829158/image-id/3470i601F2DCE974604A8

 

In order to see this run a trace to anywhere.  Then ping the second address in the trace, which is the first node beyond your modem.  Run it for something like 100 or 200 pings and just sit back and watch the ping times as they scroll by.  You will probably see pings in the 20 to 30 ms range, then some high time ping possibly in the 200 to 300 ms timeframe.  If you do this, please let me know what your results are.  If by some chance you have an average in the 10 ms range, I'll probably ask you to send me a copy of the whole ping test so that I can have a look at it, ping by ping.  The maximum number of pings that the command window will hold, so that you can copy it, is 293, despite the fact that the test itself might be much longer.  

 

Just as an aside, your signal levels are in spec, but, personal opinion the downstream levels are pretty high.  They should be down at 0 dBmV.  But, if they aren't presenting any issues at this time, better to let sleeping dogs lie.  Over the years that will come down as the external cable ages.

 

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

kool saw this post and thought i would  give it a go...think maybe i might have a problem....did the tracert then used the 2nd ip to do a ping with..

 

ping 99.253.232.11

Pinging 99.253.232.11 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 99.253.232.11:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping 99.253.232.11 -t

Pinging 99.253.232.11 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 99.253.232.11:
Packets: Sent = 44, Received = 0, Lost = 44 (100% loss),

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

Datalink
Resident Expert
Resident Expert

My guess is that you're on a Cisco CMTS at the moment, which is probably set to not respond to pings.  

When you have time, can you log into your modem, navigate to the STATUS ...... DOCSIS EVENT page and have a look for one of the following sequences:

a. CMTS-MAC=00:17:10 which indicates that you are connected to a Casa Systems Cable Modem Termination System (CMTS), or;
b. any of the following which indicates that you are connected to a Cisco Systems CMTS.

1. CMTS-MAC=00:05:00
2. CMTS-MAC=00:12:43
3. CMTS-MAC=00:14:f1
4. CMTS-MAC=00:1f:ca

5. CMTS-MAC=e0:2f:6d
 

Please let me know what CMTS you're on, Cisco or Casa?

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

Ok, can you delete the events log as it has your modem MAC address in it.  

 

You're on a Casa CMTS.  Its interesting that pinging the second IP fails.  What happens when you ping something usual, like google.ca or google.com?

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

 

ping google.ca

Pinging google.ca [2607:f8b0:400b:80b::2003] with 32 bytes of data:
Reply from 2607:f8b0:400b:80b::2003: time=15ms
Reply from 2607:f8b0:400b:80b::2003: time=16ms
Reply from 2607:f8b0:400b:80b::2003: time=15ms
Reply from 2607:f8b0:400b:80b::2003: time=30ms

Ping statistics for 2607:f8b0:400b:80b::2003:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 30ms, Average = 19ms

 

 

 

ping rogers.ca

Pinging rogers.ca [207.245.252.27] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.245.252.27:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

ping google.com

Pinging google.com [2607:f8b0:400b:80a::200e] with 32 bytes of data:
Reply from 2607:f8b0:400b:80a::200e: time=12ms
Reply from 2607:f8b0:400b:80a::200e: time=12ms
Reply from 2607:f8b0:400b:80a::200e: time=17ms
Reply from 2607:f8b0:400b:80a::200e: time=13ms

Ping statistics for 2607:f8b0:400b:80a::200e:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 17ms, Average = 13ms

 

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

Datalink
Resident Expert
Resident Expert

Thats a little strange.  The IPV4 address times out but the IPV6 addresses work.  Try this.

 

tracert -6 ipv6.google.com

 

Then, using the second IP address, ping that address.  It should return a ping.  You can force the use of IPV6 by using "-6" in the command.

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

yup now i get ping 🙂

 

ping 2607:f798:804:2d2::1 -t

Pinging 2607:f798:804:2d2::1 with 32 bytes of data:
Reply from 2607:f798:804:2d2::1: time=28ms
Reply from 2607:f798:804:2d2::1: time=29ms
Reply from 2607:f798:804:2d2::1: time=19ms
Reply from 2607:f798:804:2d2::1: time=51ms
Reply from 2607:f798:804:2d2::1: time=16ms
Reply from 2607:f798:804:2d2::1: time=16ms
Reply from 2607:f798:804:2d2::1: time=16ms
Reply from 2607:f798:804:2d2::1: time=13ms
Reply from 2607:f798:804:2d2::1: time=12ms
Reply from 2607:f798:804:2d2::1: time=14ms
Reply from 2607:f798:804:2d2::1: time=12ms
Reply from 2607:f798:804:2d2::1: time=16ms
Reply from 2607:f798:804:2d2::1: time=16ms
Reply from 2607:f798:804:2d2::1: time=14ms
Reply from 2607:f798:804:2d2::1: time=12ms
Reply from 2607:f798:804:2d2::1: time=13ms
Reply from 2607:f798:804:2d2::1: time=14ms
Reply from 2607:f798:804:2d2::1: time=11ms
Reply from 2607:f798:804:2d2::1: time=12ms
Reply from 2607:f798:804:2d2::1: time=14ms
Reply from 2607:f798:804:2d2::1: time=12ms
Reply from 2607:f798:804:2d2::1: time=21ms
Reply from 2607:f798:804:2d2::1: time=13ms
Reply from 2607:f798:804:2d2::1: time=12ms
Reply from 2607:f798:804:2d2::1: time=15ms
Reply from 2607:f798:804:2d2::1: time=14ms
Reply from 2607:f798:804:2d2::1: time=16ms
Reply from 2607:f798:804:2d2::1: time=18ms
Reply from 2607:f798:804:2d2::1: time=22ms
Reply from 2607:f798:804:2d2::1: time=22ms
Reply from 2607:f798:804:2d2::1: time=17ms
Reply from 2607:f798:804:2d2::1: time=13ms
Reply from 2607:f798:804:2d2::1: time=21ms
Reply from 2607:f798:804:2d2::1: time=17ms
Reply from 2607:f798:804:2d2::1: time=22ms

Ping statistics for 2607:f798:804:2d2::1:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 51ms, Average = 17ms

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

Datalink
Resident Expert
Resident Expert

looks good, can you do the same, running the test for 250 pings and post just the end results.  I might ask you to send me the whole test and a couple of other bits of data.

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

Ping statistics for 2607:f798:804:2d2::1:
Packets: Sent = 250, Received = 250, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 223ms, Average = 20ms