HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.2 release notes (5697-7964 - Page 18

Automatic Fabric Configuration Server FCS policy distribution will, Fixed in Fabric OS 5.3.1

Page 18 highlights

Intermittent supportsave failure messages seen during supportsave loop. Fixed in Fabric OS 5.3.1 Traffic stops during FCIP testing with tape pipelining enabled, when host floods the switch with Name Server query. This occurs because the query response is not passed back to the host on the backbone switch through the FCR router. Fixed in Fabric OS 5.3.1 When executing fastwrite with tape pipelining with a slow responding tape device, the switch sent improper frame causing tape job to Fixed in Fabric OS 5.3.1 fail. Ultimately, this caused the initiator to lose access to the tape drive. When FICON host sends PLOGI directly to a device immediately after registering with the Management Server, PLOGI may be rejected be- Fixed in Fabric OS 5.3.1 cause the routing tables have not been established. Incorrect GID FT response from Name Server caused host with multiple HBAs to log errors during HBA IOP reset. When host does its GID FT request, it gets a response for the other HBA though that HBA didn't register for FC4 type. Subsequent PLOGI, PRLI sequence to the nonFC4 type HBA is rejected and an error logged on the host. Fixed in Fabric OS 5.3.1 Automatic Fabric Configuration Server (FCS) policy distribution will not work properly on a future release with current Fabric OS 5.x in the fabric. Fixed in Fabric OS 5.3.1 Port scn removes logical paths from wrong port, resulting in some paths not coming online. Fixed in Fabric OS 5.3.1 If CALD restarts, it can no longer provide CAL cache data on EM, leading to possible SMI agent experiencing a reconnect issue. Fixed in Fabric OS 5.3.1 When Third party system sends PLOGI/PRLI frames with its DID as a broadcast format, the 2/128 forwards the frame as a broadcast frame to all switch ports, causing other devices in the fabric to malfunction and overextend the switch CPU. This issue only affects 2/128. Fixed in Fabric OS 5.3.1 Occasional kernel panic occurs during reboot. Fixed in Fabric OS 5.3.1 18

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22

Fixed in Fabric OS 5.3.1
Intermittent
supportsave
failure messages seen during
sup-
portsave
loop.
Fixed in Fabric OS 5.3.1
Traffic stops during FCIP testing with tape pipelining enabled, when
host floods the switch with Name Server query. This occurs because
the query response is not passed back to the host on the backbone
switch through the FCR router.
Fixed in Fabric OS 5.3.1
When executing
fastwrite
with tape pipelining with a slow respond-
ing tape device, the switch sent improper frame causing tape job to
fail. Ultimately, this caused the initiator to lose access to the tape drive.
Fixed in Fabric OS 5.3.1
When FICON host sends PLOGI directly to a device immediately after
registering with the Management Server, PLOGI may be rejected be-
cause the routing tables have not been established.
Fixed in Fabric OS 5.3.1
Incorrect GID FT response from Name Server caused host with multiple
HBAs to log errors during HBA IOP reset. When host does its GID FT
request, it gets a response for the other HBA though that HBA didn’t
register for FC4 type. Subsequent PLOGI, PRLI sequence to the non-
FC4 type HBA is rejected and an error logged on the host.
Fixed in Fabric OS 5.3.1
Automatic Fabric Configuration Server (FCS) policy distribution will
not work properly on a future release with current Fabric OS 5.x in
the fabric.
Fixed in Fabric OS 5.3.1
Port
scn
removes logical paths from wrong port, resulting in some
paths not coming online.
Fixed in Fabric OS 5.3.1
If CALD restarts, it can no longer provide CAL cache data on EM,
leading to possible SMI agent experiencing a reconnect issue.
Fixed in Fabric OS 5.3.1
When Third party system sends PLOGI/PRLI frames with its DID as a
broadcast format, the 2/128 forwards the frame as a broadcast frame
to all switch ports, causing other devices in the fabric to malfunction
and overextend the switch CPU. This issue only affects 2/128.
Fixed in Fabric OS 5.3.1
Occasional kernel panic occurs during reboot.
18