Motorola SB1, Руководство интегратора

Страница: 58 / 136

3 - 22 SB1 Integrator Guide
•
Fusion Settings that are applied persistently, as part of WLAN Settings Object in a bundle, can still be
uninstalled. But since the configuration performed by the WLAN Settings Object is not removed from the
Fusion persistence database, such configuration continues to persist across subsequent cold boots.
•
When using previous versions of Fusion, a WLAN Settings Object could be removed, thus causing the
configuration it performed to stop persisting across subsequent cold boots. This is no longer possible
with Fusion X2.
•
While a means is provided via the
Wireless Settings
to reset the persistence database, no means is
provided to initiate such a reset from MSP.
•
If the WLAN settings that are applied to configure Fusion reference any Certificates (e.g. for EAP-TLS),
then Fusion automatically persists those certificates in its persistence database along with the rest of the
Fusion configuration.
•
This ensures that everything needed to maintain WLAN connectivity persists across subsequent cold
boots.
•
This produces different behavior from that seen on devices with older versions of Fusion. In particular,
certificates that were previously transient (i.e. intentionally did not persist across subsequent cold
boots) are be persistent (i.e. are persist across subsequent cold boots). This could lead to confusion,
especially in mixed populations of devices.
•
Certificates that are installed persistently, as part of a Certificate Settings Object in a bundle, are
persisted both by Fusion X2 and by MSP. While this does not result in a change of behavior,
compared to older versions of Fusion, it could lead to less than optimal results. In particular, on
devices with Fusion X2, Certificates are unnecessarily reinstalled by MSP and this could increase the
time it takes for the WLAN to become usable after subsequent cold boots.
•
Certificates that are installed persistently, as part of a Certificate Settings Object in a bundle, can be
uninstalled. But since certificates are not removed from the Fusion persistence database, they continue
to persist across subsequent cold boots.
•
When using prior versions of Fusion, a Certificate Settings Object could be removed, thus causing the
certificates it installed to stop persisting across subsequent cold boots. This is no longer possible with
Fusion X2.
•
While it is possible to reset the persistence database using
Wireless Settings
, it is not possible to
reset the persistence database from MSP.