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

• When an E_Port or F_Port comes online (PORT_ONLINE), if the resources are available, any flows
specifying that port will be installed in the ASIC and made active. If the resources are not available,
the flow will stay deactivated.
• When an E_Port is changed (EPORT_CHANGE), if the resources are available, any flows specifying
that port will be installed in the ASIC and made active. If the resources are not available (for
example, if there is already a flow using that port), the flow will stay deactivated.
• When an F_Port is changed (FPORT_CHANGE), if the resources are available, any flows specifying
that port will be installed in the ASIC and made active. If the resources are not available (for
example, if there is already a flow using that port), the flow will stay deactivated.
An F_Port trunk has same trunk index for both the master and slave ports (as displayed in the output
for switchshow, below). In order to create the same flow definition on the master and slave ports
when portIdMode is set to “index”, the domain/Index can be obtained by using the porttrunkarea –
show all command (as shown below). If you create a flow using the trunk index, then depending
upon whether the trunk index maps to the master or the slave port the flow may or may not be
installed. If the slave port becomes the master, it will be installed.
switch:admin> switchshow
…
Index Port Address Media Speed State Proto
==================================================
…
4 4 010400 id N8 Online FC F-Port (Trunk master)
4 5 010400 id N8 Online FC F-Port (Trunk port, master is Port 4)
…
switch:admin> porttrunkarea --show all
Port Type State Master TI DI
-------------------------------------
0 -- -- -- 0
1 -- -- -- 1
2 -- -- -- 2
3 -- -- -- 3
4 F-port Master 4 4 4
5 F-port Slave 4 4 5
• If a PID is changed for a WWN flow and the new PID does not match the PID in the flow definition,
the active flow will be uninstalled and then reinstalled with the updated PID in the flow definition.
Firmware upgrade and downgrade considerations
There are no restrictions on upgrading the firmware of a switch that has Flow Vision installed. However,
downgrading the firmware on a switch with Flow Vision installed will fail if any Flow Vision-related
configurations are present on the switch being downgraded. Both user-defined and system-defined
flows support the configuration upload and download procedures.
Flow Vision functionality will not be affected if a switch running Fabric OS 7.3.0 is connected to a switch
running Fabric OS 7.2.x. Connecting to a switch running any version of Fabric OS earlier than 7.2.0 will
disable Flow Vision.
Upgrade considerations
The following items should be taken into consideration when upgrading to Fabric OS 7.3.0:
• When moving a configuration from a switch running Fabric OS 7.2.x to one running 7.3.0, predefined
flows will be included automatically when the older configuration is downloaded to a switch running
Fabric OS 7.3.0, but they will remain deactivated after download.
• If the in-flight encryption and compression functionality is enabled, then any Flow Mirror flow active
before the upgrade will be deactivated after the upgrade and a RASlog entry displayed on the
console.
Firmware upgrade and downgrade considerations
Flow Vision Administrators Guide 31
53-1003168-01