Guidelines For Using Msp With Fusion; Persistence Differences Between Fusion X2 And Previous Versions Of Fusion - Motorola SB1 Integrator Manual

Guidelines for Using MSP with Fusion

The SB1 supports the latest version of Fusion, Fusion X2.xx. WLAN Settings to configure Fusion can be
created using prior MSP Settings Classes, such as Network.WLAN.FusionPublic and
Network.WLAN.Fusion30Public. In addition, to support the full capabilities of Fusion X2, the new MSP Settings
Class Network.WLAN.FusionX2Public is also supported.
If only SB1s are being managed, the Network.WLAN.FusionX2Public MSP Settings Class provides the best
experience since it is tailored to use the capabilities of Fusion X2. Similarly, if a mixed population of Motorola
Solutions devices that all support Fusion X2 are managed, the Network.WLAN.FusionX2Public MSP Settings
Class is the preferred choice. In cases where a mixed population of SB1s and older devices, which do not
support Fusion X2, are used, it may be preferable to use an older MSP Settings Class so a single Settings
Object can target a wider number of devices.
When using an older MSP Settings Class, the capabilities supported by the Settings Class may not exactly
match the capabilities of all devices with which it is compatible. Backward compatibility means that each SB1
that can accept Settings Objects created using a given MSP Settings Class supports as much WLAN
functionality as it can based on the version of Fusion and the WLAN hardware present on the SB1. Certain
features that can be selected in a Settings Object created via such a MSP Settings Class might not be
supported on every device that can accept and process Settings Objects of that MSP Settings Class. It is
important to carefully test a representative sample of each type of device to ensure that a Settings Object
achieves the desired result when sent to a mixed population of devices.

Persistence Differences Between Fusion X2 and Previous Versions of Fusion

Fusion on the SB1 implements persistence as a standard feature. When configuring Fusion, the settings are
automatically stored persistently in a database contained within the SB1. On all subsequent cold boots, the
configuration stored in the database is automatically reapplied. There is no way to turn off the automatic
persistence, but there is a way to reset Fusion back to its default state. See
more information.
This persistence behavior is different from all prior versions of Fusion that did not automatically store Fusion
Settings persistently. This difference has the following important implications when MSP is used to configure
Fusion on the SB1.
All Fusion settings that are applied directly as part of a Staging Profile (not in a bundle) are automatically
•
persisted by Fusion even though they are not explicitly persisted by MSP.
• This produces different behavior from that seen on devices with older versions of Fusion. In particular,
WLAN Settings that were previously transient (i.e. intentionally did not persist across subsequent cold
boots) are persistent (i.e. are persist across subsequent cold boots). This could lead to confusion,
especially in mixed populations of devices.
• Fusion settings that are applied persistently, as part of a bundle, are persisted both by Fusion and
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, WLAN Settings are
unnecessarily reapplied by MSP and this could increase the time it takes for the WLAN to become
usable after subsequent cold boots.
• Choosing the "Disable all other profiles:" in a Settings Object causes all other WLAN Profiles, aside
from the one being defined in that Settings Object, to be disabled. When using Fusion, the WLAN
Profiles are persisted and the disabling of such WLAN Profiles are persisted. The result is
approximately equivalent to that produced by older versions of Fusion, since only the WLAN Profile
defined by the Settings Object will be enabled and is used after subsequent cold boots. One
difference is that on Fusion X2, all defined WLAN Profiles will persist (albeit disabled) across
subsequent cold boots and hence could be re-enabled, whereas in older versions of Fusion, those
WLAN Profiles would not persist across subsequent Cold Boots.
Wireless Settings 3 - 21
Factory Defaults on page 3-16
for