10-27-2016 12:10 PM
Hi Gdkitty,
Thanks for following up. No, there is no drop during the bad times; the strength is indeed fairly consistent across all the channels, and in both good and bad times.
I've read something about "CMTS" issues but I don't know enough to say whether it is perhaps related to my woes.
Sam
10-28-2016 08:28 AM
The CMTS is something at the local head end.. sort of where the modem registers to.
There have been CMTS changes recently, with them changing to CASA instead of cisco.. but generally shouldnt be causing what your happening.
Unless its just droping the registration or something.. that the cmts is having issues in that way.
10-28-2016 07:57 PM
Thanks again Gdkitty. I picked up a Cisco modem this afternoon, so let's see if it can fair better than the two Hitron misses I've had thus far.
11-15-2016 06:31 PM
Hey @Datalink sorry for the late reply. It suddenly stopped not working! 🙂 Unofrtuntely for the past week it's been off and on again (not as badly but more than normal I would think)
Ever since then, my roll-off has been better on the downstream, reaching 300ish Mhz vs. 621. Upstream is still low as you said, hovering around 30-33 dBmV range. This correlates with a few changes I made to the wiring sytem in my house. I haven't changed the actual wire, but I have replaced a few splitters which were unknowlingly in positions that were better catered to couplers (I used splitters for those instead of couplers) Silver ones if that make any difference. That obviously changed my timeout situation for the better, but not my upstream.
I have an old splitter (only one now) that is rated at 5-1000Mhz. Is that sufficent or should I be looking at higher ones of the 2Ghz range? It's also silver plated vs the gold I'm seeing at Best Buy and the Source. So far it's good! But if it comes back, I might look into the actual cable replacement and a tech visit. Thanks in advance again.
12-12-2016 02:43 PM
Hello,
Exact same problem for me as well, my internet have been disconnecting atleast 3-4 times a day and it last for roughly 30 secs. I have swopped modem and the samething is still happening. I nothiced this issue occured when there was a issue with Rogers back on October 27 (case number C116716310). I called Tech 3 times and they couldnt find any issue but to tell me to unplug the modem. I live in a Condo, so I guess the lines run accross the whole building.
I have the CGN3ROG router and here is my log ( not sure what it means), hopefully someone can shine a light.
Thanks
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Signal noise ratio (dB) | Channel ID |
1 | 591000000 | 256QAM | -7.300 | 37.636 | 31 |
2 | 363000000 | 256QAM | -6.600 | 37.636 | 10 |
3 | 369000000 | 256QAM | -6.500 | 37.356 | 11 |
4 | 375000000 | 256QAM | -6.400 | 37.636 | 12 |
5 | 381000000 | 256QAM | -6.300 | 37.356 | 13 |
6 | 387000000 | 256QAM | -6.900 | 37.636 | 14 |
7 | 393000000 | 256QAM | -7.500 | 37.356 | 15 |
8 | 399000000 | 256QAM | -7.300 | 37.636 | 16 |
9 | 405000000 | 256QAM | -7.600 | 37.356 | 17 |
10 | 411000000 | 256QAM | -7.300 | 37.356 | 18 |
11 | 417000000 | 256QAM | -7.200 | 37.636 | 19 |
12 | 423000000 | 256QAM | -7.300 | 37.356 | 20 |
13 | 429000000 | 256QAM | -6.400 | 37.356 | 21 |
14 | 435000000 | 256QAM | -5.800 | 37.636 | 22 |
15 | 441000000 | 256QAM | -6.300 | 37.636 | 23 |
16 | 447000000 | 256QAM | -6.600 | 37.356 | 24 |
17 | 555000000 | 256QAM | -5.300 | 37.636 | 25 |
18 | 561000000 | 256QAM | -5.800 | 37.636 | 26 |
19 | 567000000 | 256QAM | -5.700 | 37.356 | 27 |
20 | 573000000 | 256QAM | -5.700 | 37.356 | 28 |
21 | 579000000 | 256QAM | -6.400 | 37.356 | 29 |
22 | 585000000 | 256QAM | -6.500 | 37.636 | 30 |
23 | 357000000 | 256QAM | -6.900 | 36.610 | 9 |
24 | 597000000 | 256QAM | -6.800 | 37.356 | 32 |
Port ID | Frequency (MHz) | BandWidth | Modulation Type | Signal Strength (dBmV) | Channel ID |
1 | 30596000 | 6400000 | ATDMA | 46.000 | 1 |
2 | 9999984 | 6400000 | ATDMA | 51.000 | --- |
3 | 9999984 | 6400000 | ATDMA | 50.250 | --- |
12-13-2016 08:32 AM
12-18-2016
09:22 PM
- last edited on
12-18-2016
10:11 PM
by
RogersMaude
I am trying to figure out what is causing my modem go through these changes... for some reason during certain hours .. there isn't a specific time frame the modem stats spike and there is a big difference in variation .
When the jumps happen my internet starts behaving differently, and more t3 errors start showing up in my modem log and hiccups in the internet where things dont load.
Yesterday:
Downstream Overview
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 693000000 | 256QAM | -1.200 | 47 | 39.636 |
2 | 363000000 | 256QAM | -1.300 | 10 | 40.946 |
3 | 369000000 | 256QAM | 1.700 | 11 | 40.946 |
4 | 375000000 | 256QAM | 1.400 | 12 | 40.366 |
5 | 381000000 | 256QAM | 1.200 | 13 | 40.366 |
6 | 387000000 | 256QAM | 1.200 | 14 | 40.366 |
7 | 393000000 | 256QAM | -1.300 | 15 | 40.366 |
8 | 399000000 | 256QAM | -1.600 | 16 | 40.946 |
9 | 405000000 | 256QAM | -1.800 | 17 | 40.266 |
10 | 411000000 | 256QAM | -1.100 | 18 | 40.946 |
11 | 417000000 | 256QAM | -1.500 | 19 | 40.466 |
12 | 423000000 | 256QAM | 1.700 | 20 | 40.566 |
13 | 429000000 | 256QAM | 1.800 | 21 | 40.466 |
14 | 435000000 | 256QAM | 1.900 | 22 | 40.946 |
15 | 441000000 | 256QAM | 1.100 | 23 | 40.946 |
16 | 447000000 | 256QAM | -1.500 | 24 | 40.946 |
17 | 555000000 | 256QAM | -1.300 | 25 | 38.936 |
18 | 561000000 | 256QAM | -1.200 | 26 | 37.356 |
19 | 567000000 | 256QAM | -0.900 | 27 | 37.636 |
20 | 573000000 | 256QAM | -0.800 | 28 | 37.636 |
21 | 681000000 | 256QAM | 1.100 | 45 | 37.636 |
22 | 687000000 | 256QAM | 0.100 | 46 | 37.636 |
23 | 357000000 | 256QAM | 0.700 | 9 | 40.366 |
24 | 699000000 | 256QAM | 1.500 | 48 | 39.356 |
Today:
Downstream Overview
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | Signal noise ratio (dB) |
1 | 693000000 | 256QAM | 2.300 | 47 | 37.636 |
2 | 363000000 | 256QAM | 3.700 | 10 | 40.946 |
3 | 369000000 | 256QAM | 3.700 | 11 | 40.946 |
4 | 375000000 | 256QAM | 3.700 | 12 | 40.366 |
5 | 381000000 | 256QAM | 4.000 | 13 | 40.366 |
6 | 387000000 | 256QAM | 4.200 | 14 | 40.366 |
7 | 393000000 | 256QAM | 4.300 | 15 | 40.366 |
8 | 399000000 | 256QAM | 4.600 | 16 | 40.946 |
9 | 405000000 | 256QAM | 4.800 | 17 | 40.366 |
10 | 411000000 | 256QAM | 5.100 | 18 | 40.946 |
11 | 417000000 | 256QAM | 5.500 | 19 | 40.366 |
12 | 423000000 | 256QAM | 5.700 | 20 | 40.366 |
13 | 429000000 | 256QAM | 5.800 | 21 | 40.366 |
14 | 435000000 | 256QAM | 6.000 | 22 | 40.946 |
15 | 441000000 | 256QAM | 6.100 | 23 | 40.946 |
16 | 447000000 | 256QAM | 6.500 | 24 | 40.946 |
17 | 555000000 | 256QAM | -1.300 | 25 | 37.636 |
18 | 561000000 | 256QAM | -1.200 | 26 | 37.356 |
19 | 567000000 | 256QAM | -0.900 | 27 | 37.636 |
20 | 573000000 | 256QAM | -0.800 | 28 | 37.636 |
21 | 681000000 | 256QAM | 2.100 | 45 | 37.636 |
22 | 687000000 | 256QAM | 2.100 | 46 | 37.636 |
23 | 357000000 | 256QAM | 3.700 | 9 | 40.366 |
24 | 699000000 | 256QAM | 2.500 | 48 | 37.356 |
Upstream seems pretty consistent on both days:
Upstream Overview
Port ID | Frequency (MHz) | Modulation | Signal strength (dBmV) | Channel ID | BandWidth |
1 | 23700000 | ATDMA - 64QAM | 44.500 | 2 | 6400000 |
2 | 38596000 | ATDMA - 64QAM | 46.250 | 3 | 3200000 |
3 | 30596000 | ATDMA - 64QAM | 44.500 | 1 | 6400000 |
12-19-2016 10:01 AM
Both of those are within spec.. and still pretty close to the good point.. that i wouldnt think that DIRECTLY is the issue your having. Its only when you start getting close to/above +/- 10 that you really start seeing a bunch.
Question is, what is causing the varriance?
Does this happen randomly durring the day? Or does it seem to happen more at a specific time?
Randomly.. could be something like the connector outside the house is going (with the weather, etc).
More specific times.. i am guessing its more of an area issue. When more people are on, etc.. that something cang handle the strain, and then your seeing signal changes... as well as possible OTHER issues at the local node, etc possibly, which may be causing the problems.
12-20-2016 12:16 AM
@Gdkitty wrote:Both of those are within spec.. and still pretty close to the good point.. that i wouldnt think that DIRECTLY is the issue your having. Its only when you start getting close to/above +/- 10 that you really start seeing a bunch.
Question is, what is causing the varriance?
Does this happen randomly durring the day? Or does it seem to happen more at a specific time?
Randomly.. could be something like the connector outside the house is going (with the weather, etc).
More specific times.. i am guessing its more of an area issue. When more people are on, etc.. that something cang handle the strain, and then your seeing signal changes... as well as possible OTHER issues at the local node, etc possibly, which may be causing the problems.
From what I have gathered, it seems to happen between 2-7 sometimes 9 and the stats drop off again to "norm"
But on lets say weekends i've had it all day until midnight .
So it could be an "area" issue , or maybe something going on at the tap,
They are within spec, but there is a variance between the lower to highest and back down.. like some channels jump and others remain .
I don't know to be honest.. there have been periodic slow down and ping spikes but nothing huge
12-20-2016 02:51 PM
I am also having similar issue, my wifi for 2.4/5g is very unstable. Below is the event log, not sure what they mean, but i see alot of "errors", "no range response". I got a tech coming this friday, but does anyone know whats going on in the mean time? Thanks
No | Time | type | Priority | Event |
1 | 12/13/16 21:19:48 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
2 | 12/13/16 21:19:48 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
3 | 12/13/16 21:19:48 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
4 | 12/13/16 21:19:48 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
5 | 12/13/16 21:19:49 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
6 | 12/13/16 21:19:49 | 82000300 | critical | Ranging Request Retries exhausted;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
7 | 12/13/16 21:19:49 | 82000600 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
8 | 12/13/16 21:20:32 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
9 | 12/13/16 21:23:46 | 90000000 | warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
10 | 12/17/16 07:44:02 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
11 | 12/17/16 08:58:06 | 68010300 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
12 | 12/18/16 03:25:00 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
13 | 12/18/16 08:58:06 | 68010300 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
14 | 12/19/16 08:36:17 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
15 | 12/19/16 08:58:07 | 68010300 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
16 | 12/19/16 22:21:05 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
17 | 12/20/16 02:16:36 | 84020200 | warning | Lost MDD Timeout;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
18 | 12/20/16 05:40:04 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
19 | 12/20/16 08:58:08 | 68010300 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |
20 | 12/20/16 15:42:24 | 82000200 | critical | No Ranging Response received - T3 time-out;CM-MAC=78:8d:f7:af:68:c0;CMTS-MAC=00:17:10:93:71:0e;CM-QOS=1.1;CM-VER=3.0; |