| Time |
Priority |
Description |
| Thu Nov 07 23:20:19 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Thu Nov 07 16:34:28 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Thu Nov 07 16:33:44 2013 |
Notice (6) |
TLV-11 - unrecognized OID;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Thu Nov 07 16:33:43 2013 |
Warning (5) |
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Thu Nov 07 16:33:26 2013 |
Notice (6) |
TLV-11 - unrecognized OID;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Thu Nov 07 12:55:19 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Thu Nov 07 03:46:29 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:57:00 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:56:01 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Nov 05 23:29:33 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:29:31 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:28:07 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:28:07 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:27:51 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:27:51 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:27:37 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:27:37 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:27:22 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:27:21 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:26:18 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:26:17 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:26:15 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:26:08 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:26:05 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:19:15 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:18:39 2013 |
Critical (3) |
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:18:09 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Tue Nov 05 23:11:48 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:11:46 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Tue Nov 05 23:11:32 2013 |
Critical (3) |
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established |
Warning (5) |
DHCP WARNING - Non-critical field invalid in response ;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established |
Critical (3) |
No Ranging Response received - T3 time-out;CM-MAC=44:94:fc:ca:8f:09;CMTS-MAC=50:57:a8:89:44:9d;CM-QOS=1.0;CM-VER=3.0; |
Health_Edge
Valued Contributor III
•
4.2K Messages
3 T3 errors and 1 T4 error over 4 days. I wouldn't think that would be problematic and would cause a issue more with instances of lag sometimes and not throughput.
Are the speed tests direct to the modem? When Ultimate was installed, where you getting 100Mb then? Also what are the signal levels of the modem?
0
0
DerrickW
Valued Contributor
•
1.2K Messages
The modem log doesn't help much for this type of issue. We can check the signal levels and have you ping some IP addresses and run a couple of trace routes to see if there are any lags on the network that could be causing the slow upload.
I also ran a speed test on the site testmy.net, when I checked the result details it shows the destination as Dallas TX. That would explain lower results as the test server is further away. We need to check the signal levels of the modem, make sure everything is good on our end. Are you connected to a router or direct to the modem?
0
0
Kevfactor
New Contributor
•
32 Messages
Yeah directly to the big gate way with an Ethernet. i have another router but i just use that for the houses laptops which only browse sites maybe 3 times a week.
i think i always had this problem because the house has some old wiring. I tried streaming before when i was only getting 1.5 upload speeds and couldn't do at like 650 kbs. i get the speeds here and there but i think it's just like you said maybe lag issues in constantly getting those speeds.
edit: dids't see the admin. but yeah the computers are plugged into the modem. on testmy.net it has a DC server which i got around 3 upload(bit better at least hehe).
0
0
DerrickW
Valued Contributor
•
1.2K Messages
Yes, 3 Mbps is much better than 650 kbps lol I would have to agree! Sounds like you have a smarthome with built-in ethernet outlets. Would it be possible to test a direct modem connection (provided it's not too difficult, depending on where your modem is)?
0
0
Kevfactor
New Contributor
•
32 Messages
nope it is directly plugged into the modem/gateway that was provided with the net package. no ethernet outlets(i wish!). one pc that i dont use much has a 20 foot ethernet cable running accross the home, the other that i use all the time is about 3 feet away from the modem/gateway thing.
0
0
Health_Edge
Valued Contributor III
•
4.2K Messages
What kind of modem/device are you plugging in to? That is important. What is the model number of the modem from Cox? Should be printed on a sticker somewhere on it.
0
0
Accepted Solution
DerrickW
Valued Contributor
•
1.2K Messages
0
0
Kevfactor
New Contributor
•
32 Messages
thx found something! seems to be getting worse as now it's getting bad scores on both speedtest and the cox site too. I'll try to set something up one one of my days off work :)
0
0