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

Miscellaneous

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

6.3.1a and later Implemented support for modes 2 and 3 as described below. The default setting for all ports is mode 0, regardless of what Fabric OS version was previously installed. However, ports previously set to mode 1 by the user via the portcfg- fillword command are persistent, and will therefore remain at mode 1 after Fabric OS upgrade. • If version 6.2.0d or 6.3.1c was installed in the factory, the default setting is mode 1 for the internal ports and mode 0 for the external ports. The setting can be changed by the user on a port-by-port basis and will be persistent. Upgrading to a version later than 6.3.1c does not affect the current mode settings. • If a pre-6.2.0d version was installed in the factory, the default setting for all internal and external ports is mode 0. The setting can be changed by the user on a port-by-port basis and will be persistent. Upgrading to version 6.3.1a or later does not affect the current mode setting, with the exception of version 6.4.0b or later as described below. • If upgraded to version 6.4.0b, regardless of what version was factory installed, all internal ports will be set to mode 1, and all external ports to mode 0. The setting can be changed by the user on a port-by-port basis and will be persistent. 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 • 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 HP StorageWorks Fabric OS 6.3.1c Release Notes 39

  • 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
•
If version 6.2.0d or 6.3.1c was in-
stalled in the factory, the default set-
ting is mode 1 for the internal ports
and mode 0 for the external ports.
The setting can be changed by the
user on a port-by-port basis and will
be persistent. Upgrading to a version
later than 6.3.1c does not affect the
current mode settings.
•
If a pre-6.2.0d version was installed
in the factory, the default setting for
all internal and external ports is mode
0. The setting can be changed by the
user on a port-by-port basis and will
be persistent. Upgrading to version
6.3.1a or later does not affect the
current mode setting, with the excep-
tion of version 6.4.0b or later as de-
scribed below.
•
If upgraded to version 6.4.0b, regard-
less of what version was factory in-
stalled, all internal ports will be set to
mode 1, and all external ports to
mode 0. The setting can be changed
by the user on a port-by-port basis
and will be persistent.
Implemented support for modes 2 and 3
as described below. The default setting
for all ports is mode 0, regardless of what
Fabric OS version was previously in-
stalled. However, ports previously set to
mode 1 by the user via the
portcfg-
fillword
command are persistent, and
will therefore remain at mode 1 after
Fabric OS upgrade.
6.3.1a and later
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
•
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
HP StorageWorks Fabric OS 6.3.1c Release Notes
39