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
Network Architect
Network Architect
Posts: 611

Re: CODA-4582 - Open Issues for Investigation

Hello Community!

 

I'm sorry it has been a little while since my last visit (5 full pages in this thread) but as I said previously, from time to time my boss still wants me to do my real job which I have to do if I want to be able to keep said job and support all of you on the side Smiley Happy

 

That being said, I read all the messages in this tread (will follow up with the other regular threads where I'm active and private messages in the next couple of hours) and picked up a few items for Hitron.

 

Version 2.0.10.29 and 2.0.10.30T1 were initial test code of a brand new development branch. These firmwares were not as stable as I would have wanted but there was a lot more work done on it in the last 2 weeks. We have 2 new firmwares coming soon with a lot of fixes while will hopefully bring on par with the general stability of 2.0.10.27 along with the new features.

 

We have also broken down that was original planned in 2.0.10.30T1 in 2 different builds coming between now and the end of July. The first one will include some of the DFS and band steering changes while the second will focus on WiFi speed improvement.

 

Given the comments in here, I will definitely re-run all my latency tests on these new versions and compare with 2.0.10.27.


@Max24, noted you have a speed issue and will look into it.

 

@RyzenFX, OFDM loss (I think it's a localized problem). Did you make any progress with this issue?

 

@ishine80, I understand that you have intermittent connectivity issue. Will wait for the hardwired test to troubleshoot further.

 

Dave

I'm a Reliable Contributor
Posts: 579

Re: CODA-4582 - Open Issues for Investigation

@RogersDave Welcome back! Smiley Very Happy

 

I have made some progress with this issue and I was able to switch modems. Unfortunately this hasn't resolved the issue for me as my modem is still not reporting a lock to an OFDM carrier. I contacted tier 2 customer support and they said that my modem is connected to an OFDM carrier, which is odd considering that my modem interface is still not showing a lock. I'll call again and see if it's a localized issue. 

 

Also, I will compare my League of Legends game logs on .27 to those of .30T1 to see if there is a latency problem in .30T1.

I'm a Reliable Contributor
Posts: 609

Re: CODA-4582 - Open Issues for Investigation

@RogersDave

 

Thanks for the update Dave!

 

By any chance do you have any info on DOCSIS 3.1 upstream deployment?

Highlighted
I Plan to Stick Around
Posts: 18

Re: CODA-4582 - Open Issues for Investigation

@RogersDave, Just an update since my last posting I had spoken with a supervisor last week July 5th and again on July 7th and was advised that the issue was being investigated on the node and a area ticket had been created should be listed on my account I can provide you the number if need be. The ticket is still being worked on AFAIK however I noticed speeds were restored earlier this week Wednesday, July 12th, not sure what the problem was or is. But my guess is some speed restriction was in effect as sometimes when I ran speedtests prior to July 12th my download would sometimes to 800-900 then instantly drop down to around the 550 range and the upload would sometimes start off at 43-36 then drop down to 1-6mbps.

 

Since my speeds were restored I've now been having issues with the port speed dropping from gigabit down to 100M and I have to change the ethernet cable to another port to restore the speed back to gigabit (faster than restarting the modem). Not sure what is causing this as I assumed it was fixed in the earlier firmware versions..

I Plan to Stick Around
Posts: 17

Re: CODA-4582 - Open Issues for Investigation

@Datalink@RogersDave

 

Finally had some time to get a few things tested.  Hooked up my better of the two laptops through ethernet and found ethernet could not connect when my cell phone dropped the wifi signal.  Note that at the same time my daughter was still able to stream youtube kids on the old iphone that's not linked to any cell network.  

 

Below is the message on the ethernet through my laptop: it stated there was an unknown network and could not connect to network as a general message.  

 

IPv6 address: fd00:6477:7de2:58f2:a869:fccf:baa2:424
IPv6 DNS Servers: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Manufacturer: Realtek
Description: Realtek PCIe FE Family Controller
Driver version: 9.1.406.2015

 

I will run the other tests that @Datalink suggested later in the evening respond on the same thread.  

I Plan to Stick Around
Posts: 124

Re: CODA-4582 - Open Issues for Investigation

I am having this same issue with the CODA Running .27 FW in bridge mode. Randomly throughout the day or night there will connection issues with high latency and patcket loss and then finally the modem reboots itself. The connection is excellent otherwise until these events happen. I have not contacted support as of yet. Any suggestions prior to doing so would be great. Does the newer .29 FW correct issues like this?

Here is my Docsis log.

 

N

o. 

Time 

Type 

Priority 

Event 

07/20/2017 05:51:52 

84020200 

warning 

Lost MDD Timeout;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 06:23:39 

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; 

07/20/2017 06:23:40 

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; 

07/20/2017 06:23:40 

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; 

07/20/2017 06:28:40 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 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; 

07/20/2017 06:29:04 

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; 

07/20/2017 07:24:18 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 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; 

07/20/2017 07:24:18 

85010200 

warning 

TCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

07/20/2017 08:07:48 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 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; 

10 

07/20/2017 08:08:18 

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/20/2017 08:08:18 

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/20/2017 08:08:18 

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/20/2017 08:08:18 

82000400 

critical 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 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; 

14 

07/20/2017 08:08:22 

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; 

15 

07/20/2017 08:08:23 

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; 

16 

07/20/2017 08:08:23 

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; 

17 

07/20/2017 08:08:43 

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; 

18 

07/20/2017 08:09:01 

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; 

19 

07/20/2017 08:09:04 

84000700 

warning 

RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=00:17:10:93:b3:0e;CM-QOS=1.1;CM-VER=3.1; 

20 

07/20/2017 09:57:52 

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;

 

Here is my Docsis WAN signals:

 

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 

290600000 

YES 

YES 

YES 

-0.500000 

Downstream Overview 

 

 

 

 

 

Port ID 

Frequency (MHz) 

Modulation 

Signal strength (dBmV) 

Channel ID 

Signal noise ratio (dB) 

1 

639000000 

256QAM 

2.500 

14 

35.084 

2 

849000000 

256QAM 

3.100 

2 

34.484 

3 

855000000 

256QAM 

3.200 

3 

34.926 

4 

861000000 

256QAM 

2.500 

4 

34.346 

5 

579000000 

256QAM 

1.500 

5 

35.084 

6 

585000000 

256QAM 

1.700 

6 

35.084 

8 

597000000 

256QAM 

2.200 

8 

35.595 

9 

603000000 

256QAM 

2.000 

9 

35.595 

10 

609000000 

256QAM 

2.000 

10 

35.084 

11 

615000000 

256QAM 

1.800 

11 

35.084 

12 

621000000 

256QAM 

1.700 

12 

34.926 

13 

633000000 

256QAM 

2.400 

13 

35.084 

14 

303000000 

256QAM 

-1.700 

1 

35.595 

15 

645000000 

256QAM 

2.000 

15 

34.926 

16 

651000000 

256QAM 

2.000 

16 

35.084 

17 

657000000 

256QAM 

2.300 

17 

35.084 

18 

663000000 

256QAM 

2.500 

18 

35.084 

19 

669000000 

256QAM 

3.000 

19 

35.595 

20 

675000000 

256QAM 

2.600 

20 

35.084 

21 

681000000 

256QAM 

2.300 

21 

35.084 

22 

687000000 

256QAM 

2.600 

22 

35.084 

23 

693000000 

256QAM 

2.700 

23 

35.084 

24 

699000000 

256QAM 

3.000 

24 

35.084 

25 

705000000 

256QAM 

3.200 

25 

35.084 

26 

711000000 

256QAM 

3.100 

26 

35.595 

27 

717000000 

256QAM 

3.000 

27 

35.084 

28 

723000000 

256QAM 

3.100 

28 

35.084 

29 

825000000 

256QAM 

3.100 

29 

34.484 

30 

831000000 

256QAM 

2.800 

30 

34.484 

31 

837000000 

256QAM 

2.900 

31 

34.484 

32 

843000000 

256QAM 

2.700 

32 

34.926 

 

Upstream Overview 

 

 

 

 

 

Port ID 

Frequency (MHz) 

Modulation 

Signal strength (dBmV) 

Channel ID 

Bandwidth 

1 

30596000 

ATDMA - 64QAM 

42.750 

1 

6400000 

2 

38595805 

ATDMA - 64QAM 

47.250 

3 

3200000 

3 

23700000 

ATDMA - 64QAM 

41.500 

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

I'm a Reliable Contributor
Posts: 609

Re: CODA-4582 - Open Issues for Investigation

@RyzenFX

 

http://about.rogers.com/cnwposts/rogers-communications-2q17-investment-community-teleconference-july...

 

The Rogers Conference was at 8:00 AM ET today, have you heard any announcement about a new gateway or the deployment of D3.1 Upstream?

I Plan to Stick Around
Posts: 154

Re: CODA-4582 - Open Issues for Investigation


@JohnBeaudin wrote:

@RyzenFX

 

http://about.rogers.com/cnwposts/rogers-communications-2q17-investment-community-teleconference-july...

 

The Rogers Conference was at 8:00 AM ET today, have you heard any announcement about a new gateway or the deployment of D3.1 Upstream?


They better hurry up. Bell came a month ago to install fibre right into my suite. Says that in about 3-4 months they'll be lighting up the building and offering enticing Gigabit (940/100) plans to get people onboard, around or slightly lower than the same price as Rogers' special pricing plans.

I Plan to Stick Around
Posts: 13

Re: CODA-4582 - Open Issues for Investigation

Been experiencing this the past 7-8 weeks. Much much longer than prior FW transitions, and now very inconvenient.

1. Modem constantly reboots knocking out my OBI VOIP ATA

2. WIFI signal interrupts while modem LEDs lit up, knocking out phones and tablets

3. WIFI signal reach reduced. Used to easily reach end of backyard ~25-30 metres. Now it struggles just outside the back door.

 

Last night was THE WORST episode. Streaming was interrupted every 5-10 minutes.

 

I'm on .29 FW. But this was an issue when I saw .27. I cannot recall the last stable version #.

Speedtest used to indicate near 900 +/- originally. Now, just approaches 500 but more often in the 250-350 range. Between "EVENTS" all runs well.

 

I've gone back several pages and see I'm not alone. Very similar DOCSIS logs.

 

Any assistance/direction before I return the CODA?

 

Thanks

 

 

 

 

 

Resident Expert
Resident Expert
Posts: 1,074

Re: CODA-4582 - Open Issues for Investigation

@nobs2016 for the WiFi range issue, make sure you set the 5Ghz to the higher channels (149+) and set 2.4Ghz to either 1, 6, or 11.