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