HP 4400 HP B-series Fabric OS 6.4.1b Release Notes (5697-0886, March 2011-incl - Page 36

Miscellaneous, Encryption behavior

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

Page 36 highlights

Miscellaneous • During non-disruptive firmware upgrades, E_Ports in R-RDY mode may cause some frame drops on the E-Port links. • On the HP StorageWorks 8/8, 8/24, 8/40, and 8/80 SAN Switches with factory installed Fabric OS 6.3.1a, the assignment of PIDs (FCIDs) is non-deterministic. The area field of the PIDs is assigned the first time the switch is booted up, based on the order that ports are recognized and brought up by the system. Switch PIDs area will not be equal to port number, which may impact servers such as FICON or static PID bind servers that need area equal to port numbers to log in to the fabric successfully. To avoid this issue, you can bind PIDs using the portaddress --bind [slot_number/]port_number [16-bit_address] command prior to allowing devices to log in to the switch. Once assigned, the PIDs are maintained across reboots and future Fabric OS upgrades. This issue does not impact switches that do not have Fabric OS 6.3.1a factory installed. Field upgrade to a later version of Fabric OS does not resolve this situation. For environments in which this is an issue, the specified workaround needs to be implemented until a future version of Fabric OS is factory installed. • Beginning with Fabric OS 6.2.0, the data collected by SupportSave operations was greatly expanded to include all readable registers within the ASIC. In cases where some registers may be unused and therefore contain invalid data, a CDR-1003 error message would be issued. Fabric OS 6.3.1b and later now reclassifies these messages as warnings, rather than critical errors. • HP recommends that no more the 50 F_Port Top Talkers be enabled on a 4/256 Director in a large fabric (>4000 devices). • HP recommends that for directors with more than 300 E_Ports, the switch be disabled prior to executing the switchCfgTrunk command (used to disable or enable trunking on the switch). • For the configure command in Fabric OS 6.4.0x, the default value that displays for Maximum Logins per switch has been corrected. The actual default value is now displayed. The default value itself has not changed. • POST diagnostics for the 8/40 SAN Switch have been modified in Fabric OS 6.3.1b, 6.4.0, and later releases to eliminate an INIT NOT DONE error at the end of an ASIC diagnostic port loopback test. This modification addresses BL-1020 Initialization errors encountered during the POST portloopbacktest. Encryption behavior • HP recommends that the encrypted LUN containers be created when all of the nodes/encryption engines (EEs) in the Data Encryption Key (DEK)/High Availability Cluster (HAC) are up and enabled. ◦ If two Encryption Engines are part of a High Availability Cluster, configure the host/target pair such that they form a multipath from both EEs. Avoid connecting both the host/target 36

  • 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
Miscellaneous
•
During non-disruptive firmware upgrades, E_Ports in R-RDY mode may cause some frame drops
on the E-Port links.
•
On the HP StorageWorks 8/8, 8/24, 8/40, and 8/80 SAN Switches with factory installed
Fabric OS 6.3.1a, the assignment of PIDs (FCIDs) is non-deterministic. The area field of the
PIDs is assigned the first time the switch is booted up, based on the order that ports are
recognized and brought up by the system. Switch PIDs area will not be equal to port number,
which may impact servers such as FICON or static PID bind servers that need area equal to
port numbers to log in to the fabric successfully. To avoid this issue, you can bind PIDs using
the
portaddress --bind [slot_number/]port_number [16-bit_address]
command prior to allowing devices to log in to the switch. Once assigned, the PIDs are
maintained across reboots and future Fabric OS upgrades. This issue does not impact switches
that do not have Fabric OS 6.3.1a factory installed. Field upgrade to a later version of Fabric
OS does not resolve this situation. For environments in which this is an issue, the specified
workaround needs to be implemented until a future version of Fabric OS is factory installed.
•
Beginning with Fabric OS 6.2.0, the data collected by
SupportSave
operations was greatly
expanded to include all readable registers within the ASIC. In cases where some registers
may be unused and therefore contain invalid data, a CDR-1003 error message would be
issued. Fabric OS 6.3.1b and later now reclassifies these messages as warnings, rather than
critical errors.
•
HP recommends that no more the 50 F_Port Top Talkers be enabled on a 4/256 Director in
a large fabric (>4000 devices).
•
HP recommends that for directors with more than 300 E_Ports, the switch be disabled prior
to executing the
switchCfgTrunk
command (used to disable or enable trunking on the
switch).
•
For the configure command in Fabric OS 6.4.0x, the default value that displays for Maximum
Logins per switch has been corrected. The actual default value is now displayed. The default
value itself has not changed.
•
POST diagnostics for the 8/40 SAN Switch have been modified in Fabric OS 6.3.1b, 6.4.0,
and later releases to eliminate an
INIT NOT DONE
error at the end of an ASIC diagnostic
port loopback test. This modification addresses BL-1020 Initialization errors encountered
during the POST
portloopbacktest
.
Encryption behavior
•
HP recommends that the encrypted LUN containers be created when all of the nodes/encryption
engines (EEs) in the Data Encryption Key (DEK)/High Availability Cluster (HAC) are up and
enabled.
◦
If two Encryption Engines are part of a High Availability Cluster, configure the host/target
pair such that they form a multipath from both EEs. Avoid connecting both the host/target
36