Solved

New SB8200 Install Modem and event log issues

  • 29 November 2022
  • 8 replies
  • 992 views
B
Rank
  • bert The Certified
  • The Certified
  • 6 replies

Below is the Status report and Event Log for new install of an SB8200 Modem with the Surfboard 2 tower wifi 6 mesh system added on.

I’ve had problems with weak or briefly dropping internet along with event log timeouts with old Netgear modem for a long time also.

can Someone interpret this and see if this would indicate a problem with the 35 year old coaxial cable underground from old Comcast now Xfinity ?


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     423000000 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
4     Locked     QAM256     423000000 Hz     1.5 dBmV     42.4 dB     1402     1352
1     Locked     QAM256     405000000 Hz     3.3 dBmV     43.1 dB     1417     1369
2     Locked     QAM256     411000000 Hz     2.9 dBmV     43.0 dB     1324     1383
3     Locked     QAM256     417000000 Hz     1.8 dBmV     42.4 dB     1513     1337
5     Locked     QAM256     429000000 Hz     2.0 dBmV     42.6 dB     1511     1306
6     Locked     QAM256     435000000 Hz     1.9 dBmV     42.5 dB     1373     1397
7     Locked     QAM256     441000000 Hz     2.1 dBmV     42.7 dB     1394     1367
8     Locked     QAM256     447000000 Hz     1.9 dBmV     42.6 dB     1373     1365
9     Locked     QAM256     453000000 Hz     2.2 dBmV     42.5 dB     1364     1300
10     Locked     QAM256     459000000 Hz     2.3 dBmV     42.8 dB     1393     1363
11     Locked     QAM256     465000000 Hz     2.5 dBmV     42.9 dB     1448     1378
12     Locked     QAM256     471000000 Hz     2.5 dBmV     42.8 dB     1460     1320
13     Locked     QAM256     477000000 Hz     2.5 dBmV     42.8 dB     1489     1340
14     Locked     QAM256     483000000 Hz     2.4 dBmV     42.7 dB     1445     1401
15     Locked     QAM256     489000000 Hz     2.3 dBmV     42.7 dB     1522     1457
16     Locked     QAM256     495000000 Hz     2.7 dBmV     42.8 dB     1531     1379
17     Locked     QAM256     507000000 Hz     2.9 dBmV     43.0 dB     1539     1340
18     Locked     QAM256     513000000 Hz     2.8 dBmV     43.1 dB     1534     1373
19     Locked     QAM256     519000000 Hz     3.2 dBmV     43.2 dB     1517     1377
20     Locked     QAM256     525000000 Hz     3.1 dBmV     43.0 dB     1488     1375
21     Locked     QAM256     531000000 Hz     3.5 dBmV     43.2 dB     1481     1486
22     Locked     QAM256     537000000 Hz     3.1 dBmV     43.2 dB     1497     1450
23     Locked     QAM256     543000000 Hz     3.4 dBmV     43.2 dB     1528     1398
24     Locked     QAM256     549000000 Hz     3.1 dBmV     43.0 dB     1568     1381
25     Locked     QAM256     555000000 Hz     3.3 dBmV     43.2 dB     1462     1421
26     Locked     QAM256     561000000 Hz     3.0 dBmV     43.0 dB     1465     1410
27     Locked     QAM256     567000000 Hz     3.2 dBmV     43.1 dB     1582     1370
28     Locked     QAM256     573000000 Hz     3.0 dBmV     43.0 dB     1476     1450
29     Locked     QAM256     579000000 Hz     3.2 dBmV     43.1 dB     1443     1447
30     Locked     QAM256     585000000 Hz     3.3 dBmV     43.0 dB     1551     1415
31     Locked     QAM256     591000000 Hz     3.3 dBmV     43.0 dB     1430     1414
32     Locked     QAM256     597000000 Hz     3.7 dBmV     43.0 dB     1513     1444
193     Locked     Other     690000000 Hz     5.2 dBmV     42.2 dB     1939666362     833

 

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

 

Current System Time: Tue Nov 29 14:49:08 2022

 

 

EVENT LOG: ( I put periods where my mac address was, think I got them all :)


Date Time     Event ID     Event Level     Description
11/29/2022 12:46     82000500     3     "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=-------------;CMTS-MAC=………...;CM-QOS=1.1;CM-VER=3.1;"
11/29/2022 07:19     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=…………..;CMTS-MAC=…………..;CM-QOS=1.1;CM-VER=3.1;"
11/29/2022 07:19     84020300     5     "MDD message timeout;CM-MAC=…………….;CMTS-MAC=…………...;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 23:20     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=………….;CMTS-MAC=………….;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 23:20     84020300     5     "MDD message timeout;CM-MAC=………….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 12:28     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=………….;CMTS-MAC=………..;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 12:27     82000500     3     "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=…………..;CMTS-MAC=……...:00;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 12:27     84020300     5     "MDD message timeout;CM-MAC=………..;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 09:19     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 3 6 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=…………..;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 09:19     84020300     5     "MDD message timeout;CM-MAC=………..;CMTS-MAC=………….;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 01:20     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 3 6 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 01:20     84020300     5     "MDD message timeout;CM-MAC=………...;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 01:19     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 3 6 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=………...;CMTS-MAC=………...;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 01:19     82000500     3     "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=………...;CMTS-MAC=………...;CM-QOS=1.1;CM-VER=3.1;"
11/28/2022 01:19     84020300     5     "MDD message timeout;CM-MAC=………...;CMTS-MAC=…………..;CM-QOS=1.1;CM-VER=3.1;"
11/27/2022 23:18     82000500     3     "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=………...;CMTS-MAC=………...;CM-QOS=1.1;CM-VER=3.1;"
11/27/2022 21:20     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 3 6 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=………..;CMTS-MAC=………...;CM-QOS=1.1;CM-VER=3.1;"
11/27/2022 21:20     82000500     3     "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=………..;CMTS-MAC=………...;CM-QOS=1.1;CM-VER=3.1;"
11/27/2022 21:20     84020300     5     "MDD message timeout;CM-MAC=………...;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/27/2022 08:20     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 3 6 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=……….;CMTS-MAC=……..;CM-QOS=1.1;CM-VER=3.1;"
11/27/2022 08:20     82000500     3     "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/27/2022 08:20     84020300     5     "MDD message timeout;CM-MAC=………...;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/26/2022 20:20     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 3 6 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=………...;CMTS-MAC=……..;CM-QOS=1.1;CM-VER=3.1;"
11/26/2022 20:20     84020300     5     "MDD message timeout;CM-MAC=………..;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/26/2022 13:14     2436694061     5     "Dynamic Range Window violation"
11/26/2022 13:14     82001100     5     "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=………..;CMTS-MAC=……...;CM-QOS=1.1;CM-VER=3.1;"
11/25/2022 21:24     2436694061     5     "Dynamic Range Window violation"
11/25/2022 21:24     82001100     5     "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=………..;CMTS-MAC=………...;CM-QOS=1.1;CM-VER=3.1;"
11/25/2022 14:42     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 6 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=………….;CMTS-MAC=…...;CM-QOS=1.1;CM-VER=3.1;"
11/25/2022 14:42     84020300     5     "MDD message timeout;CM-MAC=…….;CMTS-MAC=……..;CM-QOS=1.1;CM-VER=3.1;"
11/24/2022 12:07     74010100     6     "CM-STATUS message sent. Event Type Code: 4; Chan ID: 6 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=…...;CMTS-MAC=……...;CM-QOS=1.1;CM-VER=3.1;"
11/24/2022 12:07     82000500     3     "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
11/24/2022 12:07     84020300     5     "MDD message timeout;CM-MAC=……...;CMTS-MAC=……..;CM-QOS=1.1;CM-VER=3.1;"
11/24/2022 02:22     2436694061     5     "Dynamic Range Window violation"
11/24/2022 02:22     82001100     5     "RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=……..;CMTS-MAC=……..;CM-QOS=1.1;CM-VER=3.1;"
11/24/2022 00:07     74010100     6<

 

icon

Best answer by plemans 2 December 2022, 23:26

View original
This topic has been closed for comments

8 replies

S
Rank
Userlevel 5
Badge +41

Hello bert, 

 

I just read the Cable Signal Levels information that you just shared and found an issue: The upstream levels.

 

For 3 or more Upstream channels the Power Levels should be between 45 to 51 dBmV and channel 1 and 5 are below the range. It’s minimal, I know, but it could affect the signal to cause the signal to drop. I’ll be attaching our official article for that information as reference at the end of the reply.

Now, how this is fixed? first you can attempt a Factory Reset by following this steps:

 

Factory Reset With the Reset Button

Resetting the SB8200 cable modem can fix connectivity issues and ensure it is operating at the fastest speed available for the Internet service subscribed.

  1. If there is no Internet access resetting the SB8200 cable modem to factory default can fix connectivity issue. 
     
  2. Carefully insert the tip of a pen or the end of an unwound paperclip into the reset button.
     
  3. Press and hold down the Reset button for 10 seconds and then release it.  The front panel LEDs will flash.

    NOTE: There may be up to one minute delay for the Power LED on the SB8200 front panel to light up after the modem starts up.

    User-added image

If that didn’t help, you will need to have your Service Provider readjust these levels to the right range. Let us know if the issue is fixed.

 

Information about the Cable Signal Levels:

 

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

 

SURFboard Community Moderator Team
B
Rank

Thank you for responding.

I saw those levels were just a tad low.

I actually have been dealing with Xfinity and they are sending out a tech tomorrow afternoon.

I was hoping someone would reply here so I could have this input before the tech arrives.

I’ll post here with results in case it could help someone else down the road.

B
Rank

I did do the 10 second reset after my last post, and for the next hour or so before i went to bed the un correctable’s were all zero.

just woke up this morning and the thousands of un correctable’s are there still, but the power on the upstream channels is a bit lower than before the reset…

 

Xfinity will be here this afternoon. Ill see if they can get those power levels withing range.

 

 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 43.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 44.0 dBmV
3 3 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 44.0 dBmV
4 4 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 45.0 dBmV
5 5 Locked SC-QAM Upstream 40400000 Hz 3200000 Hz 43.0 dBmV

 

 

 
B
Rank

Yesterday afternoon, Xfinity replaced the underground cable from their box in the neighbor’s yard to my house but left an old 8’ section between that line and the line into my house.

Tech said he had errors before but not now that he replaced the line.

I mentioned about adjusting the upstream power levels to fall between the 45-51 as suggested, but he said the higher he would go the less ability it would have for a better connection, that he likes to see them on the lower side, so he didn't adjust them.

we agreed to see if the new section of cable would correct my issues…

 

24 hours later, same problem, but power levels are now 45 and 46 with an average of about 3800 un correctable errors compared to half of that before he showed up.

 

now what ??

operation of the cable modem.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 423000000 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
4 Locked QAM256 423000000 Hz 1.6 dBmV 41.9 dB 1580 1649
1 Locked QAM256 405000000 Hz 3.3 dBmV 42.5 dB 1409 1575
2 Locked QAM256 411000000 Hz 3.0 dBmV 42.5 dB 2230 3384
3 Locked QAM256 417000000 Hz 2.0 dBmV 42.1 dB 2143 3571
5 Locked QAM256 429000000 Hz 2.2 dBmV 42.1 dB 2283 3316
6 Locked QAM256 435000000 Hz 2.3 dBmV 42.3 dB 2166 3311
7 Locked QAM256 441000000 Hz 2.9 dBmV 42.5 dB 2276 4189
8 Locked QAM256 447000000 Hz 2.6 dBmV 42.3 dB 2109 3877
9 Locked QAM256 453000000 Hz 2.6 dBmV 42.4 dB 2316 3763
10 Locked QAM256 459000000 Hz 2.7 dBmV 42.5 dB 1485 2281
11 Locked QAM256 465000000 Hz 2.8 dBmV 42.4 dB 2406 4304
12 Locked QAM256 471000000 Hz 2.8 dBmV 42.6 dB 2424 4761
13 Locked QAM256 477000000 Hz 2.8 dBmV 42.4 dB 2275 4607
14 Locked QAM256 483000000 Hz 2.7 dBmV 42.4 dB 2381 4585
15 Locked QAM256 489000000 Hz 2.6 dBmV 42.4 dB 2403 4604
16 Locked QAM256 495000000 Hz 3.1 dBmV 42.5 dB 2548 4935
17 Locked QAM256 507000000 Hz 3.2 dBmV 42.7 dB 2408 4584
18 Locked QAM256 513000000 Hz 3.1 dBmV 42.6 dB 2316 4723
19 Locked QAM256 519000000 Hz 3.6 dBmV 42.9 dB 2266 4677
20 Locked QAM256 525000000 Hz 3.5 dBmV 42.9 dB 2389 4606
21 Locked QAM256 531000000 Hz 4.0 dBmV 42.9 dB 2483 5085
22 Locked QAM256 537000000 Hz 3.5 dBmV 42.9 dB 2305 4711
23 Locked QAM256 543000000 Hz 3.9 dBmV 42.8 dB 2378 5239
24 Locked QAM256 549000000 Hz 3.4 dBmV 42.8 dB 2560 5202
25 Locked QAM256 555000000 Hz 3.6 dBmV 42.8 dB 2225 4937
26 Locked QAM256 561000000 Hz 3.3 dBmV 42.7 dB 2548 4853
27 Locked QAM256 567000000 Hz 3.5 dBmV 42.6 dB 1418 1715
28 Locked QAM256 573000000 Hz 3.3 dBmV 42.7 dB 2373 4920
29 Locked QAM256 579000000 Hz 3.5 dBmV 42.9 dB 2384 4751
30 Locked QAM256 585000000 Hz 3.5 dBmV 42.7 dB 2406 4873
31 Locked QAM256 591000000 Hz 3.6 dBmV 42.8 dB 2282 4863
32 Locked QAM256 597000000 Hz 3.9 dBmV 42.9 dB 2372 4990
193 Locked Other 690000000 Hz 5.0 dBmV 41.8 dB 223917188 418

 

 

 
Upstream Bonded Channels
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 45.0 dBmV
2 2 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 45.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 40400000 Hz 3200000 Hz 45.0 dBmV

 

 

 

Current System Time: Fri Dec 2 14:20:17 2022

 

B
Rank

 These are the only events logged since the tech did his thing.

Its now 1450 hrs, last event was just after midnight last night.

With soooo many un correctable errors…..why ?

 

 

Date Time

 Event ID Event Level Description
12/02/2022 00:50 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
12/02/2022 00:30 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
12/02/2022 00:30 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
12/02/2022 00:30 84020300 5 "MDD message timeout;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
12/01/2022 17:00 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=……….;CMTS-MAC=……….;CM-QOS=1.1;CM-VER=3.1;"
12/01/2022 17:00 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
plemans
Rank
Userlevel 6
Badge +40

You still have line issues. Check all your connectors in the home. 

If you can, direct connect the modem to where the line comes into the home. This helps prevent the line in the home being the issue

Current setup: Netgear CM3000-->Netgear RBE973S-->2.5gig tp-link switch, Xfinity 1.4gig/240mbps
B
Rank

Thanks,

I just pulled the newer RG6 from the modem enough to take it straight to the new cable the tech ran yesterday to the outside of the house now (got rid of the 8’ old cable between the two)

 

Now all cable is new with only their splitter on the outside of the house for them to check their signals….

20 minutes later, getting over 100 uncorrectables on all channels.

 

I scheduled them to come back out this Thursday, gotta bee from their pole under the street now, well see….

B
Rank

Xfinity Tech was out last night and said his supervisor checked and saw my neighbors are experiencing the same thing, so we can close this thread and chalk this up to another case of internet supplier problems not my wiring or modem.

Terms & ConditionsCookie settings