Deployment Guide

Firmware downgrade considerations
When downgrading from Fabric OS 7.3.0 to any previous version of the operating system, the
following MAPS-related behaviors should be expected:
• When an active Command Processor (CP) is running Fabric OS 7.3.0 or 7.2.0 with MAPS disabled,
and the standby device has an earlier version of Fabric OS, High Availability will be synchronized,
but MAPS will not be allowed to be enabled until the firmware on the standby device is upgraded.
The mapsConfig --enablemaps command fails and an error message is displayed.
• When an active CP is running Fabric OS 7.3.0 or 7.2.0 and MAPS is enabled, but the standby
device is running Fabric OS 7.1.0 or earlier, then High Availability will not be synchronized until the
standby CP is upgraded to Fabric OS 7.3.0 or 7.2.0.
• On devices with a single CP, there is no change in behavior when downgrading to an earlier version
of Fabric OS.
• Downgrading to versions of Fabric OS prior to version 7.3.0 will fail if some features are not
supported in the earlier firmware and their loss could impact MAPS functionality. In this case, MAPS
provides instructions on how to disable these features before firmware downgrade. An example of
this is if either MAPS actions or rules include Fabric Performance Impact monitoring or port
decommissioning. Refer to Port decommissioning and firmware downgrades on page 54 for
additional information.
• Downgrading to versions of Fabric OS prior to version 7.3.0 will trigger a warning message if any
feature is not supported in the earlier firmware and keeping the feature configuration is harmless. In
this case, MAPS provides a warning message similar to the following, but does not block the
downgrade.
WARNING: <A>, <B>, <C> feature(s) is/are enabled. These features are not
available in FOS <a.b.c> release.
Do you want to continue?
Examples of this condition include MAPS having any user-created rules pertaining to monitoring the
following: D_Ports, L2_DEVCNT_PER, LSAN_DEVCNT_PER, ZONE_CFGSZ_PER,
BB_FCR_CNT, or ETH_MGMT_PORT.
• Downgrading to versions of Fabric OS prior to version 7.3.0 is not allowed if the MAPS “Fabric
Performance Impact monitoring” feature is enabled. You must disable FPI using the mapsConfig –
disablefpimon command before starting the firmware downgrade.
Fabric Watch to MAPS migration
Fabric Watch and MAPS cannot coexist on a switch. To use MAPS, you must migrate from Fabric
Watch to MAPS.
On a switch running Fabric OS 7.2.0 or later, or when you upgrade your existing switch to a later
version, Fabric Watch is enabled by default. On an upgraded switch, Fabric Watch continues to
monitor as in Fabric OS 7.1.0 until MAPS is activated.
When you start MAPS for the first time, it can automatically convert the Fabric Watch configurations to
ones that are compatible with MAPS so you do not need to recreate all of the thresholds and rules.
However if you do not make the conversion as part of the initial migration, you will need to configure
the rules manually.
Refer to Enabling MAPS using Fabric Watch rules on page 19 for instructions on starting MAPS
using your existing Fabric Watch rules.
Firmware downgrade considerations
16 Monitoring and Alerting Policy Suite Administrator's Guide
53-1003147-01