Appreciation for the reply @RogersDave
I have been having the speed degradation on .23 (after not getting it on .19) and after physically separating my modem and router (Airport Extreme 6th gen). There is about 6 ft between them at this point. No other changes were made. I have all my channels and it hasn't changed after two full days.
I just wanted to offer it up as a datapoint for you.
As a bit more info here are my signal levels after the two days. Also note - before moving it I was never able to get channel 24. As you can see all channels are now available. Fingers crossed it stays this way.
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB) 1 591000000 256QAM -1.100 31 40.366 2 657000000 256QAM -2.100 41 40.946 3 597000000 256QAM -1.400 32 40.946 4 363000000 256QAM -0.800 10 40.946 5 369000000 256QAM -0.800 11 40.366 6 375000000 256QAM -1.300 12 40.946 7 381000000 256QAM -1.500 13 40.366 8 387000000 256QAM -1.000 14 40.946 9 393000000 256QAM -0.700 15 40.946 10 399000000 256QAM -0.400 16 40.946 11 405000000 256QAM 0.200 17 40.946 12 411000000 256QAM 0.100 18 40.946 13 417000000 256QAM -0.400 19 40.946 14 423000000 256QAM -0.500 20 40.366 15 429000000 256QAM -0.900 21 40.946 16 435000000 256QAM -1.100 22 40.946 17 441000000 256QAM -0.600 23 40.946 18 447000000 256QAM -0.300 24 40.946 19 567000000 256QAM -2.500 27 40.366 20 573000000 256QAM -2.100 28 40.366 21 579000000 256QAM -1.500 29 40.366 22 585000000 256QAM -1.100 30 40.366 23 555000000 256QAM -1.800 25 40.366 24 561000000 256QAM -2.200 26 40.946 25 603000000 256QAM -1.800 33 40.946 26 357000000 256QAM -0.700 9 40.946 27 615000000 256QAM -1.700 35 40.366 28 621000000 256QAM -1.600 36 40.366 29 633000000 256QAM -1.200 37 40.946 30 639000000 256QAM -1.500 38 40.366 31 645000000 256QAM -1.700 39 40.946 32 651000000 256QAM -2.000 40 40.946
OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv) 0 NA NA NO NO NO NA 1 NA NA NO NO NO NAUpstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth 1 38596000 ATDMA - 64QAM 37.000 3 3200000 2 30596000 ATDMA - 64QAM 33.000 1 6400000 3 23700000 ATDMA - 64QAM 33.000 2 6400000OFDM/OFDMA Overview
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
I have also noticed speed degradation after being bumped to .23, I hope this doesn't last long after losing betwee 200-225Mbps down is pretty significant but not as bad as others have claimed. Still not getting the 50up, dont know if someone here from Rogers on here can look in to that for me.
Here is a Rogers Speed Check completed about 5mins ago (the one with the lower speed) and the speed check run shortly after I received the .23 firmware on the 11th. The difference between the two of them being run is about 17mins apart.
Here are is my recent downstream overview, I am missing channels channels 2-10 but that was also the case on .19 (just disappeared out of the blue one day) but that never affected my performance at all.
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||30596000||ATDMA - 64QAM||35.750||4||6400000|
|2||38596000||ATDMA - 64QAM||38.500||6||3200000|
|3||23700000||ATDMA - 64QAM||35.000||5||6400000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
So far I have rebooted the modem 4 times today.
And with each reboot, the internet issue creeps up faster than before.
Now I am having to reboot every 1 to 2 hours.
I am actually amazed that others are facing the same issue under Rogers- Canada's second largest ISP.
@prateeck7 As Dave mentioned, Hitron, Intel, and CASA are all working 7-days a week to get this problem fixed, and lately they've made some progress, which can possibly lead to a fix in the next few days or by next week. Also, keep in mind that once Dave receives the fix, there are still tests needed to be run in the lab to ensure it's stability which could take another 3-4 days.
Clearly this issue is prioritized, thus other features & fixes have a lower priority untill they fix the speed degradation issue. What's next on the list to be fixed is the UDP issue, which hopefully Intel can fix as soon as possible.
From what I'm seeing I suggest being patient for now, and HOPEFULLY we will have a fix by late next week.
Just to add to @RyzenFX's comment, the CASA CMTS equipment is fairly new, installed during and after last summer. The Intel Puma 7 modems are also new, as in brand new to ISP operations. Intel and Broadcom are in a race to bring their versions of DOCSIS 3.1 modems into operation, and so far, both chipsets are having problems of some type. By now, the CASA CMTS and Hitron's CODA-4582 should have received CableLabs certification, indicating that they are capable of operating with each other, and with other CMTS equipment and modems. Its interesting that the current problem is cropping up after that certification testing. As Dave indicated, this is a high priority item with everyone at the table working to solve the problem. So, as frustrating as it is, all we can do is wait for the solution to be determined and distributed in a firmware update.
Had a weird incident happen tonight - thought another firmware was being pushed out but after the internet came back online I noticed that the firmware was still at .23
Checked my logs, just don't know what to make of it. You can see the first incident happend at 23:10 and this lasted for a good 10-15mins. I did a power reset by pulling the power cord for 60sec. and plugging back in, after it came back online I noticed that I got all 32 channels back (2-10 and 32 were missing for quite some time) and might signal levels slightly improved but I am still getting speeds of 700-750 down on Rogers Speed Check.
|15||02/14/2017 23:10:28||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=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|16||02/14/2017 23:10:55||84020200||warning||Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|17||02/14/2017 23:24:58||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=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|18||02/14/2017 23:25:18||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
|19||02/14/2017 23:49:58||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=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;|
WIth all due respect, aren't some of these issues attributable to lack of proper trials. You'd think that big issues like speed degradation could be identified in a trial.
I realize there's a moving target, as firmware on the modems and backend change, but you have to ask yourself if proper due diligence was performed. Also, whether getting into bed with Hitron again was such a good idea.
I am having to reboot modem every 1 hour now. I am not in a position to be patient. This is not some start up small ISP we are talking about here. This is a big Canadian company- 2nd largest ISP in Canada.
There is no need for me to be patient.
And the supervisor's I have talked to have confirmed me that they have YET to find what is causing the problem.
I was patient for 2 months. That's enough for the company of this size to test my patience.
I had a tech come over yesterday and he basically advised me to try to downgrade to a Ignite or Rocket Modem. You guys won't even let customers do that. To be honest you guys should be crediting clients every month till this issue is resolved - that will force you guys to try to come to a solution quicker. Its a hassle to go upstairs and power cycle my modem every 4-5 hours.. If clients want to leave and break their contract u guys should waive the cancellation fee.