Brocade

Brocade Administration
&
Troubleshooting
10th Jan 2014

Jayaprakash Aridos
Brocade Storage SAN Family
The Leading SAN Connectivity Solutions
for Open Systems & Mainframe Environments
SAN256B-2
(2109-M48)
SAN Fabric Management Tools 16 to 384-ports
1, 2, 4, 10Gbps
SAN256M FC, FICON
(2027-256)
32 to 256-ports
1, 2, 4, 10Gbps
SAN140M FC, FICON
Fabric Manager EFCM (2027-140)
4 to 140-ports
1, 2, 4, 10Gbps
FC, FICON
SAN64B-2
(2005-B64)
32 to 64-ports FC Routing, iSCSI
NEW 1, 2, 4Gbps and Extension
FC, FICON Solutions
SAN32B-3 SAN18B-R (2005-R18)
(2005-B5K) 256B FCR Blade (FC
16 to 32-ports #3450)
1, 2, 4Gbps FC 256B iSCSI (FC #3460)
4 Gbps SAN
SAN16B-2 Switch Module
(2005-B16) for IBM BladeCenter
8 to 16-ports 1, 2, 4Gbps FC
1, 2, 4Gbps FC
Brocade Administration & *10 Gbps on SAN256B in 3Q07
12/30/15 2
Troubleshooting
Brocade Advanced Features
Enhancing Performance and Availability
Feature Description SAN Benefits

Next generation SAN
8 Gbit/sec performance today. 8 Gbit/sec
Double SAN Link
Bandwidth bandwidth. Performanc Improved Performance
e 8 Gbit/sec Inter-Switch Links
Dynamically balance (ISLs)
traffic across multiple 8 Gbit/sec links to next-gen
links and trunk
Dynamic Path groups.
devices
Up to 32 Gbit/sec ISL Trunks
Selection
Infrastructure
Simplification
Build SAN with Simpler SAN topology
up to 32 Gbit/sec Increased SAN Availability
performance
ISL Trunking optimized trunks. Investment Protection
Up to 32Gbit/sec Trunk
Extend native FC Enhanced Business Continuity
links up to 500 km. Improved distances and
Extended Combine with ISL SAN performance for Metro Mirroring
Trunking up to
Fabric 250 km.
and Remote Backup
SAN
Brocade Administration &
12/30/15 3
Troubleshooting
Enhancing Fault Isolation, Management and Security
Hardware Prevents one device Isolate devices from each other in
from communicating to the fabric such that there is no
Enforced another device it is not possible interaction between
authorized to access. SAN devices that are not explicitly
Zoning Enforced at the ASIC defined. Enhance security and fault
level
isolation.
Fabric Monitoring and alerting Enhance Business Continuity

of key SAN statistics
Watch such as perf, error, SAN Improve application availability
security
Alert admin of marginal/hard errors
Advanced Highly granular SAN Enhance performance monitoring

perf. monitoring to
Performance differentiate traffic Simplify capacity planning
Monitoring between devices SAN
Enable bill-back capabilities
Advanced Robust encryption, Enhance Business Continuity

authentication and
Security authorization SAN Protect SAN from hackers
policies
Reduce user errors

12/30/15 4
Troubleshooting
FCIP, FC Routing and Partitioning
Partition the SAN fabric Allows separation of a SAN fabric into

Virtual SAN at port level to isolate smaller fabrics that may overlap and
Fabrics mngt, admin roles, share devices
RSCNs, fabric events
Create HW logical Independent fabric services per

SAN LPARS partition at card level partition allows true Segmentation
Spare
for independent Production ports of data, control and management
managed directors in a traffic
single chassis Test
Backup
FCIP Extends FC links up to Enhanced Business Continuity.

1000s km over IP Improved Global Mirroring and
Tunneling network. FC and FCIP /IP
SAN
Tape Vaulting
Fast Write SAN P
TC
FC Routing Route selected SAN Improve storage resource sharing,

traffic between SAN Enables SAN consolidation,
islands w/o merging Maintains SAN security and fault
fabrics and admin isolation

12/30/15 5
Troubleshooting
Brocade Advanced
Features
FICON
FeatureSpecificDescription
Features SAN Benefits
FICON/FC FICON and FCP zSerie Auto-sensing protocol and port
protocol intermix at the siSerie DS8000 speeds increase flexibility and
Intermix port level.
s
pSeries DS6000 provides greater port level
DS4000
granularity.
xSeries
N-Port Allows multiple Linux Use fewer FCP channels on

Logical Partitions to z9 Mainframe
Virtualization share a single FCP
M48
(NPIV) channel Better channel utilization and

simpler infrastructure
High Integrity Binds Switches to Enhanced Business Continuity.

Fabric for increased M48
Fabrics Security Improved distances/performance
M48 for Metro Mirroring and Remote
(FICON Backup
Cascading)
FICON CUP FICON in-band z9 Simplify management and

management of monitoring of directors
Directors from the In-band M48
Mainframe Management
Single point of management for
Enterprises

12/30/15 6
Troubleshooting
New Hardware from Brocade
10Gbps blade (FC #3470)
6-ports for 10Gbps ISL connectivity using SW, LW and ELW
XFP media
All Brocade directors now offer 10Gbps inter-switch links
Ideal for Long distance, high bandwidth BC/DR solutions
Support distances over 100km
iSCSI blade (FC #3460)

Supports iSCSI initiators and Fibre Channel
target/initiator
8 GigE ports and 8 FC ports (1/2/4 Gbps)
64 iSCSI initiators per port, 512 initiators per blade
Up to 4 blades per SAN256B (2048 tested)

12/30/15 7
Troubleshooting
FOS Enhancements from Brocade
FC Routing and FCIP:
Increased Scalability for the SAN18B-R or FC-FCIP Routing Blade for
M48
Up to 12 Layer 2 switches and 12 FC Routers in the backbone fabric
FCIP tunnels offer QoS capabilities to ensure specific bandwidth
FC and FCIP FastWrite capabilities to enhance long distance mirroring
solutions
Security management:
Complete migration of Secure Fabric OS features in the base FOS
code
A new Security Administrator role for separation of security and
fabric administrators
Tracking of logins to see breaches in the fabric.
Fabric authentication with standards-based improvement for device-
to-fabric attachment (FC-SP DH-CHAP)
IPv6 capabilities for all management interfaces
IP over FC support:
Supporting Broadcast Zoning to reduce device interruption
Targeted for the film industry
When using FC as a common backbone for for host-to-storage and
host-to-host file transfer.
Reducing overall production time and improving the integrity/security
of digital data transfers.
Access Gateway feature added to SAN16B-2 to allow greater scalability and
simplify connectivity
12/30/15 8
Troubleshooting
Brocade Switch Module for BladeCenter
Connecting to McDATA SAN fabrics
Connecting BladeCenter to McDATA fabrics:
2007 use the no-cost feature on Brocade called Access Gateway
2008 use Access Gateway feature or the M-EOS (NI) mode
Do not use the former McDATA/QLogic module

QLogic HW and firmware
Being End-of-Lifed
Not as good a solution as Brocade SAN Switch in long run
2006 2007 2008
Access Gateway Native McDATA

Brocade Interoperability Interoperability
BladeCenter
SAN Switch
Modules
End
McDATA/QLogi Sale
c
FC Switch
Modules

12/30/15 9
Troubleshooting
NPIV & NPV
Two technologies that seem to have come to the fore recently are
NPIV (N_Port ID Virtualization) and NPV (N_Port Virtualization).
NPIV
What NPIV does is allow a single physical N_Port to have multiple WWPNs,
and therefore multiple N_Port_IDs, associated with it. After the normal
FLOGI process, an NPIV-enabled physical N_Port can subsequently issue
additional commands to register more WWPNs and receive more
N_Port_IDs (one for each WWPN). The Fibre Channel switch must also
support NPIV, as the F_Port on the other end of the link would see
multiple WWPNs and multiple N_Port_IDs coming from the host and must
know how to handle this behavior.
N port identifier virtualization (NPIV) provides a means to assign multiple
FC IDs to a single N port. This feature allows multiple applications on the N
port to use different identifiers and allows access control, zoning, and port
security to be implemented at the application level. The following
figureshows an example application using NPIV.

12/30/15 10
Troubleshooting
12/30/15 11
Troubleshooting
NPV
NPV introduces a new type of Fibre Channel port, the NP_Port. The NP_Port
connects to an F_Port and acts as a proxy for other N_Ports on the NPV-enabled
switch. Essentially, the NP_Port looks like an NPIV-enabled host to the F_Port on
the other end. An NPV-enabled switch will register additional WWPNs (and
receive additional N_Port_IDs) via NPIV on behalf of the N_Ports connected to it.
The physical N_Ports dont have any knowledge this is occurring and dont need
any support for it; its all handled by the NPV-enabled switch.
So why is this functionality useful? There is the immediate benefit of being
able to scale your Fibre Channel fabric without having to add domain IDs,
yes, but in what sorts of environments might this be particularly useful?
Consider a blade server environment, like an HP c7000 chassis, where there
are Fibre Channel switches in the back of the chassis. By using NPV on these
switches, you can add them to your fabric without having to assign a
domain ID to each and every one of them.
Benefits of NPIV
Without NPIV, its not possible because the N_Port on the physical host would
have only a single WWPN (and N_Port_ID). Any LUNs would have to be zoned and
presented to this single WWPN. Because all VMs would be sharing the same
WWPN on the one single physical N_Port, any LUNs zoned to this WWPN would be
visible to all VMs on that host because all VMs are using the same physical
N_Port, same WWPN, and same N_Port_ID.
With NPIV, the physical N_Port can
Brocade register additional
Administration & WWPNs (and N_Port_IDs).12
12/30/15
Troubleshooting
Each VM can have its own WWPN. When you build SAN zones and present LUNs
Ex., VMWare hosts & TOPS
LPARS
Ex., SANTap Module in Meritor

12/30/15 13
Troubleshooting
Benefits of Brocade Access Gateway
No cost feature solves real-world SAN issues
Traditional Datacenter Datacenter using Access Gateway
FC FC FC FC
Switch Switch Switch Switch Access Gateway Access Gateway Access Gateway
SAN SW
AG Brocade
Change Cisco
Modes McData
FC FC FC FC
Switch Switch Switch Switch
Access Gateway Access Gateway Access Gateway
Concerns with Bladed Servers: Access Gateway offers these benefits:

Difficult to connect to McDATA fabrics Connects to McDATA Fabrics
Limited SAN scalability Simplifies fabric & allows greater scalability
Obscure Admin responsibility (SAN admin vs Clear Admin responsibility
Server admin)

12/30/15 14
Troubleshooting
SAN16B-2 using Brocade Access Gateway
No cost feature simplifies edge connectivity
NEW
Change
Change
16B
16B from
from
SAN16B-2 SAN16B-2 SAN16B-2 Switch
Switch Access Gateway Access Gateway Access Gateway
mode
mode to
to
AG
AG mode
mode
SAN32B-3 SAN32B-3
Typical Core-Edge Topology: Core-Edge Topology with Access Gateway:

One to two core switches Reduce the total number of domains
3 to many edge switches Connect to FOS, M-EOS and Cisco fabrics with NPIV
In this example: In this example:
1 SAN32B-3 core switch 1 SAN32B-3 core switch
3 SAN16B-2 edge switches 3 SAN16B-2 edge Access Gateways
4 domains to manage 1 domain to manage

12/30/15 15
Troubleshooting
AG Feature Support Statement
AG is supported on the 4Gb Brocade SAN Switch Module
for BladeCenter and SAN16B-2:
FOS 5.2.1b or above for SAN Switch Module for
BladeCenter
FOS 5.3+ for SAN16B-2
Access Gateway feature requires that NPIV (N-port ID
virtualization) capability be enabled on the external
switches:
Brocade switches running FOS 5.1 with NPIV enabled
McDATA switches running EOS 9.0 with NPIV enabled
M-EOS 9.6 offers NPIV in base code
Cisco switches running OS 3.0 with NPIV enabled

12/30/15 16
Troubleshooting
Typical AG Deployment Scenarios
Use AG Feature only when needed to help overcome an issue.
Default mode for switch module should always be FC switch.
When to use AG?

Enterprise and large data centers where the fabric size is becoming a burden
Greater than 50 switches in an all b-type (Brocade) fabric
Greater than 30 switches in a fabric that includes m-type (McDATA) products
Connecting BladeCenter or 16B-2 to McDATA or Cisco SAN fabrics
Requires NPIV feature on the external switches
Customers SAN Admin group does not want an embedded switch in server
products (i.e. BladeCenter)
When NOT to use AG?
Connecting SAN targets (such as storage) directly to switch module
Environments where customers require switch features not supported by AG
ISL Trunking
Long Distance support greater than 10km (using Extended Fabric license)

12/30/15 17
Troubleshooting
Brocade Director Roadmap
Investing Today & Tomorrow
Seamless growth for
all director platforms
2006 2007 2008 & beyond
Next Generation Core

BROCADE AG SAN32B-3 Common Management - EFCM
(BladeCenter) Native Interoperability (M-EOS)
Partitioning
Virtual Fabrics
Features:
1, 2, 4, 8 and 10Gbps
FCP, FICON, FCIP,
FCR, iSCSI, Apps
256B Director
384-ports 1,2,4 Gig
FCP, FICON, FCIP 10Gig blade (ISL) FOS 6.x
iSCSI Blade 8Gbps blades
FC Routing
FCP and FICON
Virtual Fabrics
Native Interoperability (M-EOS)
NPIV
256M Director
256-ports 1,2,4 Gig E/OS 9.6
Hard Partitions NPIV E/OS 9.7
Virtual Fabrics IPv6
Security Ench
10Gbit/sec ISL Interoperability
Interoperability
Open Trunking enhancements and
enhancements and
validation
validation
140M Director
140-ports 1,2,4 Gig E/OS 9.7
10Gbit/sec ISL Interoperability
IPv6
Open Trunking enhancements and
Interoperability
NPIV validation
enhancements and
validation
12/30/15 18
Troubleshooting
Next Generation Core Platform
Consolidating and Scaling Your Infrastructure
2007: 2008-2011:
4Gb products are just now 4Gb directors will connect into hi-perf Core.
becoming prevalent. End-to- Multiple protocols & very high bandwidth allow
End solutions with servers, disk for greatest data center consolidation. 8Gb
and tape. FC devices will start rolling out.
140M 256M 256B Edge

NG Core Director connects
to all 4Gb directors
Next Gen Core

Core
8Gb 8Gb 4Gb
No rip-and-replace for Next Gen SAN.

Seamless growth for all director
12/30/15 platforms. Brocade Administration &
19
Troubleshooting
Networking Fundamentals
FC Topology
Fabric Scalability
Initiator/Target relationship
Switch Ports
FC definitions
ISL Concepts
Cable selection
Host Support
12/30/15 20
Troubleshooting
Design the Fabric for your requirements
Cascad
e Cascade Configurations are
appropriate when: Full
Traffic patterns are localized
onto individual switches mesh
Consider the Fabric Port Mesh Configurations are

Count : appropriate when:
The total number of FC ports in Traffic patterns are evenly
the Fabric, this would include distributed
ALL ports on ALL switches for A Overall bandwidth consumption
fabric, remember that you have is low
dual fabrics, larger numbers The maximum config is four to
should mean moving from five switches
cascade / mesh to core-edge Core-
Core-Edge Configs are
appropriate when:
Edge
Fabric is likely to grow
A flexible system is required
because of unknown or
undefined requirements Brocade Administration &
12/30/15 21
Reliability is required this type Troubleshooting
Fabric or Network
Architectures
Types of architectures are:
Single-Switch
Cascade
Mesh
Core-Edge
Director

12/30/15 22
Troubleshooting
Cascade
Maximum hop count supported is
three

12/30/15 23
Troubleshooting
Mesh
Partial Mesh

12/30/15 24
Troubleshooting
Core-Edge

12/30/15 25
Troubleshooting
Fabric Choices What are
they?

12/30/15 26
Troubleshooting
How many fabrics are show
below?

12/30/15 27
Troubleshooting
Fabric Scalability
Examples of Fabric Scalability
Scale performance by adding

ISLs or additional core
switches
Scale # ISLs
Scale # Core Switches

Scale fabric size by
replacing existing
core with a larger
core
Scale fabric Scale # ports
size by adding
switches
12/30/15
Troubleshooting
28
Design the Fabric for your
requirements
Serviceability using a Dual Fabric Design
Firmware upgrade can be done without I/O interruption if the
following Rolling Upgrade is applied
Dual path is required from server and storage
Add new switches or upgrade current switches easily
1 2 3
Upgrade Upgrade
New Both
Storage Firmware Storage Switches Storage
have New
12/30/15
Troubleshooting Firmware 29
Initiator/Target Relationship
HOST (Initiator) Fabric/Network Controller (Target)
Fibre Channel HBAs

Windows or UNIX
FC SCSI over FC
Application driver Fibre Channel driver
iGroup SCSI
File SCSI iSCSI WAFL
System driver driver
RAID
iSCSI TCP/ SCSI over TCP/IP TCP/

IP
Data ONTA
driver IP (iSCSI)
iSCSI HBAs or Ethernet NICs Fibre Channel or

Serial ATA Attach
SCSI Adapters
LUN

12/30/15 Direct Attached Storage (DAS)
Troubleshooting
30
WWNN and WWPN
Examples
HBA WWNN (World Wide Node
Name)
20:00:00:2b:34:26:a6:54
HBA WWPN (World Wide Port

Name)
21:00:00:2b:34:26:a6:54
22:00:00:2b:34:26:a6:54

12/30/15 31
Troubleshooting
Switch Ports
E_Port - An expansion port connecting two switches to
make a fabric.
F_Port - A fabric port to which an N_Port attaches.
FL_Port - A fabric loop port to which a loop attaches;
needs FL card LED turned on. It is the gateway to the
fabric for NL_Ports on a loop.
G_Port - A generic port that supports either E_Port or
F_Port functionality.
L_Port - Node Loop port; a port supporting the
Arbitrated Loop protocol.
N_Port - A fibre channel port in a fabric or point-to-
point connection.
12/30/15 32
Troubleshooting
SAN Made Easy Auto
Discovery
U_Port What do I want to be when
I grow up?
y/n Is something plugged into the port?

n
o yes
FL_Port y/n Do you want to talk loop?

yes
no
G_Port Im waiting for someone to talk to me
fabric Are you a switch or a fabric point-to-point

F_Port
pt-to-pt device?
switch
E_Port

12/30/15 33
Troubleshooting
FC Definitions
ISL: Inter-Switch Link or a Switch-to-Switch Link; ISLs connect between two
switch nodes to form E_ports.
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 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.
Redundancy: When devices have two or more fabrics and multiple paths
for a source to reach its destination the fabric is considered to have
redundancy. This is critical so that when an initiator primary path fails, the
secondary initiator path will be available so that initiator hosts can still
communicate with their targets, at reduced performance.
Resiliency: The ability of a fabric to adapt to or tolerate a failure of a

component. A fabric is said to have resiliency when it can tolerate 1 or
more device failures from any component within the fabric, whether it is a
switch, ISL, or HBA failure.
RSCN: Registered State Change Notification is the fabric mechanism that

allows notifications to be sent to nodes if a change occurs within the fabric,
ie. device going offline or online on a fabric port.
12/30/15 34
Troubleshooting
SCR: State Change Registrations are used by devices to register to receive
FC Definitions
ISL Oversubscription Ratio: Inter-switch Link Oversubscription Ratio is the ratio of
device, or data input ports that might drive I/O between switches to the number of
ISLs over which the traffic could cross.
ISL Oversubscription = Number of Host Nodes: Number of ISLs, or IO=Nhn:Ni.
Fan-in ratio: The ratio of storage ports to a single host port
Fan-out ratio: The ratio of host ports to a single storage port
Buffer-to-buffer credits: The number of buffer-to-buffer credits determines the

number of Fibre Channel frames that a switch can transmit on a link at one time
before requiring an acknowledgement back from the receiver. Performance
degradation may occur if there arent enough credits available to sustain
communication between switches. As the distance between switches increases,
additional buffer-to-buffer credits are required to maintain maximum performance.
Credits are allocated from a common pool of memory on the switch ASIC.
Formula to approximate # of Credits required over long distance:

Buffer Credits = ((Distance in KM) * (Data Rate) * 1000) / 2112
Data Rate = 1.0625 Mbaud for 1 Gbit/sec Fibre Channel

12/30/15 35
Troubleshooting
Best Practice ISL Oversubscription
A 7:1 ISL oversubscription ratio is aligned with an industry average
of 6:1 fan-out. The trend in the storage industry is that the hosts
to storage ratios are increasing, as is the performance of storage
devices. A 7:1 ISL oversubscription ratio should be targeted in SAN
designs, with the ISL oversubscription ratio being adjusted higher
or lower to meet particular performance requirements. While this
ISL oversubscription ratio is conservative, it is felt that the cost of
not having enough performance and having to reshuffle devices
and ISLs is much greater than the cost of having a few extra spare
ports that can be used to connect SAN devices at a later point in
time.
Rule of thumb: The higher the ISL oversubscription ratio, the lower
the performance and conversely, the lower the ISL
oversubscription ratio, the higher the expected I/O performance.
An ISL oversubscription ratio of 3:1 results in high performance
and fewer available ports while an ISL oversubscription ratio of
15:1 results in lower potential performance and additional
available ports reserved for devices. With the advent of 4Gbps
ISLs, higher oversubscription ratios can exist while maintaining
more than adequate bandwidth (since bandwidth is doubled per
ISL) and higher device port
12/30/15 counts
Brocade for 2Gbps
Administration & devices. 36
Troubleshooting
FC SAN Host Support
OS HBA Multipath Host Cluster Volume Mgr File System
Vendor Emulex / MPIO NetApp DSM / MSCS MMC /
VERITAS DSM for MPIO*VERITAS VCS
NTFS
Qlogic VERITAS VxVM*
Emulex / VERITAS DMP / VERITAS VCS / VERITAS VERITAS
Native 4Gb MPxIO* Native SUN Cluster* VxVM VxFS
JFS/ HFS
HP PVLinks / MC ServiceGuard / LVM /
Native Raw
VERITAS DMP VERITAS VCS VERITAS VxVMVERITAS VxFS
SANpath / JFS/2
Native MPIO HACMP LVM Raw
ext3 / ext2 /
Oracle 9i, 10g RAC /
QLogic QLogic LVM Under Test Reiser /
RH Cluster Suite*
GFS*
ext3
QLogic QLogic Oracle 9i, 10g, RAC ext2
Reiser
QLogic QLogic Novell Clusters NSS
Emulex VMware MSCS VMware VMFS 2.x

QLogic VirtualCenter (VMotion) Raw
12/30/15
* (via PVR) 37
Troubleshooting
Cable Distance Chart

12/30/15 38
Troubleshooting
Zoning and Troubleshooting
Important Commands
Zoning (how to zone)
Zoning Best practices
Troubleshooting Procedure
Basic Troubleshooting

12/30/15 39
Troubleshooting
FC switch tools provided by switch manufacturer
(Brocade)
switchshow
Displays status of the FC switch and all its ports
Show FC nodes currently logged into the switch (depends on
FC zones, if any)
cfgshow
Show zones currently available on the FC switch
Shows information about the current FC configuration and
which zone(s) are enabled
supportshow: Displays switch information for debugging
purposes
ssshow: Displays information about the name server
nsshow: Verifies that clients are logged into the name server
fabricshow: Displays fabric membership information
configure
Changes switch configuration settings.
Switch need to be offline to run this
Brocade Administration & command
12/30/15 40
Troubleshooting
FC switch tools provided by manufacturer
(Brocade) (cont.)
alicreate, zonecreate: Create aliases and zones
cfgcreate, cfgsave, cfgenable,cfgshow: Manage zone

configs
version: Displays firmware version information
portshow, portcfgshow, porterrshow, portLogDumpPort,

portenable, portdisable
Manage ports
diagshow: Displays switch diagnostics
webUI: Web GUI available by browsing to the switch ip adress

nodefind, nszonemeber To search wwns across fabric and
inside zoning
12/30/15
Troubleshooting
41
Switch Zoning
Domain on Brocade Switches
Make sure that the Domain ID is set to a different
value on all switches in a fabric
Example : if there are two fabrics in solution then
the Domain ID on each switch in Fabric A should
be set to an increasing odd number and for Fabric
B set each Domain ID to an increasing even
number
Fabric A 11, 13, 15, 17, etc.
Fabric B 10, 12, 14, 16, etc.
Note: if HP-UX is involved then skip 8, this ID was used for
Loop Configs
Name Server service in fabric that provides
directory services and info about ALL devices in
the fabric
12/30/15 43
Troubleshooting
Define and Implement
Zoning
How do I manage Zoning?
Manage zone physically or Logically
Three components to the zone information
One or more devices are placed in a zone
One or more zones are placed in a configuration
One and only one config is made the effective
Soft Zoning: Name Server assisted
Name Server restricts visibility
Always available when zoning enabled
No reduction in performance
Hard Zoning: Hardware Enforced
Available when certain rule checking criteria are met through
hardware logic checking.
Provides additional security in addition to Soft zoning
Prevents illegal access from bad citizens.
No reduction in performance with hard-Port level zoning.
Available using port or WWN with Brocade 2 Gbit/sec

12/30/15 44
Troubleshooting
Zoning
Zoning Setup Guidelines
Create a detailed diagram of the fabric, showing all the switches
with their ISLs
Create a blowup diagram of each switch in the fabric to account
for devices
Account for private loop devices if they exist
There are special considerations for mixed 1 Gbit/sec and
2Gbit/sec based fabrics
For security reasons, consider disabling a port if the zoned fabric is
going to contain unused ports, with nothing connected to them
Configure one zone at a time and then test it
Do not create all the zones at once; it will be troublesome to debug
After the first zone is setup in the fabric, plug in devices and then test
the connections to confirm that everything is functioning properly
This process may seem a little tedious, but it will save time and money
trying to debug this after creating all the zones and then plugging in
12/30/15 the devices 45
Troubleshooting
Zoning
Implementing Zoning
Naming convention
There typically of three types of devices, server HBA, the storage port, and
the tape port.
These will have an alias.
SRV for servers
STO for Storage
TPE for Tape
For example,
SRV_MAILPROD_SLT5 a server, hostname mailprod, in PCI slot 5
Keep names as small as possible to conserve space in zone database
Minimize duplication in alias definitions where possible
Keep zoning database as clean and accurate as possible
Fabric Name
Fabric name is the name that the fabric is generally known by.
PROD configuration is to easily identify the configuration that can be
implemented and provide the most generic services.
BACKUP_XX, TEST_XX may be used

12/30/15 46
Troubleshooting
Zoning
10 Zoning Rules - Brocade
1) If security is a priority, then a Hard Zone-based
architecture coupled with Hardware Enforcement is
recommended
2) Using aliases, though optional, should force some structure
when defining your zones.
3) Add Secure Fabric OS into the Zone Architecture if extra
security is required.
4) If a SilkWorm 12000 is part of the fabric, then use it to
administer zoning within the Fabric
5) If QuickLoop is required for legacy devices and the switch
is running Brocade Fabric OS v4.x:
QuickLoop / QuickLoop zones cannot run on switches
running Brocade Fabric OS v4.x.
QuickLoop Fabric Assist - Brocade Fabric OS v4.x cannot
have a Fabric Assist host directly connected to it.

12/30/15 47
Troubleshooting
Zoning
10 Zoning Rules - Brocade
6) Before implementing a zone run the Zone Analyzer and

isolate any possible problems.
7) Before enabling or changing a fabric configuration,
verify that no one is issuing I/O in the zone that will
change.
8) Changes to zoning should be done during preventative
maintenance to minimize any potential disruption.
9) After changing or enabling a zone configuration,
confirm that nodes and storage are able to see and
access one another.
10)LUN Masking should be used in conjunction with fabric
zoning for maximum effectiveness.

12/30/15 48
Troubleshooting
Zoning Example Single
Fabric
Host2 Host3
Host1 Host4
zone1
FC Fabric
zone2
What is needed on the hosts
systems and on which systems is
it needed in this configuration?
Storage

12/30/15 49
Troubleshooting
Simple Troublshooting Cmds
cfgactshow |grep cfg =====>to check the current zoneset
config

zoneshow *zone_name* <-- To search in zones
alishow *alias_name* <-- To search in alias
cfgactshow |grep <host_name> To search zone in active
zoneset
switchshow |grep <wwn> <-- to check flogi information
nszonemember <wwn> <-- FCNS database and to check
zoned' objects
portshow <interface> <-- To Show interface
portloginshow <interface> <-- To list port logins
fabricshow <-- To check switch topology

12/30/15 50
Troubleshooting
Zoning Ex.,
Step by step zone creation and activation
cfgactvshow |grep cfg - check the current activated zoneset or configuration
alicreate "S0ADCF1S2P8_HBA2_PROD", "c0:50:76:00:51:3e:00:06" <-- To create fcalias

alicreate "S0ADCF1S2P8_HBA2_LPM", "c0:50:76:00:51:3e:00:07"

zonecreate "USCLSITPS002_S0ADCF1S2P8_HBA2_CX1571_SPA0",
"S0ADCF1S2P8_HBA2_PROD; S0ADCF1S2P8_HBA2_LPM; CX1571_SPA0" <-- To create zone
zoneshow *USCLSITPS002_S0ADCF1S2P8_HBA2_CX1571_SPA0* <--- Check the zone is

created on the switch

cfgsave <-- To save configuration file

cfgadd "Fab2_VF70_10212013", "USCLSITPS002_S0ADCF1S2P8_HBA2_CX1571_SPA0" <-- To
add zone into existing configuration (zoneset)
cfgsave <-- To save latest configuration

cfgenable "Fab2_VF70_10212013" <-- To activate configuration file (activate zoneset)

12/30/15 51
Troubleshooting
Troubleshooting Ideas
Microsoft Word
Document

12/30/15 52
Troubleshooting
Q&A

12/30/15 53
Troubleshooting
THANK U

12/30/15 54
Troubleshooting

Brocade

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Brocade

Enviado por

Direitos autorais:

Formatos disponíveis

Brocade Administration

10th Jan 2014

Feature Description SAN Benefits

Fabric Monitoring and alerting Enhance Business Continuity

Advanced Highly granular SAN Enhance performance monitoring

Advanced Robust encryption, Enhance Business Continuity

Brocade Administration &

Feature Description SAN Benefits

Partition the SAN fabric Allows separation of a SAN fabric into

Create HW logical Independent fabric services per

FCIP Extends FC links up to Enhanced Business Continuity.

FC Routing Route selected SAN Improve storage resource sharing,

Brocade Administration &

N-Port Allows multiple Linux Use fewer FCP channels on

(NPIV) channel Better channel utilization and

High Integrity Binds Switches to Enhanced Business Continuity.

FICON CUP FICON in-band z9 Simplify management and

Brocade Administration &

iSCSI blade (FC #3460)

Brocade Administration &

Do not use the former McDATA/QLogic module

2006 2007 2008

Access Gateway Native McDATA

Brocade Administration &

Brocade Administration &

Ex., SANTap Module in Meritor

Brocade Administration &

Traditional Datacenter Datacenter using Access Gateway

Access Gateway Access Gateway Access Gateway

Concerns with Bladed Servers: Access Gateway offers these benefits:

Brocade Administration &

Typical Core-Edge Topology: Core-Edge Topology with Access Gateway:

Brocade Administration &

Brocade Administration &

When to use AG?

Brocade Administration &

2006 2007 2008 & beyond

Next Generation Core

140M 256M 256B Edge

Next Gen Core

8Gb 8Gb 4Gb

No rip-and-replace for Next Gen SAN.

Consider the Fabric Port Mesh Configurations are

Brocade Administration &

Brocade Administration &

Brocade Administration &

Brocade Administration &

Brocade Administration &

Brocade Administration &

Scale performance by adding

Scale # Core Switches

Fibre Channel HBAs

iSCSI TCP/ SCSI over TCP/IP TCP/

iSCSI HBAs or Ethernet NICs Fibre Channel or

Brocade Administration &

HBA WWPN (World Wide Port

Brocade Administration &

y/n Is something plugged into the port?

FL_Port y/n Do you want to talk loop?

G_Port Im waiting for someone to talk to me

fabric Are you a switch or a fabric point-to-point

Brocade Administration &

Locality: The degree that I/O is confined to a particular switch or segment

zoneshow USCLSITPS002_S0ADCF1S2P8_HBA2_CX1571_SPA0 <--- Check the zone is