Seer's profile

New Contributor

 • 

41 Messages

Closed

Constant drop of signal from CG3000-RD

WHat is going on Cox several times a day I lose my internet connection and it takes a minute or 2 for it to return.  Several times I watched the gateway reboot itself and on other times the lights on the front looked ok.  I am paying good money for a service and not getting it.  I do not need someone to keep telling me to reboot the modem or they can see nothing wrong yet there are all these critical errors in my log and they all correspond to the times I have lost my signal.  Am I going to have to keep wasting my time paying for something that is not working all the time by making repeated trips to a local cox outlet for a replacement gateway for which I am paying rent on?

 Tue Nov 26 06:38:22 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Tue Nov 26 06:37:40 2013    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Mon Nov 25 17:34:11 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Mon Nov 25 09:59:42 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sun Nov 24 23:58:57 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sun Nov 24 18:57:01 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sun Nov 24 10:38:54 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sun Nov 24 05:21:18 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sat Nov 23 15:32:29 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sat Nov 23 06:18:13 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Fri Nov 22 22:28:15 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Fri Nov 22 14:50:46 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Thu Nov 21 18:22:02 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established   Warning (5)   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established   Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.0;CM-VER=3.0; 

Valued Contributor III

 • 

4.2K Messages

Looks like maybe you have low signal levels. Could you post them? You can find them Maintence > Gateway Status > Connection Status.(See page 22 for more info)

New Contributor

 • 

41 Messages


Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 837000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK DEF001_vm2.0_d.cfg
Security Enabled BPI+

Downstream Bonded Channels
Lock Status Modulation Channel ID Symbol rate Frequency Power SNR DOCSIS/EuroDOCSIS locked
Locked QAM256 89 5360 Ksym/sec 837000000 Hz 0.1 dBmV 40.3 dB DOCSIS
Locked QAM256 90 5360 Ksym/sec 843000000 Hz 0.1 dBmV 40.6 dB DOCSIS
Locked QAM256 91 5360 Ksym/sec 849000000 Hz 0.1 dBmV 40.4 dB DOCSIS
Locked QAM256 92 5360 Ksym/sec 855000000 Hz -0.4 dBmV 40.4 dB DOCSIS
Locked QAM256 93 5360 Ksym/sec 861000000 Hz -0.5 dBmV 39.9 dB DOCSIS
Locked QAM256 94 5360 Ksym/sec 867000000 Hz -1.1 dBmV 39.7 dB DOCSIS
Locked QAM256 95 5360 Ksym/sec 873000000 Hz -1.0 dBmV 39.5 dB DOCSIS
Locked QAM256 96 5360 Ksym/sec 879000000 Hz -0.8 dBmV 39.9 dB DOCSIS

Upstream Bonded Channels
Lock Status Modulation Channel ID Symbol rate Frequency Power
Locked ATDMA 3 5120 Ksym/sec 36100000 Hz 38.5 dBmV
Locked TDMA and ATDMA 1 2560 Ksym/sec 23300000 Hz 36.8 dBmV
Locked ATDMA 2 5120 Ksym/sec 29600000 Hz 38.8 dBmV
Unlocked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

Current System Time:Tue Nov 26 10:19:36 2013

Valued Contributor III

 • 

4.2K Messages

Well I was wrong. Those signal levels are about as good as you can get.  Better then mine actually 

So if signal levels are good and your getting T4 then next thing I would say is hardware, but you said you have replaced that multiple times.

::Edit:: I think you need a technician and have them focus on the upstream frequency around 23300000Hz.

Locked ATDMA 3 5120 Ksym/sec 36100000 Hz 38.5 dBmV
Locked TDMA and ATDMA 1 2560 Ksym/sec 23300000 Hz 36.8 dBmV
Locked ATDMA 2 5120 Ksym/sec 29600000 Hz

38.8 dBmV

Could just be the way the area is configed, but something seems odd about Channel ID 1. The lower SNR, different symbol rate. Its not anything I would say is "bad" by any means but atleast its a place to start.

New Contributor

 • 

41 Messages

I was getting this issue with my old surfboard so I foowed Cox's advice and got a new gateway from them stiill not working maybe i need to get another one to to troubleshoot it

 

Valued Contributor III

 • 

4.2K Messages

No, I doubt its the hardware if the problem occured with 2 seperate modems, unless they are different problems.

I would check the power(electrical). Do you have it connected directly to a electrical wall socket? 

New Contributor

 • 

12 Messages

I'm having the same problem, ugh

Former Moderator

 • 

7.1K Messages

@susie

I'm wondering if in your case the issue might be power related based on some of the diagnostic data I'm seeing from this end.  Do you have the modem plugged into some kind of power strip with a lot of other devices?  I'd suggest trying to plug it into a different outlet or circuit if possible and see if there is any change.

New Contributor

 • 

41 Messages

Not a power issue as it is plugged directly into a wall outlet.  Just before this my modem decided to reboot itself and this is my recent log.  Looks like someone is trying to get into my modem as well.  What is it with all these critical errors and problems right now I am sick of this **.

Fri Nov 29 07:34:48 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Fri Nov 29 07:34:07 2013    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Fri Nov 29 01:00:58 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Thu Nov 28 09:06:59 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Wed Nov 27 20:55:50 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Wed Nov 27 19:11:28 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Wed Nov 27 12:45:02 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Wed Nov 27 00:41:24 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Tue Nov 26 14:12:50 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Tue Nov 26 06:38:22 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Mon Nov 25 17:34:11 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Mon Nov 25 09:59:42 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 

Former Moderator

 • 

7.1K Messages

What are you seeing that looks like somebody is trying to get into your modem?  As for the events you're seeing, it may be necessary at this point to arrange for a technician to come out and troubleshoot further.

New Contributor

 • 

41 Messages

 Admin login authentication fail 

When I copied the log there were several of these but when I pasted it they disappeared.  I know I did not cause them.

Former Moderator

 • 

7.1K Messages

You can recover from that by doing a factory reset and using the information on the bottom of the device to connect wirelessly.  The admin password to access the router settings would also be reset allowing you to login and change it.

New Contributor

 • 

41 Messages

Why is it rebooting itself then is another question I got htis new form the cox store and pay a lease rate on it.  Can I just return it and get another?

Former Moderator

 • 

7.1K Messages

You could certainly give that a try first.  If that doens't help it may be necessary to arrange for a technician to come out and troubleshoot further.

New Contributor

 • 

41 Messages

Well here we go again some things never change I am wasting my time to get this looked at.


Time Priority Description
 Mon Dec 02 08:01:00 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Mon Dec 02 08:00:19 2013    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sat Nov 30 19:51:53 2013    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sat Nov 30 12:37:52 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0; 
 Sat Nov 30 04:07:54 2013    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:22:65:98;CMTS-MAC=00:21:a0:fb:23:75;CM-QOS=1.1;CM-VER=3.0;