CM500-100NAS intermittently slow internet

Question

Hi,Yesterday, if I tried to browse the web, the browser would just hang, but now everything seems to be fine. This happens every now and then. All of the lights on the modem were green. This modem is on their support modems list. An XFinity tech came down and said that the signal they're putting out is fine. They made the cable connection to our apartment more secure, and I don't see any loose connections. The firmware on the modem (pushed by the ISP) is the latest version. I checked out the modem's config page for errors in the log, and I found this:Time Priority Description 2024-2-26, 20:18:59Warning (5)Dynamic Range Window violation2024-2-26, 20:18:45Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:00:28Notice (6)Honoring MDD; IP provisioning mode = IPv61970-1-1, 00:00:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-2-26, 19:52:04Critical (3)Resetting the cable modem due to docsDevResetNow2024-1-16, 18:29:59Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-16, 18:29:58Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-16, 18:29:55Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-16, 18:29:54Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-16, 18:29:53Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-16, 18:29:52Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2024-1-16, 18:29:49Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2024-1-16, 18:29:47Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2024-1-16, 18:29:46Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2024-1-16, 18:29:11Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2024-1-16, 18:29:04Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2024-1-16, 18:28:58Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2024-1-16, 18:28:55Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-12-20, 23:35:05Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-12-18, 01:20:26Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-12-11, 08:57:48Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-11-16, 10:48:29Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-11-16, 10:48:17Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-11-11, 16:29:49Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:00:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-10-25, 10:44:04Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-10-25, 10:31:04Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-10-25, 09:55:47Critical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.0;CM-VER=3.0;2023-10-25, 09:55:33Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;2023-10-25, 00:04:09Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:00:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-10-10, 17:45:56Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;1970-1-1, 00:00:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-10-10, 14:46:04Critical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.0;CM-VER=3.0;2023-10-10, 14:45:58Critical (3)No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-10-10, 14:45:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-10-10, 14:45:38Critical (3)No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-10-10, 14:45:19Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;2023-10-10, 14:45:18Critical (3)No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;1970-1-1, 00:56:25Critical (3)No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.0;CM-VER=3.0;&nbsp;The error at the top from yesterday (2024-2-26) is the most relevant, but I provided the whole log to help with context. I think the fifth error down is when XFinity was resetting the modem since I gave them a call.Finally, these are my modem's metrics:&nbsp;Do these look normal?Any help is greatly appreciated. I work from home, so I need my internet to be reliable. Thank you.

Retired_Member · Answer

16x4 DOCSIS 3.0.&nbsp; it's a fossil.&nbsp;&nbsp;&nbsp;&nbsp;

kchieppo · Answer

I only have a 200 mbps plan, but that's more than enough for my household. At most, we're watching Netflix. It's rare that I need to upload a large file for work. Our area got the speed upgrade, but I don't think we need it.

FURRYe38 · Answer

You have a ton of correctables and uncorrectables.&nbsp;
&nbsp;
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP.&nbsp;Indicates a signal issue on the ISP line up to the modem.
&nbsp;
Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended.&nbsp;What is the brand and model of the host wifi router connected to the modem?
&nbsp;
Have the ISP check the signal and line quality UP to the modem.&nbsp;Be sure the ISP provisions the modem correctly.Be sure there are no coax cable line splitters in the between the modem and ISP service box.&nbsp;Be sure your using good quality RG6 coax cable up to the modem.&nbsp;Start with removing any amplifiers, signal attenuators, or splitters from the coax.From there check the line for kinks, damage, moisture in the line.Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.Be sure to power OFF the modem for 1 minute then back ON.https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-routerhttps://www.duckware.com/tech/solving-intermittent-cable-modem-issues.htmlhttps://highspeed.tips/docsis-events/

kchieppo · Answer

Thank you very much for your response.XFinity customer service was extremely unhelpful - just recommending their modem lol. Need to get a tech out here again.I'm using CAT5E to connect my modem to router. I'll find/buy a CAT6. I'm using a Deco X20 - a modern WiFi 6 router.XFinity checked the signal quality up to the modem in the past, but they said it was fine. If I have them come out again, I'll ask if they could check it again. I'm not using any splitters. Both the cable that connects to my modem and the cable running outside appear to be RG6. The line looks like it's in good shape and any connections I can access are secure. Sometimes powering the modem off, waiting, then powering on will fix any issues, but often it doesn't.I checked out the links you sent. According to that, the correctables/uncorrectables are due to noise. So it seems like the issue has to do with my line or the ISP. Given that the ISP has been out here before and said their signal is fine, I'm suspecting something's bad in the line.Your response was extremely helpful. Thank you again.

FURRYe38 · Answer

Ya, have tech come out on site and take a look. Have them look at the logs from the modem and info I posted about.&nbsp;

Forum Discussion

CM500-100NAS intermittently slow internet

8 Replies

Time	Priority	Description
2024-2-26, 20:18:59	Warning (5)	Dynamic Range Window violation
2024-2-26, 20:18:45	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:28	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:00:21	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-2-26, 19:52:04	Critical (3)	Resetting the cable modem due to docsDevResetNow
2024-1-16, 18:29:59	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-16, 18:29:58	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-16, 18:29:55	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-16, 18:29:54	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-16, 18:29:53	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-16, 18:29:52	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2024-1-16, 18:29:49	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2024-1-16, 18:29:47	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2024-1-16, 18:29:46	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2024-1-16, 18:29:11	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2024-1-16, 18:29:04	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2024-1-16, 18:28:58	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2024-1-16, 18:28:55	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-12-20, 23:35:05	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-12-18, 01:20:26	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-12-11, 08:57:48	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-11-16, 10:48:29	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-11-16, 10:48:17	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-11-11, 16:29:49	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:21	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-25, 10:44:04	Critical (3)	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-10-25, 10:31:04	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-10-25, 09:55:47	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-25, 09:55:33	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
2023-10-25, 00:04:09	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:21	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-10, 17:45:56	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:21	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-10, 14:46:04	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-10, 14:45:58	Critical (3)	No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-10, 14:45:39	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-10, 14:45:38	Critical (3)	No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-10, 14:45:19	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2023-10-10, 14:45:18	Critical (3)	No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:56:25	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f1:aa:64;CMTS-MAC=00:90:f0:5b:04:00;CM-QOS=1.0;CM-VER=3.0;