HP StorageWorks Fabric OS 6.3.3d Release Notes (5697-0493, May 2010 - includes all 6.3.0x versions)

8-Gb SAN Switch for HP
BladeSystem c-Class
All 8-Gb switches (except 8-Gb
SAN Switch for HP BladeSystem
c-Class)
Fabric OS version
0IDLE for Link Init, IDLE for fill
word
1ARB(FF) for Link Init, ARB(FF) for
fill word (NOTE: not supported with
XP storage arrays)
Mode:
1
6.1.2x was not supported on EVA4400 embedded switch module.
2
6.1.2x was not supported on this switch.
Updated command message
When executing the lscfg --create command with the following syntax:
switch_128:FID128:admin> lscfg --create 1 About to create switch with
fid=1. Please wait... Logical Switch with FID (1) has been successfully
created.
You should expect to see the following revised message:
Logical Switch has been created with default configurations. Please
configure the Logical Switch with appropriate switch and protocol settings
before activating the Logical Switch.
Miscellaneous
After changing domain offset followed by issuing an hafailover command on a DC SAN Backbone
Director, DC04 SAN Director, or 4/256 SAN Director running Fabric OS 6.3 in interopmode 2, the
console log may generate continuous Unknown LSR type messages. You must either reboot the
switch or issue another hafailover command to terminate the messages.
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 ports are recognized and brought up by the
system. Switch PIDs area will be not equal to the 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.
38