HP StorageWorks Fabric OS 5.3.
Legal and notice information © Copyright 2008 Hewlett-Packard Development Company, L.P. © Copyright 2008 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.1a Effective date May 2008 Description Fabric OS 5.3.1a is a firmware release that contains fixes since the release of Fabric OS 5.3.1. It also includes all fixes from the Fabric OS 5.2.3 release on the 5.2 stream. There is no new device support added with this release for HP StorageWorks platforms. Update recommendations If your model is the SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32 or SAN Switch 2/128, HP strongly recommends that you upgrade to Fabric OS 5.3.1a as soon as possible.
• Brocade 4Gb SAN Switch for HP p-Class BladeSystem (Brocade 4012) • Brocade 4Gb SAN Switch for HP c-Class BladeSystem (Brocade 4024) 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.
• • • • • • • • • • • • • • Support for iSCSI re-direction • Support for CHAP binding • Support for LUN delete from a virtual target Access Gateway mode support on the HP StorageWorks 4/16 SAN Switch (not supported on the 4/8 SAN Switch) Access Gateway enhancements: • Web Tools support • Fabric Manager support • NPIV on F_ports Fibre Channel Routing enhancements IP Broadcast zone support IP over FC also via FCR IP Filter support (formerly MAC and Management port ACLs in Secure Fabric OS (SFOS)) Support
and virtual) attached to it while allowing easy SAN connectivity. The edge fabric switch provides all the fabric services while Access Gateway connects to the edge switch by what appears as a Host Bus Adapter (HBA) connection. This architecture allows the deployment of many additional servers without requiring a domain and the associated fabric rebuild traffic that is prevalent when switches are powered on, or added, or removed from a fabric.
IMPORTANT: Fabric OS 5.3.0 is the last major release that is compatible with SFOS. Fabric OS 5.3.
Prerequisites Table 1 summarizes current Fabric OS firmware versions. However, HP recommends using the latest supported firmware release versions to get the greatest benefit from the SAN. For a list of retired products, see the HP website http://www.hp.com. IMPORTANT: The Fabric OS versions listed in the Earliest compatible version column below are the earliest versions supported by HP at the time 5.3.1a released.
Model Earliest compatible version Recommended version HP StorageWorks SAN Director 16 Port 8Gb FC blade (FC8-16) 6.0.0b 6.0.0b HP StorageWorks SAN Director 32 Port 8Gb FC blade (FC8-32) 6.0.0b 6.0.0b HP StorageWorks SAN Director 48 Port 8Gb FC blade (FC8-48) 6.0.0b 6.0.0b HP StorageWorks SAN Director 6 Port 10Gb ISL blade (FC10-6) 6.0.0b 6.0.0b Fabric Manager 5.2.0a 5.4.0a NOTE: The B-Series MP Router Blade (for use with the 4/256 Director only) must run Fabric OS 5.1.0d or later.
• A Fabric OS 5.3.1a configuration file cannot be used on the same switch after the switch has been downgraded to firmware version 5.1.x or 5.2.x. • When you downgrade to Fabric OS 5.0.x, you must also remove additional 5.1.x features and any installed B-Series MP Router blades. Important notes Table 2 provides information relevant to the release. Table 2 Important release information Topic Description ipfilter command Starting with Fabric OS version 5.3.
Topic Description 4/256 SAN Director Fans operate at the correct speed; that is, at maximum on bootup. However, this initial speed may trigger an error message that indicates that the speed is too high (Above threshold). Disregard this message. Fans operate at the correct speed; that is, at maximum on bootup. However, this initial speed may trigger an error message that indicates that the speed is too high (Above threshold). Disregard this message.
Topic Description FC4-16IP iSCSI Blade for the 4/256 SAN Director • Do not insert the Blade until the system is running Fabric OS 5.2.1b or later. • iSCSI virtual target creation involves adding LUNs to the virtual targets. The user discovers the LUNs by executing the fclunquery command. Testing has revealed that some devices do not respond properly to the LUN query. The user will need to use tools from the array vendor to determine LUN information required for iSCSI target creation.
Topic Description FC Routing • If an HP StorageWorks MP Router is present in the backbone fabric, the command fcrDisable may take up to 8 minutes to complete. If the MP Router is replaced by a B-Series MP Router Blade (FR4-18i) or an HP StorageWorks 400 MP Router, the command completes immediately. • EX_Port trunking is not enabled by default. • FCR switch does not support an edge fabric with one McDATA switch set to ‘never principal’. The EX_Port connected to that edge fabric will not come up.
Topic Description Scalability • Support for Default Zoning policies has been added to Fabric OS 5.1.0. Typically, when you issue the cfgDisable command in a large fabric with thousands of devices, the name server indicates to all hosts that they can communicate with each other. To ensure that all devices in a fabric do not see each other during a cfgDisable operation, you can activate a Default Zone with policy set to no access.
Topic Description Access Gateway Mode Port State When a disabled port on a switch in Access Gateway mode is connected to a configured loop HBA, the port state alternates between Nosync and Insync. The switchShow command displays the state of the remote HBA port that is continuously attempting to reconnect to the disabled port. Access Gateway mode is not supported in the p-Class BladeSystem if there are two half-height servers (BL3xp) in the same sleeve (Server Slot 1 and 9, or 2 and 10, etc).
Topic Description iSCSI • Enterprise storage array targets may not show up consistently in the disk management window of an iSCSI initiator when the same LUNs are mapped to two different virtual targets (VTs). When the initiator logs in to the VTs, the targets keep disappearing from the disk management window. If the session to one of the VTs is disconnected, the remaining VT appears and stabilizes in the disk management window.
Additional Fabric OS 5.3.0 enhancements Additional Fabric OS 5.3.0 enhancements include: • Provides new Fabric OS commands to rename an alias, a zone and a zone configuration. Zone –copy copies the zone object to a new zone object. Zoneobjectrename renames the zone object. • Detects and handles a corrupted zone configuration [under /etc/fabos/zone*] gracefully instead of rebooting. The switch also logs the error in RASLog. • Adds a new command that provides both the WWN and serial number of the switch.
Closed defect summary Solution New active CP got Oops and reboot during initialization after hafailover command issued. Fixed in Fabric OS 5.3.0 After CP reboot, VE tunnel does not come up due to GE0 port on FR4-18i stuck in No_Sync state when using copper SFP’s. Fixed in Fabric OS 5.3.0 Switch does not generate RSCN following zoning changes using cfgEnable in interop mode, resulting in no PLOGI from hosts, and no target discovery. Fixed in Fabric OS 5.3.
Closed defect summary Solution With large zoneset (over 1200 zones) API library crashes as the zone library does memcpy that does not have terminating zero in the buffer. Fixed in Fabric OS 5.3.0 Change made in 5.2.0 to limit the number of FDISCs per unit of time, caused timeouts of NPIV logins in some BladeServer configurations with VC-FC. Fixed in Fabric OS 5.3.0. When FOS version prior to 5.2.0 is upgraded to a later version and the fabric.ops.mode.
Closed defect summary Solution Web Tools is missing “Invalid CRCS” under Fabric Watch end to end class pull down menu, due to missing “CRC Error” option. Fixed in Fabric OS 5.3.0 GUI component size squeezed due to lack of proper refresh after resizing. Fixed in Fabric OS 5.3.0 Errlog (raslog) messages not available for diagnosing DHCP problems. Fixed in Fabric OS 5.3.
Closed defect summary Solution If Dynamic Load Sharing (DLS) or In-Order Delivery is disabled, it can’t be enabled from Web Tools. However, it can be set/reset via CLI. Fixed in Fabric OS 5.3.0 Web Tools event filtering uses a time range of 0-11 rather than 1-12. In Web Tools Fabric Events and Events window, on invoking filter button and filtering based on “from” time or “to” time, on providing a time greater than 12 (e.g. 12:30 PM) will result in an error stating that time should be in range of 0-11.
Closed defect summary Solution SNMP traps repeatedly sent from the switch every 2 seconds when port taken out of a fault state implicitly by removing cable or module. Caused by too many port offline SCNs being sent out during port fault and recover when there is laser fault. Fixed in Fabric OS 5.3.0 Firmware downgrade to Fabric OS 5.1 or earlier is blocked even after ports 256 – 384 are removed from DCC policy created using [*] option. Currently have to delete DCC policy to avoid this.
Closed defect summary Solution Collecting supportsave info on 4/256 could cause error message on active CP console log. Fixed in Fabric OS 5.3.0 Host takes a long time to log in when disabled/unused GE-iSCSI ports have IP addresses configured to them. When host does a "SendTargets=All" those IP addresses will be in the list, but will be unreachable. Fixed in Fabric OS 5.3.0 After changing Backbone FID, switchshow does not display LE port information for some EX or VEX ports.
Closed defect summary Solution When upgrading 4/256 to Fabric OS 5.2.0b from 5.2.0a, both ISL trunk connections to an edge switch connected to FC4-16IP were lost. Found in test lab and due to “lab mode” setting, not accessible to customers. Fixed in Fabric OS 5.3.0 Counter Address_err counting inappropriate data. Fixed in Fabric OS 5.3.0 When assigning IP address to a GE port with no cable connection, the FC4-16IP Blade incorrectly reports back to iSCSI initiator that port is valid.
Table 4 Fabric OS 5.3.0a closed defects Closed defect summary Solution Iswitchd panic occurred during data migration with DMM when invalid frame issued to the switch. Fixed in Fabric OS 5.3.0a. Diag failure caused FA4-18 to report a fault after continuously running CP failover test. Fixed in Fabric OS 5.3.0a. Panic occurred on SAN Director 2/128 when running MS commands GPT/GPPN/GPS/GAPNL continuously. Fixed in Fabric OS 5.3.0a.
Closed defect summary Solution When the SFP/XFP power and voltage readings are above or below the range, an excessive number of alert messages were reported. Fixed in Fabric OS 5.3.0b. Third-party application will not work with the 400 MP Router Fast Write application (sends FCP_RSP without sequence initiative). Fixed in Fabric OS 5.3.0b.
Fabric OS 5.3.0d fixes Table 7 lists defects closed in the Fabric OS 5.3.0d firmware release. Table 7 Fabric OS 5.3.0d closed defects Closed defect summary Solution During POST & system verification tests, customer may see false failures from stress tests only intended for engineering design verification. Removed "minicycle" for all platforms as well as certain tests for multi-protocol router blade, & iSCSI blade, with 5.3.0d.
Linux kernel issue may occur on 2Gb switches running Fabric OS 5.3.0x caused by service daemon thread (fwd, nsd, fabricd) becoming unresponsive due to deadlock condition. This can trigger a panic, or snmpd hang. Fixed in Fabric OS 5.3.1 Fabric OS crash occasionally seen when Access Gateway enabled switch is rebooted with large number of Access Gateway devices in the fabric. Fixed in Fabric OS 5.3.1 During fastwrite, specific third party device drops a frame that is not 8 byte aligned.
Fabric OS 5.3.1a fixes Table 9 lists defects closed in this Fabric OS 5.3.1a firmware release. Table 9 Fabric OS 5.3.1a closed defects Closed defect summary Solution F_Port link initialization failure caused by the switch not responding to NOS with OLS (continues to send idles). Fixed in Fabric OS 5.3.1a When downgrading from 6.0.0x to Fabric OS 5.3.0c, then 5.2.1b, then 5.0.5a, the switch can get into an endless reboot causing file system errors to be reported. Fixed in Fabric OS 5.3.
