HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.1.1b Release Notes (AA-RWEEG - Page 17

Fabric OS 5.1.1a fixes, Fabric OS 5.1.1b fixes

Page 17 highlights

Fabric OS 5.1.1a fixes Table 4 lists defects closed per this Fabric OS 5.1.1a release. Table 4 Fabric OS 5.1.1a closed defects Closed defect summary Solution During testing with a vendor's new 4Gb HBA, a port on a 4/8 SAN Switch or 4/16 SAN Switch does not activate. When there are too many link level errors during link initialization with this particular HBA, avoid faulting the port too soon by disabling the primitive interrupts for a short period of time. Switch panic or CP failover when a kernel Applies a Linux kernel patch to allow correct process is started by a non-root user. tracking of the root process. Inserting an unsupported FC4-48 blade into a pre-Fabric OS 5.2 chassis causes FAULTY(1) error that will not clear with blade removal. The workaround if not upgrading to Fabric OS 5.1.1a is to schedule a convenient time to perform reboot of the active CP. Fabric OS 5.1.1b fixes Table 5 lists defects closed per this Fabric OS 5.1.1b release. Table 5 Fabric OS 5.1.1b closed defects Closed defect summary Solution Modifying an FCIP tunnel on a 400 MP Router or a B-Series MP Router blade running Fabric OS 5.1.1 or Fabric OS 5.1.1a may trigger a switch or blade fault. Fixed in Fabric OS 5.1.1b. 4Gb switches & MP routers can potentially Fixed in Fabric OS 5.1.1b. trigger a port FAULT after rebooting. Fabric OS 5.1.1b 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17

Fabric OS 5.1.1a fixes
Table 4
lists defects closed per this Fabric OS 5.1.1a release.
Table 4 Fabric OS 5.1.1a closed defects
Closed defect summary
Solution
During testing with a vendor’s new 4Gb
HBA, a port on a 4/8 SAN Switch or 4/16
SAN Switch does not activate.
When there are too many link level errors
during link initialization with this particular
HBA, avoid faulting the port too soon by
disabling the primitive interrupts for a short
period of time.
Switch panic or CP failover when a kernel
process is started by a non-root user.
Applies a Linux kernel patch to allow correct
tracking of the root process.
Inserting an unsupported FC4-48 blade
into a pre-Fabric OS 5.2 chassis causes
FAULTY(1) error that will not clear with blade
removal.
The workaround if not upgrading to Fabric
OS 5.1.1a is to schedule a convenient time
to perform reboot of the active CP.
Fabric OS 5.1.1b fixes
Table 5
lists defects closed per this Fabric OS 5.1.1b release.
Table 5 Fabric OS 5.1.1b closed defects
Closed defect summary
Solution
Modifying an FCIP tunnel on a 400 MP
Router or a B-Series MP Router blade
running Fabric OS 5.1.1 or Fabric OS
5.1.1a may trigger a switch or blade fault.
Fixed in Fabric OS 5.1.1b.
4Gb switches & MP routers can potentially
trigger a port FAULT after rebooting.
Fixed in Fabric OS 5.1.1b.
Fabric OS 5.1.1b
17