Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 114

Internal and external loopback tests, Enabling beaconing through HCM

Page 114 highlights

3 Diagnostics Use the fcdiag --linkbeacon command to enable end-to-end beaconing. fcdiag --linkbeacon {on | off} where: port_id on | off ID of the port for which you want to run a link beacon 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, you would use 1/1 as the port identification. Toggle on or off. If turned on, you can specify duration. Enabling beaconing through HCM Enable link and port beaconing using the following steps. 1. Launch the HCM. 2. Select the base adapter port from the device tree window. 3. Click Configure > Beacon. 4. Click the Link check box, the Port check box, or both. Internal and external loopback tests Use the BCU or the HCM to perform a loopback test for a specific port. Loopback tests require that you disable the port. The following loopback tests are available: • Internal Random data patterns are sent to the adapter port, then returned without transmitting through the port. The returned data is validated to determine port operation. Errors may indicate a failed port. • External For this test, a loopback connector is required for the port. For mezzanine or expansion card adapters, this test can be performed using a pass-through module. Random data patterns are sent to the adapter port. The data transmits from the port and then returns. The returned data is validated to determine port operation. Errors may indicate a failed port. Performing loopback tests through BCU Use the diag --loopback BCU command test to verify port function through a loopback test. bcu diag --loopback [-t ][-s ] [-c ] [-p ] where: port_id loopback type ID of the port for which you want to run the 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 you would use 1/1 as the port identification. Type of loopback test. Possible values are internal, external, and serdes. 90 Brocade Adapters Troubleshooting Guide 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

90
Brocade Adapters Troubleshooting Guide
53-1002145-01
Diagnostics
3
Use the
fcdiag --linkbeacon
command to enable end-to-end beaconing.
fcdiag --linkbeacon <portid> {on | off}
where:
port_id
ID of the port for which you want to run a link beacon 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, you
would use 1/1 as the port identification.
on | off
Toggle on or off. If turned on, you can specify duration.
Enabling beaconing through HCM
Enable link and port beaconing using the following steps.
1.
Launch the HCM.
2.
Select the base adapter port from the device tree window.
3.
Click
Configure > Beacon
.
4.
Click the
Link
check box, the
Port
check box, or both.
Internal and external loopback tests
Use the BCU or the HCM to perform a loopback test for a specific port. Loopback tests require that
you disable the port. The following loopback tests are available:
Internal
Random data patterns are sent to the adapter port, then returned without transmitting through
the port. The returned data is validated to determine port operation. Errors may indicate a
failed port.
External
For this test, a loopback connector is required for the port. For mezzanine or expansion card
adapters, this test can be performed using a pass-through module. Random data patterns are
sent to the adapter port. The data transmits from the port and then returns. The returned data
is validated to determine port operation. Errors may indicate a failed port.
Performing loopback tests through BCU
Use the
diag --loopback
BCU command test to verify port function through a loopback test.
bcu diag --loopback <port_id> [-t <loopback_type>][-s <speed>]
[-c <frame_count>] [-p <pattern>]
where:
port_id
ID of the port for which you want to run the 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 you would
use 1/1 as the port identification.
loopback type
Type of loopback test. Possible values are internal, external, and serdes.