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
Highlighted
I Plan to Stick Around
Posts: 154

Re: CODA-4582 - Open Issues for Investigation


@sbenninger wrote:

I am on my second CODA now and both have the same issue with losing connection to the CMTS random times throughout the day. It is in bridge mode and for ~30s before the issue the latency shoots up then the 2 blue arrows go green then flashing to start to re-sync. Sometimes once a day up to 10 times a day. I am on the .27 firmware version but I have just signed up for the beta program to see if it helps...not sure how long it takes for the update to be pushed out?

 

Tech support checked all my signals, logs, area issues etc and could find no issues hence the suggestion to swap the CODA but the issue still remains.

 

One thing I was able to catch (perhaps its normal?) is that my WAN IP temporarily went to a 192.168.100.xx IP address right as the issue happened and after re-connection back to my normal 99.x.x.x address.

 

Thanks,


You're clearly losing signal, which means that there should be something in the logs. I find it hard to believe that there's no issues at all.

 

You might need to rule out on-premises issues. Since this happens frequently, and with two different modems, it's likely to be something in your location.

 

Try to connect directly to the incoming line, this is ideal and can eliminate almost all on-site issues. If you can do this, run a constant ping and check for drops throughout the day.

 

If necessary run through a single Y-splitter only, and try to have the modem directly next to the incoming line and splitter to avoid any potential issues with cabling in your residence. No amplifiers other other devices. Ensure that it's a high quality proper splitter designed for cable modems.

 

If you can prove that the issue still exists in those cases, you can get a technician to come out and evaluate.

Highlighted
I Plan to Stick Around
Posts: 135

Re: CODA-4582 - Open Issues for Investigation

Thanks for the suggestion. There is 1 splitter right near the modem that was installed 2.5years ago when we moved in. I will disconnect the cable box and run straight through to the modem for a day (if the fam can live without cable for a day) and see if that resolves anything. If I remove the splitter will the signal become too strong? At my old house I needed a -3db pad to knock down the signal with a direct line to the cable modem.

Highlighted
I Plan to Stick Around
Posts: 154

Re: CODA-4582 - Open Issues for Investigation


@sbenninger wrote:

Thanks for the suggestion. There is 1 splitter right near the modem that was installed 2.5years ago when we moved in. I will disconnect the cable box and run straight through to the modem for a day (if the fam can live without cable for a day) and see if that resolves anything. If I remove the splitter will the signal become too strong? At my old house I needed a -3db pad to knock down the signal with a direct line to the cable modem.


Check your 192.168.100.1 page and look for the modem signal levels. As long as they're under 8 you should be fine to remove the splitter.

Highlighted
I Plan to Stick Around
Posts: 135

Re: CODA-4582 - Open Issues for Investigation


@Telek wrote:

@sbenninger wrote:

Thanks for the suggestion. There is 1 splitter right near the modem that was installed 2.5years ago when we moved in. I will disconnect the cable box and run straight through to the modem for a day (if the fam can live without cable for a day) and see if that resolves anything. If I remove the splitter will the signal become too strong? At my old house I needed a -3db pad to knock down the signal with a direct line to the cable modem.


Check your 192.168.100.1 page and look for the modem signal levels. As long as they're under 8 you should be fine to remove the splitter.


For reference here are the logs that look to indicate a loss of signal:

No.         Time      Type      Priority Event

1              06/30/2017 09:35:52       90000000             warning                MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:97:de:05;CM-QOS=1.1;CM-VER=3.1;

2              06/30/2017 09:46:03       84000500             critical   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:97:de:05;CM-QOS=1.1;CM-VER=3.1;

3              07/26/2017 18:02:03       90000000             warning                MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

4              07/26/2017 18:02:11       69010200             notice   SW Download INIT - Via Config file bac10800010664777d660640

5              07/26/2017 18:02:58       69011200             notice   SW download Successful - Via Config file

6              07/26/2017 18:38:57       90000000             warning                MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

7              07/27/2017 17:37:35       82000200             critical   No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

8              07/27/2017 17:37:35       82000300             critical   Ranging Request Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

9              07/27/2017 17:37:35       82000600             critical   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

10           07/27/2017 17:37:37       82000200             critical   No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

11           07/27/2017 17:37:37       82000300             critical   Ranging Request Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

12           07/27/2017 17:37:37       82000600             critical   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

13           07/27/2017 17:37:38       82000300             critical   Ranging Request Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

14           07/27/2017 17:37:38       82000600             critical   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

15           07/27/2017 17:38:05       82000200             critical   No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

16           07/27/2017 17:38:25       90000000             warning                MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1;

I Plan to Stick Around
Posts: 135

Re: CODA-4582 - Open Issues for Investigation

And signal levels with the splitter removed. I have a -3db attenuator if needed.

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1615000000256QAM5.9001132.237
2849000000256QAM7.800231.915
3855000000256QAM7.500331.689
4861000000256QAM6.700431.072
5579000000256QAM5.900532.585
6585000000256QAM6.200632.676
7591000000256QAM6.300732.963
8597000000256QAM6.200832.963
9603000000256QAM6.300932.676
10609000000256QAM6.2001032.585
11303000000256QAM2.500133.957
12621000000256QAM5.9001232.237
13633000000256QAM6.6001332.585
14639000000256QAM6.8001432.585
15645000000256QAM6.6001532.321
16651000000256QAM6.6001632.321
17657000000256QAM6.8001732.676
18663000000256QAM6.8001832.676
19669000000256QAM7.2001933.063
20675000000256QAM7.2002033.063
21681000000256QAM6.8002132.963
22687000000256QAM6.6002232.963
23693000000256QAM6.9002332.676
24699000000256QAM7.7002432.676
25705000000256QAM7.5002532.676
26711000000256QAM7.3002632.676
27717000000256QAM7.5002732.676
28723000000256QAM7.4002832.321
29825000000256QAM7.4002932.321
30831000000256QAM7.1003031.994
31837000000256QAM7.0003131.915
32843000000256QAM7.1003231.915
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K290600000YESYESYES3.599998
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
138596000ATDMA - 64QAM44.25033200000
230596000ATDMA - 64QAM40.00016400000
323700000ATDMA - 64QAM39.75026400000
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: 154

Re: CODA-4582 - Open Issues for Investigation

@sbenninger your log is full of errors -- that's pretty clearly a problem. Don't know why the tech would say there was no issue.

 

Your signal levels are great, no need for an attenuator. However your SNR is lower than I'd like to see (usually 38+).

 

Run it like this for a day, see if you have any problems.  Is it directly connected to the incoming line (not via cabling that's in the residence?)

Highlighted
I Plan to Stick Around
Posts: 135

Re: CODA-4582 - Open Issues for Investigation

Yes this line comes into the house by the electrical panel right from the rogers dmarc box and the modem is about 8ft away. The rest of the house is fed from separate feeds from the dmarc. There are rogers and bell green boxes right in front of my house by the road. 

 

For reference the SNR was ~34-35.5db prior to taking out the splitter. They have dropped with the direct feed. Perhaps I should add the attenuator to see if the SNR improves at a lower signal strength?

 

thanks for your assistance. 

Highlighted
I Plan to Stick Around
Posts: 154

Re: CODA-4582 - Open Issues for Investigation

You could try, but probably best to leave it as is and see if the condition improves.

Highlighted
Resident Expert
Resident Expert
Posts: 1,100

Re: CODA-4582 - Open Issues for Investigation


@sbenninger wrote:

Yes this line comes into the house by the electrical panel right from the rogers dmarc box and the modem is about 8ft away. The rest of the house is fed from separate feeds from the dmarc. There are rogers and bell green boxes right in front of my house by the road. 

 

For reference the SNR was ~34-35.5db prior to taking out the splitter. They have dropped with the direct feed. Perhaps I should add the attenuator to see if the SNR improves at a lower signal strength?

 

thanks for your assistance. 


as mentioned your SNR is low, call in and ask them to check other houses in the area. If everyone has bad SNR then perhaps you need a maintenance crew sent out to see where the noise is coming from. If the low SNR is just on your line then something is causing noise, perhaps ingress on a cable or something in the DMARC.

 



Highlighted
I Plan to Stick Around
Posts: 35

Re: CODA-4582 - Open Issues for Investigation

I still have Loss of ofdm lock. Luckily I haven't seen it since a tech visit recently. Also have GUI issues where it fails to load the tables with pfsense after it provisions itself on the network.