HP 4400 Release Note page 40

Table 1 1 Fabric OS 6.2.2 closed defects (continued)
Closed defect summary
A switch panic occurs due to third-party management application giving
bad response or no response to FCP LUN request.
SwNs table lists one fewer name server entry than the actual number of
devices (first entry shown in nsallshow CLI command)
The urouteshow command lags for several seconds while displaying the
route information. The lag is longer on products with large port counts, such
as directors
The errorshow command log still shows the original chassis name after
a chassis name change.
The sequence of creating two TI zones, not saving the change, and then
modifying the attributes with the zone --add command results in
misconfigured attributes that will cause software verify on remote switches
when changes are committed. This can lead to a switch reboot or panic.
Configuring IP address of CP1 blade from CP0 on any director: after
hafailover the hostname portion of the configuration is no longer there
for CP1. Other IP configuration information remains intact.
The switchstatusshow command output was not updated after the faulty
blade (multiprotocol router blade, multiprotocol extension blade, or 10/24
FCoE blade) was brought back up, enabled, and online.
FDMI: fdmid crashes when a Brocade HBA with virtual ports is connected
to a 4/256 SAN Director.
Fabric Watch SFP messages get logged after upgrade to Fabric OS 6.1.1b,
due to I2C read values of 0xff and I2C NACK error case not being properly
handled.
Switch gets nsd panic when third-party switch in interopmode 3 and Fabric
OS 6.2 sends invalid frames.
Server does not see some devices on shared primary ports connected to
48 port blades using domain/port session based zoning.
The configdownload command does not load tstimezone info after
changing tzh and tzm in the config.txt file to new values.
Transient detected error on internal link caused 8-Gb blade to be faulted
with reason=5 or 4.
40
Solution
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Workaround prior to update: Other
methods of creating TI Zones and
modifying the definitions work seamlessly.
It is just this odd set of steps that produce
the failing condition. When creating
multiple TI zones, they should be saved
before modifying the attributes. You can
clean up problem by using zone --add
to modify the attributes again after the
save. You can also delete and re-create
the TI zone.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Run the
ipaddrset command again from CP1
to configure CP1 hostname.
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Workaround prior to update: Log out all
the devices that have registered their HBA
information and log them in after the
fabric is stable.
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Fixed in Fabric OS 6.2.2
Workaround prior to update: Set up
tstimezone through CLI.
Fixed in Fabric OS 6.2.2
Workaround prior to update: Use
slotpoweroff and slotpoweron to
clear the fault.