HP 3PAR StoreServ 7400 2-node Implementing HP Virtual Connect Direct-Attach Fi - Page 5

Integrating into SAN fabric environments

Get HP 3PAR StoreServ 7400 2-node PDF manuals and user guides View all HP 3PAR StoreServ 7400 2-node manuals
Add to My Manuals
Save this manual to your list of manuals

Page 5 highlights

On a traditional SAN, there is no knowledge of how each device was intended to connect, since zone configuration is the responsibility of the SAN administrator. Implicit zoning:  Configures automatically based on the VC fabric definitions and server profile SAN connectivity selections.  Allows servers connected to a direct-attach fabric to access the storage attached to uplinks in that same direct attach fabric.  Restricts visibility between server ports and between storage uplink ports.  Controls visibility on both Name Server scans and Registered State Change Notification (RSCN) messages.  Conforms to 3PAR best practices around initiator-based zoning (one zone per FC initiator). Network latency reduction When comparing the design architecture and specifications of an HP direct-attach solution to a fabric-attach solution, our testing shows up to a 55% reduction in storage network one-way latency (2.05 microseconds for direct-attach, 4.5 microseconds for fabric-attach). The direct-attach solution does not have time delays associated with SAN switches, transceivers,and their cables. Lower latency means higher precision and is a component of Quality of Service (QoS). Integrating into SAN fabric environments If you choose, you can use the HP Virtual Connect direct-attach Fibre Channel components in a mixed fabric environment: 1. Connect the Virtual Connect FlexFabric 10Gb/24-port Module to storage systems through a traditional FC SAN fabric. 2. Connect directly to the HP 3PAR Storage system with FC. 3. Connect the Ethernet ports to your LAN. Note that using HP 3PAR StoreServ systems in a direct-attach Fibre Channel environment might require connectivity to an external SAN for some situations, including the following:  An external SAN fabric is required to use 3PAR Peer Motion, an application allowing movement of data and workloads between 3PAR systems.  A 3PAR data replication service like Remote Copy over Fibre Channel (RCFC) requires use of an external SAN Fabric. However, a LAN-based alternative using Remote Copy over IP (RCIP) does not require an external SAN fabric and will not increase complexity and IT infrastructure costs.  Direct-attach architecture does not allow attaching either disk or tape backup systems directly to HP VC FlexFabric modules. As shown in Figure 4, the Virtual Connect FlexFabric 10Gb/24-port Module in a BladeSystem server can be configured for FC fabric-attach, FC direct-attach, and Ethernet connections. The mixed fabric-attach and direct-attach connections require creating two different fabrics because a VC SAN fabric can only contain uplink ports of one type. 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
5
On a traditional SAN, there is no knowledge of how each device was intended to connect, since zone configuration is the
responsibility of the SAN administrator.
Implicit zoning:
Configures automatically based on the VC fabric definitions and server profile SAN connectivity selections.
Allows servers connected to a direct-attach fabric to access the storage attached to uplinks in that same direct
attach fabric.
Restricts visibility between server ports and between storage uplink ports.
Controls visibility on both Name Server scans and Registered State Change Notification (RSCN) messages.
Conforms to 3PAR best practices around initiator-based zoning (one zone per FC initiator).
Network latency reduction
When comparing the design architecture and specifications of an HP direct-attach solution to a fabric-attach solution,
our testing shows up to a 55% reduction in storage network one-way latency (2.05 microseconds for direct-attach, 4.5
microseconds for fabric-attach). The direct-attach solution does not have time delays associated with SAN switches,
transceivers,and their cables. Lower latency means higher precision and is a component of Quality of Service (QoS).
Integrating into SAN fabric environments
If you choose, you can use the HP Virtual Connect direct-attach Fibre Channel components in a mixed fabric
environment:
1.
Connect the Virtual Connect FlexFabric 10Gb/24-port Module to storage systems through a traditional FC SAN
fabric.
2.
Connect directly to the HP 3PAR Storage system with FC.
3.
Connect the Ethernet ports to your LAN.
Note that using HP 3PAR StoreServ systems in a direct-attach Fibre Channel environment might require connectivity to
an external SAN for some situations, including the following:
An external SAN fabric is required to use 3PAR Peer Motion, an application allowing movement of data and workloads
between 3PAR systems.
A 3PAR data replication service like Remote Copy over Fibre Channel (RCFC) requires use of an external SAN Fabric.
However, a LAN-based alternative using Remote Copy over IP (RCIP) does not require an external SAN fabric and will
not increase complexity and IT infrastructure costs.
Direct-attach architecture does not allow attaching either disk or tape backup systems directly to HP VC FlexFabric
modules.
As shown in Figure 4, the Virtual Connect FlexFabric 10Gb/24-port Module in a BladeSystem server can be configured for
FC fabric-attach, FC direct-attach, and Ethernet connections. The mixed fabric-attach and direct-attach connections
require creating two different fabrics because a VC SAN fabric can only contain uplink ports of one type.