Cisco SN 5420 Storage Router Software Configuration Guide, Release 2.1
Chapter 5 - Configuring SCSI Routing
Downloads: This chapterpdf (PDF - 286.0KB) The complete bookPDF (PDF - 4.58MB) | Feedback

Configuring SCSI Routing

Table Of Contents

Configuring SCSI Routing

Prerequisite Tasks

Configuration Tasks

Creating a SCSI Routing Instance

Configuring a Server Interface

Configuring a Device Interface

Configuring iSCSI Targets

Configuring an Access List

Configuring Access

Verifying and Saving Configuration


Configuring SCSI Routing


This chapter explains how to configure your SN 5420 Storage Router for SCSI routing and contains the following sections:

Prerequisite Tasks

Configuration Tasks

Creating a SCSI Routing Instance

Configuring a Server Interface

Configuring a Device Interface

Configuring iSCSI Targets

Configuring an Access List

Configuring Access

Verifying and Saving Configuration

SCSI routing can be configured using CLI commands, as described in this chapter, or via the web-based GUI. To access the web-based GUI, point your browser to the storage router's management interface IP address. After logging on, click the Help link to access online help for the GUI.

Prerequisite Tasks

Before configuring SCSI routing, make sure you have configured all system parameters as described in "First-Time Configuration," or "Configuring System Parameters."

If the VLAN service is to be used with the SN 5420 Storage Router, configure VLANs as described in "Configuring for VLAN," before proceeding.

Configuration Tasks

To configure SCSI routing on your SN 5420 Storage Router, perform the following steps:


Step 1 Create a SCSI routing instance. Once an instance is created, you will configure that instance with parameters for a server interface, a device interface, iSCSI targets, and access by IP hosts and FC server instances.


Note A single FC server instance exists on an SN 5420 deployed for iSCSI SAN interconnect. The FC server instance is allowed access to storage devices via a SCSI routing instance configured in a remote SN 5420 deployed for SCSI routing. For more information on iSCSI SAN interconnect, see the "iSCSI SAN Interconnect Overview" section in "Before Configuring SN 5420 Storage Router Software."


Step 2 Configure the server interface with or without VLAN.

Step 3 Configure the device interface.

Step 4 Configure iSCSI targets.

Step 5 (Optional) Configure an access list defining which IP hosts and FC server instances can access iSCSI targets configured as part of a SCSI routing instance. An access list is necessary if you want to specify access to iSCSI targets on a per-IP host (and FC server instance) basis. An access list is not necessary if you want to specify that all IP hosts and FC server instances have access to the iSCSI targets configured in a SCSI routing instance.

Step 6 Configure access. This determines which IP hosts and FC server instances can access the iSCSI targets configured as part of a SCSI routing instance.

Step 7 Verify and save configuration.


Note Although this is shown as the last step, you can verify and save the configuration at any point in the process of performing the configuration tasks. Save your configuration by using the save all bootconfig CLI command. This command saves all configuration data to the bootable configuration, which is then used when the storage router is rebooted.




Caution When making changes to a SCSI routing instance (such as adding or deleting targets or changing access) be sure to make the complementary changes to the iSCSI driver configuration of IP hosts that use that SCSI routing instance to access the storage resources. See the readme files for the appropriate iSCSI drivers for additional details. (You can access the latest iSCSI drivers and readme and example configuration files from Cisco.com.)

Figure 5-1 illustrates SCSI routing configuration elements, and Figure 5-2 illustrates the example configuration used in this chapter. Figure 5-3 illustrates how the configuration of SCSI routing instances determines VLAN access to storage devices.

Figure 5-1 Configuration Elements for SCSI Routing

Figure 5-2 SCSI Routing Parameters Example Configuration

Figure 5-3 Configuration of SCSI Routing Instance Determines VLAN Access to Storage Devices

Creating a SCSI Routing Instance

Creating a SCSI routing instance consists of naming the new instance. Use the following procedure to create a SCSI routing instance.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus

Create a SCSI routing instance by naming the new instance (zeus).

Note You can define up to 12 instances on a single SN 5420 or across a cluster. For additional details about configuring SN 5420 clusters for high availability, see "Configuring a Storage Router Cluster."

Configuring a Server Interface

Configuring a server interface consists of assigning a server interface along with an IP address and subnet mask to the desired SCSI routing instance. If the SN 5420 is to be used with VLAN, specify the VLAN by its VID.

Without VLAN

Use the following procedure to configure a server interface for a SCSI routing instance.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus serverif ge2 10.1.0.45/24

Assign a server interface (ge2) to the desired SCSI routing instance (zeus). Specify the IP address and subnet mask (10.1.0.45/24) that IP hosts and FC server instances will use to access the SCSI routing instance. In this example, the subnet mask of 255.255.255.0 was set using CIDR style (/24).

With VLAN

Use the following procedure to assign a server interface and VLAN to a SCSI routing instance.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus serverif ge2 vlan 100 10.1.0.45/24

Assign a VLAN, identified by its VID (100), to the desired SCSI routing instance (zeus). Specify the server interface (ge2) and the IP address and subnet mask (10.1.0.45/24) that the VLAN will use to access the SCSI routing instance. In this example, the subnet mask of 255.255.255.0 was set using CIDR style (/24).

Note To look up the VID, use the show vlan command. VIDs are listed in the VLAN column.

Configuring a Device Interface

Configuring a device interface consists of assigning a device interface to the desired SCSI routing instance and specifying the topology of that device interface. Use the following procedure to configure a device interface for a SCSI routing instance.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus deviceif fc1

Assign a device interface (fc1) to the desired SCSI routing instance (zeus). This is the interface on the storage router that the specified SCSI routing instance will use to access physical storage devices.

Step 3 

interface fc1 topology ptppref

or

interface fc1 topology loop

or

interface fc1 topology ptp

(Optional) Specify the topology of the device interface. By default, the device interface topology setting is configured as looppref, which sets a preference for loop topology. If the device interface does not accept the attempt to establish loop activation, point-to-point topology is assumed.

If you wish to set a preference for point-to-point topology, change the topology to ptppref, as shown in the first example.

If all storage devices are connected to a hub with the intention of running in an arbitrated loop, change the topology to loop, as shown in the second example.

If all storage devices are connected in a point-to-point topology, change the topology to ptp, as shown in the third example.

Step 4 

save all bootconfig

Save your configuration to the bootable configuration, which is then used when the storage router is rebooted.

Step 5 

reboot

Reboot the storage router. A reboot is necessary to make the new topology selection effective.

Once the device interface is added, the SCSI routing instance becomes active.

Configuring iSCSI Targets

Configuring iSCSI targets consists of specifying the SCSI routing instance to which an iSCSI target is to be assigned, specifying the iSCSI target, and mapping the iSCSI target to a physical storage device. When assigning an iSCSI target, you can specify the physical storage device either by physical storage address, serial number, or by an index number assigned to the device.


Note When a new iSCSI target is configured, IP hosts and FC server instances do not have access to it. You need to configure access to newly created iSCSI targets according to the "Configuring Access" section later in this chapter.


Use the procedures that follow according to mapping type and storage addressing type:

Target-and-LUN mapping using LoopID addressing

Target-and-LUN mapping using WWPN addressing

Target-and-LUN mapping using LUNWWN addressing

Target-and-LUN mapping using Serial Number addressing

Target-only mapping using LoopID addressing

Target-only mapping using WWPN addressing

Target-and-LUN mapping using LoopID addressing

Use the following procedure to map iSCSI targets to storage devices by physical storage address.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_email lun 23 loopid 15 lun 0

Specify desired SCSI routing instance (zeus). Specify iSCSI target (chimaera_email) and LUN (23), and map it to a physical address (LoopID 15, LUN 0).

Use the following procedure to map iSCSI targets to storage devices by an index number.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_email lun 23 loopid #?

Specify desired SCSI routing instance (zeus). Specify iSCSI target (chimaera_email) and LUN (23), and prompt for an indexed list of available storage addresses using the number sign and a question mark (#?).

Step 3 

scsirouter zeus target chimaera_email lun 23 loopid #5

Select a physical address designated by an index number (see index number 5 in Example 5-1) to map the iSCSI target (chimaera_email) and LUN (23) combination to the desired physical address (LoopID 15, LUN 0).

Example 5-1 Indexed List of Storage Devices

id         lunwwn          wwpn     loopid lun  vendor    product
         serial number
  1: 20000020371912d5 22000020371912d5   8   0 SEAGATE  ST318451FC 
     LS099969000019511C2H
  2: 20000020371912da 22000020371912da   9   0 SEAGATE  ST318451FC 
     LS097776000019511C3B
  3: 200000203719129d 220000203719129d  10   0 SEAGATE  ST318451FC 
     LS101990000019411NGQ
  4: 2000002037191505 2200002037191505  12   0 SEAGATE  ST318451FC 
     LS092288000019512N3V
  5: 20000020371912b2 22000020371912b2  15   0 SEAGATE  ST318451FC 
     LS099843000019430RC7
  6: 200000203719152e 220000203719152e   7   0 SEAGATE  ST318451FC 
     LS093221000019451JM5

Target-and-LUN mapping using WWPN addressing

Use the following procedure to map iSCSI targets to storage devices by physical storage address.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_apps lun 24 wwpn 22:00:00:20:37:19:15:05 lun 0

Specify desired SCSI routing instance (zeus). Specify iSCSI target (chimaera_apps) and LUN (24), and map it to the desired physical address (WWPN 22:00:00:20:37:19:15:05 LUN 0).

Use the following procedure to map iSCSI targets to storage devices by an index number.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_apps lun 31 wwpn #?

Specify desired SCSI routing instance (zeus). Specify iSCSI target (chimaera_apps) and LUN (31), and prompt for an indexed list of available storage addresses using the number sign and a question mark (#?).

Step 3 

scsirouter zeus target chimaera_apps lun 31 wwpn #4

Choose a physical address designated by an index number (see index number 4 in Example 5-1) to map the iSCSI target (chimaera_apps) and LUN (31) combination to the desired physical address (WWPN 22:00:00:20:37:19:15:05, LUN 0).

Target-and-LUN mapping using LUNWWN addressing

Use the following procedure to map iSCSI targets to storage devices by physical storage address.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_eng lun 17 lunwwn 22:00:00:20:37:19:12:9d

Specify desired SCSI routing instance (zeus). Specify iSCSI target (chimaera_eng) and LUN (17), and map it to the desired physical address (LUNWWN 22:00:00:20:37:19:12:9d).

Use the following procedure to map iSCSI targets to storage devices by an index number.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_eng lun 17 lunwwn #?

Specify desired SCSI routing instance (zeus). Specify iSCSI target (chimaera_eng) and LUN (17), and prompt for an indexed list of available storage addresses using the number sign and a question mark (#?).

Step 3 

scsirouter zeus target chimaera_eng lun 17 lunwwn #3

Choose a physical address designated by an index number (see index number 3 in Example 5-1) to map the iSCSI target (chimaera_eng) and LUN (17) combination to the desired physical address (LUNWWN 22:00:00:20:37:19:12:9d)

Target-and-LUN mapping using Serial Number addressing

Use the following procedure to map iSCSI targets to storage devices by serial number.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target pegasus_web lun 3 serial LS093221000019451JM5

Specify desired SCSI routing instance (zeus). Specify iSCSI target (pegasus_web) and LUN (3), and map it to the desired physical address (serial number LS093221000019451JM5).

Use the following procedure to map iSCSI targets to storage devices by an index number.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target pegasus_web lun 3 serial #?

Specify desired SCSI routing instance (zeus). Specify iSCSI target (pegasus_web) and LUN (3), and prompt for an indexed list of available storage addresses using the number sign and a question mark (#?).

Step 3 

scsirouter zeus target pegasus_web lun 3 serial #

Choose a physical address designated by an index number (see index number 6 in Example 5-1) to map the iSCSI target (pegasus_web) and LUN (3) combination to the desired physical address (serial number LS093221000019451JM5)

Target-only mapping using LoopID addressing

Use the following procedure to map iSCSI targets to storage devices by physical storage address.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target pegasus_dbase loopid 8

Specify desired SCSI routing instance (zeus). Specify iSCSI target (pegasus_dbase), and map it to the desired physical address (LoopID 8) and any LUNs available as part of that LoopID.

Use the following procedure to map iSCSI targets to storage devices by index numbers.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target pegasus_dbase loopid #?

Specify desired SCSI routing instance (zeus). Specify iSCSI target (pegasus_dbase), and prompt for an indexed list of available storage addresses using the number sign and a question mark (#?).

Step 3 

scsirouter zeus target pegasus_dbase loopid #1

Choose a physical address designated by an index number (see index number 1 in Example 5-1) to map the iSCSI target (pegasus_dbase) to the desired physical address (LoopID 8, LUN 0).

Target-only mapping using WWPN addressing

Use the following procedure to map iSCSI targets to storage devices by physical storage address.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target pegasus_email wwpn 22:00:00:20:37:19:12:da

Specify desired SCSI routing instance (zeus). Specify iSCSI target (pegasus_email), and map it to the desired physical address (WWPN 22:00:00:20:37:19:12:da) and any LUNs available as part of that WWPN.

Use the following procedure to map iSCSI targets to storage devices by index numbers.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target pegasus_email wwpn #?

Specify desired SCSI routing instance (zeus). Specify iSCSI target (pegasus_email), and prompt for an indexed list of available storage addresses using the number sign and a question mark (#?).

Step 3 

scsirouter zeus target pegasus_email wwpn #2

Choose a physical address designated by an index number (see index number 2 in Example 5-1) to map the iSCSI target (pegasus_email) to desired physical address (WWPN (22:00:00:20:37:19:12:da).

Configuring an Access List

Configuring an access list consists of creating an accesslist by naming it and specifying the IP addresses of IP hosts and FC server instances that have permission to access storage devices via iSCSI target names. An access list is necessary if you want to specify access to iSCSI targets on a per-IP host (and FC server instance) basis. An access list is not necessary if you want to specify that all IP hosts and FC server instances have access to the iSCSI targets configured in a SCSI routing instance.

Use the following procedure to configure an access list.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

accesslist aegis

Create an access list by naming it (aegis). There is a 31 character limit.

Step 3 

accesslist aegis description "Access to zeus SCSI routing service"

(Optional) Add a string as a description for the access list. Enclose the string using single or double quotes.

Step 4 

accesslist aegis 10.2.0.23/32 10.3.0.36/32 10.4.0.49/32

Add IP addresses of IP hosts and FC server instances to the access list. Separate multiple IP addresses with a space. To limit the access to each IP address, set the subnet mask to 255.255.255.255. In this example, the subnet mask was set using CIDR style (/32).


Note In a cluster environment, all access lists must be created and maintained on the first storage router to join the cluster. If you issue the accesslist commands from another storage router in the cluster, the CLI displays an informational message with the IP address of the storage router that is currently handling all access list functions. For more information on operating the SN 5420 in a cluster, see "Maintaining and Managing the Storage Router."


Configuring Access

Configuring access consists of specifying which iSCSI targets can be accessed by IP hosts and FC server instances. When configuring access, you can specify one iSCSI target at a time or all iSCSI targets. Similarly, you can specify one access list at a time or all IP hosts and FC server instances using a SCSI routing instance. In addition, you can deny access to iSCSI targets one at a time or all at once.

The default for access to newly configured iSCSI targets is none. You must configure access according to the information provided in this section.


Note In a cluster environment, all access lists must be created and maintained on the first storage router to join the cluster. If you issue the accesslist commands from another storage router in the cluster, the CLI displays an informational message with the IP address of the storage router that is currently handling all access list functions. For more information on operating the SN 5420 in a cluster, see "Maintaining and Managing the Storage Router."


Use the procedures that follow according to the type of access:

Access an iSCSI target by IP hosts and FC server instances identified in an access list

Access an iSCSI target by all IP hosts and FC server instances

Access all iSCSI targets by IP hosts and FC server instances identified in an access list

Access all iSCSI targets by all IP hosts and FC server instances

Access denied to one iSCSI target

Access denied to all iSCSI targets

Access an iSCSI target by IP hosts and FC server instances identified in an access list

Use the following procedure to specify one iSCSI target at a time to be accessible by IP hosts and FC server instances listed in an access list.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_email accesslist aegis

Specify that an iSCSI target (chimaera_email), configured as part of a SCSI routing instance (zeus), can be accessed by IP hosts and FC server instances listed in an access list (aegis).

Access an iSCSI target by all IP hosts and FC server instances

Use the following procedure to specify one iSCSI target at a time to be accessible by all IP hosts and FC server instances.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_apps accesslist all

Specify that an iSCSI target (chimaera_apps), configured as part of a SCSI routing instance (zeus), can be accessed by all IP hosts and FC server instances.

Access all iSCSI targets by IP hosts and FC server instances identified in an access list

Use the following procedure to specify all iSCSI targets to be accessible by IP hosts and FC server instances listed in an access list.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target all accesslist aegis

Specify that all iSCSI targets that were configured as part of the specified SCSI routing instance (zeus) can be accessed by IP hosts and FC server instances listed in an access list (aegis).

Access all iSCSI targets by all IP hosts and FC server instances

Use the following procedure to specify all iSCSI targets to be accessible by all IP hosts and FC server instances.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target all accesslist all

Specify that all iSCSI targets that were configured as part of the specified SCSI routing instance (zeus) can be accessed by all IP hosts and FC server instances.

Access denied to one iSCSI target

Use the following procedure to deny access by IP hosts and FC server instances to one iSCSI target at a time.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target chimaera_apps accesslist none

Specify that no IP host or FC server instance can access the iSCSI target (chimaera_apps), configured as part of the specified SCSI routing instance (zeus).

Access denied to all iSCSI targets

Use the following procedure to deny access by all IP hosts and FC server instances to all iSCSI targets at once.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

scsirouter zeus target all accesslist none

Specify that no IP hosts and FC server instances can access any iSCSI targets that were configured as part of the specified SCSI routing instance (zeus).

Verifying and Saving Configuration

Verify the access list configuration and the SCSI routing configuration using the procedures that follow. You can save the configuration at any time by using the save all bootconfig command. You must save the running configuration to the bootable configuration for it to be retained in the storage router when it is rebooted. Once you have saved the configuration, you can verify that the configuration to be used when the storage router is rebooted matches the currently running configuration.

Use the following procedure to verify access list configuration.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

show accesslist

Display a list of all existing access lists (Example 5-2).

Step 3 

show accesslist aegis

Display the IP addresses of IP hosts and FC server instances in an access list (Example 5-3).

Example 5-2 Verifying Existence of an Access List

[SN5420]# show accesslist
aegis
hris-mgmt

Example 5-3 Verifying IP Addresses in an Access List Named aegis

[SN5420]# show accesslist aegis
accesslist aegis description "Access to zeus SCSI routing service"
accesslist aegis 10.2.0.23/32
accesslist aegis 10.3.0.36/32
accesslist aegis 10.4.0.49/32


Use the following procedure to verify the configuration of a SCSI routing instance.

 
Command
Description

Step 1 

enable

Enter Administrator mode.

Step 2 

show scsirouter zeus

Display the parameters configured for the specified SCSI routing instance (Example 5-4).

Example 5-4 Verifying Configuration for a SCSI Routing Instance

[SN5420]# show scsirouter zeus
zeus description "(not set)"
zeus authenticate "none"
zeus primary "none"
zeus proxy server disabled
Failover Primary Node is not set
Failover Secondary Node is not set
zeus target naming authority "none"
zeus target log level is "notification"
zeus serverif ge2 10.1.0.45/24
zeus deviceif fc1 
zeus target chimaera_email description "(not set)"
zeus target chimaera_email WWUI "iqn.1987-05.com.cisco.00.f51a39962a9735e52770eca71f4cf14f.chimaera_email"
zeus target chimaera_email enabled "TRUE" 
zeus target chimaera_email accesslist "aegis" 
zeus target chimaera_email lun 23 loopid "15" lun "0" 
zeus target chimaera_apps description "(not set)"
zeus target chimaera_apps WWUI "iqn.1987-05.com.cisco.00.f163299abf291d7e6791675c67226e40.chimaera_apps"
zeus target chimaera_apps enabled "TRUE" 
zeus target chimaera_apps accesslist "none" 
zeus target chimaera_apps lun 24 wwpn "22:00:00:20:37:19:15:05" lun "0" 
zeus target chimaera_eng description "(not set)"
zeus target chimaera_eng WWUI "iqn.1987-05.com.cisco.00.f1a367809af3ef49fc16645bbb8c7036.chimaera_eng"
zeus target chimaera_eng enabled "TRUE" 
zeus target chimaera_eng accesslist "aegis" 
zeus target chimaera_eng lun 17 lunwwn "22:00:00:20:37:19:12:9d" 
zeus target pegasus_web description "(not set)"
zeus target pegasus_web WWUI "iqn.1987-05.com.cisco.00.7c7e0aafc74273168d4eab679ab19ac8.pegasus_web"
zeus target pegasus_web enabled "TRUE" 
zeus target pegasus_web accesslist "none" 
zeus target pegasus_web lun 3 serial "LS093221000019451JM5" 
zeus target pegasus_dbase description "(not set)"
zeus target pegasus_dbase WWUI "iqn.1987-05.com.cisco.00.4c988b45621a135b331b6cf3279010b9.pegasus_dbase"
zeus target pegasus_dbase enabled "TRUE" 
zeus target pegasus_dbase accesslist "hris-mgmt" 
zeus target pegasus_dbase loopid "8" 
zeus target pegasus_email description "(not set)"
zeus target pegasus_email WWUI "iqn.1987-05.com.cisco.00.3dd747e7c7d358de7625af51a1c8d4d6.pegasus_email"
zeus target pegasus_email enabled "TRUE" 
zeus target pegasus_email accesslist "all" 
zeus target pegasus_email wwpn "22:00:00:20:37:19:12:da"