HP 1606 Fabric OS FCIP Administrators Guide v6.4.0 (53-1001766-01, November 20 - Page 17

FCIP concepts, IP WAN network considerations

Get HP 1606 PDF manuals and user guides View all HP 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

FCIP concepts 1 FCIP concepts Fibre Channel over IP (FCIP) enables you to use existing IP wide area network (WAN) infrastructure to connect Fibre Channel SANs. FCIP supports applications such as remote data replication (RDR), centralized SAN backup, and data migration over very long distances that are impractical or very costly using native Fibre Channel connections. FCIP tunnels are used to pass Fibre Channel I/O through an IP network. FCIP tunnels are built on a physical connection between two peer switches or blades. Fibre Channel frames enter FCIP through virtual E_ports (VE_ports or VEX_ports) and are encapsulated and passed to TCP layer connections. The TCP connections insure in-order delivery of FC frames and lossless transmission. The Fibre Channel fabric and all Fibre Channel targets and initiators are unaware of the presence of the IP network. Figure 1 shows the relationship of FC and TCP/IP layers, and the general concept of FCIP tunneling. TCP IP LINK PHY FIGURE 1 FCIP tunnel concept and TCP/IP layers IP WAN network considerations Because FCIP uses TCP connections over an existing wide area network, consult with the WAN carrier and IP network administrator to be sure that the network hardware and software equipment operating in the data path can properly support the TCP connections. When consulting, keep the following in mind: • Routers and firewalls that are in the data path must be configured to pass FCIP traffic (TCP port 3225) and IPSec traffic, if IPsec is used (UDP port 500). TCP port 3226 must be configured for the 7500/FR4-18i only. • To enable recovery from a WAN failure or outage, be sure that diverse, redundant network paths are available across the WAN. • Be sure the underlying WAN infrastructure is capable of supporting the redundancy and performance expected in your implementation. Fabric OS FCIP Administrator's Guide 3 53-1001766-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Fabric OS FCIP Administrator’s Guide
3
53-1001766-01
FCIP concepts
1
FCIP concepts
Fibre Channel over IP (FCIP) enables you to use existing IP wide area network (WAN) infrastructure
to connect Fibre Channel SANs. FCIP supports applications such as remote data replication (RDR),
centralized SAN backup, and data migration over very long distances that are impractical or very
costly using native Fibre Channel connections. FCIP tunnels are used to pass Fibre Channel I/O
through an IP network. FCIP tunnels are built on a physical connection between two peer switches
or blades. Fibre Channel frames enter FCIP through virtual E_ports (VE_ports or VEX_ports) and are
encapsulated and passed to TCP layer connections. The TCP connections insure in-order delivery of
FC frames and lossless transmission. The Fibre Channel fabric and all Fibre Channel targets and
initiators are unaware of the presence of the IP network.
Figure 1
shows the relationship of FC and
TCP/IP layers, and the general concept of FCIP tunneling.
FIGURE 1
FCIP tunnel concept and TCP/IP layers
IP WAN network considerations
Because FCIP uses TCP connections over an existing wide area network, consult with the WAN
carrier and IP network administrator to be sure that the network hardware and software equipment
operating in the data path can properly support the TCP connections. When consulting, keep the
following in mind:
•
Routers and firewalls that are in the data path must be configured to pass FCIP traffic (TCP
port 3225) and IPSec traffic, if IPsec is used (UDP port 500). TCP port 3226 must be
configured for the 7500/FR4-18i only.
•
To enable recovery from a WAN failure or outage, be sure that diverse, redundant network
paths are available across the WAN.
•
Be sure the underlying WAN infrastructure is capable of supporting the redundancy and
performance expected in your implementation.
TCP
IP
LINK
PHY