HP StorageWorks 2/64 HP StorageWorks Fabric OS 5.0.5b Release Notes (AA-RW1WD - Page 11

Fabric scalability, Problem determination, Fabric OS 5.0.5a fixes, Fabric OS 5.0.5b fixes

Page 11 highlights

Fabric scalability Fabric OS 5.0.5b supports the same fabric scalability as Fabric OS v4.4.0: 2,650 ports with 50 domains. Problem determination Fabric OS 5.0.5b features the fcPing command, which provides the ability to check Fibre Channel connectivity between any two nodes in a fabric. Fabric OS 5.0.5a fixes Table 2 lists improvements included in Fabric OS 5.0.5a. Table 2 Fabric OS 5.0.5a closed defects Closed Defects Host cannot see a specific device on 2Gb platforms: SAN Switch 2/32, Core Switch 2/64, SAN Director 2/128. The workaround if not upgrading to this latest 5.0.5a release is to remove and reinsert the cable, or run portDisable/portEnable. In rare cases, the zoning daemon (zoned) caused the switch to panic during HAfailover. An abrupt power failure on a port blade on a 4/256 SAN Director caused the CPs to sometimes fail. In the event of an abrupt power failure, the fix allows a small delay for the power failure to be reflected in the power status register. Revised the error message that displays when portCfgGPort is issued for embedded switches. Fabric OS 5.0.5b fixes Table 3 lists improvements included in Fabric OS 5.0.5b. Table 3 Fabric OS 5.0.5b closed defects Closed Defects Inserting unsupported FC4-48 blade into a pre-Fabric OS v5.2 chassis causes FAULTY(1) error that will not clear with blade removal. HAsync is dropped, and an active CP reboot is required to recover. If not upgrading to this Fabric OS 5.0.5b release the workaround is to schedule a convenient time to reboot the active CP. HBA occasionally may not log into a 4Gb switch during auto topology discovery. If not upgrading to this Fabric OS 5.0.5b release the workaround is to use portCfgGPort to lock the switch in G port mode. To reestablish the link on the affected port, issue portDisable and portEnable. Fabric OS 5.0.5b 11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13

Fabric scalability
Fabric OS 5.0.5b supports the same fabric scalability as Fabric OS v4.4.0: 2,650
ports with 50 domains.
Problem determination
Fabric OS 5.0.5b features the
fcPing
command, which provides the ability to check
Fibre Channel connectivity between any two nodes in a fabric.
Fabric OS 5.0.5a fixes
Table 2
lists improvements included in Fabric OS 5.0.5a.
Table 2 Fabric OS 5.0.5a closed defects
Closed Defects
Host cannot see a specific device on 2Gb platforms: SAN Switch 2/32, Core Switch
2/64, SAN Director 2/128.
The workaround if not upgrading to this latest 5.0.5a release is to remove and reinsert the
cable, or run
portDisable
/
portEnable
.
In rare cases, the zoning daemon (zoned) caused the switch to panic during HAfailover.
An abrupt power failure on a port blade on a 4/256 SAN Director caused the CPs to
sometimes fail. In the event of an abrupt power failure, the fix allows a small delay for the
power failure to be reflected in the power status register.
Revised the error message that displays when
portCfgGPort
is issued for embedded
switches.
Fabric OS 5.0.5b fixes
Table 3
lists improvements included in Fabric OS 5.0.5b.
Table 3 Fabric OS 5.0.5b closed defects
Closed Defects
Inserting unsupported FC4-48 blade into a pre-Fabric OS v5.2 chassis causes FAULTY(1)
error that will not clear with blade removal. HAsync is dropped, and an active CP reboot
is required to recover. If not upgrading to this Fabric OS 5.0.5b release the workaround
is to schedule a convenient time to reboot the active CP.
HBA occasionally may not log into a 4Gb switch during auto topology discovery. If not
upgrading to this Fabric OS 5.0.5b release the workaround is to use
portCfgGPort
to lock the switch in G port mode. To reestablish the link on the affected port, issue
portDisable
and
portEnable
.
Fabric OS 5.0.5b
11