HP 1606 HP StorageWorks Fabric OS 6.3.2b Release Notes (5697-0777, November 20 - Page 48

Fabric Watch FW-1186 and FW-1190 messages are logged with values above 100%. Likely to occur during first Fabric Watch polling cycle Fixed in Fabric OS 6.3.2a. after slotstatsclear command has been issued. Traffic routed through an 8Gb 48 port blade in a DC SAN Backbone director running Fabric OS 6.3.0 through 6.3.2 will be misrouted following an HA failover. HA failover can be triggered in numerous ways including a firmware upgrade. When this occurs in this configuration, the DCX misroutes traffic on a primary shared area port after a secondary shared area F_Port goes though a route recalculation. Level of disruption varies from causing a SCSI abort, RTWR error, to hosts and targets losing the ability to communicate. Workaround prior to upgrade: Bounce affected primary port or move device off the secondary shared area port. Fixed in Fabric OS 6.3.2a. Fabric gets into a mode where communications between the local switch and remote switch flow in only one direction, causing the remote switch to disable the local switch without any notification or reason being logged. Messages are seen indicating RTWR has reached max retries in RASLOG. Fixed in Fabric OS 6.3.2a. Multi-sequence frames are not properly handled by switches in Access Fixed in Fabric OS 6.3.2a. Gateway mode, leading to memory corruption and switch agdd panic. Formatting of errdump messages resulting from changes made to support virtual fabrics causes some firmware upgrade log messages related to the previously installed version of Fabric OS to be lost after upgrade to Fabric OS 6.2.0 or later. Fixed in Fabric OS 6.3.2a. Haenable command is not auto rebooting the standby CP when the standby CP is removed and reseated/replaced. As a result the active and backup CP end up out of synch. Can occur with either 4Gb or 8Gb director class switches. Workaround prior to upgrade: Reboot the standby CP manually. Fixed in Fabric OS 6.3.2a. A multiple critical CDR-1003 raslog occurred during supportsave. After a non-disruptive upgrade from Fabric OS 6.1.x to Fabric OS 6.2.x, CDR-1003 CRITICAL messages may be posted during a supportSave operation on Brocade 4Gb platforms. With the fix in this release, the critical message is updated to a Warning and it can be ignored unless it is persistent and does not occur during supportsave. Workaround prior to upgrade: Ignore if CDR-1003 occurs during supportsave and is not persistent. Fixed in Fabric OS 6.3.2a. With some types of servers that do not cut off the light during reboot, the connected switch cannot bring an F_Port on line for a long time due to multiple reinitialization attempts caused by unstable signal/port fault period. Fixed in Fabric OS 6.3.2a. Network security vulnerabilities identified via network vulnerability scan Fixed in Fabric OS 6.3.2a. need to be addressed with the encryption switch and blade. Newly active CP fails to completely recover from either firmware download (6.2.x to 6.3.x) or hafailover, due to persistent disabled GE_Port on Multi-protocol router blade. Requires a reboot of both CPs to regain hasync. Can occur with either 4Gb or 8Gb director class switches. Fixed in Fabric OS 6.3.2a. On Multi-protocol router blade or 400 MP router, after a TCP/FCIP processor panic, the CP panics with a "Oops: kernel access of bad area" message when attempting to output RASLOG messages. Fixed in Fabric OS 6.3.2a. 48