CODA-4582 - Open Issues for Investigation

[RogersDave]

*** This post was last edited May 2, 2017 ***

Good morning Community,

As I mentioned in a post two days ago, we have received the next firmware 2.0.10.20 from Hitron. We are currently running initial testing on this version and will push it out to participants in the firmware trial program as soon as it passes initial testing.

However, while running these tests, we discovered abnormal behavior with ICMP and are awaiting feedback from Hitron today to asses how this will be addressed. As soon as I this is confirmed, I’ll update the change log with the correct version information and start pushing it out.

In parallel, we are still working on the following high priority items. In some cases below, I requested affected customers to reach out to me via private message. If you do so, please include your modem MAC address in the subject line (even if we exchange messages daily) as there are a lot of you reaching out to me daily 🙂

UDP Packet Loss

The investigation for what has been reported as UDP packet loss is still ongoing. We have deployed a probe at one fellow forum member on both a CODA-4582 and a CGNM-3552 to collect additional data. We are actively working with Hitron and Intel on the results observed.

Based on what we know so far, in most instances UDP packet loss is coupled with higher uplink usage in the area. Although the impact is noticeable in specific logs (League of Legends), the root cause for the perceivable impact (while playing) is likely related to bufferbloat (see next issue).

Bufferbloat

When comparing the performance of a CODA-4582 to a CGNM-3552 in the same network conditions, the CODA-4582 consistently reports higher bufferbloat when tested on DSLReports.

Update April 12: The solution for this problem will come in two folds. It will require a change in software which will possibly be included in 2.0.10.27 but more likely in 2.0.10.28 and a change in network configuration.

The network configuration change is not compatible with the current firmware so this change will only come after a vast majority of the modems are running the new code. We are however looking at a way to make the change only for specific modems to support testing in the community.

Update April 22: This problem seems resolved in firmware 2.0.10.27

5 GHz WiFi Low range for channels 36 to 48

Lower WiFi channels on the modem have a much smaller range. This is due in part to the limit imposed by Industry Canada to maximum transmit power.

Furthermore, the current automatic channel selection (auto mode) tends to select the lower channels when in similar load conditions.

Workaround: manually select higher channels (149-153-157-161)

Update April 22: The channel selection algorithm has been improved in firmware 2.0.10.27

Loss of OFDM Channel Lock

Under some RF conditions, the modem fails to lock properly on the OFDM channel. This typically result in variable performance.

Update April 12: This problem is resolved in 2.0.10.26T2

List of connected device does not get fully populated

This is a known issue that has been tracked since firmware 2.0.10.13. We are making improvements at every firmware but it is not a perfect system.

The situation is worst after a reboot or firmware upgrade as the list gets reset and must be repopulated as devices renew their DHCP lease.

NAT Loopback not working for wired clients

When setting up port forwarding to an internal server, it is possible for a client on WiFi to reach the server using the external IP/port. If the client is on a wired interface, it doesn't work.

Update April 12: This problem is resolved in 2.0.10.26T2 (not confirmed)

LAN Counters not working

Some customers reported that LAN counters (especially in bridge mode) are reporting inaccurate values.

This problem has been reported to Hitron for investigation.

Unexpected modem reboot

Some customers reported their modem reboots unexpectedly. We have also seen this behavior in our lab.

Update April 12: This problem is resolved in 2.0.10.26T2

Missing SC-QAM Channels

After a reboot, some modems are missing SC-QAM channels. A fix has been implemented in 2.0.10.26T2 to address this behavior but it has not corrected all scenarios.

Investigation continues with Hitron.

WiFi Survey

The WiFi Survey functionality in firmware 2.0.10.26T2 (and possibly before) reports incorrect SSID names.

Guest Network

When connecting to the Guest Network, an error message is displayed "only allow DHCP client to use this wireless".  This has been reported in firmware 2.0.10.26T2.

Update April 22: This issue has been resolved in firmware 2.0.10.27

Update May 2: It seems this issue is not fully resolved and still experienced by some users

---

Future Planned Improvements

The following are items that we are working on in parallel of the above.

• Improvement in WiFi speeds
• Improvement in latency / bufferbloat

Dave

*Edited Labels*

[Datalink]

Ok, the only question is whether or not there is any restriction for gigibit plans that ony allows the CODA-4582.  The CGNM-3552 is the next candidate for that plan but again, what restrictions are there, if any?  The Rogers store staff should be able to answer that. 

Can you log into the modem, navigate to the STATUS .... DOCSIS WAN page, copy the downstream and upstream tables and paste them into a post, just to see where the signal levels are?  That copy and paste process will paste in the text data from the tables.  If the modem and router are close together, even with the additional shielding over the Docsis Tuner, I would run an experiment, and that is to shut down the 2.4 Ghz on the router and then reboot the modem to see what impact if any that the router wifi might have on the modem.

[arrago]

my signals have been great since the black dot version

[gp-se]

---

@StephKitty wrote:

@gp-se Thanks for the help.  I didn't realize that I was missing so many of these channels.  A Rogers tech came over about an hour ago to swap out the modem and make sure my signals were okay.

I now have the Black Dot version of the modem from Rogers which seems to have fixed the issue so far.  One thing I did notice though is that my firmware is only 2.0.10.13 and has not been updated to the latest firmware it should be on which i believe is 2.0.10.19.  Not a huge deal I guess since it's working so far, i'll just wait for it to be pushed to the latest firmware eventually.  

---

I'm glad the modem swap fixed the issue, after 24-48 hours you'll be on the latest firmware (.19-public, .23-beta)

[timfolkins]

Annnnnd... like clockwork on .23 less than 6 hours after a reboot the previously stable signal strength jumps up to +10's. and download speed goes in the crapper.

Pppplllllllleeease put me back to .19... or pop in with some sort of update.

This is ugly.

I will add that this was after a factory reset as well.

[lethalsniper]

Don't worry your not the only guy with your signal levels rising since firmwares update Also on .23

[Mayoo]

Ok.. So i have narrowed down the issue and found out my speeds are back to 900Mbps down / 40mbps UP between 1.30AM - 8.30AM everyday !!! 

So when i run Speed test at 1.30AM - 8.30AM every day, my speeds are back to 900mbps/40mbps up while rest of the hours its stuck at 400Mbps .. 

Is this due to Network Congestion ? My area is still  on DOCSIS 3.0 

[Alex4161]

@Mayoo

I would suggest that you call Rogers Support and open a ticket. They can contact their Network group to monitor the issue and make the necessary changes. I had a packet loss/performance issue last month and after a few weeks the ticket was closed and I no longer experience this problem.

[lethalsniper]

@Datalinkso my modem just rebooted on its own once again so after It came back on I logged in to modem and I noticed the WAN Time was reseted but it's showing modem LAN time has been on for 1 day and 1 hr

Updated modem just rebooted again this time wan and Lan time is the same , wonder if theres any work being done

SYNC Timing Synchronization failure - Loss of Sync

DHCP RENEW WARNING - Field invalid in response v4 option

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

B-INIT-RNG Failure - Retries exceeded

MIMO Event MIMO: Stored

No Ranging Response received - T3 time-out

DHCP FAILED

those are just some of error codes i,m getting

[Adva]

Is there a way of telling if my area is 3.1 active?

I receieve Rogers Fibre to the Home in a new housing area. Does that guarantee 3.1 or not?

thanks

[lethalsniper]

@RogersDave

my modem r rebooted on its own once again so after It came back on I logged in to modem and I noticed the WAN Time was reseted but it's showing modem LAN time has been on for 1 day and 1 hr

then maybe after 40 min modem rebooted again this time wan and Lan time back to 0 , is there any work being done to the modem or noise issues or node, somthing must be going on because it also so happ yesterday around the same time ? which i,m on the23 trial firmware and it also been happening last week so basically it's been happing 23 firmware, should I swapp the modem out @RogersDave

SYNC Timing Synchronization failure - Loss of Sync
DHCP RENEW WARNING - Field invalid in response v4 option
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
B-INIT-RNG Failure - Retries exceeded
MIMO Event MIMO: Stored
No Ranging Response received - T3 time-out
DHCP FAILED
those are just some of error codes i,m getting

[Jeffj]

---

@lethalsniper wrote:
@RogersDave

my modem r rebooted on its own once again so after It came back on I logged in to modem and I noticed the WAN Time was reseted but it's showing modem LAN time has been on for 1 day and 1 hr

then maybe after 40 min modem rebooted again this time wan and Lan time back to 0 , is there any work being done to the modem or noise issues or node, somthing must be going on because it also so happ yesterday around the same time ? which i,m on the23 trial firmware and it also been happening last week so basically it's been happing 23 firmware, should I swapp the modem out @RogersDave

SYNC Timing Synchronization failure - Loss of Sync
DHCP RENEW WARNING - Field invalid in response v4 option
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
B-INIT-RNG Failure - Retries exceeded
MIMO Event MIMO: Stored
No Ranging Response received - T3 time-out
DHCP FAILED
those are just some of error codes i,m getting

---

I am getting these exact same issues all started on .23 and all the same errors in my logs. im also missing channel 13 now it comes back after reboot but i cant get over 100mbps down and channel 13 drops again. 

[lethalsniper]

Yea don't know if I should swapp the modem or just wait for Rogersdave to reply , the coda I have is the one with the black round sticker is yours ?

[Jeffj]

Mine is not a black dot. I am also in your boat waiting for @RogersDave to advise. 

[gp-se]

Since you have an original non-black dot Modem I would suggest swapping it out. 

[lethalsniper]

What about me ? I have the back dot sticker modem I'm having issues

[Jeffj]

---

@gp-se wrote:

Since you have an original non-black dot Modem I would suggest swapping it out. 

---

I'll wait for dave, as he has looked at my modem multiple times and said i dont suffer any issues from 2.4ghz interference.  Let him have a look at this modem before i swap it.

[timfolkins]

Unfortunately the time between the reboot and speed degrading (signal strength) seems to be getting shorter. It was around 6h for me. Tonight it got bad after only 2h.

[NBomb]

So I'm having a REALLY bad time right now.

Speed tests over 4 different devices, wired, wireless, mobile, PC, Mac, different browsers, all giving me between .8mbit and 18mbit down, 12-25mbit up at the moment.

Getting ~2-4% packet loss to the last hop on a pingplot to google.com, although I don't know that that's related.

On every speed test the graph is SUPER erratic. Generally it will spike up up at the beginning and dip way down to sub-1mbit for the duration, except in one case where it went @ 0mbit until ~70% of the way through and jumped up to 3mbit or so.

A tech was out here last weekend, replaced every coax connector in the house, and said the modem and/or connection was otherwise fine. This issue started maybe 1.5-2 wks ago.

I'm including my signal levels although I feel like they're fine, on the off chance I'm missing something. D3.1 seems to have been 'enabled' in my area recently as well, if that means anything.

Thanks for your patience/help!

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Signal noise ratio (dB)
1	645000000	256QAM	-1.000	15	40.946
2	561000000	256QAM	-1.700	2	40.946
3	567000000	256QAM	-1.900	3	40.946
4	573000000	256QAM	-2.200	4	40.366
5	579000000	256QAM	-2.700	5	40.366
6	585000000	256QAM	-2.600	6	40.366
7	591000000	256QAM	-2.500	7	40.366
8	597000000	256QAM	-3.000	8	40.366
9	603000000	256QAM	-3.400	9	38.983
10	609000000	256QAM	-2.700	10	40.366
11	615000000	256QAM	-3.000	11	40.366
12	621000000	256QAM	-2.500	12	40.366
13	633000000	256QAM	-2.100	13	40.366
14	639000000	256QAM	-1.500	14	40.366
15	555000000	256QAM	-1.800	1	40.366
16	651000000	256QAM	-1.500	16	40.366
17	657000000	256QAM	-1.200	17	40.946
18	663000000	256QAM	-0.900	18	40.366
19	669000000	256QAM	-0.700	19	40.946
20	675000000	256QAM	-0.900	20	40.946
21	681000000	256QAM	-1.100	21	40.366
22	687000000	256QAM	-1.000	22	40.366
23	693000000	256QAM	-1.100	23	40.946
24	699000000	256QAM	-1.000	24	40.946
25	705000000	256QAM	-1.400	25	40.946
26	711000000	256QAM	-1.500	26	40.946
27	717000000	256QAM	-2.100	27	40.366
28	723000000	256QAM	-2.000	28	40.366
29	825000000	256QAM	-2.400	29	40.946
30	831000000	256QAM	-2.300	30	40.366
31	837000000	256QAM	-2.500	31	40.366
32	843000000	256QAM	-3.200	32	40.366

[Datalink]

@NBomb what modem do you have as indicated by the product sticker at the back of the modem?  Can you post the rest of the signal data, including the OFDM data if you have a CODA-4582 and the upstream data along with the upstream OFDM data (currently inactive)

[NBomb]

Hi Datalink, thanks for looking in. I'm on .19 w/ the CODA non-dot.

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	4K	275600000	YES	YES	YES	-2.000000

Upstream Overview

Port ID	Frequency (MHz)	Modulation	Signal strength (dBmV)	Channel ID	Bandwidth
1	38595707	ATDMA - 64QAM	43.000	3	3200000
2	30596000	ATDMA - 64QAM	39.250	1	6400000
3	23700000	ATDMA - 64QAM	41.000	2	6400000

OFDM/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

[Datalink]

There seems to be a common thread to some of these complaints.  Docsic 3.1 goes active and the data rates take a dive and/or Docsis 3.0 channels go missing.  This situation requires the services of SuperDave, but, unfortunately he's a little busy these days.  Have you done a modem restart or factory reset at all to see what affect they might have?

Do you happen to be using the 2.4 Ghz wifi on the modem?  If so, can you try an experiment and that is to log into the modem, disable the 2.4 Ghz wifi and reboot the modem (ADMIN .... DEVICE RESET .... Reboot).  After the reboot run a speedtest at www.speedtest.net using the Toronto or Montreal Rogers server depending on which is closer.