This chapter provides an overview of the basic configurations that need to be completed before getting started with IOA-specific configurations:
•IP Access Lists
•Zone Default Policy
•Configuring FC-Redirect v2 Mode
•Using FC-Redirect with CFS Regions
SSH needs to be enabled on all the IOA switches for Fabric Manager to provision IOA. By default, the SSH service is enabled with the RSA key.
To enable the SSH service, follow these steps:
switch# config t
Enters configuration mode.
switch(config)# feature ssh
Enables the use of the SSH service.
For more information about the SSH service, refer to the Cisco MDS 9000 Family NX-OS Security Configuration Guide.
CFS must be enabled on the IOA switches as well as those switches of which the hosts and targets are directly connected to. FC-Redirect internally uses CFS to configure the rules for any given flow in the fabric.
To globally enable CFS distribution on a switch, follow these steps:
switch# config t
Enters configuration mode.
switch(config)# cfs distribute
Enables (default) CFS distribution on the switch.
For more information about CFS, refer to the Cisco MDS 9000 Family NX-OS System Management Configuration Guide.
IP Access Lists
Cluster communication requires the use of the Management interface. IP ACL configurations must allow UDP and TCP traffic on ports 9333, 9334, 9335, and 9336.
Zone Default Policy
For FC-Redirect to work correctly, the default zone policy on all the switches in the IOA environment must be configured to deny and the initiator-target pairs must be configured in user-defined zones.
This section includes the following topics:
•FC-Redirect Unsupported Switches
FC-Redirect Unsupported Switches
FC-Redirect is not supported on the following switches, and hence IOA is not supported:
•Cisco MDS 9140 Switch
•Cisco MDS 9134 Switch
•Cisco MDS 9124 Switch
•Cisco MDS 9120 Switch
•Cisco MDS 9020 Switch
FC-Redirect requirements for IOA include the following:
•The MDS switch with the MSM-18/4 Module installed or the 9222i Switch needs to be running Cisco MDS NX-OS Release 4.2(1) or later.
•The targets must be connected to a FC-Redirect-capable switch running Cisco MDS NX-OS Release 4.2(1) or later. The hosts must be connected to a FC-Redirect-capable switch running Cisco MDS SAN-OS Release 3.3(1c) or later.
•32 targets per MSM-18/4 Module can be FC-Redirected.
•In FC-Redirect v2 mode, up to 128 hosts per target are supported. If you do not enable FC-Redirect v2, this is limited to 16 hosts per target.
•CFS is enabled by default. Ensure that the CFS is enabled on the switches that have the host and the target connected. Also ensure that the CFS is not disabled on switches that are part of the IOA cluster.
•Advanced zoning capabilities like quality of service (QoS), logical unit number (LUN) zoning, and read-only LUNs must not be used for FC-Redirect hosts and targets.
Configuring FC-Redirect v2 Mode
To enable the v2 mode in FC-Redirect, use the fc-redirect version2 enable command in configuration mode. To disable the v2 mode in FC-Redirect, use the no form of the command.
This command is used to increase scalability of FC-Redirect. Disabling v2 mode after it is enabled in the fabric is not recommended. However, if you want to disable v2 mode, you cannot disable it until all FC-Redirect configurations are deleted. FC-Redirect configurations can be deleted only by deleting all corresponding application configurations.
The MDS switches not running Cisco NX-OS 3.3(1c) and later cannot be added to the fabric after the v2 mode is enabled. If the switches are added, all further FC-Redirect configuration changes will fail across the fabric. This could lead to traffic disruption for applications such as IOA, SME, and DMM.
Use the show fc-redirect configs command to see the list of applications that create FC-Redirect configurations.
If v2 mode is enabled in the fabric and you want to move a switch to a different fabric, use the clear fc-redirect decommission-switch command before moving the switch to a different fabric. If the mode is not enabled, all switches in the new fabric will be converted to v2 mode automatically.
Note Ensure that there are no fabric changes or upgrades in progress. . For more information see "Software Requirements" section on page 1-5. Use the show fc-redirect peer-switches command (UP state) to see all the switches in the fabric
To enable v2 mode in FC-Redirect, follow these steps:
Step 1 Enter the following command:
switch# fc-redirect version2 enable
Step 2 Enter yes.
Please make sure to read and understand the following implications
before proceeding further:
1) This is a Fabric wide configuration. All the switches in the
fabric will be configured in Version2 mode.Any new switches
added to the fabric will automatically be configured in version2
2) SanOS 3.2.x switches CANNOT be added to the Fabric after Version2
mode is enabled. If any 3.2.x switch is added when Version2 mode
is enabled, all further FC-Redirect Configuration changes will Fail
across the fabric. This could lead to traffic disruption for
3) If enabled, Version2 mode CANNOT be disabled till all FC-Redirect
configurations are deleted. FC-Redirect configurations can be
deleted ONLY after all the relevant application configurations
are deleted. Please use the command 'show fc-redirect configs'
to see the list of applications that created FC-Redirect
4) 'write erase' will NOT disable this command. After 'write erase'
on ANY switch in the fabric, the user needs to do:
'clear fc-redirect decommission-switch'
on that that switch. Without that, if the user moves the switch
to a different fabric it will try to convert all the switches
in the fabric to Version2 mode automatically. This might lead
to Error conditions and hence Traffic disruption.
Do you want to continue? (Yes/No) [No]Yes
Step 3 Enter yes.
Before proceeding further, please check the following:
1) All the switches in the fabric are seen in the output of
'show fc-redirect peer-switches' command and are in 'UP' state.
2) All switches in the fabric are running SanOS version 3.3.x or
3) Please make sure the Fabric is stable ie.,
No fabric changes/upgrades in progress
Do you want to continue? (Yes/No) [No] Yes
Using FC-Redirect with CFS Regions
The FC-Redirect feature uses Cisco Fabric Services (CFS) regions to distribute the FC-Redirect configuration. By default, the configuration is propagated to all FC-Redirect-capable switches in the fabric. CFS regions can be used to restrict the distribution of the FC-Redirect configuration.
Note Using FC Redirect with CFS regions is an optional configuration only if the number of switches in the SAN exceeds the scalability limit supported by IOA. As of MDS NX-OS Release 4.2(1), the number of switches supported in a fabric is 34.
To learn more about CFS regions, refer to the Cisco MDS 9000 Family NX-OS System Management Configuration Guide.
Guidelines for Designing CFS Regions For FC-Redirect
To design CFS regions for FC-Redirect, follow these guidelines:
•Ensure that the CFS region configuration for FC-Redirect can be applied to all FC-Redirect-based applications. The applications include Cisco SME, Cisco DMM, Cisco IOA, and any future applications.
•Ensure that all FC-Redirect-capable switches, that are connected to the hosts, targets, and the application switches (switches with MSM-18/4 modules in a cluster), are configured in the same region.
•All switches in the region must have a common VSAN.
•For existing IOA installations, refer to "Configuring CFS Regions For FC-Redirect" section for steps on migrating to CFS regions.
•Remove all instances of the previous configurations when a switch is moved to a region or moved out of a region.
Configuring CFS Regions For FC-Redirect
To configure the CFS regions for FC-Redirect, do the following tasks:
Step 1 Configure a switch in the CFS region as shown in the following example:
Repeat this step for all the switches that are included in the specified region.
Step 2 Confirm that all the required switches are available in the CFS region by entering the show fc-redirect peer-switches command.
Step 3 To migrate existing Cisco IOA installations to CFS regions for FC-Redirect, delete all the existing FC-Redirect configurations created by the switches in other regions from each switch. To remove the configurations, perform the following steps:
a. Obtain a list of all FC-Redirect configurations by entering the show fc-redirect configs command.
b. Remove all configurations created by the switches in other regions by using the clear fc-redirect configs command. The configurations are removed from the switches but the switches remain active in the region in which they are created.