ALL Switch

1
Brocade Communications Systems

Brocade Communications Systems, Inc. is an American technology company
specializing in data and storage networking products. Originally known for its
leadership in Fibre Channel storage networks, the company has expanded its focus
to include a wide range of products for New IP and Third platform technologies.
Offerings now include routers and switches optimized for data center, campus and
carrier environments, IP and Fibre Channel storage network fabrics;
Brocade was founded in August 1995, by Seth Neiman (a venture capitalist, a former executive
from Sun Microsystems and a professional auto racer), Kumar Malavalli (a co-author of the
Fibre Channel specification) and Paul R. Bonderson (a former executive from Intel Corporation
and Sun Microsystems). Neiman became the first CEO of the company.
The company's first product, SilkWorm, which was a Fibre Channel Switch, was released in
early 1997. A second generation of switches was announced in 1999.[3]
On January 14, 2013, Brocade named Lloyd Carney as new chief executive Officer
Brocade hardware products include Fibre Channel SAN directors and switches; ultralow-latency data center switches; Ethernet fabrics, Federal and enterprise Ethernet
(LAN/WLAN) switches; WAN (Internet) routers; application delivery controllers (load
balancers); Fibre Channel fabric extension switches; embedded Fibre Channel and
Ethernet switch blades; Fibre Channel host bus adapters (HBAs); converged Fibre
Channel/Ethernet network adapters (CNAs), and Ethernet transceivers. Other
hardware solutions from Brocade support common protocols including iSCSI, FCIP,
GigE, FICON, FCoE, DCB/CEE, and Layer 4-7 networking protocols
Brocade's first Fibre Channel switch SilkWorm 1000 (SW1000) (released in 1997)
was based on the "Stitch" ASIC and their own VxWorks-based firmware (Fabric OS or
FOS).
In May 2011,[10] Brocade launched the industry's first "Gen 5 Fibre Channel" (16
Gbit/s) SAN platform family including the Brocade DCX 8510 Backbone, 6510 switch
and 1860 Fabric Adapter
In April 2012, Brocade launched the 6505 switch (24-port) entry-level switch.
In March 2013, Brocade launched the 6520 96-port Gen 5 Fibre Channel high-density switch and
announced Brocade Fabric Vision technology. Brocade Fabric Vision technology introduces
advanced diagnostics, monitoring, and management capabilities through a combination of ASIC,
FOS, and Brocade Network Advisor. New features include Brocade Monitoring and Alerting
Policy Suite (MAPS) for fabric-wide threshold configuration and monitoring and Brocade Flow
Vision for data flow monitoring and analysis.
EMC Connectrix DS-4900B SAN Switch
EMC Connectrix DS-4900B Switch: 32, 48, or 64 Ports | 1, 2

and 4 Gbit/sec
The EMC Connectrix DS-4900B is a high-performance, high-availability Fibre Channel switch
that provides high port density for addressing mission-critical storage requirements. With a
flexible architecture that supports 1, 2, and 4 Gbit/sec technology with 32, 48, or 64 ports, the
EMC Connectrix DS-4900B provides an affordable high-port-count, single-domain solution.
The EMC Connectrix DS-4900B provides pay-as-you-grow scalability through flexible Ports
on Demand capabilities. Because it is fully compatible with previous 1 and 2 Gbit/sec devices, as
well as the EMC Connectrix DCX Backbone, the EMC Connectrix DS-4900B protects existing
technology investments while providing a strategic solution for the future.
Key Features and Benefits
Provides up to 64 ports in a single domain and a 2U enclosure for higher density and
more easily managed SAN fabrics with fewer domains
Protects existing investments in EMC Connectrix Fabric OS and EMC Connectrix MEOS*-based environments through native E_Port switch interoperability
Utilizes Ports on Demand capabilities for fast, easy, and cost-effective scalability from 32
to 64 ports in 16-port increments
Enables switch consolidation through its high port count increasing utilization,
lowering management expenses, and reducing fabric complexity
Protects existing device investments with auto-configuring 1, 2, and 4 Gbit/sec

capabilities
Supports full 4 Gbit/sec operations at distances up to 100 kilometers (or 500 kilometers at
1 Gbit/sec) for cost-effective business continuance
Increases network performance with enhanced EMC Connectrix ISL Trunking, which
enables a high-speed data path up to 32 Gbit/sec
Meets high-availability requirements with redundant, hot-pluggable components, nondisruptive software upgrades, and hot code activation
EMC Connectrix optical transceiver modules are available in multiple models to satisfy a
wide range of speed and distance requirements. These Small Form-factor Pluggable
(SFP) modules are optimized for EMC Connectrix storage networking products to
maximize performance, reduce power consumption, and help ensure the highest
availability of mission-critical applications.

EMC Connectrix DS-5000B Switch: 16, 24, or 32 Ports | 1, 2,
and 4 Gbit/sec
A Flexible, High-Performance Midrange SAN Switch designed for rapidly growing
environments, the EMC Connectrix DS-5000B combines scalability with superior investment
protection. It features a flexible architecture that supports native E_Port interoperability for
seamless connectivity into EMC Connectrix Fabric OS (FOS) or M-Enterprise OS (M-EOS)
environments, allowing organizations to non-disruptively expand their existing SAN fabrics. (MEOS fabrics are McDATA switches and directors running Enterprise OS.)
The EMC Connectrix DS-5000B is fully compatible with EMC Connectrix 1, 2, and 4
Gbit/sec devices, including the EMC Connectrix DCX Backbone, protecting existing technology
investments while providing a strategic solution for the future.
Featuring scalable Ports on Demand capabilities, the EMC Connectrix DS-5000B is available in
configurations of 16, 24, or 32 ports in an efficient 1U design. It also provides best-in-class
performance for midrange SAN switches, featuring a non-blocking architecture with as many as
32 ports concurrently active at 4 Gbit/sec full duplex to provide an aggregate bandwidth of 256
Gbit/sec. Organizations can manage the EMC Connectrix DS-5000B through a command line
interface, EMC Connectrix Web Tools, EMC Connectrix Enterprise Fabric Connectivity
Manager (EFCM), or EMC Connectrix Fabric Manager.
Delivers up to 32 ports in an optimized form factor that does not require a rail kit for
deployment in a 19-inch rack
Protects existing investments in EMC Connectrix Fabric OS and M-EOS*-based

environments through native E_Port switch interoperability
Provides industry-leading power and cooling efficiency to reduce Total Cost of

Ownership (TCO) and improve availability
Utilizes EMC Connectrix EFCM 9.x and EMC Connectrix Fabric Manager for easy
deployment within new and existing fabrics
Features Ports on Demand capabilities for fast, easy, and cost-effective scalability from
16 to 32 ports in 8-port increments
Protects existing device investments with auto-configuring 1, 2, and 4 Gbit/sec

capabilities
Meets high-availability requirements with redundant, hot-pluggable components and nondisruptive software upgrades
Utilizes the EMC Connectrix EZSwitchSetup wizard, simplifying installation and

management
EMC Connectrix optical transceiver modules are available in multiple models to satisfy a
wide range of speed and distance requirements. These Small Form-factor Pluggable
(SFP) modules are optimized for EMC Connectrix storage networking products to
maximize performance, reduce power consumption, and help ensure the highest
availability of mission-critical applications.
EMC Connectrix B Series DS-5100B

The Connectrix DS-5100B is an Enterprise class 1U, 40-port Fibre Channel 1, 2, 4 or 8 Gbps
Fibre Channel switch that offers the next generation, single-chip architecture for Storage Area
Networks (SANs). The DS-5100B is designed to function in large-scale enterprise SANs and can
also fit the requirements of small to medium-sized work groups.
Because the DS-5100B has a slim 1U height and a high port count, you can use the DS-5100B to
create very dense fabrics in a relatively small space. With its flexible Ports On Demand (POD)
capability, the DS-5100B provides excellent overall value as the foundation of a SAN with the
ability to grow with an organizations SAN needs.
The DS-5100B is the latest mid-range offer from the Connectrix B-Series family of entry-toenterprise products. It supports the following features:
Up to 40 ports of high-performance 8 Gbps technology and POD scaling from 24 to 32 or 40

ports.
Support for 1, 2, 4, and 8 Gbps auto-sensing Fibre Channel switch and router ports.
FICON, FICON Cascading and FICON Control Unit Port ready.
Two hot-swappable, redundant integrated power supply and fan FRUs.
Universal ports that self-configure as E, F, M, or FL_ ports. EX_Ports are activated on a per
port basis with the optional Integrated Routing license.
Fibre Channel Routing (FCR) service that provides improved scalability and fault isolation
(through the optional Integrated Routing license).
An RJ45 Ethernet management port, that in conjunction with EZSwitchSetup, supports switch
IP address discovery and configuration, eliminating the need to attach a serial cable to configure
the switch IP address and greatly increasing the ease of use.
USB port that provides storage for firmware updates, output of the supportsave command and
storage for configuration uploads and downloads
Single motherboard design with 667 MHz PowerPC 440EPx Reduced Instruction Set Computer
(RISC) CPU and integrated peripherals which provide high performance.
Inter-Switch Link (ISL) Trunking (licensable) which allows up to eight ports (at 2G, 4G, or
8G speeds) between a pair of switches combined to form a single, logical ISL with a speed of up
to 128 Gbps full duplex for optimal bandwidth utilization and load balancing.
Dynamic Path Selection (DPS), which optimizes fabric-wide performance and load balancing
by automatically routing data to the most efficient available path in the fabric.
Rack-mount designed using existing optional rail kits (fixed, sliding, and mid-mount/Telco rail
kits) on a 19 EIA rack.
Industry-leading extended distance support, which enables native Fibre Channel extension
greater than 590 km.
Expanded security for up to 16,000 hardware zones. Hardware zoning is accomplished at the
port level of the switch or by World Wide Name (WWN). Hardware zoning permits or denies
delivery of frames to any destination port address.
Unicast, multicast (255 groups), and broadcast data traffic type, are support.
Brocade Small Form-Factor Pluggable (SFP) or SFP+ optical transceivers support any
combination of Short Wavelength (SWL), Long Wavelength (LWL) or Extended Long
Wavelength (ELWL) optical media among the switch ports.
Fabric Operating System (Fabric OS), which delivers distributed intelligence throughout the
network and enables a wide range of value-added applications including Advanced Web Tools
and Zoning. Optional Fabric Services include: Adaptive Networking with QoS, Extended
Fabrics, Enhanced Group Management, Fabric Watch, ISL Trunking, Integrated Routing, and
End-to-End Performance Monitoring (APM).
Port-to-port latency minimized to 700 nanoseconds through the use of cut-through frame
routing at 8 Gbps.
Extensive diagnostics and system monitoring capabilities, which enhance high Reliability,
Availability, and Serviceability (RAS).
The EZSwitchSetup wizard, which makes SAN configuration a 3-step point-and click task.
Port numbering
The Fibre Channel ports on the DS-5100B are numbered from left to right, in eight-port groups
from 0 to 39
Ports on demand
The DS-5100B can be purchased with 24, 32, or 40 licensed ports. As your needs increase, you
can activate unlicensed ports by purchasing and installing the Ports on Demand optional licensed
product. After it has been installed, the license appears under the licenseShow command as Ports
on Demand license.
By default, ports 0 through 23 are enabled on the DS-5100B. To enable ports 24 through 31,
install a Ports on Demand license key. To enable ports 32 through 39, install another Ports on
Demand license. After you have installed the license keys, you must enable the ports. You can do
so without disrupting switch operation by using the
portEnable command on each port individually. Alternatively, you can disable and re-enable the
switch to activate all ports simultaneously.
Product Description
EMC Connectrix DS-5300B Switch: 48, 64, or 80 Ports | 1, 2,
4 and 8 Gbit/sec
The EMC Connectrix DS-5300B is an 8 Gbit/sec Fibre Channel switch that provides superior
performance and port density for the most demanding SAN environments. With up to 80 ports in
an efficient 2U design, it is an ideal solution for enabling greater data center consolidation and
virtualization throughout the enterprise.
An Enterprise Switch for the most Demanding

Environments
The EMC Connectrix DS-5300B Switch combines 1, 2, 4, and 8 Gbit/sec technology in
configurations of 48, 64, or 80 ports in an efficient 2U design. The combination of port density,
performance, and pay-as-you-grow scalability enables greater server and storage utilization
while reducing complexity for virtualized data centers.
The evolutionary design makes it very efficient in regard to power, cooling, and rack density,
enabling medium- and large-scale server and storage consolidation for greater cost savings and
manageability. The EMC Connectrix DS-5300B also includes Adaptive Networking capabilities
to provide the highest service levels for mission-critical data center applications.
Industry-Leading Performance and Scalibility

The EMC Connectrix DS-5300B features a non-blocking architecture with as many as 80 ports
concurrently active at 8 Gbit/sec (full duplex) with no over-subscription providing an aggregate
bandwidth of 1360 Gbit/sec. This level of performance and connectivity is ideal for expanding
virtual server environments. In addition, enhanced ISL Trunking can supply up to 68 Gbit/sec of
balanced data throughput in a single logical link.
The high port density of the EMC Connectrix DS-5300B uniquely enables fan-out from the core
of the data center fabric with less than half the number of switch devices compared to traditional
32- or 40-port edge switches. As a result, it can provide a single-domain solution that simplifies
fabric management and reduces the data center footprint.
With capabilities such as Ports On Demand scalability from 48 to 64 or 80 ports, the EMC
Connectrix DS-5300B also enables organizations to grow their storage networks when necessary,
in a non-disruptive manner.
To support SAN extension, the EMC Connectrix DS-5300B enables servers and storage devices
to reside up to 600 kilometers apart, helping organizations to implement the most sophisticated
business continuance and disaster recovery initiatives.
Adaptive Networking Service

The EMC Connectrix DS-5300B utilizes EMC Connectrix Adaptive Networking services, a suite
of tools for optimizing fabric behavior and ensuring ample bandwidth for mission-critical
applications. These tools currently include QoS, Ingress Rate Limiting, Traffic Isolation, and Top
Talkers. For additional flexibility and value, the EMC Connectrix DS-5300B also provides
Integrated Routing capabilities to connect switches in different fabrics.
Delivers full 8 Gbit/sec 1:1 performance for up to 80 ports in a single-domain, optimized

2U form factor
Ofers best-in-class port density and scalability for an enterprise SAN switch
Protects existing device investments with auto-sensing 1, 2, 4, and 8 Gbit/sec capabilities
Enables pay-as-you-grow capabilities with Ports On Demand scalability from 48 to 64

or 80 ports
Provides Adaptive Networking services such as Quality of Service (QoS) to help

optimize application performance in consolidated, virtual environments
Improves energy efficiency by combining increased bandwidth with lower power

consumption
Utilizes the EMC Connectrix EZSwitchSetup wizard to simplify installation, and is

Microsoft Simple SAN-compatible
Provides Fibre Channel Integrated Routing capabilities, enabling selective device sharing
while maintaining remote fabric isolation
End-To-End Performance and Reliability

EMC Connectrix 8Gb switches require EMC Connectrix optical transceiver modules, which are
available in a multiple models to satisfy a wide range of speed and distance requirements. These
Small Form-factor Pluggable (SFP) modules are optimized for EMC Connectrix 8Gb products to
maximize performance, reduce power consumption, and help ensure the highest availability of
miss ion-critical applications.
EMC Connectrix ED-48000B Director
Product Description
EMC Connectrix ED-48000B Director: 16, 32 and 48 Ports |
4, 8, and 10 Gbit/sec
With industry-leading 4, 8, and 10 Gbit/sec Fibre Channel and FICON performance, the EMC
Connectrix ED-48000B provides high availability, multiprotocol connectivity, and broad
investment protection for EMC Connectrix Fabric OS and EMC Connectrix M-Enterprise OS
(M-EOS) fabrics. It scales non-disruptively from 32 to as many as 384 concurrently active 4 or 8
Gbit/sec full-duplex ports in a single domain.
Key Specifications
4 Gb/sec port speeds
Up to 384 ports in a single domain
Up to 1152 ports per rack
16, 32, or 48 ports per blade
Hot-swappable Field-Replaceable Units
The EMC Connectrix ED-48000B also provides industry-leading power and cooling efficiency,
helping to reduce the total cost of ownership. In addition, it supports blades for Fibre Channel
Routing, FCIP SAN extension, and iSCSI, and is designed to support a wide range of fabricbased applications. It also supports the EMC Connectrix FC10-6 blade, providing 10 Gbit/sec
Fibre Channel data transfer for specific types of data-intensive storage applications.
A Reliable Foundation for Core-to-Edge SANs

With its fifth-generation, high-performance architecture, the EMC Connectrix ED-48000B is a
reliable foundation for core-to-edge SANs, enabling fabrics capable of supporting thousands of
hosts and storage devices. To provide even higher performance, enhanced EMC Connectrix ISL
Trunking combines up to eight 8 Gbit/sec ports between switches into a single, logical highspeed trunk running at up to 64 Gbit/sec. Other services provide additional Quality of Service
(QoS) and Traffic Management capabilities to optimize fabric performance.
Utilizing EMC Connectrix Fabric OS, the EMC Connectrix ED-48000B also supports native
interoperability with existing EMC Connectrix M-EOS fabrics.
Ideal for Enterprise Applications

The EMC Connectrix ED-48000B is designed to integrate with heterogeneous environments that
include IBM mainframe and open platforms with multiple operating systems such as Microsoft
Windows, Linux, Solaris, HP-UX, AIX, and i5/OS. These capabilities help make it ideal for
enterprise management and high-volume transaction processing applications such as:
ERP
10
Data warehousing
Data backup
Remote mirroring
High-availability clustering
A Cost-effective Platform for High-performance

Designed for use in the EMC Connectrix ED-48000B Director, the EMC Connectrix FR4-18i
SAN Extension Blade provides performance-optimized FCIP as well as Fibre Channel Routing
services.. The EMC Connectrix FR4-18i offers a wide range of benefits for inter-SAN
connectivity, including long-distance SAN extension, greater resource sharing, and simplified
management.
The EMC Connectrix ED-48000B also supports the EMC Connectrix FC4-16IP iSCSI Blade,
which enables cost-effective, easy-to-manage Ethernet connectivity so low-cost servers can
access high-performance Fibre Channel storage resources.
Integrated Fabric Application Mobility

The EMC Connectrix ED-48000B supports the EMC Connectrix FA4-18 blade for a variety of
fabric-based applications increasing flexibility, improving operational efficiency, and simplifying
SAN management. This includes EMC Connectrix OEM and ISV Partner applications for
storage virtualization/volume management, replication, and data mobility, as well as EMC
Connectrix Data Migration Manager (DMM).
Enterprise-Class Directors for Any SAN Environment

High Availability
Combining reliable architectures with fully redundant hardware components and innovative
software, EMC Connectrix directors provide ultra-high availability to meet enterprise-class
availability requirements. As a result, they help support a strategic SAN infrastructure capable of
addressing the most demanding business requirements.
EMC CONNECTRIX DS-6505B

The EMC Connectrix DS-6505B
Switch provides exceptional price/performance value, combining flexibility,
simplicity, and enterprise-class functionality in an entry-level switch.
Designed to enable maximum flexibility and reliability, the Connectrix DS-6505B is
11
configurable in 12 or 24 ports and supports 4, 8, or 16 Gigabits per second (Gb/s)

speeds in an efficiently designed 1U package. It comes standard with a single
power supply with integrated fans. A second, optional power supply provides
additional redundancy for increased resiliency.
CONNECTIVIT y mANAGEmENT
Interface
EMC Connectrix Manager Converged Network Edition 11.1.4
Fabric Operating System 7.0.1 or higher
Advanced Web Tools
SSH, HTTPS, RADIUS
SNMP v3 (FE MIB, FC Management MIB)
SMI-S compliant
Management Access
Call-home integration with Connectrix Manager Converged Network Edition
10/100 Mbps Ethernet (RJ-45), in-band over Fibre Channel, serial port (RJ-45), and
one USB port
Firmware Upgrades
Non-disruptive download and activation Compatibility
Connectrix B Series switches and directors
Diagnostics
D_Port offline diagnostics; POST and embedded online/offline diagnostics including
extensive
RAS features, RAS trace logging, FCping, and Pathinfo (FCtraceroute)
End of manufacturer support

EMC DS-4900B Switch 4Gb 64 Port SAN Switch
Connectrix - Brocade DS- 5000B
Connectrix - Brocade DS-5100B (4G Switch)
Connectrix - Brocade DS-5100B-8G (8G Switch)
2021-01-31
2021-01-31
2021-01-31
INITIAL CONFIGURATION
2014-01-31 2021-01-31
2007-03-01
2008-07-14
2010-01-04
12
When a new switch has arrived for installation into a fabric, it is suggested to use a
serial cable to configure the switch with an IP address. After the IP address is
configured, the serial connection to the switch may be dropped and an SSH, telnet, or
Web Tools session may be used for further switch configuration because of its
convenience and speed.
HyperTerminal on a PC,
To configure the connection in a B-Series environment:

Bits per second: 9600 Data bits: 8
Parity: None Stop bits: 1 Flow control: None
Installation steps
1. Insert the serial cable provided to an RS-232 serial port on the workstation
FOS switches use a straight-through cable
M-EOS switches use a null modem cable
2. Verify the switch has power and is past the POST stage
3. Invoke the ipaddrset command to set the IP address, subnet mask and default
gateway
IP addresses are assigned to the management interface of a switch, director, or
backbone and used to remotely manage the switch through telnet or SSH. A
switch (B5100, B300, etc.) only has a single management interface and only
uses a single IP address.
Directors and backbones require three IP addresses: one for chassis/switch
management and one for each CP blade. The IP addresses used for the CP
blades will always connect to the blades they are assigned, the chassis
management IP will always connect to the active CP.
13
B51:admin> ipaddrset
Ethernet IP Address [10.255.240.72]:
Ethernet Subnetmask [255.255.255.192]:
Gateway IP Address [10.255.240.126]:
DHCP [Off]:
B51:admin> ipaddrshow
SWITCH
Ethernet IP Address: 10.255.240.72
Ethernet Subnetmask: 255.255.255.192
Gateway IP Address: 10.255.240.126
DHCP: Off
On Brocade 300, 5100,5300, 6505, 6510 and 6520 DHCP is enabled by default. If you have the
DHCP server on the same IP subnet as the switch then you can use DHCP to assign IP address to
your switch. If not, you have to assign static IP address.
Enabling DHCP
Connect the DHCP-enabled switch to the network, power on the switch, and the switch
automatically obtains the Ethernet IP address, Ethernet subnet mask, and default gateway
address from the DHCP server. The DHCP client can only connect to a DHCP server on the same
subnet as the switch.
14
Domain IDs
Domain IDs are set dynamically on Brocade switches. The default value is 1. You can change the
domain ID if you want to control the ID number or resolve conflict while merging fabrics. Conflicts
can be automatically resolved if one of the two switchs domain ID is not set persistently.
ATTENTION
Do not use domain ID 0. The use of this domain ID can cause the switch to reboot continuously.
Avoid changing the domain ID on the FCS switch in secure mode. To minimize down time, change
the domain IDs on the other switches in the fabric.
Viewing your Domain ID

1. Log in using account with admin privileges.
2. Issue the fabricShow command
DS_5100:admin> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr Name
------------------------------------------------------------------------1: fffc01 10:00:00:05:1e:02:0e:de 10.246.54.240 0.0.0.0 "DS_200B"
2: fffc02 10:00:00:05:1e:02:93:75 10.246.54.241 0.0.0.0 "DS_5100"
4: fffc04 10:00:00:05:1e:44:b6:00 10.246.54.79 10.10.10.10 >"ED_DCX_B"
Switch ID: The switchs domain_ID and embedded port D_ID.
Setting your Domain ID

Here are the steps to configure Domain ID manually
1. Connect to the switch and log in on an account assigned to the admin role.
2. Enter the switchDisable command to disable the switch.
3. Enter the configure command.
4. Enter y after the Fabric Parameters prompt:
Fabric parameters (yes, y, no, n): [no] y
5. Enter a unique domain ID at the Domain prompt. Use a domain ID value from 1 through 239 for
normal operating
mode (FCSW-compatible). Domain: (1..239) [1] 3
6. Respond to the remaining prompts, or press Ctrl-D to accept the other settings and exit.
7. Enter the switchEnable command to re-enable the switch.
Default timeout on switches is 10 minutes. When changing the timeout value

you can use the login command to restart the login session and use the new
timeout value.
15
B51:admin> date
Tue May 16 15:00:57 UTC 2006
B51:admin> tsclockserver
LOCL
B51:admin> tsclockserver 128.118.25.3
Updating Clock Server configuration...done.
B51:admin> tsclockserver
128.118.25.3
SET SWITCH NAME:

SW:admin> switchname "SJC2_C4_E_B5100"
Committing configuration...
Done.
SJC2_C4_E_B5100:admin> switchname
SJC12_C4_E_B5100:admin> fabricshow
Switch ID Worldwide Name Enet IP Addr FC IP Addr
1: fffc01 10:00:00:05:1e:02:12:a5 10.255.248.32 0.0.0.0
"SJC2_C4_E_B300"
2: fffc02 10:00:00:05:1e:02:ab:21 10.255.248.35 0.0.0.0
>"SJC2_C4_E_B5100"
Switch names can be duplicated in the fabric. To see a list of the existing switch names
and their IP settings, use the command fabricshow.
16
The syslogd facility is used by the syslog server to determine the source of a log
message. In an operating system environment this would be determined by the
subsystem that is logging the message (kernel, mail daemon, system daemons,
etc.). There are also eight local facilities defined by the syslog standard for use
by applications and hardware, these are local0 through local7.
Multiple concurrent logins are supported. An admin role account
can login up to two times, non-admin roles allow up to four logins per account.
17
If you do not use the a option as shown below you will only see users currently
logged into the switch.
B51:admin> userconfig --show a
B51:admin> userconfig --add jdoe -r admin -d "Jane Doe"

Setting initial password for jdoe
Enter new password:
Re-type new password:
Account jdoe has been successfully added.
18
The Remote Authentication Dial-In User Service (or RADIUS) is a protocol for
carrying Authentication, Authorization, and Accounting (AAA) information about
remote user access between a Network Access Server (which desires to
authenticate its links) and a shared Authentication Server. RADIUS is an open
standard (IETF RFC 2865 and RFC 2866).
The Lightweight Directory Access Protocol (or LDAP) is an application protocol
for querying and modifying directory services running over TCP/IP. A directory is
a set of objects with attributes organized in a logical and hierarchical manner.
Note: AAA stands for Authentication, Authorization, and Accounting
19
To implement a highly available solution that provides redundancy and

minimizes the effect of network outages:
Implement multiple RADIUS or LDAP servers on the network
Configure all switches to authenticate with all RADIUS or LDAP servers
Configure all switches to use a local database as secondary authentication
The aaaconfig command is also used to manage the list of LDAP or RADIUS
servers for the switch:
aaaconfig --show
aaaconfig --add | --change server -conf radius|ldap
[-p port] [-d domain] [-t timeout] [-s secret]
[-a chap | pap | peap-mschapv2]
aaaconfig --remove server -conf radius|ldap
aaaconfig --move server -conf radius|ldap to_position
aaaconfig --authspec aaa1[;aaa2] [-backup]
aaaconfig help
20
B51:admin> switchstatusshow
Switch Health Report
Report time: 05/06/2008 09:54:21 PM
Switch Name: B51
IP address: 192.168.176.59
SwitchState: HEALTHY
Duration: 06:23
Power supplies monitor HEALTHY
Temperatures monitor HEALTHY
Fans monitor HEALTHY
Flash monitor HEALTHY
Marginal ports monitor HEALTHY
Faulty ports monitor HEALTHY
Missing SFPs monitor HEALTHY
All ports are healthy
switchstatusshow will display the overall status of the switch that include
internal switch status, faulty ports, missing SFPs, power supplies, temperatures,
fans, portstatus, and ISLStatus. The status may be one of the following:
marginal/warning or down/failed.
switchstatuspolicyshow: This command prints the current policy
parameters for calculating the overall status of the switch. The tolerances for
calculating the status of the switch can be configured with switchstatuspolicyset.
21
The switchshow command can be used to verify the switch is operating

correctly and display information about the switch status.
switchName The switchs name
switchType Model.motherboard-revision, look in module appendix for a
complete listing of switch model types.
switchState The state of this switch: Online, Offline, Testing, or Faulty
switchMode The switch mode, Native or InterOp
switchRole The switch role: Principal, Subordinate, or disabled
switchDomain The domain ID of this switch: 0 to 31 or 1 to 239.
switchID The 24-bit address of this switch's embedded port: 0xfffc00 to
0xfffcef.
switchWwn The World Wide Name of this switch
switchBeacon Indicates if the beacon is turned on or not
Zoning zoning status
Port Number Each line shows the port number: 0 to 23, the GBIC type, the
port state and a comment field
Checking Switch Status
1. Log in with account that has admin privileges
2. Use the switchShow command to check the status of the all ports
3. Use switchStatusShow command to check the status of switch
Configuring the fabric name

To set and display the fabric name, use the command fabricname as shown in the following
example:
switch:user> fabricname --set myfabric@1
Using the fabricname --set command without a fabric name takes the existing fabric name and
synchronizes it across the entire fabric. An error message displays if no name is configured.
To clear the fabric name, use the fabricname --clear command.
Upgrade and downgrade considerations

Fabric names are lost during a firmware downgrade. No default fabric name is provided. If a fabric
name is needed, it must be configured after the upgrade.
22
Swapping port area IDs

If a device that uses port binding is connected to a port that fails, you can use port swapping to
make another
physical port use the same PID as the failed port. The device can then be plugged into the new
port without the
need to reboot the device.
Use the following procedure to swap the port area IDs of two physical switch ports. In order to
swap port area IDs,
the port swap feature must be enabled, and both switch ports must be disabled. The swapped
area IDs for the two
ports remain persistent across reboots, power cycles, and failovers.
1. Connect to the switch and log in using an account assigned to the admin role.
2. Enable the portSwapEnable command to enable the feature.
3. Enter the portDisable command on each of the source and destination ports to be swapped.
ecp:admin>portdisable 1
4. Enter the portSwap command.
ecp:admin>portswap 1 2
5. Enter the portSwapShow command to verify that the port area IDs have been swapped.
A table shows the physical port numbers and the logical area IDs for any swapped ports.
6. Enter the portSwapDisable command to disable the port swap feature.
23
24
Powering off a Brocade switch

The following procedure describes how to gracefully shut down a switch.
2. Enter the sysShutdown command.
3. At the prompt, enter y.
switch:admin> sysshutdown
This command will shutdown the operating systems on your switch.
You are required to power-cycle the switch in order to restore operation.
Are you sure you want to shutdown the switch [y/n]?y
4. Wait until the following message displays:
Broadcast message from root (ttyS0) Wed Jan 25 16:12:09 2006...
The system is going down for system halt NOW !!
INIT: Switching to runlevel: 0
INIT: Sending processes the TERM signal
Unmounting all filesystems.
The system is halted
flushing ide devices: hda
Power down.
5. Power off the switch.
Switch restart
When you restart the switch, the restart takes effect immediately. Ensure that there is no traffic
or other management on the
switch, because traffic is interrupted during the restart; however, frames are not dropped. Be
sure to save your changes
before the restart, because any changes not saved are lost.
Performing a fast boot

A fast boot reduces boot time significantly by bypassing the power-on self test (POST).
1. Open the Switch Administration window.
2. Click Fastboot.
3. On the Fastboot Confirmation window, click Yes to continue.
4. Click Apply.
Performing a reboot
Use the following procedure to reboot the CP and execute the normal power-on booting
sequence.
2. Click Reboot.
3. On the Reboot Confirmation window, click Yes to continue.
4. Click Apply
25
Prior to Fabric OS v6.1.0, a zoning license was required. From Fabric OS v6.1.0
and up, a zoning license is not required.
A zone is a specified group of fabric-connected devices, also called zone
members. Devices can only communicate with other devices in the same zone.
Devices can be members of multiple zones
Once zoning is enabled any device not defined in a zone will be unable to
communicate.
Devices are grouped into zones as zone members, zones are grouped into a
zone configuration. A fabric can have multiple zone configurations defined; but
only one configuration may be enabled at any time.
Zoning is a fabric wide configuration, changes made on any switch in the fabric
will be propagated to the entire fabric. Changes in zoning will send RSCNs only
to devices that are in the same zone and therefore affected by the change.
26
A zone set comprises a group of zones that can be activated or deactivated as a

single entity in a fabric. Multiple zone sets may be defined in a fabric, but only
one zone set can be active at a time. Zone members, zones, and zone sets form
the hierarchy defined in the zoning process (see Figure in the slide). Members
are nodes within the SAN that can be included in a zone. Switch ports, HBA
ports, and storage device ports can be members of a zone. A port or node can
be a member of multiple zones. Nodes distributed across multiple switches in a
switched fabric may also be grouped into the same zone. Zone sets are also
referred to as zone configurations.
27
A zone configuration is a group of zones that are enforced whenever that zone
configuration is enabled. A zone can be included in more than one zone
configurations.
To define a zone configuration, specify the list of zones to be included and assign a
zone configuration name. Zoning may be disabled at any time. When a zone
configuration is in effect, all zones that are members of that configuration are in effect.
Defined configuration: The complete set of all zone objects that have
been defined in the fabric.
Effective configuration: A single zone configuration that is currently in effect. The
effective configuration is built when an administrator enables a specified zone
configuration. This configuration is compiled by checking for undefined zone names, or
zone alias names, or other issues.
Saved configuration: A copy of the defined configuration plus the name of the
effective configuration which is saved in flash memory by the cfgsave command.
There may be differences between the saved configuration and the defined
configuration if the system administrator has modified any of the zone definitions and
has not saved them.
28
Use the cfgenable command to enable a zone configuration. The specified

zone configuration is built by checking for undefined zone names, zone alias
names, or other inconsistencies by expanding zone aliases, removing duplicate
entries, and then installing the current configuration.
If the build fails, the previous state is preserved (zoning remains disabled, or the
previous configuration remains in effect). If the build succeeds, the new
configuration replaces the previous configuration
Use the cfgdisable command to disable the current zone configuration. The
fabric returns to non-zoning mode, in which all devices see each other.
This command clears and commits the current zoning transaction buffer to both
volatile and flash memory. If a transaction is open on a different switch in the
fabric when this command is run, the transaction on the other switch is
automatically aborted. A message is displayed on the other switches to indicate
the aborting of the transaction.
29
Use the cfgclear command to clear all zone information in the defined
configuration. All defined zone objects are deleted.
After using the cfgclear command, use the cfgsave command to commit the
defined and effective configuration to flash memory for all the switches in the fabric.
To completely clear the zoning database, use the following commands:
cfgdisable, cfgclear, cfgsave.
30
Use the cfgsave command to save the current zone configuration. The defined
configuration and the name of the enabled configuration are written to flash
memory in all switches in the fabric.
Because the saved configuration is reloaded at power on, only valid
configurations are saved. The cfgsave command verifies that the enabled
configuration is valid by performing the same tests as cfgenable. If the tests
fail, an error is displayed and the configuration is not saved. Tests might fail if a
configuration has been modified since the last cfgenable.
This command ends and commits the current transaction. If a transaction is
open on a different switch in the fabric when this command is run, the
transaction on the other switch is automatically aborted and a message is
displayed on the other switches.
If the defined configuration is larger than the supported maximum zoning
database size, the following message is issued:
Commit zone DB larger than supported - <zone db size>
greater than <max zone db size>
Note: A cfgsave does not make any changes to the effective configuration. A
cfgenable command is still needed to enable any changes made in the
defined configuration.
The command cfgshow displays the defined configuration and
since zoning has not been enabled, there is no effective configuration
31
Zone database size

The maximum size of a zone database is the upper limit for the defined configuration,
and it is determined by the amount of flash memory available for storing the defined
configuration. To display the zone database size, enter cfgSize.
The supported maximum zone database size is 2 MB for systems running only Brocade
DCX, DCX-4S, and DCX 8510 platforms. The presence of any other platform reduces
the maximum zone database size to 1 MB.
32
When using a mixed fabric that is, a fabric containing two or more switches running
different release levels of Fabric OS you should use the switch with the latest Fabric
OS level to perform
zoning tasks. Switches with earlier versions of Fabric OS do not have the same
capability to view all the functionality that more recent versions of Fabric OS provide, as
functionality is backwards-compatible
but not forward-compatible.
Zone using the core switch in preference to using an edge switch.
Zone using a Backbone rather than a switch. A Backbone has more resources to
handle zoning changes and implementations.
Zoning:
Advantage of zoning
Zoning reduces the number of paths between a host and logical unit number (LUN).
Zoning keeps the primary and the secondary path in different zones.
Zoning improves the security by limiting the access between nodes.
Zoning increases the reliability by isolating the problems.
Zoning also reduces the cross talks between the host initiators and the hba.
Setting the default zone to no access when the fabric is first built allows devices
to connect to the fabric, do their FLOGI and Name Server update but not access
any other device connected to the fabric. This permits the physical connection to
be done in one phase and the enabling of a zone configuration to allow access
to be done in another phase.
The recommended grouping method for Zoning is Single Initiator Zoning,
sometimes called Single HBA Zoning. With this method, each zone has only a
single HBA and one or more storage ports. If the HBA has both disk and tape
storage devices, then you need to create two zones: one zone with the HBA and
the disk devices and a second zone with the HBA and the tape devices. Single
Initiator Zoning is optimal because it prevents any host-to-host interaction and
limits RSCNs to just the zones that need the information within the RSCN.
Zoning commands make changes that affect the entire fabric. When executing fabriclevel configuration tasks, allow time for the changes to propagate across the fabric
before executing any subsequent commands. For a large fabric, you should wait several
minutes between commands.
Zoning can be categorized into three types:

Port zoning: It uses the FC addresses of the physical ports to define zones. In
port zoning, access to data is determined by the physical switch port to which a
node is connected. The zone members are the switch domain ID and port
33
number to which HBA and its targets (storage devices) are connected. The FC
address is dynamically assigned when the node port logs on to the fabric.
Therefore, if a node is moved to any other port in the fabric, its FC address
changes. This creates the need to reconfigure the zoning. However, if an HBA or
storage device port fails, an administrator just has to replace the failed device
without changing the zoning configuration.
WWN zoning: It uses World Wide Names to define zones. The zone members
are the unique WWN addresses of the HBA and its targets (storage devices). A
major advantage of WWN zoning is its flexibility. It allows the SAN to be recabled
without reconfiguring the zone information. This is possible because the WWN is
static to the node port.
Mixed zoning: It combines the qualities of both WWN zoning and port zoning.
Using mixed zoning enables a specific port to be tied to the WWN of a node.
Zone aliases
A zone alias is a name assigned to a logical group of ports or WWNs. By creating an
alias, you can assign a familiar name to a device or group multiple devices into a single
name. This simplifies cumbersome data entry and allows an intuitive naming structure
(such as using "NT_Hosts" to define all NT hosts in the fabric). Using zone aliases
eliminates the need for long lists of individual zone member names.
Zone aliases also simplify repetitive entry of zone objects such as port numbers or a
WWN. For example, you can use the name "Eng" as an alias for
"10:00:00:80:33:3f:aa:11".
Creating an alias
switch:admin> alicreate "array1", "2,32; 2,33; 2,34; 4,4"
switch:admin> alicreate "array2", "21:00:00:20:37:0c:66:23; 4,3"
switch:admin> alicreate "loop1", "4,6"
switch:admin> cfgsave
Zoning
A switch with out an active configuration is of no use, Zoning is a process in which a channel
between host and a target is established. There are two types, hard and soft zoning. Nowadays
softzoning is implemented widely.
In simple terms soft zoning will be done using wwn of the host and target, if we use switch ports
then its called as hard zoning.
WWN - Word Wide Name
Steps:
34
Host and target will login to the switch as F-port, we can check the port type and wwn's by
executing the below command in CLI.
#switchshow - overall information like speed SFP info (id = SFP; cu = embedded port), type of
port (N, F, U port etc)
Zoning Steps:
Each wwn will be given a alias (for our understanding), then we group two alias and call it as a
zone, likewise multiple zone with different combination can be created and then we add the
zones to a config, config is a collection of zones. There can be multiple config's but only one can
be active at any given time. Lets see the important CLI syntaxes,
1. alicreate - to create a alias for a wwn
Syntax :
alicreate "test1", "21:00:00:e0:8b:1d:f9:03

alicreate "test2", "21:00:00:e0:8b:1d:f9:02
To verify - alishow "test1"
2. zonecreate - to create a zone which consists of two aliases
Syntax :
zonecreate "zone1", "test1; test2"

To verify - zoneshow "zone1"
(test1 and test2 is the alias that we created in the previous step)
3. cfgcreate - to create a config which may have multiple zones
Syntax :
cfgcreate "cfg1", "zone1"
35
To add another zone cfgcreate "cfg1", "zone2"
Now that we have created a config with two zones, it has to be saved before enabling it, below
is the syntax
# cfgsave "cfg1"
Then enable the config,
# cfgenable "cfg1"
Enabling a cfg will cause the switch to reboot. Below are some important commands that makes
zoning easier.
aliAdd
Add a member to a zone alias
aliCopy
Copy a zone alias
aliCreate
Create a zone alias
aliDelete
Delete a zone alias
aliRemove
Remove a member from a zone alias
aliRename
Rename a zone alias
aliShow
Print zone alias information
cfgAdd
Add a member to a configuration
cfgCopy
Copy a zone configuration
cfgCreate
Create a zone configuration
cfgDelete
Delete a zone configuration
cfgRemove
Remove a member from a configuration
cfgRename
Rename a zone configuration
cfgShow
Print zone configuration information
zoneAdd
Add a member to a zone
zoneCopy
Copy a zone
36
zoneCreate
Create a zone
zoneDelete
Delete a zone
zoneRemove
Remove a member from a zone
zoneRename
Rename a zone
zoneShow
Print zone information
cfgClear
Clear all zone configurations
cfgDisable
Disable a zone configuration
cfgEnable
Enable a zone configuration
cfgSave
Save zone configurations in flash
cfgSize
Print size details of zone database
cfgActvShow
Print effective zone configuration
cfgTransAbort
Abort zone configuration transaction
How to zone a Brocade SAN switch in command line base?

How to zone a Brocade SAN switch in command line base?
Here are the basics to add a new device to a Brocade SAN fabric. working with a
Brocade DCX switch. In this scenario, there is a new server come with 2 HBA card
that going to attach to the SAN switches.
Terminology
HBA - Host Bus Adapter, HBA card is the device that connects the servers to a
Storage Area Networks (SAN) via Fibre Channel.
WWN - World Wide Name, a unique 8-byte number identifying the HBA. Each WWN
is an 8-byte number derived from an IEEE OUI (for the first 3 bytes) and vendorsupplied information.
FC Zone - Fibre Channel Zone, a partitioned subset of the fabric. Members of a zone
are allowed to communicate with each other, but devices are not allowed to
communicate across zones.
37
Steps to Zone Brocade Switch

1.Plug in the FC Connector into an open port on the switch.
2.Login to the server and verify the HBA connection. It should see the switch but not
the storage device.
3.Check the Brocade Switch Port. To do so, telnet to the brocade switches and login
as user admin.
switch 1 - fabric A (SWITCH_1)
switch 2 - fabric B (SWITCH_2)
Create aliases for the hosts HBA's on each switch
Example:
switch_1> alicreate " HOSTNAME01_HBA_0","10:00:00:c9:69:3d:53"
switch_2> alicreate " HOSTNAME01_HBA_1","10:00:00:c9:69:ae:4e"
Tips: Do a switchshow to capture the WWN before start the aliases creation.
4.Create the storage zones using the aliases on each switch
switch_1> zonecreate "Z_HOSTNAME01_A", "HOSTNAME01_HBA_0"
switch_2> zonecreate "Z_HOSTNAME01_B", "HOSTNAME01_HBA_1"
Check the configuration
switch_1> zoneshow Z_HOSTNAME01_A
switch_2> zoneshow Z_HOST01_B
5.Add the zones to the fabrics on each switch
switch_1> cfgshow SWITCH_A
switch_1> cfgadd "SWITCH_A","Z_ HOSTNAME01_A"
switch_1> cfgsave
switch_1> cfgenable SWITCH_A
switch_1> zoneshow
switch_2> cfgshow SWITCH_B
switch_2> cfgadd " SWITCH_B","Z_ HOSTNAME01_B"
switch_2> cfgsave
switch_2> cfgenable SWITCH_A
switch_2> zoneshow
6.Login back in to the server to verify. It should now see the storage devices
38
How to do zoning for a Brocade SAN switch

Terminology
HBA - Host Bus Adapter, which in this case, refers to the Fibre Channel Card. In LAN
networking, its analogous to an Ethernet card.
WWN - World Wide Name, a unique 8-byte number identifying the HBA. In Ethernet
networking, its analogous to the MAC address.
FC Zone - Fibre Channel Zone, a partitioned subset of the fabric. Members of a zone are
allowed to communicate with each other, but devices are not allowed to communicate across
zones. An FC Zone is loosely analogous to a VLAN.
Steps to Zone Brocade Switch
1) Plug in the FC Connector into an open port on the switch.
2) Login to the server and verify the HBA connection. It should see the switch but not the
storage device.
3) Login to the Brocade Switch GUI interface. Youll need Java enabled on your browser.
4) Check the Brocade Switch Port.
1. On the visual depiction of the switch, click on the port where you plugged in the FC
connector.
2. The Port Administration Services screen should pop up. Youll need to enable the pop-up.
3. Verify that the Port Status is Online. Note the port number.
4. Close the Port Administration Services screen.
5) Find the WWN of your new device
1. Navigate back to the original GUI page.
2. Select Zone Admin, an icon on the bottom left of the screen. It looks like two squares and
a rectangle.
3. Expand the Ports & Attaching Devices under the Member Selection List.
4. Expand the appropriate port number. Note the attached WWN.
6) Create a new alias for this device
1. Click New Alias button
39
2. Follow menu instructions

7) Add the appropriate WWN to the alias
1. Select your new device name from the Name drop down menu
2. Expand the WWNs under Member Selection List
3. Highlight the appropriate WWN
4. Select Add Member
8) Add the alias to the appropriate zone
1. Select the Zone tab
2. Select the appropriate zone from the Name drop down menu
3. Select the appropriate alias from the Member Selection List
4. Click Add Member
9) Ensure that the zone is in Zone Config in the Zone Config tab
10) Save your changes by selecting ZoningActions -> Enable Config
11) Login back in to the server to verify. It should now see the storage devices.
Besides that, here has a demo video keep you all for more understanding on how exactly the
steps does.
Zoning steps in brocade SAN Switch

abc login: admin
Password:
abc:admin> switchshow
switchName:
abc
switchType:
34.0
switchState: Online
switchMode:
Native
switchRole:
Principal
switchDomain: 1
switchId:
fffc03
40
switchWwn:
10:00:00:05:1e:09:ab:c7
zoning:
ON (cfg)
switchBeacon: OFF
Area Port Media Speed State
Proto
=====================================
0 0 id N4 No_Light
1 1 id N4 No_Light
2 2 id N4 No_Light
3 3 id N4 No_Light
4 4 id N4 Online
F-Port 50:06:01:60:41:e0:eb:4d
5 5 id N2 Online
F-Port 10:00:00:00:c9:70:83:f0
6 6 id N4 Online
F-Port 50:06:01:69:41:e0:eb:4d
7 7 id N2 Online
F-Port 10:00:00:00:c9:50:6a:24
8 8 -- N4 No_Module
(No POD License) Disabled
9 9 -- N4 No_Module
10 10 -- N4 No_Module
abc:admin> cfgactvshow
Effective configuration:
cfg: cfg
zone: zone_PORT_5_PORT_0
10:00:00:00:c9:70:83:f0
50:06:01:60:41:e0:ed:8e
10:00:00:00:c9:50:6a:24
50:06:01:60:41:e0:ed:8e
abc:admin> zonecreate
"zone_clariion_A","10:00:00:00:c9:70:83:f0;50:06:01:60:41:e0:eb:4d"
abc:admin> zonecreate
"zone_clariion_B","10:00:00:00:c9:70:83:f0;50:06:01:69:41:e0:eb:4d"
abc:admin> cfgadd "cfg","zone_clariion_A;zone_clariion_B"
abc:admin> cfgsave
You are about to save the Defined zoning configuration. This
41
action will only save the changes on Defined configuration.
Any changes made on the Effective configuration will not
take effect until it is re-enabled.
Do you want to save Defined zoning configuration only? (yes, y, no, n): [no] y
Updating flash ...
abc:admin> cfgenable "cfg"
You are about to enable a new zoning configuration.
This action will replace the old zoning configuration with the
current configuration selected.
Do you want to enable 'cfg' configuration (yes, y, no, n): [no] y
zone config "cfg" is in effect
Updating flash ...
cfg: cfg
10:00:00:00:c9:70:83:f0
50:06:01:60:41:e0:ed:8e
10:00:00:00:c9:50:6a:24
50:06:01:60:41:e0:ed:8e
zone: zone_clariion_A
10:00:00:00:c9:70:83:f0
50:06:01:60:41:e0:eb:4d
zone: zone_clariion_B
10:00:00:00:c9:70:83:f0
50:06:01:69:41:e0:eb:4d
cfg: cfg
10:00:00:00:c9:70:83:f0
50:06:01:60:41:e0:eb:4d
10:00:00:00:c9:70:83:f0
50:06:01:69:41:e0:eb:4d
10:00:00:00:c9:50:6a:24
42
50:06:01:60:41:e0:eb:4d
10:00:00:00:c9:50:6a:24
50:06:01:69:41:e0:eb:4d
cfg: cfg
10:00:00:00:c9:70:83:f0
50:06:01:60:41:e0:eb:4d
10:00:00:00:c9:70:83:f0
50:06:01:69:41:e0:eb:4d
10:00:00:00:c9:50:6a:24
50:06:01:60:41:e0:eb:4d
10:00:00:00:c9:50:6a:24
50:06:01:69:41:e0:eb:4d
Zoning Commands
alicreate Name,
domain,port#
alicreate
Name,portname1;
portname2
alidelete Name
aliadd Name,
domain,port#
aliremove Name,
domain,port#
alishow AliName
zonecreate Zone Name,
alias1; alias2
zonedelete ZoneName
zoneadd ZoneName,
alias name
zoneremove ZoneName,
alias name
Used to create an alias

To create multiple ports under a single alias
To delete an alias
To add additional ports to an alias
To remove a port from the alias
To show the alias configuration on the switch
To create zones based on alias
To delete a zone
To add additional alias into the zone
To remove an alias from the zone
43
zoneshow zoneName
To show the zone configuration information
cfgcreate Configname,
To create configurations by adding in zones
Zone1; Zone2
cfgdelete ConfigName To delete a configuration
cfgadd ConfigName,
To add additional zones in the configuration
Zone3
cfgremove ConfigName,
To remove a zone from the configuration
Zone3
cfgshow ConfigName To show the details of that configuration
cfgenable ConfigName To enable a configuration on the switch
To have the effective configuration to be written into the flash
cfgsave
memory
- Open SwitchExplorer using IE.
- You can see the following screen once you login.
44
- Click at Zone Admin.
- You will see the following screen.
45
- Click at Zone Tab.
- Click at New Zone button.
- Name the Zone
46
Example: utv eccapp_Tape
Make sure the newly created Zone is highlighted in the drop down list box.
- Select the WWN which you want to add to the Zone and Click at Add Member
button.
47
Now the member is added to the Zone.
In the same way you can add another/multiple members to the zone.
Click at Zone Config Tab.

Expand the Zones and make sure the newly created Zone is listed in the
Zones.
Click at Save Config Button
48
- It will prompt to save the configuration.
Click Yes
- Now add the Zone to the existing Zone Config Member list by Selecting the Zone
and Click at Add Member button.
- Now it will be listed under the existing Zone Config Member list.
49
- Click At Save Config button to save the configuration.
- Click at Enable Config button.
- It will prompt for the confirmation. Click at OK button.
50
Click at Yes Button.
Now the Configuration will save.
You can confirm the same by checking the following command at bottom.
For Confirmation, close the Switch Explorer and reopen it.
Best practices for zoning

The following are recommendations for using zoning:
Always zone using the highest Fabric OS-level switch.
Switches with lower Fabric OS versions do not have the capability to view all the functionality that
a newer Fabric
OS provides as functionality is backwards compatible but not forwards compatible.
Zone using the core switch versus an edge switch.
Zone using a director over a switch.
A director has more resources to handle zoning changes and implementations.
Zone on the switch you connect to when bringing up Web Tools (the proxy switch).
51
A new switch is one that has not previously been connected to a fabric. Before
connecting the new switch, check to see if any zoning data exists with the
cfgshow command. If it exists, use the cfgdisable, cfgclear, and
cfgsave commands to sanitize it.
When a new switch is connected to a zoned fabric, all zone configuration data is
immediately copied from the zoned fabric into the new switch. If a zone
configuration is enabled in the fabric, then the same configuration becomes
enabled in the new switch. After this operation, the cfgshow command displays
the same output on all switches in the fabric, including the new switch.
Effective and defined zone configuration match : Ensure that the effective and defined
zone configurations match. If they do not match, and you merge with another switch, the
merge may be successful, but unpredictable zoning and routing behavior can occur.
The zone configuration database is stored in nonvolatile memory by the cfgSave
command. All switches in the fabric have a copy of this database. When a change is
made to the defined configuration, the switch where the changes were made must close
its transaction for the changes to be propagated throughout the fabric.
Both fabrics have identical zones and configurations enabled, including the default zone
mode. The two fabrics will join to make one larger fabric with the same zone
configuration across the newly created fabric.
52
If the two fabrics have different zone configurations, they will not be merged. If the two
fabrics cannot join, the ISL between the switches will segment.
Merge conflicts
When a merge conflict is present, a merge will not take place and the ISL will segment.
Use the switchShow or errDump commands to obtain additional information about
possible merge conflicts, because many non-zone-related configuration parameters can
cause conflicts
A merge is not possible if any of the following conditions exist:
Configuration mismatch: Zoning is enabled in both fabrics and the zone configurations
that are enabled are different in each fabric.
Type mismatch: The name of a zone object in one fabric is used for a different type of
zone object in the other fabric.
Content mismatch: The definition of a zone object in one fabric is different from the
definition of the zone object with the same name in the other fabric.
Zone database size: The zone database size exceeds the maximum limit of another
switch.
The SAN A is comprised of many interconnected switches. Each switch has a

unique domain ID within the fabric. Hosts (represented by the computer icon)
are able to connect to storage (represented by the disk icon) across switches
within SAN
FC-FC Routing is performed by a Fibre Channel router, to pass frames from a
source device in one fabric toward a destination device in another fabric without
merging the fabrics.
There are two kinds of routing protocols on intranet networks,
53
distance vector and link state.

Distance vector is based on hop count. This is the number of switches that a frame
passes through to get from the source switch to the destination switch.
Link state is based on a metric value based on a cost. The cost could be based on
bandwidth, line speed, or round-trip time.
\
With the link state protocol, switches that discover a route identify the networks to which
they are attached, receiving an initial route table from the principal switch. After an initial
message is sent out, the switch only notifies the others when changes occur.
It is recommended that no more than seven hops occur between any two switches. This
limit is not required or enforced by Fabric Shortest Path First (FSPF). Its purpose is to
ensure that a frame is not delivered to a destination after the Resource Allocation
TimeOut Value (R_A_TOV) has expired.
FSPF
Fabric Shortest Path First (FSPF) is a link state path selection protocol that directs
traffic along the shortest path between the source and destination based upon the link
cost. FSPF is also referred to as Layer 2 routing. FSPF detects link failures, determines
the shortest route for traffic, updates the routing table, provides fixed routing paths
within a fabric, and maintains correct ordering of frames.
FSPF also keeps track of the state of the links on all switches in the fabric and
associates a cost with each link. The protocol computes paths from a switch to all the
other switches in the fabric by adding the cost of all links traversed by the path, and
chooses the path that minimizes the costs. This collection of the link states, including
costs, of all the switches in the fabric constitutes the topology database or link state
database.
54
An inter-switch link (ISL) is a link between two switches, E_Port-to-E_Port. The ports of
the two switches automatically come online as E_Ports once the login process finishes
successfully.
When connecting two switches together, Brocade recommends the best practice that
the following parameters are differentiated:
Domain ID
Switch name
Chassis name
55
Routing policies
By default, all routing protocols place their routes into a routing table. You can control
the routes that a protocol places into each table and the routes from that table that the
protocol advertises by defining one or more routing policies and then applying them to
the specific routing protocol.
The routing policy is responsible for selecting a route based on one of three userselected routing policies:
Port-based routing
Exchange-based routing
Device-based routing
The two main functions of a Principal Switch are to:

Ensure unique domain IDs throughout the fabric
Synchronize time throughout the fabric
FSPF uses several frames to perform its functions. Since it may run before
fabric routing is set up, FSPF does not use the routing tables to propagate the
frames, but floods the frames throughout the fabric hop-by-hop. At the
beginning, frames are flooded on all the Inter-Switch Links (ISLs); as the
protocol progresses, it builds a spanning tree rooted on the Principal Switch.
Frames are then sent only on the ISLs that belong to the spanning tree. These
ISLs are called Principal ISLs.
Where there are multiple ISLs between switches, the first ISL to respond to
connection requests becomes the Principal ISL. Only one ISL from each switch
will be used as the Principal ISL.
Upstream means going out that E_Port is going toward the Principal Switch.
Downstream means going out that E_Port is going away from the Principal
Switch. These designations are seen in the switchshow output.
56
57
Switches are shipped with trunking enabled on all ports. To use trunking, you
must first install the Brocade trunking license. Trunking is enabled automatically
when the trunking license is activated and ports are reinitialized. Trunks are
easily managed using either Fabric OS CLI commands or Web Tools.
FC-FC Routing
The FC-FC routing service provides Fibre Channel routing (FCR) between two or more fabrics
without merging those
fabrics. A Fibre Channel router (FC router) is a switch running the FC-FC routing service. The FCFC routing service
can be simultaneously used as an FC router and as a SAN extension over wide area networks
(WANs) using FCIP.
FCR supports backbone-to-edge routing, allowing devices in the backbone to communicate with
devices on the
edge fabric.
58
Brocade Data Center Fabric Manager is a key component of the Brocade Data
Center Fabric (DCF) architecture. It is designed to unify management of data
center fabricsfrom the storage ports to the Host Bus Adapters (HBAs)
attached to physical or virtualized servers. It can be used to configure and
manage the Brocade DCX Backbone along with Brocade Directors, routers, and
switches. DCFM supports Brocade encryption capabilities for data-at-rest and
HBA products.
59
DCFM Professional is a fabric management application included with Brocade

switches that contains a subset of the DCFM Enterprise edition features. DCFM
Professional enables centralized management of up to 1000 devices in a single,
pure Fabric OS fabric. It performs important functions, including firmware
downloads and fabric configuration for groups of switches while accessing
device-level information.
DCFM Professional is shipped with Brocade 4 Gbps and 8 Gbps hardware
products and is also available via web download.
Footnote 1: DCFM Professional is targeted at the Small and Medium Business
segment. DCFM does not support enterprise-class products/technologies, such
as the DCX Backbone (does support DCX-4S), Fabric-based Encryption
products, Fibre Channel Routing, FICON, etc. Customers using these products
and technologies should consider DCFM Enterprise.
Footnote 2: DCFM Professional supports only pure-Fabric OS fabrics and
manages only one fabric at a time. DCFM Professional does not support M-EOS
platforms.
60
SAN Health Diagnostics Capture

A free data capture utility formerly known as SAN Health 3.0.2
SAN Health Professional
Brocade SAN Health Professional provides a framework for loading the original report
data generated by SAN Health Diagnostics Capture. This framework supports extended
functionality beyond the capabilities of an Excel report and Visio topology diagram.
Capabilities such as searching, comparing, custom report generation, and change
analysis are all available in an easy-to-use GUI
SAN Health Professional Change Analysis
An optional subscription-based add-on module for SAN Health Professional that
enables organizations to compare two SAN Health reports run at different times to
visually identify what items have changed. A change report can be quickly created.
SAN Health Expert
This is a Professional Services engagement subscription service designed for
organizations that want additional analysis and advice from a Brocade SAN expert. Live
consultations are done quarterly. This license was designed primarily for secure sites.
The secure site has a server on-site and a consultant periodically visits to examine the
SAN Health output.
61
Simple Network Management Protocol (SNMP) is a standard method for

monitoring and managing network devices. Using SNMP components, you can
program tools to view, browse, and manipulate Brocade switch variables and set
up enterprise-level management processes.
Every Brocade switch runs an SNMP agent and Management Information Base
(MIB). The agent accesses MIB information about a device and makes it
available to a network manager station. You can manipulate information of your
choice by trapping MIB elements using the Fabric OS CLI, Web Tools, or Fabric
Manager.
The SNMP Access Control List (ACL) provides a way for the administrator to
restrict SNMP get/set operations to certain hosts/IP addresses. This is used for
enhanced management security in the storage area network.
Network management is all about keeping the network up and running,
monitoring and controlling network devices remotely using conventional network
technology. Local management and remote management are two ways of
managing a device. Enterprise management software, like HP OpenView, Tivoli,
and EMC Control Center, monitor thousands of devices in an enterprise. Many
of these packages have add-on components that are tailored to manage
Brocade SANs. There are also commercial and freely available packages that
can be run separately by the SAN administrator so that they can get alerts, trend
performance and capture details of errors of switches separately from large
network management station.
62
63
The supportsave capture process requires an FTP server if you want to save
the data off the switch. A USB stick can also be used on supported platforms for
storing the supportsave capture.
The Brocade Fabric OS Message Reference manual has message text,

probable cause, recommended action, and severity level for each message.
64
The RAS Log, also called the system message log, is implemented as a circular
buffer. When more than maximum entries are added to the log file, old entries
are overwritten by new entries.
By default RAS Log error messages are saved to nonvolatile storage.
RAS Logs save a maximum of 1024 messages in random access memory
(RAM) as a circular buffer
RAS Log messages are numbered sequentially from 1 to 2,147,483,647
(0x7ffffff)
The sequence number will continue to increase beyond the storage limit of
1024 messages
The sequence number can be reset to 1 using the errclear command
The sequence number is persistent across power cycles and switch reboots
RAS Log
RAS log is the Brocade FOS error message log. Messages are organized by Brocade
FOS component, and each one has a unique identifier as well as severity, source and
platform information and a text message.
RAS log is available from each switch and director via the errdump command. RAS
log messages can be forwarded to a syslog server for centralized collection or viewed
within Brocade Network Advisor via the Master Log.
Audit Log
The Audit log is a collection of information created when specific events are identified on
a Brocade platform. The log can be dumped via the auditdump command, and audit
data can also be forwarded to a syslog server for centralized collection.
Information is collected on many different events associated with zoning, security,
trunking, FCIP, FICON, and others. Each release of the Brocade FOS provides more
audit information.
65
Here is a partial list of helpful commands and tools associated with identifying
these problems; all problem determination steps include switchshow and
errshow:
Segmented fabric: switchshow, configshow, fabricshow,
fabstatsshow, portshow, portcfgshow, check zone related commands,
and license configuration. You can also use the DCFM Zone Merge Tool to
merge the zone configurations.
Port/node configuration: portcfgshow, configshow, portlogdump,
portshow, fabricshow, trunkshow, portcfglongdistance,
licenseshow, and portshow
Missing device: Check physical connectivity using switchshow,
portshow, and fcping (see example on next page). Check fabric
connectivity with nsallshow, nsshow, nscamshow, zoning(zoneshow, etc.)
and port configuration commands (portcfgshow, portshow). Optionally use
a diagnostic tests such as porttest; this will test link components and port.
LUN masking may also prevent a host from seeing the storage.
Timeout/sluggishness: urouteshow, topologyshow, porterrshow,
portshow, portstatsshow, portcfgshow, portbuffershow,
aptpolicy, and bottleneckmon (Fabric OS v6.3 or later). You can also
use DCFM or Fabric Watch to identify congestion problems
Commands and tools to use for licensing issues: licenseshow, licenseadd
66
Commands and tools to use for Marginal Link issues: portstatsshow,

porterrshow, errdump, Fabric Watch.
Portstats64show displays the 64-bit hardware statistics for a port.
Configuration file backup

Brocade recommends keeping a backup configuration file. You should keep individual
backup files for all switches in the fabric and avoid copying configurations from one
switch to another. The configUpload command, by default, only uploads the switch
context configuration for the logical switch context in which the command is executed.
The following information is notsaved in a backup:
dnsConfig command information
Passwords
Before you upload a configuration file, verify that you can reach the FTP server from the
switch. Using a
Telnet connection, save a backup copy of the configuration file from a logical switch to a
host computer.
Secure File Transfer Protocol (SFTP) is now an option when uploading a configuration
file. SFTP is analogous to Secure Copy Protocol (SCP). SFTP can be used for the
configupload , configdownload , supportsave , and auto FFDC/trace upload (supportftp )
commands.
Uploading a configuration file in interactive mode

1. Verify that the FTP, SFTP, or SCP service is running on the host computer.
2. Connect to the switch and log in using an account with admin permissions.
3. Enter the configUpload command. The command becomes interactive and you are
prompted for the required information.
4. Store a soft copy of the switch configuration information in a safe place for future
reference.
Example of configUpload on a switch without Admin Domains
switch:admin> configupload
Protocol (scp, ftp, sftp, local) [ftp]: sftp
Server Name or IP Address [host]: 10.1.2.3
User Name [user]: UserFoo
Path/Filename [<home dir>/config.txt]: switchConfig.txt
Section (all|chassis|FID# [all]): chassis
username@10.1.2.3
's password:
Password: <hidden>
configUpload complete
The switch section of the configuration file contains information for all of the following:
Boot parameters
67
Configuration
Bottleneck configuration
Flow Vision configuration
FCoE software configuration
Zoning
Defined security policies
Active security policies
iSCSI
CryptoDev
FICU saved files
VS_SW_CONF
MAPS configuration
Banner
configDownload command.is used to restore

configuration file
Enter the configDownload command, without the -vf operand, to download the regular
configuration data. This step does not cause a reboot.
Brocade switch config upload , download :

configupload :
switch26:admin> configupload
Protocol (scp or ftp) [ftp]: ftp
User Name [user]: root
File Name [config.txt]:
Password:
configUpload complete: All config parameters are uploaded

switch26:admin>
switch26:admin> switchdisable
switch26:admin> configdownload
Protocol (scp or ftp) [ftp]: ftp
68
User Name [user]: root

File Name [config.txt]:
*** CAUTION ***
This command is used to download a backed-up configuration
for a specific switch. If using a file from a different
switch, this file's configuration settings will override
any current switch settings. Downloading a configuration
file, which was uploaded from a different type of switch,
may cause this switch to fail. A switch reboot might be
required for some parameter changes to take effect.
configDownload operation may take several minutes
to complete for large files.
Do you want to continue [y/n]: y
Password:
Activating configDownload: Switch is disabled
configDownload complete: All config parameters are downloaded

switch26:admin>
Creating a configuration backup file

Keep a backup copy of the configuration file in case the configuration is lost or unintentional
changes are made. You should
keep individual backup files for all switches in the fabric. You should avoid copying configurations
from one switch to
another.
4. Select Show Advanced Mode.
5. Select the Configure tab.
The Configure screen is displayed.
6. Select the Upload/Download tab.
The Upload/Download configuration screen is displayed. By default, Config Upload is chosen
under Function, and Network is
chosen as the source of the configuration file.
69
7. If you upload from a network, type the host name or IP address in the Host Name or IP field,
the user ID and password required for access to the host in the User Name and Password fields,
and choose the Protocol Type used for the upload. The default is FTP. If you choose
Secure Copy Protocol (SCP), you cannot specify anonymous in the User Name field.
If you choose USB as the configuration file source, the network parameters are not needed and
are not displayed. You can skip to step 6.
An info link is enabled when USB is chosen as the source of the configuration file. If you click
on info, the following information message is displayed
70
8. Type the configuration file with a fully-qualified path, or select the configuration file name in
the Configuration File Name field.
9. Use the Fabric ID selector to select the fabric ID of the logical switch from which the
configuration file is to uploaded. The selector will show all the virtual fabric IDs that have been
defined, the default of 128 for the physical switch, chassis level configuration, and all chassis and
switches.
NOTE
If you are using a USB device, it must be connected and mounted before you upload or download.
10. Click Apply.
You can monitor the progress by watching the Upload/Download Progress bar.
Restoring a configuration
Restoring a configuration involves overwriting the configuration on the switch by downloading a previously
saved
backup configuration file. Perform this procedure during a planned down time.
Make sure that the configuration file you are downloading is compatible with your switch model.
Configuration files from other model switches might cause your switch to fail.
2. Select Show Advanced Mode.
3. Select the Configure tab.
The Configure screen is displayed.
4. Select the Upload/Download tab.
The Upload/Download configuration screen is displayed ().
By default, Config Upload is chose under Function, and Network is chosen as the source of the configuration
file.
71
5. Under Function, select Config Download to Switch.

6. 6. If you download from a network, type the host name or IP address in the Host Name or
IP field, the user ID and
7. password required for access to the host in the User Name and Password fields, and
choose the Protocol Type used for
8. the upload. The default is FTP. If you choose
9. Secure Copy Protocol (SCP), you cannot specify anonymous in the User Name field.
10. 7. If you choose USB as the configuration file source, the network parameters are not
needed and are not displayed, and
11. you can skip to step 6.
72
An info link is enabled when USB is chosen as the source of the configuration file. If you click info, the following
information message is displayed.
8. Type the configuration file with a fully-qualified path, or select the configuration file in the
Configuration File Name field.
9. Use the Fabric ID selector to select the fabric ID of the logical switch to which the configuration
file is to downloaded.
The selector will show all the virtual fabric IDs that have been defined, the default of 128 for the
physical switch, chassis
level configuration, and all chassis and switches.
10. Type the fabric ID of the logical switch in Template Fabric ID.
NOTE
If you are using a USB device, it must be connected and mounted before you upload or download.
11. Click Apply.
You can monitor the progress by watching the Upload/Download Progress bar.
Diagnostic Port (D_Port)

D_Port mode allows you to convert a Fibre Channel port into a diagnostic port for
testing link traffic, electrical loopbacks, and optical loopbacks between a pair of
switches, a pair of Access Gateways, and an Access Gateway and a switch. The ports
must use 10G or 16G Brocade-branded SFPs.
73
Support is also provided for running D_Port tests between a host bus adapter (HBA)
and a switch. The test results that are reported can be very useful in diagnosing a
variety of port and link problems.
Understanding D_Port
The D_Port does not carry any user traffic, and is designed to run only specific diagnostics
tests on
it for identifying link-level faults or failures. Basically, in order to bring up a port in D_Port
mode, you
must configure both ends of the link between a given pair of switches (or switches
configured as
Access Gateways), and you must disable the existing port before you can configure it as a
D_Port.
The fundamentals of D_Port testing are as follows:
1. The user configures the desired ports on both ends of the connection.
2. Once both sides are configured, a basic test suite is initiated automatically when the link
comes online, conducting diagnostic tests in the following order: (1) electrical loopback, (2)
optical loopback, and (3) link traffic.
3. After the automatic test is complete, the user can view results (through CLI or GUI) and
rectify
issues (if any) that are reported.
4. The user can also start (and restart) the test manually to verify the link.
Advantages of D_Port
Use the D_Port tests for the following situations:

Testing a new link before adding it to the fabric
Testing a trunk member before joining it with the trunk
Testing long-distance cables and SFPs
Brocade Switch Technical Support

Contact your switch supplier for hardware, firmware, and software support,
including product repairs and part ordering. To expedite your call, have the following
information immediately available :
1. General Information
Technical Support contract number, if applicable
Switch model
74
Fabric OS v6.1.1a Release Notes, v1.0 Page 6 of 33
Switch operating system version
Error numbers and messages received
supportSave command output

Detailed description of the problem, including the switch or fabric behavior
immediately
following the problem, and specific questions
Description of any troubleshooting steps already performed and the results
Serial console and Telnet session logs
Syslog message logs
2. Switch Serial Number

The switch serial number is provided on the serial number label.
The serial number label is located as follows:
Brocade 200EOn the nonport side of the chassis
Brocade 4100, 4900, and 7500/7500EOn the switch ID pull-out tab located inside
the
chassis on the port side on the left
Brocade 300, 5000, 5100, and 5300On the switch ID pull-out tab located on the
bottom of
the port side of the switch
Brocade 7600On the bottom of the chassis
Brocade 48000 Inside the chassis next to the power supply bays
Brocade DCXBottom right of the port side.
75
3. World Wide Name (WWN)

Use the wwn command to display the switch WWN.
If you cannot use the wwn command because the switch is inoperable, you can get
the
WWN from the same place as the serial number, except for the Brocade DCX. For
the
Brocade DCX, access the numbers on the WWN cards by removing the Brocade logo
plate at the top of the non-port side. The WWN is printed on the LED side of both
cards.
Firmware download from a USB device

The Brocade 300, 5100, 5300, 6505, 6510 and 6520 support a firmware download from Brocade
branded USB
device attached to the switch. Before the USB device can be accessed by the firmwareDownload
command, it must
be enabled and mounted as a file system. The firmware images to be downloaded must be stored
under the
relative path from /usb/usbstorage/brocade/firmware or use the absolute path in the USB file
system. Multiple
images can be stored under this directory.
There is a firmwarekey directory where the public key signed firmware is stored.
When the firmwareDownload command line option, -U (upper case), is specified, the
firmwareDownload command
downloads the specified firmware image from the USB device. When specifying a path to a
firmware image in the
USB device, you can only specify the relative path to /firmware or the absolute path.
Enabling USB
1. Log in to the switch using an account assigned to the admin role.

2. Enter the usbStorage -e command.
Viewing the USB file system
1. Log in to the switch using an account assigned to the admin role.

2. Enter the usbStorage -l command.
Brcd:admin> usbstorage l
firmware\ 381MB 2010 Mar 28 15:33
v6.4.0\ 381MB 2010 Mar 28 10:39
config\ 0B 2010 Mar 28 15:33
support\ 0B 2010 Mar 28 15:33
firmwarekey\ 0B 2010 Mar 28 15:33
Available space on usbstorage 79%
Downloading from USB using the relative path
1. Log in to the switch as admin.
2. Enter the firmwareDownload -U command.
ecp:admin>firmwaredownload U v6.4.0
Downloading from USB using the absolute path
1. Log in to the switch as admin.
2. Enter the firmwareDownload command with the -U operand.
ecp:admin>firmwaredownload U /usb/usbstorage/brocade/firmware/v6.4.0
A guide in updating Brocade SAN switch firmwares
76
Posted on January 8, 2016
I would like to share some of my personal best-practices in upgrading firmwares on Brocade

SAN switches and/or directors. This blog post is divided in several sections:
Pre-upgrade tasks;
Upgrading the SAN switch;
Post-upgrade tasks;
Alternative FTP server;
Putty log of a SAN switch upgrade.
First of all, its important to mention every Brocade SAN switch has two firmware partitions.
The Fabric OS (also referred to as FOS) is booted from the active partition, whereas the
secondary partition is used to provide the ability to perform a non-disruptive firmware upgrade
or as a fallback mechanism in case the firmware on the primary partition is damaged.
SANSWITCH:admin>firmwareshow
Appl
Primary/Secondary
FOS
FOS v7.0.0c
Versions
v7.0.0c
The firmware on the SAN switch can be upgraded disruptively or, non-disruptively which will
take some more time. When you are upgrading SAN switch components in a live production
environment, its highly advisable to use the non-disruptive approach.
The firmware upgrade path can be collected from the Brocade Fabric OS vA.B.CD Release
Notes. In general, we can say non-disruptive upgrade is supported from the previous version
(identified as B in the version information). For example: v7.1.2b > v7.2.1c > v7.3.1d > v7.4.1.
A disruptive upgrade is supported within the same version (identified as A in the version
information, for example: v7.2.x to v7.4.1). Refer to the release notes to confirm the firmware
migration path as this can differ from version to version.
Overall, we can say the firmware update takes about 20 minutes. When upgrading two fabrics
consisting out of 2 switches per fabric running on version 7.1.2b, we need to perform 3 updates
to reach version 7.4.1. Bringing the total number of updates to 12 for both fabrics. Its
unnecessary to say this will take a significant time (estimated 240 minutes or 4 hours).
There are some possibilities to speed some things up!
77
Update SAN switches from the inside out. Start with the SAN switches in the
core of the fabric, and finish with the switches on the edge of the fabric.
As a general best-practice, dont upgrade SAN switches over both fabrics at

the same time. I usually work on a version-by-version fabric-by-fabric basis to
limit the fabric convergence to one specific fabric, allowing data
communication to occur on the standby fabric.
Initiate the second firmware update once the initial switch is performing an
HA reboot, this will avoid multiple SAN switches to reboot within the same
fabric as the same time!
Prepare everything upfront! Download all the firmware files and store them
on the FTP you will use to perform the upgrades. Make sure the SAN switch is
able to connect to the FTP server over the network. Create an overall
planning, allowing you to easily follow-up on the various tasks during the
update(s).
The first firmware in the migration path can be installed on the secondary
partition without rebooting the switch. This shortens the intervention with 15
minutes per switch. This is achieved by executing the command:
firmwaredownload with the operand -r followed by an hareboot and a
firmwarecommit during the maintenance time window.
As a general recommendation, I would advise to schedule this intervention in a low-IO timewindow (outside production hours). A downtime for the systems is not required as the multi-path
software should fail-over storage paths without interrupting the applications.
PREPARATION TASKS:
1. Get a view on the SAN topology and its connected devices. The easiest way
is to use Brocade SAN Health or HP SAN Visibility.
2. Verify the firmware compatibility between SAN switch firmware, host bus
adapters, storage firmware, etc. For HP material, please refer to HP Single
Point Of Connectivity Knowledge (SPOCK). Refer to the vendor documentation
for any remaining information.
3. Download the firmware files in advance. The firmware files can be rather big
(up to 1GB a piece) and take some time to be downloaded.
4. Update server components (HBA cards, MPIO, etc) upfront.
5. Verify if all systems are redundantly connected/configured on the fiber
channel fabrics. Do not conclude if the system is redundantly connected, all
paths to the various storage components are available. My own experiences
taught me storage paths can be unavailable even though it should not be the
case.
78
6. Schedule a blackout of the backup environment during the firmware updates.
Tape drives do not support MPIO and power-cycling the switches tend to give
hardware errors in the backup application.
7. Validate the health state of the SAN switches by executing the command:
switchstatusshow. In case something is faulty, the issue can be resolved
before the maintenance.
SANSWITCH:admin> switchstatusshow
Switch Health Report Report time: 12/17/2015 08:50:16 AM
Switch Name: SANSWITCH
IP address: 192.168.101.220
Duration: 14016:36
Error ports monitor HEALTHY
PRE-UPGRADE TASKS:
In order to prepare the intervention, the following steps should be executed:
1. Before updating the firmware, its advised to reboot the SAN switch to release
any pending commands and/or locks. The switch can be easily rebooted by
executing the command hareboot and takes a few minutes. A switch reboot
is transparent for redundantly configured servers.
2. Collect a supportsave as a baseline (command: supportsave and follow the
guidance outlined in the interactive prompt). This will allow reverse analysis
in case of any issues without wasting time.
3. Save the configuration of the switch to an FTP site by executing the
command: configdownload and follow the steps in the interactive prompt.
4. Verify the health state of the SAN switch before updating the SAN switch
firmware. This can be performed in the GUI or by executing the CLIcommand: switchstatusshow.
79
5. Take a closer look the switch event logs by executing the command:
errshow or errdump.
6. Clear the counters on the fiber channel ports by executing the command
statsclear or the command portstatsclear -i <start-to-end-index>.
UPGRADING THE SAN SWITCH FIRMWARE:

First of all, I would advise to use the non-disruptive approach to update the SAN switch
firmware. Start with a SAN switch in the core of the fabric, once the system is performing an HA
reboot, continue with another switch in the core or continue with an edge switch. The best way to
address this is to work from the inside out. Once fabric A has been updated with version X,
update the switches in fabric B with version X, before installing version Y on the switches
in fabric A.
1. Verify the health state of the SAN switch by using the command
switchstatusshow.
2. The firmware installation can be performed by using the GUI which is pretty
straightforward, but does not provide any decent follow-up. An alternative is
to use the commandline. The command to be executed is
firmwaredownload and provides a set of operands, such as -s or -r
which allows the firmware to be downloaded to the secondary partition
without a system reboot. In case you want to use the interactive prompt,
execute the command: firmwaredownload and follow the steps in the
wizard.
3. Once the firmwaredownload has been started without any additional
operands, the system performs an hareboot automatically, followed with a
firmwarecommit. The status of the firmware installation process, can be
followed by executing the command firmwaredownloadstatus once the
switch has been rebooted.
4. After switch reboot, execute the three steps listed above on the remaining
switches in the fabrics (one-by-one).
POST-UPGRADE ACTIONS:
Once the firmware has been installed on the system, execute the following steps to collect a
baseline after firmware installation on the Fiber-channel Switches:
1. Clear the counters on the fiber channel ports by executing the command
statsclear or the command portstatsclear -i <start-to-end-index>.
2. Take a closer look the switch event logs for any errors by executing the
command: errshow or errdump.
80
3. Verify the health state of the SAN switch by using the command
switchstatusshow.
4. Collect a supportsave as a baseline (command: supportsave and follow the
guidance outlined in the interactive prompt). This will allow reverse analysis
in case of any issues without wasting time.
Alternative for FTP SERVER:

In case no FTP server is available within the network, or you work as an IT consultant and you
have to do this often, it can be a lot easier to install FileZilla FTP server on your laptop.
Additionally, some switches allow to update the firmwares by using an USB device plugged into
the SAN switch. This can be useful when no FTP server is available, but requires physical
access.
PUTTY LOG OF A SAN SWITCH UPGRADE:
This section provides some additional information on how to upgrade a Brocade SAN switch
from the commandline. The switch being upgraded is an HP StorageWorks 4/8 SAN
switch (type: 34.0) from version v6.1.0d to v6.2.2e. Its a rather old switch with a rather old
firmware which was still lying around at my place.
STEP 1: rebooting the SAN switch.
SANSWITCH:admin> hareboot
HA Rebooting
SANSWITCH:admin>
STEP 2: collecting a supportsave.
SANSWITCH:admin> supportsave
This command will collect RASLOG, TRACE, supportShow, core file, FFDC data and other
support information and then transfer them to a FTP/SCP server or a USB device. This
operation can take several minutes.
NOTE: supportSave will transfer existing trace dump file first, then automatically generate and
transfer latest one. There will be two trace dump files transfered after this command.
OK to proceed? (yes, y, no, n): [no] y
Host IP or Host Name: 192.168.0.121
User Name: cfg
Password:
81
Protocol (ftp or scp): ftp

Remote Directory: .
Saving support information for switch:SANSWITCH, module:CONSOLE0
tSave_files/SANSWITCH-S0-201601081536-CONSOLE0.gz: 535.00 B 9.45 kB/s
Saving support information for switch:SANSWITCH, module:SSAVELOG
tSave_files/SANSWITCH-S0-201601081545-sslog.ss.gz: 1.87 kB 93.85 kB/s
SupportSave completed
SANSWITCH:admin>
STEP 3: saving the switch configuration to the FTP server as a fall-back mechanism.
SANSWITCH:admin> configupload
Protocol (scp, ftp, local) [ftp]: ftp
User Name [user]: cfg
File Name [config.txt]: SANSWITCH-CFG.txt
Password:
configUpload complete: All config parameters are uploaded
SANSWITCH:admin>
STEP 4: verifying the switch health state prior to new firmware installation.
Switch Health Report Report time: 01/08/2016 03:57:32 PM
Switch Name: SANSWITCH
IP address: 192.168.0.241
Duration: 00:23
Fabric Watch is not licensed
82
Detailed port information is not included

SANSWITCH:admin>
STEP 5: consulting the switch logs.
SANSWITCH:admin> errdump
2016/01/08-15:34:11, [FSSM-1002], 232,, INFO, SilkWorm200E, HA State is in sync.
2016/01/08-15:34:11, [FSSM-1003], 233,, WARNING, SilkWorm200E, HA State out of sync.
2016/01/08-15:35:10, [SEC-1203], 234,, INFO, SANSWITCH, Login information: Login
successful via TELNET/SSH/RSH. IP Addr: 192.168.0.121
2016/01/08-15:46:18, [SS-1000], 235,, INFO, SilkWorm200E, supportSave has uploaded
support information to the host with IP address 192.168.0.121.
2016/01/08-15:54:47, [CONF-1001], 236,, INFO, SANSWITCH, configUpload completed
successfully. All config parameters are uploaded.
SANSWITCH:admin>
STEP 6: clearing the port statistics. All error counters are resetted to zero.
SANSWITCH:admin> statsclear
SANSWITCH:admin> porterrshow
STEP 7: installing the newer firmware revision on the SAN switch.
SANSWITCH:admin> firmwaredownload
Server Name or IP Address: 192.168.0.121
User Name: flash
File Name: .
Network Protocol(1-auto-select, 2-FTP, 3-SCP) [1]: 2
Password: *****
Checking system settings for firmwaredownload
Server IP: 192.168.0.121, Protocol IPv4
System settings check passed.
You can run firmwaredownloadstatus to get the status of this command.
This command will cause a warm/non-disruptive boot on the switch, but will require that
existing telnet, secure telnet or SSH sessions be restarted.
Do you want to continue [Y]: Y
Firmware is being downloaded to the switch. This step may take up to 30 minutes.
Preparing for firmwaredownload
Removing fabos-drivers
83
Start to install packages

dir ##################################################
ldconfig ##################################################
STEP 8: consulting the firmware revision on both partitions. During the upgrade process, you
will notice the secondary partition will transition from the old version (v6.1.0d) into an
Unknown state, before it will display the newer software revision (v6.2.2e).
SANSWITCH:admin> firmwareshow
Appl Primary/Secondary Versions
FOS v6.2.2e
FOS unknown
STEP 9: verify the firmware installation status by executing the command
firmwaredownloadstatus. In the log, you will notice the upgrade on the primary partition first,
the hareboot, the commit of the firmware on the secondary partition.
SANSWITCH:admin> firmwaredownloadstatus
[1]: Fri Jan 8 16:16:50 2016
Firmware is being downloaded to the switch. This step may take up to 30 minutes.
[2]: Fri Jan 8 16:22:49 2016
Firmware has been downloaded to the secondary partition of the switch.
[3]: Fri Jan 8 16:24:54 2016
The firmware commit operation has started. This may take up to 10 minutes.
[4]: Fri Jan 8 16:30:05 2016
The commit operation has completed successfully.
[5]: Fri Jan 8 16:30:05 2016
Firmwaredownload command has completed successfully. Use firmwareshow to verify the
firmware versions.
STEP 10: once the switch has been updated to the latest version, execute the following
commands again to close the intervention:
SANSWITCH:admin> statsclear
SANSWITCH:admin> supportsave
84
@@@@@
Firmware Upgrade CLI - Midrange Switch
The following summary describes the default behavior of the firmwareDownload command on
Brocade 200E, 300, 4012, 4016, 4018, 4020, 4024, 4100, 4900, 5000, 5100, 5300, 7500,
and 7600,7800 switches.
1. The Fabric OS downloads the firmware to the secondary partition.
2. The system performs a high-availability reboot (haReboot). After the haReboot, the
former secondary partition is the primary partition.
3. The system replicates the firmware from the primary to the secondary partition.
4. Software application (SA) software is upgraded only when firmwareDownload is issued with
the SA option.
The upgrade process first downloads and then commits the firmware to the switch. After you
start the process, do not enter any disruptive commands (such as reboot) that will interrupt the
process.
The entire firmware download and commit process takes approximately 17 minutes. If there is
a problem, wait for the time-out (30 minutes for network problems). Disrupting the process
can render the switch inoperable. Do not disconnect the switch from power during the process
because the switch could become inoperable when rebooted.
If the firmware download fails in a director or enterprise-class platform, the CPs may
end up with different versions of firmware and are unable to achieve HA
synchronization between the two blades. In such cases, issue the firmwareDownload
-s command on the standby CP; the single mode (-s) option allows you to upgrade
the firmware on the standby CP to match the firmware version running on the active
CP.
Well I do this manually

1. Log into standby CP (slot 6)
2. Collect logs and config, configupload, supportsave
3. Check status -> hashow, firmwareshow, errdump -r
4. firmwaredownload -s -n - Starts download of FOS to secondary partition of standby CP
(slot 6)
5. Check status again
6. Reboot standby CP again - reboot
85
7. Now standby CP is running on new FOS code, hence do hafailover

8. Standby CP (slot 6) becomes Active CP (slot 5)
9. Loginto the newly designated standby CP (slot 5) and run firmwaredownload -s -n
10. Reboot slot 5 standby CP
11. Do complete health check, check error logs, host connectivity and create and commit a
dummy zone
12. Run firmwarecommit on both CP if you are satisfied or you can do these after a few days
as well
The slot numbers may be different, I have just cited these for clarity.
Below is a list of useful Brocade CLI commands that I keep at my desk for reference. Theyre
divided up into categories for Zoning, Show, Port, Time/Date, License, Banner, Password,
SNMP, User Config, Firmware, and Miscellaneous.
Zoning Commands
alicreate Name,
domain,port#
alicreate
Name,portname1;
portname2
alidelete Name
aliadd Name,
domain,port#
aliremove Name,
domain,port#
alishow AliName
zonecreate Zone Name,
alias1; alias2
zonedelete ZoneName
zoneadd ZoneName,
alias name
zoneremove ZoneName,
alias name
zoneshow zoneName
cfgcreate Configname,
Zone1; Zone2
Used to create an alias

To create multiple ports under a single alias
To delete an alias
To add additional ports to an alias
To remove a port from the alias
To show the alias configuration on the switch
To create zones based on alias
To delete a zone
To add additional alias into the zone
To remove an alias from the zone
To show the zone configuration information
To create configurations by adding in zones
86
cfgdelete ConfigName To delete a configuration

cfgadd ConfigName,
To add additional zones in the configuration
Zone3
cfgremove ConfigName,
To remove a zone from the configuration
Zone3
cfgshow ConfigName To show the details of that configuration
cfgenable ConfigName To enable a configuration on the switch
To have the effective configuration to be written into the flash
cfgsave
memory
Show Commands
psshow
fansshow
tempshow
sensorshow
nsshow
nsshow -t
nsshow -r
nscamshow
nsallshow
licenseshow
date
bannershow
httpcfgshow
switchname
fabricshow
userconfig show -a
switchstatusshow
switchstatuspolicyshow
portshow
portcfgshow
configshow fabric.ops
Displays the status of the power supply

Displays the status of the fans
Displays the status of the temperature readings
Displays the status of the sensor readings
Displays information in the name server
Displays information in the name server
Displays the information in the name server along with the state
change registration details
Displays detailed information of all the devices connected to all the
switches in the fabric (Remote Name Servers)
Displays the 24 bit address of all devices that are in the fabric
Displays all the licenses that have been added in the switch
Displays the current date set on the switch
Displays the banner that will appear when logging in using the CLI
or web tools
Displays the JAVA version the switch expects at the management
console
Displays the name of the switch
Displays information of all the switches in the fabric
Displays the account information like role , description , password
exp date , locked status
Displays the overall status of the switch
Displays policy set for the switch regarding Marginal(Yellow) or
Down(Red) error status
To show the port status
Displays the speed set for all ports on all slots and other detailed
port information
Displays the parameters of the switch. Ensure all switches in a
87
fabric have the same parameters in order to communicate

configshow
fabric.ops.pidFormat
switchuptime OR uptime
firmwareshow
version
hashow
Displays the PID set for a switch Core , Native or Extended edge
Displays the uptime for the switch
Displays the firmware on the switch
Displays the current firmware version on the switch
Displays the status of local and remote CPs. High availability ,
heartbeat and synchronization
Port Settings
portcfgshow
portcfg rscnsupr [slot/port]
enable
portcfg rscnsupr [slot/port]
disable
portname
portdisable
portenable
portcfgpersistentdisable
portcfgpersistentenable
portshow
portcfgspeed ,
switchcfgspeed
portcfgshow
portcfgdefault
portcfglongdistance
portcfgeport
Displays the port settings

A registered state change registration is suppressed when a state
change occurs on the port
A registered state change registration is sent when a state change
occurs on the port
To assign a name for a port
To disable a port or slot
To enable a port or slot
To disable a port , status would not change even after rebooting the
switch
To enable a port , status would not change even after rebooting the
switch
To show the port status
To set speed for a port#te 0:auto negotiated 1,2,4 Gbit/sec , 1 :
1Gbit/sec , 2 : 2 Gbit/sec , 4 : 4Gbit/sec
To set speed for all the ports on the switch Note 0:auto negotiated
1,2,4 Gbit/sec , 1 : 1Gbit/sec , 2 : 2 Gbit/sec , 4 : 4Gbit/sec
Displays the speed set for all ports on all slots and other detailed
port information
To set the port settings to default
To set the long distance mode . Default is L0(Normal), as per
distance will display LE <=10 kms , L0.5 <=25kms , L1 <=50 kms,
L2<=100kms , LD=auto , LS = Static
Used to disable a port from being a E port
Time and Date Settings

date
tsclockserver 10.10.1.1
Displays the current date set on the switch

Instruction for the principal switch to synchronize time with the
NTP server (specify the ip address of the NTP server)
88
tsclockserver LOCL
date mmddhhmmyy
tstimezone -5
Instruction to stop NTP server synchronization (Local time of the

switch)
To set the time of the switch when the NTP server synchronization
is cancelled
To set the time zone for individual switches
License Commands
licenseshow
licenseadd
licenseremove
licenseidshow
Displays all the licenses that are added in the switch

To add a new license to the switch
To remove a license from the switch
Based on Switch WWN
Banner Commands
bannershow
bannerset
bannerset
Displays the banner that will appear when logging in using the CLI
or web tools
To set the banner which will appear when logging in using the CLI
or web tools
To remove the bannerset (two quotes)
Password commands
passwd
passwdcfg set -lowercase
3 uppercase 1 -digits 2
-punctuation 2 -minlength
10 -history 3
passwdcfg set
-minpasswordage 1
passwdcfg set
-maxpasswordage 30
passwdcfg set -warning 23
passwdcfg set
-lockoutthreshold 5
passwdcfg set
-lockoutduration 30
passwdcfg setdefault
SNMP Commands
To change the password for that particular login

To set the password rules
To set the minimum password age in Days

To set the maximum password age in Days
To set a warning for the expiration Days remaining
To set the account lockout thresh hold
To set the account lockout duration in Minutes
To restore the password policy to Factory settings (min length 8,
history -1 , lockoutduration 30)
89
snmpconfig
agtcfgset
snmpmibcapset
snmpconfig for 5.0 above fos

snmp config for fos below 5.0
for choosing the MIBs for the snmp settings
User Configuration
userconfig show -a /
userconfig show
userconfig add john -r
admin -d John Doe
userconfig show john
Displays all the account information like role , description , password

expiration date , locked status
To add a new account -r = role , -d = description
Displays all the information for the account john

To Disable an account , usually default a/cs like admin and user . But
userconfig change -e no ensure before disabling the admin a/c there is another a/c with admin
rights
userconfig change -e
To Enable an account
yes
Firmware commands
configupload
configdownload
Saves the switch config as an ASCII text file to an FTP server

To restore a switch configuration from ASCII text file Note Need to
disable the switch before downloading the config file
configure => cfgload

attributes : [y] => Ensure Fabric OS v 4.4 & above provides Secure File Copy Protocol (SCP)
secure config upload / during upload or download of configurations
download : [y]
firmwaredownload
To download the firmware to be installed on the switch
firmwareshow
To be run after installing the firmware on the switch
version
Displays the current firmware version on the switch
Needs to be run after installing the firmware. This does not include
fastboot
the post.
reboot
Needs to be run after installing the firmware. This includes the post.
Miscellaneous commands
killtelnet
configure
quietmode
quietmode 1
switchname
switchname
To kill a particular session which is using telnet

To configure a switch
To switch off the quiet mode
To suppress messages to the console
Displays the switch name
To assign a switch name
90
EXAMPLE
To set the banner which will appear when logging in using the CLI or
web tools
timeout
Displays the timeout time set for Telnet session on the switch
timeout 10
To set a specific timeout time for the Telnet session
switchuptime or uptime Displays the uptime for the switch
To set speed for all the ports on the switch Note 0:auto negotiated
switchcfgspeed
1,2,4 Gbit/sec , 1 : 1Gbit/sec , 2 : 2 Gbit/sec , 4 : 4Gbit/sec
fastboot
To reboot the switch without post
reboot
To reboot the switch with the post
switchstatusshow
Displays the overall status of the switch
Displays policy set for the switch regarding Marginal(Yellow) or
switchstatuspolicyshow
To change the policy set for the switch regarding Marginal(Yellow) or
switchstatuspolicyset
bannerset
NPIV overview
N_Port ID Virtualization (NPIV) enables a single Fibre Channel protocol port to appear
as multiple, distinct ports, providing separate port identification within the fabric for
each operating system image behind the port (as if each operating system image
had its own unique physical port). NPIV assigns a different virtual port ID to each
Fibre Channel protocol device. NPIV is designed to enable you to allocate virtual
addresses without affecting your existing hardware implementation. The virtual port
has the same properties as an N_Port, and is therefore capable of registering with all
services of the fabric.
Each NPIV device has a unique device PID, Port WWN, and Node WWN, and should
act the same as all other physical devices in the fabric; in other words, multiple
virtual devices emulated by NPIV appear no different than regular devices
connected to a non-NPIV port. The same zoning rules apply to NPIV devices as nonNPIV devices. Zones can be defined by domain,port notation, by WWN zoning, or
both. To perform zoning to the granularity of the virtual N_Port IDs, you must use
WWN-based zoning.
If you are using domain,port zoning for an NPIV port, and all the virtual PIDs
associated with the port are included in the zone, then a port login (PLOGI) to a nonexistent virtual PID is not blocked by the switch; rather, it is delivered to the device
attached to the NPIV port. In cases where the device is not capable of handling such
unexpected PLOGIs,you should use WWN-based zoning.
Configuring NPIV
The NPIV feature is enabled by default. You can set the number of virtual N_Port_IDs
per port to a value between 1 and 255 per port. The default setting is 126. To
specify the number of virtual N_Port_IDs per port on a switch, use the
portCfgNPIVport command to enable or disable the feature. Once the feature is
91
enabled on the port, you can specify the number of logins per port. If the feature
has been disabled, then the NPIV port configuration will not work.
The addressing mode can limit the maximum number of NPIV logins to 127 or 63
depending on the mode. The portCfgNPIVPort command can set the maximum
number of NPIV login limit to anything from 1 to 255, regardless of the addressing
mode. Whichever of these two (addressing mode or the value configured through
the portCfgNPIVPort) is lower will be the maximum number that can be logged in.
Viewing NPIV port configuration information

2. Enter the portCfgShow command to view the switch ports information.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@
FabricOS : Reset to factory default and setup basic config on Brocade Fiber Channel
switch fabric By Kaven G. | June 8, 2014
0 Comment
This tutorial is about resetting your Brocade Fiber Chanel Fabric (FabricOS) to
factory defaut. To perform these commands youll need elevated root or admin
users privileges.
1. Reset config to factory default :
configdefault -all
2. Set usernames and passwords to factory default :
passwddefault
3. Set ethernet (management interface) IP addresses :
ipaddrset
4. Set logical switch config parameters :
configure
5. Removes a license key from this system (WARNING! You may want to skip that
step if you do not have any backup of your license key, see notes) :
licenseremove
92
NOTES : This step is a part of the full factory default, however is useless since
licence belong to the physical device and cannot be applied to any other Brocade
products. This is not required unless you really know what youre doing.
6. Activates a default zone configuration :
defzone --allaccess
7. Clear all zone configurations and save zone configurations in flash :
cfgclear;cfgsave
8. Set this switchs name :
switchname
9. Set the chassiss name :
chassisname
10. Configure SNMP :
snmpconfig
@@@@@@@@@@@@@@@@@@@@
Small form-factor pluggable transceiver
The small form-factor pluggable (SFP) is a compact, hot-pluggable transceiver
used for both telecommunication and data communications applications
SFP+
The enhanced small form-factor pluggable (SFP+) is an enhanced version of the SFP that
supports data rates up to 16 Gbit/s.
Small form-factor pluggable (SFP) is a specification for a new generation of optical modular
transceivers. The devices are designed for use with small form factor (SFF) connectors, and offer
high speed and physical compactness. They are hot-swappable.
SFP Modules
Small Form-Factor Pluggable (SFP) Copper and Optical

Fiber Transceivers
SFP+ and SFP Interconnect Solutions
Supporting 2.5 to 10 Gbps data rates for Gigabit Ethernet and Fibre Channel applications, Molexs SFP+ and SFP products
ensure industry-wide compatibility
The differences between SFP and SFP+
93
1. SFP doesn't support 10G transmission data rate that means they can't be used in the same
network.
2. From the price, SFP+ is more expensive than SFP+

3. SFP is based on IEEE802.3 and SFF-8472 while SFP+ is based on SFF-8431.
4. XFP, SFP and SFP+ Comparison
XFP
SFP
10 Gigabit Small
Stands for
SFP+
Small Form-factor
Small Form-factor Pluggable

Form Factor Pluggable
Pluggable plus
155M/622M/
Data rate
10G
1.25G
6G/8.5G/10G
2.5G/3G/4.25G
Dual fiber
Dual fiber
Dual fiber
Single Fiber/WDM
Single Fiber/WDM
Single Fiber/WDM
CWDM
CWDM
CWDM
DWDM
DWDM
DWDM
Terms
300m/2km/
220m/300m/
10km/15km/
220m/300m/
20km/40km/
2km/10km/
60km/80km/
20km/40km/
100km/120km/
60km/80km
2km/10km/
Distance
20km/40km/
60km/80km/
120km
150km
Wavelengths
850nm/1310nm/1550nm
850nm/1310nm/1550nm
220m/300m/
94
2km/10km/
1270nm/1330nm
310nm/1490nm/1550nm
1270nm-1610nm
1270nm-1610nm
20km/40km/
60km/80km/
ITU17~ITU61
ITU17~ITU61
120km
sfpshow - Provides information on SFP and their state, check for

power

ALL Switch

Uploaded by

Document Information

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

ALL Switch

Uploaded by

Copyright:

Available Formats

1

Brocade Communications Systems

EMC Connectrix DS-4900B SAN Switch

EMC Connectrix DS-4900B Switch: 32, 48, or 64 Ports | 1, 2

Key Features and Benefits

Protects existing device investments with auto-configuring 1, 2, and 4 Gbit/sec

EMC Connectrix DS-5000B SAN Switch

Key Features and Benefits

Protects existing investments in EMC Connectrix Fabric OS and M-EOS*-based

Provides industry-leading power and cooling efficiency to reduce Total Cost of

Protects existing device investments with auto-configuring 1, 2, and 4 Gbit/sec

Utilizes the EMC Connectrix EZSwitchSetup wizard, simplifying installation and

EMC Connectrix B Series DS-5100B

Up to 40 ports of high-performance 8 Gbps technology and POD scaling from 24 to 32 or 40

An Enterprise Switch for the most Demanding

Industry-Leading Performance and Scalibility

Adaptive Networking Service

Key Features and Benefits

Delivers full 8 Gbit/sec 1:1 performance for up to 80 ports in a single-domain, optimized

Protects existing device investments with auto-sensing 1, 2, 4, and 8 Gbit/sec capabilities

Enables pay-as-you-grow capabilities with Ports On Demand scalability from 48 to 64

Provides Adaptive Networking services such as Quality of Service (QoS) to help

Improves energy efficiency by combining increased bandwidth with lower power

Utilizes the EMC Connectrix EZSwitchSetup wizard to simplify installation, and is

End-To-End Performance and Reliability

4 Gb/sec port speeds

Up to 384 ports in a single domain

Up to 1152 ports per rack

16, 32, or 48 ports per blade

Hot-swappable Field-Replaceable Units

A Reliable Foundation for Core-to-Edge SANs

Ideal for Enterprise Applications

A Cost-effective Platform for High-performance

Integrated Fabric Application Mobility

Enterprise-Class Directors for Any SAN Environment

EMC CONNECTRIX DS-6505B

configurable in 12 or 24 ports and supports 4, 8, or 16 Gigabits per second (Gb/s)

End of manufacturer support

To configure the connection in a B-Series environment:

Viewing your Domain ID

Setting your Domain ID

Fabric parameters (yes, y, no, n): [no] y

Default timeout on switches is 10 minutes. When changing the timeout value

SET SWITCH NAME:

B51:admin> userconfig --add jdoe -r admin -d "Jane Doe"

To implement a highly available solution that provides redundancy and

The switchshow command can be used to verify the switch is operating

Configuring the fabric name

Upgrade and downgrade considerations

Swapping port area IDs

4. Enter the portSwap command.

Powering off a Brocade switch

Performing a fast boot

A zone set comprises a group of zones that can be activated or deactivated as a

Use the cfgenable command to enable a zone configuration. The specified

Zone database size

Zoning can be categorized into three types:

1. alicreate - to create a alias for a wwn

alicreate "test1", "21:00:00:e0:8b:1d:f9:03

2. zonecreate - to create a zone which consists of two aliases

zonecreate "zone1", "test1; test2"

3. cfgcreate - to create a config which may have multiple zones

cfgcreate "cfg1", "zone1"

Add a member to a zone alias