Configuring the Fibre Channel Gateway

Transcription

1 CHAPTER 6 This chapter describes Fibre Channel gateway configuration and includes the following sections: Before You Begin, page 6-1 Administering the Fibre Channel Gateway, page 6-1 Pre-configuration Checklist, page 6-2 Configuring a New Fibre Channel Gateway, page 6-2 Updating Existing Configurations, page 6-2 Bringing Up a Fibre Channel Gateway Module, page 6-3 Configuring Global Policies, page 6-5 Configuring Port Parameters, page 6-7 Configuring Initiators, ITs, and ITLs, page 6-15 Before You Begin If the gateway ports connect to a Fibre Channel switch, the corresponding Fibre Channel switch port needs to be configured as an E port. See the FC-switch specific documentation to obtain the set of appropriate commands to perform this configuration. If the gateway port connects directly to a storage device, then the storage port needs to act as an F port, which is usually the default behavior. See the storage-specific documentation to configure the storage port as an F port. Administering the Fibre Channel Gateway Use the CLI to administer your Fibre Channel gateway modules. See the Cisco SFS Product Family Command Reference. 6-1

2 Pre-configuration Checklist Chapter 6 Pre-configuration Checklist Before you can connect a Cisco Fibre Channel gateway port to a fabric, verify that the following tasks have been completed: The Fibre Channel gateway module is up. (See the Bringing Up a Fibre Channel Gateway Module section on page 6-3.) The Fibre Channel gateway port is up. (See the Bringing Up a Fibre Channel Port section on page 6-14.) You have set up the correct interop mode for the port. (See the About Interop Modes section on page 6-7.) You have set up the correct the domain ID for the port. (See the Setting Domain ID section on page 6-9.) You have set up the correct the port speed. (See the Setting the Port Speed section on page 6-10.) Configuring a New Fibre Channel Gateway After you install a new Fibre Channel gateway (see the Cisco SFS 3504 Multifabric Server Switch Hardware Installation Guide for more information), perform the following steps: Bring up your gateway (see the Bringing Up a Fibre Channel Gateway Module section on page 6-3) so that it can pass traffic. Configure global SRP/ITL attributes to assign default attributes to new ITLs. (See the Configuring Initiators, ITs, and ITLs section on page 6-15 for information about how to perform this step and the following steps in this section.) Discover ITLs (see the Configuring ITLs section) to provide communication paths between hosts and storage. Customize ITLs and ITs (see the Configuring Individual ITL Attributes section) to grant or deny storage access beyond defaults and to configure custom behavior beyond defaults. Updating Existing Configurations To make changes to existing Fibre Channel gateway configurations, perform any one of the following tasks in this section. (See the Configuring Initiators, ITs, and ITLs section on page 6-15 for information about how to perform the tasks in this section.) Reconfigure global ITL attributes (see the Configuring Individual ITL Attributes section) to change the default configuration of new ITLs. Note Remember that when you change global defaults, existing ITLs that you created with the original defaults do not change. You must reconfigure existing ITLs individually. Reconfigure existing ITLs (see the Configuring Individual ITL Attributes section) to update access and behavior as your SAN priorities and requirements change. 6-2

3 Chapter 6 Bringing Up a Fibre Channel Gateway Module Add additional ITLs (see the Configuring ITLs section) as you add storage devices and hosts. Bringing Up a Fibre Channel Gateway Module Bring up interface cards to run traffic between IB hosts and Fibre Channel storage. To bring up a Fibre Channel gateway module, perform the following steps: Open a CLI session, and log in as a user with Fibre Channel read-write access privileges. (For more information about privilege levels and access levels, see Table 2-1 on page 2-2, Privilege Levels, and Table 2-2 on page 2-2, Access Levels. ) Login: super Password: xxxxx Enter the enable command to enter Privileged EXEC mode: Enter the show card command to verify that your module booted successfully. Note Do not proceed until the boot stage field displays done and the boot status field displays success. show card Card Information admin oper admin oper oper slot type type status status code fc4port4g fc4port4g up up normal 2 fc4port4g fc4port4g up up normal 3 en6port1g3500 en6port1g3500 up up normal 4 en6port1g3500 en6port1g3500 up up normal 5* controllerib12port4xddr controllerib12port4xddr up up normal Card Boot Information boot boot boot slot stage status image done success image-a:sfs_os /build626 2 done success image-a:sfs_os /build626 3 done success image-a:sfs_os /build626 4 done success image-a:sfs_os /build626 5 done success image-a:sfs_os /build626 Card Seeprom product pca pca fru slot serial-number serial-number number number 6-3

4 Bringing Up a Fibre Channel Gateway Module Chapter JAB111501C5 JAB111501C JAB111501BF JAB111501BF JAB B JAB B JAB JAB JAB111902Z1 JAB111902Z Step 5 Enter global configuration mode. Enter the card command and the slot number in which your Fibre Channel gateway resides. card 2 SFS-3504(config-card-2)# Note On the Cisco SFS 3504 Series Switch, gateways can be inserted and configured in slots 1-4 only. Step 6 Enter the no shutdown command to bring up the card. SFS-3504(config-card-2)# no shutdown SFS-3504(config-card-2)# Bringing Down a Fibre Channel Module To bring down a module, follow these steps: Step 5 Open a CLI session, and log in as a user with Fibre Channel read-write privileges. (For more information about privilege levels and access levels, see Table 2-1 on page 2-2, Privilege Levels, and Table 2-2 on page 2-2, Access Levels. ) Login: super Password: xxxxx Enter privileged EXEC mode: Identify the module to be shut down: card 2 Shut down the module. SFS-3504(config-card-2)# shutdown 6-4

5 Chapter 6 Configuring Global Policies Configuring Global Policies When you configure global policies, you create a series of default characteristics for random access devices (disks) and sequential access devices (tape). These characteristics automatically apply to all initiators, ITs, and ITLs that you add thereafter. The global policies that you configure automatically apply to every ITL series that you create after that. If you make changes to the global policies on your device, those changes do not propagate to your existing ITLs; they only apply to the new ITLs as you create them. Note Configure global policies before you configure individual initiators, ITs, and ITLs. When you add initiators, ITs, and ITLs, you can customize them on an individual basis. For example, use global policies to deny all LUN access to all new initiators, and then grant each initiator access to only the LUNs that you want them to access. Configuring Port Mask Policy Initiator access to a gateway port can be restricted or allowed. By default, the policy is restricted. If access is set to restricted, you must manually configure the port mask to allow access to the gateway port. To manually configure the port mask, perform the following steps: Configure the port mask by entering the no fc srp-global gateway-portmask-policy restricted command. Configuring ITL Policies You can choose between configuring load-balancing or failover when configuring ITL policies. You cannot use both or neither one. To configure ITL policies, perform the following steps: Enter global configuration mode. Configure load balancing to specify if SRP traffic should be load-balanced across Fibre Channel ports: fc srp-global itl dynamic-gateway-port-loadbalancing 6-5

6 Configuring Global Policies Chapter 6 Step 5 Set the port failover. One active Fibre Channel port is used for SRP traffic. If the port goes down, then another active port takes over. fc srp-global itl dynamic-gateway-port-failover Set the number of times an SRP command should be retried on the Fibre Channel side: fc srp-global itl max-retry 10 Set the timeout value, in seconds, after which a command should be retried: fc srp-global itl min-io-timeout 120 Configuring the LUN Access Policy Initiator access to LUNs is restricted (default) or allowed. If the LUN access policy for any particular ITL (or for all ITLs) is restricted, any new initiator that gets created will inherit that policy. Consequently, this initiator is able to discover new LUNs (through the discover-itl process), but it is not able to connect to any of those LUNS. For the host to access any of the discovered LUNs, you must grant individual access to any of those discovered LUNs. If the LUN access policy is not restricted, any new initiator is able to discover LUNs and connect to any or all of them without user intervention. Administrative users can restrict individual host access to any individual LUN. To configure LUN access policy, perform the following steps: Enter global configuration mode. Enter the command to set the LU policy to restricted: fc srp-global lun-policy restricted Verifying Global Policies To verify global policies, perform the following steps: Enter privileged EXEC mode: Verify the configuration, as shown in the following example: show fc srp-global SRP Global Information default-gateway-portmask-policy : restricted 6-6

7 Chapter 6 Configuring Port Parameters default-lun-policy : restricted default-itl-hi-mark : 16 default-itl-max-retry : 5 default-itl-min-io-timeout : 10 default-itl-dynamic-path-affinity : false default-itl-dynamic-gateway-port-load-balancing : true default-itl-dynamic-gateway-port-failover : false default-seq-itl-hi-mark : 1 default-seq-itl-max-retry : 1 default-seq-itl-min-io-timeout : 60 default-seq-itl-dynamic-path-affinity : false default-seq-itl-dynamic-gateway-port-load-balancing : false default-seq-itl-dynamic-gateway-port-failover : true Configuring Port Parameters This section includes the following topics: About Interop Modes, page 6-7 Setting the Interop Mode, page 6-8 Setting Domain ID, page 6-9 Setting the Connection Type, page 6-9 Setting the Port Speed, page 6-10 Configuring the Trunk Mode, page 6-12 Displaying the Current Port Settings, page 6-12 Bringing Up a Fibre Channel Port, page 6-14 Shutting Down a Fibre Channel Port, page 6-14 About Interop Modes Interoperability is the facet of an implementation where multiple vendor products come in contact with each other. Fibre Channel standards have been put into place to guide vendors toward common external Fibre Channel interfaces. The gateway ports on the Cisco SFS 3504 Server Switch interoperate with Cisco MDS, Brocade, and McData switches and support the following interoperability modes: Default or Native Interop Mode 0 This mode is a port mode that defines the default port behavior, and it is recommended for a VSAN that is communicating with a SAN composed entirely of Cisco MDS 9000 switches. Interop Mode 1 This mode is the standard interoperability mode. It interoperates with Brocade McData, and Cisco MDS switches that have been configured for their own interoperability modes. Brocade, McData, and Cisco MDS switches must be running in interop mode for them to work with this port mode. Interop Mode 2 This mode, also known as legacy switch interop mode 2, allows seamless integration with specific Brocade switches with fewer than 16 ports that are running in their own native mode of operation. Brocade switches must be configured with core pid = 0 to work with this mode. 6-7

8 Configuring Port Parameters Chapter 6 Interop Mode 3 Similar to interop mode 2, interoperability mode 3 was introduced for Brocade switches that contained more than 16 ports. With this VSAN-based interop mode, Brocade switches do not need to be altered from their native mode (core pid = 1) and can be seamlessly added to a new or existing Cisco MDS SAN-OS VSAN. This mode is also known as legacy switch interop mode 3. Interop Mode 4 This mode, also known as legacy switch interop mode 4, provides seamless integration between the Cisco SFS 3504 Fibre Channel gateway and McData switches running in McData Fabric 1.0 interop mode. For more information about interop modes, see the Cisco MDS 9000 Family Switch-to-Switch Interoperability Configuration Guide. Setting the Interop Mode When setting the Interop mode, you must shut down the port first, set the mode, and then bring up the port again. For more information about interop modes, see the About Interop Modes section on page 6-7. To set the interop mode, perform the following steps: Step 5 Step 6 Step 7 Enter the interface for which you want to set the interop mode: (config)interface fc 2/1 SFS-3504(config-if-fc-2/1)# Shut down the port: (config-if-fc-2/1)# shutdown Determine which interop modes are available: (config-if-fc-2/1)# interop? Possible interop values: 0 Native mode 1 Brocade and McData in interop mode 2 Brocade with 16 or less ports in native mode 3 Brocade with more than 16 ports in native mode 4 McData in native mode Configure the interop mode. The following example shows how to configure Native mode: SFS-3504(config-if-fc-2/1)# interop 0 Bring up the port again: (config-if-fc-2/1)# no shutdown 6-8

9 Chapter 6 Configuring Port Parameters Setting Domain ID Domain IDs should be unique across the SAN. If you are connecting to the same fabric, all gateway ports on the same module can share the same domain ID. All active VSANS on the interface use the configured domain ID. Interop Mode 0 Domain ID values are 1 to 239. Interop Mode1 Domain ID values are 97 to 127 to accommodate the McData restriction in this same range. Interop Mode 2 Domain ID values are 1 to 239. Interop Mode 3 Domain ID values are 1 to 239. Interop Mode 4 Domain ID values are 97 to 127 to accommodate the McData restriction in this same range. Setting the domain ID is mandatory, and you must follow the steps in the recommended order. To set the domain ID, follow these steps: Step 5 Enter the interface for which you want to set the domain ID: interface fc 2/1 Shut down the port: (config-if-fc-2/1)# shutdown Set the domain ID: SFS-3504(config-if-fc-2/1)# domain <id> Bring up the port again: (config-if-fc-2/1)# no shutdown Setting the Connection Type For more information about connection types, see the Topologies section on page 5-4. To set the connection type, perform the following steps: Enter the interface for which you want to set the connection type: interface fc 2/1 6-9

10 Configuring Port Parameters Chapter 6 Shut down the port: (config-if-fc-2/1)# shutdown Set the connection type. Select from the following connection types: Force E Set this type when connecting to a Fibre Channel switch. Force F Set this type when connecting direct-attached storage. Force E or F Set this type to detect the connection type. Set the connection type to Force E with the following command: SFS-3504(config-if-fc-2/1)# connection-type force-e Set the connection type to Force F with the following command: SFS-3504(config-if-fc-2/1)# connection-type force-f Set the connection type to Force E or F with the following command: SFS-3504(config-if-fc-2/1)# connection-type auto-e-or-f Step 5 Bring up the port again: (config-if-fc-2/1)# no shutdown Setting the Port Speed You can set the port speed to 1 Gbps, 2 Gbps, or 4 Gbps on a Cisco SFS 3504 Server Switch. When you set the speed, you need to set the port speed value to 1000, 2000, or Note Using the auto-negotiate command overrides the speed setting. You must disable auto-negotiation with the no auto-negotiate command to set the port speed. To set the port speed, follow these steps: Enter the interface for which you want to set the port speed: interface fc 2/1 Set the port speed: SFS-3504(config-if-fc-2/1)# speed

11 Chapter 6 Configuring Port Parameters Setting the Port VSAN By default, all ports are assigned the VSAN ID of 1. To change a port VSAN, perform the following steps: Enter the interface that you want to assign to a VSAN: interface fc 2/1 Assign the port to the VSAN: SFS-3504(config-if-fc-2/1)# vsan 20 The following output shows the assigned port VSAN: Fibre Channel Interface Information port : 2/1 name : 2/1 type : fc4gfx desc : 2/1 (129) last-change : Tue Jun 30 18:29: fc-address : 00:00:00 gateway wwnn : 20:00:00:1b:0d:00:47:05 wwpn : 20:00:00:1b:0d:00:47:15 mtu : 2048 auto-negotiate-supported : yes auto-negotiate : enabled admin-status : up oper-status : up admin-speed : 4gbps oper-speed : 2gbps admin-connection-type : force-e oper-connection-type : E-port link-trap : enabled principle switch wwnn : 20:14:00:0d:ec:0e:fd:c1 port wwnn : 00:00:00:00:00:00:00:00 distributed svc timeout : 5000 error detect timeout : 2000 fabric stability timeout : 5000 receiver xmitter timeout : 100 resource allo timeout : check age : 5 hello dead interval : 80 hello interval : 20 link state ack interval : 5 link state refresh time : 30 max age : 60 admin domain id : 20 oper domain id : 20 interop mode : 0 connection error : 0 admin port vsan : 20 oper port vsan : 20 admin trunk mode : on 6-11

12 Configuring Port Parameters Chapter 6 oper trunk mode : on Allowed Vsan List : all(1-4093) Active Vsan List : 20 Active Vsan Up List : 20 SFP State : Present SFP product id : DS-SFP-FC4G-SW SFP Vendor id : FTLF8524P2BNL-C2 SFP Vendor Serial Number : FNS111213A1 SFP CLEI Code : COUIAAHCAA SFP Cisco Part Number : SFP VID : V01 Configuring the Trunk Mode Trunking enables interconnect ports to transmit and receive frames in more than one VSAN, over the same physical link, using Extended ISL (EISL) frame format. To configure the trunk mode, perform the following steps: Enter the interface for which you want to configure the trunk mode: interface fc 2/1 Set the trunk mode. Enter the following command to set the trunk mode to on : interface fc 2/1 switchport trunk mode on Enter the following command to set the trunk mode to off : interface fc 2/1 switchport trunk mode off Enter the following command to set the trunk mode to auto : interface fc 2/1 switchport trunk mode auto Displaying the Current Port Settings To display the current port setting, perform the following steps: 6-12

13 Chapter 6 Configuring Port Parameters Display the port settings: show interface fc <slot/port> The following example shows port settings for slot 1 port 1: Fibre Channel Interface Information port : 2/1 name : 2/1 type : fc4gfx desc : 2/1 (129) last-change : Mon Jun 29 23:54: fc-address : 00:00:00 gateway wwnn : 20:00:00:1b:0d:00:47:05 wwpn : 20:00:00:1b:0d:00:47:15 mtu : 2048 auto-negotiate-supported : yes auto-negotiate : enabled admin-status : up oper-status : down admin-speed : 4gbps oper-speed : unknown admin-connection-type : force-e oper-connection-type : down link-trap : enabled principle switch wwnn : 20:01:00:1b:0d:00:47:05 port wwnn : 00:00:00:00:00:00:00:00 distributed svc timeout : 5000 error detect timeout : 2000 fabric stability timeout : 5000 receiver xmitter timeout : 100 resource allo timeout : check age : 5 hello dead interval : 80 hello interval : 20 link state ack interval : 5 link state refresh time : 30 max age : 60 admin domain id : 0 oper domain id : 0 interop mode : 0 connection error : 0 admin port vsan : 1 oper port vsan : unknown admin trunk mode : on oper trunk mode : off Allowed Vsan List : all(1-4093) Active Vsan List : none Active Vsan Up List : none SFP State : Present SFP product id : DS-SFP-FC4G-SW SFP Vendor id : FTLF8524P2BNL-C2 SFP Vendor Serial Number : FNS111213A1 SFP CLEI Code : COUIAAHCAA SFP Cisco Part Number : SFP VID : V

14 Configuring Port Parameters Chapter 6 Bringing Up a Fibre Channel Port You bring up a Fibre Channel interface port to run traffic over the port. To bring up a Fibre Channel gateway card with the CLI, perform the following steps: Open a CLI session, and log in as a user with Fibre Channel read-write privileges. (For more information about privilege levels and access levels, see Table 2-1 on page 2-2, Privilege Levels, and Table 2-2 on page 2-2, Access Levels. ) Login: super Password: xxxxx Enter the enable command to enter privileged EXEC mode: Enter the interface command with the fc keyword the slot#/port# identifier of the port to enter Fibre Channel interface configuration submode: interface fc 2/1 SFS-3504(config-if-fc-2/1)# Note On the Cisco SFS 3504 Series Switch, gateways can be inserted and configured in slots 1-4 only. Step 5 Enter the no shutdown command to bring up the card: SFS-3504(config-if-fc-2/1)# no shutdown SFS-3504(config-if-fc-2/1)# Shutting Down a Fibre Channel Port To bring down a module, perform the following steps: Open a CLI session, and log in as a user with Fibre Channel read-write privileges. (For more information about privilege levels and access levels, see Table 2-1 on page 2-2, Privilege Levels, and Table 2-2 on page 2-2, Access Levels. ) Login: super Password: xxxxx Enter privileged EXEC mode: 6-14

15 Chapter 6 Configuring Initiators, ITs, and ITLs Step 5 ure Identify the port to shut down: interface fc 2/1 Shut down the specified port: SFS-3504(config-if-fc-2/1)# shutdown Configuring Initiators, ITs, and ITLs This section includes the following topics: Creating and Configuring SRP Initiators, page 6-15 Configuring FC Targets, page 6-19 Configuring IT Pairs, page 6-20 Discovering ITLs, page 6-21 Configuring ITL Bindings, page 6-21 Creating and Configuring SRP Initiators Initiators are created using the eight-byte node GUID and the eight-byte initiator extension (currently zero on the SFS chassis). You can use the CLI to enable the switch chassis to perform all of the initiator-to-gateway port mappings for you, or you can manually configure the WWNN and WWPNs. This section includes the following topics: Performing Automatic Initiator-Port Mappings, page 6-15 Configuring Port Mappings Manually, page 6-17 Performing Automatic Initiator-Port Mappings Use the auto-bind command to enable the switch chassis to perform initiator-to-gateway port mappings. The Cisco 3504 Server Switch can accommodate Fibre Channel gateways in slots 1 through 4, with four ports for each gateway. The auto-bind command binds the new initiator to all possible ports. To allow the switch chassis to perform initiator-to gateway mappings, perform the following steps: FS-3504(config)# 6-15

16 Configuring Initiators, ITs, and ITLs Chapter 6 Enter the fc srp initiator command with the initiator GUID, followed by the auto-bind command: fc srp initiator 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 auto-bind Enter the show fc srp initiator <initiator GUID> command to verify that the initiators were created, as shown in the following example: show fc srp initiator 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 SRP Initiators guid: 01:00:00:00:00:00:00:00 extension: 00:00:00:00:00:00:00:00 description: init : wwnn: 20:05:00:1b:0d:00:ae: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: auto-bind result: success wwpns: port wwpn fc-addr vsan 1/1 20:01:00:1b:0d:00:ae:12 00:00:00 1 1/2 20:01:00:1b:0d:00:ae:12 00:00:00 1 1/3 20:01:00:1b:0d:00:ae:12 00:00:00 1 1/4 20:01:00:1b:0d:00:ae:12 00:00:00 1 2/1 20:05:00:1b:0d:00:ae:14 00:00:00 1 2/2 20:05:00:1b:0d:00:ae:14 00:00:00 1 2/3 20:05:00:1b:0d:00:ae:14 00:00:00 1 2/4 20:05:00:1b:0d:00:ae:14 00:00:00 1 3/1 20:05:00:1b:0d:00:ae:16 13:01:06 1 3/2 20:05:00:1b:0d:00:ae:16 00:00:00 1 3/3 20:05:00:1b:0d:00:ae:16 00:00:00 1 3/4 20:05:00:1b:0d:00:ae:16 00:00:00 1 4/1 20:05:00:1b:0d:00:ae:18 14:01:06 1 4/2 20:05:00:1b:0d:00:ae:18 00:00:00 1 4/3 20:05:00:1b:0d:00:ae:18 00:00:00 1 4/4 20:05:00:1b:0d:00:ae:18 00:00:00 1 The above example shows that the initiator that has been configured is automatically bound to all possible gateway ports in the chassis. 6-16

17 Chapter 6 Configuring Initiators, ITs, and ITLs Configuring Port Mappings Manually You can configure individual WWPNs for the initiator by using the CLI to suggest a unique value for the WWNN and WWPN. The process shown in this section is the manual equivalent of Performing Automatic Initiator-Port Mappings section on page To manually create SRP initiators on gateways in the Cisco SFS 3504 Server Switch, perform the following steps: Enter the fc srp initiator <Initiator-guid> <Initiator-extension> wwnn? command, as shown in the first line of the following example: fc srp initiator 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 wwnn? <wwnn> - Initiator wwnn suggested wwnn = 20:01:00:1b:0d:00:47:00 fc srp initiator 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 wwnn The output above shows that the switch chassis has suggested a WWNN for the new initiator. All WWNNs must be unique, so following the switch suggestion assures a unique WWNN. Follow the switch suggestion by entering the fc srp initiator <Initiator-guid> <Initiator-extension> wwnn command, followed by the suggested WWNN, as shown in the following example: fc srp initiator 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 wwnn 20:01:00:1b:0d:00:47:00 Verify that the WWNN has been created by entering the show fc srp initiator <Initiator-guid> <Initiator-extension> command, as shown in the following example: show fc srp initiator 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 SRP Initiators guid: 01:00:00:00:00:00:00:00 extension: 00:00:00:00:00:00:00:00 description: init : wwnn: 20:01:00:1b:0d:00:47: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 The preceding example shows that a new initiator has been created but not bound to any gateway ports. 6-17

18 Configuring Initiators, ITs, and ITLs Chapter 6 Step 5 Bind this new initiator with one or more gateway ports by assigning a World Wide Port Name and a VSAN to the initiator so that the initiator can gain access to the Fibre Channel fabric. Enter the fc srp initiator-wwpn <Initiator-guid> <Initiator-extension> <slot/port> <WWPN> [vsan <VSAN ID] command, as shown in the following example that binds the initiator to gateway port 1/1: fc srp initiator-wwpn 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 1/1? <wwpn> - wwpn suggested wwpn = 20:01:00:1b:0d:00:ae:12 fc srp initiator-wwpn 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 1/1 The example above shows that the server switch suggests a unique WWPN value for this initiator, as is did for the WWNN in. Note In the Cisco 3504 Server Switch, each initiator needs a unique WWPN per gateway, and port 1 of each gateway must be assigned a WWPN. These Cisco 3504 gateway WWPN assignments are different from those a Cisco SFS 3012 Server Switch, in which each port has a unique WWPN. Step 6 Follow the switch suggestion by entering the fc srp initiator-wwpn <Initiator-guid> <Initiator-extension> <slot/port> <WWPN> [vsan <VSAN ID] command, as shown in the following example: fc srp initiator-wwpn 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 1/1 20:01:00:1b:0d:00:47:00 Step 7 Verify the configuration by entering the show fc srp initiator <Initiator-guid> <Initiator-extension> command, as shown in the following example: show fc srp initiator 01:00:00:00:00:00:00:00 00:00:00:00:00:00:00:00 SRP Initiators guid: 01:00:00:00:00:00:00:00 extension: 00:00:00:00:00:00:00:00 description: init : wwnn: 20:01:00:1b:0d:00:47: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 1/1 20:01:00:1b:0d:00:ae:12 00:00:00 1 1/2 20:01:00:1b:0d:00:ae:12 00:00:00 1 1/3 20:01:00:1b:0d:00:ae:12 00:00:00 1 1/4 20:01:00:1b:0d:00:ae:12 00:00:

19 Chapter 6 Configuring Initiators, ITs, and ITLs Step 8 Step 9 Exit configuration mode: exit Verify the initiator configuration by entering the show fc srp initiator <Initiator-guid> <Initiator-extension> command, as shown in the following example: show fc srp initiator <Initiator-guid> <Initiator-extension> show fc srp initiator 00:05:ad:00:00:03:02:20 00:00:00:00:00:00:00:00 SRP Initiators guid: 00:05:ad:00:00:03:02:20 extension: 00:00:00:00:00:00:00:00 description: linux-vs-1/1 wwnn: 2f:fe:00:05:ad:01:81:48 credit: 0 active-ports: 2/3 pkeys: bootup-target: 50:06:0e:80:00:43:3c:00 bootup-lu: 00:16: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 vsan 2/1 2f:fe:00:05:ad:05:81:48 00:00:00 1 2/2 2f:fe:00:05:ad:05:81:48 00:00:00 1 2/3 2f:fe:00:05:ad:05:81:48 64:03:03 1 2/4 2f:fe:00:05:ad:05:81:48 00:00:00 1 Configuring FC Targets Normally, targets are auto detected from the fabric. If you need to configure a target, use the fc srp target command. To configure a target, perform the following steps: Enter the fc srp target <WWPN> ioc-guid <guid> command: fc srp target 20:02:00:20:c2:06:18:13 ioc-guid 00:1b:0d:00:00:00:47:a4 6-19

20 Configuring Initiators, ITs, and ITLs Chapter 6 Verify the configuration by entering the show fc srp target command in user EXEC mode. If your target shows up in the command output, the configuration succeeded. show fc srp target SRP Targets wwpn: 20:02:00:20:c2:06:18:13 wwnn: 00:00:00:00:00:00:00:00 description: SRP.T10: C ioc-guid: 00:1b:0d:00:00:00:47:a4 service-name: SRP.T10: C protocol-ids: 00:00:00:00:00:00:00:00:00:00 fc-address: b0:00:01 mtu: 0 connection-type: down physical-access: 2/1 vsan: 20 Configuring IT Pairs If a WWPN has been assigned to an initiator, and some ports are active, then targets will be discovered. Once targets are discovered, IT pairs are automatically created based on the zoning in the fabric. However, you can create an IT pair manually. To configure an IT pair and to configure an individual port masking policy for a particular IT, perform the following steps: Configure the IT pair by entering the fc srp it <initiator-guid> <initiator-extension> <target-wwpn> command, as shown in the following example: fc srp it 00:05:ad:00:00:00:22:48 00:00:00:00:00:00:00:00 21:01:00:20:c2:03:31:99 Set the port mask for the IT pair by entering the fc srp it <initiator-guid> <initiator-extension> <target-wwpn> gateway-portmask-policy restricted <port/slot> command, as shown in the following example: fc srp it 00:05:ad:00:00:00:22:48 00:00:00:00:00:00:00:00 21:01:00:20:c2:03:31:99 gateway-portmask-policy restricted 2/1-2/2 6-20

21 Chapter 6 Configuring Initiators, ITs, and ITLs Verify your IT configurations by entering the show fc srp it <initiator-guid> <initiator-extension> <target wwpn> command, as shown in the following example: show fc srp it 00:05:ad:00:00:00:22:48 00:00:00:00:00:00:00:00 21:01:00:20:c2:03:31:99 SRP IT guid: 00:05:ad:00:00:00:22:48 extension: 00:00:00:00:00:00:00:00 target-wwpn: 21:01:00:20:c2:03:31:99 description: it non-restricted-ports: 2/1-2/4,3/1-3/4 active-ports: 2/1-2/2 physical-access: 2/1-2/2 mode: normal-mode action: none result: none Total: 1 its. Discovering ITLs To discover ITLs, perform the following steps: Enter the fc srp initiator discover-itl command in the following format: fc srp initiator <initiator-guid> <initiator-extension> discover-itl Configuring ITL Bindings ITL bindings are automatically created when you enter the discover-itl command. To configure an ITL binding and to configure the LUN policy for an individual ITL, perform the following steps: Enter the fc srp itl command in this format: fc srp itl <initiator-guid> <initiator-extension> <target-wwpn> <FC-lu-id> <srp-lu-id> 6-21

22 Configuring Initiators, ITs, and ITLs Chapter 6 Return to user EXEC mode: exit Verify the configuration: show fc srp itl 00:05:ad:00:00:00:22:48 00:00:00:00:00:00:00:00 21:01:00:20:c2:03:31:99 SRP ITL guid: 00:05:ad:00:00:00:22:48 extension: 00:00:00:00:00:00:00:00 target-wwpn: 21:01:00:20:c2:03:31:99 fc-lunid: 00:02:00:00:00:00:00:00 srp-lunid: 00:00:00:00:00:00:00:02 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:32: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 FC description: itl device-category: random lun-policy: non restricted non-restricted-ports: 2/1-2/4,3/1-3/4 active-ports: 2/1-2/2 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: