HP StorageWorks 2/32 HP StorageWorks Fabric OS 5.2.1b Release Notes (AA-RWEYC- - Page 19

Non-disruptive configdownload may fail if invalid threshold alarm filter is used, due to invalid value. Fixed per Fabric OS 5.2.1. On 4/256, moving the switch PID to 2, waiting for the fabric to stabilize, and then issuing hafailover causes an assert on the new active CP. Fixed per Fabric OS 5.2.1. Redundant message about EX port trunking resulted from checking system settings for firmwaredownload Fabric OS 5.2.0 to 5.1.0d. Fixed per Fabric OS 5.2.1. Portperfshow command does not display traffic on configured VE tunnel. However, issuing the portstatsshow command displays the traffic. Fixed per Fabric OS 5.2.1. Downloading a config file that contains only Fabric Watch parameters incorrectly fails when header and termination labels are absent. Fixed per Fabric OS 5.2.1. After MPR 400 shut down, the other side of VE links on a 4/256 still has stale/uncompleted info of VE links on switchshow. Fabricshow still has some incomplete info from the MPR 400. Fixed per Fabric OS 5.2.1. In User Defined AD [Device members]/ADO, inconsistencies observed for GiGE Port Details. Fixed per Fabric OS 5.2.1. When pathinfo CLI is used in interactive mode with extended stats, reverse path and strict source route an error is returned if hop count given is less than total hop count required to reach destination domain plus the reverse path. Fixed per Fabric OS 5.2.1. Disabling and enabling a trunk master on a 4/256 causes 4/16 switch on other side of the ISL to be stuck at Port_Flt. Not likely in user Fixed per Fabric OS 5.2.1. scenario as this was found in stress-to-fail testing. In Web Tools, if user tries to configure the port speed through port admin services window for FC4-48 port, the port is also getting flagged as locked G-port when observed through portcfgshow CLI. No impact to functionality. Fixed per Fabric OS 5.2.1. On 4/256, rtedebug cli returns error "REASON: ROUTE_ABSENT" for a device connected to FC4-48 port blade during stress testing. Fixed per Fabric OS 5.2.1. When multiple API clients try to get default zone mode at the same time, core files can be generated by the common access layer daemon Fixed per Fabric OS 5.2.1. on the switch. Port Zoning view displays the info when a user refreshes AD information from the fabric. AD membership information in the ZET is broken for the refresh operation on the Port Zoning view. Fixed per Fabric OS 5.2.1. Inserting an FC4-48 blade into a pre-Fabric OS 5.2 chassis (unsupported) causes FAULTY(1) error that will not clear with blade removal. Fixed per Fabric OS 5.2.1. When host PC uses the Java plugin 1.4.2_08, the event time filter is filtering on the basis of AM time when PM time is provided in "TO" field. Fixed per Fabric OS 5.2.1. The supportsave command fails with illegal option -s saving CORE FFDC. Fixed per Fabric OS 5.2.1. RCSD panic during zone activation on 4/32 due to shared memory allocation failure. Fixed per Fabric OS 5.2.1. If HBA sends previously assigned PID in the SID of the FLOGI on ports 32-47 on the FC4-48 port blade will come up as a g-port. Fixed per Fabric OS 5.2.1. Some operations initiated from Fabric Manager, Web Tools, and/or SMI-A will fail if the system switch is running Fabric OS v5.2.0a for more than 30 days. Fixed per Fabric OS 5.2.1. HP StorageWorks Fabric OS 5.2.1b release notes 19