HP 1606 HP StorageWorks Fabric OS 6.3.1c Release Notes (5697-0509 September 2 - Page 83

With HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb, Fixed in Fabric OS 6.3.1

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

Page 83 highlights

Fabric binding does not work in 239 domain mode in Interopmode 3 Fixed in Fabric OS 6.2.2 with FCR on 8 Gb switches. EX port rejects it. Fixed in Fabric OS 6.3.1 Auto-assignment of slot based licenses for the Multiprotocol extension Fixed in Fabric OS 6.3.1 blade not working correctly when adding more than 2. Fabric Watch sometimes logs messages with values above 100%. Most likely occurs during first Fabric Watch polling cycle after slot- Fixed in Fabric OS 6.3.1 statsclear command is issued. Fabric class areas > Zoning Changes in fwconfigure does not function correctly. Zone changes do not get recorded in the FW module, Fixed in Fabric OS 6.3.1 resulting in appropriate threshold alarms not being raised. Unable to load IF.mib and SW.mib in AdventNet MIB Browser, resulting Fixed in Fabric OS 6.3.1 in the user being unable to load IF.mib and SW.mib. In a rare occurrence, HA synchronization is lost after a switch with trunk ports panics and manual reboot was needed to recover, due to race condition with trunk ports dropping Exchange Fabric Parameter (EFP) response. Fixed in Fabric OS 6.3.1 The following message may display on the console while firmware commit is in progress: ssnGet: Unable to get WWN info.sw= 0 rc=-5. Fixed in Fabric OS 6.3.1 Display of the CP disappeared from Web Tools when the blade exper- Fixed in Fabric OS 6.3.1 ienced a fault. After using the ipaddrset -cp command to set a host name of CP blade on any director switch, the standby CP incorrectly displays the host name of the CP rather than the chassis host name. For the change to take effect after firmware upgrade, the user must logout, then log back in to see the change. Fixed in Fabric OS 6.3.1 With HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb BladeSystem switches for p-Class and c-Class BladeSystem, speed negotiation fails when the port is locked as G_Port, and port cannot come online. Fixed in Fabric OS 6.3.1 The portbeacon command support has not been implemented in Fabric OS 6.3.x. Fixed in Fabric OS 6.3.1 Fixed in Fabric OS 6.3.1 CALD panic occurred on a director and CPs got out of sync, but no failover happened as CALD was in defunct state due to race condition. Workaround prior to upgrade: Manually reboot. When a host in a backbone fabric with a pair of Multiprotocol Extension blades, 1606 extension SAN switches, or a combination of the two is rebooted, it is unable to discover targets in the edge fabric due to timing window where a SID zone miss could drop a frame. If initiator does not retry PLOGI, it will fail to discover targets in the edge fabric. Fixed in Fabric OS 6.3.1 Workaround prior to upgrade: Disable and then enable the target. During power off/on switch test with HP StorageWorks DC SAN or DC04 SAN directors, a panic rather than a blade fault can occur when blades get too hot, or there is a bad temperature sensor, or spurious sensor reading. Fixed in Fabric OS 6.3.1 HP StorageWorks Fabric OS 6.3.1c Release Notes 83

  • 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
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
Fixed in Fabric OS 6.3.1
Fabric binding does not work in 239 domain mode in Interopmode 3
Fixed in Fabric OS 6.2.2 with FCR on 8 Gb switches. EX port rejects
it.
Fixed in Fabric OS 6.3.1
Auto-assignment of slot based licenses for the Multiprotocol extension
blade not working correctly when adding more than 2.
Fixed in Fabric OS 6.3.1
Fabric Watch sometimes logs messages with values above 100%. Most
likely occurs during first Fabric Watch polling cycle after
slot-
statsclear
command is issued.
Fixed in Fabric OS 6.3.1
Fabric class areas > Zoning Changes in
fwconfigure
does not
function correctly. Zone changes do not get recorded in the FW module,
resulting in appropriate threshold alarms not being raised.
Fixed in Fabric OS 6.3.1
Unable to load IF.mib and SW.mib in AdventNet MIB Browser, resulting
in the user being unable to load IF.mib and SW.mib.
Fixed in Fabric OS 6.3.1
In a rare occurrence, HA synchronization is lost after a switch with trunk
ports panics and manual reboot was needed to recover, due to race
condition with trunk ports dropping Exchange Fabric Parameter (EFP)
response.
Fixed in Fabric OS 6.3.1
The following message may display on the console while firmware
commit is in progress:
ssnGet: Unable to get WWN info.sw=
0 rc=-5
.
Fixed in Fabric OS 6.3.1
Display of the CP disappeared from Web Tools when the blade exper-
ienced a fault.
Fixed in Fabric OS 6.3.1
After using the
ipaddrset -cp
command to set a host name of CP
blade on any director switch, the standby CP incorrectly displays the
host name of the CP rather than the chassis host name. For the change
to take effect after firmware upgrade, the user must logout, then log
back in to see the change.
Fixed in Fabric OS 6.3.1
With HP StorageWorks 4/8 and 4/16 SAN switches, and 4 Gb
BladeSystem switches for p-Class and c-Class BladeSystem, speed ne-
gotiation fails when the port is locked as G_Port, and port cannot come
online.
Fixed in Fabric OS 6.3.1
The
portbeacon
command support has not been implemented in
Fabric OS 6.3.x.
Fixed in Fabric OS 6.3.1
Workaround prior to upgrade:
Manually reboot.
CALD panic occurred on a director and CPs got out of sync, but no
failover happened as CALD was in defunct state due to race condition.
Fixed in Fabric OS 6.3.1
Workaround prior to upgrade:
Disable and then enable the target.
When a host in a backbone fabric with a pair of Multiprotocol Extension
blades, 1606 extension SAN switches, or a combination of the two is
rebooted, it is unable to discover targets in the edge fabric due to timing
window where a SID zone miss could drop a frame. If initiator does
not retry PLOGI, it will fail to discover targets in the edge fabric.
Fixed in Fabric OS 6.3.1
During power off/on switch test with HP StorageWorks DC SAN or
DC04 SAN directors, a panic rather than a blade fault can occur when
blades get too hot, or there is a bad temperature sensor, or spurious
sensor reading.
HP StorageWorks Fabric OS 6.3.1c Release Notes
83