Skip to main content

  • Home

  • Getting Started

    • Offers

U
user_cd429e
1st Reply
1st Topic
Conversation Starter

Contributor

 • 

44 Messages

Monday, October 25th, 2021 5:43 PM

Closed

Error logs.

All, any help on these modem log errors?

Date Time

Event ID

Event Level

Description

10/25/2021 09:21

82000500

3

“Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;”

10/25/2021 09:15

2436694061

5

“Dynamic Range Window violation”

10/25/2021 09:15

82001200

5

“RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;”

10/25/2021 09:15

2436694061

5

“Dynamic Range Window violation”

10/25/2021 09:15

82001200

5

“RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;”

10/25/2021 09:15

2436694061

5

“Dynamic Range Window violation”

10/25/2021 09:15

82001200

5

“RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;”

10/25/2021 09:15

2436694061

5

“Dynamic Range Window violation”

10/25/2021 09:15

82001200

5

"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[Edited: "Personal Information"];CMTS-

Question

 • 

Updated 

3 years ago

861

5

0

This conversation is no longer open for comments or replies and is no longer visible to community members.

This post was created from this comment on different post
EG

Expert

 • 

104.4K Messages

3 years ago

First. Are you actually experiencing any connectivity problems or are you just focusing on those error log entries ?

0

0

user_cd429e

Contributor

 • 

44 Messages

3 years ago

@EG, I hope this finds you well!

Yes I am experiencing connectivity issues with high latency spikes.  The modem log events of Dynamic Range Window Violation, RNG-RSP CCAP commanded power in excess of 6 dB Below the value corresponding to the top of the draw, and T3 time outs usually occur at the same time as the latency spikes.  I use PingPlotter to monitor the latency.  The high latency is 100% latency (packet loss) lasting several milliseconds for each spike and lasting across as long as 1 minute across the entire graph (see examples below).  The modem events, from what I have read are most likely caused by noise on the lines to my home.  Since my post at the beginning of this thread I have been in contact with the local manager of service (Andre) who is going to have the lines and connections checked.  He is also monitoring connections and event logs in my neighborhood.  

https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html

Here is what I posted at the beginning of this thread.

I posted 6 months ago with the title of "numerous uncorrectables".  At that time and still now there are daily latency issues with my xfinity connection.  The modem files still show numerous uncorrectables and errors.  

Arris SB8200 Modem. 

When latency occurs I run a program called Ping Plotter and can see the very high latency on its graph.  

As you will see in the logs below there are continuous errors indicating a Dynamic Range Window Violation and Power in excess of 6db below something called "top of the draw".  These errors have been continuous as long as I can remember even after Comcast came out and checked my lines and installed a single splitter in my outside box (which did correct the Upstream Bonded Channel db power. 

0

0

EG

Expert

 • 

104.4K Messages

3 years ago

O/k. Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.

2

0

user_cd429e

Contributor

 • 

44 Messages

@EG  

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 507000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
5 Locked QAM256 507000000 Hz -2.4 dBmV 43.7 dB 430 1140
2 Locked QAM256 489000000 Hz -2.8 dBmV 43.5 dB 415 1209
3 Locked QAM256 495000000 Hz -2.5 dBmV 43.6 dB 419 1139
4 Locked QAM256 501000000 Hz -2.4 dBmV 43.7 dB 384 1153
6 Locked QAM256 513000000 Hz -2.2 dBmV 43.7 dB 432 1146
7 Locked QAM256 519000000 Hz -2.2 dBmV 43.6 dB 393 1187
8 Locked QAM256 525000000 Hz -2.3 dBmV 43.6 dB 382 1171
9 Locked QAM256 531000000 Hz -2.2 dBmV 43.6 dB 486 1148
10 Locked QAM256 537000000 Hz -2.2 dBmV 43.7 dB 365 1184
11 Locked QAM256 543000000 Hz -2.3 dBmV 43.5 dB 368 1167
12 Locked QAM256 549000000 Hz -2.3 dBmV 43.3 dB 450 1103
13 Locked QAM256 555000000 Hz -2.4 dBmV 43.4 dB 405 1174
14 Locked QAM256 561000000 Hz -2.4 dBmV 43.3 dB 420 1139
15 Locked QAM256 567000000 Hz -2.3 dBmV 43.3 dB 405 1128
16 Locked QAM256 573000000 Hz -2.4 dBmV 43.3 dB 404 1090
17 Locked QAM256 579000000 Hz -2.5 dBmV 43.1 dB 401 1090
18 Locked QAM256 585000000 Hz -2.4 dBmV 43.1 dB 424 1107
19 Locked QAM256 591000000 Hz -2.5 dBmV 42.9 dB 440 1139
20 Locked QAM256 597000000 Hz -2.4 dBmV 42.9 dB 451 1120
21 Locked QAM256 603000000 Hz -2.3 dBmV 43.0 dB 370 1041
22 Locked QAM256 609000000 Hz -2.5 dBmV 42.9 dB 401 982
23 Locked QAM256 615000000 Hz -2.5 dBmV 42.6 dB 347 1076
24 Locked QAM256 621000000 Hz -2.3 dBmV 42.9 dB 337 1079
25 Locked QAM256 627000000 Hz -2.4 dBmV 42.9 dB 366 1008
26 Locked QAM256 633000000 Hz -2.7 dBmV 42.8 dB 327 1033
27 Locked QAM256 639000000 Hz -2.8 dBmV 42.7 dB 355 1039
28 Locked QAM256 645000000 Hz -2.6 dBmV 42.7 dB 409 956
29 Locked QAM256 651000000 Hz -2.7 dBmV 42.7 dB 333 1066
30 Locked QAM256 657000000 Hz -2.9 dBmV 42.7 dB 319 1005
31 Locked QAM256 663000000 Hz -2.8 dBmV 42.7 dB 333 988
32 Locked QAM256 669000000 Hz -2.7 dBmV 42.6 dB 338 1045
33 Locked Other 690000000 Hz -2.1 dBmV 41.0 dB 3584922045 26



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 48.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 46.0 dBmV
3 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 46.0 dBmV
4 4 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 46.0 dBmV
5 5 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 46.0 dBmV



Current System Time: Mon Oct 25 17:48:45 2021

3 years ago

0

CCDevin

Problem Solver

 • 

735 Messages

@user_cd429e Hi! I see you have been in great hands with @EG! 

As EG recommended, we can look further into the signals on our end and check into the area to be sure we fully diagnose this and resolve these connection issues for you. I'd like to share some steps to message us directly so we can gather your personal account information securely. If you don't mind, please include your first and last name and your complete address so we can get started right away. Thank you! 

Here's the detailed steps to Direct Message us:
• Click "Sign In" if necessary
• Click the "Direct Message" icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message

I no longer work for Comcast. 

3 years ago

EG

Expert

 • 

104.4K Messages

3 years ago

O/k. Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) / an upstream channel-return path impairment 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 can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.

You should get a reply here in your topic. Good luck !

4

0

user_cd429e

Contributor

 • 

44 Messages

@EG  Thank you very much!

3 years ago

0

EG

Expert

 • 

104.4K Messages

My pleasure !

..................................

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer!tick

3 years ago

user_cd429e

Contributor

 • 

44 Messages

Update on my situation.  

1.  The local Comcast Manager of Operations sent a line tech who came on 10/26.  The line tech checked the line from the pole to my modem and found all to be OK.  He also removed the 3 way splitter that Comcast had installed in my outside box a few months ago.

2.  I bought and installed a new router on 10/26 before the line tech arrived (Old router - Linksys 1900AC which was about 7 years old.  New router - ASUS RT-AX86U

Since the 26th I have had no more error events in my modem logs and no latency issues.

The mystery is ... was the splitter causing the issue or could my router have somehow caused error events in the modem?

3 years ago

0

user_cd429e

Contributor

 • 

44 Messages

@EG

Update on my situation.  

1.  The local Comcast Manager of Operations sent a line tech who came on 10/26.  The line tech checked the line from the pole to my modem and found all to be OK.  He also removed the 3 way splitter that Comcast had installed in my outside box a few months ago.

2.  I bought and installed a new router on 10/26 before the line tech arrived (Old router - Linksys 1900AC which was about 7 years old.  New router - ASUS RT-AX86U

Since the 26th I have had no more error events in my modem logs and no latency issues.

The mystery is ... was the splitter causing the issue or could my router have somehow caused error events in the modem?

The uncorrectables are a lot less and the Upstream Bonded Channels Power lowered from 44 to 37 dBmv and the Downstream Bonded Channels power went from a -2.1 to a +5.9 dBmv.  See log below.

Connection
StatusConnection

The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 507000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
5 Locked QAM256 507000000 Hz 5.9 dBmV 43.6 dB 7 0
2 Locked QAM256 489000000 Hz 5.7 dBmV 43.6 dB 10 0
3 Locked QAM256 495000000 Hz 5.9 dBmV 43.4 dB 165 842
4 Locked QAM256 501000000 Hz 5.9 dBmV 43.7 dB 196 1019
6 Locked QAM256 513000000 Hz 5.9 dBmV 43.4 dB 222 978
7 Locked QAM256 519000000 Hz 5.9 dBmV 43.4 dB 7 0
8 Locked QAM256 525000000 Hz 5.7 dBmV 43.5 dB 173 1005
9 Locked QAM256 531000000 Hz 5.8 dBmV 43.4 dB 200 833
10 Locked QAM256 537000000 Hz 5.9 dBmV 43.4 dB 160 891
11 Locked QAM256 543000000 Hz 5.8 dBmV 43.4 dB 199 941
12 Locked QAM256 549000000 Hz 5.8 dBmV 43.4 dB 162 854
13 Locked QAM256 555000000 Hz 5.7 dBmV 43.3 dB 178 855
14 Locked QAM256 561000000 Hz 5.8 dBmV 43.2 dB 141 608
15 Locked QAM256 567000000 Hz 5.7 dBmV 43.2 dB 226 955
16 Locked QAM256 573000000 Hz 5.6 dBmV 43.2 dB 161 596
17 Locked QAM256 579000000 Hz 5.6 dBmV 43.0 dB 235 965
18 Locked QAM256 585000000 Hz 5.6 dBmV 42.9 dB 200 822
19 Locked QAM256 591000000 Hz 5.5 dBmV 42.9 dB 191 892
20 Locked QAM256 597000000 Hz 5.6 dBmV 42.8 dB 197 834
21 Locked QAM256 603000000 Hz 5.7 dBmV 42.9 dB 208 905
22 Locked QAM256 609000000 Hz 5.6 dBmV 42.9 dB 194 922
23 Locked QAM256 615000000 Hz 5.6 dBmV 42.6 dB 212 890
24 Locked QAM256 621000000 Hz 5.7 dBmV 42.9 dB 209 909
25 Locked QAM256 627000000 Hz 5.7 dBmV 42.9 dB 221 884
26 Locked QAM256 633000000 Hz 5.7 dBmV 42.9 dB 203 904
27 Locked QAM256 639000000 Hz 5.7 dBmV 42.8 dB 234 877
28 Locked QAM256 645000000 Hz 5.8 dBmV 42.8 dB 185 856
29 Locked QAM256 651000000 Hz 5.8 dBmV 42.7 dB 219 887
30 Locked QAM256 657000000 Hz 5.6 dBmV 42.8 dB 193 851
31 Locked QAM256 663000000 Hz 5.8 dBmV 42.9 dB 227 891
32 Locked QAM256 669000000 Hz 5.7 dBmV 42.9 dB 211 910
33 Locked Other 690000000 Hz 6.3 dBmV 41.5 dB 2483140529 0



Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 37.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 37.0 dBmV
3 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 37.0 dBmV
4 4 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 37.0 dBmV
5 5 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 37.0 dBmV



Current System Time: Sat Oct 30 05:32:00 2021

3 years ago

0

EG

Expert

 • 

104.4K Messages

3 years ago

Looks good ! A router on the LAN side of a modem can not cause those RF signal errors on the WAN connection to the Comcast system.

2

user_cd429e

Contributor

 • 

44 Messages

@EG 

Thanks again EG.  Still no errors or latency issues but I had an odd thing happen this morning.  My router lost connection to the Internet and would not connect until I restarted the modem (and I restarted the router at the same time).  I understand that this forum is not for ASUS routers but wanted to ask in case you had some insight.  My router system log seems to indicate that Comcast was not giving me an IP address which caused the loss of connectivity.  But I am not sure what happened.  Here are a few lines from the router log.  Oddly there are log lines from May 2021 but this router was bought new and installed on 10/26/2021.  

Nov  1 04:59:45 rc_service: ntp 2119:notify_rc restart_diskmon
Nov  1 04:59:45 disk_monitor: Finish
Nov  1 04:59:45 disk monitor: be idle
Nov  1 04:59:49 crond[1628]: time disparity of 1837734 minutes detected
Nov  1 04:59:51 BWDPI: fun bitmap = 47f
Nov  1 04:59:52 modprobe: module ip6t_REJECT not found in modules.dep
Nov  1 04:59:52 modprobe: module ip6t_ROUTE not found in modules.dep
Nov  1 04:59:52 modprobe: module ip6t_LOG not found in modules.dep
Nov  1 04:59:52 dhcp client: bound 73.23.13.58/255.255.254.0 via 73.23.12.1 for 209981 seconds.
Nov  1 05:00:10 wlceventd: wlceventd_proc_event(527): eth7: Auth D6:1D:01:A5:7A:00, status: Successful (0), rssi:0
Nov  1 05:00:10 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind D6:1D:01:A5:7A:00, status: 0, reason: Unspecified reason (1), rssi:0
Nov  1 05:00:10 wlceventd: wlceventd_proc_event(527): eth7: Auth D6:1D:01:A5:7A:00, status: Successful (0), rssi:0
Nov  1 05:00:10 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind D6:1D:01:A5:7A:00, status: 0, reason: Unspecified reason (1), rssi:0
Nov  1 05:00:10 wlceventd: wlceventd_proc_event(527): eth7: Auth D6:1D:01:A5:7A:00, status: Successful (0), rssi:0
Nov  1 05:00:10 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind D6:1D:01:A5:7A:00, status: 0, reason: Unspecified reason (1), rssi:0
Nov  1 05:00:10 wlceventd: wlceventd_proc_event(527): eth7: Auth D6:1D:01:A5:7A:00, status: Successful (0), rssi:0

3 years ago

0

user_cd429e

Contributor

 • 

44 Messages

@EG 

Checked my logs daily and the below is what I see today.  Anything to be concerned about?

Event Log
Status > Event Log

The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

Date Time Event ID Event Level Description
11/16/2021 00:55 67061600 6

"DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 01:01 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
11/16/2021 01:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 01:00 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 01:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 01:00 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 01:00 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:58 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:58 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:58 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:58 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:58 82000400 3 "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:57 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:56 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:56 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:56 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:55 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:54 74010100 6 "CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:54 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:54 74010100 6 "CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:49 74010100 6 "CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:49 84020300 5 "MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:49 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:49 74010100 6 "CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/16/2021 00:49 74010100 6 "CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/15/2021 00:38 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
11/15/2021 00:38 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"

(edited)

3 years ago

0

forum icon

New to the Community?

Start Here