HP StorageWorks MSA 2/8 HP StorageWorks Fabric OS 3.X Document Addendum (AA-RW - Page 95

Diag-errstat Trunc, Diag-init

Page 95 highlights

Diagnostic and system error messages reference guide DIAG-ERRSTAT (TRUNC) Message CRITICAL DIAG-ERRSTAT (TRUNC), 1, , pass , Pt TruncFrm Error Counter is sb 0, Err# Probable Cause The Port Error Statistics counter is nonzero, which means that a Truncated frame error was detected when receiving frames. This can be caused by a faulty cable or deteriorated SFP. It can also indicate more serious problems in the motherboard or ASIC. This message is generated by the portloopbacktest or spinsilk command. The error code value is for internal use only. Recommended Action Check for a faulty cable or deteriorated SFP. Replace the cable or SFP if necessary. If the problem persists: ■ For the SAN Switch 2/16, replace the motherboard FRU. ■ For the SAN Switch 2/8 EL, replace the entire switch. Severity CRITICAL DIAG-INIT Message CRITICAL DIAG-INIT, 1, , pass , Pt Failed to go active after initialization, Err# Probable Cause The port failed to go active in the loopback mode requested. This can be caused by a faulty cable or deteriorated SFP. It can also indicate more serious problems in the motherboard or ASIC. This message is generated by the crossporttest, portloopbacktest, or spinsilk command. The error code value is for internal use only. Fabric OS 3.x Document Addendum 95

  • 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

Diagnostic and system error messages reference guide
95
Fabric OS 3.x Document Addendum
DIAG-ERRSTAT (TRUNC)
Message
Probable Cause
The Port Error Statistics counter is nonzero, which means that a
Truncated frame
error
was detected when receiving frames. This can be caused by a faulty cable or deteriorated SFP.
It can also indicate more serious problems in the motherboard or ASIC. This message is
generated by the
portloopbacktest
or
spinsilk
command. The
error code
value
is for internal use only.
Recommended Action
Check for a faulty cable or deteriorated SFP. Replace the cable or SFP if necessary. If the
problem persists:
For the SAN Switch 2/16, replace the motherboard FRU.
For the SAN Switch 2/8 EL, replace the entire switch.
Severity
CRITICAL
DIAG-INIT
Message
Probable Cause
The port failed to go active in the loopback mode requested. This can be caused by a faulty
cable or deteriorated SFP. It can also indicate more serious problems in the motherboard or
ASIC. This message is generated by the
crossporttest
,
portloopbacktest
, or
spinsilk
command. The
error code
value is for internal use only.
<timestamp>
CRITICAL DIAG-ERRSTAT (TRUNC), 1, <test name>, pass <number>,
Pt<port information> TruncFrm Error Counter is <number> sb 0,
Err# <error code>
<timestamp>
CRITICAL DIAG-INIT, 1, <test name>, pass <number>,
Pt<port information><speed> Failed to go active after initialization,
Err# <error code>