Frequent Visitor
•
8 Messages
MB8600 - HUGE # OFDM corrected errors and high # of uncorrected errors in log for other channels
Have a Moto MB8600 and consistantly see a huge # of OFDM errors. There is only one cable connector between the ingress and the wall outlet. The connector and wall plate were wired by Xfinity. So, NO SPLITTERS between ingress and wall plate. Uptime = 6 days as of this log:
| ||||||||||||||||||||||||
|
| ||||||||
|
| Downstream Bonded Channels |
|
|
| Channel | Lock Status | Modulation | Channel ID | Freq. (MHz) | Pwr (dBmV) | SNR (dB) | Corrected | Uncorrected |
| 1 | Locked | QAM256 | 30 | 621.0 | 0.8 | 40.3 | 13 | 20 |
| 2 | Locked | QAM256 | 10 | 501.0 | 1.8 | 41.2 | 23 | 23 |
| 3 | Locked | QAM256 | 11 | 507.0 | 1.8 | 41.3 | 198 | 953 |
| 4 | Locked | QAM256 | 12 | 513.0 | 1.7 | 41.2 | 179 | 965 |
| 5 | Locked | QAM256 | 13 | 519.0 | 1.6 | 41.1 | 196 | 946 |
| 6 | Locked | QAM256 | 14 | 525.0 | 1.4 | 41.2 | 197 | 952 |
| 7 | Locked | QAM256 | 15 | 531.0 | 1.2 | 40.9 | 224 | 933 |
| 8 | Locked | QAM256 | 16 | 537.0 | 1.4 | 41.0 | 214 | 940 |
| 9 | Locked | QAM256 | 17 | 543.0 | 1.3 | 40.7 | 207 | 943 |
| 10 | Locked | QAM256 | 18 | 555.0 | 1.0 | 40.6 | 212 | 937 |
| 11 | Locked | QAM256 | 19 | 561.0 | 1.2 | 40.7 | 213 | 931 |
| 12 | Locked | QAM256 | 20 | 567.0 | 1.1 | 40.6 | 218 | 941 |
| 13 | Locked | QAM256 | 21 | 573.0 | 0.9 | 40.5 | 203 | 947 |
| 14 | Locked | QAM256 | 22 | 579.0 | 1.1 | 40.6 | 207 | 943 |
| 15 | Locked | QAM256 | 23 | 585.0 | 0.7 | 40.3 | 216 | 935 |
| 16 | Locked | QAM256 | 24 | 591.0 | 0.9 | 40.5 | 202 | 946 |
| 17 | Locked | OFDM PLC | 25 | 693.0 | 0.8 | 38.8 | -1353202805 | 18 |
| 18 | Locked | QAM256 | 26 | 597.0 | 0.8 | 40.3 | 215 | 994 |
| 19 | Locked | QAM256 | 27 | 603.0 | 0.6 | 40.1 | 191 | 966 |
| 20 | Locked | QAM256 | 28 | 609.0 | 0.5 | 40.3 | 181 | 979 |
| 21 | Locked | QAM256 | 29 | 615.0 | 0.7 | 40.3 | 196 | 962 |
| 22 | Locked | QAM256 | 31 | 627.0 | 0.7 | 40.4 | 215 | 941 |
| 23 | Locked | QAM256 | 32 | 633.0 | 0.9 | 40.5 | 195 | 962 |
| 24 | Locked | QAM256 | 33 | 639.0 | 0.7 | 40.4 | 201 | 965 |
| 25 | Locked | QAM256 | 34 | 645.0 | 0.8 | 40.4 | 238 | 943 |
| 26 | Locked | QAM256 | 35 | 651.0 | 0.6 | 40.1 | 202 | 955 |
| 27 | Locked | QAM256 | 36 | 657.0 | 0.8 | 40.5 | 210 | 1010 |
| 28 | Locked | QAM256 | 37 | 663.0 | 0.6 | 40.6 | 217 | 1004 |
| 29 | Locked | QAM256 | 38 | 669.0 | 0.6 | 40.4 | 218 | 996 |
| 30 | Locked | QAM256 | 39 | 675.0 | 0.5 | 39.8 | 242 | 1011 |
| 31 | Locked | QAM256 | 40 | 681.0 | 0.3 | 40.4 | 220 | 1033 |
| 32 | Locked | QAM256 | 41 | 687.0 | 0.3 | 40.3 | 227 | 1029 |
EG
Expert
•
111.6K Messages
5 years ago
FWIW, there is a known glitch with some makes / models of modem's firmware where the measuring mechanism incorrectly reads the power level, the SNR, and the bit errors for that channel. So it reads many errors when there really aren't.
The bit errors are really pretty low on the QAM256 channels.
Are you actually experiencing any connectivity problems ? The downstream stats are good. Please also post the upstream power level figures.
0
0
EG
Expert
•
111.6K Messages
5 years ago
Upstream power ?
0
0
bdm1955
Frequent Visitor
•
8 Messages
5 years ago
I'd characterize it as choppy. Have the MB8600 attached to a RAX45 with TV using ethernet from RAX45 to TV. Picture freezes or drops xFinity altogether - intermittant problems with both 2.4 & 5Ghz wireless (2 AX devices among N & AC devices). On the laptops/desktops/Samsung S10+ (AX device), Surface Laptop3 (AX device) web pages won't load and then after another try or two, they do render.
MB8600 & RAX45 both rebooted 6 days ago (after power was restored to my home) so both devices should have the latest firmware versions.
0
0
bdm1955
Frequent Visitor
•
8 Messages
5 years ago
Upstream seems OK.
0
0
EG
Expert
•
111.6K Messages
5 years ago
It's good. Are there any error / event log entries ? If so, please post them as well.
0
0
EG
Expert
•
111.6K Messages
5 years ago
Yeah. There is not a "category" only for upstream events. The logging feature logs all general RF errors / events.
The signal stats are o/k but the error log entries indicate that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS to see whether or not everything is in the green zone, see your node / cable plant and modem health, and also see a history plot for the modem. You should get a reply here in your topic. Good luck !
0
0
bdm1955
Frequent Visitor
•
8 Messages
5 years ago
No, the logs don't show any Upstream events/errors - no category for them at all.
0
0
bdm1955
Frequent Visitor
•
8 Messages
5 years ago
I misspoke. The Connection status screen does not. Below is the current Event Log. A number of these are OFDM related. (I removed the "MAC" data from the records):
Log
Time Priority Description
06:14:26
Sat Aug 8 2020 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
06:14:27
Sat Aug 8 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
06:14:51
Sat Aug 8 2020 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
06:14:52
Sat Aug 8 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
06:15:20
Sat Aug 8 2020 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
06:15:21
Sat Aug 8 2020 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
06:19:19
Sat Aug 8 2020 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;
09:23:14
Sat Aug 8 2020 Notice (6) Honoring MDD; IP provisioning mode = IPv6
09:23:01
Sat Aug 8 2020 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;
08:24:42
Tue Aug 11 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
15:19:57
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;
15:20:22
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;
15:22:45
Tue Aug 11 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
15:29:37
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;
15:30:10
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;
19:16:32
Tue Aug 11 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
23:16:41
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;
23:16:42
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;
23:16:43
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;
23:16:49
Tue Aug 11 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;
06:12:08
Wed Aug 12 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
08:19:24
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;
08:19:49
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;
09:36:58
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;
09:37:27
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;
09:37:54
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;
09:38:18
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;
10:28:42
Wed Aug 12 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
23:18:58
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 23; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;
23:18:59
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;
23:19:01
Wed Aug 12 2020 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;
11:07:14
Thu Aug 13 2020 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;
0
0
EG
Expert
•
111.6K Messages
5 years ago
Quite welcome !
0
0
bdm1955
Frequent Visitor
•
8 Messages
5 years ago
Great! Thank you.
0
0
CCAmir
Gold Problem Solver
•
7.2K Messages
5 years ago
Hi bdm1955, I'd be happy to check your signal levels to help pinpoint where this issue could be coming from so that we can get it resolved. To get started could you please send me a private message with your full name and account number by clicking on my name (ComcastAmir) and then click "Send a message"?
0
wiley2
Regular Visitor
•
3 Messages
5 years ago
@bdm1955 I'm having the same issue - any chance you could post an update on what the support rep found?
0
ndiesslin
New Poster
•
1 Message
5 years ago
I'm having this exact same issue as well!
0
0
EG
Expert
•
111.6K Messages
5 years ago
@ndiesslin
Please create a new topic of your own here on this board detailing your issue. Thanks. 4 month old dead now being closed.
0
0