User guide

17
Release Notes for the CiscoWorks Wireless LAN Solution Engine, Release 2.7.1
OL-6255-01
Known and Resolved Problems
CSCsa15540 Inventory does not start for
partially successful jobs.
When a job is only partially successful, the
inventory cycle does not start up, and the new
information is not be displayed until the next
regularly scheduled inventory.
To work around this problem, create an
on-demand inventory job for the access points
that were successfully upgraded in the partially
successful firmware job.
CSCsa16324 If you run CLI “services status”
on the standby box, the database
failure shows.
After you turn on Redundancy and telnet to the
standby box and run CLI of “services status,”
the failure message should say:
SQL1117N A connection to or activation of
database “WLSEDB” cannot be made
There is no workaround to this problem. You
can ignore this message.
CSCsa20490 Incomplete WDS configuration
causes flood of run now inventory
jobs created.
Before configuring WDS, you must make sure
the APs in your network are discovered and
managed in WLSE. If WLSE is unable to
discover the WDS AP and the WDS AP is
configured with the WLSE server, WLSE
attempts to discover the AP from whom it heard
WDS packets every 30 seconds.
There is no workaround to this problem, except
to ensure the device community strings are
configured correctly.
Table 2 Known Problems in the WLSE (Continued)
Bug ID Summary Explanation