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

commitment of available bandwidth resulting in the following behaviors.

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

FCIP tunnel issues 4 Refer to the Fabric OS Administrator's Guide to review the setup of the ipRoute. 6. Confirm FCIP tunnel is configured correctly. The Compression, Fastwrite, and Tape Pipelining settings must match the opposite endpoint or the tunnel may not come up. Remote and local IP and WWN should be opposite each other. portshow fciptunnel ge1 all Port: ge1 Tunnel ID 0 Tunnel Description Not Configured Remote IP Addr 20.24.60.164 Local IP Addr 20.23.70.177 Remote WWN Not Configured Local WWN 10:00:00:05:1e:37:0d:59 Compression off Fastwrite off Tape Pipelining off Committed Rate 1000000 Kbps (1.000000 Gbps) SACK on Min Retransmit Time 100 Keepalive Timeout 10 Max Retransmissions 8 VC QoS Mapping off DSCP Marking (Control): 0, DSCP Marking (Data): 0 VLAN Tagging Not Configured TCP Byte Streaming off Status : Active Connected Count: 2 Uptime 31 seconds Symptom 7. Get a GE ethernet sniffer trace. Rule out all possible blocking factors. 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). If possible blocking factors have been rule out, simulate a connection attempt using the portCmd --ping command, from source to destination, and then take an Ether trace between the two endpoints. The Ether trace can be examined to further troubleshoot the FCIP connectivity. FCIP tunnel goes online and offline. Probable cause and recommended action A bouncing tunnel is one of the most common problems. This issue is usually because of an over commitment of available bandwidth resulting in the following behaviors. • Too much data tries to go over the link. • Management data gets lost, queued too long, and timeouts expire. • Data exceeds timeouts multiple times. Take the following steps gather information. • Verify what link bandwidth is available. • Confirm the IP path is being used exclusively for FCIP traffic. Fabric OS FCIP Administrator's Guide 93 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
93
53-1001766-01
FCIP tunnel issues
4
Refer to the
Fabric OS Administrator’s Guide
to review the setup of the ipRoute.
6.
Confirm FCIP tunnel is configured correctly.
The Compression, Fastwrite, and Tape Pipelining settings must match the opposite endpoint or
the tunnel may not come up. Remote and local IP and WWN should be opposite each other.
portshow fciptunnel ge1 all
Port: ge1
-------------------------------------------
Tunnel ID 0
Tunnel Description Not Configured
Remote IP Addr 20.24.60.164
Local IP Addr 20.23.70.177
Remote WWN Not Configured
Local WWN 10:00:00:05:1e:37:0d:59
Compression off
Fastwrite off
Tape Pipelining off
Committed Rate 1000000 Kbps (1.000000 Gbps)
SACK on
Min Retransmit Time 100
Keepalive Timeout 10
Max Retransmissions 8
VC QoS Mapping off
DSCP Marking (Control): 0, DSCP Marking (Data): 0
VLAN Tagging Not Configured
TCP Byte Streaming off
Status : Active
Connected Count: 2
Uptime 31 seconds
7.
Get a GE ethernet sniffer trace.
Rule out all possible blocking factors. 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). If possible blocking factors have been rule out, simulate a connection attempt using the
portCmd
--
ping
command, from source to destination, and then take an Ether trace between
the two endpoints. The Ether trace can be examined to further troubleshoot the FCIP
connectivity.
Symptom
FCIP tunnel goes online and offline.
Probable cause and recommended action
A bouncing tunnel is one of the most common problems. This issue is usually because of an over
commitment of available bandwidth resulting in the following behaviors.
•
Too much data tries to go over the link.
•
Management data gets lost, queued too long, and timeouts expire.
•
Data exceeds timeouts multiple times.
Take the following steps gather information.
•
Verify what link bandwidth is available.
•
Confirm the IP path is being used exclusively for FCIP traffic.