There is very limited information in the On Premises User Guide.
For example the actual configurations that are allowed to be used, their naming convention etc? I assume they are taken from the SNMP MIBS? If so that should actually probably be added to the manual. Also a method of acquiring this information or a link to your site that displays the mibs.
I did discover you can pull the config from onboarded devices. But it may not include ALL the configuration options there are available in a radio (via snmp)
For example - do I need to save and edit the entire config? Or can I just take one configuration and push that specifically to one radio?
While already have access to this information some others may not. So a guide as to how to get the information to configure (proper naming convention, maybe a list etc) would be very helpful.
If there is one posted somewhere else (other than the Cambium downloads section) please direct me to it! Thanks!
So I found a couple videos. Oddly enough I've followed this formula by saving existing configs as templates and then just removing the information you don't want to update. I figured this would be the way things would go. I verified my json was correct and even tried it manually with the correct information. Each time I get an error. There is something to the process I am missing. Anyone care to help?
The error on the AP I was trying to update showed this
ection in 5 seconds
11/29/2016 : 13:01:52 UTC : : Configuration file "cns_config.cfg", triggered from CNS-NG server, successfully imported. 12/01/2016 : 10:56:18 UTC : : JSON parse error: Could not find property "cfgFileString" in input 12/01/2016 : 10:56:18 UTC : : Aborting header file import 12/01/2016 : 10:56:18 UTC : : Config import failed 12/01/2016 : 12:17:34 UTC : : Config file: Could not find property "userParameters" 12/01/2016 : 12:17:34 UTC : : Configuration file "cns_config.cfg", triggered from CNS-NG server, failed to import. 12/01/2016 : 12:17:34 UTC : : Config import failed
Now it could be I am missing the userParameters section and there may be a need for a cgfilestring as well. However none of that is mentioned in the docs either. Nor was it shown in the demonstration video.
I took the liberty of downloading and looking at an actual config and it does show those parameters.
So the question is this - when editing a config what are the bare minimum requirements for the config to work on a 450 and or an ePMP?
PMP devices require "cfgFileString" and "cfgFileVersion". There was an update made to automatically insert these parameters for the user before pushing to the device but I don't think it's been deployed yet. Until then you should include them in your templates. Give me a few minutes to check on when the issue was fixed.
I posted a basic guide for configuration templates here. It sounds like you are doing something similar already. The best way to see what is supported by template configuration is to edit a device and export its configuration first. MIB to configuration template correlation depends on the device line. ePMP is close to 1-to-1 in terms of naming and supported parameters but I think there are a couple parameters that are not supported. A good example is action-based OIDs for things like triggering auto-population of the latitude/longitude.
You can take partial configurations out of a full configuration and just push the parameters you want to change. That link above explains how to do that.
You may have seen these already but here are a list of links with information that may be useful to you or others:
I pushed a simple template without "cfgFileString" and "cfgFileVersion" on one of our test servers without issue. Once we update the cloud servers "cfgFileString" and "cfgFileVersion" will no longer be requried in PMP templates. Until then be sure to include those parameters.
We have already included some example templates for both ePMP and PMP platforms as well as wifi platforms under the Configure->Templates section . If you want to make some more specific templates please read the configuration from the device by going to configure->Devices after selecting the particular device and click on view device config.
This can be saved as template and then keep the parameters you need for the template and can remove the other not needed parameters.
Thanks for your replies and help in this matter. I'll take another look at the docs to see if they are newer than what I've read already.
I am on an earlier version of the software and as of the today there were no 450 templates in the system. Only ePMP. So its possible we are discussing things that will be resolved when you release the newer version (today I think?)
I'll give you a quick rundown of what I'm trying to do as simply as possible.
Here is a really simple update to the syslog ip. The JSON is valid but it doesn't actually work.