STILL unable to set protocol filters on 450SMs with cnMaestro

so I posted this issue on this forum and the 450 forum several months ago, and the release notes for 16.0.0.1 state that this issue was fixed but it for sure is NOT fixed.  I've been trying to set the protocol filters on 450SMs with this template. cnMaestro says it processes and completes but the SM is not updated.

VERY FRUSTRATING!!! :-/

{
"networkConfig": {
"webAutoUpdate": 3,
"ethernetLinkSpeed": 12,
"packetFilterArp": 0,
   "packetFilterSnmpIpv6": 1,
   "packetFilterSmb": 1,
   "packetFilterPppoe": 0,
   "packetFilterOtherIpv4": 0,
   "packetFilterAllIpv4": 0,
   "packetFilterBootpServer": 1,
   "packetFilterBootpClientIpv6": 1,
   "packetFilterMulticastIpv6": 1,
   "packetFilterAllIpv6Others": 0,
   "packetFilterSnmp": 1,
   "packetFilterSmbIpv6": 1,
   "packetFilterBootpServerIpv6": 1,
   "packetFilterAllIpv6": 0,
   "packetFilterAllOthers": 0,
   "packetFilterBootpClient": 1,
   "packetFilterMulticastIpv4": 1,
   "packetFilterDirection": 1
},
"cfgFileString": "Canopy configuration file",
"cfgFileVersion": "1.0"
}
2 Likes

I have forwarded this to our development team.

1 Like

I am having this same issue, I have upgraded to 16.1 and still same issue.  Was this ever resolved?

1 Like

Hi 360comm

I just validated this in the lab here at Rolling Meadows, it looks like the above jason template code was missing the "userParameters": { section that the SM was checking for, below is the corrected code for applying the filter above.

{
 "userParameters": {
  "networkConfig": {
  "webAutoUpdate": 3,
  "ethernetLinkSpeed": 12,
  "packetFilterArp": 0,
   "packetFilterSnmpIpv6": 1,
   "packetFilterSmb": 1,
   "packetFilterPppoe": 0,
   "packetFilterOtherIpv4": 0,
   "packetFilterAllIpv4": 0,
   "packetFilterBootpServer": 1,
   "packetFilterBootpClientIpv6": 1,
   "packetFilterMulticastIpv6": 1,
   "packetFilterAllIpv6Others": 0,
   "packetFilterSnmp": 1,
   "packetFilterSmbIpv6": 1,
   "packetFilterBootpServerIpv6": 1,
   "packetFilterAllIpv6": 0,
   "packetFilterAllOthers": 0,
   "packetFilterBootpClient": 1,
   "packetFilterMulticastIpv4": 1,
   "packetFilterDirection": 1
  }
},
  "cfgFileString": "Canopy configuration file",
  "cfgFileVersion": "1.0"
}

If the AP/SM parses the json and finds a formatting error or something missing it will not import the file.

A quick test to check to see if the file is correct is to import it directly into a test AP or SM via it's GUI under "Configuration → Unit Settings".

From there you can upload and apply your test json file and validate to make sure the formatting is correct.

In the case of the code that was missing the "userParameters": { section this is what I saw:

With the corrected json this is the output:



I hope this helps.

5 Likes

Thank you

1 Like