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

FCIP tunnel issues

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

4 FCIP tunnel issues FCIP tunnel issues The following are common FCIP tunnel issues and recommended actions for you to follow to fix the issue. NOTE The portshow -perf and - params options can be applied only to the 7500 switch and FR4-18i blade. Symptom FCIP tunnel does not come Online. Probable cause and recommended action Confirm the following steps. 1. Confirm GE port is online. portshow ge1 Eth Mac Address: 00.05.1e.37.93.06 Port State: 1 Online Port Phys: 6 In_Sync Port Flags: 0x3 PRESENT ACTIVE Port Speed: 1G 2. Confirm IP configuration is correct on both tunnel endpoints. portshow ipif ge1 Port: ge1 Interface IP Address NetMask MTU 0 11.1.1.1 255.255.255.0 1500 3. Enter the portCmd --ping command to the remote tunnel endpoint from both endpoints. The -s value is the source IP address; the -d value is the destination IP address. portcmd --ping ge1 -s 11.1.1.1 -d 11.1.1.2 Pinging 11.1.1.2 from ip interface 11.1.1.1 on 0/ge1 with 64 bytes of data Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64 Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64 Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64 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 the command is successful, 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 IP route. If there are routed IP connections that provide for the FCIP tunnel, then both ends of the tunnel must have defined ipRoute entries. 92 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
92
Fabric OS FCIP Administrator’s Guide
53-1001766-01
FCIP tunnel issues
4
FCIP tunnel issues
The following are common FCIP tunnel issues and recommended actions for you to follow to fix the
issue.
NOTE
The portshow -perf and - params options can be applied only to the 7500 switch and FR4-18i blade.
Symptom
FCIP tunnel does not come Online.
Probable cause and recommended action
Confirm the following steps.
1.
Confirm GE port is online.
portshow ge1
Eth Mac Address: 00.05.1e.37.93.06
Port State: 1
Online
Port Phys:
6
In_Sync
Port Flags: 0x3
PRESENT ACTIVE
Port Speed: 1G
2.
Confirm IP configuration is correct on both tunnel endpoints.
portshow ipif ge1
Port: ge1
Interface
IP Address
NetMask
MTU
----------------------------------------------------------
0
11.1.1.1
255.255.255.0
1500
3.
Enter the
portCmd
--
ping
command to the remote tunnel endpoint from both endpoints.
The -s value is the source IP address; the –d value is the destination IP address.
portcmd --ping ge1 -s 11.1.1.1 -d 11.1.1.2
Pinging 11.1.1.2 from ip interface 11.1.1.1 on 0/ge1 with 64 bytes of data
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
Reply from 11.1.1.2: bytes=64 rtt=0ms ttl=64
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 the command is successful, 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 IP route.
If there are routed IP connections that provide for the FCIP tunnel, then both ends of the tunnel
must have defined ipRoute entries.