advertisement
HP Fabric OS 6.2.2e Release Notes
HP Part Number: 5697-0809
Published: February 2011
Edition: First
© Copyright 2011 Hewlett-Packard Development Company, L.P.
© Copyright 2011 Brocade Communications Systems, Incorporated
Version
6.2.2e
NOTE: This software conforms to the Fibre Channel (FC) standards and accepted engineering practices and procedures.
Description
Fabric OS 6.2.0b introduced support for the HP StorageWorks Encryption SAN Switch and the
HP DC Switch Encryption FC Blade. Fabric OS 6.2.2e continues this support. 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 (which continue to be supported with this release):
•
Support for the 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 ports)
◦ Supports existing 10-Gb 6 port ISL blade
◦ Supports existing Multi-protocol (MP) Router blade
◦ Supports inter-chassis link (ICL) connectivity to other DC04 SAN Directors and DC SAN
Backbone Directors
•
Virtual Fabrics (VFs)
◦ 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 that 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 providing connectivity for multiple logical fabrics
•
FC Routing (FCR) and FCIP enhancements
◦ FCIP (SCSI) read tape pipelining
◦ Serial Over TCP (SOTCP) enhancements
◦ Logical storage area network (LSAN) tagging
◦ Support for Pathinfo over MetaSAN
◦ Use Fabric Shortest Path First (FSPF) cost in the FCR backbone fabric to find the shortest path to the edge fabric
◦ In-band management link over FCIP connections for HP StorageWorks 400 MP 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 of temporary licenses for Adaptive Networking, Integrated Routing, and Fabric Watch
Version 3
•
Security enhancements
◦ IPv6 auto-configuration
◦ IPsec with IPv6 (for management port)
◦ Configurable switch-wide policy requiring authentication of all host bus adapters (HBAs)
◦ Remote Authentication Dial-In User Service (RADIUS) enhancements allowing password expiration and source IP address information
◦ LDAP enhancement allowing for an alternate domain userPrincipalName (UPN)
◦ IPv6 certified for Joint Interoperability Test Command (JITC) Approved Product List
•
Fiber connectivity (FICON) enhancements
◦ Request Node Identification Data (RNID) support for control unit port (CUP)
◦ New FC addressing modes for support with VF
◦ Support for HP StorageWorks SAN Director 48 Port 8-Gb FC Blade with VF-enabled HP
StorageWorks DC SAN Backbone Director and DC04 SAN Director for FICON environments
NOTE: For information on specific versions of Fabric OS supported for FICON, see the
B-series FICON Connectivity Stream.
•
Access Gateway (AG) 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 the M-EOS 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 features/enhancements added with Fabric OS 6.2.2b:
•
New parameter implemented in configurechassis command to allow adjustment of SFP polling during high CPU load situations
Update recommendation
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. If DCFM is not running on your fabric, HP recommends that you review
(page 28) before you upgrade to Fabric OS 6.1.1x or later, and take note of what has changed so you can assess the impact on your fabric.
All products supported by Fabric OS 6.0.x can be upgraded to Fabric OS 6.2.2e. If applicable,
HP recommends that you upgrade to Fabric OS 6.2.2e as soon as possible to take advantage of the latest fixes and features.
For more information, see “Firmware upgrades and downgrades” (page 19) .
4
Supersedes
Fabric OS 6.2.2d, released October 2010
New feature descriptions
This section describes new features introduced in Fabric OS 6.2.0a and carried forward with
Fabric OS 6.2.2e.
Virtual Fabrics
•
VF is 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. When 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 logical switch is managed as a completely independent layer 2 FC switch, and can be deployed in independent fabrics known as logical fabrics.
•
VF allows the user to create a special logical switch known as the base switch, which is used for connectivity to other base switches and also as a backbone fabric for FCR. Individual logical fabrics can 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.
•
VF is part of the base Fabric OS and does not require a license. VF 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 by 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 the FCR backbone fabric uses the most efficient route to reach a destination fabric, preventing the use of an FCIP link when an ISL is available.
•
In-band management link over FCIP connections for the 400 MP Router allows a management station to communicate with a remote 400 MP Router through the GE ports. This allows a single management station located on the WAN side of the 400 MP Router to communicate with the management interface on the CP for management tasks such as firmware downloads,
SNMP polling, SNMP traps, troubleshooting, 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 Domain ID (DID) setting.
New feature descriptions 5
6
NOTE: For information on specific switches and switch firmware supported for interop applications, see the HP StorageWorks Fabric Interoperability: Merging Fabrics Based on M-series and B-series
Fibre Channel Switches Application Notes.
Security enhancements
•
Configurable stateless IPv6 auto-configuration is supported.
•
IPsec with IPv6 support provides greater security for management ports and configurable security policies for IPv4/IPv6 addresses.
•
A switch-wide policy requiring HBA authentication requires that the FC-SP bit be set during
Fabric login (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 specify how many days in advance they should be notified of password expiration.
•
An LDAP enhancement adds the ability to provide an alternate UPN to domain authentication.
Port beaconing support
The portBeacon CLI command was added in Fabric OS 6.2.1. It allows individual ports to be identified by enabling a special LED function. The portBeacon command has the following characteristics:
•
Function: Sets port beaconing mode on or off.
•
Syntax: portbeacon -–mode [slot]/port
•
Description: Enables or disables port beaconing mode on a specified port. This command works with 4-Gb (or larger) FC ports, with the exception of the HP StorageWorks SAN Director
6 Port 10-Gb FC ISL Blade (FC10-6).
When beaconing mode is enabled on a port, the port LED flashes amber and green for 2.5
seconds each, in an alternating pattern, and continues until you turn it off. Beaconing mode is useful if you want to locate a specific port.
Beaconing mode takes over the port LEDs. The normal flashing LED pattern associated with an active, fault, or disabled port is suppressed, and only the beaconing pattern is displayed.
Other commands are still executable and functional. However, if diagnostic frame-based tests, such as the portLoopbackTest, are executed, the diagnostic LED pattern is interleaved with the port beaconing pattern.
•
Operands: ––enable turns beaconing mode on; ––disable turns beaconing mode off.
•
Examples:
◦ To turn beaconing mode on: switch:admin> portbeacon ––enable 1/0
◦ To turn beaconing mode off: switch:admin> portbeacon ––disable 2/1
Diagnostics restrictions
The porttest and spinfab commands are not supported on the following ports in Fabric OS
6.2.1 or later:
•
Ports connected to shared-area ports (ports 16–47 on 48-port blades)
•
Ports connected to ports with area swapped
•
ICLs
•
Slave ports in trunk groups
•
Long-distance ports
•
Ports connected to a logical switch and base switch (Fabric OS 6.2.x only), if VF is enabled
Optionally licensed software
The following are optionally licensed features in Fabric OS 6.2.x:
•
Ports on Demand —Allows customers to instantly scale the fabric by provisioning additional ports via a license key upgrade (applies to select switch models).
•
Extended Fabrics —Provides greater than 10 km of switched fabric connectivity at full bandwidth over long distances. (Depending on the platform, the distance can be up to 3,000 km.)
•
ISL Trunking —Provides the ability to aggregate multiple physical links into one logical link for enhanced network performance and fault tolerance. It also includes Access Gateway ISL
Trunking on the products that support Access Gateway deployment.
•
Advanced Performance Monitoring —Enables performance monitoring of networked storage resources. This license includes the Top Talkers feature.
•
High-Performance Extension over FCIP/FC (formerly known as FC-IP Services)—For the HP
StorageWorks B-series MP Router blade and 400 MP Router, this license key also includes the FC Fast Write (FCFW) 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 the 400 MP
Router and B-series MP Router blade.
•
Fabric Watch —Monitors mission-critical switch operations, and now includes new Port Fencing capabilities.
•
FICON Management Server (also known as CUP)—Enables host control of switches in mainframe environments.
•
ICLs —Provide dedicated high-bandwidth links between two DC SAN Backbone Director or
DC04 SAN Director chassis, without consuming valuable front-end 8-Gb 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 —Allows a user to ensure high priority connections and obtain the network resources necessary for optimum performance, even in congested environments. The quality of service (QoS) SID/DID Prioritization and Ingress Rate Limiting features are the first components of this license, and are available on all 8-Gb platforms.
•
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 FCR. This eliminates the need to add a B-series MP Router blade or use the 400 MP Router for FCR purposes, and also provides double the bandwidth for each FCR connection (when connected to another
8-Gb-capable port).
•
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 data center infrastructure.
Included licensed software
The Enhanced Group Management license is included with all HP 8-Gb switches. Enhanced Group
Management enables full management of the device in a data center fabric with increased element management functionality and management task aggregation throughout the environment. This license is used in conjunction with DCFM application software.
New feature descriptions 7
Temporary license support
HP now supports temporary licenses or Universal Temporary Licenses. To obtain the Universal
Temporary Licenses, select the StorageWorks Software Demo & Evaluation Downloads option at the HP website: http://www.software.hp.com
Previously licensed software now included with base Fabric OS
The capabilities described in this section are included as part of the base Fabric OS. No additional purchase or licensing is necessary.
NOTE: Advanced Zoning and Web Tools licenses are no longer necessary. These features are enabled automatically on all products running Fabric OS 6.1 or later.
Standards compliance
This software conforms to the FC standards and 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, see the HP website: http://www.hp.com
.
New hardware support
Support for the HP StorageWorks DC04 SAN Director was introduced with Fabric OS 6.2.0a.
The DC04 SAN Director:
•
Has 192 ports, 8 Gb/s technology in an 8U chassis with horizontal slots (9U with standard port side airflow kit)
•
Supports HP StorageWorks SAN Director 16 Port 8-Gb FC Blade, SAN Director 32 Port 8-Gb
FC Blade, and SAN Director 48 Port 8-Gb FC Blade
•
Supports all special-purpose blades available for the DC SAN Backbone Director
•
Supports ICL connectivity to other DC04 SAN Director or DC SAN Backbone Director chassis
Fabric OS 6.2.0b introduced support for the HP StorageWorks Encryption SAN Switch and the
DC Switch Encryption FC Blade. The encryption switch provides:
•
48 Gb/s of encryption processing power, upgradeable to 96 Gb/s
•
Industry standard AES-256 algorithms for data-at-rest encryption
•
32 FC ports, 8 Gb/s in 2U form factor
•
Integration with HP StorageWorks SKM
The encryption blade provides 16 ports and is supported in the DC SAN Backbone Director and
DC04 SAN Director.
NOTE: The encryption switch and encryption blade are unique products compared to standard
FC switches. HP highly recommends that you read the Fabric OS Encryption Administrator's Guide before configuring these products in any fabric.
8
Supported product models
The following product models can be upgraded to Fabric OS 6.2.2e:
•
HP StorageWorks 4/8 SAN Switch and 4/16 SAN Switch (Brocade 200E)
•
HP StorageWorks 4/32 SAN Switch (Brocade 4100)
•
HP StorageWorks 4/32B SAN Switch (Brocade 5000)
•
HP StorageWorks 4/64 SAN Switch (Brocade 4900)
•
HP StorageWorks 4/256 SAN Director (Brocade 48000)
•
HP StorageWorks 16 Port 4-Gb Blade (FC4-16)
•
HP StorageWorks 32 Port 4-Gb Blade (FC4-32)
•
HP StorageWorks 4/48 SAN Director Blade (FC4-48)
•
HP StorageWorks Multi-Protocol Router Blade (Brocade FR4-18i)
•
HP StorageWorks 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)
•
HP StorageWorks 8/8 and 8/24 SAN Switches (Brocade 300)
•
HP StorageWorks 8/40 SAN Switch (Brocade 5100)
•
HP StorageWorks 8/80 SAN Switch (Brocade 5300)
•
HP StorageWorks 400 Multi-protocol Router (Brocade 7500)
•
HP StorageWorks Encryption SAN Switch (Brocade BES)
•
HP StorageWorks DC04 SAN Director (Brocade DCX-4S)
•
HP StorageWorks DC SAN Backbone Director (Brocade DCX)
•
HP StorageWorks SAN Director 16 Port 8-Gb FC Blade (Brocade FC8-16)
•
HP StorageWorks SAN Director 32 Port 8-Gb FC Blade (Brocade FC8-32)
•
HP StorageWorks SAN Director 48 Port 8-Gb FC Blade (Brocade FC8-48)
•
HP StorageWorks SAN Director 6 Port 10-Gb FC ISL Blade (Brocade FC10-6)
•
HP StorageWorks DC Switch Encryption FC Blade (Brocade FS8-18)
•
HP StorageWorks EVA4400 embedded switch module (Brocade 5410)
•
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)
Unsupported product models
Any products not listed in the “Supported product models” (page 8) section, are unsupported with Fabric OS 6.2.2e.
Devices supported
For a list of supported devices, see the HP website: http://www.hp.com/go/san
Operating systems
For a list of supported 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)
•
Brocade 8-Gb SAN Switch for HP BladeSystem c-Class (Brocade 5480)
•
HP StorageWorks 4/16 SAN Switch (Brocade 200E)
Unsupported product models 9
•
HP StorageWorks 8/24 SAN Switch (Brocade 300)
•
HP StorageWorks 8/40 SAN Switch (Brocade 5100)
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. The 8/40 switch must also have all ports enabled in order to support Access Gateway mode. 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”
(page 9) and also by the following B-series switches:
•
HP StorageWorks SAN Switch 4/32
•
HP StorageWorks SAN Switch 4/32B
•
HP StorageWorks SAN Switch 4/64
•
HP StorageWorks SAN Director 4/256
•
HP StorageWorks SAN Switch 8/80
•
HP StorageWorks DC SAN Backbone Director
•
HP StorageWorks DC04 SAN Director
•
HP StorageWorks 400 Multi-protocol Router
•
HP StorageWorks EVA4400 Embedded Switch Module
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 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.
For more information, see the Brocade Access Gateway Administrator's Guide, available on: http://www.hp.com/go/san
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 switches: 2/12 (ES4300), 2/24 (ES4500), 2/16 (ES3216), 2/32 (ES3232), 2/64
(ED6064), 2/140 (M6140), M4400, Mi10K running EOS 09.07.02 with Brocade Fabric
OS 6.1.0x
•
McDATA switches: 2/12 (ES4300), 2/24 (ES4500), 2/16 (ES3216), 2/32 (ES3232), 2/64
(ED6064), 2/140 (M6140), M4400, Mi10K running EOS 09.09.00 or 09.09.03 with
Brocade Fabric OS 6.2.0x, 6.2.1x, and 6.2.2x
10
•
Cisco switches: MDS 9216, MDS 9216A, MDS 9506, MDS 9509 running SAN OS 3.0(2a) with Brocade Fabric OS 6.1.0x
•
Cisco switches: MDS 9216, MDS 9216A, MDS 9216i, MDS 9506, MDS 9509, MDS 9120,
MDS 9140, MDS 9124, MDS 9134 running SAN OS 3.2(3) with Brocade Fabric OS 6.2.0x,
6.2.1x, and 6.2.2x
Secure Fabric OS feature not compatible with Fabric OS 6.x and later
Fabric OS 5.3.x is the last Fabric OS version 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.
For environments with SFOS installed on switches that cannot be upgraded to Fabric OS 5.3 or later version, FC routing can be used to interoperate with Fabric OS 6.2.2e.
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 through 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: Do not configure zoning through a switch operating with Fabric OS 3.x in a fabric that has products operating with newer versions of Fabric OS.
Prerequisites
Table 1 (page 11) lists the supported Fabric OS firmware versions. HP recommends using the latest supported firmware 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 (page 11) are the earliest versions supported by HP for connection to switches running
Fabric OS 6.2.2e at the time of its release.
Table 1 Supported Fabric OS versions
Model
HP StorageWorks 1-Gb Switch
HP StorageWorks MSA SAN Switch 2/8
HP StorageWorks SAN Switch 2/8 EL
HP StorageWorks SAN Switch 2/16
HP StorageWorks SAN Switch 2/16 EL
HP StorageWorks Core Switch 2/64
HP StorageWorks SAN Director 2/128 in Chassis configuration modes 3 and 4 only
Earliest compatible version
Not supported (support ended
December 2007)
3.2.1c
Not supported (support ended
September 2009)
Recommended version
N/A
3.2.1c
1, 5, 7
N/A
HP StorageWorks SAN Switch 2/8V
HP StorageWorks SAN Switch 2/16V
HP StorageWorks SAN Switch 2/32
HP StorageWorks SAN Director 2/128
5.3.2b
5.3.2c
Secure Fabric OS feature not compatible with Fabric OS 6.x and later 11
12
Table 1 Supported Fabric OS versions (continued)
Model
HP StorageWorks 4/8 SAN Switch
HP StorageWorks 4/16 SAN Switch
Earliest compatible version
6.2.1b
HP StorageWorks 4/256 SAN Director
HP StorageWorks 4/64 SAN Switch
HP StorageWorks Multi-Protocol Router Blade
(FR4-18i)
6
HP StorageWorks 16 Port 4-Gb Blade (FC4-16)
HP StorageWorks 32 Port 4-Gb Blade (FC4-32)
HP StorageWorks 48 Port 4-Gb Blade (FC4-48)
HP StorageWorks 400 MP Router
6
HP StorageWorks 4/32 SAN Switch
HP StorageWorks 4/32B SAN Switch
HP StorageWorks iSCSI Director Blade (FC4-16IP)
6.2.1b
Brocade 4-Gb SAN Switch for HP p-Class BladeSystem
Brocade 4-Gb SAN Switch for HP c-Class BladeSystem
6.2.1b
HP StorageWorks MP Router XPath OS 7.4.1e
HP StorageWorks DC SAN Backbone Director 6.2.1b
Brocade 8-Gb SAN Switch for HP BladeSystem c-Class 6.2.1b
6.2.1b
HP StorageWorks EVA4400 embedded switch module, 8-Gb Brocade
HP StorageWorks DC04 SAN Director 6.2.1b
6.2.1b
HP StorageWorks SAN Director 16 Port 8-Gb FC
Blade (FC8-16)
HP StorageWorks SAN Director 32 Port 8-Gb FC
Blade (FC8-32)
HP StorageWorks SAN Director 48 Port 8-Gb FC
Blade (FC8-48)
HP StorageWorks SAN Director 6 Port 10-Gb ISL
Blade (FC10-6)
HP StorageWorks 8/8 SAN Switch
HP StorageWorks 8/24 SAN Switch
HP StorageWorks 8/40 SAN Switch
HP StorageWorks 8/80 SAN Switch
6.2.1b
6.2.1b
HP StorageWorks Encryption SAN Switch 6.21b
HP DC Switch Encryption FC Blade
Mi10k
HP StorageWorks Director 2/140 and 2/64
HP StorageWorks Edge Switch 2/32, 2/12 and 2/24
M4400, M4700 (McDATA Fabric Mode and Open
Fabric Mode)
2, 4
6.2.1b
M-EOS 9.9.5
3
Fabric Manager
8
Data Center Fabric Manager
5.2.0a
10.1.4
Recommended version
6.2.2e
6.4.1a
6.2.2e
XPath OS 7.4.1f
6
6.4.1a
6.4.1a
6.4.1a
6.4.1a
6.4.1a
6.4.1a
6.4.1a
6.4.1a
6.4.1a
M-EOS 9.9.8 or later
3
5.5
10.4.2
Table notes:
1
In a fabric with products running older versions of Fabric OS, all zoning and fabric operations must be performed using interfaces to products running the latest version of Fabric OS. This is important for Brocade 3xxx series switches that do not support zoning configuration for newer products.
2
Other M-EOS models can participate in a fabric with Fabric OS 6.2; however, they cannot be attached directly to any products running Fabric OS 6.2 via an E_Port. For information about HP support of interoperable fabrics, see HP StorageWorks Merging Fabrics Based on M-series and
B-series Fibre Channel Switches Application Notes, available at http://www.hp.com
.
3
HP strongly recommends that M-EOS products operate with the most recent version of M-EOS that supports interoperability. For information about HP support of interoperable fabrics, see HP
StorageWorks Merging Fabrics Based on M-series and B-series Fibre Channel Switches Application
Notes, available at http://www.hp.com
.
4
When routing to an M-EOS edge fabric using frame redirection, the fabric must have a Fabric
OS-based product to configure the frame redirection zone information.
5
Products operating with Fabric OS versions earlier than 5.3.1b or 6.1.0e cannot participate in a logical fabric that is using XISLs (in the base fabric).
6
SANRouters 1620 and 2640 must not be used with XPath or Fabric OS-based routing (FCR) for connections to the same edge fabric.
7
These platforms cannot be attached directly to hosts or targets for encryption flows.
8
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 upgrade to DCFM 10.4.x because it includes Admin Domain support, although some support is limited. For more information, see the Data Center Fabric Manager User
Guide for 10.4.x.
4/256 SAN Director blade support
Fabric OS 6.2.2e is fully qualified and supports the Director blades listed in Table 2 (page 13) .
Table 2 4/256 SAN Director blade support matrix
Director blade
FC4-16
FC4-32
FC4-48
FC8-16
FC8-32
FC8-48
FC10-6
Number of blades
Supported with any mix with up to eight blades of each type. No intermix restrictions. The 4/256 SAN Director must run Fabric OS
6.0.0b or later to support the FC8-16 port blade, and Fabric OS
6.1.0a or later to support the FC8-32 and FC8-48 port blades.
FC4-16IP (iSCSI blade)
FR4-18i (FCIP/FC Router blade)
Up to four blades of this type
Up to two blades of this type. Up to eight FR4-18i blades can be installed if they are used only for FC Fast Write or FCIP without routing.
4/256 SAN Director blade support 13
DC SAN Backbone and DC04 SAN Director blade support
Fabric OS 6.2.2e is fully qualified and supports the DC Director blades listed in Table 3 (page
14) .
Table 3 DC Director blade support matrix
Director blade
FC8-16
FC8-32
FC8-48
FC10-6
Number of blades
Supported with Fabric OS 6.0.0b or later with any mix, with up to eight blades of each type on the DC SAN Backbone Director.
There are no intermix restrictions. The DC04 SAN Director requires
Fabric OS 6.2.0a or later, and supports up to four blades.
FC4-16IP (iSCSI blade)
FR4-18i (FCIP/FC Router blade)
FS8-18 (DC Switch Encryption FC blade)
Not supported with the DC SAN Backbone Director or DC04 SAN
Director
Supported with Fabric OS 6.0.0b or later, with a maximum of four blades of this type on the DC SAN Backbone Director. Up to eight
FR4-18i blades can be installed if they are used only for FC Fast
Write or FCIP without routing in the DC SAN Backbone Director.
The DC04 SAN Director requires Fabric OS 6.2.0a or later, and supports up to four blades.
Supported with Fabric OS 6.2.0b or later, with a maximum of four blades of this type on the DC SAN Backbone Director or DC04
SAN Director
Power supply requirements for Director blades
Table 4 (page 14) 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
FC4-16
FC4-32
FC4-48
FC8-16
FC8-32
4/256 SAN Director
Two power supplies
DC SAN Backbone Director and DC04 SAN
Director
1
Two power supplies
FC8-48
FC10-6
Four power supplies Two power supplies
14
Table 4 Power supplies required for blades in director chassis (continued)
Director blade
FR4-18i (FCIP/FC Router blade)
FC4-16IP (iSCSI blade)
FS8-18 (DC Switch Encryption FC blade)
4/256 SAN Director
Four power supplies
Not supported
DC SAN Backbone Director and DC04 SAN
Director
1
Two power supplies. The FC4-16IP blades are not supported in the DC SAN Backbone Director and DC04 SAN Director.
• A DC SAN Backbone Director with 3 or more
FS8-18 blades, requires (2+2) 220 VAC power supplies for redundancy.
• A DC SAN Backbone Director with 1 or 2
FS8-18 blades, requires (2) 220 VAC power supplies for redundancy.
•
The DC04 SAN Director requires (2) 220
VAC power supplies to provide redundant configuration with any number of FS8-18 blades.
1 The DC Director can operate with nominal power of 110 VAC. See the appropriate hardware reference guide for power specifications. FC10-6, FC8-48, FR4-18i and FS8-18 are not supported in the DC SAN or DC04 SAN Directors in a 110 VAC configuration.
FC 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.
New OUI Support on B-Series platforms
Overview
The OUI (Organizationally Unique Identifier) value is part of a Fibre Channel WWN that uniquely identifies the manufacturer of Fibre Channel products. The OUI values assigned to Brocade are used by Fabric OS to validate certain fabric interoperability support.
The currently assigned OUI/WWN values are nearing exhaustion, necessitating Brocade to use a new OUI value for WWN assignment. The new OUI value for Brocade is 00:05:33 . A WWN of 10:00: 00:05:33 :41:5c:c1 , for example, demonstrates the usage of the new OUI. WWNs with the current OUI value are expected to be consumed by mid-2010. Brocade factory shipments of switches after this time will have WWNs that include the new OUI.
Fabric OS 6.2.2b has been enhanced to recognize the new Brocade OUI value to guarantee proper functionality. It is important to note that no switch with the new OUI/WWN should be downgraded to a version of Fabric OS that does not recognize this new OUI. It is also important to note that specific minimum requirements for recognition of the new OUI will neither be validated nor enforced by Fabric OS.
Impact of products with the new OUI to existing fabrics/environments
In most situations, a switch that uses the new OUI can be seamlessly added to an existing fabric, even if the other switches in that fabric are not using Fabric OS versions that are aware of the new
FC Routing scalability 15
OUI value. However, there are some exceptions and limitations to consider before adding a switch utilizing the new OUI to an existing fabric or environment.
•
Fabrics with encryption products: If an HP StorageWorks encryption switch or blade using the new OUI is added to an edge fabric of a Fibre Channel routed fabric, Frame Redirection capability could be impacted across the FCR backbone, thus impacting the encryption functionality. Therefore, the FC routers in the FCR backbone fabric will need to be upgraded to a firmware version that supports the new OUI.
•
Interopmode 2 and 3 fabrics: In an interopmode 2 or 3 fabric with VE ports, the switches on both ends of the VE link must run a firmware version that supports the new OUI, or the VE ports may not function correctly, resulting in unpredictable behavior.
DCFM compatibility
Fabric OS 6.2.2e is fully compatible with DCFM 10.1.x, 10.3.x, and 10.4.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).
Starting with DCFM 10.3.0, DCFM is available in three versions:
•
DCFM Professional —Bundled with B-series switches, it is ideally suited for small- and medium-sized businesses that need a lightweight management product to manage their smaller fabrics (one physical fabric at a time, up to 1,000 ports).
•
DCFM Professional Plus —Designed for medium-sized businesses or departmental storage networks, it features support for up to 4 fabrics and 2,560 ports.
•
DCFM Enterprise —Designed for enterprise-class customers, it showcases unparalleled performance and scalability (24 physical fabrics, up to 9,000 switch ports). This is the only version of DCFM that supports the HP StorageWorks DC SAN Backbone Director and FICON.
DCFM Enterprise configures and manages DC SAN Backbone Directors, along with other
B-series directors, routers, switches, and HBAs. Existing EFCM and FM customers that have active Maintenance and Support contracts are provided a seamless migration path to DCFM
Enterprise.
EFCM and FM compatibility
With the introduction of DCFM, both EFCM and FM have been put into sustaining mode. Significant compatibility issues exist between FM and Fabric OS 6.1.1 and later, including (but not limited to) compromised functionality in the zoning dialog and performance graphs, port enabling/disabling, and FICON wizard. HP strongly recommends that customers migrate from these products to DCFM Enterprise.
Fabric OS compatibility
(page 11) lists the earliest versions of software supported in this release, that is, the earliest supported software versions that interoperate. HP recommends using the latest software versions to get the greatest benefit from the SAN.
When using the new VF feature, 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 the minimum firmware levels noted in the Fabric OS Interoperability table.
16
When using either the HP StorageWorks Encryption SAN Switch or the HP StorageWorks DC
Switch Encryption FC Blade, switches attached to hosts and targets, or switches that are part of the encryption flow, must operate with the following minimum levels:
•
2-Gb platforms must operate with Fabric OS 5.3.2b or later.
•
4-Gb and 8-Gb platforms must operate with Fabric OS 6.1.0h, 6.1.2a, or later.
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 supported by Fabric
OS 6.2.2e support both interopmodes 2 and 3, with the exception of the 4/32 SAN Switch.
NOTE: HP may not support all of these switches in this mode. For information about support in interopmodes 2 and 3, see the HP StorageWorks Fabric Interoperability: Merging Fabrics Based
on M-series and B-series Fibre Channel Switches Application Notes, available at http:// www.hp.com
.
Table 5 (page 17) specifies the support of Fabric OS features when operating in either interopmode
2 (McDATA Fabric Mode) or interopmode 3 (Open Fabric Mode) with Fabric OS 6.2.2e.
Table 5 Feature support in interopmodes 2 and 3
Fabric OS Features (supported in interopmode 0)
IM = interopmode
L2 Fabric OS Hot Code Load
Fabric OS Hot Code Load with FCR
Zone Activation Support
Traffic Isolation Zones
1
Frame Redirection (devices attached to Fabric OS)
1
Frame Redirection (devices attached to M-EOS)
1
Frame Redirection over FCR
10
FCR Fabric Binding (route to M-EOS fabric with Fabric Binding)
9
L2 Fabric Binding
DCC policies
SCC policies
E/Ex_Port Authentication
ISL Trunking (frame level)
Dynamic Path Selection (DPS, exchange-based routing)
Dynamic Load Sharing (DLS, port-based routing)
Virtual Channels (VC RDY)
FICON Management Server (Cascading)
FICON MIHPTO
Full Scalability (to maximum M-EOS fabric limits)
Adaptive Networking QoS
Adaptive Networking: Ingress Rate Limiting
Yes
Yes
Yes
No
No*
Yes
Yes
2
Yes
3
Yes
Yes
2
Yes
Yes
No
Yes
4
Yes
Yes
Yes
Yes
Fabric OS 6.2.2e
IM 2 IM 3
Yes
Yes
Yes
Yes
Yes
Yes
11
No
Yes
11
Yes
11
Yes
11
Yes
No*
No
No*
Yes
Yes
2
Yes
3
Yes
Yes
2
No*
No*
Yes
No
No*
Fabric OS feature compatibility in native connectivity modes 17
18
Table 5 Feature support in interopmodes 2 and 3 (continued)
Fabric OS Features (supported in interopmode 0)
IM = interopmode
Advanced Performance Monitoring (APM)
APM: Top Talkers
Admin Domains
Secure Fabric OS
5
Fabric Watch
Ports on Demand (POD)
NPIV
Timer Server Function (NTP)
Open E_Port
6
Broadcast Zoning
FDMI
Remote Switch
Port Mirroring
Extended Fabrics
Alias Server
Platform Service
FCIP (VE_Ports)
IPFC (IP over FC)
M-EOS ALPA 0x13 configuration
VE_Port to VEX_Port
Integrated Routing
9
Domain Offset Support
239 Domain Support (available on Mi10k only)
Yes
Yes
Yes
No
N/A
No
No
Yes
Yes
8
No
No
No
Yes
Yes
Yes
Yes
Yes
No
No*
No*
No
N/A
N/A
Fabric OS 6.2.2e
IM 2 IM 3
Yes
Yes
Yes
No
No*
No*
No
N/A
N/A
No
No
No
Yes
Yes
7
No
No
Yes
Yes
8
Yes
Yes
Yes
No
Yes
12
Masterless F_Port Trunking (AG connect to Fabric OS switches only)
FC10-6 to FC10-6 ISL
RASLog Events on duplicate WWNs
Virtual Fabrics
Logical Fabric using LISLs (XISLs in base Fabric)
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
No
*
Indicates that the feature is available, but not officially tested or supported.
1
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.
2
Allowed only between Fabric OS-based switches.
3
DPS is supported outbound from Fabric OS-based switches. M-EOS can provide reciprocal load balancing using Open Trunking.
4
SCC policies supported only in conjunction with L2 Fabric Binding support.
5
Not supported in Fabric OS 6.0 or later.
6
Mode 3 qualified only with M-EOS switches.
7
Not on FCR.
8
Supported only locally within the Fabric OS switch.
9
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 operate in IM 2 or IM 3.
10
To support Frame Redirection to an edge M-EOS fabric, there must be at least one Fabric OS switch in the edge fabric to configure Frame Redirection Zones.
11
12
Only Frame Redirection 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.
Supported through FCR only. All routers in the backbone must be running Fabric OS 6.2.x.
NOTE: FICON Cascaded CUP is qualified only on select platforms.
Firmware upgrades and downgrades
Upgrading to Fabric OS 6.2.2e 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, ensuring a truly seamless and nondisruptive 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 DC04 SAN Director cannot be downgraded to a release earlier than Fabric OS 6.2.0a.
All downgrades from Fabric OS 6.2.x to Fabric OS 6.1.x require a restart and are disruptive to traffic. Platforms supporting VF must have the feature disabled before downgrading to a release earlier than 6.2.0a. When downgrading from Fabric OS 6.2.x to 6.1, configuration parameters
(such as the switch name) are not persisted in Fabric OS 6.2.
To ensure nondisruptive Hot Code Load (HCL), neighbor switches should be operating with Fabric
OS 6.2.0a or later before loading Fabric OS 6.2.2e on the following platforms:
•
Brocade 4Gb SAN Switch for HP p-Class BladeSystem
•
Brocade 4Gb SAN Switch for HP c-Class BladeSystem
•
HP StorageWorks SAN Switch 4/32
•
HP StorageWorks 4/8 and 4/16 SAN Switches
When upgrading to Fabric OS 6.2.2e 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 this new version. This is normal behavior and the firmware upgrade is not disruptive.
Fabric OS 6.2.2e does not support concurrent FC Routing (EX_Ports) and Top Talkers features.
Before upgrading to this version, you must disable one of these features.
Only products based on 4-Gb and 8-Gb-capable ASICs are supported by Fabric OS 6.2.2e. Older products using previous generation 2-Gb ASICs will remain on the 5.x code stream. Fabric OS
5.x is fully compatible in fabrics running Fabric OS 6.2.x and for routing.
For routed SANs with M-EOS switches in an edge fabric, upgrades to Fabric OS 6.2.2e are nondisruptive if all EX_Ports to M-EOS edge fabrics are attached to 4/256 SAN Directors with an
MP Router blade (FR4-18i).
Fabric OS feature compatibility in native connectivity modes 19
The HP StorageWorks DC SAN Director with HP StorageWorks DC Switch Encryption FC Blade and the HP StorageWorks Encryption SAN Switch cannot be downgraded to a version earlier than Fabric OS 6.2.0b.
After upgrading the Encryption SAN Switch and the DC SAN Director with DC Switch Encryption
FC Blade to Fabric OS 6.2.2e, you cannot downgrade them to a version earlier than Fabric OS
6.2.0d if HP SKM key vault is configured. Doing so will result in the loss of encryption services in
HP SKM environments.
If there are multiple node EGs in a fabric, complete the firmware download on one node at a time before downloading on another node.
On the HP StorageWorks 8/8 and 8/24 SAN Switches and the Brocade 8Gb SAN Switch for
HP BladeSystem c-Class, do not use the -n option to downgrade from Fabric OS 6.2.2e to a version earlier than 6.2.x. Using the -n option can cause the firmware versions to get out of sync, resulting in rolling kernel panics. The switch will not recover and you will need to return it to your supplier for repair via RMA. Switches using Integrated Routing and Fabric OS 6.2.2e cannot be upgraded to Fabric OS 6.3.x versions earlier than 6.3.0d.
Firmware upgrade instructions
IMPORTANT: HP recommends that users upgrade to Fabric OS 6.2.2e as soon as possible.
Upgrading to Fabric OS 6.2.2e is allowed only from Fabric OS 6.1.x. For guidelines, see
(page 4) .
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. If you are not running
DCFM on your fabric, HP recommends that before upgrading to Fabric OS 6.2.x or later, you review (page 28) and note what has changed in order to assess the impact to your fabric.
To access the latest Fabric OS 6.2.2e firmware, configuration files, and MIB files, see the HP website: http://www.hp.com/support/downloads
At the website:
1.
Under 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 .
4.
Select V6.x Firmware for HP StorageWorks B-series FC Switches for Fabric OS 6.2.2e:
•
To download the firmware, select Download .
•
To read the release notes, select the Release Notes tab.
To verify that the firmware download is complete, enter the firmwareDownloadStatus command on the switch, verify that the process is complete, and then proceed to the next switch.
Scalability
For details on supported scalability, see the HP StorageWorks SAN Design Reference Guide, available on the HP website: http://www.hp.com
FICON support
The HP StorageWorks DC04 SAN Director is not supported for FICON Cascading in interopmode
2 or 3 for use in mixed fabrics with M-EOS platforms.
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 VF-capable platforms, the VF feature must be enabled after upgrading to Fabric OS 6.2.x
in order to utilize the related capabilities, including Logical Switches and Logical Fabrics.
•
When creating Logical Fabrics that include switches that are not VF-capable, it is possible to have two Logical Switches with different FIDs in the same fabric. Be sure 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 nondisruptive 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 1 MB.
•
A switch with VF enabled cannot use Port Mirroring or participate in a fabric that uses IP filter or password database distribution or administrative domains. You must disable the VF feature before deploying it in a fabric that uses these features.
Licensing behavior
When operating a switch with Fabric OS 6.2.x, some licenses may be displayed as Unknown .
This is due to changes in licensing requirements for some features that no longer require a license key and may still be installed on a switch.
Frame Redirection
The following restriction in Fabric OS 6.2.0x has been removed for Fabric OS 6.2.1 and later.
In Fabric OS 6.2.0, Frame Redirection zoning is not allowed with Default Zoning ( all access in IM 0 and default zone in IM 2). This was allowed in previous releases. There is no software enforcement to block the upgrade.
Adaptive networking/flow-based QoS prioritization
•
When using QoS in a fabric with 4-G ports or switches, Fabric OS 6.0 or later 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 any 8-Gb FC blades in the HP StorageWorks 4/256
SAN Director.
•
Any products that are not capable of operating with Fabric OS 6.0 cannot exist in a fabric with flow-based QoS. Major problems occur if previous-generation 2-Gb 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
Other important notes and recommendations 21
distance configuration for these ports or explicitly disabling QoS on other ports, freeing up buffers for the last four ports.
•
With the Fabric OS 6.2.1 and later firmware upgrade, the default behavior of the Adaptive
Networking QoS feature changes as follows:
◦ Default QoS behavior is disabled on 4-Gb platforms.
◦ Default QoS behavior is disabled on the Extended Fabrics E_Ports on both 4-Gb and
8-Gb platforms.
This fix addressed the following unexpected behaviors that occurred when the Adaptive
Networking QoS feature was enabled by default in earlier Fabric OS releases:
◦ Splitting of a single trunk group into multiple trunk groups upon port toggle, since the toggled ports come online with QoS enabled, while the remaining ports in the trunk group have QoS disabled.
◦ Fewer buffer credits being made available to normal E_Ports after a port toggle, even when QoS is not being utilized.
◦ An unexpected change to a fill-word configuration on an Extended Fabrics E_Port after a port toggle. If an Extended Fabrics E_Port is using IDLE primitives as fill words, and if that port toggles, the fill-word configuration is changed to use ARB primitives.
NOTE: After upgrading to this firmware release, if users want to enable the Adaptive Networking
QoS feature on 4-Gb platforms and on the Extended Fabrics E_Ports on both 4-Gb and 8-Gb platforms, they must do so explicitly through the available user interfaces.
FC Routing
All FCR switches must be running Fabric OS 6.2.1x or later in order to support M-EOS 239 Domain
Mode on the Mi10K.
FCR backbone fabric ID changes
•
With 8-Gb 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 FC 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) must 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.
•
Integrated Routing EX_Ports are supported only in the base switch on a switch with VF enabled.
To test Integrated Routing functionality, first disable the VF feature ( fosconfig --disable vf ).
•
Integrated Routing and Top Talkers cannot run concurrently in Fabric OS 6.2.x. To use
Integrated Routing, be sure to disable Top Talkers before configuring EX_Ports.
22
Access gateway
When in Access Gateway (AG) 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 allows FCS Automatic Distribution only when in strict mode, requiring only switches with Fabric OS 6.0 or later.
FIPS
FIPS mode should not be enabled on the 4/8 and 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.
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, and it can still be enabled on unsupported LS.
•
The pkicert (1.06) utility can cause evm errors. Therefore, each new switch should be isolated from the fabric in non-VF mode to install new certificates.
•
For FIPS mode, certificates must be installed before FIPS activation.
FICON
For the 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.
FL_Port (loop) support
•
The 8-Gb 48 port FC blade now supports the attachment of loop devices in the DC SAN and
DC04 Directors.
•
VF must be enabled on the chassis, and loop devices can be attached only to ports on a
48-port blade assigned to a non-default logical switch operating with the default 10-bit addressing mode. (Loop devices may not be in the default Logical Switch.)
•
A maximum of 144 ports can be used for connectivity to loop devices in a single logical switch in a chassis.
•
Loop devices are supported when attached to ports on the 8-Gb and 4-Gb 16- and 32-port
FC blades, with no new restrictions.
Port Mirroring
•
On the 8/80 SAN Switch, the Port Mirroring feature has a limitation where all port mirror resources must remain in the same ASIC port group. The resources are the configure mirror
Other important notes and recommendations 23
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 VF feature enabled.
10 G interoperability
10 G interop between HP StorageWorks SAN Director 6 Port 10 Gb FC blade and McDATA blades is not supported due to a hardware limitation. However, the SAN Director 6 Port 10 Gb
FC blade is supported in a chassis running in interopmode 2 or 3 (SAN Director 6 Port 10 Gb FC blade to SAN Director 6 Port 10 Gb FC blade connections only). A SAN Director 6 Port 10-Gb
FC blade will not synchronize with a McDATA 10 G blade, but will not negatively impact the system.
Zoning
Beginning with Fabric OS 6.2.0, all WWNs containing uppercase characters are automatically converted to lowercase when associated with a zone alias and stored as part of a saved configuration on a switch. For example, a WWN entered as either AA.BB.CC.DD.EE.FF.GG.HH
or aa.bb.cc.dd.ee.ff.gg.hh when associated with a zone alias will be stored as aa.bb.cc.dd.ee.ff.gg.hh on a switch operating with Fabric OS 6.2.0 or later.
This behavioral change in saved zone alias WWN members does not impact most environments.
However, in a scenario where a switch with a zone alias WWN member with uppercase characters
(saved on the switch with pre-Fabric OS 6.2.0 code) is merged with a switch with the same alias member WWN in lower case characters, the merge fails, because the switches do not recognize these zoning configurations as being the same. For more information and workaround solutions, see the latest Fabric OS Administrator Guide.
Fabric Watch
Core Blade status reporting modification
Fabric Watch has been modified so that Core blade status reporting matches CP blade reporting, rather than status reported by port blades.
Table 6 (page 24) shows the changes.
Table 6 Fabric Watch Blade Status reporting
FE Area
CP
Down
0
Threshold
Marginal
1
Original behavior if one blade is absent or off
New behavior if one blade is absent or off
Core blade
Port blade
0
0
1
1
Switch/Standby CP state will be marginal.
Switch/Core Blade state will be healthy.
Switch/Blade state will be healthy.
No change.
Switch/Core Blade state will be marginal.
No change.
NOTE: If any type of blade goes to a faulty state, the switch/blade state will be marginal.
Port Fencing
•
When the Port Fencing trigger threshold is exceeded for ITW, LR, 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 of approximately 6 seconds) is always ignored to account for expected link transition errors. The port is disabled only upon detection of a second set of
24
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 select the SNMP Trap check box in the
Above row. Making this change in Web Tools disables Port Fencing. If this happens, you must re-enable the Port Fencing bit from the CLI. The Port Fencing feature is not supported for Loss of Sync (LOS) and Link Failure (LF) areas of Port/F-port/E-port classes.
Extended Fabrics and R_RDY flow control
•
Starting with Fabric OS 5.1, the Extended Fabrics feature is supported with R_RDY flow control
(R_RDY flow control mode can be enabled using 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. When 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. In this mode only data virtual channels are available when 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.
8-Gb Link Init and fill words
This section describes the portCfgfillWord command.
Other important notes and recommendations 25
Overview
The FC Physical Interfaces (FC-PI) standard defines the requirements for a physical layer. It considers all aspects of transmit, receive, and cable-plant performance requirements for optical and electrical links. The FC-PI standard has been modified to support new physical-layer variants that operate at higher data rates than those specified in FC-PI-2. The standard enables interoperability of transmitter devices, receiver devices, interconnects, and components from different manufacturers. New variants include support for an 800 MB/s data rate. The previous implementation by Brocade was to use IDLE for Link Init and as fill words, which works for 1-Gb, 2-Gb, 4-Gb, and most 8-Gb devices. However, some of the new 8-Gb devices have problems with the IDLE/IDLE sequence at
8 Gb. 8-Gb switches, HBAs, and smaller mid-range 8-Gb storage devices are using the IDLE/IDLE sequences without any problems. Some of the new 8-Gb devices require that the ARB (FF)/ARB
(FF) sequence have successful Link Initialization. Brocade has developed an implementation of ARB
(FF)/ARB (FF) for initialization and fill words. The portcfgfillword command, first introduced in Fabric OS 6.1.2, configures the ARB(FF)/ARB(FF) implementation.
portCfgFillWord command
The portCfgFillWord command configures the fill word for a single 8-Gb FC port.
•
Syntax: portcfgfillword [slotnumber/]portnumber, mode
•
Description: Use this command to configure the fill word for an 8-Gb FC port. (It does not apply to a non-8-Gb FC port.) This command disables and re-enables the port; the port comes online with the new fill-word setting. The configuration is stored in nonvolatile memory and is persistent across switch reboots and power cycles.
•
Notes: This configuration cannot be set on VE_Ports or VEX_Ports. Use the portCfgShow command to display user-configured fill-word settings. The execution of this command is subject to any Administrative Domain or Virtual Fabric restrictions.
•
Operands: This command has the following operands:
◦ slotnumber —For blade systems only, specifies the slot number of the port to be configured, followed by a slash (/).
◦ portnumber —Specifies the number of the port to be configured, relative to its slot for blade systems. Use the switchShow command to display a list of valid ports.
◦ mode —Specifies the fill word for portnumber . This operand is required. Valid values are as follows:
– 0 —IDLE in Link Init and IDLE as fill word (default)
– 1 —ARB(FF) in Link Init and ARB(FF) as fill word
•
Example: To set the fill word of a port to ARB(FF)-ARB(FF): switch:admin> portcfgfillword 2/3, 1
See also the description of the portCfgShow command in the Fabric OS Command Reference
Manual.
•
Behavior:
◦ Default mode
The only mode of operation in releases earlier than Fabric OS 6.1.2 was the IDLE implementation.
Fabric OS 6.2.0a and 6.2.0b defaulted to ARB(FF)/ARB(FF) for 8-Gb devices.
26
With Fabric OS 6.1.2x and 6.2.0d and later, the default reverted to the IDLE implementation. The new portCfgFillWord command was also implemented beginning with these versions, and enables the user to configure the ARB(FF) configuration.
◦ Existing product
For products in the field, this change has no effect on current configurations. The mode is currently 0, and during a firmware upgrade, the mode will remain 0 and no devices will be impacted. If a new device is added to the configuration, and it requires the ARB sequence, the ports can be configured at that time.
Loading Fabric OS 6.1.2x or later does not automatically change the mode (with the exception of 6.2.0a and 6.2.0b, as noted above). In current configurations, the mode must be changed manually. This does not affect 1-Gb, 2-Gb, or 4-Gb devices. The mode
1 setting has no effect on these devices; it affects only devices that negotiate or are fixed at 8-Gb speeds.
◦ Changing the mode after Fabric OS 6.1.2x has been installed
If you change the mode after installing Fabric OS 6.1.2x or later, with the exception as noted above for 6.2.0a and 6.2.0b, the portCfgFillWord command changes the configuration parameter in accordance with the selected mode, and automatically disables/enables the port for which the command was invoked. Subsequent Link
Initializations will default to the new mode setting).
◦ Other scenarios
The portCfgFillWord command has no effect on 1-Gb, 2-Gb, or 4-Gb devices, but the mode is persistent. If a device attempts to negotiate or is fixed at 8 Gb, the configured mode will take effect. The persistent configuration is on a port-by-port basis; that is, if an
8-Gb device is connected to a 2-Gb or 4-Gb SFP, and that SFP is replaced with an 8-Gb
SFP, then the current behavior of the mode is activated.
◦ The following table provides a portcfgfillword summary:
Fabric OS version
Any Fabric OS earlier than 6.1.2
All 8-Gb switches except 8-Gb SAN
Switch for HP BladeSystem c-Class
All ports set to IDLE.
No ARB(FF) capability.
8-Gb SAN Switch for HP BladeSystem c-Class
All ports set to IDLE.
No ARB(FF) capability.
Note : Fabric OS 6.1.2x is not supported on this switch.
Fabric OS 6.2.0x
earlier than 6.2.0c
ARB(FF) set by default on all ports and cannot be changed.
All ports (internal and external) default to ARB(FF) mode and cannot be changed.
Fabric OS 6.1.2x and
6.2.0c and later
Note : HP does not support Fabric OS
6.1.2c or 6.2.0c.
Added the ability to change portcfgfillword to IDLE or ARB(FF) mode
Added the ability to change portcfgfillword to IDLE or ARB(FF) mode
Note : Fabric OS 6.1.2x is not supported on this switch.
Other important notes and recommendations 27
Fabric OS version
All 8-Gb switches except 8-Gb SAN
Switch for HP BladeSystem c-Class
8-Gb SAN Switch for HP BladeSystem c-Class
Fabric OS 6.1.2x and
6.2.0d through 6.2.x
Regardless of the Fabric OS version that was previously installed, all ports default to IDLE [mode 0]. However if they were changed to ARB(FF) [mode 1] manually, they remain in ARB(FF) mode.
Can be changed by the user.
– If Fabric OS 6.2.0d was factory-installed, all internal ports remain at ARB(FF) [mode 1], and external ports remain in IDLE [mode
0].
– If Fabric OS earlier than 6.2.0d was factory-installed, all internal and external ports remain at IDLE [mode
0]. However, if they were changed to
ARB(FF) [mode 1] manually, then they remain in ARB(FF) mode.
Can be changed by the user.
Mode: 0 — IDLE for Link Init, IDLE for fill word
1 — ARB(FF) for Link Init, ARB(FF) for fill word (NOTE: not supported with XP storage arrays)
•
Updated command message:
When executing the lscfg --create command with the following syntax: switch_128:FID128:admin> lscfg --create 1 About to create switch with fid=1. Please wait... Logical Switch with FID (1) has been successfully created .
You should expect to see the following revised message:
Logical Switch has been created with default configurations. Please configure the Logical Switch with appropriate switch and protocol settings before activating the Logical Switch.
Web Tools functionality moved to DCFM
The functionality that was moved from Web Tools 6.1.1 to DCFM applies to all versions of DCFM and also applies to Fabric OS 6.2.x.
Table 7 (page 28) describes these changes.
Table 7 Web Tools functionality in DCFM
Function
Add unzoned devices
Web Tools 6.1.0
Zone Admin
DCFM
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.
Zone Admin
Analyze zone configuration
Define device alias Zone Admin
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
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.
Configure > Zoning
28
Table 7 Web Tools functionality in DCFM (continued)
Function
Device accessibility matrix
Web Tools 6.1.0
Zone Admin
DCFM
Configure > Zoning
The Compare dialog provides the Storage-Host and
Host-Storage view in a tree representation that is comparable to the Device Accessibility Matrix when all devices are selected.
Fabric events
Fabric summary
FCIP tunnel configuration
1
GigE ports interface
GigE ports route
Non-local switch ports display in zoning tree
Monitor > Fabric events
Reports > Fabric summary
Monitor > Logs > Events
Monitor > Reports > Fabric
Summary report
Port Admin Module, GigE tab Configure > FCIP tunnel
Port Admin Module, GigE tab
Port Admin Module, GigE tab
Zone Admin
Admin Domain
Switch Admin > DCC policies
Performance Monitoring
2
Configure > FCIP tunnel
Configure > FCIP tunnel
Configure > Zoning
Remove offline or inaccessible devices
Zone Admin Configure > Zoning
Replace/Replace All zone members by selecting the offline devices from the zone tree. Offline devices have an unknown overlay badge with good visibility.
Zone database summary ping
Zone Admin Configure > Zoning
Zoning report for both online and offline database
1 Viewing FCIP tunnels is supported in Web Tools 6.1.1, but New, Edit Config, and Delete are available only in DCFM.
2 In Web Tools, non-local switch port id/WWN can be added using text box.
Encryption behavior
•
HP recommends that the encrypted LUN containers be created when all of the nodes/Encryption
Engines (EE) in the Data Encryption Key (DEK)/High Availability Cluster (HAC) are up and enabled.
•
If two EEs are part of a HAC, configure the host/target pair such that they form a multipath from both EEs. Avoid connecting both host/target pairs to the same EE. This connectivity does not provide full redundancy when EE failure results in HAC failover.
•
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).
– When 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 Container 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
Encryption behavior 29
30 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.
•
A new LUN state is available: Disabled (Key not in sync) . This new state indicates re-keying was started on a remote EE but the local EE is not capable of starting rekey because it does not have the KeyID that was used by the remote EE in re-keying (that is, the newest key returned from the key vault does not match with the KeyID used by remote EE). You must use the cryptocfg --discoverLUN <ContainerName> interface to re-enable the LUN only after the keys are properly synced between two key vaults.
Both VMware and clustering technologies use SCSI reservations to control host I/O access to
LUNs. When the HP Encryption Switch/HP Encryption Blade is performing a rekeying operation
(first time encryption or otherwise), it accommodates the use of this methodology. In deployments that have multiple physical initiators accessing a target/LUN from an EE, Fabric OS 6.2x does not have the ability to failover FTE/rekey operations within the EE. Therefore, during FTE/Rekey operations in these environments, only one physical initiator can be allowed to access the target/LUN combination; this is true for all EEs exposing the LUN. If only one initiator has access to a Target/LUN on a particular EE, no configuration modification is required during
FTE/Rekey operations.
•
The cryptocfg -manual_rekey -all command should not be used in environments with multiple encryption engines (encryption blades) installed in a director-class chassis when more than one encryption engine has access to the same LUN. In such situations, use the cryptocfg -manual_rekey CTCLUN NumInitiator PWWN command to manually rekey the LUNs.
•
Avoid changing the configuration of any LUN that belongs to a Crypto Target Container/LUN configuration while the rekeying process for that LUN is active. If the user changes the LUN’s settings during manual or auto, rekeying 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 rekeying processes running in all Crypto Target Containers and corrupts any LUN engaged in a rekeying 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
CTCs, which will in turn remove the associated frame redirection zone information. Make sure to back up all data before taking this action.
•
Before committing configurations or modifications to the CTC or LUNs on an HP encryption switch or 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 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 nondeterministic behavior and may result in faulting of the HP encryption switch or encryption blade.
•
When creating an HA Cluster or EG with two or more HP encryption switch/encryption blades, the GE_Ports (I/O sync links) must be configured with an IP address for the eth0 and eth1
Ethernet interfaces 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 recover 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] command 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.
•
The HP Encryption Switch and HP Encryption blade support registration of only one HPSKM
Key Vault for Fabric OS 6.2.2x. Multiple HP SKM Key Vaults can be clustered at the SKM server level. Registration of a second SKM key vault is not blocked.
When the registered key vault connection goes down or the registered key vault is down, you must correct the connection with Key Vault, or replace the failed SKM and re-register (deregister failed SKM entry and register the new SKM entry) on the HP Encryption Switch or HP Encryption blade. You must ensure that the replaced (new) SKM key vault is in sync with the rest of the
SKM units in Cluster in terms of Keys Database (manually sync the Key Database from existing
SKM Key Vault in Cluster to new or replacing SKM Key Vault using SKM Admin Guide Provided
Key Synchronization methods).
•
The SKM is supported with Multiple Nodes and Dual SKM Key Vaults. Two-way certificate exchange is supported. See the Encryption Admin Guide for configuration information.
•
Direct FICON device connectivity is not supported for the HP Encryption Switch, or HP
Encryption Blade for front end User Ports. Also, FICON devices as part of Encryption or
Clear-Text flows are not supported, which means FICON devices cannot be configured as
Crypto Target Containers on the encryption switch or blade.
•
Ensure that all encryption engines in the HA cluster (HAC), Data Encryption Key (DEK) cluster, or encryption group are online before invoking or starting rekey operations on LUNs. Also ensure that all target paths for a LUN are online before invoking or starting rekey operations on LUNs.
Encryption behavior 31
32
•
If writes are done to a LUN that is undergoing first time encryption or rekeying, you may see failed I/Os. HP recommends that host I/O operations are quiesced and not started again until rekey operations or first time encryption operations for the LUN are complete.
•
When all nodes in an EG (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 EG. 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 EG with the same EG name. This will make that node the GL node and the rest of the Crypto Target Container configurations will remain intact in this EG.
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 EG on this fresh switch/node with the same EG 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.
•
The Encryption SAN Switch and Encryption FC blade do not support QoS. When using encryption or Frame Redirection, participating flows should not be included in QoS Zones.
•
With Windows and Veritas Volume Manager/Veritas Dynamic Multipathing, when LUN sizes less than 400 MB are presented to the Encryption SAN Switch for encryption, a host panic can occur. Fabric OS 6.2.2e does not support this configuration.
•
To clean up the stale rekey information for the LUN, use one of the following methods:
◦ Method 1
1.
Modify the LUN policy from encrypt to cleartext and commit. The LUN will become disabled.
2.
Enable the LUN using cryptocfg --enable –LUN . Modify the LUN policy from clear-text to encrypt with enable_encexistingdata to enable the first time encryption and do commit. This clears the stale rekey metadata on the LUN and the
LUN can be used again for encryption.
◦ Method 2
1.
Remove the LUN from Crypto Target Container and commit.
2.
Add the LUN back to the Crypto Target Container with LUN
State=”clear-text”, policy=”encrypt” and enable_encexistingdata set for enabling the First Time Encryption and commit. This clears the stale rekey metadata on the LUN and the LUN can be used again for encryption.
•
Relative to the HP Encryption switch and HP Encryption blade, all nodes in the Encryption
Group must be at the same firmware level before starting a rekey or First Time Encryption operation. Make sure that existing rekey or First Time Encryption operations complete before upgrading any of the encryption products in the Encryption Group. Also, make sure that the firmware upgrade of all nodes in the Encryption Group completes before starting a rekey or
First Time Encryption operation.
•
SKM FIPS mode enablement
FIPS compliance mode is disabled in SKM by default. To enable it, follow the procedure described in the SKM User Guide, “Configuring the Key Manager for FIPS Compliance” section.
NOTE: Per FIPS requirements, you cannot enable or disable FIPS when there are keys on the Key
Manager. Therefore, if you must enable FIPS, HP strongly recommends that you do so during the initial SKM configuration, before any key sharing between the switch and the SKM occurs.
Initial setup of encrypted LUNs
IMPORTANT: While performing first-time encryption to a LUN with more than one initiator active at the time, rekey operations slow to a standstill. Define LUNs for a single initiator at a time to avoid this occurrence.
NOTE: When configuring multipath LUNs, care should be taken to add LUN 0 on all of the paths, subject to the following considerations:
•
If LUN 0 presented by the back-end target is a controller LUN (not a disk LUN; that is, not visible in the discoverLUN output), add LUN 0 to the container as a clear text LUN. Make sure all of the paths have this LUN 0 added for MPIO operation (EVA configuration, for example).
•
If LUN 0 presented by the back-end target is a disk LUN, LUN 0 can be added to the container either as clear text or encrypted (MSA configuration, for example).
•
For HP-UX, LUN 0 can appear as 0x0 or 0x400, but both of them are LUN 0 only and should be treated alike.
Fabric OS 6.2.1 fixes
Table 8 (page 34) lists defects closed in the Fabric OS 6.2.1 firmware release. In addition to including all fixes from previous 6.2.0x releases, 6.2.1 contains all fixes included in the 5.3.2b,
6.0.1a, 6.1.1d, and 6.1.2a releases.
Initial setup of encrypted LUNs 33
34
Table 8 Fabric OS 6.2.1 closed defects
Closed defect summary Solution
Sshd allows admin login to execute root-level Linux commands, but admin
CLI commands fail with a command not found error.
Fixed in Fabric OS 6.2.1
Workaround prior to update: A workaround to facilitate execution of admin level CLI commands using ssh , is to use syntax similar to ssh -l admin
192.168.1.12 rbash --login -c switchshow.
Or, if a command is needed that works on both older (correctly operating) Fabric OS and the newer/affected Fabric OS: ssh -l admin 192.168.1.12 switchshow
|| rbash --login -c switchshow.
On rare occasions, an extra RSCN is delivered when HA failover is performed before the name server is in sync.
Fixed in Fabric OS 6.2.1
Firmware is not enforcing a mandatory switch disable before configuring the backbone fabric ID.
Common Area Loader Daemon (CALD) shared memory is not released, leading to high CPU load and inability to run many of the CLI commands; causes no space left on device error.
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Workaround prior to update: Run hafailover prior to the upgrade.
In mixed Fabric OS and M-EOSc fabric in interopmode 2, with more than
500 devices, nameserver database counts do not match. This issue does not exist with M-EOSn based switches in a mixed fabric.
Fixed in Fabric OS 6.2.1
Toggling the N_Port could cause the F_Port to get disabled, leading to the crypto LUN getting stuck in a Not ready (LUN rediscovery) state with HP
StorageWorks Encryption SAN Switch in Access Gateway mode.
Fixed in Fabric OS 6.2.1
A switch having a zone object with an extra ";" or -p flag for a zone create does not perform an error check for alphanumeric characters, which can trigger loss of zone configuration after a firmware upgrade, or can cause a switch panic after the cfgenable command.
Fixed in Fabric OS 6.2.1
In Access Gateway mode, the FDMI database does not show proper information after disabling the port connected to an HBA. Brocade_Software
Identity instance for the remaining node is missing in Brocade SMIA.
Fixed in Fabric OS 6.2.1
During a stress test with switchdisable / switchenable of all switches in a fabric, we observed both verify failure and a switch panic in the RTE module.
Fixed in Fabric OS 6.2.1
A small timing window exists due to a corner case where, if a device sends
PLOGI before the route is set up, it could cause PLOGI to drop in single switch fabric. This is caused by race condition where PLOGI is transmitted prior to the name server query, when the internal route has not yet been established for the WWN zoning pair.
Fixed in Fabric OS 6.2.1
Authentication fails after 15 minutes if external authentication, such as LDAP or Radius server, is configured. The user is not able to login using Web
Tools or web page. Invalid password is reported. This issue does not occur when the CLI is used.
Fixed in Fabric OS 6.2.1
I/O cannot resume when jamming the status frame with IDLE with QoS enabled. Link reset does not load the buffers correctly and I/O can be disrupted
Fixed in Fabric OS 6.2.1
A Common Area Loader Daemon (CALD) memory leak occurs while running management applications using the SMI interface. This causes a switch panic/restart and fabric disruption.
Fixed in Fabric OS 6.2.1
Table 8 Fabric OS 6.2.1 closed defects (continued)
Closed defect summary Solution
The following SNMP-related issues exist in code:
•
The cpLastEvent value is shown incorrectly in the browser.
•
The cpStatusChange trap is not sent to the trap recipients.
• There is an incompatibility with client using older MIBs (pre-Fabric OS
6.2.0 MIB).
• The swEndDeviceInvalidWord mid command returns bad words .
• SNMP displays incorrect index value for atTable , ipTable, and ipNetTodefia Table of MIB-2.
•
MIB fails to compile on third-party SAN Management software
( swPmgrEventType ).
Fixed in Fabric OS 6.2.1
After upgrade to Fabric OS 6.2.0, Fabric Watch reports HP StorageWorks
4/8, 4/16 SAN switches, and embedded 4-Gb switches as unhealthy and issues a warning message that compact flash is 90% full.
Fixed in Fabric OS 6.2.1
A bad SFP triggered an i2C access causing the following problems on the port/slot display and CPU load on HP StorageWorks 4/256 SAN director:
• Executing a slotshow command causes a no system control access to slot error.
•
The sfpshow command gives Mod_val , or an i2C access message.
Fixed in Fabric OS 6.2.1
Port statemismatch occurs on internal ports of 4-Gb embedded switches between switchshow and portcfgshow . The portcfgshow command shows a persistent disable state while the port is enabled.
Fixed in Fabric OS 6.2.1
After removing EE and F_Port TT filters on HP StorageWorks DC SAN director in non-VF (Virtual Fabrics) mode, and enabling Fabric mode Top
Talkers, the flow values are inaccurate.
Fixed in Fabric OS 6.2.1
If TI zone operations are performed simultaneously on different switches, the active CP may failover due to termination of the name server module
A switch restart on HP StorageWorks DC SAN or DC04 director (power cycle or reboot of both CPs) causes random ICL E_Ports to be segmented.
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Due to a rare corner case, a port reset at the same time as an end-to-end
PLOGI or during a PLOGI storm can lead to a kernel panic with the message
Oops: kernel access of bad area, sig: 11 [#1] and sometimes cold recovery.
Fixed in Fabric OS 6.2.1
HA failover on HP StorageWorks DC SAN director times out, causing a switch reboot.
Fixed in Fabric OS 6.2.1
Workaround prior to update: Manually block/unblock an E_Port to rebuild the fabric.
Daemons may panic during FID (logical switch) deletion and creation if there is no significant time delay between the deletion and creation. The switch becomes unresponsive and the daemon panics.
In a FICON environment, a switch may panic when blocking/unblocking an E_Port due to incorrect RNID data count.
Concurrent reboot of HP StorageWorks DC SAN directors at both ends of
DWDM link causes the link to fail to come up, because the link is unable to sync before the port is enabled at the correct speed.
Devices attached to a switch in Access Gateway mode are reported by
DCFM/weblinker as physical rather than virtual devices.
A switch reboot/hafailover with kernel assert in the FCPH module occurs when the received frame size is too big.
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Fabric OS 6.2.1 fixes 35
36
Table 8 Fabric OS 6.2.1 closed defects (continued)
Closed defect summary Solution
In an FCR environment (with a router or switch configured for FCR), a switch runs out of memory when it is connected with the Mi10k. The Mi10k sends continuous RRQ frames because the Fabric OS-based switch did not handle
RRQ frames with either accept or reject.
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Several problems occurred that were related to the configdownload commands. Some of these problems caused a core dump.
A switch panic/hafailover occurs due to a weblinker.cfg
panic seen during overnight slot command script test when modify/distribute ACL database, and during RNID response processing.
Fixed in Fabric OS 6.2.1
A blade fault occurred in HP StorageWorks 4/256 SAN director on an
8-Gb 48-port blade in either slot 1 or slot 10 when the director was fully loaded with 8-Gb 48-port blades.
Fixed in Fabric OS 6.2.1
Starting with Fabric OS 6.1.2, supportsave was updated to collect more data. A Parity error may be logged as data is read from disabled ports on switches that were updated from a lower code level but never cold booted.
Fixed in Fabric OS 6.2.1
Frame Redirect zones cannot be created when defzone is set to allaccess .
Fixed in Fabric OS 6.2.1
Workaround prior to update: Set defzone to noaccess .
Memory leak during security script testing.
FCIP tunnels on the HP StorageWorks 400 MP Router or the MP Router blade do not come up due to a timing issue caused when using optical-to-copper converters in the path.
Fixed in Fabric OS 6.2.1
In 8-Gb routed fabric, PLOGI in acceleration path did not program cam entry properly, leading to backbone hosts not being able to see edge fabric target.
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
In a cascaded Access Gateway configuration of three switches with both
AGs in port group mode, when the QoS license is removed from the fabric switch and switchdisable / enable is performed, traffic continues for medium priority flows, but stops flowing for high and low priorities until the
QoS license is reinstalled.
Fixed in Fabric OS 6.2.1
When a trunk master port is disabled, Fabric Watch incorrectly sets the new trunk master's health to offline and the remote side to faulty, even though the port is online. This is a Web Tools display problem with no functionality impact.
Fixed in Fabric OS 6.2.1
Unable to get F_Ports (trunk ports) data from Web Tools, but CLI works.
Fabric becomes unstable after changing EX_Port trunk to E_Port trunk.
Switches bounce between reachable and unreachable in edge fabric.
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
Fabric OS 6.2 RADIUS Calling-station-ID (31) implementation is used for both device called by and workstation called from host name/IP address. As a result, RADIUS will not work properly and restriction of host access is not possible.
Fixed in Fabric OS 6.2.1
When the host transmits PLOGI to the name server in Access Gateway mode, the name server responds with ACK then ACC. The AG forwards the ACC to the host, which responds with ACK, but it never gets forwarded back to the name server, causing the exchange to abort.
Fixed in Fabric OS 6.2.1
Fixed in Fabric OS 6.2.1
OpenVMS init command does not complete, which prevents OpenVMS from mounting the file system with either the HP StorageWorks Encryption
SAN Switch, or the encryption blade.
During blade insertion or switch power up, the port fence disabled ports that are running diagtest trigger blade fault during blade POST.
Fixed in Fabric OS 6.2.1
Table 8 Fabric OS 6.2.1 closed defects (continued)
Closed defect summary
HP StorageWorks DC SAN Director temperature sensor reported spurious readings leading to the CRITICAL HIL-1502 message without having first issued the HIL-1501 warning.
Solution
Fixed in Fabric OS 6.2.1
Workaround prior to update: Ignore isolated/spurious high temperature
CRITICAL errors when not preceded by warnings.
After a power cycle, HIL-1610 WARNING appeared on the HP
StorageWorks 8/40 SAN Switch, reporting that Fan/PS unit 1 was not supplying power; fan speeds were not available.
Fixed in Fabric OS 6.2.1
Workaround prior to update: This warning can be safely ignored when seen at boot time. It is caused by a single false sensor reading below minimum.
HP StorageWorks Encryption SAN Switch can go to the faulty state after upgrading to any Fabric OS 6.2.0x version.
Fixed in Fabric OS 6.2.1
Firmwarecommit can fail on the HP StorageWorks Encryption SAN Switch or encryption blade with a message about a missing properties file when upgrading to Fabric OS 6.2.0d or later.
Fixed in Fabric OS 6.2.1
An internal timing race condition can cause one or more F_Ports or E_Ports to be brought down, leading to frame discards. The port will be brought back online automatically at the end of the HA or firmware upgrade operation.
Fixed in Fabric OS 6.2.1
In a FICON environment, some frame drops occur on TI zone-enabled ISLs during an upgrade to or from Fabric OS 6.2.0x. This causes Interface
Control Checks (IFCCs) to be reported.
Fixed in Fabric OS 6.2.1
Fabric OS 6.2.1a fixes
Table 9 (page 37) lists defects closed in the Fabric OS 6.2.1a firmware release.
Table 9 Fabric OS 6.2.1a closed defects
Closed defect summary Solution
Device connectivity across the FCIP link with the HP StorageWorks 400 MP
Router or MP Router blade will be lost after WAN issues. Credit information from the portshow of the FCIP tunnel will display a negative credit number.
Fixed in Fabric OS 6.2.1a
Fixed in Fabric OS 6.2.1a
SMI failed to discover all switches over EX_Port after hafailover , and reports LOGIN FAILED after the GPL2 query targeted to the translate domain is rejected.
SFP power supply values are not displayed correctly after doing a nondisruptive firmware upgrade to Fabric OS 6.2.1.
Fixed in Fabric OS 6.2.1a
Workaround prior to update: Executing the same command again shows the correct values.
High CPU load from DCFM doing supportsave causes the port to go offline with a laser FLT/link reset.
Fixed in Fabric OS 6.2.1a
Name server database counts do not match for Fabric OS 6.2.1 and M-EOS
9.9.0 switches in the same fabric, so the host cannot see the device. This occurs when an HBA capable of an RHBA command and an M-EOS switch are in the same fabric.
Fixed in Fabric OS 6.2.1a
The host cannot see the device due to a login failure with a non-FC standard value (0x0000EF) to the name server, when the switch has port alpa also enabled in interopmode 2.
Fixed in Fabric OS 6.2.1a
With Fabric OS 6.2.1 in a logical switch setup, a segmentation fault/core dump occurs after configdefault .
Fixed in Fabric OS 6.2.1a
Fabric OS 6.2.1a fixes 37
Table 9 Fabric OS 6.2.1a closed defects (continued)
HP StorageWorks DC SAN Director panics due to termination of msd during fabric reconfiguration while doing switchdisable , agshow , switchenable loop, in a fabric with an Access Gateway device with more than 56 switches.
Fixed in Fabric OS 6.2.1a
A small memory leak occurs when multiple simultaneous MIB WALK queries are performed.
Fixed in Fabric OS 6.2.1a
Fixed in Fabric OS 6.2.1a
96-bit licenses disappear from the HP StorageWorks 8/80 SAN Switch due to a race condition, even when there are no fabric changes in the environment.
Merging an M6140 M-EOS switch into a Fabric OS switch fabric causes a Fabric OS switch to panic.
Fixed in Fabric OS 6.2.1a
Fabric OS 6.2.1b fixes
Table 10 (page 38) lists defects closed in the Fabric OS 6.2.1b firmware release. In addition to including all fixes from the 6.2.0x, 6.2.1, and 6.2.1a releases, it contains all fixes included in the
5.3.2c, 6.1.2b, and 6.2.0g releases.
Table 10 Fabric OS 6.2.1b closed defects
Closed defect summary Solution
Switch panic occurs due to an out-of-memory condition when a management application performs repeated FCR LUN emulation queries via SMI, or when polling a switch whose password has changed multiple times.
Fixed in Fabric OS 6.2.1b
Workaround prior to update: Disable SMI agents.
HP StorageWorks DC SAN Director panicked and rebooted after fwshow
--disable --port command.
Fixed in Fabric OS 6.2.1b
Segmentation fault causes a CALD panic in the fabric when the switch running Fabric OS 5.2.x sends an internal query to directors that were not properly set up to handle switches with more than 256 ports.
Switch panic is triggered by size-64 kernel message buffer being used up in a virtual fabric with logical ISL configured.
Fixed in Fabric OS 6.2.1b
Fixed in Fabric OS 6.2.1b
Workaround prior to update: Configure only DISLs between switches.
Fabric OS 6.2.2 fixes
Table 11 (page 38) lists defects closed in the Fabric OS 6.2.2 firmware release. In addition to including all fixes from previous 6.2.1x releases, 6.2.2 contains all fixes included in the 5.3.2c,
6.0.1a, 6.1.1d, 6.1.2b and 6.2.0g releases.
Table 11 Fabric OS 6.2.2 closed defects
Closed defect summary Solution
HP StorageWorks 4/256 SAN Director with multiprotocol router blade does not see new device across LSAN after upgrade from Fabric OS 5.x
non-disruptively to Fabric OS 6.2.x. Bounce of host port causes paths to be lost between host and target.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Do a slotpoweroff / slotpoweron of the router blade or reboot.
8Gb blade in HP StorageWorks DC SAN Director configured for Integrated
Routing fails to route traffic on EX ports after firmware upgrade from 6.1
to 6.2. If there is an additional hafailover , a new device is added.
Bouncing the device ports could trigger a route problem leading to the host not being able to see the device.
Fixed in Fabric OS 6.2.2
Workaround prior to update: If problem has already occurred, bounce all EX ports in the same chip together. After recovery, fabric is no longer susceptible to the problem.
38
Table 11 Fabric OS 6.2.2 closed defects (continued)
Closed defect summary Solution
Numerous Reliable Transport Write and Read errors (RTWR) observed when going to translate domain. Switch-to-switch NameServer frames are intended for the LE domain but use any valid F/E-port instead of using the LE port
ID. Frame will be dropped rather than accepted or rejected, which results in repeated RTWR attempts.
Fixed in Fabric OS 6.2.2
HP StorageWorks Multiprotocol Router Blade heartbeat stops, causing a reboot while traffic is running over FCIP links. This may cause CP failover, disrupting traffic only on the router blade.
Fixed in Fabric OS 6.2.2
After blade fault, port was taken offline at asic level, but offline SCN (State
Change Notification) was not sent to routing module, fspfd, fabricd, which created an inconsistent view between application and kernel on the port state of the faulted blade. Leads to Switch not ready for F or L port message with replacement blade.
Fixed in Fabric OS 6.2.2
In a fabric with more than 50 switches, non-disruptive firmware downloads
(HCL) on an HP StorageWorks DC SAN Director fails on the standby CP.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Run firmwaredownload again.
Rolling reboot occurred on HP StorageWorks DC04 SAN director with multiprotocol extension blade installed when firmware downgraded from
Fabric OS 6.3.x to 6.2.
Fixed in Fabric OS 6.2.2
TI zones become disabled when Telnet times out following TI zone change.
Cfgsave actually pushes the data, but should not do so, as due to session timeout, stale transaction is not properly terminated before processing new
TI zone, which can result in erroneous TI zone properties list and lead to other fabric wide instability events.
Fixed in Fabric OS 6.2.2
When FMS mode (FICON Managed Switch) is enabled, then disabled, hafailover toggles online ports and results in traffic disruption.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Do not toggle FMS mode without resetting the
ASIC.
The switchstatusshow command in CLI does not show correct status when a core blade is powered off. It reports Core Blades monitor
HEALTHY .
Loss of an E_Port to a neighboring Mi10k during a zone push operation caused zoning request to fail with Transaction Commit failed.
Reason code 2 (26) - Aca Was Rejected:Remote Switch busy, Retry in a few seconds .
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Link timeout occurs on switch port connected to any Access Gateway during hafailover /reboot of AG switch with rlsdisable=0 , causing traffic disruption.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Disable RLS as follows: Configure → system services
→ disable RLS probing
If Fabric Watch fwalarms is turned off and Errlog is turned on, fabric watch daemon can crash causing a switch panic.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Disable
ErrLog and Port Fencing (using the fwconfigure command) in the threshold alarm matrix configuration for all port related thresholds. This prevents the problem-causing functions from being called.
Evmd (Event Monitor Daemon) crash causes switch to assert/reboot several hours after lscfg --delete when running SMI proxy client or SMI-like interface, due to timer events being processed in the context of a deleted logical switch.
Fixed in Fabric OS 6.2.2
Fabric OS 6.2.2 fixes 39
40
Table 11 Fabric OS 6.2.2 closed defects (continued)
Closed defect summary
A switch panic occurs due to third-party management application giving bad response or no response to FCP LUN request.
SwNs table lists one fewer name server entry than the actual number of devices (first entry shown in nsallshow CLI command)
Solution
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
The urouteshow command lags for several seconds while displaying the route information. The lag is longer on products with large port counts, such as directors
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
The errorshow command log still shows the original chassis name after a chassis name change.
The sequence of creating two TI zones, not saving the change, and then modifying the attributes with the zone --add command results in misconfigured attributes that will cause software verify on remote switches when changes are committed. This can lead to a switch reboot or panic.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Other methods of creating TI Zones and modifying the definitions work seamlessly.
It is just this odd set of steps that produce the failing condition. When creating multiple TI zones, they should be saved before modifying the attributes. You can clean up problem by using zone --add to modify the attributes again after the save. You can also delete and re-create the TI zone.
Configuring IP address of CP1 blade from CP0 on any director: after hafailover the hostname portion of the configuration is no longer there for CP1. Other IP configuration information remains intact.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Run the ipaddrset command again from CP1 to configure CP1 hostname .
The switchstatusshow command output was not updated after the faulty blade (multiprotocol router blade, multiprotocol extension blade, or 10/24
FCoE blade) was brought back up, enabled, and online.
Fixed in Fabric OS 6.2.2
FDMI: fdmid crashes when a Brocade HBA with virtual ports is connected to a 4/256 SAN Director.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Log out all the devices that have registered their HBA information and log them in after the fabric is stable.
Fabric Watch SFP messages get logged after upgrade to Fabric OS 6.1.1b, due to I2C read values of 0xff and I2C NACK error case not being properly handled.
Fixed in Fabric OS 6.2.2
Switch gets nsd panic when third-party switch in interopmode 3 and Fabric
OS 6.2 sends invalid frames.
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Server does not see some devices on shared primary ports connected to
48 port blades using domain/port session based zoning.
The configdownload command does not load tstimezone info after changing tzh and tzm in the config.txt
file to new values.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Set up tstimezone through CLI.
Transient detected error on internal link caused 8-Gb blade to be faulted with reason=5 or 4.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Use slotpoweroff and slotpoweron to clear the fault.
Table 11 Fabric OS 6.2.2 closed defects (continued)
Closed defect summary Solution
When running the Zone admin, with 48 port blade where there is port address sharing, devices show up on the wrong port. When port index and port address of the given port is different, end device will be seen connected to a different port (U port) than the original one (F_Port).
Fixed in Fabric OS 6.2.2
HP StorageWorks DC Switch Encryption blade comes up faulty after firmwaredownload -sf and reboot of both CPs at the same time.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Reseat the blade.
After upgrade to Fabric OS 6.x, rsh using user credential gets ifmodeshow eth0: ioctl (ETHTOOL_GSET) failed error in response to ifmodeshow command. Telnet and rsh with root credential work fine.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Set suid permissions for ethmode: c hmod +s
/fabos/libexec/ethmode
Backup job stopped for an extended period of time when running through
HP StorageWorks Encryption switch or encryption blade after bouncing 1 of the 2 connected ISLs.
The 4Gb SAN Switch for HP c-Class BladeSystem AG may login to DC
SAN Director with wrong PWWN.
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Workaround prior to update: Reboot AG.
During director switch initialization from power on, reboot, or hafailover , daemons fail to load causing switch to auto reboot and ffdc HAM-1008 and HAM-1007 errors are observed.
Fixed in Fabric OS 6.2.2
When running a third-party host scan, the http daemon ( weblinker.fcg
) terminates and restarts several times, causing a temporary management service interruption.
Fixed in Fabric OS 6.2.2
In Fabric OS 6.2, OID for connUnitType no longer returns the correct access gateway mode status after upgrade from Fabric OS 6.1.1d to 6.2.0f.
Fixed in Fabric OS 6.2.2
Fabric binding does not work in 239 domain mode in Interopmode 3 with
FCR on 8Gb switches. EX port rejects it.
Fixed in Fabric OS 6.2.2
Fabric Watch sometimes logs messages with values above 100%. Most likely occurs during first Fabric Watch polling cycle after slotstatsclear command is issued.
Fixed in Fabric OS 6.2.2
The following message may display on the console while firmware commit is in progress: ssnGet: Unable to get WWN info.sw=0 rc=-5 .
Fixed in Fabric OS 6.2.2
While doing a disruptive CP reboot on a director class switch (reboot active
CP when no standby CP is present), if simultaneous fabric update causes a large volume of F-Class traffic, a potential exists for an edge switch to be faulted due to lack of response from the core director.
Fixed in Fabric OS 6.2.2
In a rare circumstance with a switch running Fabric Watch, a panic can occur after fwd terminated with exit code:134, exit sig:17, and parent sig:0 when IPC buffer is overrun on a busy system.
Fixed in Fabric OS 6.2.2
Telnet banner and switchname are not consistent after a new switchname is defined without doing multiple hafailover commands. Can also occur after a standby CP is replaced where the new CP hosts file does not get synchronized with active CP without two hafailover commands.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Use the hostname xyz command when a switchname xyz is used. The problem does not occur with SSH; it does not use the banner.
The SNMP manager gets incorrect MIB information from a switch running
Fabric OS 6.1.x, due to a change in SwFwEPortUtil and SwFwEPort-
Pktl between SW_v5_7 to SW_v5_8 MIB.
Fixed in Fabric OS 6.2.2
Fabric OS 6.2.2 fixes 41
Table 11 Fabric OS 6.2.2 closed defects (continued)
Closed defect summary Solution
When port 254 is used in directors in non-FICON setup, after multiple hafailovers , port 254 may lose its name server entry, and/or CP reports a synchronization error while overall system HA maintains sync.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Reboot standby CP to force a re-synchronization.
During firmwaredownload , standby CP reboots due to assert and recovers with no functional impact observed.
Fixed in Fabric OS 6.2.2
With HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb
BladeSystem switches for p-Class and c-Class BladeSystem, speed negotiation fails when the port is locked as G-port, and port cannot come online.
Fixed in Fabric OS 6.2.2
On a switch running Fabric OS 6.2.x, when a firmwaredownload -sn and reboot is executed with Fabric OS 6.3.0x such that the new firmware image is active but the secondary image has the old image, if a firmwarerestore is run to revert back to the original image, it will fail.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Invoke a manual reboot.
CALD panic occurred on a director and CPs got out of sync, but no failover happened as CALD was in defunct state due to race condition.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Manually reboot the switch.
Supportsave does not clear the FFDC files, leading to continued FFDC file warnings being issued until a second supportsave is issued.
Fixed in Fabric OS 6.2.2
Peak data rate is reported as 4096 MB/s for 2Gb/s port.
Fixed in Fabric OS 6.2.2
NPIV tape devices may not be seen by hosts due to name server not sending subsequent PLOGI ACC following a sequence where NPIV device sends
LOGO before link down.
Fixed in Fabric OS 6.2.2
HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb BladeSystem switch for c-Class BladeSystem has incomplete supportsave .
Fixed in Fabric OS 6.2.2
Workaround prior to update: Run individual command such as portstatsshow on the switch.
On HP StorageWorks DC SAN or DC04 director, SwFCPortTxType MIB does not report the type of CoreBlade's ICL port correctly. Reports as swFCPortTxType.385 unknown(1)
Fixed in Fabric OS 6.2.2
Configdownload removes license keys from a new replacement switch.
This applies only to Fabric OS 6.2.x code.
Fixed in Fabric OS 6.2.2
Fabric OS 6.2.2a fixes
Table 12 (page 42) lists defects closed in the Fabric OS 6.2.2a firmware release.
Table 12 Fabric OS 6.2.2a closed defects
Closed defect summary
After a target port bounce, the FC FastWrite host cannot recognize the target due to a cam setup problem on the backend port used by FC
FastWrite.
Solution
Fixed in Fabric OS 6.2.2a
After upgrading to Fabric OS 6.2.x, the 400 MP Router or Multiprotocol
Router blade detects a credit problem on virtual channel 0, causing a frame drop on FCIP and FC FastWrite, and the host is unable to recognize the target.
Fixed in Fabric OS 6.2.2a
42
Table 12 Fabric OS 6.2.2a closed defects (continued)
Closed defect summary Solution
While running Fabric OS 6.2.2, the switch can panic after executing a fcplunquery or iscsicfg CLI command for the target entity on HP
StorageWorks iSCSI Director Blade. An FCPD termination occurs if a PRLI or Report LUN query times out during fcplunquery / iscsicfg command and the LOGO response is missing a message queue required for processing, resulting in a switch panic.
Fabric class areas → Zoning Changes in fwconfigure does not function correctly. Zone changes are not recorded in the FW module, resulting in threshold alarms not being raised as appropriate.
Fixed in Fabric OS 6.2.2a
Fixed in Fabric OS 6.2.2a
Fixed in Fabric OS 6.2.2a
After using the ipaddrset -cp command to set a CP blade or director switch host name, the standby CP incorrectly displays the CP host name instead of the chassis host name. For the change to take effect, after upgrading the firmware, the user must logout, and then log back in.
During reboot, HP StorageWorks D2D Backup System device sends the explicit logout; however, the switch does not clean up the route properly, resulting in the hosts being unable to detect the tape devices.
Fixed in Fabric OS 6.2.2a
Username/password authentication can fail when using Microsoft Active
Directory (LDAP) from Server 2008 for authentication. Users can experience problems after upgrade from a Microsoft Windows host using older versions of the LDAP protocol for authentications.
Fixed in Fabric OS 6.2.2a
After using the snmpconfig -set snmpv command to set SNMPv3, the switch configdownload command failed with the following message: snmp.snmpv3Usm.0.usmPrivProtocol:6 Invalid Value .
Fixed in Fabric OS 6.2.2a
If you set fwsettocustom , the HP StorageWorks DC SAN Backbone
Director does not output FW-1003/FW-1004 after an hafailover or reboot, and you will not be notified about temperature over threshold events.
Fixed in Fabric OS 6.2.2a
The systemverification and portloopbacktest diagnostic tests report marginal blade failures on an HP StorageWorks DC SAN Director, but after the tests are complete, Fabric Watch reports switch is healthy.
Fixed in Fabric OS 6.2.2a
Fabric OS 6.2.2b fixes
Table 13 (page 43) lists defects closed in the Fabric OS 6.2.2b firmware release.
Table 13 Fabric OS 6.2.2b closed defects
Closed defect summary Solution
After upgrading EFCM to 9.7.4 and HP StorageWorks 4/256 SAN director to 6.2.0x, customer is unable to discover switches due to performance of
SNMP get for connUnitLinkTable being reduced in 6.2.x.
Fixed in Fabric OS 6.2.2b
Excessive internal messages cause a RASLOG flood condition and a weblinkerfcg message appears on FCIP switches in the fabric (HP
StorageWorks 1606 Extension SAN Switch and Multiprotocol Extension
Blade). This can lead to other important RASLOG messages being lost. This issue has no functional impact and occurs on platforms not running ipsd
(IP Security Daemon).
Fixed in Fabric OS 6.2.2b
No cascaded FICON CUP connectivity on 4/256 Director with 8Gb blade when E_Port and F_Port are on different ASICs on the blade.
Fixed in Fabric OS 6.2.2b
Under heavy CPU load, SFP laser fault condition may cause links to reset.
Fixed in Fabric OS 6.2.2b (New parameter added to Fabric OS 6.2.2b to allow adjustment of SFP polling interval to avoid laser faults.)
Fabric OS 6.2.2b fixes 43
Table 13 Fabric OS 6.2.2b closed defects (continued)
Closed defect summary Solution
In a very rare circumstance, a configuration file for dynamic area mapping gets corrupted after firmwarecommit , leading to both CPs failing and switch not booting up.
Fixed in Fabric OS 6.2.2b
Workaround prior to update: Remove the port2Bound file in /etc/fobos/ port2Bound in both active and standby
CPs, and in both partitions on both CPs, then reboot the switch.
Switch can panic or hafailover when detecting termination of daemons due to bad EOF frames being forwarded to the CPU for processing.
Fixed in Fabric OS 6.2.2b
CP fails to boot on DC SAN director, DC04 SAN director, and 8/80 SAN switch on power up or during hafailover and CF access error: HDA: drive not ready message may be seen on the console.
Fixed in Fabric OS 6.2.2b
Workaround prior to update: Reboot the switch again.
Performing multiple configdownload operations through DCFM or CLI can trigger memory issues with webd leading to restart or switch panic.
Fixed in Fabric OS 6.2.2b
After code upgrade to Fabric OS 6.2.x on 4Gb embedded switches, there is not enough room left in compact flash for the switch to operate adequately.
If there is a core dump, switch compact flash could get full, resulting in switch not being able to boot up due to a corrupted file system, etc.
Fixed in Fabric OS 6.2.2b
Fabric OS 6.2.2c fixes
Table 14 (page 45) lists defects closed in the Fabric OS 6.2.2c firmware release.
44
Table 14 Fabric OS 6.2.2c closed defects
Closed defect summary Solution
8 Gb Directors with an 8 Gb blade in slot 1 or 8 Gb switches can see a frame drop in the fabric when
Ex/VEx ports are configured in the same ASIC as an
F/E port with EGID 0, leading to either the host not seeing a target, or poor performance in the fabric.
This issue can be identified by running sloterrshow
1 on directors, or sloterrshow on the switches, and the type6_miss counter should continuously increment during traffic load on backend port/E_Port.
Fixed in Fabric OS 6.2.2c.
Workaround prior to update:
Avoid configuring an EX_Port or a VEx_Port near an F/E_Port with an EGID of 0. To identify a port with an EGID of 0, login as root and run bladeportmap [1] . The first port where Upt is not -1 uses EGID 0. Once the problem occurs, make the
F/E_Port into an EX_Port and then configure it back to an
F/E_Port to fix the problem port by executing the following instructions:
1.
Disable the F/E_Port.
2.
Configure the F/E_Port as an EX_Port for a valid FID.
3.
Connect a link between the FID and the EX_Port (IFL).
4.
Enable the port.
5.
Verify that the link is online, then disable the port.
6.
Disable the EX_Port configuration.
7.
Connect the host/ISL back to the F/E_Port.
8.
Enable the port.
After upgrading Fabric OS from 6.1.x to 6.2.x on 4
Gb switches or director, the switch or director may get into a perpetual reboot condition if the http configuration is invalid (inconsistency between SSL certificate and http configuration).
Fixed in Fabric OS 6.2.2c.
Workaround prior to update:
Manually ensure that http.enabled matches with SSL certificate by configshow http.enabled
as admin user. If it's inconsistent with SSL Certificate requirement, execute
/fabos/libexec/webdconfigure as root to set "HTTP
Enable" to yes . Or schedule a window, disable switch, and configdownload a file with http.enable:1 [end] when switch is at FOS 6.1.x to correct the configuration.
If the switch is already stuck in a reboot loop, login as root via serial console, copy and paste the following command string into console as one line before the next reboot: sed 's/http.enabled:1/http.enabled:1/g'
</etc/fabos/fabos.0.conf> tmp; cp tmp /etc/fabos/fabos.0.conf;cp tmp
/mnt/etc/fabos/fabos.0.conf;rm tmp
After hot code load, switch in access gateway mode panics and reboots, and usually a [PORT-1003] is entered in raslog .
Fixed in Fabric OS 6.2.2c.
VE tunnel bounce, VEx/Ex port bounce observed after hareboot on 8 Gb switch configured for FCR under heavy load condition. This impacts HP StorageWorks
400 Multiprotocol router, multiprotocol router blade, or any 8 Gb switch configured with VEx/Ex/VE ports.
Fixed in Fabric OS 6.2.2c.
All 64 bit port status counters not available in SNMP, even though they are available in the CLI using the portStats64Show command.
Fabric OS 6.2.2c now exposes these counters through SNMP
Running supportsaves -k multiple times on FOS
6.2.x causes raslogd to crash and restart. This can lead to hafailover on directors and reboot on switches.
Fixed in Fabric OS 6.2.2c.
Fabric OS 6.2.2c fixes 45
Table 14 Fabric OS 6.2.2c closed defects (continued)
Closed defect summary Solution
On B-series 4 Gb switches, multiple critical level
CDR-1003 raslog entries seen during supportsave after non-disruptive upgrade from FOS
6.1.x to 6.2.x.
With Fabric OS v6.2.2c, this specific occurrence of CDR-1003 is updated to log as a warning rather than critical. It can be safely ignored unless it becomes persistent, or does not happen during supportsave .
WebTools nameserver is not reflecting the alias and zones created in DCFM. Alias and zone to which the device belongs is not displayed in the "member of zone" and "member of alias" column.
Fixed in Fabric OS 6.2.2c.
Workaround prior to update:
Use WebTools to create a zone/alias rather than DCFM.
Fabric OS 6.2.2d fixes
Table 15 (page 46) lists defects closed in the Fabric OS 6.2.2d firmware release.
Table 15 Fabric OS 6.2.2d closed defects
Closed defect summary Solution
During a reboot, the host might not come up when connected to an HP StorageWorks 4/8 SAN Switch,
HP StorageWorks 4/16 SAN Switch, or Brocade 4
Gb SAN Switch for HP c-Class BladeSystem. The host is unable to log in because the switch comes online as a G_Port rather than an F_Port.
Fixed in Fabric OS 6.2.2d.
Weblinker processes terminate and then restart when the DCFM management application queries Top Talker information from the switch.
Fixed in Fabric OS 6.2.2d.
For all 8 Gb switches, the host is unable to discover its targets after an HA failover or a code upgrade on the router port. This is because the domain table routing entry is accidentally cleared on an EX_Port.
Fixed in Fabric OS 6.2.2d.
When Access Gateway mode is enabled, switch panics occur during upgrades from FOS 6.1.x to FOS
6.2.2c. This does not occur when upgrading from
FOS 6.1.x to any other FOS 6.2 release.
Fixed in Fabric OS 6.2.2d.
Fabric Watch messages (FW-1186 and FW-1190) with invalid values can be logged at the first Fabric
Watch polling cycle after the slotstatsclear command is issued.
Fixed in Fabric OS 6.2.2d.
A switch that is connected locally can be disabled by a remotely connected switch due to directional route problems in the fabric. When this happens, messages are logged in RASLOG indicating that RTWR has reached the maximum retries.
Fixed in Fabric OS 6.2.2d.
When Access Gateway mode is enabled, switches can mishandle multisequence frames causing memory corruption and agdd switch panic.
Fixed in Fabric OS 6.2.2d.
A fabric containing two router devices in the backbone, both connected via EX_Ports to the same edge fabric through an M-EOS switch in IM 2 mode, causes the router device to core dump and panic.
Fixed in Fabric OS 6.2.2d.
46
Table 15 Fabric OS 6.2.2d closed defects (continued)
Closed defect summary Solution
After upgrading to FOS 6.2.x firmware on 4 Gb switches, critical messages (CDR-1003) are posted to the RASLOG when a SupportSave operation is executed.
Fixed in Fabric OS 6.2.2d.
Workaround prior to update :
Customers can ignore the CDR-1003 critical messages logged during SupportSave operations since they have been downgraded to warnings with this release. However, CDR-1003 critical messages for other operations should not be ignored.
Path loss traces do not contain enough debugging information when Access Gateway mode is enabled.
Fixed in Fabric OS 6.2.2d.
Administration passwords are reset to the default password after upgrading from FOS 6.1.x to FOS
6.2.2c on all switches.
Fixed in Fabric OS 6.2.2d.
Some FA MIB counters/statistics are available through the Command Line Interface, but they are not available through SNMP for all switches.
Fixed in Fabric OS 6.2.2d.
Erroneous port faults may be reported in the RASLOG after a switch with a large number of link-down events has been in operation for an extended period of time.
Fixed in Fabric OS 6.2.2d.
Fabric OS 6.2.2e fixes
Table 16 (page 47) lists defects closed in the Fabric OS 6.2.2e firmware release.
Table 16 Fabric OS 6.2.2e closed defects
Closed defect summary Solution
The fans on an HP StorageWorks DC SAN Backbone
Director Switch may erroneously be flagged as bad and get logged with a "[PLAT-5042], FAN I2C reset” error code in the Raslog, even though they are operating properly.
Fixed in Fabric OS 6.2.2e.
Workaround prior to update :
Reseating the fans will allow the fans to recover from the faulty state.
The Switchshow command reports the switch port state as "Mod_Val" rather than "Online" after a switch reboot test and ISL fails to form. This applies to all switches except for the HP 8/8 Base (0) e-port SAN
Switch, HP 8/8 (8)-ports Enabled SAN, HP 8/24 Base
16-ports Enabled SAN Switch Switch, HP 8/40 Base
24-ports Enabled SAN Switch, and the HP 8/40
Power Pack+ 24-ports SAN Switch.
Fixed in Fabric OS 6.2.2e.
Access Gateway is not displayed by the DCFM client when utilizing an EOS seed switch.
Fixed in Fabric OS 6.2.2e.
When more than one RPC connection is established simultaneously on a switch with busy management applications, a race condition may cause multiple connections to free a shared object and trigger rpcd panic.
Fixed in Fabric OS 6.2.2e.
After performing a LOGO following a firmware download the switch route is not properly established.
The host cannot see the target because the PLOGI
Accept from the HBA is dropped by the switch.
Fixed in Fabric OS 6.2.2e.
The LED for online trunked F-Ports goes from a steady green to off after a code upgrade or hareboot/hafailover.
Fixed in Fabric OS 6.2.2e.
Fabric OS 6.2.2e fixes 47
Table 16 Fabric OS 6.2.2e closed defects (continued)
Closed defect summary
A switch panic occurs when a management application polls for Access Gateway device information or when agshow command is executed.
WARNING raslog messages of "[CDR-1003]" unnecessarily generate the call home function.
SNMPmibwalk only shows MIB connUnitPortEntries for ports that have SFPs installed.
Solution
Fixed in Fabric OS 6.2.2e.
Fixed in Fabric OS 6.2.2e.
Fixed in Fabric OS 6.2.2e.
Effective date
February 2011
48
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement