Community Forum
Top

Upstream issues causing disconnects again!

JakeMaxis
Frequent Visitor
‎07-02-2020 09:06 AM

Upstream issues causing disconnects again!

Back at the start of the epidemic I was seeing frequent disconnects due to upstream issues indicated by my modem.  Typically I would disconnect and then see the upstream light on my modem flash green.

 

After a month or so of calling, texting and forum back and forth got a tech out here thanks to @ComcastAmir  whom I hope can possibly help again.  The tech found water in the line and up at the drop where critters had chewed into it, replaced the drop and everything worked great.. for a month and a half.

 

About 2-3 weeks ago I have started to have the same issue increasing in frequency.  I have pretty much had to go back to working from home hotspotted to my phone and the kids and wife are unable to enjoy some of the tech around the house, also concerning is the security system is linked to the internet.

 

I have tried other modems as well, currently have my CM500 connected which does the flashing green upstream when disconnecting as well as an old surfboard 6121 which sometimes shows a blue upstream a green upstream or no upstream indicator.  Both exhibit the same disconnect issues.

 

I have been getting the run around between the online assistant and the call center. 

 

June 26 I got a hold of someone on the assistant generating a ticket #051-214-679 and told me I would recieve a call from a technical support specialist in 24 hours.... didnt happen.

 

June 29th it took over an hour to get a real person on the phone who said that the previous ticket was closed, but would schedule me a call with a tech support specialist again even gave me a time 2-3pm on July 1st.  This would ofcourse be under a new ticket number 912-872-399.... again no call.

 

I am connected to the internet direct to the chord coming into the house so should not be any spitter issues.

 

So now I am here getting booted a few times from the internet so I can get the data for you guys to look at let me know.  Thank you!

 

Startup Procedure  
Procedure Status Comment
Acquire Downstream Channel 429000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
 
  
Downstream Bonded Channels  
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 38 429000000 Hz 4.8 dBmV 40.9 dB 469 352
2 Locked QAM256 39 435000000 Hz 5.2 dBmV 40.8 dB 420 259
3 Locked QAM256 40 441000000 Hz 5.3 dBmV 40.7 dB 442 266
4 Locked QAM256 41 447000000 Hz 5.2 dBmV 40.6 dB 481 311
5 Locked QAM256 33 453000000 Hz 5.4 dBmV 40.6 dB 535 276
6 Locked QAM256 34 459000000 Hz 5.5 dBmV 40.6 dB 535 343
7 Locked QAM256 35 465000000 Hz 5.6 dBmV 40.7 dB 527 270
8 Locked QAM256 36 471000000 Hz 5.7 dBmV 40.8 dB 390 417
9 Locked QAM256 1 477000000 Hz 5.8 dBmV 40.8 dB 495 226
10 Locked QAM256 2 483000000 Hz 5.6 dBmV 40.8 dB 364 451
11 Locked QAM256 3 489000000 Hz 5.4 dBmV 40.7 dB 379 289
12 Locked QAM256 4 495000000 Hz 5.4 dBmV 40.6 dB 433 204
13 Locked QAM256 5 507000000 Hz 5.5 dBmV 39.8 dB 441 257
14 Locked QAM256 6 513000000 Hz 5.5 dBmV 40.6 dB 411 242
15 Locked QAM256 7 519000000 Hz 5.4 dBmV 40.5 dB 369 309
16 Locked QAM256 8 525000000 Hz 5.2 dBmV 40.4 dB 446 214
 
 
  
Upstream Bonded Channels  
 
 
 
 
Time Priority Description
2020-7-2, 07:42:47 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-7-2, 07:42:18 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:37:44 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:37:41 Warning (5) Dynamic Range Window violation
2020-7-2, 07:33:00 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-7-2, 07:32:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:27:51 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:21:23 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-7-2, 07:21:14 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
2020-7-2, 07:20:53 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:16:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:16:33 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:16:33 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:16:11 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:16:10 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:16:10 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 07:15:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:42:13 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-7-2, 04:42:03 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
2020-7-2, 04:41:39 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:37:32 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:37:32 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:37:32 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:37:21 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:37:21 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:37:21 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:36:57 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:36:55 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:36:55 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-2, 04:35:48 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-1, 22:08:41 Warning (5) Dynamic Range Window violation
2020-7-1, 22:07:58 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-1, 20:40:19 Warning (5) Dynamic Range Window violation
2020-7-1, 20:40:18 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-1, 20:38:30 Warning (5) Dynamic Range Window violation
2020-7-1, 20:35:37 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2020-7-1, 20:35:13 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-1, 20:30:59 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-1, 20:30:58 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-1, 20:30:58 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
0 Likes
Reply
JakeMaxis
Frequent Visitor
‎07-06-2020 09:26 PM

Re: Upstream issues causing disconnects again!

Hoping to get some help after the holiday. Thank you!
0 Likes
Reply
mEistFX
Frequent Visitor
‎07-07-2020 12:48 AM

Re: Upstream issues causing disconnects again!

Hey man just someone else on here updating my forum post. Noticed yours decided to read it. I'd like to mention that you forgot to include your actual upstream bonded channel levels. I did notice a lot of errors reguarding the upstream so those levels are imporant to know in such a situation. that could be your issue if the levels are out of spec.

Also when posting if you copy and paste and click the " Incert code " its a lot easier to post.

here is a example of what mine look like

Upstream Bonded Channels
Channel 	Lock Status 	US Channel Type 	Channel ID 	Symbol Rate 	Frequency 	Power
1	Locked	ATDMA	4	5120 Ksym/sec	17300000 Hz	47.0 dBmV
2	Locked	ATDMA	3	5120 Ksym/sec	23700000 Hz	44.5 dBmV
3	Locked	ATDMA	2	5120 Ksym/sec	30100000 Hz	44.5 dBmV
4	Locked	ATDMA	1	5120 Ksym/sec	36500000 Hz	42.0 dBmV

Now thats not too high tbh but I would be happy if they was a tad bit lower heh. I've been having packet loss issues. So I have ordered a new modem hoping this would resolve the issue. Hope you get some actual support soon because I know how frustrating this can be. Believe me I've been posting on here for about a month and have also reached out to tech support as well several times now. I've not gotten really any help at all so don't feel bad.  But if you can post your upsetream levels so we know whats going on on your end. 🙂

0 Likes
Reply
JakeMaxis
Frequent Visitor
‎07-11-2020 09:41 PM

Re: Upstream issues causing disconnects again!

Sorry was called away on business for a few days.  Came home to internet still acting up.  Here is what I am getting after a reset for upstream.

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 42 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 42 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 42 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 42.3 dBmV

 

Not sure really if they are good at all and like I said just reset.  Got away with having internet for 30 minutes straight with myself and the wife on our computers working, then booted with the usual flashing upstream icon on the modem.

Thanks for responding to my message 

0 Likes
Reply
JakeMaxis
Frequent Visitor
‎07-11-2020 10:13 PM

Re: Upstream issues causing disconnects again!

already had a few disconnects after I posted.  Here is the the values after yet another reset.

 



Apply Cancel
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency
0

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 507000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 5 507000000 Hz 7 dBmV 39.7 dB 6 28
2 Locked QAM256 38 429000000 Hz 6.3 dBmV 40.7 dB 0 0
3 Locked QAM256 39 435000000 Hz 6.6 dBmV 40.7 dB 0 0
4 Locked QAM256 40 441000000 Hz 6.7 dBmV 40.6 dB 0 0
5 Locked QAM256 41 447000000 Hz 6.6 dBmV 40.4 dB 0 0
6 Locked QAM256 33 453000000 Hz 6.7 dBmV 40.4 dB 0 0
7 Locked QAM256 34 459000000 Hz 6.8 dBmV 40.4 dB 0 0
8 Locked QAM256 35 465000000 Hz 6.9 dBmV 40.5 dB 0 0
9 Locked QAM256 36 471000000 Hz 7.1 dBmV 40.6 dB 0 0
10 Locked QAM256 1 477000000 Hz 7.1 dBmV 40.6 dB 0 0
11 Locked QAM256 2 483000000 Hz 7 dBmV 40.6 dB 0 0
12 Locked QAM256 3 489000000 Hz 6.9 dBmV 40.5 dB 0 0
13 Locked QAM256 4 495000000 Hz 6.9 dBmV 40.5 dB 0 0
14 Locked QAM256 6 513000000 Hz 7 dBmV 40.5 dB 0 0
15 Locked QAM256 7 519000000 Hz 7 dBmV 40.4 dB 0 0
16 Locked QAM256 8 525000000 Hz 6.8 dBmV 40.3 dB 0 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 41.8 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 41.8 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 41.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 42 dBmV

Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power

Current System Time:Sat Jul 11 21:11:06 2020
System Up Time:00:03:19

0 Likes
Reply
JakeMaxis
Frequent Visitor
‎07-11-2020 10:15 PM

Re: Upstream issues causing disconnects again!

and the event log.

Time	Priority	Description
1970-1-1, 00:00:34	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:00:27	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:21	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:28	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:22	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:28	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:21	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-7-11, 13:49:29	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
2020-7-11, 13:49:05	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 13:44:45	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 13:44:45	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 13:44:45	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 13:44:26	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 13:44:25	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 13:44:25	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 13:43:17	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:43:42	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
2020-7-11, 10:43:12	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:39:14	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:39:12	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:39:12	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:39:07	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:39:06	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:39:06	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:37:58	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:21:58	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
2020-7-11, 10:21:28	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:17:17	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:17:15	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:17:15	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 10:16:07	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:58:28	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:54:08	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:54:08	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:54:08	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:54:06	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:53:47	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:53:47	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 09:52:40	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.1;CM-VER=3.0;
2020-7-11, 03:39:46	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:78:54:08;CMTS-MAC=00:01:5c:ae:1e:5b;CM-QOS=1.0;CM-VER=3.0;
0 Likes
Reply
Visit Our Help Communities