Time
|
Priority
|
Description
|
Sun May 17 10:30:55 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 8; Chan ID: 1 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:30:54 2020
|
Critical (3)
|
No Ranging Response received - T3 time-out;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:30:52 2020
|
Critical (3)
|
16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:30:52 2020
|
Critical (3)
|
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:30:52 2020
|
Critical (3)
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:25:57 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 8; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:25:44 2020
|
Critical (3)
|
16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:25:44 2020
|
Critical (3)
|
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:25:44 2020
|
Critical (3)
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:24:59 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 4; Chan ID: 36; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:24:55 2020
|
Critical (3)
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:24:41 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:24:41 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 5; Chan ID: 15 16 17 18 19 21 22 23 27 31 33 36; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:24:37 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 23; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:24:37 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:24:32 2020
|
Critical (3)
|
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:23:47 2020
|
Critical (3)
|
No Ranging Response received - T3 time-out;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:23:35 2020
|
Critical (3)
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:22:29 2020
|
Warning (5)
|
MDD message timeout;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:22:29 2020
|
Critical (3)
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:22:23 2020
|
Warning (5)
|
MDD message timeout;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:22:23 2020
|
Critical (3)
|
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:15:35 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:14:19 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:06:10 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:05:26 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:04:16 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:03:51 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:01:05 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 10:00:17 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:59:16 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:58:16 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:54:49 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:54:19 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:47:20 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:46:46 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:42:03 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:40:24 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 22; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:40:14 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 20; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
Sun May 17 09:38:33 2020
|
Notice (6)
|
CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-[MAC removed};CMTS-MAC=[MAC removed];CM-QOS=1.1;CM-VER=3.1;
|
EG
Expert
•
103.5K Messages
4 years ago
The upstream power is in spec. Please also post the rest of the downstream channel stats.
0
0
EG
Expert
•
103.5K Messages
4 years ago
You need to post the signal status numbers as well.
Please post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
0
0
mmamm
Frequent Visitor
•
5 Messages
4 years ago
Would this work? Thanks.
Status
Profile ID
ID
MER
Number Range
Codewords
Codewords
Codewords
0
0
mmamm
Frequent Visitor
•
5 Messages
4 years ago
Signal status: GOOD
0
0
mmamm
Frequent Visitor
•
5 Messages
4 years ago
0
0
EG
Expert
•
103.5K Messages
4 years ago
All of the signal stats are good 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
CCChe
Official Employee
•
6.9K Messages
4 years ago
Hi @mmamm,
Thank you for posting to the Xfinity Forum. We appreciate you for posting your signals so we could help isolate the cause of your connectivity issues. I agree with @EG. I'd like to check the CMTS, node health, and historical plots so I can help find a resolution. Can you please send me a private message? To send a private message, click on "ComcastChe" and then click send a message.
0
mmamm
Frequent Visitor
•
5 Messages
4 years ago
Hi, still awaiting for your input on this issue.
0
0
EG
Expert
•
103.5K Messages
4 years ago
I'm re-escalating this.
1
0
XfinityJoeTru
Official Employee
•
7K Messages
4 years ago
Hi mmamm. Apologies for our delay in getting back with your. I found your message with ComcastChe and I checked your account and responded back to you. Thanks for hanging in there with us!
2
EG
Expert
•
103.5K Messages
3 years ago
Year old dead thread now being closed.
0
0