HP Surestore 64 fw 05.01.00 and sw 07.01.00 - Director Product Manager - User - Page 169

Link Incident Log, Link Incident Log

Page 169 highlights

Using Logs Link Incident Log The Link Incident Log displays the 1000 most recent link incidents with the date the incident occurred, the time it occurred, and the port on which the incident took place. The information is useful to maintenance personnel for isolating port problems [particularly expansion port (E_Port) segmentation problems] and repair verification. Figure 56: Link Incident Log Each log entry contains: ■ Date/Time-The date and time of the incident. ■ Port-The number of the port on which the incident occurred. ■ Link Incident-A short description of the incident. The following events may cause a link incident to be written to the log. - Implicit incident. The attached node detects a condition that may cause problems on the link. - Bit-error threshold exceeded. The number of code violation errors has exceeded threshold. - Loss-of-signal or loss-of-synchronization. This occurs if a cable is unplugged from an attached node. Loss-of-synchronization condition has persisted for longer than the resource allocation time out value (R_A_TOV). - Not-operational (NOS) primitive sequence received. A NOS was recognized. - Primitive sequence timeout. Link reset protocol timeout occurred. Timeout occurred for an appropriate response while in NOS receive state and after NOS is no longer recognized. Director Product Manager User Guide 169

  • 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

Using Logs
169
Director Product Manager User Guide
Link Incident Log
The Link Incident Log displays the 1000 most recent link incidents with the date
the incident occurred, the time it occurred, and the port on which the incident took
place. The information is useful to maintenance personnel for isolating port
problems [particularly expansion port (E_Port) segmentation problems] and repair
verification.
Figure 56:
Link Incident Log
Each log entry contains:
Date/Time—
The date and time of the incident.
Port—
The number of the port on which the incident occurred.
Link Incident—
A short description of the incident. The following events
may cause a link incident to be written to the log.
Implicit incident. The attached node detects a condition that may cause
problems on the link.
Bit-error threshold exceeded. The number of code violation errors has
exceeded threshold.
Loss-of-signal or loss-of-synchronization. This occurs if a cable is
unplugged from an attached node. Loss-of-synchronization condition has
persisted for longer than the resource allocation time out value
(R_A_TOV).
Not-operational (NOS) primitive sequence received. A NOS was
recognized.
Primitive sequence timeout. Link reset protocol timeout occurred.
Timeout occurred for an appropriate response while in NOS receive state
and after NOS is no longer recognized.