Tag:"T3" | Cox Community

Critical T3 Errors - Multiple
Need some assistance. I've had multiple issues with disconnects while gaming and the history of errors listed below is alarming. Need some advice. Connections are tight and secure. No splitters in line. Cox installed coaxial cables. I've done the trouble shooting within the apartment. Sat Nov 23 01:48:43 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MA... Mon Nov 25 21:38:42 2019 Notice (6) TLV-11 - unrecognized OID;CM-MAC= ;CMTS-MAC=... Tue Nov 26 15:12:18 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/... Tue Nov 26 15:12:18 2019 Warning (5) MDD message timeout;CM-MAC= ;CMTS-MAC=70:6e:... Tue Nov 26 15:12:21 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/... Tue Nov 26 15:12:22 2019 Warning (5) MDD message timeout;CM-MAC= ;CMTS-MAC=70:6e:... Tue Nov 26 15:12:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:13:00 2019 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00... Tue Nov 26 15:15:48 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:15:48 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:15:48 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:18:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:18:47 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:18:47 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:19:07 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:19:07 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retrie... Tue Nov 26 15:19:07 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream... Tue Nov 26 15:28:27 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Tue Nov 26 15:29:09 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4... Thu Nov 28 07:37:54 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Fri Nov 29 03:43:24 2019 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-... Sat Nov 30 05:43:25 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -... Sat Nov 30 05:43:27 2019 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MA... Sat Nov 30 05:44:32 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no U... Sat Nov 30 10:34:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received -...
stangcolts
5 years ago Place Internet
699Views
0likes
1Comment
no ranging response
I am constantly getting these errors I had this happen so much before I replaced my modem and router and signal is only going through one router. I've spoken to cox they sent out a tech said the signal line was good. ( of course it was good when he tested it then but after an hour or so it did it again this happened like 15 times earlier in the morning today 9/3) tried talking to cox on the phone as well and they just say the signal looks good talked to router and modem manufacturer and they say this is an issue with the ISP Thu Sep 05 18:39:19 2019 3 No Ranging Response received - T3 time-out;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:39:58 2019 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:39:59 2019 3 No Ranging Response received - T3 time-out;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:40:18 2019 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:40:19 2019 3 No Ranging Response received - T3 time-out;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:40:22 2019 3 Ranging Request Retries exhausted;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:40:22 2019 3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:40:58 2019 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Thu Sep 05 18:40:59 2019 3 No Ranging Response received - T3 time-out;CM-MAC=3c:04:61:44:9d:29;CMTS-MAC=00:b6:70:99:d0:ef;CM-QOS=1.1;CM-VER=3.0; Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked 256QAM 41 405.00 MHz 3.80 dBmV 38.98 dB 2253 12652 2 Locked 256QAM 1 783.00 MHz 10.50 dBmV 40.37 dB 590 5115 3 Locked 256QAM 2 789.00 MHz 10.80 dBmV 40.37 dB 367 4370 4 Locked 256QAM 3 795.00 MHz 10.40 dBmV 38.61 dB 730 2877 5 Locked 256QAM 4 801.00 MHz 10.20 dBmV 38.98 dB 494 6235 6 Locked 256QAM 9 831.00 MHz 10.30 dBmV 38.61 dB 1174 7087 7 Locked 256QAM 10 837.00 MHz 9.70 dBmV 38.98 dB 723 5763 8 Locked 256QAM 11 843.00 MHz 9.60 dBmV 38.61 dB 595 4218 9 Locked 256QAM 12 849.00 MHz 9.90 dBmV 38.98 dB 867 7166 10 Locked 256QAM 17 879.00 MHz 10.60 dBmV 38.98 dB 405 4517 11 Locked 256QAM 18 885.00 MHz 10.60 dBmV 38.98 dB 715 5133 12 Locked 256QAM 19 891.00 MHz 10.80 dBmV 38.61 dB 1009 6954 13 Locked 256QAM 20 897.00 MHz 11.00 dBmV 38.98 dB 771 7000 14 Locked 256QAM 21 903.00 MHz 11.10 dBmV 38.61 dB 1186 6446 15 Locked 256QAM 22 909.00 MHz 10.40 dBmV 38.98 dB 479 5315 16 Locked 256QAM 25 927.00 MHz 10.50 dBmV 38.98 dB 1047 5620 17 Locked 256QAM 26 933.00 MHz 10.90 dBmV 38.61 dB 1176 5733 18 Locked 256QAM 27 939.00 MHz 11.00 dBmV 38.98 dB 712 6406 19 Locked 256QAM 28 945.00 MHz 10.90 dBmV 40.37 dB 492 5236 20 Locked 256QAM 29 951.00 MHz 10.50 dBmV 38.61 dB 794 6213 21 Locked 256QAM 30 957.00 MHz 10.40 dBmV 38.61 dB 481 5322 22 Locked 256QAM 33 357.00 MHz 3.50 dBmV 38.61 dB 2169 14630 23 Locked 256QAM 34 363.00 MHz 3.40 dBmV 38.98 dB 2564 15093 24 Locked 256QAM 35 369.00 MHz 3.50 dBmV 38.61 dB 3046 17282 25 Locked 256QAM 36 375.00 MHz 3.70 dBmV 39.20 dB 62 2814 26 Locked 256QAM 37 381.00 MHz 3.70 dBmV 39.20 dB 98 3204 27 Locked 256QAM 38 387.00 MHz 3.40 dBmV 39.20 dB 78 2869 28 Locked 256QAM 42 411.00 MHz 3.90 dBmV 39.20 dB 196 3884 29 Locked 256QAM 43 417.00 MHz 4.10 dBmV 38.90 dB 319 4774 30 Locked 256QAM 44 423.00 MHz 4.40 dBmV 38.90 dB 357 5219 31 Locked 256QAM 45 429.00 MHz 4.10 dBmV 39.20 dB 434 5141 32 Locked 256QAM 46 435.00 MHz 4.10 dBmV 38.90 dB 317 5000 > Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 3 5120 kSym/s 32.20 MHz 37.21 dBmV 2 Locked ATDMA 4 5120 kSym/s 38.60 MHz 48.50 dBmV 3 ---- ---- 2 ---- 25.80 MHz ---- 4 Locked ATDMA 1 5120 kSym/s 19.30 MHz 43.50 dBmV
logiKing
6 years ago Place Internet
233Views
0likes
0Comments
Field Tech for T3 timeouts?
I've work in networking for 11 years, doing everything for working the Tier 3 help desk at Time Warner, to supporting network and internet services for fortune 500s. Currently I am a lead at TP-Link. In my years I have never had a field tech know how to fix a T3 timeout. But guess what that is what Cox is saying that I need to do. More than likely it will be a contractor who gets paid per job and has no clue as to what he is doing. This is a ridiculous waste of time. I called back and spoke to Tier 2, who said that they didn't see any errors on their end, although Tier 1 did. They said that Tier 1 didn't know how to read the system. Told me that a field tech as to come out before Maintenance can be sent to the node. I offered to send the logs of my modem but was told they can't take them. I swear if this tech tried to say it's my equipment I am going to go through the roof. Their is no way my modem or router for that matter are causing a service level issue.
Lead_at_TP-Link
8 years ago Place Archives
1.9KViews
0likes
3Comments
Increasing frequency T3 intermittent timeouts
I've been having t3 interference and subsequent intermittent disconnects for about a year now, have had techs out multiple times only to tell me they dont know the reason its happening. Linked is pics of what I think is the issue -- upstream bonded noise, I have changed modems 3 times (all self-produced), currently these stats are with Netgear CG3000Dv2 , its happening more and more often, I'm about to cancel service if I can't solve the problem. =( (I dc'd twice while writing this.)
taylor9dj
8 years ago Place Archives
2.2KViews
0likes
4Comments
Loss of connectivity, IPv6 only (no IPv4) and DOCSIS T3/T4 errors
Our two Win10 computers go from disconnected, IPv6 access only, IPv4 and IPv6 full access, everything ok and back again. This has been happening for several weeks. I have swapped out cable modem (NETGEAR C6300BD), NIC cards and switch in the house without impact. The ethernet interface often says: IPv4 Connectivity: No network access IPv6 Connectivity: Internet You can also see this in online forums as "only google works" as all IPv6 sites work - but there aren't many. When running diagnostics the error is "Ethernet" does not have a valid IP configuration" Not fixed. Also noticed teredo tunneling was being used to do IPv6 over IPv4 and that this is one of the least prefered methods. After reviewing cable modem event logs there are several T4 errors and some T3 errors. Therefore I believe this problem is between cable modem and Cox. NETGEAR C6300BD Event Log T4 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:28:33:90;CMTS-MAC=00:13:5f:05:c1:b1;CM-QOS=1.1;CM-VER=3.0;
JiminAlpine
8 years ago Place Archives
11KViews
0likes
21Comments
STILL HAVING PROBLEMS WITH MY INTERNET AFTER 6 MONTHS OF NO ONE REALLY FIXING IT!!! HELP???
THESE ARE MY LEVELS.....THEY GIVE ME FLUCTUATING UPLOAD AND DOWNLOAD SPEEDS. I HAVE THE ULTIMATE PACKAGE, AND YET HAVE FAILED TO SEE THE ULTIMATE SPEEDS!..... BELOW IS THE LEVELS AND MY EVENT LOG! Procedure Status Comment Acquire Downstream Channel 939000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK ^1/5D1F5F68/132003 Security Enable BPI+ Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR 1 Locked QAM256 94 939000000 Hz 10.1 dBmV 38.3 dB 2 Locked QAM256 93 933000000 Hz 9.7 dBmV 38.6 dB 3 Locked QAM256 95 945000000 Hz 10.3 dBmV 38.2 dB 4 Locked QAM256 96 951000000 Hz 10.4 dBmV 38.6 dB 5 Locked QAM256 89 909000000 Hz 9.1 dBmV 37.9 dB 6 Locked QAM256 90 915000000 Hz 9.1 dBmV 38.2 dB 7 Locked QAM256 91 921000000 Hz 9.3 dBmV 38.1 dB 8 Locked QAM256 92 927000000 Hz 9.0 dBmV 37.5 dB Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 35102000 Hz 41.5 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 20202000 Hz 41.8 dBmV 3 Locked TDMA and ATDMA 2 2560 Ksym/sec 23402000 Hz 41.8 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 28202000 Hz 41.8 dBmV AND HERE IS MY EVENT LOG Time Priority Description 2015-12-16, 02:35:00.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:34:18.0 Notice (6) TLV-11 - unrecognized OID;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:34:18.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:21:18.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:20:36.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:19:26.0 Critical (3) Resetting the cable modem due to docsDevResetNow 2015-12-16, 02:19:17.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 02:19:00.0 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 01:29:20.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 01:28:38.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-16, 01:16:24.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-15, 17:28:11.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-15, 03:44:10.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-14, 13:46:42.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 17:35:00.0 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 17:34:17.0 Critical (3) TLV-11 - Illegal Set operation failed;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 16:48:05.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-13, 14:37:02.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 22:43:11.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 12:51:40.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 08:10:20.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 08:10:20.0 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 08:10:20.0 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-12, 02:07:32.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-11, 09:20:53.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-10, 17:28:06.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-10, 13:15:53.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; 2015-12-09, 23:43:36.0 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=dc:ef:09:1c:6d:98;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Notice (6) WiFi Interface [wl0] set to Channel 4 (Side-Band Channel:N/A) - Reason:INIT Time Not Established Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:N/A) - Reason:INIT
VAbeachResiJA
9 years ago Place Archives
3.8KViews
0likes
2Comments
Extremely Slow Upload Speeds!!! Started Unicast Maintenance Ranging - No Response received
I have been a customer for a year now, and for four months out of the year i have been having intermittent problems. The thing is i work online and pay for the fastest internet speed that they have. My bill alone for internet is $90. I have been getting T3 and T4 timeouts constantly. They sent every level of tech out to my home, and still no fix!...... The last tech who was a supervisor said that the problem was a "plant issue". That was 2 months ago, now im still getting upload speeds @ 1.35mbps ......I hold meetings and conferences online streaming and because of this issue i have been messing up with work. Please!!!!! I need help!!! I have viewed this forum and other forums involving this problem and did the proper research, but no one will speak on this problem and there have been no resolution concerning these timeouts! HERE IS A RUNDOWN OF MY EVEN LOG! Mon Aug 24 06:46:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 06:03:37 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 06:02:31 2015 Critical (3) Resetting the cable modem due to docsDevResetNow Mon Aug 24 05:46:37 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 05:46:30 2015 Critical (3) REG RSP not received;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 24 05:20:18 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 13:43:54 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 05:34:34 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 23 03:00:25 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 23:48:54 2015 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 23:48:50 2015 Critical (3) REG RSP not received;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 23:47:39 2015 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 22 23:13:48 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 12:34:55 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 02:41:10 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 22 02:13:34 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Fri Aug 21 13:58:15 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Thu Aug 20 06:16:20 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Thu Aug 20 03:44:51 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Wed Aug 19 12:17:40 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Wed Aug 19 05:18:34 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Tue Aug 18 18:07:48 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 17 07:41:24 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Mon Aug 17 02:37:55 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sun Aug 16 01:45:48 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Sat Aug 15 18:09:15 2015 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:b0:ce:65:db:58;CMTS-MAC=00:13:5f:00:d7:ac;CM-QOS=1.1;CM-VER=3.0; Startup Procedure Procedure Status Comment Acquire Downstream Channel 813000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK ^1/675721E6/132003 Security Enabled BPI+ Downstream Bonded Channels Lock Status Modulation Channel ID Symbol rate Frequency Power SNR DOCSIS/EuroDOCSIS locked Locked QAM256 73 5360 Ksym/sec 813000000 Hz 8.7 dBmV 39.4 dB DOCSIS Locked QAM256 74 5360 Ksym/sec 819000000 Hz 8.0 dBmV 39.3 dB DOCSIS Locked QAM256 75 5360 Ksym/sec 825000000 Hz 7.3 dBmV 39.0 dB DOCSIS Locked QAM256 76 5360 Ksym/sec 831000000 Hz 6.7 dBmV 39.1 dB DOCSIS Locked QAM256 81 5360 Ksym/sec 861000000 Hz 7.0 dBmV 39.1 dB DOCSIS Locked QAM256 82 5360 Ksym/sec 867000000 Hz 7.0 dBmV 39.0 dB DOCSIS Locked QAM256 83 5360 Ksym/sec 873000000 Hz 7.3 dBmV 39.0 dB DOCSIS Locked QAM256 84 5360 Ksym/sec 879000000 Hz 7.1 dBmV 38.9 dB DOCSIS Upstream Bonded Channels Lock Status Modulation Channel ID Symbol rate Frequency Power Locked ATDMA 3 5120 Ksym/sec 28202000 Hz 43.0 dBmV Locked TDMA and ATDMA 1 2560 Ksym/sec 20202000 Hz 42.5 dBmV Locked TDMA and ATDMA 2 2560 Ksym/sec 23402000 Hz 44.5 dBmV Locked ATDMA 4 5120 Ksym/sec 35102000 Hz 44.5 dBmV 8/24/2015 6:37 AM EDT 68.13.216.18572.31 Mb/s 0.64 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:29 AM EDT 68.13.216.18551.47 Mb/s 4.25 Mb/s 35 ms Chesapeake, VA<50miShare8/24/2015 6:28 AM EDT 68.13.216.18547.72 Mb/s 1.17 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:25 AM EDT 68.13.216.18566.64 Mb/s 0.70 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:20 AM EDT 68.13.216.185167.37 Mb/s 13.69 Mb/s 29 ms Chesapeake, VA<50miShare8/24/2015 6:17 AM EDT 68.13.216.18581.83 Mb/s 13.42 Mb/s 30 ms Chesapeake, VA<50miShare8/24/2015 6:15 AM EDT 68.13.216.18545.23 Mb/s 1.62 Mb/s 31 ms Chesapeake, VA<50miShare8/24/2015 6:14 AM EDT 68.13.216.18598.19 Mb/s 2.25 Mb/s 29 ms Chesapeake, VA<50miShare8/24/2015 6:13 AM EDT 68.13.216.18554.85 Mb/s 4.09 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:11 AM EDT 68.13.216.18568.22 Mb/s 17.93 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 6:10 AM EDT 68.13.216.18591.54 Mb/s 3.17 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:10 AM EDT 68.13.216.185142.18 Mb/s 18.49 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:09 AM EDT 68.13.216.18575.50 Mb/s 5.51 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 6:07 AM EDT 68.13.216.18560.31 Mb/s 21.70 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 6:06 AM EDT 68.13.216.185150.58 Mb/s 21.98 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 6:05 AM EDT 68.13.216.18593.70 Mb/s 22.26 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 5:51 AM EDT 68.98.247.19962.60 Mb/s 1.74 Mb/s 33 ms Chesapeake, VA<50miShare8/24/2015 5:41 AM EDT 68.98.247.19969.84 Mb/s 3.49 Mb/s 32 ms Chesapeake, VA<50miShare8/24/2015 5:30 AM EDT 68.98.247.19973.57 Mb/s 5.13 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 5:29 AM EDT 68.98.247.199108.80 Mb/s 3.37 Mb/s 34 ms Chesapeake, VA<50miShare8/24/2015 5:28 AM EDT 68.98.247.199174.02 Mb/s 10.00 Mb/s 30 ms Chesapeake, VA<50miShare8/24/2015 5:27 AM EDT 68.98.247.199149.44 Mb/s 17.56 Mb/s 29 ms Chesapeake, VA<50miShare8/23/2015 2:15 PM EDT 68.98.247.19989.39 Mb/s 22.17 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 11:14 AM EDT 68.98.247.19993.95 Mb/s 22.35 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 11:04 AM EDT 68.98.247.19985.74 Mb/s 22.57 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 10:12 AM EDT 68.98.247.199142.90 Mb/s 22.35 Mb/s 33 ms Chesapeake, VA<50miShare8/23/2015 10:11 AM EDT 68.98.247.199137.29 Mb/s 22.57 Mb/s 31 ms Chesapeake, VA<50miShare8/23/2015 12:59 AM EDT 68.98.247.19962.82 Mb/s 1.15 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 12:58 AM EDT 68.98.247.19954.27 Mb/s 6.10 Mb/s 34 ms Chesapeake, VA<50miShare8/23/2015 12:55 AM EDT 68.98.247.19952.43 Mb/s 1.42 Mb/s 30 ms Chesapeake, VA<50miShare8/23/2015 12:38 AM EDT 68.98.247.19980.54 Mb/s 5.11 Mb/s 23 ms Rocky Mount, NC~100miShare8/23/2015 12:36 AM EDT 68.98.247.199109.39 Mb/s 22.28 Mb/s 21 ms Rocky Mount, NC~100miShare8/23/2015 12:35 AM EDT 68.98.247.19994.18 Mb/s 8.01 Mb/s 21 ms Rocky Mount, NC~100miShare8/23/2015 12:30 AM EDT 68.98.247.19988.04 Mb/s 0.61 Mb/s 22 ms Rocky Mount, NC~100miShare8/23/2015 12:29 AM EDT 68.98.247.19992.63 Mb/s 2.72 Mb/s 23 ms Rocky Mount, NC~100miShare8/23/2015 12:28 AM EDT 68.98.247.19979.95 Mb/s 8.43 Mb/s 22 ms Rocky Mount, NC~100miShare8/23/2015 12:26 AM EDT 68.98.247.19975.52 Mb/s 1.50 Mb/s 24 ms Rocky Mount, NC~100miShare8/22/2015 11:56 PM EDT 68.98.247.19948.79 Mb/s 1.37 Mb/s 23 ms Rocky Mount, NC~100miShare8/22/2015 11:39 PM EDT 68.98.247.19916.60 Mb/s 6.31 Mb/s 32 ms Chesapeake, VA<50miShare8/22/2015 11:10 PM EDT 68.98.247.19936.31 Mb/s 0.63 Mb/s 36 ms Chesapeake, VA<50miShare8/22/2015 11:03 PM EDT 68.98.247.19924.71 Mb/s 1.26 Mb/s 30 ms Chesapeake, VA<50miShare8/22/2015 11:02 PM EDT 68.98.247.19930.49 Mb/s 1.03 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 11:01 PM EDT 68.98.247.19916.06 Mb/s 0.14 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 10:59 PM EDT 68.98.247.19947.25 Mb/s 0.65 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 10:50 PM EDT 68.98.247.19917.18 Mb/s 10.56 Mb/s 27 ms Richmond, VA~100miShare8/22/2015 9:01 PM EDT 68.98.247.19921.48 Mb/s 2.91 Mb/s 32 ms Chesapeake, VA<50miShare8/22/2015 8:41 PM EDT 68.98.247.19958.12 Mb/s 22.61 Mb/s 37 ms Chesapeake, VA<50miShare8/22/2015 8:39 PM EDT 68.98.247.19923.78 Mb/s 1.63 Mb/s 31 ms Chesapeake, VA<50miShare8/22/2015 8:33 PM EDT 68.98.247.19931.64 Mb/s 1.46 Mb/s 34 ms Chesapeake, VA<50miShare8/22/2015 7:59 PM EDT 68.98.247.19948.69 Mb/s 8.34 Mb/s 33 ms Chesapeake, VA<50miShareLOAD MORE RESULTS HERE ARE MY SPEED TEST
VAbeachResiJA
10 years ago Place Archives
2.7KViews
0likes
1Comment
Motorola Surfboard SB6121 keeps resetting due to t3/t4 errors
As my subject says, I keep having my modem reset after maybe two to three hours. I check the modem logs and it tells me it is due to a t3 or t4 error. I have called tech support and they don't know and can't give me any form of solid answer. I have been bumped to tier 2 service and they just refresh the signal. I have a tech coming tomorrow, but I was hoping to get a handle on the issue, prior. Here are a few screens from my modem's logs and signal. any help would be awesome, thanks!
gmsols
10 years ago Place Archives
3KViews
0likes
3Comments
T3 and T4 Timeouts from an ex-field technician
Starting in September of 2013, I noticed my connection becoming intermittent at best. Voice conferencing and gaming would literally go from 23 ms to over 10k ms and then obviously I would disconnect from the server. About a week after this first started happening, it started to randomly disconnect while I was simply browsing the internet. I found the modem was cycling itself. At the time I had an extremely old but trusty Motorola Surfboard SB5100. Despite having this modem throughout the DOCSIS 3.0 updates, and despite it having worked fine through it all hither to the point in time, I figured it may be the modem (after a 12 year run, I wasn't complaining...) I accessed the modem diagnostic page at 192.168.100.1 and saw that in the logs there were massive amounts of T3 timeouts. Being an ex-field technician for Cox, I knew this could have gone one of two ways. It was either the modem or it was something in the node (most likely an amplifier in the trunk line) that was to blame. I called Cox for the heck of it just to see if they could see anything on their end, and as usual, no. Everything on their end was fine, but again, having been a field tech for 5 years, I know that phone based customer service is very limited, they're not at the house, they don't have a meter and they're sure as heck not taking level readings. Ok, fair enough. I purchased a Motorola Surfboard SB6141 to replace the 5100 and finally upgrade to DOCSIS 3.0. I called them, had the modem provisioned, went to the diagnostics page, was "wowed" by 8 downstream and 4 upstream channels, wondering why I had not upgraded the modem sooner, but alas, not 2 hours after provisioning, there was a T3 timeout. Now I know it's not the modem, time to get on the phone and make things happen. I called, they said they would send a tech out. The tech (CONTRACTOR) came out and I explained the whole situation to him. I showed him the modem diagnostics, I explained what I knew about everything, and he agreed with me. He did NOT check levels, he did NOT check the tap at the pole (I have a 340 foot drop from the pole to the house, it's RG-11. A new install was done less than a year ago, including the drop and inside lines, and I told him this, so he probably "assumed" things were good up there...). He scheduled a 5C, which is the "internal" code name for "get a maintenance (plant) technician out to the pole to see what's up". I got a call from my old lead technician about a week later. He told me that the maintenance tech found water in the drop and cut it back to where the "stinger" (copper in the connector) wasn't black from water damage, and that another tech would be out in the next day or two in order to run a new drop. Two days later ANOTHER CONTRACTOR comes to the house to run the new drop. I saw his spool of RG-11 and I knew he didn't have enough left to get from the pole to the house. He removed the drop at the sub pole, and due to not wanting to bother him, I came back inside. 20 minutes later I went back out and he was gone. He never replaced the drop. He probably figured he didn't have enough cable to do it after removing the drop at the sub pole, rehung it, and left. This pissed me off. In the meantime I contacted my old lead and asked him what the deal was, explaining that not only were these T3's still happening, but they were getting worse, and they were leading into T4's. He scheduled for the drop to be re-run AGAIN the next week and made sure it would be an in house guy arriving, NOT a contractor. Sure enough, another lead technician and a field tech came to the house and ran a new drop. They didn't have enough RG-11 so they ran half RG-11, then installed a ground block at the sub pole and ran RG-6 the rest of the way. He said he would be back (this was a month ago and it still hasn't happened) to replace the RG-6 half of the drop with RG-11. He gave me his cell number to contact directly if this kept going on. It kept going on. The T3's were getting worse. I asked him on the phone to set up a 5C, he said he would but this was a week and a half after he replaced the drop and hadn't been out to finish the RG-11, so my faith in relying on him was null. I therefore called customer service. I explained that, despite having JUST bought a new modem, FIOS was a phone call away if this wasn't resolved. Per usual, they went RIGHT back to square one and wanted to send out a tech. I told them to stop reading the script from their screen and focus on their keyboard in order to LISTEN AND UNDERSTAND exactly what I had JUST explained to them. For over a month I was implying that this was a plant issue, no one wanted to listen. The phone techs didn't want to listen, the lead techs did not want to listen, the lead techs kept coming back with 50 other excuses as to what could be causing it. I questioned them as to why they would do this when they knew I used to be a tech and I wasn't an idiot. The final call was made to customer service. Again, they said they had to send a tech out, despite two months of this **, in order to get a 5C scheduled. Ok, last time I am playing this game. The tech came out and I caught him on my way home from work. He was an in house guy and I caught him as he was at the pole taking levels. He told me that every port from the tap was bonkers, he replaced the tap and the levels were STILL bonkers, and that he did not understand how two lead techs and four field techs didn't realize this was a plant issue from day one. I concurred. He took down every piece of information I gave him about the new drop, the new modem, signal levels at the modem, etc, etc, and made a detailed log for the maintenance techs who came out. He also told me that there are only SIX HOUSES ON MY NODE, LITERALLY. This means that the trunk line feeding my house only feeds a total of 6 houses. Do you know how easy that is for plant (maintenance) to troubleshoot? There is one amplifier that is literally humping my tap, if here's an inch of trunk line from the amplifier into the tap then it's a lot. I suspected that amplifier from the get go, but even if it wasn't, there would only be at most ONE MORE amplifier in that node, so yeah, one amp checked out good, guess which one's bad? Real easy stuff here people, real easy. So, the tech scheduled the 5C (the second one that had to happen in this whole fiasco), and the maintenance tech came out. I don't know if it was the same or a different one, but this time around (after TWO MONTHS OF THIS **) the problem was resolved. It has been two weeks and I have not seen a single T3 or T4 in my log. I see where it lost connection due to the maintenance guy doing what he had to do and of course the service gets interrupted during this, but honestly, after the modem cycle, there is not ONE added entry to the log, nothing; whereas every other "visit" would result in a T3 less than 10 minutes later. These T3 (and later T4's due to the issue getting progressively worse) were happening every ten to twenty minutes on some days, other days every hour or so. I use VOIP for telephone. Imagine not having 911 access for the whole day because your ISP can't get it's act together. I held out having FIOS reinstalled (it was installed here when it first came out) because I honestly can't stand those hacks. Having said that, had that last tech not been so thorough, had the second maintenance tech not done his job and resolved the issue, Verizon was seriously the next phone call. I didn't go into a whole lot of detail about levels and diagnostics here because I did enough of that with customer service and all the techs that visited. I wanted to make a point here to Cox. Not all customers are complete idiots. Not all customers have zero clue about how information travels from their house to the MTC. Maybe instead of treating everyone equally as morons, you should start treating them all equally as intelligent folk. Imagine how many folks out there were never field techs, imagine how many would have switched back to Verizon within the first week, let alone sticking it out for two months. I was a field tech, I have working knowledge of the system, I was treated like a complete idiot, how do you think that makes me feel? It actually makes me feel pretty damned good right about now knowing I was right the whole damned time about the issue being a plant related occurrence, but I can tell you right now when these people tell you over the phone and face to face that you're "wrong", and that they need to go through steps that, again as an ex-tech, you KNOW they don't need to go through, all the while the internet that we pay for monthly and (in some cases) our phone service (through another provider in my instance) has fallen to complete useless garbage, labeling it as "infuriating" somehow undermines the true nature of it. I know that not every single problem faced is one of a plant issue, this is obvious. Red flags should be raised, however, after every single other step has been taken and fails, instead of attempting to loop the same damned process all over again; that is simply ridiculous. What is also ridiculous is the fact that contractors are being sent in place of in house technicians and basically this leads to repeat trouble calls. This is something that is completely unacceptable, especially when one has to take time out of their day (or out of work) every time a call has to be rescheduled. I know not every contractor is a bad contractor, but out of the entire bunch, I can name 3 that I would have work at my house, that's about it. To make it relative to the in house technicians, I can list about 20 off the top of my head that I would let work at my house from start to finish with a cable job any day of the year. I hope this type of issue, or at least the steps to the resolution of this type of problem does not happen again. I will definitely be more prone to calling Verizon early on if an issue is not resolved in a suitable amount of time, not TWO MONTHS AFTER.
Old_Field_Tech
11 years ago Place Archives
46KViews
4likes
2Comments
Motorola Surfboard SB6141 Lost Connection Issues
My modem keeps dropping connection the last few days and last night it was really bad. It was constantly trying to reboot. Here is what i was able to capture before it tried to reboot again. Time Priority Code Message Jan 01 1970 00:28:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:44 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:24 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:02 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:42 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:41 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:21 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:02 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:30 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:25:53 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:25:34 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:25:33 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0;
Solved
gmcmenimen
12 years ago Place Archives
16KViews
0likes
3Comments