Survey Of SAN

Complete Data
Completed For
as
On
Tue Sep 30 2008

SAN Health Client Version : 3.1.5

Reporter Builder Version : 3.1.5
 TABLE OF CONTENTS
SAN SUMMARY
SAN Summary For Complete Data........................................................................................................................................................
Page 3
SAN Ports........................................................................................................................................................ Page 4
Visio Topology Diagram........................................................................................................................................................
Page 5
FABRIC DETAILS
Fabric - TK-606
Fabric Summary and Port Map For TK-606........................................................................................................................................................
Page 6
Zone Summary For TK-606........................................................................................................................................................
Page 7
SWITCH DETAILS
Switch Summary and Port Details For CLPSWTKSCO78........................................................................................................................................................
Page 8
APPENDICES
Explanatory Notes........................................................................................................................................................ Page 10
Glossary........................................................................................................................................................ Page 19
References........................................................................................................................................................ Page 21

Table Of Contents Page 3 of 27

 Tue Sep 30 13:10:15 2008

INTRODUCTION Table OfContents

Site Contact rodolfo ibiapino

nalista
rodolfo.ibiapino@thyssenkrupp.com
11 1111111
Address asdfasdfas
campo limpo
RI
Romania
11111111
SAN Name Complete Data
Audit Data File rodolfo_ibiapino_080930_1310_Complete_Data.BSH
Date Of Audit Tue Sep 30 2008
Number Of Fabrics 1
Number Of Switches 1
Number Of Ports 8

This report contains summary information for all SAN fabrics identified, such as total port count, performance,
oversubscription ratios, port utilization, and number of attached devices followed by specific information on each fabric,
such as the connected switches, zoning configuration, and a port map. A separate section provides switch level
information such as licenses, port level configurations and ISL usage. Port level details such as bandwidth utilization,
CRC counts and port status provides a snapshot on overall port health. Other items in this report include historical
performance graphs plus guidelines and recommendations. The Visio diagram shows the logical connection of the
switches in the fabrics as well as the connected devices. ISLs, trunks and devices are shown exactly how they are
connected to the switch ports. From this diagram, the fabric topology and other information can be viewed quickly and
easily. Customized views of devices allow for online device identification, snapshot of performance stats and switch
attachment details.

The report consists of 3 separate sections with each providing a greater drill down to each level. The SAN summary
view provides an at a glance viewpoint of the entire scanned SAN fabric. A fabric summary and detail section provides
zoning and switch details. The switch summaries provide detailed information on each configuration and an entire list
of ports and associated settings. Throughout each section, information critical to the health of the SAN is highlighted to
allow for actions to be taken if necessary. General guidelines and recommendations are tailored to the gathered
information provided in the SAN Health report.

The following color scheme is used identify if further investigation or action is necessary based upon SAN Health’s
assessment.
RED Critical A situation exists where if not corrected, loss of access to data may occur. Action is necessary.
ORANGE Important A situation exists where if not corrected, may result in a malfunctioning of the SAN.
BLUE Review Further investigation is necessary to assess the impact to the SAN
WHITE Normal Best practices are being adhered to, no further investigation is necessary.

BROCADE SAN HEALTH SOFTWARE AND THESE AUDIT RESULTS ARE PROVIDED FOR INFORMATIONAL PURPOSES ONLY. ALL RECOMMENDATIONS SHOULD
BE REVIEWED AGAINST CURRENT BUSINESS NEEDS AND SYSTEM DESIGN REQUIREMENTS. THIS SOFTWARE AND INFORMATION IS PROVIDED "AS IS"
WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF
MERCHANTABILITY, NONINFRINGEMENT OR FITNESS FOR ANY PARTICULAR PURPOSE. ADDITIONALLY, IN NO EVENT SHALL BROCADE OR ITS SUPPLIERS
BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, LOST DATA, LOSS OF USE OR COSTS OF
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES) INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES
ARISING IN ANY WAY OUT OF THE USE OF OR INABILITY TO USE THIS SOFTWARE OR INFORMATION, UNDER ANY CAUSE OF ACTION OR THEORY OF
LIABILITY, AND IRRESPECTIVE OF WHETHER SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. BROCADE, THE BROCADE B
WEAVE LOGO, SECURE FABRIC OS, AND SILKWORM ARE REGISTERED TRADEMARKS OF BROCADE COMMUNICATIONS SYSTEMS, INC., IN THE UNITED
STATES AND/OR IN OTHER COUNTRIES. FICON IS A REGISTERED TRADEMARK OF IBM CORPORATION IN THE U.S. AND OTHER COUNTRIES. ALL OTHER
BRANDS, PRODUCTS, OR SERVICE NAMES ARE OR MAY BE TRADEMARKS OR SERVICE MARKS OF, AND ARE USED TO IDENTIFY, PRODUCTS OR SERVICES
OF THEIR RESPECTIVE OWNERS.

Introduction Page 4 of 27
 Tue Sep 30 13:10:15 2008

SAN SUMMARY DETAILS FOR COMPLETE DATA Table OfContents

SWITCHES IN SAN Complete Data

Fabric Name Switch Name Domain IP Address World Wide Name Model Speed OS Ver Ports Unused
TK CLPSWTKSCO78 2 10.100.0.28 10:00:00:60:69:c0:63:43 3200 2G 3.2.1c 8 4
SUMMARY FOR 1 SWITCHES TOTALING 8 PORTS THAT ARE 50 % UTILIZED
Switch Count Port Count Port Use Metrics
Fabric Name 1G 2G 4G Total 1G 2G 4G Total ISL Ports Devices Unused Utilization
TK 0 1 0 1 0 8 0 8 0 4 4 50%
DEVICE COUNT FOR ALL FABRICS
Device Description Count Device Description Count
Hitachi Thunder 2 Qlogic HBA 2
PORT USE
Port Use Fan Out Ratios Port Long Distance Modes
Fabric Name Disk Tape Host ISL Free Total Host:Disk Port:ISL Device:ISL 10km 25km 50km 100km Auto
TK 2 0 2 0 4 8 1:1 8:0 4:0 8 0 0 0 0
BANDWIDTH UTILIZATION STATISTICS
Device Bandwidth Utilization (per port) ISL Bandwidth Utilization (per port)
Dev. 0 - 25% 25-75% 75-100% Average Max ISL 0 - 25% 25-75% 75-100% Average Max
Fabric Name Count Av max Av Max Av Max MB/s MB/s Count Av max Av Max Av Max MB/s MB/s
TK 4 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
LICENSE SUMMARY
Full Fabric 1 WEB TOOLS 1 Zoning 1 Trunking 0 SES 0
Perf. Monitoring 0 Fabric Watch 0 Extended Fabric 0 Remote Switch 0 Secure FOS 0
Quick Loop 1 VL2 Upgrade 0 VL4 Upgrade 0
ZONING METRICS
Zone Aliases Statistics Zone Statistics Config Statistics
Fabric Name Database Use Aliases AvMem MaxMemHanging Zones AvMem MaxMemHanging Configs AvMem MaxMemHanging
TK 0.1% of 258k 4 1 1 0 2 2 2 0 1 2 2 0

Complete Data - SAN Summary Page 5 of 27

 Tue Sep 30 13:10:15 2008

DEVICE MAP FOR COMPLETE DATA Table OfContents

TK
Dom Area Slot/Port Speed Port ID Description Name / Alias Model Firmware Driver Port World Wide Name Additional Information
2 0 N/A 2 G 020000 Hitachi Thunder storage_0a 9500 DF600 UnReported UnReported 50:06:0e:80:00:42:93:80 SN17043 Cluster9 PortA
2 2 N/A 2 G 020200 Qlogic HBA esx_hba0a QLA2340 3.03.19 7.08 21:00:00:e0:8b:0e:96:fc vm33.1 2.5GHz PCI-Express Dual Port
2 4 N/A 2 G 020400 Hitachi Thunder storage_0b 9500 DF600 UnReported UnReported 50:06:0e:80:00:42:93:81 SN17043 Cluster9 PortB
2 6 N/A 2 G 020600 Qlogic HBA clsrv020_hba0b QLA2340 3.03.25 9.1.7.16 21:00:00:e0:8b:1d:b7:05 2.5GHz PCI-Express Dual Port

Complete Data - SAN Ports Page 6 of 27

 Tue Sep 30 13:10:15 2008

VISIO TOPOLOGY DIAGRAM Table OfContents

Tips:

1) There are two choices for inserting the Visio diagram, the first is to simply print the diagram from Visio and then use this printout as a
replacement for this page. The second is to use a program such as Snag it from www.techsmith.com to screen capture the diagram and
depending on layout, rotate it by 90 degrees and then paste it on to this page.

2) To view additional device information and parameters when using the Visio diagram, select "Customes Property Window" from the
View menu and then click on any object within the Visio diagram.

3) When printing this report, under the FILE PRINT option, ensure that you select the "Entire Workbook" option to have all sheets print with
the correct page number.

Topology Diagram Page 7 of 27

 Tue Sep 30 13:10:15 2008

FABRIC SUMMARY FOR TK Table OfContents

SUMMARY FOR TK ( 1 SWITCHES IN FABRIC )

Switch Name Domain IP Address
World Wide Name Model Speed OS Ver Status Days Up Switch Date Mode Serial Number Ports Unused
CLPSWTKSCO78 2 10.100.0.28
10:00:00:60:69:c0:63:43 3200 2G 3.2.1c Healthy 18 Sep 30 Native 1000006069c06343 8 4
ATTACHED DEVICE COUNT 3 (Including all NPIV and Loop Devices)
Device Description Count Device Description Count Device Description Count
Hitachi Thunder 2 Qlogic HBA 2
PORT USE
Port Counts Attached Device Types Inter Switch Links Fan Out Ratios Port Speeds Long Distance Modes
Switch Name Total Free Unlcnsd Disk Tape Host Applinc Gtway ISL IFL TrnkMstrTrnkSlv Hst:Trg Dvc:ISL GigE 1G 2G 4G 8G 10G 10km 25km 50km 100k 300k Auto
CLPSWTKSCO78 8 4 0 2 0 2 0 0 0 0 0 0 1:1 4:0 0 0 8 0 0 0 8 0 0 0 0 0
SWITCH COMPONENT HEALTH STATUS
Switch
Pwr Sply Fans Tmp Sns Slot/Port Cards Error Log Msgs
Switch Name CP0 Status CP1 Status High Availability Status
OK Marg OK Marg OK Marg OK MargActve Disbld Flty VacntCritical Error Warn
CLPSWTKSCO78 1 0 0 0 5 0 3 0 0 0 0 0 0 0 0 - - -
LICENSE SUMMARY

Adaptive Networking

12 Ports On Demand

16 Ports On Demand
B-Series Secure FOS
M-Series SANtegrity
Storage Application

4 Ports On Demand

8 Ports On Demand
Extension Services

Integrated Routing

Inter Chassis Links

FICON CUP Zoning

High Performance
Adv. Performance
M-Series Element

2 Domain Fabric

4 Domain Fabric
(E-Port Capable)
Extended Fabric

Mi10k Dynamic
Virtualization
Fabric Watch

M-Series Full

FICON Tape
Partitioning

FICON XRC
FICON CUP
Monitoring
Web Tools

Full Fabric
N Port ID
Trunking
Manager

Volatility
Service
Zoning

Switch Name
CLPSWTKSCO78 Yes Yes - - - - - - - - - - - - - - - - - - Yes - - - - -
ISL / TRUNK SUMMARY
From Switch To Switch ISL or FSPF Furtherest Dynamic Available Bandwidth and Utilization
Name Dom Area Slot/Port Name Dom Area Slot/Port Trunk Type Cost Pnt (Hops) or Static Speed BW Average % Use Peak % Use
No ISLs
BANDWIDTH UTILIZATION STATISTICS
All Active Ports % BW used All ISL Ports % BW used All Host Ports % BW used All Target Ports % BW used
Switch Name
Count Av Peek 0-25 25-75 75-100 Count Av Peek 0-25 25-75 75-100 Count Av Peek 0-25 25-75 75-100 Count Av Peek 0-25 25-75 75-100
CLPSWTKSCO78 4 0 0 4 0 0 0 0 0 0 0 0 2 0 0 2 0 0 2 0 0 2 0 0
PORT MAP
Brocade 3200 Switch Name:CLPSWTKSCO78 WWN:10:00:00:60:69:c0:63:43 IP Address:10.100.0.28 Domain ID:2
Area Slot/Port Port ID Status Type Speed Name / Alias / Zone Model Description Port World Wide NameNode World Wide Name Media SFP Type Bound Lng Dst Avg Perf Max Perf
0 N/A 020000 Online F 2 G AN storage_0a 9500 DF600 Hitachi Thunder50:06:0e:80:00:42:93:80
50:06:0e:80:00:42:93:80Short AGILENT SCSI L0 0 0
1 N/A No_Light 2 Gbps Short AGILENT L0 0 0
2 N/A 020200 Online F 2 G AN esx_hba0a QLA2340 Qlogic HBA 21:00:00:e0:8b:0e:96:fc 20:00:00:e0:8b:0e:96:fcShort AGILENT SCSI L0 0 0
3 N/A No_Light 2 Gbps Short AGILENT L0 0 0
4 N/A 020400 Online F 2 G AN storage_0b 9500 DF600 Hitachi Thunder50:06:0e:80:00:42:93:81
50:06:0e:80:00:42:93:81Short FINISAR SCSI L0 0 0
5 N/A No_Light 2 Gbps Short AGILENT L0 0 0
6 N/A 020600 Online F 2 G AN clsrv020_hba0b QLA2340 Qlogic HBA 21:00:00:e0:8b:1d:b7:0520:00:00:e0:8b:1d:b7:05Short AGILENT SCSI L0 0 0
7 N/A No_Light 2 Gbps ShortCISCO-AGILENT L0 0 0

TK - Fabric Summary Page 8 of 27

 Tue Sep 30 13:10:15 2008

ZONING DETAILS FOR TK Table OfContents

CONFIG "ZoneConfig_120908" IS ACTIVE

Zone Aliases Statistics Zone Statistics Config Statistics Zones in
Database Use Aliases AvMem MaxMemHanging Zones AvMem MaxMemHanging Configs Av NumMax NumHanging Active Config
0.1% of 258k 4 1 1 0 2 2 2 0 1 2 2 0 2
4 ALIASES
Alias Name Alias Member(s)
clsrv020_hba0b 21:00:00:e0:8b:1d:b7:05
esx_hba0a 21:00:00:e0:8b:0e:96:fc
storage_0a 50:06:0e:80:00:42:93:80
storage_0b 50:06:0e:80:00:42:93:81
2 ZONES
Zone Name Zone Member(s)
zone_clsrv020 clsrv020_hba0b storage_0b
zone_esx esx_hba0a storage_0a
1 CONFIG
Config Name Config Member(s)
ZoneConfig_120908 zone_clsrv020 zone_esx
RUNNING CONFIG "ZoneConfig_120908" WITH 2 ACTIVE ZONES
Active Zones Active Zone Member(s)
zone_clsrv020 21:00:00:e0:8b:1d:b7:05 50:06:0e:80:00:42:93:81
zone_esx 21:00:00:e0:8b:0e:96:fc 50:06:0e:80:00:42:93:80

TK - Zoning Details Page 9 of 27

 Tue Sep 30 13:10:15 2008

SWITCH SUMMARY DETAILS FOR CLPSWTKSCO78 Table OfContents

CLPSWTKSCO78 IN FABRIC TK
Switch Name CLPSWTKSCO78 Brocade Model Brocade 3200 Switch FOS Version 3.2.1c
IP Address 10.100.0.28 WWN 10:00:00:60:69:c0:63:43 FOS Build Date Wed Jun 20 13:21:52 2007
FC IP address 0.0.0.0 Domain ID 2 Port Count 8
Vendor Brocade Direct Support Serial Number 10:00:00:60:69:c0:63:43 Unused Ports 4
Switch Status Healthy MAC Address 0:60:69:c0:63:43 ISL Ports 0
Active Config ON (ZoneConfig_120908) Ethernet Port AUTO Switch Speed 2G
Zone DB Use 0.1 % of 258 kbytes Switch Date Tue Sep 30 07:43:45 2008 Switch State Online
POST Enabled QuickLoop Disabled Switch Mode Native
Telnet Timeout Disabled Fabric Watch Not Licensed Role in Fabric Principal
LICENSE SUMMARY
Full Fabric Yes WEB TOOLS Yes Zoning Yes Trunking No SES No
Perf. Monitoring No Fabric Watch No Extended Fabric No Remote Switch No Secure FOS No
Quick Loop Yes VL2 Upgrade - VL4 Upgrade -
I/O PARAMETERS
Buffer Credits 16 Data Field Size 2112 Error Detect Time 2000 Resource Timeout 10000 IOD Setting Disabled
Port ID Mode 1 Distance Mode 0 Interop Mode No Translative Mode 0 DLS Setting Set
ENVIRONMENTAL STATUS
Switch Up Time Last Boot Up At Powered On For Last Reboot Reason
18 Days Fri Sep 12 04:58:31 2008 1935 days Power-on
Fan Status or if OK Speed in RPM Power Supply Status Av CPU Load Prior to Audit
Fan 1 Fan 2 Fan 3 Fan 4 Fan 5 Fan 6 PS 1 PS 2 PS 3 PS 4 1 Min 5 Min 15 Min
OK OK OK OK OK - - - - - - - -
Switch Temperature Sensors Director Blade Temperature Sensors
Sen 1 Sen 2 Sen 3 Sen 4 Sen 5 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot 9 Slot 10
C 39 33 33 - - - - - - - - - - - -
F 102 91 91 - - - - - - - - - - - -
Current Switch Faulty Ports Missing SFPs Power Supplies Temp Sensors Faulty Fans Port Status ISL Status
Alerting Policy Marginal Down Marginal Down Marginal Down Marginal Down Marginal Down Marginal Down Marginal Down
Thresholds 1 2 0 0 - - 1 2 1 2 1 2 - -
MONITORING AND ALERTING
FABRIC WATCH SYSLOG SETTINGS
Status Syslog Status IP Address 1 IP Address 2 IP Address 3 IP Address 4 IP Address 5 IP Address 6
Not Licensed Not In Use - - - - - -
SNMP SETTINGS
Switch Description Switch Location Contact Information
FibreChannelSwitch EndUserPremise FieldSupport
Community Strings : SecretCode(rw) OrigEquipMfr(rw) private(rw) public(ro) common(ro) FibreChannel(ro)
Access Control List : Not Configured Not Configured Not Configured Not Configured Not Configured Not Configured
ISL / TRUNK SUMMARY
From Domain To Domain From Port To Port Speed Bandwidth Type Deskew AvPerf Max Perf
No ISLs
IMPORTANT ALERTS AND WARNINGS
Description None
Error Level Date Stamp Process
PORT DETAILS FOR CLPSWTKSCO78
Port 0 storage_0a Hitachi Thunder 9500 DF600 SN17043 Cluster9 PortA HITACHI DF600F 0000
Av Perf 0 MB/s Port WWN 50:06:0e:80:00:42:93:80 Speed 2 Gbps Port ID 020000 Media ShortWave SFP Type AGILENT
Peak Perf 0 MB/s NodeWWN 50:06:0e:80:00:42:93:80 Type F-Port Status Online LD level L0 Bound SCSI
Tx 1.5g Rx 896m EcIn 0 crc 0 Shrt 0 Lng 0 EOF 0 Eout 44 Sync 4 Link 0 C3D 0 Lsig 0 Rjct 0 Bsy 0
Port 2 esx_hba0a Qlogic HBA QLA2340 [36] QLA2340 FW:v3.03.19 DVR:v7.08-vm33.1
Av Perf 0 MB/s Port WWN 21:00:00:e0:8b:0e:96:fc Speed 2 Gbps Port ID 020200 Media ShortWave SFP Type AGILENT
Peak Perf 0 MB/s NodeWWN 20:00:00:e0:8b:0e:96:fc Type F-Port Status Online LD level L0 Bound SCSI
Tx 896m Rx 1.5g EcIn 0 crc 0 Shrt 0 Lng 0 EOF 0 Eout 307k Sync 4 Link 0 C3D 0 Lsig 0 Rjct 0 Bsy 0
Port 4 storage_0b Hitachi Thunder 9500 DF600 SN17043 Cluster9 PortB HITACHI DF600F 0000
Av Perf 0 MB/s Port WWN 50:06:0e:80:00:42:93:81 Speed 2 Gbps Port ID 020400 Media ShortWave SFP Type FINISAR
Peak Perf 0 MB/s NodeWWN 50:06:0e:80:00:42:93:81 Type F-Port Status Online LD level L0 Bound SCSI
Tx 218m Rx 702m EcIn 0 crc 0 Shrt 0 Lng 0 EOF 0 Eout 60 Sync 5 Link 0 C3D 0 Lsig 0 Rjct 0 Bsy 0
Port 6 clsrv020_hba0b Qlogic HBA QLA2340 [33] QLA2340 FW:v3.03.25 DVR:v9.1.7.16

CLPSWTKSCO78 - Switch Information Page 10 of 27

 Tue Sep 30 13:10:15 2008

Av Perf 0 MB/s Port WWN 21:00:00:e0:8b:1d:b7:05 Speed 2 Gbps Port ID 020600 Media ShortWave SFP Type AGILENT
Peak Perf 0 MB/s NodeWWN 20:00:00:e0:8b:1d:b7:05 Type F-Port Status Online LD level L0 Bound SCSI
Tx 702m Rx 218m EcIn 0 crc 0 Shrt 0 Lng 0 EOF 0 Eout 13m Sync 10k Link 0 C3D 0 Lsig 0 Rjct 0 Bsy 0

CLPSWTKSCO78 - Switch Information Page 11 of 27

Tue Sep 30 13:10:15 2008

CLPSWTKSCO78 - Switch Information Page 12 of 27

Tue Sep 30 13:10:15 2008

CLPSWTKSCO78 - Switch Information Page 13 of 27

 Tue Sep 30 13:10:15 2008

APPENDIX A - Explanatory Notes Table OfContents

SAN Health provides a wealth of information about your SAN and automated recommendations based on the captured data. These notes
provide an explanation of the report organization, captured value meanings and other information to help you best use the report. Important
items are highlighted throughout these notes. Specific guidance will be supplied to ease the investigation and if needed, the troubleshooting
process. These explanatory notes follow the order of the report Table of Contents.

1.1 SAN Summary Section

The SAN Summary section provides tables that summarize the fabrics, switches and devices that compose the SAN which was the subject
of this SAN Health audit. Each table provides high-level data about the switches, overall health and monitoring, overall switch count and
port use, device counts/types, performance statistics, and zoning summaries. Values that merit attention by the SAN administrator are
highlighted in red, orange and blue. If a value is highlighted in one of these colors, it is recommended that action be taken to assess the
impact to your SAN.
1.1.1 Switches in SAN Table
SWITCHES IN SAN EXAMPLE SAN 1
Fabric Name Switch Name Domain IP Address World Wide Name Model Speed FOS Ver Ports Unused
ETS-Fabric-A EDGE18 4 10.32.5.18 10:00:00:60:69:51:74:ed 3800 2G v3.1.2 16 5
ETS-Fabric-A EDGE19 5 10.32.5.19 10:00:00:60:69:51:75:0d 3800 2G v3.1.2 16 6
ETS-Fabric-B CORE39 156 192.168.184.156 10:00:00:60:69:90:0e:c1 3900 2G v4.2.0c 32 23
This table displays information for all switches selected for data capture in your SAN. Caveat: SAN Health displays the Brocade model
number for each switch. Switches purchased through OEMs may have different model numbers printed on their cases.

1.1.2 Health and Monitoring Status Table

HEALTH AND MONITORING STATUS FOR EXAMPLE SAN 1
Switch State Power Supplies Fans Temp Sensors Errors SNMP SysLog
Fabric Name Marg OK Bad Marg OK Bad Marg OK Low OK High Lvl1 Lvl2 No Yes No Yes
ETS-Fabric-A 0 5 0 0 10 0 0 20 0 15 0 0 3 5 0 0 5
ETS-Fabric-B 0 1 1 0 1 0 0 6 0 5 0 0 0 1 0 1 0
TOTALS 0 6 1 0 11 0 0 26 0 20 0 0 3 6 0 6 0
This table provides information about the overall health of each fabric. Each row provides information about one fabric, except the last row
which provides an overall total for all fabrics.
Items to Watch For
The Switch State is determined by the Switch Status Policy settings. If you believe that your switch is incorrectly displayed as Marginal of
Faulty, review the corresponding Switch Status Policy thresholds in the Switch Details section of this report.

The Temperature Sensors are located inside the switch. In some switch models, high temperature readings may be normal. When high
readings are noted in SAN Health, it is important to check that the ambient air temperature at the airflow intake for the switch does not
exceed 40 Degrees Celsius. If that is the case, and all fans are working, then the temperature sensor reading is not a problem.
The Error Levels "PANIC" and "CRITICAL" are added to the Level 1 error count. The Error Level "ERROR" is added to the Level 2 count.
Level 1 errors are rare and should always be investigated immediately. Level 2 errors should be investigated, but are not always indicative
of a real problem. First check the error date on the Switch Details page.

On some switch models up to over two thousand error messages may be stored, so a significant number of historical messages may remain
in memory, which means that many error messages may be left over conditions that occurred long ago, e.g. when the switches were
originally installed or when a major change was made to the fabric. If the error message is recent and/or repeating, or looks serious, you
should contact your support provider.

It is common for the Syslog alert to be highlighted in blue. This means that the switch is not configured to send alert messages to a syslog
server. Configuring a syslog server is always recommended. In extreme error conditions, the log inside the switch may becomes full,
causing important error messages to "scroll" out of memory. Using an external syslog server ensures that all error messages are saved.

Explanatory Notes Page 14 of 27

 Tue Sep 30 13:10:15 2008

1.1.3 SAN Switch and Port Count Summary Table

SUMMARY FOR 6 SWITCHES TOTALLING 112 PORTS THAT ARE 51 % UTILIZED
Switch Count Port Count Port Use Metrics
Fabric Name 1G 2G 4G Total 1G 2G 4G Total ISL Ports Devices Unused Utilization
ETS-Fabric-A 0 5 0 5 0 80 0 80 22 26 32 60%
ETS-Fabric-B 0 1 0 1 0 32 0 32 0 9 23 28%
TOTALS 0 6 0 6 0 112 0 112 22 35 55 51%

This table provides information about switch and port resources for each fabric. Total switch and port counts are reported on the last line.
Items to Watch For
Look at the overall port utilization of each fabric. High utilization indicates that future growth may be difficult unless more ports are added
soon.

1.1.4 Attached Device Count Table

DEVICE COUNT FOR ALL FABRICS
Device Description Count Device Description Count Device Description Count Device Description Count
APPLE 2 CROSSROADS 1 EMC 11 EMULEX 9
HP 6 SEAGATE 5 XIOTECH 1

This table provides information about the number of SAN attached devices, sorted by vendor. The vendor ID is discovered by decoding the
WWN of the device. SAN Health cannot tell from the WWN whether or not the device has been rebadged by an OEM after manufacture, so
the original manufacturer of the device is displayed.
Items To Watch For
A Device type of UNKNOWN indicates that SAN Health was unable to decode its WWN. SAN Health supports a large number of decodes
and it is rare to see an UNKNOWN device. Please help us to improve SAN Health by letting SHAdmin@brocade.com know what the device
is if you see this error. Once added to the WWN Decode tables, all subsequent audits will display the device properly. Also, please let us
know if you believe that a device has been decoded incorrectly.

1.1.5 Port Use Table

PORT USE
Port Use Fan Out Ratios Port Long Distance Modes
Fabric Name Disk Tape Host ISL Free Total Host:Disk Port:ISL Device:ISL 10km 25km 50km 100km Auto
ETS-Fabric-A 16 1 9 22 32 80 0.56:1 2.64:1 0.18:1 80 0 0 0 0
ETS-Fabric-B 9 0 0 0 23 32 0: 9 32:0 9:0 32 0 0 0 0
TOTALS 25 1 9 22 55 112 0.36:1 112 0 0 0 0
This table provides more information about how resources are being used within each fabric.

Items To Watch For

The device types of Disk, Host, Tape, Appliance and Switch are determined by parsing name server information. This is not always
accurate, since some devices do not register enough information with the name server to be certain. In these case, SAN Health makes an
educated guess. For example Emulex, Qlogic, and JNI devices are usually HBAs, so these are counted as hosts. If you believe that SAN
Health is incorrectly typing a particular device please let us know at SHAdmin@brocade.com.
Host:Disk This ratio shows how many hosts are accessing each storage device on average. The industry average seems to be about 6:1
host to storage ports. Higher ratios may be appropriate if hosts are relatively slow or inactive. Lower ratios may be needed if hosts require
top performance from their storage subsystems. If you have high performance hosts and a high H:D ratio, consider deploying more storage
ports to improve performance.
Device:ISL This ratio shows how many devices may potentially try to use each ISL, also known as ISL over subscription. Like the H:D ratio,
acceptable over subscription ratios range widely depending on performance requirements. Over subscription indicates a POTENTIAL for
congestion, but not necessarily a presence of it. High ratios are acceptable if devices are running slowly, or traffic is intermittent, or some IO
is localized within switches and therefore does not need to cross the ISLs.
Port:ISL This ratio shows what the potential for congestion will be if all ports are filled with devices. A low number could mean that ISL
connections can be eliminated to save cost. A high number could mean that ISLs need to be added to improve performance.
In the Port Use details, pay attention to the number of free ports in each fabric so that growth can be accommodated.
In the Long Distance Modes column, it is typical that most ports will be set for 10km. Longer distance connections are possible with an
Extended Fabric license and additional switch configuration.

Explanatory Notes Page 15 of 27

 Tue Sep 30 13:10:15 2008

1.1.6 Bandwidth Utilization Statistics Table

BANDWIDTH UTILIZATION STATISTICS
Device Bandwidth Utilization (per port) ISL Bandwidth Utilization (per port)
Dev. 0 - 25% 25-75% 75-100% Average Max ISL 0 - 25% 25-75% 75-100% Average Max
Fabric Name Count Av max Av Max Av Max MB/s MB/s Count Av max Av Max Av Max MB/s MB/s
ETS-Fabric-A 26 26 13 0 13 0 0 14 69 22 22 16 0 6 0 0 14.7 58
ETS-Fabric-B 9 9 8 0 1 0 0 11.3 44 0 0 0 0 0 0 0 0 0
TOTALS 35 35 21 0 14 0 0 12.6 22 22 16 0 6 0 0 7.4

This table shows the bandwidth utilization for each fabric. The devices and ISLs are counted by percent usage of the available full duplex
bandwidth of that port. For example, a device producing 100MB/s of traffic on a 1G, 2G or 4G switch would be displayed as 50%, 25%, and
12.5%, respectively, for the different switch speeds. The maximum and average values are provided in Mbytes/sec.

Items to Watch For

Red or Orange means that congestion may impact the performance of your SAN. If this is the case, you should review the performance
graphs for the switches in question, collect longer term samples, and then use this data to determine if device placement or ISL layout may
be optimized.

1.1.7 License Summary Table

LICENSE SUMMARY
Full Fabric 6 WEB TOOLS 6 Zoning 6 Trunking 6 SES 6
Perf. Monitoring 6 Fabric Watch 6 Extended Fabric 6 Remote Switch 6 Secure FOS 6
Quick Loop 6 VL2 Upgrade 0 VL4 Upgrade 0

This table shows the number and type of licenses present in the SAN. This information can be helpful in determining if all required licenses
exist for existing functionality, or for new features intended for later deployment. For detailed information on each licensed feature, refer to
the product documentation available in the technical library on Brocade Connect or the Brocade Partner Network.

Full Fabric: Required to connect more than 1 other switch to the switch with this license.
WEB TOOLS: Required for web based switch and Fabric OS element management tasks.
Zoning: Required for establishing zoning configurations whereby device-to-device access is controlled and easily modified.
Trunking: Allows for multiple physical ISL connections to be logically considered as one and their bandwidth to be agregated.
SES: SCSI Enclosure Services allows for detailed information about e.g. a RAID array to be passed to a host.
Perf. Monitoring: Required for detailed performance monitoring within WEB TOOLs.
Fabric Watch: Required for a highly configurable in-band switch monitoring capability.
Extended Fabric: Required for connecting switches to form a fabric with greater than 10km between them.
Remote Switch: Required for connecting switches to older FCIP gateway devices. Not commonly used or needed today.
Seure FOS: Provides a policy based secure environment based on PKI and a heiracical security model.
Quick Loop: Required for legacy private loop only HBAs.
VL2 Upgrade: Required to upgrade a Value Line switch from a 2 domain fabric limit.
VL4 Upgrade: Required to upgrade a Value Line switch from a 4 domain fabric limit.

1.1.8 Zoning Metrics Table

ZONING METRICS
` Zone Aliases Statistics Zone Statistics Config Statistics
Fabric Name Database Use Aliases AvMem MaxMem Hanging Configs AvMem MaxMem Hanging Configs AvMem MaxMem Hanging
ETS-Fabric-A 1.4% of 98k 28 1 1 0 6 3.2 7 0 1 6 6 0
ETS-Fabric-B 4.5% of 127k 15 1 1 8 4 5.5 9 4 1 4 4 1
TOTALS 43 1 1 8 10 4.4 9 4 2 5 6 1
This table shows summary zoning configuration data for each fabric. More detail can be found in the fabric and switch sections.

Items to Watch For

Although the actual zone database size in this example does not appear to be large, zoning data is highly compressed and it is unusual to
see zone database usage greater than 70%.
If SAN Health alerts on the zone database use, this field will be highlighted yellow or red. You should review all zone data to look for items
such as hanging zones, and remove any old or uneccessary zoning information. You may also want to review the naming convention that
you use as an uneccessarily long naming convention leads to a higher usage of the zone database.
If hanging aliases, hanging zones or hanging configs are found, these fields will be highlighted in blue. A hanging zoning element is one
that has been defined in the zoning configuration, but for which SAN Health can not find the corresponding device in the fabric. If you have
hanging aliases, zones or configs, be sure to investigate and take the appropriate corrective action.

Explanatory Notes Page 16 of 27

 Tue Sep 30 13:10:15 2008

1.1.9 Microsoft Visio Topology Diagram Tab

This section is left blank by default. It is included as a placeholder for you to insert the Visio Diagram of your SAN that was included with the
report. Follow the instructions below to correctly print the Visio topology diagram.

Items to Watch For

Some modifications may be required to print the diagram correctly.
1. Move the first fabric to a convenient location by selecting all Viso objects that define the fabric and dragging it with the mouse. For dual
fabric SANs, usually fabric A is moved on top of fabric B, and offset slightly.
2. Select the grid and resize to the approximate desired size using the handles on the sides or corners.
3. Now setup the page. There are two steps and both require selecting [File][Page Setup] from the menu.
a. Under the Print Setup tab, select the Paper Size attributes appropriate for your printer and the Paper Orientation as either portrait or
landscape. The "fit to 1 page down and 1 page across" setting should be selected for best results.
b. Under the Page Size tab, select "size to fit drawing contents" in the Page Size area of the window.
4. Finally, select [File][Print Preview] and be sure the grid surrounds fabrics in the SAN. Make any final adjustments, then print.

1.1.10 SAN Assessment & Recommendations Tab

This section suggests ways to improve operational efficiency, and to conform to Brocade guidelines and industry best practices.
1.2 Fabric Details Section
This section provides a summary for each fabric, zoning details, and a port map. Values critical to fabric health are highlighted. If a value is
red or orange, action probably needs to be taken. If the value is highlighted in blue, action may or may not have to be taken.
This page has tables that provide insight into the switches, devices and connections which comprise each fabric.
Fabric Summary Page
1.2.1 Fabric Summary Table
SUMMARY FOR ETS-Fabric-A ( 3 SWITCHES IN FABRIC )
Switch Name Domain IP Address World Wide Name Model Speed FOS Ver Ports Unused Days Up
CORE15 1 10.32.5.15 10:00:00:60:69:51:73:1b 3800 2G v3.1.2 16 6 58
EDGE17 3 10.32.5.17 10:00:00:60:69:51:75:18 3800 2G v3.1.2 16 9 58
This table provides similar information as presented in the SAN Summary section, but at the fabric level.

1.2.2 Health Status And Monitoring Table

HEALTH STATUS AND MONITORING
Switch State Power Supplies Fans Temp Sensors Errors SNMP SysLog
Switch Name Marg OK Bad Marg OK Bad Marg Ok Low OK High Lvl1 Lvl2 No Yes No Yes
CORE15 0 1 0 0 2 0 0 4 0 3 0 0 1 1 0 1 0
CORE16 0 1 0 0 2 0 0 4 0 3 0 0 1 1 0 1 0
EDGE17 0 1 0 0 2 0 0 4 0 3 0 0 0 1 0 1 0
TOTALS 0 3 0 0 6 0 0 12 0 9 0 0 2 3 0 3 0
This is similar to the SAN Summary section, but at the fabric level.
1.2.3 Device Count Table
DEVICE COUNT
Device Description Count Device Description Count Device Description Count Device Description Count
HP 6 CROSSROADS 1 EMC 8 EMULEX 9
This is similar to the SAN Summary section, but at the fabric level.
1.2.4 Port Use Table
PORT USE
Port Use Fan Out Ratios Port Long Distance Modes
Switch Name Disk Tape Host ISL Free Total Host:Disk Port:ISL Device:ISL 10km 25km 50km 100km Auto
CORE15 6 0 0 4 6 16 0: 6 3:1 0.5:1 16 0 0 0 0
CORE16 7 0 0 3 6 16 0: 7 4.33:1 1.33:1 16 0 0 0 0
EDGE17 3 0 0 4 9 16 0: 3 3:1 0.75:1 16 0 0 0 0
TOTALS 16 0 0 11 21 48 0:16 48 0 0 0 0
This is similar to the SAN Summary section, but at the fabric level.

Explanatory Notes Page 17 of 27

 Tue Sep 30 13:10:15 2008

1.2.5 Bandwidth Utilization Statistics Table

BANDWIDTH UTILIZATION STATISTICS
Device Bandwidth Utilization (per port) ISL Bandwidth Utilization (per port)
Dev. 0 - 25% 25-75% 75-100% Average Max ISL 0 - 25% 25-75% 75-100% Average Max
Switch Name Count Av max Av Max Av Max MB/s MB/s Count Av max Av Max Av Max MB/s MB/s
CORE15 6 6 6 0 0 0 0 3.3 28 4 4 4 0 0 0 0 4 25
CORE16 7 7 2 0 5 0 0 17.7 69 3 3 2 0 1 0 0 19.7 55
EDGE17 3 3 2 0 1 0 0 10 36 4 4 4 0 0 0 0 19.2 44
TOTALS 16 16 10 0 6 0 0 10.33 11 11 10 0 1 0 0 14.3
This is similar to the SAN Summary section, but at the fabric level.
1.2.6 ISL / Trunk Summary Table
ISL / TRUNK SUMMARY
From Switch To Switch ISL or Available Bandwidth and Utilization
Name DomainPort Name DomainPort Trunk Type Speed BW Average Use Peak Use
EDGE19 5 10 CORE16 2 10 Trunk Master 2G 2G 31.1 MB/s 16% 55 MB/s 28%
EDGE19 5 9 CORE15 1 9 Slave To P8 2G 22.4 MB/s 11% 58 MB/s 29%
This table contains greater detail on inter-switch links and trunks. The left half of the table shows to which switch and port the ISLs/trunk
groups are connected. The ISL or Trunk Type column shows the configuration: ISL, trunk master or trunk slave. Pay attention to the
average and peak use in the right column. If these values are high, they will be highlighted and action may be required to improve
performance.

1.2.7 License Summary Table

LICENSE SUMMARY
Full Web Fabric Perf. Quick ExtendedRemote SCSI Enc VL Secure
Switch Name Fabric Tools Zoning watch MonitorTrunking Loop Fabric Switch Services Upgrade FOS
CORE15 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes
EDGE17 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes
This is similar to the SAN Summary section, but at the fabric level.
Zoning Summary and Details Page
This section contains tables further details about the zoning within the fabric. As usual, important values will be flagged.
1.2.8 Active Config Table
CONFIG "ETS_B" IS ACTIVE
Zone Aliases Statistics Zone Statistics Config Statistics Zones in
Database Use Aliases AvMem MaxMem Hanging Zones AvMem MaxMem Hanging Configs Av Num Max Num Hanging Active Config
1.4% of 98k 28 1 1 0 6 3.2 7 0 1 6 6 0 6
The table heading displays the name of the active configuration in the fabric at the time of data capture. The zone database use column tells
you if you are in danger if hitting a zone scalability limit. If so, look for hanging zone objects. These objects can potentially be removed,
which would reduce database use and simplify the overall zoning configuration.
1.2.9 Aliases Table
4 ALIASES
Alias Name Alias Member(s)
ETS_BACKUP01 10:00:00:00:c9:27:2e:f1
ETS_BOOTP01 10:00:00:00:c9:2b:9d:ac
The table heading shows the number of aliases defined in the zoning database, and the table shows each alias definition. Hanging alias
members are highlighted in blue. These should be investigated, and removed if the corresponding WWNs are really inactive.

1.2.10 Zone Table

3 ZONES
Zone Name Zone Member(s)
BACKUP_ZONE ETS_BACKUP01 IT_TAPE
FILE01_ZONE ets_hsg80_1 ets_hsg80_2 ets_hsg80_3 ETS_FILE01_1
ETS_FILE01_2 FC4700_WIN_SPA1 OLD_ETS_FILE01
The table heading provides the number of zones defined in the zoning database, and the table lists zones and their members. Hanging
members are highlighted. Note that if a multiple zones contain the same hanging alias, all will be highlighted.

Explanatory Notes Page 18 of 27

 Tue Sep 30 13:10:15 2008

1.2.11 Config Table

1 CONFIG
Config Name Config Member(s)
ETS_SAN FILE01_ZONE NFS01_ZONE WEB01_ZONE
IMAGE01_ZONE BACKUP_ZONE APPLE_ZONE
The table heading shows the number of zoning configurations defined, and the table lists config names their and members. Hanging
members are highlighted. Note that if a multiple configs contain the same hanging zone, all will be highlighted.
1.2.12 RUNNING CONFIG WITH ACTIVE ZONES
RUNNING CONFIG "ETS_SAN" WITH 6 ACTIVE ZONES
Active Zones Active Zone Member(s)
BACKUP_ZONE 10:00:00:00:c9:27:2e:f1 10:00:00:e0:02:02:88:24
FILE01_ZONE 50:00:1f:e1:00:15:70:b0 50:00:1f:e1:00:15:70:a0 50:00:1f:e1:00:15:71:40 10:00:00:00:c9:2b:4f:b5
10:00:00:00:c9:2b:50:a5 50:06:01:61:40:04:c2:fd 10:00:00:00:c9:2b:52:b6
The table heading shows the number of zones in the active configuration, and the table lists active zones and their members. Hanging zone
members are highlighted. Note that if a multiple active zones contain the same hanging WWN, all will be highlighted.
Items to Watch For
Hanging aliases, zones, and configurations can fill up the zoning database. Removing hanging zone objects can free up zone database
space, and will also simplify other ongoing administrative tasks.

1.2.13 Port Map Page

This section has a table with information about every port in the fabric. Important items are highlighted. These include the port status,
whether or not a device is in a zone, and performance statistics that exceed thresholds.
Domain Port Speed Status Type World Wide Name Alias Name Description Avg Perf Max Perf Port ID
1 0 2 Gbps Online F-Port 60:00:39:30:00:00:4e:a1 APPLE1 APPLE 1.8 MB/s 13 MB/s 010000
1 13 2 Gbps Online F-Port 10:00:00:00:c9:2d:03:71 NOT ZONED EMULEX 0 MB/s 0 MB/s 040d00
1 3 2 Gbps No_Light

Items to Watch For

Port status should be normally Online or No_light. If not, root cause analysis is recommended. The most common cause is cable or SFP
issues. Also check the device driver installation and configuration.
High bandwidth utilization on a port will attract an alert, this may be a sign of congestion or over subscription of a device and should be
investigated. e.g a disk port with too many high performance hosts assigned to it.
A device will be highlighted when SAN Health cannot find a corresponding zone for a device and zoning is enabled. Devices in this state
are unable to pass I/O on the fabric and you should expect to see the performance values at 0 MB/s.
A Segmented ISLs occurs when the Fabric I/O parameters for the switches on each end of the ISL are different or when a zoning conflict
occurs. Segmented ISLs will be highlighted and the port details page for the switch will usually have additional information on the cause.

1.3 Switch Details Section

This section has information about each switch. Each subsection is populated with values gathered in the data capture process.
Values critical to switch health are highlighted. If a value is red or orange, action should be taken. If the highlight is blue, action may or may
not have to be taken. It is important to review each highlighted item to understand the potential impact to your SAN.

Explanatory Notes Page 19 of 27

 Tue Sep 30 13:10:15 2008

1.3.1 Switch Summary Table

SWITCH SUMMARY FOR CORE15 IN FABRIC ETS-Fabric-A
Switch Name CORE15 Brocade Model Silkworm 3800 FOS Version v3.1.2
IP Address 10.32.5.15 WWN 10:00:00:60:69:51:73:1b FOS Build Date Wed Feb 25 18:22:56 2004
FC IP address 0.0.0.0 Domain ID 1 Port Count 16
Vendor Brocade Communications Serial Number 10:00:00:60:69:51:73:1b Unused Ports 6
Switch Status HEALTHY/OK MAC Address 0:60:69:51:73:1b ISL Ports 4
Active Config ON (ETS_SAN) Ethernet Port AUTO Switch Speed 2G
Zone DB Use 1.4 % of 98 kbytes Switch Date Thu Apr 29 19:00:22 2004 Switch State Online
POST Enabled QuickLoop Disabled Switch Mode Native
Telnet Timeout Not Set Fabric Watch Alarms are enabled Role in Fabric Principal

This table has detailed switch configuration information. The heading has the name of the switch and the fabric of which it is a member.
Items such as Zone DB usage, Telnet Timeout, and Switch State will highlighted if values are not within guidelines.
The Switch Status field's value reflects the output of the switchStatusShow Fabric OS CLI command, which is based on values set by
switchStatusPolicySet. The Active Config field displays the status and name of the currently enabled zoning configuration. POST stands
for Power On Self Test. Most switches are set to run POST diagnostics with each cold boot. A fastboot will not initiate POST. The Switch
State is usually online or offline. Error conditions will be highlighted.

Items to Watch For

Pay attention to the Switch Status, Zone DB Use, Fabric OS Version and Unused Ports.
1.3.2 License Summary Table
LICENSE SUMMARY
Full Fabric Yes WEB TOOLS Yes Zoning Yes Trunking Yes SES Yes
Perf. Monitoring Yes Fabric Watch Yes Extended Fabric Yes Remote Switch Yes Secure FOS Yes
Quick Loop Yes VL2 Upgrade No VL4 Upgrade No
This is similar to the SAN Summary section, but with information for a particular switch. For additional detail on the values and what they
mean, refer to the SAN Summary section.
1.3.3 I/O Parameters Section
I/O PARAMETERS
Buffer Credits 16 Data Field Size 2112 Error Detect Time 2000 Resource Timeout 10000 IOD Setting set
Port ID Mode 1 Distance Mode 0 Interop Mode No Translative Mode 0 DLS Setting 0
This section contains a table with information about the I/O parameters set on the switch. All of these settings can be configured under the
Fabric parameters area with the switch offline using the configure CLI command. (The exceptions are IOD and DLS.) Most of these
parameters never need to change from default values.

Buffer Credits -- Number of buffer-to-buffer credits available for an ISL. The default is usually 8 or 16.
Data Field Size -- Fibre Channel Frame Payload size. The default is 2112 bytes
Resource Timeout -- Also known as RA_TOV, this allows devices to discard FC frames after too much time has passed.
IOD Setting -- A setting for FSPF which guarentees in order delivery in failure modes at the expense of fabric convergance speed.
DLS Setting -- Dynamic Load Sharing is a setting for FSPF which affects performance.
Port ID Mode -- A fabric wide switch setting that is either native (0), core (1) extended edge (2)
Distance Mode -- Weather or not the switch is enabled for 10km or greater connectivity
Interop Mode -- A mode to enable multivendor fabric connectivity. Using this setting violates most OEM support matricies.
Translative Mode -- A QuickLoop setting only applicable to early versions of Fabric OS
Important Items to Watch For
The switch Port ID format setting will be either native (0), core (1) or extended edge(2). With native PID mode, only older switches with 16
ports or less can be added non-disruptively. If switches with more than 16 ports need to be added, each switch in the fabric should be
changed to core or extended edge settings. Be aware to potential impact to hosts and HBAs that use the PID for persistent target/LUN
binding: using the extended edge setting can mitigate the impact of a PID format change to a running fabric. The vast majority of Brocade
switches deployed in the field today use the core setting by default, as do all new switches currently shipping.

Explanatory Notes Page 20 of 27

 Tue Sep 30 13:10:15 2008

1.3.4 Environmental Status Table

ENVIRONMENTAL STATUS
Switch Up Time Last Boot Up At Powered On For Last Reboot Reason
58 Days Tue Mar 2 01:48:13 2004 328 days, 1:50 Reboot
Fan Status or if OK Speed in RPM Power Supply Status Av CPU Load Prior to Audit
Fan 1 Fan 2 Fan 3 Fan 4 Fan 5 Fan 6 PS 1 PS 2 PS 3 PS 4 1 Min 5 Min 15 Min
9900 10260 9990 9840 N/A N/A OK OK N/A N/A N/A N/A N/A
Switch Temperature Sensors Director Blade Temperature Sensors
Sen 1 Sen 2 Sen 3 Sen 4 Sen 5 Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7 Slot 8 Slot 9 Slot 10
C 40 34 33 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
F 104 93 91 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
Current Switch Faulty Ports Missing SFPs Power Supplies Temp Sensors Faulty Fans Port Status ISL Status
Alerting Policy Marginal Down Marginal Down Marginal Down Marginal Down Marginal Down Marginal Down Marginal Down
Thresholds 1 2 0 0 1 2 1 2 1 2 0 0 0 0
This table has detailed information on the switch environmental status. Where as the Monitoring and Alerting table in the Fabric Details
showed summary information for the entire fabric, this section is focused on displaying much greater environmental status detail gathered
from the switch itself.
These settings are configured by using switchStatusPolicySet, WEBTOOLs or Fabric Manager.
Items to Watch For
Be sure to investigate any highlighted items. Specific actions will be provided in the recommendations section. If a non-director class
switch is being displayed, be aware that the values of the Director Blade Temperature Sensors will be N/A. This is normal. Some highlights
may seem inappropriate dependant on your requirements. For example, switches configured for redundant power but only connected to
one power source are flagged. If this condition is normal in your data center, you can modify the switchStatusPolicy settings to prevent
future warning messages.

1.3.5 Monitoring and Alerting Table

MONITORING AND ALERTING
FABRIC WATCH SYSLOG SETTINGS
Status Syslog Status IP Address 1 IP Address 2 IP Address 3 IP Address 4 IP Address 5 IP Address 6
enabled Not In Use N/A N/A N/A N/A N/A N/A
SNMP SETTINGS
Switch Description Switch Location Contact Information
FibreChannelSwitch. EndUserPremise FieldSupport.
Community Strings : SecretCode(rw) OrigEquipMfr(rw) private(rw) public(ro) common(ro) FibreChannel(ro)
Access Control List : Not Configured Not Configured Not Configured Not Configured Not Configured Not Configured
This table provides information about switch monitoring and alerting configuration status. Whereas the Monitoring and Alerting table in the
Fabric Details showed summary information for the entire fabric, this section is focused on settings for a particular switch.
Parameters are configured by the switchStatusPolicy settings. Areas that are monitored include, power supplies, fans/blowers,
temperatures, CPU load, and switch uptime.
1.3.6 ISL/Trunk Summary Table
ISL / TRUNK SUMMARY
From Domain To Domain From Port To Port Speed Bandwidth Type Deskew AvPerf Max Perf
1 5 9 9 2G Slave To P8 16 3 MB/s 18 MB/s
1 5 8 8 2G 4G Trunk Master 15 3 MB/s 18 MB/s
1 4 5 5 2G Slave To P4 15 5.2 MB/s 25 MB/s
1 4 4 4 2G 4G Trunk Master 16 5.2 MB/s 25 MB/s
This table has details about ISLs connected to the switch. The values are explained in the ISL/Trunk table in under Fabric Details.
1.3.7 Important Alerts and Warnings Table
IMPORTANT ALERTS AND WARNINGS
Description ZONE-TRANS_ABORT, 2, Zoning transaction aborted - Zone Config update received
Error Level ERROR Date Stamp Tue Apr 06 14:38:19 2004 Process tZone
This table contains switch-oriented alerts and warnings. Anything that appears here should be carefully investigated. If no alerts are
captured, the Description field will have “No Critical Alerts Found”. Be sure to check the date stamp on the alert as it may correspond to the
time of a maintenance event or another known cause. The date stamp should also be checked for age, as some switches store up to 2,000
log messages, alerts may be of historically insignificant.

Explanatory Notes Page 21 of 27

 Tue Sep 30 13:10:15 2008

1.3.8 Port and Device Details Section

PORT DETAILS FOR CORE15 IN FABRIC ETS-Fabric-A
Port 0 APPLE1 Apple XServ RAID
Av Perf 1.8 MB/s Port WWN 60:00:39:30:00:00:4e:a1 Speed 2 Gbps Port ID 010000 Media ShortWave SFP Type AGILENT
Peak Perf 13 MB/s NodeWWN 60:00:39:30:00:00:4e:a1 Type F-Port Status Online LD level L0 Bound SCSCI
Tx 230k Rx 242k EcIn 0 crc 0 Shrt 0 Lng 0 EOF 0 Eout 7.7m Sync 53 Link 3 C3D 0 Lsig 4 Rjct 0 Bsy 0
Port 1 APPLE2 Apple XServ RAID
Av Perf 1.5 MB/s Port WWN 60:00:39:30:00:00:44:11 Speed 2 Gbps Port ID 010100 Media ShortWave SFP Type AGILENT
Peak Perf 11 MB/s NodeWWN 60:00:39:30:00:00:44:11 Type F-Port Status Online LD level L0 Bound SCSCI
Tx 38m Rx 17m EcIn 0 crc 0 Shrt 0 Lng 0 EOF 0 Eout 5.1m Sync 59 Link 6 C3D 0 Lsig 3 Rjct 0 Bsy 0
Port 2 Unused Port
This table has condensed information about all ports on a switch. Each port is labeled with the device name if a device is attached, or if
interconnecting another switch, the ISL and the switch name to which it is attached. It provides the greatest level of detail for a particular
port.

The heading contains the name of the switch and fabric of which the port is a member. The Type field is assigned F_Port, E_Port or FL_Port
depending on what is connected at the other end of the cable. "Lsig" stands for Loss of Signal, "Rjct" for Reject and "Bsy" for Busy. Tx and
Rx are aggregate counters for the number of transmitted and received frames on the port prior to the last time it was cleared. The "Bound"
parameter displays which FC-4 types (upper layer protocol) are used for the port. Most often, this value will usually be SCSI, TCPI/IP or
FICON.

Items to Watch For

The port status should be normally Online or No_light. Ports with nothing attached but powered on will be labeled as Unused Port. Pay
attention to the Tx/Rx, crc, Sync, Lsig, Rjct and Bsy frame counters. High numbers will be flagged. This may mean a bad cable, SFP or
failed switch port. One notable exception is the crc counter. When attaching a 1 Gb/sec device to a 2 Gb/sec port, this value will could be
quite high and still be perfectly normal. Check this case before troubleshooting further if a high crc count is reported.

1.3.9 Historical Performance Graph

The performance graph displays performance values captured in the data gathering process. The Y-Axis is in MB/sec and the X-axis is the
time in minutes. If desired, the graph can be customized. For the procedure, please refer to the SAN Health FAQ.

Explanatory Notes Page 22 of 27

 Tue Sep 30 13:10:15 2008

The performance graph displays performance values captured in the data gathering process. The Y-Axis is in MB/sec and the X-axis is the
time in minutes. If desired, the graph can be customized. For the procedure, please refer to the SAN Health FAQ.

Explanatory Notes Page 23 of 27

 Tue Sep 30 13:10:15 2008
Table Of
APPENDIX B - Glossary Contents

These terms and definitions are provided to ensure a consistent language for describing SANs. This section is not intended to
be all-inclusive.
Blocking
This is the inability of one device to connect to another device. The Brocade Virtual Channel implementation of Fibre Channel
does not block. The term blocking is often confused with the term congestion.
Congestion
If two or more sources contend for the same destination, performance for each source may decrease; however, available
bandwidth is shared fairly by all sources contending for the same destination. Congestion is the realization of the potential of
over-subscription. Congestion may be due to contention for a shared storage port or host port, or an ISL.

Control Processor
The term control processor is associated with a SilkWorm 12000/24000 component/FRU (field replicable unit). The
SilkWorm 2000, 3200, 3800, and 3900 switches do not have a FRU specifically associated with it and when CP is used in the
context of other SilkWorm switches, the reference is to the switch CPU and not a FRU.
Core PID Format
The 24-bit Switch Fabric Port Identification (PID) also known as SID consists of Domain_ID, Area and AL_PA fields.

Core Switch
Also known as a “core fabric switch.” This is one of the switches at the logical center of a Core/Edge fabric. There are
generally at least two core switches per Core/Edge fabric to enable resiliency within the fabric. Ports on a core switch are
normally used for ISLs.
Hosts and storage also connect to the core switch.
DASD
Direct Attach Storage Device
Edge Switch
This is one of the switches on the logical outside edge of a Core/Edge fabric. There are generally many more edge switches
than core switches. Ports on edge switches are used for SAN device connections.
Fabric
One or more interconnected Fibre Channel switches. The term “Fabric” usually refers to the interconnected switches.
Fabric Segmentation
A fabric is unable to resolve the switch configuration parameters during the rebuild process with one or more switches, and
may isolate them from the fabric. Impact: I/O operations are ceased only on those devices losing their access due to
segmentation.
Fabric Topology
A topology is “the logical layout of the components of a computer system or network and their interconnections.” A fabric
topology is the layout of the switches that form a fabric.
Fan-in
The ratio of storage ports to a single host port.
Fan-out
The ratio of host ports to a single storage port.
FRU
Field Replaceable Unit
FSPF
Fabric Shortest Path First protocol. The FSPF protocol was developed by Brocade and subsequently adopted by the Fibre
Channel standards community for allowing switches to discover the fabric topology and route frames correctly. It is now the
industry standard routing protocol for Fibre Channel networks.
Hanging Alias
An Alias entry that has been defined in the zone configuration set, where one or more of it's members are not physically
connected to the fabric.
Hanging Zone
A zone entry that has been defined in the zone configuration set, where one or more of it's members are not physically
connected to the fabric.

Glossary Page 24 of 27
Hanging Zone
A zone entry that has been defined in the zone configuration set, where one or more of it's members are not physically
Tue
connected to Sep 30 13:10:15 2008
the fabric.

Glossary Page 25 of 27
 Tue Sep 30 13:10:15 2008
Hop Count
For evaluating SAN designs, the hop count is identical to the number of ISLs that a frame must traverse to reach its
destination.
ISL Inter-Switch Link.
ISLs connect two switches via E-ports.
ISL Over-Subscription Ratio
The over-subscription ratio for an ISL is the number of different ports that could contend for the use of its bandwidth. If there
are 14 node ports on a switch and two ISLs, the ratio is 14:2, or 7:1. This assumes all ports are 2Gb/sec. If there are a mixture
of 1 Gb/sec and 2Gb/sec, the calculation is a bit more complex. Please refer to the Brocade DDM for details.

Latency
The time it takes for a frame to traverse from its source to its destination is referred to as the latency of the link. Sometimes a
frame is switched from source to destination on a single switch and other times a frames must traverse several hops between
switches before it reaches its destination.
Locality
The degree that I/O is confined to a particular switch or segment of a fabric. If two devices that need to communicate with
each other are located on the same switch or fabric segment, then these two devices are said to have high locality. If these
same devices are located on different switches or segments of a fabric and these two devices
need to communicate with each other, then these devices are said to have low locality.
Logical Switch
The SilkWorm 12000 can contain up to 128 ports in a 14U chassis, configured as two 64-port switches. Each switch is known
as a logical switch and may also be referred to as a domain.
Node
Any SAN device – usually either a host or storage device – that attaches to a fabric.

Over-Subscription
A condition where more nodes could potentially contend for the use of a resource – such as an ISL – than that resource could
simultaneously support, that resource is said to be over-subscribed.
PID bindings
Static mapping between physical and logical devices on a host accomplished via Port_ID (PID).
Redundant Fabric
A SAN composed of two or more independent fabrics The multiple fabric architecture makes dual fabric SANs redundant.

Resilience
The ability of a fabric to adapt to or tolerate a failure of a component.
SAN
A Storage Area Network (SAN) can consist of one or more related fabrics and the
connected SAN devices.
SAN Architecture
The overall design or structure of a storage area network solution. This includes one or more related fabrics, each of which has
a topology. Other components included, such as host, storage, and other SAN devices.
SAN Port Count
The number of ports available for connection by nodes in the entire SAN. The SAN Port Count equals the fabric port count in
a single fabric SAN and is equal to the sum of each fabric’s port count in a multi-fabric SAN.
Scalability
The ease with which a particular design can grow and adapt without requiring a significant change in SAN architecture or
requiring a substantial re-layout of existing SAN devices.
Single Fabric
A SAN composed of a single fabric may be configured to provide one or more paths via different switches of the fabric.
Impact: Offers no Protection at fabric level. All paths are closed when fabric is offline, completely stopping I/Os.

SPOF
A single point of failure. A SPOF in a SAN is any component – either hardware or
software – that could cause a fabric or a SAN to fail.

Glossary Page 26 of 27
 Tue Sep 30 13:10:15 2008
Table Of
APPENDIX C - References Contents

1. Brocade SilkWorm Multiprotocol Router SAN Design Guide (53-0000552-xx)

2. Brocade SilkWorm Design, Deployment, and Management Guide (53-0000366-xx)
3. SAN Migration Guide (53-0000360-xx)
4. LAN Guidelines For Brocade SilkWorm Switches (53-0000350-0x)
5. Exploring Brocade ISL Trunking (53-0000263-0x)
6. Core Switch PID Format Update Best Practices (53-0001626-0x)
7. Zoning Implementation Strategies For Brocade SAN Fabrics (www.brocade.com)
8. Introducing Brocade Multiprotocol Routing Services (white paper on www.brocade.com)
9. SAN Connectivity Using the Brocade SilkWorm Multiprotocol Router (53-0000487-01)
10. Brocade MPRS Solution Guide: Microsoft Cluster Server Over iSCSI (53-0000488-xx)
11. Brocade MPRS Solution Guide: Meta SAN Tape Consolidation (53-0000489-xx)
12. Brocade MPRS Solution Guide: FCIP Remote Site Connectivity (53-0000498-xx)
13. Marginal Link Troubleshooting Guide

References Page 27 of 27