The development team have coded two options to capture the radios current configuration, they both produce a text based output which can be compared by another application or compare tool to detect configuration changes and for version control. We do have new traps in 4.5.x that alert if a setting has been changed should you require that level or change detection, otherwise the show run commands do provide a way to compare.
show run all
Produces a text output of all of the configuration points and shows a “default value” for each.
show run changes
Shows any setting that has a value different from the default and is an easier way to see items that need changing to configure a spare radio for example.
Note: The default values are not settings that GRE have set during production they are values Development have selected to build a radio from scratch and are applicable for all frequency options, effectively defaults that will let a radio startup and allow configuration.
It is worth running the commands to save as factory database on each radio should you want a restore point on them after deployment. This will save the site specific settings to the radio.
configure database factory save
At present there is only one way to capture a backup from the units that can be uploaded back to the device and that is by using the CCMS and downloading the Configuration Database files. The text from either show command can not be pasted back into a radio, like a Cisco switch or router can. Our CLI is not ready to do that yet, I believe there is a roadmap to do so.