HP StorageWorks Fabric OS 6.2.1 release notes Part number: 5697-0275 Second edition: December 2009...
Legal and notice information © Copyright 2009 Hewlett-Packard Development Company, L.P. © Copyright 2009 Brocade Communications Systems, Incorporated...
Version 6.2.1 NOTE: This software conforms to the Fibre Channel standards and accepted engineering practices and procedures. Effective date August 2009 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.1 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)
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 Multi-protocol Router TCP byte streaming for FCIP connections with WAN optimization hardware Improved FCIP statistics support, including TCP connection history, high watermark information, and connection snapshot capability Support of temporary licenses for Adaptive Networking, Integrated Routing, and Fabric Watch...
signing individual ports to a logical switch. Each logical switch is managed as a completely inde- pendent layer 2 Fibre Channel 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.
The portBeacon CLI command has been 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.
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 Multi-protocol Router blade. Fabric Watch—Monitors mission-critical switch operations, and now includes new Port Fencing capabilities.
Standards compliance This software conforms to the Fibre Channel 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 web site: http://www.hp.com. Update recommendations NOTE: With the introduction of Fabric OS 6.1.1, certain features and functions were removed from Web...
NOTE: The encryption switch and encryption blade are unique products compared to standard Fibre Channel switches. HP highly recommends that you read the Fabric OS Encryption Administrator's Guide before configuring these products in any fabric. Supported product models The following product models can be upgraded to Fabric OS 6.2.1: 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 SAN Switch 2/16, which operates with Fabric OS 3.2.x (Brocade 3800) HP StorageWorks SAN Switch 2/32 (Brocade 3900) HP StorageWorks Core Switch 2/64, which operates with Fabric OS 5.0.x (Brocade 12000) HP StorageWorks SAN Director 2/128 (Brocade 24000) HP StorageWorks Multi-protocol (MP) Router, which operates with XPath OS 7.4.x (Brocade AP7420) IMPORTANT:...
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.
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 lists the supported Fabric OS firmware versions. HP recommends using the latest supported firmware versions to get the greatest benefit from the SAN.
Table 1 Supported Fabric OS versions Model Earliest compatible version Recommended version Not supported, end of sup- HP StorageWorks 1-Gb Switch port (December 2007) HP StorageWorks SAN Switch 2/8 EL HP StorageWorks SAN Switch 2/16 3.2.1c 3.2.1c HP StorageWorks MSA SAN Switch 2/8 HP StorageWorks Core Switch 2/64 HP StorageWorks SAN Director 2/128 in Chassis 5.0.5e...
HP StorageWorks SAN Director 16 Port 8-Gb FC Blade (FC8-16) HP StorageWorks SAN Director 32 Port 8-Gb FC 6.1.0f 6.2.1 Blade (FC8-32) HP StorageWorks SAN Director 48 Port 8-Gb FC Blade (FC8-48) HP StorageWorks SAN Director 6 Port 10-Gb ISL 6.1.0f 6.2.1 Blade (FC10-6)
4/256 SAN Director blade support Fabric OS 6.2.1 is fully qualified and supports the Director blades listed in Table Table 2 4/256 SAN Director blade support matrix Director blade Number of blades FC4-16 FC4-32 Supported with any mix with up to eight blades of each FC4-48 type.
Power supply requirements for Director blades Table 4 lists power supply requirements for Director blades to provide full redundancy (220 VAC power is assumed). IMPORTANT: Director blades must meet minimum Fabric OS levels to operate in the Director chassis. For example, the FC8-32 is not supported in the 4/256 SAN Director with Fabric OS 6.0.x.
Important notes This section contains information that you should consider before you use this Fabric OS release. DCFM compatibility Fabric OS 6.2.1 is fully compatible with DCFM 10.1.x management software. DCFM is a comprehensive SAN management application that enables end-to-end management of HP B-series Data Center Fabrics.
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.1 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.
FICON MIHPTO Full Scalability (to maximum M-EOS fabric limits) Adaptive Networking QoS Adaptive Networking: Ingress Rate Limiting Advanced Performance Monitoring (APM) APM: Top Talkers Admin Domains Secure Fabric OS Fabric Watch Ports on Demand (POD) NPIV Timer Server Function (NTP) Open E_Port Broadcast Zoning FDMI...
Virtual Fabrics Logical Fabric using LISLs (XISLs in base Fabric) Indicates that the feature is available, but not officially tested or supported. 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.
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.1 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.1 from Fabric OS 6.1.0g or earlier, the CPs do not fully synchronize...
NOTE: With the introduction of Fabric OS 6.1.1, certain features and functions were removed from Web Tools (resident in the firmware) and migrated to the Data Center Fabric Manager (DCFM) management application. This has been carried forward to Fabric OS 6.2.x. HP recommends that before upgrading to Fabric OS 6.2.x or later, if you are not running DCFM on your fabric, you review the Web Tools functionality moved to...
tachometer. This situation leads to Fabric OS falsely reporting the fan/power supply as faulty, which could lead to unnecessary return of fan/power supply assemblies. This issue can be avoided by connecting the power cord to the fan/power supply and external power prior to seating it in the switch, then turning on the power switch immediately after insertion.
the QoS model. If the switch is rebooted, 28 of 32 ports will come up in QoS mode; the last four ports will come up in buffer-limited mode. Workarounds include disabling long distance configur- ation for these ports or explicitly disabling QoS on other ports, freeing up buffers for the last four ports.
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.
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.
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.
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.
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 set- tings before activating the Logical Switch.
HP recommends using DCFM for managing the following environments: pure FOS based fabrics, mixed FOS and M-EOS fabrics where the FOS switch/director is the seed switch. EFCM is the recommended management software for M-EOS only fabrics when a FOS switch or director can not be used as the seed switch.
If a port card is removed from a system with Virtual Fabrics enabled and replaced by a port card with fewer ports, the missing ports will not be able to be removed, which results in configuration change problems. To prevent this, the ports should be re- moved from the Logical Switch to which they are Serviceability assigned prior to the card being removed.
Define device alias Zone Admin Configure > Zoning Configure > Zoning The Compare dialog provides the Storage-Host and Host-Storage Device accessibility matrix Zone Admin view in a tree representation that is comparable to the Device Accessibility Matrix when all devices are selected. Fabric events Monitor >...
Once the LUN comes online and clear-text host I/O starts, modify the LUN from clear-text to encrypt, including the enable_encexistingdata option to convert the LUN from clear-text to encrypted. An exception to this LUN configuration process: if the LUN was previously encrypted by the HP Encryption Switch or HP Encryption Blade, the LUN can be added to the Crypto Target Container with the encrypt and lunstate =“encrypted”...
When creating an HA Cluster or Encryption Group with two or more HP Encryption Switch/En- cryption Blades, the GE Ports (I/O sync links) must be configured with an IP address for the eth0 and eth1 Ethernet interfaces using ipaddrset. In addition, both eth0 and eth1 Ethernet ports should be connected to the network for redundancy.
Perform a configdownload to the new GL node of a previously uploaded configuration file for the EG from an old GL Node. For any containers hosted on the failed GL node, issue cryptocfg --replace to change the WWN association of containers from failed GL node to the new GL node. Initial setup of encrypted LUNs IMPORTANT: While performing first-time encryption to a LUN with more than one initiator active at the time, rekey...
USB port LED of HP StorageWorks DC SAN Backbone Director CP Fixed in Fabric OS 6.2.0 blade stays ON after HA failover. CUP Port stuck in Contingent Allegiance State after z9 Host IPL. Fixed in Fabric OS 6.2.0 Spinfab and porttest (diagnostics) are not supported on ICL ports. Fixed in Fabric OS 6.2.0 Bogus core_file created and transferred after the first reboot after a Fixed in Fabric OS 6.2.0...
Fixed in Fabric OS 6.2.0 Workaround prior to upgrade: Reject code '0B' response to a QSA frame causes channel definition Block off a badly misbehaving port errors. that is generating bad traffic on a switch port that is putting a lot of stress on the embedded port.
In some instances, portshow may display inaccurate port authentic- Fixed in Fabric OS 6.2.0 ation description or state after a CP failover. Internal server ports on embedded platform: traffic may stop due to Fixed in Fabric OS 6.2.0 loss of buffer credit. The error message is cryptic when the interop fabric contains more than 60 devices in the default zone and the user tries cfgenablecfg- Fixed in Fabric OS 6.2.0...
Zone Transaction appears to succeed in SMIA when the transaction Fixed in Fabric OS 6.2.0 was aborted by web GUI. Port address from switchshow does not include offset used for Interop Fixed in Fabric OS 6.2.0 mode 2. Fixed in Fabric OS 6.2.0 Workaround prior to upgrade: CRC errors did not match between portstatsshow and port- Use portstatsshow to determine...
No F_RJT's being returned for class 2 frames that are not routable ac- Fixed in Fabric OS 6.2.0 cording to a QoS/TI configuration. Fixed in Fabric OS 6.2.0 B-series Multi-protocol Router blade failed to do blade firmwaredown- Workaround prior to upgrade: load.
Fixed in Fabric OS 6.2.0 Occasionally an LD port gets into a lock up state that causes port- GetVCCredits get failed and the ISL segments with LD incom- Workaround prior to upgrade: plete, although portcfgshow shows both sides of ISL config are the Reset with portcfgdefault/port- same.
Fixed in Fabric OS 6.2.0 Name Server database is being set with incorrect WWN's for NPIV Workaround prior to upgrade: nodes when port ALPA = 0x13. Port ALPA must be set to default value of 0x00 for ports hosting NPIV nodes. Potential timeouts and aborts during Device Discovery and CU busy Fixed in Fabric OS 6.2.0 processing when using FICON XRC Emulation.
Security Violation Console Message reported on nonexistent port# on an HP StorageWorks 4/64 SAN Switch (interopmode 2) with no se- Fixed in Fabric OS 6.2.0 curity policy set. Fabric OS does not send RSCN for CUP disable / enable in NI Fixed in Fabric OS 6.2.0 mode 2.
CAL exception “Non-Secure tunnel can not be configured on the same port as IP sec enabled tunnels.” come when trying to configure an IP Fixed in Fabric OS 6.2.0 Sec tunnel on a switch which already had Non secure tunnels in it. Fast Write will attempt to configure, even on an HP StorageWorks B- series Multi-protocol Router blade that has failed to initialize success- Fixed in Fabric OS 6.2.0...
Fixed in Fabric OS 6.2.0 Command ipaddrshow does not show the IP address of a blade that Workaround prior to upgrade: is seated in slot 12 of an HP StorageWorks DC SAN Backbone Direct- Issue ipaddrshow -slot 12 to get the information.
Fixed in Fabric OS 6.2.0 Workaround prior to upgrade: No RSCN sent for physical device offline/online. switchdisable/enable of the 400 MP router allows the devices to see each other. CRC error observed between HP StorageWorks 8/40 and 8/80 SAN Fixed in Fabric OS 6.2.0 switches with a particular SFP type.
Fabric OS 6.2.0b fixes Table 10 lists defects closed in the Fabric OS 6.2.0b firmware release. Table 10 Fabric OS 6.2.0b closed defects Closed defect summary Solution CUP can fail to send CU-End to clear busy. CUP is still responsive, but Fixed in Fabric OS 6.2.0b the host is waiting for the CUE.
Fabric OS 6.2.0c fixes Table 11 lists defects closed in the Fabric OS 6.2.0c firmware release. Table 11 Fabric OS 6.2.0c closed defects Closed defect summary Solution Workaround prior to upgrade: Lock the switch port to 8 Gb, rather than When port locked as G_Port, 8-Gb device may connect at 4 Gb rather rely on auto-negotiation.
Repeatedly disconnecting and reconnecting ISL links between the HP Fixed in Fabric OS 6.2.0c StorageWorks Encryption SAN Switch in an HA cluster environment while rekey operations are in progress may cause data miscompare. Internal recovery scheme can attempt to correct a valid Frame Redirec- Fixed in Fabric OS 6.2.0c tion RAM Filter, which can lead to one existing filter being corrupted, potentially causing misrouted frames.
Detected termination of 0.weblinker.fcg on HP StorageWorks Fixed in Fabric OS 6.2.0d DC04 SAN Director and messages like KSWD-1002, 5766, SLOT 4 | FFDC | CHASSIS, WARNING displayed on the console. After enabling Virtual Fabrics via DCFM on HP StorageWorks 8/40 Fixed in Fabric OS 6.2.0d SAN Switch, some ports may be disabled.
Two new FRU classes have been created in Fabric OS 6.2.0d Applications cannot distinguish between application blade and Core (coreblade and blades using SNMP. applicationblade). Two more values for SNMP port status: validating (10) [module is being validated] and SNMP object swFCPortPhyState gets invalid value 11. invalidModule (11) [module is invalid] have been added to Fabric OS 6.2.0d.
VEX port receives bad SFID and frame cannot be routed to translate Fixed in Fabric OS 6.2.0e domain due to continuous RTWR retries from backbone fabric where fabricshow is missing IP address. E-Port Class Link Resets are not fencing. RASLOG message will be Fixed in Fabric OS 6.2.0e presented indicating link resets are above threshold, but the port will not have been fenced as expected.
Fabric OS 6.2.0f fixes Table 14 lists defects closed in the Fabric OS 6.2.0f firmware release. Table 14 Fabric OS 6.2.0f closed defects Closed defect summary Solution Unexpected termination of a Remote Procedure Call (RPC) daemon Fixed in Fabric OS 6.2.0f occurs and then restarts non-disruptively.
An encrypted LUN goes into the internal encryption engine (EE) LUN state (Disabled (key not in sync)) as a result of rekeying and Fixed in Fabric OS 6.2.0g High Availability Cluster (HAC)/Data Encryption Key (DEK) cluster failover and failback. This results in the encrypted LUN not being available for crypto operations.
Fabric OS 6.2.1 fixes Table 16 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. These fixes are identified in Table Table 16 Fabric OS 6.2.1 closed defects Closed defect summary...
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 Fixed in Fabric OS 6.2.1 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.
A switch restart on HP StorageWorks DC SAN or DC04 director (power Fixed in Fabric OS 6.2.1 cycle or reboot of both CPs) causes random ICL E_Ports to be segmen- ted. 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 Fixed in Fabric OS 6.2.1 the message Oops: kernel access of bad area, sig: 11...
In 8–Gb routed fabric, PLOGI in acceleration path did not program Fixed in Fabric OS 6.2.1 cam entry properly, leading to backbone hosts not being able to see edge fabric target. FCIP tunnels on the HP Storageworks 400 MP Router and the Multi Fixed in Fabric OS 6.2.1 Protocol router blade do not come up due to a timing issue caused when using optical-to-copper converters in the path.
Firmwarecommit can fail on HP StorageWorks Encryption SAN Fixed in Fabric OS 6.2.1 Switch or Encryption blade with message regarding missing properties file when upgrading to Fabric OS 6.2.0d or later 6.2.0x version. Internal timing race condition can cause one or more F_ports or E_ports to be brought down, leading to frame discards.