2 # Copyright 2009 Sun Microsystems, Inc. All rights reserved.
3 # Use is subject to license terms.
7 # The contents of this file are subject to the terms of the
8 # Common Development and Distribution License (the "License").
9 # You may not use this file except in compliance with the License.
11 # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
12 # or http://www.opensolaris.org/os/licensing.
13 # See the License for the specific language governing permissions
14 # and limitations under the License.
16 # When distributing Covered Code, include this CDDL HEADER in each
17 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
18 # If applicable, add the following below this CDDL HEADER, with the
19 # fields enclosed by brackets "[]" replaced with your own identifying
20 # information: Portions Copyright [yyyy] [name of copyright owner]
25 # DO NOT EDIT -- this file is generated by the Event Registry.
29 # keys: fault.memory.page
31 msgid "SUN4U-8000-1A.type"
33 msgid "SUN4U-8000-1A.severity"
35 msgid "SUN4U-8000-1A.description"
36 msgstr "The number of errors associated with this memory module continues to exceed acceptable levels. Refer to %s for more information."
37 msgid "SUN4U-8000-1A.response"
38 msgstr "An attempt will be made to remove this memory page from service."
39 msgid "SUN4U-8000-1A.impact"
40 msgstr "The performance of the system may be minimally impacted as a result of removing the memory page from operation."
41 msgid "SUN4U-8000-1A.action"
42 msgstr "No repair action is recommended at this time."
45 # keys: fault.memory.dimm
47 msgid "SUN4U-8000-2S.type"
49 msgid "SUN4U-8000-2S.severity"
51 msgid "SUN4U-8000-2S.description"
52 msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information."
53 msgid "SUN4U-8000-2S.response"
54 msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached."
55 msgid "SUN4U-8000-2S.impact"
56 msgstr "Total system memory capacity has been reduced."
57 msgid "SUN4U-8000-2S.action"
58 msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to identify the memory module."
61 # keys: fault.memory.bank
63 msgid "SUN4U-8000-35.type"
65 msgid "SUN4U-8000-35.severity"
67 msgid "SUN4U-8000-35.description"
68 msgstr "The number of errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information."
69 msgid "SUN4U-8000-35.response"
70 msgstr "Pages of memory associated with this memory module are being removed from service as errors are reported."
71 msgid "SUN4U-8000-35.impact"
72 msgstr "Total system memory capacity will be reduced as pages are retired."
73 msgid "SUN4U-8000-35.action"
74 msgstr "Schedule a repair procedure to replace the affected memory module. Use fmdump -v -u <EVENT_ID> to identify the module."
77 # keys: fault.cpu.ultraSPARC-III.dcache
79 msgid "SUN4U-8000-4Y.type"
81 msgid "SUN4U-8000-4Y.severity"
83 msgid "SUN4U-8000-4Y.description"
84 msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information."
85 msgid "SUN4U-8000-4Y.response"
86 msgstr "The fault manager will attempt to remove the affected CPU from service."
87 msgid "SUN4U-8000-4Y.impact"
88 msgstr "System performance may be affected."
89 msgid "SUN4U-8000-4Y.action"
90 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
93 # keys: fault.cpu.ultraSPARC-III.icache
95 msgid "SUN4U-8000-53.type"
97 msgid "SUN4U-8000-53.severity"
99 msgid "SUN4U-8000-53.description"
100 msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information."
101 msgid "SUN4U-8000-53.response"
102 msgstr "The fault manager will attempt to remove the affected CPU from service."
103 msgid "SUN4U-8000-53.impact"
104 msgstr "System performance may be affected."
105 msgid "SUN4U-8000-53.action"
106 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
108 # code: SUN4U-8000-6H
109 # keys: fault.cpu.ultraSPARC-III.l2cachedata
111 msgid "SUN4U-8000-6H.type"
113 msgid "SUN4U-8000-6H.severity"
115 msgid "SUN4U-8000-6H.description"
116 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
117 msgid "SUN4U-8000-6H.response"
118 msgstr "The fault manager will attempt to remove the affected CPU from service."
119 msgid "SUN4U-8000-6H.impact"
120 msgstr "System performance may be affected."
121 msgid "SUN4U-8000-6H.action"
122 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
124 # code: SUN4U-8000-7D
125 # keys: fault.cpu.ultraSPARC-III.l2cachetag
127 msgid "SUN4U-8000-7D.type"
129 msgid "SUN4U-8000-7D.severity"
131 msgid "SUN4U-8000-7D.description"
132 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
133 msgid "SUN4U-8000-7D.response"
134 msgstr "The fault manager will attempt to remove the affected CPU from service."
135 msgid "SUN4U-8000-7D.impact"
136 msgstr "System performance may be affected."
137 msgid "SUN4U-8000-7D.action"
138 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
140 # code: SUN4U-8000-84
141 # keys: fault.cpu.ultraSPARC-IIIi.dcache
143 msgid "SUN4U-8000-84.type"
145 msgid "SUN4U-8000-84.severity"
147 msgid "SUN4U-8000-84.description"
148 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
149 msgid "SUN4U-8000-84.response"
150 msgstr "The fault manager will attempt to remove the affected CPU from service."
151 msgid "SUN4U-8000-84.impact"
152 msgstr "System performance system may be affected."
153 msgid "SUN4U-8000-84.action"
154 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
156 # code: SUN4U-8000-9R
157 # keys: fault.cpu.ultraSPARC-IIIi.icache
159 msgid "SUN4U-8000-9R.type"
161 msgid "SUN4U-8000-9R.severity"
163 msgid "SUN4U-8000-9R.description"
164 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
165 msgid "SUN4U-8000-9R.response"
166 msgstr "The fault manager will attempt to remove the affected CPU from service."
167 msgid "SUN4U-8000-9R.impact"
168 msgstr "System performance may be affected."
169 msgid "SUN4U-8000-9R.action"
170 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
172 # code: SUN4U-8000-AC
173 # keys: fault.cpu.ultraSPARC-IIIi.l2cachedata
175 msgid "SUN4U-8000-AC.type"
177 msgid "SUN4U-8000-AC.severity"
179 msgid "SUN4U-8000-AC.description"
180 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
181 msgid "SUN4U-8000-AC.response"
182 msgstr "The fault manager will attempt to remove the affected CPU from service."
183 msgid "SUN4U-8000-AC.impact"
184 msgstr "System performance may be affected."
185 msgid "SUN4U-8000-AC.action"
186 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
188 # code: SUN4U-8000-CQ
189 # keys: fault.cpu.ultraSPARC-IIIi.l2cachetag
191 msgid "SUN4U-8000-CQ.type"
193 msgid "SUN4U-8000-CQ.severity"
195 msgid "SUN4U-8000-CQ.description"
196 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
197 msgid "SUN4U-8000-CQ.response"
198 msgstr "The fault manager will attempt to remove the affected CPU from service."
199 msgid "SUN4U-8000-CQ.impact"
200 msgstr "System performance may be affected."
201 msgid "SUN4U-8000-CQ.action"
202 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
204 # code: SUN4U-8000-DE
205 # keys: fault.cpu.ultraSPARC-IIIplus.dcache
207 msgid "SUN4U-8000-DE.type"
209 msgid "SUN4U-8000-DE.severity"
211 msgid "SUN4U-8000-DE.description"
212 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
213 msgid "SUN4U-8000-DE.response"
214 msgstr "The fault manager will attempt to remove the affected CPU from service."
215 msgid "SUN4U-8000-DE.impact"
216 msgstr "System performance may be affected."
217 msgid "SUN4U-8000-DE.action"
218 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
220 # code: SUN4U-8000-EJ
221 # keys: fault.cpu.ultraSPARC-IIIplus.icache
223 msgid "SUN4U-8000-EJ.type"
225 msgid "SUN4U-8000-EJ.severity"
227 msgid "SUN4U-8000-EJ.description"
228 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
229 msgid "SUN4U-8000-EJ.response"
230 msgstr "The fault manager will attempt to remove the affected CPU from service."
231 msgid "SUN4U-8000-EJ.impact"
232 msgstr "System performance may be affected."
233 msgid "SUN4U-8000-EJ.action"
234 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
236 # code: SUN4U-8000-F2
237 # keys: fault.cpu.ultraSPARC-IIIplus.l2cachedata
239 msgid "SUN4U-8000-F2.type"
241 msgid "SUN4U-8000-F2.severity"
243 msgid "SUN4U-8000-F2.description"
244 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
245 msgid "SUN4U-8000-F2.response"
246 msgstr "The fault manager will attempt to remove the affected CPU from service."
247 msgid "SUN4U-8000-F2.impact"
248 msgstr "System performance may be affected."
249 msgid "SUN4U-8000-F2.action"
250 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
252 # code: SUN4U-8000-GX
253 # keys: fault.cpu.ultraSPARC-IIIplus.l2cachetag
255 msgid "SUN4U-8000-GX.type"
257 msgid "SUN4U-8000-GX.severity"
259 msgid "SUN4U-8000-GX.description"
260 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
261 msgid "SUN4U-8000-GX.response"
262 msgstr "An attempt will be made to remove the affected CPU from service."
263 msgid "SUN4U-8000-GX.impact"
264 msgstr "System performance may be affected."
265 msgid "SUN4U-8000-GX.action"
266 msgstr "Schedule a repair procedure to replace the affected CPU. Use fmdump -v -u <EVENT_ID> to identify the CPU."
268 # code: SUN4U-8000-H5
269 # keys: fault.cpu.ultraSPARC-IV.dcache
271 msgid "SUN4U-8000-H5.type"
273 msgid "SUN4U-8000-H5.severity"
275 msgid "SUN4U-8000-H5.description"
276 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
277 msgid "SUN4U-8000-H5.response"
278 msgstr "The fault manager will attempt to remove the affected CPU from service."
279 msgid "SUN4U-8000-H5.impact"
280 msgstr "System performance may be affected."
281 msgid "SUN4U-8000-H5.action"
282 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
284 # code: SUN4U-8000-JS
285 # keys: fault.cpu.ultraSPARC-IV.icache
287 msgid "SUN4U-8000-JS.type"
289 msgid "SUN4U-8000-JS.severity"
291 msgid "SUN4U-8000-JS.description"
292 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
293 msgid "SUN4U-8000-JS.response"
294 msgstr "The fault manager will attempt to remove the affected CPU from service."
295 msgid "SUN4U-8000-JS.impact"
296 msgstr "System performance may be affected."
297 msgid "SUN4U-8000-JS.action"
298 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
300 # code: SUN4U-8000-KA
301 # keys: fault.cpu.ultraSPARC-IV.l2cachedata
303 msgid "SUN4U-8000-KA.type"
305 msgid "SUN4U-8000-KA.severity"
307 msgid "SUN4U-8000-KA.description"
308 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
309 msgid "SUN4U-8000-KA.response"
310 msgstr "The fault manager will attempt to remove the affected CPU from service."
311 msgid "SUN4U-8000-KA.impact"
312 msgstr "System performance may be affected."
313 msgid "SUN4U-8000-KA.action"
314 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
316 # code: SUN4U-8000-LP
317 # keys: fault.cpu.ultraSPARC-IV.l2cachetag
319 msgid "SUN4U-8000-LP.type"
321 msgid "SUN4U-8000-LP.severity"
323 msgid "SUN4U-8000-LP.description"
324 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
325 msgid "SUN4U-8000-LP.response"
326 msgstr "The fault manager will attempt to remove the affected CPU from service."
327 msgid "SUN4U-8000-LP.impact"
328 msgstr "System performance may be affected."
329 msgid "SUN4U-8000-LP.action"
330 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
332 # code: SUN4U-8000-MD
333 # keys: fault.cpu.ultraSPARC-III.fpu
335 msgid "SUN4U-8000-MD.type"
337 msgid "SUN4U-8000-MD.severity"
339 msgid "SUN4U-8000-MD.description"
340 msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information."
341 msgid "SUN4U-8000-MD.response"
342 msgstr "The fault manager will attempt to remove the affected CPU from service."
343 msgid "SUN4U-8000-MD.impact"
344 msgstr "System performance may be affected."
345 msgid "SUN4U-8000-MD.action"
346 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
348 # code: SUN4U-8000-NH
349 # keys: fault.cpu.ultraSPARC-IIIi.fpu
351 msgid "SUN4U-8000-NH.type"
353 msgid "SUN4U-8000-NH.severity"
355 msgid "SUN4U-8000-NH.description"
356 msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information."
357 msgid "SUN4U-8000-NH.response"
358 msgstr "The fault manager will attempt to remove the affected CPU from service."
359 msgid "SUN4U-8000-NH.impact"
360 msgstr "System performance may be affected."
361 msgid "SUN4U-8000-NH.action"
362 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
364 # code: SUN4U-8000-P3
365 # keys: fault.cpu.ultraSPARC-IIIplus.fpu
367 msgid "SUN4U-8000-P3.type"
369 msgid "SUN4U-8000-P3.severity"
371 msgid "SUN4U-8000-P3.description"
372 msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information."
373 msgid "SUN4U-8000-P3.response"
374 msgstr "The fault manager will attempt to remove the affected CPU from service."
375 msgid "SUN4U-8000-P3.impact"
376 msgstr "System performance may be affected."
377 msgid "SUN4U-8000-P3.action"
378 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
380 # code: SUN4U-8000-QY
381 # keys: fault.cpu.ultraSPARC-IV.fpu
383 msgid "SUN4U-8000-QY.type"
385 msgid "SUN4U-8000-QY.severity"
387 msgid "SUN4U-8000-QY.description"
388 msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information."
389 msgid "SUN4U-8000-QY.response"
390 msgstr "The fault manager will attempt to remove the affected CPU from service."
391 msgid "SUN4U-8000-QY.impact"
392 msgstr "System performance may be affected."
393 msgid "SUN4U-8000-QY.action"
394 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
396 # code: SUN4U-8000-RQ
397 # keys: fault.cpu.ultraSPARC-IVplus.fpu
399 msgid "SUN4U-8000-RQ.type"
401 msgid "SUN4U-8000-RQ.severity"
403 msgid "SUN4U-8000-RQ.description"
404 msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information."
405 msgid "SUN4U-8000-RQ.response"
406 msgstr "The fault manager will attempt to remove the affected CPU from service."
407 msgid "SUN4U-8000-RQ.impact"
408 msgstr "System performance may be affected."
409 msgid "SUN4U-8000-RQ.action"
410 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
412 # code: SUN4U-8000-SC
413 # keys: fault.cpu.ultraSPARC-IVplus.dcache
415 msgid "SUN4U-8000-SC.type"
417 msgid "SUN4U-8000-SC.severity"
419 msgid "SUN4U-8000-SC.description"
420 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
421 msgid "SUN4U-8000-SC.response"
422 msgstr "The fault manager will attempt to remove the affected CPU from service."
423 msgid "SUN4U-8000-SC.impact"
424 msgstr "System performance may be affected."
425 msgid "SUN4U-8000-SC.action"
426 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
428 # code: SUN4U-8000-TR
429 # keys: fault.cpu.ultraSPARC-IVplus.icache
431 msgid "SUN4U-8000-TR.type"
433 msgid "SUN4U-8000-TR.severity"
435 msgid "SUN4U-8000-TR.description"
436 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
437 msgid "SUN4U-8000-TR.response"
438 msgstr "The fault manager will attempt to remove the affected CPU from service."
439 msgid "SUN4U-8000-TR.impact"
440 msgstr "System performance may be affected."
441 msgid "SUN4U-8000-TR.action"
442 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
444 # code: SUN4U-8000-U4
445 # keys: fault.cpu.ultraSPARC-IVplus.pcache
447 msgid "SUN4U-8000-U4.type"
449 msgid "SUN4U-8000-U4.severity"
451 msgid "SUN4U-8000-U4.description"
452 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
453 msgid "SUN4U-8000-U4.response"
454 msgstr "The fault manager will attempt to remove the affected CPU from service."
455 msgid "SUN4U-8000-U4.impact"
456 msgstr "System performance may be affected."
457 msgid "SUN4U-8000-U4.action"
458 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
460 # code: SUN4U-8000-VX
461 # keys: fault.cpu.ultraSPARC-IVplus.dtlb
463 msgid "SUN4U-8000-VX.type"
465 msgid "SUN4U-8000-VX.severity"
467 msgid "SUN4U-8000-VX.description"
468 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
469 msgid "SUN4U-8000-VX.response"
470 msgstr "The fault manager will attempt to remove the affected CPU from service."
471 msgid "SUN4U-8000-VX.impact"
472 msgstr "System performance may be affected."
473 msgid "SUN4U-8000-VX.action"
474 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
476 # code: SUN4U-8000-W2
477 # keys: fault.cpu.ultraSPARC-IVplus.itlb
479 msgid "SUN4U-8000-W2.type"
481 msgid "SUN4U-8000-W2.severity"
483 msgid "SUN4U-8000-W2.description"
484 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
485 msgid "SUN4U-8000-W2.response"
486 msgstr "The fault manager will attempt to remove the affected CPU from service."
487 msgid "SUN4U-8000-W2.impact"
488 msgstr "System performance may be affected."
489 msgid "SUN4U-8000-W2.action"
490 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
492 # code: SUN4U-8000-XJ
493 # keys: fault.cpu.ultraSPARC-IVplus.l2cachedata
495 msgid "SUN4U-8000-XJ.type"
497 msgid "SUN4U-8000-XJ.severity"
499 msgid "SUN4U-8000-XJ.description"
500 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
501 msgid "SUN4U-8000-XJ.response"
502 msgstr "The fault manager will attempt to remove the affected CPU from service."
503 msgid "SUN4U-8000-XJ.impact"
504 msgstr "System performance may be affected."
505 msgid "SUN4U-8000-XJ.action"
506 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
508 # code: SUN4U-8000-YE
509 # keys: fault.cpu.ultraSPARC-IVplus.l2cachetag
511 msgid "SUN4U-8000-YE.type"
513 msgid "SUN4U-8000-YE.severity"
515 msgid "SUN4U-8000-YE.description"
516 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
517 msgid "SUN4U-8000-YE.response"
518 msgstr "The fault manager will attempt to remove the affected CPU from service."
519 msgid "SUN4U-8000-YE.impact"
520 msgstr "System performance may be affected."
521 msgid "SUN4U-8000-YE.action"
522 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
524 # code: SUN4U-8001-0J
525 # keys: fault.cpu.ultraSPARC-IVplus.l3cachedata
527 msgid "SUN4U-8001-0J.type"
529 msgid "SUN4U-8001-0J.severity"
531 msgid "SUN4U-8001-0J.description"
532 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
533 msgid "SUN4U-8001-0J.response"
534 msgstr "The fault manager will attempt to remove the affected CPU from service."
535 msgid "SUN4U-8001-0J.impact"
536 msgstr "System performance may be affected."
537 msgid "SUN4U-8001-0J.action"
538 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
540 # code: SUN4U-8001-1E
541 # keys: fault.cpu.ultraSPARC-IVplus.l3cachetag
543 msgid "SUN4U-8001-1E.type"
545 msgid "SUN4U-8001-1E.severity"
547 msgid "SUN4U-8001-1E.description"
548 msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information."
549 msgid "SUN4U-8001-1E.response"
550 msgstr "The fault manager will attempt to remove the affected CPU from service."
551 msgid "SUN4U-8001-1E.impact"
552 msgstr "System performance may be affected."
553 msgid "SUN4U-8001-1E.action"
554 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
556 # code: SUN4U-8001-2X
557 # keys: defect.ultraSPARC-II.memory.nodiag
559 msgid "SUN4U-8001-2X.type"
561 msgid "SUN4U-8001-2X.severity"
563 msgid "SUN4U-8001-2X.description"
564 msgstr "The Solaris Fault Manager received an event from the IO subsystem for which automated diagnosis software is currently unavailable. Refer to %s for more information."
565 msgid "SUN4U-8001-2X.response"
566 msgstr "The error information has been saved for examination by Sun."
567 msgid "SUN4U-8001-2X.impact"
568 msgstr "The error log will need to be manually examined using fmdump(1M) in order to determine if any human response is required."
569 msgid "SUN4U-8001-2X.action"
570 msgstr "Use fmdump -ev -u <EVENT-ID> to view and record the undiagnosed errors."
572 # code: SUN4U-8001-32
573 # keys: fault.memory.datapath
575 msgid "SUN4U-8001-32.type"
577 msgid "SUN4U-8001-32.severity"
579 msgid "SUN4U-8001-32.description"
580 msgstr "Errors have been detected on multiple memory modules, suggesting that a problem exists somewhere else in the system. Refer to %s for more information."
581 msgid "SUN4U-8001-32.response"
582 msgstr "Error reports from the affected components will be logged for examination by Sun."
583 msgid "SUN4U-8001-32.impact"
584 msgstr "System performance and stability may be affected."
585 msgid "SUN4U-8001-32.action"
586 msgstr "Contact your service provider for further diagnosis."
588 # code: SUN4U-8001-4R
589 # keys: fault.io.datapath
591 msgid "SUN4U-8001-4R.type"
593 msgid "SUN4U-8001-4R.severity"
595 msgid "SUN4U-8001-4R.description"
596 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
597 msgid "SUN4U-8001-4R.response"
598 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
599 msgid "SUN4U-8001-4R.impact"
600 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
601 msgid "SUN4U-8001-4R.action"
602 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
604 # code: SUN4U-8001-54
605 # keys: defect.io.pci.driver fault.io.datapath
607 msgid "SUN4U-8001-54.type"
609 msgid "SUN4U-8001-54.severity"
611 msgid "SUN4U-8001-54.description"
612 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
613 msgid "SUN4U-8001-54.response"
614 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
615 msgid "SUN4U-8001-54.impact"
616 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
617 msgid "SUN4U-8001-54.action"
618 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
620 # code: SUN4U-8001-6Q
621 # keys: fault.io.datapath fault.io.pci.bus
623 msgid "SUN4U-8001-6Q.type"
625 msgid "SUN4U-8001-6Q.severity"
627 msgid "SUN4U-8001-6Q.description"
628 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
629 msgid "SUN4U-8001-6Q.response"
630 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
631 msgid "SUN4U-8001-6Q.impact"
632 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
633 msgid "SUN4U-8001-6Q.action"
634 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
636 # code: SUN4U-8001-7C
637 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus
639 msgid "SUN4U-8001-7C.type"
641 msgid "SUN4U-8001-7C.severity"
643 msgid "SUN4U-8001-7C.description"
644 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
645 msgid "SUN4U-8001-7C.response"
646 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
647 msgid "SUN4U-8001-7C.impact"
648 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
649 msgid "SUN4U-8001-7C.action"
650 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
652 # code: SUN4U-8001-83
653 # keys: fault.io.datapath fault.io.pci.device
655 msgid "SUN4U-8001-83.type"
657 msgid "SUN4U-8001-83.severity"
659 msgid "SUN4U-8001-83.description"
660 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
661 msgid "SUN4U-8001-83.response"
662 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
663 msgid "SUN4U-8001-83.impact"
664 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
665 msgid "SUN4U-8001-83.action"
666 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
668 # code: SUN4U-8001-9Y
669 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device
671 msgid "SUN4U-8001-9Y.type"
673 msgid "SUN4U-8001-9Y.severity"
675 msgid "SUN4U-8001-9Y.description"
676 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
677 msgid "SUN4U-8001-9Y.response"
678 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
679 msgid "SUN4U-8001-9Y.impact"
680 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
681 msgid "SUN4U-8001-9Y.action"
682 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
684 # code: SUN4U-8001-AD
685 # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device
687 msgid "SUN4U-8001-AD.type"
689 msgid "SUN4U-8001-AD.severity"
691 msgid "SUN4U-8001-AD.description"
692 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
693 msgid "SUN4U-8001-AD.response"
694 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
695 msgid "SUN4U-8001-AD.impact"
696 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
697 msgid "SUN4U-8001-AD.action"
698 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
700 # code: SUN4U-8001-CH
701 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device
703 msgid "SUN4U-8001-CH.type"
705 msgid "SUN4U-8001-CH.severity"
707 msgid "SUN4U-8001-CH.description"
708 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
709 msgid "SUN4U-8001-CH.response"
710 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
711 msgid "SUN4U-8001-CH.impact"
712 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
713 msgid "SUN4U-8001-CH.action"
714 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
716 # code: SUN4U-8001-DA
717 # keys: fault.io.hbus
719 msgid "SUN4U-8001-DA.type"
721 msgid "SUN4U-8001-DA.severity"
723 msgid "SUN4U-8001-DA.description"
724 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
725 msgid "SUN4U-8001-DA.response"
726 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
727 msgid "SUN4U-8001-DA.impact"
728 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
729 msgid "SUN4U-8001-DA.action"
730 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
732 # code: SUN4U-8001-EP
733 # keys: defect.io.pci.driver fault.io.hbus
735 msgid "SUN4U-8001-EP.type"
737 msgid "SUN4U-8001-EP.severity"
739 msgid "SUN4U-8001-EP.description"
740 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
741 msgid "SUN4U-8001-EP.response"
742 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
743 msgid "SUN4U-8001-EP.impact"
744 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
745 msgid "SUN4U-8001-EP.action"
746 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
748 # code: SUN4U-8001-F5
749 # keys: fault.io.hbus fault.io.pci.bus
751 msgid "SUN4U-8001-F5.type"
753 msgid "SUN4U-8001-F5.severity"
755 msgid "SUN4U-8001-F5.description"
756 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
757 msgid "SUN4U-8001-F5.response"
758 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
759 msgid "SUN4U-8001-F5.impact"
760 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
761 msgid "SUN4U-8001-F5.action"
762 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
764 # code: SUN4U-8001-GS
765 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus
767 msgid "SUN4U-8001-GS.type"
769 msgid "SUN4U-8001-GS.severity"
771 msgid "SUN4U-8001-GS.description"
772 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
773 msgid "SUN4U-8001-GS.response"
774 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
775 msgid "SUN4U-8001-GS.impact"
776 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
777 msgid "SUN4U-8001-GS.action"
778 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
780 # code: SUN4U-8001-H2
781 # keys: fault.io.hbus fault.io.pci.device
783 msgid "SUN4U-8001-H2.type"
785 msgid "SUN4U-8001-H2.severity"
787 msgid "SUN4U-8001-H2.description"
788 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
789 msgid "SUN4U-8001-H2.response"
790 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
791 msgid "SUN4U-8001-H2.impact"
792 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
793 msgid "SUN4U-8001-H2.action"
794 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
796 # code: SUN4U-8001-JX
797 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device
799 msgid "SUN4U-8001-JX.type"
801 msgid "SUN4U-8001-JX.severity"
803 msgid "SUN4U-8001-JX.description"
804 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
805 msgid "SUN4U-8001-JX.response"
806 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
807 msgid "SUN4U-8001-JX.impact"
808 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
809 msgid "SUN4U-8001-JX.action"
810 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
812 # code: SUN4U-8001-KE
813 # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device
815 msgid "SUN4U-8001-KE.type"
817 msgid "SUN4U-8001-KE.severity"
819 msgid "SUN4U-8001-KE.description"
820 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
821 msgid "SUN4U-8001-KE.response"
822 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
823 msgid "SUN4U-8001-KE.impact"
824 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
825 msgid "SUN4U-8001-KE.action"
826 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
828 # code: SUN4U-8001-LJ
829 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device
831 msgid "SUN4U-8001-LJ.type"
833 msgid "SUN4U-8001-LJ.severity"
835 msgid "SUN4U-8001-LJ.description"
836 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
837 msgid "SUN4U-8001-LJ.response"
838 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
839 msgid "SUN4U-8001-LJ.impact"
840 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
841 msgid "SUN4U-8001-LJ.action"
842 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
844 # code: SUN4U-8001-MC
845 # keys: fault.io.datapath fault.io.hbus
847 msgid "SUN4U-8001-MC.type"
849 msgid "SUN4U-8001-MC.severity"
851 msgid "SUN4U-8001-MC.description"
852 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
853 msgid "SUN4U-8001-MC.response"
854 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
855 msgid "SUN4U-8001-MC.impact"
856 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
857 msgid "SUN4U-8001-MC.action"
858 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
860 # code: SUN4U-8001-NQ
861 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus
863 msgid "SUN4U-8001-NQ.type"
865 msgid "SUN4U-8001-NQ.severity"
867 msgid "SUN4U-8001-NQ.description"
868 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
869 msgid "SUN4U-8001-NQ.response"
870 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
871 msgid "SUN4U-8001-NQ.impact"
872 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
873 msgid "SUN4U-8001-NQ.action"
874 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
876 # code: SUN4U-8001-P4
877 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus
879 msgid "SUN4U-8001-P4.type"
881 msgid "SUN4U-8001-P4.severity"
883 msgid "SUN4U-8001-P4.description"
884 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
885 msgid "SUN4U-8001-P4.response"
886 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
887 msgid "SUN4U-8001-P4.impact"
888 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
889 msgid "SUN4U-8001-P4.action"
890 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
892 # code: SUN4U-8001-QR
893 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus
895 msgid "SUN4U-8001-QR.type"
897 msgid "SUN4U-8001-QR.severity"
899 msgid "SUN4U-8001-QR.description"
900 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
901 msgid "SUN4U-8001-QR.response"
902 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
903 msgid "SUN4U-8001-QR.impact"
904 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
905 msgid "SUN4U-8001-QR.action"
906 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
908 # code: SUN4U-8001-RH
909 # keys: fault.io.datapath fault.io.hbus fault.io.pci.device
911 msgid "SUN4U-8001-RH.type"
913 msgid "SUN4U-8001-RH.severity"
915 msgid "SUN4U-8001-RH.description"
916 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
917 msgid "SUN4U-8001-RH.response"
918 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
919 msgid "SUN4U-8001-RH.impact"
920 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
921 msgid "SUN4U-8001-RH.action"
922 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
924 # code: SUN4U-8001-SD
925 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device
927 msgid "SUN4U-8001-SD.type"
929 msgid "SUN4U-8001-SD.severity"
931 msgid "SUN4U-8001-SD.description"
932 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
933 msgid "SUN4U-8001-SD.response"
934 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
935 msgid "SUN4U-8001-SD.impact"
936 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
937 msgid "SUN4U-8001-SD.action"
938 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
940 # code: SUN4U-8001-TY
941 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device
943 msgid "SUN4U-8001-TY.type"
945 msgid "SUN4U-8001-TY.severity"
947 msgid "SUN4U-8001-TY.description"
948 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
949 msgid "SUN4U-8001-TY.response"
950 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
951 msgid "SUN4U-8001-TY.impact"
952 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
953 msgid "SUN4U-8001-TY.action"
954 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
956 # code: SUN4U-8001-U3
957 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device
959 msgid "SUN4U-8001-U3.type"
961 msgid "SUN4U-8001-U3.severity"
963 msgid "SUN4U-8001-U3.description"
964 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
965 msgid "SUN4U-8001-U3.response"
966 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
967 msgid "SUN4U-8001-U3.impact"
968 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
969 msgid "SUN4U-8001-U3.action"
970 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
972 # code: SUN4U-8001-VS
973 # keys: fault.io.schizo
975 msgid "SUN4U-8001-VS.type"
977 msgid "SUN4U-8001-VS.severity"
979 msgid "SUN4U-8001-VS.description"
980 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
981 msgid "SUN4U-8001-VS.response"
982 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
983 msgid "SUN4U-8001-VS.impact"
984 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
985 msgid "SUN4U-8001-VS.action"
986 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
988 # code: SUN4U-8001-W5
989 # keys: defect.io.pci.driver fault.io.schizo
991 msgid "SUN4U-8001-W5.type"
993 msgid "SUN4U-8001-W5.severity"
995 msgid "SUN4U-8001-W5.description"
996 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
997 msgid "SUN4U-8001-W5.response"
998 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
999 msgid "SUN4U-8001-W5.impact"
1000 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1001 msgid "SUN4U-8001-W5.action"
1002 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1004 # code: SUN4U-8001-XP
1005 # keys: fault.io.pci.bus fault.io.schizo
1007 msgid "SUN4U-8001-XP.type"
1009 msgid "SUN4U-8001-XP.severity"
1011 msgid "SUN4U-8001-XP.description"
1012 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1013 msgid "SUN4U-8001-XP.response"
1014 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1015 msgid "SUN4U-8001-XP.impact"
1016 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1017 msgid "SUN4U-8001-XP.action"
1018 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1020 # code: SUN4U-8001-YA
1021 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo
1023 msgid "SUN4U-8001-YA.type"
1025 msgid "SUN4U-8001-YA.severity"
1027 msgid "SUN4U-8001-YA.description"
1028 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1029 msgid "SUN4U-8001-YA.response"
1030 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1031 msgid "SUN4U-8001-YA.impact"
1032 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1033 msgid "SUN4U-8001-YA.action"
1034 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1036 # code: SUN4U-8002-0R
1037 # keys: fault.io.pci.device fault.io.schizo
1039 msgid "SUN4U-8002-0R.type"
1041 msgid "SUN4U-8002-0R.severity"
1043 msgid "SUN4U-8002-0R.description"
1044 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1045 msgid "SUN4U-8002-0R.response"
1046 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1047 msgid "SUN4U-8002-0R.impact"
1048 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1049 msgid "SUN4U-8002-0R.action"
1050 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1052 # code: SUN4U-8002-14
1053 # keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo
1055 msgid "SUN4U-8002-14.type"
1057 msgid "SUN4U-8002-14.severity"
1059 msgid "SUN4U-8002-14.description"
1060 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1061 msgid "SUN4U-8002-14.response"
1062 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1063 msgid "SUN4U-8002-14.impact"
1064 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1065 msgid "SUN4U-8002-14.action"
1066 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1068 # code: SUN4U-8002-2Q
1069 # keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo
1071 msgid "SUN4U-8002-2Q.type"
1073 msgid "SUN4U-8002-2Q.severity"
1075 msgid "SUN4U-8002-2Q.description"
1076 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1077 msgid "SUN4U-8002-2Q.response"
1078 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1079 msgid "SUN4U-8002-2Q.impact"
1080 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1081 msgid "SUN4U-8002-2Q.action"
1082 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1084 # code: SUN4U-8002-3C
1085 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo
1087 msgid "SUN4U-8002-3C.type"
1089 msgid "SUN4U-8002-3C.severity"
1091 msgid "SUN4U-8002-3C.description"
1092 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1093 msgid "SUN4U-8002-3C.response"
1094 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1095 msgid "SUN4U-8002-3C.impact"
1096 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1097 msgid "SUN4U-8002-3C.action"
1098 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1100 # code: SUN4U-8002-4J
1101 # keys: fault.io.datapath fault.io.schizo
1103 msgid "SUN4U-8002-4J.type"
1105 msgid "SUN4U-8002-4J.severity"
1107 msgid "SUN4U-8002-4J.description"
1108 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1109 msgid "SUN4U-8002-4J.response"
1110 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1111 msgid "SUN4U-8002-4J.impact"
1112 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1113 msgid "SUN4U-8002-4J.action"
1114 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1116 # code: SUN4U-8002-5E
1117 # keys: defect.io.pci.driver fault.io.datapath fault.io.schizo
1119 msgid "SUN4U-8002-5E.type"
1121 msgid "SUN4U-8002-5E.severity"
1123 msgid "SUN4U-8002-5E.description"
1124 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1125 msgid "SUN4U-8002-5E.response"
1126 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1127 msgid "SUN4U-8002-5E.impact"
1128 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1129 msgid "SUN4U-8002-5E.action"
1130 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1132 # code: SUN4U-8002-6X
1133 # keys: fault.io.datapath fault.io.pci.bus fault.io.schizo
1135 msgid "SUN4U-8002-6X.type"
1137 msgid "SUN4U-8002-6X.severity"
1139 msgid "SUN4U-8002-6X.description"
1140 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1141 msgid "SUN4U-8002-6X.response"
1142 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1143 msgid "SUN4U-8002-6X.impact"
1144 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1145 msgid "SUN4U-8002-6X.action"
1146 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1148 # code: SUN4U-8002-72
1149 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo
1151 msgid "SUN4U-8002-72.type"
1153 msgid "SUN4U-8002-72.severity"
1155 msgid "SUN4U-8002-72.description"
1156 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1157 msgid "SUN4U-8002-72.response"
1158 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1159 msgid "SUN4U-8002-72.impact"
1160 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1161 msgid "SUN4U-8002-72.action"
1162 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1164 # code: SUN4U-8002-8A
1165 # keys: fault.io.datapath fault.io.pci.device fault.io.schizo
1167 msgid "SUN4U-8002-8A.type"
1169 msgid "SUN4U-8002-8A.severity"
1171 msgid "SUN4U-8002-8A.description"
1172 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1173 msgid "SUN4U-8002-8A.response"
1174 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1175 msgid "SUN4U-8002-8A.impact"
1176 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1177 msgid "SUN4U-8002-8A.action"
1178 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1180 # code: SUN4U-8002-9P
1181 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo
1183 msgid "SUN4U-8002-9P.type"
1185 msgid "SUN4U-8002-9P.severity"
1187 msgid "SUN4U-8002-9P.description"
1188 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1189 msgid "SUN4U-8002-9P.response"
1190 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1191 msgid "SUN4U-8002-9P.impact"
1192 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1193 msgid "SUN4U-8002-9P.action"
1194 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1196 # code: SUN4U-8002-A5
1197 # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo
1199 msgid "SUN4U-8002-A5.type"
1201 msgid "SUN4U-8002-A5.severity"
1203 msgid "SUN4U-8002-A5.description"
1204 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1205 msgid "SUN4U-8002-A5.response"
1206 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1207 msgid "SUN4U-8002-A5.impact"
1208 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1209 msgid "SUN4U-8002-A5.action"
1210 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1212 # code: SUN4U-8002-CS
1213 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo
1215 msgid "SUN4U-8002-CS.type"
1217 msgid "SUN4U-8002-CS.severity"
1219 msgid "SUN4U-8002-CS.description"
1220 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1221 msgid "SUN4U-8002-CS.response"
1222 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1223 msgid "SUN4U-8002-CS.impact"
1224 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1225 msgid "SUN4U-8002-CS.action"
1226 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1228 # code: SUN4U-8002-D3
1229 # keys: fault.io.hbus fault.io.schizo
1231 msgid "SUN4U-8002-D3.type"
1233 msgid "SUN4U-8002-D3.severity"
1235 msgid "SUN4U-8002-D3.description"
1236 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1237 msgid "SUN4U-8002-D3.response"
1238 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1239 msgid "SUN4U-8002-D3.impact"
1240 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1241 msgid "SUN4U-8002-D3.action"
1242 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1244 # code: SUN4U-8002-EY
1245 # keys: defect.io.pci.driver fault.io.hbus fault.io.schizo
1247 msgid "SUN4U-8002-EY.type"
1249 msgid "SUN4U-8002-EY.severity"
1251 msgid "SUN4U-8002-EY.description"
1252 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1253 msgid "SUN4U-8002-EY.response"
1254 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1255 msgid "SUN4U-8002-EY.impact"
1256 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1257 msgid "SUN4U-8002-EY.action"
1258 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1260 # code: SUN4U-8002-FD
1261 # keys: fault.io.hbus fault.io.pci.bus fault.io.schizo
1263 msgid "SUN4U-8002-FD.type"
1265 msgid "SUN4U-8002-FD.severity"
1267 msgid "SUN4U-8002-FD.description"
1268 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1269 msgid "SUN4U-8002-FD.response"
1270 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1271 msgid "SUN4U-8002-FD.impact"
1272 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1273 msgid "SUN4U-8002-FD.action"
1274 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1276 # code: SUN4U-8002-GH
1277 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo
1279 msgid "SUN4U-8002-GH.type"
1281 msgid "SUN4U-8002-GH.severity"
1283 msgid "SUN4U-8002-GH.description"
1284 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1285 msgid "SUN4U-8002-GH.response"
1286 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1287 msgid "SUN4U-8002-GH.impact"
1288 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1289 msgid "SUN4U-8002-GH.action"
1290 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1292 # code: SUN4U-8002-HC
1293 # keys: fault.io.hbus fault.io.pci.device fault.io.schizo
1295 msgid "SUN4U-8002-HC.type"
1297 msgid "SUN4U-8002-HC.severity"
1299 msgid "SUN4U-8002-HC.description"
1300 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1301 msgid "SUN4U-8002-HC.response"
1302 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1303 msgid "SUN4U-8002-HC.impact"
1304 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1305 msgid "SUN4U-8002-HC.action"
1306 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1308 # code: SUN4U-8002-JQ
1309 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo
1311 msgid "SUN4U-8002-JQ.type"
1313 msgid "SUN4U-8002-JQ.severity"
1315 msgid "SUN4U-8002-JQ.description"
1316 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1317 msgid "SUN4U-8002-JQ.response"
1318 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1319 msgid "SUN4U-8002-JQ.impact"
1320 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1321 msgid "SUN4U-8002-JQ.action"
1322 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1324 # code: SUN4U-8002-K4
1325 # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1327 msgid "SUN4U-8002-K4.type"
1329 msgid "SUN4U-8002-K4.severity"
1331 msgid "SUN4U-8002-K4.description"
1332 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1333 msgid "SUN4U-8002-K4.response"
1334 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1335 msgid "SUN4U-8002-K4.impact"
1336 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1337 msgid "SUN4U-8002-K4.action"
1338 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1340 # code: SUN4U-8002-LR
1341 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1343 msgid "SUN4U-8002-LR.type"
1345 msgid "SUN4U-8002-LR.severity"
1347 msgid "SUN4U-8002-LR.description"
1348 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1349 msgid "SUN4U-8002-LR.response"
1350 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1351 msgid "SUN4U-8002-LR.impact"
1352 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1353 msgid "SUN4U-8002-LR.action"
1354 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1356 # code: SUN4U-8002-M2
1357 # keys: fault.io.datapath fault.io.hbus fault.io.schizo
1359 msgid "SUN4U-8002-M2.type"
1361 msgid "SUN4U-8002-M2.severity"
1363 msgid "SUN4U-8002-M2.description"
1364 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1365 msgid "SUN4U-8002-M2.response"
1366 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1367 msgid "SUN4U-8002-M2.impact"
1368 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1369 msgid "SUN4U-8002-M2.action"
1370 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1372 # code: SUN4U-8002-NX
1373 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo
1375 msgid "SUN4U-8002-NX.type"
1377 msgid "SUN4U-8002-NX.severity"
1379 msgid "SUN4U-8002-NX.description"
1380 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1381 msgid "SUN4U-8002-NX.response"
1382 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1383 msgid "SUN4U-8002-NX.impact"
1384 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1385 msgid "SUN4U-8002-NX.action"
1386 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1388 # code: SUN4U-8002-PE
1389 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo
1391 msgid "SUN4U-8002-PE.type"
1393 msgid "SUN4U-8002-PE.severity"
1395 msgid "SUN4U-8002-PE.description"
1396 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1397 msgid "SUN4U-8002-PE.response"
1398 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1399 msgid "SUN4U-8002-PE.impact"
1400 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1401 msgid "SUN4U-8002-PE.action"
1402 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1404 # code: SUN4U-8002-QJ
1405 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo
1407 msgid "SUN4U-8002-QJ.type"
1409 msgid "SUN4U-8002-QJ.severity"
1411 msgid "SUN4U-8002-QJ.description"
1412 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1413 msgid "SUN4U-8002-QJ.response"
1414 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1415 msgid "SUN4U-8002-QJ.impact"
1416 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1417 msgid "SUN4U-8002-QJ.action"
1418 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1420 # code: SUN4U-8002-RS
1421 # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo
1423 msgid "SUN4U-8002-RS.type"
1425 msgid "SUN4U-8002-RS.severity"
1427 msgid "SUN4U-8002-RS.description"
1428 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1429 msgid "SUN4U-8002-RS.response"
1430 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1431 msgid "SUN4U-8002-RS.impact"
1432 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1433 msgid "SUN4U-8002-RS.action"
1434 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1436 # code: SUN4U-8002-S5
1437 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo
1439 msgid "SUN4U-8002-S5.type"
1441 msgid "SUN4U-8002-S5.severity"
1443 msgid "SUN4U-8002-S5.description"
1444 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1445 msgid "SUN4U-8002-S5.response"
1446 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1447 msgid "SUN4U-8002-S5.impact"
1448 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1449 msgid "SUN4U-8002-S5.action"
1450 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1452 # code: SUN4U-8002-TP
1453 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1455 msgid "SUN4U-8002-TP.type"
1457 msgid "SUN4U-8002-TP.severity"
1459 msgid "SUN4U-8002-TP.description"
1460 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1461 msgid "SUN4U-8002-TP.response"
1462 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1463 msgid "SUN4U-8002-TP.impact"
1464 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1465 msgid "SUN4U-8002-TP.action"
1466 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1468 # code: SUN4U-8002-UA
1469 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1471 msgid "SUN4U-8002-UA.type"
1473 msgid "SUN4U-8002-UA.severity"
1475 msgid "SUN4U-8002-UA.description"
1476 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1477 msgid "SUN4U-8002-UA.response"
1478 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1479 msgid "SUN4U-8002-UA.impact"
1480 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1481 msgid "SUN4U-8002-UA.action"
1482 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1484 # code: SUN4U-8002-VH
1485 # keys: fault.io.xmits
1487 msgid "SUN4U-8002-VH.type"
1489 msgid "SUN4U-8002-VH.severity"
1491 msgid "SUN4U-8002-VH.description"
1492 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1493 msgid "SUN4U-8002-VH.response"
1494 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1495 msgid "SUN4U-8002-VH.impact"
1496 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1497 msgid "SUN4U-8002-VH.action"
1498 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1500 # code: SUN4U-8002-WD
1501 # keys: defect.io.pci.driver fault.io.xmits
1503 msgid "SUN4U-8002-WD.type"
1505 msgid "SUN4U-8002-WD.severity"
1507 msgid "SUN4U-8002-WD.description"
1508 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1509 msgid "SUN4U-8002-WD.response"
1510 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1511 msgid "SUN4U-8002-WD.impact"
1512 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1513 msgid "SUN4U-8002-WD.action"
1514 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1516 # code: SUN4U-8002-XY
1517 # keys: fault.io.pci.bus fault.io.xmits
1519 msgid "SUN4U-8002-XY.type"
1521 msgid "SUN4U-8002-XY.severity"
1523 msgid "SUN4U-8002-XY.description"
1524 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1525 msgid "SUN4U-8002-XY.response"
1526 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1527 msgid "SUN4U-8002-XY.impact"
1528 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1529 msgid "SUN4U-8002-XY.action"
1530 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1532 # code: SUN4U-8002-Y3
1533 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.xmits
1535 msgid "SUN4U-8002-Y3.type"
1537 msgid "SUN4U-8002-Y3.severity"
1539 msgid "SUN4U-8002-Y3.description"
1540 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1541 msgid "SUN4U-8002-Y3.response"
1542 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1543 msgid "SUN4U-8002-Y3.impact"
1544 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1545 msgid "SUN4U-8002-Y3.action"
1546 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1548 # code: SUN4U-8003-0Y
1549 # keys: fault.io.pci.device fault.io.xmits
1551 msgid "SUN4U-8003-0Y.type"
1553 msgid "SUN4U-8003-0Y.severity"
1555 msgid "SUN4U-8003-0Y.description"
1556 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1557 msgid "SUN4U-8003-0Y.response"
1558 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1559 msgid "SUN4U-8003-0Y.impact"
1560 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1561 msgid "SUN4U-8003-0Y.action"
1562 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1564 # code: SUN4U-8003-13
1565 # keys: defect.io.pci.driver fault.io.pci.device fault.io.xmits
1567 msgid "SUN4U-8003-13.type"
1569 msgid "SUN4U-8003-13.severity"
1571 msgid "SUN4U-8003-13.description"
1572 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1573 msgid "SUN4U-8003-13.response"
1574 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1575 msgid "SUN4U-8003-13.impact"
1576 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1577 msgid "SUN4U-8003-13.action"
1578 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1580 # code: SUN4U-8003-2H
1581 # keys: fault.io.pci.bus fault.io.pci.device fault.io.xmits
1583 msgid "SUN4U-8003-2H.type"
1585 msgid "SUN4U-8003-2H.severity"
1587 msgid "SUN4U-8003-2H.description"
1588 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1589 msgid "SUN4U-8003-2H.response"
1590 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1591 msgid "SUN4U-8003-2H.impact"
1592 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1593 msgid "SUN4U-8003-2H.action"
1594 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1596 # code: SUN4U-8003-3D
1597 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.xmits
1599 msgid "SUN4U-8003-3D.type"
1601 msgid "SUN4U-8003-3D.severity"
1603 msgid "SUN4U-8003-3D.description"
1604 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1605 msgid "SUN4U-8003-3D.response"
1606 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1607 msgid "SUN4U-8003-3D.impact"
1608 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1609 msgid "SUN4U-8003-3D.action"
1610 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1612 # code: SUN4U-8003-4P
1613 # keys: fault.io.datapath fault.io.xmits
1615 msgid "SUN4U-8003-4P.type"
1617 msgid "SUN4U-8003-4P.severity"
1619 msgid "SUN4U-8003-4P.description"
1620 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1621 msgid "SUN4U-8003-4P.response"
1622 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1623 msgid "SUN4U-8003-4P.impact"
1624 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1625 msgid "SUN4U-8003-4P.action"
1626 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1628 # code: SUN4U-8003-5A
1629 # keys: defect.io.pci.driver fault.io.datapath fault.io.xmits
1631 msgid "SUN4U-8003-5A.type"
1633 msgid "SUN4U-8003-5A.severity"
1635 msgid "SUN4U-8003-5A.description"
1636 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1637 msgid "SUN4U-8003-5A.response"
1638 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1639 msgid "SUN4U-8003-5A.impact"
1640 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1641 msgid "SUN4U-8003-5A.action"
1642 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1644 # code: SUN4U-8003-6S
1645 # keys: fault.io.datapath fault.io.pci.bus fault.io.xmits
1647 msgid "SUN4U-8003-6S.type"
1649 msgid "SUN4U-8003-6S.severity"
1651 msgid "SUN4U-8003-6S.description"
1652 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1653 msgid "SUN4U-8003-6S.response"
1654 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1655 msgid "SUN4U-8003-6S.impact"
1656 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1657 msgid "SUN4U-8003-6S.action"
1658 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1660 # code: SUN4U-8003-75
1661 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.xmits
1663 msgid "SUN4U-8003-75.type"
1665 msgid "SUN4U-8003-75.severity"
1667 msgid "SUN4U-8003-75.description"
1668 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1669 msgid "SUN4U-8003-75.response"
1670 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1671 msgid "SUN4U-8003-75.impact"
1672 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1673 msgid "SUN4U-8003-75.action"
1674 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1676 # code: SUN4U-8003-8E
1677 # keys: fault.io.datapath fault.io.pci.device fault.io.xmits
1679 msgid "SUN4U-8003-8E.type"
1681 msgid "SUN4U-8003-8E.severity"
1683 msgid "SUN4U-8003-8E.description"
1684 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1685 msgid "SUN4U-8003-8E.response"
1686 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1687 msgid "SUN4U-8003-8E.impact"
1688 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1689 msgid "SUN4U-8003-8E.action"
1690 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1692 # code: SUN4U-8003-9J
1693 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.xmits
1695 msgid "SUN4U-8003-9J.type"
1697 msgid "SUN4U-8003-9J.severity"
1699 msgid "SUN4U-8003-9J.description"
1700 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1701 msgid "SUN4U-8003-9J.response"
1702 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1703 msgid "SUN4U-8003-9J.impact"
1704 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1705 msgid "SUN4U-8003-9J.action"
1706 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1708 # code: SUN4U-8003-A2
1709 # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits
1711 msgid "SUN4U-8003-A2.type"
1713 msgid "SUN4U-8003-A2.severity"
1715 msgid "SUN4U-8003-A2.description"
1716 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1717 msgid "SUN4U-8003-A2.response"
1718 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1719 msgid "SUN4U-8003-A2.impact"
1720 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1721 msgid "SUN4U-8003-A2.action"
1722 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1724 # code: SUN4U-8003-CX
1725 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits
1727 msgid "SUN4U-8003-CX.type"
1729 msgid "SUN4U-8003-CX.severity"
1731 msgid "SUN4U-8003-CX.description"
1732 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1733 msgid "SUN4U-8003-CX.response"
1734 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1735 msgid "SUN4U-8003-CX.impact"
1736 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1737 msgid "SUN4U-8003-CX.action"
1738 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1740 # code: SUN4U-8003-D4
1741 # keys: fault.io.hbus fault.io.xmits
1743 msgid "SUN4U-8003-D4.type"
1745 msgid "SUN4U-8003-D4.severity"
1747 msgid "SUN4U-8003-D4.description"
1748 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1749 msgid "SUN4U-8003-D4.response"
1750 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1751 msgid "SUN4U-8003-D4.impact"
1752 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1753 msgid "SUN4U-8003-D4.action"
1754 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1756 # code: SUN4U-8003-ER
1757 # keys: defect.io.pci.driver fault.io.hbus fault.io.xmits
1759 msgid "SUN4U-8003-ER.type"
1761 msgid "SUN4U-8003-ER.severity"
1763 msgid "SUN4U-8003-ER.description"
1764 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1765 msgid "SUN4U-8003-ER.response"
1766 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1767 msgid "SUN4U-8003-ER.impact"
1768 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1769 msgid "SUN4U-8003-ER.action"
1770 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1772 # code: SUN4U-8003-FC
1773 # keys: fault.io.hbus fault.io.pci.bus fault.io.xmits
1775 msgid "SUN4U-8003-FC.type"
1777 msgid "SUN4U-8003-FC.severity"
1779 msgid "SUN4U-8003-FC.description"
1780 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1781 msgid "SUN4U-8003-FC.response"
1782 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1783 msgid "SUN4U-8003-FC.impact"
1784 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1785 msgid "SUN4U-8003-FC.action"
1786 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1788 # code: SUN4U-8003-GQ
1789 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.xmits
1791 msgid "SUN4U-8003-GQ.type"
1793 msgid "SUN4U-8003-GQ.severity"
1795 msgid "SUN4U-8003-GQ.description"
1796 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1797 msgid "SUN4U-8003-GQ.response"
1798 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1799 msgid "SUN4U-8003-GQ.impact"
1800 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1801 msgid "SUN4U-8003-GQ.action"
1802 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1804 # code: SUN4U-8003-HD
1805 # keys: fault.io.hbus fault.io.pci.device fault.io.xmits
1807 msgid "SUN4U-8003-HD.type"
1809 msgid "SUN4U-8003-HD.severity"
1811 msgid "SUN4U-8003-HD.description"
1812 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1813 msgid "SUN4U-8003-HD.response"
1814 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1815 msgid "SUN4U-8003-HD.impact"
1816 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1817 msgid "SUN4U-8003-HD.action"
1818 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1820 # code: SUN4U-8003-JH
1821 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.xmits
1823 msgid "SUN4U-8003-JH.type"
1825 msgid "SUN4U-8003-JH.severity"
1827 msgid "SUN4U-8003-JH.description"
1828 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1829 msgid "SUN4U-8003-JH.response"
1830 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1831 msgid "SUN4U-8003-JH.impact"
1832 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1833 msgid "SUN4U-8003-JH.action"
1834 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1836 # code: SUN4U-8003-K3
1837 # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1839 msgid "SUN4U-8003-K3.type"
1841 msgid "SUN4U-8003-K3.severity"
1843 msgid "SUN4U-8003-K3.description"
1844 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1845 msgid "SUN4U-8003-K3.response"
1846 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1847 msgid "SUN4U-8003-K3.impact"
1848 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1849 msgid "SUN4U-8003-K3.action"
1850 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1852 # code: SUN4U-8003-LY
1853 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1855 msgid "SUN4U-8003-LY.type"
1857 msgid "SUN4U-8003-LY.severity"
1859 msgid "SUN4U-8003-LY.description"
1860 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1861 msgid "SUN4U-8003-LY.response"
1862 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1863 msgid "SUN4U-8003-LY.impact"
1864 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1865 msgid "SUN4U-8003-LY.action"
1866 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1868 # code: SUN4U-8003-M5
1869 # keys: fault.io.datapath fault.io.hbus fault.io.xmits
1871 msgid "SUN4U-8003-M5.type"
1873 msgid "SUN4U-8003-M5.severity"
1875 msgid "SUN4U-8003-M5.description"
1876 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1877 msgid "SUN4U-8003-M5.response"
1878 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1879 msgid "SUN4U-8003-M5.impact"
1880 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1881 msgid "SUN4U-8003-M5.action"
1882 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1884 # code: SUN4U-8003-NS
1885 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.xmits
1887 msgid "SUN4U-8003-NS.type"
1889 msgid "SUN4U-8003-NS.severity"
1891 msgid "SUN4U-8003-NS.description"
1892 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1893 msgid "SUN4U-8003-NS.response"
1894 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1895 msgid "SUN4U-8003-NS.impact"
1896 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1897 msgid "SUN4U-8003-NS.action"
1898 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1900 # code: SUN4U-8003-PA
1901 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits
1903 msgid "SUN4U-8003-PA.type"
1905 msgid "SUN4U-8003-PA.severity"
1907 msgid "SUN4U-8003-PA.description"
1908 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1909 msgid "SUN4U-8003-PA.response"
1910 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1911 msgid "SUN4U-8003-PA.impact"
1912 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1913 msgid "SUN4U-8003-PA.action"
1914 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1916 # code: SUN4U-8003-QP
1917 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits
1919 msgid "SUN4U-8003-QP.type"
1921 msgid "SUN4U-8003-QP.severity"
1923 msgid "SUN4U-8003-QP.description"
1924 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1925 msgid "SUN4U-8003-QP.response"
1926 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1927 msgid "SUN4U-8003-QP.impact"
1928 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1929 msgid "SUN4U-8003-QP.action"
1930 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1932 # code: SUN4U-8003-RX
1933 # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits
1935 msgid "SUN4U-8003-RX.type"
1937 msgid "SUN4U-8003-RX.severity"
1939 msgid "SUN4U-8003-RX.description"
1940 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1941 msgid "SUN4U-8003-RX.response"
1942 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1943 msgid "SUN4U-8003-RX.impact"
1944 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1945 msgid "SUN4U-8003-RX.action"
1946 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1948 # code: SUN4U-8003-S2
1949 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits
1951 msgid "SUN4U-8003-S2.type"
1953 msgid "SUN4U-8003-S2.severity"
1955 msgid "SUN4U-8003-S2.description"
1956 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1957 msgid "SUN4U-8003-S2.response"
1958 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1959 msgid "SUN4U-8003-S2.impact"
1960 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1961 msgid "SUN4U-8003-S2.action"
1962 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1964 # code: SUN4U-8003-TJ
1965 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1967 msgid "SUN4U-8003-TJ.type"
1969 msgid "SUN4U-8003-TJ.severity"
1971 msgid "SUN4U-8003-TJ.description"
1972 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
1973 msgid "SUN4U-8003-TJ.response"
1974 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1975 msgid "SUN4U-8003-TJ.impact"
1976 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1977 msgid "SUN4U-8003-TJ.action"
1978 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
1980 # code: SUN4U-8003-UE
1981 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1983 msgid "SUN4U-8003-UE.type"
1985 msgid "SUN4U-8003-UE.severity"
1987 msgid "SUN4U-8003-UE.description"
1988 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
1989 msgid "SUN4U-8003-UE.response"
1990 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1991 msgid "SUN4U-8003-UE.impact"
1992 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1993 msgid "SUN4U-8003-UE.action"
1994 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
1996 # code: SUN4U-8003-VQ
1997 # keys: fault.io.schizo fault.io.xmits
1999 msgid "SUN4U-8003-VQ.type"
2001 msgid "SUN4U-8003-VQ.severity"
2003 msgid "SUN4U-8003-VQ.description"
2004 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2005 msgid "SUN4U-8003-VQ.response"
2006 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2007 msgid "SUN4U-8003-VQ.impact"
2008 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2009 msgid "SUN4U-8003-VQ.action"
2010 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2012 # code: SUN4U-8003-WC
2013 # keys: defect.io.pci.driver fault.io.schizo fault.io.xmits
2015 msgid "SUN4U-8003-WC.type"
2017 msgid "SUN4U-8003-WC.severity"
2019 msgid "SUN4U-8003-WC.description"
2020 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2021 msgid "SUN4U-8003-WC.response"
2022 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2023 msgid "SUN4U-8003-WC.impact"
2024 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2025 msgid "SUN4U-8003-WC.action"
2026 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2028 # code: SUN4U-8003-XR
2029 # keys: fault.io.pci.bus fault.io.schizo fault.io.xmits
2031 msgid "SUN4U-8003-XR.type"
2033 msgid "SUN4U-8003-XR.severity"
2035 msgid "SUN4U-8003-XR.description"
2036 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2037 msgid "SUN4U-8003-XR.response"
2038 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2039 msgid "SUN4U-8003-XR.impact"
2040 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2041 msgid "SUN4U-8003-XR.action"
2042 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2044 # code: SUN4U-8003-Y4
2045 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo fault.io.xmits
2047 msgid "SUN4U-8003-Y4.type"
2049 msgid "SUN4U-8003-Y4.severity"
2051 msgid "SUN4U-8003-Y4.description"
2052 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2053 msgid "SUN4U-8003-Y4.response"
2054 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2055 msgid "SUN4U-8003-Y4.impact"
2056 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2057 msgid "SUN4U-8003-Y4.action"
2058 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2060 # code: SUN4U-8004-0A
2061 # keys: fault.io.pci.device fault.io.schizo fault.io.xmits
2063 msgid "SUN4U-8004-0A.type"
2065 msgid "SUN4U-8004-0A.severity"
2067 msgid "SUN4U-8004-0A.description"
2068 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2069 msgid "SUN4U-8004-0A.response"
2070 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2071 msgid "SUN4U-8004-0A.impact"
2072 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2073 msgid "SUN4U-8004-0A.action"
2074 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2076 # code: SUN4U-8004-1P
2077 # keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo fault.io.xmits
2079 msgid "SUN4U-8004-1P.type"
2081 msgid "SUN4U-8004-1P.severity"
2083 msgid "SUN4U-8004-1P.description"
2084 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2085 msgid "SUN4U-8004-1P.response"
2086 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2087 msgid "SUN4U-8004-1P.impact"
2088 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2089 msgid "SUN4U-8004-1P.action"
2090 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2092 # code: SUN4U-8004-25
2093 # keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2095 msgid "SUN4U-8004-25.type"
2097 msgid "SUN4U-8004-25.severity"
2099 msgid "SUN4U-8004-25.description"
2100 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2101 msgid "SUN4U-8004-25.response"
2102 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2103 msgid "SUN4U-8004-25.impact"
2104 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2105 msgid "SUN4U-8004-25.action"
2106 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2108 # code: SUN4U-8004-3S
2109 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2111 msgid "SUN4U-8004-3S.type"
2113 msgid "SUN4U-8004-3S.severity"
2115 msgid "SUN4U-8004-3S.description"
2116 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2117 msgid "SUN4U-8004-3S.response"
2118 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2119 msgid "SUN4U-8004-3S.impact"
2120 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2121 msgid "SUN4U-8004-3S.action"
2122 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2124 # code: SUN4U-8004-43
2125 # keys: fault.io.datapath fault.io.schizo fault.io.xmits
2127 msgid "SUN4U-8004-43.type"
2129 msgid "SUN4U-8004-43.severity"
2131 msgid "SUN4U-8004-43.description"
2132 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2133 msgid "SUN4U-8004-43.response"
2134 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2135 msgid "SUN4U-8004-43.impact"
2136 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2137 msgid "SUN4U-8004-43.action"
2138 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2140 # code: SUN4U-8004-5Y
2141 # keys: defect.io.pci.driver fault.io.datapath fault.io.schizo fault.io.xmits
2143 msgid "SUN4U-8004-5Y.type"
2145 msgid "SUN4U-8004-5Y.severity"
2147 msgid "SUN4U-8004-5Y.description"
2148 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2149 msgid "SUN4U-8004-5Y.response"
2150 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2151 msgid "SUN4U-8004-5Y.impact"
2152 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2153 msgid "SUN4U-8004-5Y.action"
2154 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2156 # code: SUN4U-8004-6D
2157 # keys: fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits
2159 msgid "SUN4U-8004-6D.type"
2161 msgid "SUN4U-8004-6D.severity"
2163 msgid "SUN4U-8004-6D.description"
2164 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2165 msgid "SUN4U-8004-6D.response"
2166 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2167 msgid "SUN4U-8004-6D.impact"
2168 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2169 msgid "SUN4U-8004-6D.action"
2170 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2172 # code: SUN4U-8004-7H
2173 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits
2175 msgid "SUN4U-8004-7H.type"
2177 msgid "SUN4U-8004-7H.severity"
2179 msgid "SUN4U-8004-7H.description"
2180 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2181 msgid "SUN4U-8004-7H.response"
2182 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2183 msgid "SUN4U-8004-7H.impact"
2184 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2185 msgid "SUN4U-8004-7H.action"
2186 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2188 # code: SUN4U-8004-8R
2189 # keys: fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits
2191 msgid "SUN4U-8004-8R.type"
2193 msgid "SUN4U-8004-8R.severity"
2195 msgid "SUN4U-8004-8R.description"
2196 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2197 msgid "SUN4U-8004-8R.response"
2198 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2199 msgid "SUN4U-8004-8R.impact"
2200 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2201 msgid "SUN4U-8004-8R.action"
2202 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2204 # code: SUN4U-8004-94
2205 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits
2207 msgid "SUN4U-8004-94.type"
2209 msgid "SUN4U-8004-94.severity"
2211 msgid "SUN4U-8004-94.description"
2212 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2213 msgid "SUN4U-8004-94.response"
2214 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2215 msgid "SUN4U-8004-94.impact"
2216 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2217 msgid "SUN4U-8004-94.action"
2218 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2220 # code: SUN4U-8004-AQ
2221 # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2223 msgid "SUN4U-8004-AQ.type"
2225 msgid "SUN4U-8004-AQ.severity"
2227 msgid "SUN4U-8004-AQ.description"
2228 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2229 msgid "SUN4U-8004-AQ.response"
2230 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2231 msgid "SUN4U-8004-AQ.impact"
2232 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2233 msgid "SUN4U-8004-AQ.action"
2234 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2236 # code: SUN4U-8004-CC
2237 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2239 msgid "SUN4U-8004-CC.type"
2241 msgid "SUN4U-8004-CC.severity"
2243 msgid "SUN4U-8004-CC.description"
2244 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2245 msgid "SUN4U-8004-CC.response"
2246 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2247 msgid "SUN4U-8004-CC.impact"
2248 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2249 msgid "SUN4U-8004-CC.action"
2250 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2252 # code: SUN4U-8004-DJ
2253 # keys: fault.io.hbus fault.io.schizo fault.io.xmits
2255 msgid "SUN4U-8004-DJ.type"
2257 msgid "SUN4U-8004-DJ.severity"
2259 msgid "SUN4U-8004-DJ.description"
2260 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2261 msgid "SUN4U-8004-DJ.response"
2262 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2263 msgid "SUN4U-8004-DJ.impact"
2264 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2265 msgid "SUN4U-8004-DJ.action"
2266 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2268 # code: SUN4U-8004-EE
2269 # keys: defect.io.pci.driver fault.io.hbus fault.io.schizo fault.io.xmits
2271 msgid "SUN4U-8004-EE.type"
2273 msgid "SUN4U-8004-EE.severity"
2275 msgid "SUN4U-8004-EE.description"
2276 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2277 msgid "SUN4U-8004-EE.response"
2278 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2279 msgid "SUN4U-8004-EE.impact"
2280 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2281 msgid "SUN4U-8004-EE.action"
2282 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2284 # code: SUN4U-8004-FX
2285 # keys: fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2287 msgid "SUN4U-8004-FX.type"
2289 msgid "SUN4U-8004-FX.severity"
2291 msgid "SUN4U-8004-FX.description"
2292 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2293 msgid "SUN4U-8004-FX.response"
2294 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2295 msgid "SUN4U-8004-FX.impact"
2296 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2297 msgid "SUN4U-8004-FX.action"
2298 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2300 # code: SUN4U-8004-G2
2301 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2303 msgid "SUN4U-8004-G2.type"
2305 msgid "SUN4U-8004-G2.severity"
2307 msgid "SUN4U-8004-G2.description"
2308 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2309 msgid "SUN4U-8004-G2.response"
2310 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2311 msgid "SUN4U-8004-G2.impact"
2312 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2313 msgid "SUN4U-8004-G2.action"
2314 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2316 # code: SUN4U-8004-HS
2317 # keys: fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2319 msgid "SUN4U-8004-HS.type"
2321 msgid "SUN4U-8004-HS.severity"
2323 msgid "SUN4U-8004-HS.description"
2324 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2325 msgid "SUN4U-8004-HS.response"
2326 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2327 msgid "SUN4U-8004-HS.impact"
2328 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2329 msgid "SUN4U-8004-HS.action"
2330 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2332 # code: SUN4U-8004-J5
2333 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2335 msgid "SUN4U-8004-J5.type"
2337 msgid "SUN4U-8004-J5.severity"
2339 msgid "SUN4U-8004-J5.description"
2340 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2341 msgid "SUN4U-8004-J5.response"
2342 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2343 msgid "SUN4U-8004-J5.impact"
2344 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2345 msgid "SUN4U-8004-J5.action"
2346 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2348 # code: SUN4U-8004-KP
2349 # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2351 msgid "SUN4U-8004-KP.type"
2353 msgid "SUN4U-8004-KP.severity"
2355 msgid "SUN4U-8004-KP.description"
2356 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2357 msgid "SUN4U-8004-KP.response"
2358 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2359 msgid "SUN4U-8004-KP.impact"
2360 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2361 msgid "SUN4U-8004-KP.action"
2362 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2364 # code: SUN4U-8004-LA
2365 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2367 msgid "SUN4U-8004-LA.type"
2369 msgid "SUN4U-8004-LA.severity"
2371 msgid "SUN4U-8004-LA.description"
2372 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2373 msgid "SUN4U-8004-LA.response"
2374 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2375 msgid "SUN4U-8004-LA.impact"
2376 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2377 msgid "SUN4U-8004-LA.action"
2378 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2380 # code: SUN4U-8004-MH
2381 # keys: fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits
2383 msgid "SUN4U-8004-MH.type"
2385 msgid "SUN4U-8004-MH.severity"
2387 msgid "SUN4U-8004-MH.description"
2388 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2389 msgid "SUN4U-8004-MH.response"
2390 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2391 msgid "SUN4U-8004-MH.impact"
2392 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2393 msgid "SUN4U-8004-MH.action"
2394 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2396 # code: SUN4U-8004-ND
2397 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits
2399 msgid "SUN4U-8004-ND.type"
2401 msgid "SUN4U-8004-ND.severity"
2403 msgid "SUN4U-8004-ND.description"
2404 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2405 msgid "SUN4U-8004-ND.response"
2406 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2407 msgid "SUN4U-8004-ND.impact"
2408 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2409 msgid "SUN4U-8004-ND.action"
2410 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2412 # code: SUN4U-8004-PY
2413 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2415 msgid "SUN4U-8004-PY.type"
2417 msgid "SUN4U-8004-PY.severity"
2419 msgid "SUN4U-8004-PY.description"
2420 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2421 msgid "SUN4U-8004-PY.response"
2422 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2423 msgid "SUN4U-8004-PY.impact"
2424 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2425 msgid "SUN4U-8004-PY.action"
2426 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2428 # code: SUN4U-8004-Q3
2429 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2431 msgid "SUN4U-8004-Q3.type"
2433 msgid "SUN4U-8004-Q3.severity"
2435 msgid "SUN4U-8004-Q3.description"
2436 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2437 msgid "SUN4U-8004-Q3.response"
2438 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2439 msgid "SUN4U-8004-Q3.impact"
2440 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2441 msgid "SUN4U-8004-Q3.action"
2442 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2444 # code: SUN4U-8004-RC
2445 # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2447 msgid "SUN4U-8004-RC.type"
2449 msgid "SUN4U-8004-RC.severity"
2451 msgid "SUN4U-8004-RC.description"
2452 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2453 msgid "SUN4U-8004-RC.response"
2454 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2455 msgid "SUN4U-8004-RC.impact"
2456 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2457 msgid "SUN4U-8004-RC.action"
2458 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2460 # code: SUN4U-8004-SQ
2461 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2463 msgid "SUN4U-8004-SQ.type"
2465 msgid "SUN4U-8004-SQ.severity"
2467 msgid "SUN4U-8004-SQ.description"
2468 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2469 msgid "SUN4U-8004-SQ.response"
2470 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2471 msgid "SUN4U-8004-SQ.impact"
2472 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2473 msgid "SUN4U-8004-SQ.action"
2474 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2476 # code: SUN4U-8004-T4
2477 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2479 msgid "SUN4U-8004-T4.type"
2481 msgid "SUN4U-8004-T4.severity"
2483 msgid "SUN4U-8004-T4.description"
2484 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2485 msgid "SUN4U-8004-T4.response"
2486 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2487 msgid "SUN4U-8004-T4.impact"
2488 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2489 msgid "SUN4U-8004-T4.action"
2490 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2492 # code: SUN4U-8004-UR
2493 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2495 msgid "SUN4U-8004-UR.type"
2497 msgid "SUN4U-8004-UR.severity"
2499 msgid "SUN4U-8004-UR.description"
2500 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2501 msgid "SUN4U-8004-UR.response"
2502 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2503 msgid "SUN4U-8004-UR.impact"
2504 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2505 msgid "SUN4U-8004-UR.action"
2506 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2508 # code: SUN4U-8004-V2
2509 # keys: fault.io.psycho
2511 msgid "SUN4U-8004-V2.type"
2513 msgid "SUN4U-8004-V2.severity"
2515 msgid "SUN4U-8004-V2.description"
2516 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2517 msgid "SUN4U-8004-V2.response"
2518 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2519 msgid "SUN4U-8004-V2.impact"
2520 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2521 msgid "SUN4U-8004-V2.action"
2522 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2524 # code: SUN4U-8004-WX
2525 # keys: defect.io.pci.driver fault.io.psycho
2527 msgid "SUN4U-8004-WX.type"
2529 msgid "SUN4U-8004-WX.severity"
2531 msgid "SUN4U-8004-WX.description"
2532 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2533 msgid "SUN4U-8004-WX.response"
2534 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2535 msgid "SUN4U-8004-WX.impact"
2536 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2537 msgid "SUN4U-8004-WX.action"
2538 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2540 # code: SUN4U-8004-XE
2541 # keys: fault.io.datapath fault.io.psycho
2543 msgid "SUN4U-8004-XE.type"
2545 msgid "SUN4U-8004-XE.severity"
2547 msgid "SUN4U-8004-XE.description"
2548 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2549 msgid "SUN4U-8004-XE.response"
2550 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2551 msgid "SUN4U-8004-XE.impact"
2552 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2553 msgid "SUN4U-8004-XE.action"
2554 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2556 # code: SUN4U-8004-YJ
2557 # keys: defect.io.pci.driver fault.io.datapath fault.io.psycho
2559 msgid "SUN4U-8004-YJ.type"
2561 msgid "SUN4U-8004-YJ.severity"
2563 msgid "SUN4U-8004-YJ.description"
2564 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2565 msgid "SUN4U-8004-YJ.response"
2566 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2567 msgid "SUN4U-8004-YJ.impact"
2568 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2569 msgid "SUN4U-8004-YJ.action"
2570 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2572 # code: SUN4U-8005-0E
2573 # keys: fault.io.hbus fault.io.psycho
2575 msgid "SUN4U-8005-0E.type"
2577 msgid "SUN4U-8005-0E.severity"
2579 msgid "SUN4U-8005-0E.description"
2580 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2581 msgid "SUN4U-8005-0E.response"
2582 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2583 msgid "SUN4U-8005-0E.impact"
2584 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2585 msgid "SUN4U-8005-0E.action"
2586 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2588 # code: SUN4U-8005-1J
2589 # keys: defect.io.pci.driver fault.io.hbus fault.io.psycho
2591 msgid "SUN4U-8005-1J.type"
2593 msgid "SUN4U-8005-1J.severity"
2595 msgid "SUN4U-8005-1J.description"
2596 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2597 msgid "SUN4U-8005-1J.response"
2598 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2599 msgid "SUN4U-8005-1J.impact"
2600 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2601 msgid "SUN4U-8005-1J.action"
2602 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2604 # code: SUN4U-8005-22
2605 # keys: fault.io.datapath fault.io.hbus fault.io.psycho
2607 msgid "SUN4U-8005-22.type"
2609 msgid "SUN4U-8005-22.severity"
2611 msgid "SUN4U-8005-22.description"
2612 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2613 msgid "SUN4U-8005-22.response"
2614 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2615 msgid "SUN4U-8005-22.impact"
2616 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2617 msgid "SUN4U-8005-22.action"
2618 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2620 # code: SUN4U-8005-3X
2621 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.psycho
2623 msgid "SUN4U-8005-3X.type"
2625 msgid "SUN4U-8005-3X.severity"
2627 msgid "SUN4U-8005-3X.description"
2628 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2629 msgid "SUN4U-8005-3X.response"
2630 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2631 msgid "SUN4U-8005-3X.impact"
2632 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2633 msgid "SUN4U-8005-3X.action"
2634 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2636 # code: SUN4U-8005-44
2637 # keys: fault.io.pci.bus fault.io.psycho
2639 msgid "SUN4U-8005-44.type"
2641 msgid "SUN4U-8005-44.severity"
2643 msgid "SUN4U-8005-44.description"
2644 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2645 msgid "SUN4U-8005-44.response"
2646 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2647 msgid "SUN4U-8005-44.impact"
2648 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2649 msgid "SUN4U-8005-44.action"
2650 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2652 # code: SUN4U-8005-5R
2653 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.psycho
2655 msgid "SUN4U-8005-5R.type"
2657 msgid "SUN4U-8005-5R.severity"
2659 msgid "SUN4U-8005-5R.description"
2660 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2661 msgid "SUN4U-8005-5R.response"
2662 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2663 msgid "SUN4U-8005-5R.impact"
2664 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2665 msgid "SUN4U-8005-5R.action"
2666 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2668 # code: SUN4U-8005-6C
2669 # keys: fault.io.datapath fault.io.pci.bus fault.io.psycho
2671 msgid "SUN4U-8005-6C.type"
2673 msgid "SUN4U-8005-6C.severity"
2675 msgid "SUN4U-8005-6C.description"
2676 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2677 msgid "SUN4U-8005-6C.response"
2678 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2679 msgid "SUN4U-8005-6C.impact"
2680 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2681 msgid "SUN4U-8005-6C.action"
2682 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2684 # code: SUN4U-8005-7Q
2685 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.psycho
2687 msgid "SUN4U-8005-7Q.type"
2689 msgid "SUN4U-8005-7Q.severity"
2691 msgid "SUN4U-8005-7Q.description"
2692 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2693 msgid "SUN4U-8005-7Q.response"
2694 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2695 msgid "SUN4U-8005-7Q.impact"
2696 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2697 msgid "SUN4U-8005-7Q.action"
2698 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2700 # code: SUN4U-8005-8Y
2701 # keys: fault.io.hbus fault.io.pci.bus fault.io.psycho
2703 msgid "SUN4U-8005-8Y.type"
2705 msgid "SUN4U-8005-8Y.severity"
2707 msgid "SUN4U-8005-8Y.description"
2708 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2709 msgid "SUN4U-8005-8Y.response"
2710 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2711 msgid "SUN4U-8005-8Y.impact"
2712 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2713 msgid "SUN4U-8005-8Y.action"
2714 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2716 # code: SUN4U-8005-93
2717 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.psycho
2719 msgid "SUN4U-8005-93.type"
2721 msgid "SUN4U-8005-93.severity"
2723 msgid "SUN4U-8005-93.description"
2724 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2725 msgid "SUN4U-8005-93.response"
2726 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2727 msgid "SUN4U-8005-93.impact"
2728 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2729 msgid "SUN4U-8005-93.action"
2730 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2732 # code: SUN4U-8005-AH
2733 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho
2735 msgid "SUN4U-8005-AH.type"
2737 msgid "SUN4U-8005-AH.severity"
2739 msgid "SUN4U-8005-AH.description"
2740 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2741 msgid "SUN4U-8005-AH.response"
2742 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2743 msgid "SUN4U-8005-AH.impact"
2744 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2745 msgid "SUN4U-8005-AH.action"
2746 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2748 # code: SUN4U-8005-CD
2749 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho
2751 msgid "SUN4U-8005-CD.type"
2753 msgid "SUN4U-8005-CD.severity"
2755 msgid "SUN4U-8005-CD.description"
2756 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2757 msgid "SUN4U-8005-CD.response"
2758 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2759 msgid "SUN4U-8005-CD.impact"
2760 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2761 msgid "SUN4U-8005-CD.action"
2762 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2764 # code: SUN4U-8005-DP
2765 # keys: fault.io.pci.device fault.io.psycho
2767 msgid "SUN4U-8005-DP.type"
2769 msgid "SUN4U-8005-DP.severity"
2771 msgid "SUN4U-8005-DP.description"
2772 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2773 msgid "SUN4U-8005-DP.response"
2774 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2775 msgid "SUN4U-8005-DP.impact"
2776 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2777 msgid "SUN4U-8005-DP.action"
2778 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2780 # code: SUN4U-8005-EA
2781 # keys: defect.io.pci.driver fault.io.pci.device fault.io.psycho
2783 msgid "SUN4U-8005-EA.type"
2785 msgid "SUN4U-8005-EA.severity"
2787 msgid "SUN4U-8005-EA.description"
2788 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2789 msgid "SUN4U-8005-EA.response"
2790 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2791 msgid "SUN4U-8005-EA.impact"
2792 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2793 msgid "SUN4U-8005-EA.action"
2794 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2796 # code: SUN4U-8005-FS
2797 # keys: fault.io.datapath fault.io.pci.device fault.io.psycho
2799 msgid "SUN4U-8005-FS.type"
2801 msgid "SUN4U-8005-FS.severity"
2803 msgid "SUN4U-8005-FS.description"
2804 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2805 msgid "SUN4U-8005-FS.response"
2806 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2807 msgid "SUN4U-8005-FS.impact"
2808 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2809 msgid "SUN4U-8005-FS.action"
2810 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2812 # code: SUN4U-8005-G5
2813 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.psycho
2815 msgid "SUN4U-8005-G5.type"
2817 msgid "SUN4U-8005-G5.severity"
2819 msgid "SUN4U-8005-G5.description"
2820 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2821 msgid "SUN4U-8005-G5.response"
2822 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2823 msgid "SUN4U-8005-G5.impact"
2824 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2825 msgid "SUN4U-8005-G5.action"
2826 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2828 # code: SUN4U-8005-HX
2829 # keys: fault.io.hbus fault.io.pci.device fault.io.psycho
2831 msgid "SUN4U-8005-HX.type"
2833 msgid "SUN4U-8005-HX.severity"
2835 msgid "SUN4U-8005-HX.description"
2836 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2837 msgid "SUN4U-8005-HX.response"
2838 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2839 msgid "SUN4U-8005-HX.impact"
2840 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2841 msgid "SUN4U-8005-HX.action"
2842 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2844 # code: SUN4U-8005-J2
2845 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.psycho
2847 msgid "SUN4U-8005-J2.type"
2849 msgid "SUN4U-8005-J2.severity"
2851 msgid "SUN4U-8005-J2.description"
2852 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2853 msgid "SUN4U-8005-J2.response"
2854 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2855 msgid "SUN4U-8005-J2.impact"
2856 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2857 msgid "SUN4U-8005-J2.action"
2858 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2860 # code: SUN4U-8005-KJ
2861 # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho
2863 msgid "SUN4U-8005-KJ.type"
2865 msgid "SUN4U-8005-KJ.severity"
2867 msgid "SUN4U-8005-KJ.description"
2868 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2869 msgid "SUN4U-8005-KJ.response"
2870 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2871 msgid "SUN4U-8005-KJ.impact"
2872 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2873 msgid "SUN4U-8005-KJ.action"
2874 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2876 # code: SUN4U-8005-LE
2877 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho
2879 msgid "SUN4U-8005-LE.type"
2881 msgid "SUN4U-8005-LE.severity"
2883 msgid "SUN4U-8005-LE.description"
2884 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2885 msgid "SUN4U-8005-LE.response"
2886 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2887 msgid "SUN4U-8005-LE.impact"
2888 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2889 msgid "SUN4U-8005-LE.action"
2890 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2892 # code: SUN4U-8005-MQ
2893 # keys: fault.io.pci.bus fault.io.pci.device fault.io.psycho
2895 msgid "SUN4U-8005-MQ.type"
2897 msgid "SUN4U-8005-MQ.severity"
2899 msgid "SUN4U-8005-MQ.description"
2900 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2901 msgid "SUN4U-8005-MQ.response"
2902 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2903 msgid "SUN4U-8005-MQ.impact"
2904 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2905 msgid "SUN4U-8005-MQ.action"
2906 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2908 # code: SUN4U-8005-NC
2909 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.psycho
2911 msgid "SUN4U-8005-NC.type"
2913 msgid "SUN4U-8005-NC.severity"
2915 msgid "SUN4U-8005-NC.description"
2916 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2917 msgid "SUN4U-8005-NC.response"
2918 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2919 msgid "SUN4U-8005-NC.impact"
2920 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2921 msgid "SUN4U-8005-NC.action"
2922 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2924 # code: SUN4U-8005-PR
2925 # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho
2927 msgid "SUN4U-8005-PR.type"
2929 msgid "SUN4U-8005-PR.severity"
2931 msgid "SUN4U-8005-PR.description"
2932 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2933 msgid "SUN4U-8005-PR.response"
2934 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2935 msgid "SUN4U-8005-PR.impact"
2936 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2937 msgid "SUN4U-8005-PR.action"
2938 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2940 # code: SUN4U-8005-Q4
2941 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho
2943 msgid "SUN4U-8005-Q4.type"
2945 msgid "SUN4U-8005-Q4.severity"
2947 msgid "SUN4U-8005-Q4.description"
2948 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2949 msgid "SUN4U-8005-Q4.response"
2950 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2951 msgid "SUN4U-8005-Q4.impact"
2952 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2953 msgid "SUN4U-8005-Q4.action"
2954 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2956 # code: SUN4U-8005-RD
2957 # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
2959 msgid "SUN4U-8005-RD.type"
2961 msgid "SUN4U-8005-RD.severity"
2963 msgid "SUN4U-8005-RD.description"
2964 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2965 msgid "SUN4U-8005-RD.response"
2966 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2967 msgid "SUN4U-8005-RD.impact"
2968 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2969 msgid "SUN4U-8005-RD.action"
2970 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
2972 # code: SUN4U-8005-SH
2973 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
2975 msgid "SUN4U-8005-SH.type"
2977 msgid "SUN4U-8005-SH.severity"
2979 msgid "SUN4U-8005-SH.description"
2980 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
2981 msgid "SUN4U-8005-SH.response"
2982 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2983 msgid "SUN4U-8005-SH.impact"
2984 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2985 msgid "SUN4U-8005-SH.action"
2986 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
2988 # code: SUN4U-8005-T3
2989 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
2991 msgid "SUN4U-8005-T3.type"
2993 msgid "SUN4U-8005-T3.severity"
2995 msgid "SUN4U-8005-T3.description"
2996 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
2997 msgid "SUN4U-8005-T3.response"
2998 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2999 msgid "SUN4U-8005-T3.impact"
3000 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3001 msgid "SUN4U-8005-T3.action"
3002 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3004 # code: SUN4U-8005-UY
3005 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
3007 msgid "SUN4U-8005-UY.type"
3009 msgid "SUN4U-8005-UY.severity"
3011 msgid "SUN4U-8005-UY.description"
3012 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3013 msgid "SUN4U-8005-UY.response"
3014 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3015 msgid "SUN4U-8005-UY.impact"
3016 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3017 msgid "SUN4U-8005-UY.action"
3018 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3020 # code: SUN4U-8005-V5
3021 # keys: fault.io.tomatillo
3023 msgid "SUN4U-8005-V5.type"
3025 msgid "SUN4U-8005-V5.severity"
3027 msgid "SUN4U-8005-V5.description"
3028 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3029 msgid "SUN4U-8005-V5.response"
3030 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3031 msgid "SUN4U-8005-V5.impact"
3032 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3033 msgid "SUN4U-8005-V5.action"
3034 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3036 # code: SUN4U-8005-WS
3037 # keys: defect.io.pci.driver fault.io.tomatillo
3039 msgid "SUN4U-8005-WS.type"
3041 msgid "SUN4U-8005-WS.severity"
3043 msgid "SUN4U-8005-WS.description"
3044 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3045 msgid "SUN4U-8005-WS.response"
3046 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3047 msgid "SUN4U-8005-WS.impact"
3048 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3049 msgid "SUN4U-8005-WS.action"
3050 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3052 # code: SUN4U-8005-XA
3053 # keys: fault.io.datapath fault.io.tomatillo
3055 msgid "SUN4U-8005-XA.type"
3057 msgid "SUN4U-8005-XA.severity"
3059 msgid "SUN4U-8005-XA.description"
3060 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3061 msgid "SUN4U-8005-XA.response"
3062 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3063 msgid "SUN4U-8005-XA.impact"
3064 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3065 msgid "SUN4U-8005-XA.action"
3066 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3068 # code: SUN4U-8005-YP
3069 # keys: defect.io.pci.driver fault.io.datapath fault.io.tomatillo
3071 msgid "SUN4U-8005-YP.type"
3073 msgid "SUN4U-8005-YP.severity"
3075 msgid "SUN4U-8005-YP.description"
3076 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3077 msgid "SUN4U-8005-YP.response"
3078 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3079 msgid "SUN4U-8005-YP.impact"
3080 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3081 msgid "SUN4U-8005-YP.action"
3082 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3084 # code: SUN4U-8006-04
3085 # keys: fault.io.hbus fault.io.tomatillo
3087 msgid "SUN4U-8006-04.type"
3089 msgid "SUN4U-8006-04.severity"
3091 msgid "SUN4U-8006-04.description"
3092 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3093 msgid "SUN4U-8006-04.response"
3094 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3095 msgid "SUN4U-8006-04.impact"
3096 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3097 msgid "SUN4U-8006-04.action"
3098 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3100 # code: SUN4U-8006-1R
3101 # keys: defect.io.pci.driver fault.io.hbus fault.io.tomatillo
3103 msgid "SUN4U-8006-1R.type"
3105 msgid "SUN4U-8006-1R.severity"
3107 msgid "SUN4U-8006-1R.description"
3108 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3109 msgid "SUN4U-8006-1R.response"
3110 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3111 msgid "SUN4U-8006-1R.impact"
3112 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3113 msgid "SUN4U-8006-1R.action"
3114 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3116 # code: SUN4U-8006-2C
3117 # keys: fault.io.datapath fault.io.hbus fault.io.tomatillo
3119 msgid "SUN4U-8006-2C.type"
3121 msgid "SUN4U-8006-2C.severity"
3123 msgid "SUN4U-8006-2C.description"
3124 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3125 msgid "SUN4U-8006-2C.response"
3126 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3127 msgid "SUN4U-8006-2C.impact"
3128 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3129 msgid "SUN4U-8006-2C.action"
3130 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3132 # code: SUN4U-8006-3Q
3133 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.tomatillo
3135 msgid "SUN4U-8006-3Q.type"
3137 msgid "SUN4U-8006-3Q.severity"
3139 msgid "SUN4U-8006-3Q.description"
3140 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3141 msgid "SUN4U-8006-3Q.response"
3142 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3143 msgid "SUN4U-8006-3Q.impact"
3144 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3145 msgid "SUN4U-8006-3Q.action"
3146 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3148 # code: SUN4U-8006-4E
3149 # keys: fault.io.pci.bus fault.io.tomatillo
3151 msgid "SUN4U-8006-4E.type"
3153 msgid "SUN4U-8006-4E.severity"
3155 msgid "SUN4U-8006-4E.description"
3156 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3157 msgid "SUN4U-8006-4E.response"
3158 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3159 msgid "SUN4U-8006-4E.impact"
3160 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3161 msgid "SUN4U-8006-4E.action"
3162 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3164 # code: SUN4U-8006-5J
3165 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.tomatillo
3167 msgid "SUN4U-8006-5J.type"
3169 msgid "SUN4U-8006-5J.severity"
3171 msgid "SUN4U-8006-5J.description"
3172 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3173 msgid "SUN4U-8006-5J.response"
3174 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3175 msgid "SUN4U-8006-5J.impact"
3176 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3177 msgid "SUN4U-8006-5J.action"
3178 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3180 # code: SUN4U-8006-62
3181 # keys: fault.io.datapath fault.io.pci.bus fault.io.tomatillo
3183 msgid "SUN4U-8006-62.type"
3185 msgid "SUN4U-8006-62.severity"
3187 msgid "SUN4U-8006-62.description"
3188 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3189 msgid "SUN4U-8006-62.response"
3190 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3191 msgid "SUN4U-8006-62.impact"
3192 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3193 msgid "SUN4U-8006-62.action"
3194 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3196 # code: SUN4U-8006-7X
3197 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.tomatillo
3199 msgid "SUN4U-8006-7X.type"
3201 msgid "SUN4U-8006-7X.severity"
3203 msgid "SUN4U-8006-7X.description"
3204 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3205 msgid "SUN4U-8006-7X.response"
3206 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3207 msgid "SUN4U-8006-7X.impact"
3208 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3209 msgid "SUN4U-8006-7X.action"
3210 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3212 # code: SUN4U-8006-8P
3213 # keys: fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3215 msgid "SUN4U-8006-8P.type"
3217 msgid "SUN4U-8006-8P.severity"
3219 msgid "SUN4U-8006-8P.description"
3220 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3221 msgid "SUN4U-8006-8P.response"
3222 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3223 msgid "SUN4U-8006-8P.impact"
3224 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3225 msgid "SUN4U-8006-8P.action"
3226 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3228 # code: SUN4U-8006-9A
3229 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3231 msgid "SUN4U-8006-9A.type"
3233 msgid "SUN4U-8006-9A.severity"
3235 msgid "SUN4U-8006-9A.description"
3236 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3237 msgid "SUN4U-8006-9A.response"
3238 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3239 msgid "SUN4U-8006-9A.impact"
3240 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3241 msgid "SUN4U-8006-9A.action"
3242 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3244 # code: SUN4U-8006-AS
3245 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3247 msgid "SUN4U-8006-AS.type"
3249 msgid "SUN4U-8006-AS.severity"
3251 msgid "SUN4U-8006-AS.description"
3252 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3253 msgid "SUN4U-8006-AS.response"
3254 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3255 msgid "SUN4U-8006-AS.impact"
3256 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3257 msgid "SUN4U-8006-AS.action"
3258 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3260 # code: SUN4U-8006-C5
3261 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3263 msgid "SUN4U-8006-C5.type"
3265 msgid "SUN4U-8006-C5.severity"
3267 msgid "SUN4U-8006-C5.description"
3268 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3269 msgid "SUN4U-8006-C5.response"
3270 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3271 msgid "SUN4U-8006-C5.impact"
3272 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3273 msgid "SUN4U-8006-C5.action"
3274 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3276 # code: SUN4U-8006-DY
3277 # keys: fault.io.pci.device fault.io.tomatillo
3279 msgid "SUN4U-8006-DY.type"
3281 msgid "SUN4U-8006-DY.severity"
3283 msgid "SUN4U-8006-DY.description"
3284 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3285 msgid "SUN4U-8006-DY.response"
3286 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3287 msgid "SUN4U-8006-DY.impact"
3288 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3289 msgid "SUN4U-8006-DY.action"
3290 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3292 # code: SUN4U-8006-E3
3293 # keys: defect.io.pci.driver fault.io.pci.device fault.io.tomatillo
3295 msgid "SUN4U-8006-E3.type"
3297 msgid "SUN4U-8006-E3.severity"
3299 msgid "SUN4U-8006-E3.description"
3300 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3301 msgid "SUN4U-8006-E3.response"
3302 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3303 msgid "SUN4U-8006-E3.impact"
3304 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3305 msgid "SUN4U-8006-E3.action"
3306 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3308 # code: SUN4U-8006-FH
3309 # keys: fault.io.datapath fault.io.pci.device fault.io.tomatillo
3311 msgid "SUN4U-8006-FH.type"
3313 msgid "SUN4U-8006-FH.severity"
3315 msgid "SUN4U-8006-FH.description"
3316 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3317 msgid "SUN4U-8006-FH.response"
3318 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3319 msgid "SUN4U-8006-FH.impact"
3320 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3321 msgid "SUN4U-8006-FH.action"
3322 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3324 # code: SUN4U-8006-GD
3325 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.tomatillo
3327 msgid "SUN4U-8006-GD.type"
3329 msgid "SUN4U-8006-GD.severity"
3331 msgid "SUN4U-8006-GD.description"
3332 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3333 msgid "SUN4U-8006-GD.response"
3334 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3335 msgid "SUN4U-8006-GD.impact"
3336 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3337 msgid "SUN4U-8006-GD.action"
3338 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3340 # code: SUN4U-8006-HQ
3341 # keys: fault.io.hbus fault.io.pci.device fault.io.tomatillo
3343 msgid "SUN4U-8006-HQ.type"
3345 msgid "SUN4U-8006-HQ.severity"
3347 msgid "SUN4U-8006-HQ.description"
3348 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3349 msgid "SUN4U-8006-HQ.response"
3350 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3351 msgid "SUN4U-8006-HQ.impact"
3352 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3353 msgid "SUN4U-8006-HQ.action"
3354 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3356 # code: SUN4U-8006-JC
3357 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.tomatillo
3359 msgid "SUN4U-8006-JC.type"
3361 msgid "SUN4U-8006-JC.severity"
3363 msgid "SUN4U-8006-JC.description"
3364 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3365 msgid "SUN4U-8006-JC.response"
3366 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3367 msgid "SUN4U-8006-JC.impact"
3368 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3369 msgid "SUN4U-8006-JC.action"
3370 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3372 # code: SUN4U-8006-KR
3373 # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo
3375 msgid "SUN4U-8006-KR.type"
3377 msgid "SUN4U-8006-KR.severity"
3379 msgid "SUN4U-8006-KR.description"
3380 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3381 msgid "SUN4U-8006-KR.response"
3382 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3383 msgid "SUN4U-8006-KR.impact"
3384 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3385 msgid "SUN4U-8006-KR.action"
3386 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3388 # code: SUN4U-8006-L4
3389 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo
3391 msgid "SUN4U-8006-L4.type"
3393 msgid "SUN4U-8006-L4.severity"
3395 msgid "SUN4U-8006-L4.description"
3396 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3397 msgid "SUN4U-8006-L4.response"
3398 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3399 msgid "SUN4U-8006-L4.impact"
3400 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3401 msgid "SUN4U-8006-L4.action"
3402 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3404 # code: SUN4U-8006-MX
3405 # keys: fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3407 msgid "SUN4U-8006-MX.type"
3409 msgid "SUN4U-8006-MX.severity"
3411 msgid "SUN4U-8006-MX.description"
3412 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3413 msgid "SUN4U-8006-MX.response"
3414 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3415 msgid "SUN4U-8006-MX.impact"
3416 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3417 msgid "SUN4U-8006-MX.action"
3418 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3420 # code: SUN4U-8006-N2
3421 # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3423 msgid "SUN4U-8006-N2.type"
3425 msgid "SUN4U-8006-N2.severity"
3427 msgid "SUN4U-8006-N2.description"
3428 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3429 msgid "SUN4U-8006-N2.response"
3430 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3431 msgid "SUN4U-8006-N2.impact"
3432 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3433 msgid "SUN4U-8006-N2.action"
3434 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3436 # code: SUN4U-8006-PJ
3437 # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3439 msgid "SUN4U-8006-PJ.type"
3441 msgid "SUN4U-8006-PJ.severity"
3443 msgid "SUN4U-8006-PJ.description"
3444 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3445 msgid "SUN4U-8006-PJ.response"
3446 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3447 msgid "SUN4U-8006-PJ.impact"
3448 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3449 msgid "SUN4U-8006-PJ.action"
3450 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3452 # code: SUN4U-8006-QE
3453 # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3455 msgid "SUN4U-8006-QE.type"
3457 msgid "SUN4U-8006-QE.severity"
3459 msgid "SUN4U-8006-QE.description"
3460 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3461 msgid "SUN4U-8006-QE.response"
3462 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3463 msgid "SUN4U-8006-QE.impact"
3464 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3465 msgid "SUN4U-8006-QE.action"
3466 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3468 # code: SUN4U-8006-R5
3469 # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3471 msgid "SUN4U-8006-R5.type"
3473 msgid "SUN4U-8006-R5.severity"
3475 msgid "SUN4U-8006-R5.description"
3476 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3477 msgid "SUN4U-8006-R5.response"
3478 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3479 msgid "SUN4U-8006-R5.impact"
3480 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3481 msgid "SUN4U-8006-R5.action"
3482 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3484 # code: SUN4U-8006-SS
3485 # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3487 msgid "SUN4U-8006-SS.type"
3489 msgid "SUN4U-8006-SS.severity"
3491 msgid "SUN4U-8006-SS.description"
3492 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3493 msgid "SUN4U-8006-SS.response"
3494 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3495 msgid "SUN4U-8006-SS.impact"
3496 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3497 msgid "SUN4U-8006-SS.action"
3498 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3500 # code: SUN4U-8006-TA
3501 # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3503 msgid "SUN4U-8006-TA.type"
3505 msgid "SUN4U-8006-TA.severity"
3507 msgid "SUN4U-8006-TA.description"
3508 msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information."
3509 msgid "SUN4U-8006-TA.response"
3510 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3511 msgid "SUN4U-8006-TA.impact"
3512 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3513 msgid "SUN4U-8006-TA.action"
3514 msgstr "\nSchedule a repair procedure to replace the affected device. Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
3516 # code: SUN4U-8006-UP
3517 # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3519 msgid "SUN4U-8006-UP.type"
3521 msgid "SUN4U-8006-UP.severity"
3523 msgid "SUN4U-8006-UP.description"
3524 msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n Refer to %s for more information."
3525 msgid "SUN4U-8006-UP.response"
3526 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3527 msgid "SUN4U-8006-UP.impact"
3528 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3529 msgid "SUN4U-8006-UP.action"
3530 msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s). Schedule a repair of the most likely suspect \nlisted in the output. If the most likely suspect is a package then run \npkgchk on the package(s).\n"
3532 # code: SUN4U-8006-VD
3533 # keys: fault.cpu.ultraSPARC-IIIiplus.dcache
3535 msgid "SUN4U-8006-VD.type"
3537 msgid "SUN4U-8006-VD.severity"
3539 msgid "SUN4U-8006-VD.description"
3540 msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information."
3541 msgid "SUN4U-8006-VD.response"
3542 msgstr "The fault manager will attempt to remove the affected CPU from service."
3543 msgid "SUN4U-8006-VD.impact"
3544 msgstr "System performance may be affected."
3545 msgid "SUN4U-8006-VD.action"
3546 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3548 # code: SUN4U-8006-WH
3549 # keys: fault.cpu.ultraSPARC-IIIiplus.icache
3551 msgid "SUN4U-8006-WH.type"
3553 msgid "SUN4U-8006-WH.severity"
3555 msgid "SUN4U-8006-WH.description"
3556 msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information."
3557 msgid "SUN4U-8006-WH.response"
3558 msgstr "The fault manager will attempt to remove the affected CPU from service."
3559 msgid "SUN4U-8006-WH.impact"
3560 msgstr "System performance may be affected."
3561 msgid "SUN4U-8006-WH.action"
3562 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3564 # code: SUN4U-8006-X3
3565 # keys: fault.cpu.ultraSPARC-IIIiplus.l2cachedata
3567 msgid "SUN4U-8006-X3.type"
3569 msgid "SUN4U-8006-X3.severity"
3571 msgid "SUN4U-8006-X3.description"
3572 msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information."
3573 msgid "SUN4U-8006-X3.response"
3574 msgstr "The fault manager will attempt to remove the affected CPU from service."
3575 msgid "SUN4U-8006-X3.impact"
3576 msgstr "System performance may be affected."
3577 msgid "SUN4U-8006-X3.action"
3578 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3580 # code: SUN4U-8006-YY
3581 # keys: fault.cpu.ultraSPARC-IIIiplus.l2cachetag
3583 msgid "SUN4U-8006-YY.type"
3585 msgid "SUN4U-8006-YY.severity"
3587 msgid "SUN4U-8006-YY.description"
3588 msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information."
3589 msgid "SUN4U-8006-YY.response"
3590 msgstr "The fault manager will attempt to remove the affected CPU from service."
3591 msgid "SUN4U-8006-YY.impact"
3592 msgstr "System performance may be affected."
3593 msgid "SUN4U-8006-YY.action"
3594 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3596 # code: SUN4U-8007-03
3597 # keys: fault.cpu.ultraSPARC-IIIiplus.fpu
3599 msgid "SUN4U-8007-03.type"
3601 msgid "SUN4U-8007-03.severity"
3603 msgid "SUN4U-8007-03.description"
3604 msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information."
3605 msgid "SUN4U-8007-03.response"
3606 msgstr "The fault manager will attempt to remove the affected CPU from service."
3607 msgid "SUN4U-8007-03.impact"
3608 msgstr "System performance may be affected."
3609 msgid "SUN4U-8007-03.action"
3610 msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3612 # code: SUN4U-8007-1Y
3613 # keys: fault.asic.cds.dp
3615 msgid "SUN4U-8007-1Y.type"
3617 msgid "SUN4U-8007-1Y.severity"
3619 msgid "SUN4U-8007-1Y.description"
3620 msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information."
3621 msgid "SUN4U-8007-1Y.response"
3622 msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3623 msgid "SUN4U-8007-1Y.impact"
3624 msgstr "System performace may be affected.\n"
3625 msgid "SUN4U-8007-1Y.action"
3626 msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3628 # code: SUN4U-8007-2D
3629 # keys: fault.asic.dx.dp
3631 msgid "SUN4U-8007-2D.type"
3633 msgid "SUN4U-8007-2D.severity"
3635 msgid "SUN4U-8007-2D.description"
3636 msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information."
3637 msgid "SUN4U-8007-2D.response"
3638 msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3639 msgid "SUN4U-8007-2D.impact"
3640 msgstr "System performace may be affected.\n"
3641 msgid "SUN4U-8007-2D.action"
3642 msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3644 # code: SUN4U-8007-3H
3645 # keys: fault.asic.sdi.dp
3647 msgid "SUN4U-8007-3H.type"
3649 msgid "SUN4U-8007-3H.severity"
3651 msgid "SUN4U-8007-3H.description"
3652 msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information."
3653 msgid "SUN4U-8007-3H.response"
3654 msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3655 msgid "SUN4U-8007-3H.impact"
3656 msgstr "System performace may be affected.\n"
3657 msgid "SUN4U-8007-3H.action"
3658 msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3660 # code: SUN4U-8007-4A
3661 # keys: fault.asic.cp.dp
3663 msgid "SUN4U-8007-4A.type"
3665 msgid "SUN4U-8007-4A.severity"
3667 msgid "SUN4U-8007-4A.description"
3668 msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information."
3669 msgid "SUN4U-8007-4A.response"
3670 msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3671 msgid "SUN4U-8007-4A.impact"
3672 msgstr "System performace may be affected.\n"
3673 msgid "SUN4U-8007-4A.action"
3674 msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3676 # code: SUN4U-8007-5P
3677 # keys: fault.asic.rp.dp
3679 msgid "SUN4U-8007-5P.type"
3681 msgid "SUN4U-8007-5P.severity"
3683 msgid "SUN4U-8007-5P.description"
3684 msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information."
3685 msgid "SUN4U-8007-5P.response"
3686 msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3687 msgid "SUN4U-8007-5P.impact"
3688 msgstr "System performace may be affected.\n"
3689 msgid "SUN4U-8007-5P.action"
3690 msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3692 # code: SUN4U-8007-65
3693 # keys: fault.io.oberon
3695 msgid "SUN4U-8007-65.type"
3697 msgid "SUN4U-8007-65.severity"
3699 msgid "SUN4U-8007-65.description"
3700 msgstr "Oberon PCI-Express hostbridge fault\n Refer to %s for more information."
3701 msgid "SUN4U-8007-65.response"
3702 msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3703 msgid "SUN4U-8007-65.impact"
3704 msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3705 msgid "SUN4U-8007-65.action"
3706 msgstr "Ensure that the latest drivers and patches are installed, schedule a repair procedure to replace the affected device if necessary, or contact Sun for support."
3708 # code: SUN4U-8007-7S
3709 # keys: fault.cpu.SPARC64-VI.chip
3711 msgid "SUN4U-8007-7S.type"
3713 msgid "SUN4U-8007-7S.severity"
3715 msgid "SUN4U-8007-7S.description"
3716 msgstr "The number of errors associated with this CHIP has exceeded acceptable levels. Refer to %s for more information."
3717 msgid "SUN4U-8007-7S.response"
3718 msgstr "An attempt will be made to remove the affected CHIP from service."
3719 msgid "SUN4U-8007-7S.impact"
3720 msgstr "The system will not be functioning at the same performance level with the CHIP removal."
3721 msgid "SUN4U-8007-7S.action"
3722 msgstr "Schedule a repair procedure to replace the affected CHIP. Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCHIP."
3724 # code: SUN4U-8007-8J
3725 # keys: fault.cpu.SPARC64-VI.core
3727 msgid "SUN4U-8007-8J.type"
3729 msgid "SUN4U-8007-8J.severity"
3731 msgid "SUN4U-8007-8J.description"
3732 msgstr "The number of errors associated with this CORE has exceeded acceptable levels. Refer to %s for more information."
3733 msgid "SUN4U-8007-8J.response"
3734 msgstr "An attempt will be made to remove the affected CORE from service."
3735 msgid "SUN4U-8007-8J.impact"
3736 msgstr "The system will not be functioning at the same performance level with the CORE removal."
3737 msgid "SUN4U-8007-8J.action"
3738 msgstr "Schedule a repair procedure to replace the affected CORE. Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCORE.\n"
3740 # code: SUN4U-8007-9E
3741 # keys: fault.cpu.SPARC64-VI.strand
3743 msgid "SUN4U-8007-9E.type"
3745 msgid "SUN4U-8007-9E.severity"
3747 msgid "SUN4U-8007-9E.description"
3748 msgstr "The number of errors associated with this STRAND has exceeded acceptable levels. Refer to %s for more information."
3749 msgid "SUN4U-8007-9E.response"
3750 msgstr "An attempt will be made to remove the affected STRAND from service."
3751 msgid "SUN4U-8007-9E.impact"
3752 msgstr "The system will not be functioning at the same performance level with the STRAND removal."
3753 msgid "SUN4U-8007-9E.action"
3754 msgstr "Schedule a repair procedure to replace the affected STRAND. Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nSTRAND.\n"
3756 # code: SUN4U-8007-AX
3757 # keys: fault.io.pci.device-invreq fault.io.tomatillo
3759 msgid "SUN4U-8007-AX.type"
3761 msgid "SUN4U-8007-AX.severity"
3763 msgid "SUN4U-8007-AX.description"
3764 msgstr "Either the transmitting device sent an invalid request or the receiving device failed to respond.\n Refer to %s for more information."
3765 msgid "SUN4U-8007-AX.response"
3766 msgstr "One or more device instances may be disabled\n"
3767 msgid "SUN4U-8007-AX.impact"
3768 msgstr "Loss of services provided by the device instances associated with this fault\n"
3769 msgid "SUN4U-8007-AX.action"
3770 msgstr "Ensure that the latest drivers and patches are installed. If a plug-in card is involved check for badly-seated cards or bent pins. Otherwise schedule a repair procedure to replace the affected device(s). Use fmdump -v -u <EVENT_ID> to identify the devices or contact Sun for support.\n"
3772 # code: SUN4U-8007-C2
3773 # keys: fault.cpu.SPARC64-VII.chip
3775 msgid "SUN4U-8007-C2.type"
3777 msgid "SUN4U-8007-C2.severity"
3779 msgid "SUN4U-8007-C2.description"
3780 msgstr "The number of errors associated with this CHIP has exceeded acceptable levels. Refer to %s for more information."
3781 msgid "SUN4U-8007-C2.response"
3782 msgstr "An attempt will be made to remove the affected CHIP from service."
3783 msgid "SUN4U-8007-C2.impact"
3784 msgstr "The system will not be functioning at the same performance level with the CHIP removal."
3785 msgid "SUN4U-8007-C2.action"
3786 msgstr "Schedule a repair procedure to replace the affected CHIP. Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCHIP."
3788 # code: SUN4U-8007-DR
3789 # keys: fault.cpu.SPARC64-VII.core
3791 msgid "SUN4U-8007-DR.type"
3793 msgid "SUN4U-8007-DR.severity"
3795 msgid "SUN4U-8007-DR.description"
3796 msgstr "The number of errors associated with this CORE has exceeded acceptable levels. Refer to %s for more information."
3797 msgid "SUN4U-8007-DR.response"
3798 msgstr "An attempt will be made to remove the affected CORE from service."
3799 msgid "SUN4U-8007-DR.impact"
3800 msgstr "The system will not be functioning at the same performance level with the CORE removal."
3801 msgid "SUN4U-8007-DR.action"
3802 msgstr "Schedule a repair procedure to replace the affected CORE. Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCORE.\n"
3804 # code: SUN4U-8007-E4
3805 # keys: fault.cpu.SPARC64-VII.strand
3807 msgid "SUN4U-8007-E4.type"
3809 msgid "SUN4U-8007-E4.severity"
3811 msgid "SUN4U-8007-E4.description"
3812 msgstr "The number of errors associated with this STRAND has exceeded acceptable levels. Refer to %s for more information."
3813 msgid "SUN4U-8007-E4.response"
3814 msgstr "An attempt will be made to remove the affected STRAND from service."
3815 msgid "SUN4U-8007-E4.impact"
3816 msgstr "The system will not be functioning at the same performance level with the STRAND removal."
3817 msgid "SUN4U-8007-E4.action"
3818 msgstr "Schedule a repair procedure to replace the affected STRAND. Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nSTRAND.\n"
3820 # code: SUN4U-8007-FQ
3821 # keys: fault.cpu.ultraSPARC-IVplus.l2cachedata-line
3823 msgid "SUN4U-8007-FQ.type"
3825 msgid "SUN4U-8007-FQ.severity"
3827 msgid "SUN4U-8007-FQ.description"
3828 msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information."
3829 msgid "SUN4U-8007-FQ.response"
3830 msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3831 msgid "SUN4U-8007-FQ.impact"
3832 msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3833 msgid "SUN4U-8007-FQ.action"
3834 msgstr "No repair action is recommended at this time.\n"
3836 # code: SUN4U-8007-GC
3837 # keys: fault.cpu.ultraSPARC-IVplus.l3cachedata-line
3839 msgid "SUN4U-8007-GC.type"
3841 msgid "SUN4U-8007-GC.severity"
3843 msgid "SUN4U-8007-GC.description"
3844 msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information."
3845 msgid "SUN4U-8007-GC.response"
3846 msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3847 msgid "SUN4U-8007-GC.impact"
3848 msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3849 msgid "SUN4U-8007-GC.action"
3850 msgstr "No repair action is recommended at this time.\n"
3852 # code: SUN4U-8007-HH
3853 # keys: fault.cpu.ultraSPARC-IVplus.l2cachetag-line
3855 msgid "SUN4U-8007-HH.type"
3857 msgid "SUN4U-8007-HH.severity"
3859 msgid "SUN4U-8007-HH.description"
3860 msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information."
3861 msgid "SUN4U-8007-HH.response"
3862 msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3863 msgid "SUN4U-8007-HH.impact"
3864 msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3865 msgid "SUN4U-8007-HH.action"
3866 msgstr "No repair action is recommended at this time.\n"
3868 # code: SUN4U-8007-JD
3869 # keys: fault.cpu.ultraSPARC-IVplus.l3cachetag-line
3871 msgid "SUN4U-8007-JD.type"
3873 msgid "SUN4U-8007-JD.severity"
3875 msgid "SUN4U-8007-JD.description"
3876 msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n Refer to %s for more information."
3877 msgid "SUN4U-8007-JD.response"
3878 msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3879 msgid "SUN4U-8007-JD.impact"
3880 msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3881 msgid "SUN4U-8007-JD.action"
3882 msgstr "No repair action is recommended at this time.\n"
3884 # code: SUN4U-8007-KY
3885 # keys: fault.memory.dimm-page-retires-excessive
3887 msgid "SUN4U-8007-KY.type"
3889 msgid "SUN4U-8007-KY.severity"
3891 msgid "SUN4U-8007-KY.description"
3892 msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels.\n Refer to %s for more information."
3893 msgid "SUN4U-8007-KY.response"
3894 msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached.\n"
3895 msgid "SUN4U-8007-KY.impact"
3896 msgstr "Total system memory capacity has been reduced.\n"
3897 msgid "SUN4U-8007-KY.action"
3898 msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n"
3900 # code: SUN4U-8007-L3
3901 # keys: fault.memory.dimm-ue-imminent
3903 msgid "SUN4U-8007-L3.type"
3905 msgid "SUN4U-8007-L3.severity"
3907 msgid "SUN4U-8007-L3.description"
3908 msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n Refer to %s for more information."
3909 msgid "SUN4U-8007-L3.response"
3910 msgstr "None at this time.\n"
3911 msgid "SUN4U-8007-L3.impact"
3912 msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n"
3913 msgid "SUN4U-8007-L3.action"
3914 msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n"
3916 # code: SUN4U-8007-MS
3917 # keys: fault.memory.dram-ue-imminent
3919 msgid "SUN4U-8007-MS.type"
3921 msgid "SUN4U-8007-MS.severity"
3923 msgid "SUN4U-8007-MS.description"
3924 msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n Refer to %s for more information."
3925 msgid "SUN4U-8007-MS.response"
3926 msgstr "None at this time.\n"
3927 msgid "SUN4U-8007-MS.impact"
3928 msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n"
3929 msgid "SUN4U-8007-MS.action"
3930 msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n"