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

Fixed in Fabric OS 6.3.1b, bit_address] command prior

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 89 highlights

After 1606 extension switch reboot, PLOGI aborts seen due to F_RJT for the ACCEPT frame. Host cannot see the target if PLOGI comes in before RSCN is propagated on the 1606 extension switch or multiprotocol extension blade VE ports due to backend port programming not completing in time. Fixed in Fabric OS 6.3.1b In a rare corner case, the encryption switch or encryption blade does not handle an error case correctly when key attribute retrieval from key Fixed in Fabric OS 6.3.1b vault fails, leading to a panic. With two FCRs (routers or switches with IR functionality) in the backbone and both connected to the same edge fabric through EX ports, and edge fabric has MEOS in IM2 mode, switch can panic upon receiving periodic GE_PT from MEOS switches due to the FCR not handling it properly. Fixed in Fabric OS 6.3.1b Internal ports of of 8Gb c-Class switch need to be forced to arb/arb for portcfgfillword (mode 1) to improve characteristics for future mezzanine card. Fixed in Fabric OS 6.3.1b HP 1606 extension switch and multiprotocol extension blade do not always auto-restart after detection of a critical error when running Fabric OS 6.3.1a. A manual reboot may be required to recover the 1606 switch and a slot power off/on to recover the multiprotocol extension blade. Fixed in Fabric OS 6.3.1b Supportsave hangs after unplugging and then plugging in the network cable on the encryption switch or blade due to a race condition that causes the encryption switch cluster to update continuously and supportsave not to finish. Fixed in Fabric OS 6.3.1b On HP 8/8, 8/24, 8/40 and 8/80 switches shipped with Fabric OS 6.3.1a factory installed, the assignment of PIDs is non-deterministic. The area field will be assigned based on the order that ports are recognized and brought up by the system the first time (and only the first time) it is booted. This can impact servers that need their area equal to the port numbers to login to the fabric successfully. This does not impact switches that upgrade to 6.3.1a in the field. Fixed in Fabric OS 6.3.1b Workaround prior to upgrade: In environments with devices that rely on the area of the PID to match the port number, users should bind PIDs using the portaddress -bind [slot_number/]port_number [16bit_address] command prior to allowing devices to log in to the switch. Host that implements strict FCP/FCP-2 protocol frame fields checking for EOF delimiter, fails to discover LUNs when more than 64 LUNs are added to the encryption switch or encryption blade from the storage array. Fixed in Fabric OS 6.3.1b Port based routing frames are out of order when FCP image pairs concurrently initiate exchanges as originators over GE ports. Leads to very poor performance over FCIP link between two 1606 extension switches or multiprotocol extension blades over 1G GE port. Fixed in Fabric OS 6.3.1b HP StorageWorks Fabric OS 6.3.1c Release Notes 89

  • 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.1b
After 1606 extension switch reboot, PLOGI aborts seen due to F_RJT
for the ACCEPT frame. Host cannot see the target if PLOGI comes in
before RSCN is propagated on the 1606 extension switch or multipro-
tocol extension blade VE ports due to backend port programming not
completing in time.
Fixed in Fabric OS 6.3.1b
In a rare corner case, the encryption switch or encryption blade does
not handle an error case correctly when key attribute retrieval from key
vault fails, leading to a panic.
Fixed in Fabric OS 6.3.1b
With two FCRs (routers or switches with IR functionality) in the backbone
and both connected to the same edge fabric through EX ports, and
edge fabric has MEOS in IM2 mode, switch can panic upon receiving
periodic GE_PT from MEOS switches due to the FCR not handling it
properly.
Fixed in Fabric OS 6.3.1b
Internal ports of of 8Gb c-Class switch need to be forced to arb/arb
for portcfgfillword (mode 1) to improve characteristics for future
mezzanine card.
Fixed in Fabric OS 6.3.1b
HP 1606 extension switch and multiprotocol extension blade do not
always auto-restart after detection of a critical error when running
Fabric OS 6.3.1a. A manual reboot may be required to recover the
1606 switch and a slot power off/on to recover the multiprotocol exten-
sion blade.
Fixed in Fabric OS 6.3.1b
Supportsave hangs after unplugging and then plugging in the network
cable on the encryption switch or blade due to a race condition that
causes the encryption switch cluster to update continuously and sup-
portsave not to finish.
Fixed in Fabric OS 6.3.1b
Workaround prior to upgrade:
In
environments with devices that rely
on the area of the PID to match the
port number, users should bind PIDs
using the portaddress -bind
[slot_number/]port_number [16-
bit_address] command prior to
allowing devices to log in to the
switch.
On HP 8/8, 8/24, 8/40 and 8/80 switches shipped with Fabric OS
6.3.1a factory installed, the assignment of PIDs is non-deterministic.
The area field will be assigned based on the order that ports are recog-
nized and brought up by the system the first time (and only the first time)
it is booted. This can impact servers that need their area equal to the
port numbers to login to the fabric successfully. This does not impact
switches that upgrade to 6.3.1a in the field.
Fixed in Fabric OS 6.3.1b
Host that implements strict FCP/FCP-2 protocol frame fields checking
for EOF delimiter, fails to discover LUNs when more than 64 LUNs are
added to the encryption switch or encryption blade from the storage
array.
Fixed in Fabric OS 6.3.1b
Port based routing frames are out of order when FCP image pairs con-
currently initiate exchanges as originators over GE ports. Leads to very
poor performance over FCIP link between two 1606 extension switches
or multiprotocol extension blades over 1G GE port.
HP StorageWorks Fabric OS 6.3.1c Release Notes
89