HP StorageWorks 2/32 HP StorageWorks Fabric OS 5.2.1b Release Notes (AA-RWEYC- - Page 14

Services SNS, port mirroring, Secure FOS, SMI-S, and Zoning. These switch, IP over FC, ISL Trunking

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

Page 14 highlights

• 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 be observed when a low impairment is put to the link. FCIP • 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 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 using the blade server SAN switch in Access Gateway mode, most switch features are no longer applicable. These features include Admin Domains, Advanced Performance Monitoring, direct connection to SAN target devices, Fibre Channel Arbitrated 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 features are available in the default switch mode of operation. Access 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 Channel Arbitrated Loop operation. The c-Class half-height blade 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 When a disabled port on a switch in Access Gateway mode is connected to a configured 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 that cascading Access Gateway devices or connecting FCP targets, loop devices, or FICON channel/control units on the F_Ports are not supported. 14

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
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 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
fi
gured on 2 GbE ports.
•
Backup jobs initiated from the Symantec BackupExec application slowed
noticeably after adding signi
fi
cant I/O traf
fi
c 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 using the blade server SAN switch in Access Gateway mode, most
switch features are no longer applicable. These features include Admin
Domains, Advanced Performance Monitoring, direct connection to SAN target
devices, Fibre Channel Arbitrated 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
features are available in the default switch mode of operation.
Access 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
Channel Arbitrated Loop operation. The c-Class half-height blade servers do
not require Fibre Channel Arbitrated Loop and work
fi
ne with both access
gateway mode and Standard Switch Mode.
Access Gateway Mode Port
State
When a disabled port on a switch in Access Gateway mode is connected to a
con
fi
gured 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 con
fi
guration requires Fibre Channel Arbitrated
Loop operation, which con
fl
icts 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
that cascading Access Gateway devices or connecting FCP targets, loop
devices, or FICON channel/control units on the F_Ports are not supported.
14