Poweredge Fru Error
Contents |
and WarningsIntroductionAMP Event MessagesASR Event MessagesBAR Event MessagesBAT Event MessagesBIOS Event MessagesBOOT Event MessagesCBL Event MessagesCMC Event MessagesCPU Event dell poweredge r710 specs MessagesCPUA Event MessagesCTL Event MessagesDH Event MessagesDIAG Event MessagesDIS dell poweredge r710 manual Event MessagesDKM Event MessagesECM Event MessagesENC Event MessagesEPP Event MessagesFAN Event MessagesFC Event dell poweredge r710 memory configuration MessagesFCD Event MessagesFLDC Event MessagesFSD Event MessagesHWC Event MessagesIOID Event MessagesIOV Event MessagesIPA Event MessagesISM Event MessagesJCP Event MessagesLC Event MessagesLIC Event MessagesLNK dell poweredge r710 price Event MessagesLOG Event MessagesMEM Event MessagesNIC Event MessagesOSD Event MessagesOSE Event MessagesPCI Event MessagesPDR Event MessagesPFM Event MessagesPOW Event MessagesPR Event MessagesPST Event MessagesPSU Event MessagesPSUA Event MessagesPWR Event MessagesRAC Event MessagesRDU Event MessagesRED Event MessagesRFL Event MessagesRFLA Event MessagesRFM Event MessagesRRDU Event MessagesRSI Event MessagesSEC
Dell Poweredge R710 Dimensions
Event MessagesSEL Event MessagesSSD Event MessagesSTOR Event MessagesSUP Event MessagesSWC Event MessagesSWU Event MessagesSYS Event MessagesTMP Event MessagesTMPS Event MessagesTST Event MessagesUEFI Event MessagesUSR Event MessagesVDR Event MessagesVF Event MessagesVFL Event MessagesVFLA Event MessagesVLT Event MessagesVME Event MessagesVRM Event Messages Dölj innehållsförteckning PDF Loading, Please wait. CMC Event Messages CMC001 Message The operation is successfully completed. Detailed Description The operation is successfully completed. Recommended Response Action No response action is required. Category Configuration (CMC = Chassis Management Controller) Severity Severity 3 (Informational) No alerts are applicable for this message CMC002 Message Unable to complete the operation because of an unknown issue. Detailed Description The operation cannot be successfully completed because of an unknown issue. Recommended Response Action Do one of the following: 1) Retry the operation. 2) Reset CMC and retry the operation. Category Configu
Error Detected Check FRU x E1418 - CPU # Presence CPU # not detected Check CPU is seated properly E141F - CPU Protocol CPU # protocol error Power cycle AC E1420 -
Dell Poweredge R710 End Of Life
CPU Bus PERR CPU Bus parity error Power cycle AC E1421 - CPU dell poweredge r710 drivers Init CPU initialization error E122A - CPU VTT PwrGd Processor VTT voltage regulator has failed. E1229 - CPU # dell poweredge r710 hard drive VCORE CPU # VCORE Regulator failure. Reseat CPU E1410 - CPU # IERR CPU had encountered an error caused by a component on the bus. E1423 - Temp CPU # Processor temperature http://www.dell.com/support/manuals/us/en/19/dell-opnmang-sw-v8.1/EEMI_13G_v1.2-v1/CMC-Event-Messages?guid=GUID-58C6E5B8-778E-4E1A-BC1E-1053D0E1D3DF&lang=en-us sensors are showing the processor temperature has reached a point outside of the allowed range. E141C - CPU Mismatch Unsupported CPU config Check CPU or BIOS revision E1422 - CPU Machine Chk CPU # machine check error Power Cycle AC E122C - CPU Power Fault CPU Power Fault Power cycle AC E122B - 0.9V Over Voltage 0.9 V regulator voltage has exceeded the allowable http://www.dell.com/support/article/us/en/04/SLN163714/en voltage range. Troubleshooting If the server will POST and BOOT into the OS, the BIOS and BMC should be updated to the latest versions. If the server will not post, drain the flea power and retry POST. Reseat any voltage regulator modules, terminator cards and power pods. Reseat all processors. Test each processor, one at a time in the first position. Test any additional processor components such as power pods or voltage regulator modules (VRM), one at a time, in the first position. Swap components with known-good components, when available. If the problem or error can be narrowed down to a processor, or a motherboard, contact Dell Support. Some errors may be caused by memory failures. Verify through the SEL logs if there are SBE or MBE events preceding the Machine Check event, and troubleshoot the memory by swapping DIMMS between banks or slots to isolate the failing component. If the problem follows a particular DIMM, replace the DIMM. if the problem follows the memory slot, replace the system board or memory riser as appropriate. If the server completes POST and is able to start Windows, check the Windows Event Lo
FRU may hold a variety of information, such as device information, hardware information, serial numbers, and part numbers. Listed below are general IPMI options, tool specific options, trouble shooting information, workaround information, examples, and known issues. For a general http://www.gnu.org/s/freeipmi/manpages/man8/ipmi-fru.8.html introduction to FreeIPMI please see freeipmi(7). GENERAL OPTIONS The following options are general options for configuring IPMI communication and executing general tool commands. -D IPMIDRIVER, --driver-type=IPMIDRIVER Specify the driver type to use instead of doing an auto selection. The currently available outofband drivers are LAN and LAN_2_0, which perform IPMI 1.5 and IPMI 2.0 respectively. The currently available inband drivers are KCS, SSIF, OPENIPMI, SUNBMC, and INTELDCMI. --disable-auto-probe dell poweredge Do not probe in-band IPMI devices for default settings. --driver-address=DRIVER-ADDRESS Specify the in-band driver address to be used instead of the probed value. DRIVER-ADDRESS should be prefixed with "0x" for a hex value and '0' for an octal value. --driver-device=DEVICE Specify the in-band driver device path to be used instead of the probed path. --register-spacing=REGISTER-SPACING Specify the in-band driver register spacing instead of the probed value. Argument is in dell poweredge r710 bytes (i.e. 32bit register spacing = 4) --target-channel-number=CHANNEL-NUMBERFR Specify the in-band driver target channel number to send IPMI requests to. --target-slave-address=SLAVE-ADDRESSFR Specify the in-band driver target slave number to send IPMI requests to. -h IPMIHOST1,IPMIHOST2,..., --hostname=IPMIHOST1[:PORT],IPMIHOST2[:PORT],... Specify the remote host(s) to communicate with. Multiple hostnames may be separated by comma or may be specified in a range format; see HOSTRANGED SUPPORT below. An optional port can be specified with each host, which may be useful in port forwarding or similar situations. -u USERNAME, --username=USERNAME Specify the username to use when authenticating with the remote host. If not specified, a null (i.e. anonymous) username is assumed. The user must have atleast USER privileges in order for this tool to operate fully. -p PASSWORD, --password=PASSWORD Specify the password to use when authenticationg with the remote host. If not specified, a null password is assumed. Maximum password length is 16 for IPMI 1.5 and 20 for IPMI 2.0. -P, --password-prompt Prompt for password to avoid possibility of listing it in process lists. -k K_G, --k-g=K_G Specify the K_g BMC key to use when authenticating with the remote host for IPMI 2.0. If not specified, a null key is assumed. To input the key in hexadecimal form, prefix the
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 24 Oct 2016 11:32:12 GMT by s_wx1011 (squid/3.5.20)