HP StorageWorks 1606 Brocade Fabric OS Troubleshooting and Diagnostics Guide v - Page 85

iSCSI Issues, In this Connectivity

Get HP StorageWorks 1606 - Extension SAN Switch PDF manuals and user guides View all HP StorageWorks 1606 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 85 highlights

iSCSI Issues Chapter 10 In this chapter •Connectivity 71 •Zoning 73 •Authentication 74 Connectivity The following issues deal with the iSCSI FC4-16IP blade connectivity between devices. NOTE The iSCSI blade FC4-16IP is not supported in the Brocade DCX or DCX-4S enterprise-class platforms. Symptom iSCSI host reports connection failed. Probable cause and recommended action Network connectivity is having problems. Verify the IP address using the portShow ipif /ge command. Verify the IP route using the portShow iproute /ge command. Ping the PC using the portCmd - -ping /ge -s -d command. 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 a backslash ( \ ) 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 Troubleshoot and Diagnostics Guide 71 53-1001340-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
Fabric OS Troubleshoot and Diagnostics Guide
71
53-1001340-01
Chapter
10
iSCSI Issues
In this chapter
•
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
•
Zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
73
•
Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
74
Connectivity
The following issues deal with the iSCSI FC4-16IP blade connectivity between devices.
NOTE
The iSCSI blade FC4-16IP is not supported in the Brocade DCX or DCX-4S enterprise-class platforms.
Symptom
iSCSI host reports connection failed.
Probable cause and recommended action
Network connectivity is having problems.
Verify the IP address using the
portShow ipif <
slot
>/ge<
port
>
command.
Verify the IP route using the
portShow iproute <
slot
>/ge<
port
>
command.
Ping the PC using the
portCmd - -ping <
slot
>/ge<
port
> -s <
source IP
> -d <
destination IP
>
command.
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 a backslash ( \ ) 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