HP 4400 HP StorageWorks Fabric OS 6.2.2e Release Notes (5697-0809, February 20 - Page 36

Table 8 Fabric OS 6.2.1 closed defects (continued) Closed defect summary Solution In an FCR environment (with a router or switch configured for FCR), a switch Fixed in Fabric OS 6.2.1 runs out of memory when it is connected with the Mi10k. The Mi10k sends continuous RRQ frames because the Fabric OS-based switch did not handle RRQ frames with either accept or reject. Several problems occurred that were related to the configdownload commands. Some of these problems caused a core dump. Fixed in Fabric OS 6.2.1 A switch panic/hafailover occurs due to a weblinker.cfg panic seen during overnight slot command script test when modify/distribute ACL database, and during RNID response processing. Fixed in Fabric OS 6.2.1 A blade fault occurred in HP StorageWorks 4/256 SAN director on an 8-Gb 48-port blade in either slot 1 or slot 10 when the director was fully loaded with 8-Gb 48-port blades. Fixed in Fabric OS 6.2.1 Starting with Fabric OS 6.1.2, supportsave was updated to collect more Fixed in Fabric OS 6.2.1 data. A Parity error may be logged as data is read from disabled ports on switches that were updated from a lower code level but never cold booted. Frame Redirect zones cannot be created when defzone is set to allaccess. Fixed in Fabric OS 6.2.1 Workaround prior to update: Set defzone to noaccess. Memory leak during security script testing. Fixed in Fabric OS 6.2.1 In 8-Gb routed fabric, PLOGI in acceleration path did not program cam Fixed in Fabric OS 6.2.1 entry properly, leading to backbone hosts not being able to see edge fabric target. FCIP tunnels on the HP StorageWorks 400 MP Router or the MP Router blade do not come up due to a timing issue caused when using optical-to-copper converters in the path. Fixed in Fabric OS 6.2.1 In a cascaded Access Gateway configuration of three switches with both Fixed in Fabric OS 6.2.1 AGs in port group mode, when the QoS license is removed from the fabric switch and switchdisable/enable is performed, traffic continues for medium priority flows, but stops flowing for high and low priorities until the QoS license is reinstalled. When a trunk master port is disabled, Fabric Watch incorrectly sets the new trunk master's health to offline and the remote side to faulty, even though the port is online. This is a Web Tools display problem with no functionality impact. Fixed in Fabric OS 6.2.1 Unable to get F_Ports (trunk ports) data from Web Tools, but CLI works. Fixed in Fabric OS 6.2.1 Fabric becomes unstable after changing EX_Port trunk to E_Port trunk. Switches bounce between reachable and unreachable in edge fabric. Fixed in Fabric OS 6.2.1 Fabric OS 6.2 RADIUS Calling-station-ID (31) implementation is used for Fixed in Fabric OS 6.2.1 both device called by and workstation called from host name/IP address. As a result, RADIUS will not work properly and restriction of host access is not possible. When the host transmits PLOGI to the name server in Access Gateway Fixed in Fabric OS 6.2.1 mode, the name server responds with ACK then ACC. The AG forwards the ACC to the host, which responds with ACK, but it never gets forwarded back to the name server, causing the exchange to abort. OpenVMS init command does not complete, which prevents OpenVMS Fixed in Fabric OS 6.2.1 from mounting the file system with either the HP StorageWorks Encryption SAN Switch, or the encryption blade. During blade insertion or switch power up, the port fence disabled ports Fixed in Fabric OS 6.2.1 that are running diagtest trigger blade fault during blade POST. 36