CODA-4582 - Open Issues for Investigation

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: 98

Re: CODA-4582 - Open Issues for Investigation


@timfolkins wrote:

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 IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1591000000256QAM-1.1003140.366
2657000000256QAM-2.1004140.946
3597000000256QAM-1.4003240.946
4363000000256QAM-0.8001040.946
5369000000256QAM-0.8001140.366
6375000000256QAM-1.3001240.946
7381000000256QAM-1.5001340.366
8387000000256QAM-1.0001440.946
9393000000256QAM-0.7001540.946
10399000000256QAM-0.4001640.946
11405000000256QAM0.2001740.946
12411000000256QAM0.1001840.946
13417000000256QAM-0.4001940.946
14423000000256QAM-0.5002040.366
15429000000256QAM-0.9002140.946
16435000000256QAM-1.1002240.946
17441000000256QAM-0.6002340.946
18447000000256QAM-0.3002440.946
19567000000256QAM-2.5002740.366
20573000000256QAM-2.1002840.366
21579000000256QAM-1.5002940.366
22585000000256QAM-1.1003040.366
23555000000256QAM-1.8002540.366
24561000000256QAM-2.2002640.946
25603000000256QAM-1.8003340.946
26357000000256QAM-0.700940.946
27615000000256QAM-1.7003540.366
28621000000256QAM-1.6003640.366
29633000000256QAM-1.2003740.946
30639000000256QAM-1.5003840.366
31645000000256QAM-1.7003940.946
32651000000256QAM-2.0004040.946

 

OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
1NANANONONONA
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
138596000ATDMA - 64QAM37.00033200000
230596000ATDMA - 64QAM33.00016400000
323700000ATDMA - 64QAM33.00026400000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.00004K

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.

Screen Shot 2017-02-14 at 21.37.59.png

 

Screen Shot 2017-02-11 at 21.20.25.png

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.

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1591000000256QAM5.400738.983
11621000000256QAM5.3001238.605
12633000000256QAM6.3001335.780
13639000000256QAM7.4001437.636
14645000000256QAM7.9001540.366
15651000000256QAM7.9001637.636
16657000000256QAM7.8001738.983
17663000000256QAM7.9001838.983
18669000000256QAM7.8001938.605
19675000000256QAM8.1002038.605
20681000000256QAM8.4002138.983
21687000000256QAM8.1002238.983
22693000000256QAM7.9002338.983
23699000000256QAM7.0002438.605
24705000000256QAM5.9002540.366
25711000000256QAM5.6002638.983
26717000000256QAM6.1002738.605
27723000000256QAM6.8002838.983
28825000000256QAM3.7002938.605
29831000000256QAM3.1003038.983
30837000000256QAM2.3003137.636
31843000000256QAM1.3003238.605
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
04K275600000YESYESYES4.800003
1NANANONONONA
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
130596000ATDMA - 64QAM35.75046400000
238596000ATDMA - 64QAM38.50063200000
323700000ATDMA - 64QAM35.00056400000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.00004K
Highlighted
I Plan to Stick Around
Posts: 24

Re: CODA-4582 - Open Issues for Investigation

2.0.10.13, wired to PC

I Plan to Stick Around
Posts: 85

Re: CODA-4582 - Open Issues for Investigation

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.

I Plan to Stick Around
Posts: 24

Re: CODA-4582 - Open Issues for Investigation

2.0.10.13, wired to PC

 

Untitled-1.jpg

I'm a Reliable Contributor
Posts: 581

Re: CODA-4582 - Open Issues for Investigation

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

 

 

 

Resident Expert
Resident Expert
Posts: 6,291

Re: CODA-4582 - Open Issues for Investigation

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.  



I Plan to Stick Around
Posts: 98

Re: CODA-4582 - Open Issues for Investigation

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.

 

1502/14/2017 23:10:2882000400criticalReceived 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;
1602/14/2017 23:10:5584020200warningLost 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;
1702/14/2017 23:24:5882000400criticalReceived 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;
1802/14/2017 23:25:1882000200criticalNo 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;
1902/14/2017 23:49:5882000400criticalReceived 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;
I Plan to Stick Around
Posts: 75

Re: CODA-4582 - Open Issues for Investigation

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 Plan to Stick Around
Posts: 85

Re: CODA-4582 - Open Issues for Investigation

Patience?

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've Been Around
Posts: 1

Re: CODA-4582 - Open Issues for Investigation

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.