3 Messages
Issues With Speed and Packet Loss
Let me preface this by saying that an Xfinity tech came out to my address, checked my equipment, and verified it was fine. He identified an issue with signal from the circuit, replaced the coaxial connectors, and it was fine. For a week.
I've been having speed issues for the last month, on and off. Instead of gigabit speeds, it will frequently drop to 50 mb/s or less (with a bare minimum of 5% packet loss).
The Xfinity automated troubleshooter finds no issue with my service because my modem is connected, and tells me to kick rocks. If I schedule a callback, the Helpdesk Agent runs through the generic troubleshooting steps, finds no issue, and tells me to kick rocks and talk to my modem manufacturer. The last one I spoke to actually told me to reset my mobile phone to resolve the issue, and then hung up on me when I told them that was ridiculous and I would not be doing that (if you can believe it).
I've factory reset my MB8600 and re-set it up, which made no difference. The same with my Asus RT-AX68U.
After running a tracert and noticing drops and latency outside my home network, I decided to check my Modem's log and connection status. I'm seeing a large amount of MDD Message timeout warnings which line up with the packet loss I see, and a massive number of uncorrected code words on all Downstream channels. I've attached the logs and the connection info below.
To my eye, it looks like an issue upstream on the circuit, but I wanted other eyes on it and maybe to speak to someone at Xfinity that isn't reading a script and refusing to deviate from it. Any help would be appreciated.
22:19:45 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:19:53 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;-QOS=1.1;CM-VER= | |||
22:20:00 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:01 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:05 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:18 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:21 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:23 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 27 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:39 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:20:59 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:10 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:14 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:17 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:30 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:30 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:41 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:45 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:48 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:49 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:49 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:51 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER= | |||
22:21:51 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:21:59 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:22:05 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:22:19 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:22:23 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:22:28 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:01 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:06 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:11 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:33 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:33 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:23:45 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:01 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:03 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:16 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:22 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:24:28 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:00 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:03 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:10 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:22 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:29 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:32 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:38 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:45 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:46 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:25:57 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 27 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:14 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:16 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:24 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:26 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:30 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:31 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:31 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 30 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:34 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:35 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:41 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:42 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:43 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 28 29 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:52 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:26:55 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 8 9 11 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:27:02 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER= | |||
22:27:04 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:27:07 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:27:08 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:27:08 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 31 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:27:40 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:27:52 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:27:56 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:28:02 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:28:14 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:28:37 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:28:56 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:29:04 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:29:06 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:29:19 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:29:32 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:29:49 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:29:52 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:29:55 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:04 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:21 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:28 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:31 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:46 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:46 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:50 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:30:54 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:08 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:13 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:22 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:24 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:25 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:32 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:36 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:39 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:39 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:46 Mon Nov 27 2023 |
Notice (6) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 27 28 29 30; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1; | |||
22:31:52 Mon Nov 27 2023 |
Warning (5) | MDD message timeout;CM-QOS=1.1;CM-VER=3.1; |
|
|
||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||
|
No Responses!