HP StorageWorks Fabric OS 5.3.
Legal and notice information © Copyright 2007 Hewlett-Packard Development Company, L.P. © Copyright 2007 Brocade Communications Systems, Incorporated Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Version 5.3.0 Effective date July 2007 Description Fabric OS 5.3.0 contains enhancements and fixes since the release of Fabric OS 5.2.1b. There is no new device support added with this release for HP StorageWorks platforms. Update recommendations HP strongly recommends that users upgrade to Fabric OS 5.3.0 as soon as possible. Install Fabric OS 5.3.0 before installing the latest released port and intelligent blades. Consider the following before upgrading: • If upgrading from Fabric OS 5.1.
Support for embedded switch models The B-Series embedded switches have transitioned from supporting the Fabric OS 5.0.5 stream only, to operating with Fabric OS 5.2.1b and later. The B-Series embedded switch models include: • Brocade 4Gb SAN Switch for HP p-Class BladeSystem (Brocade 4012) • Brocade 4Gb SAN Switch for HP c-Class BladeSystem (Brocade 4024) NOTE: The Fabric OS 5.0.5 stream remains active for the Core Switch 2/64 and for the SAN Director 2/128 in chassis modes 3 and 4.
New features in Fabric OS 5.3.0 This section describes Fabric OS 5.3.0 added features and improvements. Highlights of Fabric OS 5.3.
Refer to the Brocade Access Gateway Administrator’s Guide available on http://www.hp.com/go/san for more information. Access Gateway support in non-Brocade fabrics In addition to being supported in Brocade fabrics, Access Gateway is supported for connectivity to the following: • McDATA fabrics running EOS 09.00.xx with Brocade FOS 5.2.1b • McDATA fabrics running EOS 09.02.xx or 09.03.xx with Brocade FOS 5.3.0 • Cisco fabrics running SAN-OS 3.0(2a) with Brocade FOS 5.2.1b • Cisco fabrics running SAN-OS 3.
• Additional password security options • Lockout of Admin users that fail authorization. • Flexible E_Port authentication settings, allowing better interoperability options for fabrics with varying levels of support. Certificate authentication is now optional. • Auditing of authorization attempts. FC4–16IP (iSCSI blade) Support for the FC4-16IP iSCSI blade was introduced with FOS 5.2.1b. This support continues with FOS 5.3.0.
If the DHCP feature is enabled and a connection (Ethernet cable) exists from the p-Class SAN switch to an Ethernet network where a DHCP service is active, the switch should request and obtain an IP address automatically. Additional enhancements New optional FC Fast Write feature for the 400 MP Router (Brocade 7500) and B-Series MP Router blade (FR4–18i) provides optimization and performance improvements for synchronous SCSI write operations. New Web Tools features in Fabric OS 5.3.
Prerequisites Table 1 summarizes current Fabric OS firmware versions. These are the earliest recommended software versions that work together. However, HP recommends using the latest supported firmware release versions to get the greatest benefit from the SAN. For a list of retired products, visit the HP web site http://www.hp.com. Table 1 Current supported Fabric OS versions Model Earliest compatible version Recommended version HP StorageWorks 1 Gb Switch 2.6.2c 2.6.
Firmware upgrade instructions IMPORTANT: HP strongly recommends that users upgrade to Fabric OS 5.3.0 as soon as possible. To access the latest Fabric OS 5.3.0 firmware, configuration files, and MIB files, go to the following HP web site: http://www.hp.com/go/san. CAUTION: Install port blades like the HP StorageWorks 4/48 SAN Director Blade (FC4–48) only after upgrading to Fabric OS 5.2.0a or later. HP does not support directly upgrading from more than two previous releases.
Important notes Table 2 provides information relevant to the release of Fabric OS 5.3.0. Table 2 Important release information Topic Description MSA 1000 and MSA 1500 For the FC4–48, if an MSA 1000 or MSA 1500 is directly connected to ports 32–47 of the blade, it will log in as a G-port. This has been seen on both active-active (v7.00.B700) and active-passive (v4.24.B272) MSA firmware. Ports 0 through 31 of this card log in correctly as F-ports. To prevent this from occurring when running Fabric OS 5.2.
FC4–48 port blade for the 4/256 SAN Director • The HP StorageWorks 4/48 SAN Director blade requires a minimum of Fabric OS 5.2.0a. Do not insert the FC4–48 blade into the 4/256 chassis until the chassis is running Fabric OS 5.2.0a or later. After Fabric OS has been updated and an FC4–48 has been installed, the Fabric OS will not be able to be downgraded earlier than 5.2.0a until the FC4–48 is removed. • The FC4–48 blade supports only core PID (fmt 1) in Secure Fabric OS.
Firmware upgrade/ downgrade • When upgrading from Fabric OS 5.1.0x to 5.2.0x or 5.3.0, if there are two or more inter-fabric links (IFLs) connected to an edge fabric, one IFL will stay online and the other IFLs will go online and offline. This will cause a temporary traffic disruption going from multiple IFLs to one IFL and then back to multiple IFLs. This is due to the new front domain consolidation feature in Fabric OS 5.2.0, where the IFLs connected to the same edge share the same front domain.
HA If there is an already segmented port and backbone devices are exported to an edge fabric, a build fabric/fabric reconfiguration can occur after running haFailover. Ensure that there are no segmented ports before upgrading firmware. IPSec for B-Series MP Router Blade (FR4–18i) • IPSec implementation details: • Pre-shared key • Main mode (IKE negotiation protocol) • Tunnel mode in Encapsulating Security Payload (ESP) • IPSec specific statistics not provided.
FCIP • Frame drops observed on FCIP slow links: • The frame drops occur when the FCIP tunnel bandwidth is set to 10 Base-T (10Mbps), E1 (1.048Mbps), or T1 (1.544Mbps). • With E1 or T1, frames are dropped even without an impaired link. • With 10 Base-T, frame drops may be observed when a low impairment is put to the link. • The portperfshow command indicated incorrect (smaller) bidirectional throughput on the FCIP tunnel when Fastwrite/Tape Pipelining is enabled.
Zoning considerations with FC4–48 blade B-Series switches running pre-5.2.0 firmware do not accept zone databases with Domain, Port Index, references to ports higher than 255. Zoning in Fabric OS 5.2.0 and later, therefore, do not allow a Domain, Port Index entry for ports above 255 to be created unless all switches in the fabric are at Zoning considerations continued... Fabric OS 5.2.0 or later versions. Once such an entry has been put into the zone database, an attempt to connect a pre-Fabric OS 5.2.
Fabric OS 5.3.0 fixes Table 3 lists defects closed in the Fabric OS 5.3.0 firmware release. Table 3 Fabric OS 5.3.0 closed defects Closed defect summary Solution 4/256 Director running FICON with fsmode enabled & DLS on and port based route policy panics after upgrade from Fabric OS 5.0.x to 5.1.x or 5.2.0. Fixed per Fabric OS 5.3.0 Kernel Ops error when counter is overrun during stress to fail test. Fixed per Fabric OS 5.3.
FICON traps sent with wrong “Enterprise” value resulting in trap being processed as a swFault. Fixed per Fabric OS 5.3.0 In Web Tools customized port detail report, the report will be generated for all ports even if the user gives a particular port range as a filter. Fixed per Fabric OS 5.3.0 On 2Gb/s platforms, switch panic can occur if unstable or faulty port generates excessive number of interrupts. Fixed per Fabric OS 5.3.
In a FICON environment a Switch panic (in the Management Server daemon) could be seen if the switch receives one of three FICON specific frames (FICON GCAP, RLIR, RNID) and the fabric goes "unstable" (fabric being rebuilt such as when one of the switches in the fabric is powered off) before a response is sent. Fixed per Fabric OS 5.3.0 Traffic can’t be routed into backbone fabric from EX_port on 400 MP router with domain ID 7 or 12 and from FR4-18i blade in 4/256 with various domain ID’s.
Modifying port speed and trunking on FC4-48 ports from Web Tools, followed by HAfailover, and then trying to re-launch, Port Admin window on those same ports fails to reload Web Tools window. Fixed per Fabric OS 5.3.0 F_Port route cleanup doesn’t happen correctly when NPIV is used on switch in Access Gateway mode. Fixed per Fabric OS 5.3.0 EZSwitch Setup device display is overlapped in Display Connection window when window size not maximized. Fixed per Fabric OS 5.3.
Portstats: Selecting the “Show delta” radio button and clicking on the clear counter button, doesn’t clear the counters. It changes the values to negative. Clicking the clear counter button again will reset counter to zero. Fixed per Fabric OS 5.3.0 May see FFDC warning messages when manually changing switch IP address in DHCP network. Fixed per Fabric OS 5.3.
During stress testing, switch may report fabric busy following issuance of a long string of operations repeatedly. Fixed per Fabric OS 5.3.0 When using interactive mode to execute pathinfo, but with an invalid source port value, there is no error message. Fixed per Fabric OS 5.3.0 After receiving login reject on FC4-16IP, subsequent login attempts may fail intermittently under some conditions. This can be avoided by moving the session back to init state after rejecting a login. Fixed per Fabric OS 5.3.
Denial-of-Service condition affecting X.509 certificates verification (NISCC #729618) due to SSL vulnerability in OpenSSL. FOS 5.3.0 includes new version of OpenSSL that resolves this. Fixed per Fabric OS 5.3.0 Incorrect time in Web Tools Switch Health report. Fixed per Fabric OS 5.3.0 Incorrect F_Port behavior when RX side of the cable is disconnected, while the TX side is still inserted. Fixed per Fabric OS 5.3.
