Forum Discussion
How to get stats from a VM hub (no need to logon to the hub)
Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode
- Click on the “> Check router status” button
- Click on the “Downstream” tab, copy the text and paste into your reply, do not take a screen shot
- Click on the “Upstream” tab, copy the text and paste into your reply
- Click on the “Networking” tab, copy the text and paste into your reply.
- Do NOT post photos or screen shots they will be rejected as they contain MAC addresses. The board software will automatically change MAC addresses to **:** if done as above.
- Raffo8 months agoTuning inChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 418000000 6.8 39 QAM 256 8 2 362000000 7.4 39 QAM 256 1 3 370000000 7.3 39 QAM 256 2 4 378000000 7.3 39 QAM 256 3 5 386000000 7.2 39 QAM 256 4 6 394000000 7.1 39 QAM 256 5 7 402000000 7 39 QAM 256 6 8 410000000 6.9 39 QAM 256 7 9 426000000 6.6 39 QAM 256 9 10 434000000 6.2 39 QAM 256 10 11 442000000 5.9 39 QAM 256 11 12 450000000 5.9 39 QAM 256 12 13 458000000 5.7 39 QAM 256 13 14 466000000 5.5 39 QAM 256 14 15 474000000 5.4 39 QAM 256 15 16 482000000 5.2 39 QAM 256 16 17 490000000 5 39 QAM 256 17 18 498000000 4.7 39 QAM 256 18 19 506000000 4.6 39 QAM 256 19 20 514000000 4.6 39 QAM 256 20 21 522000000 4.4 39 QAM 256 21 22 530000000 4.2 39 QAM 256 22 23 538000000 4.1 39 QAM 256 23 24 546000000 4.2 39 QAM 256 24 25 554000000 4.2 39 QAM 256 25 26 562000000 3.9 39 QAM 256 26 27 570000000 3.7 38 QAM 256 27 28 578000000 3.4 38 QAM 256 28 29 586000000 3.4 38 QAM 256 29 30 594000000 3.4 39 QAM 256 30 31 602000000 3.4 39 QAM 256 31 3.0 Downstream channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors1 Locked 39 56 19 2 Locked 39 68 14 3 Locked 39 70 0 4 Locked 39 78 0 5 Locked 39 85 1 6 Locked 39 61 13 7 Locked 39 70 19 8 Locked 39 61 19 9 Locked 39 70 13 10 Locked 39 79 0 11 Locked 39 66 0 12 Locked 39 88 0 13 Locked 39 81 4 14 Locked 39 96 14 15 Locked 39 113 9 16 Locked 39 125 10 17 Locked 39 121 0 18 Locked 39 137 0 19 Locked 39 137 0 20 Locked 39 139 0 21 Locked 39 143 1 22 Locked 39 148 1 23 Locked 39 176 2 24 Locked 39 158 0 25 Locked 39 164 1 26 Locked 39 202 2 27 Locked 38 192 3 28 Locked 38 218 14 29 Locked 38 279 19 30 Locked 39 244 15 31 Locked 39 258 16 3.1 Downstream channels
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)37 94 4K 1840 QAM 4096 1108 3.1 Downstream channels
Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)37 Locked 38 0.0 2817568414 2215 - Raffo8 months agoTuning inChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 49600000 41.5 5120 QAM 64 1 1 43100000 41.5 5120 QAM 64 2 2 36600000 41 5120 QAM 64 3 3 30100000 40.5 5120 QAM 64 4 4 23600000 40.8 5120 QAM 64 9 3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts0 ATDMA 0 0 0 0 1 ATDMA 0 0 0 0 2 ATDMA 0 0 1 0 3 ATDMA 0 0 0 0 4 ATDMA 0 0 0 0 3.1 Upstream channels
Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation10 10.4 37.0 2K QAM 256 3.1 Upstream channels
Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts10 OFDMA 208 74000000 0 0 - Akua_A8 months agoForum Team
Raffo Please let us know how the appointment goes and if you need any further help.
- Raffo8 months agoTuning in
Engineer visited, changed a cable and some connectors inside and outside the house. But no change, the speed is all over the place so he has said he will report back for the cabinet that I am connected at to be looked at by a different team. He was a top guy though and tried all he could, but he didn’t understand what was happening either
- Raffo8 months agoTuning inTime Priority Description
07-06-2024 18:27:03 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 14:53:46 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 14:51:55 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 11:29:08 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 11:26:45 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 10:44:20 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 10:36:23 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 09:49:43 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 07-06-2024 09:47:25 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 12:12:57 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 12:11:21 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 12:07:12 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 12:00:51 notice CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 11:57:43 notice CM-STATUS message sent. Event Type Code: 20; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 11:57:35 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 11:28:25 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 06-06-2024 11:26:14 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 05-06-2024 16:09:55 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 05-06-2024 16:08:29 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 05-06-2024 16:06:43 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 05-06-2024 16:05:54 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 04-06-2024 21:57:29 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 04-06-2024 19:05:36 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 04-06-2024 07:04:44 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 04-06-2024 07:03:10 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-06-2024 23:03:40 notice GUI Login Status - Login Success from LAN interface 03-06-2024 15:23:59 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-06-2024 15:20:17 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-06-2024 13:00:58 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-06-2024 12:58:42 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-06-2024 10:03:56 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-06-2024 10:01:35 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 02-06-2024 20:53:16 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; - Tudor8 months agoVery Insightful Person
Too many errors, but the figures are accumulative since the hub was last power cycled. So please turn off your hub for a short period, this will reset the counters, then post a new full set of stats after about two hours. This will indicate the current line status.
- Raffo8 months agoTuning in
Will do. Thank you
- Raffo8 months agoTuning in
I accidentally marked this as the solution and can’t undo it. I posted my stats like you asked could you take a look please? It looks like too many errors for a 2 hour time period to me but I am not an expert in these things
Related Content
- 9 months ago
- 16 days ago