05-31-2016 08:42 AM - last edited on 03-14-2018 04:23 PM by RogersRoland
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.
06-15-2017 11:41 PM - edited 06-15-2017 11:43 PM
@tester2013 what version firmware is loaded on the modem, V2.0.10.27 or V2.0.10.29? Is the downstream LED showing a light blue for DOCSIS 3.1 operation, or the same blue colour as the upstream for DOCSIS 3.0 operation? Just wondering if this is a DOCSIS issue or a user display issue?
06-16-2017 12:02 AM - last edited on 06-16-2017 08:02 AM by RogersPrasana
@Datalink I am on .27 and up arrow is CYAN and the down arrow is blue
Was speaking with the Rogers chat rep and he got upset at me for copying and pasting the DOCSIS WAN log..told me he doesnt know what it means and it doesnt make sense...I was like "how are you a Rogers tech support?"
06-16-2017 12:09 AM - edited 06-16-2017 12:15 AM
Actually the LED colours are reversed, at least according to Hitron. DOCSIS 3.1 operation is supposed to be Cyan, looks light blue to me, DOCSIS 3.0 is the normal blue. Currently, only the downstream path is DOSCIS 3.1, Upstream is still DOCSIS 3.0. So, am I assuming correctly then that the modem is still running DOCSIS 3.1 as seen by the different Downstream/Upstream colours?
Have you tried a modem restart, as in pull the power, wait for 10 to 15 seconds and then reapply power? Then log into the modem to check the DOCSIS WAN tab?
Are you running any VPNs by chance?
06-16-2017 12:16 AM - edited 06-16-2017 12:17 AM
@Datalink Mine is cyan. Pulling the power would solve it for sure but will come back to the same issue afterwards...
No VPNS present,
06-16-2017 12:20 AM
06-16-2017 12:24 AM
@Datalink Lots of errors (16 errors) on the DOCSIS Event Log..I was going to copy and paste it but it has my MAC on it..
06-16-2017 12:28 AM
06-16-2017 12:34 AM
1 | 01/01/1970 00:01:05 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=xxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
2 | 06/12/2017 21:03:29 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=axxx.xxx.xxx.xxx ;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
3 | 06/12/2017 21:03:39 | 69010200 | notice | SW Download INIT - Via Config file bac101000106a84e3fcee610 |
4 | 06/12/2017 21:04:28 | 69011200 | notice | SW download Successful - Via Config file |
5 | 06/12/2017 21:06:18 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
6 | 06/12/2017 21:34:50 | 68010300 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xxx.xxx.xxx.xxx ;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
7 | 06/13/2017 09:20:38 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=xxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
8 | 06/13/2017 16:34:51 | 68010300 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
9 | 06/13/2017 23:41:59 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
10 | 06/15/2017 10:35:47 | 84020200 | warning | Lost MDD Timeout;CM-MAC=axxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
11 | 06/15/2017 11:38:27 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=xxx.xxx.xxx.xxx 10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
12 | 06/15/2017 11:38:39 | 84000500 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
13 | 06/15/2017 11:39:07 | 82000400 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xxx.xxx.xxx.xxx :10;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
14 | 06/15/2017 11:40:15 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=xxx.xxx.xxx.xxx ;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
15 | 06/15/2017 11:40:26 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=1 post cfg file MIMO=-1;CM-MAC=xxx.xxx.xxx.xxx ;CMTS-MAC=0xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
16 | 06/15/2017 11:40:48 | 84000700 | warning | RCS Partial Service;CM-MAC=xxx.xxx.xxx.xxx ;CMTS-MAC=xxx.xxx.xxx.xxx ;CM-QOS=1.1;CM-VER=3.1; |
06-16-2017 12:40 AM - edited 06-16-2017 12:42 AM
Thats actually not bad. I generally don't get too excited over the log entries unless I can tie a log entry to a modem failure or reboot. I've seen a couple of MDD Timeouts cause reboots, but then I've seen MDD Timeouts with no indication of an issue from the modem.
A good portion of those log entries are spaced out, indicating on occasional issue. Yesterday morning was an exception, with a string of alerts. Are you seeing any modem failures or problematic data rates?
06-16-2017 12:42 AM
No modem failures as of yet...but My upload has dropped from 50mbps to about 36-40..asked the Rogers rep and he told me because 50 mbps was not consistent so they are keeping it between 35-50 mbps..
Other than that I dont feel that much of a difference in speed coming from the CGN 3552
06-16-2017 12:51 AM
06-16-2017 04:12 AM
@Datalink Resetting it has bought back the missing DOCSIS 3.1 settings
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 615000000 | 256QAM | 0.000 | 11 | 38.605 |
2 | 849000000 | 256QAM | -1.700 | 2 | 37.356 |
3 | 855000000 | 256QAM | 1.800 | 3 | 37.636 |
4 | 861000000 | 256QAM | 1.900 | 4 | 37.636 |
5 | 579000000 | 256QAM | 0.600 | 5 | 38.983 |
6 | 585000000 | 256QAM | -0.700 | 6 | 38.605 |
7 | 591000000 | 256QAM | 0.000 | 7 | 38.605 |
8 | 597000000 | 256QAM | -0.300 | 8 | 38.983 |
9 | 603000000 | 256QAM | -0.900 | 9 | 37.636 |
10 | 609000000 | 256QAM | -0.300 | 10 | 38.605 |
11 | 303000000 | 256QAM | 0.500 | 1 | 38.605 |
12 | 621000000 | 256QAM | 0.600 | 12 | 38.605 |
13 | 633000000 | 256QAM | -1.200 | 13 | 37.636 |
14 | 639000000 | 256QAM | -0.100 | 14 | 37.636 |
15 | 645000000 | 256QAM | -1.100 | 15 | 38.605 |
16 | 651000000 | 256QAM | 0.200 | 16 | 38.605 |
17 | 657000000 | 256QAM | -0.700 | 17 | 37.636 |
18 | 663000000 | 256QAM | -0.300 | 18 | 37.356 |
19 | 669000000 | 256QAM | 0.200 | 19 | 37.636 |
20 | 675000000 | 256QAM | -1.100 | 20 | 38.983 |
21 | 681000000 | 256QAM | 1.100 | 21 | 38.983 |
22 | 687000000 | 256QAM | 0.000 | 22 | 38.605 |
23 | 693000000 | 256QAM | -0.500 | 23 | 37.636 |
24 | 699000000 | 256QAM | 0.300 | 24 | 38.605 |
25 | 705000000 | 256QAM | -1.300 | 25 | 38.605 |
26 | 711000000 | 256QAM | -0.300 | 26 | 38.605 |
27 | 717000000 | 256QAM | -2.100 | 27 | 37.636 |
28 | 723000000 | 256QAM | -3.800 | 28 | 37.356 |
29 | 825000000 | 256QAM | -2.400 | 29 | 37.636 |
30 | 831000000 | 256QAM | -3.300 | 30 | 37.636 |
31 | 837000000 | 256QAM | -3.200 | 31 | 37.636 |
32 | 843000000 | 256QAM | -1.700 | 32 | 37.636 |
Receiver | FFT type | Subcarr 0 Frequency(MHz) | PLC locked | NCP locked | MDC1 locked | PLC power(dBmv) |
0 | NA | NA | NO | NO | NO | NA |
1 | 4K | 275600000 | YES | YES | YES | 1.099998 |
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Bandwidth |
1 | 30596000 | ATDMA - 64QAM | 35.500 | 4 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 39.000 | 6 | 3200000 |
3 | 23700000 | ATDMA - 64QAM | 35.500 | 5 | 6400000 |
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 |
06-19-2017 06:58 PM
Hello Everyone,
I have the version .29 firmware pushed on my CODA modem and notice an option to enable MOCA which is set to Disabled. What exactly does this do and should I enable it?
I do have Rogers Whole Home PVR setup so I am not sure if this impacts this.
Thanks
06-19-2017 07:15 PM - edited 06-19-2017 07:17 PM
@Alex4161 leave it disabled for now. MoCA stands for Multimedia over Cable Alliance. That organization publishes communications standards for running networks over the cable network that is used in your home. That requires an ethernet to MoCA adapter at both ends of the cable network. When its running, it would allow you to run ethernet over cable, allowing you to use the intra/internet in locations of the home where there is no ethernet cabling. That also includes running wifi in remote locations of the home. You would only enable that if you had a MoCA filter installed on your incoming cable to prevent leakage of MoCA data outside of the home or ingress to your home from the outside cable network, and if you had another MoCA adapter set up somewhere in your home. This also requires a MoCA qualified splitter or amplifier on the cable network. Whole Home PVR also uses the MoCA network, but the two systems should be able to co-exist.
06-19-2017 07:29 PM
06-19-2017 07:35 PM - edited 06-19-2017 07:36 PM
@AOD999 can you post the STATUS .... DOCSIS WAN downstream and upstream tables? The copy and paste process will paste in the text contents of the tables.
06-19-2017 07:38 PM
06-20-2017 08:29 AM
06-20-2017 07:08 PM
So your upstream and downstream lights are both dark blue?
Where are you located? The entire cable footprint should be running DOCSIS 3.1 (light blue on downstream).
I would call into Rogers and ask them to check your line, you should be using DOCSIS 3.1
If your signal is weak/borderline the modem could be trying to keep a connection using DOCSIS 3.
06-20-2017 07:15 PM
@gp-se wrote:So your upstream and downstream lights are both dark blue?
Where are you located? The entire cable footprint should be running DOCSIS 3.1 (light blue on downstream).
I would call into Rogers and ask them to check your line, you should be using DOCSIS 3.1
If your signal is weak/borderline the modem could be trying to keep a connection using DOCSIS 3.
It is 3.1 with the new modem. old modem would lose it all the time before i swapped it out. Both modems have the weird UI corruption where none of the tabs within the modem can be reached.
06-20-2017 07:53 PM
@AOD999 wrote:
@gp-se wrote:
So your upstream and downstream lights are both dark blue?
Where are you located? The entire cable footprint should be running DOCSIS 3.1 (light blue on downstream).
I would call into Rogers and ask them to check your line, you should be using DOCSIS 3.1
If your signal is weak/borderline the modem could be trying to keep a connection using DOCSIS 3.
It is 3.1 with the new modem. old modem would lose it all the time before i swapped it out. Both modems have the weird UI corruption where none of the tabs within the modem can be reached.
That fact that two modems have GUI corruption is odd. Have you tried to log into the modem using a different browser/computer/mobile phone