33 msgstr "Fault"
35 msgstr "Critical"
37 msgstr "A fatal clock distribution error was detected by an ASIC or a CPU chip.\n  Refer to %s for more information."
39 msgstr "An attempt will be made to deconfigure the faulty components after one or more domains are reset.\n"
41 msgstr "One or more domains will be reset. Please consult the detail section of the knowledge article for \nadditional information.\n"
43 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
49 msgstr "Fault"
51 msgstr "Critical"
53 msgstr "A Clock chip has detected a lack of connectivity between the base cabinet and the expansion cabinet.\n  Refer to %s for more information."
55 msgstr "The entire platform is reset and the active Clock Units are deconfigured during recovery.\n"
57 msgstr "The entire platform is reset and the active Clock Units are deconfigured during recovery.\n"
59 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
65 msgstr "Fault"
67 msgstr "Critical"
69 msgstr "A fatal error was detected within a Clock chip.\n  Refer to %s for more information."
71 msgstr "The platform will be reset. If there is redundant clock capability, an attempt will be made to deconfigure \nthe active Clock Unit from service. \n"
73 msgstr "If the platform lacks redundant clock capability, the platform will be powered down and will not\npower up. If the platform has redundant clock capability, the platform will be reset and the\nfaulty Clock Unit will be deconfigured during recovery.\n"
75 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
81 msgstr "Fault"
83 msgstr "Critical"
85 msgstr "Fault was detected during poweron self-test, either within a Clock chip with within one of the external\ninterfaces of a Clock chip.\n  Refer to %s for more information."
87 msgstr "An attempt will be made to remove the affected components from service. Please consult the detail \nsection of the knowledge article for additional information.\n"
89 msgstr "The entire platform is reset. If the platform lacks redundant clock capability, the platform will be \npowered down and will not power up. If the platform has redundant clock capability, the platform will be \nreset and the faulty Clock Unit will be deconfigured during recovery.\n"
91 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
97 msgstr "Fault"
99 msgstr "Critical"
101 msgstr "An internal fatal error within a CPU chip was detected.\n  Refer to %s for more information."
103 msgstr "The domain using this CPU will be reset and the CPU chip will be deconfigured.\n"
105 msgstr "The CPU chip will be deconfigured after the domain is reset.\n"
107 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
113 msgstr "Fault"
115 msgstr "Critical"
117 msgstr "An internal fatal error within a core on a CPU chip was detected.\n  Refer to %s for more information."
119 msgstr "The domain using this CPU will be reset and the core will be deconfigured.\n"
121 msgstr "The domain using this CPU chip is reset.\n"
123 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
129 msgstr "Fault"
131 msgstr "Critical"
133 msgstr "An internal fatal error within a strand on a CPU chip was detected.\n  Refer to %s for more information."
135 msgstr "The domain using this CPU will be reset and the strand will be deconfigured.\n"
137 msgstr "The domain using this CPU chip is reset.\n"
139 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
145 msgstr "Fault"
147 msgstr "Major"
149 msgstr "An internal non-fatal uncorrectable error within a CPU chip has been detected.\n  Refer to %s for more information."
151 msgstr "The CPU chip will be deconfigured after the platform is power cycled or after the domain reboots \nor after a Dynamic Reconfiguration operation is performed.\n"
153 msgstr "The non-fatal uncorrectable error may cause domain to panic. The CPU chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
155 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
161 msgstr "Fault"
163 msgstr "Major"
165 msgstr "A non-fatal uncorrectable error associated with a core on a CPU chip has been detected.\n  Refer to %s for more information."
167 msgstr "The domain software will attempt to offline the core on the CPU chip.\n"
169 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. If the domain\ndoes not panic, the domain software will attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
171 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
177 msgstr "Fault"
179 msgstr "Major"
181 msgstr "When a non-fatal uncorrectable error occurs on a core on a CPU chip, domain software attempts to\noffline the core. This fault occurs when the number of offline attempts has exceeded an\nacceptable threshold.\n  Refer to %s for more information."
183 msgstr "Future non-fatal uncorrectable errors for this core on a CPU chip will not be recorded on the XSCF.\n"
185 msgstr "The uncorrectable error trap may cause the domain to panic.\n"
187 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
193 msgstr "Fault"
195 msgstr "Major"
197 msgstr "A non-fatal uncorrectable error has been detected on a strand on a CPU chip.\n  Refer to %s for more information."
199 msgstr "The strand on the CPU chip is deconfigured.\n"
201 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic.\n"
203 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
209 msgstr "Fault"
211 msgstr "Major"
213 msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
215 msgstr "The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
217 msgstr "No immediate impact. The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
219 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
225 msgstr "Fault"
227 msgstr "Major"
229 msgstr "The number of correctable errors associated with a core on a CPU chip have exceeded an acceptable threshold.\n  Refer to %s for more information."
231 msgstr "A request is sent to the domain software to attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
233 msgstr "No immediate impact.\n"
235 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
241 msgstr "Fault"
243 msgstr "Major"
245 msgstr "The number of correctable errors on a core on a CPU chip has exceeded an acceptable threshold. \nThis fault occurs when the number of offline attempts has exceeded an acceptable threshold.\n  Refer to %s for more information."
247 msgstr "Future correctable errors for this core on a CPU chip will not be recorded on the XSCF.\n"
249 msgstr "No immediate impact.\n"
251 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
257 msgstr "Fault"
259 msgstr "Minor"
261 msgstr "The number of correctable errors within a way of a CPU chip's L2 cache has exceeded an acceptable threshold.\n  Refer to %s for more information."
263 msgstr "The way of the CPU chip's cache is deconfigured. The performance of the CPU chip is reduced.\n"
265 msgstr "There is a performance loss for the CPU chip.\n"
267 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
273 msgstr "Upset"
275 msgstr "Critical"
277 msgstr "A hard-to-diagnose problem was detected by the CPU chip.\n  Refer to %s for more information."
279 msgstr "Nothing is deconfigured.\n"
281 msgstr "The domain may drop to the OpenBoot PROM 'OK' prompt.\n"
283 msgstr "The platform administrator should check to see if any other hardware failure has occurred on the platform.\nIf the problem occurs while running OpenBoot PROM, then the platform administrator should check to make sure that \nthe OpenBoot PROM environment variables have not been set incorrectly. If neither of these courses of action \nprovide a resolution, then the platform administrator should schedule a service action.\nPlease consult the detail section of the knowledge article for additional information.\n"
289 msgstr "upset"
291 msgstr "Critical"
293 msgstr "An unexpected trap with some unknown cause was detected by a CPU chip during POST.\n  Refer to %s for more information."
295 msgstr "Nothing is deconfigured.\n"
297 msgstr "The domain is reset.\n"
299 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
305 msgstr "Fault"
307 msgstr "Major"
309 msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n  Refer to %s for more information."
311 msgstr "Nothing is deconfigured.\n"
313 msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n"
315 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
321 msgstr "Fault"
323 msgstr "Major"
325 msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n  Refer to %s for more information."
327 msgstr "Nothing is deconfigured.\n"
329 msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n"
331 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
337 msgstr "Fault"
339 msgstr "Minor"
341 msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
343 msgstr "Nothing is deconfigured.\n"
345 msgstr "No immediate impact.\n"
347 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
353 msgstr "Fault"
355 msgstr "Major"
357 msgstr "A fatal error in a DIMM was detected by POST.\n  Refer to %s for more information."
359 msgstr "The memory associated with the memory bank that contains this\nDIMM is deconfigured.\n"
361 msgstr "POST is restarted after the memory associated with the memory bank that contains\nthis DIMM has been deconfigured.\n"
363 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
369 msgstr "Fault"
371 msgstr "Major"
373 msgstr "An uncorrectable memory error (UE) has been detected.\n  Refer to %s for more information."
375 msgstr "The 64MB of memory containing the memory that caused the UE will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed.\n"
377 msgstr "The domain will receive an uncorrectable error trap which may cause the domain to panic. \n"
379 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
385 msgstr "Fault"
387 msgstr "Major"
389 msgstr "A data compare error has been detected within a MAC chip when memory is in mirror mode.\n  Refer to %s for more information."
391 msgstr "The memory associated with the MAC chip will be deconfigured after the platform is power cycled \nor after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
393 msgstr "The domain will receive an uncorrectable error trap which may cause the domain to panic. \n"
395 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
401 msgstr "Fault"
403 msgstr "Minor"
405 msgstr "A permanent correctable memory error (PCE) has been detected.\n  Refer to %s for more information."
407 msgstr "The 64MB chunk of memory that contains the permanent correctable error will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
409 msgstr "Minimal impact.\n"
411 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
417 msgstr "Fault"
419 msgstr "Minor"
421 msgstr "The number of permanent correctable errors (PCE's) on single DIMM exceeds an\nacceptable threshold.\n  Refer to %s for more information."
423 msgstr "No immediate action is taken and nothing is deconfigured.\n"
425 msgstr "Minimal impact to system.\n"
427 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
433 msgstr "Fault"
435 msgstr "Major"
437 msgstr "The number of uncorrectable and correctable errors on single DIMM exceeds an\nacceptable threshold. This fault is detected while running POST.\n  Refer to %s for more information."
439 msgstr "The memory associated with the memory bank containing the errors is deconfigured.\n"
441 msgstr "POST is restarted after the memory associated with the memory bank has been deconfigured.\n"
443 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
449 msgstr "Fault"
451 msgstr "Critical"
453 msgstr "A fatal error has occurred within a FLP chip.\n  Refer to %s for more information."
455 msgstr "A single domain will be reset and the IO Channel associated with the\nFLP chip will be deconfigured during recovery.\n"
457 msgstr "Domain will be reset.\n"
459 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
465 msgstr "Fault"
467 msgstr "Major"
469 msgstr "The number of correctable errors associated with a FLP chip has exceeded an\nacceptable threshold.\n  Refer to %s for more information."
471 msgstr "The IO Channel associated with the FLP chip will be deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
473 msgstr "No immediate impact. The IO Channel associated with the FLP chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is \nperformed.\n"
475 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
481 msgstr "upset"
483 msgstr "Critical"
485 msgstr "Failure to boot Solaris on a domain via an internal disk drive on the SAS controller.\n  Refer to %s for more information."
487 msgstr "Nothing is deconfigured.\n"
489 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
491 msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n"
497 msgstr "Fault"
499 msgstr "Critical"
501 msgstr "A fatal error occurred on the interface between an IOC chip and a FLP chip.\n  Refer to %s for more information."
503 msgstr "The IO Channel associated with the FLP chip will be deconfigured after the domain\nusing the IO Channel is reset.\n"
505 msgstr "The domain using the IO Channel associated with the FLP chip is reset. The IO Channel will\ndeconfigured after the domain is reset.\n"
507 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
513 msgstr "Fault"
515 msgstr "Critical"
517 msgstr "A fatal error was detected within an IOC chip.\n  Refer to %s for more information."
519 msgstr "The IOC chip (two IO Channels) will be deconfigured after the domains (one or two domains) using\nthe IOC chip are reset.\n"
521 msgstr "The domains (one or two domains) using the IOC chip are reset. The IOC chip (two IO Channels) will be \ndeconfigured after the domains are reset.\n"
523 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
529 msgstr "Upset"
531 msgstr "Critical"
533 msgstr "A fatal DMA master timeout detected by an IOC chip.\n  Refer to %s for more information."
535 msgstr "The domains (one or two domains) using the IOC chip are reset. No components are deconfigured.\n"
537 msgstr "The domains (one or two domains) using the IOC chip are reset.\n"
539 msgstr "The precise cause of the fault cannot be isolated. Please schedule a repair action.\nPlease consult the detail section of the knowledge article for additional information.\n"
545 msgstr "Fault"
547 msgstr "Critical"
549 msgstr "A fatal error was detected within an IOC chip. This fatal error affects only a single\nIO Channel.\n  Refer to %s for more information."
551 msgstr "The IO Channel will be deconfigured after the domain is reset.\n"
553 msgstr "The domain using the IO Channel is reset. The IO Channel will be deconfigured after\nthe domain is reset.\n"
555 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information\n"
561 msgstr "Fault"
563 msgstr "Critical"
565 msgstr "A fatal error was detected within an IOC chip. The fatal error affects only one leaf within\nan IO Channel (1/2 an IO Channel).\n  Refer to %s for more information."
567 msgstr "The IO Channel leaf (1/2 an IO Channel) will be deconfigured after the domain using the IO\nChannel is reset.\n"
569 msgstr "The domain using the IO Channel leaf is reset. The IO Channel leaf (1/2 an IO Channel) will be\ndeconfigured after the domain is reset.\n"
571 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
577 msgstr "Fault"
579 msgstr "Critical"
581 msgstr "A fatal error was detected on a PCI-Express card in a PCI slot.\n  Refer to %s for more information."
583 msgstr "The PCI-Express card is deconfigured.\n"
585 msgstr "The domain using the PCI slot is reset.\n"
587 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
593 msgstr "Fault"
595 msgstr "Critical"
597 msgstr "A fatal error was detected on a PCI-X card in a PCI slot.\n  Refer to %s for more information."
599 msgstr "The PCI-X card is deconfigured.\n"
601 msgstr "The domain using the PCI slot is reset.\n"
603 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
609 msgstr "Fault"
611 msgstr "Critical"
613 msgstr "A fatal error was detected within a PCIe/PCI-X bridge chip.\n  Refer to %s for more information."
615 msgstr "All internal I/O behind the PCIe/PCI-X bridge chip is deconfigured (if the\nPCIe/PCI-X bridge chip is located on an IOU or IOUA) or all the PCI-X slots \nin an I/O Boat are deconfigured (if the PCIe/PCI-X bridge chip is located on\nan I/O Boat).\n"
617 msgstr "The domain using the PCIe/PCI-X bridge chip is reset.\n"
619 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
625 msgstr "Fault"
627 msgstr "Critical"
629 msgstr "A fatal error was detected within a PCIe switch chip.\n  Refer to %s for more information."
631 msgstr "All internal I/O behind the PCIe switch chip is deconfigured (if the PCIe switch chip\nis located on an IOU) or all the PCI-Express slots or PCI-X slots in an I/O Boat are \ndeconfigured (if the PCIe switch chip is located on an I/O Boat).\n"
633 msgstr "The domain using the PCIe switch chip is reset.\n"
635 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
641 msgstr "Fault"
643 msgstr "Critical"
645 msgstr "A fatal error was detected within a Gigabit Ethernet (GbE) controller.\n  Refer to %s for more information."
647 msgstr "The Gigabit Ethernet (GbE) controller is deconfigured.\n"
649 msgstr "The domain using the Gigabit Ethernet (GbE) controller is reset.\n"
651 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
657 msgstr "Fault"
659 msgstr "Critical"
661 msgstr "A fatal error was detected within a SAS (Serial Attached SCSI) controller.\n  Refer to %s for more information."
663 msgstr "The internal SAS devices behind the SAS controller (internal HDDs, internal DVD drives, internal\ntape drives) are deconfigured.\n"
665 msgstr "The domain using the SAS controller is reset.\n"
667 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
673 msgstr "Fault"
675 msgstr "Major"
677 msgstr "A non-fatal uncorrectable error occurred on the interface between an IOC chip and a FLP chip.\n  Refer to %s for more information."
679 msgstr "The IO Channel corresponding to the FLP chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
681 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe IO Channel corresponding to the FLP chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
683 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
689 msgstr "Fault"
691 msgstr "Major"
693 msgstr "A non-fatal uncorrectable error was detected within an IOC chip. This error affects\na single IO Channel.\n  Refer to %s for more information."
695 msgstr "The IO Channel will be deconfigured after the platform is power cycled or after the domain reboots or \nafter a Dynamic Reconfiguration operation is performed.\n"
697 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic.  The IO Channel will be deconfigured \nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed.\n"
699 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
705 msgstr "Fault"
707 msgstr "Major"
709 msgstr "Non-fatal uncorrectable error was detected within an IOC chip. This error affects\na single IO Channel leaf (1/2 an IO Channel).\n  Refer to %s for more information."
711 msgstr "The IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
713 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
715 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
721 msgstr "Fault"
723 msgstr "Major"
725 msgstr "A non-fatal uncorrectable \"PCI-E card no-credit update\" error has been detected by an IOC chip.\n  Refer to %s for more information."
727 msgstr "The IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
729 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe IO Channel leaf (1/2 an IO Channel) will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
731 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
737 msgstr "Fault"
739 msgstr "Major"
741 msgstr "A non-fatal uncorrectable error occurred due to a PCI-Express card in a PCI-Express slot.\n  Refer to %s for more information."
743 msgstr "The PCI-Express slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
745 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe PCI-Express slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
747 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
753 msgstr "Fault"
755 msgstr "Major"
757 msgstr "A non-fatal uncorrectable error occcurred due to a PCI-X card in a PCI slot.\n  Refer to %s for more information."
759 msgstr "The PCI-X slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
761 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nThe PCI-X slot will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
763 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
769 msgstr "Fault"
771 msgstr "Major"
773 msgstr "A non-fatal uncorrectable error was detected within a PCIe/PCI-X bridge chip.\n  Refer to %s for more information."
775 msgstr "All internal I/O behind the PCIe/PCI-X bridge chip is deconfigured (if the\nPCIe/PCI-X bridge chip is located on an IOU or IOUA) or all the PCI-X slots \nin an I/O Boat are deconfigured (if the PCIe/PCI-X bridge chip is located on\nan I/O Boat). The deconfiguration will take place after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
777 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nAll internal I/O behind the PCIe/PCI-X bridge chip is deconfigured (if the\nPCIe/PCI-X bridge chip is located on an IOU or IOUA) or all the PCI-X slots \nin an I/O Boat are deconfigured (if the PCIe/PCI-X bridge chip is located on\nan I/O Boat). The deconfiguration will take place after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
779 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
785 msgstr "Fault"
787 msgstr "Major"
789 msgstr "A non-fatal uncorrectable error was detected within a PCIe switch chip.\n  Refer to %s for more information."
791 msgstr "All internal I/O behind the PCIe switch chip is deconfigured (if the PCIe switch chip\nis located on an IOU) or all the PCI-Express slots or PCI-X slots in an I/O Boat are \ndeconfigured (if the PCIe switch chip is located on an I/O Boat). The deconfiguration\nwill take place after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n"
793 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \nAll internal I/O behind the PCIe switch chip is deconfigured (if the PCIe switch chip\nis located on an IOU) or all the PCI-Express slots or PCI-X slots in an I/O Boat are \ndeconfigured (if the PCIe switch chip is located on an I/O Boat). The deconfiguration\nwill take place after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n"
795 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
801 msgstr "Fault"
803 msgstr "Major"
805 msgstr "The number of correctable errors on the interface between an IOC chip and a FLP chip has exceeded \nan acceptable threshold.\n  Refer to %s for more information."
807 msgstr "The IO Channel that is associated with the FLP chip will be deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
809 msgstr "No immediate impact. The IO Channel that is associated with the FLP chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is \nperformed.\n"
811 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
817 msgstr "Fault"
819 msgstr "Major"
821 msgstr "The number of correctable errors within a IOC Chip has exceeded an acceptable threshold. This fault\naffects a single IO Channel.\n  Refer to %s for more information."
823 msgstr "The IO Channel is deconfigured after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n"
825 msgstr "No immediate impact. The IO Channel is deconfigured after the platform is power cycled or after the \ndomain reboots or after a Dynamic Reconfiguration operation is performed.\n"
827 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
833 msgstr "Fault"
835 msgstr "Major"
837 msgstr "The number of correctable errors within a IOC Chip has exceeded an acceptable threshold. This fault\naffects a single IO Channel leaf (1/2 an IO Channel).\n  Refer to %s for more information."
839 msgstr "The IO Channel leaf (1/2 an IO Channel) is deconfigured after the platform is power cycled or after \nthe domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
841 msgstr "No immediate impact. The IO Channel leaf (1/2 an IO Channel) is deconfigured after the platform is \npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
843 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
849 msgstr "Upset"
851 msgstr "Critical"
853 msgstr "Failure to boot Solaris on a domain using a device on an IO Channel.\n  Refer to %s for more information."
855 msgstr "Nothing is deconfigured.\n"
857 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
859 msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary. Please consult the detail section of the \nknowledge article for additional information.\n"
865 msgstr "Upset"
867 msgstr "Critical"
869 msgstr "Failure to boot Solaris on a domain using a device on IO Channel leaf (1/2 an IO Channel).\n  Refer to %s for more information."
871 msgstr "Nothing is deconfigured.\n"
873 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
875 msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary. Please consult the detail section of the \nknowledge article for additional information.\n"
881 msgstr "Upset"
883 msgstr "Critical"
885 msgstr "Failure to boot Solaris on a domain via GbE.\n  Refer to %s for more information."
887 msgstr "Nothing is deconfigured.\n"
889 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
891 msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n"
897 msgstr "Upset"
899 msgstr "Critical"
901 msgstr "Failure to boot Solaris on a domain using a device in a PCI-X slot.\n  Refer to %s for more information."
903 msgstr "Nothing is deconfigured.\n"
905 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt\n"
907 msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n"
913 msgstr "Upset"
915 msgstr "Critical"
917 msgstr "Failure to boot Solaris on a domain using a device in a PCI-Express slot.\n  Refer to %s for more information."
919 msgstr "Nothing is deconfigured.\n"
921 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
923 msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n"
929 msgstr "Upset"
931 msgstr "Critical"
933 msgstr "Failure to boot Solaris on a domain using a device behind a PCI-Express/PCI-X \nbridge chip. This includes the PCI-X slot and internal I/O on an IOU (if the\nPCI-Express/PCI-X bridge is located on an IOU or IOUA) and the PCI-X slots of\nan I/O Boat (if the PCI-Express/PCI-X bridge is located on an I/O Boat).\n  Refer to %s for more information."
935 msgstr "Nothing is deconfigured.\n"
937 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
939 msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n"
945 msgstr "upset"
947 msgstr "Critical"
949 msgstr "Failure to boot Solaris on a domain using a device behind a PCI-Express switch chip.\nThis includes PCI-X slot and internal I/O devices (if the PCI-Express switch chip \nis located on an IOU), and the PCI-Express slots and PCI-X slots on an I/O Boat\n(if the PCI-Express switch chip is located on an I/O Boat).\n  Refer to %s for more information."
951 msgstr "Nothing is deconfigured.\n"
953 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
955 msgstr "The platform administrator should investigate the cause of the boot problem\nand schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n"
961 msgstr "Upset"
963 msgstr "Critical"
965 msgstr "Failure to boot Solaris on a domain using an internal SAS (Serial Attached\nSCSI) device. This includes the internal hard drives and the internal DVD drives\nand the internal tape drives.\n  Refer to %s for more information."
967 msgstr "Nothing is deconfigured.\n"
969 msgstr "The domain drops to the OpenBoot PROM 'ok' prompt.\n"
971 msgstr "The platform administrator should investigate the cause of the boot\nproblem and schedule a service action, if necessary.\nPlease consult the detail section of the knowledge article for additional information.\n"
977 msgstr "Fault"
979 msgstr "Critical"
981 msgstr "JTAG read or write failure to a specific chip.\n  Refer to %s for more information."
983 msgstr "The resources associated with the chip will be deconfigured. Please consult the detail section \nof the knowledge article for additional information.\n"
985 msgstr "The platform may be reset or a domain may be reset. The platform may be unable to restart.\nPlease consult the detail section of the knowledge article for additional information.\n"
987 msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
993 msgstr "Fault"
995 msgstr "Critical"
997 msgstr "JTAG access failure to a specific chip when attempting a reconfiguration operation.\nPlease consult the detail section of the knowledge article for additional information.\n  Refer to %s for more information."
999 msgstr "The resources associated with the chip will be deconfigured. Please consult the detail section of \nthe knowledge article for additional information.\n"
1001 msgstr "The platform may be reset or a domain may be reset. The platform may become unbootable.\nIt is also possible that some other problem may occur. Please consult the detail section of the \nknowledge article for additional information.\n"
1003 msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1009 msgstr "Fault"
1011 msgstr "Critical"
1013 msgstr "I2C access failure to an I2C device.\n  Refer to %s for more information."
1015 msgstr "The resources associated with the I2C device may deconfigured. The speed of all fans on the platform\nmay be raised. Please consult the detail section of the knowledge article for additional information.\n"
1017 msgstr "It is possible that the platform will not be able to be be restarted. Please consult the detail section \nof the knowledge article for additional information.\n"
1019 msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1025 msgstr "Fault"
1027 msgstr "Critical"
1029 msgstr "I2C access failure to a specific chip when attempting a reconfiguration operation.\nPlease consult the detail section of the knowledge article for additional information.\n  Refer to %s for more information."
1031 msgstr "The resources associated with the chip will be deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n"
1033 msgstr "One or more domains may be reset. It is also possible that some other problem may occur. \nPlease consult the detail section of the knowledge article for additional information.\n"
1035 msgstr "The platform administrator should schedule a service action to replace\nthe affected Field Replaceable Unit (FRU), the identity of which can be\ndetermined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1041 msgstr "Fault"
1043 msgstr "Critical"
1045 msgstr "A fatal error was detected within a MAC chip.\n  Refer to %s for more information."
1047 msgstr "Memory associated within the MAC chip will be deconfigured.\n"
1049 msgstr "Platform may be reset or domains using the MAC chip will be reset.\n"
1051 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1057 msgstr "Fault"
1059 msgstr "Critical"
1061 msgstr "A fatal error was detected within the part of a MAC chip that controls a memory bank.\n  Refer to %s for more information."
1063 msgstr "The bank of memory is deconfigured.\n"
1065 msgstr "Domain using the memory bank will be reset.\n"
1067 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1073 msgstr "Fault"
1075 msgstr "Major"
1077 msgstr "A non-fatal uncorrectable error was detected within a MAC chip.\n  Refer to %s for more information."
1079 msgstr "Memory associated with the MAC chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1081 msgstr "The domain may panic, the MAC memory patrol feature may stop working, or access to MAC registers from the\ndomain may fail.\n"
1083 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1089 msgstr "Fault"
1091 msgstr "Major"
1093 msgstr "A non-fatal uncorrectable error was detected within the part of a MAC chip that controls a memory bank.\n  Refer to %s for more information."
1095 msgstr "Memory associated with this memory bank is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1097 msgstr "The domain will encounter an non-fatal uncorrectable error and the domain may panic.\n"
1099 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1105 msgstr "Fault"
1107 msgstr "Major"
1109 msgstr "The number of correctable errors detected within a MAC chip has exceeded an\nacceptable threshold.\n  Refer to %s for more information."
1111 msgstr "Memory associated to the MAC will be deconfigured after the platform is power cycled or after \nthe domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1113 msgstr "No immediate impact. Memory associated to the MAC will be deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1115 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1121 msgstr "Fault"
1123 msgstr "Major"
1125 msgstr "The number of correctable errors detected within the part of a MAC chip that controls a memory\nbank has exceeded an acceptable threshold.\n  Refer to %s for more information."
1127 msgstr "Memory associated with the memory bank will be deconfigured after the platform is power cycled or after \nthe domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1129 msgstr "No immediate impact. Memory associated with the memory bank will be deconfigured after the platform \nis power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1131 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1137 msgstr "Fault"
1139 msgstr "Major"
1141 msgstr "Machine Administration Sofware (MADM) on the domain detected a serious I/O problem.\n  Refer to %s for more information."
1143 msgstr "No immediate action is taken and nothing is deconfigured.\n"
1145 msgstr "Problem with an I/O device.\n"
1147 msgstr "The platform administrator should use the output of the showlogs command to determine\nif a service action is necessary.  Please consult the detail section of the knowledge\narticle for additional information.\n"
1153 msgstr "Fault"
1155 msgstr "Critical"
1157 msgstr "Machine Administration Sofware (MADM) on the domain detected a fatal I/O problem.\n  Refer to %s for more information."
1159 msgstr "Nothing is deconfigured on the XSCF, but the domain will deconfigure the I/O device.\n"
1161 msgstr "Problem with an I/O device.\n"
1163 msgstr "The platform administrator should use the output of the showlogs command to determine\nif a service action is necessary.  Please consult the detail section of the knowledge\narticle for additional information.\n"
1169 msgstr "Fault"
1171 msgstr "Critical"
1173 msgstr "A fatal error occurred on the interface between a MBC chip and a SC chip.\n  Refer to %s for more information."
1175 msgstr "Resources associated with the faulty FRU will be deconfigured. Please consult the \ndetail section of the knowledge article for additional information.\n"
1177 msgstr "Either the platform or a domain is reset. The platform may become unbootable.\nPlease consult the detail section of the knowledge article for additional information.\n"
1179 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1185 msgstr "Fault"
1187 msgstr "Critical"
1189 msgstr "A fatal error was detected within a MBC chip.\n  Refer to %s for more information."
1191 msgstr "Resources associated with the faulty FRU will be deconfigured. Please consult the \ndetail section of the knowledge article for additional information.\n"
1193 msgstr "Either the platform will be reset or a domain may be reset. The platform may become unbootable.\nPlease consult the detail section of the knowledge article for additional information.\n"
1195 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1201 msgstr "Fault"
1203 msgstr "Critical"
1205 msgstr "A non-fatal uncorrectable error occurred on the interface between a MBC chip and a SC chip.\n  Refer to %s for more information."
1207 msgstr "No immediate action is taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconfigured after the platform is\npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed. This resource deconfiguration may cause the platform to become\nunbootable. Please consult the detail section of the knowledge article for additional information.\n"
1209 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \n"
1211 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1217 msgstr "Fault"
1219 msgstr "Critical"
1221 msgstr "A non-fatal uncorrectable error occurred on the interface between a MBC chip and the XSCF.\n  Refer to %s for more information."
1223 msgstr "No immediate action is taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconfigured after the platform is\npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed. This resource deconfiguration may cause the platform to become\nunbootable. Please consult the detail section of the knowledge article for additional information.\n"
1225 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \n"
1227 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1233 msgstr "Fault"
1235 msgstr "Critical"
1237 msgstr "A non-fatal uncorrectable error was detected within a MBC chip.\n  Refer to %s for more information."
1239 msgstr "No immediate action is taken by XSCF software due to this fault.\nResources associated with the faulty FRU will be deconfigured after the platform is\npower cycled or after the domain reboots or after a Dynamic Reconfiguration operation \nis performed. This resource deconfiguration may cause the platform to become\nunbootable. Please consult the detail section of the knowledge article for additional information.\n"
1241 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. \n"
1243 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1249 msgstr "Fault"
1251 msgstr "Major"
1253 msgstr "An uncorrectable error was detected on a DMA channel between two MBC chips on two\ndifferent FRUs. Please consult the detail section of the knowledge article for additional information.\n  Refer to %s for more information."
1255 msgstr "There are two DMA channels between MBC chips. If the first DMA channel fails, the system\nwill switch to using the second DMA channel. If the second DMA channel fails, then the\nFRU with the MBC chip becomes unmanageable. If the second DMA channel fails, then resources\nassociated with the FRU with the MBC chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nDeconfiguration of these resources may reduce system performance or may cause the\nplatform to become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n"
1257 msgstr "If it is the second DMA channel for the MBC chip that has failed, the XSCF will no longer be able \nto contact the chips and devices that are connected to the faulty MBC chip.\n"
1259 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1265 msgstr "Fault"
1267 msgstr "Major"
1269 msgstr "A non-fatal uncorrectable internal error was detected on the DMA interface used by DSCP \non a MBC chip.\n  Refer to %s for more information."
1271 msgstr "DSCP will switch to use some other XSB's DMA interface, if there is an operational DMA interface\non another XSB in this domain. Otherwise, the system will continue to use the existing DMA interface.\nThe XSB with this DMA interface will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nPlease consult the detail section of the knowledge article for additional information.\n"
1273 msgstr "The domain may encounter an uncorrectable error, but the domain will not panic.\n"
1275 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1281 msgstr "Fault"
1283 msgstr "Major"
1285 msgstr "XSCF software detected a problem on the command interface between the XSCF and an XSB.\n  Refer to %s for more information."
1287 msgstr "If the problem can be isolated to a specific XSB, the system will switch to use some other XSB's \ncommand interface, if there is an operational command interface on another XSB in this domain. Otherwise, \nthe system will continue to use the existing command interface. The XSB with this command interface will \nbe deconfigured after the platform is power cycled or after the domain reboots or after a Dynamic \nReconfiguration operation is performed. If the problem cannot be isolated to a specific XSB, no\ndeconfiguration is performed. Please consult the detail section of the knowledge article for additional \ninformation.\n"
1289 msgstr "No immediate impact.\n"
1291 msgstr "If the problem can be isolated to a specific XSB, schedule a repair action to replace the affected \nField Replaceable Unit (FRU), the identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1297 msgstr "Fault"
1299 msgstr "Major"
1301 msgstr "The number of correctable errors on the interface between a MBC chip and a SC chip has exceeded \nan acceptable threshold.\n  Refer to %s for more information."
1303 msgstr "Resources associated with this SC chip (this includes CPU chips, memory, and I/O) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration \noperation is performed. Please consult the detail section of the knowledge article for additional information.\n"
1305 msgstr "No immediate action. Resources associated with this SC chip (this includes CPU chips, memory, and I/O) \nwill be deconfigured after the platform is power cycled or after the domain reboots or after a Dynamic \nReconfiguration operation is performed. Please consult the detail section of the knowledge article for \nadditional information.\n"
1307 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1313 msgstr "Fault"
1315 msgstr "Major"
1317 msgstr "The number of correctable errors within the SRAM of a MBC chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
1319 msgstr "The resources associated with this MBC chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n"
1321 msgstr "No immediate impact.\n"
1323 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1329 msgstr "Fault"
1331 msgstr "Major"
1333 msgstr "An error was detected within the section of a MBC chip dealing with a specific\nXSB. This error is detected during self-test.\n  Refer to %s for more information."
1335 msgstr "The XSB is deconfigured.\n"
1337 msgstr "No immediate impact. The XSB is deconfigured.\n"
1339 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1345 msgstr "Fault"
1347 msgstr "Critical"
1349 msgstr "The MAC chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1351 msgstr "Nothing is deconfigured.\n"
1353 msgstr "The domain using the MAC chip will be reset.\n"
1355 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1361 msgstr "Fault"
1363 msgstr "Critical"
1365 msgstr "The SC chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1367 msgstr "Resources may be deconfigured after a platform reset.\nPlease consult the detail section of the knowledge article for additional information.\n"
1369 msgstr "Either the platform or a domain will be reset. Please consult the detail section of the \nknowledge article for additional information.\n"
1371 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1377 msgstr "Fault"
1379 msgstr "Critical"
1381 msgstr "The XB chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1383 msgstr "Resources may be deconfigured after a platform reset.\nPlease consult the detail section of the knowledge article for additional information.\n"
1385 msgstr "The platform will be reset.\n"
1387 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1393 msgstr "Fault"
1395 msgstr "Critical"
1397 msgstr "The IOC chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1399 msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n"
1401 msgstr "The domains using the IOC chip will be reset.\n"
1403 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1409 msgstr "Fault"
1411 msgstr "Critical"
1413 msgstr "The Clock chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1415 msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n"
1417 msgstr "The platform will be reset.\n"
1419 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1425 msgstr "Fault"
1427 msgstr "Critical"
1429 msgstr "A CPU chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1431 msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n"
1433 msgstr "The domain using the CPU chip will reset.\n"
1435 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1441 msgstr "Fault"
1443 msgstr "Critical"
1445 msgstr "A FLP chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1447 msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n"
1449 msgstr "The domain using the FLP chip will be reset.\n"
1451 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1457 msgstr "Fault"
1459 msgstr "Critical"
1461 msgstr "A MBC chip has detected it does not have sufficient power to continue operating.\n  Refer to %s for more information."
1463 msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n"
1465 msgstr "Either the platform or a domain will be reset. Please consult the detail section of \nthe knowledge article for additional information.\n"
1467 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1473 msgstr "Fault"
1475 msgstr "Critical"
1477 msgstr "Some ASIC has detected it does not have sufficient power to continue operating. It is unknown\nwhich type of ASIC detected the falure.\n  Refer to %s for more information."
1479 msgstr "Nothing is deconfigured.\nPlease consult the detail section of the knowledge article for additional information.\n"
1481 msgstr "Either the platform or a domain will be reset. Please consult the detail section of \nthe knowledge article for additional information.\n"
1483 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
1489 msgstr "Fault"
1491 msgstr "Minor"
1493 msgstr "An undervoltage or overvoltage warning was detected by a device or FRU.\n  Refer to %s for more information."
1495 msgstr "Nothing is deconfigured and no action is taken as a result of this warning.\n"
1497 msgstr "None.\n"
1499 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1505 msgstr "Fault"
1507 msgstr "Critical"
1509 msgstr "A serious undervoltage failure has occurred on a device or FRU.\n  Refer to %s for more information."
1511 msgstr "The device or FRU will be deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n"
1513 msgstr "Domains may be reset, platform may become unbootable, or the platform may be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
1515 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1521 msgstr "Fault"
1523 msgstr "Critical"
1525 msgstr "An attempt to power-off a FRU or a device has failed during a power-off sequence. \nPlease consult the detail section of the knowledge article for additional information.\n  Refer to %s for more information."
1527 msgstr "The poweroff sequence continues. The FRU or device will be deconfigured and will\nnot be powered up during the next power-on sequence. Please consult the detail section \nof the knowledge article for additional information.\n"
1529 msgstr "Platform may become unbootable. Please consult the detail section of the knowledge \narticle for additional information.\n"
1531 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1537 msgstr "Fault"
1539 msgstr "Critical"
1541 msgstr "A component in a FRU has signaled it has failed. Please consult the detail section of \nthe knowledge article for additional information.\n  Refer to %s for more information."
1543 msgstr "The component in the FRU will be deconfigured (which may cause the FRU to be deconfigured). Please \nconsult the detail section of the knowledge article for additional information.\n"
1545 msgstr "Domains may be reset, the platform may become unbootable, or the platform may be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
1547 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1553 msgstr "Fault"
1555 msgstr "Critical"
1557 msgstr "An misconfigured FRU or device has been detected during powerup. Please consult the detail \nsection of the knowledge article for additional information.\n  Refer to %s for more information."
1559 msgstr "The misconfigured FRU or device will not be powered up. Please consult the detail section of \nthe knowledge article for additional information.\n"
1561 msgstr "The misconfigured FRU or device will not be powered up. The platform may not powerup.\nPlease consult the detail section of the knowledge article for additional information.\n"
1563 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1569 msgstr "Fault"
1571 msgstr "Critical"
1573 msgstr "A FRU or device is missing or could not be detected during powerup. Please consult the detail section \nof the knowledge article for additional information.\n  Refer to %s for more information."
1575 msgstr "If the device is not redundant, powerup of the FRU will be rejected.\nPlease consult the detail section of the knowledge article for additional information.\n"
1577 msgstr "The powerup request for FRU or device may be rejected, or the entire platform may not be powered up.\nPlease consult the detail section of the knowledge article for additional information.\n"
1579 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1585 msgstr "Fault"
1587 msgstr "Minor"
1589 msgstr "A FRU's presence was unexpectedly detected. This may be caused by insertion\nof the FRU without following the correct procedure. Please consult the detail section of the \nknowledge article for additional information.\n  Refer to %s for more information."
1591 msgstr "Nothing is deconfigured and no immediate action is taken. The FRU will not be\nconfigured into the system.\n"
1593 msgstr "None.\n"
1595 msgstr "If the FRU was inserted without following correct procedure, please use the\ncorrect procedure. Otherwise, schedule a repair action to replace the affected Field \nReplaceable Unit (FRU), the identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1601 msgstr "Fault"
1603 msgstr "Major"
1605 msgstr "A FRU's presence detect signal has suddenly disappeared. This may be caused\nby removal of the FRU without following the correct procedure.\nPlease consult the detail section of the knowledge article for additional information.\n  Refer to %s for more information."
1607 msgstr "The FRU will be deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n"
1609 msgstr "The platform may be reset, or the platform may be powered down, or a domain may be reset.\nPlease consult the detail section of the knowledge article for additional information.\n"
1611 msgstr "If the FRU has not been removed without following the correct procedure,\nschedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1617 msgstr "Fault"
1619 msgstr "Major"
1621 msgstr "PSU has detected a loss of AC power.\n  Refer to %s for more information."
1623 msgstr "The PSU will be deconfigured. If sufficient operational PSU's remain, the fan speeds of\nall fans will be increased. Please consult the detail section of the knowledge article for \nadditional information.\n"
1625 msgstr "If there are insufficient operational PSU's, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
1627 msgstr "The platform administrator should check the AC power connections and schedule a \nservice action, if necessary. Please consult the detail section of the knowledge article \nfor additional information.\n"
1633 msgstr "Fault"
1635 msgstr "Major"
1637 msgstr "Problems have been detected with an external UPS.\n  Refer to %s for more information."
1639 msgstr "Nothing is deconfigured and no immediate action is taken.\n"
1641 msgstr "None.\n"
1643 msgstr "The platform administrator should investigate the UPS.\n"
1649 msgstr "Fault"
1651 msgstr "Critical"
1653 msgstr "Error detected by an RCI device on the RCI Network.\n  Refer to %s for more information."
1655 msgstr "Nothing is deconfigured. The entire system may be powered down or there may be no \ncommunication with RCI devices. Please consult the detail section of the knowledge article \nfor additional information.\n"
1657 msgstr "The entire system may be powered down or there may be no communication with RCI devices.\nPlease consult the detail section of the knowledge article for additional information.\n"
1659 msgstr "The platform administrator should use the output of the showlogs command to determine\nwhat type of service action is necessary.  Please consult the detail section of the knowledge\narticle for additional information.\n"
1665 msgstr "Fault"
1667 msgstr "Critical"
1669 msgstr "A fatal error was detected within a SC chip. This error may affect multiple CMU's.\n  Refer to %s for more information."
1671 msgstr "The CMU that contains this SC chip and all its associated IO are deconfigured.\n"
1673 msgstr "One or more domains are reset. Please consult the detail section of the knowledge article for \nadditional information.\n"
1675 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1681 msgstr "Fault"
1683 msgstr "Critical"
1685 msgstr "A fatal error occurred on the interface between a CPU chip and a SC chip.\n  Refer to %s for more information."
1687 msgstr "The CPU chip is deconfigured.\n"
1689 msgstr "The single domain using the CPU chip is reset.\n"
1691 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1697 msgstr "Fault"
1699 msgstr "Critical"
1701 msgstr "A fatal error occurred on the interface between a SC chip and a CPU chip.\n  Refer to %s for more information."
1703 msgstr "The CPU chip is deconfigured.\n"
1705 msgstr "The single domain using the CPU chip is reset.\n"
1707 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1713 msgstr "Fault"
1715 msgstr "Critical"
1717 msgstr "A fatal error occurred on the interface between a SC chip and a XB chip.\n  Refer to %s for more information."
1719 msgstr "The CMU containing the SC chip along with all its associated IO is deconfigured.\n"
1721 msgstr "All domains using the CMU are reset.\n"
1723 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1729 msgstr "Fault"
1731 msgstr "Critical"
1733 msgstr "A fatal error occurred on the interface between a MAC chip and a SC chip.\n  Refer to %s for more information."
1735 msgstr "Memory associated with the MAC chip is deconfigured.\n"
1737 msgstr "One or more domains will be reset. Please consult the detail section of the knowledge \narticle for additional information.\n"
1739 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1745 msgstr "Fault"
1747 msgstr "Critical"
1749 msgstr "A fatal error occurred on the interface between a SC chip and a MAC chip.\n  Refer to %s for more information."
1751 msgstr "Memory associated with the MAC chip is deconfigured.\n"
1753 msgstr "One or more domains will be reset. Please consult the detail section of the knowledge \narticle for additional information.\n"
1755 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1761 msgstr "Fault"
1763 msgstr "Critical"
1765 msgstr "A fatal error occurred on the interface between a SC chip and the portion of the MAC chip \ninterfaces with a single memory bank.\n  Refer to %s for more information."
1767 msgstr "Memory associated with the memory bank is deconfigured.\n"
1769 msgstr "One or more domains will be reset. Please consult the detail section of the knowledge \narticle for additional information.\n"
1771 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1777 msgstr "Fault"
1779 msgstr "Critical"
1781 msgstr "A fatal error occurred on the interface between an IO Channel and a SC chip.\n  Refer to %s for more information."
1783 msgstr "The IO Channel is deconfigured.\n"
1785 msgstr "The domain that is using the IO Channel is reset.\n"
1787 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1793 msgstr "Fault"
1795 msgstr "Critical"
1797 msgstr "A fatal error occurred on the interface between a SC chip and an IO Channel.\n  Refer to %s for more information."
1799 msgstr "The IO Channel is deconfigured.\n"
1801 msgstr "The domain that is using the IO Channel is reset.\n"
1803 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1809 msgstr "Fault"
1811 msgstr "Critical"
1813 msgstr "A fatal error on the interface between two SC chips has occurred.\n  Refer to %s for more information."
1815 msgstr "Some number of CPU chips, some number of MAC chips, and some amount of IO will be deconfigured.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n"
1817 msgstr "One or more domains will be reset. The platform may become unbootable. \nPlease consult the detail section of the knowledge article for additional information.\n"
1819 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1825 msgstr "Fault"
1827 msgstr "Critical"
1829 msgstr "A fatal error was detected within a SC chip.\n  Refer to %s for more information."
1831 msgstr "Some number of CPU chips, some number of MAC chips, and some amount of IO will be deconfigured.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n"
1833 msgstr "One or more domains will be reset. The platform may become unbootable. Please consult the \ndetail section of the knowledge article for additional information.\n"
1835 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1841 msgstr "Fault"
1843 msgstr "Critical"
1845 msgstr "A non-fatal uncorrectable error was detected within a SC chip.\n  Refer to %s for more information."
1847 msgstr "Nothing is deconfigured.\n"
1849 msgstr "No immediate action is taken as a result of this fault. The domain may not\nbe operational. Please consult the detail section of the knowledge article for additional information.\n"
1851 msgstr "The platform administrator should investigate and see if there is some other\nhardware fault that might possibly be related to this fault.\nPlease consult the detail section of the knowledge article for additional information.\n"
1857 msgstr "Fault"
1859 msgstr "Minor"
1861 msgstr "The number of correctable errors on the interface between a CPU chip and a SC chip \nhas exceeded an acceptable threshold.\n  Refer to %s for more information."
1863 msgstr "The CPU chip is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1865 msgstr "No immediate impact. The CPU chip is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1867 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1873 msgstr "Fault"
1875 msgstr "Major"
1877 msgstr "The number of correctable errors on the interface between a SC chip and a XB chip \nhas exceeded an acceptable threshold.\n  Refer to %s for more information."
1879 msgstr "The CMU and all its associated IO are deconfigured after the platform is power cycled or \nafter the domains using the CMU reboot or after a Dynamic Reconfiguration operation is performed.\n"
1881 msgstr "No immediate impact. The CMU and all its associated IO are deconfigured after the platform is power \ncycled or after the domains using the CMU reboot or after a Dynamic Reconfiguration operation is performed.\n"
1883 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1889 msgstr "Fault"
1891 msgstr "Minor"
1893 msgstr "The number of correctable errors on the interface between a MAC chip and a SC chip\nhas exceeded an acceptable threshold.\n  Refer to %s for more information."
1895 msgstr "Memory associated with the MAC is deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1897 msgstr "No immediate impact. Memory associated with the MAC is deconfigured after the platform is power \ncycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
1899 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1905 msgstr "Fault"
1907 msgstr "Major"
1909 msgstr "The number of correctable errors on the interface between an IO Channel and a SC chip \nhas exceeded an acceptable threshold.\n  Refer to %s for more information."
1911 msgstr "The IO Channel is deconfigured after the platform is power cycled or after the domain reboots or after a \nDynamic Reconfiguration operation is performed.\n"
1913 msgstr "No immediate impact. The IO Channel is deconfigured after the platform is power cycled or after the domain \nreboots or after a Dynamic Reconfiguration operation is performed.\n"
1915 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1921 msgstr "Fault"
1923 msgstr "Critical"
1925 msgstr "The number of correctable errors on the interface between two SC chips has exceeded an acceptable threshold.\n  Refer to %s for more information."
1927 msgstr "Some resources associated with the SC chips (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n"
1929 msgstr "No immediate impact. Some resources associated with the SC chips (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n"
1931 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1937 msgstr "Fault"
1939 msgstr "Critical"
1941 msgstr "The number of correctable errors detected within a SC chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
1943 msgstr "Some resources associated with the SC chip (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n"
1945 msgstr "No immediate impact. Some resources associated with the SC chip (CPU chips, memory, IO Channels) will be deconfigured\nafter the platform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for additional information.\n"
1947 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1953 msgstr "Fault"
1955 msgstr "Minor"
1957 msgstr "The number of correctable errors within the L2 cache tags of a SC chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
1959 msgstr "One of the L2 cache ways is deconfigured for all the CPU chips associated with this SC chip.\n"
1961 msgstr "The domain is unaffected, except for the performance of the CPU chips.\n"
1963 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1969 msgstr "Fault"
1971 msgstr "Critical"
1973 msgstr "Self-test error detected within a  SC chip or a SC chip interface to another chip.\n  Refer to %s for more information."
1975 msgstr "Some number of CPU chips, some number of MAC chips, and some amount of IO will be deconfigured.\nThe platform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n"
1977 msgstr "Running domains are unaffected by this fault, as this occurs during self-test. The\nplatform may become unbootable. Please consult the detail section of the knowledge article for \nadditional information.\n"
1979 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
1985 msgstr "Defect"
1987 msgstr "Major"
1989 msgstr "An XSCF firmware process has unexpectedly terminated. \n  Refer to %s for more information."
1991 msgstr "The XSCF firmware will be rebooted.\n"
1993 msgstr "XSCF functionality will be unavailable until the XSCF has restarted.\n"
1995 msgstr "Schedule a repair action to upgrade the XCP firmware. Please consult the detail section \nof the knowledge article for additional information.\n"
2001 msgstr "Upset"
2003 msgstr "Major"
2005 msgstr "The XSCF has detected that a Solaris domain has panic'ed.\n  Refer to %s for more information."
2007 msgstr "No action is taken due to this fault.\n"
2009 msgstr "The Solaris domain has panic'ed.\n"
2011 msgstr "The administrator should look at the domain's console to identify the cause of the panic.\nPlease consult the detail section of the knowledge article for additional information.\n"
2017 msgstr "Upset"
2019 msgstr "Major"
2021 msgstr "The XSB could not be successfully configured into a domain.\n  Refer to %s for more information."
2023 msgstr "Nothing is deconfigured.\n"
2025 msgstr "XSB is not successfully configured into a domain.\n"
2027 msgstr "The platform administrator should investigate why the XSB could not be configured \ninto the domain. Please consult the detail section of the knowledge article for additional \ninformation.\n"
2033 msgstr "Upset"
2035 msgstr "Major"
2037 msgstr "The XSCF could not determine whether POST is running correctly on a domain/XSB.\n  Refer to %s for more information."
2039 msgstr "Nothing is deconfigured.\n"
2041 msgstr "The domain or the XSB will be powered down.\n"
2043 msgstr "The platform administrator should check for some sort of fault that could have\ncaused this failure. Please consult the detail section of the knowledge article for additional \ninformation.\n"
2049 msgstr "Upset"
2051 msgstr "Major"
2053 msgstr "Domain does not respond to XSCF keep-alive messages.\n  Refer to %s for more information."
2055 msgstr "The XSCF will send a message to the domain asking it to panic.\n"
2057 msgstr "The XSCF will send a message to the domain asking it to panic.\n"
2059 msgstr "To investigate potential hardware problems, the platform administrator should\nlook at the fault logs on the XSCF to determine if there is some other hardware\nproblem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n"
2065 msgstr "Upset"
2067 msgstr "Minor"
2069 msgstr "TTY buffer for a domain overflowed, resulting in lost domain console data.\n  Refer to %s for more information."
2071 msgstr "No action is taken as a result of this fault.\n"
2073 msgstr "Domain console data is lost.\n"
2075 msgstr "None. Please consult the detail section of the knowledge article for additional information.\n"
2081 msgstr "Upset"
2083 msgstr "Major"
2085 msgstr "Domain did not respond to an XSCF request for it to panic.\n  Refer to %s for more information."
2087 msgstr "The XSCF will send an XIR interrupt to the domain.\n"
2089 msgstr "The XSCF will send an XIR interrupt to the domain.\n"
2091 msgstr "The platform administrator should look at the fault logs on the XSCF to determine if there is \nsome hardware problem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n"
2097 msgstr "Upset"
2099 msgstr "Major"
2101 msgstr "Domain did not respond to an XIR interrupt sent by the XSCF.\n  Refer to %s for more information."
2103 msgstr "The XSCF will attempt to reset the domain.\n"
2105 msgstr "The XSCF will attempt to reset the domain.\n"
2107 msgstr "The platform administrator should look at the fault logs on the XSCF to determine if there is \nsome hardware problem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n"
2113 msgstr "Upset"
2115 msgstr "Major"
2117 msgstr "Domain does not respond to the XSCF's request to reset itself.\n  Refer to %s for more information."
2119 msgstr "The XSCF will power the domain down.\n"
2121 msgstr "The XSCF will power the domain down.\n"
2123 msgstr "The platform administrator should look at the fault logs on the XSCF to determine if there is \nsome hardware problem that may be causing the upset. Please consult the detail section of \nthe knowledge article for additional information.\n"
2129 msgstr "Fault"
2131 msgstr "Major"
2133 msgstr "The fan rotation speed for a fan is lower is than its predefined threshold or a fan \nhas stopped completely.\n  Refer to %s for more information."
2135 msgstr "If there are sufficient fans to maintain normal operation, fan speeds for fans on the \nrest of the platform are raised. If there are insufficient fans to maintain normal\noperation, domains are requested to shut down.\n"
2137 msgstr "If there are insufficient fans to maintain normal operation, domains are sent shutdown requests.\nIf the fan is in a PSU, the PSU is deconfigured.\n"
2139 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2145 msgstr "Fault"
2147 msgstr "Minor"
2149 msgstr "Fan rotation speed either dropped below a threshold or rose above a threshold during fan speed change\ntesting.\n  Refer to %s for more information."
2151 msgstr "Nothing is deconfigured.\n"
2153 msgstr "No action is taken.\n"
2155 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2161 msgstr "Fault"
2163 msgstr "Critical"
2165 msgstr "Under temperature condition detected by the inlet temperature sensor.\n  Refer to %s for more information."
2167 msgstr "Nothing is deconfigured.\n"
2169 msgstr "System may crash due to ASIC's operating outside their intended temperature ranges.\n"
2171 msgstr "The platform administrator should check for the cause of the under temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n"
2177 msgstr "Fault"
2179 msgstr "Major"
2181 msgstr "Over-temperature condition detected by an inlet temperature sensor, exhaust temperature sensor, \nor CPU temperature sensor.\n  Refer to %s for more information."
2183 msgstr "Fan speed will be raised for all fans on the platform.\n"
2185 msgstr "No immediate impact.\n"
2187 msgstr "Platform administrator should investigate the cause of the over-temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n"
2193 msgstr "Fault"
2195 msgstr "Critical"
2197 msgstr "Over-temperature warning condition has been detected by inlet temperature sensor, exhaust temperature \nsensor, or CPU temperature sensor.\n  Refer to %s for more information."
2199 msgstr "Fan speed will be raised for all fans on the platform. Shutdown messages will be sent to \ndomains on the platform.\n"
2201 msgstr "Shutdown messages will be sent to domains on the platform.\n"
2203 msgstr "Platform administrator should investigate the cause of the over-temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n"
2209 msgstr "Fault"
2211 msgstr "Critical"
2213 msgstr "Dangerous over-temperature condition detected by an exhaust temperature sensor or CPU \ntemperature sensor.\n  Refer to %s for more information."
2215 msgstr "Nothing is deconfigured. Either the platform will be powered down or specific domains will \nbe powered down. Please consult the detail section of the knowledge article for additional information.\n"
2217 msgstr "Either the platform will be powered down or specific domains will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2219 msgstr "Platform administrator should investigate the cause of the over-temperature condition.\nPlease consult the detail section of the knowledge article for additional information.\n"
2225 msgstr "Fault"
2227 msgstr "Critical"
2229 msgstr "A fatal error occurred on an interface between a XB chip and an IOC chip.\n  Refer to %s for more information."
2231 msgstr "Either the entire IOC chip or a single IO Channel will be deconfigured,\ndepending upon whether a crossbar way was deconfigured prior to the fault.\nPlease consult the detail section of the knowledge article for additional information.\n"
2233 msgstr "One or two domains will be reset, depending upon whether a crossbar way was deconfigured\nprior to the fault. Please consult the detail section of the knowledge article for additional \ninformation.\n"
2235 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2241 msgstr "Fault"
2243 msgstr "Critical"
2245 msgstr "A fatal error has occurred on an interface between a SC chip and an IOC chip,\nvia an XB chip.\n  Refer to %s for more information."
2247 msgstr "Either the entire IOC  chip or a single IO Channel will be deconfigured depending upon whether a \ncrossbar way was deconfigured prior to the fault. Please consult the detail section of the \nknowledge article for additional information.\n"
2249 msgstr "One or two domains will be reset, depending upon whether a crossbar way was deconfigured\nprior to the fault. Please consult the detail section of the knowledge article for additional \ninformation.\n"
2251 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2257 msgstr "Fault"
2259 msgstr "Major"
2261 msgstr "A fatal error has been detected on the cable interface between two XBU's.\n  Refer to %s for more information."
2263 msgstr "If a crossbar way has been deconfigured, the platform is powered down. Otherwise,\na crossbar way is deconfigured. Please consult the detail section of the knowledge \narticle for additional information.\n"
2265 msgstr "The entire platform is reset. If a crossbar way has been deconfigured, the platform is \npowered down. Otherwise, a crossbar way is deconfigured and the platform continues\nto operate with reduced performance. Please consult the detail section of the \nknowledge article for additional information.\n"
2267 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2273 msgstr "Fault"
2275 msgstr "Critical"
2277 msgstr "A fatal error has been detected on the interface between two XB chips.\n  Refer to %s for more information."
2279 msgstr "If the fault can be isolated to a CMU, the CMU and all its associated IO are deconfigured. \nIf the fault cannot be isolated to a single CMU, if a crossbar way has been deconfigured, the platform \nis powered down. Otherwise, a crossbar way is deconfigured and the platform continues to operate with \nreduced performance. Please consult the detail section of the knowledge article for additional information.\n"
2281 msgstr "If the fault can be isolated to a CMU, then one or more domains are reset and the CMU and all\nits associated IO are deconfigured. If the fault cannot be isolated to a single CMU, the entire platform is \nreset. If a crossbar way has been deconfigured, the platform is powered down. Otherwise, a crossbar way \nis deconfigured and the platform continues to operate with reduced performance.\nPlease consult the detail section of the knowledge article for additional information.\n"
2283 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2289 msgstr "Upset"
2291 msgstr "Critical"
2293 msgstr "A fatal protocol error detected by a XB chip.\n  Refer to %s for more information."
2295 msgstr "Nothing is deconfigured.\n"
2297 msgstr "The entire platform is reset.\n"
2299 msgstr "The component that is at fault is difficult to determine.\nPlease consult the detail section of the knowledge article for additional information.\n"
2305 msgstr "Fault"
2307 msgstr "Critical"
2309 msgstr "A fatal error was detected within a XB chip.\n  Refer to %s for more information."
2311 msgstr "Depending upon which part of the XB chip is faulty, either a crossbar way is deconfigured,\nor a CMU and all its associated IO are deconfigured, or an IOC chip is deconfigured,\nor an IO Channel within an IOC chip is deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n"
2313 msgstr "Depending upon which part of the XB chip is faulty, either the entire platform is\nreset, or one or more domains are reset. If the response includes deconfiguring a crossbar\nway and this is the first crossbar way to be deconfigured, the platform will operate\nwith reduced performance. If the response includes deconfiguring a crossbar way\nand a crossbar way has already been deconfigured, the platform is powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2315 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2321 msgstr "Fault"
2323 msgstr "Major"
2325 msgstr "The number of correctable errors on the interface between an XB chip and an IOC chip\nhas exceeded an acceptable threshold.\n  Refer to %s for more information."
2327 msgstr "Depending upon whether a crossbar way has already been deconfigured, either an IOC chip or an\nIOC channel will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nPlease consult the detail section of the knowledge article for additional information.\n"
2329 msgstr "No immediate impact.  Depending upon whether a crossbar way has already been deconfigured, either an IOC \nchip or an IOC channel will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\nPlease consult the detail section of the knowledge article for additional information.\n"
2331 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2337 msgstr "Fault"
2339 msgstr "Major"
2341 msgstr "The number of correctable errors on the interface between two XB chips communicating\nover an XBU cable has exceeded an acceptable threshold.\n  Refer to %s for more information."
2343 msgstr "The crossbar way is deconfigured the next time the platform is restarted. If this is the\nfirst crossbar way to be deconfigured, the platform will operate with reduced performance.\nIf a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2345 msgstr "No immediate impact. The crossbar way is deconfigured the next time the platform is restarted. \nIf this is the first crossbar way to be deconfigured, the platform will operate with reduced \nperformance. If a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2347 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2353 msgstr "Fault"
2355 msgstr "Major"
2357 msgstr "The number of correctable errors on the interface between two XB chips on the same XBU\nhas exceeded an acceptable threshold.\n  Refer to %s for more information."
2359 msgstr "The crossbar way is deconfigured the next time the platform is restarted. If this is the\nfirst crossbar way to be deconfigured, the platform will operate with reduced performance.\nIf a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2361 msgstr "No immediate impact. The crossbar way is deconfigured the next time the platform is restarted. \nIf this is the first crossbar way to be deconfigured, the platform will operate with reduced \nperformance. If a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2363 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2369 msgstr "Fault"
2371 msgstr "Major"
2373 msgstr "The number of correctable errors within a XB chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
2375 msgstr "The crossbar way is deconfigured the next time the platform is restarted. If this is the\nfirst crossbar way to be deconfigured, the platform will operate with reduced performance.\nIf a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2377 msgstr "No immediate impact. The crossbar way is deconfigured the next time the platform is restarted. \nIf this is the first crossbar way to be deconfigured, the platform will operate with reduced \nperformance. If a crossbar way has already been deconfigured, the platform will be powered down.\nPlease consult the detail section of the knowledge article for additional information.\n"
2379 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2385 msgstr "Fault"
2387 msgstr "Major"
2389 msgstr "Self-test error detected within a XB chip or within the interface of the\nXB chip to another chip.\n  Refer to %s for more information."
2391 msgstr "Depending upon which part of the XB chip is faulty, either a crossbar way is deconfigured,\nor a CMU and all its associated IO are deconfigured, or an IOC chip is deconfigured,\nor an IO Channel within an IOC chip is deconfigured. Please consult the detail section of the \nknowledge article for additional information.\n"
2393 msgstr "Depending upon which part of the XB chip is faulty, either the entire platform is\nreset, or one or more domains are reset. If the response includes deconfiguring a crossbar\nway and this is the first crossbar way to be deconfigured, the platform will operate\nwith reduced performance. If the response includes deconfiguring a crossbar way\nand a crossbar way has already been deconfigured, the platform is powered down.\nDomains are not affected, as this fault can only occur while the platform is powering up.\nPlease consult the detail section of the knowledge article for additional information.\n"
2395 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2401 msgstr "Fault"
2403 msgstr "Critical"
2405 msgstr "Fatal error detected within a XB chip. This fatal error may affect multiple CMU's.\n  Refer to %s for more information."
2407 msgstr "The CMU and all its associated IO are deconfigured.\n"
2409 msgstr "The domains running on the CMU that is deconfigured will be reset. Other\ndomains on the platform may also be reset. The CMU and all its associated \nIO are deconfigured.\n"
2411 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2417 msgstr "Fault"
2419 msgstr "Major"
2421 msgstr "Hardware problem detected within an XSCFU.\n  Refer to %s for more information."
2423 msgstr "The platform may become unmanageable. The platform may not be able to reboot. If the configuration\nhas redundant XSCFUs, the XSCF software may fail over to the other XSCFU. If the configuration has\nredundant XSCFUs, XSCFU failover may be disabled. Please consult the detail section of the knowledge \narticle for additional information.\n"
2425 msgstr "The domains will continue to run. The platform may become unmanageable. The platform\nmay not be able to reboot. If the configuration has redundant XSCFUs, the XSCF software may\nfail over to the other XSCFU. If the configuration has redundant XSCFUs, XSCFU failover may\nbe disabled. Please consult the detail section of the knowledge article for additional \ninformation.\n"
2427 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2433 msgstr "Fault"
2435 msgstr "Critical"
2437 msgstr "The XSCFU_C and XSCFU_B have mismatched board numbers. This problem will only\noccur during platform power-on.\n  Refer to %s for more information."
2439 msgstr "No domains will be allowed to be powered up until the problem is corrected.\n"
2441 msgstr "The entire platform is unbootable.\n"
2443 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2449 msgstr "upset"
2451 msgstr "Minor"
2453 msgstr "A hard-to-diagnose failure of the XSCF has occurred.\n  Refer to %s for more information."
2455 msgstr "The XSCFU will reboot. If the configuration has redundant XSCFU's, the standby XSCFU \nmay take over as the active XSCFU.\n"
2457 msgstr "The XSCFU will reboot. If the configuration has redundant XSCFU's, the standby XSCFU \nmay take over as the active XSCFU. There is no impact to the domains.\n"
2459 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
2465 msgstr "Fault"
2467 msgstr "Critical"
2469 msgstr "An internal fatal error within a CPU chip was detected.\n  Refer to %s for more information."
2471 msgstr "The domain using this CPU will be reset and the CPU chip will be deconfigured.\n"
2473 msgstr "The CPU chip will be deconfigured after the domain is reset.\n"
2475 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2481 msgstr "Fault"
2483 msgstr "Critical"
2485 msgstr "An internal fatal error within a core on a CPU chip was detected.\n  Refer to %s for more information."
2487 msgstr "The domain using this CPU will be reset and the core will be deconfigured.\n"
2489 msgstr "The domain using this CPU chip is reset.\n"
2491 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2497 msgstr "Fault"
2499 msgstr "Critical"
2501 msgstr "An internal fatal error within a strand on a CPU chip was detected.\n  Refer to %s for more information."
2503 msgstr "The domain using this CPU will be reset and the strand will be deconfigured.\n"
2505 msgstr "The domain using this CPU chip is reset.\n"
2507 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2513 msgstr "Fault"
2515 msgstr "Major"
2517 msgstr "An internal non-fatal uncorrectable error within a CPU chip has been detected.\n  Refer to %s for more information."
2519 msgstr "The CPU chip will be deconfigured after the platform is power cycled or after the domain reboots \nor after a Dynamic Reconfiguration operation is performed.\n"
2521 msgstr "The non-fatal uncorrectable error may cause domain to panic. The CPU chip will be deconfigured after the \nplatform is power cycled or after the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
2523 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2529 msgstr "Fault"
2531 msgstr "Major"
2533 msgstr "A non-fatal uncorrectable error associated with a core on a CPU chip has been detected.\n  Refer to %s for more information."
2535 msgstr "The domain software will attempt to offline the core on the CPU chip.\n"
2537 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic. If the domain\ndoes not panic, the domain software will attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
2539 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2545 msgstr "Fault"
2547 msgstr "Major"
2549 msgstr "When a non-fatal uncorrectable error occurs on a core on a CPU chip, domain software attempts to\noffline the core. This fault occurs when the number of offline attempts has exceeded an\nacceptable threshold.\n  Refer to %s for more information."
2551 msgstr "Future non-fatal uncorrectable errors for this core on a CPU chip will not be recorded on the XSCF.\n"
2553 msgstr "The uncorrectable error trap may cause the domain to panic.\n"
2555 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2561 msgstr "Fault"
2563 msgstr "Major"
2565 msgstr "A non-fatal uncorrectable error has been detected on a strand on a CPU chip.\n  Refer to %s for more information."
2567 msgstr "The strand on the CPU chip is deconfigured.\n"
2569 msgstr "The non-fatal uncorrectable error trap may cause the domain to panic.\n"
2571 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2577 msgstr "Fault"
2579 msgstr "Major"
2581 msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
2583 msgstr "The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
2585 msgstr "No immediate impact. The CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
2587 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2593 msgstr "Fault"
2595 msgstr "Major"
2597 msgstr "The number of correctable errors associated with a core on a CPU chip have exceeded an acceptable threshold.\n  Refer to %s for more information."
2599 msgstr "A request is sent to the domain software to attempt to offline the core on the CPU chip.\nThe core of the CPU chip will be deconfigured after the platform is power cycled or \nafter the domain reboots or after a Dynamic Reconfiguration operation is performed.\n"
2601 msgstr "No immediate impact.\n"
2603 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2609 msgstr "Fault"
2611 msgstr "Major"
2613 msgstr "The number of correctable errors on a core on a CPU chip has exceeded an acceptable threshold. \nThis fault occurs when the number of offline attempts has exceeded an acceptable threshold.\n  Refer to %s for more information."
2615 msgstr "Future correctable errors for this core on a CPU chip will not be recorded on the XSCF.\n"
2617 msgstr "No immediate impact.\n"
2619 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2625 msgstr "Fault"
2627 msgstr "Minor"
2629 msgstr "The number of correctable errors within a way of a CPU chip's L2 cache has exceeded an acceptable threshold.\n  Refer to %s for more information."
2631 msgstr "The way of the CPU chip's cache is deconfigured. The performance of the CPU chip is reduced.\n"
2633 msgstr "There is a performance loss for the CPU chip.\n"
2635 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2641 msgstr "Upset"
2643 msgstr "Critical"
2645 msgstr "A hard-to-diagnose problem was detected by the CPU chip.\n  Refer to %s for more information."
2647 msgstr "Nothing is deconfigured.\n"
2649 msgstr "The domain may drop to the OpenBoot PROM 'OK' prompt.\n"
2651 msgstr "The platform administrator should check to see if any other hardware failure has occurred on the platform.\nIf the problem occurs while running OpenBoot PROM, then the platform administrator should check to make sure that \nthe OpenBoot PROM environment variables have not been set incorrectly. If neither of these courses of action \nprovide a resolution, then the platform administrator should schedule a service action.\nPlease consult the detail section of the knowledge article for additional information.\n"
2657 msgstr "upset"
2659 msgstr "Critical"
2661 msgstr "An unexpected trap with some unknown cause was detected by a CPU chip during POST.\n  Refer to %s for more information."
2663 msgstr "Nothing is deconfigured.\n"
2665 msgstr "The domain is reset.\n"
2667 msgstr "Please consult the detail section of the knowledge article for additional information.\n"
2673 msgstr "Fault"
2675 msgstr "Major"
2677 msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n  Refer to %s for more information."
2679 msgstr "Nothing is deconfigured.\n"
2681 msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n"
2683 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2689 msgstr "Fault"
2691 msgstr "Major"
2693 msgstr "An internal non-fatal uncorrectable error has been detected within the CPU chip.\n  Refer to %s for more information."
2695 msgstr "Nothing is deconfigured.\n"
2697 msgstr "The non-fatal uncorrectable error may cause the domain to panic.\n"
2699 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"
2705 msgstr "Fault"
2707 msgstr "Minor"
2709 msgstr "The number of correctable errors associated with a CPU chip has exceeded an acceptable threshold.\n  Refer to %s for more information."
2711 msgstr "Nothing is deconfigured.\n"
2713 msgstr "No immediate impact.\n"
2715 msgstr "Schedule a repair action to replace the affected Field Replaceable Unit (FRU),\nthe identity of which can be determined using fmdump -v -u EVENT_ID.\nPlease consult the detail section of the knowledge article for additional information.\n"

Indexes created Wed Jul 03 21:38:27 MDT 2024