HP 1606 HP StorageWorks Fabric OS 6.3.2b Release Notes (5697-0777, November 20 - Page 33

Miscellaneous, Encryption behavior

Page 33 highlights

Modes 0-Idle for link init, idle for fill word 1-Arb(ff) for link init, arb(ff) for fill word (not supported with EVA or XP storage arrays) 2-Idle for link init, arb(ff) for fill word 3-Initially attempts mode 1 link initialization. If unsuccessful in achieving active state, reverts to mode 2. Steady state fill word is arb(ff). (not supported with XP storage arrays earlier than Fabric OS 6.4.0a.) Miscellaneous • 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. During non-disruptive firmware upgrades, E_Ports in R_RDY mode may cause some frame drops on the E_Port links. • Modem capability for the 4/256 director is not supported in Fabric OS 6.2.0 and later. • 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, customers 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 will not resolve this situation. For environments in which this will be an issue, the specified workaround will need 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. • A new command has been introduced in Fabric OS 6.3.2a that allows configuration of the fault delay on individual ports. The command portCfgFaultDelay allows a port to be configured to a 1.2 second fault delay versus the default setting of R_A_TOV. • NAME: portCfgFaultDelay - Configures the fault delay for a single FC port. • SYNOPSIS: portcfgfaultdelay [slot/]port, mode • DESCRIPTION: Use this command to configure the fault delay of an FC port. In the event that the link is noisy after a host power cycle, the switch may go into a soft fault state, which means a delay of R_A_TOV. Setting the mode value to 1 reduces the fault delay value to 1.2 seconds. The configuration is stored in nonvolatile memory and is persistent across switch reboots and power cycles. Use the portCfgShow command to display user-configured fault delay settings. 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 pairs to HP StorageWorks Fabric OS 6.3.2b Release Notes 33

  • 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

0
Idle for link init, idle for fill word
1
Arb(ff) for link init, arb(ff) for fill word (not supported with EVA or XP storage
arrays)
2
Idle for link init, arb(ff) for fill word
3
Initially attempts mode 1 link initialization. If unsuccessful in achieving active
state, reverts to mode 2. Steady state fill word is arb(ff). (not supported with XP
storage arrays earlier than Fabric OS 6.4.0a.)
Modes
Miscellaneous
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 loop-
back test. This modification addresses BL-1020 initialization errors encountered during the POST
portloopbacktest
. During non-disruptive firmware upgrades, E_Ports in R_RDY mode may
cause some frame drops on the E_Port links.
Modem capability for the 4/256 director is not supported in Fabric OS 6.2.0 and later.
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, customers 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 will not resolve this situation. For
environments in which this will be an issue, the specified workaround will need 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.
A new command has been introduced in Fabric OS 6.3.2a that allows configuration of the fault
delay on individual ports. The command
portCfgFaultDelay
allows a port to be configured
to a 1.2 second fault delay versus the default setting of R_A_TOV.
NAME:
portCfgFaultDelay
- Configures the fault delay for a single FC port.
SYNOPSIS:
portcfgfaultdelay [slot/]port, mode
DESCRIPTION:
Use this command to configure the fault delay of an FC port. In the event that
the link is noisy after a host power cycle, the switch may go into a soft fault state, which means
a delay of R_A_TOV. Setting the mode value to 1 reduces the fault delay value to 1.2 seconds.
The configuration is stored in nonvolatile memory and is persistent across switch reboots and
power cycles. Use the
portCfgShow
command to display user-configured fault delay settings.
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 pairs to
HP StorageWorks Fabric OS 6.3.2b Release Notes
33