Brocade Fabric OS Administrator's Guide Supporting Fabric OS v6.3.0 (53-1001336-02, November 2009)

70 Fabric OS Administrator’s Guide
53-1001336-02
Multi-service Frame Redirect
4
ordered so that it will be the first redirected device. This option does not guarantee that this
appliance will always be first. If yet another MSFR zone is created afterwards and requests to be
ordered first, then this latest addition will become the first redirected device, displacing the former
to be the second redirected device in the series.
If you have legacy FR zoning defined along with MSFR zoning, then you will see the “traditional” FR
zoning objects coexist with the new MSFR zoning objects in the defined configuration. The legacy
FR zones, the “r_e_d_I_r_c__fg” zone set, and “red_______base” zoning objects will still be
present when older frame redirection configurations are defined.
MSFR policies
There are two policies you can set for each MSFR zone, restartable and nonrestartable. If the
restartable policy is chosen, then when a virtual device fails the original flow should continue. This
policy could be used when migrating data. During data migration if the target is lost, the host will
switch from physical target to virtual target, and a new session is established with the virtual target.
If the nonrestartable policy is specified, then when any of the virtual devices go offline, the physical
devices are also considered offline and no traffic is allowed between the original host and target.
You can specify which policy, if any, to use when creating the MSFR zone or change the policy at a
later time.
This feature requires the Enhanced Frame Redirection license.
Supported Configurations
The following are supported configurations for MSFR:
Brocade 300, 4100, 4900, 5000, 5410, 5424, 5450, 5460, 5470, 5480, 5100, 5300, 5424,
7500, 7500E, 7600, 7800 and 8000 switches, Brocade 48000, DCX and DCX-4S
enterprise-class platforms support this feature.
MSFR is supported with any interopmode.
Frame Redirec zones are supported with any interopmode.
MSFR supports a maximum of seven VI/VT pairs per MSFR service configuration (i.e., seven
services/redirected-devices).
It is important to note that transit switches in the fabric do not have to be MSFR-capable in order to
properly route redirected traffic. So, while Host, Target, VI, and VT must be connected to
MSFR-capable switches, transit switches can be down-level FOS switches or McDATA switches.
Transit switches need not have the MSFR or Frame Redirection zoning information from the defined
zoning configuration.
MSFR Restrictions
The following are restrictions to implementing MSFR in your fabric:
The Host and Target must be connected to MSFR-capable Fabric OS switches.
The Fabric OS director and switch hosting an appliance must be MSFR-capable.
The appliances must be using the new MSFR API to create frame redirection zones for MSFR.
MSFR zone members can be specified by worldwide port name only.
MSFR zones can only be created in AD0.