1) Relative to version 2.5.1, this version has significant improvements in the management protocol between the ePMP device and cnMaestro.
2) This version fixes a bug that prohibited cnMaestro from completing software upgrades of ePMP devices that used non-default SNMP community strings (public/private). (Note, in order to upgrade to this version of software, using cnMaestro, your devices will need to have the default community string. Once the devices are upgraded to 2.5.2-RC9, they can use non-default SNMP community strings and future upgrades will work properly from cnMaestro.)
Other than the critical improvement mentioned above, this software version does not introduce any new ePMP features and has a few other minor bug fixes.
Still seeing an issue when attempting to update some of our AP's / SM's on our network with the new rc9. Tried rebooting the device first as well but same result.
Nov 20 11:27:33 AP-NAME DEVICE-AGENT[1946]: platform_sw_update: ENTRY
Nov 20 11:27:59 AP-NAME DEVICE-AGENT[10595]: do_sw_update2: Exited while loop sw_upd state=0
Still seeing an issue when attempting to update some of our AP's / SM's on our network with the new rc9. Tried rebooting the device first as well but same result.
Nov 20 11:27:33 AP-NAME DEVICE-AGENT[1946]: platform_sw_update: ENTRY
Nov 20 11:27:59 AP-NAME DEVICE-AGENT[10595]: do_sw_update2: Exited while loop sw_upd state=0
Can you clarify if the devices that are failing the upgrade are using non-default SNMP community strings ?
Yes, we are using custom snmp community strings on all our devices. I went ahead and tried setting them back to the defaults of public/private and re-attempted the 2.5.2-RC9, and it did successfully take the update after the change. So it seems that 2.5.2-RC9 is still having issues with non-standard snmp community values.
For an additional data point, only the read-write community name needs to be changed to 'private' for the upgrade to work, the read only string can stay at it's custom value.
Yes, we are using custom snmp community strings on all our devices. I went ahead and tried setting them back to the defaults of public/private and re-attempted the 2.5.2-RC9, and it did successfully take the update after the change. So it seems that 2.5.2-RC9 is still having issues with non-standard snmp community values.
The bug has been fixed starting with 2.5.2-RC9. But in order to benefit from the "fix", the device has to first have 2.5.2-RC9. The expectation is that the SNMP issue has been fixed if cnMaestro initiates a software upgrade on a device that is already running 2.52.-RC9 (or later).
To validate the issue has been resovled for your setup, you can do the following.
1) Set device SNMP community string to default (public/private).
2) Upgrade to 2.5.2-RC9
3) Set device SNMP community string to non-default values.
4) Downgrade to 2.5.2-RC6.
The following should complete successfully and validates that the SNMP issue has been if cnMaestro initiates a software upgrade with 2.52.-RC9 (or later).
Unfortunately, now that the devcice has 2.5.2-RC6, you will need to set the default SNMP community string on the device in upgrade back to 2.5.2-RC9.