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

Fabric OS 6.2.2d fixes, Table 14 Fabric OS 6.2.2c closed defects

Get HP 4400 PDF manuals and user guides View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 46 highlights

Table 14 Fabric OS 6.2.2c closed defects (continued) Closed defect summary Solution On B-series 4 Gb switches, multiple critical level With Fabric OS v6.2.2c, this specific occurrence of CDR-1003 CDR-1003 raslog entries seen during is updated to log as a warning rather than critical. It can be supportsave after non-disruptive upgrade from FOS safely ignored unless it becomes persistent, or does not happen 6.1.x to 6.2.x. during supportsave. WebTools nameserver is not reflecting the alias and Fixed in Fabric OS 6.2.2c. zones created in DCFM. Alias and zone to which the Workaround prior to update: device belongs is not displayed in the "member of zone" and "member of alias" column. Use WebTools to create a zone/alias rather than DCFM. 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 Closed defect summary Solution During a reboot, the host might not come up when Fixed in Fabric OS 6.2.2d. 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. Weblinker processes terminate and then restart when Fixed in Fabric OS 6.2.2d. the DCFM management application queries Top Talker information from the switch. For all 8 Gb switches, the host is unable to discover Fixed in Fabric OS 6.2.2d. 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. When Access Gateway mode is enabled, switch Fixed in Fabric OS 6.2.2d. 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. 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 Fixed in Fabric OS 6.2.2d. 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. When Access Gateway mode is enabled, switches Fixed in Fabric OS 6.2.2d. can mishandle multisequence frames causing memory corruption and agdd switch panic. 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. Fixed in Fabric OS 6.2.2d. 46

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
Table 14 Fabric OS 6.2.2c closed defects
(continued)
Solution
Closed 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
Solution
Closed 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