Storageworks 48 San Switch

HP StorageWorks Fabric OS 6.2.
0b
release notes
Part number: 5697-0352

Second edition: March 2010
Downloaded from www.Manualslib.com manuals search engine

Legal and notice information
© Copyright 2009-2010 Hewlett-Packard Development Company, L.P.
© Copyright 2009-2010 Brocade Communications Systems, Incorporated
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.
Government under vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the
express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional
warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft and Windows are registered trademarks of Microsoft Corporation.

Version
6.2.0b
NOTE:
This software conforms to the Fibre Channel standards and to accepted engineering practices and
procedures.
Effective date
March 2009
Description
Fabric OS 6.2.0b introduces support for the HP StorageWorks Encryption SAN Switch and the HP
DC Switch Encryption FC Blade. These products provide the following features:
• Data encryption support for B-Series fabrics
• Key Management support for HP Secure Key Manager (SKM)
Fabric OS 6.2.0a integrated the following new features (these features continue to be supported in
Fabric OS 6.2.0b):
• Support for the new HP StorageWorks DC04 SAN Director
• 192 ports, 8–Gb technology in 8U chassis (without required front airflow mounting kit, 9U
with kit)
• Supports existing 8–Gb FC blades (16, 32, and 48 port)
• Supports existing 10–Gb 6 port ISL blade
• Supports existing Multi-protocol Router blade
• Supports ICL connectivity to other DC04 and DC SAN Backbone directors
• Virtual Fabrics (VF)
• Full VF feature support on HP StorageWorks DC SAN Backbone Director, HP StorageWorks
DC04 SAN Director, HP StorageWorks 8/80 SAN Switch, and HP StorageWorks 8/40 SAN
Switch.
• Single physical chassis can be subdivided into two or more logical switches, creating a logical
fabric with other switches.
• Per-port assignment of ports to logical switches
• Shared ISLs provide connectivity for multiple logical fabrics.
• FCR and FCIP enhancements
• FCIP (SCSI) read tape pipelining
• Enhancements to SoTCP
• LSAN tagging
• Support Pathinfo over MetaSAN
HP StorageWorks Fabric OS 6.2.0b release notes 3

• Use FSPF cost in FCR backbone fabric to find shortest path to edge fabric
• In-band management link over FCIP connections for HP StorageWorks 400 Multi-protocol
Router
• TCP byte streaming for FCIP connections with WAN optimization hardware
• Improved FCIP statistics support, including TCP connection history, high watermark information,
and connection snapshot capability
• Support temporary licenses for Adaptive Networking, Integrated Routing, and Fabric Watch
• Security enhancements
• IPv6 auto-configuration
• IPSec with IPv6 (for management port)
• Configurable switch-wide policy requiring authentication of all HBAs
• RADIUS enhancements allowing password expiration and source IP address information
• LPAD enhancement allowing for alternate domain UPN
• IPv6 certified for JITC Approved Product List
• FICON enhancements
• RNID support for CUP
• New FC addressing modes for support with virtual fabrics
• Support for HP StorageWorks SAN Director 48 Port 8Gb FC Blade with VF-enabled HP Stor-
ageWorks DC SAN Backbone Director and DC04 SAN Director for FICON environments
• Access Gateway enhancements
• AG mode support on HP StorageWorks 8/40 SAN Switch.
• Miscellaneous
• FC ping support between switches (ping switch WWN)
• Provision of path information via CLI
• Frame redirection support in interopmode 3 (McDATA Open Fabric Mode)
• Support for M-EOSn's 239 Domain ID mode via FCR in interopmode 3
• System-wide RASLOG
• Port auto-disable support
• Ethernet port bonding for management ports
• New CLI command to configure F_Port receive buffer credits
New feature descriptions

This section describes the new features that were introduced in Fabric OS 6.2.0a.
Virtual fabrics
• Virtual Fabrics (VF) is a new capability supported on the HP StorageWorks DC SAN Backbone
Director, DC04 SAN Director, HP StorageWorks 8/80 SAN Switch, and HP StorageWorks 8/40
SAN Switch. Once enabled, VF allows the user to divide a single physical chassis or switch into
multiple logical switches by assigning individual ports to a logical switch. Each of these logical
switches is managed as a completely independent layer 2 Fibre Channel switch, and can be de-
ployed in independent fabrics known as logical fabrics.
• VF also allows the user to create a special logical switch known as the base switch, used for
connectivity to other base switches and also as a backbone fabric for Fibre Channel Routing. In-
dividual logical fabrics may utilize this shared base fabric for connectivity to other switches,

providing efficient use of resources by sharing common ISL and ICL connections among multiple
logical fabrics.
• The Virtual Fabrics feature is part of the base Fabric OS and does not require a license. Virtual
Fabrics is fully compatible with legacy Brocade products as well as M-Series switches and directors.
FCR and FCIP enhancements
• FCIP (SCSI) Read Tape Pipelining anticipates host read operations and buffers data to reduce
latency from the FCIP WAN.
• LSAN Tagging provides special behavior for designated LSAN zones using either a new speed
tag or enforce tag. The enforce tag allows individual FCRs to be configured only to import devices
in specific LSAN zones, increasing scalability. The speed tag allows designated targets to remain
imported, allowing sensitive hosts to discover targets much faster. This is useful when performing
boot over LSAN operations
• SoTCP Enhancements improve network congestion management in Slow Start Mode and helps
prevent host I/O timeouts.
• Support for Pathinfo over MetaSAN. The Pathinfo command has been enhanced to provide
path information across routed fabrics, which is especially useful when troubleshooting connectivity
problems across routed fabrics.
• FSPF cost in FCR backbone fabric uses the most efficient route to reach a destination fabric, pre-
venting the use of an FCIP link when an ISL is available.
• In-band management link over FCIP connections for the HP StorageWorks 400 Multi-protocol
Router allows a management station to communicate with a remote 400 Multi-protocol Router
through the GE ports. This allows a single management station located on the WAN side of the
400 Multi-protocol Router to communicate with the management interface on the CP for management
tasks such as firmware downloads, snmp polling, snmp traps, trouble shooting, and configuration.
Enhanced Native Connectivity with McDATA products
• Fabric OS 6.2 and M-EOS 9.9 now support Frame Redirection in McDATA Open Fabric Mode
(interopmode 3) fabrics. Frame Redirection zones must be created and activated from Fabric OS
platforms.
• Fabric OS platforms now support EX_Port connections to McDATA Open Fabric Mode Mi10ks
using the 239 DID setting.
Security enhancements
• Configurable stateless IPv6 auto-configuration support.
• IPSec with IPv6 support provides greater security for management ports and configurable security
policies for IPv4/6 addresses.
• A switch-wide policy requiring HBA authentication requires the FC-SP bit to be set in FLOGI. If the
bit is not set, the FLOGI is rejected and the port is disabled.
• A new warning for RADIUS login allows users to configure how many days in advance they should
be notified of password expiration.
• An LDAP enhancement adds the ability to provide an alternate UPN (userPrincipalName) to domain
authentication.
Contact your switch vendor regarding the use of other backup applications.
Optionally licensed software

The following are optionally licensed features in Fabric OS 6.2:
• Ports on Demand allows customers to instantly scale the fabric by provisioning additional ports
via license key upgrade (applies to select models of switches).

• Extended Fabrics provides greater than 10 km of switched fabric connectivity at full bandwidth
over long distances (depending on platform, the distance can be up to 3000 km).
• ISL Trunking provides the ability to aggregate multiple physical links into one logical link for en-
hanced network performance and fault tolerance. This also includes Access Gateway ISL Trunking
on those products that support Access Gateway deployment.
• Advanced Performance Monitoring enables performance monitoring of networked storage resources.
This license includes the TopTalkers feature.
• High Performance Extension over FCIP/FC (formerly known as FC-IP Services) for the HP Storage-
Works B-Series Multi-protocol Router blade and 400 Multi-protocol Router). This license key also
includes the FC-Fastwrite feature and IPsec capabilities.
• Accelerator for FICON license enables unique FICON emulation support for IBM’s Global Mirror
(formerly XRC) application (including Hitachi Data Systems HXRC and EMC’s XRC) as well as
Tape Pipelining for all FICON tape and virtual tape systems to significantly improve XRC and tape
backup/recovery performance over virtually unlimited distance for HP StorageWorks 400 Multi-
protocol Router and B-Series Multi-protocol Router blade.
• Fabric Watch monitors mission-critical switch operations. Fabric Watch now includes new Port
Fencing capabilities.
• The FICON Management Server (also known as CUP or Control Unit Port) enables host-control of
switches in Mainframe environments.
• ICLs, or Inter Chassis Links, provide dedicated high-bandwidth links between two HP StorageWorks
DC SAN Backbone Directors or DC04 SAN Director switch chassis, without consuming valuable
front-end 8G ports. Each DC Backbone Director/DC04 SAN Director must have the ICL license
installed in order to enable the ICL connections. (Available on the DC Backbone Director/DC04
SAN Director only)
• Adaptive Networking provides a rich framework of capability allowing a user to ensure high pri-
ority connections and obtain the network resources necessary for optimum performance, even in
congested environments. The QoS SID/DID Prioritization and Ingress Rate Limiting features are
the first components of this license, and are fully available on all 8G platforms.
• The Integrated Routing license allows ports in an HP StorageWorks DC SAN Backbone Director,
HP StorageWorks DC04 SAN Director, HP StorageWorks 8/80 SAN Switch, or HP StorageWorks
8/40 SAN Switch, to be configured as EX_ports supporting Fibre Channel Routing. This eliminates
the need to add an B-Series Multi-protocol Router blade or use the 400 Multi-protocol Router for
FCR purposes, and also provides double the bandwidth for each FCR connection (when connected
to another 8G-capable port).
• A Server Application Optimization license, introduced with Fabric OS 6.2, when deployed with
Server Adapters, optimizes overall application performance for physical servers and virtual machines
by extending virtual channels to the server infrastructure. Application specific traffic flows can be
configured, prioritized, and optimized throughout the entire data center infrastructure.
Included licensed software

The Enhanced Group Management license is included with all HP 8Gb switches. Enhanced Group
Management enables full management of the device in a datacenter fabric with deeper element
management functionality and greater management task aggregation throughout the environment.
This license is used in conjunction with Data Center Fabric Manager (DCFM) application software.
Temporary license support

Temporary licenses are not currently supported by HP.

Previously licensed software now part of base Fabric OS
The following capabilities are included as part of the base Fabric OS capability and no additional
purchase or licensing is necessary.
NOTE:
Advanced Zoning and Web Tools licenses are no longer necessary, beginning with Fabric OS 6.1.
These features are automatically enabled on all products running Fabric OS 6.1 or later
Supported switches
The following switches are supported with Fabric OS 6.2.0b:
• HP StorageWorks 4/8 and 4/16 SAN Switch
• HP StorageWorks 8/8 and 8/24 SAN Switch
• Brocade 4Gb SAN Switch for HP p-Class BladeSystem
• Brocade 4Gb SAN Switch for HP c-Class BladeSystem
• HP StorageWorks EVA4400 Embedded Switch Module
• HP StorageWorks 8Gb SAN Switch for HP BladeSystem c-Class
• HP StorageWorks SAN Switch 4/32
• HP StorageWorks 4/64 SAN Switch
• HP StorageWorks SAN Switch 4/32B
• HP StorageWorks Encryption SAN Switch
• HP StorageWorks 400 Multi-protocol Router
• HP StorageWorks 4/256 SAN Director
• HP StorageWorks DC SAN Backbone Director
• HP StorageWorks DC04 SAN Director
• HP DC Switch Encryption FC Blade
• HP StorageWorks 4/256 SAN Director 16 Port 4–Gb Blade
• HP StorageWorks Multiprotocol Router Blade
• HP StorageWorks B-Series iSCSI Director Blade
• HP StorageWorks SAN Director 16 Port 8–Gb FC Blade
• HP StorageWorks SAN Director 6 Port 10–Gb FC ISL Blade
Standards compliance
This software conforms to the Fibre Channel Standards in a manner consistent with accepted
engineering practices and procedures. In certain cases, HP might add proprietary supplemental

functions to those specified in the standards. For a list of standards conformance, visit the following
HP Web site: http://www.hp.com.
Update recommendations
All products supported by Fabric OS 6.0.x can be upgraded to Fabric OS 6.2.0b. If applicable, HP
recommends that users upgrade to Fabric OS 6.2.0b as soon as possible to take advantage of the
latest fixes and features.
See Firmware upgrades and downgrades for further information.
Supersedes
Fabric OS 6.2.0a released in January, 2009.
New hardware support

Support for HP StorageWorks DC04 SAN Director Switch was introduced with Fabric OS 6.2.0a:
• Has 192 ports, 8 Gb/sec technology in an 8U chassis with horizontal slots (9U with standard
port side air flow kit)
• Supports HP StorageWorks SAN Director 16 Port 8Gb FC blade, SAN Director 32 Port 8Gb FC
blade, and SAN Director 48 Port 8Gb FC blade
• Supports all special purpose blades available for HP StorageWorks DC SAN Backbone Director
• Supports ICL connectivity to other HP StorageWorks DC04 SAN Director Switch or DC SAN
Backbone Director chassis
Fabric OS 6.2.0b introduces support for the HP StorageWorks Encryption SAN Switch and the HP
DC Switch Encryption FC Blade. The encryption switch provides:
• 48 Gb/s of encryption processing power, upgradable to 96 Gb/s
• Industry standard AES-256 algorithms for data-at-rest encryption
• 32 Fibre Channel ports, 8 Gb/s in 2U form factor
• Integration with HP StorageWorks Secure Key Manager (SKM)
The encryption blade provides 16 ports and is supported in the DC SAN Backbone and DC04 SAN
Directors.
NOTE:
The encryption switch and blade are unique products compared to standard Fibre Channel switches.
HP highly recommends that you read the Fabric OS Encryption Administrator's Guide before
configuring these products into any fabric.
Supported product models

The following product models can be upgraded to Fabric OS 6.2.0b:
• HP StorageWorks 4/8 SAN Switch and 4/16 SAN Switch (Brocade 200E)
• HP StorageWorks 4/64 SAN Switch (Brocade 4900)
• HP StorageWorks 400 Multi-protocol Router (Brocade 7500)

• HP StorageWorks 16 Port 4-Gb Blade (FC4-16)
• HP StorageWorks 32 Port 4-Gb Blade (FC4-32)
• B-Series MP Router Blade (Brocade FR4-18i Blade)
• HP StorageWorks 4/48 SAN Director Blade (FC4-48)
• HP StorageWorks SAN Switch 4/32 (Brocade 4100)
• HP StorageWorks 4/32B SAN Switch (Brocade 5000)
• HP StorageWorks 4/256 SAN Director (Brocade 48000)
• HP StorageWorks B-Series iSCSI Director Blade (Brocade FC4-16IP) compatible with the 4/256
SAN Director model only, not supported in the DC SAN Backbone Director or DC04 SAN Director
• Brocade 4-Gb SAN Switch for HP p-Class BladeSystem (Brocade 4012)
• Brocade 4-Gb SAN Switch for HP c-Class BladeSystem (Brocade 4024)
• Brocade 8–Gb SAN Switch for HP BladeSystem c-Class (Brocade 5480)
• HP StorageWorks DC SAN Backbone Director (Brocade DC Director Data Center Backbone)
• HP StorageWorks SAN Director 16 Port 8-Gb FC blade (Brocade FC8-16)
• HP StorageWorks SAN Director 6 Port 10-Gb FC ISL blade (Brocade FC10-6)
• HP StorageWorks EVA4400 embedded switch module (Brocade 5410)
• HP StorageWorks DC04 SAN Director

Unsupported product models
The following product models cannot be upgraded to Fabric OS 6.2.0b:
• HP StorageWorks Core Switch 2/64, which operates with Fabric OS 5.0.x (Brocade 12000)
• HP StorageWorks SAN Director 2/128 (Brocade 24000)
• HP StorageWorks MSA SAN Switch 2/8, which operates with Fabric OS 3.2.x (Brocade 3000)
• HP StorageWorks SAN Switch 2/8V (Brocade 3250)
• HP StorageWorks SAN Switch 2/16V (Brocade 3850)
• HP StorageWorks SAN Switch 2/16, which operates with Fabric OS 3.2.x (Brocade 3800)
• HP StorageWorks SAN Switch 2/32 (Brocade 3900)
• HP StorageWorks Multi-protocol (MP) Router, which operates with XPath OS 7.4.x (Brocade
AP7420)
IMPORTANT:
Any enhancements for the models listed above will be delivered in Fabric OS 3.2.x, Fabric OS 5.x,
and XPath OS 7.4.x sustaining releases.
Devices supported
For a list of supported devices, see the HP website:
http://www.hp.com/go/san
Operating systems
For a list of operating systems, see the HP website:
http://www.hp.com/go/san
Access Gateway support

Access Gateway is supported with the following HP products only:
• Brocade 4-Gb SAN Switch for HP p-Class BladeSystem (Brocade 4012)
• Brocade 4-Gb SAN Switch for HP c-Class BladeSystem (Brocade 4024)
• HP StorageWorks 4/16 SAN Switch (Brocade 200E)
10

IMPORTANT:
Although the HP StorageWorks 4/8 SAN Switch uses the same hardware as the 4/16 SAN Switch,
it does not support Access Gateway. The same applies to the HP StorageWorks 8/8 and 8/24 SAN
Switches. Both use the same hardware, but only the 8/24, which has all ports licensed, has Access
Gateway support. Also, Access Gateway mode is not supported with the Brocade 4-Gb SAN Switch
for HP p-Class BladeSystem (Brocade 4012) if any half-height BladeServers (BL3xp) are configured
in the same sleeve in the p-Class enclosure. For the latest updates, see the HP website:
http://www.hp.com
Access Gateway connectivity is supported by the switches listed in Access Gateway support and also
by the following B-Series switches:
• HP StorageWorks EVA4400 embedded switch module
• HP StorageWorks DC SAN Backbone Director
• HP StorageWorks 4/256 SAN Director
• HP StorageWorks SAN Switch 4/32B
• HP StorageWorks 400 Multi-Protocol Router
Access Gateway was introduced with Fabric OS 5.2.1b. It allows a switch to operate in agmode ,
which allows simplified connectivity between large numbers of servers and the SAN. Access Gateway
leverages N_Port ID Virtualization (NPIV) to hide the complexity of the servers (both physical and
virtual) attached to it, while allowing easy SAN connectivity. The edge fabric switch provides all fabric
services, while Access Gateway connects to the edge switch by what appears as a host bus adapter
(HBA) connection. This architecture allows the deployment of many additional servers without requiring
a domain and the associated fabric rebuild traffic. Rebuild traffic is prevalent when switches are
powered on, added, or removed from a fabric.
See the Brocade Access Gateway Administrator's Guide, available on http://www.hp.com/go/san
for more information.
Access Gateway support in non-Brocade fabrics

In addition to being supported in Brocade fabrics, Access Gateway is supported for connectivity to
the following:
• McDATA fabrics running EOS 09.00.xx with Brocade Fabric OS 5.2.1b
• McDATA fabrics running EOS 09.02.xx or 09.03.xx with Brocade Fabric OS 5.3.0, 5.3.0a,
5.3.0b, 5.3.0c, 5.3.0d
• McDATA fabrics running EOS 09.06.x with Brocade Fabric OS 5.3.1, 5.3.1a, 6.0.0b, 6.0.1a
• Cisco fabrics running SAN-OS 3.0(2a) with Brocade Fabric OS 5.2.1b
• Cisco fabrics running SAN-OS versions 3.1(2a), 3.1(3), 3.1(3a) with Brocade Fabric OS 5.3.0,
5.3.0a, 5.3.0b, 5.3.0c, 5.3.0d
• Cisco fabrics running SAN-OS versions 3.0(2a) with Brocade Fabric OS 5.3.1, 5.3.1a, 6.0.0b,
6.0.1a

Secure Fabric OS feature not compatible with Fabric OS 6.x
and later
Fabric OS 5.3.x is the last Fabric OS version which was compatible with SFOS. However, all of the
security features of SFOS have been fully integrated into the base Fabric OS, starting with Fabric OS
5.3.x.
Zoning and fabric operations

When configuring zoning or other fabric-wide settings in a fabric that has products operating with
different versions of Fabric OS, HP recommends that you perform the configuration via an interface
(such as Web Tools) to a product with the most recent version of Fabric OS. Some older versions of
Fabric OS do not fully support newer hardware models, and problems may arise when configuring
settings through these older products.
NOTE:
Never perform a zoning configuration through a switch operating with Fabric OS 3.x in a fabric that
also has products operating with newer versions of Fabric OS.
Prerequisites
Table 1 lists the supported Fabric OS firmware versions. HP recommends using the latest supported
firmware release versions to get the greatest benefit from the SAN.
For a list of retired products, see the HP website:
http://www.hp.com
IMPORTANT:
The Fabric OS versions listed in the Earliest compatible version column in Table 1 are the earliest
versions supported by HP at the time of the Fabric OS 6.2.0b release.
Table 1 Supported Fabric OS versions
Model Earliest compatible version Recommended version
Not supported, end of sup-

HP StorageWorks 1-Gb Switch N/A
port (December 2007)
HP StorageWorks SAN Switch 2/8 EL

nl
HP StorageWorks SAN Switch 2/16

nl
3.2.1b 3.2.1c
MSA SAN Switch 2/8
HP StorageWorks Core Switch 2/64

nl
HP StorageWorks SAN Director 2/128 in Chassis 5.0.5e 5.0.5f

Config modes 3 and 4 only
12

HP
nl
StorageWorks SAN Switch 2/8V
HP StorageWorks SAN Switch 2/16V
nl
5.1.1b 5.3.2
HP
nl
StorageWorks SAN Switch 2/32
HP
nl
StorageWorks SAN Director 2/128
HP StorageWorks
nl
4/256 SAN Director
HP StorageWorks
nl
4/8 SAN Switch
HP StorageWorks
nl
4/16 SAN Switch
HP StorageWorks
nl
4/64 SAN Switch
HP StorageWorks B-Series MP Router Blade (FR4-
5.1.1b 6.2.0b
18i)
nl
HP StorageWorks
nl
16 Port 4-Gb Blade (FC4-16)
HP StorageWorks
nl
32 Port 4-Gb Blade (FC4-32)
HP StorageWorks
nl
400 MP Router
HP StorageWorks 4/32 SAN Switch
Brocade 4-Gb SAN Switch for HP p-Class

BladeSystem
nl
5.3.1 6.2.0b
Brocade 4-Gb SAN Switch for HP c-Class
BladeSystem
HP StorageWorks 48 Port 4-Gb Blade (FC4-48) 5.3.1 6.2.0b
HP StorageWorks B-Series iSCSI Director Blade

5.3.1 6.2.0b
(FC4-16IP)
HP StorageWorks 4/32B SAN Switch 5.3.1 6.2.0b
HP StorageWorks MP Router XPath OS 7.4.1d XPath OS 7.4.1e
HP StorageWorks DC SAN Backbone Director 6.0.0b 6.2.0b
HP StorageWorks SAN Director 16 Port 8-Gb FC

6.0.0b 6.2.0b
blade (FC8-16)

6.0.0b 6.2.0b
blade (FC8-32)

6.0.0b 6.2.0b
blade (FC8-48)
HP StorageWorks SAN Director 6 Port 10-Gb ISL

6.0.0b 6.2.0b
blade (FC10-6)
Fabric Manager1 5.2.0a 5.5
Data Center Fabric Manager 10.0.2 10.1.0
HP StorageWorks Encryption SAN Switch 6.2.0b 6.2.0b
HP DC Switch Encryption FC blade 6.2.0b 6.2.0b

1
Using HP StorageWorks Fabric Manager (FM) 5.5 or earlier with Fabric OS 6.1.1 or later can result in problems with Zoning,
Performance monitoring, SYSLOG configuration, FICON wizards, IOD Delay, AAA replication, Port enable/disable and other
functions. Unless you are using Admin Domains, HP recommends that you upgrade to HP StorageWorks Data Center Fabric
Manager (DCFM) 10.3.x to use with Fabric OS 6.1.1 or later. If you are using Admin Domains, HP recommends that you
downgrade Fabric OS to 6.1.0h.

4/256 SAN Director blade support
Fabric OS 6.2.0b is fully qualified and supports the Director blades listed in Table 2.
Table 2 4/256 SAN Director blade support matrix
Director blade Number of blades
FC4-16
FC4-32
Supported with any mix, and up to eight blades of each
FC4-48 type. No intermix restrictions. The 4/256 SAN Director
FC8-16 must run Fabric OS 6.0.0b or later to support the FC8-
FC8-32 16 port blade, and Fabric OS 6.1.0a or later to support
the FC8-32 and FC8-48 port blades.
FC8-48
FC10-6
FC4-16IP (iSCSI blade) Up to four blades of this type
Up to two blades of this type. Up to eight FR4-18i blades

FR4-18i (FCIP/FC Router blade) can be installed if they are used only for FC Fast Write
or FCIP without routing.
DC SAN Backbone and DC04 SAN Director blade support

Fabric OS 6.2.0b is fully qualified and supports the DC Director blades listed in Table 3.
Table 3 DC Director blade support matrix
Director blade Number of blades
FC8-16 Supported with Fabric OS 6.0.0b and later with any mix
FC8-32 and up to eight blades of each type on DC SAN Director
Backbone. No intermix restrictions. The DC04 SAN
FC8-48 Director requires Fabric OS 6.2.0a and later, and supports
FC10-6 up to 4 blades.
Not supported with the DC SAN Director Backbone, or

FC4-16IP (iSCSI blade)
DC04 SAN Director
Supported with Fabric OS 6.0.0b and later with a

maximum of four blades of this type on DC SAN Director
Backbone. Up to eight FR4-18i blades can be installed if
FR4-18i (FCIP/FC Router blade) they are used only for FC Fast Write or FCIP without routing
in the DC SAN Director Backbone. The DC04 SAN Director
requires Fabric OS 6.2.0a and later, and supports up to
4 blades.
Supported with Fabric OS 6.2.0b and later with a maxim-

FS8–18 (HP DC Switch Encryption FC blade) um of four blades of this type on DC SAN Director Back-
bone and DC04 SAN Director.
14

Power supply requirements for Director blades
Table 4 lists power supply requirements for Director blades to provide full redundancy (220 VAC
power is assumed).
IMPORTANT:
Director blades must meet minimum Fabric OS levels to operate in the Director chassis. For example,
the FC8-32 is not supported in the 4/256 SAN Director with Fabric OS 6.0.x.
Table 4 Power supplies required for blades in Director chassis
Director blade 4/256 SAN Director DC SAN Backbone Director and

DC04 SAN Director1
FC4-16
FC4-32
FC4-48 Two power supplies Two power supplies
FC8-16
FC8-32
FC8-48
Four power supplies Two power supplies
FC10-6
Two power supplies. The FC4-16IP

FR4-18i (FCIP/FC Router blade) blades are not supported in the DC
Four power supplies
FC4-16IP (iSCSI blade) SAN Backbone and DC04
Directors.
FS8–18 (HP DC Switch Encryption Two power supplies. Requires 220

Not supported
FC blade) VAC in the DC04 SAN director.
1
The DC Director can operate with nominal power of 110 VAC. See the appropriate hardware reference guide for power
specifications.
Fibre Channel Routing scalability

For the latest FCR scalability support information, see the HP StorageWorks SAN design reference
guide, available at:
http://www.hp.com/go/sandesignguide

Important notes
This section contains information that you should consider before you use this Fabric OS release.
DCFM compatibility
Fabric OS 6.2 is fully compatible with HP StorageWorks Data Center Fabric Manager (DCFM) 10.1.x
management software. DCFM is a comprehensive SAN management application that enables
end-to-end management of HP B-Series Data Center Fabrics. It is the next-generation product and the
successor to existing B-Series management products, including HP StorageWorks Fabric Manager
(FM) and Enterprise Fabric Connectivity Manager (EFCM).
DCFM is available in two versions: DCFM Professional, an application bundled with B-Series switches
that is ideally suited for small and medium size businesses that need a light weight management
product to manage their smaller fabrics (one physical fabric at a time, up to 1,000 ports); and DCFM
Enterprise, that is designed for enterprise-class customers and showcases unparalleled performance
and scalability (24 physical fabrics, up to 9,000 switch ports). DCFM Enterprise configures and
manages HP StorageWorks DC SAN Backbone Directors, along with other B-Series directors, routers,
and switches. and HBAs. Existing EFCM and FM customers that have active Maintenance and Support
contracts are provided a seamless migration path to DCFM Enterprise.
Fabric OS compatibility
Table 1 on page 12 lists the earliest versions of software supported in this release, that is, the earliest
supported software versions that interoperate. Brocade recommends using the latest software versions
to get the greatest benefit from the SAN.
When using the new Virtual Fabrics feature, it is HP recommends that all switches participating in a
fabric with a logical switch use the latest firmware available for those switches. All switches must be
operating at minimum firmware levels noted in the Fabric OS Interoperability table.
16

Fabric OS feature compatibility in native connectivity modes
Some Fabric OS features are not fully supported when operating in the native connectivity modes for
deployment with M-EOS-based products. All HP StorageWorks models that are supported by Fabric
OS 6.2.0b support both interopmodes 2 and 3, with the exception of the HP StorageWorks 4/32
SAN Switch.
NOTE:
HP may not support all of these switches in this mode. See “Merging Fabrics based on M-Series and
B-Series FC switches” application note available at http://www.hp.com for specific support in
interopmodes 2 and 3.
Table 5 specifies the support of various Fabric OS features when operating in either interopmode 2
(McDATA Fabric Mode) or interopmode 3 (Open Fabric Mode) with Fabric OS 6.2.0b.
Table 5 Feature support in interopmodes 2 and 3
Fabric OS Features (supported in interopmode 0) Fabric OS 6.2.0x
IM = interopmode IM 2 IM 3
L2 Fabric OS Hot Code Load Yes Yes
Fabric OS Hot Code Load with FCR Yes Yes
Zone Activation Support Yes Yes1
Traffic Isolation Zones2 Yes No
Frame Redirection (devices attached to Fabric OS)2 Yes Yes1
Frame Redirection (devices attached to M-EOS)2 Yes Yes1
Frame Redirection over FCR3 Yes Yes1
FCR Fabric Binding (route to M-EOS fabric with Fabric Binding)4 Yes Yes
L2 Fabric Binding Yes No5
DCC policies No No
SCC policies Yes6 No5
E/Ex_Port Authentication Yes Yes
ISL Trunking (frame level) Yes7 Yes7
Dynamic Path Selection (DPS, exchange-based routing) Yes8 Yes8
Dynamic Load Sharing (DLS, port-based routing) Yes Yes
Virtual Channels (VC RDY) Yes7 Yes7

FICON Management Server (Cascading) Yes No5
FICON MIHPTO Yes No5
Full Scalability (to maximum M-EOS fabric limits) Yes Yes
Adaptive Networking QoS No No
Adaptive Networking: Ingress Rate Limiting No5 No5
Advanced Performance Monitoring (APM) No5 No5
APM: TopTalkers No5 No5
Admin Domains No No
Secure Fabric OS9 N/A N/A
Fabric Watch Yes Yes
Ports on Demand (POD) Yes Yes
NPIV Yes Yes
Timer Server Function (NTP) No No
Open E_Port10 N/A N/A
Broadcast Zoning No No
FDMI No No
Remote Switch No No
Port Mirroring Yes Yes
Extended Fabrics Yes Yes11
Alias Server No No
Platform Service No No
FCIP (VE_Ports) Yes Yes
IPFC (IP over FC) Yes12 Yes12
M-EOS ALPA 0x13 configuration Yes Yes
VE to VEX Port Yes Yes
Integrated Routing4 Yes Yes
Domain Offset Support No No
239 Domain Support (available on Mi120k only) N/A Yes13
Masterless F_Port Trunking (AG connect to Fabric OS switches only) Yes Yes
FC10-6-to-FC10-6 ISL Yes Yes
18

RASLog Events on duplicate WWNs Yes Yes
Virtual Fabrics Yes Yes
Logical Fabric using LISLs (XISLs in base Fabric) No No

1
Only Frame Reduction zones can be configured on Fabric OS platforms and sent to fabrics operating in McDATA Open
Fabric Mode (interopmode 3). M-EOS 9.9 is required to support FR zones in McDATA Open Fabric Mode.
2
Requires M-EOS 9.7 or later for redirection between devices attached to Fabric OS switches, M-EOS 9.8 for redirection
between devices attached to M-EOS switches, M-EOS 9.9 for use in McDATA Open Fabric Mode. Supported EOS platforms
include M4400, M4700, M6140, and Mi10K.
3
To support Frame Reduction to an edge M-EOS fabric, there must be at least one Fabric OS switch in the edge fabric to
configure Frame Redirection Zones.
4
All routers (EX_Ports) must reside in a backbone fabric running in interopmode 0 only. Only edge fabrics with devices imported
to the backbone fabric or other edge fabrics can be operating in IM2 or IM3.
5
This feature is available, but not officially tested or supported.
6
SCC policies supported only in conjunction with 1.2 Fabric Binding support.
7
Allowed only between Fabric OS-based switches.
8
DPS is supported outbound from Fabric OS-based switches. M-EOS can provide reciprocal load balancing using OpenTrunking.
9
Not supported in Fabric OS 6.0 or later.
10
Mode 3 qualified only with M-EOS switches
11
Not on FCR.
12
Supported only locally within the Fabric OS switch.
13
Supported via FC Routing only. All routers in the backbone must be running Fabric OS 6.2.
NOTE:
FICON Cascaded CUP is qualified only on select platforms.
Firmware upgrades and downgrades

Upgrading to Fabric OS 6.2.0b is allowed only from Fabric OS 6.1.0a or later. The policy to support
only one-level migration, which began with Fabric OS 6.0.0, provides more reliable and robust
migrations for customers. By having fewer major changes in internal databases, configurations, and
subsystems, the system is able to perform the upgrade more efficiently, taking less time and ensuring
a truly seamless and non-disruptive process for the fabric. The one-release migration policy also
reduces the large number of upgrade-downgrade permutations that must be tested, allowing for the
thorough test and verification of supported migration paths.
The HP StorageWorks DC04 SAN Director Switch may not be downgraded from Fabric OS 6.2.0a.
All downgrades from Fabric OS 6.2.0a require a restart and are disruptive to traffic. Platforms
supporting Virtual Fabrics must have the feature disabled before downgrading to a version earlier
than 6.2.0a.
To ensure non-disruptive Hot Code Load (HCL), neighbor switches should be operating with Fabric
OS 6.2.0a or later prior to loading Fabric OS 6.2.0b on the following platforms:
• Brocade 4Gb SAN Switch for HP p-Class BladeSystem
• Brocade 4Gb SAN Switch for HP c-Class BladeSystem
• HP StorageWorks 4/8 and 4/16 SAN Switches
When upgrading to Fabric OS 6.2.0b from Fabric OS 6.1.0g or earlier, the CPs do not fully
synchronize until both the new active and new standby CPs are running Fabric OS 6.2.0b. This is
normal behavior and the firmware upgrade is still not disruptive.

Fabric OS 6.2.0b does not support concurrent FC Routing (EX_Ports) and TopTalkers features Upgrading
to Fabric OS 6.2.0b requires that one of these features be disabled first.
Firmware upgrade instructions
IMPORTANT:
HP strongly recommends that users upgrade to Fabric OS 6.2.0b as soon as possible. Upgrading to
Fabric OS 6.2.0b is allowed only from Fabric OS 6.1.x. See “Update recommendations” on page
8 for additional guidelines.
NOTE:
With the introduction of Fabric OS 6.1.1, certain features and functions were removed from Web
Tools (resident in the firmware) and migrated to the Data Center Fabric Manager (DCFM) management
application. This has been carried forward to Fabric OS 6.2.x. HP recommends that before upgrading
to Fabric OS 6.2.x or later, if you are not running DCFM on your fabric, you review the “Web Tools
functionality Moved to DCFM” on page 25 and note what has changed in order to assess the impact
to your fabric.
To access the latest Fabric OS 6.2.0b firmware, configuration files, and MIB files, see the HP website:
http://www.hp.com/support/downloads
At the website:
1. User Storage, select Storage Networking.
2. Select the link for the appropriate switch, select your product, and then select Cross operating
system (BIOS, firmware, Diagnostics, etc.)
3. Select Firmware (HP StorageWorks Fabric OS release notes 13).
4. Select V6.x Firmware for HP StorageWorks B-Series Fibre Channel Switches for Fabric OS 6.2.0b:
• To download the firmware, select Download.
• To read the release notes, select the Release Notes tab.
Scalability
Refer to the HP SAN Design Guide, available on http://www.hp.com for specifics on supported
scalability.
FICON support
The HP StorageWorks DC04 SAN Director Switch is not supported for FICON Cascading in
interopmode 2 or 3 for use in mixed fabrics with M-EOS platforms.
NOTE:
For information about specific versions of Fabric OS support for FICON, see the B-series FICON
Connectivity Stream.
20

Other important notes and recommendations
This section contains additional information that you should consider before you use this Fabric OS
release.
Virtual fabrics
• On Virtual Fabrics-capable platforms, the Virtual Fabrics feature must be enabled after upgrading
to Fabric OS 6.2.x in order to utilize the related capabilities, including Logical Switches and Lo-
gical Fabrics.
• When creating Logical Fabrics that include switches that are not Virtual Fabrics-capable, it is
possible to have two Logical Switches with different FIDs in the same fabric. Extra caution should
be used to verify that the FIDs match for all switches in the same Logical Fabric.
• The aptpolicy can be configured per logical switch. The Administrator Guide indicates it is a
chassis-level setting.
• In order to support non-disruptive Hot Code Load on an HP StorageWorks 8/40 SAN Switch with
VF enabled, the total zoning DB size for the entire chassis should not exceed 1MB.
Licensing behavior
When operating a switch with Fabric OS 6.2.x, some licenses may display as Unknown. This is due
to a changes in licensing requirements for some features that no longer require a license key and may
still be installed on a switch.
Frame redirection
In Fabric OS 6.2.x, Frame Redirection zoning is not allowed with Default Zoning (all access in
IM0 and default zone in IM2). This was allowed in prior releases. There is no software enforcement
to block the upgrade.
Adaptive networking/flow-based QoS prioritization

• When using QoS in a fabric with 4G ports or switches, Fabric OS 6.0 or later versions must be
installed on all products in order to pass QoS info. E_Ports from the HP StorageWorks DC SAN
Backbone Director or HP StorageWorks DC04 SAN Director to other switches must come up after
6.0 is running on those switches.
• Flow-based QoS is not supported on FC8 blades in the HP StorageWorks 4/256 SAN Director
• Any products that are not capable of operating with Fabric OS 6.0 may not exist in a fabric with
Flow-based QoS. Major problems occur if previous generation 2G products exist in the fabric.
• For the HP StorageWorks SAN Switch 4/32 and SAN Switch 4/32B, if all of the ports are E_Ports
and the switch is upgraded to Fabric OS 6.2.x, the buffers on the E_Ports are changed to utilize
the QoS model. If the switch is rebooted, 28 of 32 ports will come up in QoS mode; the last four
ports will come up in buffer-limited mode. Workarounds include disabling long distance configur-
ation for these ports or explicitly disabling QoS on other ports, freeing up buffers for the last four
ports.
FCR
All FCR switches need to be running Fabric OS 6.2.x in order to support M-EOS 239 Domain Mode
on the i10K

FCR backbone fabric ID changes
• With 8Gb director blades, the switch must be disabled to change the backbone fabric ID.
• With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the
IDs unique.
Traffic isolation over FCR

• All switches and Fibre Channel Routers, both in edge and backbone fabrics, must be running
Fabric OS 6.1.0 or later in order to support this feature.
• In order for Traffic Isolation over FCR to function properly, the associated TI zones in each fabric
(edge and backbone) need to have failover enabled.
Integrated routing
• To allow Hot Code Load on an HP StorageWorks 8/40 SAN Switch when using Integrated
Routing, the edge switch connected to the 8/40 SAN Switch must be running Fabric OS 6.1 or
later.
• The HP StorageWorks 8/40 SAN Switch does not support Hot Code Load from Fabric OS 6.1.0
to 6.2.x in a dual backbone configuration with a routed connection to an M-EOS product.
• Integrated Routing EX_Ports are supported only in the base switch on a switch with VF enabled.
To test Integrated Routing functionality, disable the VF feature (fosconfig --disable vf) first.
• Integrated Routing and TopTalkers are not concurrently supported in Fabric OS 6.2.x. To use In-
tegrated Routing, be sure to disable TopTalkers before configuring EX_Ports.
Access gateway
When in Access Gateway mode, the Automatic Port Configuration policy may not work when attached
to M-EOS switches. M-EOS ports should be set to G_port to prevent problems with port type discovery.
FCS automatic distribution

• When using the FCS Automatic Distribution feature in Fabric OS 6.0 or later, all switches in the
fabric must be running Fabric OS 6.0 or later. If any switches are running Fabric OS 5.x or
earlier, only manual distribution can be used.
• Fabric OS 6.0 or later allow only FCS automatic distribution when in strict mode, requiring only
switches with Fabric OS 6.0 or later.
FIPS
FIPS mode should not be enabled on HP StorageWorks 4/8 or 4/16 SAN Switches. If FIPS is enabled,
the 4/8 and 4/16 SAN Switches will not boot.
LDAP
When using LDAP, downgrades from Fabric OS 6.2.x to earlier releases requires user intervention.
Authentication must be set to local and back to LDAP in order to continue using LDAP authentication.
22

FCAP
• Due to limitations with the certificates, FCAP authentication cannot be supported on user-defined
logical switches. FCAP will continue to function with existing certificates for non-VF and the default
logical switch of VF enabled switches. Note that authutil is not restricted from other logical
switches at this time, so it can still be enabled on unsupported LS.
• The pkicert(1.06) utility may cause evm errors, so each new switch should be isolated from the
fabric in non-vf mode, to install new certificates.
• For FIPS mode, certificates need to be installed prior to FIPS activation.
FICON
• For the HP StorageWorks DC SAN Backbone Director, FICON CUP is not allowed with a 48-port
blade in the Default Logical Switch. All ports on a 48–port blade must be assigned to a user-
defined Logical Switch to use them in a FICON CUP enabled switch.
• PDCM changes configured via Web Tools must be activated with the edit window if the Act-
ive=Saved mode is enabled.
• When RSCNs are sent out on behalf of the CUP for switchname changes in interopmode 2, the
mainframe channels interpret those RSCNs as though a paths may have gone down. This forces
the channels into a form of recovery, whereby they send TINs to the CUP to verify the logical paths
that are still established to the CUP. This results in mainframe console messages indicating that
this type of recovery has occurred.
Port mirroring
• On the HP StorageWorks 8/80 SAN Switch, the port mirroring feature has a limitation where all
port mirror resources must stay within the same ASIC port group. The resources are the configure
mirror port, Source Device, and Destination Device or ISL, if the Destination Device is located on
another switch. The ASIC port groups are 0-15, 16-31, 32-47, 48-63, and 64-79. The routes will
be broken if the port mirror resources are spread across multiple port groups.
• Port Mirroring is not supported on a switch with the Virtual Fabrics feature enabled.
10G interoperability
10G interop between HP StorageWorks SAN Director 6 Port 10Gb FC blade and McDATA blades
is not supported, due to a hardware limitation; however the HP StorageWorks SAN Director 6 Port
10Gb FC blade is supported in a chassis running in Interopmode 2 or 3 (SAN Director 6 Port 10Gb
FC blade to SAN Director 6 Port 10Gb FC blade connections only). A SAN Director 6 Port 10Gb
FC blade will not synchronize with a McDATA 10G blade, but will not negatively impact the system.
Port fencing
• When the port fencing feature is enabled for ITW or CRC errors, the first set of errors detected on
an active link that meet the custom high threshold level set by the user (or the default threshold
level) is always ignored to account for expected link transition errors. The port is disabled only
upon detection of a second set of errors; that is, the next time the user-set threshold level (or default
threshold level) is reached. This prevents a port from being disabled due to normal link transition
behaviors.
• When using the Port Fencing feature, you must first run the fwalarmsfilterset command.
This command enables the port and allows you to receive Port Fencing messages.

• Port Fencing can be inadvertently disabled from Web Tools. This occurs when you first open the
Fabric Watch configuration window and then check the SNMP Trap checkbox in the Above row.
This change in Web Tools disables Port Fencing. If this happens, you must re-enable the Port
Fencing bit from the command line interface.
Extended fabrics and R_RDY flow control

• Beginning with Fabric OS 5.1, the Extended Fabrics feature is supported in conjunction with R_RDY
flow control (R_RDY flow control mode can be enabled by the portCfgISLMode command).
R_RDY flow control mode that uses IDLE primitives does not support frame-based Trunking for
devices such as Time Division Multiplexor (TDM.) To overcome this limitation and provide support
for frame-based Trunking with Extended Fabrics, Fabric OS 6.2.x has been enhanced to support
interoperability with these distance extension devices.
Fabric OS 6.2.x allows Extended Fabrics E_ports to operate in VC_RDY mode using either ARB
or IDLE primitives as fill words. This allows frame-based Trunking to be supported on Extended
Fabrics E_Ports even when IDLE primitives are configured for these ports when operating in native
VC_RDY mode. Prior to this change, frame-based Trunking was supported only when ARB primitives
were used in VC_RDY mode. With Fabric OS 6.2.x, frame-based Trunking is supported on Extended
Fabrics E_Ports even if IDLE or ARB primitives are used when operating in native VC_RDY mode.
Implementation
The portcfglongdistance CLI parameter VC Translation Link Init is now overloaded
to specify whether the long distance link should use IDLE or ARB primitives. By default vc_init is enabled.
When vc_init is enabled, the long distance link uses ARB primitives. If vc_init is disabled, the link uses
IDLE primitives.
The buffer-to-buffer credit recovery feature is not supported on Extended Fabrics E_Port when it is
configured to use IDLE primitives. The user must disable buffer-to-buffer credit recovery feature using
the command portcfgcreditrecovery and specifying the disable option; otherwise, the link will
continuously reset.
The Adaptive Networking SID/DID Traffic Prioritization QoS feature is not supported on Extended
Fabrics E_Ports when IDLE primitives are configured on these ports. This is because in this mode only
data Virtual Channels are available while QoS related virtual channels are not available.
When connecting to an extension device that does not support ARB primitives (such as some TDM
products), the following configuration must be used:
• portcfgqos -disable <port>
• portcfgcreditrecovery –disable <port>
• portCfgLongDistance <port><LD|LD>0<distance>
The fabric parameter fabric.ops.mode.longdistance is now deprecated and should not be
used.
Table 6 summarizes the portcfgfillword command.
24

Table 6 portcfgfillword command summary
Fabric OS version All 8-Gb switches (except 8-Gb 8-Gb SAN Switch for HP
SAN Switch for HP BladeSystem BladeSystem c-Class
c-Class)
All ports set to idles. No arb(ff) All ports set to idles. No arb(ff)
Any Fabric OS earlier than 6.1.2
capability existed. 1 capability existed. 2
All ports default to arb(ff) (internal

Arb(ff) by default on all ports and
FOS 6.2.0x prior to 6.2.0c and external) and can’t be
can’t be changed.
changed.
6.1.2x and 6.2.0c and later (HP Added the ability to change portcfg- Added the ability to change portcfg-
did not support 6.2.0c) fillword to idle or arb(ff). 1 fillword to idle or arb(ff). 2
• If 6.2.0d was installed in the

factory, all internal ports remain
at arb(ff) [mode 1], external
All ports default to idle [mode 0] ports at idle [mode 0]. Can be
regardless of what FOS was previ- changed by the user.
ously installed, unless manually • If pre-6.2.0d was installed in the
6.1.2x and 6.2.0d through 6.2.x
changed to arb(ff) previously [mode factory, all internal and external
1], then it will remain arb(ff). Can ports remain at idle [mode 0],
be changed by the user. unless they were manually
changed to arb(ff) [mode 1],
then they remain at arb(ff). Can
be changed by the user.
0—IDLE for Link Init, IDLE for fill

word
Mode: 1—ARB(FF) for Link Init, ARB(FF) for
fill word (NOTE: not supported with
XP storage arrays)
1
6.1.2x was not supported on EVA4400 embedded switch module.
2
6.1.2x was not supported on this switch.
Web Tools functionality Moved to DCFM

The functionality that was moved from Web tools in 6.1.1 to DCFM is applicable to both DCFM
Professional and DCFM Enterprise and is also applicable to 6.2.x. Table 7 specifies these changes.
Table 7 Web Tools functionality in DCFM
Function Web Tools 6.1.0 DCFM Comments
Configure > Zoning

Reverse Find in the zoning dialog
provides the view of the zoned
Add unzoned devices Zone Admin
and unzoned devices in the fabric
is all zone members are selected
for Find.

Configure > Zoning:
Reverse Find in the zoning dialog
provides the view of the zoned
and unzoned devices in the fabric
if all zone members are selected
for Find.
Device Tree and Topology:
Analyze zone config Zone Admin
Connected End Devices: Custom
display from the top level in the
main frame provides the device
tree and topology view for all the
zoned devices if all zones are
selected in the active zone
configuration.
Define device alias Zone Admin Configure > Zoning
Configure > Zoning

The Compare dialog provides the
Storage-Host and Host-Storage
Device accessibility matrix Zone Admin view in a tree representation that
is comparable to the Device
Accessibility Matrix when all
devices are selected.
Fabric events Monitor > Fabric events Monitor > Logs > Events
Monitor > Reports > Fabric

Fabric summary Reports > Fabric summary
Summary report
Viewing FCIP tun-

nels is still suppor-
ted in Web Tools
Port Admin Module > 6.1.1, but New,
FCIP tunnel configuration Configure > FCIP tunnel
GigE tab Edit Config, and
Delete are avail-
able only in
DCFM.
Port Admin Module >

GigE ports interface Configure > FCIP tunnel
GigE tab
Port Admin Module >

GigE ports route Configure > FCIP tunnel
GigE tab
Zone Admin
In Web Tools,
Admin Domain non-local switch
Non-local switch ports
Switch Admin > DCC Configure > Zoning port id/WWN
display in zoning tree
policies can be added us-
Performance Monitoring ing text box.
26

Configure > Zoning
Replace/Replace All zone
members by selecting the offline
Remove Offline or inac-
Zone Admin devices from the zone tree.
cessible Devices
Offline devices have an unknown
overlay badge with good
visibility.
Configure > Zoning

Zone database summary
Zone Admin Zoning report for both online and
ping
offline database
Zoning
Encryption behavior
• HP recommends that the encrypted LUN containers be created when all the nodes/Encryption
Engines (EE) in the Data Encryption Key (DEK)/High Availability Cluster (HAC) are up and enabled.
• LUN configuration
• The following process is to be used then when configuring a LUN for encryption:
• Add the LUN as clear-text to the Crypto Target Container (CTC).
• Once the LUN comes online and clear-text host I/O starts, modify the LUN from clear-text
to encrypt, including the enable_encexistingdata option to convert the LUN from
clear-text to encrypted.
• An exception to this LUN configuration process:if the LUN was previously encrypted by the HP
Encryption Switch or HP Encryption Blade, the LUN can be added to the Crypto Target Con-
tainer with the –encrypt and –lunstate =“encrypted” options.
• LUN configurations must be committed to take effect. No more than 25 LUNs can be added
or modified in a single commit operation. Attempts to commit configurations that exceed 25
LUNs will fail with a warning. Note that there is also a five-second delay before the commit
operation takes effect.
Always ensure that any previously committed LUN configurations or LUN modifications have
taken effect before committing additional LUN configurations or additions. All LUNs should be
in an Encryption Enabled state before committing additional LUN modifications.
• Avoid changing the configuration of any LUN that belongs to a Crypto Target Container/LUN
configuration while the re-keying process for that LUN is active. If the user changes the LUN’s
settings during manual or auto, re-keying or First Time Encryption, the system reports a warning
message stating that the encryption engine is busy and a forced commit is required for the changes
to take effect. A forced commit command halts all active re-keying processes running in all Crypto
Target Containers and corrupts any LUN engaged in a re-keying operation. There is no recovery
for this type of failure.
• To remove access between a given initiator and target, the user must not only remove the active
zoning information between the initiator and target, but must also remove the associated Crypto
Target Containers (CTCs), which will in turn remove the associated frame redirection zone inform-
ation.
• Before committing configurations or modifications to the CTC or LUNs on an HP Encryption Switch
or HP Encryption Blade, make sure that there are no outstanding zoning transactions in the switch
or fabric. Failure to do so results in the commit operation for the Crypto Target or LUNs failing
and may cause the LUNs to be disabled. The user can check for outstanding zoning transaction
by issuing the cfgtransshow CLI command:

DCX_two:root> cfgtransshow
There is no outstanding zoning transaction
• Each LUN is uniquely identified by the HP Encryption Switch or HP Encryption Blade using the
LUN’s serial number. The LUN serial numbers must be unique for LUNs exposed from the same
target port. The LUN serial numbers must also be unique for LUNs belonging to different target
ports in non-multipathing configurations. Failure to ensure unique LUN serial numbers results in
non-deterministic behavior and may result in faulting of the HP Encryption Switch or HP Encryption
Blade.
• When creating an HA Cluster or Encryption Group with two or more HP Encryption Switch/En-
cryption Blades, the GE Ports (I/O sync links) must be configured with an IP address for the eth0
Ethernet interface using ipaddrset. In addition, both eth0 and eth1 Ethernet ports should be
connected to the network for redundancy. These I/O sync links connections must be established
before any Re-Key, First Time Encryption, or enabling EE for crypto operations. Failure to do so
results in HA Cluster creation failure. If the IP address for these ports is configured after the EE
was enabled for encryption, HP Encryption Switch needs to be rebooted and Encryption blades
should be slotpoweroff/slotpoweron to sync up the IP address information to the EEs. If
only one Ethernet port is configured and connected to a network, data loss or suspension of Re-
Key may occur when the network connection toggles or fails.
• initEE will remove the existing master key or link key. Backup the master key by running
cryptocfg –exportmasterkey and cryptocfg –export –currentMK before running
initEE. After initEE, regEE and enableEE, run cryptocfg –recovermasterkey to re-
cover the master key previously backed up, or in the case of fresh install run cryptocfg –
genmasterkey to generate a new master key. If you are using SKM, establish a trusted link with
SKM again. Certificate exchange between key vaults and switches are not required in this case.
• The disable EE interface CLI cryptocfg --disableEE [slot no] should be used only to
disable encryption and security capabilities of the EE from the Fabric OS Security Admin in the
event of a security compromise. When disabling the encryption capabilities of the EE using the
noted commands, the EE should not be hosting any CTCs. Ensure that all CTCs hosted on the HP
Encryption Switch or HP Encryption Blade are either removed or moved to a different EE in the
HA Cluster or EG before disabling the encryption and security capabilities.
• Whenever initNode is performed, new certificates for CP and KAC (SKM) are generated. Hence,
each time InitNode is performed, the new KAC Certificate must be loaded onto key vaults for
Secure Key Manager (SKM). Without this step, errors will occur, such as key vault not responding
and ultimately key archival and retrieval problems.
• The http server should be listening to port 9443. Secure Key Manager is supported only when
configured to port 9443.
• When all nodes in an Encryption Group (HA Cluster or DEK Cluster) are powered down (due to
catastrophic disaster or a power outage to the data center) and later nodes come back online (in
the event of the Group Leader (GL) node failing to come back up or the GL node being kept
powered down) the member nodes lose information and knowledge about the Encryption Group.
This leads to no crypto operations or commands (except node initialization) being available on
the member nodes after the power-cycle. This condition persists until the GL node is back online.
• Workaround. In the case of a datacenter power down, bring the GL node online first, before
the other member nodes are brought back up.
In the event of the GL node failing to come back up, the GL node can be replaced with a new
node. The following are the procedures to allow an EG to function with existing member nodes
and to replace the failed GL node with a new node
• Make one of the existing member nodes the Group Leader node and continue operations:
1. On one of the member nodes, create the Encryption Group with the same Encryption
Group name. This will make that node the GL node and the rest of the Crypto Target
Container and Tape Pool related configurations will remain intact in this Encryption Group.
28

2. For any containers hosted on the failed GL node, issue cryptocfg --replace to
change the WWN association of containers from the failed GL node to the new GL node.
• Replace the failed GL node with a new node:

1. On the new node, follow the switch/node initialization steps.
2. Create an Encryption Group on this fresh switch/node with the same Encryption Group
name as before.
3. Perform a configdownload to the new GL node of a previously uploaded configuration
file for the EG from an old GL Node.
4. For any containers hosted on the failed GL node, issue cryptocfg --replace to
change the WWN association of containers from failed GL node to the new GL node.
Initial setup of encrypted LUNs
IMPORTANT:
While performing first-time encryption to a LUN with more than one initiator active at the time, re-key
operations slow to a standstill. Define LUNs for a single initiator at a time to avoid this occurrence.
Fabric OS 6.2.0 fixes

The following table lists defects closed in the Fabric OS 6.2.0 firmware release.
Table 8 Fabric OS 6.2.0 closed defects
Closed defect summary Solution
Fixed in Fabric OS 6.2.0.

Workaround prior to upgrade:
Add Member button is disabled while creating a new TI Zone when
the switch is in VF mode. Add Other Port button can be used to
add ports.Tthis is available in the
ADD TI Zone window.

Under stress testing, cfgsave takes a long time and fails to propagate Workaround prior to upgrade:
on 64 VE-VE FCIP tunnel 33 switch core-edge topology running I/O. Wait until fabric is not saturated to
push configs around.

Adding a B-Series switch with conflicting domain ID into an EOS fabric Workaround prior to upgrade:
may cause another switch to segment. Check the domain ID before adding
a switch to any fabric.
USB port LED of HP StorageWorks DC SAN Backbone Director CP

blade stays ON after HA failover.
CUP Port stuck in Contingent Allegiance State after z9 Host IPL. Fixed in Fabric OS 6.2.0.
Spinfab and porttest (diagnostics) are not supported on ICL ports. Fixed in Fabric OS 6.2.0.

Bogus core_file created and transferred after the first reboot after a
firmwaredownload.

B-Series Multi-protocol (MP) Router blades in HP StorageWorks DC
SAN Backbone Director chassis may fail sysverification tests.
Rerun system verification.
With a switch in Interop Mode 2 or 3, the Zoning configuration is not

being included in configupload.
FICON Channel continuously sends RRQ frames for approximately 20

seconds before aborting.

If QoS and Diff Serv are enabled, some FCIP tunnels may not come
online in the case of an 8 to 1 fan-in scenario.
Port disable/enable the VE-Port
Under rare conditions, fabric mode TopTalker monitor does not display
correct flow values.
Attempting to configure port mirroring on a director with both 4Gb

and 8Gb blades may result in a software Verify error.

In rare instances the Name Server DB is out of sync between FOS and Workaround prior to upgrade:
EOS switches in interop mode 3. After locating the device ID, disable
and then enable that device.

Seccertutil show does not display the contents of certificates with Only LDAP certificates with .cer ex-
.cer extension. tension is supported; so use the
--ldapcert option for importing
.cer certificates.
When resetting all the hosts on a blade or slotpoweroff on a blade,

HP StorageWorks 4/256 SAN Director CP reboots due to the Software
Watchdog detecting unexpected termination of the Name Server
daemon.
Fastboot causes unnecessary FFDC, ERROR, ..., libipadm:

em_AdmSwitchNameGet()

In some instances of congestion in the Ethernet network, the displayed
VE port utilization value is incorrect.
Use portperfshow command.

Reject code '0B' response to a QSA frame causes channel definition Block off a badly misbehaving port
errors. that is generating bad traffic on a
switch port that is putting a lot of
stress on the embedded port.
30

When the switch name is set using CLI and then read using the Read
Port Address Name x'B2' command to the CUP Port x'FE' it returns the
switch name with a x'7F' attach after the last character in the Switch
Name.

A failed Pause frame (sent during firmwaredownload process in Workaround prior to upgrade:
Interop Modes 2 and 3), causes a fabric rebuild. Use the -o option to override the co-
operative HCL feature.

In some instances, HCL on an HP StorageWorks 8/40 SAN switch in
Interop Mode requires the use of the -o option.
Use the -o option.

A turboramtest failure does not fully disable the port on an HP
StorageWorks 8/80 SAN switch.
Reboot the switch.
Web Tools: The HP StorageWorks DC04 SAN Director attention LEDs

on the switch view GUI window do not turn amber when blade needs Fixed in Fabric OS 6.2.0.
attention.

N-Port between AG and Edge Switch (300) may become stuck at E-
Port Unknown state.D Disable and then enable the port on
the AG to bring the port back online
as an N-Port.

After multiple successive fastboots of an HP StorageWorks DC04 SAN
Director, there was a panic due to the zone daemon dying.
Fastboot a single time.
FICON PTP VTS Selective Resets and Aborted sequences caused by

incorrect entry into FICON tape read pipelining.
EX_Port fails to come online after downgrading firmware from Fabric

OS 6.x to 5.3 under certain conditions.

Tstimezone settings cannot be changed or restored with config- Workaround prior to upgrade:
download. Remove the ts.tz parameter in the
config file and then download.

If a large number of EX_Ports are enabled at the same time, occasion- Workaround prior to upgrade:
ally some fail due to incompatible flow control parameters. Portdisable and then enable the
EX_Ports that failed.
In some instances, portshow may display inaccurate port authentic-

ation description or state after a CP failover.
Internal server ports on embedded platform: traffic may stop due to

loss of buffer credit.

The error message is cryptic when the interop fabric contains more
than 60 devices in the default zone and the user tries cfgenablecfg- Fixed in Fabric OS 6.2.0.
disable.
When disabling/enabling a port, port fencing disables the port be-

cause the allowable number of invalid transmission words is exceeded.

Ag --show on an HP StorageWorks 8/8 or 8/24 SAN Switch shows
incorrect edge switch IP address after a slave port is swapped with
an N-port outside of the trunk group. Reboot the switch and ag --show
cli will show the correct output.

The 32-character switchname and chassisname extensions do not fully Workaround prior to upgrade:
display in RASLOG outputs, such as errdump or supportsave out- Use only 16-character switchname
put. and chassisname fields if full name
display in the logs is required.
FFDC occurs when 16-31 char switch/chassis name is input on a

platform that only supports up to 15.
I2C response failure and subsequent reset occasionally results in HP

StorageWorks DC SAN Backbone Director fan fault errors.

Under some conditions N_Port Failover may not work when swapping Execute portdisable/porten-
trunked and non-trunked N_Ports on an Access Gateway. able of F_Ports or switchdis-
able/switchenable or reboot the
switch.

Auto_ELP setting for EX_Port is not restored by configdownload. Workaround prior to upgrade:
Use auto_elp mode.
When running stressful IRNDUP to CUP tests, user may observe Inter-
mittent Channel Timeouts.

Warnings of excessively high temperature seen on some HP Storage- Increase cooling or relocate switch to
Works 8/40 SAN switches. cooler location. Be sure switch is in-
stalled with proper spacing above
and below it.

POST (portloopback test) intermittently fails on HP StorageWorks
400 Multi-protocol Router and B-Series Multi-protocol Router blade. Rerun diags by rebooting the switch
or powering on the slot with B-Series
Multiprotocol Router blade.
Zone Transaction appears to succeed in SMIA when the transaction

was aborted by web GUI.
Port address from switchshow does not include offset used for Interop
mode 2.
32

CRC errors did not match between portstatsshow and port-
errshow. Use portstatsshow to determine
whether there are CRC errors on a
link.
Under rare conditions, an HP StorageWorks DC SAN Backbone Dir-

ector panics during SAK IRNDUP when the software watchdog detects Fixed in Fabric OS 6.2.0.
an unexpected termination of the FICON CUP daemon (ficud).

User may need to change TI zone member in order to modify TI Zone Use configupload/download to
property (failover setting). change the TI zone, or modify the
member and the property (failover
disable/enable) together.
SW_RSCNs for RSCNs generated by attached nodes are not being

handled in McDATA Mode.
Legacy zone commands can be used to modify TI zones. Fixed in Fabric OS 6.2.0.
After hareboot, "Probing failed" on F_Port messages may be seen

on the HP StorageWorks 8/8, 8/24, 8/40, and 8/80 SAN switches.
HP StorageWorks 400 Multi-protocol Router panicked after TI zone

activation.

B-Series Multi-protocol Router blade faulted after overnight stress testing. Workaround prior to upgrade:
Do not configure an FCIP Tunnel.
Received error message with high temperature (89) on edge HP Stor-

ageWorks DC SAN Backbone Director in fabric.

The portcfgnpivport CLI command will not toggle trunked slave
ports if the user disables NPIV configuration on that port. The user must manually toggle (en-
able/disable) the slave port to com-
plete the operation.

Faulted (51) core blade due to POST failure, resulted from overnight
power cycle test. Disable the diagnostic POST, then
slotpoweroff on the faulted core
blade.
After attempting cfgdisable on a system in native interopmode and

with default zoning set to all access and a large zoneset of at least Fixed in Fabric OS 6.2.0.
460 devices, the switch became faulty.
No F_RJT's being returned for class 2 frames that are not routable ac-
cording to a QoS/TI configuration.

B-Series Multi-protocol Router blade failed to do blade firmwaredown- Workaround prior to upgrade:
load. Perform slot power off / slot power
on the blade that timed out.
Switch reboots when IFL is enabled. Fixed in Fabric OS 6.2.0.
Frame drop observed after creating a TI zone with failover enabled

in the backbone fabric ( TI over FCR).
Hard Zoning disabled when ports toggle. Fixed in Fabric OS 6.2.0.
Pathinfo doesn't match urouteshow and rtedebug. Fixed in Fabric OS 6.2.0.
Sensors show incorrect command output in fully loaded HP Storage-

Works DC SAN Backbone Director.
Update to VC assignment scheme within core ASIC management

structure.

Fastwrite performance issue with a particular FCIP Ex-port configuration.
Disable FCR routing and Ex-ports and
merge the fabric into one large fabric.

Under Port Base Routing, topologyshow always shows None for the Use urouteshow to view the 'Out
In Port field on HP StorageWorks 8/8, 8/24, and 8/40 SAN Switches. Port' selected for a particular 'In Port'
to a domain when using Port Based
Routing.
HCL on switch continues if sent Pause frame is rejected by attached

M-EOS switch. HCL on switch will sometimes continue, even when a Fixed in Fabric OS 6.2.0.
sent Pause frame is rejected by another switch in the fabric.
N_Port on Edge_AG_200E_PG got disabled with reason code Initi-

ator/target connected to N-Port.
Firmware download of Fabric OS 6.1.0 is allowed on an embedded

blade that should not allow it.
Fabric Rebuild during HP StorageWorks 8/40 SAN Switch HCL when

1 of 2 Backbones connect to a M6140 director.
If Turboramtest is performed, the Telnet console will disconnect. Fixed in Fabric OS 6.2.0.
Incorrect error when changed switchname for more than 24 charac-

ters through CLI in FMS mode.
F_Ports on HP StorageWorks 8/8 and 8/24 SAN Switches AG cannot

login, and become G-Ports.

Occasionally an LD port gets into a lock up state that causes port-
GetVCCredits get failed and the ISL segments with LD incomp,
although portcfgshow shows both sides of ISL config are the same. Reset with portcfgdefault/port-
cfgqos.
34

EE monitor counters may not get updated after performing switch- Retrieve all EE monitors from the
disable/switchenble or reboot. FLASH by issuing perfcfgrestore.
All EE monitor counters will be prop-
erly updated.
Static routing does not affect dynamic routes with DLS ON on supported
platforms.

The gzoneinfo.htm page returns empty data when CLI actually Do any other HTTP post operation
shows defined/eff cfg zone info for fabric. from DCFM and then you see both
the old data and the newly pushed
zone info. Rebooting the switch
sometimes helps.
Third-party storage center application does not survive in an FCIP

network with 1% packet loss and 100 ms network latency.
Traffic Isolation failover policy reverts back to disabled from enabled

after changing the port membership list.
Hareboot on HP StorageWorks 400 Multi-protocol Router FC fastwrite

enabled switch causes the system to panic with "Oops: kernel access Fixed in Fabric OS 6.2.0.
of bad area, sig: 11 [#1]."
Fabric Mode TT displays redundant flows with different values for the
same SID/DID pair on the core switches when there are redundant Fixed in Fabric OS 6.2.0.
trunk groups to the same edge domain.

DLS ON does not rebalance when ISLs to a different switch are re- Workaround prior to upgrade:
moved on HP StorageWorks DC SAN Backbone Director and HP Perform switchdisable and
StorageWorks 8/80 SAN Switch. switchenable to force a rebalance
of the routes.
On an HP StorageWorks 8/80 SAN Switch, the system status LED

does not flash amber/green when a power supply is faulted.
User with admin role in some AD is able to add another user with
admin role in AD as ALL.
Reset to default button is grayed out always in SCSI vs. IP traffic setup
window.
USB Admin is not in sync with CLI when launched . It shows the correct
info only when we click refresh button.

Name Server database is being set with incorrect WWN's for NPIV Workaround prior to upgrade:
nodes when port ALPA = 0x13. Port ALPA must be set to default value
of 0x00 for ports hosting NPIV nodes.
Potential timeouts and aborts during Device Discovery and CU busy

processing when using FICON XRC Emulation.

When an HP StorageWorks DC SAN Backbone Director blade is
powered off, Fabric Watch displays unnecessary warning message
about SFP voltages. Ignore messages; they indicate no
problem and have no side effect.
The EnumerateSelectedInstances CAL call returns a port that

is not present in GFABRIC MS call.
FICON Tape Write Pipelining does not function with converter. Fixed in Fabric OS 6.2.0.
In configure tab under switch admin tab, if value entered in R_A_TOV

and E_D_TOV is more than the threshold, the error message displays Fixed in Fabric OS 6.2.0.
the wrong range of values to be entered.

Integrated Routing with multiple ports in an EX_Port trunk, may not Disable trunking on HP StorageWorks
properly send an entire exchange on the same link. DC SAN Backbone Director and HP
StorageWorks 8/8, 8/24, 8/40,
and 8/80 SAN switches EX_Ports.
Sort does not work on Accessible Devices screen of name server. Fixed in Fabric OS 6.2.0.

Seccertutil gencsr is not accepted in non-interactive mode if Workaround prior to upgrade:
parameter has a space in it. Use the interactive mode to generate
the csr file.
IPAD FFDC error occurred after reboot of HP StorageWorks 4/8 or

4/16 SAN Switch.

HP StorageWorks 8/80 SAN Switch licenses disappeared and user
is not able to re-install them.
Clean install.
Switch Throughput Utilization Graph launches with all ports in graph

if we try launching by removing all ports from the edit Switch Fixed in Fabric OS 6.2.0.
Throughput Utilization dialog.
CUP Asynchronous Error Reporting Location not being set by default. Fixed in Fabric OS 6.2.0.
AG N_Port connected to embedded switch in interopmode 2 could

not restart traffic after switchdisable/enable followed by con- Fixed in Fabric OS 6.2.0.
figupload/download.
All ports come up Disabled (Persistent) after FMS mode is set while
switch is offline.
Fast Write could obtain incorrect FCP command data length if the
optional additional CDB length is selected.
Security Violation Console Message reported on un-existing port# on

an HP StorageWorks 4/64 SAN Switch (interopmode 2) with no se- Fixed in Fabric OS 6.2.0.
curity policy set.
Fabric OS does not send RSCN for CUP disable / enable in NI

mode 2.
36

Channel ack_1 to Control Unit ACC is being F_RJT'd after successful
RNID.

F_RJT not returned for unroutable class 2 PLOGI. Workaround prior to upgrade:
Do not use port 0 for an ISL.
Missing CE DE status. Fixed in Fabric OS 6.2.0.
FMS does not retry status after FICON channel returns LBY for Device
End.
FICON CUP reports incorrect Director Size Code in Basic Sense and
Sense ID data for HP StorageWorks 8/40 and 8/80 SAN switches.

Portcfgspeed command on 8G FC platforms are accepting invalid Do not provide a value of 5 to the
port speed = 5. portcfgspeed command. Speed
will be set to 8. If that is not desired,
re-submit the command with the
proper port speed.
XRC Emulation allows FICON Disk Control Unit paths to be activated

with DPR Mode.
FMS stuck busy condition caused host *MASTER* START PENDING

upon bringing switch online to mainframe operating system.
CP card of HP StorageWorks 4/256 SAN Director is set to FAULTY

(51).
HP StorageWorks 8/8, 8/24, 8/40, and 8/80 SAN switches: when

normal fan activity is interrupted, the high RPM fan rate cycle time Fixed in Fabric OS 6.2.0.
takes 1 hour.
RLS request from FICON host receives LS_RJT 031F in Interopmode 2. Fixed in Fabric OS 6.2.0.
FMS Mode enable failed due to insufficient frame filtering resources

on some ports.

HP StorageWorks DC SAN Backbone Director blades fault after reset- Workaround prior to upgrade:
ting a server with 32 HBAs. Power cycle the slot. Set port speed
to anything other than autonegotiate.
Fast Write configuration not properly installed after repeated, back-to-

back cable pull and re-inserts.
Out of Order frames delivered to HP StorageWorks DC SAN Backbone

Director via FICON channel from HP StorageWorks 8/40 SAN Switch Fixed in Fabric OS 6.2.0.
attached to a storage device (DASD).
CAL exception “Non-Secure tunnel can not be configured on the same

port as IP sec enabled tunnels.” come when trying to configure an IP Fixed in Fabric OS 6.2.0.
Sec tunnel on a switch which already had Non secure tunnels in it.

Fastwrite will attempt to configure, even on an HP StorageWorks B-
Series Multi-protocol Router blade that has failed to initialize success- Fixed in Fabric OS 6.2.0.
fully.
Zoned crashes after HP StorageWorks DC SAN Backbone Director

power cycle and zone transaction aborted

SMIA does not have information about SFP/GBIC type for a port. The embedded platforms have well
known user/server ports documented
in the user manuals.
The tag field of the node identifier command returned contains the port
number on which the command was received, instead of the tag field Fixed in Fabric OS 6.2.0.
of the device on the other end of the link.

Gzoneinfo.htm is returning empty zone information on fabric with
Fabric OS 6.1.1.
Reboot the switch.
Kernel Panic on 8Gb SAN Switch for HP BladeSystem c-Class after

firmwaredownload.
Conversion of uwatt to dbm for GE ports Tx Rx values shown in Web

Tools are incorrect.

HP StorageWorks 8/40 SAN Switch: FRU faulty status is not recovered
correctly. Turn on the power switch as soon as
possible after inserting a fan/power
supply unit into the system.

For McDATA mode edge fabric, only
Third-party array responds to ADISC with LOGO only over router McDATA switches have to be connec-
fabric, S_ID does not match N_ID. ted directly to FCR. The work around
is valid as long as we have only
McDATA switches directly connected
to Ex-Ports.
Ipfilter – Audit log (SEC- 3035, 3036, 3037): message properties

generating log without the appropriate key word.
AG trunks are not formed correctly when connected to an embedded

switch.
Tape Selective Reset error due to incorrect handling of Early End Syn-
chronization status.
F_port prefers to multiple N_ports Fixed in Fabric OS 6.2.0.
FICON Device Level Ack Emulation Processing error. Fixed in Fabric OS 6.2.0.
38

Command ipaddrshow does not show the IP address of a blade that
is seated in slot 12 of an HP StorageWorks DC SAN Backbone Direct-
or. Issue ipaddrshow -slot 12 to get
the information.
Re-key of LUNs hosted through active/passive ports will not complete

if started on the passive path.
Wave Length column in port optics dialog is currently blank. Fixed in Fabric OS 6.2.0.
Host may lose targets on edge AG in cascaded setup when failover Fixed in Fabric OS 6.2.0.
from core-AG to another core-AG connected to different edge fabric Workaround prior to upgrade:
switches. Disable/enable the N_port.

Web Tools zoning breaks when third-party storage virtualization ap- Workaround prior to upgrade:
pliance changed to standby mode. Change the third-party storage virtual-
ization appliance to standby cf mode.
The removal of an encryption performance upgrade license is not

prevented.
After configuring HP StorageWorks 8/8 or 8/24 SAN Switch AG so

that F-Port Trunking works and then performing portdisable on N-
Ports and then hareboot the 8/8 or 8/24 SAN Switch AG caused
unexpected termination of AGD
Audit Log [ZONE -3001] not generated when a member is added to

TI Zone.
The topologyshow command cannot show the "In ports" mapped

to "Out port" in port-based routing policy.

TCP RX Window advertisement can be much smaller than the actual
size of the RX Window. Reduce the committed rate on the FCIP
tunnel until the RX window is less than
33 MB.

FICON Tape Write Pipelining selectively resets after CmdRetry to No Workaround prior to upgrade:
Op Sequence or LBY. Disable FICON Tape Write Pipelin-
ing.
Ficud panic and reboot on HP StorageWorks DC SAN Backbone

Director occurs after executing host command to display the switch.
The event description from swEventTraps (related to RLIR events) is

not well formatted.
Four-node LUN discovery fails if one of the LUN out of 4 LUNs is tres-
passed.
Third-party application paths fails when FC FastWrite is enabled with

bi-directional traffic.
Java running out of memory in Web Tools. Fixed in Fabric OS 6.2.0.

No RSCN sent for physical device offline/online.1 switchdisable/enable of the HP
StorageWorks 400 Multi-protocol
router allows the devices to see each
other
CRC error observed between HP StorageWorks 8/40 and 8/80 SAN

switches with a particular SFP type.
Fibre Channel FastWrite path does not recover after restoring DWDM
connection.
Console security feature causes process failure. Fixed in Fabric OS 6.2.0.
PORT RSCNs are sent to DPC (VIs & VTs) every time when the config-
uration changes, which is unrelated to VT/VI. This affects any applic- Fixed in Fabric OS 6.2.0.
ation that uses frame redirect zoning.

FICON tape Write Acceleration sent UC status to channel twice for
one UC from device side.
Resubmit failed jobs.
Various tape creation or restore process issues found with FICON tape. Fixed in Fabric OS 6.2.0.
Initiator does not log into target several hours into ISL failover stress
test that forces host path failover.
Trying to enable a LUN on a member node fails stating ‘Specified

target not hosted by local node.’
Configdownload fails for fdd.* parameters from Fabric OS 6.1.1

to v6.2.0 through CAL.
With default zoning set to All Access, ACK frame with FC_type Exten-
ded Link can be dropped.
Fabric OS 6.2.0a fixes

The following table lists defects closed in the Fabric OS 6.2.0a firmware release.
Table 9 Fabric OS 6.2.0a closed defects
In a B2E routed environment, when the user executes the Pathinfo

Fixed in Fabric OS 6.2.0a.
command in BB querying for xlate domain, the switch may panic.
Some OS/HBA combinations take down the FC link when N_port-

generated RSCNs are delivered by switch with 0x08 (Fabric OS 6.1.1b
and 6.1.0g) or 0x20 (6.1.0x) as event qualifier. The fix reverts back
to Fabric OS 6.0 value of 0x00.
Switches slowly leaked memory over an extended period while being

managed by DCFM.
40

Fabric OS 6.2.0b fixes
The following table lists defects closed in the Fabric OS 6.2.0b firmware release.
Table 10 Fabric OS 6.2.0b closed defects
CUP can fail to send CU-End to clear busy. CUP is still responsive, but
Fixed in Fabric OS 6.2.0b.
the host is waiting for the CUE.
WWN card FRU replacement does not send async reports to FICON
host, so that customers do not know when a WWN card has been Fixed in Fabric OS 6.2.0b.
removed.
Customers may experience high CPU load and unexpected blade errors
due to an ASIC-generated interrupt handling problem.
Unable to configure ports using configdownload if the ports are

not physically present in the director (blade not plugged in).
Workaround prior to upgrade: Do not

On HP StorageWorks DC SAN Director, after running fosconfig change VF mode until dual CP chassis
--enable vf, followed by fosconfig --disable vf, customer is in sync
cannot log in via Telnet or serial port, and a Cannot assign valid
AD at the login session error occurs.
.

Activate the same PDCM Matrix from
When activating a saved PDCM Matrix from activate CUP Port Web Tools with Active=Save
Connectivity Configuration dialog in Web Tools, with Act- Mode check from Edit CUP Port
ive=Save Mode checked, Web Tools displays an error. Connectivity configuration
window.
Workaround prior to upgrade: The

switch name can be displayed from
c-Class Onboard Administrator is unable to read the switchname Fabric OS CLI command
for Brocade 8Gb SAN Switch for HP BladeSystem c-Class. switchname
Workaround prior to upgrade: Stop

End-to-end data frames in one direction of bidirectional I/O not re- and restart I/O may recover.
covered after switchdisable and switchenable on a Base switch.
Unexpected software call traceback error messages occasionally being

displayed on DC04 console.
Frame drops sometimes occur when a trunk port comes online, even
with Lossless DLS feature enabled.
Interactive mode stores supportsave files in switch root directory

rather than the USB device, which can also result in compact flash Fixed in Fabric OS 6.2.0b.
storage overflow.

42

Storageworks 48 San Switch

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Storageworks 48 San Switch

Uploaded by

Copyright:

Available Formats

HP StorageWorks Fabric OS 6.2.

Part number: 5697-0352

Downloaded from www.Manualslib.com manuals search engine

Downloaded from www.Manualslib.com manuals search engine

HP StorageWorks Fabric OS 6.2.0b release notes 3

Downloaded from www.Manualslib.com manuals search engine

New feature descriptions

Downloaded from www.Manualslib.com manuals search engine

Optionally licensed software

HP StorageWorks Fabric OS 6.2.0b release notes 5

Downloaded from www.Manualslib.com manuals search engine

Included licensed software

Temporary license support

Downloaded from www.Manualslib.com manuals search engine

HP StorageWorks Fabric OS 6.2.0b release notes 7

Downloaded from www.Manualslib.com manuals search engine

New hardware support

Supported product models

Downloaded from www.Manualslib.com manuals search engine

HP StorageWorks Fabric OS 6.2.0b release notes 9

Downloaded from www.Manualslib.com manuals search engine

Access Gateway support

Downloaded from www.Manualslib.com manuals search engine

Access Gateway support in non-Brocade fabrics

HP StorageWorks Fabric OS 6.2.0b release notes 11

Downloaded from www.Manualslib.com manuals search engine

Zoning and fabric operations

Table 1 Supported Fabric OS versions

Model Earliest compatible version Recommended version

Not supported, end of sup-

HP StorageWorks SAN Switch 2/8 EL

HP StorageWorks SAN Switch 2/16

HP StorageWorks Core Switch 2/64

HP StorageWorks SAN Director 2/128 in Chassis 5.0.5e 5.0.5f

Downloaded from www.Manualslib.com manuals search engine

Brocade 4-Gb SAN Switch for HP p-Class

HP StorageWorks 48 Port 4-Gb Blade (FC4-48) 5.3.1 6.2.0b

HP StorageWorks B-Series iSCSI Director Blade

HP StorageWorks 4/32B SAN Switch 5.3.1 6.2.0b

HP StorageWorks MP Router XPath OS 7.4.1d XPath OS 7.4.1e

HP StorageWorks DC SAN Backbone Director 6.0.0b 6.2.0b

HP StorageWorks SAN Director 16 Port 8-Gb FC

HP StorageWorks SAN Director 32 Port 8-Gb FC

HP StorageWorks SAN Director 48 Port 8-Gb FC

HP StorageWorks SAN Director 6 Port 10-Gb ISL

Fabric Manager1 5.2.0a 5.5

Data Center Fabric Manager 10.0.2 10.1.0

HP StorageWorks Encryption SAN Switch 6.2.0b 6.2.0b

HP DC Switch Encryption FC blade 6.2.0b 6.2.0b

HP StorageWorks Fabric OS 6.2.0b release notes 13

Downloaded from www.Manualslib.com manuals search engine

Director blade Number of blades

FC4-16IP (iSCSI blade) Up to four blades of this type

Up to two blades of this type. Up to eight FR4-18i blades

DC SAN Backbone and DC04 SAN Director blade support

Director blade Number of blades

Not supported with the DC SAN Director Backbone, or

Supported with Fabric OS 6.0.0b and later with a

Supported with Fabric OS 6.2.0b and later with a maxim-

Downloaded from www.Manualslib.com manuals search engine

Table 4 Power supplies required for blades in Director chassis

Director blade 4/256 SAN Director DC SAN Backbone Director and

Two power supplies. The FC4-16IP