Start a New Discussion

Start a New Discussion

Orbi WiFi 7 RBE973
Reply

Connection dropping once or twice in an hour, not sure what to make of the logs

gaowebdv
Follower
Follower
‎2020-07-08 04:50 PM
‎2020-07-08 04:50 PM

Connection dropping once or twice in an hour, not sure what to make of the logs

I'm on my 3rd modem now. Replaced an old one with SB6190 because I was having issues with network dropping constantly. Issue wasn't resolved so got CM700 and the issue continues. I think the problem is with the isp but I'm not sure how I would find that out. Can someone who is knowledgeable please look at my modem logs and tell me what's wrong with my internet?

TimePriorityDescription
Jul 08 2020 17:37:14Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 17:37:14Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 17:37:14Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 17:37:44Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 17:37:44Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 17:37:49Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 17:37:49Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 17:39:00Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jul 08 2020 17:39:17Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 17:39:38Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 08 2020 17:51:53Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 19:18:56Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 19:18:57Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 19:19:56Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 19:19:56Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 19:20:00Critical (3)Ranging Request Retries exhausted
Jul 08 2020 19:20:00Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted
Jul 08 2020 19:20:00Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 19:20:13Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 19:20:14Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 19:20:53Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 08 2020 19:46:07Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:03:01Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 20:03:01Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:03:04Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 20:03:04Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:04:31Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jul 08 2020 20:05:07Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:05:29Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 08 2020 20:31:39Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:31:39Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 20:31:40Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:32:15Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 20:32:15Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:32:19Critical (3)Unicast Ranging Received Abort Response - initializing MAC
Jul 08 2020 20:32:20Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 20:33:28Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Jul 08 2020 20:33:57Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Jul 08 2020 21:45:05Critical (3)No Ranging Response received - T3 time-out
Jul 08 2020 21:48:08Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Jul 08 2020 21:53:05Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

Here's the messages only since it seems the full table above is getting cut off

Description
No Ranging Response received - T3 time-out
No Ranging Response received - T3 time-out
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
No Ranging Response received - T3 time-out
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Ranging Request Retries exhausted
Unicast Maintenance Ranging attempted - No response - Retries exhausted
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
No Ranging Response received - T3 time-out
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Unicast Ranging Received Abort Response - initializing MAC
No Ranging Response received - T3 time-out
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
No Ranging Response received - T3 time-out
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
No Ranging Response received - T3 time-out
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

 

 

 

Model: CM700|High Speed Cable Modem—DOCSIS 3.0
Message 1 of 2
0 Kudos
Reply
plemans
Guru Guru
Guru
‎2020-07-09 09:52 AM
‎2020-07-09 09:52 AM

Re: Connection dropping once or twice in an hour, not sure what to make of the logs

You also need the screen snip of the cable connections page. 

The T3 errors tend to be line issues through. And if you're on your 3rd modem, it probably isn't the modem.

If you have any splitters, amplifiers, attenuators in line, remove them. 

You'd want the isp to check the line. 

Message 2 of 2
Reply
Discussion stats
  • 1 reply
  • ‎2020-07-08 04:50 PM
  • 632 views
  • 1 kudo
  • 2 in conversation
Announcements

Orbi WiFi 7