HP StorageWorks 4/16 HP StorageWorks Fabric OS 5.3.1a release notes (AA-RWEYJ- - Page 19

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 Fixed in Fabric OS 5.3.0. with VC-FC. When FOS version prior to 5.2.0 is upgraded to a later version and the fabric.ops.mode.pidFormat value was previously set to zero, the switch will continually reboot. Fixed in Fabric OS 5.3.0 In extremely rare conditions when a particular timing window is hit at the same time an internal end to end monitor wraps its counter, the standby CP can get stuck in a reboot loop. The condition is that due to a race condition, a partial HA update arrives before a full update from the active CP, resulting in standby CP going into continuous restart cycle. Fixed in Fabric OS 5.3.0 When MS request issued with WWN that didn't exist in the fabric, the MS Daemon panicked. Fixed in Fabric OS 5.3.0 The 2/128 was forwarding PLOGI frames received with DID as broadcast format which was causing issues with other devices in the fabric. Fixed in Fabric OS 5.3.0. No longer forwards these type of frames. For platforms running 5.2.0 and above with domain, port zoning, there is a small window during which if a device sends it PLOGI very fast, and before the nameserver information has been fully propagated, the PLOGI may be dropped. Fixed in Fabric OS 5.3.0 CLI systemverification command incorrectly reports false positive failure on FC4-16IP Blade. This diagnostic command is not typically run by a customer. Fixed in Fabric OS 5.3.0 "Stats" menu option does not work when executing minicycle command. Fixed in Fabric OS 5.3.0 Process login drop due to devices in different edge fabrics with same node WWN. Applies to 4/256 with FCR-18i Blade, and 400 MP Router. Routers may not forward the Nameserver request to proper domain, resulting in request timeout & retries every 2 seconds. Fixed in Fabric OS 5.3.0 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 in 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 Fixed in Fabric OS 5.3.0 with various domain ID's. Rapidly issuing repeated supportsave commands can cause switch panic due to out of memory condition. Fixed in Fabric OS 5.3.0 When interop mode set to 1, "Disable NodeName Zone Checking" parameter also changes from 0 to 1, but returns to 0 after switch reboot. Fixed in Fabric OS 5.3.0 Due to race condition in RNID command from FICON channels, FICON CUP daemon crashes and switch panics after switch comes up then it starts processing the RNID command. Problem affects FICON environment for Fabric OS 5.1 and later. Fixed in Fabric OS 5.3.0 Web Tools error message provided when fmsmode setting fails is not clear. Fixed in Fabric OS 5.3.0 HP StorageWorks Fabric OS 5.3.1a release notes 19