Cisco SFS InfiniBand Redundancy Configuration Guide, Release 2.10 - Fibre Channel Gateway and SRP Redundancies [Cisco SFS 3500 Series Multifabric Server Switches]

Table Of Contents

Fibre Channel Gateway and SRP Redundancies

Dynamic Load Balancing

Dynamic Gateway Failover

Path Affinity

Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3504 Server Switch

Verifying Configured Initiator

Verifying IT

Verifying LU

Configuring Fibre Channel Gateway Redundancy Using the Cisco SFS 3012R Server Switch

Configuring Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012 Server Switch

Verifying Configuration for a Single Cisco SFS 3012R Server Switch

Configuring Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches

Verifying Configuration for Two Cisco SFS 3012R Server Switches

Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3001 Server Switch

Configuring Two Cisco SFS 3001 Server Switches

Verifying Redundancy Configuration for Cisco SFS 3001 Server Switches

Fibre Channel Gateway and SRP Redundancies

This chapter describes Fibre Channel gateway redundancies and includes the following sections:

•Dynamic Load Balancing

•Dynamic Gateway Failover

•Path Affinity

•Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3504 Server Switch

•Configuring Fibre Channel Gateway Redundancy Using the Cisco SFS 3012R Server Switch

•Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3001 Server Switch

Note For expansions of acronyms and abbreviations used in this publication, see "Acronyms and Abbreviations."

Fibre Channel gateway redundancy is based on the concept of using all available paths if the configured policy allows for it. Each ITL has a redundancy policy set and the gateway paths are used according to those policies. Access to the available paths can either be granted or denied. The connection manager that is resident on the controller determines the path of the Initiator/Target.

A logical diagram of Fibre Channel gateways in a redundant configuration is shown in Figure 8-1.

Figure 8-1 Logical Diagram of Fibre Channel Gateways in a Redundant Configuration

The examples in the next sections show the most popular deployment of different types of I/O chassis.

The following features enable Fibre Channel gateways to support redundancy and high availability:

•Dynamic Load Balancing

•Dynamic Gateway Failover

•Path Affinity

Dynamic Load Balancing

These features work within a chassis for the Cisco SFS 3504, SFS 3012R, and SFS 3001 Server Switches. Dynamic load balancing automatically distributes traffic from a host to a target evenly across all available paths and thus provides increased availability. It prevents against single points of failure or performance bottlenecks.

Dynamic Gateway Failover

This feature is supported by the Cisco SFS 3504, SFS 3012R, and SFS 3001 Server Switches. Dynamic gateway failover enables available gateways to assume the traffic of gateways that fail by having one or more redundant gateways available that are ready to provide service. Fibre Channel gateways support greater granular high availability at the port level and thereby ensure load balancing is utilized most efficiently.

Path Affinity

This feature is supported by the SFS 3012R and the Cisco SFS 3001 Server Switches. Path affinity compensates for the lack of load balancing capabilities of the storage systems, including the storage systems for which multiple paths are available. When multiple I/Os are initiated to a storage system with a queue depth that is greater than one, the host has an affinity to the path that was selected and the I/Os are transmitted on that path until I/O count to that host reaches zero. The next set of I/Os can have a different path affinity. Therefore, at any given time, there is only one path in use, although multiple paths are available. However, each time the path could be different. This is different from port failover, where only one path is used until the path no longer exists.

Note The Cisco SFS 3504 Server Switch does not support path affinity.

Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3504 Server Switch

This section describes how to configure Fibre Channel gateway redundancy for the Cisco SFS 3504 chassis and includes the following topics:

•Verifying Configured Initiator

•Verifying IT

•Verifying LU

Two or more Cisco SFS 3504 Server Switches must be used to provide high availability redundancy. A very typical deployment would consist of two Cisco SFS 3504 Server Switches with two Fibre Channel gateways in each (see Figure 8-2).

The Product ID number for the Fibre Channel gateway card is SFS-3500-FCGW-4G. Each Fibre Channel gateway card is a 4-port, 4 Gbps per-port capable InfiniBand-to-Fibre Channel gateway module.

The Cisco SFS 3504 Server Switches support VSANs. For more details about VSANs, see the Cisco SFS InfiniBand Software Configuration Guide and the Cisco SFS Product Family Command Reference.

Figure 8-2 Fibre Channel Redundancy with Dual Cisco SFS 3504 Server Switches

To configure the first Cisco SFS 3504 Server Switch, perform the following steps:

Step 1 Enter configuration mode.

The following example shows how to enter configuration mode:
SFS-3504> enable
SFS-3504# config
Step 2 Configure the initiator.

The following example shows how to configure the initiator:
SFS-3504(config)# fc srp initiator
initiator           initiator-wwpn
SFS-3504(config)# fc srp initiator 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 wwnn ?
 <wwnn>            - Initiator wwnn
suggested wwnn = 20:08:00:1b:0d:00:12:00
SFS-3504(config)# fc srp initiator 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 wwnn 
20:08:00:1b:0d:00:12:00
SFS-3504(config)#
SFS-3504(config)# fc srp initiator-wwpn 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 
3/1 ?
<wwpn>                - wwpn
suggested wwpn = 20:08:00:1b:0d:00:12:16
SFS-3504(config)# fc srp initiator-wwpn 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 
3/1 20:08:00:1b:0d:00:12:16 vsan 20
SFS-3504(config)#
Step 3 Apply port masking.

The following example shows how to apply port masking:
SFS-3504(config)# no fc srp it  00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 
20:01:00:20:c2:03:31:99 gateway-portmask-policy restricted 3/1-3/4
Step 4 Discover the LUNs.

The following example shows how to discover the LUNs:
SFS-3504(config)# fc srp initiator 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 
discover-itl
Step 5 Set the logical unit policy to load balancing, failover, or path-affinity.

The following example shows how to set the logical unit policy to load balancing:
SFS-3504(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing
SFS-3504(config)# exit
To configure the second Cisco SFS 3504 Server Switch, perform Step 1 to Step 5 on the switch.

Verifying Configured Initiator

The following is sample output from the show fc srp initiator command that shows how to verify the configured initiator for the first Cisco SFS 3504 Server Switch:
SFS-3504# show fc srp initiator 
================================================================================
                                 SRP Initiators
================================================================================
                     guid: 00:05:ad:00:00:00:22:3c
                extension: 00:00:00:00:00:00:00:00
              description: svbu-fc-host-12
                     wwnn: 20:08:00:1b:0d:00:12:00
                   credit: 0
             active-ports: none
                    pkeys:
            bootup-target: 00:00:00:00:00:00:00:00
                bootup-lu: 00:00:00:00:00:00:00:00
        alt-bootup-target: 00:00:00:00:00:00:00:00
            alt-bootup-lu: 00:00:00:00:00:00:00:00
                   action: none
                   result: none
                    wwpns: port    wwpn                     fc-addr        vsan
                            3/1    20:08:00:1b:0d:00:12:16  14:01:01         20
                            3/2    20:08:00:1b:0d:00:12:16  14:04:01         20
                            3/3    20:08:00:1b:0d:00:12:16  14:04:01         20
                            3/4    20:08:00:1b:0d:00:12:16  14:04:01         20
To verify the configured initiator for the second Cisco SFS 3504 Server Switch, use the command after 
configuring the switch.
Verifying IT

The following is sample output from the show fc srp it command that shows how to verify IT for the first Cisco SFS 3504 Server Switch:

SFS-3504# show fc srp it 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 20:01:00:20:c2:03:31:99

================================================================================

SRP IT

================================================================================

guid: 00:05:ad:00:00:00:22:3c

extension: 00:00:00:00:00:00:00:00

target-wwpn: 20:01:00:20:c2:03:31:99

description: it

non-restricted-ports: 3/1-3/4

active-ports: 3/1

physical-access: 3/1

mode: normal-mode

action: none

result: none

To verify the IT for the second Cisco SFS 3504 Server Switch, use the command after configuring the switch.

Verifying LU

The following is sample output from the show fc srp itl command that shows how to verify LU for the first Cisco SFS 3504 Server Switch:
SFS-3504# show fc srp itl 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 
20:01:00:20:c2:03:31:99 00:00:00:00:00:00:00:00
================================================================================
                                    SRP ITL
================================================================================
                                    guid: 00:05:ad:00:00:00:22:3c
                               extension: 00:00:00:00:00:00:00:00
                             target-wwpn: 20:01:00:20:c2:03:31:99
                                fc-lunid: 00:00:00:00:00:00:00:00
                               srp-lunid: 00:00:00:00:00:00:00:00
               logical-id (raw 64 bytes): 02:01:00:22:54:4d:53:20:20:20:20:20:46:43:36:35
                                        : 20:20:20:20:20:20:20:20:20:20:20:20:30:33:33:31
                                        : 39:39:30:30:30:30:00:00:00:00:00:00:00:00:00:00
                                        : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          logical-id (formatted display): TMS     FC65            0331990000
                             description: itl
                         device-category: random
                              lun-policy: restricted
                    non-restricted-ports: 3/1-3/4
                            active-ports: none
                         physical-access: none
                                 hi-mark: 16
                               max-retry: 5
                          min-io-timeout: 10
                   dynamic-path-affinity: false
      dynamic-gateway-port-loadbalancing: true
      dynamic-storage-port-loadbalancing:
           dynamic-gateway-port-failover: false
           dynamic-storage-port-failover:
                            active-slots: none
Configuring Fibre Channel Gateway Redundancy Using the Cisco SFS 3012R Server Switch

This section describes how to configure Fibre Channel gateway redundancy using the Cisco SFS 3012R Server Switch and includes the following topics:

•Configuring Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012 Server Switch

•Verifying Configuration for a Single Cisco SFS 3012R Server Switch

•Configuring Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches

•Verifying Configuration for Two Cisco SFS 3012R Server Switches

The Cisco SFS 3012R Server Switch has various redundancies built into the chassis. It has twelve gateway slots, two controller modules, and two switch cards. Each gateway is connected to both switch cards through the backplane. A single Cisco SFS 3012R Server Switch is therefore capable of being configured for high availability.

For more information about this product, see "Cisco SFS 3504 and Cisco SFS 3000 Series Server Switch Redundancy."

Configuring Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012 Server Switch

This section describes how to configure Fibre Channel gateway redundancy using a single Cisco SFS 3012R Server Switch.

The example in this section shows a typical single-switch configuration with four Fibre Channel gateways and two switch cards. Two of the gateways, slots 2 and 4, are configured to use switch cards in the first slot and the other two gateways, slots 3 and 5, are configured to use switch cards in the next slot. (For information about the location of the slot numbers, see Figure 4-4.) Thus if any of the switch cards fail, two gateways continue to remain operational. If the Fibre Channel ports of the gateways are required to be connected to two different Fibre Channel switches, connect the gateways to the same IB switch card that are connected to different Fibre Channel switches. Thus if any one Fibre Channel switch and any one IB switch card were to fail, at least one gateway continues to remain operational.

Note For the purpose of this example, gateways in slots 2 and 3 must be connected to different Fibre Channel switches than gateways in slots 4 and 5.

The topology used in this example is shown in Figure 8-3.

Figure 8-3 Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012R Server Switch

Once the redundancy groups are configured, a primary bridge is selected and forwarding is enabled.

To configure a single Cisco SFS 3012R Server Switch, perform the following steps:

Step 1 Telnet to the Cisco SFS 3012R Server Switch.

The following example shows how to Telnet to the server switch and enter the configuration mode:
telnet ip-address <switch address>
SFS-3012R-1> enable 
SFS-3012R-1# configure
Step 2 Configure the IB initiator using the IB GUID and the GUID extension.

The following example shows how to configure the IB initiator and then change the initiator description:
SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
auto-bind
SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
description ib-fc-init-1
Step 3 Apply port masking.

The following example shows how to apply port masking:
SFS-3012R-1(config)# no fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 gateway-portmask-policy restricted 2/1-2/2,3/1,3/2
Step 4 Discover the LUNs.

The following example shows how to discover the LUNs:
SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
discover-itl 
Step 5 Set the logical unit policy to load balancing, failover, or path-affinity.

The following example shows how to set the logical unit policy to load balancing:
SFS-3012R-1(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing
Step 6 Exit the switch.

The following example shows how to exit the switch:
SFS-3012R-1(config)# exit
Verifying Configuration for a Single Cisco SFS 3012R Server Switch

To verify the redundancy configuration for a single Cisco SFS 3012R Server Switch, perform the following steps:

Step 1 Telnet to the server switch.

The following example shows how to Telnet to the server switch:
telnet ip-address <switch address>
SFS-3012R-1> enable 
Step 2 Verify the configured initiator.

The following sample output from the show fc srp initiator command shows how to verify the configured initiator:
SFS-3012R-1# show fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00
================================================                                 
SRP Initiators
================================================      
               	guid: 29:01:00:05:ad:00:24:fc
                extension: 00:00:00:00:00:00:00:00
              description: ib-fc-init-1
                     wwnn: 20:01:00:05:ad:00:1b:4f
                   credit: 0
             active-ports: none
                    pkeys: 
            bootup-target: 00:00:00:00:00:00:00:00
                bootup-lu: 00:00:00:00:00:00:00:00
        alt-bootup-target: 00:00:00:00:00:00:00:00
            alt-bootup-lu: 00:00:00:00:00:00:00:00
                   action: discover-itl
                   result: success
               wwpns: port    wwpn                     	   fc-addr 
                            2/1    20:01:00:05:ad:20:1b:4f  67:0f:04
                            2/2    20:01:00:05:ad:24:1b:4f  67:0e:04
                            3/1    20:01:00:05:ad:30:1b:4f  67:11:18
                            3/2    20:01:00:05:ad:34:1b:4f  67:10:18
Step 3 Verify the configured Initiator/Target.

The following sample output from the show fc srp it command shows how to verify the configured Initiator/Target:
SFS-3012R-1# show fc srp it  29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70
================================================
SRP IT
================================================
                                    guid: 29:01:00:05:ad:00:24:fc
                               extension: 00:00:00:00:00:00:00:00
                             target-wwpn: 50:02:0f:23:00:00:08:70
                             description: it
                    non-restricted-ports: 2/1-2/2,3/1-3/2
                            active-ports: none
                         physical-access: 2/1-2/2,3/1-3/2
                                    mode: normal-mode
                                  action: none
                                  result: none
Step 4 Verify the configured logical unit.

The following is sample output from the show fc srp itl command that shows how to verify the configured logical unit:
SFS-3012R-1# show fc srp itl 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 00:00:00:00:00:00:00:00
================================================
SRP ITL
================================================
                                    guid: 29:01:00:05:ad:00:24:fc
                               extension: 00:00:00:00:00:00:00:00
                             target-wwpn: 50:02:0f:23:00:00:08:70
                                fc-lunid: 00:00:00:00:00:00:00:00
                               srp-lunid: 00:00:00:00:00:00:00:00
      logical-id (raw 64 bytes): 01:03:00:10:60:06:01:60:a2:70:0d:00:70:ad:1c:0a
                                        : 3b:a8:db:11:00:00:00:00:00:00:00:00:00:00:00:00
                                        : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
                                        : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          logical-id (formatted display): 60060160A2700D0070AD1C0A3BA8DB11
                             description: itl
                         device-category: random
                              lun-policy: non restricted
                    non-restricted-ports: 2/1-2/2,3/1-3/2
                            active-ports: none
                         physical-access: 2/1-2/2,3/1-3/2
                                 hi-mark: 16
                               max-retry: 5
                          min-io-timeout: 10
                   dynamic-path-affinity: false
      dynamic-gateway-port-loadbalancing: true
      dynamic-storage-port-loadbalancing: 
           dynamic-gateway-port-failover: false
           dynamic-storage-port-failover: 
                            active-slots: none
Step 5 Exit the switch.

The following example shows how to exit the switch:
SFS-3012R-1(config)# exit
Step 6 To verify the redundancy configuration for the second Cisco SFS 3012R Server Switch, repeat Step 1 to Step 5 for the next switch.

Configuring Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches

This section describes how to configure Fibre Channel gateway redundancy using two Cisco SFS 3012R Server Switches.

This typical example shows a setup of two Cisco SFS 3012R Server Switches with a total of four Fibre Channel gateways that are available as two for each server switch. Both gateways in each chassis are configured to use different switch cards. The gateway in slot 2 uses the switch card in one slot and the gateway in slot 3 uses the switch card in the other slot. Thus if any of the switch cards fail, the other gateway continues to remain operational. If the Fibre Channel ports of the gateways are connected to two different Fibre Channel switches, the gateways in the same chassis must be connected to different Fibre Channel switches. This topology allows one chassis and one Fibre Channel switch failure without interruption to the service. The topology used in this example is shown in Figure 8-4.

Figure 8-4 Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches

Once a redundancy group is configured, a primary bridge group is elected and forwarding is enabled.

To configure two Cisco SFS 3012R Server Switches, perform the following steps:

Step 1 Telnet to the first Cisco SFS 3012R Server Switch.

The following example shows how to Telnet to the server switch:
telnet ip-address <switch address>
SFS-3012R-1> enable 
SFS-3012R-1# configure
Step 2 Configure the IB initiator using the IB GUID and the GUID extension.

The following example shows how to configure the IB initiator and then change the initiator description:
SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
auto-bind
SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
description ib-fc-init-1
Step 3 Apply port masking.

The following example shows how to apply port masking:
SFS-3012R-1(config)# no fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 gateway-portmask-policy restricted 2/1-2/2,3/1,3/2
Step 4 Discover the LUNs.

The following example shows how to discover the LUNs:
3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
discover-itl 
Step 5 Set the logical unit policy to load balancing, failover, or path-affinity.

The following example shows how to set the logical unit policy to load balancing:
SFS-3012R-1(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing
Step 6 Exit the switch.

The following example shows how to exit the switch:
SFS-3012R-1(config)# exit
Step 7 To configure the second Cisco SFS 3012R Server Switch, repeat Step 1 to Step 6 for the next switch.

Verifying Configuration for Two Cisco SFS 3012R Server Switches

To verify configuration for the two Cisco SFS 3012R Server Switches, perform the following steps:

Step 1 Telnet to the Cisco SFS 3012R Server Switch.

The following example shows how to Telnet to the server switch:
telnet ip-address <switch address>
SFS-3012R-1> enable 
Step 2 Verify the configured initiator.

The following is sample output from the show fc srp initiator command that shows how to verify the configured initiator:
SFS-3012R-1# show fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00
================================================                                 
SRP Initiators
================================================      
               	guid: 29:01:00:05:ad:00:24:fc
                extension: 00:00:00:00:00:00:00:00
              description: ib-fc-init-1
                     wwnn: 20:01:00:05:ad:00:1b:4f
                   credit: 0
             active-ports: none
                    pkeys: 
            bootup-target: 00:00:00:00:00:00:00:00
                bootup-lu: 00:00:00:00:00:00:00:00
        alt-bootup-target: 00:00:00:00:00:00:00:00
            alt-bootup-lu: 00:00:00:00:00:00:00:00
                   action: discover-itl
                   result: success
               wwpns: port    wwpn                     	   fc-addr 
                            2/1    20:01:00:05:ad:20:1b:4f  67:0f:04
                            2/2    20:01:00:05:ad:24:1b:4f  67:0e:04
                            3/1    20:01:00:05:ad:30:1b:4f  67:11:18
                            3/2    20:01:00:05:ad:34:1b:4f  67:10:18
Step 3 Verify the configured Initiator/Target.

The following is sample output from the show fc srp it command that shows how to verify the configured Initiator/Target:
SFS-3012R-1# show fc srp it  29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 
================================================
SRP IT
================================================
                                    guid: 29:01:00:05:ad:00:24:fc
                               extension: 00:00:00:00:00:00:00:00
                             target-wwpn: 50:02:0f:23:00:00:08:70
                             description: it
                    non-restricted-ports: 2/1-2/2,3/1-3/2
                            active-ports: none
                         physical-access: 2/1-2/2,3/1-3/2
                                    mode: normal-mode
                                  action: none
                                  result: none
Step 4 Verify the configured logical unit.

The following is sample output from the show fc srp itl command that shows how to verify the configured logical unit:
SFS-3012R-1# show fc srp itl 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 00:00:00:00:00:00:00:00
================================================
SRP ITL
================================================
                                    guid: 29:01:00:05:ad:00:24:fc
                               extension: 00:00:00:00:00:00:00:00
                             target-wwpn: 50:02:0f:23:00:00:08:70
                                fc-lunid: 00:00:00:00:00:00:00:00
                               srp-lunid: 00:00:00:00:00:00:00:00
      logical-id (raw 64 bytes): 01:03:00:10:60:06:01:60:a2:70:0d:00:70:ad:1c:0a
                                        : 3b:a8:db:11:00:00:00:00:00:00:00:00:00:00:00:00
                                        : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
                                        : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          logical-id (formatted display): 60060160A2700D0070AD1C0A3BA8DB11
                             description: itl
                         device-category: random
                              lun-policy: non restricted
                    non-restricted-ports: 2/1-2/2,3/1-3/2
                            active-ports: none
                         physical-access: 2/1-2/2,3/1-3/2
                                 hi-mark: 16
                               max-retry: 5
                          min-io-timeout: 10
                   dynamic-path-affinity: false
      dynamic-gateway-port-loadbalancing: true
      dynamic-storage-port-loadbalancing: 
           dynamic-gateway-port-failover: false
           dynamic-storage-port-failover: 
                            active-slots: none
Step 5 Exit the switch.

The following example shows how to exit the switch:
SFS-3012R-1(config)# exit
Step 6 To verify the configuration for the second Cisco SFS 3012R switch, repeat Step 1 to Step 5 for the switch.

Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3001 Server Switch

This section describes how to configure Fibre Channel gateway redundancy for the Cisco SFS 3001 Server Switch and includes the following topics:

•Configuring Two Cisco SFS 3001 Server Switches

•Verifying Redundancy Configuration for Cisco SFS 3001 Server Switches

Two or more Cisco SFS 3001 Server Switches must be used to provide high availability redundancy. A typical deployment consists of two Cisco SFS 3001 Server Switches using one Fibre Channel gateway in each (see Figure 8-5).

Figure 8-5 Fibre Channel Gateway Redundancy Using Two Cisco SFS 3001 Server Switches

A single Cisco SFS 3001 Server Switch provides power supply redundancy only. A single Cisco SFS 3001 Server Switch cannot provide Fibre Channel gateway redundancy, because it contains a single gateway slot. For more information about this product, see "Cisco SFS 3504 and Cisco SFS 3000 Series Server Switch Redundancy."

Configuring Two Cisco SFS 3001 Server Switches

This section describes how to configure two Cisco SFS 3001 Server Switches. To configure two Cisco SFS 3001 Server Switches, perform the following steps:

Step 1 Telnet to the server switch.

The following example shows how to Telnet to a server switch:
telnet ip-address <switch address>
SFS-3001-1> enable 
SFS-3001-1# configure
Step 2 Configure the IB initiator using the IB GUID and the GUID-extension.

The following is sample output from the show fc srp initiator command that shows how to configure the IB initiator and then change the initiator description:
SFS-3001-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
auto-bind
SFS-3001-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
description ib-fc-init-1
Step 3 Apply port masking.

The following example shows how to apply port masking:
SFS-3001-1(config)# no fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 gateway-portmask-policy restricted 2/1-2/2
Step 4 Discover the LUNs.

The following example shows how to discover the LUNs:
SFS-3001-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
discover-itl
Step 5 Set the logical unit policy to load balancing, failover, or path affinity.

The following example shows how to set the logical unit policy to load balancing:
SFS-3001-1(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing
Step 6 To configure the second Cisco SFS 3001 Server Switch, repeat Step 1 to Step 5 for the next switch.

Verifying Redundancy Configuration for Cisco SFS 3001 Server Switches

To verify redundancy for the Cisco SFS 3001 Server Switches, perform the following steps:

Step 1 Telnet to the first Cisco SFS 3001 Server Switch.

The following example shows how to Telnet to the server switch:
telnet ip-address <switch address>
SFS-3001-1> enable 
Step 2 Verify the configured initiator.

The following example shows how to verify the configured initiator:
SFS-3001-1# show fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00
================================================                                 
SRP Initiators
================================================      
               	guid: 29:01:00:05:ad:00:24:fc
                extension: 00:00:00:00:00:00:00:00
              description: ib-fc-init-1
                     wwnn: 20:01:00:05:ad:00:1b:4f
                   credit: 0
             active-ports: none
                    pkeys: 
            bootup-target: 00:00:00:00:00:00:00:00
                bootup-lu: 00:00:00:00:00:00:00:00
        alt-bootup-target: 00:00:00:00:00:00:00:00
            alt-bootup-lu: 00:00:00:00:00:00:00:00
                   action: discover-itl
                   result: success
               wwpns: port    wwpn                     	   fc-addr 
                            2/1    20:01:00:05:ad:20:1b:4f  67:0f:04
                            2/2    20:01:00:05:ad:24:1b:4f  67:0e:04
Step 3 Verify the configured Initiator/Target.

The following is sample output from the show fc srp it command that shows how to verify the configured Initiator/Target:
SFS-3001-1# show fc srp it  29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 
================================================
SRP IT
================================================
                                    guid: 29:01:00:05:ad:00:24:fc
                               extension: 00:00:00:00:00:00:00:00
                             target-wwpn: 50:02:0f:23:00:00:08:70
                             description: it
                    non-restricted-ports: 2/1-2/2
                            active-ports: none
                         physical-access: 2/1-2/2
                                    mode: normal-mode
                                  action: none
                                  result: none
Step 4 Verify the configured logical unit.

The following is sample output from the show fc srp itl command that shows how to verify the configured logical unit:
SFS-3001-1# show fc srp itl 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 
50:02:0f:23:00:00:08:70 00:00:00:00:00:00:00:00
================================================
SRP ITL
================================================
                                    guid: 29:01:00:05:ad:00:24:fc
                               extension: 00:00:00:00:00:00:00:00
                             target-wwpn: 50:02:0f:23:00:00:08:70
                                fc-lunid: 00:00:00:00:00:00:00:00
                               srp-lunid: 00:00:00:00:00:00:00:00
      logical-id (raw 64 bytes): 01:03:00:10:60:06:01:60:a2:70:0d:00:70:ad:1c:0a
                                        : 3b:a8:db:11:00:00:00:00:00:00:00:00:00:00:00:00
                                        : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
                                        : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
          logical-id (formatted display): 60060160A2700D0070AD1C0A3BA8DB11
                             description: itl
                         device-category: random
                              lun-policy: non restricted
                    non-restricted-ports: 2/1-2/2
                            active-ports: none
                         physical-access: 2/1-2/2
                                 hi-mark: 16
                               max-retry: 5
                          min-io-timeout: 10
                   dynamic-path-affinity: false
      dynamic-gateway-port-loadbalancing: true
      dynamic-storage-port-loadbalancing: 
           dynamic-gateway-port-failover: false
           dynamic-storage-port-failover: 
                            active-slots: none
Step 5 Exit from the switch.

The following example shows how to exit from the switch:
SFS-3001-1# exit
Step 6 To verify the configuration for the second Cisco SFS 3001 Server Switch, repeat Step 1 to Step 5 for the next switch.

	Cisco SFS InfiniBand Redundancy Configuration Guide, Release 2.10
	Fibre Channel Gateway and SRP Redundancies
Cisco SFS InfiniBand Redundancy Configuration Guide, Release 2.10 Index Preface Overview Cisco SFS 7008P and SFS 7000 Series Server Switch Redundancy InfiniBand Server Switch Module Redundancy for the IBM BladeCenter Cisco SFS 3504 and Cisco SFS 3000 Series Server Switch Redundancy Subnet Manager Redundancy Host Redundancy, IPoIB, and SRP Redundancy Ethernet Gateway and IPoIB Redundancies Fibre Channel Gateway and SRP Redundancies Typical Redundancy Use Case Acronyms and Abbreviations	Download this chapter Fibre Channel Gateway and SRP Redundancies Download the complete book Full book PDF (PDF - 3 MB) Feedback Table Of Contents Fibre Channel Gateway and SRP Redundancies Dynamic Load Balancing Dynamic Gateway Failover Path Affinity Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3504 Server Switch Verifying Configured Initiator Verifying IT Verifying LU Configuring Fibre Channel Gateway Redundancy Using the Cisco SFS 3012R Server Switch Configuring Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012 Server Switch Verifying Configuration for a Single Cisco SFS 3012R Server Switch Configuring Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches Verifying Configuration for Two Cisco SFS 3012R Server Switches Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3001 Server Switch Configuring Two Cisco SFS 3001 Server Switches Verifying Redundancy Configuration for Cisco SFS 3001 Server Switches Fibre Channel Gateway and SRP Redundancies This chapter describes Fibre Channel gateway redundancies and includes the following sections: •Dynamic Load Balancing •Dynamic Gateway Failover •Path Affinity •Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3504 Server Switch •Configuring Fibre Channel Gateway Redundancy Using the Cisco SFS 3012R Server Switch •Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3001 Server Switch Note For expansions of acronyms and abbreviations used in this publication, see "Acronyms and Abbreviations." Fibre Channel gateway redundancy is based on the concept of using all available paths if the configured policy allows for it. Each ITL has a redundancy policy set and the gateway paths are used according to those policies. Access to the available paths can either be granted or denied. The connection manager that is resident on the controller determines the path of the Initiator/Target. A logical diagram of Fibre Channel gateways in a redundant configuration is shown in Figure 8-1. Figure 8-1 Logical Diagram of Fibre Channel Gateways in a Redundant Configuration The examples in the next sections show the most popular deployment of different types of I/O chassis. The following features enable Fibre Channel gateways to support redundancy and high availability: •Dynamic Load Balancing •Dynamic Gateway Failover •Path Affinity Dynamic Load Balancing These features work within a chassis for the Cisco SFS 3504, SFS 3012R, and SFS 3001 Server Switches. Dynamic load balancing automatically distributes traffic from a host to a target evenly across all available paths and thus provides increased availability. It prevents against single points of failure or performance bottlenecks. Dynamic Gateway Failover This feature is supported by the Cisco SFS 3504, SFS 3012R, and SFS 3001 Server Switches. Dynamic gateway failover enables available gateways to assume the traffic of gateways that fail by having one or more redundant gateways available that are ready to provide service. Fibre Channel gateways support greater granular high availability at the port level and thereby ensure load balancing is utilized most efficiently. Path Affinity This feature is supported by the SFS 3012R and the Cisco SFS 3001 Server Switches. Path affinity compensates for the lack of load balancing capabilities of the storage systems, including the storage systems for which multiple paths are available. When multiple I/Os are initiated to a storage system with a queue depth that is greater than one, the host has an affinity to the path that was selected and the I/Os are transmitted on that path until I/O count to that host reaches zero. The next set of I/Os can have a different path affinity. Therefore, at any given time, there is only one path in use, although multiple paths are available. However, each time the path could be different. This is different from port failover, where only one path is used until the path no longer exists. Note The Cisco SFS 3504 Server Switch does not support path affinity. Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3504 Server Switch This section describes how to configure Fibre Channel gateway redundancy for the Cisco SFS 3504 chassis and includes the following topics: •Verifying Configured Initiator •Verifying IT •Verifying LU Two or more Cisco SFS 3504 Server Switches must be used to provide high availability redundancy. A very typical deployment would consist of two Cisco SFS 3504 Server Switches with two Fibre Channel gateways in each (see Figure 8-2). The Product ID number for the Fibre Channel gateway card is SFS-3500-FCGW-4G. Each Fibre Channel gateway card is a 4-port, 4 Gbps per-port capable InfiniBand-to-Fibre Channel gateway module. The Cisco SFS 3504 Server Switches support VSANs. For more details about VSANs, see the Cisco SFS InfiniBand Software Configuration Guide and the Cisco SFS Product Family Command Reference. Figure 8-2 Fibre Channel Redundancy with Dual Cisco SFS 3504 Server Switches To configure the first Cisco SFS 3504 Server Switch, perform the following steps: Step 1 Enter configuration mode. The following example shows how to enter configuration mode: SFS-3504> enable SFS-3504# config Step 2 Configure the initiator. The following example shows how to configure the initiator: SFS-3504(config)# fc srp initiator initiator initiator-wwpn SFS-3504(config)# fc srp initiator 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 wwnn ? <wwnn> - Initiator wwnn suggested wwnn = 20:08:00:1b:0d:00:12:00 SFS-3504(config)# fc srp initiator 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 wwnn 20:08:00:1b:0d:00:12:00 SFS-3504(config)# SFS-3504(config)# fc srp initiator-wwpn 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 3/1 ? <wwpn> - wwpn suggested wwpn = 20:08:00:1b:0d:00:12:16 SFS-3504(config)# fc srp initiator-wwpn 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 3/1 20:08:00:1b:0d:00:12:16 vsan 20 SFS-3504(config)# Step 3 Apply port masking. The following example shows how to apply port masking: SFS-3504(config)# no fc srp it 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 20:01:00:20:c2:03:31:99 gateway-portmask-policy restricted 3/1-3/4 Step 4 Discover the LUNs. The following example shows how to discover the LUNs: SFS-3504(config)# fc srp initiator 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 discover-itl Step 5 Set the logical unit policy to load balancing, failover, or path-affinity. The following example shows how to set the logical unit policy to load balancing: SFS-3504(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing SFS-3504(config)# exit To configure the second Cisco SFS 3504 Server Switch, perform Step 1 to Step 5 on the switch. Verifying Configured Initiator The following is sample output from the show fc srp initiator command that shows how to verify the configured initiator for the first Cisco SFS 3504 Server Switch: SFS-3504# show fc srp initiator ================================================================================ SRP Initiators ================================================================================ guid: 00:05:ad:00:00:00:22:3c extension: 00:00:00:00:00:00:00:00 description: svbu-fc-host-12 wwnn: 20:08:00:1b:0d:00:12:00 credit: 0 active-ports: none pkeys: bootup-target: 00:00:00:00:00:00:00:00 bootup-lu: 00:00:00:00:00:00:00:00 alt-bootup-target: 00:00:00:00:00:00:00:00 alt-bootup-lu: 00:00:00:00:00:00:00:00 action: none result: none wwpns: port wwpn fc-addr vsan 3/1 20:08:00:1b:0d:00:12:16 14:01:01 20 3/2 20:08:00:1b:0d:00:12:16 14:04:01 20 3/3 20:08:00:1b:0d:00:12:16 14:04:01 20 3/4 20:08:00:1b:0d:00:12:16 14:04:01 20 To verify the configured initiator for the second Cisco SFS 3504 Server Switch, use the command after configuring the switch. Verifying IT The following is sample output from the show fc srp it command that shows how to verify IT for the first Cisco SFS 3504 Server Switch: SFS-3504# show fc srp it 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 20:01:00:20:c2:03:31:99 ================================================================================ SRP IT ================================================================================ guid: 00:05:ad:00:00:00:22:3c extension: 00:00:00:00:00:00:00:00 target-wwpn: 20:01:00:20:c2:03:31:99 description: it non-restricted-ports: 3/1-3/4 active-ports: 3/1 physical-access: 3/1 mode: normal-mode action: none result: none To verify the IT for the second Cisco SFS 3504 Server Switch, use the command after configuring the switch. Verifying LU The following is sample output from the show fc srp itl command that shows how to verify LU for the first Cisco SFS 3504 Server Switch: SFS-3504# show fc srp itl 00:05:ad:00:00:00:22:3c 00:00:00:00:00:00:00:00 20:01:00:20:c2:03:31:99 00:00:00:00:00:00:00:00 ================================================================================ SRP ITL ================================================================================ guid: 00:05:ad:00:00:00:22:3c extension: 00:00:00:00:00:00:00:00 target-wwpn: 20:01:00:20:c2:03:31:99 fc-lunid: 00:00:00:00:00:00:00:00 srp-lunid: 00:00:00:00:00:00:00:00 logical-id (raw 64 bytes): 02:01:00:22:54:4d:53:20:20:20:20:20:46:43:36:35 : 20:20:20:20:20:20:20:20:20:20:20:20:30:33:33:31 : 39:39:30:30:30:30:00:00:00:00:00:00:00:00:00:00 : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 logical-id (formatted display): TMS FC65 0331990000 description: itl device-category: random lun-policy: restricted non-restricted-ports: 3/1-3/4 active-ports: none physical-access: none hi-mark: 16 max-retry: 5 min-io-timeout: 10 dynamic-path-affinity: false dynamic-gateway-port-loadbalancing: true dynamic-storage-port-loadbalancing: dynamic-gateway-port-failover: false dynamic-storage-port-failover: active-slots: none Configuring Fibre Channel Gateway Redundancy Using the Cisco SFS 3012R Server Switch This section describes how to configure Fibre Channel gateway redundancy using the Cisco SFS 3012R Server Switch and includes the following topics: •Configuring Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012 Server Switch •Verifying Configuration for a Single Cisco SFS 3012R Server Switch •Configuring Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches •Verifying Configuration for Two Cisco SFS 3012R Server Switches The Cisco SFS 3012R Server Switch has various redundancies built into the chassis. It has twelve gateway slots, two controller modules, and two switch cards. Each gateway is connected to both switch cards through the backplane. A single Cisco SFS 3012R Server Switch is therefore capable of being configured for high availability. For more information about this product, see "Cisco SFS 3504 and Cisco SFS 3000 Series Server Switch Redundancy." Configuring Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012 Server Switch This section describes how to configure Fibre Channel gateway redundancy using a single Cisco SFS 3012R Server Switch. The example in this section shows a typical single-switch configuration with four Fibre Channel gateways and two switch cards. Two of the gateways, slots 2 and 4, are configured to use switch cards in the first slot and the other two gateways, slots 3 and 5, are configured to use switch cards in the next slot. (For information about the location of the slot numbers, see Figure 4-4.) Thus if any of the switch cards fail, two gateways continue to remain operational. If the Fibre Channel ports of the gateways are required to be connected to two different Fibre Channel switches, connect the gateways to the same IB switch card that are connected to different Fibre Channel switches. Thus if any one Fibre Channel switch and any one IB switch card were to fail, at least one gateway continues to remain operational. Note For the purpose of this example, gateways in slots 2 and 3 must be connected to different Fibre Channel switches than gateways in slots 4 and 5. The topology used in this example is shown in Figure 8-3. Figure 8-3 Fibre Channel Gateway Redundancy Using a Single Cisco SFS 3012R Server Switch Once the redundancy groups are configured, a primary bridge is selected and forwarding is enabled. To configure a single Cisco SFS 3012R Server Switch, perform the following steps: Step 1 Telnet to the Cisco SFS 3012R Server Switch. The following example shows how to Telnet to the server switch and enter the configuration mode: telnet ip-address <switch address> SFS-3012R-1> enable SFS-3012R-1# configure Step 2 Configure the IB initiator using the IB GUID and the GUID extension. The following example shows how to configure the IB initiator and then change the initiator description: SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 auto-bind SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 description ib-fc-init-1 Step 3 Apply port masking. The following example shows how to apply port masking: SFS-3012R-1(config)# no fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 gateway-portmask-policy restricted 2/1-2/2,3/1,3/2 Step 4 Discover the LUNs. The following example shows how to discover the LUNs: SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 discover-itl Step 5 Set the logical unit policy to load balancing, failover, or path-affinity. The following example shows how to set the logical unit policy to load balancing: SFS-3012R-1(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing Step 6 Exit the switch. The following example shows how to exit the switch: SFS-3012R-1(config)# exit Verifying Configuration for a Single Cisco SFS 3012R Server Switch To verify the redundancy configuration for a single Cisco SFS 3012R Server Switch, perform the following steps: Step 1 Telnet to the server switch. The following example shows how to Telnet to the server switch: telnet ip-address <switch address> SFS-3012R-1> enable Step 2 Verify the configured initiator. The following sample output from the show fc srp initiator command shows how to verify the configured initiator: SFS-3012R-1# show fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 ================================================ SRP Initiators ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 description: ib-fc-init-1 wwnn: 20:01:00:05:ad:00:1b:4f credit: 0 active-ports: none pkeys: bootup-target: 00:00:00:00:00:00:00:00 bootup-lu: 00:00:00:00:00:00:00:00 alt-bootup-target: 00:00:00:00:00:00:00:00 alt-bootup-lu: 00:00:00:00:00:00:00:00 action: discover-itl result: success wwpns: port wwpn fc-addr 2/1 20:01:00:05:ad:20:1b:4f 67:0f:04 2/2 20:01:00:05:ad:24:1b:4f 67:0e:04 3/1 20:01:00:05:ad:30:1b:4f 67:11:18 3/2 20:01:00:05:ad:34:1b:4f 67:10:18 Step 3 Verify the configured Initiator/Target. The following sample output from the show fc srp it command shows how to verify the configured Initiator/Target: SFS-3012R-1# show fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 ================================================ SRP IT ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 target-wwpn: 50:02:0f:23:00:00:08:70 description: it non-restricted-ports: 2/1-2/2,3/1-3/2 active-ports: none physical-access: 2/1-2/2,3/1-3/2 mode: normal-mode action: none result: none Step 4 Verify the configured logical unit. The following is sample output from the show fc srp itl command that shows how to verify the configured logical unit: SFS-3012R-1# show fc srp itl 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 00:00:00:00:00:00:00:00 ================================================ SRP ITL ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 target-wwpn: 50:02:0f:23:00:00:08:70 fc-lunid: 00:00:00:00:00:00:00:00 srp-lunid: 00:00:00:00:00:00:00:00 logical-id (raw 64 bytes): 01:03:00:10:60:06:01:60:a2:70:0d:00:70:ad:1c:0a : 3b:a8:db:11:00:00:00:00:00:00:00:00:00:00:00:00 : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 logical-id (formatted display): 60060160A2700D0070AD1C0A3BA8DB11 description: itl device-category: random lun-policy: non restricted non-restricted-ports: 2/1-2/2,3/1-3/2 active-ports: none physical-access: 2/1-2/2,3/1-3/2 hi-mark: 16 max-retry: 5 min-io-timeout: 10 dynamic-path-affinity: false dynamic-gateway-port-loadbalancing: true dynamic-storage-port-loadbalancing: dynamic-gateway-port-failover: false dynamic-storage-port-failover: active-slots: none Step 5 Exit the switch. The following example shows how to exit the switch: SFS-3012R-1(config)# exit Step 6 To verify the redundancy configuration for the second Cisco SFS 3012R Server Switch, repeat Step 1 to Step 5 for the next switch. Configuring Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches This section describes how to configure Fibre Channel gateway redundancy using two Cisco SFS 3012R Server Switches. This typical example shows a setup of two Cisco SFS 3012R Server Switches with a total of four Fibre Channel gateways that are available as two for each server switch. Both gateways in each chassis are configured to use different switch cards. The gateway in slot 2 uses the switch card in one slot and the gateway in slot 3 uses the switch card in the other slot. Thus if any of the switch cards fail, the other gateway continues to remain operational. If the Fibre Channel ports of the gateways are connected to two different Fibre Channel switches, the gateways in the same chassis must be connected to different Fibre Channel switches. This topology allows one chassis and one Fibre Channel switch failure without interruption to the service. The topology used in this example is shown in Figure 8-4. Figure 8-4 Fibre Channel Gateway Redundancy Using Two Cisco SFS 3012R Server Switches Once a redundancy group is configured, a primary bridge group is elected and forwarding is enabled. To configure two Cisco SFS 3012R Server Switches, perform the following steps: Step 1 Telnet to the first Cisco SFS 3012R Server Switch. The following example shows how to Telnet to the server switch: telnet ip-address <switch address> SFS-3012R-1> enable SFS-3012R-1# configure Step 2 Configure the IB initiator using the IB GUID and the GUID extension. The following example shows how to configure the IB initiator and then change the initiator description: SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 auto-bind SFS-3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 description ib-fc-init-1 Step 3 Apply port masking. The following example shows how to apply port masking: SFS-3012R-1(config)# no fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 gateway-portmask-policy restricted 2/1-2/2,3/1,3/2 Step 4 Discover the LUNs. The following example shows how to discover the LUNs: 3012R-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 discover-itl Step 5 Set the logical unit policy to load balancing, failover, or path-affinity. The following example shows how to set the logical unit policy to load balancing: SFS-3012R-1(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing Step 6 Exit the switch. The following example shows how to exit the switch: SFS-3012R-1(config)# exit Step 7 To configure the second Cisco SFS 3012R Server Switch, repeat Step 1 to Step 6 for the next switch. Verifying Configuration for Two Cisco SFS 3012R Server Switches To verify configuration for the two Cisco SFS 3012R Server Switches, perform the following steps: Step 1 Telnet to the Cisco SFS 3012R Server Switch. The following example shows how to Telnet to the server switch: telnet ip-address <switch address> SFS-3012R-1> enable Step 2 Verify the configured initiator. The following is sample output from the show fc srp initiator command that shows how to verify the configured initiator: SFS-3012R-1# show fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 ================================================ SRP Initiators ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 description: ib-fc-init-1 wwnn: 20:01:00:05:ad:00:1b:4f credit: 0 active-ports: none pkeys: bootup-target: 00:00:00:00:00:00:00:00 bootup-lu: 00:00:00:00:00:00:00:00 alt-bootup-target: 00:00:00:00:00:00:00:00 alt-bootup-lu: 00:00:00:00:00:00:00:00 action: discover-itl result: success wwpns: port wwpn fc-addr 2/1 20:01:00:05:ad:20:1b:4f 67:0f:04 2/2 20:01:00:05:ad:24:1b:4f 67:0e:04 3/1 20:01:00:05:ad:30:1b:4f 67:11:18 3/2 20:01:00:05:ad:34:1b:4f 67:10:18 Step 3 Verify the configured Initiator/Target. The following is sample output from the show fc srp it command that shows how to verify the configured Initiator/Target: SFS-3012R-1# show fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 ================================================ SRP IT ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 target-wwpn: 50:02:0f:23:00:00:08:70 description: it non-restricted-ports: 2/1-2/2,3/1-3/2 active-ports: none physical-access: 2/1-2/2,3/1-3/2 mode: normal-mode action: none result: none Step 4 Verify the configured logical unit. The following is sample output from the show fc srp itl command that shows how to verify the configured logical unit: SFS-3012R-1# show fc srp itl 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 00:00:00:00:00:00:00:00 ================================================ SRP ITL ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 target-wwpn: 50:02:0f:23:00:00:08:70 fc-lunid: 00:00:00:00:00:00:00:00 srp-lunid: 00:00:00:00:00:00:00:00 logical-id (raw 64 bytes): 01:03:00:10:60:06:01:60:a2:70:0d:00:70:ad:1c:0a : 3b:a8:db:11:00:00:00:00:00:00:00:00:00:00:00:00 : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 logical-id (formatted display): 60060160A2700D0070AD1C0A3BA8DB11 description: itl device-category: random lun-policy: non restricted non-restricted-ports: 2/1-2/2,3/1-3/2 active-ports: none physical-access: 2/1-2/2,3/1-3/2 hi-mark: 16 max-retry: 5 min-io-timeout: 10 dynamic-path-affinity: false dynamic-gateway-port-loadbalancing: true dynamic-storage-port-loadbalancing: dynamic-gateway-port-failover: false dynamic-storage-port-failover: active-slots: none Step 5 Exit the switch. The following example shows how to exit the switch: SFS-3012R-1(config)# exit Step 6 To verify the configuration for the second Cisco SFS 3012R switch, repeat Step 1 to Step 5 for the switch. Configuring Fibre Channel Gateway Redundancy for the Cisco SFS 3001 Server Switch This section describes how to configure Fibre Channel gateway redundancy for the Cisco SFS 3001 Server Switch and includes the following topics: •Configuring Two Cisco SFS 3001 Server Switches •Verifying Redundancy Configuration for Cisco SFS 3001 Server Switches Two or more Cisco SFS 3001 Server Switches must be used to provide high availability redundancy. A typical deployment consists of two Cisco SFS 3001 Server Switches using one Fibre Channel gateway in each (see Figure 8-5). Figure 8-5 Fibre Channel Gateway Redundancy Using Two Cisco SFS 3001 Server Switches A single Cisco SFS 3001 Server Switch provides power supply redundancy only. A single Cisco SFS 3001 Server Switch cannot provide Fibre Channel gateway redundancy, because it contains a single gateway slot. For more information about this product, see "Cisco SFS 3504 and Cisco SFS 3000 Series Server Switch Redundancy." Configuring Two Cisco SFS 3001 Server Switches This section describes how to configure two Cisco SFS 3001 Server Switches. To configure two Cisco SFS 3001 Server Switches, perform the following steps: Step 1 Telnet to the server switch. The following example shows how to Telnet to a server switch: telnet ip-address <switch address> SFS-3001-1> enable SFS-3001-1# configure Step 2 Configure the IB initiator using the IB GUID and the GUID-extension. The following is sample output from the show fc srp initiator command that shows how to configure the IB initiator and then change the initiator description: SFS-3001-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 auto-bind SFS-3001-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 description ib-fc-init-1 Step 3 Apply port masking. The following example shows how to apply port masking: SFS-3001-1(config)# no fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 gateway-portmask-policy restricted 2/1-2/2 Step 4 Discover the LUNs. The following example shows how to discover the LUNs: SFS-3001-1(config)# fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 discover-itl Step 5 Set the logical unit policy to load balancing, failover, or path affinity. The following example shows how to set the logical unit policy to load balancing: SFS-3001-1(config)# fc srp lu <64 byte lu-id string> dynamic-gateway-port-loadbalancing Step 6 To configure the second Cisco SFS 3001 Server Switch, repeat Step 1 to Step 5 for the next switch. Verifying Redundancy Configuration for Cisco SFS 3001 Server Switches To verify redundancy for the Cisco SFS 3001 Server Switches, perform the following steps: Step 1 Telnet to the first Cisco SFS 3001 Server Switch. The following example shows how to Telnet to the server switch: telnet ip-address <switch address> SFS-3001-1> enable Step 2 Verify the configured initiator. The following example shows how to verify the configured initiator: SFS-3001-1# show fc srp initiator 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 ================================================ SRP Initiators ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 description: ib-fc-init-1 wwnn: 20:01:00:05:ad:00:1b:4f credit: 0 active-ports: none pkeys: bootup-target: 00:00:00:00:00:00:00:00 bootup-lu: 00:00:00:00:00:00:00:00 alt-bootup-target: 00:00:00:00:00:00:00:00 alt-bootup-lu: 00:00:00:00:00:00:00:00 action: discover-itl result: success wwpns: port wwpn fc-addr 2/1 20:01:00:05:ad:20:1b:4f 67:0f:04 2/2 20:01:00:05:ad:24:1b:4f 67:0e:04 Step 3 Verify the configured Initiator/Target. The following is sample output from the show fc srp it command that shows how to verify the configured Initiator/Target: SFS-3001-1# show fc srp it 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 ================================================ SRP IT ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 target-wwpn: 50:02:0f:23:00:00:08:70 description: it non-restricted-ports: 2/1-2/2 active-ports: none physical-access: 2/1-2/2 mode: normal-mode action: none result: none Step 4 Verify the configured logical unit. The following is sample output from the show fc srp itl command that shows how to verify the configured logical unit: SFS-3001-1# show fc srp itl 29:01:00:05:ad:00:24:fc 00:00:00:00:00:00:00:00 50:02:0f:23:00:00:08:70 00:00:00:00:00:00:00:00 ================================================ SRP ITL ================================================ guid: 29:01:00:05:ad:00:24:fc extension: 00:00:00:00:00:00:00:00 target-wwpn: 50:02:0f:23:00:00:08:70 fc-lunid: 00:00:00:00:00:00:00:00 srp-lunid: 00:00:00:00:00:00:00:00 logical-id (raw 64 bytes): 01:03:00:10:60:06:01:60:a2:70:0d:00:70:ad:1c:0a : 3b:a8:db:11:00:00:00:00:00:00:00:00:00:00:00:00 : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 : 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 logical-id (formatted display): 60060160A2700D0070AD1C0A3BA8DB11 description: itl device-category: random lun-policy: non restricted non-restricted-ports: 2/1-2/2 active-ports: none physical-access: 2/1-2/2 hi-mark: 16 max-retry: 5 min-io-timeout: 10 dynamic-path-affinity: false dynamic-gateway-port-loadbalancing: true dynamic-storage-port-loadbalancing: dynamic-gateway-port-failover: false dynamic-storage-port-failover: active-slots: none Step 5 Exit from the switch. The following example shows how to exit from the switch: SFS-3001-1# exit Step 6 To verify the configuration for the second Cisco SFS 3001 Server Switch, repeat Step 1 to Step 5 for the next switch.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks