Brocade Flow Vision Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 32)

Downgrade considerations
The following items should be taken into consideration when downgrading to a version of Fabric OS
earlier than 7.3.0:
• All Flow Vision-related flows or simulation ports must be deleted prior to performing a downgrade to
any version of Fabric OS prior to version 7.2.0; if they are not, the downgrade will be blocked and a
warning message displayed.
• Flow counts that exceed the supported scalability limits will not be replayed when downgraded or
failed over to a version of Fabric OS earlier than 7.3.0.
• Predefined flows will not be replayed, and flow definitions for newly introduced features will not be
replayed from the flow configuration.
• Downgrading from Fabric OS 7.3.0 is not allowed if a Flow Mirror flow is active for local flow
mirroring (LFM). You must first deactivate any active flow that is using a local mirror port.
• Flows that were created with the following keyword combinations are automatically deactivated.
‐ -bidir and -frametype
‐ -ingrport and -frametype
• Flows created using learning on E_Ports and EX_Ports will not be replayed after the downgrade.
• Flows created using monitor support on XISL ports will not be replayed after the downgrade.
• Flows will be deleted from memory configuration when firmware is downgraded.
High Availability and Flow Vision
High Availability (HA) preserves only the Flow Vision configuration settings through an HA failover, HA
reboot, or a power cycle and reboot. It does not save feature-related data (for example, statistics).
User-defined or system-defined (predefined) flows will not be restored if failed over to an earlier
version of Fabric OS.
If a standby command processor (CP) with a downgrade revision code comes online and any flows
(active or non-active) are configured, the HA will be out of sync. If a standby CP with a downgrade
revision code comes online and no flows (active or non-active) are configured, HA will be in sync but
flow creation will fail.
Refer to the following sections for information on how each feature is treated under HA:
• Flow Monitor and High Availability on page 57
• Flow Generator and High Availability on page 73
• Flow Mirror and High Availability on page 90
Flow Vision integration with MAPS
Statistics generated using Flow Vision can be monitored with the Monitoring and Alerting Policy Suite
(MAPS) threshold service.
Refer to the individual features for information on how that feature interacts with MAPS, and the
Monitoring and Alerting Policy Suite Administrator's Guide for more details on MAPS in general.
High Availability and Flow Vision
32 Flow Vision Administrators Guide
53-1003168-01