- Device Manager Help
- Configuring Cisco DCNM-SAN Server
- Configuring Authentication in Cisco DCNM-SAN
- Configuring Cisco DCNM-SAN Client
- Device Manager
- Configuring Performance Manager
- Configuring High Availability
- Configuring Trunking
- Configuring PortChannels
- Configuring N Port Virtualization
- Configuring Interfaces
- Configuration of Fibre Channel Interfaces
- Using the CFS Infrastructure
- Configuring SNMP
- Configuring Domain Parameters
- Configuring and Managing Zones
- Configuring FCoE
- Configuring Dense Wavelength Division Multiplexing
- Configuring and Managing VSANs
- Discovering SCSI Targets
- Configuring SAN Device Virtualization
- Configuring Fibre Channel Routing Services and Protocols
- Managing FLOGI, Name Server, FDMI, and RSCN Databases
- Configuring FICON
- Creating Dynamic VSANs
- Distributing Device Alias Services
- Configuring Advanced Fabric Features
- Configuring Users and Common Role
- Configuring Security Features on an External AAA Server
- Configuring Certificate Authorities and Digital Certificates
- Configuring FC-SP and DHCHAP
- Configuring Cisco TrustSec Fibre Channel Link Encryption
- Configuring FIPS
- Configuring IPv4 and IPv6 Access Control Lists
- Configuring IPsec Network Security
- Configuring Port Security
- Configuring Fabric Binding
- Configuring FCIP
- Configuring the SAN Extension Tuner
- Configuring iSCSI
- Configuring IP Services
- Configuring IP Storage
- Configuring IPv4 for Gigabit Ethernet Interfaces
- Configuring IPv6 for Gigabit Ethernet Interfaces
- Configuring SCSI Flow Services
- Configuring SCSI Flow Statistics
- Configuring Fibre Channel Write Acceleration
- Monitoring the Network
- Monitoring Performance
- Configuring Call Home
- Configuring System Message Logging
- Scheduling Maintenance Jobs
- Configuring RMON
- Configuring Fabric Configuration Server
- Monitoring Network Traffic Using SPAN
- Monitoring System Processes and Logs
- Configuring QoS
- Configuring Port Tracking
- Configuring FlexAttach Virtual pWWN
- Configuring Interface Buffers
- Verifying Ethernet Interfaces
Configuring the SAN Extension Tuner
The SAN Extension Tuner (SET) feature is unique to the Cisco MDS 9000 Family of switches. This feature helps you optimize FCIP performance by generating either direct access (magnetic disk) or sequential access (magnetic tape) SCSI I/O commands and directing such traffic to a specific virtual target. You can specify the size of the test I/O transfers and how many concurrent or serial I/Os to generate while testing. The SET reports the resulting I/Os per second (IOPS) and I/O latency, which helps you determine the number of concurrent I/Os needed to maximize FCIP throughput.
Information About the SAN Extension Tuner
The SAN extension tuner (SET) feature is unique to the Cisco MDS 9000 Family of switches. This feature helps you optimize FCIP performance by generating either direct access (magnetic disk) or sequential access (magnetic tape) SCSI I/O commands and directing such traffic to a specific virtual target. Applications such as remote copy and data backup use FCIP over an IP network to connect across geographically distributed SANs. SET is implemented in IPS ports. When enabled, this feature can be used to generate SCSI I/O commands (read and write) to the virtual target based on your configured options.
Note SAN Extension Tuner is not supported on the Cisco Fabric Switch for HP c-Class BladeSystem, the Cisco Fabric Switch for IBM BladeCenter, and 16-Port Storage Services Node (SSN-16).
Note As of Cisco MDS SAN-OS Release 3.3(1a), SAN Extension Tuner is supported on the Multiservice Module (MSM) and the Multiservice Modular Switch.
Applications such as remote copy and data backup use FCIP over an IP network to connect across geographically distributed SANs. To achieve maximum throughput performance across the fabric, you can tune the following configuration parameters:
- The TCP parameters for the FCIP profile.
- The number of concurrent SCSI I/Os generated by the application.
- The transfer size used by the application over an FCIP link.
SET is implemented in IPS ports. When enabled, this feature can be used to generate SCSI I/O commands (read and write) to the virtual target based on your configured options (see Figure 39-1).
Figure 39-1 SCSI Command Generation to the Virtual Target
The SET feature assists with tuning by generating varying SCSI traffic workloads. It also measures throughput and response time per I/ O over an FCIP link.
Before tuning the SAN fabric, be aware of the following guidelines:
– The tuned configuration is not persistent.
– The virtual N ports created do not register FC4 features supported with the name server. This is to avoid the hosts in the SAN from discovering these N ports as regular initiators or targets.
– Login requests from other initiators in the SAN are rejected.
– The virtual N ports do not implement the entire SCSI suite; it only implements the SCSI read and write commands.
– Tuner initiators can only communicate with tuner targets.
- Verify that the Gigabit Ethernet interface is up at the physical layer (GBIC and Cable connected—an IP address is not required).
- Enable iSCSI on the switch (no other iSCSI configuration is required).
- Enable the interface (no other iSCSI interface configuration is required)
See “Creating iSCSI Interfaces” section for more information.
- Create an iSCSI interface on the Gigabit Ethernet interface and enable the interface (no other iSCSI interface configuration is required)
see “Creating iSCSI Interfaces” section for more information.
- Configure the virtual N ports in a separate VSAN or zone as required by your network.
- Be aware that a separate VSAN with only virtual N ports is not required, but is recommended as some legacy HBAs may fail if logins to targets are rejected.
- Do not use same Gigabit Ethernet interface to configure virtual N ports and FCIP links—use different Gigabit Ethernet interfaces. While this is not a requirement, it is recommended as the traffic generated by the virtual N ports may interfere with the performance of the FCIP link.
This section includes the following topics:
SAN Extension Tuner Setup
Figure 39-2 provides a sample physical setup in which the virtual N ports are created on ports that are not a part of the FCIP link for which the throughput and latency is measured.
Figure 39-2 N Port Tuning Configuration Physical Example
Figure 39-3 provides a sample logical setup in which the virtual N ports are created on ports that are not a part of the FCIP link for which the throughput and latency is measured.
Figure 39-3 Logical Example of N Port Tuning for a FCIP Link
Data Pattern
By default, an all-zero pattern is used as the pattern for data generated by the virtual N ports. You can optionally specify a file as the data pattern to be generated by selecting a data pattern file from one of three locations: the bootflash: directory, the volatile: directory, or the slot0: directory. This option is especially useful when testing compression over FCIP links. You can also use Canterbury corpus or artificial corpus files for benchmarking purposes.
Licensing Requirements for SAN Extension Tuner
To use the SET, you need to obtain the SAN_EXTN_OVER_IP license (see the Cisco Family NX-OS Licensing Guide).
The following table shows the licensing requirements for this feature:
Default Settings
Table 39-1 lists the default settings for tuning parameters.
Configuring the SAN Extension Tuner
This section includes the following topics:
- Tuning the FCIP Link
- Using the SAN Extension Tuner Wizard
- Enabling the Tuner
- Configuring nWWN
- Configuring the Virtual N Port
- Assigning the SCSI Read/Write
- Assigning SCSI Tape Read/Write
- Configuring a Data Pattern
Tuning the FCIP Link
To tune the required FCIP link, follow these steps:
Step 1 Configure the nWWN for the virtual N ports on the switch.
Step 2 Enable iSCSI on the interfaces on which you want to create the N ports.
Step 3 Configure the virtual N ports on either side of the FCIP link.
Step 4 Ensure that the virtual N ports are not visible to real initiators in the SAN. You can use zoning (see the Fabric Configuration Guide, Cisco DCNM for SANCisco MDS 9000 Family NX-OS Fabric Configuration Guide) to segregate the real initiators. Ensure that the zoning configuration is set up to allow the virtual N-ports to communicate with each other.
Step 5 Start the SCSI read and write I/Os.
Step 6 Add more N ports (as required) to other Gigabit Ethernet ports in the switch to obtain maximum throughput. One scenario that may require additional N ports is if you use FCIP PortChannels.
Using the SAN Extension Tuner Wizard
You can use the SAN Extension Tuner wizard to perform the these tasks:
- Configuring nWWN ports
- Enabling iSCSI
- Configuring Virtual N ports
- Assigning SCSI read and write CLI commands
- Assigning SCSI tape read and write CLI commands
- Configuring a data pattern for SCSI commands
To tune the required FCIP link using the SAN Extension Tuner Wizard in Cisco DCNM-SAN, follow these steps:
Step 1 Right-click a valid FCIP link in the Fabric pane, and then select SAN Extension Tuner from the drop-down list. You can also highlight the link and choose Tools > Other > SAN Extension Tuner.
You see the Select Ethernet Port Pair dialog box.
Step 2 Select the Ethernet port pairs that correspond to the FCIP link you want to tune and click Next.
Note The Ethernet ports you select should be listed as down.
You see the Specify Parameters dialog box.
Step 3 Create and activate a new zone to ensure that the virtual N ports are not visible to real initiators in the SAN by clicking Yes to the zone creation dialog box.
Step 4 (Optional) Change the default settings for the transfer data size and the number of concurrent SCSI read and write commands as follows:
a. Set Transfer Size to the number of bytes that you expect your applications to use over the FCIP link.
b. Set Read I/0 to the number of concurrent SCSI read commands you expect your applications to generate over the FCIP link.
c. Set Write I/0 to the number of concurrent outstanding SCSI write commands you expect your applications to generate over the FCIP link.
Note There is only one outstanding I/O at a time to the virtual N port that emulates the tape behavior.
d. Check the Use Pattern File check box and select a file that you want to use to set the data pattern that is generated by the SAN extension tuner. See the “Data Pattern” section.
You see the Results dialog box.
Step 6 Click Start to start the tuner. The tuner sends a continuous stream of traffic until you click Stop.
Step 7 Click Show to see the latest tuning statistics. You can select this while the tuner is running or after you stop it.
Step 8 Click Stop to stop the SAN extension tuner.
Enabling the Tuner
The tuning feature is disabled by default in all switches in the Cisco 9000 Family. When you enable this feature, tuning is globally enabled for the entire switch.
Configuring the Virtual N Port
To configure the virtual N port for tuning, follow these steps:
Assigning the SCSI Read/Write
You can assign SCSI read and write commands on a one-time basis or on a continuous basis.
To assign SCSI read or write commands on a one-time basis, follow these steps:
To generate SCSI read or write commands continuously, follow these steps:
To specify a transfer ready size for a SCSI write command, follow these steps:
Assigning SCSI Tape Read/Write
You can assign SCSI tape read and write commands on a one-time basis or on a continuous basis.
Note There is only one outstanding I/O at a time to the virtual N-port that emulates the tape behavior.
To assign SCSI tape read and or write commands on a one-time basis, follow these steps:
To generate SCSI tape read or write commands continuously, follow these steps:
Configuring a Data Pattern
To optionally configure a data pattern for SCSI commands, follow these steps:
Verifying SAN Extension Tuner Configuration
To display SAN extension tuner configuration information, perform one of the following tasks:
Verifying the SAN Extension Tuner Configuration
The show commands display the current SAN extension tuner settings for the Cisco MDS switch (see Examples 39-1 to 39-6 ).
Example 39-1 Displays Entries in the FLOGI Database
INTERFACE VSAN FCID PORT NAME NODE NAME ------------------------------------------------------------------------------
iscsi3/4 200 0x050000 12:00:00:00:00:00:00:56 10:00:00:00:00:00:00:00
Example 39-2 Displays Details for a VSAN Entry in the FLOGI Database
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x020000 N 22:22:22:22:22:22:22:22 scsi-fcp
Example 39-3 Displays All Virtual N Ports Configured on the Specified Interface
Example 39-4 Displays N Ports Configured on a Specified Gigabit Ethernet Interface
Example 39-5 Displays the Transfer Ready Size Configured for a Specified N Port
Example 39-6 Displays All Virtual N Ports Configured in This Switch