HP 1606 HP B-series Fabric OS 6.4.1b Release Notes (5697-0886, March 2011-incl - Page 50

Table 9 Fabric OS 6.4.0 closed defects (continued) Closed defect summary Solution WWN Based PID Assignment assigning wrong PID to port in first position Fixed in Fabric OS 6.4.0 in wwnAddress -show PID binding list. Problem running traffic over ports after FCIP bounce. FCIP link recovers, but Fixed in Fabric OS 6.4.0 routes to FC ports do not. With SNMP severity set to 3, the DC SAN Backbone director sends out traps Fixed in Fabric OS 6.4.0 when a core blade is inserted, but not when it is removed. RTWR (Reliable Transport Write and Read) messages are logged when more Fixed in Fabric OS 6.4.0 than 16 dynamic paths are set up to remote domains on HP 8Gb switches. Workaround prior to upgrade: You may experience path loss and traffic interruption. Limit the number of dynamic paths on these platforms. If there are more than 16 dynamic paths already on these platforms, upgrade to the fixed release could be a cold recovery. When an HP 10/24 FCoE blade is installed in the highest number slot in a Fixed in Fabric OS 6.4.0 DC SAN Director or DC04 SAN Director, it will not send out any UAs Workaround prior to upgrade: (unsolicited advertisements), so FCoE traffic will not occur. Install FCOE10-24 to lower slot. Switch displays incorrect information upon userconfig --show command Fixed in Fabric OS 6.4.0 execution. Changes to admin password on a switch are not being recorded properly (password last change date shows incorrect date). Zoning restriction does not work for NPIV/loop ports when one device tries to get another device's information on the same port using name-based queries (GID_PN, GID_NN), which could lead to device communication failures. Fixed in Fabric OS 6.4.0 Host failed to discover tapes due to a VI/VT (Virtual Initiator/Virtual Target) Fixed in Fabric OS 6.4.0 database mismatch between the switches that are part of the same Encryption Workaround prior to upgrade: Group (EG). As a result, the host cannot discover tape devices that are part of the same EG. Issue cryptocfg --commit again to sync up the VT/VI database across nodes in the EG. In FICON environment, detected termination of process ficud:2658, running Fixed in Fabric OS 6.4.0 Fabric OS 6.2.0e. Ports on the DC SAN director 48 port 8Gb blade become persistently disabled after upgrading from Fabric OS 6.2.x to 6.3.x with VF disabled and fmsmode enabled. Fixed in Fabric OS 6.4.0 Workaround prior to upgrade: Manually re-enable ports. After moving some servers from backbone to edge, FCR-1022 messages are Fixed in Fabric OS 6.4.0 seen and devices are no longer getting exported into backbone. If backbone and edge fabric have different switch PID formats, such as when edge fabric is in IM2 mode, while backbone fabric is not, un-import a device did not free up resource. When resource is exhausted, importing another device into the backbone fails with [FCR-1022] Local proxy device slot entries exhausted in raslog . Both 4Gb and 8Gb FCRs are affected and are more likely to be seen if there is frequent device offline/online in edge fabrics. Termination of non-restartable daemons always triggers failover/reboot for Fixed in Fabric OS 6.4.0 recovery, Termination of non-VF and non-FSS compliant daemons (raslogd and traced) always triggers stateless restart. However, in certain cases, cold recovery can be triggered by the restart of a restartable daemon. Enhancement request to add a user selectable parameter to adjust SFP polling Fixed in Fabric OS 6.4.0. New during high CPU load situation. parameter added to Fabric OS 6.4.0 to allow adjustment of SFP polling interval to avoid laser faults. 50