Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 119

SCSI test, Trace route, Tracing the route through BCU

Get Dell Brocade 825 PDF manuals and user guides View all Dell Brocade 825 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 119 highlights

Diagnostics 3 4. Select Queue Test. 5. Click Start. SCSI test Use the fcdiag --scsitest command to test SCSI components and display discovered LUN information, such as LUN number, device type and qualifier, vendor ID, product ID, revision number, size of LUN, and LUN status. fcdiag --scsitest [-l ] where: port_id rpwwn lpwwn ID of the port from that you want to test. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index. For example, to specify adapter 1, port 1 use 1/1 as the port identification. Remote PWWN to which you want to trace the route. Logical PWWN. 0 indicates the base port or else the virtual port. Trace route Use the BCU and HCM to trace the SAN path between the adapter and remote end point. Tracing the route through BCU Use the fcdiag --traceroute BCU command to trace the route between end points. fcdiag --fctraceroute [-l ] where: port_id rpwwn lpwwn ID of the port from which you want to trace the route. This could be the PWWN, port hardware path, or user-specified port name. This could also be the adapter-index/port-index. For example, to specify adapter 1, port 1 use 1/1 as the port identification. Remote PWWN to which you want to trace the route. Logical PWWN. 0 indicates the base port. Tracing the route through HCM Use the FC Trace Route test to trace the route between the adapter port and a Fibre Channel target port. To run this test, use the following steps: 1. Launch the HCM. 2. Select Configure > Diagnostics to display the Diagnostics dialog box. 3. Click the FC Protocol Tests tab. 4. Select FC Trace Route. 5. Select the adapter port and target for which you wish to trace the route. Brocade Adapters Troubleshooting Guide 95 53-1002145-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
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
Brocade Adapters Troubleshooting Guide
95
53-1002145-01
Diagnostics
3
4.
Select
Queue Test
.
5.
Click
Start
.
SCSI test
Use the
fcdiag --scsitest
command to test SCSI components and display discovered LUN
information, such as LUN number, device type and qualifier, vendor ID, product ID, revision number,
size of LUN, and LUN status.
fcdiag -–scsitest <port_id> <rpwwn> [-l <lpwwn>]
where:
port_id
ID of the port from that you want to test. This could be the PWWN, port
hardware path, or user-specified port name. This could also be the
adapter-index/port-index. For example, to specify adapter 1, port 1 use 1/1
as the port identification.
rpwwn
Remote PWWN to which you want to trace the route.
lpwwn
Logical PWWN. 0 indicates the base port or else the virtual port.
Trace route
Use the BCU and HCM to trace the SAN path between the adapter and remote end point.
Tracing the route through BCU
Use the
fcdiag --traceroute
BCU command to trace the route between end points.
fcdiag -–fctraceroute <port_id> <rpwwn> [-l <lpwwn>]
where:
port_id
ID of the port from which you want to trace the route. This could be the
PWWN, port hardware path, or user-specified port name. This could also be
the adapter-index/port-index. For example, to specify adapter 1, port 1 use
1/1 as the port identification.
rpwwn
Remote PWWN to which you want to trace the route.
lpwwn
Logical PWWN. 0 indicates the base port.
Tracing the route through HCM
Use the FC Trace Route test to trace the route between the adapter port and a Fibre Channel target
port. To run this test, use the following steps:
1.
Launch the HCM.
2.
Select
Configure > Diagnostics
to display the
Diagnostics
dialog box.
3.
Click the
FC Protocol Tests
tab.
4.
Select
FC Trace Route
.
5.
Select the adapter port and target for which you wish to trace the route.