HP StorageWorks 4/16 HP StorageWorks Fabric OS 6.0.1a release notes (AA-RWFMA- - Page 10

Firmware upgrade instructions, Important notes, Table 4 Important release information

Get HP StorageWorks 4/16 - SAN Switch PDF manuals and user guides View all HP StorageWorks 4/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 10 highlights

Firmware upgrade instructions IMPORTANT: HP strongly recommends that users upgrade to Fabric OS 6.0.1a as soon as possible. Please note, upgrading to Fabric OS 6.0.1a is only allowed from Fabric OS 5.3.x or later. To access the latest Fabric OS 6.0.1a firmware, configuration files, and MIB files, go to the following HP website: http://www.hp.com/go/san Important notes Table 4 provides information you should know prior to upgrading to Fabric OS 6.0.1a. Table 4 Important release information Topic Description HP StorageWorks B-Series MP Router Blade (FR4-18i) The FR4-18i ships with Fabric OS 6.x. If inserted into a chassis running a version of firmware that is different than the revision level currently on the blade, the blade firmware will be upgraded or downgraded to match the firmware revision on the chassis. Configuration requirements for connecting A6795A HBA to 48 port blades for Boot from SAN When connecting an A6795A Fibre Channel Adapter to an HP StorageWorks 4/48 SAN Director Blade (FC4-48), or 8/48 DC director blade (FC8-48) and attempting to boot from SAN, the communications at login between these two devices causes the login to fail. This results in the port getting disabled by the switch. The switch port that the HBA is connected to must be locked to a G_Port to correct this issue and allow the devices to negotiate a point-to-point connection. This will disable loop negotiation at the switch port. Using the portCfgGport CLI command or GUI interface, lock the port to which the A6795A HBA is connected to G_Port. An example of the CLI command is: portCfgGport [SlotNumber/PortNumber] 1 FICON support Adaptive Networking/ Flow-Based QoS Prioritization The FC4-48 Director port blade is not supported to connect to System z environments via FICON channels or via FCP zLinux on System z. To attach the 4/256 SAN Director to the System z environment, use an FC4-16 or FC4-32 Director blade. • When using Quality of Service (QoS) in a fabric with 4Gb ports or switches, Fabric OS 6.x or later must be installed on all products in order to pass QoS info. • Flow based QoS is NOT supported on 8Gb blades in the 4/256 SAN Director. • Any products that are not capable of operating with Fabric OS 6.x may not exist in fabric with Flow based QoS. • If trunks are used, there should be at least two flows per priority going through the trunk. Otherwise, bandwidth allocation might not be prioritized proportionally. Top Talkers When multiple F_Ports come up, the F_Port flow information displayed might not be accurate. This will be resolved in a subsequent release. Traffic Isolation When configuring a TI zone with failover disabled, user needs to make sure that the E-ports of the TI zone are corresponding to valid paths (use topologyshow via the CLI to verify this), otherwise, routing might be missing for ports in that TI zone. 10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
Firmware upgrade instructions
IMPORTANT:
HP strongly recommends that users upgrade to Fabric OS 6.0.1a as soon as possible. Please note,
upgrading to Fabric OS 6.0.1a is only allowed from Fabric OS 5.3.x or later.
To access the latest Fabric OS 6.0.1a
fi
rmware, con
fi
guration
fi
les, and MIB
fi
les, go to the following
HP website:
h
t
t
p
:
/
/
w
w
w
.
h
p
.
c
o
m
/
g
o
/
s
a
n
Important notes
Table 4
provides information you should know prior to upgrading to Fabric OS 6.0.1a.
Table 4 Important release information
Topic
Description
HP StorageWorks
B-Series MP Router Blade
(FR4-18i)
The FR4-18i ships with Fabric OS 6.x. If inserted into a chassis running a version
of
fi
rmware that is different than the revision level currently on the blade, the
blade
fi
rmware will be upgraded or downgraded to match the
fi
rmware revision
on the chassis.
Con
fi
guration
requirements for
connecting A6795A
HBA to 48 port blades
for Boot from SAN
When connecting an A6795A Fibre Channel Adapter to an HP StorageWorks
4/48 SAN Director Blade (FC4–48), or 8/48 DC director blade (FC8-48) and
attempting to boot from SAN, the communications at login between these two
devices causes the login to fail. This results in the port getting disabled by the
switch. The switch port that the HBA is connected to must be locked to a G_Port to
correct this issue and allow the devices to negotiate a point-to-point connection.
This will disable loop negotiation at the switch port.
Using the
portCfgGport
CLI command or GUI interface, lock the port to which
the A6795A HBA is connected to G_Port.
An example of the CLI command is:
portCfgGport [SlotNumber/PortNumber] 1
FICON support
The FC4-48 Director port blade is not supported to connect to System z
environments via FICON channels or via FCP zLinux on System z. To attach the
4/256 SAN Director to the System z environment, use an FC4-16 or FC4-32
Director blade.
Adaptive Networking/
Flow-Based QoS
Prioritization
•
When using Quality of Service (QoS) in a fabric with 4Gb ports or switches,
Fabric OS 6.x or later must be installed on all products in order to pass QoS
info.
•
Flow based QoS is NOT supported on 8Gb blades in the 4/256 SAN
Director.
•
Any products that are not capable of operating with Fabric OS 6.x may
not
exist in fabric with Flow based QoS.
•
If trunks are used, there should be at least two
fl
ows per priority going
through the trunk. Otherwise, bandwidth allocation might not be prioritized
proportionally.
Top Talkers
When multiple F_Ports come up, the F_Port
fl
ow information displayed might not
be accurate. This will be resolved in a subsequent release.
Traf
fi
c Isolation
When con
fi
guring a TI zone with failover disabled, user needs to make sure that
the E-ports of the TI zone are corresponding to valid paths (use
topologyshow
via the CLI to verify this), otherwise, routing might be missing for ports in that
TI zone.
10