HP StorageWorks Fabric OS 6.x administrator guide (5697-7344, March 2008)
Fabric OS 6.x administrator guide 495
Enabling Brocade Native mode
When you change the mode from McDATA Fabric or McDATA Open Fabric mode to Brocade Native
mode, existing configurations will be erased and the switch must assume the zone configuration from the
fabric it joins or a new configuration must be configured. When you change the switch to Brocade Native
mode, all configuration parameters return to their default states and can be modified using the
configure command. The existing preferred configuration must be changed to a value within the user
Domain ID range specified for the mode before changing to Brocade Native mode is allowed. If the
preferred Domain ID is not in this range, the mode conversion changes the Domain ID to 1.
To enable Brocade Native mode or disable interoperability:
1. Connect to the switch and log in as admin.
2. Enter the switchDisable command to disable the switch.
switch:admin> switchdisable
3. Enter the interopmode 0 command to disable interoperability.
This command resets a number of parameters and disables McDATA Open Fabric
mode or the McDATA Fabric mode.
switch:admin> interopmode 0
Interop mode is disabled
The switch effective configuration will be lost.
The system will reboot to allow the change to take effect.
Do you want to continue? (yes, y, no, n): [no] y
4. The switch reboots automatically after changing the interoperability mode.
5. After removing each switch, wait for a fabric reconfiguration.
6. Repeat this procedure on all Brocade switches in the fabric.
NOTE: McDATA switches cannot talk to switches in Brocade Native mode.
Enabling Fabric OS L2 SANtegrity (Fabric Binding)
SANtegrity is required only in legacy McDATA fabrics running EFCM management software. The support
for SANtegrity in this release is for Fabric Binding. Fabric Binding is required for FICON in mixed fabrics.
Fabric OS 6.0 will run separate fabric security policies that will be analogous to SANtegrity fabric binding.
Interaction between McDATA SANtegrity and Fabric OS security policies is minimized to McDATA
SANtegrity requests initiated by the attached McDATA switch. Brocade security policies do not initiate any
requests or verifications to the McDATA fabric. Downgrading to a Fabric OS version that does not support
SANtegrity interoperability without first disabling Fabric Binding will cause ports to segment upon
subsequent initialization (for example, disable and then enable or add new ISL).
When Fabric Binding is turned on, only the switches that are currently in the fabric are included in the
binding list that is sent out.
Fabric Binding lets you configure a Fabric Binding Membership list that each switch in a fabric can use to
validate between itself and its neighbor. McDATA SANtegrity Fabric Binding uses a list made up of
Domain ID and WWN pairs and implies Insistent Domain IDs. Brocade uses Fabric Data Distribution of
Switch Connection Control policies through a Brocade fabric. Interoperability between mixed fabrics
requires switches to exchange and validate their Fabric Binding Membership list upon bringing up an ISL.
When Fabric Binding is enabled, a Fabric Binding check is performed each time a link is initialized to
ensure that the switches can connect. If this check fails on either switch, the link will be segmented.
EFCM software facilitates the synchronization of the Brocade and McDATA policies and should be used to
configure and enable Fabric Binding in a mixed fabric. Configuration through other management
interfaces requires careful synchronization, and is not recommended.
Fabric Binding is always enabled or disabled on the entire fabric. EFCM allows enabling Fabric Binding
either separately or as part of the Enterprise Fabric mode feature. Enterprise Fabric mode is used for
FICON environments and turns on several features including Fabric Binding.