Hello,
I am having intermitted network issue recently and started looking into Motorola modem (MB7621) this morning. When I first checked connection page I notice there are too many large numbers of Corrected and Uncorrected. After restart my modem, uncorrected almost gone except one or two left. Since I restart the modem the internet seems smooth now.
Question:
1) Are data in corrected column look normal?
2) Any potential issue based on the data at this moment?
Thanks,
*+------------------------------------------
Please see the data below:
Connection
| Startup Sequence |
 |
|
|
|
| Startup Step |
Status |
Comment |
|
| Acquire Downstream Channel |
603000000 Hz |
Locked |
|
| Upstream Connection |
OK |
Operational |
|
| Boot State |
OK |
Operational |
|
| Configuration File |
OK |
|
|
| Security |
Enabled |
BPI+ |
|
|
| Connection Status |
|
|
|
|
| System Up Time |
0 days 01h:46m:03s |
|
|
| Network Access |
Allowed |
|
|
|
| Downstream Bonded Channels |
|
|
|
|
| Channel |
Lock Status |
Modulation |
Channel ID |
Freq. (MHz) |
Pwr (dBmV) |
SNR (dB) |
Corrected |
Uncorrected |
| 1 |
Locked |
QAM256 |
33 |
603.0 |
2.7 |
38.1 |
1195185 |
0 |
| 2 |
Locked |
QAM256 |
41 |
651.0 |
1.7 |
37.5 |
3197946 |
1 |
| 3 |
Locked |
QAM256 |
42 |
657.0 |
1.9 |
37.8 |
2031231 |
0 |
| 4 |
Locked |
QAM256 |
43 |
663.0 |
1.5 |
37.4 |
3750595 |
1 |
| 5 |
Locked |
QAM256 |
44 |
669.0 |
1.7 |
37.3 |
3417531 |
1 |
| 6 |
Locked |
QAM256 |
25 |
555.0 |
2.2 |
37.8 |
1571680 |
0 |
| 7 |
Locked |
QAM256 |
26 |
561.0 |
2.5 |
38.1 |
1602157 |
0 |
| 8 |
Locked |
QAM256 |
27 |
567.0 |
3.0 |
38.0 |
1789496 |
0 |
| 9 |
Locked |
QAM256 |
28 |
573.0 |
4.2 |
38.8 |
660767 |
0 |
| 10 |
Locked |
QAM256 |
29 |
579.0 |
3.6 |
38.5 |
675380 |
0 |
| 11 |
Locked |
QAM256 |
30 |
585.0 |
3.4 |
38.6 |
443468 |
0 |
| 12 |
Locked |
QAM256 |
31 |
591.0 |
2.3 |
37.9 |
843585 |
0 |
| 13 |
Locked |
QAM256 |
32 |
597.0 |
3.0 |
38.4 |
569669 |
0 |
| 14 |
Locked |
QAM256 |
34 |
609.0 |
3.1 |
38.2 |
1377057 |
0 |
| 15 |
Locked |
QAM256 |
35 |
615.0 |
2.0 |
37.5 |
1570124 |
0 |
| 16 |
Locked |
QAM256 |
36 |
621.0 |
1.8 |
37.3 |
1018797 |
0 |
| 17 |
Locked |
QAM256 |
37 |
627.0 |
3.1 |
39.4 |
1484438 |
0 |
| 18 |
Locked |
QAM256 |
38 |
633.0 |
3.1 |
38.9 |
1522218 |
0 |
| 19 |
Locked |
QAM256 |
39 |
639.0 |
2.4 |
39.0 |
2730120 |
0 |
| 20 |
Locked |
QAM256 |
40 |
645.0 |
2.0 |
38.8 |
3635865 |
0 |
| 21 |
Locked |
QAM256 |
21 |
531.0 |
1.3 |
38.1 |
1750438 |
0 |
| 22 |
Locked |
QAM256 |
22 |
537.0 |
0.7 |
37.9 |
2631474 |
0 |
| 23 |
Locked |
QAM256 |
23 |
543.0 |
2.4 |
38.9 |
858059 |
0 |
| 24 |
Locked |
QAM256 |
24 |
549.0 |
3.0 |
39.5 |
914817 |
0 |
| Total |
|
|
|
|
|
|
41242097 |
3 |
|
| Upstream Bonded Channels |
|
|
|
|
| Channel |
Lock Status |
Channel Type |
Channel ID |
Symb. Rate (Ksym/sec) |
Freq. (MHz) |
Pwr (dBmV) |
| 1 |
Locked |
ATDMA |
3 |
5120 |
22.8 |
36.0 |
| 2 |
Locked |
ATDMA |
1 |
5120 |
35.6 |
37.4 |
| 3 |
Locked |
ATDMA |
2 |
5120 |
29.2 |
35.9 |
| 4 |
Locked |
ATDMA |
4 |
5120 |
16.4 |
35.8 |
| 5 |
Locked |
ATDMA |
5 |
1280 |
39.6 |
37.9 |
| 6 |
Not Locked |
Unknown |
0 |
0 |
0 |
0.0 |
| 7 |
Not Locked |
Unknown |
0 |
0 |
0 |
0.0 |
| 8 |
Not Locked |
Unknown |
0 |
0 |
0 |
0.0 |
|
user_1z36lc
5 Messages
2 years ago
After running for couple of hours it turns out to be worse:
Advice please!!
0
0
user_1z36lc
5 Messages
2 years ago
Here are the log information from modem:
Event Log
Log
Time
Priority
Description
Mon Dec 04 03:00:00 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:07 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:11 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:11 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:48 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:48 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:51 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:51 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:00:54 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:01:00 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:01:07 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:01:11 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:01:11 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:28:58 2023
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:29:52 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:30:37 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:30:51 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:31:08 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:31:41 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:31:59 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:32:46 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:32:59 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:46:29 2023
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.0;CM-VER=3.0;
Mon Dec 04 03:48:43 2023
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:49:07 2023
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 03:49:44 2023
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 04:29:44 2023
Critical (3)
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 04:32:07 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 04:33:27 2023
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.1;CM-VER=3.0;
Mon Dec 04 10:26:50 2023
Critical (3)
Resetting the cable modem due to docsDevResetNow
Time Not Established
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=x.y.x;CMTS-MAC=d.e.f;CM-QOS=1.0;CM-VER=3.0;
Time Not Established
Notice (6)
Honoring MDD; IP provisioning mode = IPv6
0
0
EG
Expert
•
111K Messages
2 years ago
The downstream channel SNR values are lower to out of spec in your second post. It appears that there is spurious noise leaking into line(s) somewhere. Here's some stuff that you can try but you may need to get a tech out to investigate this;
In an effort to try to obtain better connectivity, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
(edited)
4
0
EG
Expert
•
111K Messages
2 years ago
Okay so as an FYI. If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated.
Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it up to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.
Good luck !
0
0