U

Contributor

 • 

44 Messages

Friday, March 26th, 2021 8:27 PM

Closed

Numerous Uncorrectables

I have been seeing a ton of uncorrectables and have had a lot of intermittent latency.  Modem is an SB8200.  Xfinity checked my lines today and area nodes and found all to be good. The did find a loose 75 ohm terminator on my splitter and they removed my splitter and just used an inline connector instead.  Note that I have only internet and not cable or phone.

See my modem logs below.  What can be done about the uncorrectables?

Connection

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 4.3 dBmV 43.0 dB 2909 4218
2 Locked QAM256 489000000 Hz 4.0 dBmV 43.0 dB 2722 6067
3 Locked QAM256 495000000 Hz 4.2 dBmV 43.0 dB 3804 8867
4 Locked QAM256 501000000 Hz 4.3 dBmV 43.0 dB 3780 8261
6 Locked QAM256 513000000 Hz 4.3 dBmV 42.9 dB 2551 6374
7 Locked QAM256 519000000 Hz 4.3 dBmV 42.8 dB 3095 8214
8 Locked QAM256 525000000 Hz 4.2 dBmV 42.8 dB 2777 6868
9 Locked QAM256 531000000 Hz 4.2 dBmV 42.8 dB 4556 8132
10 Locked QAM256 537000000 Hz 4.3 dBmV 42.8 dB 2795 6626
11 Locked QAM256 543000000 Hz 4.2 dBmV 42.9 dB 2880 7479
12 Locked QAM256 549000000 Hz 4.2 dBmV 42.9 dB 3078 8080
13 Locked QAM256 555000000 Hz 4.2 dBmV 42.7 dB 3000 7563
14 Locked QAM256 561000000 Hz 4.2 dBmV 42.5 dB 3025 8410
15 Locked QAM256 567000000 Hz 4.1 dBmV 42.5 dB 3453 8516
16 Locked QAM256 573000000 Hz 3.9 dBmV 42.4 dB 2980 8123
17 Locked QAM256 579000000 Hz 3.9 dBmV 42.2 dB 4398 11374
18 Locked QAM256 585000000 Hz 3.9 dBmV 42.5 dB 3340 8608
19 Locked QAM256 591000000 Hz 3.7 dBmV 42.2 dB 3005 8229
20 Locked QAM256 597000000 Hz 3.7 dBmV 42.2 dB 2927 8666
21 Locked QAM256 603000000 Hz 3.8 dBmV 42.3 dB 3343 8431
22 Locked QAM256 609000000 Hz 3.5 dBmV 42.1 dB 4381 8403
23 Locked QAM256 615000000 Hz 3.4 dBmV 42.0 dB 3837 7748
24 Locked QAM256 621000000 Hz 3.5 dBmV 42.1 dB 3739 7895
25 Locked QAM256 627000000 Hz 3.4 dBmV 42.1 dB 3719 7768
26 Locked QAM256 633000000 Hz 3.4 dBmV 41.9 dB 3537 7568
27 Locked QAM256 639000000 Hz 3.3 dBmV 42.0 dB 3558 7714
28 Locked QAM256 645000000 Hz 3.3 dBmV 41.9 dB 3713 7673
29 Locked QAM256 651000000 Hz 3.3 dBmV 42.0 dB 4044 10326
30 Locked QAM256 657000000 Hz 3.1 dBmV 41.9 dB 4146 8279
31 Locked QAM256 663000000 Hz 3.2 dBmV 41.9 dB 4182 8292
32 Locked QAM256 669000000 Hz 3.1 dBmV 42.0 dB 4246 7723
33 Locked Other 690000000 Hz 3.5 dBmV 40.5 dB 825534217 909



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: Fri Mar 26 12:05:32 2021

Expert

 • 

110K Messages

4 years ago

It's really not that many, but it depends on the total uptime of the modem since it was last re-booted. The signal stats are good.

Are you actually experiencing any connectivity issues, or are you just focusing on those bit errors ?

Contributor

 • 

44 Messages

4 years ago

EG,

Aren't any uncorrectables a problem?  I have been researching and it seems they are.  In answer to you question, I have latency issues which is why I started looking at the modem logs.

Uptimewise, I hard reset this modem a couple of days ago in a effort to eliminate the latency issues so these uncorrectables are all recent.  

https://arris.secure.force.com/consumers/articles/General_FAQs/SB8200-Cable-Signal-Levels/?l=en_US&fs=RelatedArticle

https://www.dslreports.com/forum/r30372719-Signals-What-a-difference-a-new-drop-line-can-make

Contributor

 • 

44 Messages

4 years ago

Arris just told me that the upstream power is too low and that there should be 8 channels instead of 5.  Upstream power should be It should be minumum 45 dBmv and max 61 but is is 37.

https://arris.secure.force.com/consumers/articles/General_FAQs/SB8200-Cable-Signal-Levels/?l=en_US&fs=RelatedArticle

Any additional help or insight would be appreciated.

Expert

 • 

110K Messages

4 years ago

@user_cd429e 

You wrote: "Aren't any uncorrectables a problem?"

Not if they are a small amount over an appreciable period of time.

Just to clear things up about Arris's assertions;

Arris is wrong ! They have been passing the buck and have been conning people with that statement lately !!  They are probably trying to cover up for their liabilities about the lawsuits against them because of their use of the horrible Puma 6 chipsets... Only the Comcast plant / engineering specs matter;

Specification Min Max
Downstream Power Level 
Cable Modems -10dBmV +10dBmV
Gateways and EMTAs -7dBmV +7dBmV
Downstream Signal to Noise Ratio 35dB -
Upstream Power Level +35dBmV +50dBmV
Upstream Signal to Noise Ratio 31dB -
Upstream Receive Power -2dBmV 
+2dBmV

They are also wrong about the number of upstream channels as Comcast currently offers only up to five channels no matter what the modem is capable of.

Moving on. You stated that you are having a problem with "intermittent latency". That could be being caused by an RF signal impairment / line impairment of some type, or by an intermittent capacity / traffic congestion problem on your local cable segment / local node. If it is the latter, there is not much that you can do about it other than to complain to them persistently about it.

That said. I'll ask for more info which can help to reveal signal problems. Are there any RF error log enties being shown in the 8200 cable modem ? If so, please post them in their entirety.

Is there a router / WiFi connection in the mix here ?

(edited)

Contributor

 • 

44 Messages

4 years ago

Hello EG,

This is an SB8200 which does not appear to use the PUMA chipset.  https://www.mbreviews.com/arris-sb8200-review/

I do have a WRT1900AC Linksys router with 4 hardwired connections and wifi. The hardwired connections distribute to SB3005 switches and then to devices on the hard wired network.  WiFi is used for mobile devices.  

All testing is done on a PC that is on the LAN - RJ45 connection.  I have monitored the Internet bandwidth usage via my router login and see nothing pulling high BW.  For instance my main PC, where I do this testing, typically is using between .02Mbps and .08Mbps total BW.  

When seeing latency issues I use Ping Plotter program to monitor the latency.  

Here is the log from this morning.  I see no entry updates since the service call yesterday when the line technicians disconnected my line for testing.

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
03/26/2021 11:00 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;"
03/26/2021 11:00 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;"
03/26/2021 11:00 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;"
03/26/2021 11:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:59 84020300 5 "MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:59 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:57 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;"
03/26/2021 10:57 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;"
03/26/2021 10:57 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;"
03/26/2021 10:57 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:56 84020300 5 "MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:56 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:54 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;"
03/26/2021 10:53 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;"
03/26/2021 10:48 2436694061 5 "Dynamic Range Window violation"
03/26/2021 10:48 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;"
03/26/2021 10:48 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;"
03/26/2021 10:46 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:46 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;"
03/26/2021 10:46 68001102 3 "Config File Rejected due to Invalid or Unexpected TLV 11 encoding;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:46 73040200 3 "TLV-11 - Illegal Set operation failed;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:46 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
03/26/2021 10:46 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;"
03/26/2021 10:45 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=0[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:42 84020300 5 "MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:42 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:42 84020300 5 "MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:42 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/26/2021 10:42 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;"
03/26/2021 10:41 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;"
03/26/2021 10:41 2436694061 5 "Dynamic Range Window violation"
03/26/2021 10:41 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;"
03/26/2021 10:30 2436694061 5 "Dynamic Range Window violation"
03/26/2021 10:30 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds 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;"
03/26/2021 10:27 2436694061 5 "Dynamic Range Window violation"
03/26/2021 10:27 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;"
03/26/2021 10:27 2436694061 5 "Dynamic Range Window violation"
03/26/2021 10:27 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;"
03/26/2021 10:27 2436694061 5 "Dynamic Range Window violation"
03/26/2021 10:27 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;"
03/26/2021 10:00 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;"
03/26/2021 01:31 2436694061 5 "Dynamic Range Window violation"
03/26/2021 01:31 82001100 5 "RNG-RSP CCAP Commanded Power Exceeds 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;"
03/26/2021 01:29 2436694061 5 "Dynamic Range Window violation"
03/26/2021 01:29 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;"
03/26/2021 01:29 2436694061 5 "Dynamic Range Window violation"
03/26/2021 01:29 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;"
03/26/2021 01:29 2436694061 5 "Dynamic Range Window violation"
03/26/2021 01:29 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;"
03/25/2021 20:38 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;"

  

(edited)

Contributor

 • 

44 Messages

4 years ago

What I have in mind from here is:

Xfinity has escalated and a higher level technician will be calling me next week.  

I will once again hard reset my modem, mainly to clear the logs and current results.  

I will connect a laptop directly to modem's RJ45 (not through my router network) and check the modem logs.  

I have ordered a high quality splitter and 75 ohm termination cap and may install these to see if my upstream power levels increase,

Expert

 • 

110K Messages

4 years ago

@user_cd429e 

It doesn't seem that you understand. It doesn't matter whether or not your particular modem uses it (the Puma 6). They are saying that as a a boilerplate response to help them to get away with murder (so to speak) legally. It's being used as a universal excuse so that they don't have to address their problem. They are passing the blame for their deficiencies on to the ISP's instead. You don't need to raise the upstream power. There is nothing wrong with it. The Comcast system automatically controls it to a level that it needs to clearly hear the modem at their headend. I hope that that was clearer for you. 

That said.

The signal stats are o/k (as stated), but the error log entries indicate 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 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 !

(edited)

Contributor

 • 

44 Messages

4 years ago

EG, I just factory reset my modem to get a better picture of things as they stand now.  Interestingly I now have no uncorrectables.  I will check it again later and each day.  Any thoughts on this change and on how current the modem logs are when they are viewed?  All that Xfinity did was verify the nodes near me and test my line which they said was good.  Otherwise they removed the splitter which had a very loose terminator on the unused output.

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 651000000 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
29 Locked QAM256 651000000 Hz 4.2 dBmV 42.3 dB 0 0
2 Locked QAM256 489000000 Hz 4.6 dBmV 43.3 dB 0 0
3 Locked QAM256 495000000 Hz 4.8 dBmV 43.4 dB 0 0
4 Locked QAM256 501000000 Hz 4.8 dBmV 43.4 dB 0 0
5 Locked QAM256 507000000 Hz 4.8 dBmV 43.4 dB 0 0
6 Locked QAM256 513000000 Hz 4.8 dBmV 43.3 dB 0 0
7 Locked QAM256 519000000 Hz 4.8 dBmV 43.3 dB 0 0
8 Locked QAM256 525000000 Hz 4.6 dBmV 43.1 dB 1 0
9 Locked QAM256 531000000 Hz 4.7 dBmV 43.2 dB 0 0
10 Locked QAM256 537000000 Hz 4.7 dBmV 43.2 dB 0 0
11 Locked QAM256 543000000 Hz 4.6 dBmV 43.0 dB 0 0
12 Locked QAM256 549000000 Hz 4.6 dBmV 43.0 dB 0 0
13 Locked QAM256 555000000 Hz 4.5 dBmV 42.9 dB 0 0
14 Locked QAM256 561000000 Hz 4.5 dBmV 42.8 dB 0 0
15 Locked QAM256 567000000 Hz 4.4 dBmV 42.8 dB 0 0
16 Locked QAM256 573000000 Hz 4.2 dBmV 42.6 dB 2 0
17 Locked QAM256 579000000 Hz 4.1 dBmV 42.6 dB 0 0
18 Locked QAM256 585000000 Hz 4.1 dBmV 42.6 dB 0 0
19 Locked QAM256 591000000 Hz 3.9 dBmV 42.4 dB 0 0
20 Locked QAM256 597000000 Hz 4.0 dBmV 42.3 dB 0 0
21 Locked QAM256 603000000 Hz 4.0 dBmV 42.4 dB 1 0
22 Locked QAM256 609000000 Hz 3.8 dBmV 42.4 dB 2 0
23 Locked QAM256 615000000 Hz 3.8 dBmV 42.1 dB 2 0
24 Locked QAM256 621000000 Hz 3.9 dBmV 42.3 dB 1 0
25 Locked QAM256 627000000 Hz 4.0 dBmV 42.2 dB 0 0
26 Locked QAM256 633000000 Hz 4.0 dBmV 42.3 dB 0 0
27 Locked QAM256 639000000 Hz 4.1 dBmV 42.2 dB 1 0
28 Locked QAM256 645000000 Hz 4.2 dBmV 42.3 dB 0 0
30 Locked QAM256 657000000 Hz 4.0 dBmV 42.3 dB 0 0
31 Locked QAM256 663000000 Hz 4.2 dBmV 42.3 dB 3 0
32 Locked QAM256 669000000 Hz 4.1 dBmV 42.3 dB 0 0
33 Locked Other 690000000 Hz 4.6 dBmV 41.0 dB 68846709 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 Mar 27 13:16:03 2021

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
03/27/2021 13:03 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;"
03/27/2021 13:03 68001102 3 "Config File Rejected due to Invalid or Unexpected TLV 11 encoding;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
03/27/2021 13:03 73040200 3 "TLV-11 - Illegal Set operation failed;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
01/01/1970 00:02 84020200 5 "Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84020200 5 "Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:01 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

(edited)

Expert

 • 

110K Messages

4 years ago

The bit error counter and the error log entries get reset to zero every time the device gets reset or re-booted. That stuff is cumulative and starts re-counting and re-recording from that point on until the next reset.

(edited)

Contributor

 • 

44 Messages

4 years ago

Ok so a modem restart would clear the buffers?

Expert

 • 

110K Messages

4 years ago

Yup

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Contributor

 • 

44 Messages

4 years ago

Update, I installed a splitter today (Extreme 2 Way HD Digital 1Ghz High Performance Coax Cable Splitter BDS102H).  I hard reset the modem and then checked the logs.  The results are that the Upstream Bonded Channels Power increased from 37 dBmv to 40 dBmv and that the Downstream Bonded Channel power changed from an average of 4.6 dBmv to and average of 1.7 dBmv.  See below... 

Before adding splitter:

Startup Procedure

Procedure

Status

Comment

Acquire Downstream Channel

651000000 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

29

Locked

QAM256

651000000 Hz

4.7 dBmV

42.4 dB

132

0

2

Locked

QAM256

489000000 Hz

4.9 dBmV

43.2 dB

39

0

3

Locked

QAM256

495000000 Hz

5.0 dBmV

43.4 dB

41

0

4

Locked

QAM256

501000000 Hz

5.0 dBmV

43.4 dB

38

0

5

Locked

QAM256

507000000 Hz

5.0 dBmV

43.4 dB

44

0

6

Locked

QAM256

513000000 Hz

5.0 dBmV

43.2 dB

54

0

7

Locked

QAM256

519000000 Hz

4.9 dBmV

43.3 dB

53

0

8

Locked

QAM256

525000000 Hz

4.7 dBmV

43.1 dB

69

0

9

Locked

QAM256

531000000 Hz

4.7 dBmV

43.2 dB

71

0

10

Locked

QAM256

537000000 Hz

4.8 dBmV

43.1 dB

85

0

11

Locked

QAM256

543000000 Hz

4.6 dBmV

43.0 dB

79

0

12

Locked

QAM256

549000000 Hz

4.7 dBmV

43.1 dB

80

0

13

Locked

QAM256

555000000 Hz

4.6 dBmV

42.9 dB

94

0

14

Locked

QAM256

561000000 Hz

4.6 dBmV

42.9 dB

104

0

15

Locked

QAM256

567000000 Hz

4.6 dBmV

42.9 dB

108

0

16

Locked

QAM256

573000000 Hz

4.5 dBmV

42.8 dB

105

0

17

Locked

QAM256

579000000 Hz

4.5 dBmV

42.7 dB

113

0

18

Locked

QAM256

585000000 Hz

4.5 dBmV

42.7 dB

114

0

19

Locked

QAM256

591000000 Hz

4.4 dBmV

42.6 dB

153

0

20

Locked

QAM256

597000000 Hz

4.6 dBmV

42.6 dB

130

0

21

Locked

QAM256

603000000 Hz

4.6 dBmV

42.6 dB

139

0

22

Locked

QAM256

609000000 Hz

4.4 dBmV

42.4 dB

124

0

23

Locked

QAM256

615000000 Hz

4.4 dBmV

42.4 dB

151

0

24

Locked

QAM256

621000000 Hz

4.6 dBmV

42.6 dB

142

0

25

Locked

QAM256

627000000 Hz

4.5 dBmV

42.4 dB

132

0

26

Locked

QAM256

633000000 Hz

4.6 dBmV

42.6 dB

127

0

27

Locked

QAM256

639000000 Hz

4.6 dBmV

42.6 dB

122

0

28

Locked

QAM256

645000000 Hz

4.7 dBmV

42.4 dB

117

0

30

Locked

QAM256

657000000 Hz

4.5 dBmV

42.4 dB

152

0

31

Locked

QAM256

663000000 Hz

4.6 dBmV

42.6 dB

129

0

32

Locked

QAM256

669000000 Hz

4.5 dBmV

42.5 dB

117

0

33

Locked

Other

690000000 Hz

5.0 dBmV

41.0 dB

3084993835

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

38.0 dBmV

 

_______________________________________________________________________________________________________________________________

After adding splitter:

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 651000000 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
29 Locked QAM256 651000000 Hz 1.2 dBmV 42.2 dB 0 0
2 Locked QAM256 489000000 Hz 1.4 dBmV 42.9 dB 0 0
3 Locked QAM256 495000000 Hz 1.7 dBmV 43.1 dB 0 0
4 Locked QAM256 501000000 Hz 1.7 dBmV 43.2 dB 0 0
5 Locked QAM256 507000000 Hz 1.8 dBmV 43.3 dB 0 0
6 Locked QAM256 513000000 Hz 1.8 dBmV 43.0 dB 0 0
7 Locked QAM256 519000000 Hz 1.8 dBmV 43.0 dB 0 0
8 Locked QAM256 525000000 Hz 1.7 dBmV 42.9 dB 0 0
9 Locked QAM256 531000000 Hz 1.7 dBmV 42.9 dB 0 0
10 Locked QAM256 537000000 Hz 1.8 dBmV 42.9 dB 0 0
11 Locked QAM256 543000000 Hz 1.7 dBmV 42.9 dB 0 0
12 Locked QAM256 549000000 Hz 1.8 dBmV 43.1 dB 0 0
13 Locked QAM256 555000000 Hz 1.7 dBmV 42.8 dB 0 0
14 Locked QAM256 561000000 Hz 1.8 dBmV 42.9 dB 0 0
15 Locked QAM256 567000000 Hz 1.6 dBmV 42.8 dB 0 0
16 Locked QAM256 573000000 Hz 1.6 dBmV 42.7 dB 0 0
17 Locked QAM256 579000000 Hz 1.5 dBmV 42.4 dB 0 0
18 Locked QAM256 585000000 Hz 1.5 dBmV 42.4 dB 0 0
19 Locked QAM256 591000000 Hz 1.3 dBmV 42.4 dB 0 0
20 Locked QAM256 597000000 Hz 1.5 dBmV 42.3 dB 0 0
21 Locked QAM256 603000000 Hz 1.5 dBmV 42.4 dB 0 0
22 Locked QAM256 609000000 Hz 1.2 dBmV 42.5 dB 0 0
23 Locked QAM256 615000000 Hz 1.2 dBmV 42.2 dB 0 0
24 Locked QAM256 621000000 Hz 1.3 dBmV 42.3 dB 0 0
25 Locked QAM256 627000000 Hz 1.3 dBmV 42.4 dB 0 0
26 Locked QAM256 633000000 Hz 1.2 dBmV 42.3 dB 0 0
27 Locked QAM256 639000000 Hz 1.3 dBmV 42.3 dB 0 0
28 Locked QAM256 645000000 Hz 1.0 dBmV 42.3 dB 0 0
30 Locked QAM256 657000000 Hz 1.0 dBmV 42.2 dB 0 0
31 Locked QAM256 663000000 Hz 1.1 dBmV 42.0 dB 0 0
32 Locked QAM256 669000000 Hz 0.8 dBmV 42.2 dB 0 0
33 Locked Other 690000000 Hz 1.3 dBmV 40.8 dB 15479074 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 40.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 40.0 dBmV
3 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 40.0 dBmV
4 4 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 40.0 dBmV
5 5 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 40.0 dBmV



Current System Time: Fri Apr 2 15:43:19 2021

_____________________________________________________________________________________________________________________________

The event logs look similar in both cases...

Before adding splitter:

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.

Top of Form

Date Time

Event ID

Event Level

Description

03/27/2021 13:03

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;"

03/27/2021 13:03

68001102

3

"Config File Rejected due to Invalid or Unexpected TLV 11 encoding;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"

03/27/2021 13:03

73040200

3

"TLV-11 - Illegal Set operation failed;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:02

2436694066

6

"Honoring MDD; IP provisioning mode = IPv6"

01/01/1970 00:02

84020200

5

"Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:02

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:02

84020200

5

"Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:01

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

After adding splitter:

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
04/02/2021 15:40 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;"
04/02/2021 15:40 68001102 3 "Config File Rejected due to Invalid or Unexpected TLV 11 encoding;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:01:5c:a7:96:6f;CM-QOS=1.1;CM-VER=3.1;"
04/02/2021 15:40 73040200 3 "TLV-11 - Illegal Set operation failed;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:01:5c:a7:96:6f;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
01/01/1970 00:02 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:01:5c:a7:96:6f;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84020200 5 "Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84020200 5 "Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

(edited)

Contributor

 • 

44 Messages

4 years ago

Having trouble posting

Contributor

 • 

44 Messages

4 years ago

Update, I installed a splitter today (Extreme 2 Way HD Digital 1Ghz High Performance Coax Cable Splitter BDS102H).  I hard reset the modem and then checked the logs.  The results are that the Upstream Bonded Channels Power increased from 37 dBmv to 40 dBmv and that the Downstream Bonded Channel power changed from an average of 4.6 dBmv to and average of 1.7 dBmv.  See below... 

Before adding splitter:

Startup Procedure

Procedure

Status

Comment

Acquire Downstream Channel

651000000 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

29

Locked

QAM256

651000000 Hz

4.7 dBmV

42.4 dB

132

0

2

Locked

QAM256

489000000 Hz

4.9 dBmV

43.2 dB

39

0

3

Locked

QAM256

495000000 Hz

5.0 dBmV

43.4 dB

41

0

4

Locked

QAM256

501000000 Hz

5.0 dBmV

43.4 dB

38

0

5

Locked

QAM256

507000000 Hz

5.0 dBmV

43.4 dB

44

0

6

Locked

QAM256

513000000 Hz

5.0 dBmV

43.2 dB

54

0

7

Locked

QAM256

519000000 Hz

4.9 dBmV

43.3 dB

53

0

8

Locked

QAM256

525000000 Hz

4.7 dBmV

43.1 dB

69

0

9

Locked

QAM256

531000000 Hz

4.7 dBmV

43.2 dB

71

0

10

Locked

QAM256

537000000 Hz

4.8 dBmV

43.1 dB

85

0

11

Locked

QAM256

543000000 Hz

4.6 dBmV

43.0 dB

79

0

12

Locked

QAM256

549000000 Hz

4.7 dBmV

43.1 dB

80

0

13

Locked

QAM256

555000000 Hz

4.6 dBmV

42.9 dB

94

0

14

Locked

QAM256

561000000 Hz

4.6 dBmV

42.9 dB

104

0

15

Locked

QAM256

567000000 Hz

4.6 dBmV

42.9 dB

108

0

16

Locked

QAM256

573000000 Hz

4.5 dBmV

42.8 dB

105

0

17

Locked

QAM256

579000000 Hz

4.5 dBmV

42.7 dB

113

0

18

Locked

QAM256

585000000 Hz

4.5 dBmV

42.7 dB

114

0

19

Locked

QAM256

591000000 Hz

4.4 dBmV

42.6 dB

153

0

20

Locked

QAM256

597000000 Hz

4.6 dBmV

42.6 dB

130

0

21

Locked

QAM256

603000000 Hz

4.6 dBmV

42.6 dB

139

0

22

Locked

QAM256

609000000 Hz

4.4 dBmV

42.4 dB

124

0

23

Locked

QAM256

615000000 Hz

4.4 dBmV

42.4 dB

151

0

24

Locked

QAM256

621000000 Hz

4.6 dBmV

42.6 dB

142

0

25

Locked

QAM256

627000000 Hz

4.5 dBmV

42.4 dB

132

0

26

Locked

QAM256

633000000 Hz

4.6 dBmV

42.6 dB

127

0

27

Locked

QAM256

639000000 Hz

4.6 dBmV

42.6 dB

122

0

28

Locked

QAM256

645000000 Hz

4.7 dBmV

42.4 dB

117

0

30

Locked

QAM256

657000000 Hz

4.5 dBmV

42.4 dB

152

0

31

Locked

QAM256

663000000 Hz

4.6 dBmV

42.6 dB

129

0

32

Locked

QAM256

669000000 Hz

4.5 dBmV

42.5 dB

117

0

33

Locked

Other

690000000 Hz

5.0 dBmV

41.0 dB

3084993835

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

38.0 dBmV

 

_______________________________________________________________________________________________________________________________

After adding splitter:

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 651000000 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
29 Locked QAM256 651000000 Hz 1.2 dBmV 42.2 dB 0 0
2 Locked QAM256 489000000 Hz 1.4 dBmV 42.9 dB 0 0
3 Locked QAM256 495000000 Hz 1.7 dBmV 43.1 dB 0 0
4 Locked QAM256 501000000 Hz 1.7 dBmV 43.2 dB 0 0
5 Locked QAM256 507000000 Hz 1.8 dBmV 43.3 dB 0 0
6 Locked QAM256 513000000 Hz 1.8 dBmV 43.0 dB 0 0
7 Locked QAM256 519000000 Hz 1.8 dBmV 43.0 dB 0 0
8 Locked QAM256 525000000 Hz 1.7 dBmV 42.9 dB 0 0
9 Locked QAM256 531000000 Hz 1.7 dBmV 42.9 dB 0 0
10 Locked QAM256 537000000 Hz 1.8 dBmV 42.9 dB 0 0
11 Locked QAM256 543000000 Hz 1.7 dBmV 42.9 dB 0 0
12 Locked QAM256 549000000 Hz 1.8 dBmV 43.1 dB 0 0
13 Locked QAM256 555000000 Hz 1.7 dBmV 42.8 dB 0 0
14 Locked QAM256 561000000 Hz 1.8 dBmV 42.9 dB 0 0
15 Locked QAM256 567000000 Hz 1.6 dBmV 42.8 dB 0 0
16 Locked QAM256 573000000 Hz 1.6 dBmV 42.7 dB 0 0
17 Locked QAM256 579000000 Hz 1.5 dBmV 42.4 dB 0 0
18 Locked QAM256 585000000 Hz 1.5 dBmV 42.4 dB 0 0
19 Locked QAM256 591000000 Hz 1.3 dBmV 42.4 dB 0 0
20 Locked QAM256 597000000 Hz 1.5 dBmV 42.3 dB 0 0
21 Locked QAM256 603000000 Hz 1.5 dBmV 42.4 dB 0 0
22 Locked QAM256 609000000 Hz 1.2 dBmV 42.5 dB 0 0
23 Locked QAM256 615000000 Hz 1.2 dBmV 42.2 dB 0 0
24 Locked QAM256 621000000 Hz 1.3 dBmV 42.3 dB 0 0
25 Locked QAM256 627000000 Hz 1.3 dBmV 42.4 dB 0 0
26 Locked QAM256 633000000 Hz 1.2 dBmV 42.3 dB 0 0
27 Locked QAM256 639000000 Hz 1.3 dBmV 42.3 dB 0 0
28 Locked QAM256 645000000 Hz 1.0 dBmV 42.3 dB 0 0
30 Locked QAM256 657000000 Hz 1.0 dBmV 42.2 dB 0 0
31 Locked QAM256 663000000 Hz 1.1 dBmV 42.0 dB 0 0
32 Locked QAM256 669000000 Hz 0.8 dBmV 42.2 dB 0 0
33 Locked Other 690000000 Hz 1.3 dBmV 40.8 dB 15479074 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 40.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 40.0 dBmV
3 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 40.0 dBmV
4 4 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 40.0 dBmV
5 5 Locked SC-QAM Upstream 39600000 Hz 1600000 Hz 40.0 dBmV



Current System Time: Fri Apr 2 15:43:19 2021

_____________________________________________________________________________________________________________________________

The event logs look similar in both cases...

Before adding splitter:

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.

Top of Form

Date Time

Event ID

Event Level

Description

03/27/2021 13:03

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;"

03/27/2021 13:03

68001102

3

"Config File Rejected due to Invalid or Unexpected TLV 11 encoding;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"

03/27/2021 13:03

73040200

3

"TLV-11 - Illegal Set operation failed;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:02

2436694066

6

"Honoring MDD; IP provisioning mode = IPv6"

01/01/1970 00:02

84020200

5

"Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:02

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:02

84020200

5

"Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

01/01/1970 00:01

84000100

3

"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

After adding splitter:

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
04/02/2021 15:40 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;"
04/02/2021 15:40 68001102 3 "Config File Rejected due to Invalid or Unexpected TLV 11 encoding;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
04/02/2021 15:40 73040200 3 "TLV-11 - Illegal Set operation failed;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
01/01/1970 00:02 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;"
01/01/1970 00:02 84020200 5 "Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84020200 5 "Lost MDD Timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 00:02 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

(edited)

Expert

 • 

110K Messages

4 years ago

For what ? You don't need that splitter. The stats were already in spec. It wasn't broke. You didn't need to fix it. Besides, a splitter should not be used as an attenuator. It could make things worse. "Attenuator Pads" are made specifically for that purpose.

forum icon

New to the Community?

Start Here