The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides an overview of the basic configurations that need to be completed before getting started with IOA-specific configurations:
SSH needs to be enabled on all the IOA switches for Cisco DCNM-SAN to provision IOA. By default, the SSH service is enabled with the RSA key.
To enable the SSH service, follow these steps:
|
|
|
---|---|---|
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:
|
|
|
---|---|---|
For more information about CFS, refer to the Cisco MDS 9000 Family NX-OS System Management Configuration Guide.
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.
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:
IOA does not support any FCoE connected devices including devices connected through the MDS FCoE linecard (DX-X9708-K9).
In Cisco MDS NX-OS Release 5.2(x), you cannot install a FCoE module in a switch that is running DMM, SME, or IOA.
FC-Redirect is not supported on the following switches, which also means that IOA is not supported:
FC-Redirect requirements for IOA include the following:
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. 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:
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.
To design CFS regions for FC-Redirect, follow these guidelines:
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.
Internet protocol over Fibre Channel (IPFC) provides IP forwarding or in-band switch management over a Fibre Channel interface (instead of management using the Gigabit Ethernet mgmt 0 interface). You can use IPFC to specify that IP frames be transported over Fibre Channel using encapsulation techniques. IP frames are encapsulated into Fibre Channel frames so that cluster management information can transmit across the Fibre Channel network without using an overlay Ethernet network.
When an IOA cluster communicates via the IPFC interface, the cluster management messages can be sent and received on Fibre Channel ISLs by encapsulating cluster management messages in Fibre Channel frames instead of using the management interface.
Note Configuring IOA cluster with the IPFC interface is optional and is supported in Cisco MDS NX-OS Release 5.0(4c) or later. Support for GUI for configuring IOA cluster with the IPFC interface might be added in the future releases.
Note You must configure the nodes in an IOA cluster either to use an IPFC interface or a management interface. We do not recommend using the combination of two interface configurations.
To configure IOA cluster using the IPFC interface, follow these steps:
Step 1 Create an IPFC interface.
a. Create a VSAN to use for in-band management.
b. Configure an IPv4 address and subnet mask for the VSAN interface.
Step 3 Change the local node to use IPFC interface’s IPv4 address.
Step 4 Add the IOA interfaces to the cluster.
Step 5 Add the remote node with IPFC interface IPv4 address.
Step 6 Add the IOA interface of the remote cluster.
The process of configuring an IOA cluster to use the IPFC interface involves a number of configuration tasks that should be completed in the following order:
The first step in the process of configuring an IOA cluster to use the IPFC interface is to create a VSAN interface and configure IPv4 addresses.
To create an interface VSAN, perform this task:
|
|
|
---|---|---|
Configures the IPV4 address and netmask for the selected interface. |
||
After creating the VSAN and configuring the IPv4 address, use the show interface vsan command to verify the configuration:
To enable IPv4 routing, perform this task:
|
|
|
---|---|---|
After enabling IPv4 routing, use the show ip routing to verify the configuration.
To verify the connectivity, use the show ip route and ping commands.
To create an IOA cluster and IOA interface in the local node, perform this task:
|
|
|
---|---|---|
Switch(config-ioa-cl)# node switchname/ip address ip-address 10.1.1.1 |
Adds or changes the node address from the mgmt0 address to the IPFC interface address. |
|
To configure an IOA cluster, you can use the name of the switch if the network supports DNS service. The IOA cluster requires switch name to IP address resolution.
To verify the cluster configuration, use the show ioa cluster name node summary command.
To verify the IP address of the node, use the show ioa cluster name node command.
To add a remote node, perform this task:
|
|
|
---|---|---|
Switch(config-ioa-cl)# node <switchname/ip address> ip-address 10.1.1.2 |
Adds remote node to the cluster with the IPFC interface address. |
|
To verify the node configuration, use the show ioa cluster name node summary command:
To verify the IP address of the node, use the show ioa cluster name node command:
To see all of the configured interfaces in the IOA cluster, use the show ioa cluster name interface summary command:
This section includes an example for creating an IOA cluster using IPFC interface. Figure 2-1 illustrates the IOA cluster configuration used in this example. The sample topology shows the FC ISL between sw-231-14 and sw-231-19 switches.
Figure 2-1 Configuration Example
The following example creates an interface VSAN and configures IP address on sw-231-14 and enables IP routing:
The following example creates an interface VSAN and configure IP address on sw-231-19 and enables IP routing.
The following example verifies the configuration of sw-231-14 using the show interface command.
The following example verifies the configuration of sw-231-19 using the show interface command:
The following example verifies the connectivity using the ping command:
The following example configures IOA site on switch sw-231-14:
The following example configures IOA site on switch sw-231-19:
The following example configures IOA cluster ctrl1 on switch sw-231-14:
The following example forces the node to use IPFC interface addresss:
The following example adds a remote node to an IOA cluster:
The following example adds an IOA interfaces on the switch sw-231-14:
The following example adds an IOA interface on the switch sw-231-19:
The following example verifies the cluster configuration using the show cluster name node summary command:
The following example verifies the IP address that is configured on the switch using the show ioa cluster cluster name node command:
The following example verifies the IOA interface that is configured on the switch using the show ioa cluster cluster name interface summary command:
To convert an existing IOA cluster to use the IPFC Interface, follow these steps:
This example for converting an IOA cluster to use the IPFC interface has the following steps:
The following example verifies the IOA cluster configuration that is configured on the switch using show ioa cluster cluster name node summary command:
The following example verifies the IP address that is configured on the switch using the show ioa cluster cluster name node command:
The following example verifies the status of the flows using the show ioa cluster cluster name flows command. The nodes in this example are using mgmt0 interface address.
The following example shuts down the IOA cluster on a local node using shut down command:
The following example shuts down the IOA cluster on the remote node using the shut down command:
The following example removes the IOA cluster from the remote node using the no ioa cluster cluster name command:
Note In case of removal of IOA cluster from the master node, clear all the FC-redirect configurations from the fabric, refer to “Configuring CFS Regions For FC-Redirect”.
The following example verifies the absence of the IOA cluster on the remote node using the show ioa cluster cluster name command:
The following example removes the remote node from the cluster in the local switch:
The following example changes the local node to use the IPFC address:
The following example activates the single node cluster:
The following example adds a remote node with IPFC address:
The following example adds the IOA interfaces to the remote node:
The following example verifies the status of the IOA clusters using the show ioa cluster cluster name node summary command:
The following example verifies the status of the IOA clusters using the show ioa cluster cluster name flows command: