8490 Remove Sun/Solaris references from FMA messages
Reviewed by: Jason King <jason.king@joyent.com>
Reviewed by: Elijah Zupancic <elijah.zupancic@joyent.com>
Reviewed by: Robert Mustacchi <rm@joyent.com>
Reviewed by: Jerry Jelinek <jerry.jelinek@joyent.com>

          --- old/usr/src/cmd/fm/dicts/SUN4U.po
          +++ new/usr/src/cmd/fm/dicts/SUN4U.po

   1    1  #
   2    2  # Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
   3    3  # Use is subject to license terms.
   4    4  #
   5    5  # CDDL HEADER START
   6    6  #
   7    7  # The contents of this file are subject to the terms of the
   8    8  # Common Development and Distribution License (the "License").
   9    9  # You may not use this file except in compliance with the License.
  10   10  #
  11   11  # You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
  12   12  # or http://www.opensolaris.org/os/licensing.
  13   13  # See the License for the specific language governing permissions
  14   14  # and limitations under the License.
  15   15  #
  16   16  # When distributing Covered Code, include this CDDL HEADER in each
  17   17  # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
  18   18  # If applicable, add the following below this CDDL HEADER, with the
  19   19  # fields enclosed by brackets "[]" replaced with your own identifying
  20   20  # information: Portions Copyright [yyyy] [name of copyright owner]
  21   21  #
  22   22  # CDDL HEADER END
  23   23  #
  24   24  #
  25   25  # DO NOT EDIT -- this file is generated by the Event Registry.
  26   26  #
  27   27  #
  28   28  # code: SUN4U-8000-1A
  29   29  # keys: fault.memory.page
  30   30  #
  31   31  msgid "SUN4U-8000-1A.type"
  32   32  msgstr "Fault"
  33   33  msgid "SUN4U-8000-1A.severity"
  34   34  msgstr "Minor"
  35   35  msgid "SUN4U-8000-1A.description"
  36   36  msgstr "The number of errors associated with this memory module continues to exceed acceptable levels.  Refer to %s for more information."
  37   37  msgid "SUN4U-8000-1A.response"
  38   38  msgstr "An attempt will be made to remove this memory page from service."
  39   39  msgid "SUN4U-8000-1A.impact"
  40   40  msgstr "The performance of the system may be minimally impacted as a result of removing the memory page from operation."
  41   41  msgid "SUN4U-8000-1A.action"
  42   42  msgstr "No repair action is recommended at this time."
  43   43  #
  44   44  # code: SUN4U-8000-2S
  45   45  # keys: fault.memory.dimm
  46   46  #
  47   47  msgid "SUN4U-8000-2S.type"
  48   48  msgstr "Fault"
  49   49  msgid "SUN4U-8000-2S.severity"
  50   50  msgstr "Major"
  51   51  msgid "SUN4U-8000-2S.description"
  52   52  msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels.  Refer to %s for more information."
  53   53  msgid "SUN4U-8000-2S.response"
  54   54  msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached."
  55   55  msgid "SUN4U-8000-2S.impact"
  56   56  msgstr "Total system memory capacity has been reduced."
  57   57  msgid "SUN4U-8000-2S.action"
  58   58  msgstr "Schedule a repair procedure to replace the affected memory module. Use 'fmadm faulty' to identify the memory module."
  59   59  #
  60   60  # code: SUN4U-8000-35
  61   61  # keys: fault.memory.bank
  62   62  #
  63   63  msgid "SUN4U-8000-35.type"
  64   64  msgstr "Fault"
  65   65  msgid "SUN4U-8000-35.severity"
  66   66  msgstr "Critical"
  67   67  msgid "SUN4U-8000-35.description"
  68   68  msgstr "The number of errors associated with this memory module has exceeded acceptable levels.  Refer to %s for more information."
  69   69  msgid "SUN4U-8000-35.response"
  70   70  msgstr "Pages of memory associated with this memory module are being removed from service as errors are reported."
  71   71  msgid "SUN4U-8000-35.impact"
  72   72  msgstr "Total system memory capacity will be reduced as pages are retired."
  73   73  msgid "SUN4U-8000-35.action"
  74   74  msgstr "Schedule a repair procedure to replace the affected memory module. Use fmdump -v -u <EVENT_ID> to identify the module."
  75   75  #
  76   76  # code: SUN4U-8000-4Y
  77   77  # keys: fault.cpu.ultraSPARC-III.dcache
  78   78  #
  79   79  msgid "SUN4U-8000-4Y.type"
  80   80  msgstr "Fault"
  81   81  msgid "SUN4U-8000-4Y.severity"
  82   82  msgstr "Major"
  83   83  msgid "SUN4U-8000-4Y.description"
  84   84  msgstr "The number of errors associated with a CPU has exceeded acceptable levels.  Refer to %s for more information."
  85   85  msgid "SUN4U-8000-4Y.response"
  86   86  msgstr "The fault manager will attempt to remove the affected CPU from service."
  87   87  msgid "SUN4U-8000-4Y.impact"
  88   88  msgstr "System performance may be affected."
  89   89  msgid "SUN4U-8000-4Y.action"
  90   90  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
  91   91  #
  92   92  # code: SUN4U-8000-53
  93   93  # keys: fault.cpu.ultraSPARC-III.icache
  94   94  #
  95   95  msgid "SUN4U-8000-53.type"
  96   96  msgstr "Fault"
  97   97  msgid "SUN4U-8000-53.severity"
  98   98  msgstr "Major"
  99   99  msgid "SUN4U-8000-53.description"
 100  100  msgstr "The number of errors associated with a CPU has exceeded acceptable levels.  Refer to %s for more information."
 101  101  msgid "SUN4U-8000-53.response"
 102  102  msgstr "The fault manager will attempt to remove the affected CPU from service."
 103  103  msgid "SUN4U-8000-53.impact"
 104  104  msgstr "System performance may be affected."
 105  105  msgid "SUN4U-8000-53.action"
 106  106  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 107  107  #
 108  108  # code: SUN4U-8000-6H
 109  109  # keys: fault.cpu.ultraSPARC-III.l2cachedata
 110  110  #
 111  111  msgid "SUN4U-8000-6H.type"
 112  112  msgstr "Fault"
 113  113  msgid "SUN4U-8000-6H.severity"
 114  114  msgstr "Major"
 115  115  msgid "SUN4U-8000-6H.description"
 116  116  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 117  117  msgid "SUN4U-8000-6H.response"
 118  118  msgstr "The fault manager will attempt to remove the affected CPU from service."
 119  119  msgid "SUN4U-8000-6H.impact"
 120  120  msgstr "System performance may be affected."
 121  121  msgid "SUN4U-8000-6H.action"
 122  122  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 123  123  #
 124  124  # code: SUN4U-8000-7D
 125  125  # keys: fault.cpu.ultraSPARC-III.l2cachetag
 126  126  #
 127  127  msgid "SUN4U-8000-7D.type"
 128  128  msgstr "Fault"
 129  129  msgid "SUN4U-8000-7D.severity"
 130  130  msgstr "Major"
 131  131  msgid "SUN4U-8000-7D.description"
 132  132  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 133  133  msgid "SUN4U-8000-7D.response"
 134  134  msgstr "The fault manager will attempt to remove the affected CPU from service."
 135  135  msgid "SUN4U-8000-7D.impact"
 136  136  msgstr "System performance may be affected."
 137  137  msgid "SUN4U-8000-7D.action"
 138  138  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 139  139  #
 140  140  # code: SUN4U-8000-84
 141  141  # keys: fault.cpu.ultraSPARC-IIIi.dcache
 142  142  #
 143  143  msgid "SUN4U-8000-84.type"
 144  144  msgstr "Fault"
 145  145  msgid "SUN4U-8000-84.severity"
 146  146  msgstr "Major"
 147  147  msgid "SUN4U-8000-84.description"
 148  148  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 149  149  msgid "SUN4U-8000-84.response"
 150  150  msgstr "The fault manager will attempt to remove the affected CPU from service."
 151  151  msgid "SUN4U-8000-84.impact"
 152  152  msgstr "System performance system may be affected."
 153  153  msgid "SUN4U-8000-84.action"
 154  154  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 155  155  #
 156  156  # code: SUN4U-8000-9R
 157  157  # keys: fault.cpu.ultraSPARC-IIIi.icache
 158  158  #
 159  159  msgid "SUN4U-8000-9R.type"
 160  160  msgstr "Fault"
 161  161  msgid "SUN4U-8000-9R.severity"
 162  162  msgstr "Major"
 163  163  msgid "SUN4U-8000-9R.description"
 164  164  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 165  165  msgid "SUN4U-8000-9R.response"
 166  166  msgstr "The fault manager will attempt to remove the affected CPU from service."
 167  167  msgid "SUN4U-8000-9R.impact"
 168  168  msgstr "System performance may be affected."
 169  169  msgid "SUN4U-8000-9R.action"
 170  170  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 171  171  #
 172  172  # code: SUN4U-8000-AC
 173  173  # keys: fault.cpu.ultraSPARC-IIIi.l2cachedata
 174  174  #
 175  175  msgid "SUN4U-8000-AC.type"
 176  176  msgstr "Fault"
 177  177  msgid "SUN4U-8000-AC.severity"
 178  178  msgstr "Major"
 179  179  msgid "SUN4U-8000-AC.description"
 180  180  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 181  181  msgid "SUN4U-8000-AC.response"
 182  182  msgstr "The fault manager will attempt to remove the affected CPU from service."
 183  183  msgid "SUN4U-8000-AC.impact"
 184  184  msgstr "System performance may be affected."
 185  185  msgid "SUN4U-8000-AC.action"
 186  186  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 187  187  #
 188  188  # code: SUN4U-8000-CQ
 189  189  # keys: fault.cpu.ultraSPARC-IIIi.l2cachetag
 190  190  #
 191  191  msgid "SUN4U-8000-CQ.type"
 192  192  msgstr "Fault"
 193  193  msgid "SUN4U-8000-CQ.severity"
 194  194  msgstr "Major"
 195  195  msgid "SUN4U-8000-CQ.description"
 196  196  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 197  197  msgid "SUN4U-8000-CQ.response"
 198  198  msgstr "The fault manager will attempt to remove the affected CPU from service."
 199  199  msgid "SUN4U-8000-CQ.impact"
 200  200  msgstr "System performance may be affected."
 201  201  msgid "SUN4U-8000-CQ.action"
 202  202  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 203  203  #
 204  204  # code: SUN4U-8000-DE
 205  205  # keys: fault.cpu.ultraSPARC-IIIplus.dcache
 206  206  #
 207  207  msgid "SUN4U-8000-DE.type"
 208  208  msgstr "Fault"
 209  209  msgid "SUN4U-8000-DE.severity"
 210  210  msgstr "Major"
 211  211  msgid "SUN4U-8000-DE.description"
 212  212  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 213  213  msgid "SUN4U-8000-DE.response"
 214  214  msgstr "The fault manager will attempt to remove the affected CPU from service."
 215  215  msgid "SUN4U-8000-DE.impact"
 216  216  msgstr "System performance may be affected."
 217  217  msgid "SUN4U-8000-DE.action"
 218  218  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 219  219  #
 220  220  # code: SUN4U-8000-EJ
 221  221  # keys: fault.cpu.ultraSPARC-IIIplus.icache
 222  222  #
 223  223  msgid "SUN4U-8000-EJ.type"
 224  224  msgstr "Fault"
 225  225  msgid "SUN4U-8000-EJ.severity"
 226  226  msgstr "Major"
 227  227  msgid "SUN4U-8000-EJ.description"
 228  228  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 229  229  msgid "SUN4U-8000-EJ.response"
 230  230  msgstr "The fault manager will attempt to remove the affected CPU from service."
 231  231  msgid "SUN4U-8000-EJ.impact"
 232  232  msgstr "System performance may be affected."
 233  233  msgid "SUN4U-8000-EJ.action"
 234  234  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 235  235  #
 236  236  # code: SUN4U-8000-F2
 237  237  # keys: fault.cpu.ultraSPARC-IIIplus.l2cachedata
 238  238  #
 239  239  msgid "SUN4U-8000-F2.type"
 240  240  msgstr "Fault"
 241  241  msgid "SUN4U-8000-F2.severity"
 242  242  msgstr "Major"
 243  243  msgid "SUN4U-8000-F2.description"
 244  244  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 245  245  msgid "SUN4U-8000-F2.response"
 246  246  msgstr "The fault manager will attempt to remove the affected CPU from service."
 247  247  msgid "SUN4U-8000-F2.impact"
 248  248  msgstr "System performance may be affected."
 249  249  msgid "SUN4U-8000-F2.action"
 250  250  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 251  251  #
 252  252  # code: SUN4U-8000-GX
 253  253  # keys: fault.cpu.ultraSPARC-IIIplus.l2cachetag
 254  254  #
 255  255  msgid "SUN4U-8000-GX.type"
 256  256  msgstr "Fault"
 257  257  msgid "SUN4U-8000-GX.severity"
 258  258  msgstr "Major"
 259  259  msgid "SUN4U-8000-GX.description"
 260  260  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 261  261  msgid "SUN4U-8000-GX.response"
 262  262  msgstr "An attempt will be made to remove the affected CPU from service."
 263  263  msgid "SUN4U-8000-GX.impact"
 264  264  msgstr "System performance may be affected."
 265  265  msgid "SUN4U-8000-GX.action"
 266  266  msgstr "Schedule a repair procedure to replace the affected CPU. Use fmdump -v -u <EVENT_ID> to identify the CPU."
 267  267  #
 268  268  # code: SUN4U-8000-H5
 269  269  # keys: fault.cpu.ultraSPARC-IV.dcache
 270  270  #
 271  271  msgid "SUN4U-8000-H5.type"
 272  272  msgstr "Fault"
 273  273  msgid "SUN4U-8000-H5.severity"
 274  274  msgstr "Major"
 275  275  msgid "SUN4U-8000-H5.description"
 276  276  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 277  277  msgid "SUN4U-8000-H5.response"
 278  278  msgstr "The fault manager will attempt to remove the affected CPU from service."
 279  279  msgid "SUN4U-8000-H5.impact"
 280  280  msgstr "System performance may be affected."
 281  281  msgid "SUN4U-8000-H5.action"
 282  282  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 283  283  #
 284  284  # code: SUN4U-8000-JS
 285  285  # keys: fault.cpu.ultraSPARC-IV.icache
 286  286  #
 287  287  msgid "SUN4U-8000-JS.type"
 288  288  msgstr "Fault"
 289  289  msgid "SUN4U-8000-JS.severity"
 290  290  msgstr "Major"
 291  291  msgid "SUN4U-8000-JS.description"
 292  292  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 293  293  msgid "SUN4U-8000-JS.response"
 294  294  msgstr "The fault manager will attempt to remove the affected CPU from service."
 295  295  msgid "SUN4U-8000-JS.impact"
 296  296  msgstr "System performance may be affected."
 297  297  msgid "SUN4U-8000-JS.action"
 298  298  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 299  299  #
 300  300  # code: SUN4U-8000-KA
 301  301  # keys: fault.cpu.ultraSPARC-IV.l2cachedata
 302  302  #
 303  303  msgid "SUN4U-8000-KA.type"
 304  304  msgstr "Fault"
 305  305  msgid "SUN4U-8000-KA.severity"
 306  306  msgstr "Major"
 307  307  msgid "SUN4U-8000-KA.description"
 308  308  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 309  309  msgid "SUN4U-8000-KA.response"
 310  310  msgstr "The fault manager will attempt to remove the affected CPU from service."
 311  311  msgid "SUN4U-8000-KA.impact"
 312  312  msgstr "System performance may be affected."
 313  313  msgid "SUN4U-8000-KA.action"
 314  314  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 315  315  #
 316  316  # code: SUN4U-8000-LP
 317  317  # keys: fault.cpu.ultraSPARC-IV.l2cachetag
 318  318  #
 319  319  msgid "SUN4U-8000-LP.type"
 320  320  msgstr "Fault"
 321  321  msgid "SUN4U-8000-LP.severity"
 322  322  msgstr "Major"
 323  323  msgid "SUN4U-8000-LP.description"
 324  324  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 325  325  msgid "SUN4U-8000-LP.response"
 326  326  msgstr "The fault manager will attempt to remove the affected CPU from service."
 327  327  msgid "SUN4U-8000-LP.impact"
 328  328  msgstr "System performance may be affected."
 329  329  msgid "SUN4U-8000-LP.action"
 330  330  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 331  331  #
 332  332  # code: SUN4U-8000-MD
 333  333  # keys: fault.cpu.ultraSPARC-III.fpu
 334  334  #
 335  335  msgid "SUN4U-8000-MD.type"
 336  336  msgstr "Fault"
 337  337  msgid "SUN4U-8000-MD.severity"
 338  338  msgstr "Major"
 339  339  msgid "SUN4U-8000-MD.description"
 340  340  msgstr "A fault has been detected in the FPU of this CPU.  Refer to %s for more information."
 341  341  msgid "SUN4U-8000-MD.response"
 342  342  msgstr "The fault manager will attempt to remove the affected CPU from service."
 343  343  msgid "SUN4U-8000-MD.impact"
 344  344  msgstr "System performance may be affected."
 345  345  msgid "SUN4U-8000-MD.action"
 346  346  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 347  347  #
 348  348  # code: SUN4U-8000-NH
 349  349  # keys: fault.cpu.ultraSPARC-IIIi.fpu
 350  350  #
 351  351  msgid "SUN4U-8000-NH.type"
 352  352  msgstr "Fault"
 353  353  msgid "SUN4U-8000-NH.severity"
 354  354  msgstr "Major"
 355  355  msgid "SUN4U-8000-NH.description"
 356  356  msgstr "A fault has been detected in the FPU of this CPU.  Refer to %s for more information."
 357  357  msgid "SUN4U-8000-NH.response"
 358  358  msgstr "The fault manager will attempt to remove the affected CPU from service."
 359  359  msgid "SUN4U-8000-NH.impact"
 360  360  msgstr "System performance may be affected."
 361  361  msgid "SUN4U-8000-NH.action"
 362  362  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 363  363  #
 364  364  # code: SUN4U-8000-P3
 365  365  # keys: fault.cpu.ultraSPARC-IIIplus.fpu
 366  366  #
 367  367  msgid "SUN4U-8000-P3.type"
 368  368  msgstr "Fault"
 369  369  msgid "SUN4U-8000-P3.severity"
 370  370  msgstr "Major"
 371  371  msgid "SUN4U-8000-P3.description"
 372  372  msgstr "A fault has been detected in the FPU of this CPU.  Refer to %s for more information."
 373  373  msgid "SUN4U-8000-P3.response"
 374  374  msgstr "The fault manager will attempt to remove the affected CPU from service."
 375  375  msgid "SUN4U-8000-P3.impact"
 376  376  msgstr "System performance may be affected."
 377  377  msgid "SUN4U-8000-P3.action"
 378  378  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 379  379  #
 380  380  # code: SUN4U-8000-QY
 381  381  # keys: fault.cpu.ultraSPARC-IV.fpu
 382  382  #
 383  383  msgid "SUN4U-8000-QY.type"
 384  384  msgstr "Fault"
 385  385  msgid "SUN4U-8000-QY.severity"
 386  386  msgstr "Major"
 387  387  msgid "SUN4U-8000-QY.description"
 388  388  msgstr "A fault has been detected in the FPU of this CPU.  Refer to %s for more information."
 389  389  msgid "SUN4U-8000-QY.response"
 390  390  msgstr "The fault manager will attempt to remove the affected CPU from service."
 391  391  msgid "SUN4U-8000-QY.impact"
 392  392  msgstr "System performance may be affected."
 393  393  msgid "SUN4U-8000-QY.action"
 394  394  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 395  395  #
 396  396  # code: SUN4U-8000-RQ
 397  397  # keys: fault.cpu.ultraSPARC-IVplus.fpu
 398  398  #
 399  399  msgid "SUN4U-8000-RQ.type"
 400  400  msgstr "Fault"
 401  401  msgid "SUN4U-8000-RQ.severity"
 402  402  msgstr "Major"
 403  403  msgid "SUN4U-8000-RQ.description"
 404  404  msgstr "A fault has been detected in the FPU of this CPU.  Refer to %s for more information."
 405  405  msgid "SUN4U-8000-RQ.response"
 406  406  msgstr "The fault manager will attempt to remove the affected CPU from service."
 407  407  msgid "SUN4U-8000-RQ.impact"
 408  408  msgstr "System performance may be affected."
 409  409  msgid "SUN4U-8000-RQ.action"
 410  410  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 411  411  #
 412  412  # code: SUN4U-8000-SC
 413  413  # keys: fault.cpu.ultraSPARC-IVplus.dcache
 414  414  #
 415  415  msgid "SUN4U-8000-SC.type"
 416  416  msgstr "Fault"
 417  417  msgid "SUN4U-8000-SC.severity"
 418  418  msgstr "Major"
 419  419  msgid "SUN4U-8000-SC.description"
 420  420  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 421  421  msgid "SUN4U-8000-SC.response"
 422  422  msgstr "The fault manager will attempt to remove the affected CPU from service."
 423  423  msgid "SUN4U-8000-SC.impact"
 424  424  msgstr "System performance may be affected."
 425  425  msgid "SUN4U-8000-SC.action"
 426  426  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 427  427  #
 428  428  # code: SUN4U-8000-TR
 429  429  # keys: fault.cpu.ultraSPARC-IVplus.icache
 430  430  #
 431  431  msgid "SUN4U-8000-TR.type"
 432  432  msgstr "Fault"
 433  433  msgid "SUN4U-8000-TR.severity"
 434  434  msgstr "Major"
 435  435  msgid "SUN4U-8000-TR.description"
 436  436  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 437  437  msgid "SUN4U-8000-TR.response"
 438  438  msgstr "The fault manager will attempt to remove the affected CPU from service."
 439  439  msgid "SUN4U-8000-TR.impact"
 440  440  msgstr "System performance may be affected."
 441  441  msgid "SUN4U-8000-TR.action"
 442  442  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 443  443  #
 444  444  # code: SUN4U-8000-U4
 445  445  # keys: fault.cpu.ultraSPARC-IVplus.pcache
 446  446  #
 447  447  msgid "SUN4U-8000-U4.type"
 448  448  msgstr "Fault"
 449  449  msgid "SUN4U-8000-U4.severity"
 450  450  msgstr "Major"
 451  451  msgid "SUN4U-8000-U4.description"
 452  452  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 453  453  msgid "SUN4U-8000-U4.response"
 454  454  msgstr "The fault manager will attempt to remove the affected CPU from service."
 455  455  msgid "SUN4U-8000-U4.impact"
 456  456  msgstr "System performance may be affected."
 457  457  msgid "SUN4U-8000-U4.action"
 458  458  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 459  459  #
 460  460  # code: SUN4U-8000-VX
 461  461  # keys: fault.cpu.ultraSPARC-IVplus.dtlb
 462  462  #
 463  463  msgid "SUN4U-8000-VX.type"
 464  464  msgstr "Fault"
 465  465  msgid "SUN4U-8000-VX.severity"
 466  466  msgstr "Major"
 467  467  msgid "SUN4U-8000-VX.description"
 468  468  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 469  469  msgid "SUN4U-8000-VX.response"
 470  470  msgstr "The fault manager will attempt to remove the affected CPU from service."
 471  471  msgid "SUN4U-8000-VX.impact"
 472  472  msgstr "System performance may be affected."
 473  473  msgid "SUN4U-8000-VX.action"
 474  474  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 475  475  #
 476  476  # code: SUN4U-8000-W2
 477  477  # keys: fault.cpu.ultraSPARC-IVplus.itlb
 478  478  #
 479  479  msgid "SUN4U-8000-W2.type"
 480  480  msgstr "Fault"
 481  481  msgid "SUN4U-8000-W2.severity"
 482  482  msgstr "Major"
 483  483  msgid "SUN4U-8000-W2.description"
 484  484  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 485  485  msgid "SUN4U-8000-W2.response"
 486  486  msgstr "The fault manager will attempt to remove the affected CPU from service."
 487  487  msgid "SUN4U-8000-W2.impact"
 488  488  msgstr "System performance may be affected."
 489  489  msgid "SUN4U-8000-W2.action"
 490  490  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 491  491  #
 492  492  # code: SUN4U-8000-XJ
 493  493  # keys: fault.cpu.ultraSPARC-IVplus.l2cachedata
 494  494  #
 495  495  msgid "SUN4U-8000-XJ.type"
 496  496  msgstr "Fault"
 497  497  msgid "SUN4U-8000-XJ.severity"
 498  498  msgstr "Major"
 499  499  msgid "SUN4U-8000-XJ.description"
 500  500  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 501  501  msgid "SUN4U-8000-XJ.response"
 502  502  msgstr "The fault manager will attempt to remove the affected CPU from service."
 503  503  msgid "SUN4U-8000-XJ.impact"
 504  504  msgstr "System performance may be affected."
 505  505  msgid "SUN4U-8000-XJ.action"
 506  506  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 507  507  #
 508  508  # code: SUN4U-8000-YE
 509  509  # keys: fault.cpu.ultraSPARC-IVplus.l2cachetag
 510  510  #
 511  511  msgid "SUN4U-8000-YE.type"
 512  512  msgstr "Fault"
 513  513  msgid "SUN4U-8000-YE.severity"
 514  514  msgstr "Major"
 515  515  msgid "SUN4U-8000-YE.description"
 516  516  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 517  517  msgid "SUN4U-8000-YE.response"
 518  518  msgstr "The fault manager will attempt to remove the affected CPU from service."
 519  519  msgid "SUN4U-8000-YE.impact"
 520  520  msgstr "System performance may be affected."
 521  521  msgid "SUN4U-8000-YE.action"
 522  522  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 523  523  #
 524  524  # code: SUN4U-8001-0J
 525  525  # keys: fault.cpu.ultraSPARC-IVplus.l3cachedata
 526  526  #
 527  527  msgid "SUN4U-8001-0J.type"
 528  528  msgstr "Fault"
 529  529  msgid "SUN4U-8001-0J.severity"
 530  530  msgstr "Major"
 531  531  msgid "SUN4U-8001-0J.description"
 532  532  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 533  533  msgid "SUN4U-8001-0J.response"
 534  534  msgstr "The fault manager will attempt to remove the affected CPU from service."
 535  535  msgid "SUN4U-8001-0J.impact"
 536  536  msgstr "System performance may be affected."
 537  537  msgid "SUN4U-8001-0J.action"
 538  538  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 539  539  #
 540  540  # code: SUN4U-8001-1E
 541  541  # keys: fault.cpu.ultraSPARC-IVplus.l3cachetag
 542  542  #
 543  543  msgid "SUN4U-8001-1E.type"
 544  544  msgstr "Fault"
 545  545  msgid "SUN4U-8001-1E.severity"
 546  546  msgstr "Major"
 547  547  msgid "SUN4U-8001-1E.description"
 548  548  msgstr "The number of errors associated with this CPU has exceeded acceptable levels.  Refer to %s for more information."
 549  549  msgid "SUN4U-8001-1E.response"
 550  550  msgstr "The fault manager will attempt to remove the affected CPU from service."
 551  551  msgid "SUN4U-8001-1E.impact"
 552  552  msgstr "System performance may be affected."
 553  553  msgid "SUN4U-8001-1E.action"

 554  554  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
 555  555  #
 556  556  # code: SUN4U-8001-2X
 557  557  # keys: defect.ultraSPARC-II.memory.nodiag
 558  558  #
 559  559  msgid "SUN4U-8001-2X.type"
 560  560  msgstr "Defect"
 561  561  msgid "SUN4U-8001-2X.severity"
 562  562  msgstr "Minor"
 563  563  msgid "SUN4U-8001-2X.description"
 564      -msgstr "The Solaris Fault Manager received an event from the IO subsystem for which automated diagnosis software is currently unavailable.  Refer to %s for more information."
      564 +msgstr "The illumos Fault Manager received an event from the IO subsystem for which automated diagnosis software is currently unavailable.  Refer to %s for more information."
 565  565  msgid "SUN4U-8001-2X.response"
 566      -msgstr "The error information has been saved for examination by Sun."
      566 +msgstr "The error information has been saved for examination by your illumos distribution team."
 567  567  msgid "SUN4U-8001-2X.impact"
 568  568  msgstr "The error log will need to be manually examined using fmdump(1M) in order to determine if any human response is required."
 569  569  msgid "SUN4U-8001-2X.action"
 570  570  msgstr "Use fmdump -ev -u <EVENT-ID> to view and record the undiagnosed errors."
 571  571  #
 572  572  # code: SUN4U-8001-32
 573  573  # keys: fault.memory.datapath
 574  574  #
 575  575  msgid "SUN4U-8001-32.type"
 576  576  msgstr "Fault"
 577  577  msgid "SUN4U-8001-32.severity"
 578  578  msgstr "Major"
 579  579  msgid "SUN4U-8001-32.description"
 580  580  msgstr "Errors have been detected on multiple memory modules, suggesting that a problem exists somewhere else in the system.  Refer to %s for more information."
 581  581  msgid "SUN4U-8001-32.response"
 582      -msgstr "Error reports from the affected components will be logged for examination by Sun."
      582 +msgstr "Error reports from the affected components will be logged for examination by your illumos distribution team."
 583  583  msgid "SUN4U-8001-32.impact"
 584  584  msgstr "System performance and stability may be affected."
 585  585  msgid "SUN4U-8001-32.action"
 586  586  msgstr "Contact your service provider for further diagnosis."
 587  587  #
 588  588  # code: SUN4U-8001-4R
 589  589  # keys: fault.io.datapath
 590  590  #
 591  591  msgid "SUN4U-8001-4R.type"
 592  592  msgstr "Fault"
 593  593  msgid "SUN4U-8001-4R.severity"
 594  594  msgstr "Critical"
 595  595  msgid "SUN4U-8001-4R.description"
 596  596  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 597  597  msgid "SUN4U-8001-4R.response"
 598  598  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 599  599  msgid "SUN4U-8001-4R.impact"
 600  600  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 601  601  msgid "SUN4U-8001-4R.action"
 602      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      602 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 603  603  #
 604  604  # code: SUN4U-8001-54
 605  605  # keys: defect.io.pci.driver fault.io.datapath
 606  606  #
 607  607  msgid "SUN4U-8001-54.type"
 608  608  msgstr "Fault"
 609  609  msgid "SUN4U-8001-54.severity"
 610  610  msgstr "Critical"
 611  611  msgid "SUN4U-8001-54.description"
 612  612  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 613  613  msgid "SUN4U-8001-54.response"
 614  614  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 615  615  msgid "SUN4U-8001-54.impact"
 616  616  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 617  617  msgid "SUN4U-8001-54.action"
 618      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      618 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 619  619  #
 620  620  # code: SUN4U-8001-6Q
 621  621  # keys: fault.io.datapath fault.io.pci.bus
 622  622  #
 623  623  msgid "SUN4U-8001-6Q.type"
 624  624  msgstr "Fault"
 625  625  msgid "SUN4U-8001-6Q.severity"
 626  626  msgstr "Critical"
 627  627  msgid "SUN4U-8001-6Q.description"
 628  628  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 629  629  msgid "SUN4U-8001-6Q.response"
 630  630  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 631  631  msgid "SUN4U-8001-6Q.impact"
 632  632  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 633  633  msgid "SUN4U-8001-6Q.action"
 634      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      634 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 635  635  #
 636  636  # code: SUN4U-8001-7C
 637  637  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus
 638  638  #
 639  639  msgid "SUN4U-8001-7C.type"
 640  640  msgstr "Fault"
 641  641  msgid "SUN4U-8001-7C.severity"
 642  642  msgstr "Critical"
 643  643  msgid "SUN4U-8001-7C.description"
 644  644  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 645  645  msgid "SUN4U-8001-7C.response"
 646  646  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 647  647  msgid "SUN4U-8001-7C.impact"
 648  648  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 649  649  msgid "SUN4U-8001-7C.action"
 650      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      650 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 651  651  #
 652  652  # code: SUN4U-8001-83
 653  653  # keys: fault.io.datapath fault.io.pci.device
 654  654  #
 655  655  msgid "SUN4U-8001-83.type"
 656  656  msgstr "Fault"
 657  657  msgid "SUN4U-8001-83.severity"
 658  658  msgstr "Critical"
 659  659  msgid "SUN4U-8001-83.description"
 660  660  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 661  661  msgid "SUN4U-8001-83.response"
 662  662  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 663  663  msgid "SUN4U-8001-83.impact"
 664  664  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 665  665  msgid "SUN4U-8001-83.action"
 666      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      666 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 667  667  #
 668  668  # code: SUN4U-8001-9Y
 669  669  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device
 670  670  #
 671  671  msgid "SUN4U-8001-9Y.type"
 672  672  msgstr "Fault"
 673  673  msgid "SUN4U-8001-9Y.severity"
 674  674  msgstr "Critical"
 675  675  msgid "SUN4U-8001-9Y.description"
 676  676  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 677  677  msgid "SUN4U-8001-9Y.response"
 678  678  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 679  679  msgid "SUN4U-8001-9Y.impact"
 680  680  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 681  681  msgid "SUN4U-8001-9Y.action"
 682      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      682 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 683  683  #
 684  684  # code: SUN4U-8001-AD
 685  685  # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device
 686  686  #
 687  687  msgid "SUN4U-8001-AD.type"
 688  688  msgstr "Fault"
 689  689  msgid "SUN4U-8001-AD.severity"
 690  690  msgstr "Critical"
 691  691  msgid "SUN4U-8001-AD.description"
 692  692  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 693  693  msgid "SUN4U-8001-AD.response"
 694  694  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 695  695  msgid "SUN4U-8001-AD.impact"
 696  696  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 697  697  msgid "SUN4U-8001-AD.action"
 698      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      698 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 699  699  #
 700  700  # code: SUN4U-8001-CH
 701  701  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device
 702  702  #
 703  703  msgid "SUN4U-8001-CH.type"
 704  704  msgstr "Fault"
 705  705  msgid "SUN4U-8001-CH.severity"
 706  706  msgstr "Critical"
 707  707  msgid "SUN4U-8001-CH.description"
 708  708  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 709  709  msgid "SUN4U-8001-CH.response"
 710  710  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 711  711  msgid "SUN4U-8001-CH.impact"
 712  712  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 713  713  msgid "SUN4U-8001-CH.action"
 714      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      714 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 715  715  #
 716  716  # code: SUN4U-8001-DA
 717  717  # keys: fault.io.hbus
 718  718  #
 719  719  msgid "SUN4U-8001-DA.type"
 720  720  msgstr "Fault"
 721  721  msgid "SUN4U-8001-DA.severity"
 722  722  msgstr "Critical"
 723  723  msgid "SUN4U-8001-DA.description"
 724  724  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 725  725  msgid "SUN4U-8001-DA.response"
 726  726  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 727  727  msgid "SUN4U-8001-DA.impact"
 728  728  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 729  729  msgid "SUN4U-8001-DA.action"
 730      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      730 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 731  731  #
 732  732  # code: SUN4U-8001-EP
 733  733  # keys: defect.io.pci.driver fault.io.hbus
 734  734  #
 735  735  msgid "SUN4U-8001-EP.type"
 736  736  msgstr "Fault"
 737  737  msgid "SUN4U-8001-EP.severity"
 738  738  msgstr "Critical"
 739  739  msgid "SUN4U-8001-EP.description"
 740  740  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 741  741  msgid "SUN4U-8001-EP.response"
 742  742  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 743  743  msgid "SUN4U-8001-EP.impact"
 744  744  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 745  745  msgid "SUN4U-8001-EP.action"
 746      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      746 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 747  747  #
 748  748  # code: SUN4U-8001-F5
 749  749  # keys: fault.io.hbus fault.io.pci.bus
 750  750  #
 751  751  msgid "SUN4U-8001-F5.type"
 752  752  msgstr "Fault"
 753  753  msgid "SUN4U-8001-F5.severity"
 754  754  msgstr "Critical"
 755  755  msgid "SUN4U-8001-F5.description"
 756  756  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 757  757  msgid "SUN4U-8001-F5.response"
 758  758  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 759  759  msgid "SUN4U-8001-F5.impact"
 760  760  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 761  761  msgid "SUN4U-8001-F5.action"
 762      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      762 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 763  763  #
 764  764  # code: SUN4U-8001-GS
 765  765  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus
 766  766  #
 767  767  msgid "SUN4U-8001-GS.type"
 768  768  msgstr "Fault"
 769  769  msgid "SUN4U-8001-GS.severity"
 770  770  msgstr "Critical"
 771  771  msgid "SUN4U-8001-GS.description"
 772  772  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 773  773  msgid "SUN4U-8001-GS.response"
 774  774  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 775  775  msgid "SUN4U-8001-GS.impact"
 776  776  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 777  777  msgid "SUN4U-8001-GS.action"
 778      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      778 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 779  779  #
 780  780  # code: SUN4U-8001-H2
 781  781  # keys: fault.io.hbus fault.io.pci.device
 782  782  #
 783  783  msgid "SUN4U-8001-H2.type"
 784  784  msgstr "Fault"
 785  785  msgid "SUN4U-8001-H2.severity"
 786  786  msgstr "Critical"
 787  787  msgid "SUN4U-8001-H2.description"
 788  788  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 789  789  msgid "SUN4U-8001-H2.response"
 790  790  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 791  791  msgid "SUN4U-8001-H2.impact"
 792  792  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 793  793  msgid "SUN4U-8001-H2.action"
 794      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      794 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 795  795  #
 796  796  # code: SUN4U-8001-JX
 797  797  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device
 798  798  #
 799  799  msgid "SUN4U-8001-JX.type"
 800  800  msgstr "Fault"
 801  801  msgid "SUN4U-8001-JX.severity"
 802  802  msgstr "Critical"
 803  803  msgid "SUN4U-8001-JX.description"
 804  804  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 805  805  msgid "SUN4U-8001-JX.response"
 806  806  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 807  807  msgid "SUN4U-8001-JX.impact"
 808  808  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 809  809  msgid "SUN4U-8001-JX.action"
 810      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      810 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 811  811  #
 812  812  # code: SUN4U-8001-KE
 813  813  # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device
 814  814  #
 815  815  msgid "SUN4U-8001-KE.type"
 816  816  msgstr "Fault"
 817  817  msgid "SUN4U-8001-KE.severity"
 818  818  msgstr "Critical"
 819  819  msgid "SUN4U-8001-KE.description"
 820  820  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 821  821  msgid "SUN4U-8001-KE.response"
 822  822  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 823  823  msgid "SUN4U-8001-KE.impact"
 824  824  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 825  825  msgid "SUN4U-8001-KE.action"
 826      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      826 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 827  827  #
 828  828  # code: SUN4U-8001-LJ
 829  829  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device
 830  830  #
 831  831  msgid "SUN4U-8001-LJ.type"
 832  832  msgstr "Fault"
 833  833  msgid "SUN4U-8001-LJ.severity"
 834  834  msgstr "Critical"
 835  835  msgid "SUN4U-8001-LJ.description"
 836  836  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 837  837  msgid "SUN4U-8001-LJ.response"
 838  838  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 839  839  msgid "SUN4U-8001-LJ.impact"
 840  840  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 841  841  msgid "SUN4U-8001-LJ.action"
 842      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      842 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 843  843  #
 844  844  # code: SUN4U-8001-MC
 845  845  # keys: fault.io.datapath fault.io.hbus
 846  846  #
 847  847  msgid "SUN4U-8001-MC.type"
 848  848  msgstr "Fault"
 849  849  msgid "SUN4U-8001-MC.severity"
 850  850  msgstr "Critical"
 851  851  msgid "SUN4U-8001-MC.description"
 852  852  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 853  853  msgid "SUN4U-8001-MC.response"
 854  854  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 855  855  msgid "SUN4U-8001-MC.impact"
 856  856  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 857  857  msgid "SUN4U-8001-MC.action"
 858      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      858 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 859  859  #
 860  860  # code: SUN4U-8001-NQ
 861  861  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus
 862  862  #
 863  863  msgid "SUN4U-8001-NQ.type"
 864  864  msgstr "Fault"
 865  865  msgid "SUN4U-8001-NQ.severity"
 866  866  msgstr "Critical"
 867  867  msgid "SUN4U-8001-NQ.description"
 868  868  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 869  869  msgid "SUN4U-8001-NQ.response"
 870  870  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 871  871  msgid "SUN4U-8001-NQ.impact"
 872  872  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 873  873  msgid "SUN4U-8001-NQ.action"
 874      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      874 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 875  875  #
 876  876  # code: SUN4U-8001-P4
 877  877  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus
 878  878  #
 879  879  msgid "SUN4U-8001-P4.type"
 880  880  msgstr "Fault"
 881  881  msgid "SUN4U-8001-P4.severity"
 882  882  msgstr "Critical"
 883  883  msgid "SUN4U-8001-P4.description"
 884  884  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 885  885  msgid "SUN4U-8001-P4.response"
 886  886  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 887  887  msgid "SUN4U-8001-P4.impact"
 888  888  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 889  889  msgid "SUN4U-8001-P4.action"
 890      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      890 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 891  891  #
 892  892  # code: SUN4U-8001-QR
 893  893  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus
 894  894  #
 895  895  msgid "SUN4U-8001-QR.type"
 896  896  msgstr "Fault"
 897  897  msgid "SUN4U-8001-QR.severity"
 898  898  msgstr "Critical"
 899  899  msgid "SUN4U-8001-QR.description"
 900  900  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 901  901  msgid "SUN4U-8001-QR.response"
 902  902  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 903  903  msgid "SUN4U-8001-QR.impact"
 904  904  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 905  905  msgid "SUN4U-8001-QR.action"
 906      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      906 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 907  907  #
 908  908  # code: SUN4U-8001-RH
 909  909  # keys: fault.io.datapath fault.io.hbus fault.io.pci.device
 910  910  #
 911  911  msgid "SUN4U-8001-RH.type"
 912  912  msgstr "Fault"
 913  913  msgid "SUN4U-8001-RH.severity"
 914  914  msgstr "Critical"
 915  915  msgid "SUN4U-8001-RH.description"
 916  916  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 917  917  msgid "SUN4U-8001-RH.response"
 918  918  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 919  919  msgid "SUN4U-8001-RH.impact"
 920  920  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 921  921  msgid "SUN4U-8001-RH.action"
 922      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      922 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 923  923  #
 924  924  # code: SUN4U-8001-SD
 925  925  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device
 926  926  #
 927  927  msgid "SUN4U-8001-SD.type"
 928  928  msgstr "Fault"
 929  929  msgid "SUN4U-8001-SD.severity"
 930  930  msgstr "Critical"
 931  931  msgid "SUN4U-8001-SD.description"
 932  932  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 933  933  msgid "SUN4U-8001-SD.response"
 934  934  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 935  935  msgid "SUN4U-8001-SD.impact"
 936  936  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 937  937  msgid "SUN4U-8001-SD.action"
 938      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      938 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 939  939  #
 940  940  # code: SUN4U-8001-TY
 941  941  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device
 942  942  #
 943  943  msgid "SUN4U-8001-TY.type"
 944  944  msgstr "Fault"
 945  945  msgid "SUN4U-8001-TY.severity"
 946  946  msgstr "Critical"
 947  947  msgid "SUN4U-8001-TY.description"
 948  948  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 949  949  msgid "SUN4U-8001-TY.response"
 950  950  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 951  951  msgid "SUN4U-8001-TY.impact"
 952  952  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 953  953  msgid "SUN4U-8001-TY.action"
 954      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      954 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 955  955  #
 956  956  # code: SUN4U-8001-U3
 957  957  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device
 958  958  #
 959  959  msgid "SUN4U-8001-U3.type"
 960  960  msgstr "Fault"
 961  961  msgid "SUN4U-8001-U3.severity"
 962  962  msgstr "Critical"
 963  963  msgid "SUN4U-8001-U3.description"
 964  964  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 965  965  msgid "SUN4U-8001-U3.response"
 966  966  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 967  967  msgid "SUN4U-8001-U3.impact"
 968  968  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 969  969  msgid "SUN4U-8001-U3.action"
 970      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
      970 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
 971  971  #
 972  972  # code: SUN4U-8001-VS
 973  973  # keys: fault.io.schizo
 974  974  #
 975  975  msgid "SUN4U-8001-VS.type"
 976  976  msgstr "Fault"
 977  977  msgid "SUN4U-8001-VS.severity"
 978  978  msgstr "Critical"
 979  979  msgid "SUN4U-8001-VS.description"
 980  980  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
 981  981  msgid "SUN4U-8001-VS.response"
 982  982  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 983  983  msgid "SUN4U-8001-VS.impact"
 984  984  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
 985  985  msgid "SUN4U-8001-VS.action"
 986      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
      986 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
 987  987  #
 988  988  # code: SUN4U-8001-W5
 989  989  # keys: defect.io.pci.driver fault.io.schizo
 990  990  #
 991  991  msgid "SUN4U-8001-W5.type"
 992  992  msgstr "Fault"
 993  993  msgid "SUN4U-8001-W5.severity"
 994  994  msgstr "Critical"
 995  995  msgid "SUN4U-8001-W5.description"
 996  996  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
 997  997  msgid "SUN4U-8001-W5.response"
 998  998  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
 999  999  msgid "SUN4U-8001-W5.impact"
1000 1000  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1001 1001  msgid "SUN4U-8001-W5.action"
1002      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1002 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1003 1003  #
1004 1004  # code: SUN4U-8001-XP
1005 1005  # keys: fault.io.pci.bus fault.io.schizo
1006 1006  #
1007 1007  msgid "SUN4U-8001-XP.type"
1008 1008  msgstr "Fault"
1009 1009  msgid "SUN4U-8001-XP.severity"
1010 1010  msgstr "Critical"
1011 1011  msgid "SUN4U-8001-XP.description"
1012 1012  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1013 1013  msgid "SUN4U-8001-XP.response"
1014 1014  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1015 1015  msgid "SUN4U-8001-XP.impact"
1016 1016  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1017 1017  msgid "SUN4U-8001-XP.action"
1018      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1018 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1019 1019  #
1020 1020  # code: SUN4U-8001-YA
1021 1021  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo
1022 1022  #
1023 1023  msgid "SUN4U-8001-YA.type"
1024 1024  msgstr "Fault"
1025 1025  msgid "SUN4U-8001-YA.severity"
1026 1026  msgstr "Critical"
1027 1027  msgid "SUN4U-8001-YA.description"
1028 1028  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1029 1029  msgid "SUN4U-8001-YA.response"
1030 1030  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1031 1031  msgid "SUN4U-8001-YA.impact"
1032 1032  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1033 1033  msgid "SUN4U-8001-YA.action"
1034      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1034 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1035 1035  #
1036 1036  # code: SUN4U-8002-0R
1037 1037  # keys: fault.io.pci.device fault.io.schizo
1038 1038  #
1039 1039  msgid "SUN4U-8002-0R.type"
1040 1040  msgstr "Fault"
1041 1041  msgid "SUN4U-8002-0R.severity"
1042 1042  msgstr "Critical"
1043 1043  msgid "SUN4U-8002-0R.description"
1044 1044  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1045 1045  msgid "SUN4U-8002-0R.response"
1046 1046  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1047 1047  msgid "SUN4U-8002-0R.impact"
1048 1048  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1049 1049  msgid "SUN4U-8002-0R.action"
1050      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1050 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1051 1051  #
1052 1052  # code: SUN4U-8002-14
1053 1053  # keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo
1054 1054  #
1055 1055  msgid "SUN4U-8002-14.type"
1056 1056  msgstr "Fault"
1057 1057  msgid "SUN4U-8002-14.severity"
1058 1058  msgstr "Critical"
1059 1059  msgid "SUN4U-8002-14.description"
1060 1060  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1061 1061  msgid "SUN4U-8002-14.response"
1062 1062  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1063 1063  msgid "SUN4U-8002-14.impact"
1064 1064  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1065 1065  msgid "SUN4U-8002-14.action"
1066      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1066 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1067 1067  #
1068 1068  # code: SUN4U-8002-2Q
1069 1069  # keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo
1070 1070  #
1071 1071  msgid "SUN4U-8002-2Q.type"
1072 1072  msgstr "Fault"
1073 1073  msgid "SUN4U-8002-2Q.severity"
1074 1074  msgstr "Critical"
1075 1075  msgid "SUN4U-8002-2Q.description"
1076 1076  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1077 1077  msgid "SUN4U-8002-2Q.response"
1078 1078  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1079 1079  msgid "SUN4U-8002-2Q.impact"
1080 1080  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1081 1081  msgid "SUN4U-8002-2Q.action"
1082      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1082 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1083 1083  #
1084 1084  # code: SUN4U-8002-3C
1085 1085  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo
1086 1086  #
1087 1087  msgid "SUN4U-8002-3C.type"
1088 1088  msgstr "Fault"
1089 1089  msgid "SUN4U-8002-3C.severity"
1090 1090  msgstr "Critical"
1091 1091  msgid "SUN4U-8002-3C.description"
1092 1092  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1093 1093  msgid "SUN4U-8002-3C.response"
1094 1094  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1095 1095  msgid "SUN4U-8002-3C.impact"
1096 1096  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1097 1097  msgid "SUN4U-8002-3C.action"
1098      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1098 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1099 1099  #
1100 1100  # code: SUN4U-8002-4J
1101 1101  # keys: fault.io.datapath fault.io.schizo
1102 1102  #
1103 1103  msgid "SUN4U-8002-4J.type"
1104 1104  msgstr "Fault"
1105 1105  msgid "SUN4U-8002-4J.severity"
1106 1106  msgstr "Critical"
1107 1107  msgid "SUN4U-8002-4J.description"
1108 1108  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1109 1109  msgid "SUN4U-8002-4J.response"
1110 1110  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1111 1111  msgid "SUN4U-8002-4J.impact"
1112 1112  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1113 1113  msgid "SUN4U-8002-4J.action"
1114      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1114 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1115 1115  #
1116 1116  # code: SUN4U-8002-5E
1117 1117  # keys: defect.io.pci.driver fault.io.datapath fault.io.schizo
1118 1118  #
1119 1119  msgid "SUN4U-8002-5E.type"
1120 1120  msgstr "Fault"
1121 1121  msgid "SUN4U-8002-5E.severity"
1122 1122  msgstr "Critical"
1123 1123  msgid "SUN4U-8002-5E.description"
1124 1124  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1125 1125  msgid "SUN4U-8002-5E.response"
1126 1126  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1127 1127  msgid "SUN4U-8002-5E.impact"
1128 1128  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1129 1129  msgid "SUN4U-8002-5E.action"
1130      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1130 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1131 1131  #
1132 1132  # code: SUN4U-8002-6X
1133 1133  # keys: fault.io.datapath fault.io.pci.bus fault.io.schizo
1134 1134  #
1135 1135  msgid "SUN4U-8002-6X.type"
1136 1136  msgstr "Fault"
1137 1137  msgid "SUN4U-8002-6X.severity"
1138 1138  msgstr "Critical"
1139 1139  msgid "SUN4U-8002-6X.description"
1140 1140  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1141 1141  msgid "SUN4U-8002-6X.response"
1142 1142  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1143 1143  msgid "SUN4U-8002-6X.impact"
1144 1144  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1145 1145  msgid "SUN4U-8002-6X.action"
1146      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1146 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1147 1147  #
1148 1148  # code: SUN4U-8002-72
1149 1149  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo
1150 1150  #
1151 1151  msgid "SUN4U-8002-72.type"
1152 1152  msgstr "Fault"
1153 1153  msgid "SUN4U-8002-72.severity"
1154 1154  msgstr "Critical"
1155 1155  msgid "SUN4U-8002-72.description"
1156 1156  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1157 1157  msgid "SUN4U-8002-72.response"
1158 1158  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1159 1159  msgid "SUN4U-8002-72.impact"
1160 1160  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1161 1161  msgid "SUN4U-8002-72.action"
1162      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1162 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1163 1163  #
1164 1164  # code: SUN4U-8002-8A
1165 1165  # keys: fault.io.datapath fault.io.pci.device fault.io.schizo
1166 1166  #
1167 1167  msgid "SUN4U-8002-8A.type"
1168 1168  msgstr "Fault"
1169 1169  msgid "SUN4U-8002-8A.severity"
1170 1170  msgstr "Critical"
1171 1171  msgid "SUN4U-8002-8A.description"
1172 1172  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1173 1173  msgid "SUN4U-8002-8A.response"
1174 1174  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1175 1175  msgid "SUN4U-8002-8A.impact"
1176 1176  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1177 1177  msgid "SUN4U-8002-8A.action"
1178      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1178 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1179 1179  #
1180 1180  # code: SUN4U-8002-9P
1181 1181  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo
1182 1182  #
1183 1183  msgid "SUN4U-8002-9P.type"
1184 1184  msgstr "Fault"
1185 1185  msgid "SUN4U-8002-9P.severity"
1186 1186  msgstr "Critical"
1187 1187  msgid "SUN4U-8002-9P.description"
1188 1188  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1189 1189  msgid "SUN4U-8002-9P.response"
1190 1190  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1191 1191  msgid "SUN4U-8002-9P.impact"
1192 1192  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1193 1193  msgid "SUN4U-8002-9P.action"
1194      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1194 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1195 1195  #
1196 1196  # code: SUN4U-8002-A5
1197 1197  # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo
1198 1198  #
1199 1199  msgid "SUN4U-8002-A5.type"
1200 1200  msgstr "Fault"
1201 1201  msgid "SUN4U-8002-A5.severity"
1202 1202  msgstr "Critical"
1203 1203  msgid "SUN4U-8002-A5.description"
1204 1204  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1205 1205  msgid "SUN4U-8002-A5.response"
1206 1206  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1207 1207  msgid "SUN4U-8002-A5.impact"
1208 1208  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1209 1209  msgid "SUN4U-8002-A5.action"
1210      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1210 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1211 1211  #
1212 1212  # code: SUN4U-8002-CS
1213 1213  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo
1214 1214  #
1215 1215  msgid "SUN4U-8002-CS.type"
1216 1216  msgstr "Fault"
1217 1217  msgid "SUN4U-8002-CS.severity"
1218 1218  msgstr "Critical"
1219 1219  msgid "SUN4U-8002-CS.description"
1220 1220  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1221 1221  msgid "SUN4U-8002-CS.response"
1222 1222  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1223 1223  msgid "SUN4U-8002-CS.impact"
1224 1224  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1225 1225  msgid "SUN4U-8002-CS.action"
1226      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1226 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1227 1227  #
1228 1228  # code: SUN4U-8002-D3
1229 1229  # keys: fault.io.hbus fault.io.schizo
1230 1230  #
1231 1231  msgid "SUN4U-8002-D3.type"
1232 1232  msgstr "Fault"
1233 1233  msgid "SUN4U-8002-D3.severity"
1234 1234  msgstr "Critical"
1235 1235  msgid "SUN4U-8002-D3.description"
1236 1236  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1237 1237  msgid "SUN4U-8002-D3.response"
1238 1238  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1239 1239  msgid "SUN4U-8002-D3.impact"
1240 1240  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1241 1241  msgid "SUN4U-8002-D3.action"
1242      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1242 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1243 1243  #
1244 1244  # code: SUN4U-8002-EY
1245 1245  # keys: defect.io.pci.driver fault.io.hbus fault.io.schizo
1246 1246  #
1247 1247  msgid "SUN4U-8002-EY.type"
1248 1248  msgstr "Fault"
1249 1249  msgid "SUN4U-8002-EY.severity"
1250 1250  msgstr "Critical"
1251 1251  msgid "SUN4U-8002-EY.description"
1252 1252  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1253 1253  msgid "SUN4U-8002-EY.response"
1254 1254  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1255 1255  msgid "SUN4U-8002-EY.impact"
1256 1256  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1257 1257  msgid "SUN4U-8002-EY.action"
1258      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1258 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1259 1259  #
1260 1260  # code: SUN4U-8002-FD
1261 1261  # keys: fault.io.hbus fault.io.pci.bus fault.io.schizo
1262 1262  #
1263 1263  msgid "SUN4U-8002-FD.type"
1264 1264  msgstr "Fault"
1265 1265  msgid "SUN4U-8002-FD.severity"
1266 1266  msgstr "Critical"
1267 1267  msgid "SUN4U-8002-FD.description"
1268 1268  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1269 1269  msgid "SUN4U-8002-FD.response"
1270 1270  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1271 1271  msgid "SUN4U-8002-FD.impact"
1272 1272  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1273 1273  msgid "SUN4U-8002-FD.action"
1274      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1274 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1275 1275  #
1276 1276  # code: SUN4U-8002-GH
1277 1277  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo
1278 1278  #
1279 1279  msgid "SUN4U-8002-GH.type"
1280 1280  msgstr "Fault"
1281 1281  msgid "SUN4U-8002-GH.severity"
1282 1282  msgstr "Critical"
1283 1283  msgid "SUN4U-8002-GH.description"
1284 1284  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1285 1285  msgid "SUN4U-8002-GH.response"
1286 1286  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1287 1287  msgid "SUN4U-8002-GH.impact"
1288 1288  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1289 1289  msgid "SUN4U-8002-GH.action"
1290      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1290 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1291 1291  #
1292 1292  # code: SUN4U-8002-HC
1293 1293  # keys: fault.io.hbus fault.io.pci.device fault.io.schizo
1294 1294  #
1295 1295  msgid "SUN4U-8002-HC.type"
1296 1296  msgstr "Fault"
1297 1297  msgid "SUN4U-8002-HC.severity"
1298 1298  msgstr "Critical"
1299 1299  msgid "SUN4U-8002-HC.description"
1300 1300  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1301 1301  msgid "SUN4U-8002-HC.response"
1302 1302  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1303 1303  msgid "SUN4U-8002-HC.impact"
1304 1304  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1305 1305  msgid "SUN4U-8002-HC.action"
1306      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1306 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1307 1307  #
1308 1308  # code: SUN4U-8002-JQ
1309 1309  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo
1310 1310  #
1311 1311  msgid "SUN4U-8002-JQ.type"
1312 1312  msgstr "Fault"
1313 1313  msgid "SUN4U-8002-JQ.severity"
1314 1314  msgstr "Critical"
1315 1315  msgid "SUN4U-8002-JQ.description"
1316 1316  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1317 1317  msgid "SUN4U-8002-JQ.response"
1318 1318  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1319 1319  msgid "SUN4U-8002-JQ.impact"
1320 1320  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1321 1321  msgid "SUN4U-8002-JQ.action"
1322      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1322 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1323 1323  #
1324 1324  # code: SUN4U-8002-K4
1325 1325  # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1326 1326  #
1327 1327  msgid "SUN4U-8002-K4.type"
1328 1328  msgstr "Fault"
1329 1329  msgid "SUN4U-8002-K4.severity"
1330 1330  msgstr "Critical"
1331 1331  msgid "SUN4U-8002-K4.description"
1332 1332  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1333 1333  msgid "SUN4U-8002-K4.response"
1334 1334  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1335 1335  msgid "SUN4U-8002-K4.impact"
1336 1336  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1337 1337  msgid "SUN4U-8002-K4.action"
1338      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1338 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1339 1339  #
1340 1340  # code: SUN4U-8002-LR
1341 1341  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1342 1342  #
1343 1343  msgid "SUN4U-8002-LR.type"
1344 1344  msgstr "Fault"
1345 1345  msgid "SUN4U-8002-LR.severity"
1346 1346  msgstr "Critical"
1347 1347  msgid "SUN4U-8002-LR.description"
1348 1348  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1349 1349  msgid "SUN4U-8002-LR.response"
1350 1350  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1351 1351  msgid "SUN4U-8002-LR.impact"
1352 1352  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1353 1353  msgid "SUN4U-8002-LR.action"
1354      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1354 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1355 1355  #
1356 1356  # code: SUN4U-8002-M2
1357 1357  # keys: fault.io.datapath fault.io.hbus fault.io.schizo
1358 1358  #
1359 1359  msgid "SUN4U-8002-M2.type"
1360 1360  msgstr "Fault"
1361 1361  msgid "SUN4U-8002-M2.severity"
1362 1362  msgstr "Critical"
1363 1363  msgid "SUN4U-8002-M2.description"
1364 1364  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1365 1365  msgid "SUN4U-8002-M2.response"
1366 1366  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1367 1367  msgid "SUN4U-8002-M2.impact"
1368 1368  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1369 1369  msgid "SUN4U-8002-M2.action"
1370      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1370 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1371 1371  #
1372 1372  # code: SUN4U-8002-NX
1373 1373  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo
1374 1374  #
1375 1375  msgid "SUN4U-8002-NX.type"
1376 1376  msgstr "Fault"
1377 1377  msgid "SUN4U-8002-NX.severity"
1378 1378  msgstr "Critical"
1379 1379  msgid "SUN4U-8002-NX.description"
1380 1380  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1381 1381  msgid "SUN4U-8002-NX.response"
1382 1382  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1383 1383  msgid "SUN4U-8002-NX.impact"
1384 1384  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1385 1385  msgid "SUN4U-8002-NX.action"
1386      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1386 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1387 1387  #
1388 1388  # code: SUN4U-8002-PE
1389 1389  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo
1390 1390  #
1391 1391  msgid "SUN4U-8002-PE.type"
1392 1392  msgstr "Fault"
1393 1393  msgid "SUN4U-8002-PE.severity"
1394 1394  msgstr "Critical"
1395 1395  msgid "SUN4U-8002-PE.description"
1396 1396  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1397 1397  msgid "SUN4U-8002-PE.response"
1398 1398  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1399 1399  msgid "SUN4U-8002-PE.impact"
1400 1400  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1401 1401  msgid "SUN4U-8002-PE.action"
1402      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1402 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1403 1403  #
1404 1404  # code: SUN4U-8002-QJ
1405 1405  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo
1406 1406  #
1407 1407  msgid "SUN4U-8002-QJ.type"
1408 1408  msgstr "Fault"
1409 1409  msgid "SUN4U-8002-QJ.severity"
1410 1410  msgstr "Critical"
1411 1411  msgid "SUN4U-8002-QJ.description"
1412 1412  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1413 1413  msgid "SUN4U-8002-QJ.response"
1414 1414  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1415 1415  msgid "SUN4U-8002-QJ.impact"
1416 1416  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1417 1417  msgid "SUN4U-8002-QJ.action"
1418      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1418 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1419 1419  #
1420 1420  # code: SUN4U-8002-RS
1421 1421  # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo
1422 1422  #
1423 1423  msgid "SUN4U-8002-RS.type"
1424 1424  msgstr "Fault"
1425 1425  msgid "SUN4U-8002-RS.severity"
1426 1426  msgstr "Critical"
1427 1427  msgid "SUN4U-8002-RS.description"
1428 1428  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1429 1429  msgid "SUN4U-8002-RS.response"
1430 1430  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1431 1431  msgid "SUN4U-8002-RS.impact"
1432 1432  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1433 1433  msgid "SUN4U-8002-RS.action"
1434      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1434 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1435 1435  #
1436 1436  # code: SUN4U-8002-S5
1437 1437  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo
1438 1438  #
1439 1439  msgid "SUN4U-8002-S5.type"
1440 1440  msgstr "Fault"
1441 1441  msgid "SUN4U-8002-S5.severity"
1442 1442  msgstr "Critical"
1443 1443  msgid "SUN4U-8002-S5.description"
1444 1444  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1445 1445  msgid "SUN4U-8002-S5.response"
1446 1446  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1447 1447  msgid "SUN4U-8002-S5.impact"
1448 1448  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1449 1449  msgid "SUN4U-8002-S5.action"
1450      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1450 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1451 1451  #
1452 1452  # code: SUN4U-8002-TP
1453 1453  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1454 1454  #
1455 1455  msgid "SUN4U-8002-TP.type"
1456 1456  msgstr "Fault"
1457 1457  msgid "SUN4U-8002-TP.severity"
1458 1458  msgstr "Critical"
1459 1459  msgid "SUN4U-8002-TP.description"
1460 1460  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1461 1461  msgid "SUN4U-8002-TP.response"
1462 1462  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1463 1463  msgid "SUN4U-8002-TP.impact"
1464 1464  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1465 1465  msgid "SUN4U-8002-TP.action"
1466      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1466 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1467 1467  #
1468 1468  # code: SUN4U-8002-UA
1469 1469  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo
1470 1470  #
1471 1471  msgid "SUN4U-8002-UA.type"
1472 1472  msgstr "Fault"
1473 1473  msgid "SUN4U-8002-UA.severity"
1474 1474  msgstr "Critical"
1475 1475  msgid "SUN4U-8002-UA.description"
1476 1476  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1477 1477  msgid "SUN4U-8002-UA.response"
1478 1478  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1479 1479  msgid "SUN4U-8002-UA.impact"
1480 1480  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1481 1481  msgid "SUN4U-8002-UA.action"
1482      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1482 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1483 1483  #
1484 1484  # code: SUN4U-8002-VH
1485 1485  # keys: fault.io.xmits
1486 1486  #
1487 1487  msgid "SUN4U-8002-VH.type"
1488 1488  msgstr "Fault"
1489 1489  msgid "SUN4U-8002-VH.severity"
1490 1490  msgstr "Critical"
1491 1491  msgid "SUN4U-8002-VH.description"
1492 1492  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1493 1493  msgid "SUN4U-8002-VH.response"
1494 1494  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1495 1495  msgid "SUN4U-8002-VH.impact"
1496 1496  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1497 1497  msgid "SUN4U-8002-VH.action"
1498      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1498 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1499 1499  #
1500 1500  # code: SUN4U-8002-WD
1501 1501  # keys: defect.io.pci.driver fault.io.xmits
1502 1502  #
1503 1503  msgid "SUN4U-8002-WD.type"
1504 1504  msgstr "Fault"
1505 1505  msgid "SUN4U-8002-WD.severity"
1506 1506  msgstr "Critical"
1507 1507  msgid "SUN4U-8002-WD.description"
1508 1508  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1509 1509  msgid "SUN4U-8002-WD.response"
1510 1510  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1511 1511  msgid "SUN4U-8002-WD.impact"
1512 1512  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1513 1513  msgid "SUN4U-8002-WD.action"
1514      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1514 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1515 1515  #
1516 1516  # code: SUN4U-8002-XY
1517 1517  # keys: fault.io.pci.bus fault.io.xmits
1518 1518  #
1519 1519  msgid "SUN4U-8002-XY.type"
1520 1520  msgstr "Fault"
1521 1521  msgid "SUN4U-8002-XY.severity"
1522 1522  msgstr "Critical"
1523 1523  msgid "SUN4U-8002-XY.description"
1524 1524  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1525 1525  msgid "SUN4U-8002-XY.response"
1526 1526  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1527 1527  msgid "SUN4U-8002-XY.impact"
1528 1528  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1529 1529  msgid "SUN4U-8002-XY.action"
1530      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1530 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1531 1531  #
1532 1532  # code: SUN4U-8002-Y3
1533 1533  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.xmits
1534 1534  #
1535 1535  msgid "SUN4U-8002-Y3.type"
1536 1536  msgstr "Fault"
1537 1537  msgid "SUN4U-8002-Y3.severity"
1538 1538  msgstr "Critical"
1539 1539  msgid "SUN4U-8002-Y3.description"
1540 1540  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1541 1541  msgid "SUN4U-8002-Y3.response"
1542 1542  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1543 1543  msgid "SUN4U-8002-Y3.impact"
1544 1544  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1545 1545  msgid "SUN4U-8002-Y3.action"
1546      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1546 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1547 1547  #
1548 1548  # code: SUN4U-8003-0Y
1549 1549  # keys: fault.io.pci.device fault.io.xmits
1550 1550  #
1551 1551  msgid "SUN4U-8003-0Y.type"
1552 1552  msgstr "Fault"
1553 1553  msgid "SUN4U-8003-0Y.severity"
1554 1554  msgstr "Critical"
1555 1555  msgid "SUN4U-8003-0Y.description"
1556 1556  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1557 1557  msgid "SUN4U-8003-0Y.response"
1558 1558  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1559 1559  msgid "SUN4U-8003-0Y.impact"
1560 1560  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1561 1561  msgid "SUN4U-8003-0Y.action"
1562      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1562 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1563 1563  #
1564 1564  # code: SUN4U-8003-13
1565 1565  # keys: defect.io.pci.driver fault.io.pci.device fault.io.xmits
1566 1566  #
1567 1567  msgid "SUN4U-8003-13.type"
1568 1568  msgstr "Fault"
1569 1569  msgid "SUN4U-8003-13.severity"
1570 1570  msgstr "Critical"
1571 1571  msgid "SUN4U-8003-13.description"
1572 1572  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1573 1573  msgid "SUN4U-8003-13.response"
1574 1574  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1575 1575  msgid "SUN4U-8003-13.impact"
1576 1576  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1577 1577  msgid "SUN4U-8003-13.action"
1578      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1578 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1579 1579  #
1580 1580  # code: SUN4U-8003-2H
1581 1581  # keys: fault.io.pci.bus fault.io.pci.device fault.io.xmits
1582 1582  #
1583 1583  msgid "SUN4U-8003-2H.type"
1584 1584  msgstr "Fault"
1585 1585  msgid "SUN4U-8003-2H.severity"
1586 1586  msgstr "Critical"
1587 1587  msgid "SUN4U-8003-2H.description"
1588 1588  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1589 1589  msgid "SUN4U-8003-2H.response"
1590 1590  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1591 1591  msgid "SUN4U-8003-2H.impact"
1592 1592  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1593 1593  msgid "SUN4U-8003-2H.action"
1594      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1594 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1595 1595  #
1596 1596  # code: SUN4U-8003-3D
1597 1597  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.xmits
1598 1598  #
1599 1599  msgid "SUN4U-8003-3D.type"
1600 1600  msgstr "Fault"
1601 1601  msgid "SUN4U-8003-3D.severity"
1602 1602  msgstr "Critical"
1603 1603  msgid "SUN4U-8003-3D.description"
1604 1604  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1605 1605  msgid "SUN4U-8003-3D.response"
1606 1606  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1607 1607  msgid "SUN4U-8003-3D.impact"
1608 1608  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1609 1609  msgid "SUN4U-8003-3D.action"
1610      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1610 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1611 1611  #
1612 1612  # code: SUN4U-8003-4P
1613 1613  # keys: fault.io.datapath fault.io.xmits
1614 1614  #
1615 1615  msgid "SUN4U-8003-4P.type"
1616 1616  msgstr "Fault"
1617 1617  msgid "SUN4U-8003-4P.severity"
1618 1618  msgstr "Critical"
1619 1619  msgid "SUN4U-8003-4P.description"
1620 1620  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1621 1621  msgid "SUN4U-8003-4P.response"
1622 1622  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1623 1623  msgid "SUN4U-8003-4P.impact"
1624 1624  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1625 1625  msgid "SUN4U-8003-4P.action"
1626      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1626 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1627 1627  #
1628 1628  # code: SUN4U-8003-5A
1629 1629  # keys: defect.io.pci.driver fault.io.datapath fault.io.xmits
1630 1630  #
1631 1631  msgid "SUN4U-8003-5A.type"
1632 1632  msgstr "Fault"
1633 1633  msgid "SUN4U-8003-5A.severity"
1634 1634  msgstr "Critical"
1635 1635  msgid "SUN4U-8003-5A.description"
1636 1636  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1637 1637  msgid "SUN4U-8003-5A.response"
1638 1638  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1639 1639  msgid "SUN4U-8003-5A.impact"
1640 1640  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1641 1641  msgid "SUN4U-8003-5A.action"
1642      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1642 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1643 1643  #
1644 1644  # code: SUN4U-8003-6S
1645 1645  # keys: fault.io.datapath fault.io.pci.bus fault.io.xmits
1646 1646  #
1647 1647  msgid "SUN4U-8003-6S.type"
1648 1648  msgstr "Fault"
1649 1649  msgid "SUN4U-8003-6S.severity"
1650 1650  msgstr "Critical"
1651 1651  msgid "SUN4U-8003-6S.description"
1652 1652  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1653 1653  msgid "SUN4U-8003-6S.response"
1654 1654  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1655 1655  msgid "SUN4U-8003-6S.impact"
1656 1656  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1657 1657  msgid "SUN4U-8003-6S.action"
1658      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1658 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1659 1659  #
1660 1660  # code: SUN4U-8003-75
1661 1661  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.xmits
1662 1662  #
1663 1663  msgid "SUN4U-8003-75.type"
1664 1664  msgstr "Fault"
1665 1665  msgid "SUN4U-8003-75.severity"
1666 1666  msgstr "Critical"
1667 1667  msgid "SUN4U-8003-75.description"
1668 1668  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1669 1669  msgid "SUN4U-8003-75.response"
1670 1670  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1671 1671  msgid "SUN4U-8003-75.impact"
1672 1672  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1673 1673  msgid "SUN4U-8003-75.action"
1674      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1674 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1675 1675  #
1676 1676  # code: SUN4U-8003-8E
1677 1677  # keys: fault.io.datapath fault.io.pci.device fault.io.xmits
1678 1678  #
1679 1679  msgid "SUN4U-8003-8E.type"
1680 1680  msgstr "Fault"
1681 1681  msgid "SUN4U-8003-8E.severity"
1682 1682  msgstr "Critical"
1683 1683  msgid "SUN4U-8003-8E.description"
1684 1684  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1685 1685  msgid "SUN4U-8003-8E.response"
1686 1686  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1687 1687  msgid "SUN4U-8003-8E.impact"
1688 1688  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1689 1689  msgid "SUN4U-8003-8E.action"
1690      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1690 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1691 1691  #
1692 1692  # code: SUN4U-8003-9J
1693 1693  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.xmits
1694 1694  #
1695 1695  msgid "SUN4U-8003-9J.type"
1696 1696  msgstr "Fault"
1697 1697  msgid "SUN4U-8003-9J.severity"
1698 1698  msgstr "Critical"
1699 1699  msgid "SUN4U-8003-9J.description"
1700 1700  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1701 1701  msgid "SUN4U-8003-9J.response"
1702 1702  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1703 1703  msgid "SUN4U-8003-9J.impact"
1704 1704  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1705 1705  msgid "SUN4U-8003-9J.action"
1706      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1706 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1707 1707  #
1708 1708  # code: SUN4U-8003-A2
1709 1709  # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits
1710 1710  #
1711 1711  msgid "SUN4U-8003-A2.type"
1712 1712  msgstr "Fault"
1713 1713  msgid "SUN4U-8003-A2.severity"
1714 1714  msgstr "Critical"
1715 1715  msgid "SUN4U-8003-A2.description"
1716 1716  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1717 1717  msgid "SUN4U-8003-A2.response"
1718 1718  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1719 1719  msgid "SUN4U-8003-A2.impact"
1720 1720  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1721 1721  msgid "SUN4U-8003-A2.action"
1722      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1722 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1723 1723  #
1724 1724  # code: SUN4U-8003-CX
1725 1725  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.xmits
1726 1726  #
1727 1727  msgid "SUN4U-8003-CX.type"
1728 1728  msgstr "Fault"
1729 1729  msgid "SUN4U-8003-CX.severity"
1730 1730  msgstr "Critical"
1731 1731  msgid "SUN4U-8003-CX.description"
1732 1732  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1733 1733  msgid "SUN4U-8003-CX.response"
1734 1734  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1735 1735  msgid "SUN4U-8003-CX.impact"
1736 1736  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1737 1737  msgid "SUN4U-8003-CX.action"
1738      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1738 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1739 1739  #
1740 1740  # code: SUN4U-8003-D4
1741 1741  # keys: fault.io.hbus fault.io.xmits
1742 1742  #
1743 1743  msgid "SUN4U-8003-D4.type"
1744 1744  msgstr "Fault"
1745 1745  msgid "SUN4U-8003-D4.severity"
1746 1746  msgstr "Critical"
1747 1747  msgid "SUN4U-8003-D4.description"
1748 1748  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1749 1749  msgid "SUN4U-8003-D4.response"
1750 1750  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1751 1751  msgid "SUN4U-8003-D4.impact"
1752 1752  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1753 1753  msgid "SUN4U-8003-D4.action"
1754      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1754 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1755 1755  #
1756 1756  # code: SUN4U-8003-ER
1757 1757  # keys: defect.io.pci.driver fault.io.hbus fault.io.xmits
1758 1758  #
1759 1759  msgid "SUN4U-8003-ER.type"
1760 1760  msgstr "Fault"
1761 1761  msgid "SUN4U-8003-ER.severity"
1762 1762  msgstr "Critical"
1763 1763  msgid "SUN4U-8003-ER.description"
1764 1764  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1765 1765  msgid "SUN4U-8003-ER.response"
1766 1766  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1767 1767  msgid "SUN4U-8003-ER.impact"
1768 1768  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1769 1769  msgid "SUN4U-8003-ER.action"
1770      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1770 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1771 1771  #
1772 1772  # code: SUN4U-8003-FC
1773 1773  # keys: fault.io.hbus fault.io.pci.bus fault.io.xmits
1774 1774  #
1775 1775  msgid "SUN4U-8003-FC.type"
1776 1776  msgstr "Fault"
1777 1777  msgid "SUN4U-8003-FC.severity"
1778 1778  msgstr "Critical"
1779 1779  msgid "SUN4U-8003-FC.description"
1780 1780  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1781 1781  msgid "SUN4U-8003-FC.response"
1782 1782  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1783 1783  msgid "SUN4U-8003-FC.impact"
1784 1784  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1785 1785  msgid "SUN4U-8003-FC.action"
1786      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1786 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1787 1787  #
1788 1788  # code: SUN4U-8003-GQ
1789 1789  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.xmits
1790 1790  #
1791 1791  msgid "SUN4U-8003-GQ.type"
1792 1792  msgstr "Fault"
1793 1793  msgid "SUN4U-8003-GQ.severity"
1794 1794  msgstr "Critical"
1795 1795  msgid "SUN4U-8003-GQ.description"
1796 1796  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1797 1797  msgid "SUN4U-8003-GQ.response"
1798 1798  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1799 1799  msgid "SUN4U-8003-GQ.impact"
1800 1800  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1801 1801  msgid "SUN4U-8003-GQ.action"
1802      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1802 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1803 1803  #
1804 1804  # code: SUN4U-8003-HD
1805 1805  # keys: fault.io.hbus fault.io.pci.device fault.io.xmits
1806 1806  #
1807 1807  msgid "SUN4U-8003-HD.type"
1808 1808  msgstr "Fault"
1809 1809  msgid "SUN4U-8003-HD.severity"
1810 1810  msgstr "Critical"
1811 1811  msgid "SUN4U-8003-HD.description"
1812 1812  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1813 1813  msgid "SUN4U-8003-HD.response"
1814 1814  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1815 1815  msgid "SUN4U-8003-HD.impact"
1816 1816  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1817 1817  msgid "SUN4U-8003-HD.action"
1818      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1818 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1819 1819  #
1820 1820  # code: SUN4U-8003-JH
1821 1821  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.xmits
1822 1822  #
1823 1823  msgid "SUN4U-8003-JH.type"
1824 1824  msgstr "Fault"
1825 1825  msgid "SUN4U-8003-JH.severity"
1826 1826  msgstr "Critical"
1827 1827  msgid "SUN4U-8003-JH.description"
1828 1828  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1829 1829  msgid "SUN4U-8003-JH.response"
1830 1830  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1831 1831  msgid "SUN4U-8003-JH.impact"
1832 1832  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1833 1833  msgid "SUN4U-8003-JH.action"
1834      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1834 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1835 1835  #
1836 1836  # code: SUN4U-8003-K3
1837 1837  # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1838 1838  #
1839 1839  msgid "SUN4U-8003-K3.type"
1840 1840  msgstr "Fault"
1841 1841  msgid "SUN4U-8003-K3.severity"
1842 1842  msgstr "Critical"
1843 1843  msgid "SUN4U-8003-K3.description"
1844 1844  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1845 1845  msgid "SUN4U-8003-K3.response"
1846 1846  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1847 1847  msgid "SUN4U-8003-K3.impact"
1848 1848  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1849 1849  msgid "SUN4U-8003-K3.action"
1850      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1850 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1851 1851  #
1852 1852  # code: SUN4U-8003-LY
1853 1853  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1854 1854  #
1855 1855  msgid "SUN4U-8003-LY.type"
1856 1856  msgstr "Fault"
1857 1857  msgid "SUN4U-8003-LY.severity"
1858 1858  msgstr "Critical"
1859 1859  msgid "SUN4U-8003-LY.description"
1860 1860  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1861 1861  msgid "SUN4U-8003-LY.response"
1862 1862  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1863 1863  msgid "SUN4U-8003-LY.impact"
1864 1864  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1865 1865  msgid "SUN4U-8003-LY.action"
1866      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1866 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1867 1867  #
1868 1868  # code: SUN4U-8003-M5
1869 1869  # keys: fault.io.datapath fault.io.hbus fault.io.xmits
1870 1870  #
1871 1871  msgid "SUN4U-8003-M5.type"
1872 1872  msgstr "Fault"
1873 1873  msgid "SUN4U-8003-M5.severity"
1874 1874  msgstr "Critical"
1875 1875  msgid "SUN4U-8003-M5.description"
1876 1876  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1877 1877  msgid "SUN4U-8003-M5.response"
1878 1878  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1879 1879  msgid "SUN4U-8003-M5.impact"
1880 1880  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1881 1881  msgid "SUN4U-8003-M5.action"
1882      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1882 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1883 1883  #
1884 1884  # code: SUN4U-8003-NS
1885 1885  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.xmits
1886 1886  #
1887 1887  msgid "SUN4U-8003-NS.type"
1888 1888  msgstr "Fault"
1889 1889  msgid "SUN4U-8003-NS.severity"
1890 1890  msgstr "Critical"
1891 1891  msgid "SUN4U-8003-NS.description"
1892 1892  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1893 1893  msgid "SUN4U-8003-NS.response"
1894 1894  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1895 1895  msgid "SUN4U-8003-NS.impact"
1896 1896  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1897 1897  msgid "SUN4U-8003-NS.action"
1898      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1898 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1899 1899  #
1900 1900  # code: SUN4U-8003-PA
1901 1901  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits
1902 1902  #
1903 1903  msgid "SUN4U-8003-PA.type"
1904 1904  msgstr "Fault"
1905 1905  msgid "SUN4U-8003-PA.severity"
1906 1906  msgstr "Critical"
1907 1907  msgid "SUN4U-8003-PA.description"
1908 1908  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1909 1909  msgid "SUN4U-8003-PA.response"
1910 1910  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1911 1911  msgid "SUN4U-8003-PA.impact"
1912 1912  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1913 1913  msgid "SUN4U-8003-PA.action"
1914      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1914 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1915 1915  #
1916 1916  # code: SUN4U-8003-QP
1917 1917  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.xmits
1918 1918  #
1919 1919  msgid "SUN4U-8003-QP.type"
1920 1920  msgstr "Fault"
1921 1921  msgid "SUN4U-8003-QP.severity"
1922 1922  msgstr "Critical"
1923 1923  msgid "SUN4U-8003-QP.description"
1924 1924  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1925 1925  msgid "SUN4U-8003-QP.response"
1926 1926  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1927 1927  msgid "SUN4U-8003-QP.impact"
1928 1928  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1929 1929  msgid "SUN4U-8003-QP.action"
1930      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1930 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1931 1931  #
1932 1932  # code: SUN4U-8003-RX
1933 1933  # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits
1934 1934  #
1935 1935  msgid "SUN4U-8003-RX.type"
1936 1936  msgstr "Fault"
1937 1937  msgid "SUN4U-8003-RX.severity"
1938 1938  msgstr "Critical"
1939 1939  msgid "SUN4U-8003-RX.description"
1940 1940  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1941 1941  msgid "SUN4U-8003-RX.response"
1942 1942  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1943 1943  msgid "SUN4U-8003-RX.impact"
1944 1944  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1945 1945  msgid "SUN4U-8003-RX.action"
1946      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1946 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1947 1947  #
1948 1948  # code: SUN4U-8003-S2
1949 1949  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.xmits
1950 1950  #
1951 1951  msgid "SUN4U-8003-S2.type"
1952 1952  msgstr "Fault"
1953 1953  msgid "SUN4U-8003-S2.severity"
1954 1954  msgstr "Critical"
1955 1955  msgid "SUN4U-8003-S2.description"
1956 1956  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1957 1957  msgid "SUN4U-8003-S2.response"
1958 1958  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1959 1959  msgid "SUN4U-8003-S2.impact"
1960 1960  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1961 1961  msgid "SUN4U-8003-S2.action"
1962      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1962 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1963 1963  #
1964 1964  # code: SUN4U-8003-TJ
1965 1965  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1966 1966  #
1967 1967  msgid "SUN4U-8003-TJ.type"
1968 1968  msgstr "Fault"
1969 1969  msgid "SUN4U-8003-TJ.severity"
1970 1970  msgstr "Critical"
1971 1971  msgid "SUN4U-8003-TJ.description"
1972 1972  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
1973 1973  msgid "SUN4U-8003-TJ.response"
1974 1974  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1975 1975  msgid "SUN4U-8003-TJ.impact"
1976 1976  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1977 1977  msgid "SUN4U-8003-TJ.action"
1978      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     1978 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
1979 1979  #
1980 1980  # code: SUN4U-8003-UE
1981 1981  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.xmits
1982 1982  #
1983 1983  msgid "SUN4U-8003-UE.type"
1984 1984  msgstr "Fault"
1985 1985  msgid "SUN4U-8003-UE.severity"
1986 1986  msgstr "Critical"
1987 1987  msgid "SUN4U-8003-UE.description"
1988 1988  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
1989 1989  msgid "SUN4U-8003-UE.response"
1990 1990  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
1991 1991  msgid "SUN4U-8003-UE.impact"
1992 1992  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
1993 1993  msgid "SUN4U-8003-UE.action"
1994      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     1994 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
1995 1995  #
1996 1996  # code: SUN4U-8003-VQ
1997 1997  # keys: fault.io.schizo fault.io.xmits
1998 1998  #
1999 1999  msgid "SUN4U-8003-VQ.type"
2000 2000  msgstr "Fault"
2001 2001  msgid "SUN4U-8003-VQ.severity"
2002 2002  msgstr "Critical"
2003 2003  msgid "SUN4U-8003-VQ.description"
2004 2004  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2005 2005  msgid "SUN4U-8003-VQ.response"
2006 2006  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2007 2007  msgid "SUN4U-8003-VQ.impact"
2008 2008  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2009 2009  msgid "SUN4U-8003-VQ.action"
2010      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2010 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2011 2011  #
2012 2012  # code: SUN4U-8003-WC
2013 2013  # keys: defect.io.pci.driver fault.io.schizo fault.io.xmits
2014 2014  #
2015 2015  msgid "SUN4U-8003-WC.type"
2016 2016  msgstr "Fault"
2017 2017  msgid "SUN4U-8003-WC.severity"
2018 2018  msgstr "Critical"
2019 2019  msgid "SUN4U-8003-WC.description"
2020 2020  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2021 2021  msgid "SUN4U-8003-WC.response"
2022 2022  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2023 2023  msgid "SUN4U-8003-WC.impact"
2024 2024  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2025 2025  msgid "SUN4U-8003-WC.action"
2026      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2026 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2027 2027  #
2028 2028  # code: SUN4U-8003-XR
2029 2029  # keys: fault.io.pci.bus fault.io.schizo fault.io.xmits
2030 2030  #
2031 2031  msgid "SUN4U-8003-XR.type"
2032 2032  msgstr "Fault"
2033 2033  msgid "SUN4U-8003-XR.severity"
2034 2034  msgstr "Critical"
2035 2035  msgid "SUN4U-8003-XR.description"
2036 2036  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2037 2037  msgid "SUN4U-8003-XR.response"
2038 2038  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2039 2039  msgid "SUN4U-8003-XR.impact"
2040 2040  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2041 2041  msgid "SUN4U-8003-XR.action"
2042      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2042 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2043 2043  #
2044 2044  # code: SUN4U-8003-Y4
2045 2045  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.schizo fault.io.xmits
2046 2046  #
2047 2047  msgid "SUN4U-8003-Y4.type"
2048 2048  msgstr "Fault"
2049 2049  msgid "SUN4U-8003-Y4.severity"
2050 2050  msgstr "Critical"
2051 2051  msgid "SUN4U-8003-Y4.description"
2052 2052  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2053 2053  msgid "SUN4U-8003-Y4.response"
2054 2054  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2055 2055  msgid "SUN4U-8003-Y4.impact"
2056 2056  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2057 2057  msgid "SUN4U-8003-Y4.action"
2058      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2058 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2059 2059  #
2060 2060  # code: SUN4U-8004-0A
2061 2061  # keys: fault.io.pci.device fault.io.schizo fault.io.xmits
2062 2062  #
2063 2063  msgid "SUN4U-8004-0A.type"
2064 2064  msgstr "Fault"
2065 2065  msgid "SUN4U-8004-0A.severity"
2066 2066  msgstr "Critical"
2067 2067  msgid "SUN4U-8004-0A.description"
2068 2068  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2069 2069  msgid "SUN4U-8004-0A.response"
2070 2070  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2071 2071  msgid "SUN4U-8004-0A.impact"
2072 2072  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2073 2073  msgid "SUN4U-8004-0A.action"
2074      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2074 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2075 2075  #
2076 2076  # code: SUN4U-8004-1P
2077 2077  # keys: defect.io.pci.driver fault.io.pci.device fault.io.schizo fault.io.xmits
2078 2078  #
2079 2079  msgid "SUN4U-8004-1P.type"
2080 2080  msgstr "Fault"
2081 2081  msgid "SUN4U-8004-1P.severity"
2082 2082  msgstr "Critical"
2083 2083  msgid "SUN4U-8004-1P.description"
2084 2084  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2085 2085  msgid "SUN4U-8004-1P.response"
2086 2086  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2087 2087  msgid "SUN4U-8004-1P.impact"
2088 2088  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2089 2089  msgid "SUN4U-8004-1P.action"
2090      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2090 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2091 2091  #
2092 2092  # code: SUN4U-8004-25
2093 2093  # keys: fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2094 2094  #
2095 2095  msgid "SUN4U-8004-25.type"
2096 2096  msgstr "Fault"
2097 2097  msgid "SUN4U-8004-25.severity"
2098 2098  msgstr "Critical"
2099 2099  msgid "SUN4U-8004-25.description"
2100 2100  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2101 2101  msgid "SUN4U-8004-25.response"
2102 2102  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2103 2103  msgid "SUN4U-8004-25.impact"
2104 2104  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2105 2105  msgid "SUN4U-8004-25.action"
2106      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2106 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2107 2107  #
2108 2108  # code: SUN4U-8004-3S
2109 2109  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2110 2110  #
2111 2111  msgid "SUN4U-8004-3S.type"
2112 2112  msgstr "Fault"
2113 2113  msgid "SUN4U-8004-3S.severity"
2114 2114  msgstr "Critical"
2115 2115  msgid "SUN4U-8004-3S.description"
2116 2116  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2117 2117  msgid "SUN4U-8004-3S.response"
2118 2118  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2119 2119  msgid "SUN4U-8004-3S.impact"
2120 2120  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2121 2121  msgid "SUN4U-8004-3S.action"
2122      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2122 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2123 2123  #
2124 2124  # code: SUN4U-8004-43
2125 2125  # keys: fault.io.datapath fault.io.schizo fault.io.xmits
2126 2126  #
2127 2127  msgid "SUN4U-8004-43.type"
2128 2128  msgstr "Fault"
2129 2129  msgid "SUN4U-8004-43.severity"
2130 2130  msgstr "Critical"
2131 2131  msgid "SUN4U-8004-43.description"
2132 2132  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2133 2133  msgid "SUN4U-8004-43.response"
2134 2134  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2135 2135  msgid "SUN4U-8004-43.impact"
2136 2136  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2137 2137  msgid "SUN4U-8004-43.action"
2138      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2138 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2139 2139  #
2140 2140  # code: SUN4U-8004-5Y
2141 2141  # keys: defect.io.pci.driver fault.io.datapath fault.io.schizo fault.io.xmits
2142 2142  #
2143 2143  msgid "SUN4U-8004-5Y.type"
2144 2144  msgstr "Fault"
2145 2145  msgid "SUN4U-8004-5Y.severity"
2146 2146  msgstr "Critical"
2147 2147  msgid "SUN4U-8004-5Y.description"
2148 2148  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2149 2149  msgid "SUN4U-8004-5Y.response"
2150 2150  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2151 2151  msgid "SUN4U-8004-5Y.impact"
2152 2152  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2153 2153  msgid "SUN4U-8004-5Y.action"
2154      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2154 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2155 2155  #
2156 2156  # code: SUN4U-8004-6D
2157 2157  # keys: fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits
2158 2158  #
2159 2159  msgid "SUN4U-8004-6D.type"
2160 2160  msgstr "Fault"
2161 2161  msgid "SUN4U-8004-6D.severity"
2162 2162  msgstr "Critical"
2163 2163  msgid "SUN4U-8004-6D.description"
2164 2164  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2165 2165  msgid "SUN4U-8004-6D.response"
2166 2166  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2167 2167  msgid "SUN4U-8004-6D.impact"
2168 2168  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2169 2169  msgid "SUN4U-8004-6D.action"
2170      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2170 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2171 2171  #
2172 2172  # code: SUN4U-8004-7H
2173 2173  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.schizo fault.io.xmits
2174 2174  #
2175 2175  msgid "SUN4U-8004-7H.type"
2176 2176  msgstr "Fault"
2177 2177  msgid "SUN4U-8004-7H.severity"
2178 2178  msgstr "Critical"
2179 2179  msgid "SUN4U-8004-7H.description"
2180 2180  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2181 2181  msgid "SUN4U-8004-7H.response"
2182 2182  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2183 2183  msgid "SUN4U-8004-7H.impact"
2184 2184  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2185 2185  msgid "SUN4U-8004-7H.action"
2186      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2186 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2187 2187  #
2188 2188  # code: SUN4U-8004-8R
2189 2189  # keys: fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits
2190 2190  #
2191 2191  msgid "SUN4U-8004-8R.type"
2192 2192  msgstr "Fault"
2193 2193  msgid "SUN4U-8004-8R.severity"
2194 2194  msgstr "Critical"
2195 2195  msgid "SUN4U-8004-8R.description"
2196 2196  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2197 2197  msgid "SUN4U-8004-8R.response"
2198 2198  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2199 2199  msgid "SUN4U-8004-8R.impact"
2200 2200  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2201 2201  msgid "SUN4U-8004-8R.action"
2202      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2202 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2203 2203  #
2204 2204  # code: SUN4U-8004-94
2205 2205  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.schizo fault.io.xmits
2206 2206  #
2207 2207  msgid "SUN4U-8004-94.type"
2208 2208  msgstr "Fault"
2209 2209  msgid "SUN4U-8004-94.severity"
2210 2210  msgstr "Critical"
2211 2211  msgid "SUN4U-8004-94.description"
2212 2212  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2213 2213  msgid "SUN4U-8004-94.response"
2214 2214  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2215 2215  msgid "SUN4U-8004-94.impact"
2216 2216  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2217 2217  msgid "SUN4U-8004-94.action"
2218      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2218 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2219 2219  #
2220 2220  # code: SUN4U-8004-AQ
2221 2221  # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2222 2222  #
2223 2223  msgid "SUN4U-8004-AQ.type"
2224 2224  msgstr "Fault"
2225 2225  msgid "SUN4U-8004-AQ.severity"
2226 2226  msgstr "Critical"
2227 2227  msgid "SUN4U-8004-AQ.description"
2228 2228  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2229 2229  msgid "SUN4U-8004-AQ.response"
2230 2230  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2231 2231  msgid "SUN4U-8004-AQ.impact"
2232 2232  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2233 2233  msgid "SUN4U-8004-AQ.action"
2234      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2234 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2235 2235  #
2236 2236  # code: SUN4U-8004-CC
2237 2237  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2238 2238  #
2239 2239  msgid "SUN4U-8004-CC.type"
2240 2240  msgstr "Fault"
2241 2241  msgid "SUN4U-8004-CC.severity"
2242 2242  msgstr "Critical"
2243 2243  msgid "SUN4U-8004-CC.description"
2244 2244  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2245 2245  msgid "SUN4U-8004-CC.response"
2246 2246  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2247 2247  msgid "SUN4U-8004-CC.impact"
2248 2248  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2249 2249  msgid "SUN4U-8004-CC.action"
2250      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2250 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2251 2251  #
2252 2252  # code: SUN4U-8004-DJ
2253 2253  # keys: fault.io.hbus fault.io.schizo fault.io.xmits
2254 2254  #
2255 2255  msgid "SUN4U-8004-DJ.type"
2256 2256  msgstr "Fault"
2257 2257  msgid "SUN4U-8004-DJ.severity"
2258 2258  msgstr "Critical"
2259 2259  msgid "SUN4U-8004-DJ.description"
2260 2260  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2261 2261  msgid "SUN4U-8004-DJ.response"
2262 2262  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2263 2263  msgid "SUN4U-8004-DJ.impact"
2264 2264  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2265 2265  msgid "SUN4U-8004-DJ.action"
2266      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2266 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2267 2267  #
2268 2268  # code: SUN4U-8004-EE
2269 2269  # keys: defect.io.pci.driver fault.io.hbus fault.io.schizo fault.io.xmits
2270 2270  #
2271 2271  msgid "SUN4U-8004-EE.type"
2272 2272  msgstr "Fault"
2273 2273  msgid "SUN4U-8004-EE.severity"
2274 2274  msgstr "Critical"
2275 2275  msgid "SUN4U-8004-EE.description"
2276 2276  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2277 2277  msgid "SUN4U-8004-EE.response"
2278 2278  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2279 2279  msgid "SUN4U-8004-EE.impact"
2280 2280  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2281 2281  msgid "SUN4U-8004-EE.action"
2282      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2282 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2283 2283  #
2284 2284  # code: SUN4U-8004-FX
2285 2285  # keys: fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2286 2286  #
2287 2287  msgid "SUN4U-8004-FX.type"
2288 2288  msgstr "Fault"
2289 2289  msgid "SUN4U-8004-FX.severity"
2290 2290  msgstr "Critical"
2291 2291  msgid "SUN4U-8004-FX.description"
2292 2292  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2293 2293  msgid "SUN4U-8004-FX.response"
2294 2294  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2295 2295  msgid "SUN4U-8004-FX.impact"
2296 2296  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2297 2297  msgid "SUN4U-8004-FX.action"
2298      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2298 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2299 2299  #
2300 2300  # code: SUN4U-8004-G2
2301 2301  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2302 2302  #
2303 2303  msgid "SUN4U-8004-G2.type"
2304 2304  msgstr "Fault"
2305 2305  msgid "SUN4U-8004-G2.severity"
2306 2306  msgstr "Critical"
2307 2307  msgid "SUN4U-8004-G2.description"
2308 2308  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2309 2309  msgid "SUN4U-8004-G2.response"
2310 2310  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2311 2311  msgid "SUN4U-8004-G2.impact"
2312 2312  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2313 2313  msgid "SUN4U-8004-G2.action"
2314      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2314 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2315 2315  #
2316 2316  # code: SUN4U-8004-HS
2317 2317  # keys: fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2318 2318  #
2319 2319  msgid "SUN4U-8004-HS.type"
2320 2320  msgstr "Fault"
2321 2321  msgid "SUN4U-8004-HS.severity"
2322 2322  msgstr "Critical"
2323 2323  msgid "SUN4U-8004-HS.description"
2324 2324  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2325 2325  msgid "SUN4U-8004-HS.response"
2326 2326  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2327 2327  msgid "SUN4U-8004-HS.impact"
2328 2328  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2329 2329  msgid "SUN4U-8004-HS.action"
2330      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2330 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2331 2331  #
2332 2332  # code: SUN4U-8004-J5
2333 2333  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2334 2334  #
2335 2335  msgid "SUN4U-8004-J5.type"
2336 2336  msgstr "Fault"
2337 2337  msgid "SUN4U-8004-J5.severity"
2338 2338  msgstr "Critical"
2339 2339  msgid "SUN4U-8004-J5.description"
2340 2340  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2341 2341  msgid "SUN4U-8004-J5.response"
2342 2342  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2343 2343  msgid "SUN4U-8004-J5.impact"
2344 2344  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2345 2345  msgid "SUN4U-8004-J5.action"
2346      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2346 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2347 2347  #
2348 2348  # code: SUN4U-8004-KP
2349 2349  # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2350 2350  #
2351 2351  msgid "SUN4U-8004-KP.type"
2352 2352  msgstr "Fault"
2353 2353  msgid "SUN4U-8004-KP.severity"
2354 2354  msgstr "Critical"
2355 2355  msgid "SUN4U-8004-KP.description"
2356 2356  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2357 2357  msgid "SUN4U-8004-KP.response"
2358 2358  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2359 2359  msgid "SUN4U-8004-KP.impact"
2360 2360  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2361 2361  msgid "SUN4U-8004-KP.action"
2362      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2362 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2363 2363  #
2364 2364  # code: SUN4U-8004-LA
2365 2365  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2366 2366  #
2367 2367  msgid "SUN4U-8004-LA.type"
2368 2368  msgstr "Fault"
2369 2369  msgid "SUN4U-8004-LA.severity"
2370 2370  msgstr "Critical"
2371 2371  msgid "SUN4U-8004-LA.description"
2372 2372  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2373 2373  msgid "SUN4U-8004-LA.response"
2374 2374  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2375 2375  msgid "SUN4U-8004-LA.impact"
2376 2376  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2377 2377  msgid "SUN4U-8004-LA.action"
2378      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2378 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2379 2379  #
2380 2380  # code: SUN4U-8004-MH
2381 2381  # keys: fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits
2382 2382  #
2383 2383  msgid "SUN4U-8004-MH.type"
2384 2384  msgstr "Fault"
2385 2385  msgid "SUN4U-8004-MH.severity"
2386 2386  msgstr "Critical"
2387 2387  msgid "SUN4U-8004-MH.description"
2388 2388  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2389 2389  msgid "SUN4U-8004-MH.response"
2390 2390  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2391 2391  msgid "SUN4U-8004-MH.impact"
2392 2392  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2393 2393  msgid "SUN4U-8004-MH.action"
2394      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2394 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2395 2395  #
2396 2396  # code: SUN4U-8004-ND
2397 2397  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.schizo fault.io.xmits
2398 2398  #
2399 2399  msgid "SUN4U-8004-ND.type"
2400 2400  msgstr "Fault"
2401 2401  msgid "SUN4U-8004-ND.severity"
2402 2402  msgstr "Critical"
2403 2403  msgid "SUN4U-8004-ND.description"
2404 2404  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2405 2405  msgid "SUN4U-8004-ND.response"
2406 2406  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2407 2407  msgid "SUN4U-8004-ND.impact"
2408 2408  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2409 2409  msgid "SUN4U-8004-ND.action"
2410      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2410 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2411 2411  #
2412 2412  # code: SUN4U-8004-PY
2413 2413  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2414 2414  #
2415 2415  msgid "SUN4U-8004-PY.type"
2416 2416  msgstr "Fault"
2417 2417  msgid "SUN4U-8004-PY.severity"
2418 2418  msgstr "Critical"
2419 2419  msgid "SUN4U-8004-PY.description"
2420 2420  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2421 2421  msgid "SUN4U-8004-PY.response"
2422 2422  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2423 2423  msgid "SUN4U-8004-PY.impact"
2424 2424  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2425 2425  msgid "SUN4U-8004-PY.action"
2426      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2426 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2427 2427  #
2428 2428  # code: SUN4U-8004-Q3
2429 2429  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.schizo fault.io.xmits
2430 2430  #
2431 2431  msgid "SUN4U-8004-Q3.type"
2432 2432  msgstr "Fault"
2433 2433  msgid "SUN4U-8004-Q3.severity"
2434 2434  msgstr "Critical"
2435 2435  msgid "SUN4U-8004-Q3.description"
2436 2436  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2437 2437  msgid "SUN4U-8004-Q3.response"
2438 2438  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2439 2439  msgid "SUN4U-8004-Q3.impact"
2440 2440  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2441 2441  msgid "SUN4U-8004-Q3.action"
2442      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2442 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2443 2443  #
2444 2444  # code: SUN4U-8004-RC
2445 2445  # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2446 2446  #
2447 2447  msgid "SUN4U-8004-RC.type"
2448 2448  msgstr "Fault"
2449 2449  msgid "SUN4U-8004-RC.severity"
2450 2450  msgstr "Critical"
2451 2451  msgid "SUN4U-8004-RC.description"
2452 2452  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2453 2453  msgid "SUN4U-8004-RC.response"
2454 2454  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2455 2455  msgid "SUN4U-8004-RC.impact"
2456 2456  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2457 2457  msgid "SUN4U-8004-RC.action"
2458      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2458 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2459 2459  #
2460 2460  # code: SUN4U-8004-SQ
2461 2461  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.schizo fault.io.xmits
2462 2462  #
2463 2463  msgid "SUN4U-8004-SQ.type"
2464 2464  msgstr "Fault"
2465 2465  msgid "SUN4U-8004-SQ.severity"
2466 2466  msgstr "Critical"
2467 2467  msgid "SUN4U-8004-SQ.description"
2468 2468  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2469 2469  msgid "SUN4U-8004-SQ.response"
2470 2470  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2471 2471  msgid "SUN4U-8004-SQ.impact"
2472 2472  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2473 2473  msgid "SUN4U-8004-SQ.action"
2474      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2474 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2475 2475  #
2476 2476  # code: SUN4U-8004-T4
2477 2477  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.schizo fault.io.xmits
2478 2478  #
2479 2479  msgid "SUN4U-8004-T4.type"
2480 2480  msgstr "Fault"
2481 2481  msgid "SUN4U-8004-T4.severity"
2482 2482  msgstr "Critical"
2483 2483  msgid "SUN4U-8004-T4.description"
2484 2484  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2485 2485  msgid "SUN4U-8004-T4.response"
2486 2486  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2487 2487  msgid "SUN4U-8004-T4.impact"
2488 2488  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2489 2489  msgid "SUN4U-8004-T4.action"
2490      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2490 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2491 2491  #
2492 2492  # code: SUN4U-8004-UR
2493 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 2494  #
2495 2495  msgid "SUN4U-8004-UR.type"
2496 2496  msgstr "Fault"
2497 2497  msgid "SUN4U-8004-UR.severity"
2498 2498  msgstr "Critical"
2499 2499  msgid "SUN4U-8004-UR.description"
2500 2500  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2501 2501  msgid "SUN4U-8004-UR.response"
2502 2502  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2503 2503  msgid "SUN4U-8004-UR.impact"
2504 2504  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2505 2505  msgid "SUN4U-8004-UR.action"
2506      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2506 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2507 2507  #
2508 2508  # code: SUN4U-8004-V2
2509 2509  # keys: fault.io.psycho
2510 2510  #
2511 2511  msgid "SUN4U-8004-V2.type"
2512 2512  msgstr "Fault"
2513 2513  msgid "SUN4U-8004-V2.severity"
2514 2514  msgstr "Critical"
2515 2515  msgid "SUN4U-8004-V2.description"
2516 2516  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2517 2517  msgid "SUN4U-8004-V2.response"
2518 2518  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2519 2519  msgid "SUN4U-8004-V2.impact"
2520 2520  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2521 2521  msgid "SUN4U-8004-V2.action"
2522      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2522 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2523 2523  #
2524 2524  # code: SUN4U-8004-WX
2525 2525  # keys: defect.io.pci.driver fault.io.psycho
2526 2526  #
2527 2527  msgid "SUN4U-8004-WX.type"
2528 2528  msgstr "Fault"
2529 2529  msgid "SUN4U-8004-WX.severity"
2530 2530  msgstr "Critical"
2531 2531  msgid "SUN4U-8004-WX.description"
2532 2532  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2533 2533  msgid "SUN4U-8004-WX.response"
2534 2534  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2535 2535  msgid "SUN4U-8004-WX.impact"
2536 2536  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2537 2537  msgid "SUN4U-8004-WX.action"
2538      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2538 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2539 2539  #
2540 2540  # code: SUN4U-8004-XE
2541 2541  # keys: fault.io.datapath fault.io.psycho
2542 2542  #
2543 2543  msgid "SUN4U-8004-XE.type"
2544 2544  msgstr "Fault"
2545 2545  msgid "SUN4U-8004-XE.severity"
2546 2546  msgstr "Critical"
2547 2547  msgid "SUN4U-8004-XE.description"
2548 2548  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2549 2549  msgid "SUN4U-8004-XE.response"
2550 2550  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2551 2551  msgid "SUN4U-8004-XE.impact"
2552 2552  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2553 2553  msgid "SUN4U-8004-XE.action"
2554      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2554 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2555 2555  #
2556 2556  # code: SUN4U-8004-YJ
2557 2557  # keys: defect.io.pci.driver fault.io.datapath fault.io.psycho
2558 2558  #
2559 2559  msgid "SUN4U-8004-YJ.type"
2560 2560  msgstr "Fault"
2561 2561  msgid "SUN4U-8004-YJ.severity"
2562 2562  msgstr "Critical"
2563 2563  msgid "SUN4U-8004-YJ.description"
2564 2564  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2565 2565  msgid "SUN4U-8004-YJ.response"
2566 2566  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2567 2567  msgid "SUN4U-8004-YJ.impact"
2568 2568  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2569 2569  msgid "SUN4U-8004-YJ.action"
2570      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2570 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2571 2571  #
2572 2572  # code: SUN4U-8005-0E
2573 2573  # keys: fault.io.hbus fault.io.psycho
2574 2574  #
2575 2575  msgid "SUN4U-8005-0E.type"
2576 2576  msgstr "Fault"
2577 2577  msgid "SUN4U-8005-0E.severity"
2578 2578  msgstr "Critical"
2579 2579  msgid "SUN4U-8005-0E.description"
2580 2580  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2581 2581  msgid "SUN4U-8005-0E.response"
2582 2582  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2583 2583  msgid "SUN4U-8005-0E.impact"
2584 2584  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2585 2585  msgid "SUN4U-8005-0E.action"
2586      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2586 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2587 2587  #
2588 2588  # code: SUN4U-8005-1J
2589 2589  # keys: defect.io.pci.driver fault.io.hbus fault.io.psycho
2590 2590  #
2591 2591  msgid "SUN4U-8005-1J.type"
2592 2592  msgstr "Fault"
2593 2593  msgid "SUN4U-8005-1J.severity"
2594 2594  msgstr "Critical"
2595 2595  msgid "SUN4U-8005-1J.description"
2596 2596  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2597 2597  msgid "SUN4U-8005-1J.response"
2598 2598  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2599 2599  msgid "SUN4U-8005-1J.impact"
2600 2600  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2601 2601  msgid "SUN4U-8005-1J.action"
2602      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2602 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2603 2603  #
2604 2604  # code: SUN4U-8005-22
2605 2605  # keys: fault.io.datapath fault.io.hbus fault.io.psycho
2606 2606  #
2607 2607  msgid "SUN4U-8005-22.type"
2608 2608  msgstr "Fault"
2609 2609  msgid "SUN4U-8005-22.severity"
2610 2610  msgstr "Critical"
2611 2611  msgid "SUN4U-8005-22.description"
2612 2612  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2613 2613  msgid "SUN4U-8005-22.response"
2614 2614  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2615 2615  msgid "SUN4U-8005-22.impact"
2616 2616  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2617 2617  msgid "SUN4U-8005-22.action"
2618      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2618 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2619 2619  #
2620 2620  # code: SUN4U-8005-3X
2621 2621  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.psycho
2622 2622  #
2623 2623  msgid "SUN4U-8005-3X.type"
2624 2624  msgstr "Fault"
2625 2625  msgid "SUN4U-8005-3X.severity"
2626 2626  msgstr "Critical"
2627 2627  msgid "SUN4U-8005-3X.description"
2628 2628  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2629 2629  msgid "SUN4U-8005-3X.response"
2630 2630  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2631 2631  msgid "SUN4U-8005-3X.impact"
2632 2632  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2633 2633  msgid "SUN4U-8005-3X.action"
2634      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2634 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2635 2635  #
2636 2636  # code: SUN4U-8005-44
2637 2637  # keys: fault.io.pci.bus fault.io.psycho
2638 2638  #
2639 2639  msgid "SUN4U-8005-44.type"
2640 2640  msgstr "Fault"
2641 2641  msgid "SUN4U-8005-44.severity"
2642 2642  msgstr "Critical"
2643 2643  msgid "SUN4U-8005-44.description"
2644 2644  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2645 2645  msgid "SUN4U-8005-44.response"
2646 2646  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2647 2647  msgid "SUN4U-8005-44.impact"
2648 2648  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2649 2649  msgid "SUN4U-8005-44.action"
2650      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2650 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2651 2651  #
2652 2652  # code: SUN4U-8005-5R
2653 2653  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.psycho
2654 2654  #
2655 2655  msgid "SUN4U-8005-5R.type"
2656 2656  msgstr "Fault"
2657 2657  msgid "SUN4U-8005-5R.severity"
2658 2658  msgstr "Critical"
2659 2659  msgid "SUN4U-8005-5R.description"
2660 2660  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2661 2661  msgid "SUN4U-8005-5R.response"
2662 2662  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2663 2663  msgid "SUN4U-8005-5R.impact"
2664 2664  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2665 2665  msgid "SUN4U-8005-5R.action"
2666      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2666 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2667 2667  #
2668 2668  # code: SUN4U-8005-6C
2669 2669  # keys: fault.io.datapath fault.io.pci.bus fault.io.psycho
2670 2670  #
2671 2671  msgid "SUN4U-8005-6C.type"
2672 2672  msgstr "Fault"
2673 2673  msgid "SUN4U-8005-6C.severity"
2674 2674  msgstr "Critical"
2675 2675  msgid "SUN4U-8005-6C.description"
2676 2676  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2677 2677  msgid "SUN4U-8005-6C.response"
2678 2678  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2679 2679  msgid "SUN4U-8005-6C.impact"
2680 2680  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2681 2681  msgid "SUN4U-8005-6C.action"
2682      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2682 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2683 2683  #
2684 2684  # code: SUN4U-8005-7Q
2685 2685  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.psycho
2686 2686  #
2687 2687  msgid "SUN4U-8005-7Q.type"
2688 2688  msgstr "Fault"
2689 2689  msgid "SUN4U-8005-7Q.severity"
2690 2690  msgstr "Critical"
2691 2691  msgid "SUN4U-8005-7Q.description"
2692 2692  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2693 2693  msgid "SUN4U-8005-7Q.response"
2694 2694  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2695 2695  msgid "SUN4U-8005-7Q.impact"
2696 2696  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2697 2697  msgid "SUN4U-8005-7Q.action"
2698      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2698 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2699 2699  #
2700 2700  # code: SUN4U-8005-8Y
2701 2701  # keys: fault.io.hbus fault.io.pci.bus fault.io.psycho
2702 2702  #
2703 2703  msgid "SUN4U-8005-8Y.type"
2704 2704  msgstr "Fault"
2705 2705  msgid "SUN4U-8005-8Y.severity"
2706 2706  msgstr "Critical"
2707 2707  msgid "SUN4U-8005-8Y.description"
2708 2708  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2709 2709  msgid "SUN4U-8005-8Y.response"
2710 2710  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2711 2711  msgid "SUN4U-8005-8Y.impact"
2712 2712  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2713 2713  msgid "SUN4U-8005-8Y.action"
2714      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2714 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2715 2715  #
2716 2716  # code: SUN4U-8005-93
2717 2717  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.psycho
2718 2718  #
2719 2719  msgid "SUN4U-8005-93.type"
2720 2720  msgstr "Fault"
2721 2721  msgid "SUN4U-8005-93.severity"
2722 2722  msgstr "Critical"
2723 2723  msgid "SUN4U-8005-93.description"
2724 2724  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2725 2725  msgid "SUN4U-8005-93.response"
2726 2726  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2727 2727  msgid "SUN4U-8005-93.impact"
2728 2728  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2729 2729  msgid "SUN4U-8005-93.action"
2730      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2730 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2731 2731  #
2732 2732  # code: SUN4U-8005-AH
2733 2733  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho
2734 2734  #
2735 2735  msgid "SUN4U-8005-AH.type"
2736 2736  msgstr "Fault"
2737 2737  msgid "SUN4U-8005-AH.severity"
2738 2738  msgstr "Critical"
2739 2739  msgid "SUN4U-8005-AH.description"
2740 2740  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2741 2741  msgid "SUN4U-8005-AH.response"
2742 2742  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2743 2743  msgid "SUN4U-8005-AH.impact"
2744 2744  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2745 2745  msgid "SUN4U-8005-AH.action"
2746      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2746 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2747 2747  #
2748 2748  # code: SUN4U-8005-CD
2749 2749  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.psycho
2750 2750  #
2751 2751  msgid "SUN4U-8005-CD.type"
2752 2752  msgstr "Fault"
2753 2753  msgid "SUN4U-8005-CD.severity"
2754 2754  msgstr "Critical"
2755 2755  msgid "SUN4U-8005-CD.description"
2756 2756  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2757 2757  msgid "SUN4U-8005-CD.response"
2758 2758  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2759 2759  msgid "SUN4U-8005-CD.impact"
2760 2760  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2761 2761  msgid "SUN4U-8005-CD.action"
2762      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2762 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2763 2763  #
2764 2764  # code: SUN4U-8005-DP
2765 2765  # keys: fault.io.pci.device fault.io.psycho
2766 2766  #
2767 2767  msgid "SUN4U-8005-DP.type"
2768 2768  msgstr "Fault"
2769 2769  msgid "SUN4U-8005-DP.severity"
2770 2770  msgstr "Critical"
2771 2771  msgid "SUN4U-8005-DP.description"
2772 2772  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2773 2773  msgid "SUN4U-8005-DP.response"
2774 2774  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2775 2775  msgid "SUN4U-8005-DP.impact"
2776 2776  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2777 2777  msgid "SUN4U-8005-DP.action"
2778      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2778 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2779 2779  #
2780 2780  # code: SUN4U-8005-EA
2781 2781  # keys: defect.io.pci.driver fault.io.pci.device fault.io.psycho
2782 2782  #
2783 2783  msgid "SUN4U-8005-EA.type"
2784 2784  msgstr "Fault"
2785 2785  msgid "SUN4U-8005-EA.severity"
2786 2786  msgstr "Critical"
2787 2787  msgid "SUN4U-8005-EA.description"
2788 2788  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2789 2789  msgid "SUN4U-8005-EA.response"
2790 2790  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2791 2791  msgid "SUN4U-8005-EA.impact"
2792 2792  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2793 2793  msgid "SUN4U-8005-EA.action"
2794      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2794 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2795 2795  #
2796 2796  # code: SUN4U-8005-FS
2797 2797  # keys: fault.io.datapath fault.io.pci.device fault.io.psycho
2798 2798  #
2799 2799  msgid "SUN4U-8005-FS.type"
2800 2800  msgstr "Fault"
2801 2801  msgid "SUN4U-8005-FS.severity"
2802 2802  msgstr "Critical"
2803 2803  msgid "SUN4U-8005-FS.description"
2804 2804  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2805 2805  msgid "SUN4U-8005-FS.response"
2806 2806  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2807 2807  msgid "SUN4U-8005-FS.impact"
2808 2808  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2809 2809  msgid "SUN4U-8005-FS.action"
2810      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2810 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2811 2811  #
2812 2812  # code: SUN4U-8005-G5
2813 2813  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.psycho
2814 2814  #
2815 2815  msgid "SUN4U-8005-G5.type"
2816 2816  msgstr "Fault"
2817 2817  msgid "SUN4U-8005-G5.severity"
2818 2818  msgstr "Critical"
2819 2819  msgid "SUN4U-8005-G5.description"
2820 2820  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2821 2821  msgid "SUN4U-8005-G5.response"
2822 2822  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2823 2823  msgid "SUN4U-8005-G5.impact"
2824 2824  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2825 2825  msgid "SUN4U-8005-G5.action"
2826      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2826 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2827 2827  #
2828 2828  # code: SUN4U-8005-HX
2829 2829  # keys: fault.io.hbus fault.io.pci.device fault.io.psycho
2830 2830  #
2831 2831  msgid "SUN4U-8005-HX.type"
2832 2832  msgstr "Fault"
2833 2833  msgid "SUN4U-8005-HX.severity"
2834 2834  msgstr "Critical"
2835 2835  msgid "SUN4U-8005-HX.description"
2836 2836  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2837 2837  msgid "SUN4U-8005-HX.response"
2838 2838  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2839 2839  msgid "SUN4U-8005-HX.impact"
2840 2840  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2841 2841  msgid "SUN4U-8005-HX.action"
2842      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2842 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2843 2843  #
2844 2844  # code: SUN4U-8005-J2
2845 2845  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.psycho
2846 2846  #
2847 2847  msgid "SUN4U-8005-J2.type"
2848 2848  msgstr "Fault"
2849 2849  msgid "SUN4U-8005-J2.severity"
2850 2850  msgstr "Critical"
2851 2851  msgid "SUN4U-8005-J2.description"
2852 2852  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2853 2853  msgid "SUN4U-8005-J2.response"
2854 2854  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2855 2855  msgid "SUN4U-8005-J2.impact"
2856 2856  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2857 2857  msgid "SUN4U-8005-J2.action"
2858      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2858 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2859 2859  #
2860 2860  # code: SUN4U-8005-KJ
2861 2861  # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho
2862 2862  #
2863 2863  msgid "SUN4U-8005-KJ.type"
2864 2864  msgstr "Fault"
2865 2865  msgid "SUN4U-8005-KJ.severity"
2866 2866  msgstr "Critical"
2867 2867  msgid "SUN4U-8005-KJ.description"
2868 2868  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2869 2869  msgid "SUN4U-8005-KJ.response"
2870 2870  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2871 2871  msgid "SUN4U-8005-KJ.impact"
2872 2872  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2873 2873  msgid "SUN4U-8005-KJ.action"
2874      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2874 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2875 2875  #
2876 2876  # code: SUN4U-8005-LE
2877 2877  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.psycho
2878 2878  #
2879 2879  msgid "SUN4U-8005-LE.type"
2880 2880  msgstr "Fault"
2881 2881  msgid "SUN4U-8005-LE.severity"
2882 2882  msgstr "Critical"
2883 2883  msgid "SUN4U-8005-LE.description"
2884 2884  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2885 2885  msgid "SUN4U-8005-LE.response"
2886 2886  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2887 2887  msgid "SUN4U-8005-LE.impact"
2888 2888  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2889 2889  msgid "SUN4U-8005-LE.action"
2890      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2890 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2891 2891  #
2892 2892  # code: SUN4U-8005-MQ
2893 2893  # keys: fault.io.pci.bus fault.io.pci.device fault.io.psycho
2894 2894  #
2895 2895  msgid "SUN4U-8005-MQ.type"
2896 2896  msgstr "Fault"
2897 2897  msgid "SUN4U-8005-MQ.severity"
2898 2898  msgstr "Critical"
2899 2899  msgid "SUN4U-8005-MQ.description"
2900 2900  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2901 2901  msgid "SUN4U-8005-MQ.response"
2902 2902  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2903 2903  msgid "SUN4U-8005-MQ.impact"
2904 2904  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2905 2905  msgid "SUN4U-8005-MQ.action"
2906      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2906 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2907 2907  #
2908 2908  # code: SUN4U-8005-NC
2909 2909  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.psycho
2910 2910  #
2911 2911  msgid "SUN4U-8005-NC.type"
2912 2912  msgstr "Fault"
2913 2913  msgid "SUN4U-8005-NC.severity"
2914 2914  msgstr "Critical"
2915 2915  msgid "SUN4U-8005-NC.description"
2916 2916  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2917 2917  msgid "SUN4U-8005-NC.response"
2918 2918  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2919 2919  msgid "SUN4U-8005-NC.impact"
2920 2920  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2921 2921  msgid "SUN4U-8005-NC.action"
2922      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2922 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2923 2923  #
2924 2924  # code: SUN4U-8005-PR
2925 2925  # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho
2926 2926  #
2927 2927  msgid "SUN4U-8005-PR.type"
2928 2928  msgstr "Fault"
2929 2929  msgid "SUN4U-8005-PR.severity"
2930 2930  msgstr "Critical"
2931 2931  msgid "SUN4U-8005-PR.description"
2932 2932  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2933 2933  msgid "SUN4U-8005-PR.response"
2934 2934  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2935 2935  msgid "SUN4U-8005-PR.impact"
2936 2936  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2937 2937  msgid "SUN4U-8005-PR.action"
2938      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2938 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2939 2939  #
2940 2940  # code: SUN4U-8005-Q4
2941 2941  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.psycho
2942 2942  #
2943 2943  msgid "SUN4U-8005-Q4.type"
2944 2944  msgstr "Fault"
2945 2945  msgid "SUN4U-8005-Q4.severity"
2946 2946  msgstr "Critical"
2947 2947  msgid "SUN4U-8005-Q4.description"
2948 2948  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2949 2949  msgid "SUN4U-8005-Q4.response"
2950 2950  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2951 2951  msgid "SUN4U-8005-Q4.impact"
2952 2952  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2953 2953  msgid "SUN4U-8005-Q4.action"
2954      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2954 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2955 2955  #
2956 2956  # code: SUN4U-8005-RD
2957 2957  # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
2958 2958  #
2959 2959  msgid "SUN4U-8005-RD.type"
2960 2960  msgstr "Fault"
2961 2961  msgid "SUN4U-8005-RD.severity"
2962 2962  msgstr "Critical"
2963 2963  msgid "SUN4U-8005-RD.description"
2964 2964  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2965 2965  msgid "SUN4U-8005-RD.response"
2966 2966  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2967 2967  msgid "SUN4U-8005-RD.impact"
2968 2968  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2969 2969  msgid "SUN4U-8005-RD.action"
2970      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     2970 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
2971 2971  #
2972 2972  # code: SUN4U-8005-SH
2973 2973  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
2974 2974  #
2975 2975  msgid "SUN4U-8005-SH.type"
2976 2976  msgstr "Fault"
2977 2977  msgid "SUN4U-8005-SH.severity"
2978 2978  msgstr "Critical"
2979 2979  msgid "SUN4U-8005-SH.description"
2980 2980  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
2981 2981  msgid "SUN4U-8005-SH.response"
2982 2982  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2983 2983  msgid "SUN4U-8005-SH.impact"
2984 2984  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
2985 2985  msgid "SUN4U-8005-SH.action"
2986      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     2986 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
2987 2987  #
2988 2988  # code: SUN4U-8005-T3
2989 2989  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
2990 2990  #
2991 2991  msgid "SUN4U-8005-T3.type"
2992 2992  msgstr "Fault"
2993 2993  msgid "SUN4U-8005-T3.severity"
2994 2994  msgstr "Critical"
2995 2995  msgid "SUN4U-8005-T3.description"
2996 2996  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
2997 2997  msgid "SUN4U-8005-T3.response"
2998 2998  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
2999 2999  msgid "SUN4U-8005-T3.impact"
3000 3000  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3001 3001  msgid "SUN4U-8005-T3.action"
3002      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3002 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3003 3003  #
3004 3004  # code: SUN4U-8005-UY
3005 3005  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.psycho
3006 3006  #
3007 3007  msgid "SUN4U-8005-UY.type"
3008 3008  msgstr "Fault"
3009 3009  msgid "SUN4U-8005-UY.severity"
3010 3010  msgstr "Critical"
3011 3011  msgid "SUN4U-8005-UY.description"
3012 3012  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3013 3013  msgid "SUN4U-8005-UY.response"
3014 3014  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3015 3015  msgid "SUN4U-8005-UY.impact"
3016 3016  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3017 3017  msgid "SUN4U-8005-UY.action"
3018      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3018 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3019 3019  #
3020 3020  # code: SUN4U-8005-V5
3021 3021  # keys: fault.io.tomatillo
3022 3022  #
3023 3023  msgid "SUN4U-8005-V5.type"
3024 3024  msgstr "Fault"
3025 3025  msgid "SUN4U-8005-V5.severity"
3026 3026  msgstr "Critical"
3027 3027  msgid "SUN4U-8005-V5.description"
3028 3028  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3029 3029  msgid "SUN4U-8005-V5.response"
3030 3030  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3031 3031  msgid "SUN4U-8005-V5.impact"
3032 3032  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3033 3033  msgid "SUN4U-8005-V5.action"
3034      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3034 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3035 3035  #
3036 3036  # code: SUN4U-8005-WS
3037 3037  # keys: defect.io.pci.driver fault.io.tomatillo
3038 3038  #
3039 3039  msgid "SUN4U-8005-WS.type"
3040 3040  msgstr "Fault"
3041 3041  msgid "SUN4U-8005-WS.severity"
3042 3042  msgstr "Critical"
3043 3043  msgid "SUN4U-8005-WS.description"
3044 3044  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3045 3045  msgid "SUN4U-8005-WS.response"
3046 3046  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3047 3047  msgid "SUN4U-8005-WS.impact"
3048 3048  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3049 3049  msgid "SUN4U-8005-WS.action"
3050      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3050 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3051 3051  #
3052 3052  # code: SUN4U-8005-XA
3053 3053  # keys: fault.io.datapath fault.io.tomatillo
3054 3054  #
3055 3055  msgid "SUN4U-8005-XA.type"
3056 3056  msgstr "Fault"
3057 3057  msgid "SUN4U-8005-XA.severity"
3058 3058  msgstr "Critical"
3059 3059  msgid "SUN4U-8005-XA.description"
3060 3060  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3061 3061  msgid "SUN4U-8005-XA.response"
3062 3062  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3063 3063  msgid "SUN4U-8005-XA.impact"
3064 3064  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3065 3065  msgid "SUN4U-8005-XA.action"
3066      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3066 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3067 3067  #
3068 3068  # code: SUN4U-8005-YP
3069 3069  # keys: defect.io.pci.driver fault.io.datapath fault.io.tomatillo
3070 3070  #
3071 3071  msgid "SUN4U-8005-YP.type"
3072 3072  msgstr "Fault"
3073 3073  msgid "SUN4U-8005-YP.severity"
3074 3074  msgstr "Critical"
3075 3075  msgid "SUN4U-8005-YP.description"
3076 3076  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3077 3077  msgid "SUN4U-8005-YP.response"
3078 3078  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3079 3079  msgid "SUN4U-8005-YP.impact"
3080 3080  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3081 3081  msgid "SUN4U-8005-YP.action"
3082      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3082 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3083 3083  #
3084 3084  # code: SUN4U-8006-04
3085 3085  # keys: fault.io.hbus fault.io.tomatillo
3086 3086  #
3087 3087  msgid "SUN4U-8006-04.type"
3088 3088  msgstr "Fault"
3089 3089  msgid "SUN4U-8006-04.severity"
3090 3090  msgstr "Critical"
3091 3091  msgid "SUN4U-8006-04.description"
3092 3092  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3093 3093  msgid "SUN4U-8006-04.response"
3094 3094  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3095 3095  msgid "SUN4U-8006-04.impact"
3096 3096  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3097 3097  msgid "SUN4U-8006-04.action"
3098      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3098 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3099 3099  #
3100 3100  # code: SUN4U-8006-1R
3101 3101  # keys: defect.io.pci.driver fault.io.hbus fault.io.tomatillo
3102 3102  #
3103 3103  msgid "SUN4U-8006-1R.type"
3104 3104  msgstr "Fault"
3105 3105  msgid "SUN4U-8006-1R.severity"
3106 3106  msgstr "Critical"
3107 3107  msgid "SUN4U-8006-1R.description"
3108 3108  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3109 3109  msgid "SUN4U-8006-1R.response"
3110 3110  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3111 3111  msgid "SUN4U-8006-1R.impact"
3112 3112  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3113 3113  msgid "SUN4U-8006-1R.action"
3114      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3114 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3115 3115  #
3116 3116  # code: SUN4U-8006-2C
3117 3117  # keys: fault.io.datapath fault.io.hbus fault.io.tomatillo
3118 3118  #
3119 3119  msgid "SUN4U-8006-2C.type"
3120 3120  msgstr "Fault"
3121 3121  msgid "SUN4U-8006-2C.severity"
3122 3122  msgstr "Critical"
3123 3123  msgid "SUN4U-8006-2C.description"
3124 3124  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3125 3125  msgid "SUN4U-8006-2C.response"
3126 3126  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3127 3127  msgid "SUN4U-8006-2C.impact"
3128 3128  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3129 3129  msgid "SUN4U-8006-2C.action"
3130      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3130 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3131 3131  #
3132 3132  # code: SUN4U-8006-3Q
3133 3133  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.tomatillo
3134 3134  #
3135 3135  msgid "SUN4U-8006-3Q.type"
3136 3136  msgstr "Fault"
3137 3137  msgid "SUN4U-8006-3Q.severity"
3138 3138  msgstr "Critical"
3139 3139  msgid "SUN4U-8006-3Q.description"
3140 3140  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3141 3141  msgid "SUN4U-8006-3Q.response"
3142 3142  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3143 3143  msgid "SUN4U-8006-3Q.impact"
3144 3144  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3145 3145  msgid "SUN4U-8006-3Q.action"
3146      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3146 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3147 3147  #
3148 3148  # code: SUN4U-8006-4E
3149 3149  # keys: fault.io.pci.bus fault.io.tomatillo
3150 3150  #
3151 3151  msgid "SUN4U-8006-4E.type"
3152 3152  msgstr "Fault"
3153 3153  msgid "SUN4U-8006-4E.severity"
3154 3154  msgstr "Critical"
3155 3155  msgid "SUN4U-8006-4E.description"
3156 3156  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3157 3157  msgid "SUN4U-8006-4E.response"
3158 3158  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3159 3159  msgid "SUN4U-8006-4E.impact"
3160 3160  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3161 3161  msgid "SUN4U-8006-4E.action"
3162      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3162 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3163 3163  #
3164 3164  # code: SUN4U-8006-5J
3165 3165  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.tomatillo
3166 3166  #
3167 3167  msgid "SUN4U-8006-5J.type"
3168 3168  msgstr "Fault"
3169 3169  msgid "SUN4U-8006-5J.severity"
3170 3170  msgstr "Critical"
3171 3171  msgid "SUN4U-8006-5J.description"
3172 3172  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3173 3173  msgid "SUN4U-8006-5J.response"
3174 3174  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3175 3175  msgid "SUN4U-8006-5J.impact"
3176 3176  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3177 3177  msgid "SUN4U-8006-5J.action"
3178      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3178 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3179 3179  #
3180 3180  # code: SUN4U-8006-62
3181 3181  # keys: fault.io.datapath fault.io.pci.bus fault.io.tomatillo
3182 3182  #
3183 3183  msgid "SUN4U-8006-62.type"
3184 3184  msgstr "Fault"
3185 3185  msgid "SUN4U-8006-62.severity"
3186 3186  msgstr "Critical"
3187 3187  msgid "SUN4U-8006-62.description"
3188 3188  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3189 3189  msgid "SUN4U-8006-62.response"
3190 3190  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3191 3191  msgid "SUN4U-8006-62.impact"
3192 3192  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3193 3193  msgid "SUN4U-8006-62.action"
3194      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3194 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3195 3195  #
3196 3196  # code: SUN4U-8006-7X
3197 3197  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.tomatillo
3198 3198  #
3199 3199  msgid "SUN4U-8006-7X.type"
3200 3200  msgstr "Fault"
3201 3201  msgid "SUN4U-8006-7X.severity"
3202 3202  msgstr "Critical"
3203 3203  msgid "SUN4U-8006-7X.description"
3204 3204  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3205 3205  msgid "SUN4U-8006-7X.response"
3206 3206  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3207 3207  msgid "SUN4U-8006-7X.impact"
3208 3208  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3209 3209  msgid "SUN4U-8006-7X.action"
3210      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3210 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3211 3211  #
3212 3212  # code: SUN4U-8006-8P
3213 3213  # keys: fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3214 3214  #
3215 3215  msgid "SUN4U-8006-8P.type"
3216 3216  msgstr "Fault"
3217 3217  msgid "SUN4U-8006-8P.severity"
3218 3218  msgstr "Critical"
3219 3219  msgid "SUN4U-8006-8P.description"
3220 3220  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3221 3221  msgid "SUN4U-8006-8P.response"
3222 3222  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3223 3223  msgid "SUN4U-8006-8P.impact"
3224 3224  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3225 3225  msgid "SUN4U-8006-8P.action"
3226      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3226 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3227 3227  #
3228 3228  # code: SUN4U-8006-9A
3229 3229  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3230 3230  #
3231 3231  msgid "SUN4U-8006-9A.type"
3232 3232  msgstr "Fault"
3233 3233  msgid "SUN4U-8006-9A.severity"
3234 3234  msgstr "Critical"
3235 3235  msgid "SUN4U-8006-9A.description"
3236 3236  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3237 3237  msgid "SUN4U-8006-9A.response"
3238 3238  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3239 3239  msgid "SUN4U-8006-9A.impact"
3240 3240  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3241 3241  msgid "SUN4U-8006-9A.action"
3242      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3242 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3243 3243  #
3244 3244  # code: SUN4U-8006-AS
3245 3245  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3246 3246  #
3247 3247  msgid "SUN4U-8006-AS.type"
3248 3248  msgstr "Fault"
3249 3249  msgid "SUN4U-8006-AS.severity"
3250 3250  msgstr "Critical"
3251 3251  msgid "SUN4U-8006-AS.description"
3252 3252  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3253 3253  msgid "SUN4U-8006-AS.response"
3254 3254  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3255 3255  msgid "SUN4U-8006-AS.impact"
3256 3256  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3257 3257  msgid "SUN4U-8006-AS.action"
3258      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3258 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3259 3259  #
3260 3260  # code: SUN4U-8006-C5
3261 3261  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.tomatillo
3262 3262  #
3263 3263  msgid "SUN4U-8006-C5.type"
3264 3264  msgstr "Fault"
3265 3265  msgid "SUN4U-8006-C5.severity"
3266 3266  msgstr "Critical"
3267 3267  msgid "SUN4U-8006-C5.description"
3268 3268  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3269 3269  msgid "SUN4U-8006-C5.response"
3270 3270  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3271 3271  msgid "SUN4U-8006-C5.impact"
3272 3272  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3273 3273  msgid "SUN4U-8006-C5.action"
3274      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3274 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3275 3275  #
3276 3276  # code: SUN4U-8006-DY
3277 3277  # keys: fault.io.pci.device fault.io.tomatillo
3278 3278  #
3279 3279  msgid "SUN4U-8006-DY.type"
3280 3280  msgstr "Fault"
3281 3281  msgid "SUN4U-8006-DY.severity"
3282 3282  msgstr "Critical"
3283 3283  msgid "SUN4U-8006-DY.description"
3284 3284  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3285 3285  msgid "SUN4U-8006-DY.response"
3286 3286  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3287 3287  msgid "SUN4U-8006-DY.impact"
3288 3288  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3289 3289  msgid "SUN4U-8006-DY.action"
3290      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3290 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3291 3291  #
3292 3292  # code: SUN4U-8006-E3
3293 3293  # keys: defect.io.pci.driver fault.io.pci.device fault.io.tomatillo
3294 3294  #
3295 3295  msgid "SUN4U-8006-E3.type"
3296 3296  msgstr "Fault"
3297 3297  msgid "SUN4U-8006-E3.severity"
3298 3298  msgstr "Critical"
3299 3299  msgid "SUN4U-8006-E3.description"
3300 3300  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3301 3301  msgid "SUN4U-8006-E3.response"
3302 3302  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3303 3303  msgid "SUN4U-8006-E3.impact"
3304 3304  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3305 3305  msgid "SUN4U-8006-E3.action"
3306      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3306 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3307 3307  #
3308 3308  # code: SUN4U-8006-FH
3309 3309  # keys: fault.io.datapath fault.io.pci.device fault.io.tomatillo
3310 3310  #
3311 3311  msgid "SUN4U-8006-FH.type"
3312 3312  msgstr "Fault"
3313 3313  msgid "SUN4U-8006-FH.severity"
3314 3314  msgstr "Critical"
3315 3315  msgid "SUN4U-8006-FH.description"
3316 3316  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3317 3317  msgid "SUN4U-8006-FH.response"
3318 3318  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3319 3319  msgid "SUN4U-8006-FH.impact"
3320 3320  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3321 3321  msgid "SUN4U-8006-FH.action"
3322      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3322 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3323 3323  #
3324 3324  # code: SUN4U-8006-GD
3325 3325  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.device fault.io.tomatillo
3326 3326  #
3327 3327  msgid "SUN4U-8006-GD.type"
3328 3328  msgstr "Fault"
3329 3329  msgid "SUN4U-8006-GD.severity"
3330 3330  msgstr "Critical"
3331 3331  msgid "SUN4U-8006-GD.description"
3332 3332  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3333 3333  msgid "SUN4U-8006-GD.response"
3334 3334  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3335 3335  msgid "SUN4U-8006-GD.impact"
3336 3336  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3337 3337  msgid "SUN4U-8006-GD.action"
3338      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3338 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3339 3339  #
3340 3340  # code: SUN4U-8006-HQ
3341 3341  # keys: fault.io.hbus fault.io.pci.device fault.io.tomatillo
3342 3342  #
3343 3343  msgid "SUN4U-8006-HQ.type"
3344 3344  msgstr "Fault"
3345 3345  msgid "SUN4U-8006-HQ.severity"
3346 3346  msgstr "Critical"
3347 3347  msgid "SUN4U-8006-HQ.description"
3348 3348  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3349 3349  msgid "SUN4U-8006-HQ.response"
3350 3350  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3351 3351  msgid "SUN4U-8006-HQ.impact"
3352 3352  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3353 3353  msgid "SUN4U-8006-HQ.action"
3354      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3354 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3355 3355  #
3356 3356  # code: SUN4U-8006-JC
3357 3357  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.device fault.io.tomatillo
3358 3358  #
3359 3359  msgid "SUN4U-8006-JC.type"
3360 3360  msgstr "Fault"
3361 3361  msgid "SUN4U-8006-JC.severity"
3362 3362  msgstr "Critical"
3363 3363  msgid "SUN4U-8006-JC.description"
3364 3364  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3365 3365  msgid "SUN4U-8006-JC.response"
3366 3366  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3367 3367  msgid "SUN4U-8006-JC.impact"
3368 3368  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3369 3369  msgid "SUN4U-8006-JC.action"
3370      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3370 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3371 3371  #
3372 3372  # code: SUN4U-8006-KR
3373 3373  # keys: fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo
3374 3374  #
3375 3375  msgid "SUN4U-8006-KR.type"
3376 3376  msgstr "Fault"
3377 3377  msgid "SUN4U-8006-KR.severity"
3378 3378  msgstr "Critical"
3379 3379  msgid "SUN4U-8006-KR.description"
3380 3380  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3381 3381  msgid "SUN4U-8006-KR.response"
3382 3382  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3383 3383  msgid "SUN4U-8006-KR.impact"
3384 3384  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3385 3385  msgid "SUN4U-8006-KR.action"
3386      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3386 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3387 3387  #
3388 3388  # code: SUN4U-8006-L4
3389 3389  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.device fault.io.tomatillo
3390 3390  #
3391 3391  msgid "SUN4U-8006-L4.type"
3392 3392  msgstr "Fault"
3393 3393  msgid "SUN4U-8006-L4.severity"
3394 3394  msgstr "Critical"
3395 3395  msgid "SUN4U-8006-L4.description"
3396 3396  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3397 3397  msgid "SUN4U-8006-L4.response"
3398 3398  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3399 3399  msgid "SUN4U-8006-L4.impact"
3400 3400  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3401 3401  msgid "SUN4U-8006-L4.action"
3402      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3402 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3403 3403  #
3404 3404  # code: SUN4U-8006-MX
3405 3405  # keys: fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3406 3406  #
3407 3407  msgid "SUN4U-8006-MX.type"
3408 3408  msgstr "Fault"
3409 3409  msgid "SUN4U-8006-MX.severity"
3410 3410  msgstr "Critical"
3411 3411  msgid "SUN4U-8006-MX.description"
3412 3412  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3413 3413  msgid "SUN4U-8006-MX.response"
3414 3414  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3415 3415  msgid "SUN4U-8006-MX.impact"
3416 3416  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3417 3417  msgid "SUN4U-8006-MX.action"
3418      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3418 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3419 3419  #
3420 3420  # code: SUN4U-8006-N2
3421 3421  # keys: defect.io.pci.driver fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3422 3422  #
3423 3423  msgid "SUN4U-8006-N2.type"
3424 3424  msgstr "Fault"
3425 3425  msgid "SUN4U-8006-N2.severity"
3426 3426  msgstr "Critical"
3427 3427  msgid "SUN4U-8006-N2.description"
3428 3428  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3429 3429  msgid "SUN4U-8006-N2.response"
3430 3430  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3431 3431  msgid "SUN4U-8006-N2.impact"
3432 3432  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3433 3433  msgid "SUN4U-8006-N2.action"
3434      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3434 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3435 3435  #
3436 3436  # code: SUN4U-8006-PJ
3437 3437  # keys: fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3438 3438  #
3439 3439  msgid "SUN4U-8006-PJ.type"
3440 3440  msgstr "Fault"
3441 3441  msgid "SUN4U-8006-PJ.severity"
3442 3442  msgstr "Critical"
3443 3443  msgid "SUN4U-8006-PJ.description"
3444 3444  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3445 3445  msgid "SUN4U-8006-PJ.response"
3446 3446  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3447 3447  msgid "SUN4U-8006-PJ.impact"
3448 3448  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3449 3449  msgid "SUN4U-8006-PJ.action"
3450      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3450 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3451 3451  #
3452 3452  # code: SUN4U-8006-QE
3453 3453  # keys: defect.io.pci.driver fault.io.datapath fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3454 3454  #
3455 3455  msgid "SUN4U-8006-QE.type"
3456 3456  msgstr "Fault"
3457 3457  msgid "SUN4U-8006-QE.severity"
3458 3458  msgstr "Critical"
3459 3459  msgid "SUN4U-8006-QE.description"
3460 3460  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3461 3461  msgid "SUN4U-8006-QE.response"
3462 3462  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3463 3463  msgid "SUN4U-8006-QE.impact"
3464 3464  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3465 3465  msgid "SUN4U-8006-QE.action"
3466      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3466 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3467 3467  #
3468 3468  # code: SUN4U-8006-R5
3469 3469  # keys: fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3470 3470  #
3471 3471  msgid "SUN4U-8006-R5.type"
3472 3472  msgstr "Fault"
3473 3473  msgid "SUN4U-8006-R5.severity"
3474 3474  msgstr "Critical"
3475 3475  msgid "SUN4U-8006-R5.description"
3476 3476  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3477 3477  msgid "SUN4U-8006-R5.response"
3478 3478  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3479 3479  msgid "SUN4U-8006-R5.impact"
3480 3480  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3481 3481  msgid "SUN4U-8006-R5.action"
3482      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3482 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3483 3483  #
3484 3484  # code: SUN4U-8006-SS
3485 3485  # keys: defect.io.pci.driver fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3486 3486  #
3487 3487  msgid "SUN4U-8006-SS.type"
3488 3488  msgstr "Fault"
3489 3489  msgid "SUN4U-8006-SS.severity"
3490 3490  msgstr "Critical"
3491 3491  msgid "SUN4U-8006-SS.description"
3492 3492  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3493 3493  msgid "SUN4U-8006-SS.response"
3494 3494  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3495 3495  msgid "SUN4U-8006-SS.impact"
3496 3496  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3497 3497  msgid "SUN4U-8006-SS.action"
3498      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3498 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3499 3499  #
3500 3500  # code: SUN4U-8006-TA
3501 3501  # keys: fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3502 3502  #
3503 3503  msgid "SUN4U-8006-TA.type"
3504 3504  msgstr "Fault"
3505 3505  msgid "SUN4U-8006-TA.severity"
3506 3506  msgstr "Critical"
3507 3507  msgid "SUN4U-8006-TA.description"
3508 3508  msgstr "\nA problem was detected in a system core bus.\n  Refer to %s for more information."
3509 3509  msgid "SUN4U-8006-TA.response"
3510 3510  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3511 3511  msgid "SUN4U-8006-TA.impact"
3512 3512  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3513 3513  msgid "SUN4U-8006-TA.action"
3514      -msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nSun for support.\n"
     3514 +msgstr "\nSchedule a repair procedure to replace the affected device.  Use\nfmdump -v -u EVENT_ID to identify the device or contact\nyour illumos distribution team for support.\n"
3515 3515  #
3516 3516  # code: SUN4U-8006-UP
3517 3517  # keys: defect.io.pci.driver fault.io.datapath fault.io.hbus fault.io.pci.bus fault.io.pci.device fault.io.tomatillo
3518 3518  #
3519 3519  msgid "SUN4U-8006-UP.type"
3520 3520  msgstr "Fault"
3521 3521  msgid "SUN4U-8006-UP.severity"
3522 3522  msgstr "Critical"
3523 3523  msgid "SUN4U-8006-UP.description"
3524 3524  msgstr "\nThe system has diagnosed a problem, the suspects include one or more \nPCI buses, devices and one or more PCI controller drivers, based on the \nerror telemetry detected by the PCI subsystem.\n  Refer to %s for more information."
3525 3525  msgid "SUN4U-8006-UP.response"
3526 3526  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3527 3527  msgid "SUN4U-8006-UP.impact"
3528 3528  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3529 3529  msgid "SUN4U-8006-UP.action"
3530      -msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is a package then run \npkgchk on the package(s).\n"
     3530 +msgstr "\nUse fmdump -v -u <EVENT_ID> to identify the \nsuspected device(s).  Schedule a repair of the most likely suspect \nlisted in the output.  If the most likely suspect is software, then consult\nyour illumos distribution team.\n"
3531 3531  #
3532 3532  # code: SUN4U-8006-VD
3533 3533  # keys: fault.cpu.ultraSPARC-IIIiplus.dcache
3534 3534  #
3535 3535  msgid "SUN4U-8006-VD.type"
3536 3536  msgstr "Fault"
3537 3537  msgid "SUN4U-8006-VD.severity"
3538 3538  msgstr "Major"
3539 3539  msgid "SUN4U-8006-VD.description"
3540 3540  msgstr "The number of errors associated with a CPU has exceeded acceptable levels.  Refer to %s for more information."

3541 3541  msgid "SUN4U-8006-VD.response"
3542 3542  msgstr "The fault manager will attempt to remove the affected CPU from service."
3543 3543  msgid "SUN4U-8006-VD.impact"
3544 3544  msgstr "System performance may be affected."
3545 3545  msgid "SUN4U-8006-VD.action"
3546 3546  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3547 3547  #
3548 3548  # code: SUN4U-8006-WH
3549 3549  # keys: fault.cpu.ultraSPARC-IIIiplus.icache
3550 3550  #
3551 3551  msgid "SUN4U-8006-WH.type"
3552 3552  msgstr "Fault"
3553 3553  msgid "SUN4U-8006-WH.severity"
3554 3554  msgstr "Major"
3555 3555  msgid "SUN4U-8006-WH.description"
3556 3556  msgstr "The number of errors associated with a CPU has exceeded acceptable levels.  Refer to %s for more information."
3557 3557  msgid "SUN4U-8006-WH.response"
3558 3558  msgstr "The fault manager will attempt to remove the affected CPU from service."
3559 3559  msgid "SUN4U-8006-WH.impact"
3560 3560  msgstr "System performance may be affected."
3561 3561  msgid "SUN4U-8006-WH.action"
3562 3562  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3563 3563  #
3564 3564  # code: SUN4U-8006-X3
3565 3565  # keys: fault.cpu.ultraSPARC-IIIiplus.l2cachedata
3566 3566  #
3567 3567  msgid "SUN4U-8006-X3.type"
3568 3568  msgstr "Fault"
3569 3569  msgid "SUN4U-8006-X3.severity"
3570 3570  msgstr "Major"
3571 3571  msgid "SUN4U-8006-X3.description"
3572 3572  msgstr "The number of errors associated with a CPU has exceeded acceptable levels.  Refer to %s for more information."
3573 3573  msgid "SUN4U-8006-X3.response"
3574 3574  msgstr "The fault manager will attempt to remove the affected CPU from service."
3575 3575  msgid "SUN4U-8006-X3.impact"
3576 3576  msgstr "System performance may be affected."
3577 3577  msgid "SUN4U-8006-X3.action"
3578 3578  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3579 3579  #
3580 3580  # code: SUN4U-8006-YY
3581 3581  # keys: fault.cpu.ultraSPARC-IIIiplus.l2cachetag
3582 3582  #
3583 3583  msgid "SUN4U-8006-YY.type"
3584 3584  msgstr "Fault"
3585 3585  msgid "SUN4U-8006-YY.severity"
3586 3586  msgstr "Major"
3587 3587  msgid "SUN4U-8006-YY.description"
3588 3588  msgstr "The number of errors associated with a CPU has exceeded acceptable levels.  Refer to %s for more information."
3589 3589  msgid "SUN4U-8006-YY.response"
3590 3590  msgstr "The fault manager will attempt to remove the affected CPU from service."
3591 3591  msgid "SUN4U-8006-YY.impact"
3592 3592  msgstr "System performance may be affected."
3593 3593  msgid "SUN4U-8006-YY.action"
3594 3594  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3595 3595  #
3596 3596  # code: SUN4U-8007-03
3597 3597  # keys: fault.cpu.ultraSPARC-IIIiplus.fpu
3598 3598  #
3599 3599  msgid "SUN4U-8007-03.type"
3600 3600  msgstr "Fault"
3601 3601  msgid "SUN4U-8007-03.severity"
3602 3602  msgstr "Major"
3603 3603  msgid "SUN4U-8007-03.description"
3604 3604  msgstr "The number of errors associated with a CPU has exceeded acceptable levels.  Refer to %s for more information."
3605 3605  msgid "SUN4U-8007-03.response"
3606 3606  msgstr "The fault manager will attempt to remove the affected CPU from service."
3607 3607  msgid "SUN4U-8007-03.impact"
3608 3608  msgstr "System performance may be affected."
3609 3609  msgid "SUN4U-8007-03.action"
3610 3610  msgstr "Schedule a repair procedure to replace the affected CPU, the identity of which can be determined using fmdump -v -u <EVENT_ID>."
3611 3611  #
3612 3612  # code: SUN4U-8007-1Y
3613 3613  # keys: fault.asic.cds.dp
3614 3614  #
3615 3615  msgid "SUN4U-8007-1Y.type"
3616 3616  msgstr "Fault"
3617 3617  msgid "SUN4U-8007-1Y.severity"
3618 3618  msgstr "Critical"
3619 3619  msgid "SUN4U-8007-1Y.description"
3620 3620  msgstr "A hardware problem was detected on the datapath interconnect.\n  Refer to %s for more information."
3621 3621  msgid "SUN4U-8007-1Y.response"
3622 3622  msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3623 3623  msgid "SUN4U-8007-1Y.impact"
3624 3624  msgstr "System performace may be affected.\n"
3625 3625  msgid "SUN4U-8007-1Y.action"
3626 3626  msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3627 3627  #
3628 3628  # code: SUN4U-8007-2D
3629 3629  # keys: fault.asic.dx.dp
3630 3630  #
3631 3631  msgid "SUN4U-8007-2D.type"
3632 3632  msgstr "Fault"
3633 3633  msgid "SUN4U-8007-2D.severity"
3634 3634  msgstr "Critical"
3635 3635  msgid "SUN4U-8007-2D.description"
3636 3636  msgstr "A hardware problem was detected on the datapath interconnect.\n  Refer to %s for more information."
3637 3637  msgid "SUN4U-8007-2D.response"
3638 3638  msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3639 3639  msgid "SUN4U-8007-2D.impact"
3640 3640  msgstr "System performace may be affected.\n"
3641 3641  msgid "SUN4U-8007-2D.action"
3642 3642  msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3643 3643  #
3644 3644  # code: SUN4U-8007-3H
3645 3645  # keys: fault.asic.sdi.dp
3646 3646  #
3647 3647  msgid "SUN4U-8007-3H.type"
3648 3648  msgstr "Fault"
3649 3649  msgid "SUN4U-8007-3H.severity"
3650 3650  msgstr "Critical"
3651 3651  msgid "SUN4U-8007-3H.description"
3652 3652  msgstr "A hardware problem was detected on the datapath interconnect.\n  Refer to %s for more information."
3653 3653  msgid "SUN4U-8007-3H.response"
3654 3654  msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3655 3655  msgid "SUN4U-8007-3H.impact"
3656 3656  msgstr "System performace may be affected.\n"
3657 3657  msgid "SUN4U-8007-3H.action"
3658 3658  msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3659 3659  #
3660 3660  # code: SUN4U-8007-4A
3661 3661  # keys: fault.asic.cp.dp
3662 3662  #
3663 3663  msgid "SUN4U-8007-4A.type"
3664 3664  msgstr "Fault"
3665 3665  msgid "SUN4U-8007-4A.severity"
3666 3666  msgstr "Critical"
3667 3667  msgid "SUN4U-8007-4A.description"
3668 3668  msgstr "A hardware problem was detected on the datapath interconnect.\n  Refer to %s for more information."
3669 3669  msgid "SUN4U-8007-4A.response"
3670 3670  msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3671 3671  msgid "SUN4U-8007-4A.impact"
3672 3672  msgstr "System performace may be affected.\n"
3673 3673  msgid "SUN4U-8007-4A.action"
3674 3674  msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3675 3675  #
3676 3676  # code: SUN4U-8007-5P
3677 3677  # keys: fault.asic.rp.dp
3678 3678  #
3679 3679  msgid "SUN4U-8007-5P.type"
3680 3680  msgstr "Fault"
3681 3681  msgid "SUN4U-8007-5P.severity"
3682 3682  msgstr "Critical"
3683 3683  msgid "SUN4U-8007-5P.description"
3684 3684  msgstr "A hardware problem was detected on the datapath interconnect.\n  Refer to %s for more information."
3685 3685  msgid "SUN4U-8007-5P.response"
3686 3686  msgstr "One or more CPUs may be offlined. Additionally, page retires for memory in the impacted region may be disabled.\n"
3687 3687  msgid "SUN4U-8007-5P.impact"
3688 3688  msgstr "System performace may be affected.\n"
3689 3689  msgid "SUN4U-8007-5P.action"
3690 3690  msgstr "Schedule a repair procedure to replace the affected component(s). The System Controller (SC) diagnostic messages have the authoritative information on the affected component(s). fmdump -v -u <EVENT-ID> can also be used, but the SC is authoritative.\n"
3691 3691  #
3692 3692  # code: SUN4U-8007-65
3693 3693  # keys: fault.io.oberon
3694 3694  #
3695 3695  msgid "SUN4U-8007-65.type"

3696 3696  msgstr "Fault"
3697 3697  msgid "SUN4U-8007-65.severity"
3698 3698  msgstr "Critical"
3699 3699  msgid "SUN4U-8007-65.description"
3700 3700  msgstr "Oberon PCI-Express hostbridge fault\n  Refer to %s for more information."
3701 3701  msgid "SUN4U-8007-65.response"
3702 3702  msgstr "This fault requires user and/or service interaction and currently does not have an automated response agent."
3703 3703  msgid "SUN4U-8007-65.impact"
3704 3704  msgstr "Possible loss of devices that may be attached to the system via this device/bus and/or system downtime."
3705 3705  msgid "SUN4U-8007-65.action"
3706      -msgstr "Ensure that the latest drivers and patches are installed, schedule a repair procedure to replace the affected device if necessary, or contact Sun for support."
     3706 +msgstr "Ensure that the latest drivers and patches are installed, schedule a repair procedure to replace the affected device if necessary, or contact your illumos distribution team for support."
3707 3707  #
3708 3708  # code: SUN4U-8007-7S
3709 3709  # keys: fault.cpu.SPARC64-VI.chip
3710 3710  #
3711 3711  msgid "SUN4U-8007-7S.type"
3712 3712  msgstr "Fault"
3713 3713  msgid "SUN4U-8007-7S.severity"
3714 3714  msgstr "Critical"
3715 3715  msgid "SUN4U-8007-7S.description"
3716 3716  msgstr "The number of errors associated with this CHIP has exceeded acceptable levels.  Refer to %s for more information."

3717 3717  msgid "SUN4U-8007-7S.response"
3718 3718  msgstr "An attempt will be made to remove the affected CHIP from service."
3719 3719  msgid "SUN4U-8007-7S.impact"
3720 3720  msgstr "The system will not be functioning at the same performance level with the CHIP removal."
3721 3721  msgid "SUN4U-8007-7S.action"
3722 3722  msgstr "Schedule a repair procedure to replace the affected CHIP.  Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCHIP."
3723 3723  #
3724 3724  # code: SUN4U-8007-8J
3725 3725  # keys: fault.cpu.SPARC64-VI.core
3726 3726  #
3727 3727  msgid "SUN4U-8007-8J.type"
3728 3728  msgstr "Fault"
3729 3729  msgid "SUN4U-8007-8J.severity"
3730 3730  msgstr "Critical"
3731 3731  msgid "SUN4U-8007-8J.description"
3732 3732  msgstr "The number of errors associated with this CORE has exceeded acceptable levels.  Refer to %s for more information."
3733 3733  msgid "SUN4U-8007-8J.response"
3734 3734  msgstr "An attempt will be made to remove the affected CORE from service."
3735 3735  msgid "SUN4U-8007-8J.impact"
3736 3736  msgstr "The system will not be functioning at the same performance level with the CORE removal."
3737 3737  msgid "SUN4U-8007-8J.action"
3738 3738  msgstr "Schedule a repair procedure to replace the affected CORE.  Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCORE.\n"
3739 3739  #
3740 3740  # code: SUN4U-8007-9E
3741 3741  # keys: fault.cpu.SPARC64-VI.strand
3742 3742  #
3743 3743  msgid "SUN4U-8007-9E.type"
3744 3744  msgstr "Fault"
3745 3745  msgid "SUN4U-8007-9E.severity"
3746 3746  msgstr "Critical"
3747 3747  msgid "SUN4U-8007-9E.description"
3748 3748  msgstr "The number of errors associated with this STRAND has exceeded acceptable levels.  Refer to %s for more information."
3749 3749  msgid "SUN4U-8007-9E.response"
3750 3750  msgstr "An attempt will be made to remove the affected STRAND from service."
3751 3751  msgid "SUN4U-8007-9E.impact"
3752 3752  msgstr "The system will not be functioning at the same performance level with the STRAND removal."
3753 3753  msgid "SUN4U-8007-9E.action"
3754 3754  msgstr "Schedule a repair procedure to replace the affected STRAND.  Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nSTRAND.\n"
3755 3755  #
3756 3756  # code: SUN4U-8007-AX
3757 3757  # keys: fault.io.pci.device-invreq fault.io.tomatillo
3758 3758  #
3759 3759  msgid "SUN4U-8007-AX.type"

3760 3760  msgstr "Fault"
3761 3761  msgid "SUN4U-8007-AX.severity"
3762 3762  msgstr "Critical"
3763 3763  msgid "SUN4U-8007-AX.description"
3764 3764  msgstr "Either the transmitting device sent an invalid request or the receiving device failed to respond.\n  Refer to %s for more information."
3765 3765  msgid "SUN4U-8007-AX.response"
3766 3766  msgstr "One or more device instances may be disabled\n"
3767 3767  msgid "SUN4U-8007-AX.impact"
3768 3768  msgstr "Loss of services provided by the device instances associated with this fault\n"
3769 3769  msgid "SUN4U-8007-AX.action"
3770      -msgstr "Ensure that the latest drivers and patches are installed. If a plug-in card is involved check for badly-seated cards or bent pins.  Otherwise schedule a repair procedure to replace the affected device(s).  Use fmdump -v -u <EVENT_ID> to identify the devices or contact Sun for support.\n"
     3770 +msgstr "Ensure that the latest drivers and patches are installed. If a plug-in card is involved check for badly-seated cards or bent pins.  Otherwise schedule a repair procedure to replace the affected device(s).  Use fmdump -v -u <EVENT_ID> to identify the devices or contact your illumos distribution team for support.\n"
3771 3771  #
3772 3772  # code: SUN4U-8007-C2
3773 3773  # keys: fault.cpu.SPARC64-VII.chip
3774 3774  #
3775 3775  msgid "SUN4U-8007-C2.type"
3776 3776  msgstr "Fault"
3777 3777  msgid "SUN4U-8007-C2.severity"
3778 3778  msgstr "Critical"
3779 3779  msgid "SUN4U-8007-C2.description"
3780 3780  msgstr "The number of errors associated with this CHIP has exceeded acceptable levels.  Refer to %s for more information."

3781 3781  msgid "SUN4U-8007-C2.response"
3782 3782  msgstr "An attempt will be made to remove the affected CHIP from service."
3783 3783  msgid "SUN4U-8007-C2.impact"
3784 3784  msgstr "The system will not be functioning at the same performance level with the CHIP removal."
3785 3785  msgid "SUN4U-8007-C2.action"
3786 3786  msgstr "Schedule a repair procedure to replace the affected CHIP.  Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCHIP."
3787 3787  #
3788 3788  # code: SUN4U-8007-DR
3789 3789  # keys: fault.cpu.SPARC64-VII.core
3790 3790  #
3791 3791  msgid "SUN4U-8007-DR.type"
3792 3792  msgstr "Fault"
3793 3793  msgid "SUN4U-8007-DR.severity"
3794 3794  msgstr "Critical"
3795 3795  msgid "SUN4U-8007-DR.description"
3796 3796  msgstr "The number of errors associated with this CORE has exceeded acceptable levels.  Refer to %s for more information."
3797 3797  msgid "SUN4U-8007-DR.response"
3798 3798  msgstr "An attempt will be made to remove the affected CORE from service."
3799 3799  msgid "SUN4U-8007-DR.impact"
3800 3800  msgstr "The system will not be functioning at the same performance level with the CORE removal."
3801 3801  msgid "SUN4U-8007-DR.action"
3802 3802  msgstr "Schedule a repair procedure to replace the affected CORE.  Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nCORE.\n"
3803 3803  #
3804 3804  # code: SUN4U-8007-E4
3805 3805  # keys: fault.cpu.SPARC64-VII.strand
3806 3806  #
3807 3807  msgid "SUN4U-8007-E4.type"
3808 3808  msgstr "Fault"
3809 3809  msgid "SUN4U-8007-E4.severity"
3810 3810  msgstr "Critical"
3811 3811  msgid "SUN4U-8007-E4.description"
3812 3812  msgstr "The number of errors associated with this STRAND has exceeded acceptable levels.  Refer to %s for more information."
3813 3813  msgid "SUN4U-8007-E4.response"
3814 3814  msgstr "An attempt will be made to remove the affected STRAND from service."
3815 3815  msgid "SUN4U-8007-E4.impact"
3816 3816  msgstr "The system will not be functioning at the same performance level with the STRAND removal."
3817 3817  msgid "SUN4U-8007-E4.action"

3818 3818  msgstr "Schedule a repair procedure to replace the affected STRAND.  Use fmdump -v -u <EVENT_ID>\nto identify the smallest CPU/Strand ID of the affected CORE on this\nSTRAND.\n"
3819 3819  #
3820 3820  # code: SUN4U-8007-FQ
3821 3821  # keys: fault.cpu.ultraSPARC-IVplus.l2cachedata-line
3822 3822  #
3823 3823  msgid "SUN4U-8007-FQ.type"
3824 3824  msgstr "Fault"
3825 3825  msgid "SUN4U-8007-FQ.severity"
3826 3826  msgstr "Minor"
3827 3827  msgid "SUN4U-8007-FQ.description"
3828      -msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
     3828 +msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
3829 3829  msgid "SUN4U-8007-FQ.response"
3830 3830  msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3831 3831  msgid "SUN4U-8007-FQ.impact"
3832 3832  msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3833 3833  msgid "SUN4U-8007-FQ.action"
3834 3834  msgstr "No repair action is recommended at this time.\n"
3835 3835  #
3836 3836  # code: SUN4U-8007-GC
3837 3837  # keys: fault.cpu.ultraSPARC-IVplus.l3cachedata-line
3838 3838  #
3839 3839  msgid "SUN4U-8007-GC.type"
3840 3840  msgstr "Fault"
3841 3841  msgid "SUN4U-8007-GC.severity"
3842 3842  msgstr "Minor"
3843 3843  msgid "SUN4U-8007-GC.description"
3844      -msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
     3844 +msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
3845 3845  msgid "SUN4U-8007-GC.response"
3846 3846  msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3847 3847  msgid "SUN4U-8007-GC.impact"
3848 3848  msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3849 3849  msgid "SUN4U-8007-GC.action"
3850 3850  msgstr "No repair action is recommended at this time.\n"
3851 3851  #
3852 3852  # code: SUN4U-8007-HH
3853 3853  # keys: fault.cpu.ultraSPARC-IVplus.l2cachetag-line
3854 3854  #
3855 3855  msgid "SUN4U-8007-HH.type"
3856 3856  msgstr "Fault"
3857 3857  msgid "SUN4U-8007-HH.severity"
3858 3858  msgstr "Minor"
3859 3859  msgid "SUN4U-8007-HH.description"
3860      -msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
     3860 +msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
3861 3861  msgid "SUN4U-8007-HH.response"
3862 3862  msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3863 3863  msgid "SUN4U-8007-HH.impact"
3864 3864  msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3865 3865  msgid "SUN4U-8007-HH.action"
3866 3866  msgstr "No repair action is recommended at this time.\n"
3867 3867  #
3868 3868  # code: SUN4U-8007-JD
3869 3869  # keys: fault.cpu.ultraSPARC-IVplus.l3cachetag-line
3870 3870  #
3871 3871  msgid "SUN4U-8007-JD.type"
3872 3872  msgstr "Fault"
3873 3873  msgid "SUN4U-8007-JD.severity"
3874 3874  msgstr "Minor"
3875 3875  msgid "SUN4U-8007-JD.description"
3876      -msgstr "The Solaris Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
     3876 +msgstr "The illumos Fault Manager has determined that the\nnumber of correctable errors against a\nparticular CPU's cache index and way exceeds recommended\nlimts.\n  Refer to %s for more information."
3877 3877  msgid "SUN4U-8007-JD.response"
3878 3878  msgstr "The system will attempt to remove the CPU's offending\ncache index and way from service.\n"
3879 3879  msgid "SUN4U-8007-JD.impact"
3880 3880  msgstr "The performace of the system may be minimally impacted as\na result of removing the cache line and way from service.\nLoss of service will be limited to this CPU's cache\nline and way.\n"
3881 3881  msgid "SUN4U-8007-JD.action"
3882 3882  msgstr "No repair action is recommended at this time.\n"
3883 3883  #
3884 3884  # code: SUN4U-8007-KY
3885 3885  # keys: fault.memory.dimm-page-retires-excessive
3886 3886  #

3887 3887  msgid "SUN4U-8007-KY.type"
3888 3888  msgstr "Fault"
3889 3889  msgid "SUN4U-8007-KY.severity"
3890 3890  msgstr "Major"
3891 3891  msgid "SUN4U-8007-KY.description"
3892 3892  msgstr "The number of correctable errors associated with this memory module has exceeded acceptable levels.\n  Refer to %s for more information."
3893 3893  msgid "SUN4U-8007-KY.response"
3894 3894  msgstr "Pages of memory associated with this memory module have been removed from service, up to a limit which has now been reached.\n"
3895 3895  msgid "SUN4U-8007-KY.impact"
3896 3896  msgstr "Total system memory capacity has been reduced.\n"
3897 3897  msgid "SUN4U-8007-KY.action"
3898 3898  msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n"
3899 3899  #
3900 3900  # code: SUN4U-8007-L3
3901 3901  # keys: fault.memory.dimm-ue-imminent
3902 3902  #
3903 3903  msgid "SUN4U-8007-L3.type"
3904 3904  msgstr "Fault"
3905 3905  msgid "SUN4U-8007-L3.severity"
3906 3906  msgstr "Critical"
3907 3907  msgid "SUN4U-8007-L3.description"
3908 3908  msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n  Refer to %s for more information."
3909 3909  msgid "SUN4U-8007-L3.response"
3910 3910  msgstr "None at this time.\n"
3911 3911  msgid "SUN4U-8007-L3.impact"
3912 3912  msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n"
3913 3913  msgid "SUN4U-8007-L3.action"
3914 3914  msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n"
3915 3915  #
3916 3916  # code: SUN4U-8007-MS
3917 3917  # keys: fault.memory.dram-ue-imminent
3918 3918  #
3919 3919  msgid "SUN4U-8007-MS.type"
3920 3920  msgstr "Fault"
3921 3921  msgid "SUN4U-8007-MS.severity"
3922 3922  msgstr "Critical"
3923 3923  msgid "SUN4U-8007-MS.description"
3924 3924  msgstr "A pattern of correctable errors has been observed suggesting the potential exists that an uncorrectable error may occur.\n  Refer to %s for more information."
3925 3925  msgid "SUN4U-8007-MS.response"
3926 3926  msgstr "None at this time.\n"
3927 3927  msgid "SUN4U-8007-MS.impact"
3928 3928  msgstr "None at this time. However, the potential uncorrectable error warrants proactive service action to avoid any unplanned system outages.\n"
3929 3929  msgid "SUN4U-8007-MS.action"
3930 3930  msgstr "Schedule a repair procedure to replace the DIMM. Use fmadm faulty to identify the DIMM to replace.\n"

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX