Table 14 Fabric OS 6.2.2c closed defects (continued)
SolutionClosed defect summary
With Fabric OS v6.2.2c, this specific occurrence of CDR-1003
is updated to log as a warning rather than critical. It can be
safely ignored unless it becomes persistent, or does not happen
during supportsave.
On B-series 4 Gb switches, multiple critical level
CDR-1003 raslog entries seen during
supportsave after non-disruptive upgrade from FOS
6.1.x to 6.2.x.
Fixed in Fabric OS 6.2.2c.
Workaround prior to update:
Use WebTools to create a zone/alias rather than DCFM.
WebTools nameserver is not reflecting the alias and
zones created in DCFM. Alias and zone to which the
device belongs is not displayed in the "member of
zone" and "member of alias" column.
Fabric OS 6.2.2d fixes
Table 15 (page 46) lists defects closed in the Fabric OS 6.2.2d firmware release.
Table 15 Fabric OS 6.2.2d closed defects
SolutionClosed defect summary
Fixed in Fabric OS 6.2.2d.During a reboot, the host might not come up when
connected to an HP StorageWorks 4/8 SAN Switch,
HP StorageWorks 4/16 SAN Switch, or Brocade 4
Gb SAN Switch for HP c-Class BladeSystem. The host
is unable to log in because the switch comes online
as a G_Port rather than an F_Port.
Fixed in Fabric OS 6.2.2d.Weblinker processes terminate and then restart when
the DCFM management application queries Top Talker
information from the switch.
Fixed in Fabric OS 6.2.2d.For all 8 Gb switches, the host is unable to discover
its targets after an HA failover or a code upgrade on
the router port. This is because the domain table
routing entry is accidentally cleared on an EX_Port.
Fixed in Fabric OS 6.2.2d.When Access Gateway mode is enabled, switch
panics occur during upgrades from FOS 6.1.x to FOS
6.2.2c. This does not occur when upgrading from
FOS 6.1.x to any other FOS 6.2 release.
Fixed in Fabric OS 6.2.2d.Fabric Watch messages (FW-1186 and FW-1190)
with invalid values can be logged at the first Fabric
Watch polling cycle after the slotstatsclear
command is issued.
Fixed in Fabric OS 6.2.2d.A switch that is connected locally can be disabled by
a remotely connected switch due to directional route
problems in the fabric. When this happens, messages
are logged in RASLOG indicating that RTWR has
reached the maximum retries.
Fixed in Fabric OS 6.2.2d.When Access Gateway mode is enabled, switches
can mishandle multisequence frames causing memory
corruption and agdd switch panic.
Fixed in Fabric OS 6.2.2d.A fabric containing two router devices in the
backbone, both connected via EX_Ports to the same
edge fabric through an M-EOS switch in IM 2 mode,
causes the router device to core dump and panic.
46
To Next Page
Loading...
