1# 2# Copyright 2008 Sun Microsystems, Inc. All rights reserved. 3# Use is subject to license terms. 4# 5# CDDL HEADER START 6# 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. 10# 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. 15# 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] 21# 22# CDDL HEADER END 23# 24#ident "%Z%%M% %I% %E% SMI" 25# 26# DO NOT EDIT -- this file is generated by the Event Registry. 27# 28# 29# code: SUN4U-8000-1A 30# keys: fault.memory.page 31# 32msgid "SUN4U-8000-1A.type" 33msgstr "Fault" 34msgid "SUN4U-8000-1A.severity" 35msgstr "Minor" 36msgid "SUN4U-8000-1A.description" 37msgstr "The number of errors associated with this memory module continues to exceed acceptable levels. Refer to %s for more information." 38msgid "SUN4U-8000-1A.response" 39msgstr "An attempt will be made to remove this memory page from service." 40msgid "SUN4U-8000-1A.impact" 41msgstr "The performance of the system may be minimally impacted as a result of removing the memory page from operation." 42msgid "SUN4U-8000-1A.action" 43msgstr "No repair action is recommended at this time." 44# 45# code: SUN4U-8000-2S 46# keys: fault.memory.dimm 47# 48msgid "SUN4U-8000-2S.type" 49msgstr "Fault" 50msgid "SUN4U-8000-2S.severity" 51msgstr "Major" 52msgid "SUN4U-8000-2S.description" 53msgstr "The number of errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information." 54msgid "SUN4U-8000-2S.response" 55msgstr "Pages of memory associated with this memory module are being removed from service as errors are reported." 56msgid "SUN4U-8000-2S.impact" 57msgstr "Total system memory capacity will be reduced as pages are retired." 58msgid "SUN4U-8000-2S.action" 59msgstr "Schedule a repair procedure to replace the affected memory module. Use fmdump -v -u <EVENT_ID> to identify the module." 60# 61# code: SUN4U-8000-35 62# keys: fault.memory.bank 63# 64msgid "SUN4U-8000-35.type" 65msgstr "Fault" 66msgid "SUN4U-8000-35.severity" 67msgstr "Critical" 68msgid "SUN4U-8000-35.description" 69msgstr "The number of errors associated with this memory module has exceeded acceptable levels. Refer to %s for more information." 70msgid "SUN4U-8000-35.response" 71msgstr "Pages of memory associated with this memory module are being removed from service as errors are reported." 72msgid "SUN4U-8000-35.impact" 73msgstr "Total system memory capacity will be reduced as pages are retired." 74msgid "SUN4U-8000-35.action" 75msgstr "Schedule a repair procedure to replace the affected memory module. Use fmdump -v -u <EVENT_ID> to identify the module." 76# 77# code: SUN4U-8000-4Y 78# keys: fault.cpu.ultraSPARC-III.dcache 79# 80msgid "SUN4U-8000-4Y.type" 81msgstr "Fault" 82msgid "SUN4U-8000-4Y.severity" 83msgstr "Major" 84msgid "SUN4U-8000-4Y.description" 85msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." 86msgid "SUN4U-8000-4Y.response" 87msgstr "The fault manager will attempt to remove the affected CPU from service." 88msgid "SUN4U-8000-4Y.impact" 89msgstr "System performance may be affected." 90msgid "SUN4U-8000-4Y.action" 91msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 92# 93# code: SUN4U-8000-53 94# keys: fault.cpu.ultraSPARC-III.icache 95# 96msgid "SUN4U-8000-53.type" 97msgstr "Fault" 98msgid "SUN4U-8000-53.severity" 99msgstr "Major" 100msgid "SUN4U-8000-53.description" 101msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." 102msgid "SUN4U-8000-53.response" 103msgstr "The fault manager will attempt to remove the affected CPU from service." 104msgid "SUN4U-8000-53.impact" 105msgstr "System performance may be affected." 106msgid "SUN4U-8000-53.action" 107msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 108# 109# code: SUN4U-8000-6H 110# keys: fault.cpu.ultraSPARC-III.l2cachedata 111# 112msgid "SUN4U-8000-6H.type" 113msgstr "Fault" 114msgid "SUN4U-8000-6H.severity" 115msgstr "Major" 116msgid "SUN4U-8000-6H.description" 117msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 118msgid "SUN4U-8000-6H.response" 119msgstr "The fault manager will attempt to remove the affected CPU from service." 120msgid "SUN4U-8000-6H.impact" 121msgstr "System performance may be affected." 122msgid "SUN4U-8000-6H.action" 123msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 124# 125# code: SUN4U-8000-7D 126# keys: fault.cpu.ultraSPARC-III.l2cachetag 127# 128msgid "SUN4U-8000-7D.type" 129msgstr "Fault" 130msgid "SUN4U-8000-7D.severity" 131msgstr "Major" 132msgid "SUN4U-8000-7D.description" 133msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 134msgid "SUN4U-8000-7D.response" 135msgstr "The fault manager will attempt to remove the affected CPU from service." 136msgid "SUN4U-8000-7D.impact" 137msgstr "System performance may be affected." 138msgid "SUN4U-8000-7D.action" 139msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 140# 141# code: SUN4U-8000-84 142# keys: fault.cpu.ultraSPARC-IIIi.dcache 143# 144msgid "SUN4U-8000-84.type" 145msgstr "Fault" 146msgid "SUN4U-8000-84.severity" 147msgstr "Major" 148msgid "SUN4U-8000-84.description" 149msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 150msgid "SUN4U-8000-84.response" 151msgstr "The fault manager will attempt to remove the affected CPU from service." 152msgid "SUN4U-8000-84.impact" 153msgstr "System performance system may be affected." 154msgid "SUN4U-8000-84.action" 155msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 156# 157# code: SUN4U-8000-9R 158# keys: fault.cpu.ultraSPARC-IIIi.icache 159# 160msgid "SUN4U-8000-9R.type" 161msgstr "Fault" 162msgid "SUN4U-8000-9R.severity" 163msgstr "Major" 164msgid "SUN4U-8000-9R.description" 165msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 166msgid "SUN4U-8000-9R.response" 167msgstr "The fault manager will attempt to remove the affected CPU from service." 168msgid "SUN4U-8000-9R.impact" 169msgstr "System performance may be affected." 170msgid "SUN4U-8000-9R.action" 171msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 172# 173# code: SUN4U-8000-AC 174# keys: fault.cpu.ultraSPARC-IIIi.l2cachedata 175# 176msgid "SUN4U-8000-AC.type" 177msgstr "Fault" 178msgid "SUN4U-8000-AC.severity" 179msgstr "Major" 180msgid "SUN4U-8000-AC.description" 181msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 182msgid "SUN4U-8000-AC.response" 183msgstr "The fault manager will attempt to remove the affected CPU from service." 184msgid "SUN4U-8000-AC.impact" 185msgstr "System performance may be affected." 186msgid "SUN4U-8000-AC.action" 187msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 188# 189# code: SUN4U-8000-CQ 190# keys: fault.cpu.ultraSPARC-IIIi.l2cachetag 191# 192msgid "SUN4U-8000-CQ.type" 193msgstr "Fault" 194msgid "SUN4U-8000-CQ.severity" 195msgstr "Major" 196msgid "SUN4U-8000-CQ.description" 197msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 198msgid "SUN4U-8000-CQ.response" 199msgstr "The fault manager will attempt to remove the affected CPU from service." 200msgid "SUN4U-8000-CQ.impact" 201msgstr "System performance may be affected." 202msgid "SUN4U-8000-CQ.action" 203msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 204# 205# code: SUN4U-8000-DE 206# keys: fault.cpu.ultraSPARC-IIIplus.dcache 207# 208msgid "SUN4U-8000-DE.type" 209msgstr "Fault" 210msgid "SUN4U-8000-DE.severity" 211msgstr "Major" 212msgid "SUN4U-8000-DE.description" 213msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 214msgid "SUN4U-8000-DE.response" 215msgstr "The fault manager will attempt to remove the affected CPU from service." 216msgid "SUN4U-8000-DE.impact" 217msgstr "System performance may be affected." 218msgid "SUN4U-8000-DE.action" 219msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 220# 221# code: SUN4U-8000-EJ 222# keys: fault.cpu.ultraSPARC-IIIplus.icache 223# 224msgid "SUN4U-8000-EJ.type" 225msgstr "Fault" 226msgid "SUN4U-8000-EJ.severity" 227msgstr "Major" 228msgid "SUN4U-8000-EJ.description" 229msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 230msgid "SUN4U-8000-EJ.response" 231msgstr "The fault manager will attempt to remove the affected CPU from service." 232msgid "SUN4U-8000-EJ.impact" 233msgstr "System performance may be affected." 234msgid "SUN4U-8000-EJ.action" 235msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 236# 237# code: SUN4U-8000-F2 238# keys: fault.cpu.ultraSPARC-IIIplus.l2cachedata 239# 240msgid "SUN4U-8000-F2.type" 241msgstr "Fault" 242msgid "SUN4U-8000-F2.severity" 243msgstr "Major" 244msgid "SUN4U-8000-F2.description" 245msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 246msgid "SUN4U-8000-F2.response" 247msgstr "The fault manager will attempt to remove the affected CPU from service." 248msgid "SUN4U-8000-F2.impact" 249msgstr "System performance may be affected." 250msgid "SUN4U-8000-F2.action" 251msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 252# 253# code: SUN4U-8000-GX 254# keys: fault.cpu.ultraSPARC-IIIplus.l2cachetag 255# 256msgid "SUN4U-8000-GX.type" 257msgstr "Fault" 258msgid "SUN4U-8000-GX.severity" 259msgstr "Major" 260msgid "SUN4U-8000-GX.description" 261msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 262msgid "SUN4U-8000-GX.response" 263msgstr "An attempt will be made to remove the affected CPU from service." 264msgid "SUN4U-8000-GX.impact" 265msgstr "System performance may be affected." 266msgid "SUN4U-8000-GX.action" 267msgstr "Schedule a repair procedure to replace the affected CPU. Use fmdump -v -u <EVENT_ID> to identify the CPU." 268# 269# code: SUN4U-8000-H5 270# keys: fault.cpu.ultraSPARC-IV.dcache 271# 272msgid "SUN4U-8000-H5.type" 273msgstr "Fault" 274msgid "SUN4U-8000-H5.severity" 275msgstr "Major" 276msgid "SUN4U-8000-H5.description" 277msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 278msgid "SUN4U-8000-H5.response" 279msgstr "The fault manager will attempt to remove the affected CPU from service." 280msgid "SUN4U-8000-H5.impact" 281msgstr "System performance may be affected." 282msgid "SUN4U-8000-H5.action" 283msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 284# 285# code: SUN4U-8000-JS 286# keys: fault.cpu.ultraSPARC-IV.icache 287# 288msgid "SUN4U-8000-JS.type" 289msgstr "Fault" 290msgid "SUN4U-8000-JS.severity" 291msgstr "Major" 292msgid "SUN4U-8000-JS.description" 293msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 294msgid "SUN4U-8000-JS.response" 295msgstr "The fault manager will attempt to remove the affected CPU from service." 296msgid "SUN4U-8000-JS.impact" 297msgstr "System performance may be affected." 298msgid "SUN4U-8000-JS.action" 299msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 300# 301# code: SUN4U-8000-KA 302# keys: fault.cpu.ultraSPARC-IV.l2cachedata 303# 304msgid "SUN4U-8000-KA.type" 305msgstr "Fault" 306msgid "SUN4U-8000-KA.severity" 307msgstr "Major" 308msgid "SUN4U-8000-KA.description" 309msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 310msgid "SUN4U-8000-KA.response" 311msgstr "The fault manager will attempt to remove the affected CPU from service." 312msgid "SUN4U-8000-KA.impact" 313msgstr "System performance may be affected." 314msgid "SUN4U-8000-KA.action" 315msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 316# 317# code: SUN4U-8000-LP 318# keys: fault.cpu.ultraSPARC-IV.l2cachetag 319# 320msgid "SUN4U-8000-LP.type" 321msgstr "Fault" 322msgid "SUN4U-8000-LP.severity" 323msgstr "Major" 324msgid "SUN4U-8000-LP.description" 325msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 326msgid "SUN4U-8000-LP.response" 327msgstr "The fault manager will attempt to remove the affected CPU from service." 328msgid "SUN4U-8000-LP.impact" 329msgstr "System performance may be affected." 330msgid "SUN4U-8000-LP.action" 331msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 332# 333# code: SUN4U-8000-MD 334# keys: fault.cpu.ultraSPARC-III.fpu 335# 336msgid "SUN4U-8000-MD.type" 337msgstr "Fault" 338msgid "SUN4U-8000-MD.severity" 339msgstr "Major" 340msgid "SUN4U-8000-MD.description" 341msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." 342msgid "SUN4U-8000-MD.response" 343msgstr "The fault manager will attempt to remove the affected CPU from service." 344msgid "SUN4U-8000-MD.impact" 345msgstr "System performance may be affected." 346msgid "SUN4U-8000-MD.action" 347msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 348# 349# code: SUN4U-8000-NH 350# keys: fault.cpu.ultraSPARC-IIIi.fpu 351# 352msgid "SUN4U-8000-NH.type" 353msgstr "Fault" 354msgid "SUN4U-8000-NH.severity" 355msgstr "Major" 356msgid "SUN4U-8000-NH.description" 357msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." 358msgid "SUN4U-8000-NH.response" 359msgstr "The fault manager will attempt to remove the affected CPU from service." 360msgid "SUN4U-8000-NH.impact" 361msgstr "System performance may be affected." 362msgid "SUN4U-8000-NH.action" 363msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 364# 365# code: SUN4U-8000-P3 366# keys: fault.cpu.ultraSPARC-IIIplus.fpu 367# 368msgid "SUN4U-8000-P3.type" 369msgstr "Fault" 370msgid "SUN4U-8000-P3.severity" 371msgstr "Major" 372msgid "SUN4U-8000-P3.description" 373msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." 374msgid "SUN4U-8000-P3.response" 375msgstr "The fault manager will attempt to remove the affected CPU from service." 376msgid "SUN4U-8000-P3.impact" 377msgstr "System performance may be affected." 378msgid "SUN4U-8000-P3.action" 379msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 380# 381# code: SUN4U-8000-QY 382# keys: fault.cpu.ultraSPARC-IV.fpu 383# 384msgid "SUN4U-8000-QY.type" 385msgstr "Fault" 386msgid "SUN4U-8000-QY.severity" 387msgstr "Major" 388msgid "SUN4U-8000-QY.description" 389msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." 390msgid "SUN4U-8000-QY.response" 391msgstr "The fault manager will attempt to remove the affected CPU from service." 392msgid "SUN4U-8000-QY.impact" 393msgstr "System performance may be affected." 394msgid "SUN4U-8000-QY.action" 395msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 396# 397# code: SUN4U-8000-RQ 398# keys: fault.cpu.ultraSPARC-IVplus.fpu 399# 400msgid "SUN4U-8000-RQ.type" 401msgstr "Fault" 402msgid "SUN4U-8000-RQ.severity" 403msgstr "Major" 404msgid "SUN4U-8000-RQ.description" 405msgstr "A fault has been detected in the FPU of this CPU. Refer to %s for more information." 406msgid "SUN4U-8000-RQ.response" 407msgstr "The fault manager will attempt to remove the affected CPU from service." 408msgid "SUN4U-8000-RQ.impact" 409msgstr "System performance may be affected." 410msgid "SUN4U-8000-RQ.action" 411msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 412# 413# code: SUN4U-8000-SC 414# keys: fault.cpu.ultraSPARC-IVplus.dcache 415# 416msgid "SUN4U-8000-SC.type" 417msgstr "Fault" 418msgid "SUN4U-8000-SC.severity" 419msgstr "Major" 420msgid "SUN4U-8000-SC.description" 421msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 422msgid "SUN4U-8000-SC.response" 423msgstr "The fault manager will attempt to remove the affected CPU from service." 424msgid "SUN4U-8000-SC.impact" 425msgstr "System performance may be affected." 426msgid "SUN4U-8000-SC.action" 427msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 428# 429# code: SUN4U-8000-TR 430# keys: fault.cpu.ultraSPARC-IVplus.icache 431# 432msgid "SUN4U-8000-TR.type" 433msgstr "Fault" 434msgid "SUN4U-8000-TR.severity" 435msgstr "Major" 436msgid "SUN4U-8000-TR.description" 437msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 438msgid "SUN4U-8000-TR.response" 439msgstr "The fault manager will attempt to remove the affected CPU from service." 440msgid "SUN4U-8000-TR.impact" 441msgstr "System performance may be affected." 442msgid "SUN4U-8000-TR.action" 443msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 444# 445# code: SUN4U-8000-U4 446# keys: fault.cpu.ultraSPARC-IVplus.pcache 447# 448msgid "SUN4U-8000-U4.type" 449msgstr "Fault" 450msgid "SUN4U-8000-U4.severity" 451msgstr "Major" 452msgid "SUN4U-8000-U4.description" 453msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 454msgid "SUN4U-8000-U4.response" 455msgstr "The fault manager will attempt to remove the affected CPU from service." 456msgid "SUN4U-8000-U4.impact" 457msgstr "System performance may be affected." 458msgid "SUN4U-8000-U4.action" 459msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 460# 461# code: SUN4U-8000-VX 462# keys: fault.cpu.ultraSPARC-IVplus.dtlb 463# 464msgid "SUN4U-8000-VX.type" 465msgstr "Fault" 466msgid "SUN4U-8000-VX.severity" 467msgstr "Major" 468msgid "SUN4U-8000-VX.description" 469msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 470msgid "SUN4U-8000-VX.response" 471msgstr "The fault manager will attempt to remove the affected CPU from service." 472msgid "SUN4U-8000-VX.impact" 473msgstr "System performance may be affected." 474msgid "SUN4U-8000-VX.action" 475msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 476# 477# code: SUN4U-8000-W2 478# keys: fault.cpu.ultraSPARC-IVplus.itlb 479# 480msgid "SUN4U-8000-W2.type" 481msgstr "Fault" 482msgid "SUN4U-8000-W2.severity" 483msgstr "Major" 484msgid "SUN4U-8000-W2.description" 485msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 486msgid "SUN4U-8000-W2.response" 487msgstr "The fault manager will attempt to remove the affected CPU from service." 488msgid "SUN4U-8000-W2.impact" 489msgstr "System performance may be affected." 490msgid "SUN4U-8000-W2.action" 491msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 492# 493# code: SUN4U-8000-XJ 494# keys: fault.cpu.ultraSPARC-IVplus.l2cachedata 495# 496msgid "SUN4U-8000-XJ.type" 497msgstr "Fault" 498msgid "SUN4U-8000-XJ.severity" 499msgstr "Major" 500msgid "SUN4U-8000-XJ.description" 501msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 502msgid "SUN4U-8000-XJ.response" 503msgstr "The fault manager will attempt to remove the affected CPU from service." 504msgid "SUN4U-8000-XJ.impact" 505msgstr "System performance may be affected." 506msgid "SUN4U-8000-XJ.action" 507msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 508# 509# code: SUN4U-8000-YE 510# keys: fault.cpu.ultraSPARC-IVplus.l2cachetag 511# 512msgid "SUN4U-8000-YE.type" 513msgstr "Fault" 514msgid "SUN4U-8000-YE.severity" 515msgstr "Major" 516msgid "SUN4U-8000-YE.description" 517msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 518msgid "SUN4U-8000-YE.response" 519msgstr "The fault manager will attempt to remove the affected CPU from service." 520msgid "SUN4U-8000-YE.impact" 521msgstr "System performance may be affected." 522msgid "SUN4U-8000-YE.action" 523msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 524# 525# code: SUN4U-8001-0J 526# keys: fault.cpu.ultraSPARC-IVplus.l3cachedata 527# 528msgid "SUN4U-8001-0J.type" 529msgstr "Fault" 530msgid "SUN4U-8001-0J.severity" 531msgstr "Major" 532msgid "SUN4U-8001-0J.description" 533msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 534msgid "SUN4U-8001-0J.response" 535msgstr "The fault manager will attempt to remove the affected CPU from service." 536msgid "SUN4U-8001-0J.impact" 537msgstr "System performance may be affected." 538msgid "SUN4U-8001-0J.action" 539msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 540# 541# code: SUN4U-8001-1E 542# keys: fault.cpu.ultraSPARC-IVplus.l3cachetag 543# 544msgid "SUN4U-8001-1E.type" 545msgstr "Fault" 546msgid "SUN4U-8001-1E.severity" 547msgstr "Major" 548msgid "SUN4U-8001-1E.description" 549msgstr "The number of errors associated with this CPU has exceeded acceptable levels. Refer to %s for more information." 550msgid "SUN4U-8001-1E.response" 551msgstr "The fault manager will attempt to remove the affected CPU from service." 552msgid "SUN4U-8001-1E.impact" 553msgstr "System performance may be affected." 554msgid "SUN4U-8001-1E.action" 555msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 556# 557# code: SUN4U-8001-2X 558# keys: defect.ultraSPARC-II.memory.nodiag 559# 560msgid "SUN4U-8001-2X.type" 561msgstr "Defect" 562msgid "SUN4U-8001-2X.severity" 563msgstr "Minor" 564msgid "SUN4U-8001-2X.description" 565msgstr "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." 566msgid "SUN4U-8001-2X.response" 567msgstr "The error information has been saved for examination by Sun." 568msgid "SUN4U-8001-2X.impact" 569msgstr "The error log will need to be manually examined using fmdump(1M) in order to determine if any human response is required." 570msgid "SUN4U-8001-2X.action" 571msgstr "Use fmdump -ev -u <EVENT-ID> to view and record the undiagnosed errors." 572# 573# code: SUN4U-8001-32 574# keys: fault.memory.datapath 575# 576msgid "SUN4U-8001-32.type" 577msgstr "Fault" 578msgid "SUN4U-8001-32.severity" 579msgstr "Major" 580msgid "SUN4U-8001-32.description" 581msgstr "Errors have been detected on multiple memory modules, suggesting that a problem exists somewhere else in the system. Refer to %s for more information." 582msgid "SUN4U-8001-32.response" 583msgstr "Error reports from the affected components will be logged for examination by Sun." 584msgid "SUN4U-8001-32.impact" 585msgstr "System performance and stability may be affected." 586msgid "SUN4U-8001-32.action" 587msgstr "Contact your service provider for further diagnosis." 588# 589# code: SUN4U-8001-4R 590# keys: fault.io.datapath 591# 592msgid "SUN4U-8001-4R.type" 593msgstr "Fault" 594msgid "SUN4U-8001-4R.severity" 595msgstr "Critical" 596msgid "SUN4U-8001-4R.description" 597msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 598msgid "SUN4U-8001-4R.response" 599msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 600msgid "SUN4U-8001-4R.impact" 601msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 602msgid "SUN4U-8001-4R.action" 603msgstr "\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# 605# code: SUN4U-8001-54 606# keys: defect.io.pci.driver fault.io.datapath 607# 608msgid "SUN4U-8001-54.type" 609msgstr "Fault" 610msgid "SUN4U-8001-54.severity" 611msgstr "Critical" 612msgid "SUN4U-8001-54.description" 613msgstr "\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." 614msgid "SUN4U-8001-54.response" 615msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 616msgid "SUN4U-8001-54.impact" 617msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 618msgid "SUN4U-8001-54.action" 619msgstr "\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# 621# code: SUN4U-8001-6Q 622# keys: fault.io.datapath fault.io.pci.bus 623# 624msgid "SUN4U-8001-6Q.type" 625msgstr "Fault" 626msgid "SUN4U-8001-6Q.severity" 627msgstr "Critical" 628msgid "SUN4U-8001-6Q.description" 629msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 630msgid "SUN4U-8001-6Q.response" 631msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 632msgid "SUN4U-8001-6Q.impact" 633msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 634msgid "SUN4U-8001-6Q.action" 635msgstr "\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# 637# code: SUN4U-8001-7C 638# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus 639# 640msgid "SUN4U-8001-7C.type" 641msgstr "Fault" 642msgid "SUN4U-8001-7C.severity" 643msgstr "Critical" 644msgid "SUN4U-8001-7C.description" 645msgstr "\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." 646msgid "SUN4U-8001-7C.response" 647msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 648msgid "SUN4U-8001-7C.impact" 649msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 650msgid "SUN4U-8001-7C.action" 651msgstr "\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# 653# code: SUN4U-8001-83 654# keys: fault.io.datapath fault.io.pci.device 655# 656msgid "SUN4U-8001-83.type" 657msgstr "Fault" 658msgid "SUN4U-8001-83.severity" 659msgstr "Critical" 660msgid "SUN4U-8001-83.description" 661msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 662msgid "SUN4U-8001-83.response" 663msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 664msgid "SUN4U-8001-83.impact" 665msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 666msgid "SUN4U-8001-83.action" 667msgstr "\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# 669# code: SUN4U-8001-9Y 670# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device 671# 672msgid "SUN4U-8001-9Y.type" 673msgstr "Fault" 674msgid "SUN4U-8001-9Y.severity" 675msgstr "Critical" 676msgid "SUN4U-8001-9Y.description" 677msgstr "\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." 678msgid "SUN4U-8001-9Y.response" 679msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 680msgid "SUN4U-8001-9Y.impact" 681msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 682msgid "SUN4U-8001-9Y.action" 683msgstr "\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# 685# code: SUN4U-8001-AD 686# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device 687# 688msgid "SUN4U-8001-AD.type" 689msgstr "Fault" 690msgid "SUN4U-8001-AD.severity" 691msgstr "Critical" 692msgid "SUN4U-8001-AD.description" 693msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 694msgid "SUN4U-8001-AD.response" 695msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 696msgid "SUN4U-8001-AD.impact" 697msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 698msgid "SUN4U-8001-AD.action" 699msgstr "\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# 701# code: SUN4U-8001-CH 702# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device 703# 704msgid "SUN4U-8001-CH.type" 705msgstr "Fault" 706msgid "SUN4U-8001-CH.severity" 707msgstr "Critical" 708msgid "SUN4U-8001-CH.description" 709msgstr "\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." 710msgid "SUN4U-8001-CH.response" 711msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 712msgid "SUN4U-8001-CH.impact" 713msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 714msgid "SUN4U-8001-CH.action" 715msgstr "\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# 717# code: SUN4U-8001-DA 718# keys: fault.io.hbus 719# 720msgid "SUN4U-8001-DA.type" 721msgstr "Fault" 722msgid "SUN4U-8001-DA.severity" 723msgstr "Critical" 724msgid "SUN4U-8001-DA.description" 725msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 726msgid "SUN4U-8001-DA.response" 727msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 728msgid "SUN4U-8001-DA.impact" 729msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 730msgid "SUN4U-8001-DA.action" 731msgstr "\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# 733# code: SUN4U-8001-EP 734# keys: defect.io.pci.driver fault.io.hbus 735# 736msgid "SUN4U-8001-EP.type" 737msgstr "Fault" 738msgid "SUN4U-8001-EP.severity" 739msgstr "Critical" 740msgid "SUN4U-8001-EP.description" 741msgstr "\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." 742msgid "SUN4U-8001-EP.response" 743msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 744msgid "SUN4U-8001-EP.impact" 745msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 746msgid "SUN4U-8001-EP.action" 747msgstr "\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# 749# code: SUN4U-8001-F5 750# keys: fault.io.hbus fault.io.pci.bus 751# 752msgid "SUN4U-8001-F5.type" 753msgstr "Fault" 754msgid "SUN4U-8001-F5.severity" 755msgstr "Critical" 756msgid "SUN4U-8001-F5.description" 757msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 758msgid "SUN4U-8001-F5.response" 759msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 760msgid "SUN4U-8001-F5.impact" 761msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 762msgid "SUN4U-8001-F5.action" 763msgstr "\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# 765# code: SUN4U-8001-GS 766# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus 767# 768msgid "SUN4U-8001-GS.type" 769msgstr "Fault" 770msgid "SUN4U-8001-GS.severity" 771msgstr "Critical" 772msgid "SUN4U-8001-GS.description" 773msgstr "\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." 774msgid "SUN4U-8001-GS.response" 775msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 776msgid "SUN4U-8001-GS.impact" 777msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 778msgid "SUN4U-8001-GS.action" 779msgstr "\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# 781# code: SUN4U-8001-H2 782# keys: fault.io.hbus fault.io.pci.device 783# 784msgid "SUN4U-8001-H2.type" 785msgstr "Fault" 786msgid "SUN4U-8001-H2.severity" 787msgstr "Critical" 788msgid "SUN4U-8001-H2.description" 789msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 790msgid "SUN4U-8001-H2.response" 791msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 792msgid "SUN4U-8001-H2.impact" 793msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 794msgid "SUN4U-8001-H2.action" 795msgstr "\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# 797# code: SUN4U-8001-JX 798# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device 799# 800msgid "SUN4U-8001-JX.type" 801msgstr "Fault" 802msgid "SUN4U-8001-JX.severity" 803msgstr "Critical" 804msgid "SUN4U-8001-JX.description" 805msgstr "\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." 806msgid "SUN4U-8001-JX.response" 807msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 808msgid "SUN4U-8001-JX.impact" 809msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 810msgid "SUN4U-8001-JX.action" 811msgstr "\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# 813# code: SUN4U-8001-KE 814# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device 815# 816msgid "SUN4U-8001-KE.type" 817msgstr "Fault" 818msgid "SUN4U-8001-KE.severity" 819msgstr "Critical" 820msgid "SUN4U-8001-KE.description" 821msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 822msgid "SUN4U-8001-KE.response" 823msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 824msgid "SUN4U-8001-KE.impact" 825msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 826msgid "SUN4U-8001-KE.action" 827msgstr "\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# 829# code: SUN4U-8001-LJ 830# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device 831# 832msgid "SUN4U-8001-LJ.type" 833msgstr "Fault" 834msgid "SUN4U-8001-LJ.severity" 835msgstr "Critical" 836msgid "SUN4U-8001-LJ.description" 837msgstr "\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." 838msgid "SUN4U-8001-LJ.response" 839msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 840msgid "SUN4U-8001-LJ.impact" 841msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 842msgid "SUN4U-8001-LJ.action" 843msgstr "\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# 845# code: SUN4U-8001-MC 846# keys: fault.io.datapath fault.io.hbus 847# 848msgid "SUN4U-8001-MC.type" 849msgstr "Fault" 850msgid "SUN4U-8001-MC.severity" 851msgstr "Critical" 852msgid "SUN4U-8001-MC.description" 853msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 854msgid "SUN4U-8001-MC.response" 855msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 856msgid "SUN4U-8001-MC.impact" 857msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 858msgid "SUN4U-8001-MC.action" 859msgstr "\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# 861# code: SUN4U-8001-NQ 862# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus 863# 864msgid "SUN4U-8001-NQ.type" 865msgstr "Fault" 866msgid "SUN4U-8001-NQ.severity" 867msgstr "Critical" 868msgid "SUN4U-8001-NQ.description" 869msgstr "\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." 870msgid "SUN4U-8001-NQ.response" 871msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 872msgid "SUN4U-8001-NQ.impact" 873msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 874msgid "SUN4U-8001-NQ.action" 875msgstr "\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# 877# code: SUN4U-8001-P4 878# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus 879# 880msgid "SUN4U-8001-P4.type" 881msgstr "Fault" 882msgid "SUN4U-8001-P4.severity" 883msgstr "Critical" 884msgid "SUN4U-8001-P4.description" 885msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 886msgid "SUN4U-8001-P4.response" 887msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 888msgid "SUN4U-8001-P4.impact" 889msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 890msgid "SUN4U-8001-P4.action" 891msgstr "\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# 893# code: SUN4U-8001-QR 894# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus 895# 896msgid "SUN4U-8001-QR.type" 897msgstr "Fault" 898msgid "SUN4U-8001-QR.severity" 899msgstr "Critical" 900msgid "SUN4U-8001-QR.description" 901msgstr "\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." 902msgid "SUN4U-8001-QR.response" 903msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 904msgid "SUN4U-8001-QR.impact" 905msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 906msgid "SUN4U-8001-QR.action" 907msgstr "\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# 909# code: SUN4U-8001-RH 910# keys: fault.io.datapath fault.io.hbus fault.io.pci.device 911# 912msgid "SUN4U-8001-RH.type" 913msgstr "Fault" 914msgid "SUN4U-8001-RH.severity" 915msgstr "Critical" 916msgid "SUN4U-8001-RH.description" 917msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 918msgid "SUN4U-8001-RH.response" 919msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 920msgid "SUN4U-8001-RH.impact" 921msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 922msgid "SUN4U-8001-RH.action" 923msgstr "\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# 925# code: SUN4U-8001-SD 926# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device 927# 928msgid "SUN4U-8001-SD.type" 929msgstr "Fault" 930msgid "SUN4U-8001-SD.severity" 931msgstr "Critical" 932msgid "SUN4U-8001-SD.description" 933msgstr "\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." 934msgid "SUN4U-8001-SD.response" 935msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 936msgid "SUN4U-8001-SD.impact" 937msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 938msgid "SUN4U-8001-SD.action" 939msgstr "\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# 941# code: SUN4U-8001-TY 942# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device 943# 944msgid "SUN4U-8001-TY.type" 945msgstr "Fault" 946msgid "SUN4U-8001-TY.severity" 947msgstr "Critical" 948msgid "SUN4U-8001-TY.description" 949msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 950msgid "SUN4U-8001-TY.response" 951msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 952msgid "SUN4U-8001-TY.impact" 953msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 954msgid "SUN4U-8001-TY.action" 955msgstr "\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# 957# code: SUN4U-8001-U3 958# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device 959# 960msgid "SUN4U-8001-U3.type" 961msgstr "Fault" 962msgid "SUN4U-8001-U3.severity" 963msgstr "Critical" 964msgid "SUN4U-8001-U3.description" 965msgstr "\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." 966msgid "SUN4U-8001-U3.response" 967msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 968msgid "SUN4U-8001-U3.impact" 969msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 970msgid "SUN4U-8001-U3.action" 971msgstr "\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# 973# code: SUN4U-8001-VS 974# keys: fault.io.schizo 975# 976msgid "SUN4U-8001-VS.type" 977msgstr "Fault" 978msgid "SUN4U-8001-VS.severity" 979msgstr "Critical" 980msgid "SUN4U-8001-VS.description" 981msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 982msgid "SUN4U-8001-VS.response" 983msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 984msgid "SUN4U-8001-VS.impact" 985msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 986msgid "SUN4U-8001-VS.action" 987msgstr "\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# 989# code: SUN4U-8001-W5 990# keys: defect.io.pci.driver fault.io.schizo 991# 992msgid "SUN4U-8001-W5.type" 993msgstr "Fault" 994msgid "SUN4U-8001-W5.severity" 995msgstr "Critical" 996msgid "SUN4U-8001-W5.description" 997msgstr "\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." 998msgid "SUN4U-8001-W5.response" 999msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1000msgid "SUN4U-8001-W5.impact" 1001msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1002msgid "SUN4U-8001-W5.action" 1003msgstr "\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# 1005# code: SUN4U-8001-XP 1006# keys: fault.io.pci.bus fault.io.schizo 1007# 1008msgid "SUN4U-8001-XP.type" 1009msgstr "Fault" 1010msgid "SUN4U-8001-XP.severity" 1011msgstr "Critical" 1012msgid "SUN4U-8001-XP.description" 1013msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1014msgid "SUN4U-8001-XP.response" 1015msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1016msgid "SUN4U-8001-XP.impact" 1017msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1018msgid "SUN4U-8001-XP.action" 1019msgstr "\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# 1021# code: SUN4U-8001-YA 1022# keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo 1023# 1024msgid "SUN4U-8001-YA.type" 1025msgstr "Fault" 1026msgid "SUN4U-8001-YA.severity" 1027msgstr "Critical" 1028msgid "SUN4U-8001-YA.description" 1029msgstr "\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." 1030msgid "SUN4U-8001-YA.response" 1031msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1032msgid "SUN4U-8001-YA.impact" 1033msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1034msgid "SUN4U-8001-YA.action" 1035msgstr "\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# 1037# code: SUN4U-8002-0R 1038# keys: fault.io.pci.device fault.io.schizo 1039# 1040msgid "SUN4U-8002-0R.type" 1041msgstr "Fault" 1042msgid "SUN4U-8002-0R.severity" 1043msgstr "Critical" 1044msgid "SUN4U-8002-0R.description" 1045msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1046msgid "SUN4U-8002-0R.response" 1047msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1048msgid "SUN4U-8002-0R.impact" 1049msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1050msgid "SUN4U-8002-0R.action" 1051msgstr "\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# 1053# code: SUN4U-8002-14 1054# keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo 1055# 1056msgid "SUN4U-8002-14.type" 1057msgstr "Fault" 1058msgid "SUN4U-8002-14.severity" 1059msgstr "Critical" 1060msgid "SUN4U-8002-14.description" 1061msgstr "\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." 1062msgid "SUN4U-8002-14.response" 1063msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1064msgid "SUN4U-8002-14.impact" 1065msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1066msgid "SUN4U-8002-14.action" 1067msgstr "\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# 1069# code: SUN4U-8002-2Q 1070# keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo 1071# 1072msgid "SUN4U-8002-2Q.type" 1073msgstr "Fault" 1074msgid "SUN4U-8002-2Q.severity" 1075msgstr "Critical" 1076msgid "SUN4U-8002-2Q.description" 1077msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1078msgid "SUN4U-8002-2Q.response" 1079msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1080msgid "SUN4U-8002-2Q.impact" 1081msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1082msgid "SUN4U-8002-2Q.action" 1083msgstr "\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# 1085# code: SUN4U-8002-3C 1086# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo 1087# 1088msgid "SUN4U-8002-3C.type" 1089msgstr "Fault" 1090msgid "SUN4U-8002-3C.severity" 1091msgstr "Critical" 1092msgid "SUN4U-8002-3C.description" 1093msgstr "\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." 1094msgid "SUN4U-8002-3C.response" 1095msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1096msgid "SUN4U-8002-3C.impact" 1097msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1098msgid "SUN4U-8002-3C.action" 1099msgstr "\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# 1101# code: SUN4U-8002-4J 1102# keys: fault.io.datapath fault.io.schizo 1103# 1104msgid "SUN4U-8002-4J.type" 1105msgstr "Fault" 1106msgid "SUN4U-8002-4J.severity" 1107msgstr "Critical" 1108msgid "SUN4U-8002-4J.description" 1109msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1110msgid "SUN4U-8002-4J.response" 1111msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1112msgid "SUN4U-8002-4J.impact" 1113msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1114msgid "SUN4U-8002-4J.action" 1115msgstr "\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# 1117# code: SUN4U-8002-5E 1118# keys: defect.io.pci.driver fault.io.datapath fault.io.schizo 1119# 1120msgid "SUN4U-8002-5E.type" 1121msgstr "Fault" 1122msgid "SUN4U-8002-5E.severity" 1123msgstr "Critical" 1124msgid "SUN4U-8002-5E.description" 1125msgstr "\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." 1126msgid "SUN4U-8002-5E.response" 1127msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1128msgid "SUN4U-8002-5E.impact" 1129msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1130msgid "SUN4U-8002-5E.action" 1131msgstr "\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# 1133# code: SUN4U-8002-6X 1134# keys: fault.io.datapath fault.io.pci.bus fault.io.schizo 1135# 1136msgid "SUN4U-8002-6X.type" 1137msgstr "Fault" 1138msgid "SUN4U-8002-6X.severity" 1139msgstr "Critical" 1140msgid "SUN4U-8002-6X.description" 1141msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1142msgid "SUN4U-8002-6X.response" 1143msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1144msgid "SUN4U-8002-6X.impact" 1145msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1146msgid "SUN4U-8002-6X.action" 1147msgstr "\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# 1149# code: SUN4U-8002-72 1150# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo 1151# 1152msgid "SUN4U-8002-72.type" 1153msgstr "Fault" 1154msgid "SUN4U-8002-72.severity" 1155msgstr "Critical" 1156msgid "SUN4U-8002-72.description" 1157msgstr "\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." 1158msgid "SUN4U-8002-72.response" 1159msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1160msgid "SUN4U-8002-72.impact" 1161msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1162msgid "SUN4U-8002-72.action" 1163msgstr "\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# 1165# code: SUN4U-8002-8A 1166# keys: fault.io.datapath fault.io.pci.device fault.io.schizo 1167# 1168msgid "SUN4U-8002-8A.type" 1169msgstr "Fault" 1170msgid "SUN4U-8002-8A.severity" 1171msgstr "Critical" 1172msgid "SUN4U-8002-8A.description" 1173msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1174msgid "SUN4U-8002-8A.response" 1175msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1176msgid "SUN4U-8002-8A.impact" 1177msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1178msgid "SUN4U-8002-8A.action" 1179msgstr "\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# 1181# code: SUN4U-8002-9P 1182# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo 1183# 1184msgid "SUN4U-8002-9P.type" 1185msgstr "Fault" 1186msgid "SUN4U-8002-9P.severity" 1187msgstr "Critical" 1188msgid "SUN4U-8002-9P.description" 1189msgstr "\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." 1190msgid "SUN4U-8002-9P.response" 1191msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1192msgid "SUN4U-8002-9P.impact" 1193msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1194msgid "SUN4U-8002-9P.action" 1195msgstr "\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# 1197# code: SUN4U-8002-A5 1198# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo 1199# 1200msgid "SUN4U-8002-A5.type" 1201msgstr "Fault" 1202msgid "SUN4U-8002-A5.severity" 1203msgstr "Critical" 1204msgid "SUN4U-8002-A5.description" 1205msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1206msgid "SUN4U-8002-A5.response" 1207msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1208msgid "SUN4U-8002-A5.impact" 1209msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1210msgid "SUN4U-8002-A5.action" 1211msgstr "\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# 1213# code: SUN4U-8002-CS 1214# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo 1215# 1216msgid "SUN4U-8002-CS.type" 1217msgstr "Fault" 1218msgid "SUN4U-8002-CS.severity" 1219msgstr "Critical" 1220msgid "SUN4U-8002-CS.description" 1221msgstr "\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." 1222msgid "SUN4U-8002-CS.response" 1223msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1224msgid "SUN4U-8002-CS.impact" 1225msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1226msgid "SUN4U-8002-CS.action" 1227msgstr "\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# 1229# code: SUN4U-8002-D3 1230# keys: fault.io.hbus fault.io.schizo 1231# 1232msgid "SUN4U-8002-D3.type" 1233msgstr "Fault" 1234msgid "SUN4U-8002-D3.severity" 1235msgstr "Critical" 1236msgid "SUN4U-8002-D3.description" 1237msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1238msgid "SUN4U-8002-D3.response" 1239msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1240msgid "SUN4U-8002-D3.impact" 1241msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1242msgid "SUN4U-8002-D3.action" 1243msgstr "\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# 1245# code: SUN4U-8002-EY 1246# keys: defect.io.pci.driver fault.io.hbus fault.io.schizo 1247# 1248msgid "SUN4U-8002-EY.type" 1249msgstr "Fault" 1250msgid "SUN4U-8002-EY.severity" 1251msgstr "Critical" 1252msgid "SUN4U-8002-EY.description" 1253msgstr "\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." 1254msgid "SUN4U-8002-EY.response" 1255msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1256msgid "SUN4U-8002-EY.impact" 1257msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1258msgid "SUN4U-8002-EY.action" 1259msgstr "\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# 1261# code: SUN4U-8002-FD 1262# keys: fault.io.hbus fault.io.pci.bus fault.io.schizo 1263# 1264msgid "SUN4U-8002-FD.type" 1265msgstr "Fault" 1266msgid "SUN4U-8002-FD.severity" 1267msgstr "Critical" 1268msgid "SUN4U-8002-FD.description" 1269msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1270msgid "SUN4U-8002-FD.response" 1271msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1272msgid "SUN4U-8002-FD.impact" 1273msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1274msgid "SUN4U-8002-FD.action" 1275msgstr "\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# 1277# code: SUN4U-8002-GH 1278# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo 1279# 1280msgid "SUN4U-8002-GH.type" 1281msgstr "Fault" 1282msgid "SUN4U-8002-GH.severity" 1283msgstr "Critical" 1284msgid "SUN4U-8002-GH.description" 1285msgstr "\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." 1286msgid "SUN4U-8002-GH.response" 1287msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1288msgid "SUN4U-8002-GH.impact" 1289msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1290msgid "SUN4U-8002-GH.action" 1291msgstr "\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# 1293# code: SUN4U-8002-HC 1294# keys: fault.io.hbus fault.io.pci.device fault.io.schizo 1295# 1296msgid "SUN4U-8002-HC.type" 1297msgstr "Fault" 1298msgid "SUN4U-8002-HC.severity" 1299msgstr "Critical" 1300msgid "SUN4U-8002-HC.description" 1301msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1302msgid "SUN4U-8002-HC.response" 1303msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1304msgid "SUN4U-8002-HC.impact" 1305msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1306msgid "SUN4U-8002-HC.action" 1307msgstr "\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# 1309# code: SUN4U-8002-JQ 1310# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo 1311# 1312msgid "SUN4U-8002-JQ.type" 1313msgstr "Fault" 1314msgid "SUN4U-8002-JQ.severity" 1315msgstr "Critical" 1316msgid "SUN4U-8002-JQ.description" 1317msgstr "\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." 1318msgid "SUN4U-8002-JQ.response" 1319msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1320msgid "SUN4U-8002-JQ.impact" 1321msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1322msgid "SUN4U-8002-JQ.action" 1323msgstr "\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# 1325# code: SUN4U-8002-K4 1326# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo 1327# 1328msgid "SUN4U-8002-K4.type" 1329msgstr "Fault" 1330msgid "SUN4U-8002-K4.severity" 1331msgstr "Critical" 1332msgid "SUN4U-8002-K4.description" 1333msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1334msgid "SUN4U-8002-K4.response" 1335msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1336msgid "SUN4U-8002-K4.impact" 1337msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1338msgid "SUN4U-8002-K4.action" 1339msgstr "\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# 1341# code: SUN4U-8002-LR 1342# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo 1343# 1344msgid "SUN4U-8002-LR.type" 1345msgstr "Fault" 1346msgid "SUN4U-8002-LR.severity" 1347msgstr "Critical" 1348msgid "SUN4U-8002-LR.description" 1349msgstr "\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." 1350msgid "SUN4U-8002-LR.response" 1351msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1352msgid "SUN4U-8002-LR.impact" 1353msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1354msgid "SUN4U-8002-LR.action" 1355msgstr "\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# 1357# code: SUN4U-8002-M2 1358# keys: fault.io.datapath fault.io.hbus fault.io.schizo 1359# 1360msgid "SUN4U-8002-M2.type" 1361msgstr "Fault" 1362msgid "SUN4U-8002-M2.severity" 1363msgstr "Critical" 1364msgid "SUN4U-8002-M2.description" 1365msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1366msgid "SUN4U-8002-M2.response" 1367msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1368msgid "SUN4U-8002-M2.impact" 1369msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1370msgid "SUN4U-8002-M2.action" 1371msgstr "\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# 1373# code: SUN4U-8002-NX 1374# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo 1375# 1376msgid "SUN4U-8002-NX.type" 1377msgstr "Fault" 1378msgid "SUN4U-8002-NX.severity" 1379msgstr "Critical" 1380msgid "SUN4U-8002-NX.description" 1381msgstr "\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." 1382msgid "SUN4U-8002-NX.response" 1383msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1384msgid "SUN4U-8002-NX.impact" 1385msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1386msgid "SUN4U-8002-NX.action" 1387msgstr "\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# 1389# code: SUN4U-8002-PE 1390# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo 1391# 1392msgid "SUN4U-8002-PE.type" 1393msgstr "Fault" 1394msgid "SUN4U-8002-PE.severity" 1395msgstr "Critical" 1396msgid "SUN4U-8002-PE.description" 1397msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1398msgid "SUN4U-8002-PE.response" 1399msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1400msgid "SUN4U-8002-PE.impact" 1401msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1402msgid "SUN4U-8002-PE.action" 1403msgstr "\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# 1405# code: SUN4U-8002-QJ 1406# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo 1407# 1408msgid "SUN4U-8002-QJ.type" 1409msgstr "Fault" 1410msgid "SUN4U-8002-QJ.severity" 1411msgstr "Critical" 1412msgid "SUN4U-8002-QJ.description" 1413msgstr "\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." 1414msgid "SUN4U-8002-QJ.response" 1415msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1416msgid "SUN4U-8002-QJ.impact" 1417msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1418msgid "SUN4U-8002-QJ.action" 1419msgstr "\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# 1421# code: SUN4U-8002-RS 1422# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo 1423# 1424msgid "SUN4U-8002-RS.type" 1425msgstr "Fault" 1426msgid "SUN4U-8002-RS.severity" 1427msgstr "Critical" 1428msgid "SUN4U-8002-RS.description" 1429msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1430msgid "SUN4U-8002-RS.response" 1431msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1432msgid "SUN4U-8002-RS.impact" 1433msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1434msgid "SUN4U-8002-RS.action" 1435msgstr "\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# 1437# code: SUN4U-8002-S5 1438# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo 1439# 1440msgid "SUN4U-8002-S5.type" 1441msgstr "Fault" 1442msgid "SUN4U-8002-S5.severity" 1443msgstr "Critical" 1444msgid "SUN4U-8002-S5.description" 1445msgstr "\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." 1446msgid "SUN4U-8002-S5.response" 1447msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1448msgid "SUN4U-8002-S5.impact" 1449msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1450msgid "SUN4U-8002-S5.action" 1451msgstr "\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# 1453# code: SUN4U-8002-TP 1454# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo 1455# 1456msgid "SUN4U-8002-TP.type" 1457msgstr "Fault" 1458msgid "SUN4U-8002-TP.severity" 1459msgstr "Critical" 1460msgid "SUN4U-8002-TP.description" 1461msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1462msgid "SUN4U-8002-TP.response" 1463msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1464msgid "SUN4U-8002-TP.impact" 1465msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1466msgid "SUN4U-8002-TP.action" 1467msgstr "\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# 1469# code: SUN4U-8002-UA 1470# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo 1471# 1472msgid "SUN4U-8002-UA.type" 1473msgstr "Fault" 1474msgid "SUN4U-8002-UA.severity" 1475msgstr "Critical" 1476msgid "SUN4U-8002-UA.description" 1477msgstr "\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." 1478msgid "SUN4U-8002-UA.response" 1479msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1480msgid "SUN4U-8002-UA.impact" 1481msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1482msgid "SUN4U-8002-UA.action" 1483msgstr "\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# 1485# code: SUN4U-8002-VH 1486# keys: fault.io.xmits 1487# 1488msgid "SUN4U-8002-VH.type" 1489msgstr "Fault" 1490msgid "SUN4U-8002-VH.severity" 1491msgstr "Critical" 1492msgid "SUN4U-8002-VH.description" 1493msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1494msgid "SUN4U-8002-VH.response" 1495msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1496msgid "SUN4U-8002-VH.impact" 1497msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1498msgid "SUN4U-8002-VH.action" 1499msgstr "\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# 1501# code: SUN4U-8002-WD 1502# keys: defect.io.pci.driver fault.io.xmits 1503# 1504msgid "SUN4U-8002-WD.type" 1505msgstr "Fault" 1506msgid "SUN4U-8002-WD.severity" 1507msgstr "Critical" 1508msgid "SUN4U-8002-WD.description" 1509msgstr "\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." 1510msgid "SUN4U-8002-WD.response" 1511msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1512msgid "SUN4U-8002-WD.impact" 1513msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1514msgid "SUN4U-8002-WD.action" 1515msgstr "\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# 1517# code: SUN4U-8002-XY 1518# keys: fault.io.pci.bus fault.io.xmits 1519# 1520msgid "SUN4U-8002-XY.type" 1521msgstr "Fault" 1522msgid "SUN4U-8002-XY.severity" 1523msgstr "Critical" 1524msgid "SUN4U-8002-XY.description" 1525msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1526msgid "SUN4U-8002-XY.response" 1527msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1528msgid "SUN4U-8002-XY.impact" 1529msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1530msgid "SUN4U-8002-XY.action" 1531msgstr "\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# 1533# code: SUN4U-8002-Y3 1534# keys: defect.io.pci.driver fault.io.pci.bus fault.io.xmits 1535# 1536msgid "SUN4U-8002-Y3.type" 1537msgstr "Fault" 1538msgid "SUN4U-8002-Y3.severity" 1539msgstr "Critical" 1540msgid "SUN4U-8002-Y3.description" 1541msgstr "\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." 1542msgid "SUN4U-8002-Y3.response" 1543msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1544msgid "SUN4U-8002-Y3.impact" 1545msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1546msgid "SUN4U-8002-Y3.action" 1547msgstr "\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# 1549# code: SUN4U-8003-0Y 1550# keys: fault.io.pci.device fault.io.xmits 1551# 1552msgid "SUN4U-8003-0Y.type" 1553msgstr "Fault" 1554msgid "SUN4U-8003-0Y.severity" 1555msgstr "Critical" 1556msgid "SUN4U-8003-0Y.description" 1557msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1558msgid "SUN4U-8003-0Y.response" 1559msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1560msgid "SUN4U-8003-0Y.impact" 1561msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1562msgid "SUN4U-8003-0Y.action" 1563msgstr "\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# 1565# code: SUN4U-8003-13 1566# keys: defect.io.pci.driver fault.io.pci.device fault.io.xmits 1567# 1568msgid "SUN4U-8003-13.type" 1569msgstr "Fault" 1570msgid "SUN4U-8003-13.severity" 1571msgstr "Critical" 1572msgid "SUN4U-8003-13.description" 1573msgstr "\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." 1574msgid "SUN4U-8003-13.response" 1575msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1576msgid "SUN4U-8003-13.impact" 1577msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1578msgid "SUN4U-8003-13.action" 1579msgstr "\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# 1581# code: SUN4U-8003-2H 1582# keys: fault.io.pci.bus fault.io.pci.device fault.io.xmits 1583# 1584msgid "SUN4U-8003-2H.type" 1585msgstr "Fault" 1586msgid "SUN4U-8003-2H.severity" 1587msgstr "Critical" 1588msgid "SUN4U-8003-2H.description" 1589msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1590msgid "SUN4U-8003-2H.response" 1591msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1592msgid "SUN4U-8003-2H.impact" 1593msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1594msgid "SUN4U-8003-2H.action" 1595msgstr "\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# 1597# code: SUN4U-8003-3D 1598# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.xmits 1599# 1600msgid "SUN4U-8003-3D.type" 1601msgstr "Fault" 1602msgid "SUN4U-8003-3D.severity" 1603msgstr "Critical" 1604msgid "SUN4U-8003-3D.description" 1605msgstr "\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." 1606msgid "SUN4U-8003-3D.response" 1607msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1608msgid "SUN4U-8003-3D.impact" 1609msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1610msgid "SUN4U-8003-3D.action" 1611msgstr "\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# 1613# code: SUN4U-8003-4P 1614# keys: fault.io.datapath fault.io.xmits 1615# 1616msgid "SUN4U-8003-4P.type" 1617msgstr "Fault" 1618msgid "SUN4U-8003-4P.severity" 1619msgstr "Critical" 1620msgid "SUN4U-8003-4P.description" 1621msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1622msgid "SUN4U-8003-4P.response" 1623msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1624msgid "SUN4U-8003-4P.impact" 1625msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1626msgid "SUN4U-8003-4P.action" 1627msgstr "\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# 1629# code: SUN4U-8003-5A 1630# keys: defect.io.pci.driver fault.io.datapath fault.io.xmits 1631# 1632msgid "SUN4U-8003-5A.type" 1633msgstr "Fault" 1634msgid "SUN4U-8003-5A.severity" 1635msgstr "Critical" 1636msgid "SUN4U-8003-5A.description" 1637msgstr "\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." 1638msgid "SUN4U-8003-5A.response" 1639msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1640msgid "SUN4U-8003-5A.impact" 1641msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1642msgid "SUN4U-8003-5A.action" 1643msgstr "\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# 1645# code: SUN4U-8003-6S 1646# keys: fault.io.datapath fault.io.pci.bus fault.io.xmits 1647# 1648msgid "SUN4U-8003-6S.type" 1649msgstr "Fault" 1650msgid "SUN4U-8003-6S.severity" 1651msgstr "Critical" 1652msgid "SUN4U-8003-6S.description" 1653msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1654msgid "SUN4U-8003-6S.response" 1655msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1656msgid "SUN4U-8003-6S.impact" 1657msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1658msgid "SUN4U-8003-6S.action" 1659msgstr "\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# 1661# code: SUN4U-8003-75 1662# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.xmits 1663# 1664msgid "SUN4U-8003-75.type" 1665msgstr "Fault" 1666msgid "SUN4U-8003-75.severity" 1667msgstr "Critical" 1668msgid "SUN4U-8003-75.description" 1669msgstr "\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." 1670msgid "SUN4U-8003-75.response" 1671msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1672msgid "SUN4U-8003-75.impact" 1673msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1674msgid "SUN4U-8003-75.action" 1675msgstr "\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# 1677# code: SUN4U-8003-8E 1678# keys: fault.io.datapath fault.io.pci.device fault.io.xmits 1679# 1680msgid "SUN4U-8003-8E.type" 1681msgstr "Fault" 1682msgid "SUN4U-8003-8E.severity" 1683msgstr "Critical" 1684msgid "SUN4U-8003-8E.description" 1685msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1686msgid "SUN4U-8003-8E.response" 1687msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1688msgid "SUN4U-8003-8E.impact" 1689msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1690msgid "SUN4U-8003-8E.action" 1691msgstr "\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# 1693# code: SUN4U-8003-9J 1694# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.xmits 1695# 1696msgid "SUN4U-8003-9J.type" 1697msgstr "Fault" 1698msgid "SUN4U-8003-9J.severity" 1699msgstr "Critical" 1700msgid "SUN4U-8003-9J.description" 1701msgstr "\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." 1702msgid "SUN4U-8003-9J.response" 1703msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1704msgid "SUN4U-8003-9J.impact" 1705msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1706msgid "SUN4U-8003-9J.action" 1707msgstr "\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# 1709# code: SUN4U-8003-A2 1710# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits 1711# 1712msgid "SUN4U-8003-A2.type" 1713msgstr "Fault" 1714msgid "SUN4U-8003-A2.severity" 1715msgstr "Critical" 1716msgid "SUN4U-8003-A2.description" 1717msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1718msgid "SUN4U-8003-A2.response" 1719msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1720msgid "SUN4U-8003-A2.impact" 1721msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1722msgid "SUN4U-8003-A2.action" 1723msgstr "\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# 1725# code: SUN4U-8003-CX 1726# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits 1727# 1728msgid "SUN4U-8003-CX.type" 1729msgstr "Fault" 1730msgid "SUN4U-8003-CX.severity" 1731msgstr "Critical" 1732msgid "SUN4U-8003-CX.description" 1733msgstr "\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." 1734msgid "SUN4U-8003-CX.response" 1735msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1736msgid "SUN4U-8003-CX.impact" 1737msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1738msgid "SUN4U-8003-CX.action" 1739msgstr "\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# 1741# code: SUN4U-8003-D4 1742# keys: fault.io.hbus fault.io.xmits 1743# 1744msgid "SUN4U-8003-D4.type" 1745msgstr "Fault" 1746msgid "SUN4U-8003-D4.severity" 1747msgstr "Critical" 1748msgid "SUN4U-8003-D4.description" 1749msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1750msgid "SUN4U-8003-D4.response" 1751msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1752msgid "SUN4U-8003-D4.impact" 1753msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1754msgid "SUN4U-8003-D4.action" 1755msgstr "\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# 1757# code: SUN4U-8003-ER 1758# keys: defect.io.pci.driver fault.io.hbus fault.io.xmits 1759# 1760msgid "SUN4U-8003-ER.type" 1761msgstr "Fault" 1762msgid "SUN4U-8003-ER.severity" 1763msgstr "Critical" 1764msgid "SUN4U-8003-ER.description" 1765msgstr "\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." 1766msgid "SUN4U-8003-ER.response" 1767msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1768msgid "SUN4U-8003-ER.impact" 1769msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1770msgid "SUN4U-8003-ER.action" 1771msgstr "\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# 1773# code: SUN4U-8003-FC 1774# keys: fault.io.hbus fault.io.pci.bus fault.io.xmits 1775# 1776msgid "SUN4U-8003-FC.type" 1777msgstr "Fault" 1778msgid "SUN4U-8003-FC.severity" 1779msgstr "Critical" 1780msgid "SUN4U-8003-FC.description" 1781msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1782msgid "SUN4U-8003-FC.response" 1783msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1784msgid "SUN4U-8003-FC.impact" 1785msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1786msgid "SUN4U-8003-FC.action" 1787msgstr "\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# 1789# code: SUN4U-8003-GQ 1790# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.xmits 1791# 1792msgid "SUN4U-8003-GQ.type" 1793msgstr "Fault" 1794msgid "SUN4U-8003-GQ.severity" 1795msgstr "Critical" 1796msgid "SUN4U-8003-GQ.description" 1797msgstr "\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." 1798msgid "SUN4U-8003-GQ.response" 1799msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1800msgid "SUN4U-8003-GQ.impact" 1801msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1802msgid "SUN4U-8003-GQ.action" 1803msgstr "\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# 1805# code: SUN4U-8003-HD 1806# keys: fault.io.hbus fault.io.pci.device fault.io.xmits 1807# 1808msgid "SUN4U-8003-HD.type" 1809msgstr "Fault" 1810msgid "SUN4U-8003-HD.severity" 1811msgstr "Critical" 1812msgid "SUN4U-8003-HD.description" 1813msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1814msgid "SUN4U-8003-HD.response" 1815msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1816msgid "SUN4U-8003-HD.impact" 1817msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1818msgid "SUN4U-8003-HD.action" 1819msgstr "\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# 1821# code: SUN4U-8003-JH 1822# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.xmits 1823# 1824msgid "SUN4U-8003-JH.type" 1825msgstr "Fault" 1826msgid "SUN4U-8003-JH.severity" 1827msgstr "Critical" 1828msgid "SUN4U-8003-JH.description" 1829msgstr "\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." 1830msgid "SUN4U-8003-JH.response" 1831msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1832msgid "SUN4U-8003-JH.impact" 1833msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1834msgid "SUN4U-8003-JH.action" 1835msgstr "\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# 1837# code: SUN4U-8003-K3 1838# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits 1839# 1840msgid "SUN4U-8003-K3.type" 1841msgstr "Fault" 1842msgid "SUN4U-8003-K3.severity" 1843msgstr "Critical" 1844msgid "SUN4U-8003-K3.description" 1845msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1846msgid "SUN4U-8003-K3.response" 1847msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1848msgid "SUN4U-8003-K3.impact" 1849msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1850msgid "SUN4U-8003-K3.action" 1851msgstr "\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# 1853# code: SUN4U-8003-LY 1854# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits 1855# 1856msgid "SUN4U-8003-LY.type" 1857msgstr "Fault" 1858msgid "SUN4U-8003-LY.severity" 1859msgstr "Critical" 1860msgid "SUN4U-8003-LY.description" 1861msgstr "\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." 1862msgid "SUN4U-8003-LY.response" 1863msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1864msgid "SUN4U-8003-LY.impact" 1865msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1866msgid "SUN4U-8003-LY.action" 1867msgstr "\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# 1869# code: SUN4U-8003-M5 1870# keys: fault.io.datapath fault.io.hbus fault.io.xmits 1871# 1872msgid "SUN4U-8003-M5.type" 1873msgstr "Fault" 1874msgid "SUN4U-8003-M5.severity" 1875msgstr "Critical" 1876msgid "SUN4U-8003-M5.description" 1877msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1878msgid "SUN4U-8003-M5.response" 1879msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1880msgid "SUN4U-8003-M5.impact" 1881msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1882msgid "SUN4U-8003-M5.action" 1883msgstr "\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# 1885# code: SUN4U-8003-NS 1886# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.xmits 1887# 1888msgid "SUN4U-8003-NS.type" 1889msgstr "Fault" 1890msgid "SUN4U-8003-NS.severity" 1891msgstr "Critical" 1892msgid "SUN4U-8003-NS.description" 1893msgstr "\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." 1894msgid "SUN4U-8003-NS.response" 1895msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1896msgid "SUN4U-8003-NS.impact" 1897msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1898msgid "SUN4U-8003-NS.action" 1899msgstr "\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# 1901# code: SUN4U-8003-PA 1902# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits 1903# 1904msgid "SUN4U-8003-PA.type" 1905msgstr "Fault" 1906msgid "SUN4U-8003-PA.severity" 1907msgstr "Critical" 1908msgid "SUN4U-8003-PA.description" 1909msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1910msgid "SUN4U-8003-PA.response" 1911msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1912msgid "SUN4U-8003-PA.impact" 1913msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1914msgid "SUN4U-8003-PA.action" 1915msgstr "\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# 1917# code: SUN4U-8003-QP 1918# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits 1919# 1920msgid "SUN4U-8003-QP.type" 1921msgstr "Fault" 1922msgid "SUN4U-8003-QP.severity" 1923msgstr "Critical" 1924msgid "SUN4U-8003-QP.description" 1925msgstr "\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." 1926msgid "SUN4U-8003-QP.response" 1927msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1928msgid "SUN4U-8003-QP.impact" 1929msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1930msgid "SUN4U-8003-QP.action" 1931msgstr "\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# 1933# code: SUN4U-8003-RX 1934# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits 1935# 1936msgid "SUN4U-8003-RX.type" 1937msgstr "Fault" 1938msgid "SUN4U-8003-RX.severity" 1939msgstr "Critical" 1940msgid "SUN4U-8003-RX.description" 1941msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1942msgid "SUN4U-8003-RX.response" 1943msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1944msgid "SUN4U-8003-RX.impact" 1945msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1946msgid "SUN4U-8003-RX.action" 1947msgstr "\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# 1949# code: SUN4U-8003-S2 1950# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits 1951# 1952msgid "SUN4U-8003-S2.type" 1953msgstr "Fault" 1954msgid "SUN4U-8003-S2.severity" 1955msgstr "Critical" 1956msgid "SUN4U-8003-S2.description" 1957msgstr "\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." 1958msgid "SUN4U-8003-S2.response" 1959msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1960msgid "SUN4U-8003-S2.impact" 1961msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1962msgid "SUN4U-8003-S2.action" 1963msgstr "\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# 1965# code: SUN4U-8003-TJ 1966# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits 1967# 1968msgid "SUN4U-8003-TJ.type" 1969msgstr "Fault" 1970msgid "SUN4U-8003-TJ.severity" 1971msgstr "Critical" 1972msgid "SUN4U-8003-TJ.description" 1973msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 1974msgid "SUN4U-8003-TJ.response" 1975msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1976msgid "SUN4U-8003-TJ.impact" 1977msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1978msgid "SUN4U-8003-TJ.action" 1979msgstr "\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# 1981# code: SUN4U-8003-UE 1982# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits 1983# 1984msgid "SUN4U-8003-UE.type" 1985msgstr "Fault" 1986msgid "SUN4U-8003-UE.severity" 1987msgstr "Critical" 1988msgid "SUN4U-8003-UE.description" 1989msgstr "\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." 1990msgid "SUN4U-8003-UE.response" 1991msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 1992msgid "SUN4U-8003-UE.impact" 1993msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 1994msgid "SUN4U-8003-UE.action" 1995msgstr "\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# 1997# code: SUN4U-8003-VQ 1998# keys: fault.io.schizo fault.io.xmits 1999# 2000msgid "SUN4U-8003-VQ.type" 2001msgstr "Fault" 2002msgid "SUN4U-8003-VQ.severity" 2003msgstr "Critical" 2004msgid "SUN4U-8003-VQ.description" 2005msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2006msgid "SUN4U-8003-VQ.response" 2007msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2008msgid "SUN4U-8003-VQ.impact" 2009msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2010msgid "SUN4U-8003-VQ.action" 2011msgstr "\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# 2013# code: SUN4U-8003-WC 2014# keys: defect.io.pci.driver fault.io.schizo fault.io.xmits 2015# 2016msgid "SUN4U-8003-WC.type" 2017msgstr "Fault" 2018msgid "SUN4U-8003-WC.severity" 2019msgstr "Critical" 2020msgid "SUN4U-8003-WC.description" 2021msgstr "\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." 2022msgid "SUN4U-8003-WC.response" 2023msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2024msgid "SUN4U-8003-WC.impact" 2025msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2026msgid "SUN4U-8003-WC.action" 2027msgstr "\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# 2029# code: SUN4U-8003-XR 2030# keys: fault.io.pci.bus fault.io.schizo fault.io.xmits 2031# 2032msgid "SUN4U-8003-XR.type" 2033msgstr "Fault" 2034msgid "SUN4U-8003-XR.severity" 2035msgstr "Critical" 2036msgid "SUN4U-8003-XR.description" 2037msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2038msgid "SUN4U-8003-XR.response" 2039msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2040msgid "SUN4U-8003-XR.impact" 2041msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2042msgid "SUN4U-8003-XR.action" 2043msgstr "\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# 2045# code: SUN4U-8003-Y4 2046# keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo fault.io.xmits 2047# 2048msgid "SUN4U-8003-Y4.type" 2049msgstr "Fault" 2050msgid "SUN4U-8003-Y4.severity" 2051msgstr "Critical" 2052msgid "SUN4U-8003-Y4.description" 2053msgstr "\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." 2054msgid "SUN4U-8003-Y4.response" 2055msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2056msgid "SUN4U-8003-Y4.impact" 2057msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2058msgid "SUN4U-8003-Y4.action" 2059msgstr "\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# 2061# code: SUN4U-8004-0A 2062# keys: fault.io.pci.device fault.io.schizo fault.io.xmits 2063# 2064msgid "SUN4U-8004-0A.type" 2065msgstr "Fault" 2066msgid "SUN4U-8004-0A.severity" 2067msgstr "Critical" 2068msgid "SUN4U-8004-0A.description" 2069msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2070msgid "SUN4U-8004-0A.response" 2071msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2072msgid "SUN4U-8004-0A.impact" 2073msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2074msgid "SUN4U-8004-0A.action" 2075msgstr "\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# 2077# code: SUN4U-8004-1P 2078# keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo fault.io.xmits 2079# 2080msgid "SUN4U-8004-1P.type" 2081msgstr "Fault" 2082msgid "SUN4U-8004-1P.severity" 2083msgstr "Critical" 2084msgid "SUN4U-8004-1P.description" 2085msgstr "\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." 2086msgid "SUN4U-8004-1P.response" 2087msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2088msgid "SUN4U-8004-1P.impact" 2089msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2090msgid "SUN4U-8004-1P.action" 2091msgstr "\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# 2093# code: SUN4U-8004-25 2094# keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits 2095# 2096msgid "SUN4U-8004-25.type" 2097msgstr "Fault" 2098msgid "SUN4U-8004-25.severity" 2099msgstr "Critical" 2100msgid "SUN4U-8004-25.description" 2101msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2102msgid "SUN4U-8004-25.response" 2103msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2104msgid "SUN4U-8004-25.impact" 2105msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2106msgid "SUN4U-8004-25.action" 2107msgstr "\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# 2109# code: SUN4U-8004-3S 2110# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits 2111# 2112msgid "SUN4U-8004-3S.type" 2113msgstr "Fault" 2114msgid "SUN4U-8004-3S.severity" 2115msgstr "Critical" 2116msgid "SUN4U-8004-3S.description" 2117msgstr "\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." 2118msgid "SUN4U-8004-3S.response" 2119msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2120msgid "SUN4U-8004-3S.impact" 2121msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2122msgid "SUN4U-8004-3S.action" 2123msgstr "\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# 2125# code: SUN4U-8004-43 2126# keys: fault.io.datapath fault.io.schizo fault.io.xmits 2127# 2128msgid "SUN4U-8004-43.type" 2129msgstr "Fault" 2130msgid "SUN4U-8004-43.severity" 2131msgstr "Critical" 2132msgid "SUN4U-8004-43.description" 2133msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2134msgid "SUN4U-8004-43.response" 2135msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2136msgid "SUN4U-8004-43.impact" 2137msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2138msgid "SUN4U-8004-43.action" 2139msgstr "\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# 2141# code: SUN4U-8004-5Y 2142# keys: defect.io.pci.driver fault.io.datapath fault.io.schizo fault.io.xmits 2143# 2144msgid "SUN4U-8004-5Y.type" 2145msgstr "Fault" 2146msgid "SUN4U-8004-5Y.severity" 2147msgstr "Critical" 2148msgid "SUN4U-8004-5Y.description" 2149msgstr "\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." 2150msgid "SUN4U-8004-5Y.response" 2151msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2152msgid "SUN4U-8004-5Y.impact" 2153msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2154msgid "SUN4U-8004-5Y.action" 2155msgstr "\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# 2157# code: SUN4U-8004-6D 2158# keys: fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits 2159# 2160msgid "SUN4U-8004-6D.type" 2161msgstr "Fault" 2162msgid "SUN4U-8004-6D.severity" 2163msgstr "Critical" 2164msgid "SUN4U-8004-6D.description" 2165msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2166msgid "SUN4U-8004-6D.response" 2167msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2168msgid "SUN4U-8004-6D.impact" 2169msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2170msgid "SUN4U-8004-6D.action" 2171msgstr "\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# 2173# code: SUN4U-8004-7H 2174# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits 2175# 2176msgid "SUN4U-8004-7H.type" 2177msgstr "Fault" 2178msgid "SUN4U-8004-7H.severity" 2179msgstr "Critical" 2180msgid "SUN4U-8004-7H.description" 2181msgstr "\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." 2182msgid "SUN4U-8004-7H.response" 2183msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2184msgid "SUN4U-8004-7H.impact" 2185msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2186msgid "SUN4U-8004-7H.action" 2187msgstr "\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# 2189# code: SUN4U-8004-8R 2190# keys: fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits 2191# 2192msgid "SUN4U-8004-8R.type" 2193msgstr "Fault" 2194msgid "SUN4U-8004-8R.severity" 2195msgstr "Critical" 2196msgid "SUN4U-8004-8R.description" 2197msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2198msgid "SUN4U-8004-8R.response" 2199msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2200msgid "SUN4U-8004-8R.impact" 2201msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2202msgid "SUN4U-8004-8R.action" 2203msgstr "\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# 2205# code: SUN4U-8004-94 2206# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits 2207# 2208msgid "SUN4U-8004-94.type" 2209msgstr "Fault" 2210msgid "SUN4U-8004-94.severity" 2211msgstr "Critical" 2212msgid "SUN4U-8004-94.description" 2213msgstr "\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." 2214msgid "SUN4U-8004-94.response" 2215msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2216msgid "SUN4U-8004-94.impact" 2217msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2218msgid "SUN4U-8004-94.action" 2219msgstr "\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# 2221# code: SUN4U-8004-AQ 2222# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits 2223# 2224msgid "SUN4U-8004-AQ.type" 2225msgstr "Fault" 2226msgid "SUN4U-8004-AQ.severity" 2227msgstr "Critical" 2228msgid "SUN4U-8004-AQ.description" 2229msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2230msgid "SUN4U-8004-AQ.response" 2231msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2232msgid "SUN4U-8004-AQ.impact" 2233msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2234msgid "SUN4U-8004-AQ.action" 2235msgstr "\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# 2237# code: SUN4U-8004-CC 2238# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits 2239# 2240msgid "SUN4U-8004-CC.type" 2241msgstr "Fault" 2242msgid "SUN4U-8004-CC.severity" 2243msgstr "Critical" 2244msgid "SUN4U-8004-CC.description" 2245msgstr "\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." 2246msgid "SUN4U-8004-CC.response" 2247msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2248msgid "SUN4U-8004-CC.impact" 2249msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2250msgid "SUN4U-8004-CC.action" 2251msgstr "\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# 2253# code: SUN4U-8004-DJ 2254# keys: fault.io.hbus fault.io.schizo fault.io.xmits 2255# 2256msgid "SUN4U-8004-DJ.type" 2257msgstr "Fault" 2258msgid "SUN4U-8004-DJ.severity" 2259msgstr "Critical" 2260msgid "SUN4U-8004-DJ.description" 2261msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2262msgid "SUN4U-8004-DJ.response" 2263msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2264msgid "SUN4U-8004-DJ.impact" 2265msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2266msgid "SUN4U-8004-DJ.action" 2267msgstr "\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# 2269# code: SUN4U-8004-EE 2270# keys: defect.io.pci.driver fault.io.hbus fault.io.schizo fault.io.xmits 2271# 2272msgid "SUN4U-8004-EE.type" 2273msgstr "Fault" 2274msgid "SUN4U-8004-EE.severity" 2275msgstr "Critical" 2276msgid "SUN4U-8004-EE.description" 2277msgstr "\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." 2278msgid "SUN4U-8004-EE.response" 2279msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2280msgid "SUN4U-8004-EE.impact" 2281msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2282msgid "SUN4U-8004-EE.action" 2283msgstr "\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# 2285# code: SUN4U-8004-FX 2286# keys: fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits 2287# 2288msgid "SUN4U-8004-FX.type" 2289msgstr "Fault" 2290msgid "SUN4U-8004-FX.severity" 2291msgstr "Critical" 2292msgid "SUN4U-8004-FX.description" 2293msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2294msgid "SUN4U-8004-FX.response" 2295msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2296msgid "SUN4U-8004-FX.impact" 2297msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2298msgid "SUN4U-8004-FX.action" 2299msgstr "\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# 2301# code: SUN4U-8004-G2 2302# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits 2303# 2304msgid "SUN4U-8004-G2.type" 2305msgstr "Fault" 2306msgid "SUN4U-8004-G2.severity" 2307msgstr "Critical" 2308msgid "SUN4U-8004-G2.description" 2309msgstr "\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." 2310msgid "SUN4U-8004-G2.response" 2311msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2312msgid "SUN4U-8004-G2.impact" 2313msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2314msgid "SUN4U-8004-G2.action" 2315msgstr "\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# 2317# code: SUN4U-8004-HS 2318# keys: fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits 2319# 2320msgid "SUN4U-8004-HS.type" 2321msgstr "Fault" 2322msgid "SUN4U-8004-HS.severity" 2323msgstr "Critical" 2324msgid "SUN4U-8004-HS.description" 2325msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2326msgid "SUN4U-8004-HS.response" 2327msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2328msgid "SUN4U-8004-HS.impact" 2329msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2330msgid "SUN4U-8004-HS.action" 2331msgstr "\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# 2333# code: SUN4U-8004-J5 2334# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits 2335# 2336msgid "SUN4U-8004-J5.type" 2337msgstr "Fault" 2338msgid "SUN4U-8004-J5.severity" 2339msgstr "Critical" 2340msgid "SUN4U-8004-J5.description" 2341msgstr "\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." 2342msgid "SUN4U-8004-J5.response" 2343msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2344msgid "SUN4U-8004-J5.impact" 2345msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2346msgid "SUN4U-8004-J5.action" 2347msgstr "\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# 2349# code: SUN4U-8004-KP 2350# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits 2351# 2352msgid "SUN4U-8004-KP.type" 2353msgstr "Fault" 2354msgid "SUN4U-8004-KP.severity" 2355msgstr "Critical" 2356msgid "SUN4U-8004-KP.description" 2357msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2358msgid "SUN4U-8004-KP.response" 2359msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2360msgid "SUN4U-8004-KP.impact" 2361msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2362msgid "SUN4U-8004-KP.action" 2363msgstr "\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# 2365# code: SUN4U-8004-LA 2366# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits 2367# 2368msgid "SUN4U-8004-LA.type" 2369msgstr "Fault" 2370msgid "SUN4U-8004-LA.severity" 2371msgstr "Critical" 2372msgid "SUN4U-8004-LA.description" 2373msgstr "\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." 2374msgid "SUN4U-8004-LA.response" 2375msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2376msgid "SUN4U-8004-LA.impact" 2377msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2378msgid "SUN4U-8004-LA.action" 2379msgstr "\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# 2381# code: SUN4U-8004-MH 2382# keys: fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits 2383# 2384msgid "SUN4U-8004-MH.type" 2385msgstr "Fault" 2386msgid "SUN4U-8004-MH.severity" 2387msgstr "Critical" 2388msgid "SUN4U-8004-MH.description" 2389msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2390msgid "SUN4U-8004-MH.response" 2391msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2392msgid "SUN4U-8004-MH.impact" 2393msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2394msgid "SUN4U-8004-MH.action" 2395msgstr "\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# 2397# code: SUN4U-8004-ND 2398# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits 2399# 2400msgid "SUN4U-8004-ND.type" 2401msgstr "Fault" 2402msgid "SUN4U-8004-ND.severity" 2403msgstr "Critical" 2404msgid "SUN4U-8004-ND.description" 2405msgstr "\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." 2406msgid "SUN4U-8004-ND.response" 2407msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2408msgid "SUN4U-8004-ND.impact" 2409msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2410msgid "SUN4U-8004-ND.action" 2411msgstr "\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# 2413# code: SUN4U-8004-PY 2414# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits 2415# 2416msgid "SUN4U-8004-PY.type" 2417msgstr "Fault" 2418msgid "SUN4U-8004-PY.severity" 2419msgstr "Critical" 2420msgid "SUN4U-8004-PY.description" 2421msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2422msgid "SUN4U-8004-PY.response" 2423msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2424msgid "SUN4U-8004-PY.impact" 2425msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2426msgid "SUN4U-8004-PY.action" 2427msgstr "\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# 2429# code: SUN4U-8004-Q3 2430# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits 2431# 2432msgid "SUN4U-8004-Q3.type" 2433msgstr "Fault" 2434msgid "SUN4U-8004-Q3.severity" 2435msgstr "Critical" 2436msgid "SUN4U-8004-Q3.description" 2437msgstr "\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." 2438msgid "SUN4U-8004-Q3.response" 2439msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2440msgid "SUN4U-8004-Q3.impact" 2441msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2442msgid "SUN4U-8004-Q3.action" 2443msgstr "\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# 2445# code: SUN4U-8004-RC 2446# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits 2447# 2448msgid "SUN4U-8004-RC.type" 2449msgstr "Fault" 2450msgid "SUN4U-8004-RC.severity" 2451msgstr "Critical" 2452msgid "SUN4U-8004-RC.description" 2453msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2454msgid "SUN4U-8004-RC.response" 2455msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2456msgid "SUN4U-8004-RC.impact" 2457msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2458msgid "SUN4U-8004-RC.action" 2459msgstr "\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# 2461# code: SUN4U-8004-SQ 2462# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits 2463# 2464msgid "SUN4U-8004-SQ.type" 2465msgstr "Fault" 2466msgid "SUN4U-8004-SQ.severity" 2467msgstr "Critical" 2468msgid "SUN4U-8004-SQ.description" 2469msgstr "\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." 2470msgid "SUN4U-8004-SQ.response" 2471msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2472msgid "SUN4U-8004-SQ.impact" 2473msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2474msgid "SUN4U-8004-SQ.action" 2475msgstr "\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# 2477# code: SUN4U-8004-T4 2478# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits 2479# 2480msgid "SUN4U-8004-T4.type" 2481msgstr "Fault" 2482msgid "SUN4U-8004-T4.severity" 2483msgstr "Critical" 2484msgid "SUN4U-8004-T4.description" 2485msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2486msgid "SUN4U-8004-T4.response" 2487msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2488msgid "SUN4U-8004-T4.impact" 2489msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2490msgid "SUN4U-8004-T4.action" 2491msgstr "\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# 2493# code: SUN4U-8004-UR 2494# 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# 2496msgid "SUN4U-8004-UR.type" 2497msgstr "Fault" 2498msgid "SUN4U-8004-UR.severity" 2499msgstr "Critical" 2500msgid "SUN4U-8004-UR.description" 2501msgstr "\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." 2502msgid "SUN4U-8004-UR.response" 2503msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2504msgid "SUN4U-8004-UR.impact" 2505msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2506msgid "SUN4U-8004-UR.action" 2507msgstr "\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# 2509# code: SUN4U-8004-V2 2510# keys: fault.io.psycho 2511# 2512msgid "SUN4U-8004-V2.type" 2513msgstr "Fault" 2514msgid "SUN4U-8004-V2.severity" 2515msgstr "Critical" 2516msgid "SUN4U-8004-V2.description" 2517msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2518msgid "SUN4U-8004-V2.response" 2519msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2520msgid "SUN4U-8004-V2.impact" 2521msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2522msgid "SUN4U-8004-V2.action" 2523msgstr "\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# 2525# code: SUN4U-8004-WX 2526# keys: defect.io.pci.driver fault.io.psycho 2527# 2528msgid "SUN4U-8004-WX.type" 2529msgstr "Fault" 2530msgid "SUN4U-8004-WX.severity" 2531msgstr "Critical" 2532msgid "SUN4U-8004-WX.description" 2533msgstr "\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." 2534msgid "SUN4U-8004-WX.response" 2535msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2536msgid "SUN4U-8004-WX.impact" 2537msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2538msgid "SUN4U-8004-WX.action" 2539msgstr "\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# 2541# code: SUN4U-8004-XE 2542# keys: fault.io.datapath fault.io.psycho 2543# 2544msgid "SUN4U-8004-XE.type" 2545msgstr "Fault" 2546msgid "SUN4U-8004-XE.severity" 2547msgstr "Critical" 2548msgid "SUN4U-8004-XE.description" 2549msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2550msgid "SUN4U-8004-XE.response" 2551msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2552msgid "SUN4U-8004-XE.impact" 2553msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2554msgid "SUN4U-8004-XE.action" 2555msgstr "\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# 2557# code: SUN4U-8004-YJ 2558# keys: defect.io.pci.driver fault.io.datapath fault.io.psycho 2559# 2560msgid "SUN4U-8004-YJ.type" 2561msgstr "Fault" 2562msgid "SUN4U-8004-YJ.severity" 2563msgstr "Critical" 2564msgid "SUN4U-8004-YJ.description" 2565msgstr "\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." 2566msgid "SUN4U-8004-YJ.response" 2567msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2568msgid "SUN4U-8004-YJ.impact" 2569msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2570msgid "SUN4U-8004-YJ.action" 2571msgstr "\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# 2573# code: SUN4U-8005-0E 2574# keys: fault.io.hbus fault.io.psycho 2575# 2576msgid "SUN4U-8005-0E.type" 2577msgstr "Fault" 2578msgid "SUN4U-8005-0E.severity" 2579msgstr "Critical" 2580msgid "SUN4U-8005-0E.description" 2581msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2582msgid "SUN4U-8005-0E.response" 2583msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2584msgid "SUN4U-8005-0E.impact" 2585msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2586msgid "SUN4U-8005-0E.action" 2587msgstr "\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# 2589# code: SUN4U-8005-1J 2590# keys: defect.io.pci.driver fault.io.hbus fault.io.psycho 2591# 2592msgid "SUN4U-8005-1J.type" 2593msgstr "Fault" 2594msgid "SUN4U-8005-1J.severity" 2595msgstr "Critical" 2596msgid "SUN4U-8005-1J.description" 2597msgstr "\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." 2598msgid "SUN4U-8005-1J.response" 2599msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2600msgid "SUN4U-8005-1J.impact" 2601msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2602msgid "SUN4U-8005-1J.action" 2603msgstr "\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# 2605# code: SUN4U-8005-22 2606# keys: fault.io.datapath fault.io.hbus fault.io.psycho 2607# 2608msgid "SUN4U-8005-22.type" 2609msgstr "Fault" 2610msgid "SUN4U-8005-22.severity" 2611msgstr "Critical" 2612msgid "SUN4U-8005-22.description" 2613msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2614msgid "SUN4U-8005-22.response" 2615msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2616msgid "SUN4U-8005-22.impact" 2617msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2618msgid "SUN4U-8005-22.action" 2619msgstr "\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# 2621# code: SUN4U-8005-3X 2622# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.psycho 2623# 2624msgid "SUN4U-8005-3X.type" 2625msgstr "Fault" 2626msgid "SUN4U-8005-3X.severity" 2627msgstr "Critical" 2628msgid "SUN4U-8005-3X.description" 2629msgstr "\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." 2630msgid "SUN4U-8005-3X.response" 2631msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2632msgid "SUN4U-8005-3X.impact" 2633msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2634msgid "SUN4U-8005-3X.action" 2635msgstr "\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# 2637# code: SUN4U-8005-44 2638# keys: fault.io.pci.bus fault.io.psycho 2639# 2640msgid "SUN4U-8005-44.type" 2641msgstr "Fault" 2642msgid "SUN4U-8005-44.severity" 2643msgstr "Critical" 2644msgid "SUN4U-8005-44.description" 2645msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2646msgid "SUN4U-8005-44.response" 2647msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2648msgid "SUN4U-8005-44.impact" 2649msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2650msgid "SUN4U-8005-44.action" 2651msgstr "\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# 2653# code: SUN4U-8005-5R 2654# keys: defect.io.pci.driver fault.io.pci.bus fault.io.psycho 2655# 2656msgid "SUN4U-8005-5R.type" 2657msgstr "Fault" 2658msgid "SUN4U-8005-5R.severity" 2659msgstr "Critical" 2660msgid "SUN4U-8005-5R.description" 2661msgstr "\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." 2662msgid "SUN4U-8005-5R.response" 2663msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2664msgid "SUN4U-8005-5R.impact" 2665msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2666msgid "SUN4U-8005-5R.action" 2667msgstr "\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# 2669# code: SUN4U-8005-6C 2670# keys: fault.io.datapath fault.io.pci.bus fault.io.psycho 2671# 2672msgid "SUN4U-8005-6C.type" 2673msgstr "Fault" 2674msgid "SUN4U-8005-6C.severity" 2675msgstr "Critical" 2676msgid "SUN4U-8005-6C.description" 2677msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2678msgid "SUN4U-8005-6C.response" 2679msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2680msgid "SUN4U-8005-6C.impact" 2681msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2682msgid "SUN4U-8005-6C.action" 2683msgstr "\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# 2685# code: SUN4U-8005-7Q 2686# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.psycho 2687# 2688msgid "SUN4U-8005-7Q.type" 2689msgstr "Fault" 2690msgid "SUN4U-8005-7Q.severity" 2691msgstr "Critical" 2692msgid "SUN4U-8005-7Q.description" 2693msgstr "\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." 2694msgid "SUN4U-8005-7Q.response" 2695msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2696msgid "SUN4U-8005-7Q.impact" 2697msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2698msgid "SUN4U-8005-7Q.action" 2699msgstr "\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# 2701# code: SUN4U-8005-8Y 2702# keys: fault.io.hbus fault.io.pci.bus fault.io.psycho 2703# 2704msgid "SUN4U-8005-8Y.type" 2705msgstr "Fault" 2706msgid "SUN4U-8005-8Y.severity" 2707msgstr "Critical" 2708msgid "SUN4U-8005-8Y.description" 2709msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2710msgid "SUN4U-8005-8Y.response" 2711msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2712msgid "SUN4U-8005-8Y.impact" 2713msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2714msgid "SUN4U-8005-8Y.action" 2715msgstr "\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# 2717# code: SUN4U-8005-93 2718# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.psycho 2719# 2720msgid "SUN4U-8005-93.type" 2721msgstr "Fault" 2722msgid "SUN4U-8005-93.severity" 2723msgstr "Critical" 2724msgid "SUN4U-8005-93.description" 2725msgstr "\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." 2726msgid "SUN4U-8005-93.response" 2727msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2728msgid "SUN4U-8005-93.impact" 2729msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2730msgid "SUN4U-8005-93.action" 2731msgstr "\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# 2733# code: SUN4U-8005-AH 2734# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho 2735# 2736msgid "SUN4U-8005-AH.type" 2737msgstr "Fault" 2738msgid "SUN4U-8005-AH.severity" 2739msgstr "Critical" 2740msgid "SUN4U-8005-AH.description" 2741msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2742msgid "SUN4U-8005-AH.response" 2743msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2744msgid "SUN4U-8005-AH.impact" 2745msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2746msgid "SUN4U-8005-AH.action" 2747msgstr "\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# 2749# code: SUN4U-8005-CD 2750# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho 2751# 2752msgid "SUN4U-8005-CD.type" 2753msgstr "Fault" 2754msgid "SUN4U-8005-CD.severity" 2755msgstr "Critical" 2756msgid "SUN4U-8005-CD.description" 2757msgstr "\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." 2758msgid "SUN4U-8005-CD.response" 2759msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2760msgid "SUN4U-8005-CD.impact" 2761msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2762msgid "SUN4U-8005-CD.action" 2763msgstr "\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# 2765# code: SUN4U-8005-DP 2766# keys: fault.io.pci.device fault.io.psycho 2767# 2768msgid "SUN4U-8005-DP.type" 2769msgstr "Fault" 2770msgid "SUN4U-8005-DP.severity" 2771msgstr "Critical" 2772msgid "SUN4U-8005-DP.description" 2773msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2774msgid "SUN4U-8005-DP.response" 2775msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2776msgid "SUN4U-8005-DP.impact" 2777msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2778msgid "SUN4U-8005-DP.action" 2779msgstr "\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# 2781# code: SUN4U-8005-EA 2782# keys: defect.io.pci.driver fault.io.pci.device fault.io.psycho 2783# 2784msgid "SUN4U-8005-EA.type" 2785msgstr "Fault" 2786msgid "SUN4U-8005-EA.severity" 2787msgstr "Critical" 2788msgid "SUN4U-8005-EA.description" 2789msgstr "\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." 2790msgid "SUN4U-8005-EA.response" 2791msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2792msgid "SUN4U-8005-EA.impact" 2793msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2794msgid "SUN4U-8005-EA.action" 2795msgstr "\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# 2797# code: SUN4U-8005-FS 2798# keys: fault.io.datapath fault.io.pci.device fault.io.psycho 2799# 2800msgid "SUN4U-8005-FS.type" 2801msgstr "Fault" 2802msgid "SUN4U-8005-FS.severity" 2803msgstr "Critical" 2804msgid "SUN4U-8005-FS.description" 2805msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2806msgid "SUN4U-8005-FS.response" 2807msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2808msgid "SUN4U-8005-FS.impact" 2809msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2810msgid "SUN4U-8005-FS.action" 2811msgstr "\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# 2813# code: SUN4U-8005-G5 2814# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.psycho 2815# 2816msgid "SUN4U-8005-G5.type" 2817msgstr "Fault" 2818msgid "SUN4U-8005-G5.severity" 2819msgstr "Critical" 2820msgid "SUN4U-8005-G5.description" 2821msgstr "\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." 2822msgid "SUN4U-8005-G5.response" 2823msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2824msgid "SUN4U-8005-G5.impact" 2825msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2826msgid "SUN4U-8005-G5.action" 2827msgstr "\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# 2829# code: SUN4U-8005-HX 2830# keys: fault.io.hbus fault.io.pci.device fault.io.psycho 2831# 2832msgid "SUN4U-8005-HX.type" 2833msgstr "Fault" 2834msgid "SUN4U-8005-HX.severity" 2835msgstr "Critical" 2836msgid "SUN4U-8005-HX.description" 2837msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2838msgid "SUN4U-8005-HX.response" 2839msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2840msgid "SUN4U-8005-HX.impact" 2841msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2842msgid "SUN4U-8005-HX.action" 2843msgstr "\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# 2845# code: SUN4U-8005-J2 2846# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.psycho 2847# 2848msgid "SUN4U-8005-J2.type" 2849msgstr "Fault" 2850msgid "SUN4U-8005-J2.severity" 2851msgstr "Critical" 2852msgid "SUN4U-8005-J2.description" 2853msgstr "\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." 2854msgid "SUN4U-8005-J2.response" 2855msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2856msgid "SUN4U-8005-J2.impact" 2857msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2858msgid "SUN4U-8005-J2.action" 2859msgstr "\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# 2861# code: SUN4U-8005-KJ 2862# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho 2863# 2864msgid "SUN4U-8005-KJ.type" 2865msgstr "Fault" 2866msgid "SUN4U-8005-KJ.severity" 2867msgstr "Critical" 2868msgid "SUN4U-8005-KJ.description" 2869msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2870msgid "SUN4U-8005-KJ.response" 2871msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2872msgid "SUN4U-8005-KJ.impact" 2873msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2874msgid "SUN4U-8005-KJ.action" 2875msgstr "\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# 2877# code: SUN4U-8005-LE 2878# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho 2879# 2880msgid "SUN4U-8005-LE.type" 2881msgstr "Fault" 2882msgid "SUN4U-8005-LE.severity" 2883msgstr "Critical" 2884msgid "SUN4U-8005-LE.description" 2885msgstr "\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." 2886msgid "SUN4U-8005-LE.response" 2887msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2888msgid "SUN4U-8005-LE.impact" 2889msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2890msgid "SUN4U-8005-LE.action" 2891msgstr "\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# 2893# code: SUN4U-8005-MQ 2894# keys: fault.io.pci.bus fault.io.pci.device fault.io.psycho 2895# 2896msgid "SUN4U-8005-MQ.type" 2897msgstr "Fault" 2898msgid "SUN4U-8005-MQ.severity" 2899msgstr "Critical" 2900msgid "SUN4U-8005-MQ.description" 2901msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2902msgid "SUN4U-8005-MQ.response" 2903msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2904msgid "SUN4U-8005-MQ.impact" 2905msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2906msgid "SUN4U-8005-MQ.action" 2907msgstr "\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# 2909# code: SUN4U-8005-NC 2910# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.psycho 2911# 2912msgid "SUN4U-8005-NC.type" 2913msgstr "Fault" 2914msgid "SUN4U-8005-NC.severity" 2915msgstr "Critical" 2916msgid "SUN4U-8005-NC.description" 2917msgstr "\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." 2918msgid "SUN4U-8005-NC.response" 2919msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2920msgid "SUN4U-8005-NC.impact" 2921msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2922msgid "SUN4U-8005-NC.action" 2923msgstr "\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# 2925# code: SUN4U-8005-PR 2926# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho 2927# 2928msgid "SUN4U-8005-PR.type" 2929msgstr "Fault" 2930msgid "SUN4U-8005-PR.severity" 2931msgstr "Critical" 2932msgid "SUN4U-8005-PR.description" 2933msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2934msgid "SUN4U-8005-PR.response" 2935msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2936msgid "SUN4U-8005-PR.impact" 2937msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2938msgid "SUN4U-8005-PR.action" 2939msgstr "\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# 2941# code: SUN4U-8005-Q4 2942# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho 2943# 2944msgid "SUN4U-8005-Q4.type" 2945msgstr "Fault" 2946msgid "SUN4U-8005-Q4.severity" 2947msgstr "Critical" 2948msgid "SUN4U-8005-Q4.description" 2949msgstr "\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." 2950msgid "SUN4U-8005-Q4.response" 2951msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2952msgid "SUN4U-8005-Q4.impact" 2953msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2954msgid "SUN4U-8005-Q4.action" 2955msgstr "\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# 2957# code: SUN4U-8005-RD 2958# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho 2959# 2960msgid "SUN4U-8005-RD.type" 2961msgstr "Fault" 2962msgid "SUN4U-8005-RD.severity" 2963msgstr "Critical" 2964msgid "SUN4U-8005-RD.description" 2965msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2966msgid "SUN4U-8005-RD.response" 2967msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2968msgid "SUN4U-8005-RD.impact" 2969msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2970msgid "SUN4U-8005-RD.action" 2971msgstr "\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# 2973# code: SUN4U-8005-SH 2974# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho 2975# 2976msgid "SUN4U-8005-SH.type" 2977msgstr "Fault" 2978msgid "SUN4U-8005-SH.severity" 2979msgstr "Critical" 2980msgid "SUN4U-8005-SH.description" 2981msgstr "\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." 2982msgid "SUN4U-8005-SH.response" 2983msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 2984msgid "SUN4U-8005-SH.impact" 2985msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 2986msgid "SUN4U-8005-SH.action" 2987msgstr "\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# 2989# code: SUN4U-8005-T3 2990# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho 2991# 2992msgid "SUN4U-8005-T3.type" 2993msgstr "Fault" 2994msgid "SUN4U-8005-T3.severity" 2995msgstr "Critical" 2996msgid "SUN4U-8005-T3.description" 2997msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 2998msgid "SUN4U-8005-T3.response" 2999msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3000msgid "SUN4U-8005-T3.impact" 3001msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3002msgid "SUN4U-8005-T3.action" 3003msgstr "\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# 3005# code: SUN4U-8005-UY 3006# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho 3007# 3008msgid "SUN4U-8005-UY.type" 3009msgstr "Fault" 3010msgid "SUN4U-8005-UY.severity" 3011msgstr "Critical" 3012msgid "SUN4U-8005-UY.description" 3013msgstr "\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." 3014msgid "SUN4U-8005-UY.response" 3015msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3016msgid "SUN4U-8005-UY.impact" 3017msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3018msgid "SUN4U-8005-UY.action" 3019msgstr "\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# 3021# code: SUN4U-8005-V5 3022# keys: fault.io.tomatillo 3023# 3024msgid "SUN4U-8005-V5.type" 3025msgstr "Fault" 3026msgid "SUN4U-8005-V5.severity" 3027msgstr "Critical" 3028msgid "SUN4U-8005-V5.description" 3029msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3030msgid "SUN4U-8005-V5.response" 3031msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3032msgid "SUN4U-8005-V5.impact" 3033msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3034msgid "SUN4U-8005-V5.action" 3035msgstr "\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# 3037# code: SUN4U-8005-WS 3038# keys: defect.io.pci.driver fault.io.tomatillo 3039# 3040msgid "SUN4U-8005-WS.type" 3041msgstr "Fault" 3042msgid "SUN4U-8005-WS.severity" 3043msgstr "Critical" 3044msgid "SUN4U-8005-WS.description" 3045msgstr "\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." 3046msgid "SUN4U-8005-WS.response" 3047msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3048msgid "SUN4U-8005-WS.impact" 3049msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3050msgid "SUN4U-8005-WS.action" 3051msgstr "\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# 3053# code: SUN4U-8005-XA 3054# keys: fault.io.datapath fault.io.tomatillo 3055# 3056msgid "SUN4U-8005-XA.type" 3057msgstr "Fault" 3058msgid "SUN4U-8005-XA.severity" 3059msgstr "Critical" 3060msgid "SUN4U-8005-XA.description" 3061msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3062msgid "SUN4U-8005-XA.response" 3063msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3064msgid "SUN4U-8005-XA.impact" 3065msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3066msgid "SUN4U-8005-XA.action" 3067msgstr "\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# 3069# code: SUN4U-8005-YP 3070# keys: defect.io.pci.driver fault.io.datapath fault.io.tomatillo 3071# 3072msgid "SUN4U-8005-YP.type" 3073msgstr "Fault" 3074msgid "SUN4U-8005-YP.severity" 3075msgstr "Critical" 3076msgid "SUN4U-8005-YP.description" 3077msgstr "\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." 3078msgid "SUN4U-8005-YP.response" 3079msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3080msgid "SUN4U-8005-YP.impact" 3081msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3082msgid "SUN4U-8005-YP.action" 3083msgstr "\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# 3085# code: SUN4U-8006-04 3086# keys: fault.io.hbus fault.io.tomatillo 3087# 3088msgid "SUN4U-8006-04.type" 3089msgstr "Fault" 3090msgid "SUN4U-8006-04.severity" 3091msgstr "Critical" 3092msgid "SUN4U-8006-04.description" 3093msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3094msgid "SUN4U-8006-04.response" 3095msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3096msgid "SUN4U-8006-04.impact" 3097msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3098msgid "SUN4U-8006-04.action" 3099msgstr "\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# 3101# code: SUN4U-8006-1R 3102# keys: defect.io.pci.driver fault.io.hbus fault.io.tomatillo 3103# 3104msgid "SUN4U-8006-1R.type" 3105msgstr "Fault" 3106msgid "SUN4U-8006-1R.severity" 3107msgstr "Critical" 3108msgid "SUN4U-8006-1R.description" 3109msgstr "\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." 3110msgid "SUN4U-8006-1R.response" 3111msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3112msgid "SUN4U-8006-1R.impact" 3113msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3114msgid "SUN4U-8006-1R.action" 3115msgstr "\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# 3117# code: SUN4U-8006-2C 3118# keys: fault.io.datapath fault.io.hbus fault.io.tomatillo 3119# 3120msgid "SUN4U-8006-2C.type" 3121msgstr "Fault" 3122msgid "SUN4U-8006-2C.severity" 3123msgstr "Critical" 3124msgid "SUN4U-8006-2C.description" 3125msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3126msgid "SUN4U-8006-2C.response" 3127msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3128msgid "SUN4U-8006-2C.impact" 3129msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3130msgid "SUN4U-8006-2C.action" 3131msgstr "\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# 3133# code: SUN4U-8006-3Q 3134# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.tomatillo 3135# 3136msgid "SUN4U-8006-3Q.type" 3137msgstr "Fault" 3138msgid "SUN4U-8006-3Q.severity" 3139msgstr "Critical" 3140msgid "SUN4U-8006-3Q.description" 3141msgstr "\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." 3142msgid "SUN4U-8006-3Q.response" 3143msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3144msgid "SUN4U-8006-3Q.impact" 3145msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3146msgid "SUN4U-8006-3Q.action" 3147msgstr "\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# 3149# code: SUN4U-8006-4E 3150# keys: fault.io.pci.bus fault.io.tomatillo 3151# 3152msgid "SUN4U-8006-4E.type" 3153msgstr "Fault" 3154msgid "SUN4U-8006-4E.severity" 3155msgstr "Critical" 3156msgid "SUN4U-8006-4E.description" 3157msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3158msgid "SUN4U-8006-4E.response" 3159msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3160msgid "SUN4U-8006-4E.impact" 3161msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3162msgid "SUN4U-8006-4E.action" 3163msgstr "\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# 3165# code: SUN4U-8006-5J 3166# keys: defect.io.pci.driver fault.io.pci.bus fault.io.tomatillo 3167# 3168msgid "SUN4U-8006-5J.type" 3169msgstr "Fault" 3170msgid "SUN4U-8006-5J.severity" 3171msgstr "Critical" 3172msgid "SUN4U-8006-5J.description" 3173msgstr "\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." 3174msgid "SUN4U-8006-5J.response" 3175msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3176msgid "SUN4U-8006-5J.impact" 3177msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3178msgid "SUN4U-8006-5J.action" 3179msgstr "\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# 3181# code: SUN4U-8006-62 3182# keys: fault.io.datapath fault.io.pci.bus fault.io.tomatillo 3183# 3184msgid "SUN4U-8006-62.type" 3185msgstr "Fault" 3186msgid "SUN4U-8006-62.severity" 3187msgstr "Critical" 3188msgid "SUN4U-8006-62.description" 3189msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3190msgid "SUN4U-8006-62.response" 3191msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3192msgid "SUN4U-8006-62.impact" 3193msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3194msgid "SUN4U-8006-62.action" 3195msgstr "\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# 3197# code: SUN4U-8006-7X 3198# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.tomatillo 3199# 3200msgid "SUN4U-8006-7X.type" 3201msgstr "Fault" 3202msgid "SUN4U-8006-7X.severity" 3203msgstr "Critical" 3204msgid "SUN4U-8006-7X.description" 3205msgstr "\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." 3206msgid "SUN4U-8006-7X.response" 3207msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3208msgid "SUN4U-8006-7X.impact" 3209msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3210msgid "SUN4U-8006-7X.action" 3211msgstr "\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# 3213# code: SUN4U-8006-8P 3214# keys: fault.io.hbus fault.io.pci.bus fault.io.tomatillo 3215# 3216msgid "SUN4U-8006-8P.type" 3217msgstr "Fault" 3218msgid "SUN4U-8006-8P.severity" 3219msgstr "Critical" 3220msgid "SUN4U-8006-8P.description" 3221msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3222msgid "SUN4U-8006-8P.response" 3223msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3224msgid "SUN4U-8006-8P.impact" 3225msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3226msgid "SUN4U-8006-8P.action" 3227msgstr "\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# 3229# code: SUN4U-8006-9A 3230# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.tomatillo 3231# 3232msgid "SUN4U-8006-9A.type" 3233msgstr "Fault" 3234msgid "SUN4U-8006-9A.severity" 3235msgstr "Critical" 3236msgid "SUN4U-8006-9A.description" 3237msgstr "\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." 3238msgid "SUN4U-8006-9A.response" 3239msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3240msgid "SUN4U-8006-9A.impact" 3241msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3242msgid "SUN4U-8006-9A.action" 3243msgstr "\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# 3245# code: SUN4U-8006-AS 3246# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo 3247# 3248msgid "SUN4U-8006-AS.type" 3249msgstr "Fault" 3250msgid "SUN4U-8006-AS.severity" 3251msgstr "Critical" 3252msgid "SUN4U-8006-AS.description" 3253msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3254msgid "SUN4U-8006-AS.response" 3255msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3256msgid "SUN4U-8006-AS.impact" 3257msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3258msgid "SUN4U-8006-AS.action" 3259msgstr "\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# 3261# code: SUN4U-8006-C5 3262# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo 3263# 3264msgid "SUN4U-8006-C5.type" 3265msgstr "Fault" 3266msgid "SUN4U-8006-C5.severity" 3267msgstr "Critical" 3268msgid "SUN4U-8006-C5.description" 3269msgstr "\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." 3270msgid "SUN4U-8006-C5.response" 3271msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3272msgid "SUN4U-8006-C5.impact" 3273msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3274msgid "SUN4U-8006-C5.action" 3275msgstr "\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# 3277# code: SUN4U-8006-DY 3278# keys: fault.io.pci.device fault.io.tomatillo 3279# 3280msgid "SUN4U-8006-DY.type" 3281msgstr "Fault" 3282msgid "SUN4U-8006-DY.severity" 3283msgstr "Critical" 3284msgid "SUN4U-8006-DY.description" 3285msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3286msgid "SUN4U-8006-DY.response" 3287msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3288msgid "SUN4U-8006-DY.impact" 3289msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3290msgid "SUN4U-8006-DY.action" 3291msgstr "\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# 3293# code: SUN4U-8006-E3 3294# keys: defect.io.pci.driver fault.io.pci.device fault.io.tomatillo 3295# 3296msgid "SUN4U-8006-E3.type" 3297msgstr "Fault" 3298msgid "SUN4U-8006-E3.severity" 3299msgstr "Critical" 3300msgid "SUN4U-8006-E3.description" 3301msgstr "\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." 3302msgid "SUN4U-8006-E3.response" 3303msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3304msgid "SUN4U-8006-E3.impact" 3305msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3306msgid "SUN4U-8006-E3.action" 3307msgstr "\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# 3309# code: SUN4U-8006-FH 3310# keys: fault.io.datapath fault.io.pci.device fault.io.tomatillo 3311# 3312msgid "SUN4U-8006-FH.type" 3313msgstr "Fault" 3314msgid "SUN4U-8006-FH.severity" 3315msgstr "Critical" 3316msgid "SUN4U-8006-FH.description" 3317msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3318msgid "SUN4U-8006-FH.response" 3319msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3320msgid "SUN4U-8006-FH.impact" 3321msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3322msgid "SUN4U-8006-FH.action" 3323msgstr "\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# 3325# code: SUN4U-8006-GD 3326# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.tomatillo 3327# 3328msgid "SUN4U-8006-GD.type" 3329msgstr "Fault" 3330msgid "SUN4U-8006-GD.severity" 3331msgstr "Critical" 3332msgid "SUN4U-8006-GD.description" 3333msgstr "\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." 3334msgid "SUN4U-8006-GD.response" 3335msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3336msgid "SUN4U-8006-GD.impact" 3337msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3338msgid "SUN4U-8006-GD.action" 3339msgstr "\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# 3341# code: SUN4U-8006-HQ 3342# keys: fault.io.hbus fault.io.pci.device fault.io.tomatillo 3343# 3344msgid "SUN4U-8006-HQ.type" 3345msgstr "Fault" 3346msgid "SUN4U-8006-HQ.severity" 3347msgstr "Critical" 3348msgid "SUN4U-8006-HQ.description" 3349msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3350msgid "SUN4U-8006-HQ.response" 3351msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3352msgid "SUN4U-8006-HQ.impact" 3353msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3354msgid "SUN4U-8006-HQ.action" 3355msgstr "\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# 3357# code: SUN4U-8006-JC 3358# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.tomatillo 3359# 3360msgid "SUN4U-8006-JC.type" 3361msgstr "Fault" 3362msgid "SUN4U-8006-JC.severity" 3363msgstr "Critical" 3364msgid "SUN4U-8006-JC.description" 3365msgstr "\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." 3366msgid "SUN4U-8006-JC.response" 3367msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3368msgid "SUN4U-8006-JC.impact" 3369msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3370msgid "SUN4U-8006-JC.action" 3371msgstr "\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# 3373# code: SUN4U-8006-KR 3374# keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo 3375# 3376msgid "SUN4U-8006-KR.type" 3377msgstr "Fault" 3378msgid "SUN4U-8006-KR.severity" 3379msgstr "Critical" 3380msgid "SUN4U-8006-KR.description" 3381msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3382msgid "SUN4U-8006-KR.response" 3383msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3384msgid "SUN4U-8006-KR.impact" 3385msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3386msgid "SUN4U-8006-KR.action" 3387msgstr "\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# 3389# code: SUN4U-8006-L4 3390# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo 3391# 3392msgid "SUN4U-8006-L4.type" 3393msgstr "Fault" 3394msgid "SUN4U-8006-L4.severity" 3395msgstr "Critical" 3396msgid "SUN4U-8006-L4.description" 3397msgstr "\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." 3398msgid "SUN4U-8006-L4.response" 3399msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3400msgid "SUN4U-8006-L4.impact" 3401msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3402msgid "SUN4U-8006-L4.action" 3403msgstr "\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# 3405# code: SUN4U-8006-MX 3406# keys: fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3407# 3408msgid "SUN4U-8006-MX.type" 3409msgstr "Fault" 3410msgid "SUN4U-8006-MX.severity" 3411msgstr "Critical" 3412msgid "SUN4U-8006-MX.description" 3413msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3414msgid "SUN4U-8006-MX.response" 3415msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3416msgid "SUN4U-8006-MX.impact" 3417msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3418msgid "SUN4U-8006-MX.action" 3419msgstr "\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# 3421# code: SUN4U-8006-N2 3422# keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3423# 3424msgid "SUN4U-8006-N2.type" 3425msgstr "Fault" 3426msgid "SUN4U-8006-N2.severity" 3427msgstr "Critical" 3428msgid "SUN4U-8006-N2.description" 3429msgstr "\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." 3430msgid "SUN4U-8006-N2.response" 3431msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3432msgid "SUN4U-8006-N2.impact" 3433msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3434msgid "SUN4U-8006-N2.action" 3435msgstr "\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# 3437# code: SUN4U-8006-PJ 3438# keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3439# 3440msgid "SUN4U-8006-PJ.type" 3441msgstr "Fault" 3442msgid "SUN4U-8006-PJ.severity" 3443msgstr "Critical" 3444msgid "SUN4U-8006-PJ.description" 3445msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3446msgid "SUN4U-8006-PJ.response" 3447msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3448msgid "SUN4U-8006-PJ.impact" 3449msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3450msgid "SUN4U-8006-PJ.action" 3451msgstr "\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# 3453# code: SUN4U-8006-QE 3454# keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3455# 3456msgid "SUN4U-8006-QE.type" 3457msgstr "Fault" 3458msgid "SUN4U-8006-QE.severity" 3459msgstr "Critical" 3460msgid "SUN4U-8006-QE.description" 3461msgstr "\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." 3462msgid "SUN4U-8006-QE.response" 3463msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3464msgid "SUN4U-8006-QE.impact" 3465msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3466msgid "SUN4U-8006-QE.action" 3467msgstr "\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# 3469# code: SUN4U-8006-R5 3470# keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3471# 3472msgid "SUN4U-8006-R5.type" 3473msgstr "Fault" 3474msgid "SUN4U-8006-R5.severity" 3475msgstr "Critical" 3476msgid "SUN4U-8006-R5.description" 3477msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3478msgid "SUN4U-8006-R5.response" 3479msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3480msgid "SUN4U-8006-R5.impact" 3481msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3482msgid "SUN4U-8006-R5.action" 3483msgstr "\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# 3485# code: SUN4U-8006-SS 3486# keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3487# 3488msgid "SUN4U-8006-SS.type" 3489msgstr "Fault" 3490msgid "SUN4U-8006-SS.severity" 3491msgstr "Critical" 3492msgid "SUN4U-8006-SS.description" 3493msgstr "\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." 3494msgid "SUN4U-8006-SS.response" 3495msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3496msgid "SUN4U-8006-SS.impact" 3497msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3498msgid "SUN4U-8006-SS.action" 3499msgstr "\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# 3501# code: SUN4U-8006-TA 3502# keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3503# 3504msgid "SUN4U-8006-TA.type" 3505msgstr "Fault" 3506msgid "SUN4U-8006-TA.severity" 3507msgstr "Critical" 3508msgid "SUN4U-8006-TA.description" 3509msgstr "\nA problem was detected in a system core bus.\n Refer to %s for more information." 3510msgid "SUN4U-8006-TA.response" 3511msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3512msgid "SUN4U-8006-TA.impact" 3513msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3514msgid "SUN4U-8006-TA.action" 3515msgstr "\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# 3517# code: SUN4U-8006-UP 3518# keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo 3519# 3520msgid "SUN4U-8006-UP.type" 3521msgstr "Fault" 3522msgid "SUN4U-8006-UP.severity" 3523msgstr "Critical" 3524msgid "SUN4U-8006-UP.description" 3525msgstr "\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." 3526msgid "SUN4U-8006-UP.response" 3527msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3528msgid "SUN4U-8006-UP.impact" 3529msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3530msgid "SUN4U-8006-UP.action" 3531msgstr "\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# 3533# code: SUN4U-8006-VD 3534# keys: fault.cpu.ultraSPARC-IIIiplus.dcache 3535# 3536msgid "SUN4U-8006-VD.type" 3537msgstr "Fault" 3538msgid "SUN4U-8006-VD.severity" 3539msgstr "Major" 3540msgid "SUN4U-8006-VD.description" 3541msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." 3542msgid "SUN4U-8006-VD.response" 3543msgstr "The fault manager will attempt to remove the affected CPU from service." 3544msgid "SUN4U-8006-VD.impact" 3545msgstr "System performance may be affected." 3546msgid "SUN4U-8006-VD.action" 3547msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 3548# 3549# code: SUN4U-8006-WH 3550# keys: fault.cpu.ultraSPARC-IIIiplus.icache 3551# 3552msgid "SUN4U-8006-WH.type" 3553msgstr "Fault" 3554msgid "SUN4U-8006-WH.severity" 3555msgstr "Major" 3556msgid "SUN4U-8006-WH.description" 3557msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." 3558msgid "SUN4U-8006-WH.response" 3559msgstr "The fault manager will attempt to remove the affected CPU from service." 3560msgid "SUN4U-8006-WH.impact" 3561msgstr "System performance may be affected." 3562msgid "SUN4U-8006-WH.action" 3563msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 3564# 3565# code: SUN4U-8006-X3 3566# keys: fault.cpu.ultraSPARC-IIIiplus.l2cachedata 3567# 3568msgid "SUN4U-8006-X3.type" 3569msgstr "Fault" 3570msgid "SUN4U-8006-X3.severity" 3571msgstr "Major" 3572msgid "SUN4U-8006-X3.description" 3573msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." 3574msgid "SUN4U-8006-X3.response" 3575msgstr "The fault manager will attempt to remove the affected CPU from service." 3576msgid "SUN4U-8006-X3.impact" 3577msgstr "System performance may be affected." 3578msgid "SUN4U-8006-X3.action" 3579msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 3580# 3581# code: SUN4U-8006-YY 3582# keys: fault.cpu.ultraSPARC-IIIiplus.l2cachetag 3583# 3584msgid "SUN4U-8006-YY.type" 3585msgstr "Fault" 3586msgid "SUN4U-8006-YY.severity" 3587msgstr "Major" 3588msgid "SUN4U-8006-YY.description" 3589msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." 3590msgid "SUN4U-8006-YY.response" 3591msgstr "The fault manager will attempt to remove the affected CPU from service." 3592msgid "SUN4U-8006-YY.impact" 3593msgstr "System performance may be affected." 3594msgid "SUN4U-8006-YY.action" 3595msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 3596# 3597# code: SUN4U-8007-03 3598# keys: fault.cpu.ultraSPARC-IIIiplus.fpu 3599# 3600msgid "SUN4U-8007-03.type" 3601msgstr "Fault" 3602msgid "SUN4U-8007-03.severity" 3603msgstr "Major" 3604msgid "SUN4U-8007-03.description" 3605msgstr "The number of errors associated with a CPU has exceeded acceptable levels. Refer to %s for more information." 3606msgid "SUN4U-8007-03.response" 3607msgstr "The fault manager will attempt to remove the affected CPU from service." 3608msgid "SUN4U-8007-03.impact" 3609msgstr "System performance may be affected." 3610msgid "SUN4U-8007-03.action" 3611msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>." 3612# 3613# code: SUN4U-8007-1Y 3614# keys: fault.asic.cds.dp 3615# 3616msgid "SUN4U-8007-1Y.type" 3617msgstr "Fault" 3618msgid "SUN4U-8007-1Y.severity" 3619msgstr "Critical" 3620msgid "SUN4U-8007-1Y.description" 3621msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." 3622msgid "SUN4U-8007-1Y.response" 3623msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" 3624msgid "SUN4U-8007-1Y.impact" 3625msgstr "System performace may be affected.\n" 3626msgid "SUN4U-8007-1Y.action" 3627msgstr "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# 3629# code: SUN4U-8007-2D 3630# keys: fault.asic.dx.dp 3631# 3632msgid "SUN4U-8007-2D.type" 3633msgstr "Fault" 3634msgid "SUN4U-8007-2D.severity" 3635msgstr "Critical" 3636msgid "SUN4U-8007-2D.description" 3637msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." 3638msgid "SUN4U-8007-2D.response" 3639msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" 3640msgid "SUN4U-8007-2D.impact" 3641msgstr "System performace may be affected.\n" 3642msgid "SUN4U-8007-2D.action" 3643msgstr "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# 3645# code: SUN4U-8007-3H 3646# keys: fault.asic.sdi.dp 3647# 3648msgid "SUN4U-8007-3H.type" 3649msgstr "Fault" 3650msgid "SUN4U-8007-3H.severity" 3651msgstr "Critical" 3652msgid "SUN4U-8007-3H.description" 3653msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." 3654msgid "SUN4U-8007-3H.response" 3655msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" 3656msgid "SUN4U-8007-3H.impact" 3657msgstr "System performace may be affected.\n" 3658msgid "SUN4U-8007-3H.action" 3659msgstr "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# 3661# code: SUN4U-8007-4A 3662# keys: fault.asic.cp.dp 3663# 3664msgid "SUN4U-8007-4A.type" 3665msgstr "Fault" 3666msgid "SUN4U-8007-4A.severity" 3667msgstr "Critical" 3668msgid "SUN4U-8007-4A.description" 3669msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." 3670msgid "SUN4U-8007-4A.response" 3671msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" 3672msgid "SUN4U-8007-4A.impact" 3673msgstr "System performace may be affected.\n" 3674msgid "SUN4U-8007-4A.action" 3675msgstr "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# 3677# code: SUN4U-8007-5P 3678# keys: fault.asic.rp.dp 3679# 3680msgid "SUN4U-8007-5P.type" 3681msgstr "Fault" 3682msgid "SUN4U-8007-5P.severity" 3683msgstr "Critical" 3684msgid "SUN4U-8007-5P.description" 3685msgstr "A hardware problem was detected on the datapath interconnect.\n Refer to %s for more information." 3686msgid "SUN4U-8007-5P.response" 3687msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n" 3688msgid "SUN4U-8007-5P.impact" 3689msgstr "System performace may be affected.\n" 3690msgid "SUN4U-8007-5P.action" 3691msgstr "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# 3693# code: SUN4U-8007-65 3694# keys: fault.io.oberon 3695# 3696msgid "SUN4U-8007-65.type" 3697msgstr "Fault" 3698msgid "SUN4U-8007-65.severity" 3699msgstr "Critical" 3700msgid "SUN4U-8007-65.description" 3701msgstr "Oberon PCI-Express hostbridge fault\n Refer to %s for more information." 3702msgid "SUN4U-8007-65.response" 3703msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent." 3704msgid "SUN4U-8007-65.impact" 3705msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime." 3706msgid "SUN4U-8007-65.action" 3707msgstr "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# 3709# code: SUN4U-8007-7S 3710# keys: fault.cpu.SPARC64-VI.chip 3711# 3712msgid "SUN4U-8007-7S.type" 3713msgstr "Fault" 3714msgid "SUN4U-8007-7S.severity" 3715msgstr "Critical" 3716msgid "SUN4U-8007-7S.description" 3717msgstr "The number of errors associated with this CHIP has exceeded acceptable levels. Refer to %s for more information." 3718msgid "SUN4U-8007-7S.response" 3719msgstr "An attempt will be made to remove the affected CHIP from service." 3720msgid "SUN4U-8007-7S.impact" 3721msgstr "The system will not be functioning at the same performance level with the CHIP removal." 3722msgid "SUN4U-8007-7S.action" 3723msgstr "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# 3725# code: SUN4U-8007-8J 3726# keys: fault.cpu.SPARC64-VI.core 3727# 3728msgid "SUN4U-8007-8J.type" 3729msgstr "Fault" 3730msgid "SUN4U-8007-8J.severity" 3731msgstr "Critical" 3732msgid "SUN4U-8007-8J.description" 3733msgstr "The number of errors associated with this CORE has exceeded acceptable levels. Refer to %s for more information." 3734msgid "SUN4U-8007-8J.response" 3735msgstr "An attempt will be made to remove the affected CORE from service." 3736msgid "SUN4U-8007-8J.impact" 3737msgstr "The system will not be functioning at the same performance level with the CORE removal." 3738msgid "SUN4U-8007-8J.action" 3739msgstr "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# 3741# code: SUN4U-8007-9E 3742# keys: fault.cpu.SPARC64-VI.strand 3743# 3744msgid "SUN4U-8007-9E.type" 3745msgstr "Fault" 3746msgid "SUN4U-8007-9E.severity" 3747msgstr "Critical" 3748msgid "SUN4U-8007-9E.description" 3749msgstr "The number of errors associated with this STRAND has exceeded acceptable levels. Refer to %s for more information." 3750msgid "SUN4U-8007-9E.response" 3751msgstr "An attempt will be made to remove the affected STRAND from service." 3752msgid "SUN4U-8007-9E.impact" 3753msgstr "The system will not be functioning at the same performance level with the STRAND removal." 3754msgid "SUN4U-8007-9E.action" 3755msgstr "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# 3757# code: SUN4U-8007-AX 3758# keys: fault.io.pci.device-invreq fault.io.tomatillo 3759# 3760msgid "SUN4U-8007-AX.type" 3761msgstr "Fault" 3762msgid "SUN4U-8007-AX.severity" 3763msgstr "Critical" 3764msgid "SUN4U-8007-AX.description" 3765msgstr "Either the transmitting device sent an invalid request or the receiving device failed to respond.\n Refer to %s for more information." 3766msgid "SUN4U-8007-AX.response" 3767msgstr "One or more device instances may be disabled\n" 3768msgid "SUN4U-8007-AX.impact" 3769msgstr "Loss of services provided by the device instances associated with this fault\n" 3770msgid "SUN4U-8007-AX.action" 3771msgstr "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# 3773# code: SUN4U-8007-C2 3774# keys: fault.cpu.SPARC64-VII.chip 3775# 3776msgid "SUN4U-8007-C2.type" 3777msgstr "Fault" 3778msgid "SUN4U-8007-C2.severity" 3779msgstr "Critical" 3780msgid "SUN4U-8007-C2.description" 3781msgstr "The number of errors associated with this CHIP has exceeded acceptable levels. Refer to %s for more information." 3782msgid "SUN4U-8007-C2.response" 3783msgstr "An attempt will be made to remove the affected CHIP from service." 3784msgid "SUN4U-8007-C2.impact" 3785msgstr "The system will not be functioning at the same performance level with the CHIP removal." 3786msgid "SUN4U-8007-C2.action" 3787msgstr "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# 3789# code: SUN4U-8007-DR 3790# keys: fault.cpu.SPARC64-VII.core 3791# 3792msgid "SUN4U-8007-DR.type" 3793msgstr "Fault" 3794msgid "SUN4U-8007-DR.severity" 3795msgstr "Critical" 3796msgid "SUN4U-8007-DR.description" 3797msgstr "The number of errors associated with this CORE has exceeded acceptable levels. Refer to %s for more information." 3798msgid "SUN4U-8007-DR.response" 3799msgstr "An attempt will be made to remove the affected CORE from service." 3800msgid "SUN4U-8007-DR.impact" 3801msgstr "The system will not be functioning at the same performance level with the CORE removal." 3802msgid "SUN4U-8007-DR.action" 3803msgstr "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# 3805# code: SUN4U-8007-E4 3806# keys: fault.cpu.SPARC64-VII.strand 3807# 3808msgid "SUN4U-8007-E4.type" 3809msgstr "Fault" 3810msgid "SUN4U-8007-E4.severity" 3811msgstr "Critical" 3812msgid "SUN4U-8007-E4.description" 3813msgstr "The number of errors associated with this STRAND has exceeded acceptable levels. Refer to %s for more information." 3814msgid "SUN4U-8007-E4.response" 3815msgstr "An attempt will be made to remove the affected STRAND from service." 3816msgid "SUN4U-8007-E4.impact" 3817msgstr "The system will not be functioning at the same performance level with the STRAND removal." 3818msgid "SUN4U-8007-E4.action" 3819msgstr "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# 3821# code: SUN4U-8007-FQ 3822# keys: fault.cpu.ultraSPARC-IVplus.l2cachedata-line 3823# 3824msgid "SUN4U-8007-FQ.type" 3825msgstr "Fault" 3826msgid "SUN4U-8007-FQ.severity" 3827msgstr "Minor" 3828msgid "SUN4U-8007-FQ.description" 3829msgstr "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." 3830msgid "SUN4U-8007-FQ.response" 3831msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" 3832msgid "SUN4U-8007-FQ.impact" 3833msgstr "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" 3834msgid "SUN4U-8007-FQ.action" 3835msgstr "No repair action is recommended at this time.\n" 3836# 3837# code: SUN4U-8007-GC 3838# keys: fault.cpu.ultraSPARC-IVplus.l3cachedata-line 3839# 3840msgid "SUN4U-8007-GC.type" 3841msgstr "Fault" 3842msgid "SUN4U-8007-GC.severity" 3843msgstr "Minor" 3844msgid "SUN4U-8007-GC.description" 3845msgstr "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." 3846msgid "SUN4U-8007-GC.response" 3847msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" 3848msgid "SUN4U-8007-GC.impact" 3849msgstr "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" 3850msgid "SUN4U-8007-GC.action" 3851msgstr "No repair action is recommended at this time.\n" 3852# 3853# code: SUN4U-8007-HH 3854# keys: fault.cpu.ultraSPARC-IVplus.l2cachetag-line 3855# 3856msgid "SUN4U-8007-HH.type" 3857msgstr "Fault" 3858msgid "SUN4U-8007-HH.severity" 3859msgstr "Minor" 3860msgid "SUN4U-8007-HH.description" 3861msgstr "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." 3862msgid "SUN4U-8007-HH.response" 3863msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" 3864msgid "SUN4U-8007-HH.impact" 3865msgstr "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" 3866msgid "SUN4U-8007-HH.action" 3867msgstr "No repair action is recommended at this time.\n" 3868# 3869# code: SUN4U-8007-JD 3870# keys: fault.cpu.ultraSPARC-IVplus.l3cachetag-line 3871# 3872msgid "SUN4U-8007-JD.type" 3873msgstr "Fault" 3874msgid "SUN4U-8007-JD.severity" 3875msgstr "Minor" 3876msgid "SUN4U-8007-JD.description" 3877msgstr "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." 3878msgid "SUN4U-8007-JD.response" 3879msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n" 3880msgid "SUN4U-8007-JD.impact" 3881msgstr "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" 3882msgid "SUN4U-8007-JD.action" 3883msgstr "No repair action is recommended at this time.\n" 3884