cancel
Showing results for 
Search instead for 
Did you mean: 

Dropouts after midnight daily

Anonymous
Not applicable

Been having dropouts for the past couple of days after midnight.
Checked the modem noticed upstream issues.
Which I believe is indictive of a mainline issue.
Not sure where the fault lies.

Unfortunately support via customer services hasn't yielded much help.
They just said they would monitor it and let techs know.

13/12/2022 08:00:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/12/2022 02:22:38noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/12/2022 02:22:34Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/12/2022 02:22:34Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/12/2022 19:14:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/12/2022 00:15:17noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/12/2022 00:10:12Warning!TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/12/2022 00:10:12Warning!Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 19:40:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:27Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:24Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:24criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:22criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:13Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:13criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2022 10:55:12Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1 ACCEPTED SOLUTION

Accepted Solutions

Anonymous
Not applicable

VM is sending us a new hub.

See where this Helpful Answer was posted

30 REPLIES 30

Anonymous
Not applicable

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13940000051512064 qam2
22580000051512064 qam4
34620000051512064 qam1
43260000051512064 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

Anonymous
Not applicable

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

12347500002.438256 qam13
22427500002.238256 qam14
32507500002.538256 qam15
42587500002.538256 qam16
52667500002.738256 qam17
62747500002.738256 qam18
7282750000338256 qam19
8290750000338256 qam20
92987500003.438256 qam21
103067500003.238256 qam22
113147500003.538256 qam23
123227500003.438256 qam24
133307500003.538256 qam25
143387500003.538256 qam26
153467500003.538256 qam27
163547500003.238256 qam28
173627500003.538256 qam29
183707500003.538256 qam30
193787500003.738256 qam31
203867500003.438256 qam32
213947500003.538256 qam34
224027500003.438256 qam35
234107500003.738256 qam36
244187500003.538256 qam37



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.960
2Locked38.620
3Locked38.970
4Locked38.640
5Locked38.960
6Locked38.660
7Locked38.650
8Locked38.670
9Locked38.680
10Locked38.960
11Locked38.950
12Locked38.680
13Locked38.640
14Locked38.970
15Locked38.980
16Locked38.920
17Locked38.960
18Locked38.970
19Locked38.660
20Locked38.670
21Locked38.960
22Locked38.980
23Locked38.690
24Locked38.990

Anonymous
Not applicable

Interesting situation
I saw someone mention a bad attenuator in another thread.
What do you know, when I removed the cable, it was completely bent.
I'm not sure how this occurred, but I've since changed the attenuator.

From a previous cable that was installed on the same line before.
Strangely, the previous occupant had no problems.
Second hint: Our attenuator is too high.
Latency and jitter are much more stable when using one rated at 3db as opposed to 6db.
As far as I can tell, the problem may have been the downstream rather than upstream.

No matter what we do, upstream remains at 51.

Anonymous
Not applicable

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

12347500005.438256 qam13
22427500005.338256 qam14
32507500005.538256 qam15
42587500005.538256 qam16
52667500005.938256 qam17
62747500005.838256 qam18
7282750000638256 qam19
8290750000638256 qam20
92987500006.538256 qam21
103067500006.338256 qam22
113147500006.438256 qam23
123227500006.438256 qam24
133307500006.538256 qam25
143387500006.638256 qam26
153467500006.538256 qam27
163547500006.538256 qam28
173627500006.538256 qam29
183707500006.538256 qam30
193787500006.638256 qam31
203867500006.538256 qam32
213947500006.638256 qam34
224027500006.538256 qam35
234107500006.838256 qam36
244187500006.538256 qam37



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.650
2Locked38.600
3Locked38.900
4Locked38.900
5Locked38.650
6Locked38.600
7Locked38.950
8Locked38.640
9Locked38.960
10Locked38.960
11Locked38.900
12Locked38.600
13Locked38.900
14Locked38.950
15Locked38.620
16Locked38.900
17Locked38.950
18Locked38.950
19Locked38.950
20Locked38.600
21Locked38.650
22Locked38.600
23Locked38.660
24Locked38.660

Anonymous
Not applicable

Time will tell if the issue is fixed.
Will pop back tomorrow.

Anonymous
Not applicable

Well this is rather strange it just dropped.
Yet reconnected straight away.
At 00:08 almost one minute later it reconnected.
Incidentally the modem isn't showing anything in the log.

When I logged into the modem, it came back.
So bad firmware perhaps or main line issue?
Who knows, have a stronger attenuator on the way.
I figure once we get it stable during cold months.

Should be fine all year round.
Fingers crossed.

Anonymous
Not applicable

Gone back to the 6db attenuator.
I don't trust the thing.
Middle isn't straight at all.
These are the new downstream values.

Anonymous
Not applicable

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

12347500002.538256 qam13
22427500002.538256 qam14
32507500002.738256 qam15
42587500002.738256 qam16
5266750000338256 qam17
6274750000338256 qam18
72827500003.238256 qam19
82907500003.438256 qam20
92987500003.738256 qam21
103067500003.538256 qam22
113147500003.738256 qam23
123227500003.538256 qam24
133307500003.738256 qam25
143387500003.938256 qam26
153467500003.738256 qam27
163547500003.538256 qam28
173627500003.738256 qam29
183707500003.738256 qam30
193787500003.938256 qam31
203867500003.738256 qam32
213947500003.938256 qam34
224027500003.738256 qam35
23410750000438256 qam36
244187500003.738256 qam37

Anonymous
Not applicable

Just for the hell of it.
Removed the attenuator to see how the levels would behave.
Surprisingly without any attenuator the upstream looks more stable.