HP StorageWorks Fabric OS 5.2.1b Release Notes (AA-RWEYC-TE, June 2007)

FCIP
• Frame drops observed on FCIP slow links:
• The frame drops occur when the FCIP tunnel bandwid th is set to 10
Base-T (10M bps), 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 be 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 con figured on 2 GbE ports.
• Backup jobs initiated from the Symantec BackupExec application slowed
noticeably after a dding significant I/O traffic from regular hosts and
targets to the FCIP tunnel. A port-based routing policy must be used for
Tape devices.
Access Gateway vs
Standard Switch Mode
When usi
ng the blade server SAN switch in Access Gateway mode, most
switch features are no longer applicable. These features include Admin
Domain
s, Advanced Performance Monitoring, direct connection to SAN target
device
s, Fibre Channel Arbitrated Loop support, Fabric Manager, FICON,
IP over
FC, ISL Trunking, Extended Fabrics, Managem ent Services, Name
Servi
ces (SNS), port mirroring, Secure FOS, SMI-S, and Zoning. These switch
features are available in the default switch mode of operation.
Access Gateway mode is not supported in the p-class Blade system if there
aretwohalf-heightserversinthesamesleeve(ServerSlot1and9,2and10,
and s
o on). Two p-class half-height servers in the same sleeve require Fibre
Channel Arbitrated Loop operation. The c-Class half-height blade servers do
not
require Fibre Channel Arbitrated Loop and work fine with both access
gat
eway mode and Standard Switch Mode.
Access Gateway Mode Port
State
WhenadisabledportonaswitchinAccessGatewaymodeisconnectedtoa
configure d loop HBA, the port state alternates between Nosync and Insync.
The switchShow command displays the state of the remote HBA 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 Slot 1 and
9, or 2 and 10, etc). That configuration requires Fibre Channel Arbitrated
Loop operation, which conflicts with Access Gateway mode. There is no such
restriction with c-Class, since no servers require Fibre Channel Arbitrated Loop.
Access Gateway supports only FCP initiator connections on the F_Ports. Note
thatcascadingAccessGatewaydevicesorconnectingFCPtargets,loop
devices, or FICON channel/control units on the F_Ports are not supported.
14