HP StorageWorks Fabric OS 5.2.3 Release Notes (AA-RWEYD-TE, November 2007)

System boot
Not all Fabric OS services are available when the prompt becomes available
during boot up. Wait for all the services to come up before using the switch or
performing zoning actions.
Performance M onitoring
If the user tries to save more than 512 monitors using the perfCfgSave
command, some
of the monitors may be lost.
Management — Proxy
switches
If you are using a Fabric OS 4.x switch as an API or SMI-S proxy to manage a
5.1.0 switch, you must be running Fabric OS 4.4.0d.
FCIP
• Frame drops observed on FCIP slow links:
• The frame drops occur when the FCIP tunnel bandwidth is set to 10
Base-T (10Mbps), E1 (1.048Mbps), or T1 (1.544Mbps).
• With E1 or T1, frames are dropped even without an impaired link.
• With 10 Base-T, frame drops may b e observed when a low impairment
is put to the link.
• The portperfshow command indicated incorrect (smaller) bidirectional
throughput on the FCIP tunnel when Fastwrite/Tape Pipelining is enabled.
• Fastwrite/Tape Pipelining did not inform user when it failed due to multiple
equal paths configured on 2 GbE ports.
• Backup jobs initiated from the Symantec BackupExec application slowed
noticeably after adding significant I/O trafficfromregularhostsand
targets to the FCIP tunnel. A port-based routing policy must be used for
Tape devices.
Access Gatewa y vs
Standard Switch Mode
When using the blade server SAN switch in Access Gateway mode, most
switc
h features are no longer applicable. These features include Admin
Domains, Advanced Performance Monitoring, direct connection to SAN target
devices, Fibre Channel Arbitra ted Loop support, Fabric Manager, FICON,
IP over FC, ISL Trunking, Extended Fabrics, Management Services, Name
Services (SNS), port mirroring, Secure FOS, SMI-S, and Zoning. These switch
fea
tures are available in the default switch mode of operation.
Acc
ess Gateway mode is not supported in the p-class Blade system if there
are
two half-height servers in the same sleeve (Server Slot 1 and 9, 2 and 10,
and so on). Two p-class half-height servers in the same sleeve require Fibre
Ch
annel Arbitrated Loop operation. The c-Class half-height bl ade servers do
not require Fibre Channel Arbitrated Loop and work fine with both access
gateway mode and Standard Switch Mode.
Access Gateway Mode Port
State
WhenadisabledportonaswitchinAccessGatewaymodeisconnectedtoa
configured loop HBA, the p ort state alternates between Nosync and Insync.
The switchShow comma nd disp lays the state of the remote H BA port that is
continuously attempting to reconnect to the disabled port.
Access Gateway mode is not supported in the p-Class BladeSystem if there
are two half-height servers (BL3xp) in the same sleeve (Server S lot 1 and
9, or 2 and 10, etc) . That configuration requires Fibre Channel Arbitrated
Loop operation, which conflicts with Access G ateway mode. There is no such
restriction with c-Class, since no servers require Fibre Channel Arbitrated Loop.
Access Gateway supports only FCP initiator conn ections on the F_Ports. N ote
that cascading Access Gateway devices or connecting FCP targets, loop
devices, or FICON channel/control units on the F_Ports are not supported.
LSAN across FCR
If a mixed fabric is configured for LSAN across Fibre Channel Routing (FCR)
zone changes must originate from the switch running the highest Fabric OS
release. For example, if a mixed fabric contains switches running Fabric OS
4.x, 5.1.x and 5.2.x the zone changes must originate from the switch running
FabricOS5.2.x.ThisistruewhetherornotADisenabled.
14