2014, Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron,
OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks
of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be
trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any
equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document
at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be
currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in
this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the
accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that
accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other open
source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to
the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
The document conventions describe text formatting conventions, command syntax conventions, and
important notice formats used in Brocade technical documentation.
Text formatting conventions
Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text
to highlight specific words or phrases.
Format
bold text
italic text
Courier font
Description
Identifies command names
Identifies keywords and operands
Identifies the names of user-manipulated GUI elements
Identifies text to enter at the GUI
Identifies emphasis
Identifies variables and modifiers
Identifies paths and Internet addresses
Identifies document titles
Identifies CLI output
Identifies command syntax examples
Command syntax conventions
Bold and italic text identify command syntax components. Delimiters and operators define groupings of
parameters and their logical relationships.
Convention
bold textIdentifies command names, keywords, and command options.
valueIn Fibre Channel products, a fixed value provided as input to a command
[ ]Syntax components displayed within square brackets are optional.
option is printed in plain text, for example, --show WWN.
Default responses to system prompts are enclosed in square brackets.
{ x | y | z }A choice of required parameters is enclosed in curly brackets separated by
x | yA vertical bar separates mutually exclusive elements.
< >Nonprinting characters, for example, passwords, are enclosed in angle
...
\
vertical bars. You must select one of the options.
In Fibre Channel products, square brackets may be used instead for this
purpose.
brackets.
Repeat the previous element, for example, member[member...].
Indicates a “soft” line break in command examples. If a backslash separates
two lines of a command input, enter the entire command at the prompt without
the backslash.
Notes, cautions, and warnings
Notes, cautions, and warning statements may be used in this document. They are listed in the order of
increasing severity of potential hazards.
NOTE
A Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference
to related information.
ATTENTION
An Attention statement indicates a stronger note, for example, to alert you when traffic might be
interrupted or the device might reboot.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or
extremely hazardous to you. Safety labels are also attached directly to products to warn of
these conditions or situations.
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.
You can download additional publications supporting your product at www.brocade.com. Select the
Brocade Products tab to locate your product, then click the Brocade product name or image to open the
individual product page. The user manuals are available in the resources module at the bottom of the
page under the Documentation category.
To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can
register at no cost to obtain a user ID and password.
Release notes are available on MyBrocade under Product Downloads.
White papers, online demonstrations, and data sheets are available through the Brocade website.
Contacting Brocade Technical Support
Brocade resources
As a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by email. Brocade OEM customers contact their OEM/Solutions provider.
Brocade customers
For product support information and the latest information on contacting the Technical Assistance
Center, go to http://www.brocade.com/services-support/index.html.
If you have purchased Brocade product support directly from Brocade, use one of the following methods
to contact the Brocade Technical Assistance Center 24x7.
OnlineTelephoneE-mail
Preferred method of contact for nonurgent issues:
• My Cases through MyBrocade
• Software downloads and licensing
tools
• Knowledge Base
Required for Sev 1-Critical and Sev
2-High issues:
• Continental US: 1-800-752-8061
• Europe, Middle East, Africa, and
Asia Pacific: +800-AT FIBREE
(+800 28 34 27 33)
• For areas unable to access toll
free number: +1-408-333-6061
• Toll-free numbers are available in
many countries.
support@brocade.com
Please include:
• Problem summary
• Serial number
• Installation details
• Environment description
Brocade OEM customers
If you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your
OEM/Solution Provider for all of your product support needs.
• OEM/Solution Providers are trained and certified by Brocade to support Brocade® products.
• Brocade provides backline support for issues that cannot be resolved by the OEM/Solution Provider.
• Brocade Supplemental Support augments your existing OEM support contract, providing direct
access to Brocade expertise. For more information, contact Brocade or your OEM.
• For questions regarding service levels and response times, contact your OEM/Solution Provider.
Document feedback
To send feedback and report errors in the documentation you can use the feedback form posted with
the document or you can e-mail the documentation team.
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a topic
needs further development, we want to hear from you. You can provide feedback in two ways:
• Through the online feedback form in the HTML documents posted on www.brocade.com.
• By sending your feedback to documentation@brocade.com.
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.
• Up to 512 16-Gbps external ports in a single chassis , enabling high density SAN configurations with
reduced footprint.
• Support for 2, 4, 8, and 16 Gbps autosensing Fibre Channel ports. Trunking technology groups up to
eight ports to create high performance 128-Gbps ISL trunks between switches.
• The Brocade DCX 8510-8 also supports 10-Gbps FC-type SFPs in 32/48-port 16-Gbps port blades,
and 10-GbE SFPs in the FX8-24 and FCOE10-24 application blades . The two types of SFPs are not
interchangeable.
• The 10-Gbps port speed can be manually configured on any port of the 32- and 48-port 16-Gbps port
blades.
• Support for many of the application, port blade, and control processor (CP) blades supported in the
Brocade DCX family of backbones (with the exception of the Core Switch Blade), thereby providing
flexible system configurations and fewer types of new blades.
• Beginning with Fabric OS v7.0.1, up to nine chassis can be connected with the use of 4x16 Gbps
quad SFP (QSFP) inter-chassis links (ICLs). Fabric OS v7.0.0 permits up to six chassis to be linked.
• Support for high-performance port blades running at 2, 4, 8, 10, or 16-Gbps, enabling flexible system
configuration.
• Redundant and hot-swappable control processor and core switch blades, power supplies, blower
assemblies, and WWN cards that enable a high availability platform and enable nondisruptive
software upgrades for mission-critical SAN applications.
• Universal ports that self-configure as E_Ports, F_Ports, EX_Ports and M_Ports (mirror ports). 10Gbps ports are E_Ports only.
• Diagnostic port (D_Port) functionality.
• In-flight data cryptographic (encryption/decryption) and data compression capabilities through the 16Gbps port blades when configured as ISLs.
• Fibre Channel over IP (FCIP) functionality through the FX8-24 blade.
• Fibre Channel over Ethernet (FCoE) capability through the FCOE10-24 blade.
The Brocade DCX 8510-8 features a modular and scalable mechanical construction that allows a wide
range of flexibility in installation, fabric design, and maintenance. The chassis can be mounted with the
cables facing the front of the equipment rack or to the rear, and consists of the following:
• Up to eight hot-swappable port blade assemblies that can be configured in a single chassis,
delivering up to 512 16-Gbps Fibre Channel ports.
• Two slots for control processor blades (CP8):
‐A single active CP8 blade can control all 512 ports in the chassis.
‐The standby CP8 blade assumes control of the Brocade DCX 8510-8 if the active CP fails.
• Two slots for core switch blades (CR16-8):
‐CR16-8 blade interconnects all port blades.
‐Inter-chassis link (ICL) connectors to connect to as many as nine neighboring chassis
using Fabric OS v7.0.1 or later. Only six chassis can be connected using Fabric OS v7.0.0.
using existing Ethernet infrastructure. The FCoE blade can be used in the same chassis
with only the FC8-32E and FC16-32 port blades. The FCoE blade cannot be used with any
other FC port or application blades in the same chassis.
• Modular, hot-swappable encryption blades:
‐FS8-18: 16-port, up to 4 blades per chassis, supporting in-flight data cryptographic
(encryption/decryption) and data-compression capabilities.
• Modular, hot-swappable field-replaceable units (FRUs):
‐Three blower assemblies.
‐Up to four power supplies (100-240 VAC autosensing).
‐At 110 VAC (nominal): Four power supplies are required for high availability.
‐220 VAC (nominal) is recommended for efficiency. Two or four power supplies
are provided depending on the quantity ordered. Refer to "Power specifications"
in the "Specifications" appendix for specific requirements for high availability.
‐Redundant AC primary power connections ensure high availability. Each power
supply has its own connector, so the number of primary power connections is four
for optimum efficiency and redundancy.
‐Two WWN cards.
‐Blades use small form-factor pluggable (SFP+, mSFP, and QSFP) optical transceivers.
‐‐The 8-Gbps SFP+s and mSFPs auto-negotiate at 2, 4, and 8 Gbps.
‐The 10-Gbps speeds must be manually set and require special 10-Gbps FC SFP
+ transceivers.
‐The 16-Gbps SFP+ transceivers support speeds of 2, 4, 8, 10, and 16 Gbps.
‐The 16-Gbps QSFPs supported on FC16-64 prot blade auto-negotiate at 4, 8, and
16 Gbps.
‐The 16-Gbps QSFPs based inter-chassis link (ICL) on the core blades run at 64
Gbps (four fixed 16-Gbps clustered in a single quad connector and cable).
• Blades that are serviced from the port side of the Brocade DCX 8510-8. Blowers, power supplies,
and power cables that are serviced from the nonport side.
• World Wide Name (WWN) cards on the nonport side, to maintain chassis-specific information such
as WWNs, IP addresses, and summary status information of each port blade and power supply
through LEDs.
• Redesigned cable management comb and chassis door.
Port side of the Brocade DCX 8510-8
NOTE
Airflow in the Brocade DCX 8510-8 is from the nonport (noncable) side to the port (cable) side and out
the exhaust vent.
CP8The CP8 blade contains the control plane for the chassis. There are two CP8
blades for redundancy. This control processor blade is compatible with the
Brocade DCX 8510-8, Brocade DCX 8510-4, Brocade DCX, and Brocade
DCX-4S.
Page 18
Brocade DCX 8510-8 Overview
DescriptionNameFunction
Blades available for the Brocade DCX 8510-8 (Continued)TABLE 1
Brocade DCX
8510-8 core switch
blade
32-port 8-Gbps port
blade
48-port 8-Gbps port
blade
64-port 8-Gbps port
blade
32-port 16-Gbps
port blade
48-port 16-Gbps
port blade
CR16-8The CR16-8 blade contains the ASICs for switching between port blades.
Every port blade connects to each core switch blade. There can be up to 512
16-Gbps or 8-Gbps total ports for port blades. Each core switch blade connects
to 128 backplane ports. Core switch blades have additional front port
connectivity to connect multiple chassis and backplane connections for the
storage server blade. This core switch blade is compatible only with the
Brocade DCX 8510-8. Requires specific type of QSFP transceivers.
FC8-32EA 32-port Brocade port blade supporting 2, 4, and 8 Gbps Fibre Channel port
speeds. This port blade is compatible with the Brocade DCX 8510-8 and
Brocade DCX 8510-4. This blade requires Fabric OS v7.0.1 or later to run in
this chassis.
FC8-48EA 48-port Brocade port blade supporting 2, 4, and 8 Gbps Fibre Channel port
speeds. This port blade is compatible with the Brocade DCX 8510-8 and
Brocade DCX 8510-4. This blade requires Fabric OS v7.0.1 or later to run in
this chassis.
FC8-64A 64-port Brocade port blade supporting 2, 4, and 8 Gbps port speeds with
mSFPs. This port blade is compatible with the Brocade DCX 8510-8, Brocade
DCX 8510-4, Brocade DCX, and Brocade DCX-4S.
FC16-32A 32-port Brocade port blade supporting 2, 4, 8, 10, and 16 Gbps Fibre
Channel port speeds. The blade also supports port-based in-flight encryption/
decryption and compression/decompression. This port blade is compatible with
the Brocade DCX 8510-8 and Brocade DCX 8510-4 and requires Fabric OS
v7.0.0 or later to run in this chassis.
FC16-48A 48-port Brocade port blade supporting 2, 4, 8, 10, and 16 Gbps Fibre
Channel port speeds. The blade also supports port-based in-flight encryption/
decryption and compression/decompression. This port blade is compatible with
the Brocade DCX 8510-8 and Brocade DCX 8510-4 and requires Fabric OS
v7.0.0 or later to run in this chassis.
FC16-64A 64-port Brocade port blade supporting 4, 8, and 16-Gbps Fibre Channel port
speeds. The blade also supports port-based in-flight encryption/decryption and
compression/decompression. This port blade is compatible with the Brocade
DCX 8510-8 and Brocade DCX 8510-4 and requires Fabric OS v7.3.0 or later
to run in this chassis. Requires specific type of QSFP transceivers and those
are not the same as used in the core blades.
FCOE10-24 The FCOE10-24 blade enables FCoE functionality over existing Ethernet
infrastructure utilizing CEE protocols. It has 24 10-GbE ports available. This
FCoE application blade is compatible with the Brocade DCX, Brocade
DCX-4S, and Brocade DCX 8510-8 chassis.This FCoE blade can be used in
the same chassis with only the FC8-32E and FC16-32 port blades. This FCoE
blade cannot be used with any other FC port blades or application blades in
the same chassis. Refer to the Fabric OS Release Notes for limitations in using
this blade.
FS8-18The FS8-18 blade enables data cryptographic (encryption/decryption) and
data-compression capabilities for data-at-rest. It has 16 Fibre Channel optical
SFP ports. This application blade is compatible with the Brocade DCX 8510-8,
Brocade DCX 8510-4, Brocade DCX, and Brocade DCX-4S and requires
Fabric OS v7.0.0 or later to run in the 8510-4 and 8510-8 chassis.
53-1002180-07
Page 19
Blades available for the Brocade DCX 8510-8 (Continued)TABLE 1
DescriptionNameFunction
High availability
FCIP extension
blade
High availability
The following features contribute to the Brocade DCX 8510-8 high availability design:
• Redundant, hot-swappable FRUs, including blades, power supplies, blowers, and WWN cards
• Enhanced data integrity on all data paths
• Fabric Shortest Path First (FSPF) rerouting around failed links
• Integration with Simple Network Management Protocol (SNMP) managers
• Automatic control processor failover
• Nondisruptive "hot" software code loads and activation
• Easy configuration, save, and restore
The high availability software architecture of the Brocade DCX 8510-8 provides a common framework
for all applications that reside on the system, allowing global and local states to be maintained through
any component failure. High availability elements consist of the High Availability Manager, the
heartbeat, the fault/health framework, the replicated database, initialization, and software upgrade.
The High Availability Manager controls access to the standby control processor, facilitates software
upgrades, prevents extraneous CP failover activity, closes and flushes streams, provides flow control
and message buffering, and supports a centralized active and standby state.
FX8-24The FX8-24 blade enables FCIP functionality over existing IP infrastructure. It
has 12 FC ports, 10 1-GbE ports, and two 10-GbE ports available. This
application blade is compatible with the Brocade DCX 8510-8, Brocade DCX
8510-4, Brocade DCX, and Brocade DCX-4S and requires Fabric OS v7.0.0 or
later to run in the DCX 8510-4 and DCX 8510-8 chassis.
Reliability
The Brocade DCX 8510-8 uses the following error detection and correction mechanisms to ensure
reliability of data:
• Error Detection and Correction over main control processor memory.
• Error Detection and Correction mechanism, which checks for encoder errors and fault isolation
(EDFI), such as cyclic redundancy checking (CRC), parity checking, checksum, and illegal address
checking.
• Power-on self-test (POST).
• Dual control processors that enable hot, nondisruptive fast firmware upgrades.
• One serial port and two Ethernet ports (on each control processor) for management and for service.
Offline control processor diagnostics and remote diagnostics simplify troubleshooting. The standby
control processor monitors diagnostics to ensure the system is operational should a failover be
necessary.
• Bus monitoring and control of blades and other field-replaceable units (FRUs).
The Brocade DCX 8510-8 provides the following features to enhance and ensure serviceability:
• Modular design with hot-swappable components.
• Flash memory that stores two firmware images per control processor.
• USB port on control processor blades for most tasks that formerly required an FTP/SCP server,
including software and firmware upgrades.
• Nonvolatile random-access memory (NVRAM), containing the OEM serial number, Brocade serial
number, revision information, and part number information.
• Background health-check daemon.
• Memory scrubber, self test, and bus ping to determine if a bus is not functioning.
• RASlog messages.
• SMI-S compliant.
• Hardware and software watchdog timers.
• Status LEDs.
• Predictive diagnostics analysis through Fabric Watch.
• SNMP (including version 3) integration with higher-layer managers.
Software features
The Fabric OS allows any Fibre Channel-compliant device to attach to the switches as long as it
conforms to the device login, name service, and related Fibre Channel standards. Each operating
environment requires that a Fibre Channel host bus adapter (HBA) be available with a standardscompliant driver for correct interface to the fabric.
Fabric OS consists of a set of embedded applications running on top of an embedded Linux operating
system kernel. Some of these applications include:
• Name server
• Alias server
• Zone server
• Simple Network Management Protocol (SNMP) agent
• SMI-S compliant API
• Syslog auditing
• Reliable Commit Service (RCS)
• NTP
• Tasks to manage address assignment, routing, link initialization, fabric initialization, link shutdown,
Brocade DCX 8510-8 shutdown, and the user interface
Security
The following list highlights some of the key security features available for the Brocade DCX 8510-8
and for other Brocade enterprise-class products running Fabric OS 7.0.1 or later. For details, contact
your Brocade DCX 8510-8 supplier and refer to the Brocade White Paper, "The Growing Need for
Security in Storage Area Networks."
• Trusted Switch (FCS) for central security management
• Management access controls (SNMPv3, Telnet, FTP, serial port, front panel)
• Hardware-enforced zoning by WWN, domain/port ID, or both
• Default zoning
• RSCN suppression and aggregation
• Configurable RSCN suppression by port
• NTPv3 (to synchronize timestamps)
• Event auditing
• Change tracking
• Firmware change alerts in Fabric Manager
• Persistent port disable
• Persistent domain ID
• E_Port disable
Network manageability
The Brocade DCX 8510-8 has a single domain and is managed as a single element with Brocade
Network Advisor. The Brocade DCX 8510-8 responds to its own IP address and appears as a separate
entity to the Telnet protocol and SNMP.
All management interfaces, such as Telnet, Web Tools, standards-compliant SMI-S, and Management
Server, support a "port N within blade M" naming scheme.
The Brocade DCX 8510-8 supports SNMPv1 and SNMPv3. When SNMP devices send SNMP
messages to a management console running SAN management software, the information is stored in a
management information base (MIB). Fabric OS v7.0.0 and later supports the latest Fibre Alliance Fibre
Channel Management (FCMGMT) and Storage Management Initiative (SMI) MIBs, which allow
common information necessary for management software to provide information to a SAN
administrator. Refer to the Fabric OS MIB Reference for additional MIB information.
You can set up and install the Brocade DCX 8510-8 in the following ways:
• As a standalone unit on a flat surface.
• In a 19-inch Electronic Industries Association (EIA) cabinet, using the 14U Rack Mount Kit (provided).
• In a mid-mount telecommunications (Telco) rack, using the Mid-Mount Rack Kit available from your
Brocade DCX 8510-8 supplier.
This chapter describes how to set up the Brocade DCX 8510-8 as a standalone unit. For rack-mount
installation instructions, refer to the appropriate manual as described in the following table.
The following table describes the main installation and setup tasks, the estimated time required for
each, and the items required to complete the task based on a fully populated Brocade DCX 8510-8 (512
Fibre Channel ports using the FC16-64 port blades). Configurations with fewer ports require less time.
These time estimates assume a prepared installation site and appropriate power and network
connectivity.
Installation tasks, time, and items required TABLE 2
Installation taskTime estimateItems required
Site preparation and unpacking
Brocade DCX 8510-8
Installing rack mount kit30 minutesRefer to the 14U Rack Mount Kit Installation Procedure or
Hydraulic lift or assisted lift, able to raise to a minimum of
140 cm (55 in.), with a minimum capacity of 115 kg (254
lb). The Brocade DCX 8510-8 weighs 161.2 kg (355 lb)
with eight FC16-64 port blades installed (512 ports).
the Mid-Mount Rack Kit Installation Procedure.
30 minutes
Page 24
Preparing for the Brocade DCX 8510-8 installation
Installation tasks, time, and items required (Continued)TABLE 2
Installation taskTime estimateItems required
Installing power cables and
powering on the Brocade DCX
8510-8
Establishing serial connection,
logging in to Brocade DCX 8510-8,
and configuring IP addresses
Installing an Ethernet cable,
opening a Telnet session, and
configuring the Brocade DCX
8510-8 domain ID, date and time,
and additional system parameters.
Verify and back up configuration.
Installing transceivers as needed30 minutes
Attaching fiber-optic cables, cable
ties, and cable guides
20 minutesPower cables (provided in the Brocade DCX 8510-8
20 minutesSerial cable (provided in the accessory kit).
20 minutesEthernet cabling (optional) for Telnet access.
(longer if using
high-density port
blades)
2-3 hoursFiber-optic cables, cable ties, and cable management
accessory kit).
Workstation computer with a serial port or terminal server
port and a terminal emulator application (such as
HyperTerminal).
Ethernet IP addresses for the Brocade DCX 8510-8
chassis and for both control processor blades: total three
addresses.
Refer to the Fabric OS Administrator's Guide.
SFP+, mSFP, and QSFP optical transceivers as needed.
comb.
Preparing for the Brocade DCX 8510-8 installation
NOTE
Read the Caution and Danger Notices before installation. Read Power specifications on page 131 to
plan for meeting power supply standards before installing the chassis. Read Cable management on
page 29 to plan for cable management.
The following steps are required to ensure correct installation and operation.
1. Provide a space that is 14 rack units (14U) high, 61.29 cm (24.09 in.) deep, and 43.74 cm (17.22
in.) wide. 1U is equal to 4.45 cm (1.75 in.).
Plan to install the Brocade DCX 8510-8 with the nonport side facing the air-intake aisle. The
Brocade DCX 8510-8 can be installed facing either direction, if serviceability and cooling
requirements are met.
2. Ensure that dedicated electrical branch circuits with the following characteristics are available:
NOTE
Refer to Power specifications on page 131 for specific requirements depending on your chassis
configuration.
• 200 - 240 VAC, 50-60 Hz (two branch circuits) - recommended for high availability and maximum
blade usage when configured with 192 16 Gbps ports (four circuits required for high availability if
configured with 384 16 Gbps ports)
• Two or four cables for 200 - 240 VAC service; up to four cables for 110 - 120 VAC service
• Protected by a circuit breaker in accordance with local electrical codes
• Supply circuit, line fusing, and wire size adequate to the electrical rating on the chassis nameplate
• Location close to the chassis and easily accessible
• Grounded outlets installed by a licensed electrician and compatible with the power cords
CAUTION
Use a separate branch circuit for each power cord, which provides redundancy in case one of
the circuits fails.
3. Plan for cable management before installing the chassis.
Cables can be managed in a variety of ways, such as by routing cables below the chassis, to either
side of the chassis, through cable channels on the sides of the cabinet, or by using patch panels.
4. Ensure that the following is available for configuration of the Brocade DCX 8510-8:
• Workstation with an installed terminal emulator, such as HyperTerminal
• Serial cable (provided)
• Three Ethernet cables (including one spare)
• Access to an FTP server for backing up the switch configuration or collecting supportsave output
data (optional)
• A Brocade USB stick for collecting supportsave output data (optional)
• Transceivers (copper and optical) and compatible cables
5. Ensure that the air intake and exhaust vents have a minimum of 5.1 cm (2 in.) of airspace.
6. Ensure that the air temperature on the air intake side is less than 40°C (104°F) during operation.
Unpacking and installing the Brocade DCX 8510-8
Use the following procedure to unpack and install your Brocade DCX 8510-8.
DANGER
A fully populated Brocade DCX 8510-8 (eight FC16-64 port cards, 512 ports) weighs
approximately 161.2 kg (355 lbs) and requires a hydraulic or assisted lift to install it.
1. Unpack the Brocade DCX 8510-8.
a)Cut the bands that encircle the packaging.
b)Remove the lid and the kits and foam from the top of the chassis.
c)Lift the cardboard box off the chassis and remove the plastic bag from around the
chassis.Save the packing materials for use when returning the old chassis.
d)Leave the chassis on top of the plastic shipping tray if the chassis must be transported to
The Brocade DCX 8510-8 packaging does not incorporate a wood pallet and pallet
brackets. The chassis sits on top of a plastic shipping tray.
2. Use a pallet jack or other assisted lift to transport the new chassis to the installation area. Doorways
must be wider than 36 in. (91 cm) to accommodate the chassis.
3. Remove the 14U Rack Mount Kit, accessory kit, packing foam, and antistatic plastic from the
chassis and set aside.
4. Remove the chassis door from the Brocade DCX 8510-8.
5. Remove the cable management comb.
6. Use a lift to raise the chassis to the correct level. If installing the chassis in a cabinet, follow the
instructions provided by the rack kit manufacturer.
7. If applicable, lock the wheels of the lift.
8. Gently slide the chassis onto the final installation surface, ensuring that it remains supported during
the transfer.
9. Ensure that the chassis is oriented so that the nonport side has access to intake air (cool).
10.Reinstall the cable management comb.
11.Reinstall the door. The door must be installed to meet EMI compliance.
Items included with the Brocade DCX 8510-8
The Brocade DCX 8510-8 ships with the following:
• Brocade DCX 8510-8 chassis, populated with:
‐Control processor blades (CP8)
‐Core switch blades (CR16-8)
‐Port blades, application blades, and encryption blades (included based on customer
specification)
‐Blade slot filler panels (for slots not filled by blades)
‐WWN cards
‐WWN bezel (logo plate)
‐Power supplies
‐Power supply filler panel (included if there are fewer than four power supplies)
‐Blower assemblies
‐Cable management comb
‐Chassis door
• Accessory kit containing the following items:
‐Brocade DCX 8510-8 Backbone QuickStart Guide
‐ESD grounding strap
‐USB device
‐RS-232 serial cable. The RS-232 cable has an adapter at one end that can be removed to
provide an RJ-45-style connector.
• 14U Rack Mount Kit with instructions (includes rear brackets and bottom support rails)
Order the Brocade-branded optical transceivers (SFP+, mSFP, and QSFP). The Brocade DCX 8510-8
supports SWL, LWL, and ELWL transceivers. The mSFPs and QSFPs are SWL transceivers only.
Providing power to the Brocade DCX 8510-8 Backbone
NOTE
For information about the SFP+, mSFP, and QSFP transceivers that are qualified for the Brocade DCX
8510-8, go to http://www.brocade.com/downloads/documents/matrices/sfp-matrix-mx.pdf .
Providing power to the Brocade DCX 8510-8 Backbone
For this procedure, refer to Power specifications on page 131 for power supply requirements for your
chassis.
Complete the following steps to provide power to the chassis.
DANGER
Make sure that the power source circuits are properly grounded, then use the power cord
supplied with the device to connect it to the power source.
1. Connect the AC power cords to the power supply assemblies. Two or four power cords are required
depending on electrical service and if the high availability option is selected.
2. Connect the power cords to a power source with voltage of 200 to 240 VAC, 47 to 63 Hz (normally
two power cords or as many as four) or optionally to a power source with voltage of 110 to 120 VAC,
47 to 63 Hz (up to four power cords).
NOTE
Use of the high-voltage line (200 to 240 VAC) is highly recommended because of better powerconversion efficiency. A DCX 8510-8 chassis fully loaded with 16 Gbps port blades (512 ports total)
should be supplied with four power supplies connected to 200-240 VAC lines.
3. Switch the AC power switches on the power supplies to I. The AC power switches light green when
switched on and power is supplied.
The Brocade DCX 8510-8 performs a power-on self-test (POST) each time it is powered on. POST
takes approximately 10 minutes and is complete when the indicator light activity displays the
operational state. You can bypass POST by using the fastBoot command. You can also disable
POST for successive reboots on the Brocade DCX 8510-8 using the diagDisablePost command.
NOTE
Do not connect the switch to the network until the IP addresses are configured.
For information about LED patterns, refer to Monitoring System Components on page 47.
Port numbering
The Brocade DCX 8510-8 uses the following port numbering method (Port Numbering Template on
page 151" ):
• The FC ports are numbered from 0
through 11 in two vertical columns of six
ports starting from the bottom left and
bottom right in the lower group of 12
ports. They are labeled FC on the front
panel diagram.
• The two 10-GbE ports are 0 and 1 and
are in the left column just above the FC
ports. They are labeled 10GE on the
front panel diagram.
• The 1-GbE ports are numbered 0
through 9 and are in both columns above
the FC and 10GE ports. They are labeled
GE on the front panel diagram.
Up to three FC trunking groups are permitted.
The three groups are defined as follows:
• Trunk group 0: FC ports 0, 1
• Trunk group 1: FC ports 6, 7
• Trunk group 2: FC ports 2, 3, 4, 5, 8, 9, 10,
11
Chassis slots are numbered 1 through 12, from left to right when facing the port side of the Brocade
DCX 8510-8. Control processor blades (CP8) can be installed only in slots 6 and 7. Core switch blades
(CR16-8) can be installed only in slots 5 and 8. The rest of the slots, 1-4 and 9-12, can be filled with
port, application, or encryption blades. Unused slots must be filled with blade filler panels to maintain
adequate cooling.
Cable management
The cable management comb (Port side of the Brocade DCX 8510-8 on page 15) is attached to the
chassis under the chassis door and allows for simple cable management. The comb can be installed
without service disruption.
NOTE
The minimum radius to which a 50 micron cable can be bent under full tensile load is 5.1 cm (2 in.). For
a cable under no tensile load, that minimum is 3.0 cm (1.2 in.).
Cables can be organized and managed in a variety of ways, for example, using cable channels on the
sides of the cabinet or patch panels to minimize cable management. Following is a list of
recommendations:
NOTE
You should not use tie wraps with optical cables because they are easily overtightened and can
damage the optic fibers.
Before plugging a cable into to any port, be sure to discharge the voltage stored on the cable
by touching the electrical contacts to ground surface.
• Plan for rack space required for cable management before installing the switch.
• Leave at least 1 m (3.28 ft) of slack for each port cable. This provides room to remove and replace
the switch, allows for inadvertent movement of the rack, and helps prevent the cables from being
bent to less than the minimum bend radius.
• If you are using Brocade ISL Trunking, consider grouping cables by trunking groups. The cables
used in trunking groups must meet specific requirements, as described in the Fabric OSAdministrator’s Guide .
• For easier maintenance, label the fiber-optic cables and record the devices to which they are
connected.
• Keep LEDs visible by routing port cables and other cables away from the LEDs.
• Use Velcro ® type straps to secure and organize fiber-optic cables.
NOTE
Do not route the cables in front of the air exhaust vent, which is located at the top of the port side of
the chassis.
High-density cabling
The FC8-64 high density port blade cannot use the standard LC cables because the pitch between
optics in the new mini-SFP (mSFP) transceiver is smaller than in standard SFPs. Patch cables and
panels can be used to attach standard size cabling to the blade if necessary. The following figure
illustrates the mSFP to SFP patch cable. Refer to "Best Practices Guide: High Density Cable
Management Solutions" (available at http://www.brocade.com ) for cable management guidelines for
high-density port solutions, and cable and patch panel part numbers.
FIGURE 3 Cable design for the mSFP patch cables for the FC8-64 high density port blade
1. mSFP connector
2. Duplex clip (black)
3. 6 mm cable
4. SFP connector
Note that the duplex clip on the mSFP end of the cable is black for easier recognition. Refer to
Qualified cables for the FC8-64 port blade on page 138 for a listing of the qualified mSFP optical
cables for the FC8-64 port blade.
If ISL Trunking is in use, group the cables by trunking group. The ports are color-coded to indicate
which ports can be used in the same ISL Trunking group: eight ports marked with solid black ovals
alternate with eight ports marked with oval outlines.
● Verifying correct operation and backing up the configuration......................................... 45
● Powering off the Brocade DCX 8510-8........................................................................... 46
Configuring the Brocade DCX 8510-8
The Brocade DCX 8510-8 must be configured before it is connected to the fabric, and all of the
configuration commands must be entered through the active CP blade. The Brocade DCX 8510-8
configuration includes the following parameters:
• IP address and subnet mask for the chassis
• IP addresses, host names, subnet masks, and gateway addresses for both CP blades
• Switch name
• Domain ID for the Brocade DCX 8510-8 (optional)
• WWN for the Brocade DCX 8510-8
The Brocade DCX 8510-8 WWN is initially set by the factory to match the license ID (which is based on
the chassis serial number). The WWN can be changed but the license ID cannot be modified.
The configuration information is mirrored to the standby CP blade, which allows the current
configuration to remain available even if the active CP blade fails. The configuration information for the
Brocade DCX 8510-8 is stored in the WWN cards and the flash memory of the CP blades. The
configuration can be backed up to a workstation (uploaded) and then downloaded to the active CP
blade if necessary.
NOTE
If the Brocade FS8-18 encryption blade is installed, refer to the Fabric OS Encryption Administrator’s
Guide for the procedures to configure the encryption functions.
The following figure illustrates the flow of the basic configuration tasks.
Establishing a serial connection to the Brocade DCX 8510-8
FIGURE 4 Configuration tasks
Establishing a serial connection to the Brocade DCX 8510-8
To establish a serial connection to the console port on the Brocade DCX 8510-8, complete the
following steps.
1. Verify that the Brocade DCX 8510-8 is powered on and that POST is complete by verifying that all
power LED indicators on the port, control processor, and core switch blades display a steady green
light.
2. Remove the shipping cap from the CONSOLE port on the active CP. Use the serial cable provided
with the Brocade DCX 8510-8 to connect the CONSOLE port on the active CP to a computer
workstation. The active CP blade is indicated by an illuminated (blue) LED.
The CONSOLE port is intended primarily for the initial setting of the IP address and for service
purposes.
3. Access the Brocade DCX 8510-8 using a terminal emulator application (such as HyperTerminal in a
Windows environment or tip in a UNIX environment).
4. Disable any serial communication programs running on the workstation (such as synchronization
programs).
5. Open a terminal emulator application (such as HyperTerminal on a PC, or term, tip, or kermit in a
UNIX environment), and configure the application as follows:
• In a Windows environment:
ParameterValue
Bits per second9600
Data bits8
ParityNone
Stop bits1
Flow controlNone
• In a UNIX environment, enter the following string at the prompt:
tip /dev/ttyb -9600
If ttyb is already in use, use ttya instead and enter the following string at the prompt:
tip /dev/ttya -9600
When the terminal emulator application stops reporting information, press Enter. You receive the
following login prompt:
CP0 Console Login:
6. Proceed to the next task.
Logging in to the serial console port
To log in to the Brocade DCX 8510-8 through the serial connection, follow these steps.
1. Log in to the Brocade DCX 8510-8 as admin. The default password is password. At the initial login,
you are prompted to enter new admin and user passwords. Make sure to write down the new
passwords and keep this information in a secure location.
Fabric OS (swDir)
swDir login: admin
Password:
Please change your passwords now.
Use Control-C to exit or press 'Enter' key to proceed.
2. (Optional) Modify passwords. To skip modifying the password, press Ctrl+C. For more information
on passwords, refer to the Fabric OS Administrator's Guide.
NOTE
Passwords can be 8 to 40 characters long. They must begin with an alphabetic character. They can
include numeric characters, the period (.), and the underscore (_) only. Passwords are casesensitive, and they are not displayed when you enter them on the command line. For more
information on passwords, refer to the Fabric OS Administrator's Guide.
Configuring the IP addresses
The Brocade DCX 8510-8 requires three IP addresses, which are configured using the ipAddrSet
command. IP addresses are required for both CP blades (CP0 and CP1) and for the chassis
management IP (shown as SWITCH under the ipAddrShow command) in the Brocade DCX 8510-8.
NOTE
The default IP addresses and host names for the Brocade DCX 8510-8 are:
• 10.77.77.75 / CP0 (the CP blade in slot 6 at the time of configuration)
• 10.77.77.74 / CP1 (the CP blade in slot 7 at the time of configuration)
NOTE
Resetting an IP address while the Brocade DCX 8510-8 has active IP traffic or has management and
monitoring tools running, such as DCFM, Fabric Watch, and SNMP, can cause traffic to be interrupted
or stopped.
Complete the following steps to set the IP addresses for the Brocade DCX 8510-8.
1. Log in to the active CP as admin using the serial cable connection.
2. Set up the Brocade DCX 8510-8 IP address by entering the ipaddrset -chassis command:
swDir:admin> ipAddrSet -chassis
Enter the information at the prompts. Specify the -chassis IP address. The -sw 0 IP address is not
valid on this chassis.
NOTE
The addresses 10.0.0.0 through 10.0.0.255 are reserved and used internally by the Brocade DCX
8510-8. External IPs must not use these addresses.
3. Set up the CP0 IP address by entering the ipaddrset -cp 0 command:
swDir:admin> ipAddrSet -cp 0
Enter the information at the prompts.
4. Set up the CP1 IP address by entering the ipaddrset -cp 1 command:
swDir:admin>
ipaddrset -cp 0
Host Name [cp0]:
Ethernet IP Address [10.77.77.75]: 192.168.1.2
Ethernet Subnetmask [0.0.0.0
]: 255.255.255.0
Gateway IP Address [0.0.0.0
]: 192.168.1.254
IP address is being changed...Done.
Committing configuration...Done.
swDir:admin> ipaddrset -cp 1
Host Name [cp1]:
Ethernet IP Address [10.77.77.74]: 192.168.1.3
Ethernet Subnetmask [0.0.0.0]: 255.255.255.0
Gateway IP Address [0.0.0.0]: 192.168.1.254
IP address of remote CP is being changed...Done.
Committing configuration...Done.
Logging off the serial console port and disconnecting the serial cable
You can use the serial port to monitor error messages through the serial connection. If the serial port is
no longer required, use the logout command to log out of the serial console, remove the serial cable,
and replace the plug in the serial port.
Establishing an Ethernet connection to the Brocade DCX 8510-8
After using a serial connection to configure the IP addresses for the Brocade DCX 8510-8, you can
connect the active CP blade to the local area network (LAN).
NOTE
Connecting the CP blades to a private network or VLAN is recommended.
By establishing an Ethernet connection, you can complete the Brocade DCX 8510-8 configuration using
a serial session, Telnet, or management applications, such as Web Tools or Brocade Network Advisor.
Perform the following steps to establish an Ethernet connection to the Brocade DCX 8510-8.
1. Remove the shipping plug from the Ethernet port on the active CP blade.
2. Insert one end of an Ethernet cable into the Ethernet port.
3. Connect the other end to an Ethernet 10/100/1000 BaseT LAN.
The Brocade DCX 8510-8 can be accessed through a remote connection using the command line
via Telnet or any of the management tools, such as Web Tools or Brocade Network Advisor.
4. To complete any additional Brocade DCX 8510-8 configuration procedures through a Telnet
session, log in to the Brocade DCX 8510-8 by Telnet, using the admin login. The default password
is password.
Customizing a switch name
The switch name of the Brocade DCX 8510-8 can be up to 30 characters long using Fabric OS
release 7.0.0 or later; can include letters, numbers, hyphens, and underscore characters; and must
begin with a letter.
NOTE
Changing the name causes a domain address format RSCN to be issued.
1. Enter switchName followed by the new name in double quotes.
The chassis name of the Brocade DCX 8510-8 can be up to 15 characters long; can include letters,
numbers, hyphens, and underscore characters; and must begin with a letter.
1. Enter chassisName followed by the new name in double quotes.
Each switch in the fabric must have a unique domain ID. The domain ID can be manually set through
the configure command or can be automatically set. The default domain ID for the Brocade DCX
8510-8 is 1. Use the fabricShow command to view the already assigned domain IDs.
1. Enter switchDisable to disable the Brocade DCX 8510-8.
5. Complete the remaining prompts or press Ctrl+D to accept the settings and exit.
6. Enter switchEnable to re-enable the Brocade DCX 8510-8.
Setting the date and time
The date and time settings are used for logging events. Switch operation does not depend on the date
and time; a switch with an incorrect date and time value still functions properly. However, because the
date and time are used for logging, error detection, and troubleshooting, they should be set correctly.
Setting the date
Setting the date and time
To set the date, follow these steps.
1. If necessary, log on to the Brocade DCX 8510-8 by Telnet, using the admin account.
The default password is password.
2. Enter the date command, using the following syntax:
date "mmddHHMMyy"
The values are:
• mm is the month; valid values are 01 through 12.
• dd is the date; valid values are 01 through 31.
• HH is the hour; valid values are 00 through 23.
• MM is minutes; valid values are 00 through 59.
• yy is the year; valid values are 00 through 99 (values greater than 69 are interpreted as 1970
through 1999, and values less than 70 are interpreted as 2000 through 2069).
switch:admin> date
Fri Sep 28 17:01:48 UTC 2010
switch:admin> date "0927123010"
Thu Sep 27 12:30:00 UTC 2010
switch:admin>
Setting the time zone
You must perform the procedure on all chassis for which the time zone must be set. However, you only
need to set the time zone once on each switch, because the value is written to nonvolatile memory.
Use one of the two following procedures to set the time zone.
The following procedure describes how to set the current time zone using timezone_fmt mode to
Central Standard time.
1. Log in to the switch using the default password, which is password.
The following procedure describes how to set the current time zone using
interactive mode to Pacific Standard Time.
1. Enter the tsTimeZone command as follows:
2. Enter the appropriate number or Ctrl+D to quit.
3. At the prompt, select a country location.
4. At the prompt, enter the appropriate number to specify the time zone region
Use timezone_fmt to set the time zone by Country/City or by time zone ID, such as PST.
The following example shows how to change the time zone to US/Central.
switch:admin> tstimezone
Time Zone : US/Pacific
switch:admin> tstimezone US/Central
switch:admin> tstimezone
Time Zone : US/Central
switch:admin> tstimezone --interactive
You are prompted to select a general location.
Please identify a location so that time zone rules can be set correctly.
or Ctrl+D to quit.
Synchronizing local time
To synchronize the local time of the principal or primary switch with that of an external NTP server,
follow these steps.
1. If necessary, log on to the switch by Telnet, using the admin account.
2. Enter the tsClockServer command:
switch:admin> tsclockserver
"<ntp1;ntp2>"
In this syntax, ntp1 is the IP address or DNS name of the first NTP server, which the switch must be
able to access. The variable ntp2 is the second NTP server and is optional. The operand
"<ntp1;ntp2>" is optional; by default, this value is LOCL, which uses the local clock of the principal
or primary switch as the clock server.
The tsClockServer command accepts multiple server addresses in IPv4, IPv6, or DNS name
formats. When multiple NTP server addresses are passed, tsClockServer sets the first obtainable
address as the active NTP server. The rest will be stored as backup servers that can take over if the
active NTP server fails. The principal or primary FCS switch synchronizes its time with the NTP
server every 64 seconds.
The following example shows how to set up more than one NTP server using a DNS name:
switch:admin> tsclockserver "10.32.170.1;10.32.170.2;ntp.localdomain.net"
Updating Clock Server configuration...done.
Updated with the NTP servers
Changes to the clock server value on the principal or primary FCS switch are
propagated to all switches in the fabric
Before connecting the Brocade DCX 8510-8 to the fabric, verify that the WWN-based persistent port
identifier (PID) feature on the Brocade DCX 8510-8 matches the other switches in the fabric. This
parameter must be identical for all switches in the fabric and is set using the configure command as
shown in the following example:
switch:admin>configure
Configure...
Fabric parameters (yes, y, no, n): [no] y
Domain: (1..239) [1]
Enable a 256 Area Limit
(0 = No,
1 = Zero Based Area Assignment,
2 = Port Based Area Assignment): (0..2) [0] 1
WWN Based persistent PID (yes, y, no, n): [no] yes
<command output truncated>
You can check the PID setting using the configshow command as in the following example. You can
use the | grep -i pid qualifier to pinpoint the PID information.
The 1 indicates that the WWN-based persistent PID feature is enabled. The default value is 0 for
disabled.
Verifying the PID mode
Determining installed software licenses
Depending on the vendor agreement, certain licenses are factory installed on the Brocade DCX 8510-8.
To determine which licenses are enabled, use the licenseShow command.
In this example, the license key is AAbbccDDeeFFeeGG. Keep a copy of the license key for reference.
The 64-bit chassis ID is required to obtain and activate licenses for the Brocade DCX 8510-8. The
chassis ID is available through the licenseIdShow command. The licenseShow and licenseIdShow
commands must be entered on the active CP blade. Refer to the Fabric OS Administrator's Guide for
more information.
Installing transceivers and attaching cables
The following two sets of steps cover the installation of transceivers and cables for most SFPs and for
QSFPs.
Complete the following steps to install SFP-type optical transceivers.
NOTE
mSFP transceivers are compatible only with the FC8-64 port blade. While they will fit in other blades,
this configuration is unsupported and will generate an error.
1. Add the optical transceivers and cables to the Fibre Channel ports.
The ports are color-coded to indicate which can be used in the same port group for trunking
(trunking port groups can be up to 8 ports). The ports and cables used in trunking groups must meet
specific requirements. Refer to the Fabric OS Administrator's Guide.
2. Position one of the optical transceivers so that the key is oriented correctly to the port. Insert the
transceiver into the port until it is firmly seated and the latching mechanism clicks.
Transceivers are keyed so that they can only be inserted with the correct orientation. If a transceiver
does not slide in easily, ensure that it is correctly oriented.
3. Position a cable so that the key (the ridge on one side of the cable connector) is aligned with the
slot in the transceiver. Insert the cable into the transceiver until the latching mechanism clicks.
Cables are keyed so that they can be inserted in only one way. If a cable does not slide in easily,
ensure that it is correctly oriented.
4. Repeat steps 1 through 3 for the remaining ports.
5. Organize the cables. Refer to Managing cables on page 44.
6. Verify the Brocade DCX 8510-8 and port status using the switchShow command.
7. Verify fabric connectivity using the fabricShow command.
Qualified transceivers for the FC16-64 port blade and the core blades
The following table shows the qualified transceivers for the FC16-64 port blade and the core blades.
Qualified transceivers for FC16-64 port blade and the core bladesTABLE 3
Brocade part
number
57-1000294-01
57-1000267-01
57-0000090-01
NOTE
The QSFP transceivers supported on FC16-64 port blade are not interchangeable with QSFP
transceivers supported on the core blades.
Follow these steps to install the QSFPs and cables in the FC16-64 port blades and the 16-Gbps core
blades. In the core blades, these transceivers and cables are used to form the inter-chassis links (ICLs)
with neighboring DCX 8510 Backbones. The transceivers should be installed in the blades before
connecting the cables. Because each QSFP contains four 16-Gbps ports, be aware that any problems
with one port could affect all four ports in the quad if the QSFP must be replaced.
NOTE
Even though the installation and removal procedures are the same for QSFP ports in FC16-64 port
blades and the core blades, the physical QSFP transceivers designed for FC16-64 are not compatible
with the QSFP transceivers designed for the core blades. They are not interchangeable.
1. Position one of the QSFP transceivers so that the key is oriented correctly to the port. Insert the
transceiver into the port until it is firmly seated.
Transceivers are keyed so that they can only be inserted with the correct orientation. If a transceiver
does not slide in easily, ensure that it is correctly oriented.
When the transceiver is correctly seated, the status LED will flash amber several times and then turn
solid amber.
2. Remove the protective cap from the special QSFP cable and insert it into the transceiver until it is
firmly seated.
The cables are also keyed to fit into the transceivers correctly.
When the cable is correctly seated, the status LED will change from amber to green.
Repeat steps 1 and 2 for the remaining QSFP ports.
3. Organize the cables. Refer to Cable management on page 29
4. Verify the Brocade DCX 8510-8 and connector and port status using the switchShow -qsfp
command.
The following example is from a DCX 8510-4 with a core blade installed in slot 3. Some details for the
DCX 8510-8 will be different, but the reported information for the QSFPs will be similar.
Note that the State reported for an unconnected QSFP (shown QSFP 0 and Ports 0-3 in the
example) is No_SigDet. This is different from the State of No_Synch that is reported for regular SFPs
that are unconnected.
QSFP 7 (ports 3/28-3/31, Index 748-751) in the following example shows the results for a connected
QSFP.
switch:FID128:admin> switchshow -qsfp
switchName: switch name
switchType: 121.3
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 75
switchId: fffc4b
switchWwn: 10:00:00:05:1e:4f:eb:00
zoning: ON (zoning name
)
switchBeacon: OFF
FC Router: OFF
Allow XISL Use: OFF
LS Attributes: [FID: 128, Base Switch: No, Default Switch: Yes, Address Mode 0]
Index Slot Port QSFP Address Media Speed State Proto
=============================================================
256 3 0 0 ------ id 16G No_SigDet FC
257 3 1 0 ------ id 16G No_SigDet FC
258 3 2 0 ------ id 16G No_SigDet FC
259 3 3 0 ------ id 16G No_SigDet FC
260 3 4 1 ------ -- 16G No_Module FC
261 3 5 1 ------ -- 16G No_Module FC
262 3 6 1 ------ -- 16G No_Module FC
263 3 7 1 ------ -- 16G No_Module FC
264 3 8 2 ------ -- 16G No_Module FC
265 3 9 2 ------ -- 16G No_Module FC
266 3 10 2 ------ -- 16G No_Module FC
267 3 11 2 ------ -- 16G No_Module FC
268 3 12 3 ------ -- 16G No_Module FC
269 3 13 3 ------ -- 16G No_Module FC
270 3 14 3 ------ -- 16G No_Module FC
271 3 15 3 ------ -- 16G No_Module FC
736 3 16 4 ------ -- 16G No_Module FC
737 3 17 4 ------ -- 16G No_Module FC
738 3 18 4 ------ -- 16G No_Module FC
739 3 19 4 ------ -- 16G No_Module FC
740 3 20 5 ------ -- 16G No_Module FC
741 3 21 5 ------ -- 16G No_Module FC
742 3 22 5 ------ -- 16G No_Module FC
743 3 23 5 ------ -- 16G No_Module FC
744 3 24 6 ------ -- 16G No_Module FC
745 3 25 6 ------ -- 16G No_Module FC
746 3 26 6 ------ -- 16G No_Module FC
747 3 27 6 ------ -- 16G No_Module FC
748 3 28 7 ------ id 16G Online FC E-Port 10:00:00:05:1e:
39:e4:5a trunkmaster name
(Trunk master)
749 3 29 7 ------ id 16G Online FC E-Port 10:00:00:05:1e:
39:e4:5a trunkmaster name
(Trunk master)
750 3 30 7 ------ id 16G Online FC E-Port 10:00:00:05:1e:
39:e4:5a trunkmaster name
(Trunk master)
751 3 31 7 ------ id 16G Online FC E-Port 10:00:00:05:1e:
39:e4:5a trunkmaster name
(Trunk master)
Managing cables
Cables can be organized and managed in a variety of ways, for example, using cable channels on the
port sides of the cabinet or patch panels to minimize cable management. On the Brocade DCX 8510-8
the cable management comb is located below the blades on the port side.
Following is a list of recommendations:
• Leave at least 1 m (3.28 ft) of slack for each port cable. This provides room to remove and replace
the Brocade DCX 8510-8, allows for inadvertent movement of the rack, and helps prevent the
cables from being bent to less than the minimum bend radius.
• The minimum bend radius should be no smaller than ten times the cable radius. The minimum
radius to which a 50 micron cable can be bent under full tensile load is 5.1 cm (2 in.). For a cable
under no tensile load, that minimum is 3.0 cm (1.2 in.).
• If ISL Trunking is in use, group the cables by trunking group. The ports are color-coded to indicate
which ports can be used in the same ISL Trunking group: eight ports marked with solid black ovals
alternate with eight ports marked with oval outlines.
• Generally, Velcro ® type cable restraints are recommended to avoid creating sharp bends in the
cables. Do not use tie wraps with optical cables because they are easily overtightened and can
damage the optic fibers.
• For easier maintenance, label the fiber optic cables and record the devices to which they are
connected.
• Do not route cables in front of the air exhaust vents.
• Route the cables to the bottom of the Brocade DCX 8510-8 through the cable management comb.
• Keep LEDs visible by routing port cables and other cables away from the LEDs.
Verifying correct operation and backing up the configuration
NOTE
Refer to "Cabling Best Practices" (available at http://www.brocade.com ) for cable management
guidelines.
For the procedure to install the ICL cables, refer to Inter-chassis link (ICL) cable removal and
replacement on page 106
Verifying correct operation and backing up the configuration
To verify correct operation and back up the Brocade DCX 8510-8 configuration, follow these steps. For
information about LED patterns, refer to Determining the status of a port or application blade on page
52.
Complete the following steps to back up the configuration for the Brocade DCX 8510-8.
1. Check the LEDs to verify that all components are functional.
2. If necessary, log in to the switch by Telnet, using the admin account.
3. Verify the correct operation of the Brocade DCX 8510-8 by entering the switchShow command from
the workstation. This command provides information about switch and port status.
4. Verify the correct operation of the Brocade DCX 8510-8 in the fabric by entering the fabricShow
command from the workstation. This command provides general information about the fabric.
5. To back up the configuration, run the following two steps:
a)Enter the configupload -vf command. This command uploads the Brocade DCX 8510-8
virtual fabric data.
b)Enter the configupload command. This command uploads the Brocade DCX 8510-8
configuration.
6. You can run the following commands to see additional configuration information that you can copy to
a file to save:
• configShow
• ipaddrShow
• licenseShow
• switchShow
Alternatively, you can save the configuration file to a Brocade USB device by using the usbstorage
command.
NOTE
Passwords are not saved in the configuration file, and are not uploaded during a configuration
upload.
NOTE
It is recommended that the configuration be backed up on a regular basis to ensure that a complete
configuration is available for downloading to a replacement Brocade DCX 8510-8.
Perform the following steps to power off the Brocade DCX 8510-8.
1. Shut down the Brocade DCX 8510-8 using the sysShutdown command.
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
HA is disabled
Stopping blade 1
Shutting down the blade....
Stopping blade 2
Shutting down the blade....
Stopping blade 8
Shutting down the blade....
Broadcast message from root (pts/1) Tue Aug 23 14:23:06 2010...
The system is going down for system halt NOW !!
2. Power off the chassis by flipping the AC power switches on the power supplies to O (LEDs inside
AC power switches should turn off). To maintain the ground connections, leave power cords
connected to the power supplies and to the electrical outlets.
● Determining the status of a port or application blade......................................................52
● Determining the status of a control processor blade (CP8)............................................ 63
● Determining the status of a core switch blade (CR16-8).................................................65
● Determining the status of a power supply....................................................................... 67
● Determining the status of a blower assembly................................................................. 68
● Determining the status of a WWN card...........................................................................70
Monitoring overview
The Brocade DCX 8510-8 is engineered for reliability and requires no routine operational steps or
maintenance. This chapter provides information about determining the status of each component using
LEDs and CLI commands. Refer to theWeb Tools Administrator's Guide and the Fabric OSAdministrator's Guide for additional information.
There are two commands that can be especially helpful in monitoring the health of the Brocade DCX
8510-8. These commands are switchShow and chassisShow.
Note in the switchShow command the new switchType for the Brocade DCX 8510-8 as well as the 16Gbps speed identification for capable ports. The output has been truncated to reduce information
duplication.
DCX_8510_8:admin> switchshow
switchName: DCX_8510_8
switchType: 120.3
switchState: Online
switchMode: Native
switchRole: Subordinate
switchDomain: 120
switchId: fffc78
switchWwn: 10:00:00:05:1e:d2:64:00
zoning: ON (BB)
switchBeacon: OFF
FC Router: ON
FC Router BB Fabric ID: 10
Address Mode: 0
Index Slot Port Address Media Speed State Proto
=======================================================
0 1 0 780000 id N8 No_Light FC Disabled (Switch not ready for
EX_Ports)
1 1 1 780100 id N8 No_Light FC Disabled (Switch not ready for
EX_Ports)
2 1 2 780200 -- N8 No_Module FC Disabled (Switch not ready for
EX_Ports)
3 1 3 780300 -- N8 No_Module FC Disabled (Switch not ready for
EX_Ports)
4 1 4 780400 id N8 No_Light FC Disabled (Switch not ready for
EX_Ports)
5 1 5 780500 id N8 No_Light FC Disabled (Switch not ready for
EX_Ports)
6 1 6 780600 id N8 No_Light FC
7 1 7 780700 id 4G No_Light FC
8 1 8 780800 -- N8 No_Module FC
9 1 9 780900 -- N8 No_Module FC
10 1 10 780a00 -- N8 No_Module FC
11 1 11 780b00 -- N8 No_Module FC
398 5 14 ------ id 16G No_SigDet FC
399 5 15 ------ id 16G No_SigDet FC
400 5 16 ------ id 16G No_SigDet FC
401 5 17 ------ id 16G No_SigDet FC
402 5 18 ------ id 16G No_SigDet FC
403 5 19 ------ id 16G No_SigDet FC
404 5 20 ------ id 16G No_SigDet FC
405 5 21 ------ id 16G No_SigDet FC
406 5 22 ------ id 16G No_SigDet FC
407 5 23 ------ id 16G No_SigDet FC
408 5 24 ------ id 16G No_SigDet FC
409 5 25 ------ id 16G No_SigDet FC
410 5 26 ------ id 16G No_SigDet FC
411 5 27 ------ id 16G No_SigDet FC
412 5 28 ------ id 16G No_SigDet FC
413 5 29 ------ id 16G No_SigDet FC
414 5 30 ------ id 16G No_SigDet FC
415 5 31 ------ id 16G No_SigDet FC
1152 5 32 ------ -- 16G No_Module FC
1153 5 33 ------ -- 16G No_Module FC
1154 5 34 ------ -- 16G No_Module FC
1155 5 35 ------ -- 16G No_Module FC
1156 5 36 ------ -- 16G No_Module FC
1157 5 37 ------ -- 16G No_Module FC
1158 5 38 ------ -- 16G No_Module FC
1159 5 39 ------ -- 16G No_Module FC
1160 5 40 ------ -- 16G No_Module FC
1161 5 41 ------ -- 16G No_Module FC
1162 5 42 ------ -- 16G No_Module FC
1163 5 43 ------ -- 16G No_Module FC
1164 5 44 ------ -- 16G No_Module FC
1165 5 45 ------ -- 16G No_Module FC
1166 5 46 ------ -- 16G No_Module FC
1167 5 47 ------ -- 16G No_Module FC
1168 5 48 ------ -- 16G No_Module FC
1169 5 49 ------ -- 16G No_Module FC
1170 5 50 ------ -- 16G No_Module FC
1171 5 51 ------ -- 16G No_Module FC
1172 5 52 ------ -- 16G No_Module FC
1173 5 53 ------ -- 16G No_Module FC
1174 5 54 ------ -- 16G No_Module FC
<output truncated>
DCX_8510_8:admin>
Note in the chassisShow command the Chassis Family designation for the Brocade DCX 8510-8
along with specific information about every field-replaceable unit in the chassis.
DCX_8510_8:admin> chassisshow
Chassis Family: DCX8510-8
Chassis Backplane Revision: 0
AP BLADE Slot: 1
Header Version: 2
Power Consume Factor: -250
Factory Part Num: 60-1001157-21
Factory Serial Num: ATM0427F01F
Manufacture: Day: 12 Month: 7 Year: 2010
Update: Day: 27 Month: 3 Year: 2011
Time Alive: 45 days
Time Awake: 0 days
SW BLADE Slot: 3
Header Version: 2
Power Consume Factor: -130
Factory Part Num: 60-0000071-07
Factory Serial Num: BAH0344E01G
Manufacture: Day: 2 Month: 11 Year: 2009
Update: Day: 7 Month: 2 Year: 2011
Time Alive: 280 days
Time Awake: 0 days
SW BLADE Slot: 4
Header Version: 2
Power Consume Factor: -160
Power Usage (Watts): -100
Factory Part Num: 60-1002144-02
Factory Serial Num: BQB0349F00G
Manufacture: Day: 10 Month: 12 Year: 2010
Update: Day: 28 Month: 3 Year: 2011
Determining the status of a port or application blade
FAN Unit: 1
Header Version: 2
Power Consume Factor: -126
Factory Part Num: 60-1000384-09
Factory Serial Num: AGB0652E0HA
Manufacture: Day: 29 Month: 12 Year: 2009
Update: Day: 28 Month: 3 Year: 2011
Time Alive: 319 days
Time Awake: 0 days
FAN Unit: 2
Header Version: 2
Power Consume Factor: -126
Factory Part Num: 60-1000384-09
Factory Serial Num: AGB0652E0H9
Manufacture: Day: 29 Month: 12 Year: 2009
Update: Day: 28 Month: 3 Year: 2011
Time Alive: 319 days
Time Awake: 0 days
FAN Unit: 3
Header Version: 2
Power Consume Factor: -126
Factory Part Num: 60-1000384-09
Factory Serial Num: AGB0652E0H8
Manufacture: Day: 29 Month: 12 Year: 2009
Update: Day: 28 Month: 3 Year: 2011
Time Alive: 319 days
Time Awake: 0 days
WWN Unit: 1
Header Version: 2
Power Consume Factor: -1
Factory Part Num: 60-1000491-05
Factory Serial Num: AFX0602F001
Manufacture: Day: 29 Month: 12 Year: 2009
Update: Day: 28 Month: 3 Year: 2011
Time Alive: 319 days
Time Awake: 0 days
ID: BRD0000CA
Part Num: SLKWRM0000DCX
WWN Unit: 2
Header Version: 2
Power Consume Factor: -1
Factory Part Num: 60-1000491-05
Factory Serial Num: AJX0446E009
Manufacture: Day: 29 Month: 12 Year: 2009
Update: Day: 28 Month: 3 Year: 2011
Time Alive: 319 days
Time Awake: 0 days
Chassis Factory Serial Num: AFY0601F007
DCX_8510_8:admin>
Determining the status of a port or application blade
Use the following procedure to determine the status of a port or application blade.
1. Check the LEDs on the blade. Refer to Blade illustrations on page 52.
The LED patterns may temporarily change during POST and other diagnostic tests. For information
about how to interpret the LED patterns, refer to the table following the blade descriptions.
2. Check the blade status by entering slotShow.
Blade illustrations
NOTE
The FC8-64 port blade requires narrower OM-3 LC cables offered by major manufacturers like
Corning, Molex, and Amphenol.
Determining the status of a control processor blade (CP8)
Port and application blade LED descriptions (Continued)TABLE 4
LED purposeColorStatusRecommended action
GbE Port Status (FX8-24)
- both 1 GbE and 10 GbE
ports
Steady amberPort is receiving light or
Slow-flashing amber (on 2
seconds, then off 2
seconds)
Fast-flashing amber (on
1/2 second, then off 1/2
second)
Alternating green/amberPort is bypassed.Reset the port from the
No light (LED is off)Port has no incoming
Steady greenPort is online but has no
signal carrier, but it is not
online yet.
Port is disabled due to
diagnostic tests or
portDisable or
portCfgPersistentEnable
command.
Transceiver or port is
faulty.
power, or there is no light
or signal carrier detected.
traffic.
Reset the port from the
workstation using the
portEnable or
portCfgPersistentEnable
command.
Reset the port from the
workstation using the
portEnable or
portCfgPersistentEnable
command.
Change the transceiver or
reset the switch from the
workstation.
workstation using the
portEnable or
portCfgPersistentEnable
command.
Verify that the power LED
is on, check the
transceiver and cable.
No action required.
Slow-flashing green (on 1
second, then off 1 second)
Flickering greenPort is online, with traffic
Fast-flashing amber (on
1/4 second, then off 1/4
second)
Beacon. Used to identify
specific ports.
flowing through port.
Transceiver or port is
faulty.
No action required.
No action required.
Change the transceiver or
reset the switch from the
workstation.
Determining the status of a control processor blade (CP8)
Complete the following steps to determine the status of a control processor blade (CP8)
1. Check the LED indicators on the CP blade. The LED patterns may temporarily change during POST
and other diagnostic tests. For information about how to interpret the LED patterns, refer to the
following table.
2. Check the port blade status by entering slotShow and haShow.
1. Check the LED indicators on the core switch blade. The LED patterns may temporarily change
during POST and other diagnostic tests. For information about how to interpret the LED patterns,
refer to the following table.
2. Check the core switch blade status by entering slotShow and haShow.
FIGURE 15 Core switch blade (CR16-8)
1. Power LED
2. Status LED
3. QSFP port map and trunking diagram
4. QSFP connectors
5. QSFP connectors
The following table describes the core switch blade LED patterns and the recommended actions for
those patterns.
1. Check the LED indicator on the power supply. The LED patterns may temporarily change during
POST and other diagnostic tests; for information about how to interpret the LED patterns, refer to
the following table. The Brocade DCX 8510-8 has four power supplies. Be sure to check each
module.
2. Check the power supply status by entering psShow.
The power supply status displays OK, Absent, or Faulty. If a power supply displays absent or faulty,
contact the Brocade DCX 8510-8 supplier to order replacement parts. Both physically absent or
faulty could also be the result of the power supply not being properly seated or being turned off.
FIGURE 16 Power supply
1. Power LED
The following table describes the power supply LED patterns and the recommended actions for
those patterns.
Power supply LED descriptions TABLE 7
LED purpose ColorStatusRecommended action
PowerNo light (LED is
off)
Steady greenPower supply has incoming
Flashing greenPower supply is about to fail.Replace the power supply.
Power supply does not have
incoming power and is not
providing power to the Brocade
DCX 8510-8.
power and is providing power to
the Brocade DCX 8510-8.
Determining the status of a blower assembly
Complete the following steps to determine the status of a blower assembly.
1. Check the LED indicators on the blower assembly. The LED patterns may temporarily change
during POST and other diagnostic tests; for information about how to interpret the LED patterns,
refer to following table. The Brocade DCX 8510-8 has three blowers. Be sure to check each
module.
2. Check the blower assembly status using the fanShow command.
The status for each blower assembly displays OK, Absent, or Faulty. The RPM of each fan in the
assembly is also provided. If a blower assembly displays absent or faulty, contact the Brocade DCX
Ensure that the power supply is firmly
seated, the Brocade DCX 8510-8 has
incoming power, both power cables
are connected, and AC power
switches are on.
Blower assembly LED descriptions (Continued)TABLE 8
LED purpose ColorStatusRecommended action
Flashing amber (on 1/2
second, then off 3.5
seconds)
Fast-flashing amber (on
1/2 second, then off 1/2
second)
Fan is disabled.Run the fanEnable command to
Environmental range
exceeded.
Determining the status of a WWN card
Complete the following steps to determine the status of a WWN card.
NOTE
The WWN bezel (logo plate) covers the WWN cards.
1. Enter the chassisShow command to display information about the WWN card. (WWN units
correspond to information specific to the WWN card.) Error messages that may indicate problems
with a WWN card are summarized in the following table.
Messages that may indicate WWN card failure TABLE 9
Type of messageSample error message
enable the fan.
Check for out-of-bounds
environmental condition, resolve any
problems, and reseat the unit. If the
LED continues to flash, replace the
unit.
WWN unit fails its field-replaceable
unit (FRU) header access.
WWN unit fails to power on.
WWN unit is being faulted.
WWN unit is not present or is not
accessible.
Writing to the FRU history log
(hilSetFruHistory) has failed.
<timestamp>, [EM-1004], <sequence-number>,,
CRITICAL, <system-name>, WWN # failed to power
onor<timestamp>, [EM-1043], <sequence-number>,,
WARNING, <system-name>, Can't power <FRU Id> <state
(on or off)>.
0x24c (fabos): Switch: switchname, Critical EMWWN_UNKNOWN, 1, Unknown WWN #2 is being
faultedor<timestamp>, [EM-1003], 40, SLOT 7 | FFDC
| CHASSIS, CRITICAL, Brocade_DCX, WWN 2 has unknown
hardware identifier: FRU faultedor<timestamp>,
[EM-1034], <sequence-number>,, ERROR, <systemname>, WWN # set to faulty, rc=<return code>
0x24c (fabos): Switch: switchname, Error EMWWN_ABSENT, 2, WWN #1 not presentor<timestamp>,
[EM-1036], <sequence-number>,, WARNING, <systemname>, <FRU Id> is not accessible.
0x24c (fabos): Switch: switchname, Error EMHIL_FAIL, 2, HIL Error: hilSetFruHistory failed,
rc=-3 for SLOT 3
2. Check the LED indicators on the WWN bezel and verify that they reflect the actual status of the
components. The WWN bezel covers the WWN cards and allows its LEDs to shine through. The
LEDs on the WWN bezel provide a consolidated view of the port, CP, and CR blade status.
Refer to the following table for a description of the WWN card LED patterns and the recommended
actions for those patterns.
WWN LED patterns for DCX and DCX 8510-8 TABLE 10
LED location/purposeColorStatusRecommended action
Port blade/CP/CR blade
power
Port blade/CP/CR blade
status
NOTE: If a blade slot has a filler panel installed, the corresponding LEDs on the WWN card do not light up.
NOTE: If a status LED on the WWN bezel flashes, the power LED on the WWN bezel also flashes, for
increased visibility.
Steady greenPower is okay.No action required.
Steady amberCard is faulty.Check card.
No light (LED is off)Card is okay.No action required.
The following figure displays the WWN bezel (logo plate). The WWN cards are under the bezel.
FIGURE 18 WWN bezel (logo plate) with LEDs for DCX and DCX 8510-8
● Chassis door removal and replacement..........................................................................74
● Cable management comb removal and replacement..................................................... 75
● Port, application, and encryption blade removal and replacement................................. 76
● Blade filler panel removal and replacement.................................................................... 80
● Control processor blade (CP8) removal and replacement.............................................. 82
● Core switch blade (CR16-8) removal and replacement.................................................. 90
● Power supply removal and replacement......................................................................... 93
● Blower assembly removal and replacement................................................................... 96
● WWN card removal and replacement............................................................................. 97
● Transceiver removal and replacement..........................................................................101
● Inter-chassis link (ICL) cable removal and replacement............................................... 106
● Brocade DCX 8510-8 chassis removal and replacement............................................. 111
Introduction
NOTE
Read the safety notices before servicing Caution and Danger Notices.
The field-replaceable units (FRUs) in the Brocade DCX 8510-8 can be removed and replaced without
special tools. The Brocade DCX 8510-8 can continue operating during many of the FRU replacements if
the conditions specified in the procedures are followed.
The following sections contain FRU removal and replacement procedures (RRPs).
ESD precautions
The Brocade DCX 8510-8 contains ESD-sensitive FRUs. When working with any Brocade DCX 8510-8
FRU, use correct electrostatic discharge (ESD) procedures.
• Wear a wrist grounding strap connected to chassis ground (if the Brocade DCX 8510-8 is plugged in)
or a bench ground.
• Store ESD-sensitive components in antistatic packaging.
DANGER
For safety reasons, the ESD wrist strap should contain a series 1 megaohm resistor.
CAUTION
Static electricity can damage the chassis and other electronic devices. To avoid damage, keep
static-sensitive devices in their static-protective packages until you are ready to install them.
FIGURE 20 Removal and replacement of the cable management comb
Replacing a cable management comb
Complete the following steps to replace the cable management comb.
1. Position and tighten the four (4) screws to secure the cable management comb to the chassis.
2. Arrange the cables along the cable management comb.
3. Replace the chassis door.
Port, application, and encryption blade removal and replacement
This section describes how to remove and replace port, application, and encryption blades. It does not
cover the core (CR) blades or the control processor (CP) blades.
If you do not install a module or a power supply in a slot, you must keep the slot filler panel in
place. If you run the chassis with an uncovered slot, the system will overheat.
Slots are numbered from 1 through 12, from left to right when facing the port side of the Brocade DCX
8510-8. Port, application, and encryption blades can be installed in slots 1 through 4 and 9 through 12.
This section is applicable for all the following port, application, and encryption blades supported on the
DCX 8510 chassis:
BladeDCXDCX-4SDCX 8510-4DCX 8510-8
FC8-32E port bladeNoNoSupportedSupported
FC8-48E port bladeNoNoSupportedSupported
FC8-64 port bladeSupportedSupportedSupportedSupported
Not supported in the same chassis with FC8-48E, FC8-64, FC16-48, FC16-64,
FS8-18, or FX8-24 blades.
NOTE
For complete list of limitations on the FCOE10-24 application blade, refer to the Fabric OS Release
Notes.
Time and items required
The replacement procedure for each blade takes less than 10 minutes. Removing and restoring
transceivers and cables may take longer depending on how many must be changed. The following
items are required for the blade and filler panel replacement:
• Small form-factor pluggable (SFP+, mSFP, or QSFP) transceivers (as needed)
• Optical and copper cables (as needed)
NOTE
For information about the transceivers that are qualified for the Brocade chassis, go to http://
www.brocade.com/downloads/documents/matrices/sfp-matrix-mx.pdf.
Removing a blade
Complete the following steps to remove a blade.
Follow electrostatic discharge (ESD) precautions when removing a blade. Wear a wrist grounding
strap connected to chassis ground (if the Brocade DCX 8510-8 is plugged in) or a bench ground.
DANGER
For safety reasons, the ESD wrist strap should contain a series 1 megaohm resistor.
NOTE
Before removing any cables from a blade, note the cable order (identify each cable by its physical
port). It is a good practice to keep a table of cable to port mapping.
NOTE
If multiple blades are being replaced, replace one blade at a time.
This procedure is applicable for all the following port, application, and encryption blades supported on
the Brocade DCX 8510-8.
1. Remove the chassis door.
2. Check the power LED, status LED, and port status LED to identify any possible problems. A failed
port or application blade can be identified by inspecting the LEDs on the front panel of each blade.
3. Establish a Telnet or console session.
Before replacing a blade, establish a Telnet or console connection to determine a failure and verify
operation after replacement. Use the switchShow command to view the status of the blades.
4. Check for adequate cable slack. Ensure there is plenty of cable slack to remove a blade without
cable obstruction.
5. Ensure that the part number on the unit being replaced matches the replacement part number. The
chassisShow command displays information about the blades, including part numbers (xx-
xxxxxxx-xx), serial numbers, and additional status.
6. Ensure that traffic is not flowing through the blade (port status LED should be off) prior to
disconnecting cables.
7. Ensure that traffic is not flowing through the blade.
8. Disconnect all cables and transceivers from the blade. For mSFP transceivers (FC8-64 only), it is
recommended that you use the pull tab to remove the transceiver from the blade.
9. Unscrew the two thumbscrews from the ejectors on the blade using the Phillips screwdriver.
Unscrew the top thumbscrew until it pops out. This initiates a hot-swap request.
10.Wait for the power LED to turn off in response to the hot-swap request before removing the blade.
11.Open the ejectors by rotating them toward the center of the blade face. Pull the blade out of the
chassis using the ejectors.
12.If the blade is not being replaced by another blade, install a filler panel.
FIGURE 21 Removal and replacement of the port, application, and encryption blades (FC16-48 port
blade shown)
Replacing a blade
Complete this procedure to replace a blade.
Follow electrostatic discharge (ESD) precautions when replacing a blade. Wear a wrist grounding strap
connected to chassis ground (if the Brocade DCX 8510-8 is plugged in) or a bench ground.
For safety reasons, the ESD wrist strap should contain a series 1 megaohm resistor.
NOTE
An FA4-18i application blade and the Brocade DCX 8510-8 must have the same version of firmware.
To upgrade firmware versions, refer to the Fabric OS Administrator's Guide.
1. Orient the blade so that the ports are at the front of the chassis and the flat side of the blade is on
the left.
2. Open the ejectors by rotating them toward the center of the blade face, align the flat side of the
blade inside the top and bottom rail guides in the slot, and slide the blade into the slot until it is
firmly seated.
3. Close the ejectors by rotating them away from the center of the blade. The levering action of the
ejectors seats the blade in the slot.
4. Tighten the thumbscrews using the Phillips screwdriver.
5. Verify that the power LED on the port blade is displaying a steady green light. If it does not turn on,
ensure that the blade is firmly seated.
6. Verify the Status LED on the blade. The status LED will show amber until POST completes for the
blade and then display green. If the LED remains amber, the board may not be properly seated in
the backplane or the board may be faulty.
7. Install the transceivers and cables in the blade. For mSFP (FC8-64 port blade only) and QSFP
(FC16-64 port blade only) transceivers, it is recommended that you install the cables in the
transceivers before installing the transceivers in the blade.
8. Group and route the cables through the cable management comb.
9. Replace the chassis door.
Blade filler panel removal and replacement
This section describes how to remove and replace blade filler panels.
NOTE
Some filler panels have two thumbscrews and some have only one. Be sure to unscrew or tighten both
if you are using the two-screw version.
Removing a filler panel
Complete the following steps to remove a filler panel from the chassis.
CAUTION
If you do not install a module or a power supply in a slot, you must keep the slot filler panel in
place. If you run the chassis with an uncovered slot, the system will overheat.
1. Remove the chassis door.
2. Unscrew the thumbscrews on the panel using the Phillips screwdriver.
3. Using the tabs, pull the filler panel out of the chassis.
Control processor blade (CP8) removal and replacement
Control processor blade (CP8) removal and replacement
This document describes how to remove and replace a control processor (CP8) blade. Each chassis
has two CP8 blades. In the DCX 8510-8, they are located in slots 6 and 7.
NOTE
The CP8 blade is compatible only with the Brocade DCX Backbones (including the DCX 8510
Backbones).
NOTE
The Brocade firmware upgrade policy for CP8 blades specifies testing for the current Fabric OS
release and one version earlier. It is possible to upgrade by more than one version, but it is a very
specific and detailed process. Read the directions under Downloading firmware from an FTP server on
page 87 or Downloading firmware from a USB device on page 88 carefully.
NOTE
If the new CP blade does not have the same firmware as the active CP blade, the new blade must be
upgraded to the same firmware version. You can determine the firmware version on the replacement
blade and perform a firmware upgrade if necessary after inserting the blade in the chassis, but you
must disable high availability (HA) before inserting the new blade. If the new CP blade is severely
down-level, a very specific procedure must be followed to bring the blade up to the correct firmware
version.
Time and items required
The replacement procedure for the CP blade takes approximately 30 minutes. The following items are
required for the CP blade replacement:
• Electrostatic discharge (ESD) grounding strap
• Workstation computer
• Serial cable
• IP address of an FTP server for backing up the Brocade DCX 8510-8 configuration
• #2 Phillips screwdriver
• Replacement Brocade DCX 8510-8 control processor blade (CP8)
If you are upgrading through multiple versions of the Fabric OS, consult the Table 11 on page 87
table to see which intermediate versions of the Fabric OS you might need. Plan carefully and for extra
time if this is your situation.
Faulty CP blade indicators
Confirm that you need to replace the CP blade. The following events may indicate that a CP blade is
faulty:
• The status LED on the CP blade is lit steady amber, or the power LED is not lit.
• The CP blade does not respond to Telnet commands, or the serial console is not available.
• The slotShow command does not show that the CP blade is enabled.
• The clock is inaccurate, or the CP blade does not boot up or shut down normally.
• Any of the following messages display in the error log:
‐"Slot unknown" message relating to a CP slot
‐CP blade errors or I2C timeouts
‐FRU: FRU_FAULTY messages for a CP blade
‐Configuration loader messages or "Sys PCI config" messages
‐Generic system driver messages ("FABSYS")
‐Platform system driver messages ("Platform")
‐EM messages that indicate a problem with a CP blade
‐Function fail messages for the CP master
For more information about error messages, refer to the Fabric OS Message Reference.
Recording critical Brocade DCX 8510-8 information
Back up the backbone configuration before you replace a CP blade. Refer to the Fabric OS
Administrator's Guide for backup information.
NOTE
The following instructions reference specific slot numbers. These numbers will be different between the
DCX 8510-8/DCX and the DCX 8510-4/DCX-4S chassis.
1. Connect to the chassis and log in as admin, using a serial console connection.
2. Enter haShow to determine which CP blade is active. The following example is from a DCX chassis.
DCX_124:admin> haShow
Local CP (Slot 7, CP1) : Active
Remote CP (Slot 6, CP0) : Standby, Healthy
HA Enabled, Heartbeat Up, HA State Synchronized
3. Enter all remaining commands from the serial console for the active CP blade, unless otherwise
indicated. For more information about commands, refer to the Fabric OS Command Reference.
4. If the active CP blade is faulted, automatic fail over to the standby CP blade should have occurred.
Confirm that the standby CP blade is active and power off the faulted CP blade, log in to the standby
CP blade, and skip to step 7.
If automatic failover has not occurred, manually failover the faulty blade by moving the slider to the
off position (down in the DCX 8510-8). Then power off the faulted blade, log in to the standby CP
blade, and skip to step 7.
5. If both CP blades are healthy and you want to replace the standby CP blade, log in to the active CP
blade and skip to step 7.
6. If both CP blades are healthy and you want to replace the active CP blade, log in to the active CP
blade and run the following steps:
a)Run the haFailover command to make the standby CP blade the active blade. The currently
active CP blade becomes the standby blade. Wait until the status LED on the currently
active CP blade is no longer lit.
b)Confirm the completion of the failover by running the haShow command.
c)Log in to the new active CP blade.
7. Run firmwareShow to note the firmware version of the active CP blade.
The following example shows the results of the firmwareshow command when the firmware
versions on the two CP blades are not the same. Note the warning message at the end of the
output.
DCX_120:root> firmwareshow
Slot Name Appl Primary/Secondary Versions Status
------------------------------------------------------------------------- 6 CP0 FOS v6.4.0a STANDBY
v6.4.0a
7 CP1 FOS v7.0.0 ACTIVE *
v7.0.0
WARNING: The local CP and remote CP have different versions
of firmware, please retry firmwaredownload command.
DCX_120:root>
8. Run haDisable from the active CP blade to prevent failover or communication between the CP
blades during the replacement.
9. Use the configUpload command to upload the backbone configuration to a specified FTP server.
Enter information at the prompts.
a)Run the fosconfig --show command to determine if virtual fabrics are enabled. If so, run
the configupload -vf command. This command uploads the Brocade DCX 8510-8 virtual
fabric data.
b)If virtual fabrics are not enabled, run the configupload command. This command uploads
the Brocade DCX 8510-8 configuration.
Removing a control processor blade (CP8)
The chassis continues to operate while a CP blade is being replaced if the redundant CP blade is
active and a failover does not occur. You can prevent failover by entering the haDisable command.
Complete the following steps to remove a CP8 control blade.
1. Remove the chassis door.
2. Log in to the active CP as the admin user. You can use a serial cable or Telnet, Web Tools, or
Fabric Manager. Determine which CP is active using the haShow command or view the active LED
on the front of the CP.
3. If the faulty CP is the active CP, issue the haFailover command. Wait until the failover has
completed. Use the haShow command to verify the CPs are synchronized and the failover is
complete.
Depending on the nature of the CP failure, it is possible that the haFailover command may not
work. Proceed to the next step anyway.
4. Enter the haDisable command. This is required before physically removing and replacing a CP
blade.
5. Power off the blade by sliding the slider switch in the top ejector down to the off position. Do not
eject the blade until the power LED is off and you have completed the next two steps.
6. Disconnect all cables from the faulty (standby) CP.
7. Unscrew the thumbscrew from both ejectors using the Phillips screwdriver.
8. Lever open both ejector handles simultaneously to approximately 45 degrees and pull the CP blade
out of the chassis.
FIGURE 23 Removal and replacement of the control processor blade (CP8)
Replacing a control processor blade (CP8)
NOTE
Read all of the instructions for replacing the CP blade before beginning the procedure. Use the same
version of Fabric OS on both CP blades. Using different versions is not supported and may cause
malfunctioning. If the replacement CP blade has a different version of Fabric OS, bring both blades to
the same firmware version. Once you have installed the replacement CP blade, determine the version
of firmware on the replacement CP blade and upgrade it if necessary.
Complete the following steps to remove a CP8 control blade.
1. Open the ejector handles to approximately 45 degrees. Orient the CP blade so that the handles are
toward you and the flat metal side is on your left.
2. Align the flat metal side of the CP blade inside the lower and upper blade guides in the slot. Slide
the CP blade into the slot until it is firmly seated.
3. Tighten the thumbscrew inside each handle using the Phillips screwdriver.
4. Turn the CP blade on by sliding the ON/OFF switch in the top handle up, to cover the thumbscrew.
5. Verify that the power LED is green. If not, ensure that the CP blade has power and is firmly seated
and that the ejectors are in the locked position.
6. Connect the cables to the new CP blade.
7. Remain logged in to the active CP and continue to Verifying operation of the new CP blade on page
86.
Verifying operation of the new CP blade
To verify that boot and POST are complete on the new CP blade and that the CP blade has achieved
failover redundancy, perform the following steps.
1. Enter slotShow. The command output shows the new CP blade as "enabled."
If the standby CP is unresponsive, you can try unplugging the new CP blade, running haDisable on
the active CP blade, and plugging the new CP blade back in. At that point, you can repeat step 1 to
begin the verification process again.
2. Determine the version by entering firmwareShow. If the serial console on the replacement CP
blade is connected, issue the firmwareShow command there. More information is available through
the console.
NOTE
The DCX 8510-8 requires Fabric OS 7.0.0 or later to be recognized. If the firmware on the
replacement blade is earlier than 7.0.0 it must be brought up to the version on the active CP blade,
which must be at least 7.0.0.
3. If the firmware versions for both CP blades are the same, skip to Completing the replacement on
page 89.
If the firmware version on the replacement blade does not match that on the active CP blade, a
warning message appears with the results of the firmwareshow command. The results of the
firmwareshow command may look similar to the following. Note the warning message at the end of
the output.
The following example is from a DCX 8510-8 chassis.
DCX_xyz:admin> firmwareshow
Slot Name Appl Primary/Secondary Versions Status
----------------------------------------------------------------------- 6 CP0 FOS v7.0.0 ACTIVE
v7.0.0
7 CP1 FOS v6.3.0a STANDBY *
v6.3.0a
* Local CP
WARNING: The local CP and remote CP have different versions
of firmware, please retry firmwaredownload command.
4. You must bring the replacement blade to the same firmware level as the active blade by running the
firmwareDownload -s command directly on the replacement blade to bring it up to the proper level.
The firmwareshow command results show which slots hold the active and standby (replacement)
CP blades.
If you are using an FTP server to download the firmware, skip to Downloading firmware from an
If you are using a USB device to download the firmware, skip to Downloading firmware from a USB
device on page 88. If the firmware on the standby CP blade is more than one level down from the
level on the active CP blade, you must have formatted USB devices for each of the versions you will
need to upgrade.
Steps for upgrading through multiple versions of Fabric OS TABLE 11
Current Fabric OS version Target Fabric OS version Upgrade steps
7.0.07.0.0xUse firmwaredownload -s to upgrade directly to
7.0.0x
Downloading firmware from an FTP server
For this task, refer to Verifying operation of the new CP blade on page 86 for the correct sequence of
upgrading firmware versions to reach your target version.
Complete the following steps to download the firmware from an FTP server.
1. Log in to the standby CP blade as admin. If you need to know the IP address of the standby blade,
run ipaddrshow .
You should remain logged in to the active CP blade in order to monitor it.
2. Run firmwareDownload -s to download the firmware to the standby CP blade. The -s option also
disables the autoreboot, so you will have to manually issue a reboot after the download finishes to
initiate firmwarecommit. Enter all requested information (use default values).
3. When the download process finishes, run firmwareDownloadStatus to verify that the firmware has
been updated.The command displays a running account of the progress of the firmwareDownload
command (if it is still running) until the command has completed. The final message is similar to the
following and will appear with a date and time stamp:
Slot 6 (CP0, active): Firmwaredownload command has completed successfully. Use
firmwareshow to verify the firmware versions.
4. On the standby CP blade (the blade for which you just changed the firmware level), run reboot. The
reboot of the standby CP will initiate a firmwarecommit to the secondary partition and log you out.
DCX_124:admin> reboot
Broadcast message from root (ttyS0) Fri Jun 18 14:49:45 2010...
The system is going down for reboot NOW !!
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal DCX_124:admin> HAMu Heartbeat down, stop
FSS
Unmounting all f##exiting due to signal: 9, pending signals: 0x20000, 0x0
ilesystems.
Please stand by while rebooting the system...
Restarting system.
The system is coming up, please wait...
.
.
.
Fri Jun 18 14:53:13 2010: Doing firmwarecommit now.
Please wait ...
Fri Jun 18 14:55:27 2010: Firmware commit completes successfully.
Validating the filesystem ...
Fri Jun 18 22:36:05 2010: Doing firmwarecommit now.
Please wait ...
Fri Jun 18 22:36:48 2010: Firmware commit completes successfully.
2010/06/18-14:56:50, [SULB-1004], 908, SLOT 7 | CHASSIS, INFO, Brocade_DCX,
Firmwarecommit has completed.
2010/06/18-14:56:50, [SULB-1036], 909, SLOT 7 | CHASSIS, INFO, Brocade_DCX, The
new Version: Fabric OS v6.3.0c
2010/06/18-14:56:50, [SULB-1002], 910, SLOT 7 | CHASSIS, INFO, Brocade_DCX,
Firmwaredownload command has completed successfully.
The time stamp on the co-CPU may not be in sync with the main CPU on the blade. This is not a
cause for concern.
5. Log back in to the standby CP blade and run firmwareDownloadStatus on the standby CP blade
to validate a successful commit. This may take 10 minutes.
6. If you are upgrading through several levels of the Fabric OS, repeat step 2 through step 5 as often
as necessary based on the path outlined in the preceding table. Otherwise, proceed to step 7.
7. Log out of the standby CP blade and log in to the active CP blade.
8. Proceed to Completing the replacement on page 89.
Downloading firmware from a USB device
For this task, refer to Verifying operation of the new CP blade on page 86 for the correct sequence of
upgrading firmware versions to reach your target version.
Complete the following steps to download the firmware from a USB device.
This section assumes that the new firmware has already been copied onto the USB device. The folder
structure on the USB device must be as follows in order to allow the device to be enabled:
• brocade>
‐config
‐firmware
‐firmwareKey
‐support
The firmware folder contains the folder for the specific release you are installing.
1. Insert the USB device into the active CP blade.
2. Attach a serial cable from the PC to the active CP blade.
3. Log in to the active CP blade as admin if you are not still logged in and enter usbStorage -e to
enable the USB device.
4. Remove the serial cable from the active CP blade and attach it to the standby CP blade and log in
as admin.
5. Run firmwareDownload -s to download the firmware to the standby CP blade. The -s option also
disables the autoreboot, so you will have to manually issue a reboot after the download finishes to
initiate firmwarecommit. Enter all requested information (use default values).
6. This does not apply to the DCX 8510 models. When the download process finishes, run
firmwareDownloadStatus to verify that the firmware has been updated. The command displays a
running account of the progress of the firmwareDownload command until the command has
completed. The final message is similar to the following and will appear with a date and time stamp:
Slot 6 (CP0, active): Firmwaredownload command has completed successfully. Use
firmwareshow to verify the firmware versions.
7. Ensure that you are still logged in to the standby CP blade (the blade for which you just changed
the firmware level) and type reboot. The reboot of the standby CP will initiate a firmwarecommit to
the secondary partition and log you out.
DCX_124:admin> reboot
Broadcast message from root (ttyS0) Fri Jun 18 14:49:45 2010...
The system is going down for reboot NOW !!
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal DCX_124:admin> HAMu Heartbeat down, stop
FSS
Unmounting all f##exiting due to signal: 9, pending signals: 0x20000, 0x0
ilesystems.
Please stand by while rebooting the system...
Restarting system.
The system is coming up, please wait...
.
.
.
Fri Jun 18 14:53:13 2010: Doing firmwarecommit now.
Please wait ...
Fri Jun 18 14:55:27 2010: Firmware commit completes successfully.
Validating the filesystem ...
Fri Jun 18 22:36:05 2010: Doing firmwarecommit now.
Please wait ...
Fri Jun 18 22:36:48 2010: Firmware commit completes successfully.
2010/06/18-14:56:50, [SULB-1004], 908, SLOT 7 | CHASSIS, INFO, Brocade_DCX,
Firmwarecommit has completed.
2010/06/18-14:56:50, [SULB-1036], 909, SLOT 7 | CHASSIS, INFO, Brocade_DCX, The
new Version: Fabric OS v6.3.0c
2010/06/18-14:56:50, [SULB-1002], 910, SLOT 7 | CHASSIS, INFO, Brocade_DCX,
Firmwaredownload command has completed successfully.
NOTE
The time stamp on the co-CPU may not be in sync with the main CPU on the blade. This is not a
cause for concern.
8. Log back in to the standby CP blade and enter firmwareDownloadStatus on the standby CP blade
to validate a successful commit. This may take 10 minutes.
9. If you are upgrading through several levels of the Fabric OS, repeat step 5 through step 8 as often as
necessary based on the path outlined in the preceding table. Otherwise, proceed to step 10.
10.Log out of the standby CP blade and log in to the active CP blade.
11.Proceed to Completing the replacement on page 89
Completing the replacement
Complete the following steps to complete the CP8 control blade replacement procedure.
1. Enter haEnable to re-enable HA on the active CP blade.
NOTE
For Fabric OS 7.0.0 and later, haEnable will cause the standby CP blade to reboot. Wait until POST
completes before moving to the next step. POST is complete when the Status LED on the CP blade
returns to a steady green state.
2. Enter haShow and verify that the command output includes "HA Enabled, Heartbeat Up". If it is not
yet enabled, re-enter the command until you have verified that redundancy is achieved.
DCX_124:admin> hashow
Local CP (Slot 7, CP1) : Active
Remote CP (Slot 6, CP0) : Standby, Healthy
HA Enabled, Heartbeat Up, HA State Synchronized
3. Enter firmwareShow to verify that the firmware version has been updated and that the versions are
the same on the two CP blades. The slot numbers will be different for the DCX 8510-4 or DCX-4S.
(not all slot numbers are shown).
DCX_8510:admin> firmwareshow
Slot Name Appl Primary/Secondary Versions Status
Core switch blade (CR16-8) removal and replacement
4. Pack the faulty CP blade in the packaging provided with the new CP blade, and contact the switch
supplier to determine the return procedure.
5. Replace the chassis door.
If you have one or more application blades in the chassis, the Fabric OS automatically detects
mismatches between the active CP firmware and the application blade's firmware and triggers the
auto-leveling process. This auto-leveling process automatically updates the application blade
firmware to match the active CP. At the end of the auto-leveling process, the active CP and the
application blades will run the same version of the firmware.
Core switch blade (CR16-8) removal and replacement
This section describes how to remove and replace a core switch blade (CR16-8). The Brocade DCX
8510-8 has two core switch blades: one in slot 5 and one in slot 8.
Time and items required
The replacement procedure for the core switch blade takes approximately 30 minutes. The following
items are required for the core switch blade replacement:
• Electrostatic discharge (ESD) grounding strap
• #2 Phillips screwdriver
• Replacement core switch blade
Faulty core switch blade indicators
Confirm that you need to replace the core switch blade before continuing. The following events may
indicate that a core switch blade is faulty:
• The status LED on the core switch blade is lit steady amber, or the power LED is not lit.
• The slotShow command does not show that the core switch blade is enabled.
• The haShow command indicates an error.
• Any of the following messages display in the error log:
‐"Slot unknown" message relating to a core switch slot
‐Core switch blade errors or I2C timeouts
‐FRU: FRU_FAULTY messages for a core switch blade
‐Configuration loader messages or "Sys PCI config" messages
‐Generic system driver messages ("FABSYS")
‐Platform system driver messages ("Platform")
‐EM messages that indicate a problem with a core switch blade
‐Function fail messages for the core switch master
For more information about error messages, refer to the Fabric OS Message Reference.
Removing a core switch blade (CR16-8)
Follow electrostatic discharge (ESD) precautions when removing a blade. Wear a wrist grounding
strap connected to chassis ground (if the Brocade DCX 8510-8 is plugged in) or a bench ground.
For safety reasons, the ESD wrist strap should contain a series 1 megaohm resistor.
NOTE
The CR16-8 blade is compatible only with the Brocade DCX 8510-8.
NOTE
The Brocade DCX 8510-8 continues to operate while a core switch blade is being replaced.
Complete the following steps to remove the core switch blade.
1. Remove the chassis door.
2. Unscrew the two thumbscrews from the ejectors on the blade using the Phillips screwdriver. Unscrew
the top thumbscrew until it pops out. This initiates a hot-swap request.
3. Label and then disconnect cables from the faulty core switch blade.
4. Open the ejectors by rotating them toward the center of the blade face. Pull the blade out of the
chassis using the ejectors.
FIGURE 24 Removal and replacement of the core switch blade (CR16-8)
Replacing a core switch blade (CR16-8)
Follow electrostatic discharge (ESD) precautions when replacing a blade. Wear a wrist grounding
strap connected to chassis ground (if the Brocade DCX 8510-8 is plugged in) or a bench ground.
DANGER
For safety reasons, the ESD wrist strap should contain a series 1 megaohm resistor.
NOTE
The CR16-8 blade is compatible only with the Brocade DCX 8510-8.
The Brocade DCX 8510-8continues to operate while a core switch blade is being replaced.
Complete the following steps to replace the core switch blade.
1. Open the ejectors by rotating them toward the center of the blade face. Orient the CR blade so that
the handles are toward you.
2. Align the flat side of the blade inside the top and bottom rail guides in the slot with the components
facing right, and slide the blade into the slot until it is firmly seated.
3. Close the ejectors by rotating them away from the center of the blade. The levering action of the
ejectors seats the blade in the slot.
4. Power on the blade by screwing in the thumbscrews.
5. Verify that the power LED is green (might require a few seconds). If not, ensure that the core switch
blade has power and is firmly seated and that the ejectors are in the locked position.
The status LED on the new blade is initially amber and will be until POST for the blade completes.
this may take as long as several minutes. It then turns green.
6. Connect the cables to the new core switch blade. For the DCX 8510 models, if the QSFP cables are
not used, make sure the rubber gaskets are in the QSFP transceivers.
7. Replace the chassis door.
8. Pack the faulty core switch blade in the packaging provided with the new core switch blade, and
contact the Brocade DCX 8510-8 supplier to determine the return procedure.
Power supply removal and replacement
Use this procedure to remove and replace a power supply.
NOTE
Depending on the blade configuration of the chassis and the number of power supplies installed, the
Brocade DCX 8510-8 may be able to continue operating during the replacement. Refer to Power
specifications on page 131 to determine your power requirements. If there is insufficient power, the
chassis will start powering down blades until the power demand can be met. Brocade DCX 8510-8
power supplies are 100-240 VAC, autosensing.
Time and items required
The replacement procedure for each power supply takes less than five minutes. A power supply unit or
filler panel is required for the power supply replacement.
Identifying power supplies
The following figure shows the location and identification of the power supplies.
To remove a power supply, complete the following steps.
1. Perform the appropriate following action based on whether the Brocade DCX 8510-8 is operating:
• If the Brocade DCX 8510-8 is not operating during the replacement procedure, go to step 2.
• If the Brocade DCX 8510-8 is operating and will continue to operate during the replacement,
check the power LEDs to verify that the minimum number of power supplies is functioning. Refer
to Providing power to the Brocade DCX 8510-8 Backbone on page 27 to check your power
requirements.
2. Turn off the power switch.
3. Unlatch the power cord retainer clip.
4. Remove the power cord.
5. Loosen the thumbscrew.
6. Grasp the handle and pull, sliding the power supply from the chassis and supporting the power
supply from beneath as you remove it.
7. Verify that the power LED on the power supply displays a steady green light.
8. If you are installing two new power supplies in a DCX or DCX 8510-8 chassis to bring the total of
power supplies up to four, you should change the switchstatus policy settings for power supplies to
the following in order to enable the call home feature if one power supply goes down:
switch.status.policy.PowerSupplies.down = 1
switch.status.policy.PowerSupplies.marginal = 0
For more details on executing the switchStatusPolicyShow and switchStatusPolicySet
commands, refer to the Fabric OS Command Reference.
Blower assembly removal and replacement
Use this procedure to remove and replace a blower assembly.
NOTE
The Brocade DCX 8510-8 can continue operating during the replacement if the other two blower
assemblies are operating. To ensure continuous adequate cooling, maintain three operating blower
assemblies at all times except for the brief period when replacing a blower assembly.
Time and items required
The replacement procedure for each blower assembly takes less than 5 minutes. The following items
are required for the blower assembly replacement:
• Replacement blower assembly
• #2 Phillips screwdriver
Removing a blower assembly
Complete the following steps to remove a blower assembly from the chassis.
1. Before removing a blower assembly, verify that the other blower assemblies are functioning
correctly. The power LEDs should be steady green.
2. Use the screwdriver to loosen the captive screws at the top and bottom of the blower assembly.
3. Grasp the handle and pull, sliding the blower assembly from the chassis and supporting the blower
assembly from beneath as you remove it.
FIGURE 27 Removal and replacement of the blower assembly
Replacing a blower assembly
Replacing a blower assembly
Complete the following steps to replace the blower assembly in a chassis.
1. Orient the blower assembly and slide it into the chassis, pushing firmly to ensure that it is seated.
2. Verify that the power LED displays a green light.
3. Use the screwdriver or your fingers to tighten the captive screws.
WWN card removal and replacement
There are two WWN cards located beneath the WWN bezel (logo plate). Use this procedure to remove
and replace the WWN cards. If Brocade Support has determined that a WWN card needs to be
replaced, you need to power-down the chassis, and then both the WWN cards must be replaced as a
matched pair.
Time and items required
Allow approximately 20 minutes to replace the WWN cards. The following items are needed to replace
the WWN cards:
• Electrostatic discharge (ESD) grounding strap
• #2 Phillips screwdriver (required only for some versions of the WWN card)
• If a serial console session is used: serial cable and a workstation computer with a terminal emulator
Verifying the need for replacement
Before replacing a WWN card, verify that the replacement is necessary. Any of the following events
can indicate that the card requires replacement:
• Status LEDs on the WWN bezel not reflecting the actual status of the components.
• Power or Status LEDs on WWN card (beneath logo plate) indicate a problem.
• Problems viewing or modifying the data stored on the WWN card.
• Error messages regarding WWN units #1 or #2 from the chassisshow output.
application (such as HyperTerminal for Windows systems or TIP for Solaris systems)
Preparing for the WWN card replacement
If the WWN cards require replacement, complete the following steps. Follow electrostatic discharge
(ESD) precautions.
DANGER
For safety reasons, the ESD wrist strap should contain a series 1 megaohm resistor.
1. Open a Telnet session to the chassis and log in to the active CP as admin. The default password is
"password".
2. Verify that you are logged in to the active CP. Run the haShow command to determine the active
CP.
3. Run the supportSave command on the active CP to capture all settings. These will be used later to
verify the settings have been correctly programmed.
4. Contact Brocade Technical Support for replacement of both WWN cards. Brocade Support will
request the partner or OEM to send two WWN cards from FRU inventory to the nearest Brocade
Support office to be reprogrammed. Brocade Support will require the Supportsave data taken in
the previous step so that the replacement cards can be reprogrammed prior to shipping to the
partner or your site.
NOTE
Do not execute the frureplace command. The command will no longer be functional beginning with
the release of Fabric OS 7.0.0c, but users with earlier versions of the Fabric OS should also not run
the command.
When both the replacement WWN cards have been received, complete the following steps to remove
the bezel and faulted WWN cards.
Follow electrostatic discharge (ESD) precautions. Wear a wrist grounding strap connected to chassis
ground (if the chassis is plugged in) or a bench ground.
DANGER
For safety reasons, the ESD wrist strap should contain a series 1 megaohm resistor.
1. Open a Telnet session to the chassis and log in to the active CP as admin. The default password is
"password".
2. Verify that you are logged in to the active CP. Run the haShow command to determine the active
CP.
3. Run the supportsave command on the active CP to capture all settings. If any problem occurs
during the replacement, the supportsave information will be important for solving the problem.
4. Run the following commands on the chassis before replacing the cards so that the data can be
verified after the replacement:
1. licenseidshow
2. ipaddrshow
3. switchname
4. chassisname
5. wwncardshow ipdata
6. chassisshow (look at the WWN and Chassis information at the bottom)
7. ficonshow switchrnid
The factory serial number and the sequence number in the following outputs should match, except in
the ficonshow switchrnid, which will have a number appended to the front indicating that the logical
switch number, if virtual fabrics is enabled:
switch:FID128:root> chassisshow
<output truncated>
WWN Unit: 1
Header Version: 2
Power Consume Factor: -1
Factory Part Num: 60-1000491-05
Factory Serial Num: AFX2533G001
Manufacture: Day: 19 Month: 1 Year: 2012
Update: Day: 5 Month: 5 Year: 2014
Time Alive: 756 days
Time Awake: 3 days
WWN Unit: 2
Header Version: 2
Power Consume Factor: -1
Factory Part Num: 60-1000491-05
Factory Serial Num: AJX0416G02H
Manufacture: Day: 12 Month: 8 Year: 2011
Update: Day: 5 Month: 5 Year: 2014
Time Alive: 897 days
Time Awake: 3 days
Chassis Factory Serial Num: AFY2530G00S
switch:FID128:root> ficonshow switchrnid
{
{Switch WWN Flag Parm
10:00:00:05:1e:95:b1:00 0x00 0x200a00
Type number: SLKWRM
Model number: DCX
Manufacturer: BRD
Plant of Manufacture: CA
Sequence Number: 0AFX2533G001
tag: b6ff
5. Login to the chassis and execute the switchcfgpersistentdisable command on the main switch
and other logical switches. The switchcfgpersistentdisable command disables the switches, and
ensures they remain disabled after the power is cycled. This allows you to check all the settings so
that you can verify the settings before placing the chassis back into production.
switch:FID128:root> switchcfgpersistentdisable
Switch's persistent state set to 'disabled'
switch:FID128:root>
If there are other logical switches on your chassis, use the setcontext command to connect to all
the other switches and then run switchcfgpersistentdisable on these switches as well.
6. Power down the entire chassis.
7. Remove the screws from the WWN bezel on the back of the chassis. Pull the bezel away from the
chassis and set it aside. The two WWN cards are now visible.
8. Use a Phillips screwdriver to unscrew the screws that secure each WWN card to the chassis. Label
the WWN cards and cables with #1 for the left side and #2 for the right side, for future reference.
9. Disconnect the WWN cable by depressing the cable connector latch and pulling the connector from
the WWN module.
10.Hold the WWN cards by the edges and gently pull them out from the chassis.
11.Set the WWN card on a static-free surface, such as a grounding pad.
FIGURE 28 Removal and replacement of the WWN bezel (logo plate) and WWN card