U

Thursday, September 28th, 2023 11:29 PM

Closed

Motorola 7540 persistent connection losses

Over the past 3 or 4 days, we have been experiencing connection losses ranging from as little as twice per day to as much as hourly. Up until now, we've had very stable connectivity. The only thing that changed on my side is the addition of a secured guest wifi login, and our main network's password. 

  Cable Specification Version DOCSIS 3.0
  
   Hardware Version V1.0
  
   Software Version 7540-5.7.1.36
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 25 627.0 4.3 39.8 401665 320039
2 Locked QAM256 17 579.0 4.9 40.3 442492 329218
3 Locked QAM256 18 585.0 4.4 40.1 751515 483402
4 Locked QAM256 19 591.0 4.1 40.1 764777 468026
5 Locked QAM256 20 597.0 4.9 40.2 779452 481193
6 Locked QAM256 21 603.0 4.4 40.1 768995 466327
7 Locked QAM256 22 609.0 4.1 40.1 767229 463542
8 Locked QAM256 23 615.0 4.9 40.1 773796 480698
9 Locked QAM256 24 621.0 4.2 40.0 761957 458312
10 Locked QAM256 26 633.0 5.5 40.2 763670 440052
11 Locked QAM256 27 639.0 4.6 39.9 755591 496412
12 Locked QAM256 28 645.0 4.5 40.0 761243 449189
13 Locked QAM256 29 651.0 5.8 40.2 753319 429014
14 Locked QAM256 30 657.0 4.9 40.0 759027 456211
15 Locked QAM256 31 663.0 4.8 40.0 749292 441502
16 Locked QAM256 32 669.0 6.1 40.1 745956 447988
Total             11499976 7111125


   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 3 5120 22.8 45.5
2 Locked ATDMA 2 5120 16.4 45.5
3 Locked ATDMA 4 5120 29.2 45.8
4 Locked ATDMA 5 5120 35.6 46.0

Below is my Event log for this morning, with private info removed.

Time   Priority   Description 
 Thu Sep 28 11:38:07 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:39:40 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
 Thu Sep 28 11:41:44 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:43:19 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
 Thu Sep 28 11:43:33 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:44:50 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; 
 Thu Sep 28 11:45:00 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:45:53 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; 
 Thu Sep 28 11:46:16 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:47:25 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; 
 Thu Sep 28 11:47:33 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:48:32 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
 Thu Sep 28 11:48:47 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:49:52 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; 
 Thu Sep 28 11:50:11 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:51:26 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
 Thu Sep 28 11:51:29 2023    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 
 Thu Sep 28 11:51:36 2023    Warning (5)   Lost MDD Timeout;
 Thu Sep 28 11:51:46 2023    Critical (3)   No UCDs Received - Timeout;;
 Thu Sep 28 11:52:08 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:53:05 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
 Thu Sep 28 11:53:17 2023    Critical (3)   No Ranging Response received - T3 time-out;
 Thu Sep 28 11:53:30 2023    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out; 
 Thu Sep 28 11:54:12 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; 
 Thu Sep 28 11:54:29 2023    Critical (3)   No Ranging Response received - T3 time-out; 
 Thu Sep 28 11:55:42 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
 Thu Sep 28 11:55:55 2023    Critical (3)   No Ranging Response received - T3 time-out;
 Thu Sep 28 11:56:30 2023    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;
 Thu Sep 28 11:57:02 2023    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
 Thu Sep 28 11:57:09 2023    Critical (3)   No Ranging Response received - T3 time-out
 Thu Sep 28 11:57:21 2023    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Thu Sep 28 11:58:36 2023    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;

Gold Problem Solver

 • 

26.3K Messages

2 years ago

... experiencing connection losses ranging from as little as twice per day to as much as hourly ...

Downstream, power levels and SNR values look good. Error counts seem high, but can't really be evaluated without knowing how long it has been since the counters were reset. The upstream power levels look good. There are other signal quality measures that the modem does not report, and the intermittent nature of the problem makes it harder to troubleshoot, so all we can say is between your observations and the Event Log entries, something is wrong.

Network connection problems like this are often due to poor coax connections or damaged coax cable, usually in or near your home. Running the cable through a surge protector, a defective splitter, or too many splitters can cause signal problems as well. If there is an amplifier in the line make sure it's getting power. 

If you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you can't find the problem or you'd rather have Comcast take care of it and an employee does not respond to your message here, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit (approx $100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

4 Messages

2 years ago

Thanks for taking a look. Per the coax, we don’t have a splitter or amplifier. The line from outside comes in, hits a single adapter (female-to-female), and goes directly to the modem. Nothing on the interior has been modified or moved, and the connections are solid. The modem currently has my up time as 1d: 15min, but there have been lapses in connectivity all day. I’ll troubleshoot the best I can and then have a tech out to check the supply coax. Thanks again.

forum icon

New to the Community?

Start Here