cnMaestro version updated – Issues and work-arounds

A software upgrade to cnMaestro was executed earlier today. After that, some customers have noticed one or several of the following issues.

Problem logging into cnMaestro

If this occurred, the user was presented with a message stating “Error Occurred”. (See attached screenshot.) In this case, please try clearing the browser cache (clear cookies and possibly history). Then restart the browser. This has resolved the issue for all the scenarios we have seen. (There may be an additional issue with Internet Explorer. For the time being, other browsers, such as Firefox or Chrome are recommended.)

Some devices appear DOWN in cnMaestro

A few devices may appear to be down in cnMaestro even though the devices have network connectivity. In this case, clicking on the device in the tree and viewing it’s dashboard will force the device dashboard to update to the correct status (“UP” assuming the device is truly connected.). Afterwards, click the REFRESH icon of any related parents in tree (or just click refresh of the SYSTEM element in the tree). At this point the tree will show the correct status as well, UP.

Active Alarm indicating “Device is Offline” despite device status “Up” (connected)

In this scenario, a device may show as UP in the device tree and in the device dashboard. Yet, there may be an active alarm incorrectly indicating the device is offline (not connected to cnMaestro).

To correct this condition, the device must be forced to lose and re-establish network connectivity to cnMaestro. This can be accomplished either by deregistering ePMP SMs from their APs, rebooting the device, disabling/re-enabling the devices device manager, etc.


For ePMP devices, it is strongly recommended to upgrade from 2.5.1 to 2.5.2. There are improvements specifically targeted to the cnMaestro management of the devices.  Note that although this release resolves issues associated with performing cnMaestro software upgrades on devices using non-deault SNMP community strings, devices that are still running 2.5.1 will experience this problem.  In this case, either change the ePMP community string to default values, "public"/"private" or use an alternate method to upgrade to ePMP from 2.5.1 to 2.5.2.  Once upgraded to 2.5.2, the non-default values will no longer pose a problem for cnMaestro software upgrades.