Zero Touch Option 66 and 3GHz Issues

Products PMP
1

We are moving to a zero touch setup and away from radius authentication of our 450 product. We are having issues with existing customers when they download the configuration script (the script does not set any frequencies). After the script runs, SMs no longer register. When we visit them in the field they only have frequency 3310 selected.

Has anyone else experienced this? Below is a copy of the downloaded configuration script with sensitive information removed.

{
 "userParameters": {
  "radioConfig": {
   "regionCode": 25
  },
  "portVlanConfig": {
   "ingressVIDBox": 4000
  },
  "smNetworkConfig": {
   "networkAccess": 1
  },
  "authenticationConfig": {
   "accounts": [
    {
     "userName": "admin",
     "level": 3,
     "readOnly": false,
     "passwordEncrypted": "*****"
    },
    {
     "userName": "root",
     "level": 3,
     "readOnly": false,
     "passwordEncrypted": "*****"
    }
   ]
  },
  "networkConfig": {
   "packetFilterSmb": 1,
   "snmpStatus": 0,
   "lanDhcpState": 1,
   "packetFilterPppoe": 1,
   "packetFilterAllOthers": 1,
   "packetFilterBootpServer": 1,
   "enableSecurityBanner": 0,
   "packetFilterAllIpv6": 1,
   "packetFilterDirection": 1
  },
  "location": {
   "siteName": "XXXXX",
   "siteInfoViewable": 1,
   "siteContact": "John Doe 5555555555",
   "siteLocation": "555 John Doe Ave Phoenix 85017"
  },
  "smRadioConfig": {
   "bandwidthScanList": [
    100,
    200,
    300,
    400
   ],
   "colorCodeList": [
    {
     "colorCode": 42,
     "priority": 1
    }
   ]
  },
  "smNatNetworkConfig": {
   "naptRemoteManage": 1
  },
  "vlanConfig": {
   "managementVID": 1000,
   "priorityPrecedence": 1
  }
 },
 "configFileParameters": {
  "rebootIfRequired": true,
  "setToDefaults": false
 },
 "cfgFileString": "Canopy configuration file",
 "cfgFileVersion": "1.0"
}
2

I forgot to mention that this is a random occurrence and does not affect all 3GHz SMs (maybe less than 5%). We do not have this same issue with 5GHz SMs.

3

It looks like you might have missed closing your “smRadioConfig”: {
So every setting after “bandwidthScanList” could be getting “blanked out”

4

Are you using the CBRS band (3550-3700)? If so, you can use this on the SM’s to set the proper channels using a 5MHz raster:

{
  "userParameters": {
    "radioConfig": {
      "customFrequencies": [
        3555000,
        3560000,
        3565000,
        3570000,
        3575000,
        3580000,
        3585000,
        3590000,
        3595000,
        3600000,
        3605000,
        3610000,
        3615000,
        3620000,
        3625000,
        3630000,
        3635000,
        3640000,
        3645000,
        3650000,
        3655000,
        3660000,
        3665000,
        3670000,
        3675000,
        3680000,
        3685000,
        3690000,
        3695000
      ]
    },
    "smRadioConfig": {
      "frequencyScanList": [
        3555000,
        3560000,
        3565000,
        3570000,
        3575000,
        3580000,
        3585000,
        3590000,
        3595000,
        3600000,
        3605000,
        3610000,
        3615000,
        3620000,
        3625000,
        3630000,
        3635000,
        3640000,
        3645000,
        3650000,
        3655000,
        3660000,
        3665000,
        3670000,
        3675000,
        3680000,
        3685000,
        3690000,
        3695000
      ],
      "bandwidthScanList": [
        100,
        200,
        300,
        400
      ]
    }
  }
}
5

Anthony,
Thank you for your input. I copied and pasted what I had posted and also had my system auto generate the script again and could not find a missing curly brace. I went through it several times and could not find any missing termination.

Gilbert

6

Eric,
Thank you for reviewing my post. My original auto generating scrip generated the frequency scan list. This is when I first experienced this symptom. I though it might be the frequency scan list, so I removed it and got down to the script I posted and am still having the issue with.

With all of that said, I have not been able to really test, but I think it might be radios that are currently connected to my APs (APs set to US running CBRS) that are set to region other. If you look at my script, it sets the region to US ( “regionCode”: 25). I am thinking that changing the region from other to US is causing this, but I am not sure. I only have a few 3GHz sites that I am testing this script on, so I just do not have enough data to discount this issue. I was thinking about taking that out of my configuration and seeing if I have the same results.

7

For various reasons, I think it’s a good idea to leave all the SM’s in region Other/Other. When they register to the AP they will follow the AP’s region along with getting the proper CBSD information from the AP, and you’ll see this message on the SM’s:

image

8

Eric,
You are right in that it will connect and it will give you that message. I just like having it complete and that is why it is in there. I also have it in there if a 5GHz SM connects and have not had that issue in the 5GHz variants of frequency and model.

I am taking it out for another test deployment. It is a bug though if changing the region completely clears the frequency list even if you have the frequency list defined in the zero touch configuration.

Gilbert

9

Did you ever get this resolved? We are having the exact same issue with ours.