Skip to main content
Rabiya's profile

Rabiya

New Contributor II

 • 

14 Messages

Closed

Cox connection drop @85044

Please see above logs in modem and cox fix this pls, I tried with 3 different modem, issue started 3-4 weeks ago

Discussions

 • 

Updated 

2.7K

2

0

0

J

JonathanJ

Former Moderator

 • 

1.9K Messages

@Rabiya

I've checked the surrounding area and not showing any issues the would be affecting the modem. Check the modem signal levels and they're not at the levels we like seeing them. You mention you have tried different modem. Have you check the coax cable and make sure there are no kinks and the conductor (copper pin ) is bent or just try swap the coax if you have a spare?


Jonathan J
Cox Moderator

9

0

R
Rabiya

New Contributor II

 • 

14 Messages

I tried different coax (new fresh out of pack no kinks) and also tried another room, got different power level but still same disconnect 

Like

Reply

0

D
Dave9

Contributor III

 • 

251 Messages

You posted firewall/router logs but you need to post cable modem logs. Also look at the high error rate on channel 2/927 MHz. Possible RF ingress.

Like

Reply

0

R
Rabiya

New Contributor II

 • 

14 Messages

Are these better?  I changed back to my modem that was verified working in optimal condition by cox technician a year back. I just started seeing issues 3-4 weeks ago and had to swap and try with other modem.( The log earlier posted was from router /modem combo netgear c3000. )

Like

Reply

0

D
Dave9

Contributor III

 • 

251 Messages

That still a lot of errors. And the SNR looks low. Can you post the logs too? When you changed the cable, was the modem unplugged from power? If you don't know how to post the logs you would need a Cox representative to look at those for you.

Like

Reply

0

R
Rabiya

New Contributor II

 • 

14 Messages

Aug 20 2020 07:55:25 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 07:55:25 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:26 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:18 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:13:55 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:13:51 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:13:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:13:31 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:13:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:13:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:12:51 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:12:51 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:12:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:12:31 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:12:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:12:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:11:51 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:11:51 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:11:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;
Aug 20 2020 06:11:31 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:38:df:9b:d9:ce;CM-QOS=1.1;CM-VER=3.0;

Like

Reply

0

R

Rabiya

New Contributor II

 • 

14 Messages

jonathanj  dave9 also started seeing T4, what should be the value to expect on SNR or power level?

Cable Modem Reboot due to T4 timeout ;CM-MAC=d0:39:b3:f8:cc:46;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

3

0

D
Dave9

Contributor III

 • 

251 Messages

SNR isn't great but it's technically within specs. I don't know if I trust those power levels. All channels perfectly 0 dBmV doesn't seem possible. Maybe someone from Cox can confirm those levels. This doesn't look like an easy answer.

Like

Reply

0

D
DannyS

Moderator

 • 

656 Messages

Hello, if still finding concerns over the connection and need us to check anything that could be affecting the connection? We would be happy to do so for you. When available can you please reach us on Twitter at @CoxHelp, visit us on Facebook, or email by at cox.help@cox.com for assistance anytime. -Dan

Like

Reply

0

R
Rabiya

New Contributor II

 • 

14 Messages

Yes, I need help, I see lots of T3 time out and T4 reboot of modem automatically happening, the issue is not getting resolved for me

Like

Reply

0

Related Content

Recent Discussions