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

FCIP links

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 108 highlights

4 FCIP links • Confirm that traffic shaping is configured to limit the bandwidth to available using the portShow fciptunnel all -perf -params command. Examine data from both routers. This data is not in the supportshow output and shows retransmissions indicating, input and output rates on the tunnels. Gather this information for both data and management TCP connections. 8. Run tperf for 7800 switches and FX8-24 blades, or ipperf for 7500 switches and FR4-18i blades to gather WAN performance data. FCIP links The following list contains information for troubleshooting FCIP links: • When deleting FCIP links, you must delete them in the exact reverse order they were created. That is, first delete the tunnels, then the IP interfaces, and finally the port configuration. The IP route information is removed automatically at this point. • IP addresses are retained by slot in the system. If FR4-18i blades are moved to different slots without first deleting configurations, errors can be seen when trying to reuse these IP addresses. • The portCmd --ping command only verifies physical connectivity. This command does not verify that you have configured the ports correctly for FCIP tunnels. • One port can be included in multiple tunnels, but each tunnel must have at least one port that is unique to that tunnel. • Ports at both ends of the tunnel must be configured correctly for an FCIP tunnel to work correctly. These ports can be either VE_Ports or VEX_Ports. A VEX_Port must be connected to a VE_Port. • When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and the backbone fabric will use VEX_Ports for a single tunnel. • If an FCIP tunnel fails with the "Disabled (Fabric ID Oversubscribed)" message, the solution is to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the edge fabric. • Because of an IPsec RASLog limitation, you may not be able to determine an incorrect configuration that causes an IPSec tunnel to not become active. This misconfiguration can occur on either end of the tunnel. As a result, you must correctly match the encryption method, authentication algorithm, and other configurations on each end of the tunnel. 94 Fabric OS FCIP Administrator's Guide 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
94
Fabric OS FCIP Administrator’s Guide
53-1001766-01
FCIP links
4
•
Confirm that traffic shaping is configured to limit the bandwidth to available using the
portShow fciptunnel all -perf –params
command.
Examine data from both routers. This data is not in the
supportshow
output and shows
retransmissions indicating, input and output rates on the tunnels.
Gather this information for both data and management TCP connections.
8.
Run
tperf
for 7800 switches and FX8-24 blades, or
ipperf
for 7500 switches and FR4-18i
blades to gather WAN performance data.
FCIP links
The following list contains information for troubleshooting FCIP links:
•
When deleting FCIP links, you must delete them in the exact reverse order they were created.
That is, first delete the tunnels, then the IP interfaces, and finally the port configuration. The IP
route information is removed automatically at this point.
•
IP addresses are retained by slot in the system. If FR4-18i blades are moved to different slots
without first deleting configurations, errors can be seen when trying to reuse these IP
addresses.
•
The
portCmd
--
ping
command only verifies physical connectivity. This command does not
verify that you have configured the ports correctly for FCIP tunnels.
•
One port can be included in multiple tunnels, but each tunnel must have at least one port that
is unique to that tunnel.
•
Ports at both ends of the tunnel must be configured correctly for an FCIP tunnel to work
correctly. These ports can be either VE_Ports or VEX_Ports. A VEX_Port must be connected to a
VE_Port.
•
When configuring routing over an FCIP link for a fabric, the edge fabric will use VE_Ports and
the backbone fabric will use VEX_Ports for a single tunnel.
•
If an FCIP tunnel fails with the “Disabled (Fabric ID Oversubscribed)” message, the solution is
to reconfigure the VEX_Port to the same Fabric ID as all of the other ports connecting to the
edge fabric.
•
Because of an IPsec RASLog limitation, you may not be able to determine an incorrect
configuration that causes an IPSec tunnel to not become active. This misconfiguration can
occur on either end of the tunnel. As a result, you must correctly match the encryption method,
authentication algorithm, and other configurations on each end of the tunnel.