HP StorageWorks 2/140 director product manager user guide - Page 100

Operational Statistics, Troubleshooting Tips

Get HP StorageWorks 2/140 - Director Switch PDF manuals and user guides View all HP StorageWorks 2/140 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 100 highlights

Monitoring and Managing the Director • Delimiter errors-The number of times that the director detected an unrecognized start-of-frame (SOF) delimiter, an unrecognized end-of-frame (EOF) delimiter, or an invalid class of service. This indicates that the frame arrived at the director's port corrupted. This corruption can be due to plugging/unplugging the link, bad optics at either end of the cable, bad cable, or dirty or poor connections. Moving the connection around or replacing cables can isolate the problem. • Address ID errors-A received frame had an unavailable or invalid Fibre Channel destination address, or an invalid Fibre Channel source address. This typically indicates the destination device is unavailable. • Frames too short-A received frame exceeded the Fibre Channel frame maximum size or was less than the Fibre Channel minimum size, indicating the frame arrived at the director's port corrupted. Frame corruption may be caused by device disconnection, an optical transceiver failure at the device, a bad fiber-optic cable, or a poor cable connection. Operational Statistics The following describes the Operational Statistics that display for a selected port • Offline sequences-The number of offline sequence that the port has received or transmitted. • Link resets-The number of link reset protocol frames received/transmitted by this port from/to the attached device. The director transmits a link reset to initiate the link reset protocol or recover from a link timeout. This occurs normally to establish BB_Credit or on any port in order to recover lost BB_Credit. The director receives a link reset from an attached device if the device wishes to initiate the link reset or recover from a link timeout. Troubleshooting Tips As a general rule, you should clear all counts after the system is stabilized. When looking at the Performance View, roughly keep track of the time interval when errors accumulate to judge the presence and severity of a problem. Also, recognize that there is a link recovery hierarchy implemented in Fibre Channel to handle some level of "expected anomalies." In general, only be concerned with error counts that increment very quickly. 2-40 director product manager user guide

  • 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
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
2–40
director product manager user guide
Monitoring and Managing the Director
•
Delimiter errors—
The number of times that the director detected an
unrecognized start-of-frame (SOF) delimiter, an unrecognized end-of-frame
(EOF) delimiter, or an invalid class of service. This indicates that the frame
arrived at the director’s port corrupted. This corruption can be due to
plugging/unplugging the link, bad optics at either end of the cable, bad cable, or
dirty or poor connections. Moving the connection around or replacing cables can
isolate the problem.
•
Address ID errors—
A received frame had an unavailable or invalid Fibre
Channel destination address, or an invalid Fibre Channel source address. This
typically indicates the destination device is unavailable.
•
Frames too short—
A received frame exceeded the Fibre Channel frame
maximum size or was less than the Fibre Channel minimum size, indicating the
frame arrived at the director’s port corrupted. Frame corruption may be caused by
device disconnection, an optical transceiver failure at the device, a bad fiber-optic
cable, or a poor cable connection.
Operational Statistics
The following describes the Operational Statistics that display for a selected port
•
Offline sequences
—The number of offline sequence that the port has received or
transmitted.
•
Link resets
—The number of link reset protocol frames received/transmitted by
this port from/to the attached device. The director transmits a link reset to initiate
the link reset protocol or recover from a link timeout. This occurs normally to
establish BB_Credit or on any port in order to recover lost BB_Credit. The
director receives a link reset from an attached device if the device wishes to
initiate the link reset or recover from a link timeout.
Troubleshooting Tips
As a general rule, you should clear all counts after the system is stabilized. When
looking at the
Performance View
, roughly keep track of the time interval when errors
accumulate to judge the presence and severity of a problem. Also, recognize that there
is a link recovery hierarchy implemented in Fibre Channel to handle some level of
“expected anomalies.” In general, only be concerned with error counts that increment
very quickly.