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'm a Reliable Contributor
Posts: 610

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

Rogers needs to step up their game, because Bell is aggressively deploying FTTH. Rogers is a good alternative to dsl and FTTN but can't compete with FTTH. Rogers will need to go full fibre sooner than later. And I wish they do so because it's nice to have competition , I don't want bell to have the monopoly of internet but I fear it might happen within the next 5-10 years.

I Plan to Stick Around
Posts: 33

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

Totally agree with all you guys. And i put a lot of blame on the employees that's running this "so called" community of willing customers hiding and keep lying to us with no answers or transparency at all. @RogersDave WAS THE BEST THING THAT EVER HAPPENED TO ROGERS AND THE REASON WHY MOST OF US ARE STILL HERE! I CANT EVEN WATCH A 4K YOUTUBE VIDEO ON MY DEVICE AFTER YEARS AND I AM PAYING FOR GIGABIT! And the funny thing is a 50 mbps from 3rd party dsl can.  #THE FRUSTARTION IS REAL!

I Plan to Stick Around
Posts: 125

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

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.
I'm a Reliable Contributor
Posts: 186

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

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

I Plan to Stick Around
Posts: 19

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

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.

Highlighted
Product Manager
Product Manager
Posts: 21

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

 

 

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

I Plan to Stick Around
Posts: 54

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

OK, what's going on? 

 

1510/23/2018 06:45:1369010100noticeSW Download INIT - Via NMS
1610/23/2018 06:45:4169011100noticeSW download Successful - Via NMS
1710/23/2018 11:47:1390000000warningMIMO 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;
1810/23/2018 09:37:2869010100noticeSW Download INIT - Via NMS
1910/23/2018 09:37:5769011100noticeSW download Successful - Via NMS
2010/23/2018 14:39:3590000000warningMIMO 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 Version2.0.10.36T5
I've Been Here Awhile
Posts: 2

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

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)

I Plan to Stick Around
Posts: 54

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

And again?

 

1510/23/2018 14:45:1969010100noticeSW Download INIT - Via NMS
1610/23/2018 14:45:4869011100noticeSW download Successful - Via NMS
1710/23/2018 19:47:2690000000warningMIMO 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;
1810/23/2018 19:47:3869010100noticeSW Download INIT - Via NMS
1910/23/2018 14:48:1969011100noticeSW download Successful - Via NMS
2010/23/2018 19:50:0190000000warningMIMO 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 Version2.0.10.36T5
 
I Plan to Stick Around
Posts: 315

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


@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 Version2.0.10.36T6

 

Microsoft® MVP Windows Insider - Windows Security