HP Brocade 8/12c Brocade Fabric OS Troubleshooting and Diagnostics Guide v6.2. - Page 92

the tunnel may not come up. Remote and local IP and WWN should be opposite each other.

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 92 highlights

10 FCIP tunnel issues Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64 Ping Statistics for 11.1.1.2: Packets: Sent = 4, Received = 4, Loss = 0 ( 0 percent loss) Min RTT = 0ms, Max RTT = 0ms Average = 0ms If you are able to ping, then you have IP connectivity and your tunnel should come up. If not continue to the next step. 4. Enter the portCmd --traceroute command to the remote tunnel endpoint from both endpoints. portcmd --traceroute ge1 -s 11.1.1.1 -d 11.1.1.2 Traceroute to 11.1.1.2 from IP interface 11.1.1.1 on 0/1, 64 hops max 1 11.1.1.2 0 ms 0 ms 0 ms Traceroute complete. 5. The tunnel or route lookup may fail to come online because of a missing but required ipRoute. If there are routed IP connections that provide for the FCIP tunnel, then both ends of the tunnel must have defined ipRoute entries. 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. If all possible blocking factors on the network between the two endpoints are ruled out, (for example, a firewall or proxy server) then 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. 76 Fabric OS Troubleshooting and Diagnostics Guide 53-1001187-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
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
76
Fabric OS Troubleshooting and Diagnostics Guide
53-1001187-01
FCIP tunnel issues
10
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
Ping Statistics for 11.1.1.2:
Packets: Sent = 4, Received = 4, Loss = 0 ( 0 percent loss)
Min
RTT = 0ms, Max RTT = 0ms Average = 0ms
If you are able to ping, then you have IP connectivity and your tunnel should come up. If not
continue to the next step.
4.
Enter the
portCmd
--
traceroute
command to the remote tunnel endpoint from both endpoints.
portcmd --traceroute ge1 -s 11.1.1.1 -d 11.1.1.2
Traceroute to 11.1.1.2 from IP interface 11.1.1.1 on 0/1, 64 hops max
1
11.1.1.2
0 ms
0 ms
0 ms
Traceroute complete.
5.
The tunnel or route lookup may fail to come online because of a missing but required ipRoute.
If there are routed IP connections that provide for the FCIP tunnel, then both ends of the tunnel
must have defined ipRoute entries.
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.
If all possible blocking factors on the network between the two endpoints are ruled out, (for
example, a firewall or proxy server) then 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.