Brocade Tegile Ha2100ep Fos 740 VT

53-1004095-01
December 2015
Brocade Fabric Technology

with the Tegile HA2100EP
Hybrid Flash Array
Validation Test Report
Supporting Fabric OS 7.4.0

© 2015, Brocade Communications Systems, Inc. All Rights Reserved.
ADX, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, The Effortless
Network, VCS, VDX, Vplane, and Vyatta are registered trademarks, and Fabric Vision and vADX are trademarks of Brocade
Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be
trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any
equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document
at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be
currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in
this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the
accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that
accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other open
source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to
the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
Contents
Preface..................................................................................................................................... 5
Document History..............................................................................................5
Overview........................................................................................................... 5
Purpose of This Document................................................................................5
Audience........................................................................................................... 5
Objectives......................................................................................................... 6
Related Documents ..........................................................................................6
About Brocade.................................................................................................. 6
About Tegile...................................................................................................... 6
Test Plan...................................................................................................................................8
Scope................................................................................................................ 8
What's New in This Report................................................................................8
Test Configuration.............................................................................................8
DUT Descriptions.............................................................................................. 9
DUT Specifications..........................................................................................10
Test Equipment............................................................................................... 11
Configure DUT and Test Equipment..........................................................................................12

Task 1: Brocade FC Fabric Configuration.......................................................12
Task 2: Tegile IntelliFlash HA2100EP Array Configuration.............................14
Task 3: Host Setup..........................................................................................20
Test Cases.............................................................................................................................. 24
1.0 Fabric Initialization—Base Functionality................................................... 25
1.0.1 Storage Device—Physical and Logical Login with Speed
Negotiation.................................................................................... 25
1.0.2 Zoning and LUN Mapping.......................................................... 25
1.0.3 Storage Device Fabric I/O Integrity............................................ 26
1.0.4 Storage Device Multipath Configuration—Path Integrity............26
1.1 Fabric—Advanced Functionality............................................................... 27
1.1.1 Storage Device Bottleneck Detection Using MAPS FPI—
With Congested Host.....................................................................27
1.1.2 Storage Device Bottleneck Detection Using MAPS FPI—
With Congested Fabric.................................................................. 28
1.1.3 QoS Integrity with QoS Zone-Based Traffic Prioritization.......... 29
1.1.4 QoS Integrity with CS_CTL-Based Frame Prioritization............ 30
1.1.5 Storage Device—FC Protocol Jammer Test Suite.....................31
1.1.6 Clear Link Diagnostics (D_Port) Test.........................................32
1.2 Stress and Error Recovery with Device Multipath.....................................34
1.2.1 Storage Device Fabric I/O Integrity—Congested Fabric............ 34
1.2.2 Storage Device Integrity—Device Recovery from Port
Toggle............................................................................................34
1.2.3 Storage Device Integrity—Device Recovery from Device
Relocation......................................................................................35
1.2.4 Storage Device Stress—Device Recovery from Device Port
Toggle—Extended Run................................................................. 36
Brocade Fabric Technology with the Tegile HA2100EP Hybrid Flash Array Validation Test Report 3
53-1004095-01
1.2.5 Storage Device Recovery—ISL Port Toggle (Sequential)....... 37
1.2.6 Storage Device Recovery—ISL Port Toggle (Entire Switch)... 38
1.2.7 Storage Device Recovery—Director Blade Maintenance........ 39
1.2.8 Storage Device Recovery—Switch Offline...............................40
1.2.9 Storage Device Recovery—Switch Firmware Download......... 41
1.3 Storage Device Fibre Channel Routing (FCR) Internetworking Tests.... 42
1.3.1 Storage Device Internetworking Validation with the FC
Host............................................................................................. 42
1.3.2 Storage Device Internetworking Validation with FCoE
Using VDX FlexPort.....................................................................43
1.3.3 Storage Device Edge Recovery After FCR Disruptions........... 44
1.3.4 Storage Device Backbone Recovery After FCR Disruptions... 45
1.4 Optional/Additional Tests........................................................................ 46
1.4.1 Nondisruptive Firmware Upgrade on the Storage Device........46
1.4.2 Synthetic I/O Workload Loop with Varying Block Sizes........... 47
1.4.3 VMware Workload Test............................................................48
Test Conclusions...................................................................................................................49
4 Brocade Fabric Technology with the Tegile HA2100EP Hybrid Flash Array Validation Test Report
53-1004095-01
Preface
● Document History..............................................................................................................5
● Overview........................................................................................................................... 5
● Purpose of This Document................................................................................................5
● Audience........................................................................................................................... 5
● Objectives......................................................................................................................... 6
● Related Documents ..........................................................................................................6
● About Brocade.................................................................................................................. 6
● About Tegile...................................................................................................................... 6
Document History
Date Part Number Description
December 2015 53-1004095-01 Initial version.
Overview
The Solid State Ready (SSR) program is a comprehensive testing and configuration initiative to validate
the interoperability of Fibre Channel (FC) and IP flash storage with a Brocade network infrastructure.
This program provides testing of multiple fabrics, heterogeneous servers, NICs, and HBAs in a large
port-count Brocade environment. The SSR qualification program helps verify seamless interoperability
and optimum performance of solid state storage in Brocade FC and Ethernet fabrics.
Purpose of This Document

The goal of this document is to demonstrate the compatibility of Tegile IntelliFlash HA2100EP arrays in
a Brocade FC SAN fabric running Fabric OS 7.4.0. This document provides a test report on the SSR
qualification test plan executed on the Tegile IntelliFlash HA2100EP array.
Audience
The target audience for this document includes storage administrators, solution architects, system
engineers, and technical development representatives.
53-1004095-01
Objectives
Objectives
• Test the Tegile IntelliFlash HA2100EP array with Brocade FC fabrics, in single and routed
configurations for different stress and error recovery scenarios, to validate the interoperability and
integration of the Tegile array with Brocade FC fabrics.
• Validate the performance of the FC fabric in a solid state storage environment for high-throughput
and low-latency applications.
Related Documents
• Brocade Fabric OS Administrator's Guide
• Brocade Monitoring and Alerting Policy Suite Administrator's Guide
• Brocade SAN Design and Best Practices
• Brocade SAN Fabric Administration Best Practices Guide
• Brocade Network OS Layer 2 Switching Configuration Guide
• Emulex ExpessLane Configuration
• Emulex OneCommand Manager User Manual
• QLogic QLE2672 Adapter User's Guide
• QLogic BR-1860 Adapter Administrator's Guide
About Brocade
Brocade networking solutions help the world's leading organizations transition smoothly to a world
where applications and information reside anywhere. This vision is realized through the Brocade
One™ strategy, which is designed to deliver key business benefits such as unmatched simplicity, non-
stop networking, application optimization, and investment protection.
Innovative Ethernet and storage networking solutions for data center, campus, and service provider
networks help reduce complexity and cost while enabling virtualization and cloud computing to
increase business agility.
To help ensure a complete solution, Brocade partners with world-class IT companies and provides
comprehensive education, support, and professional services offerings.
To learn more, visit www.brocade.com.
About Tegile
Tegile Systems™ is pioneering a new generation of all-flash and flash-driven hybrid enterprise storage
arrays that balance performance, capacity, features, and price for virtualization, file services, and
database applications.
Our hybrid arrays are significantly faster than legacy arrays and significantly less expensive than all
solid-state disk-based arrays. Featuring both NAS and SAN connectivity, these virtual data storage
systems are easy-to-use, fully redundant, and highly scalable. Additionally, they come complete with
built-in snapshot, replication, near-instant recovery, and virtualization management features.
53-1004095-01
Preface
Tegile's patented IntelliFlash™ technology accelerates performance to solid state speeds without
sacrificing the capacity or cost advantage of hard disk storage. Additionally it enables on-the-fly de-
duplication and compression so usable capacity is far greater than its raw capacity.
Tegile offers an extensive line of hybrid storage solutions as part of the Intelligent Flash Array portfolio.
Tegile hybrid arrays leverage the performance of flash, the density of hard disks, and the rich features
of the IntelliFlash operating system to deliver a compelling storage platform that accelerates a wide
variety of workloads in the enterprise.
Fully redundant with active/active controllers, these arrays are built for enterprise data centers with
resilience, data availability, and data protection in mind. With Tegile hybrid arrays, you no longer have
to compromise between performance, capacity, and cost for accelerating and protecting your enterprise
applications.
53-1004095-01
Test Plan
Test Plan
● Scope..............................................................................................................................8
● What's New in This Report..............................................................................................8
● Test Configuration...........................................................................................................8
● DUT Descriptions............................................................................................................ 9
● DUT Specifications........................................................................................................10
● Test Equipment............................................................................................................. 11
Scope
The Tegile IntelliFlash HA2100EP array is connected to a Brocade 16-Gb FC fabric with the two FC
target ports from each active controller connecting to the same FC fabric to support controller failover.
Testing focuses on interoperability of the Tegile storage array and determining an optimal
configuration for performance and availability. Testing covers various I/O stress and error handling
scenarios. Performance is observed within the context of best-practice fabric configuration; however
absolute maximum benchmark reporting of storage performance is beyond the scope of this test.
Details of the test steps are covered under the "Test Cases" section. Standard test-bed setup includes
IBM/HP/Dell servers with Brocade/QLogic/Emulex HBAs with two uplinks from every host to the
Brocade FC fabric. I/O generator tools used include Medusa Labs Test Tools and VMware I/O
Analyzer.
What's New in This Report

• The array firmware version under test is 2.1.3.4(150311)-368.
• The array is configured in a "dual" active controller configuration.
• The Brocade Fabric OS (FOS) version under test is 7.4.0.
• Emulex and QLogic adapters have updated firmware and drivers.
• Two new test cases have been added:
‐ 1.1.4 QoS Integrity with CS_CTL-Based Frame Prioritization
‐ 1.1.6 Clear Link Diagnostics (D_Port) Test
For detailed information, see the "DUT Descriptions" section.
The previous version of the test report covering Brocade Fabric OS 7.3.1 and Tegile array firmware
2.1.3.2(141215)-338 is available at Brocade Fabric Technology with the Tegile HA2100EP Validation
Test Report.
Test Configuration
53-1004095-01
DUT Descriptions
DUT Descriptions
The following tables provide details about the devices under test (DUTs).
TABLE 1 Storage Array

DUT ID Model Vendor Description
Tegile HA2100EP HA2100EP Tegile The HA2100EP array is a hybrid-flash array

setup with dual controllers in an HA resource
cluster. The controllers are in a "dual" active
configuration with 2x8Gb FC and 2x10GbE
ports on each controller. The array supports
the FC, iSCSI, NFS, and CIFS protocols.
TABLE 2 Switches
DUT ID Model Vendor Description
6510-1...9 BR-6510 Brocade 48-port 16-Gb FC switch
DCX-1 DCX 8510-8 Brocade 8-slot 16-Gb FC chassis
DCX-2 DCX 8510-4 Brocade 4-slot 16-Gb FC chassis
VDX-1,2 VDX 6740 Brocade 48x10GbE and 4x40GbE port switch
53-1004095-01
DUT Specifications
DUT Specifications
Storage Version
Tegile IntelliFlash HA2100EP array 2.1.3.4(150311)-368
Brocade Switches Version
DCX 8510-8 Fabric OS 7.4.0
DCX 8510-4 Fabric OS 7.4.0
6510 + Integrated Routing, Fabric Vision Licenses Fabric OS 7.4.0
VDX 6740 Network OS 5.0.1a
Adapters Version
Brocade 1860 2-port 16-Gb FC HBA/10GbE CNA Driver and firmware version 3.2.5.1
Brocade 825 2-port 8-GB FC HBA Driver and firmware version 3.2.5.1
QLogic QLE2672 2-port 16-GB FC HBA Driver 9.1.12.21, firmware 7.01.00
QLogic QLE2562 2-port 8-GB FC HBA Driver 8.07.00.08.07.0-k2, firmware 7.01.00
Emulex LPe 16202-X 2-port 16-Gb FC HBA Driver 10.4.246.0, firmware 10.4.255.23
Emulex OCe14102-UM 2-port CNA adapter Driver 10.2.370.8, firmware 10.2.370.19
DUT ID Servers RAM Processor OS
SRV-1 HP ProLiant DL380p Gen8 16 GB Intel Xeon E5-2620 Windows Server

2012 R2
SRV-2 HP ProLiant DL380p Gen8 32 GB Intel Xeon E5-2690 RHEL 6.5

v2 x86_64
SRV-3 IBM System x3650 M4 16 GB Intel Xeon E5-2620 RHEL 7 x86_64
SRV-4 IBM System x3550 M3 24 GB Intel Xeon E5645 SLES 12.0

x86_64
SRV-5 HP ProLiant DL360 Gen7 24 GB Intel Xeon E5645 VMware ESXi

5.5
SRV-6 HP ProLiant DL360 Gen7 24 GB Intel Xeon E5645 VMware ESXi

5.5
SRV-7 IBM System x3630 M4 24 GB Intel Xeon E5-2420 Windows Server

2012 R2
SRV-8 Dell PowerEdge R710 8 GB Intel Xeon L5520 Windows Server

2012
53-1004095-01
Test Equipment
Test Equipment
Device/Software Tools Version
Finisar 16-Gb Analyzer/Jammer XGIG5K2001153
Medusa Labs Test Tools 6.0.1.148039
VMware I/O Analyzer 1.6.2
53-1004095-01
Configure DUT and Test Equipment
● Task 1: Brocade FC Fabric Configuration.....................................................................12

● Task 2: Tegile IntelliFlash HA2100EP Array Configuration...........................................14
● Task 3: Host Setup........................................................................................................20
Task 1: Brocade FC Fabric Configuration

1. Enable MAPS and Fabric Performance Impact (FPI) monitoring on all switches in the fabric.
MAPS enables health monitoring on the switches to detect potential faults and create alerts. MAPS
FPI allows fabric monitoring of performance impacts, including timeouts, latency, and throughput.
Detailed information on MAPS configuration and setup can be found in the Monitoring and Alerting
Policy Suite Administrator's Guide.
• MAPS requires a Fabric Vision license to be installed.
• Enable the desired MAPS policy using any available default policy or creating a custom policy.
• Enable FPI monitoring. FPI monitoring requires "bottleneckmon" to be disabled.
root> mapsconfig --enablemaps -policy dflt_aggressive_policy

WARNING:
This command enables MAPS and replaces all Fabric Watch configurations and monitoring. Once MAPS is
enabled, the Fabric Watch configuration can't be converted to MAPS.
If you wish to convert your Fabric Watch configuration into MAPS policies, select NO to this prompt
and first issue the "mapsconfig --fwconvert" command. Once the Fabric Watch configuration is converted
into MAPS policies, you may reissue the "mapsconfig --enablemaps" command to continue this process.If
you do not use Fabric Watch or need the configuration, then select YES to enable MAPS now.
Do you want to continue? (yes, y, no, n): [no] y
Enabled dflt_aggressive_policy policy.
root> mapsconfig --actions raslog,email,sw_marginal,sw_critical
root> bottleneckmon --disable
root> mapsConfig –enableFPImon
root> mapsconfig --show

Configured Notifications: RASLOG,EMAIL,SW_CRITICAL,SW_MARGINAL
Mail Recipient: pillais@brocade.com,rlodes@brocade.com
FPI Monitoring: Enabled
Paused members :
================
PORT :
CIRCUIT :
SFP :
root> mapsdb --show

1 Dashboard Information:
========================
DB start time: Mon Apr 20 21:23:31 2015

Active policy: dflt_aggressive_policy
Configured Notifications: RASLOG,EMAIL,SW_CRITICAL,SW_MARGINAL
Fenced Ports : None
Decommissioned Ports : None
Quarantined Ports : None
2 Switch Health Report:

=======================
Current Switch Policy Status: HEALTHY
53-1004095-01
3.1 Summary Report:

===================
Category |Today |Last 7 days |

--------------------------------------------------------------------------------
Port Health |Out of operating range |Out of operating range |
BE Port Health |No Errors |No Errors |
Fru Health |In operating range |In operating range |
Security Violations |No Errors |No Errors |
Fabric State Changes |In operating range |In operating range |
Switch Resource |In operating range |In operating range |
Traffic Performance |In operating range |In operating range |
FCIP Health |Not applicable |Not applicable |
Fabric Performance Impact|In operating range |Out of operating range |
3.2 Rules Affecting Health:

===========================
Category(Rule |Repeat |Rule Name |Execution Time |Object |Triggered |

Count) Count Value(Units)
---------------------------------------------------------------------------------------------------
Port Health(100) |1 |defNON_E_F_PORTSLOSS_SIGNAL|05/04/15 10:53:06|U-Port 40|1 LOS |
| |_0 | | | |
|40 |defNON_E_F_PORTSLOSS_SIGNAL|04/30/15 12:22:40|U-Port 40|1 LOS |
| |_0 | | | |
| | | |U-Port 40|1 LOS |
| | | |U-Port 40|1 LOS |
| | | |U-Port 40|1 LOS |
| | | |U-Port 40|1 LOS |
|1 |defALL_OTHER_F_PORTSLF_0 |04/30/15 09:45:46|F-Port 10|1 |
|1 |defALL_TARGET_PORTSLOSS_SIG|04/30/15 09:39:16|U-Port 10|1 LOS |
| |NAL_0 | | | |
|1 |defALL_TARGET_PORTSSTATE_CH|04/30/15 09:39:16|U-Port 10|1 |
| |G_0 | | | |
Fabric |2 |defALL_TARGET_PORTSTX_60 |05/01/15 20:00:18|F-Port 25|60.66 % |
Performance | | | | | |
Impact(6) | | | | | |
| | | |F-Port 25|60.99 % |
|2 |defALL_PORTS_IO_LATENCY_CLE|04/29/15 21:57:16|E-Port 41|IO_LATENCY_CLEAR|
| |AR | | | |
| | | |E-Port 41|IO_LATENCY_CLEAR|
|1 |defALL_PORTS_IO_FRAME_LOSS |04/29/15 21:56:16|E-Port 41|IO_FRAME_LOSS |
|1 |defALL_PORTS_IO_PERF_IMPACT|04/29/15 15:29:14|E-Port 41|IO_PERF_IMPACT |
2. Configure zoning using the Peer Zoning feature in Fabric OS 7.4.0.
Peer zoning allows a "principal" device to communicate with the rest of the devices in the zone. The
principal device manages a peer zone. Other "nonprincipal" devices in the zone can communicate
with the principal device only; they cannot communicate with each other.
root> zonecreate –peerzone ssr_tegile_1 –principal “21:00:00:24:ff:48:b9:6a; …..” –
members “10:00:8c:7c:ff:14:e0:01; …”
root> zoneshow --peerzone all

zone: ssr_tegile_1
Property Member: 00:02:00:00:00:03:00:04
Created by: User
Principal Member(s):
21:00:00:24:ff:48:b9:6a; 21:00:00:24:ff:48:b9:6b;
50:01:43:80:06:2d:08:2a; 50:01:43:80:06:2d:08:28
Peer Member(s):
10:00:00:05:1e:60:b4:6c; 10:00:00:05:1e:60:b4:6b;
10:00:8c:7c:ff:14:e0:01; 10:00:8c:7c:ff:14:e0:00;
10:00:8c:7c:ff:03:bc:00; 10:00:8c:7c:ff:03:bc:01;
10:00:8c:7c:ff:03:9b:01; 10:00:8c:7c:ff:03:9b:00
root> cfgactvshow
zone: ssr_tegile_1
00:02:00:00:00:03:00:04; 21:00:00:24:ff:48:b9:6a;
21:00:00:24:ff:48:b9:6b; 50:01:43:80:06:2d:08:2a;
50:01:43:80:06:2d:08:28; 10:00:00:05:1e:60:b4:6c;
10:00:00:05:1e:60:b4:6b; 10:00:8c:7c:ff:14:e0:01;
10:00:8c:7c:ff:14:e0:00; 10:00:8c:7c:ff:03:bc:00;
10:00:8c:7c:ff:03:bc:01; 10:00:8c:7c:ff:03:9b:01;
10:00:8c:7c:ff:03:9b:00
53-1004095-01
Task 2: Tegile IntelliFlash HA2100EP Array Configuration
3. Configure Fibre Channel Routing (an Integrated Routing license is required).

The FC-FC routing service provides Fibre Channel routing between two or more fabrics without
merging those fabrics. For example, using FC-FC routing, you can share tape drives across multiple
fabrics without the administrative problems, such as change management, network management,
scalability, reliability, availability, and serviceability, that might result from merging the fabrics.
Detailed information on FCR setup can be found in the Brocade Fabric OS Administrator's Guide.
An example FCR configuration follows:
root> fcrconfigure –bbfid 100
root> fosconfig --enable fcr
root> portcfgexport [port#] -a1 –m[0/5] -f 10 --- {-m 0-Brocade 5-Brocade NOS
fabric}
LSAN zone is created on both fabrics.
root> cfgactvshow
zone: LSAN_ssr_tegile_peer
00:02:00:00:00:03:00:04; 21:00:00:24:ff:48:b9:6a;
50:01:43:80:06:2d:08:2a; 50:01:43:80:06:2d:08:28;
21:00:00:24:ff:48:b9:6b; 10:00:00:05:33:90:ac:9e;
10:00:00:05:33:90:ac:9f; 21:00:00:0e:1e:18:99:90;
21:00:00:0e:1e:18:99:91
Example output of exported devices

root> fcrproxydevshow
Proxy WWN Proxy Device Physical State
Created PID Exists PID
in Fabric in Fabric
------------------------------------------------------------------------
10 21:00:00:24:ff:48:b9:6a 02f001 20 551a00 Imported
10 21:00:00:24:ff:48:b9:6b 02f101 20 541e00 Imported
10 52:4a:93:7d:f3:5f:61:00 02f201 20 550e00 Imported
10 52:4a:93:7d:f3:5f:61:01 02f401 20 540400 Imported
4. Configure FlexPort on the Brocade VDX 6740 switches. The FlexPort feature allows ports to
transmit data as either 10G Ethernet or Fibre Channel and to be changed from one type to the other
without requiring a reboot.
FlexPorts configured on the VDX switch are used to uplink from the VCS fabric to the FC fabric in
this test. Detailed information on FlexPort configuration can be found in the Network OS Layer 2
Switching Configuration Guide. An example FlexPort configuration follows:
VDX6740# show running-config hardware flexport
hardware
flexport 119/0/48
type fibre-channel
!
flexport 120/0/48
type fibre-channel
!
connector-group 119/0/6
speed HighMixed
!
connector-group 120/0/6
speed HighMixed
!
Task 2: Tegile IntelliFlash HA2100EP Array Configuration

1. Configure the array with two data pools, one on each controller. We have used the two-way
mirrored pool type, and the pools are assigned to the HA resource group corresponding to each
controller.
53-1004095-01
FIGURE 1 Tegile Data Pool Creation
FIGURE 2 Tegile HA Configuration for the Storage Pool
2. The FC target ports from both controllers on the array are connected to the Brocade FC fabric.
53-1004095-01
FIGURE 3 Tegile FC Target Connections
3. Create volume group "projects" based on host group access. Default values for data compression
and de-duplication are accepted. No snapshots or replication is configured. Distribute the host
group projects evenly across the two controller nodes.
FIGURE 4 Tegile Project Configuration—General Settings
53-1004095-01
FIGURE 5 Tegile Project Mapping Configuration
53-1004095-01
FIGURE 6 Tegile Project Creation on Pool-A
53-1004095-01
FIGURE 7 Tegile Project Creation on Pool-B
FIGURE 8 Tegile Dataset Creation
53-1004095-01
Task 3: Host Setup
Task 3: Host Setup

1. Provision a minimum of two uplinks from the host to the FC fabric for redundancy, and use native
multipath tools to manage the available paths and to load-balance across them.
2. Configure the multipath settings to allow for proper failover and load balancing across the available
links.
• For Windows, native MPIO is used and the following parameters are tuned in the Windows
registry for optimal path recovery and HA failover.
The following Windows MSDSM parameters are required for HA failover to work properly:
• PathVerifyEnabled: Enabled
• PathVerificationPeriod: 30
• RetryInterval: 1
• RetryCount: 3
• PDORemovePeriod: 120
53-1004095-01
FIGURE 9 Windows Disk MPIO Properties
• For Linux, add the following to /etc/multipath.conf.

devices {
device {
vendor "TEGILE"
product "ZEBI-FC"
hardware_handler "1 alua"
path_selector "round-robin 0"
path_grouping_policy "group_by_prio"
no_path_retry 10
dev_loss_tmo 50
path_checker tur
prio alua
failback 30
}
Sample Output:
3600144f0ec770e000000536d06730008 dm-2 TEGILE ,ZEBI-FC

size=10G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 5:0:2:15 sdm 8:192 active ready running
| |- 5:0:0:15 sdr 65:16 active ready running
| |- 6:0:1:15 sdad 65:208 active ready running
| `- 6:0:2:15 sdai 66:32 active ready running
53-1004095-01
`-+- policy='round-robin 0' prio=1 status=enabled

|- 5:0:3:15 sdd 8:48 active ready running
|- 6:0:3:15 sde 8:64 active ready running
|- 6:0:0:15 sdx 65:112 active ready running
`- 5:0:1:15 sdw 65:96 active ready running
• For VMware, run the following command from the VMware host CLI to set up a default round-
robin path-selection policy for Tegile devices.
esxcli storage nmp satp rule add -s VMW_SATP_ALUA –V "TEGILE" -M "ZEBI-FC" -c
"tpgs_on” –P VMW_PSP_RR -e "Tegile Zebi FC"
FIGURE 10 VMware Path Selection Policy for Tegile
FIGURE 11 Tegile Devices Discovered on the VMware Host
53-1004095-01
FIGURE 12 VMware-Discovered Paths for Tegile Devices
53-1004095-01
Test Cases
Test Cases
1.0 Fabric Initialization—Base Functionality
1.0.1 Storage Device—Physical and Logical Login with Speed Negotiation
1.0.2 Zoning and LUN Mapping
1.0.3 Storage Device Fabric I/O Integrity
1.0.4 Storage Device Multipath Configuration—Path Integrity
1.1 Fabric—Advanced Functionality
1.1.1 Storage Device Bottleneck Detection Using MAPS FPI—With Congested Host
1.1.2 Storage Device Bottleneck Detection Using MAPS FPI—With Congested

Fabric
1.1.3 QoS Integrity with QoS Zone-Based Traffic Prioritization
1.1.4 QoS Integrity with CS_CTL-Based Frame Prioritization
1.1.5 Storage Device—FC Protocol Jammer Test Suite
1.1.6 Clear Link Diagnostics (D_Port) Test
1.2 Stress and Error Recovery with Device Multipath
1.2.1 Storage Device Fabric I/O Integrity—Congested Fabric
1.2.2 Storage Device Integrity—Device Recovery from Port Toggle
1.2.3 Storage Device Integrity—Device Recovery from Device Relocation
1.2.4 Storage Device Stress—Device Recovery from Device Port Toggle—Extended

Run
1.2.5 Storage Device Recovery—ISL Port Toggle (Sequential)
1.2.6 Storage Device Recovery—ISL Port Toggle (Entire Switch)
1.2.7 Storage Device Recovery—Director Blade Maintenance
1.2.8 Storage Device Recovery—Switch Offline
1.2.9 Storage Device Recovery—Switch Firmware Download
1.3 Storage Device—Fibre Channel Routing (FCR) Internetworking Tests
1.3.1 Storage Device Internetworking Validation with the FC Host
1.3.2 Storage Device Internetworking Validation with FCoE Using VDX FlexPort
1.3.3 Storage Device Edge Recovery After FCR Disruptions
1.3.4 Storage Device Backbone Recovery After FCR Disruptions
1.4 Optional/Additional Tests
1.4.1 Nondisruptive Firmware Upgrade on the Storage Device
1.4.2 Synthetic I/O Workload Loop with Varying Block Sizes
53-1004095-01
1.4.3 VMware Workload Test

1.0.1 Storage Device—Physical and Logical Login with Speed
Negotiation
Test Objective
Verify device login to the switch and name server with all supported speed settings.
Procedure
Test Execution
1. Set the switch ports to 4/8/16/Auto_Negotiate speeds.
portcfgspeed <port> [4/8/16/0]
Result Validation
1. Validate link states on the array, and verify speed negotiation and device login at different speeds.
2. Check the switch port status, and verify the "actual" and "configured" link speed. Check the name
server for device login.
# nscamshow
# portshow X
root> portshow 19
portIndex: 19
portName: port19
portHealth: HEALTHY
portState: 1 Online
Protocol: FC
portWwn of device(s) connected:
10:00:8c:7c:ff:22:f7:81
Distance: normal
portSpeed: N16Gbps <-
Test Results
PASS. Speed negotiation, device login, and connectivity are verified.
1.0.2 Zoning and LUN Mapping

Test Objective
Verify that host-to-LUN access exists with valid zoning.
53-1004095-01
Procedure
Test Execution
1. Create peer zones on the fabric with the target WWNs as the principal members and the initiator
WWNs as the peer members.
2. Create host groups and LUNs on the array with access to initiator WWNs.
Result Validation
Verify that LUNs are discovered on the hosts using host-specific tools.
- Linux: Check output of lsscsi

- Windows: Check output of Computer Management > Storage > Disk Management
- VMware: Check output at Configuration > Storage > Devices
Test Results
PASS. The host has read/write access to presented LUNs.

Test Objective
Validate single path host-to-LUN I/O with read/write/verify testing. Include short device cable pulls/port
toggles to validate device recovery.
Procedure
Test Execution
1. Set up read/write I/O to the LUN using Medusa.
2. Perform link disruptions by port toggles, cable pulls.
Result Validation
Check Medusa I/O logs, and verify that I/O resumes after a short downtime. Medusa I/O may pause,
but should recover without errors.
Test Results
PASS. I/O resumes after the disruption.
1.0.4 Storage Device Multipath Configuration—Path Integrity

Test Objective
Verify that multipath configures successfully. Each adapter and storage port is to reside in different
switches. For all device paths, consecutively isolate individual paths, and validate I/O integrity and
path recovery.
Procedure
Test Execution
53-1004095-01
1. Set up the host with at least two initiator ports zoned with two target ports on the array.
2. Set up multipath on the host, and start I/O.
3. Perform sequential port toggles across the initiator and target switch ports to isolate the paths.
Result Validation
1. Check the host multipath properties to verify that the toggled path recovers.
- Windows: mpclaim –s –d
- Linux: multipath –ll
- VMware: Check the paths at Configuration > Storage > Devices > Manage Paths
2. Check the host and storage logs for any failures.
3. Check the switch error logs and switch port status after toggling.
# errdumpall
# portstatsshow X
# portshow X
root> portshow 19
portHealth: HEALTHY <-
. . .
portState: 1 Online <-
. . .
10:00:8c:7c:ff:22:f7:81 <-
Distance: normal
portSpeed: N16Gbps
4. Check I/O logs, and verify that I/O continues without errors.
Test Results
PASS. I/O fails over to remaining active paths and recovers when the disrupted path is restored.

1.1.1 Storage Device Bottleneck Detection Using MAPS FPI—With
Congested Host
Test Objective
Verify that congestion on host ports is detected. Verify storage device and fabric behavior during
congestion.
Procedure
Test Execution
1. Enable MAPS monitoring and MAPS FPI on all switches. A Fabric Vision license required.
2. Start I/O from a single host initiator to multiple targets.
3. Monitor switch logs for congestion and latency (IO_PERF_IMPACT/IO_FRAME_LOSS) warnings.
Result Validation
53-1004095-01
1.1.2 Storage Device Bottleneck Detection Using MAPS FPI—With Congested Fabric
Check the switch error logs and MAPS dashboard for bottleneck warnings.
# errdumpall | grep IO_
root> errdumpall | grep IO_

2014/12/17-11:56:00:672622, [MAPS-1003], 117148/115018, FID 128, WARNING,
B6510_066_088, Port 16, Condition=ALL_F_PORTS(DEV_LATENCY_IMPACT==IO_PERF_IMPACT),
Current Value:[DEV_LATENCY_IMPACT,IO_PERF_IMPACT, 30.0% in 10 secs],
RuleName=defALL_F_PORTS_IO_PERF_IMPACT, Dashboard Category=Fabric Performance
Impact., actionHndlr.c, line: 755, comp:md, ltime:2014/12/17-11:56:00:671909
# mapsdb --show all
root> mapsdb --show
========================
. . .

=======================
3.1 Summary Report:

===================
--------------------------------------------------------------------------------
Port Health |No Errors |Out of operating range |
Security Violations |No Errors |In operating range |
Fabric State Changes |No Errors |In operating range |
Fabric Performance Impact|In operating range |In operating range |
Test Results
PASS. The bottlenecked ports are displayed on the MAPS dashboard, and a raslog warning is
created.
1.1.2 Storage Device Bottleneck Detection Using MAPS FPI—With

Congested Fabric
Test Objective
Create congestion on a switch ISL port. Verify that congestion in the fabric is detected. Verify storage
device and fabric behavior during the congestion.
Procedure
Test Execution
1. Enable MAPS monitoring and MAPS FPI on all switches. A Fabric Vision license is required.
2. Isolate a single ISL in the fabric.
3. Start I/O from multiple host initiators to multiple targets.
4. Monitor the switch logs for congestion and latency warnings (IO_PERF_IMPACT/
IO_FRAME_LOSS).
Result Validation
53-1004095-01
Check the switch error logs and MAPS dashboard for bottleneck warnings.
# errdumpall | grep IO_
root> errdumpall | grep IO_

2014/12/17-11:56:00:672622, [MAPS-1003], 117148/115018, FID 128, WARNING,
B6510_066_088, Port 16, Condition=ALL_F_PORTS(DEV_LATENCY_IMPACT==IO_PERF_IMPACT),
Current Value:[DEV_LATENCY_IMPACT,IO_PERF_IMPACT, 30.0% in 10 secs],
RuleName=defALL_F_PORTS_IO_PERF_IMPACT, Dashboard Category=Fabric Performance
Impact., actionHndlr.c, line: 755, comp:md, ltime:2014/12/17-11:56:00:671909
# mapsdb --show all
root> mapsdb --show
========================
. . .

=======================
3.1 Summary Report:

===================
--------------------------------------------------------------------------------
Port Health |No Errors |Out of operating range |
Security Violations |No Errors |In operating range |
Fabric State Changes |No Errors |In operating range |
Fabric Performance Impact|In operating range |In operating range |
Test Results
PASS. The bottlenecked ports are displayed on the MAPS dashboard, and a raslog warning is created.

Test Objective
Verify storage device behavior, and validate traffic characteristics with different QoS zones.
Procedure
Test Execution
1. Set up initiator-target pairs with Low/Medium/High QoS zones in the fabric.
zone: QOSH_ssr_tegile_1
00:02:00:00:00:03:00:04; 21:00:00:24:ff:48:b9:6a;
21:00:00:24:ff:48:b9:6b; 50:01:43:80:06:2d:08:2a;
50:01:43:80:06:2d:08:28; 10:00:00:05:1e:60:b4:6c;
10:00:00:05:1e:60:b4:6b; 10:00:8c:7c:ff:14:e0:01;
10:00:8c:7c:ff:14:e0:00; 10:00:8c:7c:ff:03:bc:00;
10:00:8c:7c:ff:03:bc:01; 10:00:8c:7c:ff:03:9b:00;
10:00:8c:7c:ff:03:9b:01
2. Start I/O from all hosts, and verify I/O statistics.
Result Validation
53-1004095-01
1. Check I/O logs, and verify that I/O continues without errors.
2. Check the switch logs and switch port status for errors.
# porterrshow
root> porterrshow
frames enc crc crc too too bad enc disc link
loss loss frjt fbsy c3timeout pcs
tx rx in err g_eof shrt long eof out c3 fail
sync sig tx rx err
0: 1.7g 2.7g 0 0 0 0 0 0 0 946 1
0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30 1
0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
Test Results
PASS. I/O from hosts in all QoS zones completes successfully without errors.

Test Objective
Verify CS_CTL I/O prioritization using the Emulex ExpressLane feature.
Procedure
Test Execution
1. Configure all switches in the fabric to be in "Auto" CS_CTL QoS mode.
root> configurechassis
Configure...
cfgload attributes (yes, y, no, n): [no]
Custom attributes (yes, y, no, n): [no]
system attributes (yes, y, no, n): [no]
fos attributes (yes, y, no, n): [no] y
Reboot needed to effect new CSCTL Mode
CSCTL QoS Mode (0 = default; 1 = auto mode): (0..1) [0] 1
root> configshow -all | grep csctlMode

fos.csctlMode:1
2. Enable CS_CTL mode on the initiator and target switch ports.
root> portcfgqos –enable [slot/]port csctl_mode
root> portcfgshow 22
. . .
CSCTL mode: ON
. . .
3. Set up initiator-target zones in the fabric, and discover the LUNs on the host.
4. Enable the ExpressLane feature on the host Emulex ports, and set the ExpressLane priority
(CS_CTL value) to high (3).
5. Enable ExpressLane on any of the discovered LUNs, and start write I/O from the host.
6. Verify I/O statistics and the CS_CTL prioritization in the fabric.
Result Validation
53-1004095-01
1. Check I/O logs, and verify that I/O continues without errors for all LUNs.
2. Verify that I/O performance improves on ExpressLane-enabled LUNs.
3. Verify CS_CTL prioritization in the fabric by monitoring the high VC buffer credits on the ISLs.
root> portregshow 0 | grep -E "_trc |bbc_mbc"
0x88982800: bbc_trc 4 0 2 2 2 2 1 1
0x88982820: bbc_trc 2 2 2 2 2 2 2 0
0x88982840: bbc_trc 0 0 0 0 0 0 0 0
0x88982860: bbc_trc 0 0 0 0 0 0 0 0
0x88982880: bbc_trc 0 0 0 0 0 0 0 0
4. Check the switch error logs and switch port status for errors.
# porterrshow
root> porterrshow
frames enc crc crc too too bad enc disc
link loss loss frjt fbsy c3timeout pcs
tx rx in err g_eof shrt long eof out c3
fail sync sig tx rx err
0: 1.7g 2.7g 0 0 0 0 0 0 0 946
1 0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30
1 0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
Test Results
PASS. I/O completes successfully for all LUNs. ExpressLane-enabled LUN performance improves, and
I/O to the LUN is prioritized throughout the FC fabric.

Test Objective
Perform FC Jammer tests including areas such as CRC corruption, packet corruption, missing frames,
host error recovery, and target error recovery.
Procedure
Test Execution
1. Insert Jammer device in the I/O path on the storage end.
2. Execute the following Jammer scenarios:
• Delete one frame.
• Delete R_RDY.
• Replace CRC of data frame.
• Replace EOF of data frame.
• Replace "good status" with "check condition".
• Replace IDLE with LR.
• Truncate frame.
• Create S_ID/D_ID error of data frame.
Result Validation
53-1004095-01
1. Check the host and storage logs for errors.

2. Check the switch logs and interface stats for errors.
# errdumpall
# porterrshow
root> porterrshow
0: 1.7g 2.7g 0 0 0 0 0 0 0 946
1 0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30
1 0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3. Verify Jammer operations and recovery using Analyzer.
Test Results
PASS. Host and target were able to recover from the errors and continue I/O operations.

Test Objective
Execute the Clear Link Diagnostics feature on all supported HBAs, and check for port and link
problems.
Procedure
Test Execution
1. The Clear Link Diagnostics test is performed with Emulex LPe16202, QLogic 2672, and QLogic
1860 HBAs.
2. The Brocade FC switch can be configured in static, dynamic, and on-demand D_Port modes. The
switch supports dynamic D_Port by default at the chassis level.
root> configure
Configure...
Fabric parameters (yes, y, no, n): [no]
D-Port Parameters (yes, y, no, n): [no] y
Dynamic D-Port (on, off): [on]
On Demand D-Port (on, off): [off]
3. With the Emulex LPe16202 adapter, the switch port is in dynamic mode, and the test is manually
initiated on the HBA port from the Emulex OneCommand Manager.
root> switchshow
0 0 030000 id N16 In_Sync FC D-Port 10:00:00:90:fa:61:92:3b
Dynamic
4. With the QLogic 2672 adapter, the HBA port is in dynamic D_Port mode, and the test is initiated by
configuring the switch port as a static D_Port.
root> portdisable 19
root> portcfgdport --enable 19
Caution: D_Port functionality is only available on 16Gb-capable platforms with

16Gb FC SFPs, 10Gb FC SFPs, 8Gb LWL/ELWL FC SFPs, QSFPs or QSFP+.
root> portenable 19
53-1004095-01
Test Cases
root> portcfgshow 19
. . .
D-Port mode: ON
root> switchshow
19 19 581300 id N16 Online FC D-Port Loopback->Port 19
5. With the QLogic 1860 adapter, the HBA port can be in static or dynamic D_Port mode.
Enabling static D_Port on the HBA:
# bcu port --disable 2/0

port disabled
# bcu diag --dportenable 2/0

D-port mode for port 2/0 enabled.
6. Execute the D_Port test, and verify that all tests pass and that no port and link problems are
reported.
Result Validation
Check the D_Port test results on the switch ports and host HBA diagnostic utilities.
Mode = Manual -> Static D_Port
Mode = Automatic -> Dynamic D_Port
root> portdporttest --show 13

D-Port Information:
===================
Port: 13
Remote WWPN: 10:00:8c:7c:ff:4f:ca:00
Mode: Manual <-
No. of test frames: 1 Million
Test frame size: 1024 Bytes
FEC (enabled/option/active): Yes/No/No
CR (enabled/option/active): Yes/No/No
Start time: Mon Apr 20 17:01:59 2015
End time: Mon Apr 20 17:02:59 2015
Status: PASSED
================================================================================
Test Start time Result EST(HH:MM:SS) Comments
================================================================================
Electrical loopback 17:02:01 PASSED -------- --------
Optical loopback 17:02:25 PASSED -------- --------
Link traffic test 17:02:50 PASSED -------- --------
================================================================================
Roundtrip link latency: 148 nano-seconds
Estimated cable distance: 2 meters
Buffers required: 1 (for 2112 byte frames at 16Gbps speed)
Egress power: Tx: -3.5 dBm, Rx: Not Avail.
Ingress power: Rx: -3.5 dBm, Tx: Not Avail.
Test Results
PASS. D_Port tests pass with all tested HBAs.
53-1004095-01

1.2.1 Storage Device Fabric I/O Integrity—Congested Fabric
Test Objective
1. From all available initiators, start a mixture of read/write/verify traffic with random data patterns
continuously to all their targets overnight.
2. Verify that no host application failover or unexpected change in I/O throughput occurs.
3. Configure fabric and devices for maximum link and device saturation.
Procedure
Test Execution
1. Start FC I/O to the storage array from multiple hosts.
2. Set up a mix of read/write traffic.
Result Validation
1. Check the host and storage logs for errors.
2. Verify the link congestion, and check the switch logs for errors.
# errdumpall
# portperfshow
# porterrshow
root> porterrshow
0: 1.7g 2.7g 0 0 0 0 0 0 0 946
1 0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30
1 0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3. Check I/O generator tool logs to verify that I/O runs without errors.
Test Results
PASS. All I/O completes without errors. All validation checks pass.
1.2.2 Storage Device Integrity—Device Recovery from Port Toggle

Test Objective
1. With I/O running, perform a quick port toggle on every storage device and adapter port.
2. Verify that host I/O recovers.
3. Perform this test sequentially for each storage device and adapter port.
53-1004095-01
1.2.3 Storage Device Integrity—Device Recovery from Device Relocation
Procedure
Test Execution
2. Perform multiple iterations of sequential port toggles across the initiator and target switch ports.
Result Validation
1. Check switch port status after toggling, and check for errors in the switch logs.
# errdumpall
# portstatsshow X
# portshow X
root> portshow 19
. . .
. . .
10:00:8c:7c:ff:22:f7:81 <-
Distance: normal
portSpeed: N16Gbps
2. Check the host multipath status on hosts to verify that the toggled path recovers.
- Windows: mpclaim -s -d
- Linux: multipath -ll
3. Check the host and storage error logs, and verify that I/O continues without errors.
Test Results
PASS. I/O fails over and recovers successfully. All validation checks pass.
1.2.3 Storage Device Integrity—Device Recovery from Device

Relocation
Test Objective
1. With I/O running, manually disconnect a port and reconnect it to a different switch in the same fabric.
2. Verify that host I/O fails over to an alternate path and that the toggled path recovers.
3. Perform this test sequentially for each storage device and adapter port.
4. Repeat the test for all switch types.
Procedure
Test Execution
2. Move storage target ports to different switch ports in the fabric.
Result Validation
1. Check for errors in the switch logs and the status of the new switch port.
# errdumpall
# portstatsshow X
53-1004095-01
1.2.4 Storage Device Stress—Device Recovery from Device Port Toggle—Extended Run
# portshow X
root> portshow 19
. . .
. . .
10:00:8c:7c:ff:22:f7:81 <-
Distance: normal
portSpeed: N16Gbps
2. Check the host multipath status on hosts to verify that the toggled path recovers.
- Windows: mpclaim -s -d
- Linux: multipath -ll
3. Check host and storage error logs, and verify that I/O continues without errors.
Test Results
1.2.4 Storage Device Stress—Device Recovery from Device Port Toggle

—Extended Run
Test Objective
1. Sequentially toggle each initiator and target port in the fabric.
2. Verify that host I/O recovers to an alternate path and that the toggled path recovers.
3. Run the test for 24 hours.
Procedure
Test Execution
2. Perform multiple iterations of sequential port toggles across the initiator and target switch ports.
Result Validation
1. Check the switch port status after toggling, and check for any errors in the switch logs.
# errdumpall
# portstatsshow X
# portshow X
root> portshow 19
. . .
. . .
10:00:8c:7c:ff:22:f7:81 <-
Distance: normal
portSpeed: N16Gbps
2. Check the multipath properties for iSCSI hosts to verify that the toggled path recovers.
On Windows: mpclaim -s -d
On Linux: multipath -ll
On VMware: Check the paths at Configuration > Storage > Devices > Manage Paths
53-1004095-01
Test Results

Test Objective
1. Sequentially toggle each ISL path on all switches. Host I/O may pause, but should recover.
2. Verify fabric ISL path redundancy between hosts and storage devices.
3. Verify host I/O throughout the test.
Procedure
Test Execution
1. Set up host multipath with links on different switches in the FC fabric, and start I/O.
2. Ensure ISL redundancy by provisioning multiple ISLs connected to different switches to provide
multiple paths through the fabric.
# islshow
root> islshow
1: 0-> 0 10:00:00:05:33:5b:7d:06 97 B6510_066_097 sp: 16.000G bw: 16.000G
TRUNK CR_RECOV FEC
2: 1-> 1 10:00:00:27:f8:0f:b9:f0 91 B6510_066_091 sp: 16.000G bw: 16.000G
TRUNK QOS CR_RECOV FEC
3: 4-> 1 10:00:00:05:33:5b:10:e8 100 B6510_066_100 sp: 16.000G bw: 16.000G
4: 34-> 34 10:00:00:27:f8:66:f3:81 92 B6520_066_92 sp: 16.000G bw: 32.000G
5: 40-> 40 50:00:53:31:39:65:ae:28 160 fcr_fd_160 sp: 16.000G bw: 16.000G
6: 41-> 41 50:00:53:35:b1:d1:de:28 1 fcr_fd_1 sp: 16.000G bw: 16.000G
3. Perform multiple iterations of sequential ISL toggles across the fabric.
Result Validation
1. Check the FC fabric status after ISL toggling. Verify that all nodes are online.
# fabricshow
root> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
-----------------------------------------------------------------------------------
1: fffc01 50:00:53:35:b1:d3:df:1b 0.0.0.0 0.0.0.0 "fcr_xd_1_40"
3: fffc03 10:00:00:05:33:13:95:9a 10.38.66.73 0.0.0.0 "B6510_066_073"
19: fffc13 10:00:00:05:33:a5:bf:86 10.38.66.74 0.0.0.0 >"B6510_066_074"
82: fffc52 10:00:00:05:33:13:96:5a 10.38.66.82 0.0.0.0 "B6510_066_082"
83: fffc53 10:00:00:05:33:5b:1d:1d 10.38.66.83 0.0.0.0 "B6510_066_083"
The Fabric has 5 switches <-

Fabric Name: SSR
2. Check the switch logs for errors, and verify that I/O fails over to an alternate ISL path in the fabric.
# errdumpall
# portperfshow
# porterrshow
root> porterrshow
53-1004095-01
0: 1.7g 2.7g 0 0 0 0 0 0 0 946

1 0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30
1 0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
Test Results
PASS. I/O re-routes to available paths in the fabric and recovers when the link is restored. All
validations checks pass.

Test Objective
1. Sequentially, and for all switches, disable all ISLs on the switch under test.
2. Verify fabric switch path redundancy between hosts and storage devices.
3. Verify that the switch can merge back into the fabric.
4. Verify the host I/O path throughout the test.
Procedure
Test Execution
2. Ensure ISL redundancy by provisioning multiple ISLs connected to different switches to provide
multiple paths through the fabric.
# islshow
root> islshow
1: 0-> 0 10:00:00:05:33:5b:7d:06 97 B6510_066_097 sp: 16.000G bw: 16.000G
TRUNK CR_RECOV FEC
2: 1-> 1 10:00:00:27:f8:0f:b9:f0 91 B6510_066_091 sp: 16.000G bw: 16.000G
3: 4-> 1 10:00:00:05:33:5b:10:e8 100 B6510_066_100 sp: 16.000G bw: 16.000G
4: 34-> 34 10:00:00:27:f8:66:f3:81 92 B6520_066_92 sp: 16.000G bw: 32.000G
5: 40-> 40 50:00:53:31:39:65:ae:28 160 fcr_fd_160 sp: 16.000G bw: 16.000G
6: 41-> 41 50:00:53:35:b1:d1:de:28 1 fcr_fd_1 sp: 16.000G bw: 16.000G
3. Perform multiple iterations of sequentially disabling all ISLs on a switch in the fabric.
Result Validation
1. Check the FC fabric status after ISL toggles. Verify that all nodes are online.
# fabricshow
root> fabricshow
----------------------------------------------------------------------------------
-
1: fffc01 50:00:53:35:b1:d3:df:1b 0.0.0.0 0.0.0.0 "fcr_xd_1_40"
3: fffc03 10:00:00:05:33:13:95:9a 10.38.66.73 0.0.0.0
"B6510_066_073"
19: fffc13 10:00:00:05:33:a5:bf:86 10.38.66.74 0.0.0.0
53-1004095-01
>"B6510_066_074"
82: fffc52 10:00:00:05:33:13:96:5a 10.38.66.82 0.0.0.0 "B6510_066_082"
83: fffc53 10:00:00:05:33:5b:1d:1d 10.38.66.83 0.0.0.0 "B6510_066_083"

Fabric Name: SSR
# errdumpall
# portperfshow
# porterrshow
root> porterrshow
0: 1.7g 2.7g 0 0 0 0 0 0 0 946
1 0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30
1 0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
Test Results
PASS. I/O fails over to an alternate path and recovers once the switch merges back into the fabric. All
validations checks pass.

Test Objective
1. Toggle each blade on the director in sequential order.
2. Include blade enable/disable, power on/off, and reboot testing.
Procedure
Test Execution
1. Uplink edge switch ISLs to different blades on the directors.
3. Perform multiple iterations of sequential disable/enable, power on/off, and reboots of all blades on
the Brocade 8510 directors.
Result Validation
1. Check the FC fabric status after the blade toggles. Verify that all nodes are present in the fabric.
# fabricshow
root> fabricshow
-----------------------------------------------------------------------------------
1: fffc01 50:00:53:35:b1:d3:df:1b 0.0.0.0 0.0.0.0 "fcr_xd_1_40"
3: fffc03 10:00:00:05:33:13:95:9a 10.38.66.73 0.0.0.0 "B6510_066_073"
19: fffc13 10:00:00:05:33:a5:bf:86 10.38.66.74 0.0.0.0 >"B6510_066_074"
82: fffc52 10:00:00:05:33:13:96:5a 10.38.66.82 0.0.0.0 "B6510_066_082"
83: fffc53 10:00:00:05:33:5b:1d:1d 10.38.66.83 0.0.0.0 "B6510_066_083"
53-1004095-01

Fabric Name: SSR
# errdumpall
# portperfshow
# porterrshow
root> porterrshow
0: 1.7g 2.7g 0 0 0 0 0 0 0 946
1 0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30
1 0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
Test Results
PASS. I/O fails over to an alternate path and recovers once the blade recovers from the disruption.

Test Objective
1. Toggle each switch in sequential order.
2. Include switch enable/disable, power on/off, and reboot testing.
Procedure
Test Execution
2. Perform multiple iterations of sequential disable/enable, power on/off, and reboots of all switches in
the fabric.
Result Validation
1. Check the FC fabric status after the switch toggle. Verify that all nodes are present in the fabric.
# fabricshow
root> fabricshow
----------------------------------------------------------------------------------
1: fffc01 50:00:53:35:b1:d3:df:1b 0.0.0.0 0.0.0.0 "fcr_xd_1_40"
3: fffc03 10:00:00:05:33:13:95:9a 10.38.66.73 0.0.0.0
"B6510_066_073"
19: fffc13 10:00:00:05:33:a5:bf:86 10.38.66.74 0.0.0.0
>"B6510_066_074"
82: fffc52 10:00:00:05:33:13:96:5a 10.38.66.82 0.0.0.0
"B6510_066_082"
83: fffc53 10:00:00:05:33:5b:1d:1d 10.38.66.83 0.0.0.0
"B6510_066_083"
53-1004095-01

Fabric Name: SSR
2. Check the switch logs for errors, and verify that the toggled switch has recovered.
# errdumpall
# switchshow
root> switchshow
switchName: B6510_066_088
switchType: 109.1
switchState: Online <-
switchMode: Native
switchRole: Subordinate
switchDomain: 88
switchId: fffc58
switchWwn: 10:00:00:27:f8:06:23:28
zoning: ON (SSR)
switchBeacon: OFF
FC Router: ON
FC Router BB Fabric ID: 100
Address Mode: 0
Fabric Name: SSR_2
Test Results
PASS. I/O fails over to an alternate path and recovers once the switch merges back into the fabric.

Test Objective
1. Sequentially perform the firmware maintenance procedure on all device-connected switches under
test.
2. Verify that host I/O continues (with minimal disruption) through the "firmware download" and that
device pathing remains consistent.
Procedure
Test Execution
2. Sequentially perform firmware upgrades on all switches in the fabric.
Result Validation
1. Verify that the firmware upgrade completes successfully on each switch node and that the nodes
merge back into the FC fabric.
# version
root> version
Kernel: 2.6.14.2
Fabric OS: v7.4.0 <-
Made on: Mon Mar 30 12:51:42 2015
Flash: Wed Apr 1 17:57:12 2015
BootProm: 1.0.11
# fabricshow
root> fabricshow
-----------------------------------------------------------------------------------
1: fffc01 50:00:53:35:b1:d3:df:1b 0.0.0.0 0.0.0.0 "fcr_xd_1_40"
53-1004095-01
1.3 Storage Device Fibre Channel Routing (FCR) Internetworking Tests
3: fffc03 10:00:00:05:33:13:95:9a 10.38.66.73 0.0.0.0

"B6510_066_073"
19: fffc13 10:00:00:05:33:a5:bf:86 10.38.66.74 0.0.0.0
>"B6510_066_074"
82: fffc52 10:00:00:05:33:13:96:5a 10.38.66.82 0.0.0.0
"B6510_066_082"
83: fffc53 10:00:00:05:33:5b:1d:1d 10.38.66.83 0.0.0.0
"B6510_066_083"

Fabric Name: SSR
2. Check I/O generator tool logs to verify that I/O runs without errors throughout the firmware upgrade.
3. Check the switch logs for errors, and verify that I/O resumes on the node after the firmware upgrade
is complete.
# errdumpall
# portperfshow
Test Results
PASS. I/O operations complete without errors. I/O fails over to an alternate path during the switch
reload after the firmware upgrade, and it resumes after the switch is online. All validation checks pass.
1.3 Storage Device Fibre Channel Routing (FCR) Internetworking

Tests
1.3.1 Storage Device Internetworking Validation with the FC Host
Test Objective
1. Configure two FC fabrics with FCR.
2. Verify that edge devices are imported into adjacent name servers and that hosts have access to
their routed targets after FC routers are configured.
Procedure
Test Execution
1. Set up FCR in an edge-backbone-edge configuration.
2. Set up LSAN zoning, verify host access to target LUNs, and start I/O.
Result Validation
1. Verify the state of the name server and the FCR fabric.
# fcrfabricshow
root> fcrfabricshow
FC Router WWN: 10:00:00:05:33:13:96:5a, Dom ID: 82,
Info: 10.38.66.82, "B6510_066_082"
EX_Port FID Neighbor Switch Info (enet IP, WWN, name)
-------------------------------------------------------------------------------
40 40 10.38.66.88 10:00:00:27:f8:06:23:28 "B6510_066_088"
41 40 10.38.66.92 10:00:00:27:f8:66:f3:81 "B6520_066_92"
FC Router WWN: 10:00:00:05:33:5b:1d:1d, Dom ID: 83,

Info: 10.38.66.83, "B6510_066_083"
53-1004095-01
1.3.2 Storage Device Internetworking Validation with FCoE Using VDX FlexPort

-------------------------------------------------------------------------------
40 40 10.38.66.92 10:00:00:27:f8:66:f3:81 "B6520_066_92"
41 40 10.38.66.88 10:00:00:27:f8:06:23:28 "B6510_066_088"
# fcrproxydevshow
in Fabric in Fabric
------------------------------------------------------------------------
40 10:00:00:05:1e:60:b4:6b 02ff02 100 132400 Imported
40 10:00:00:05:1e:60:b4:6c 02fe02 100 032400 Imported
. . .
100 50:05:07:60:5e:80:76:52 01fe02 40 612800 Imported
100 50:05:07:60:5e:80:76:71 01ff02 40 642300 Imported
Total devices displayed: 20
2. Verify that I/O runs successfully without errors.
Test Results
PASS. I/O completes successfully. Both edge fabrics have the corresponding proxy name-server
entries for the host and target ports.
1.3.2 Storage Device Internetworking Validation with FCoE Using VDX

FlexPort
Test Objective
1. Configure a FC fabric with FCR connected to an FCoE fabric.
2. Verify that edge devices are imported into adjacent name servers and that hosts have access to their
routed targets after FC routers are configured.
Procedure
Test Execution
1. Add the FCoE VCS fabric to the FCR setup.
Result Validation
1. Verify the state of the name server and the FCR fabric.
# fcrfabricshow
root> fcrfabricshow
FC Router WWN: 10:00:00:05:33:5b:7d:06, Dom ID: 97,
Info: 10.38.66.97, "B6510_066_097"
---------------------------------------------------------------------------------
18 110 10.38.66.120 10:00:50:eb:1a:62:8c:33
"VDX6740_066_120"
FC Router WWN: 10:00:00:05:33:5b:10:e8, Dom ID: 100,

Info: 10.38.66.100, "B6510_066_100"
---------------------------------------------------------------------------------
8 110 10.38.66.119 10:00:50:eb:1a:62:83:7b
"VDX6740_066_119"
# fcrproxydevshow
53-1004095-01
in Fabric in Fabric
------------------------------------------------------------------------
110 50:05:07:60:5e:80:76:52 02f001 120 612800 Imported
110 50:05:07:60:5e:80:76:71 02f101 120 642300 Imported
120 10:00:8c:7c:ff:00:48:00 03f101 110 781000 Imported
120 10:00:8c:7c:ff:00:48:01 03f001 110 771000 Imported
2. Verify that I/O runs successfully without errors.
Test Results
PASS. I/O completes successfully. Both edge fabrics have the corresponding proxy name-server
entries for the host and target ports.

Test Objective
1. Configure FCR in an edge-backbone-edge configuration.
2. With IO running, validate device access and pathing.
3. Perform reboots, switch disables, and port toggles on edge connections to disrupt device pathing
and I/O.
4. Verify path and I/O recovery once the switches and ports recover.
Procedure
Test Execution
1. Set up FCR in an edge-backbone-edge configuration.
3. Perform sequential reboots, switch disables, and ISL port toggles on the switches in the edge fabric.
Result Validation
1. Verify the FCR fabric state throughout the disruptions.
# fcrfabricshow
root> fcrfabricshow
Info: 10.38.66.82, "B6510_066_082"
-------------------------------------------------------------------------------
40 40 10.38.66.88 10:00:00:27:f8:06:23:28 "B6510_066_088"
41 40 10.38.66.92 10:00:00:27:f8:66:f3:81 "B6520_066_92"

Info: 10.38.66.83, "B6510_066_083"
-------------------------------------------------------------------------------
40 40 10.38.66.92 10:00:00:27:f8:66:f3:81 "B6520_066_92"
41 40 10.38.66.88 10:00:00:27:f8:06:23:28 "B6510_066_088"
# fcrproxydevshow
in Fabric in Fabric
------------------------------------------------------------------------
53-1004095-01
40 10:00:00:05:1e:60:b4:6b 02ff02 100 132400 Imported

40 10:00:00:05:1e:60:b4:6c 02fe02 100 032400 Imported
. . .
100 50:05:07:60:5e:80:76:52 01fe02 40 612800 Imported
100 50:05:07:60:5e:80:76:71 01ff02 40 642300 Imported
2. Check the switch logs for errors.
# errdumpall
# portperfshow
3. Check host and storage logs, and verify that I/O runs without errors.
Test Results
PASS. I/O fails over to the available switch path and recovers when the disrupted switch is restored.

Test Objective
1. Configure FCR in a backbone-edge configuration.
2. With I/O running, validate device access and pathing.
3. Perform reboots, switch disables, and port toggles on backbone connections to disrupt device
pathing and I/O.
4. Verify path and I/O recovery once the switches and ports recover.
Procedure
Test Execution
1. Connect array target ports to the backbone fabric in an edge-backbone configuration.
3. Perform sequential reboots, switch disables, and ISL port toggles on the switches in the backbone
fabric.
Result Validation
1. Verify the FCR fabric state throughout the disruptions.
# fcrfabricshow
root> fcrfabricshow
Info: 10.38.66.82, "B6510_066_082"
-------------------------------------------------------------------------------
40 40 10.38.66.88 10:00:00:27:f8:06:23:28 "B6510_066_088"
41 40 10.38.66.92 10:00:00:27:f8:66:f3:81 "B6520_066_92"

Info: 10.38.66.83, "B6510_066_083"
-------------------------------------------------------------------------------
40 40 10.38.66.92 10:00:00:27:f8:66:f3:81 "B6520_066_92"
41 40 10.38.66.88 10:00:00:27:f8:06:23:28 "B6510_066_088"
# fcrproxydevshow
in Fabric in Fabric
------------------------------------------------------------------------
53-1004095-01
40 10:00:00:05:1e:60:b4:6b 02ff02 100 132400 Imported

40 10:00:00:05:1e:60:b4:6c 02fe02 100 032400 Imported
. . .
100 50:05:07:60:5e:80:76:52 01fe02 40 612800 Imported
100 50:05:07:60:5e:80:76:71 01ff02 40 642300 Imported
2. Check the switch logs for any errors.
# errdumpall
# portperfshow
3. Check host and storage logs, and verify that I/O runs without errors.
Test Results
PASS. I/O fails over to an available switch path and recovers when the disrupted switch is restored.

1.4.1 Nondisruptive Firmware Upgrade on the Storage Device
Test Objective
1. Perform the firmware maintenance procedure on the storage device.
2. Verify that host I/O continues (with minimal disruption) through the "firmware download" and that
device pathing remains consistent.
Procedure
Test Execution
2. Perform the firmware update on all nodes of the storage array.
Result Validation
1. Check the I/O generator tool logs to verify that I/O completes without errors.
2. Check the host and storage logs for errors throughout the I/O operations.
3. Check the switch logs and port stats for errors or I/O drops.
# errdumpall
# porterrshow
root> porterrshow
sync sig tx rx err
0: 1.7g 2.7g 0 0 0 0 0 0 0 946 1
0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30 1
0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
53-1004095-01
Test Results
PASS. I/O completes successfully throughout the firmware upgrade process.

Test Objective
1. Validate storage/fabric behavior while running a workload simulation test suite.
2. Areas of focus may include random and sequential data patterns of various block sizes and database
simulation.
Procedure
Test Execution
1. Set up four standalone hosts with two multipathed initiator ports for I/O generation.
2. Use the Medusa I/O tool to generate I/O and simulate workloads.
3. Run random and sequential I/O in a loop at block transfer sizes of 512, 4k, 8k, 16k, 32k, 64k, 128k,
256k, 512k, and 1m. Include a nested loop of 100-percent read, 100-percent write, and 50-percent
read/write.
4. Run the File Server simulation workload.
5. Run the Microsoft Exchange Server simulation workload.
Result Validation
# errdumpall
# porterrshow
root> porterrshow
sync sig tx rx err
0: 1.7g 2.7g 0 0 0 0 0 0 0 946 1
0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30 1
0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
Test Results
PASS. All workload runs are monitored at the host, storage, and fabric and complete without I/O errors
or faults.
53-1004095-01

Test Objective
1. Validate storage/fabric behavior while running a virtual workload simulation test suite.
2. Areas of focus include VM environments running de-duplication/compression data patterns and
database simulation.
Procedure
Test Execution
1. Set up an ESX cluster of two hosts with four worker VMs per host.
2. Use the VMware I/O Analyzer tool to generate I/O and simulate workloads.
• Run random and sequential I/O at large and small block transfer sizes.
• Run the SQL Server simulation workload.
• Run the OLTP simulation workload.
• Run the Web Server simulation workload.
• Run the Video on Demand simulation workload.
• Run the Workstation simulation workload.
• Run the Exchange Server simulation workload.
3. Set up VMs with the Medusa I/O tool, and run random and sequential I/O in a loop at block transfer
sizes of 512, 4k, 8k, 16k, 32k, 64k, 128k, 256k, 512k, and 1m. Include a nested loop of 100-percent
read, 100-percent write, and 50-percent read/write.
Result Validation
# errdumpall
# porterrshow
root> porterrshow
sync sig tx rx err
0: 1.7g 2.7g 0 0 0 0 0 0 0 946 1
0 1 0 0 0 0 0
1: 431.1m 431.4m 0 0 0 0 0 0 0 30 1
0 1 0 0 0 0 0
2: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
3: 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
Test Results
PASS. All workload runs are monitored at the host, storage, and fabric and complete without I/O errors
or faults.
53-1004095-01
Test Conclusions
1. A pass rate of 100 percent was achieved on all test cases in the SSR qualification test plan. The
network and the storage were able to handle the various stress and error recovery scenarios without
issues.
2. Different I/O workload scenarios were simulated using Medusa and VMware I/O Analyzer tools, and
sustained performance levels were achieved across all workload types. The Brocade FC fabric
handled both the low-latency and high-throughput I/O workloads with equal efficiency without I/O
errors or packet drops.
3. The results confirm that the Tegile IntelliFlash HA2100EP array interoperates seamlessly with
Brocade FC fabrics, and they demonstrate high availability and sustained performance.
4. The Brocade Gen5 16-Gb FC switches were able to handle the sustained throughput and latency
performance requirements efficiently with fewer ISL trunks. Multiple ISLs to different switches in the
fabric should be set up to provide path redundancy through the fabric.
5. The Monitoring and Alerting Policy Suite (MAPS) heath monitor should be enabled on all switches in
the FC fabric to report fabric-wide events and traffic performance metrics. The additional MAPS
feature of Fabric Performance Impact monitoring should also be enabled to detect bottlenecks in the
form of timeouts and latency.
6. Peer zoning helps reduce the zone database size and the zoning complexity, while providing the
RSCN and hardware resource efficiencies of single-initiator zoning.
7. QoS zoning should be used to classify host-target traffic into high, medium, or low priority zones and
to provide traffic prioritization through the FC fabric for the desired host-target pair by allocating more
resources to the traffic in the higher priority zone.
8. Enabling Emulex ExpressLane on a LUN provides prioritized queuing on the HBA for traffic to that
LUN and also sets the CS_CTL tag on the frame, which allows the traffic to be prioritized through the
FC fabric based on the value of the CS_CTL tag and the corresponding priority level.
9. Host multipath should be configured for optimal availability and performance. Windows MPIO
provides default round-robin behavior across the paths; Linux and VMware systems require a custom
entry to the multipath configuration settings provided by Tegile to efficiently use all available paths
and provide high availability.
10.Configuring the Tegile HA2100EP array in a "dual" active configuration allows for better utilization of
the array resources.
53-1004095-01

Brocade Tegile Ha2100ep Fos 740 VT

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Brocade Tegile Ha2100ep Fos 740 VT

Uploaded by

Copyright:

Available Formats

53-1004095-01

Brocade Fabric Technology

Supporting Fabric OS 7.4.0

Configure DUT and Test Equipment..........................................................................................12

December 2015 53-1004095-01 Initial version.

Purpose of This Document

What's New in This Report

TABLE 1 Storage Array

Tegile HA2100EP HA2100EP Tegile The HA2100EP array is a hybrid-flash array

6510-1...9 BR-6510 Brocade 48-port 16-Gb FC switch

DCX-1 DCX 8510-8 Brocade 8-slot 16-Gb FC chassis

DCX-2 DCX 8510-4 Brocade 4-slot 16-Gb FC chassis

VDX-1,2 VDX 6740 Brocade 48x10GbE and 4x40GbE port switch

Tegile IntelliFlash HA2100EP array 2.1.3.4(150311)-368

Brocade Switches Version

DCX 8510-8 Fabric OS 7.4.0

DCX 8510-4 Fabric OS 7.4.0

6510 + Integrated Routing, Fabric Vision Licenses Fabric OS 7.4.0

VDX 6740 Network OS 5.0.1a

QLogic QLE2672 2-port 16-GB FC HBA Driver 9.1.12.21, firmware 7.01.00

QLogic QLE2562 2-port 8-GB FC HBA Driver 8.07.00.08.07.0-k2, firmware 7.01.00

Emulex OCe14102-UM 2-port CNA adapter Driver 10.2.370.8, firmware 10.2.370.19

DUT ID Servers RAM Processor OS

SRV-1 HP ProLiant DL380p Gen8 16 GB Intel Xeon E5-2620 Windows Server

SRV-2 HP ProLiant DL380p Gen8 32 GB Intel Xeon E5-2690 RHEL 6.5

SRV-3 IBM System x3650 M4 16 GB Intel Xeon E5-2620 RHEL 7 x86_64

SRV-4 IBM System x3550 M3 24 GB Intel Xeon E5645 SLES 12.0

SRV-5 HP ProLiant DL360 Gen7 24 GB Intel Xeon E5645 VMware ESXi

SRV-6 HP ProLiant DL360 Gen7 24 GB Intel Xeon E5645 VMware ESXi

SRV-7 IBM System x3630 M4 24 GB Intel Xeon E5-2420 Windows Server

SRV-8 Dell PowerEdge R710 8 GB Intel Xeon L5520 Windows Server

Finisar 16-Gb Analyzer/Jammer XGIG5K2001153

Medusa Labs Test Tools 6.0.1.148039

VMware I/O Analyzer 1.6.2

Configure DUT and Test Equipment

● Task 1: Brocade FC Fabric Configuration.....................................................................12

Task 1: Brocade FC Fabric Configuration

root> mapsconfig --enablemaps -policy dflt_aggressive_policy

root> mapsconfig --actions raslog,email,sw_marginal,sw_critical

root> bottleneckmon --disable

root> mapsConfig –enableFPImon

root> mapsconfig --show

root> mapsdb --show

DB start time: Mon Apr 20 21:23:31 2015

2 Switch Health Report:

Current Switch Policy Status: HEALTHY

3.1 Summary Report:

Category |Today |Last 7 days |

3.2 Rules Affecting Health:

Category(Rule |Repeat |Rule Name |Execution Time |Object |Triggered |

root> zoneshow --peerzone all

3. Configure Fibre Channel Routing (an Integrated Routing license is required).

Example output of exported devices

Task 2: Tegile IntelliFlash HA2100EP Array Configuration

FIGURE 1 Tegile Data Pool Creation

FIGURE 2 Tegile HA Configuration for the Storage Pool

FIGURE 3 Tegile FC Target Connections

FIGURE 4 Tegile Project Configuration—General Settings

FIGURE 5 Tegile Project Mapping Configuration

FIGURE 6 Tegile Project Creation on Pool-A

FIGURE 7 Tegile Project Creation on Pool-B

FIGURE 8 Tegile Dataset Creation

Task 3: Host Setup