DBoss
New Contributor II
Joined 4 years ago
User Profile
User Widgets
Contributions
- 6Views0likes0Comments
Re: Packet loss for over 6 years
Read my messages to Ryan. Since I am dropping packets to my first hop, there is no reason to do a traceroute. This would look like packet loss to ip72-210-60-1.ph.ph.cox.net in your screenshot. If I'm dropping packets to the first hop, then it's not even getting to the plant, much less the major hub in Dallas/FTW2Views1like0CommentsPacket loss for over 6 years
I've had packet loss issues on and off for the past 6 years. Every time it is a huge ordeal on my end with having multiple techs come to my house, diagnose nothing wrong, changing out all of my network equipment, and eventually getting someone who has access to the full logs solve my issue. This typically takes 3 weeks minimum. Today marks 1 month of dealing with this this time. I've called the FCC, the Mayor's office, my business reseller Cox rep since I resell Cox to dozens of local businesses and still they can't get this one residential issue resolved. When COVID started in March, I was having the same issue of dropped packets to my first hop (the node). This is an intermittent issue and I've told every tech I've worked with that. They still ignore me and close the ticket and I'm back to square one a day or week later when the issue returns. I will be on VOIP calls with clients, remoted into their servers, workstations, or network equipment and unable to accomplish the tasks they are paying me for because the packet loss starts and I drop connection to those systems. I now have a Cox rep that the Mayor called for me. He stated he would be sending a troubleshooting specialist to help diagnose the issue. They sent a Tier 1 tech that installs internet. This tech found 0.4% packet loss but they don't do anything below 1% packet loss so another closed ticket. If it were just 0.4% packet loss all the time I would not be dropping calls or connections. I have screenshots of packet loss to the node going back months, and the recent issue coming back a little over a month ago has screen shots at least every other day. I understand issues can be hard to diagnose. When I'm having those issues I place monitors and my best guys on them so I know it will be resolved. I do not just close a ticket. When I'm working with someone in the industry that knows something about networks/tech, I gather as much detail as they can give me, including logs, screenshots, troubleshooting they have already attempted, ect. I have all these things and have offered them to both the field techs and account reps but none want this info. This info has timestamps with examples of the packet loss to the first hop. I have screenshots of the modem event log for the entire month. I do not understand how such a large company can't triage a simple household issue properly when I run a tech business that has a fraction of their Gross revenue and can resolve internal networking issues in less time. Even if I couldn't I would be doing everything in my power to get them a stable connection. Instead I have cox charging me full price with no end in sight of this nightmare. Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=REDACTED;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Thu Oct 15 09:59:52 2020 Critical (3) Resetting the cable modem due to docsDevResetNow Thu Oct 15 10:01:45 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out 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-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.0;CM-VER=3.0; Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.0;CM-VER=3.0; Thu Oct 22 17:15:37 2020 Notice (6) TLV-11 - unrecognized OID;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.0; Fri Oct 23 09:45:06 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.0;1.9KViews1like10Comments