HP Surestore 64 HP Surestore Director FC-64 Product Manager User's Guide - Page 109

Link resets, Class 2 Statistics, Received, Frames, Busied Frames, Rejected Frames

Page 109 highlights

Monitoring and Managing the Director • 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. There are not thresholds for these values. You may determine that a problem exists by the rate that the value changes. BB_Credit starvation can occur if data is sent to a device faster than it can consume the frames. This can backup into ISLs causing degraded performance. Class 2 Statistics The Class 2 Statistics table includes: • Received Frames The number of Class 2 frames received by this F_Port from its attached N_Port. • Busied Frames The number of F_BSY frames generated by this F_Port against Class 2 frames. This can occur if frames are received before the switch completes initialization or if the switch is servicing so many requests that it can not process a new request. The port generates frames if the switch is not ready to accept commands. This may indicate temporary congestion. • Rejected Frames The number of F_RJT frames generated by this F_Port against Class 2 frames. These frames usually occur because of attached device errors. The device is expected to correct the error based on the reject code, then retry its request. If the device is able to recover, there is no cause for concern. If not, further troubleshooting may be necessary. There are no thresholds for this value. Typically, this occurs because the destination is not available due to the device's action. Performance View 93

  • 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
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260

Performance View
93
Monitoring and
Managing the Director
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.
There are not thresholds for these values. You may determine that a problem exists by
the rate that the value changes. BB_Credit starvation can occur if data is sent to a
device faster than it can consume the frames. This can backup into ISLs causing
degraded performance.
Class 2 Statistics
The Class 2 Statistics table includes:
Received
Frames
The number of Class 2 frames received by this F_Port from its attached N_Port.
Busied Frames
The number of F_BSY frames generated by this F_Port against Class 2 frames. This can
occur if frames are received before the switch completes initialization or if the switch
is servicing so many requests that it can not process a new request. The port generates
frames if the switch is not ready to accept commands. This may indicate temporary
congestion.
Rejected Frames
The number of F_RJT frames generated by this F_Port against Class 2 frames.
These frames usually occur because of attached device errors. The device is expected
to correct the error based on the reject code, then retry its request. If the device is able
to recover, there is no cause for concern. If not, further troubleshooting may be
necessary. There are no thresholds for this value. Typically, this occurs because the
destination is not available due to the device
s action.