# Problems with color code / SM association

**URL:** https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709
**Category:** PMP
**Created:** [February 3, 2016, 11:44pm UTC](https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709 "2016-02-03T23:44:30Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Tuvix\_IT](https://d10gw3vjmzyp8.cloudfront.net/user_avatar/community.cambiumnetworks.com/tuvix_it/32/11583_2.png) [@Tuvix\_IT](https://community.cambiumnetworks.com/u/Tuvix_IT)
#### Post date: [February 3, 2016, 11:44pm UTC](https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709/1 "2016-02-03T23:44:30Z")

</div>

Hi, with the upgrade 14.1.1 for AP PMP450, we noticed a strange problem with SM PMP450.

The SM, after a normal reload, an AP Scan or disconnecting in autonomy, **not back on the**  **primary color code** but in the secondary or tertiary.  
It seems that the antenna no longer see the primary color code because in Tools-\>Ap evaluation the primary disappears.  
If i wait the automatic rescan, sometimes returns to see the primary color code, sometimes not.

Often disappear others color codes: if before we could see 9 AP, after a reboot can see 2; after an another reboot still can return to 9.

When the antenna is finally back on the primary color code, we see that the signal is strong, modulation ok.

Before the upgrade does not look like there was this problem but it certainly is from December 2015.  
Here are some examples of antennas that have had the problem:  
  
**1 case) AP**

| Software Version : | 
CANOPY 14.1.2 (Build 4) AP-AES  

 |

_ **Event log AP** _

_02/01/2016 : 18:04:12 CET : :Time Set  
02/01/2016 : 23:07:38 CET : :Invalid ACK discarded, VC: 37 0a003eb38722  
02/01/2016 : 23:07:38 CET : :Invalid ACK discarded, VC: 37 0a003eb38722  
02/01/2016 : 23:07:38 CET : :Invalid ACK discarded, VC: 37 0a003eb38722  
01/02/2006 : 01:29:13 CET : :Time Set_

**SM** :

| Software Version : | 
CANOPY 14.1.1 SM-AES
 |

_System Event Log SM_

_02/02/2016 : 03:10:45 CET : :user=none; \*System Log Cleared\*;  
02/02/2016 : 05:17:56 CET : : **Error, bad input frequency** : 110219017  
02/02/2016 : 05:18:01 CET : :Error: Invalid frequency:8253864 for band:19  
02/02/2016 : 05:34:59 CET : :Error invalid frequency: 1076041706  
02/02/2016 : 05:34:59 CET : :Error: Calibration does not match frequency band:22, using first cal._

Antenna in _Secondary Color code_ (3). This is our configuration for ever SM: **Color code 1** ever 0

 ![Color_code.jpg](https://d1okf4ta8xniw3.cloudfront.net/original/2X/6/6814c8a4e43c164ccc70954c41d5e30e43fbfe9b.jpeg "Color\_code.jpg")

This is the table of _AP Evaluation_ in Color code 3, Color code 2 (primary in screenshot)&nbsp; **is missing:**

_AP List_  
_AP Selection Method used: Power Level_  
_Current entry index: 6 Session Status: REGISTERED (via **Secondary Color Code 3** )_  
  
  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 6 Frequency: 5600.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-a0-ea-f4 Region: Other_  
_Beacon Receive Power: -66.5 (-69.0 V / -70.0 H) dBm Beacon Count: 15 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 24892 feet MaxRange: 25 miles TxBER: 1 EBcast: 1_  
_Session Count: 2 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 **Color Code: 3** BeaconVersion: 1 SectorUserCount: 16 SyncSrc: 1_  
_NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6_  
_WhiteSched: 0 ICC: 1 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:5 ms_  
  
_Beacon Statistics_  
_Unsupported Feature Beacon Received : &nbsp;&nbsp; &nbsp;__0_  
_Unknown Feature Beacon Received : &nbsp;&nbsp; &nbsp;__0_  
_Old Version Beacon Received : &nbsp;&nbsp; &nbsp;__0_  
_Wrong Frequency Beacon Received : &nbsp;&nbsp; &nbsp;__0_  
_Non Lite Beacon Received : &nbsp;&nbsp; &nbsp;__0_

_&nbsp;_

_ **After a reboot, no changes**.  
After a AP rescan:_

_&nbsp;_

_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 5 Frequency: 5600.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-a0-ea-f4 Region: Other_  
_Beacon Receive Power: -66.5 (-69.0 V / -70.0 H) dBm Beacon Count: 15 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 24941 feet MaxRange: 25 miles TxBER: 1 EBcast: 1_  
_Session Count: 2 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 **Color Code: 3** BeaconVersion: 1 SectorUserCount: 15 SyncSrc: 1_  
_NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6_  
_WhiteSched: 0 ICC: 1 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:5 ms_  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 6 Frequency: 5540.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-a0-eb-14 Region: Other_  
_Beacon Receive Power: -64.0 (-67.0 V / -67.0 H) dBm Beacon Count: 15 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 24892 feet MaxRange: 25 miles TxBER: 1 EBcast: 1_  
_Session Count: 2 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 **Color Code: 2** BeaconVersion: 1 SectorUserCount: 28 SyncSrc: 1_  
_NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6_  
_WhiteSched: 0 ICC: 1 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:5 ms_

Link between AP with Color code 2 and SM have a good signal, but **why it was disappear**? _Link Capacity Test_ with **Color Code 2** (primary):

 ![CC3.png](https://d1okf4ta8xniw3.cloudfront.net/original/2X/f/f1a462e88544371fa6b214a4ac75013c2eb101a2.png "CC3.png")

In _Logs-\>SM auth-\>SM Authorization Log_ in **bold** the disconnections:

_ **01/28/2016 : 18:33:05 CET : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 375** _  
_01/28/2016 : 18:35:06 CET : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0_  
_01/28/2016 : 18:35:06 CET : Event: SMSESMSG, MsgType: SES\_AAATMPACCESS, NewState: REGISTERING, Flag 20_  
_01/28/2016 : 18:35:06 CET : Event: SMAUTHORMSG, NewState: REGISTERING, Flag 0_  
_01/28/2016 : 18:35:05 CET : Event: SMAUTHENMSG, NewState: REGISTERING, Flag 0_  
_01/28/2016 : 18:35:05 CET : Event: SMSESINS, NewState: REGISTERED, Flag 20_  
_01/28/2016 : 18:35:05 CET : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0repeated 2 times_  
_ **02/01/2016 : 11:22:34 CET : Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 1275** _  
_02/01/2016 : 11:24:36 CET : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0_  
_02/01/2016 : 11:24:36 CET : Event: SMSESMSG, MsgType: SES\_AAATMPACCESS, NewState: REGISTERING, Flag 19_  
_02/01/2016 : 11:24:36 CET : Event: SMAUTHORMSG, NewState: REGISTERING, Flag 0_  
_02/01/2016 : 11:24:35 CET : Event: SMAUTHENMSG, NewState: REGISTERING, Flag 0_  
_02/01/2016 : 11:24:35 CET : Event: SMSESINS, NewState: REGISTERED, Flag 19_  
_02/01/2016 : 11:24:35 CET : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0repeated 2 times_

In _Logs-\>SM auth-\>Sm Session Log:_

[**http://textuploader.com/573rn**](http://textuploader.com/573rn)

What are the errors **REGREQTOMAXERR** and **SMVCERR**?

 ![spettro.png](https://d1okf4ta8xniw3.cloudfront.net/original/2X/d/d110f08f1915dc871daba1a4a19421876b1c880a.png "spettro.png")

**2) SM**

| Software Version : | 
CANOPY 14.1.1 SM-AES
 |

AP List ![](http://10.52.0.32:1080/_min.gif?mac_esn=0a003ea2393a)

| 
[**http://textuploader.com/573rf**](http://textuploader.com/573rf)! &nbsp;  

 |

After an AP Rescan:

_AP List_  
_AP Selection Method used: Power Level_  
_Current entry index: 4 Session Status: REGISTERED (via **Primary Color Code 5** )_  
  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 0 Frequency: 5495.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-a0-67-fa Region: Other_  
_Beacon Receive Power: -82.2 (-84.0 V / -87.0 H) dBm Beacon Count: 5 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 25 miles TxBER: 1 EBcast: 1_  
_Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 Color Code: 6 BeaconVersion: 1 SectorUserCount: 8 SyncSrc: 1_  
_NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6_  
_WhiteSched: 0 ICC: 1 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:5 ms_  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 1 Frequency: **5550**.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-b2-65-d2 Region: Other_  
_Beacon Receive Power: -80.5 (-83.0 V / -84.0 H) dBm Beacon Count: 15 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 13 miles TxBER: 1 EBcast: 1_  
_Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -60 dBm SectorID: 0 Color Code: 103 BeaconVersion: 1 SectorUserCount: 3 SyncSrc: 1_  
_NumULSlots: 16 NumDLSlots: 60 NumULContSlots: 4_  
_WhiteSched: 0 ICC: 0 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:2.5 ms_  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 2 Frequency: **5580**.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-a2-41-e9 Region: Other_  
_Beacon Receive Power: -81.5 (-85.0 V / -84.0 H) dBm Beacon Count: 14 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 25 miles TxBER: 1 EBcast: 1_  
_Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 Color Code: 4 BeaconVersion: 1 SectorUserCount: 8 SyncSrc: 1_  
_NumULSlots: 27 NumDLSlots: 41 NumULContSlots: 6_  
_WhiteSched: 0 ICC: 1 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:2.5 ms_  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 3 Frequency: 5630.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-b2-65-bb Region: Other_  
_Beacon Receive Power: -79.9 (-82.0 V / -84.0 H) dBm Beacon Count: 10 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 13 miles TxBER: 1 EBcast: 1_  
_Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -60 dBm SectorID: 0 Color Code: 102 BeaconVersion: 1 SectorUserCount: 15 SyncSrc: 1_  
_NumULSlots: 16 NumDLSlots: 60 NumULContSlots: 4_  
_WhiteSched: 0 ICC: 0 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:2.5 ms_  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 4 Frequency: 5795.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-a0-c6-71 Region: Other_  
_Beacon Receive Power: -74.5 (-77.0 V / -78.0 H) dBm Beacon Count: 15 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 36603 feet MaxRange: 25 miles TxBER: 1 EBcast: 1_  
_Session Count: 2 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 Color Code: 5 BeaconVersion: 1 SectorUserCount: 24 SyncSrc: 1_  
_NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6_  
_WhiteSched: 0 ICC: 1 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:5 ms_  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 5 Frequency: 5860.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-b2-f7-13 Region: Other_  
_Beacon Receive Power: -87.0 (-90.0 V / -90.0 H) dBm Beacon Count: 8 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 15 miles TxBER: 1 EBcast: 0_  
_Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -58 dBm SectorID: 0 Color Code: 94 BeaconVersion: 1 SectorUserCount: 5 SyncSrc: 1_  
_NumULSlots: 19 NumDLSlots: 57 NumULContSlots: 3_  
_WhiteSched: 0 ICC: 0 Authentication: Disabled. SM configured to require authentication._  
_SM PPPoE: Supported_  
_Frame Period:2.5 ms_  
_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*_  
_Index: 6 Frequency: 5870.000 MHz&nbsp;&nbsp; Channel Bandwidth: 20.0 MHz&nbsp; Cyclic Prefix: 1/16_  
_ESN: 0a-00-3e-b2-0d-1b Region: Other_  
_Beacon Receive Power: -84.8 (-86.0 V / -91.0 H) dBm Beacon Count: 5 FECEn: 1_  
_Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 25 miles TxBER: 1 EBcast: 1_  
_Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0_  
_NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0_  
_AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 Color Code: 21 BeaconVersion: 1 SectorUserCount: 10 SyncSrc: 1_  
_NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6_  
_WhiteSched: 0 ICC: 1 Authentication: Enabled_  
_SM PPPoE: Supported_  
_Frame Period:5 ms_

Why there are two new AP (one of these is not even ours)?

This is our problem: antennas see sometimes and sometimes not APs, although very near. In this case, Ap with frequencies **5580** e **5550** are weak, but it is the same with signal -65

**3)SM**

| Software Version : | 
CANOPY 13.4 SM-AES
 |

**AP:**

| Software Version : | 
CANOPY 14.1.1 AP-AES
 |

**Primary Color Code is 1,** but after a reboot, disappear. After two AP Rescan, SM is come back in AP with Color Code 1.

 ![Nonno2.png](https://d1okf4ta8xniw3.cloudfront.net/original/2X/7/79231e53b2cee04d8dd9c647175f262868dee736.png "Nonno2.png")

I am the only one with this problem? Solutions? :(  
  
Guido - Technician

---

<div class="post-metadata">

### Author: ![Tuvix\_IT](https://d10gw3vjmzyp8.cloudfront.net/user_avatar/community.cambiumnetworks.com/tuvix_it/32/11583_2.png) [@Tuvix\_IT](https://community.cambiumnetworks.com/u/Tuvix_IT)
#### Post date: [February 4, 2016, 9:06am UTC](https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709/2 "2016-02-04T09:06:46Z")

</div>

Today another case:

**AP97** with (primary) color code **7 -&nbsp;** CANOPY 14.1.2 (Build 4) APL-AES

**AP94&nbsp;** with (secondary)&nbsp;color code **&nbsp;4 -&nbsp;** CANOPY 14.1.2 (Build 4) AP-AES

**SM** with primary color code 7 and secondary 4 **-&nbsp;** CANOPY 14.1.1 SM-AES

**09:14 =** hour of disconnection

_(in order)_

In **AP97 (primary)**, Logs -\>Ap Session:

AP Session Log ![](http://10.52.0.97/_min.gif?mac_esn=0a003eb20d58)

| 
Session Dump for LUID 5 (-\>Sm with problem)  
  
02/04/2016 : 08:38:50 CET : Event: SES\_MSG, MsgType: PAREQ, NewState: IN SESSION, Flag 0  
repeated 17 times  
**02/04/2016 : 09:14:27** CET : Event: OOS, MsgType: VCERR, NewState: IDLE, Flag 1361
 |

In the SM, logs -\> Sm sessions -\>&nbsp;

02/04/2016 : 09:14:30 CET : **Event: SMSESFAIL, MsgType: SMVCERR, NewState: OOSERVICE, Flag 1365**  
02/04/2016 : 09:18:44 CET : Event: SMSESACTIVATE, NewState: REGISTERING, Flag 0  
02/04/2016 : 09:18:44 CET : Event: SMSESMSG, MsgType: SES\_AAATMPACCESS, NewState: REGISTERING, Flag 19  
02/04/2016 : 09:18:44 CET : Event: SMAUTHORMSG, NewState: REGISTERING, Flag 0  
02/04/2016 : 09:18:44 CET : Event: SMAUTHENMSG, NewState: REGISTERING, Flag 0  
02/04/2016 : 09:18:45 CET : Event: SMSESINS, NewState: REGISTERED, Flag 19  
02/04/2016 : 09:18:45 CET : Event: SMAUTHORMSG, NewState: REGISTERED, Flag 0  
repeated 2 times

In **AP94(**secondary), Logs -\>

AP Session Log

Session Dump for LUID 27  
  
02/04/2016 : 09:20:44 CET : Event: SES\_MSG, MsgType: PAREQ, NewState: IN SESSION, Flag 0  
repeated 18 times

&nbsp;In SM:

SM Authentication Log

02/04/2016 : 09:14:30 CET : **Event: AUTHEN\_RESET** , NewState: IDLE, Flag 0  
02/04/2016 : 09:18:44 CET : Event: AUTHEN\_REQ, NewState: AUTHENTICATING, Flag 0  
02/04/2016 : 09:18:44 CET : Event: AUTHEN\_EAPSTART, NewState: AUTHENTICATING, Flag 0  
02/04/2016 : 09:18:45 CET : Event: AUTHEN\_SUC, NewState: AUTHENTICATED, Flag 0

SM Authorization Log ![](http://10.62.7.96/_min.gif?mac_esn=0a003eb1b38b)

02/04/2016 : 09:14:30 CET : Event: AUTHOR\_RESET, NewState: IDLE, Flag 0  
02/04/2016 : 09:18:44 CET : Event: AUTHOR\_MSG, MsgType: BCASTKEY, NewState: IDLE, Flag 0  
02/04/2016 : 09:18:45 CET : Event: AUTHOR\_REQ, NewState: AUTHORIZING, Flag 0  
02/04/2016 : 09:18:45 CET : Event: AUTHOR\_MSG, MsgType: BCASTKEY, NewState: AUTHORIZING, Flag 0  
02/04/2016 : 09:18:44 CET : Event: AUTHOR\_REQPARAMS, NewState: AUTHORIZING, Flag 0  
02/04/2016 : 09:18:44 CET : Event: AUTHOR\_CFGPARAMS, NewState: AUTHORIZED, Flag 126Antenna now in AP94 (secondary):

EAP Radius Log

| 
  
02/04/2016 : 09:18:44 CET : Create EAP Session.  
02/04/2016 : 09:18:44 CET : Restarted EAP Session.  
02/04/2016 : 09:18:44 CET : FULL Restart EAP Session.  
02/04/2016 : 09:18:45 CET : EAP SUCCESS For Session  
02/04/2016 : 09:18:45 CET : Deleted EAP Session. 
 |

AP List ![](http://10.62.7.96/_min.gif?mac_esn=0a003eb1b38b)

| 
AP Selection Method used: Power Level  
Current entry index: 1 Session Status: REGISTERED (via **Secondary Color Code 4)**  
  
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Index: 0 Frequency: 5715.000 MHz &nbsp; Channel Bandwidth: 20.0 MHz &nbsp;Cyclic Prefix: 1/16  
ESN: 0a-00-3e-b2-39-37 Region: Other  
Beacon Receive Power: -84.5 (-86.0 V / -90.0 H) dBm Beacon Count: 15 FECEn: 1  
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 13 miles TxBER: 1 EBcast: 1  
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0  
NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0  
AP Gain: 22 dBm AP RcvT: -60 dBm SectorID: 0 Color Code: 104 BeaconVersion: 1 SectorUserCount: 1 SyncSrc: 1  
NumULSlots: 16 NumDLSlots: 60 NumULContSlots: 4  
WhiteSched: 0 ICC: 0 Authentication: Enabled  
SM PPPoE: Supported  
Frame Period:2.5 ms  
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Index: 1 Frequency: 5740.000 MHz &nbsp; Channel Bandwidth: 20.0 MHz &nbsp;Cyclic Prefix: 1/16  
ESN: 0a-00-3e-a0-8a-a2 Region: Other  
Beacon Receive Power: -67.2 (-72.0 V / -69.0 H) dBm Beacon Count: 5 FECEn: 1  
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 46354 feet MaxRange: 25 miles TxBER: 1 EBcast: 1  
Session Count: 2 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0  
NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0  
AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 **Color Code: 4** BeaconVersion: 1 SectorUserCount: 20 SyncSrc: 1  
NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6  
WhiteSched: 0 ICC: 1 Authentication: Enabled  
SM PPPoE: Supported  
Frame Period:5 ms  
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Index: 3 Frequency: 5620.000 MHz &nbsp; Channel Bandwidth: 20.0 MHz &nbsp;Cyclic Prefix: 1/16  
ESN: 0a-00-3e-a0-b0-10 Region: Other  
Beacon Receive Power: -78.2 (-83.0 V / -80.0 H) dBm Beacon Count: 12 FECEn: 1  
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 25 miles TxBER: 1 EBcast: 1  
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0  
NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0  
AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 Color Code: 3 BeaconVersion: 1 SectorUserCount: 12 SyncSrc: 1  
NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6  
WhiteSched: 0 ICC: 1 Authentication: Enabled  
SM PPPoE: Supported  
Frame Period:5 ms  
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Index: 4 Frequency: 5795.000 MHz &nbsp; Channel Bandwidth: 20.0 MHz &nbsp;Cyclic Prefix: 1/16  
ESN: 0a-00-3e-a0-c6-71 Region: Other  
Beacon Receive Power: -83.5 (-87.0 V / -86.0 H) dBm Beacon Count: 15 FECEn: 1  
Type: Multipoint Avail: 1 Age: 0 Lockout: 0 RegFail 0 Range: 0 feet MaxRange: 25 miles TxBER: 1 EBcast: 1  
Session Count: 0 NoLUIDS: 0 OutOfRange: 0 AuthFail: 0 EncryptFail: 0 Rescan Req: 0 SMLimitReached: 0  
NoVC's: 0 VCRsv/430smFail: 0 VCActFail: 0  
AP Gain: 22 dBm AP RcvT: -63 dBm SectorID: 0 Color Code: 5 BeaconVersion: 1 SectorUserCount: 28 SyncSrc: 1  
NumULSlots: 68 NumDLSlots: 103 NumULContSlots: 6  
WhiteSched: 0 ICC: 1 Authentication: Enabled  
SM PPPoE: Supported  
Frame Period:5 ms
 |

**Where is Color Code &nbsp;7?** The signal was -64.  
In this AP94 with seconday Color Code -68.

Guido

---

<div class="post-metadata">

### Author: ![Al1](https://d10gw3vjmzyp8.cloudfront.net/user_avatar/community.cambiumnetworks.com/al1/32/11571_2.png) [@Al1](https://community.cambiumnetworks.com/u/Al1)
#### Post date: [February 18, 2016, 11:00pm UTC](https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709/3 "2016-02-18T23:00:37Z")

</div>

Thank you for this detailed analysis, Guido!

We are currently investigating an issue with SMs switching back and forth between color codes and not showing APs in the AP Eval scan list. &nbsp;I'll update here when we have more news.

-Al

---

<div class="post-metadata">

### Author: ![Lightnet\_Barry](https://d10gw3vjmzyp8.cloudfront.net/letter_avatar_proxy/v4/letter/l/b19c9b/32.png) [@Lightnet\_Barry](https://community.cambiumnetworks.com/u/Lightnet_Barry)
#### Post date: [March 4, 2016, 10:28am UTC](https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709/4 "2016-03-04T10:28:31Z")

</div>

One of our techs reported this problem yesterday.

Both SM and AP were on 14.1.1

The only information I have from it is from the AP session log dump:

03/03/2016 : 17:17:11 UTC : Event: SES\_MSG, MsgType: PAREQ, NewState: IN SESSION, Flag 0  
repeated 2 times  
03/03/2016 : 17:22:59 UTC : Event: OOS, MsgType: VCERR, NewState: IDLE, Flag 250  
03/03/2016 : 17:42:44 UTC : Event: REGREQ, NewState: REGISTERING, Flag 0  
03/03/2016 : 17:42:44 UTC : Event: AUTHEN\_SUC, NewState: IN SESSION, Flag 0  
03/03/2016 : 17:42:44 UTC : Event: SEND\_AUTHOR\_MSG, NewState: IN SESSION, Flag 0  
03/03/2016 : 17:42:44 UTC : Event: SES\_MSG, MsgType: ESNQUERY, NewState: IN SESSION, Flag 0  
03/03/2016 : 17:44:33 UTC : Event: OOS, MsgType: VCERR, NewState: IDLE, Flag 250  
03/03/2016 : 18:06:10 UTC : Event: REGREQ, NewState: REGISTERING, Flag 0  
03/03/2016 : 18:06:11 UTC : Event: OOS, MsgType: AUTHENFAIL, NewState: IDLE, Flag 0

Unfortunately the tech swapped out the SM in order to complete the installation so I have no further information currently.

The repacement SM is running 13.4

Once I get the SM back on the bench I can investigate further.

---

<div class="post-metadata">

### Author: ![Lightnet\_Barry](https://d10gw3vjmzyp8.cloudfront.net/letter_avatar_proxy/v4/letter/l/b19c9b/32.png) [@Lightnet\_Barry](https://community.cambiumnetworks.com/u/Lightnet_Barry)
#### Post date: [May 20, 2016, 3:51pm UTC](https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709/5 "2016-05-20T15:51:59Z")

</div>

I could find no issue with the SM above and it was re-used on another site with no issues arising, however I did have the same problem on a new build site today.

Again it was 14.1.1 on AP and SM, Again the same error messages "Event: OOS, MsgType: VCERR, NewState: IDLE, Flag 180" and random disconnects / reg failures.

This time I found that the SM could see another AP with partially overlaping frequency.

Once I cleaned up the partial RF overlap the issue resolved.

---

<div class="post-metadata">

### Author: ![Tuvix\_IT](https://d10gw3vjmzyp8.cloudfront.net/user_avatar/community.cambiumnetworks.com/tuvix_it/32/11583_2.png) [@Tuvix\_IT](https://community.cambiumnetworks.com/u/Tuvix_IT)
#### Post date: [May 20, 2016, 7:18pm UTC](https://community.cambiumnetworks.com/t/problems-with-color-code-sm-association/43709/6 "2016-05-20T19:18:21Z")

</div>

Hi, our problem is under investigation and we are doing some tests with Cambium although the nature of the problem is not discovered yet. Even today, for example, we have restarted an antenna that had set the primary and secondary color code with good signals:: it's back operating in the secondary after **48** minutes ........

EDIT: new beta with fix&nbsp;[http://community.cambiumnetworks.com/t5/PMP-Beta/Beta-Software-14-1-2-Build-17-for-PMP-PTP-450-and-PMP-PTP-450i/m-p/54771#M588](https://community.cambiumnetworks.com/t/beta-software-14-1-2-build-17-for-pmp-ptp-450-and-pmp-ptp-450i-is-now-available/45601)

Under test, seems works.  
Tomorrow intrusive test!
