HP AM866A Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, - Page 101

iSCSI Issues, In this Connectivity

Get HP AM866A - StorageWorks 8/8 Base SAN Switch PDF manuals and user guides
UPC - 884420064602
View all HP AM866A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 101 highlights

iSCSI Issues Chapter 11 If you are having problems with the iSCSI FC4-16IP blade connectivity, use the following chapter to troubleshoot before calling your support provider. NOTE The iSCSI blade FC4-16IP is not supported in the Brocade DCX Backbone. In this chapter •Connectivity 87 •Zoning 89 •Authentication 90 Connectivity The following issues deal with the iSCSI FC4-16IP blade connectivity between devices. Symptom iSCSI host reports connection failed. Probable cause and recommended action Network connectivity is having problems. Verify IP address using: portShow ipif /ge Verify IP route using: portShow iproute /ge Ping the PC using: portCmd - -ping /ge -s -d Make corrections to the IP information using the portCfg command. Below is an example to verify if packets can be sent to the destination IP address with maximum wait_time specified. Note that backslash ( \ ) which is used to skip the return character so you can continue the command on the next line without the return character being interpreted by the shell. switch:admin> portcmd --ping 12/ge0 -s 2007:7:30:32:227:138:10:120 -d \ 2007:7:30:32:227:77:0:60 -w 29000 Pinging 2007:7:30:32:227:77:0:60 from ip interface 2007:7:30:32:227:138:10:120 on 12/ge0 with 64 bytes of data Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=0ms ttl=255 Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=1ms ttl=255 Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=0ms ttl=255 Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=0ms ttl=255 Ping Statistics for 2007:7:30:32:227:77:0:60: Packets: Sent = 4, Received = 4, Loss = 0 ( 0 percent loss) Min RTT = 0ms, Max RTT = 1ms Average = 0ms Fabric OS Troubleshooting and Diagnostics Guide 87 53-1000853-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
Fabric OS Troubleshooting and Diagnostics Guide
87
53-1000853-01
Chapter
11
iSCSI Issues
If you are having problems with the iSCSI FC4-16IP blade connectivity, use the following chapter to
troubleshoot before calling your support provider.
NOTE
The iSCSI blade FC4-16IP is not supported in the Brocade DCX Backbone.
In this chapter
•
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
•
Zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
•
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
90
Connectivity
The following issues deal with the iSCSI FC4-16IP blade connectivity between devices.
Symptom
iSCSI host reports connection failed.
Probable cause and recommended action
Network connectivity is having problems.
Verify IP address using:
portShow ipif <
slot
>/ge<
port
>
Verify IP route using:
portShow iproute <
slot
>/ge<
port
>
Ping the PC using:
portCmd - -ping <
slot
>/ge<
port
> -s <
source IP
> -d <
destination IP
>
Make corrections to the IP information using the
portCfg
command.
Below is an example to verify if packets can be sent to the destination IP address with maximum
wait_time specified. Note that backslash ( \ ) which is used to skip the return character so you can
continue the command on the next line without the return character being interpreted by the shell.
switch:admin> portcmd --ping 12/ge0 -s 2007:7:30:32:227:138:10:120 -d \
2007:7:30:32:227:77:0:60 -w 29000
Pinging 2007:7:30:32:227:77:0:60 from ip interface 2007:7:30:32:227:138:10:120
on 12/ge0 with 64
bytes of data
Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=0ms ttl=255
Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=1ms ttl=255
Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=0ms ttl=255
Reply from 2007:7:30:32:227:77:0:60: bytes=64 rtt=0ms ttl=255
Ping Statistics for 2007:7:30:32:227:77:0:60:
Packets: Sent = 4, Received = 4, Loss = 0 ( 0 percent loss)
Min RTT = 0ms, Max RTT = 1ms Average = 0ms