HP StorageWorks 1606 HP StorageWorks Fabric OS 6.3.0a release notes (5697-0359 - Page 68
Fabric OS 6.3.0a fixes, lists defects closed in the Fabric OS 6.3.0a firmware release.
![]() |
View all HP StorageWorks 1606 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 68 highlights
Adding a tapepool (commit) cause hacluster failover even the (container Fixed in Fabric OS 6.3.0 owner) switch is still disabled. Error message may be seen on console under heavy utilization of in- Fixed in Fabric OS 6.3.0 terface to key vault. Re-key starts and host IO is blocked on failover/failback with mismatched time on EE nodes. Fixed in Fabric OS 6.3.0 FOS-FVT- Check Condition Not Propagated On Read to Physical Initi- Fixed in Fabric OS 6.3.0 ator (PI). Fixed in Fabric OS 6.3.0 FCIP tape pipelining does not propagate task retry identification (TRI). Workaround prior to code change: Disable FCIP Tapepipelining. Several harmless messages gets generated when DCFM tries to discover Fixed in Fabric OS 6.3.0 a large fabric. During stress-to-fail testing of Cold Start/Recovery on a switch with multiple Logical Switches, the local Name Server misses some device entries. Fixed in Fabric OS 6.3.0 Workaround prior to code change: Perform switchdisable/enable on the affected switches. Same device ( WWN ) is visiable in more than 2 fabric using VF function and VT not getting imported. Fixed in Fabric OS 6.3.0 Port Auto Disable - Wrong message when disabling port auto disable. Fixed in Fabric OS 6.3.0 After few hafailovers, FC fast write I/O times out and a few unexpected frame drops are seen on 1 to 2 ports out of 7-8 ports running. Fixed in Fabric OS 6.3.0 Workaround prior to code change: Disable FCFW feature or limit the number of HA Failover sequences to times when IO is not active. Desired distance is editable for the long distance mode L0:Normal initially when the page loads. Fixed in Fabric OS 6.3.0 Fabric OS 6.3.0a fixes Table 9 lists defects closed in the Fabric OS 6.3.0a firmware release. Table 9 Fabric OS 6.3.0a closed defects Closed defect summary Solution Switch panic occurs due to Out Of Memory condition when manage- Fixed in Fabric OS 6.3.0a ment application issues repeated FCR LUN emulation queries via SMI, Workaround prior to code change: or when polling a switch that had its password changed multiple times. Disable SMI agents. sysshutdown on 8Gb SAN Switch for HP BladeSystem c-Class may cause panic and reboots. Fixed in Fabric OS 6.3.0a Workaround prior to code change: Use the CLI shutdown command. 68
![](/manual_guide/products/hewlettpackard-storageworks-1606-hp-storageworks-fabric-os-630a-release-notes-56970359-2010-10ce243/68.png)