Dell Test Event Notification Message Reference 2014/10/07
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1.0 Introduction......................................................................................................13 1.1 FSD000 : "Debug authorized by customer; debugcaps: , was authorized by: , at for the period: to ." ....................... 14 2.0 Email Event Notification Test Messages..................................................... 16 2.1 Category: Audit........................................................................
2.2.6 Subcategory= Auto-Discovery [MessageID prefix =DIS].................................................. 80 2.2.7 Subcategory= Fan Event [MessageID prefix =FAN]........................................................... 82 2.2.8 Subcategory= Fiber Channel [MessageID prefix =FC].......................................................83 2.2.9 Subcategory= Hardware Config [MessageID prefix =HWC]............................................. 85 2.2.
2.3.13 Subcategory= Software Change [MessageID prefix =SWU].......................................... 216 2.3.14 Subcategory= Temperature [MessageID prefix =TMP]..................................................216 2.3.15 Subcategory= Virtual Disk [MessageID prefix =VDR]..................................................... 217 2.4 Category: System Health............................................................................................................226 2.4.
2.4.39 Subcategory= vFlash Media [MessageID prefix =VF]..................................................... 321 2.4.40 Subcategory= vFlash Event [MessageID prefix =VFL]....................................................321 2.4.41 Subcategory= vFlash Absent [MessageID prefix =VFLA]............................................... 324 2.4.42 Subcategory= Voltage [MessageID prefix =VLT]...........................................................324 2.4.43 Subcategory= Virtual Console [MessageID prefix =VRM]....
3.1.23 Subcategory= System Info [MessageID prefix =SYS].....................................................399 3.1.24 Subcategory= Temperature [MessageID prefix =TMP].................................................400 3.1.25 Subcategory= User Tracking [MessageID prefix =USR]................................................ 400 3.1.26 Subcategory= Virtual Media [MessageID prefix =VME].................................................406 3.2 Category: Configuration.............................................
3.3.3 Subcategory= Storage Contr [MessageID prefix =CTL]..................................................509 3.3.4 Subcategory= Diagnostic [MessageID prefix =DIAG]......................................................522 3.3.5 Subcategory= Storage Enclosr [MessageID prefix =ENC]...............................................525 3.3.6 Subcategory= Fan Event [MessageID prefix =FAN]......................................................... 529 3.3.7 Subcategory= Unknown [MessageID prefix =FLDC]................
3.4.29 Subcategory= IDSDM Absent [MessageID prefix =RFLA]..............................................633 3.4.30 Subcategory= FlexAddress SD [MessageID prefix =RFM]............................................. 634 3.4.31 Subcategory= IDSDM Redundancy [MessageID prefix =RRDU]................................... 634 3.4.32 Subcategory= Security Event [MessageID prefix =SEC]................................................635 3.4.33 Subcategory= Sys Event Log [MessageID prefix =SEL].............................
4.1.13 Subcategory= Power Usage [MessageID prefix =POW].................................................701 4.1.14 Subcategory= Power Supply [MessageID prefix =PSU]................................................. 701 4.1.15 Subcategory= Power Usage [MessageID prefix =PWR].................................................703 4.1.16 Subcategory= RAC Event [MessageID prefix =RAC]...................................................... 714 4.1.17 Subcategory= Redundancy [MessageID prefix =RDU]....................
4.3.5 Subcategory= Storage Enclosr [MessageID prefix =ENC]...............................................795 4.3.6 Subcategory= Fan Event [MessageID prefix =FAN]......................................................... 797 4.3.7 Subcategory= Unknown [MessageID prefix =FLDC].......................................................798 4.3.8 Subcategory= Physical Disk [MessageID prefix =PDR]................................................... 801 4.3.9 Subcategory= Power Supply [MessageID prefix =PSU]............
4.4.31 Subcategory= Software Config [MessageID prefix =SWC]........................................... 881 4.4.32 Subcategory= System Info [MessageID prefix =SYS].................................................... 883 4.4.33 Subcategory= Temperature [MessageID prefix =TMP].................................................887 4.4.34 Subcategory= Temperature Statistics [MessageID prefix =TMPS]............................... 893 4.4.35 Subcategory= UEFI Event [MessageID prefix =UEFI]...........................
1.0 Introduction 1 The Test Event Generation Message Reference contains the notification message content generated by the Dell iDRAC8 with Lifecycle Controller using the Test Event Generation feature for the following event action notification types: • Email • SNMP • Remote Syslog The message content is error and event information generated by firmware and other agents that monitor system components.
Example message subsection: 1.1 FSD000 : "Debug authorized by customer; debugcaps: , was authorized by: , at for the period: to .
Trap/EventID The identification number used as the Trap ID for SNMP alert traps and as the Event ID when the message is logged in operating system logs. Severity The classification of the event based on its impact to the platform or system. The severity can be: LCD Message Severity 1 Critical Indicates a catastrophic production problem that might severely impact production systems or components, or systems are down or not functioning.
2.0 Email Event Notification Test Messages 2 2.1 Category: Audit 2.1.1 Subcategory= BIOS Management [MessageID prefix =BIOS] 2.1.1.1 BIOS102 : "A system BIOS update is scheduled that requires a reboot." 2.1.1.2 BIOS103 : "A previously scheduled system BIOS update is canceled." 2.1.2 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 2.1.2.1 CMC8506 : "A command to shut down the CMC was initiated." 2.1.2.
2.1.2.6 CMC8511 : "Unable to synchronize the data in the Extended Storage removable flash media in the primary and secondary CMCs." 2.1.2.7 CMC8512 : "The Extended Storage feature activation timed out. The feature is not active." 2.1.2.8 CMC8513 : "The Extended Storage feature activation on the secondary CMC timed out. The feature is being returned to single CMC mode." 2.1.2.9 CMC8529 : "Unable to perform the requested action on the server-, because of insufficient privileges.
• = "" 2.1.2.17 CMC8542 : "The CMC was restarted because of a manual reset." When event is generated, message will have the following substitutions: • = "" 2.1.2.18 CMC8543 : "The CMC has reset because the thermal threshold was exceeded." When event is generated, message will have the following substitutions: • = "" 2.1.2.19 CMC8545 : "Detected a missing process failover condition detected. Process = .
2.1.2.25 CMC8553 : "An internal error occurred and a failover condition is detected." 2.1.2.26 CMC8554 : "An internal network error occurred." 2.1.2.27 CMC8555 : "An internal memory error has occurred and a failover condition is detected." 2.1.2.28 CMC8557 : "The system health failover is requested. Code ." When event is generated, message will have the following substitutions: • = "" 2.1.2.29 CMC8558 : "The system health is restored." 2.1.2.
• = "" 2.1.2.39 CMC8570 : "The server slot is disabled for DVD drive mapping." When event is generated, message will have the following substitutions: • = "" 2.1.2.40 CMC8571 : "The coin cell battery in the primary CMC is not working." 2.1.2.41 CMC8572 : "The coin cell battery in CMC is not working." When event is generated, message will have the following substitutions: • = "" 2.1.2.42 CMC8573 : "The chassis health is .
• = "admin" 2.1.3.4 DKM0004 : "DKM Error Code : error." When event is generated, message will have the following substitutions: • = "07" • = "Invalid Key format" 2.1.4 Subcategory= Fan Event [MessageID prefix =FAN] 2.1.4.1 FAN8500 : "Enhanced Cooling Mode is Enabled" 2.1.4.2 FAN8501 : "Enhanced Cooling Mode is Disabled" 2.1.4.3 FAN8502 : "The blower is not detected, because it may not be operating optimally.
• = "" 2.1.6 Subcategory= Debug [MessageID prefix =FSD] 2.1.6.1 FSD000 : "Debug authorized by customer; debugcaps: , was authorized by: , at for the period: to ." When event is generated, message will have the following substitutions: • = "DebugCaps" • = "iDRAC User" • = "unblock time" • = "start time" • = " end time" 2.1.6.
2.1.7.2 HWC8001 : "A device was added to the system at this location: . Additional Details: ." When event is generated, message will have the following substitutions: • = "VFlash" • = " NULL" 2.1.7.3 HWC8002 : "The device was removed from the system at this location: . Additional Details: ." When event is generated, message will have the following substitutions: • = "VFlash" • = " NULL" 2.1.7.
• = "USB-NIC" 2.1.10.3 ISM0002 : "The OS to iDRAC Pass-through is disabled. The iDRAC Service Module is currently enabling the OS to iDRAC Pass-through in the USB NIC mode." 2.1.10.4 ISM0003 : "The iDRAC Service Module is unable to discover iDRAC from the operating system of the server." 2.1.10.5 ISM0004 : "The iDRAC Service Module has successfully started communication with iDRAC." 2.1.10.6 ISM0005 : "The iDRAC Service Module has successfully restarted communication with iDRAC." 2.1.10.
2.1.10.16 ISM0015 : "The iDRAC Service Module detected a change in the host name of the server operating system (OS)." 2.1.10.17 ISM0016 : "The BMC watchdog reset time is changed to seconds." When event is generated, message will have the following substitutions: • = "5" 2.1.10.18 ISM0017 : "The BMC watchdog auto-recovery action is changed from to .
2.1.12 Subcategory= Licensing [MessageID prefix =LIC] 2.1.12.1 LIC000 : "The License Manager action succeeded." 2.1.12.2 LIC001 : "The License Manager command parameter used is invalid." 2.1.12.3 LIC002 : "License Manager is unable to allocate the required resources at startup." 2.1.12.4 LIC003 : "License Manager was unable to create and/or allocate the required resources." 2.1.12.5 LIC004 : "An internal system error has occurred." 2.1.12.
operation." 2.1.12.24 LIC201 : "License assigned to device expires in days." When event is generated, message will have the following substitutions: • = "DE00000000825991" • = "iDRAC" • = "5" 2.1.12.25 LIC202 : "A system error was detected during License Manager startup." 2.1.12.26 LIC203 : "The license has encountered an error.
2.1.12.33 LIC210 : "License deleted from device successfully." When event is generated, message will have the following substitutions: • = "DE00000000825991" • = "iDRAC" 2.1.12.34 LIC211 : "The iDRAC feature set has changed." 2.1.12.35 LIC212 : "The CMC features are changed." 2.1.12.36 LIC213 : "A system error was detected during License Manager startup." 2.1.12.37 LIC501 : "A required license is missing or expired." 2.1.12.
2.1.13.6 LOG326 : "The Alert Log was cleared." 2.1.13.7 LOG327 : "An Alert Log backup was created." 2.1.13.8 LOG328 : "The Server Based Management Mode is enabled." 2.1.13.9 LOG329 : "The Server Based Management Mode is disabled." 2.1.14 Subcategory= Memory [MessageID prefix =MEM] 2.1.14.1 MEM8500 : "Low memory condition detected." 2.1.14.2 MEM8501 : "Low memory warning, KB, KB.
• = "" 2.1.17.2 PSU8502 : "The PSU in slot detected 110 VAC input voltage and does not match chassis configuration." When event is generated, message will have the following substitutions: • = "" 2.1.17.3 PSU8503 : "The PSU in slot detected 220 VAC input voltage and does not match chassis configuration." When event is generated, message will have the following substitutions: • = "" 2.1.17.
2.1.17.12 PSU8513 : "Unable to complete the PSU slot firmware update. Error=0x." When event is generated, message will have the following substitutions: • = "" 2.1.17.13 PSU8515 : "Unable to set the Enable Dynamic Power Supply Engagement attribute." 2.1.17.14 PSU8516 : "Unable to set redundancy policy because PSU enumeration is in progress." 2.1.17.15 PSU8517 : "PSU redundancy policy changed." 2.1.17.16 PSU8518 : "Unable to access the PSU FRU data.
2.1.18 Subcategory= Power Usage [MessageID prefix =PWR] 2.1.18.1 PWR2250 : "Unable to turn on the server because the chassis infrastructure not ready." 2.1.18.2 PWR2251 : "Unable to turn on the server because the chassis cover is open." 2.1.18.3 PWR2252 : "Unable to turn on the server because an NDC or Mezzanine card is incompatible with the I/O Module or PCIe subsystem." 2.1.18.4 PWR2253 : "Unable to turn on the server because a PCIe card or Mezzanine card is not installed." 2.1.18.
2.1.18.12 PWR2262 : "The Intel Management Engine has reported an internal system error." 2.1.18.13 PWR2263 : "User ignored Power Supply Oversubscription Warning." 2.1.18.14 PWR2404 : "Power supply capacity alert disabled." 2.1.18.15 PWR8500 : "Chassis power state updated to from ." When event is generated, message will have the following substitutions: • = "" 2.1.18.
2.1.18.23 PWR8509 : "Unable to change the server power priority because Server Based Power Management mode is enabled." 2.1.18.24 PWR8510 : "Unable to set chassis power property .
2.1.18.25 PWR8511 : "Unable to set the CHASSIS_POWER_button_disable chassis power property." 2.1.18.26 PWR8512 : "CMC rebooted, because the power configuration data could not be accessed." 2.1.18.27 PWR8514 : "Unable to perform chassis power action due to insufficient privileges." 2.1.18.28 PWR8515 : "Unable to perform the chassis power action because the chassis is not turned on." 2.1.18.29 PWR8516 : "Unable to perform the chassis power action requested.." 2.1.18.
AC." When event is generated, message will have the following substitutions: • = "" 2.1.18.47 PWR8534 : "Unable to set Server Based Power Management Mode to enable." 2.1.18.48 PWR8535 : "Unable to set Server Based Power Management Mode to disable." 2.1.18.49 PWR8536 : "Server Performance Over Power Redundancy is enabled." 2.1.18.50 PWR8537 : "Server Performance Over Power Redundancy is disabled." 2.1.18.51 PWR8538 : "Power Remote Logging is enabled." 2.1.18.
2.1.18.59 PWR8546 : "Chassis shutdown already in progress." 2.1.18.60 PWR8547 : "Chassis is already powered off." 2.1.18.61 PWR8548 : "Chassis shutdown operation initiated." 2.1.18.62 PWR8549 : "Chassis shutdown did not complete successfully." 2.1.18.63 PWR8550 : "Chassis shutdown completed." 2.1.18.64 PWR8551 : "Successfully set Virtual Infrastructure Device power to DC Watt." When event is generated, message will have the following substitutions: • = "" 2.1.18.
• = "" 2.1.18.71 PWR8561 : "Unable to power on server because of iDRAC communication issue." When event is generated, message will have the following substitutions: • = "" 2.1.18.72 PWR8562 : "Unable to power on the server before power on timer expired." When event is generated, message will have the following substitutions: • = "" 2.1.18.
2.1.18.79 PWR8569 : "Unable to power cycle the server because the server is off." When event is generated, message will have the following substitutions: • = "" 2.1.18.80 PWR8570 : "Unable to communicate to the iDRAC, when trying to power cycle the server ." When event is generated, message will have the following substitutions: • = "" 2.1.18.
• = "" 2.1.18.88 PWR8578 : "Chassis Management Controller is unable to turn on the iDRAC on server- because power required is less than available power." When event is generated, message will have the following substitutions: • = "" 2.1.18.89 PWR8579 : "Request to reset the CMC is initiated." When event is generated, message will have the following substitutions: • = "" 2.1.18.
2.1.18.96 PWR8586 : "Chassis Management Controller is unable to turn on server- because it is not supported in the VRTX chassis." When event is generated, message will have the following substitutions: • = "" 2.1.18.97 PWR8587 : "Chassis Management Controller is unable to turn on server- because the chassis enclosure is open." When event is generated, message will have the following substitutions: • = "" 2.1.18.
• = "" 2.1.18.106 PWR8596 : "Chassis Management Controller is unable to turn on server- because PSU redundancy is lost and the available power is insufficient." When event is generated, message will have the following substitutions: • = "" 2.1.18.107 PWR8597 : "The Power Supply Unit (PSU) is turned off because it is not supported by the Chassis." When event is generated, message will have the following substitutions: • = "" 2.1.18.
2.1.18.113 PWR8666 : "iKVM power cycle initiated." 2.1.18.114 PWR8667 : "Resetting iKVM to default settings." 2.1.18.115 PWR8668 : "iKVM reset initiated." 2.1.18.116 PWR8669 : "Unable to turn on the server because of an inconsistency between the chassis components and mezzanine card." When event is generated, message will have the following substitutions: • = "" 2.1.18.
2.1.19 Subcategory= RAC Event [MessageID prefix =RAC] 2.1.19.1 RAC0100 : "The Smart Card is removed. Further communication is not possible." 2.1.19.2 RAC0101 : "The inserted Smart Card is not valid or the Smart Card reader is not supported." 2.1.19.3 RAC0102 : "The Smart Card Logon plug-in is not installed. Install the plug-in from the iDRAC Web GUI to log in using Smart Card." 2.1.19.4 RAC0103 : "This browser does not support Smart Card logon on iDRAC. Use Internet Explorer version 7.
partition." 2.1.19.30 RAC0138 : "A valid certificate is not loaded." 2.1.19.31 RAC0140 : "Firmware update has failed." 2.1.19.32 RAC0141 : "Firmware update verification failed: The update status is unknown." 2.1.19.33 RAC0142 : "File is not valid for iDRAC firmware update." 2.1.19.34 RAC0146 : "Firmware rollback has failed." 2.1.19.35 RAC0147 : "Rollback firmware is not available." 2.1.19.36 RAC0148 : "Unable to retrieve the batteries information. The system is powered off." 2.1.19.
characters." 2.1.19.65 RAC0222 : "The Destination E-mail Address is invalid." 2.1.19.66 RAC0223 : "Enter an alphanumeric value or a valid symbol for the following (see the online help for more information):" 2.1.19.67 RAC0224 : "Invalid e-mail description." 2.1.19.68 RAC0225 : "Sending the test mail failed." 2.1.19.69 RAC0226 : "Send Failed: Request processing failed." 2.1.19.70 RAC0227 : "SD card is not detected: Insert an SD Card of size greater than 256MB." 2.1.19.
2.1.19.81 RAC0242 : "The selected partition does not exist." 2.1.19.82 RAC0243 : "Partition failed: A partitioning conflict has occurred with another session." 2.1.19.83 RAC0244 : "The partition label must be unique." 2.1.19.84 RAC0245 : "The partition is in-use by another process." 2.1.19.85 RAC0246 : "Partition is read-only." 2.1.19.86 RAC0247 : "The partition is currently attached." 2.1.19.87 RAC0248 : "This operation deletes the partition permanently. Do you want to continue?" 2.1.19.
remotely through Web GUI, Remote Racadm, Ssh, and Telnet. Local Racadm and serial interface will continue to work." 2.1.19.110 RAC0273 : "iDRAC access will be limited to running the Racadm utility on the local server or using the serial interface." 2.1.19.111 RAC0274 : "See the iDRAC user documentation for more information on using the Racadm utility or the serial interface." 2.1.19.112 RAC0275 : "Click OK to disable the NIC. Click Cancel to keep the setting unchanged." 2.1.19.
Authority (CA) certificate must be uploaded. The CA certificate is used to verify the directory server SSL certificate." 2.1.19.130 RAC0294 : "The Character Accumulate Interval value is invalid. Expected range: 1-255." 2.1.19.131 RAC0295 : "The Character Send Threshold value is invalid. Expected range: 1-255." 2.1.19.132 RAC0297 : "Specify a Domain Controller Address must be configured." 2.1.19.133 RAC0298 : "Root Domain Name must be configured." 2.1.19.
2.1.19.144 RAC0701 : "Requested system powerup." 2.1.19.145 RAC0702 : "Requested system powercycle." 2.1.19.146 RAC0703 : "Requested system hardreset." 2.1.19.147 RAC0704 : "Requested system powerdown." 2.1.19.148 RAC0705 : "Requested system graceful shutdown." 2.1.19.149 RAC0706 : "Requested system NMI." 2.1.19.150 RAC0708 : "Previous reboot was due to a firmware watchdog timeout." 2.1.19.151 RAC0709 : "Unknown server inserted into chassis." 2.1.19.152 RAC0710 : "Server link tuning error." 2.1.19.
2.1.19.164 RAC0722 : "Failed to program the Chassis assigned MAC address for the NIC.Integrated.." When event is generated, message will have the following substitutions: • = "1" 2.1.19.165 RAC0723 : "The firmware version of the Chassis Management Controller is earlier than the required version ." When event is generated, message will have the following substitutions: • = "3.0" • = "4.0" 2.1.19.
2.1.20.6 RDU8508 : "CMC: cannot failover since the other CMC is nonfunctional." When event is generated, message will have the following substitutions: • = "" 2.1.20.7 RDU8509 : "CMC: cannot failover, chassis is in non-redundant state" When event is generated, message will have the following substitutions: • = "" 2.1.20.
• = "" 2.1.20.15 RDU8517 : "CMC: no action allowed while firmware update is in progress" When event is generated, message will have the following substitutions: • = "" 2.1.20.16 RDU8518 : "CMC: active CMC requests Standby CMC to go active state." When event is generated, message will have the following substitutions: • = "" 2.1.20.17 RDU8519 : "Unable to communicate with peer CMC .
2.1.21 Subcategory= Software Config [MessageID prefix =SWC] 2.1.21.1 SWC1916 : "Network Time Protocol server configuration has changed." 2.1.21.2 SWC1920 : "The Chassis Management at Server Mode is enabled." 2.1.21.3 SWC1921 : "The Chassis Management at Server Mode is disabled." 2.1.21.4 SWC1923 : "Unable to modify the server configuration by using Quick Sync because invalid credentials are entered." 2.1.21.5 SWC1924 : "Unable to modify the server configuration by using Quick Sync." 2.1.21.
• = "" 2.1.21.14 SWC8508 : "Unable to capture Profile from server in slot " When event is generated, message will have the following substitutions: • = "" 2.1.21.15 SWC8509 : "Unable to apply Profile to server in slot " When event is generated, message will have the following substitutions: • = "" 2.1.21.
• = "" 2.1.21.24 SWC8518 : "Unable to modify password of User : -" When event is generated, message will have the following substitutions: • = "" 2.1.21.25 SWC8519 : "Successfully modified user name from to ." When event is generated, message will have the following substitutions: • = "" 2.1.21.
2.1.21.32 SWC8526 : "Unable to delete Chassis Group member ()" When event is generated, message will have the following substitutions: • = "" 2.1.21.33 SWC8527 : "Chassis Management Controller is unable to update the iDRAC user name to "root"." 2.1.21.34 SWC8528 : "Chassis Management Controller is unable to update the iDRAC root password." 2.1.21.35 SWC8529 : "Chassis Management Controller unable to enable the iDRAC root user." 2.1.21.
2.1.21.44 SWC8538 : "Unable to delete key for slot of service account, due to problem saving key file." When event is generated, message will have the following substitutions: • = "" 2.1.21.45 SWC8539 : "The key delete operation successfully completed for slot of service account." When event is generated, message will have the following substitutions: • = "" 2.1.21.
• = "" 2.1.21.53 SWC8604 : "Quick Deploy Profile: Server does not support configuration using profiles." When event is generated, message will have the following substitutions: • = "" 2.1.21.54 SWC8605 : "Quick Deploy Profile: Server generation information is not recognized." When event is generated, message will have the following substitutions: • = "" 2.1.21.
• = "" 2.1.21.61 SWC8612 : "Unable to fully extract boot device information from profile: ." When event is generated, message will have the following substitutions: • = "" 2.1.21.62 SWC8613 : "Unable to fully extract boot list settings from the profile." When event is generated, message will have the following substitutions: • = "" 2.1.21.63 SWC8614 : "Legacy profile setting: is not recognized.
• = "" 61
2.1.22.2 SWU8557 : "Invalid firmware: The uploaded firmware image does not contain a verification signature." 2.1.22.3 SWU8558 : "Invalid firmware: The uploaded firmware image validation was unsuccessful." 2.1.22.4 SWU8559 : "The firmware downgrade operation is unsuccessful. A downgrade to the firmware version uploaded is not supported." 2.1.22.5 SWU8560 : "The firmware update process of Active CMC and Standby CMC was not successful because of a unrecognized image error." 2.1.
" When event is generated, message will have the following substitutions: • = "" 2.1.24 Subcategory= Temperature [MessageID prefix =TMP] 2.1.24.1 TMP8500 : "I/O Module temperature exceeded operating range." When event is generated, message will have the following substitutions: • = "" 2.1.24.2 TMP8501 : "Unable to read planar board temperature sensors. The cooling has been increased to safeguard the system." 2.1.24.
2.1.25.4 USR0008 : "The Default Login Warning feature is disabled." 2.1.25.5 USR0013 : "Insufficient user privileges to perform operation." 2.1.25.6 USR0014 : "The current user session is invalid." 2.1.25.7 USR0015 : "The specified user does not exist." 2.1.25.8 USR0016 : "Unable to get session info from the RAC." 2.1.25.9 USR0017 : "No active sessions currently exist for the specified user." 2.1.25.10 USR0018 : "No active sessions currently exist." 2.1.25.11 USR0019 : "Specified user name is too long." 2.
• = "GUI" 2.1.25.19 USR0033 : "Login for from using was incomplete." When event is generated, message will have the following substitutions: • = "root" • = "192.168.1.1" • = "GUI" 2.1.25.20 USR0034 : "Login attempt alert for from using , IP will be blocked for seconds.
2.1.25.25 USR0152 : "Unable to connect the remote VNC session, beacause an incorrect VNC password was entered from the IP ." When event is generated, message will have the following substitutions: • = "192.168.1.1" 2.1.25.26 USR0153 : "Logging off the remote VNC session from the IP address , because the session timed out." When event is generated, message will have the following substitutions: • = "192.168.1.1" 2.1.25.
2.1.25.30 USR0173 : "The Front Panel USB port switched automatically from iDRAC to operating system." 2.1.25.31 USR0174 : "The Front Panel USB device is removed from the operating system." 2.1.25.32 USR0175 : "The Front Panel USB Port Over Current is detected for the attached device on Disk.USBFront.." When event is generated, message will have the following substitutions: • = "Port" 2.1.25.
• = "" 2.1.25.43 USR8502 : "Successfully closed Session: pid= sid=" When event is generated, message will have the following substitutions: • = "" 2.1.25.44 USR8503 : "Domain user authentication was not successful. Reason code = " When event is generated, message will have the following substitutions: • = "" 2.1.25.45 USR8504 : "The IP address specified is out of range." 2.1.25.
2.1.25.52 USR8511 : "Login was successful from (username=, type=, sid=)" When event is generated, message will have the following substitutions: • = "" 2.1.25.53 USR8512 : " login was not successful (username=, reason=)" When event is generated, message will have the following substitutions: • = "" 2.1.25.
2.2.1 Subcategory= Backup/Restore [MessageID prefix =BAR] 2.2.1.1 BAR001 : "Export System Profile requested." 2.2.1.2 BAR002 : "Validating vFlash Backup partition." 2.2.1.3 BAR003 : "Preparing vFlash Backup partition." 2.2.1.4 BAR004 : "Collecting Hardware Inventory information." 2.2.1.5 BAR005 : "Collecting Lifecycle Controller data." 2.2.1.6 BAR006 : "Finalizing Backup file." 2.2.1.7 BAR007 : "Export System Profile completed." 2.2.1.8 BAR008 : "Invalid Backup file passphrase provided." 2.2.1.
Host System." 2.2.1.29 BAR029 : "Restoring Integrated Remote Access Controller firmware." 2.2.1.30 BAR030 : "Import System Profile Complete, restarting Integrated Remote Access Controller." 2.2.1.31 BAR031 : "RESERVED" 2.2.1.32 BAR032 : "Invalid system profile Backup file." 2.2.1.33 BAR033 : "Unable to Restore Lifecycle Controller data." 2.2.1.34 BAR034 : "Unable to Restore Integrated Remote Access Controller firmware." 2.2.1.35 BAR035 : "Unable to Restore Integrated Remote Access Controller configuration.
• = "PERC H310 Mini" 2.2.1.51 BAR051 : "Performing Component Configuration Restore for Device : " When event is generated, message will have the following substitutions: • = "NIC.Slot.1-1-1" 2.2.1.52 BAR052 : "Firmware update cannot be performed for Device: " When event is generated, message will have the following substitutions: • = "PERC H310 Mini" 2.2.1.
2.2.1.58 BAR058 : "Validating NFS destination access." 2.2.1.59 BAR059 : "Validating CIFS destination access." 2.2.1.60 BAR060 : "Collecting firmware inventory information." 2.2.1.61 BAR061 : "Collecting System Information." 2.2.1.62 BAR062 : "Collecting Lifecycle Controller Configuration database." 2.2.1.63 BAR063 : "Collecting Lifecycle Controller Firmware images." 2.2.1.64 BAR064 : "Collecting Integrated Remote Access Controller firmware." 2.2.1.
information." 2.2.1.84 BAR084 : "Host System Service Tag does not match the Backup file Service Tag." 2.2.1.85 BAR085 : "Unable to collect System Information for Import Backup file validation." 2.2.1.86 BAR086 : "Unable to Restore The Lifecycle Controller Configuration database." 2.2.1.87 BAR087 : "Unable to Restore the Lifecycle Controller Firmware images." 2.2.1.88 BAR088 : "No partitions available on vFlash media." 2.2.1.89 BAR089 : "Lifecycle Controller needs to be updated." 2.2.1.
processing." 2.2.1.111 BAR111 : "Server Profile operation timed out." 2.2.1.112 BAR112 : "The system identifier in the Server Profile file does not match the target system." 2.2.1.113 BAR113 : "Unable to create an Automatic Backup job." 2.2.1.114 BAR114 : "An Automatic Backup job is created." When event is generated, message will have the following substitutions: • = "JobID" 2.2.1.115 BAR115 : "The number of Automatic Server Profile backup files has reached the specified limit.
2.2.2.5 BIOS005 : "Mismatch in AttributeName and AttributeValue count" 2.2.2.6 BIOS006 : "Configuration job already created, cannot set attribute on specified target until existing job is completed or is cancelled" 2.2.2.7 BIOS007 : "Configuration job already created, cannot create another configuration job on specified target until existing job is completed or is cancelled" 2.2.2.8 BIOS008 : "No pending data present to create a Configuration job" 2.2.2.9 BIOS009 : "Lifecycle Controller is currently in use.
2.2.2.17 BIOS017 : "Unable to delete vFlash pending one-time boot configuration" 2.2.2.18 BIOS018 : "Invalid BIOS Password." 2.2.2.19 BIOS021 : "Cannot authenticate BIOS password." 2.2.2.20 BIOS022 : "Cannot set the BIOS password. Password is disabled due to a jumper setting on the motherboard." 2.2.2.21 BIOS023 : "Cannot perform the operation due to an unknown error in iDRAC." 2.2.2.22 BIOS024 : "The set operation did not complete successfully as the attribute is readonly." 2.2.2.
2.2.2.26 BIOS028 : "Unable to change the BIOS password using plain text because the password is currently being configured using a hash." 2.2.2.27 BIOS029 : "Unable to change the BIOS password because an Export Server Profile operation is already running." 2.2.2.28 BIOS030 : "Unable to change the BIOS password because an Import Server Profile operation is already running." 2.2.2.29 BIOS101 : "Unable to read or change any of the system BIOS configuration settings." 2.2.
• = "" 2.2.4 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 2.2.4.1 CMC001 : "The command was successful." 2.2.4.2 CMC002 : "General failure." 2.2.4.3 CMC003 : "Missing required parameter ." When event is generated, message will have the following substitutions: • = "parameter" 2.2.4.4 CMC004 : "Invalid parameter value for .
2.2.5 Subcategory= Cert Mgmt [MessageID prefix =DH] 2.2.5.1 DH001 : "Resource needed to perform the operation is unavailable." 2.2.5.2 DH002 : "Internal I/O failure" 2.2.5.3 DH003 : "Service tag could not be read" 2.2.5.4 DH004 : "iDRAC does not have sufficient free resources to generate keys" 2.2.5.5 DH005 : "CA Cert is corrupted, expired, or does not have signing privileges." 2.2.5.6 DH006 : "Not the right passphrase for the private key (need to re-write)." 2.2.5.
• = "Unknown" • = "Unknown" 2.2.6.9 DIS009 : "Notification of iDRAC IP address changed to sent to Provisioning Server." When event is generated, message will have the following substitutions: • = "Unknown" 2.2.6.
2.2.6.11 DIS011 : "Auto Discovery client using customer signed client certificate." 2.2.6.12 DIS012 : "Auto Discovery client using factory signed client certificate." 2.2.6.13 DIS013 : "Auto Discovery client using default client certificate." 2.2.6.14 DIS014 : "Auto Discovery client using customer provided CA certificate to authenticate Provisioning Server." 2.2.6.15 DIS015 : "Auto Discovery client using default CA certificate to authenticate Provisioning Server." 2.2.6.
not available." 2.2.7.4 FAN903 : "Cannot enable the Enhanced Cooling Mode because an unsupported fan is inserted in the Chassis." 2.2.7.5 FAN904 : "Cannot enable the Enhanced Cooling Mode because the Maximum Power Conservation Mode is enabled." 2.2.7.6 FAN905 : "Applying fan configuration settings. This may take several seconds." 2.2.7.7 FAN906 : "Changes are not made to the current settings." 2.2.7.8 FAN907 : "The Enhanced Cooling Mode feature is already enabled." 2.2.7.
2.2.8.5 FC005 : "The number of AttributeName array elements does not match the AttributeValue array element count." 2.2.8.6 FC006 : "Configuration job already created, cannot set attribute on specified target until existing job is completed or is cancelled." 2.2.8.7 FC007 : "A configuration job already exists. Unable to create another configuration job on specified target until existing job is completed or is cancelled." 2.2.8.8 FC008 : "No pending data present to create a Configuration job." 2.2.8.
2.2.8.17 FC017 : "Unable to perform the operation due to an internal error in iDRAC." 2.2.9 Subcategory= Hardware Config [MessageID prefix =HWC] 2.2.9.1 HWC0001 : "Unable to complete the operation as there is no response from iDRAC." 2.2.9.2 HWC0002 : "Unable to detect vFlash SD card." 2.2.9.3 HWC0003 : "Successfully initialized vFlash SD card." 2.2.9.4 HWC0004 : "Unable to initialize vFlash SD card." 2.2.9.5 HWC0005 : "Internal error while retrieving update information." 2.2.9.
2.2.10.4 IOID004 : "Virtual Address Persistence Policy setting for Non-Auxiliary powered devices is changed to ." When event is generated, message will have the following substitutions: • = "AC Cycle and Cold Boot and Warm Boot" 2.2.10.5 IOID005 : "Storage Initiator Persistence Policy setting is changed to ." When event is generated, message will have the following substitutions: • = "AC Cycle and Cold Boot and Warm Boot" 2.2.10.
• = " 1" 2.2.10.12 IOID115 : "Unable to configure the target settings properties of the NIC Port .
2.2.10.13 IOID116 : "Applying I/O Identity settings based on current persistence policy settings." 2.2.10.14 IOID117 : "The operation to apply I/O Identity settings based on current persistence policy settings has completed successfully." 2.2.10.15 IOID118 : "Unable to configure some or all I/O Identity settings based on current persistence policy settings." 2.2.10.16 IOID119 : "FlexAddress is enabled on all NIC and FC HBA devices." 2.2.11 Subcategory= IO Virtualization [MessageID prefix =IOV] 2.2.11.
• = "" 2.2.11.16 IOV102 : "A PCIe adapter is removed from ." When event is generated, message will have the following substitutions: • = "" 2.2.11.17 IOV103 : "A PCIe adapter in is replaced by PCIe adapter ." When event is generated, message will have the following substitutions: • = "" 2.2.11.
2.2.11.25 IOV123 : "<"PCIE Slot" or "PERC VA"> is unassigned/ unmapped from extended server slot ." When event is generated, message will have the following substitutions: • <"PCIE Slot" or "PERC VA"> = "" 2.2.11.26 IOV1001 : "The requested operation was successfully executed." 2.2.11.27 IOV1002 : "The operation was not successful." 2.2.11.28 IOV1003 : "Missing required parameter .
• = "" 2.2.12 Subcategory= DRAC IP Address [MessageID prefix =IPA] 2.2.12.1 IPA0100 : "The iDRAC IP Address changed from to ." When event is generated, message will have the following substitutions: • = "192.168.1.100" • = "192.168.2.100" 2.2.13 Subcategory= Job Control [MessageID prefix =JCP] 2.2.13.1 JCP001 : "Task successfully scheduled." 2.2.13.2 JCP002 : "Unable to schedule the job." 2.2.13.3 JCP003 : "Job failed.
2.2.13.14 JCP014 : "Maximum jobs per queue exceeded." 2.2.13.15 JCP015 : "A running job cannot be deleted." 2.2.13.16 JCP016 : "Invalid UntilTime value. A minimum of 12 minutes is required." 2.2.13.17 JCP017 : "Job creation request unsuccessful. Maximum number of jobs reached." 2.2.13.18 JCP018 : "Cannot create new jobs until the existing Export job is completed or the job is cancelled." 2.2.13.19 JCP019 : "Cannot create new jobs until the existing Import System Profile job is completed or cancelled." 2.2.
2.2.13.25 JCP024 : "Lifecycle Controller is in use. This job starts when Lifecycle Controller is available." 2.2.13.26 JCP025 : "Lifecycle Controller is not enabled." 2.2.13.27 JCP026 : "Update packages are being downloaded. This job resumes when the downloads are completed." 2.2.13.28 JCP027 : "Job created successfully." 2.2.13.29 JCP028 : "Job status updated." 2.2.13.30 JCP030 : "Unable to schedule jobs while an iDRAC firmware update or configuration job is running." 2.2.13.
• = "parameter" 2.2.14.17 LC017 : "Invalid value for the parameter, .
2.2.14.18 LC018 : "Server certificate successfully modified. iDRAC will now restart and be unavailable during restart." 2.2.14.19 LC019 : "Base64 decode of PKCS12 content was not successful." 2.2.14.20 LC020 : "PKCS12 decrypt of the certificate could not complete." 2.2.14.21 LC021 : "PKCS12 decrypt of private key could not complete." 2.2.14.22 LC022 : "Lifecycle Controller Log Export was successful." 2.2.14.23 LC023 : "Cannot access network share." 2.2.14.
running." 2.2.14.44 LC045 : "An instance of CreateConfigJob is already running." 2.2.14.45 LC046 : "An instance of DownloadServerPublicKey is already running." 2.2.14.46 LC047 : "An instance of DownloadClientCerts is already running." 2.2.14.47 LC048 : "Invalid input value for IPChangeNotifyPS." 2.2.14.48 LC049 : "Invalid value for VirtualAddressManagement." 2.2.14.49 LC050 : "Invalid value for SystemServicesState." 2.2.14.50 LC051 : "Cannot create multiple Server Profile Export jobs." 2.2.14.
2.2.14.59 LC060 : "Lifecycle controller is currently not ready to take provisioning requests" 2.2.14.60 LC061 : "Lifecycle controller is ready to take provisioning requests" 2.2.14.61 LC062 : "Export or Import server profile operation is already running." 2.2.14.62 LC063 : "Cannot create new jobs until the existing running jobs are completed or deleted." 2.2.14.63 LC064 : "The value exceeds the maximum length of characters for .
2.2.14.65 LC066 : "The Export Certificate operation is currently running." 2.2.14.66 LC067 : "Successfully exported SSL Certificate." 2.2.14.67 LC068 : "Unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress." 2.2.14.68 LC069 : "Certificate does not exist." 2.2.14.69 LC070 : "Unable to find the configuration XML import file." 2.2.14.
• = "parameters" 2.2.15.5 LIC904 : "Could not connect to network share." 2.2.15.6 LIC905 : "The LicenseName value cannot exceed 64 characters." 2.2.15.7 LIC906 : "License file is not accessible on the network share." 2.2.15.8 LIC907 : "Unable to perform the operation due to an unknown error in iDRAC." 2.2.16 Subcategory= Log event [MessageID prefix =LOG] 2.2.16.1 LOG001 : "Missing required InstanceID or JobID parameter." 2.2.16.2 LOG002 : "Invalid parameter value for InstanceID." 2.2.16.
2.2.16.16 LOG504 : "Chassis Log Export was successful." 2.2.16.17 LOG505 : "Cannot access network share." 2.2.16.18 LOG506 : "An instance of ExportChassisLog is already running." 2.2.16.19 LOG507 : "Resource allocation failure." 2.2.16.20 LOG508 : "Unable to write to the network share." 2.2.16.21 LOG509 : "The value exceeds the maximum length of characters for .
2.2.17.5 NIC005 : "Mismatch in AttributeName and AttributeValue count" 2.2.17.6 NIC006 : "A configuration job already exists, Cannot set attribute on specified target until existing job is completed or is cancelled" 2.2.17.7 NIC007 : "A configuration job already exists, Cannot create another configuration job on specified target until existing job is completed or is cancelled" 2.2.17.8 NIC008 : "No pending data present to create a Configuration job" 2.2.17.
2.2.17.17 NIC017 : "Unable to delete vFlash pending one-time boot configuration" 2.2.17.18 NIC018 : "Invalid BIOS password." 2.2.17.19 NIC021 : "Cannot authenticate specified BIOS password." 2.2.17.20 NIC022 : "Unable to set the BIOS password because of a jumper setting on the motherboard." 2.2.17.21 NIC023 : "Cannot perform the operation due to an unknown error in iDRAC." 2.2.17.22 NIC024 : "The set operation did not complete successfully as the attribute is readonly." 2.2.
system." 2.2.18.21 OSD21 : "Unable to boot to ISO image." 2.2.18.22 OSD22 : "Unable to detach ISO image from the host." 2.2.18.23 OSD23 : "Unable to continue with DetachISOImage - another command is in the process of exposing the ISO Image and booting to it." 2.2.18.24 OSD24 : "Unable to continue with DetachDrivers - UnPackAndAttach is in progress." 2.2.18.25 OSD25 : "Unable to detach USB device containing operating system drivers." 2.2.18.
and is in progress." 2.2.18.63 OSD063 : "The process of installing an operating system or hypervisor is successfully completed." 2.2.18.64 OSD064 : "The process of installing an operating system or hypervisor is abruptly stopped either by the user or the installation infrastructure." 2.2.18.65 OSD065 : "Operating System/Hypervisor Installation did not complete successfully." 2.2.19 Subcategory= PCI Device [MessageID prefix =PCI] 2.2.19.
• = "device name" 2.2.20.5 PR5 : "The configuration values stored for the previous device could not be applied to device: " When event is generated, message will have the following substitutions: • = "device name" 2.2.20.6 PR6 : "Configuration changes successfully applied to device: " When event is generated, message will have the following substitutions: • = "device name" 2.2.20.
2.2.20.16 PR16 : "Some of the configuration values could not be applied to device: " When event is generated, message will have the following substitutions: • = "device name" 2.2.20.17 PR17 : "Some of the configuration values stored for the previous device could not be applied to device: " When event is generated, message will have the following substitutions: • = "device name" 2.2.20.
• = "JID_432156780987" 2.2.20.35 PR35 : "Power Supply slot firmware update will be performed during next system reboot." When event is generated, message will have the following substitutions: • = "1" 2.2.20.36 PR36 : "Version change detected for firmware.
2.2.22.5 RAC005 : "Mismatch in AttributeName and AttributeValue count." 2.2.22.6 RAC006 : "AttributeValue cannot be changed for ReadOnly Attribute Name" 2.2.22.7 RAC007 : "Input out of Range" 2.2.22.8 RAC008 : "Invalid boolean Value" 2.2.22.9 RAC009 : "String exceeds maximum length." 2.2.22.10 RAC010 : "Invalid character value." 2.2.22.11 RAC011 : "Job already exists, cannot process more set operations." 2.2.22.12 RAC012 : "User is not authorized to perform this operation." 2.2.22.13 RAC013 : "Invalid FQDD.
2.2.22.16 RAC016 : "Invalid AttributeName." 2.2.22.17 RAC017 : "Job created to apply the attribute value." 2.2.22.18 RAC018 : "Job completed with Errors." 2.2.22.19 RAC019 : "Job did not complete successfully." 2.2.22.20 RAC020 : "Completed" 2.2.22.21 RAC021 : "Unable to set static values for IPAddress Net mask or Gateway because DHCP is Enabled." 2.2.22.22 RAC022 : "Unable to set values for User Password, IPMILan, IPMISerial or User Admin Privilege because the User Name is not configured." 2.2.22.
• = "parameter" 2.2.22.40 RAC040 : "Missing parameters ." When event is generated, message will have the following substitutions: • = "parameters" 2.2.22.41 RAC041 : "The set operation on the event filters failed." 2.2.22.42 RAC042 : "Invalid number of input parameters." 2.2.22.43 RAC043 : "Unable to update some event filter settings." 2.2.22.44 RAC044 : "Unable to update some event filter settings." 2.2.22.
2.2.22.57 RAC057 : "Unable to set Privacy Protocol to an enabled state because the Authentication Protocol attribute is set to None for the user ID: " When event is generated, message will have the following substitutions: • = "user ID" 2.2.22.58 RAC058 : "AttributeValue is not unique for AttributeName ." When event is generated, message will have the following substitutions: • = "attribute name" 2.2.22.
2.2.22.64 RAC064 : "iDRAC was successfully reset." 2.2.22.65 RAC065 : "iDRAC reset operation was not successful." 2.2.22.66 RAC066 : "iDRAC is successfully reset to factory-default properties." 2.2.22.67 RAC067 : "iDRAC reset to factory defaults operation was not successful." 2.2.22.68 RAC068 : "SHA256Password and Plain Password cannot be imported together." 2.2.22.69 RAC069 : "String Less than Min Supported Length" 2.2.22.
job queue." When event is generated, message will have the following substitutions: • = "123456789" 2.2.22.85 RAC0610 : "The passphrase and confirm passphrase values entered do not match." 2.2.22.86 RAC0612 : "Cancelling the firmware update operation will delete all the uploaded firmware files. Do you want to continue?" 2.2.22.87 RAC0613 : "The uploaded file is invalid." 2.2.22.88 RAC0614 : "Incorrect password for PKCS#12 file." 2.2.22.89 RAC0615 : "Invalid PKCS#12 file." 2.2.22.
2.2.22.101 RAC0661 : "Storage configuration operation - #(operation) is pending on the selected #{devicetype} : #{devicename}." 2.2.22.102 RAC0901 : "Invalid syntax. The -t option value must set to 1." 2.2.22.103 RAC0902 : "The -f option requires -d to also be specifed." 2.2.22.104 RAC0903 : "The -d option cannot be used with any other options." 2.2.22.105 RAC0904 : "The remote file location is not accessible or reachable." 2.2.22.106 RAC0905 : "Failed to get the USC version details." 2.2.22.
invoked by the ." When event is generated, message will have the following substitutions: • = "root" 2.2.22.133 RAC938 : "Successfully initiated configuration XML file export operation invoked by the .
2.2.22.134 RAC939 : "Unable to start the system configuration profile export or import operation." 2.2.22.135 RAC940 : "Unable to start the system configuration profile export or import operation." 2.2.22.136 RAC941 : "Successfully initiated the export operation. This operation may take several minutes to complete." 2.2.22.137 RAC942 : "Successfully initiated the import operation.
in recovery state," 2.2.22.158 RAC963 : "Unable to retrieve the status of Lifecycle Controller." 2.2.22.159 RAC964 : "Unable to perform the operation." 2.2.22.160 RAC965 : "The -l option must be specified if -u and -p are used." 2.2.22.161 RAC966 : "Unable to continue with the opearion because the user name or password is not specified." 2.2.22.162 RAC967 : "Exporting the configuration XML file to a local share is not supported when using Firmware RACADM." 2.2.22.
(PKCS12) file." 2.2.22.179 RAC985 : "Unable to configure the cfgServerBootOnce object." 2.2.22.180 RAC986 : "The "vmkey" sub-command is deprecated." 2.2.22.181 RAC987 : "Firmware update job for is initiated." When event is generated, message will have the following substitutions: • = "firmimg.d7" 2.2.22.182 RAC988 : "Unable to initiate the firmware update." When event is generated, message will have the following substitutions: • = "firmimg.d7" 2.2.22.
2.2.22.188 RAC994 : "Unable to run the "jobqueue delete --all" command." 2.2.22.189 RAC995 : "Unable to retrieve the hardware inventory." 2.2.22.190 RAC996 : "Unable to set the object value because the DNS RAC Name object is not configured." 2.2.22.191 RAC997 : "The object DNSDomainFromDHCP cannot be enabled." 2.2.22.192 RAC998 : "IPv6 cannot be enabled." 2.2.22.193 RAC999 : "The object DNSFromDHCP6 cannot be enabled." 2.2.22.194 RAC1000 : "Unable to set the object value for iDRAC IPv6 address or gateway.
2.2.22.202 RAC1008 : "The Active Directory object DCLookupByUserDomain cannot be disabled." 2.2.22.203 RAC1009 : "The Active Directory objects DCLookupEnable or GCLookupEnable cannot be enabled." 2.2.22.204 RAC1010 : "Unable to set the power cap value." 2.2.22.205 RAC1011 : "The OS to iDRAC pass-through cannot be enabled." 2.2.22.206 RAC1012 : "Unable to change the auto-negotiation state for the current NIC selection mode." 2.2.22.
• = "123456789" 2.2.22.225 RAC1033 : "Unable to retrieve the server component software inventory." 2.2.22.226 RAC1035 : "There are no pending values to be cleared." 2.2.22.227 RAC1036 : "Successfully cleared pending attribute(s) for the group specified." 2.2.22.228 RAC1037 : "Unable to clear pending attribute(s)." 2.2.22.229 RAC1038 : "Unable to clear pending values for the specified component." 2.2.22.230 RAC1039 : "The subcommand entered is not supported on the specified server." 2.2.22.
2.2.22.235 RAC1044 : "The Automatic Update (autoupdate) feature is not enabled." 2.2.22.236 RAC1045 : "Specifying ftp.dell.com as the catalog source for the Automatic Update feaure may result in frequent system firmware updates because the catalog on ftp.dell.com changes often." 2.2.22.237 RAC1046 : "Unable to view the Automatic Update (autoupdate) feature settings because the feature has not been configured." 2.2.22.238 RAC1047 : "Successfully cleared the Automatic Update (autoupdate) feature settings." 2.
2.2.22.243 RAC1052 : "The Automatic Backup (autobackup) feature is not enabled." 2.2.22.244 RAC1053 : "Unable to view the Automatic Backup (autobackup) feature settings because the feature has not been configured." 2.2.22.245 RAC1054 : "Successfully cleared the Automatic Backup (autobackup) feature settings." 2.2.22.246 RAC1055 : "Unable to clear the Automatic Backup (autobackup) feature settings because there is currently no configuration." 2.2.22.247 RAC1056 : "Rollback operation initiated successfully.
2.2.22.258 RAC1068 : "Unable to set minimum non critical threshold value of , because the value entered is greater than, or equal to the maximum non critical threshold value." When event is generated, message will have the following substitutions: • = "InletTemp" 2.2.22.259 RAC1069 : "Unable to set minimum non critical threshold value of , because the value entered is greater than, or equal to the maximum critical threshold value.
2.2.22.264 RAC1109 : "Unable to run the command, because an incorrect Share type is entered." 2.2.22.265 RAC1110 : "Unable to run the command, because an incorrect Proxy port number was entered." 2.2.22.266 RAC1111 : "Unable to delete the pending values or operations of the specified device." 2.2.22.267 RAC1112 : "Unable to delete the pending values for the specified device because the iDRAC internal storage is in use by a currently running job." 2.2.22.
2.2.22.270 RAC1115 : "Unable to run the command, because of insufficient user privileges." 2.2.22.271 RAC1116 : "Unable to run the command, because the restart flag entered is incorrect." 2.2.22.272 RAC1117 : "Unable to run the command." 2.2.22.273 RAC1118 : "Successfully initiated the update operation specified in the command." 2.2.22.274 RAC1119 : "Unable to generate a comparison report for the specified repository." 2.2.22.
to a remote share." 2.2.22.292 RAC1141 : "The iDRAC firmware rollback operation was initiated." 2.2.22.293 RAC1142 : "Unable to start the Remote Diagnostics operation because the Expiration Time entered (difference between Start Time and Expiration Time) is less than five minutes." 2.2.22.294 RAC1143 : "Configuration results are not applicable for the job type for Job: ." When event is generated, message will have the following substitutions: • = "JobID" 2.2.22.
2.2.22.296 RAC1145 : "The entered log type is invalid." 2.2.22.297 RAC1146 : "Unable to set the SNMPv3 username because SNMPv3 is not enabled for the specified user on iDRAC." 2.2.22.298 RAC1147 : "Unable to set the SNMPv3 username entered in the command because the username is not present or enabled on iDRAC." 2.2.22.299 RAC1150 : "Unable to complete the export operation." 2.2.22.300 RAC1151 : "The export operation is unsuccessful." 2.2.22.301 RAC1152 : "The export operation completed successfully." 2.2.
2.2.22.313 RAC1164 : "A remote diagnostics operation is currently running and not completed." 2.2.22.314 RAC1165 : "Unable to configure the port number that is entered for either http or https ports of the iDRAC Web server, because the port number is already in use." 2.2.22.315 RAC1166 : "Successfully initiated Configuration XML file preview operation that was invoked by .
2.2.22.316 RAC1168 : "The RACADM "getconfig" command will be deprecated in a future version of iDRAC firmware." 2.2.22.317 RAC1169 : "The RACADM "config" command will be deprecated in a future version of iDRAC firmware." 2.2.22.318 RAC1170 : "Unable to find the SSL library in the default path." 2.2.22.319 RAC1175 : "Unable to change the user configuration because modifying the user configuration at index 1 is not allowed." 2.2.22.
• = "Param1" 131
2.2.23.5 RED074 : "A required parameter is not present." 2.2.23.6 RED075 : "An Automatic Backup schedule already exists." 2.2.24 Subcategory= Remote Service [MessageID prefix =RSI] 2.2.24.1 RSI0001 : "The Lifecycle Controller Remote Services is available." 2.2.24.2 RSI0002 : "The remote service is currently not available" 2.2.24.3 RSI0003 : "The remote service is reloading data" 2.2.24.4 RSI0004 : "The remote service is unavailable" 2.2.25 Subcategory= Security Event [MessageID prefix =SEC] 2.2.25.
job for the device already exists." 2.2.26.19 STOR024 : "Unable to create a configuration job because a configuration job for the device already exists." 2.2.26.20 STOR025 : "Unable to delete any pending configuration because the configuration job is already scheduled." 2.2.26.21 STOR026 : "A configuration job was not created because there are no pending configuration changes." 2.2.26.22 STOR027 : "Virtual Disk name is not supported." 2.2.26.23 STOR028 : "Virtual disk not found." 2.2.26.
• = "DiskCachePolicy" 2.2.26.35 STOR042 : "Unsupported value for AttributeName " When event is generated, message will have the following substitutions: • = "DiskCachePolicy" 2.2.26.36 STOR043 : "One or more selected physical disk drives are part of virtual disk that is not Secondary RAID Level 0." 2.2.26.37 STOR044 : "All physical disks specified are not part of the same disk group." 2.2.26.
2.2.26.41 STOR048 : "Controller is not Dell Key Management capable." 2.2.26.42 STOR049 : "Controller is in Local Key Management mode." 2.2.26.43 STOR050 : "Controller is in Dell Key Management mode." 2.2.26.44 STOR051 : "StartingLBA and Size value combination is greater than allowed by the physical disk size." 2.2.26.45 STOR052 : "Attempt to exceed the number of supported of virtual disks on a controller or disk group." 2.2.26.46 STOR053 : "The controller key is not present.
Lifecycle Controller version on the server does not have the necessary capabilities." 2.2.26.62 STOR069 : "Unable to run the method, because the number of elements entered for VDPropNameArry and VDPropValueArray is unequal." When event is generated, message will have the following substitutions: • = "Param1" 2.2.26.63 STOR070 : "Unable to run the WS-MAN method , because an invalid parameter is entered.
2.2.26.65 STOR072 : "iDRAC Service Module (ISM) is either not present or not running on the server OS." 2.2.26.66 STOR073 : "The iDRAC Service Module version present on the server OS does not support the requested PCIe SSD (NVMe) device operation." 2.2.26.67 STOR074 : "The requested RAID configuration operation is not allowed because the controller is currently in Non-RAID mode." 2.2.26.
present on the controller. Delete the preserved cache and retry the operation." 2.2.26.83 STOR0701 : "Storage objects are unavailable in the current system configuration." 2.2.26.
2.2.26.85 STOR034 : "Invalid parameter value for RebootJobType." 2.2.27 Subcategory= Software Config [MessageID prefix =SWC] 2.2.27.1 SWC0001 : "Unable to save the network settings." 2.2.27.2 SWC0002 : "Unable to set Part Replacement policies." 2.2.27.3 SWC0003 : "Unable to display the Lifecycle log." 2.2.27.4 SWC0004 : "Unable to add a work note to the Lifecycle Log." 2.2.27.5 SWC0005 : "Unable to display the current hardware inventory." 2.2.27.
Controller GUI." 2.2.27.23 SWC0028 : "The backup Server Profile operation did not successfully complete." 2.2.27.24 SWC0029 : "Unable to retrieve status of backup Server Profile operation." 2.2.27.25 SWC0030 : "Unable to complete the backup Server Profile backup operation." 2.2.27.26 SWC0031 : "Unable to initiate the backup Server Profile backup operation." 2.2.27.27 SWC0032 : "Successfully exported the Server Configuration Profile image file to the USB drive." 2.2.27.
share folder." 2.2.27.67 SWC0072 : "Unable to export the Tech Support Report to destination folder." 2.2.27.68 SWC0073 : "Unable to start operation with the current iDRAC version." 2.2.27.69 SWC0074 : "Unable to start operation with the current iDRAC version." 2.2.27.70 SWC0075 : "Unable to perform RAID operations because the selected controller is in HBA mode." 2.2.27.
2.2.27.72 SWC0077 : "Unable to initiate the Repurpose or Retire System operation." 2.2.27.73 SWC0101 : "Unable to read available log records." 2.2.27.74 SWC0102 : "The -m option is not supported by the interface being used." 2.2.27.75 SWC0103 : "The -E option is not valid for the specified log." 2.2.27.76 SWC0104 : "The -R option is not valid for the specified log." 2.2.27.77 SWC0105 : "Invalid -m option. Try --more or refer help for proper usage" 2.2.27.
configured before a CSR can be generated." 2.2.27.101 SWC0129 : "Unable to send test email. Please make sure that your email alerts \nhave been configured correctly and connectivity to \nthe SMTP server exists." 2.2.27.102 SWC0130 : "Trap at specified index is not currently enabled." 2.2.27.103 SWC0131 : "Trap destination address must be configured." 2.2.27.104 SWC0132 : "Unable to send test trap.
2.2.27.112 SWC0140 : "RAC reset operation initiated successfully. It may take up to a minute \nfor the RAC to come back online again." 2.2.27.113 SWC0141 : "Certificate successfully downloaded from the RAC" 2.2.27.114 SWC0143 : "SSL key successfully uploaded to the RAC." 2.2.27.115 SWC0144 : "Certificate successfully uploaded to the RAC. The RAC will now reset \nto enable the new certificate and may be offline temporarily." 2.2.27.116 SWC0145 : "A CSR was generated successfully" 2.2.27.
know Remote File Share is ENABLED or DISABLED." 2.2.27.148 SWC0216 : "The -c option requires -l to also be specifed." 2.2.27.149 SWC0217 : "The -c option requires -u to also be specifed." 2.2.27.150 SWC0218 : "The -c option requires -p to also be specifed." 2.2.27.151 SWC0219 : "The -p option requires -c to also be specifed." 2.2.27.152 SWC0220 : "The -u option requires -c to also be specifed." 2.2.27.153 SWC0221 : "The -l option requires -c to also be specifed." 2.2.27.154 SWC0222 : "Invalid syntax.
AutoConfig is enabled." 2.2.27.172 SWC0240 : "The IPv6 DNS Server IP address is not allowed to be configured if IPv6 DNS Server DHCP (cfgIPv6DNSServersFromDHCP6) is enabled" 2.2.27.173 SWC0241 : "Power Cap Enable not set. Unable to modify this property" 2.2.27.174 SWC0242 : "A required license is missing or expired. Obtain an appropriate license and try again, or contact your service provider for additional details." 2.2.27.175 SWC0243 : "Certificate regenerated successfully and webserver restarted" 2.2.27.
2.2.27.184 SWC0252 : "No options were specified. The subcommand requires options to be used." 2.2.27.185 SWC0253 : "Unable to allocate memory needed to perform operation." 2.2.27.186 SWC0254 : "Unable to perform requested operation. \nIf the operation attempted was to configure DRAC, possible reason may be that \nLocal Configuration using RACADM is disabled." 2.2.27.187 SWC0255 : "Unable to open file." 2.2.27.188 SWC0256 : "Unable to read file." 2.2.27.189 SWC0257 : "Invalid syntax.
• = "1" 2.2.27.213 SWC0281 : "The specified object is READ ONLY and cannot be modified." 2.2.27.214 SWC0282 : "The specified object is READ ONLY for this index and cannot be modified." 2.2.27.215 SWC0283 : "The specified object value is not valid." 2.2.27.216 SWC0284 : "Failed to set the object value. \nPossible reason may be that Local Configuration using RACADM is disabled." 2.2.27.217 SWC0285 : "Object value is invalid." 2.2.27.
• = "1" 149
2.2.27.225 SWC0293 : "The specified object is not recognized by iDRAC." 2.2.27.226 SWC0294 : "Invalid group name specified." 2.2.27.227 SWC0295 : "Invalid object name specified." 2.2.27.228 SWC0296 : "The specified value is not allowed to be configured if the user name \nor password is blank." 2.2.27.229 SWC0297 : "Unable to remove passwords because file could not be saved." 2.2.27.
in read-only mode." 2.2.27.261 SWC0722 : "Error occurred while resetting to defaults. The reset command was not accepted." 2.2.27.262 SWC0723 : "Error occurred while Resetting to defaults. The Reset status is not available." 2.2.27.263 SWC0724 : "Error occurred while Resetting to defaults due to a timeout." 2.2.27.264 SW0725 : "iDRAC7 communication failure." 2.2.27.265 SWC1903 : "RAC SSL Certificate has been changed." 2.2.27.266 SWC1905 : "RAC Virtual Console configuration has been changed." 2.2.27.
• = "UserName" 2.2.27.277 SWC1925 : "The iDRAC Quick Sync access feature is set to the Disabled mode." 2.2.27.278 SWC1926 : "The iDRAC Quick Sync interface is enabled." 2.2.27.279 SWC1927 : "The iDRAC Quick Sync access feature is set to the read-only mode." 2.2.27.280 SWC1928 : "The iDRAC Quick Sync access feature is set to the read-write mode." 2.2.27.281 SWC1929 : "The iDRAC Quick Sync inactivity timeout value is set to .
2.2.28 Subcategory= System Info [MessageID prefix =SYS] 2.2.28.1 SYS001 : "The operation was successful." 2.2.28.2 SYS002 : "Unable to perform the operation due to an unknown error in iDRAC." 2.2.28.3 SYS003 : "Missing parameters: ." When event is generated, message will have the following substitutions: • = "parameter name" 2.2.28.4 SYS004 : "Invalid parameter value for .
2.2.28.11 SYS011 : "Pending configuration values are already committed, unable to perform another set operation." 2.2.28.12 SYS012 : "User privileges are not sufficient to perform operation." 2.2.28.13 SYS013 : "Invalid attribute name: ." When event is generated, message will have the following substitutions: • = "attribute name" 2.2.28.
2.2.28.27 SYS030 : "Collecting component configuration information." 2.2.28.28 SYS031 : "Updating component configuration." 2.2.28.29 SYS032 : "Staged component configuration is complete." 2.2.28.30 SYS033 : "Staged component configuration completed with errors." 2.2.28.31 SYS034 : "Performing component configuration for: " When event is generated, message will have the following substitutions: • = "NIC.Integrated.1-1.1" 2.2.28.
• = " linenumber" 2.2.28.46 SYS050 : "The system configuration XML file for import configuration is not compliant with schema nesting checks." 2.2.28.47 SYS051 : "The system could not be shut down within the specified time." 2.2.28.48 SYS052 : "Analyzing iDRAC, System, or Lifecycle Controller configuration for changes to be applied." 2.2.28.49 SYS053 : "Successfully imported and applied system configuration XML file." 2.2.28.
2.2.28.61 SYS065 : "Input file for import configuration operation cannot be found or opened." 2.2.28.62 SYS066 : "No changes detected for iDRAC, System, or Lifecycle Controller configuration." 2.2.28.63 SYS067 : "Unable to complete application of configuration XML file values." 2.2.28.64 SYS068 : "Configuration changes that require system reboot were not applied." 2.2.28.65 SYS069 : "No changes were applied since the current component configuration matched the requested configuration." 2.2.28.
imported to the system." 2.2.28.80 SYS088 : "Estimated time for applying configuration changes is seconds." When event is generated, message will have the following substitutions: • = "seconds" 2.2.28.81 SYS089 : "Preview of system configuration XML file is complete." 2.2.28.82 SYS090 : "The configuration XML input file contains unsupported DOCTYPE tags." 2.2.28.83 SYS091 : "Unable to complete the operation because the method is not supported." 2.2.28.
• = "JID_123456789098" 2.2.28.97 SYS152 : "Erase operations for some System Erase tasks did not complete successfully." 2.2.28.98 SYS153 : "Deleting hardware cache data for controller: ." When event is generated, message will have the following substitutions: • = "RAID.Integrated.1-1" 2.2.28.99 SYS154 : "Initiating secure erase operation on secure erase-capable drives for controller: .
2.2.28.101 SYS156 : "Erase operations for System Erase tasks successfully completed." 2.2.28.102 SYS157 : "Unable to successfully complete requested System Erase tasks." 2.2.28.103 SYS158 : "Hardware cache erase is unsuccessful." 2.2.28.104 SYS159 : "vFlash SD Card erase unsuccessful." 2.2.28.105 SYS160 : "The Lifecycle Controller logs are cleared." 2.2.28.106 SYS161 : "Tech Support Report related non-volitale storage deleted." 2.2.28.107 SYS162 : "Turning on the server to perform System Erase tasks." 2.2.
2.2.29.5 TST104 : "SNMP traps not configured." 2.2.29.6 TST105 : "Invalid parameter value for ." When event is generated, message will have the following substitutions: • = "parameter name" 2.2.29.7 TST106 : "Email alert destination address not configured." 2.2.30 Subcategory= UEFI Event [MessageID prefix =UEFI] 2.2.30.1 UEFI0027 : "The system must be restarted for the new license to become effective." 2.2.30.2 UEFI0030 : "A keyboard device is not connected to the system.
2.2.30.14 UEFI0073 : "Unable to boot because of the Secure Boot policy." When event is generated, message will have the following substitutions: • = "Disk connected to USB Front Port 1: Datastick Pro" 2.2.30.15 UEFI0074 : "The Secure Boot policy has been modified since the last time the system was started." 2.2.30.16 UEFI0075 : "Network Daughter Card 1 is not detected." 2.2.30.17 UEFI0081 : "Memory size has changed from the last time the system was started." 2.2.30.
• = "B2" 2.2.30.24 UEFI0092 : "The number of DIMM ranks has exceeded the maximum allowed ranks per channel limit." 2.2.30.25 UEFI0093 : "The DIMM installed on the memory slot: does not meet the minimum supported frequency." When event is generated, message will have the following substitutions: • = "B2" 2.2.30.26 UEFI0094 : "Unsupported Non-ECC memory module is installed on memory slot: .
2.2.30.35 UEFI0105 : "Unable to enable the Cluster on Die (COD) feature because of an unsupported memory configuration." 2.2.30.36 UEFI0113 : "Unable to enable the Fault Resilient Memory (FRM) feature because the current DIMM population or hardware configuration does not support the feature." 2.2.30.37 UEFI0114 : "Unable to enable the Fault Resilient Memory (FRM) operating mode because of mismatches in DIMM channel configurations." 2.2.30.
• = "parameter name" 2.2.31.4 USR103 : "Missing parameters ." When event is generated, message will have the following substitutions: • = "PARAM1" 2.2.31.5 USR104 : "Unable to perform the operation due to an unknown error in iDRAC." 2.2.31.6 USR105 : "The account is not configured." 2.2.32 Subcategory= vFlash Media [MessageID prefix =VF] 2.2.32.1 VF001 : "Command successful." 2.2.32.2 VF002 : "General failure" 2.2.32.
2.2.32.5 VF005 : "Empty partition creation successful" 2.2.32.6 VF006 : "Empty partition creation failed" 2.2.32.7 VF007 : "Image partition creation successful" 2.2.32.8 VF008 : "Image partition creation did not complete successfully." 2.2.32.9 VF009 : "Partition formatting successful" 2.2.32.10 VF010 : "Partition formatting did not complete successfully." 2.2.32.11 VF011 : "Wrong password" 2.2.32.12 VF012 : "SD card not present" 2.2.32.13 VF013 : "SD card locked" 2.2.32.14 VF014 : "vFlash not disabled" 2.
could not be initialized." 2.2.33.13 VFL0713 : "One or more partitions are currently attached; the SD card could not be initialized." 2.2.33.14 VFL0714 : "SD card is not ready and could not be initialized." 2.2.33.15 VFL0715 : "Error occurred while initializing the SD Card due to insufficient permission." 2.2.33.16 VFL0716 : "SD Card is not a vFlash SD Card; the SD card could not be initialized." 2.2.33.17 VFL0719 : "One or more partitions are in use; the SD card could not be initialized." 2.2.33.
2.3.1.4 BAT1003 : "The battery on learn cycle has completed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.5 BAT1004 : "The battery on learn cycle has timed out." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.6 BAT1005 : "The battery on learn cycle has been postponed.
• = "RAID Controller in Slot 5" 2.3.1.13 BAT1012 : "The battery temperature is above normal." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.14 BAT1013 : "Recharge count has exceeded the maximum limit for battery on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.
2.3.1.22 BAT1021 : "The charge level for the battery on is below the normal threshold." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.23 BAT1022 : " battery recondition is completed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.
2.3.1.31 BAT1030 : "The battery charge level is normal." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.32 BAT1031 : "The battery temperature on is above normal." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.1.33 BAT1032 : "The battery temperature on is normal.
2.3.3 Subcategory= Storage Contr [MessageID prefix =CTL] 2.3.3.1 CTL1 : "Controller event log: " When event is generated, message will have the following substitutions: • = "A foreign configuration was detected on RAID Controller in Slot 2" 2.3.3.2 CTL2 : " rebuild rate has changed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.3 CTL3 : " alarm is enabled.
• = "RAID Controller in Slot 5" 2.3.3.11 CTL11 : "Configuration on was reset." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.12 CTL12 : "An invalid SAS configuration has been detected on .
• = "RAID Controller in Slot 5" 2.3.3.20 CTL21 : "Abort CC on Error and Load Balance has changed for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.21 CTL22 : "Load Balance has changed for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.
2.3.3.29 CTL30 : "The Check Consistency rate has changed for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.30 CTL31 : "Copyback is modified for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.31 CTL32 : "Abort CC on Error is modified for .
• = "RAID Controller in Slot 5" 2.3.3.39 CTL40 : "Multi-bit ECC error on DIMM." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.40 CTL41 : "Single-bit ECC error on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.
2.3.3.48 CTL49 : "The NVRAM has corrupted data on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.49 CTL50 : "The NVRAM has corrupt data." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.
2.3.3.57 CTL58 : " SAS SMP communications error " When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" • = " not implemented" 2.3.3.58 CTL59 : " SAS expander error: " When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" • = " not implemented" 2.3.3.
• = " RAID Controller in Slot 5" 2.3.3.65 CTL66 : "Attempted to import Unsupported Virtual Disk type RAID on ." When event is generated, message will have the following substitutions: • = "not implemented" • = " RAID Controller in Slot 5" 2.3.3.66 CTL67 : "Attempted to import Virtual Disk with missing span on .
• = "RAID Controller in Slot 5" 2.3.3.74 CTL75 : "Preserved cache discarded on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.75 CTL76 : "A configuration command could not be committed to disk on " When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.
• = "RAID Controller in Slot 5" 2.3.3.83 CTL84 : " is running an unsupported firmware version." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.84 CTL85 : " is operating at less than optimal bandwidth." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.
• = "RAID Controller in Slot 6" 2.3.3.92 CTL93 : " has been successfully changed to operate in Fault Tolerant mode." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.93 CTL94 : " has been successfully changed to operate in single controller mode." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.
• = "RAID Controller in Slot 5" 2.3.3.101 CTL102 : "The is enabled." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.3.102 CTL200 : "The current firmware version is older than the required version for ." When event is generated, message will have the following substitutions: • = "5.1.10.10" • = "5.1.10.
• = "Controller 1 (PERC H800 Adapter)" 2.3.3.108 CTL206 : "Abort Check Consistency on Error and Auto Copyback on Predictive Failure values are changed for ." When event is generated, message will have the following substitutions: • = "Controller 1 (PERC H800 Adapter)" 2.3.3.109 CTL207 : "Unable to import the Virtual Disk because the supported limit is exceeded on .
• = "Controller 1 (PERC H800 Adapter)" 2.3.3.117 CTL215 : "Redundant path disconnected on ." When event is generated, message will have the following substitutions: • = "Controller 1 (PERC H800 Adapter)" 2.3.3.118 CTL216 : "Redundant path connection is restored on ." When event is generated, message will have the following substitutions: • = "Controller 1 (PERC H800 Adapter)" 2.3.3.
2.3.4.6 DIAG0146 : "Hard Drive - S/N , self test log contains previous error(s)." When event is generated, message will have the following substitutions: • = "0" • = "B363P5B000HM" 2.3.4.7 DIAG0147 : "Optical Drive - Self test: ." When event is generated, message will have the following substitutions: • = "0" • = "DRAM test failed" 2.3.4.
• <80000000000000??> = "800000000018" • = "" 2.3.4.14 DIAG0155 : "Hard Drive - Not installed." 2.3.4.15 DIAG8154 : "Tape Drive - S/N , ULTRIUM media found but drive requires ULTRIUM for ." When event is generated, message will have the following substitutions: • = "0" • = "3" • = "4, 5, or 6" • = "6" • = "writes" 2.3.4.
2.3.4.20 DIAG8160 : "PERC Battery - incorrect status = <80000000000000??>\n." When event is generated, message will have the following substitutions: • = "0" • <80000000000000??> = "8000000000000000" • = "Battery missing or disconnected" 2.3.4.21 DIAG8166 : "OS - Suspect corrupt MBR, verify MBR with Anti-Virus Application." 2.3.5 Subcategory= Storage Enclosr [MessageID prefix =ENC] 2.3.5.
2.3.5.8 ENC8 : "The alarm was disabled." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.5.9 ENC9 : "The asset tag was changed." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.5.10 ENC10 : "The asset name was changed.
• = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.5.17 ENC17 : "An Enclosure Management Module (EMM) has been discovered on ." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.5.18 ENC18 : "Communication with was lost.
• = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.5.26 ENC27 : "SAS or SATA mixing of physical disks is not supported within the ." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.5.27 ENC28 : "Enclosure Management Module (EMM) firmware version mismatch detected in . .
• = "Enclosure 0:0 on Controller 1 at Connector 0" 2.3.6 Subcategory= Fan Event [MessageID prefix =FAN] 2.3.6.1 FAN1000 : " was removed." When event is generated, message will have the following substitutions: • = "Fan 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.6.2 FAN1001 : " has been inserted.
2.3.7.6 FLDC1007 : "The cache device with WWN = and path = is removed." When event is generated, message will have the following substitutions: • = "" 2.3.7.7 FLDC1008 : "The cache device with WWN = and path = is being removed." When event is generated, message will have the following substitutions: • = "" 2.3.7.
2.3.7.14 FLDC1016 : "A valid permanent license is installed for Fluid Cache." 2.3.7.15 FLDC1017 : "A license has been installed for Fluid Cache." 2.3.7.16 FLDC1018 : "A license has been removed for Fluid Cache." 2.3.7.17 FLDC1019 : "All cache devices have been found and registered for Fluid Cache." 2.3.7.18 FLDC1020 : "The storage device with WWN = and path = is in unknown state." When event is generated, message will have the following substitutions: • = "" 2.3.7.
2.3.7.22 FLDC1024 : "Caching was enabled in write-back mode, but it is currently operating in write-through mode." 2.3.7.23 FLDC1025 : "Caching was enabled in write-back or write-through mode, it is currently operating in pass-through mode." 2.3.7.24 FLDC1026 : "Caching is no longer degraded to write-through mode and is now operating in write-back mode for Fluid Cache." 2.3.7.25 FLDC1027 : "Caching is no longer degraded to pass-through mode and is now operating in its configured mode for Fluid Cache." 2.3.
2.3.7.35 FLDC1037 : "Configuration changes are disabled, because Fluid cache is running on an expired or invalid license." 2.3.7.36 FLDC1038 : "There is not enough memory capacity to run necessary services for Fluid Cache." 2.3.7.37 FLDC1039 : "One or more cache devices are missing, resulting in Fluid Cache to be unresponsive." 2.3.8 Subcategory= Physical Disk [MessageID prefix =PDR] 2.3.8.1 PDR1 : " copyback stopped for rebuild.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.9 PDR9 : "Initialization has started on ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.10 PDR10 : " rebuild has started.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.19 PDR19 : "SMART FPT exceeded for ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.20 PDR20 : "SMART configuration change for ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.29 PDR29 : "Rebuild on completed with error(s)." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.30 PDR30 : "A global hot spare failed.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.39 PDR39 : "A blink operation has initiated on ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.40 PDR40 : "The blink operation has ceased on .
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.49 PDR50 : "Insufficient space on the global hot spare ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.50 PDR51 : "Hot spare SMART polling has failed.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.59 PDR60 : "Error occurred on : ." When event is generated, message will have the following substitutions: • • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" = " Error 123" 2.3.8.60 PDR61 : "The rebuild of failed due to errors on the source physical disk.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.69 PDR70 : "Copyback started from to ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" • = " Disk 6 in Enclosure 0 on Coonnector 0 of RAID Controller in Slot 5" 2.3.8.70 PDR71 : "Copyback completed from to .
2.3.8.78 PDR79 : "A user terminated Copyback from to ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" • = " Disk 6 in Enclosure 0 on Coonnector 0 of RAID Controller in Slot 5" 2.3.8.79 PDR81 : "Microcode update started on .
2.3.8.87 PDR93 : "Microcode update on has completed." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.88 PDR94 : "Microcode update on has timed out." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.
2.3.8.97 PDR104 : "The has turned off because the critical temperature threshold is exceeded." When event is generated, message will have the following substitutions: • = "Param1" 2.3.8.98 PDR105 : " is assigned as dedicated hot-spare." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.8.
• = "PCIe Solid-State Drive in Slot 9 in Bay 1" 2.3.8.106 PDR114 : "The is approaching read-only mode." When event is generated, message will have the following substitutions: • = "PCIe Solid-State Drive in Slot 9 in Bay 1" 2.3.8.107 PDR115 : "The is in read-only mode.
• = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 2.3.8.115 PDR211 : " has encountered storage medium error." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 2.3.8.116 PDR212 : "The state of changed from Ready to Non-RAID.
2.3.9.4 PSU1003 : " is switched OFF." When event is generated, message will have the following substitutions: • = "PSU 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.9.5 PSU1004 : "Power supply cable has been inserted into ." When event is generated, message will have the following substitutions: • = "PSU 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.9.
2.3.10 Subcategory= RAC Event [MessageID prefix =RAC] 2.3.10.1 RAC0500 : "There are no batteries to be displayed." 2.3.10.2 RAC0501 : "There are no physical disks to be displayed." 2.3.10.3 RAC0502 : "There are no virtual disks to be displayed." 2.3.10.4 RAC0503 : "There are no out-of-band capable controllers to be displayed." 2.3.10.5 RAC0504 : "There are no enclosures to be displayed." 2.3.10.6 RAC0505 : "There are no devices to be displayed." 2.3.10.
2.3.11.4 SSD1004 : "Exported the log file." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 2.3.11.5 SSD1005 : "Successfully initialized ." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 2.3.11.
• = "CDB:xyz, Sense:abc" 2.3.12.3 STOR3 : "CEM Storage Management has lost communication with the ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 2.3.12.4 STOR4 : "CEM Storage Management encountered internal error." 2.3.12.5 STOR5 : "Redundancy lost.
2.3.12.6 STOR6 : "CEM Storage Management detected inventory change(s) after host reboot." 2.3.12.7 STOR7 : "The storage management instrumentation is performing an inventory refresh operation." 2.3.12.8 STOR8 : "Detected two RAID controllers in integrated slots. This configuration is not currently supported and the second controller will not be powered on." 2.3.12.9 STOR9 : "No RAID controllers have been detected. Access to shared storage will not be available." 2.3.12.
2.3.12.22 STOR0101 : "No RAID controller is displayed." 2.3.12.23 STOR0102 : "No batteries are displayed." 2.3.12.24 STOR0103 : "No physical disks are displayed." 2.3.12.25 STOR0104 : "No virtual disks are displayed." 2.3.12.26 STOR0105 : "No enclosures are displayed." 2.3.12.27 STOR0106 : "Fans are not connected to enclosures or data about fans is unavailable." 2.3.12.28 STOR0107 : "EMMs are not connected to enclosures or data about EMMs is unavailable." 2.3.12.
2.3.12.36 STOR0203 : "The current operating system kernel version and the non-RAID SCSI driver version are older than the minimum required versions." 2.3.12.37 STOR0204 : "The non-RAID SCSI driver version is older than the minimum required version." 2.3.12.38 STOR0205 : "Global rescan initiated for all storage components in the system." 2.3.12.39 STOR0206 : "Smart thermal shutdown feature is enabled." 2.3.12.40 STOR0207 : "Smart thermal shutdown feature is disabled." 2.3.12.
2.3.12.46 STOR0501 : "Unable to configure RAID." 2.3.12.47 STOR0502 : "Unable to launch RAID Configuration wizard." 2.3.12.48 STOR0503 : "Successfully erased RAID configuration." 2.3.12.49 STOR0504 : "Successfully completed RAID operation." 2.3.12.50 STOR0505 : "Unable to delete virtual disks." 2.3.12.51 STOR0506 : "Unable to create virtual disk." 2.3.12.52 STOR0507 : "Insufficient physical disk space on selected RAID controller." 2.3.12.
2.3.14.3 TMP7 : " has failed." When event is generated, message will have the following substitutions: • = "Temperature Sensor 0 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.14.4 TMP1000 : " exceeded the maximum warning threshold." When event is generated, message will have the following substitutions: • = "Temperature Sensor 0 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 2.3.14.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.4 VDR4 : " was created." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.5 VDR5 : " was deleted." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.6 VDR6 : " configuration has changed.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.14 VDR14 : "The consistency check on was cancelled." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.15 VDR15 : "Initialization of was cancelled." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.24 VDR24 : "Reconfiguration of has completed." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.25 VDR25 : " rebuild is completed." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.35 VDR35 : "Background initialization has completed for ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.36 VDR36 : " initialization is in-progress .
2.3.15.44 VDR44 : " disk cache policy has changed." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.45 VDR45 : " blink has been initiated." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.46 VDR46 : " blink has ceased.
2.3.15.53 VDR53 : "The consistency check logging of inconsistent parity data is disabled for ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.54 VDR54 : " initialization is terminated." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.55 VDR55 : " initialization has failed.
2.3.15.62 VDR93 : " bad block medium error is cleared." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.63 VDR94 : "Controller preserved cache was recovered for ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 2.3.15.64 VDR95 : "Unable to log block .Bad block table on is full.
• = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 2.3.15.71 VDR101 : "Virtual Adapter mapping reported for . Virtual Adapter 1 is now . Virtual Adapter 2 is now . Virtual Adapter 3 is now .
• = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 2.3.15.79 VDR109 : "Successfully deleted Controller Enhanced cache ()." When event is generated, message will have the following substitutions: • = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 2.3.15.80 VDR110 : "Unrecoverable storage medium error detected on .
2.4.1.4 AMP0303 : "The system board current is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "fail-safe" 2.4.1.5 AMP0304 : "The system board current is outside of range." When event is generated, message will have the following substitutions: • = "fail-safe" 2.4.1.6 AMP0305 : "The system board current is within range.
2.4.1.13 AMP0312 : "System level current is less than the lower warning threshold." 2.4.1.14 AMP0313 : "System level current is less than the lower critical threshold." 2.4.1.15 AMP0314 : "System level current is greater than the upper warning threshold." 2.4.1.16 AMP0315 : "System level current is greater than the upper critical threshold." 2.4.1.17 AMP0316 : "System level current is outside of range." 2.4.1.18 AMP0317 : "System level current is within range." 2.4.1.
• = " 100.000" 2.4.1.29 AMP404 : "The sensor detected an error with a value of A." When event is generated, message will have the following substitutions: • = "System Board Pwr Consumption" • = " 658" 2.4.1.30 AMP405 : "The sensor state has changed to a failed state with a value of A.
• = "Tue Jan 08 10:56:54 2013" 2.4.2.17 ASR201 : "The watchdog timer restarted the system at ." When event is generated, message will have the following substitutions: • = "Tue Jan 08 10:56:54 2013" 2.4.2.18 ASR202 : "The watchdog timer turned off the system at .
2.4.3.12 BAT0011 : "The storage battery for disk drive bay is operating normally." When event is generated, message will have the following substitutions: • = "1" 2.4.3.13 BAT0012 : "The storage battery for disk drive bay has failed." When event is generated, message will have the following substitutions: • = "1" 2.4.3.14 BAT0013 : "The storage battery for disk drive bay is present." When event is generated, message will have the following substitutions: • = "1" 2.
2.4.3.21 BAT0030 : "The system board battery is reading low." 2.4.3.22 BAT0031 : "The system board battery status is unknown." 2.4.4 Subcategory= Cable [MessageID prefix =CBL] 2.4.4.1 CBL0001 : "Backplane power cable disconnected." When event is generated, message will have the following substitutions: • = "1" 2.4.4.2 CBL0002 : "Backplane signal cable disconnected." When event is generated, message will have the following substitutions: • = "1" 2.4.4.
• = "PERC SAS B0" • = "2" • = "PCIe C" 2.4.5 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 2.4.5.1 CMC8502 : "Unable to access the IPv6 information of the server." 2.4.5.2 CMC8503 : "Unable to access the IPv4 information of the server." 2.4.5.3 CMC8504 : "Unable to access server: , because the NIC is disabled on the identified server." When event is generated, message will have the following substitutions: • = "" 2.4.
• = "" 2.4.5.10 CMC8520 : "The FRU on server is not functioning." When event is generated, message will have the following substitutions: • = "" 2.4.5.11 CMC8521 : "The Mezz card 1 FRU for the server is not functioning." When event is generated, message will have the following substitutions: • = "" 2.4.5.12 CMC8522 : "The Mezz card 2 FRU for the server is not functioning.
2.4.5.19 CMC8534 : "Unable to turn on the server because the power requirement request exceeds the power cap value." When event is generated, message will have the following substitutions: • = "" 2.4.6 Subcategory= Processor [MessageID prefix =CPU] 2.4.6.1 CPU0000 : "CPU has an internal error (IERR)." When event is generated, message will have the following substitutions: • = "1" 2.4.6.2 CPU0001 : "CPU has a thermal trip (over-temperature) event.
2.4.6.9 CPU0008 : "CPU is disabled." When event is generated, message will have the following substitutions: • = "1" 2.4.6.10 CPU0009 : "CPU terminator is present." When event is generated, message will have the following substitutions: • = "1" 2.4.6.11 CPU0010 : "CPU is throttled." When event is generated, message will have the following substitutions: • = "1" 2.4.6.12 CPU0011 : "Uncorrectable Machine Check Exception detected on CPU .
• = "1" 2.4.6.19 CPU0701 : "CPU protocol error detected." When event is generated, message will have the following substitutions: • = "1" 2.4.6.20 CPU0702 : "CPU bus parity error detected." 2.4.6.21 CPU0703 : "CPU bus initialization error detected." 2.4.6.22 CPU0704 : "CPU machine check error detected." When event is generated, message will have the following substitutions: • = "1" 2.4.6.23 CPU0800 : "CPU voltage regulator module is present.
2.4.6.29 CPU0806 : "CPU voltage regulator module is incorrectly configure." When event is generated, message will have the following substitutions: • = "1" 2.4.6.30 CPU0816 : "CPU voltage regulator module is absent." When event is generated, message will have the following substitutions: • = "1" 2.4.6.31 CPU0817 : "CPU voltage regulator module is operating normally." When event is generated, message will have the following substitutions: • = "1" 2.
• = "0" 2.4.8.4 DIAG0114 : "Cache integrity test discrepancy " When event is generated, message will have the following substitutions: • = "Unable to start application processor(s)." 2.4.8.5 DIAG0115 : "CPU Stress Thermal condition. Limit C, Actual C." When event is generated, message will have the following substitutions: • = "60" • = "73" 2.4.8.6 DIAG0121 : "Memory errors detected, but successfully resolved." 2.4.8.
2.4.8.16 DIAG0213 : "System board - CMOS battery failure detected." 2.4.8.17 DIAG0221 : "System board - Interval timer not functional." 2.4.8.18 DIAG0232 : "RTC - did not generate periodic ticks." 2.4.8.19 DIAG0233 : "System board - RTC seconds count is not updating." 2.4.8.20 DIAG0234 : "System board - HPET <1>, incorrect time period. Expected = , Found = ." When event is generated, message will have the following substitutions: • <1> = "1" • = "1" • = "0" 2.4.8.
• = "CPU1" • = "78" 2.4.8.30 DIAG0315 : "Sensor: The () reading C) is lower than expected." When event is generated, message will have the following substitutions: • = "CPU1" • = "0" 2.4.8.31 DIAG0321 : "LCD EDID - Unable to access EDID EEPROM." 2.4.8.32 DIAG0322 : "LCD panel - Unable to modify brightness." 2.4.8.33 DIAG0323 : "Unable to detect inverter lamp status." 2.4.8.
2.4.8.46 DIAG 0414 : "Cables - not detected." When event is generated, message will have the following substitutions: • = "Inverter cable" 2.4.8.47 DIAG0415 : "Cables - Check the following cable, jumper, connection, or sensor: ." When event is generated, message will have the following substitutions: • = "Intrusion" 2.4.8.48 DIAG0511 : "Fan - The () fan failed to respond correctly.
• = "CPU Thermistor" • = "7" • = "8" 2.4.8.54 DIAG8003 : "Fan - Unable to set Manufacturing Mode." 2.4.8.55 DIAG8004 : "Fan - Unable to determine fan speeds." 2.4.8.56 DIAG8005 : "LCD BIST not supported. or Fan - Fan speed failure. Expected at least , observed ." When event is generated, message will have the following substitutions: • = "3500" • = "2600" 2.4.8.57 DIAG8006 : "Fan - Unable to set fans to speed.
• = "1" 2.4.8.64 DIAG8013 : "LCD doesnt support test commands." When event is generated, message will have the following substitutions: • = "LCD" 2.4.8.65 DIAG8014 : "ADDF module () device () failed with error code , number . No EPSA beep code mapped." When event is generated, message will have the following substitutions: • = "8008" • = "2" 2.4.8.66 DIAG8015 : "Unable to stop all APs. The system may be unstable and should be rebooted." 2.
2.4.8.74 DIAG8171 : "PCIe - PCI device in physical Slot , PciTag , is present but not responding" When event is generated, message will have the following substitutions: • = "1" • = "300" 2.4.8.75 DIAG8611 : "User reported not hearing speaker tone" 2.4.8.76 DIAG800B : "Retrieve vendor ID function error." 2.4.8.77 DIAG800C : "Get/Set inverter mode function error. Vendor: Revision: .
2.4.9 Subcategory= Dell Key Mngr [MessageID prefix =DKM] 2.4.9.1 DKM1000 : "A network problem detected. Cannot contact key management server." 2.4.9.2 DKM1001 : "The key management service is operating correctly." 2.4.9.3 DKM1002 : "Key management server certificate problem detected." 2.4.9.4 DKM1004 : "The key management server received a bad request." 2.4.9.5 DKM1006 : "Key management server error detected." 2.4.10 Subcategory= Fan Event [MessageID prefix =FAN] 2.4.10.
2.4.10.8 FAN0007 : "Fan was inserted." When event is generated, message will have the following substitutions: • = "1" 2.4.10.9 FAN0008 : "Fan is present." When event is generated, message will have the following substitutions: • = "1" 2.4.10.10 FAN0009 : "Fan is absent." When event is generated, message will have the following substitutions: • = "1" 2.4.10.11 FAN0010 : "Fan is disabled.
• = "Blower" 2.4.10.18 FAN0017 : " RPM is within normal operating range." When event is generated, message will have the following substitutions: • = "Blower" 2.4.10.19 FAN0018 : "Enhanced Cooling Mode is not supported for fan ." When event is generated, message will have the following substitutions: • = "1" 2.4.10.20 FAN0019 : "An incompatibility between operating mode and fan type was corrected for fan .
2.4.10.26 FAN0026 : "The sensor detected an error with a value of RPM." When event is generated, message will have the following substitutions: • • = "Fan 1" = " 1" 2.4.10.27 FAN0027 : "The sensor has failed with a value of RPM." When event is generated, message will have the following substitutions: • • = "Fan 1" = " 1" 2.4.10.28 FAN0023 : "Unable to read the sensor value.
• = "KVM" 2.4.12.4 HWC1003 : "The is enabled." When event is generated, message will have the following substitutions: • = "KVM" 2.4.12.5 HWC1004 : "The storage adapter is present." 2.4.12.6 HWC1005 : "The storage adapter is absent." 2.4.12.7 HWC1006 : "The storage adapter is disabled." 2.4.12.8 HWC1007 : "The storage adapter is enabled." 2.4.12.9 HWC1008 : "The backplane is present." 2.4.12.10 HWC1009 : "The backplane is absent." 2.4.12.11 HWC1010 : "The backplane is disabled." 2.
2.4.12.19 HWC1200 : "The sled is inserted in slot ." When event is generated, message will have the following substitutions: • = "VGA" • = "1" 2.4.12.20 HWC1201 : "The sled is removed from slot ." When event is generated, message will have the following substitutions: • = "VGA" • = "1" 2.4.12.21 HWC2000 : "The cable or interconnect is connected.
• = "DRAC" 2.4.12.28 HWC2007 : "The is installed correctly." When event is generated, message will have the following substitutions: • = "DRAC" 2.4.12.29 HWC2008 : "A fabric mismatch detected for mezzanine card ." When event is generated, message will have the following substitutions: • = "B1" 2.4.12.30 HWC2009 : "Mezzanine card is installed correctly." When event is generated, message will have the following substitutions: • = "B1" 2.4.12.
• = "IOM" 2.4.12.38 HWC3001 : "The is inserted." When event is generated, message will have the following substitutions: • = "IOM" 2.4.12.39 HWC3002 : "Server is removed." When event is generated, message will have the following substitutions: • = "1" 2.4.12.40 HWC3003 : "Server was inserted." When event is generated, message will have the following substitutions: • = "1" 2.4.12.41 HWC3004 : "IO module is removed.
2.4.12.49 HWC4011 : "Hardware unsuccessfully updated for mezzanine card ." When event is generated, message will have the following substitutions: • = "C2" 2.4.12.50 HWC4012 : "Hardware successfully updated for embedded NIC." 2.4.12.51 HWC4013 : "Hardware unsuccessfully updated for embedded NIC." 2.4.12.52 HWC4014 : "Link Tuning data successfully updated." 2.4.12.53 HWC4015 : "Link Tuning error detected." 2.4.12.54 HWC4016 : "Hardware incompatibility detected with mezzanine card .
2.4.12.59 HWC5002 : "A fabric mismatch detected on ." When event is generated, message will have the following substitutions: • = "IOM" 2.4.12.60 HWC5003 : " is operating correctly." When event is generated, message will have the following substitutions: • = "iDRAC" 2.4.12.61 HWC5004 : "A link tuning failure detected on ." When event is generated, message will have the following substitutions: • = "IOM" 2.4.12.62 HWC5006 : "A failure is detected on .
• = "A1" 2.4.12.69 HWC5032 : "A fabric mismatch detected on IO module ." When event is generated, message will have the following substitutions: • = "A1" 2.4.12.70 HWC5033 : "IO module is operating correctly." When event is generated, message will have the following substitutions: • = "A1" 2.4.12.71 HWC5034 : "A link tuning failure detected on IO module ." When event is generated, message will have the following substitutions: • = "A1" 2.
• = "LCD" 2.4.12.79 HWC6004 : "Cannot communicate with controller." When event is generated, message will have the following substitutions: • = "IOM" 2.4.12.80 HWC6005 : "Communications restored for controller." When event is generated, message will have the following substitutions: • = "IOM" 2.4.12.81 HWC7000 : "Server health changed to a normal state." When event is generated, message will have the following substitutions: • = "1" 2.4.12.
• = "1" 2.4.12.88 HWC8004 : "The SD card device sensor has failed. SD card location: , SD card device type: , SD card state: ." When event is generated, message will have the following substitutions: • = "Main System Chassis" • = " vFlash" • = " NULL" 2.4.12.89 HWC8005 : "The SD card device has returned to normal state. SD card location: , SD card device type: , SD card state: .
• = " NULL" 2.4.12.94 HWC8501 : "Unable to complete the operation because of an issue with the I/O panel cable." 2.4.12.95 HWC8502 : "The I/O panel cable is connected." 2.4.12.96 HWC8503 : "Communication to the control panel has been restored." 2.4.12.97 HWC8504 : "The Chassis Management Controller (CMC) cannot communicate with the control panel." 2.4.12.98 HWC8506 : "Unable to synchronize control panel firmware due to internal error." 2.4.12.
2.4.13.5 IOV108 : "Power fault detected on PCIE adapter in ." When event is generated, message will have the following substitutions: • = "" 2.4.13.6 IOV109 : "An error condition associated with the PCIe slot is cleared." 2.4.13.7 IOV110 : "Successfully updated Chassis Infrastructure firmware." 2.4.13.8 IOV111 : "Unable to update Chassis Infrastructure firmware." 2.4.13.9 IOV112 : "Chassis Infrastructure firmware is not valid." 2.4.13.
• = "" 2.4.13.17 IOV2008 : "The Chassis Management Controller (CMC) is unable to communicate with the PCIe subsystem." 2.4.14 Subcategory= Link Status [MessageID prefix =LNK] 2.4.14.1 LNK0001 : "Network share name unavailable." 2.4.14.2 LNK0002 : "Unable to resolve host name." 2.4.14.3 LNK0003 : "Unable to connect to the DNS server." 2.4.14.4 LNK0004 : "Unable to connect to FTP server." 2.4.14.5 LNK0005 : "Unable to connect to DHCP server." 2.4.14.
• = "Command" 2.4.15.3 LOG323 : "The log size is near maximum capacity. Log type: ." When event is generated, message will have the following substitutions: • = "Command" 2.4.15.4 LOG324 : "The log size has reached its maximum capacity. Log type: ." When event is generated, message will have the following substitutions: • = "Command" 2.4.15.5 LOG325 : "Unable to receive any log entries. Log type: .
2.4.16.6 MEM0005 : "Persistent correctable memory error limit reached for a memory device at location(s) ." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.7 MEM0006 : "Memory device at location is present." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.8 MEM0007 : "Unsupported memory configuration; check memory device at location .
2.4.16.15 MEM0022 : "Memory device at location is absent." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.16 MEM0024 : "Memory device at location is no longer spare memory." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.17 MEM0600 : "Memory device was added at location .
• = "DIMM1" 2.4.16.25 MEM1003 : "Memory device at location failed to transition to in test." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.26 MEM1004 : "Memory device at location is powered off." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.27 MEM1005 : "Memory device at location failed to power off.
• = "DIMM1" 2.4.16.35 MEM1013 : "Memory device at location is in a full state." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.36 MEM1014 : "Memory device at location is in a power save state." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.37 MEM1015 : "Memory device at location is in a power active state.
• = "DIMM1" 2.4.16.46 MEM1206 : "Memory mirror redundancy is degraded. Check memory device at location ." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.47 MEM1207 : "Memory spare is redundant." 2.4.16.48 MEM1208 : "Memory spare redundancy is lost. Check memory device at location ." When event is generated, message will have the following substitutions: • = "DIMM1" 2.4.16.
2.4.16.57 MEM6004 : "Memory device status is critical. Memory device location: , Possible memory module event cause: ." When event is generated, message will have the following substitutions: • = "DIMM_A1" • = " Single bit error logging disabled" 2.4.16.58 MEM6005 : "Memory device has failed. Memory device location: , Possible memory module event cause: .
• = "1" 2.4.16.68 MEM9005 : "Intel SMI 2 Memory interconnect has degraded." When event is generated, message will have the following substitutions: • = "1" 2.4.16.69 MEM9006 : "Intel QPI interconnect has a non-recoverable issue." When event is generated, message will have the following substitutions: • = "1" 2.4.16.70 MEM9007 : "Intel SMI 2 Memory interconnect has a nonrecoverable issue.
2.4.17.3 NIC500 : "The requested object is not allowed to be configured if DHCP \nis enabled." 2.4.17.4 NIC501 : "The requested object is not allowed to be configured if Auto Config \nis enabled." 2.4.17.5 NIC502 : "DHCP is required to be enabled on the NIC before DHCP can be \nenabled for DNS server or domain name objects." 2.4.17.6 NIC503 : "The DNS server IP address is not allowed to be configured \nif DNS server DHCP (cfgDNSServersFromDHCP) is enabled." 2.4.17.
function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 2.4.19.3 PCI1304 : "An I/O channel check error was detected." 2.4.19.4 PCI1306 : "A software error was detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 2.4.19.
• = "1" • = "1" • = "1" 2.4.19.10 PCI1318 : "A fatal error was detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 2.4.19.11 PCI1319 : "A high-severity issue is detected in the SSD bay , Slot ." When event is generated, message will have the following substitutions: • = "1" • = "1" 2.4.19.
2.4.19.16 PCI1344 : "An I/O channel check error was detected." 2.4.19.17 PCI1346 : "A software error was detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 2.4.19.18 PCI1348 : "A PCI parity error was detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 2.4.19.19 PCI1350 : "A PCI system error was detected on a component at slot .
• = "1" • = "1" 2.4.19.26 PCI2001 : "The component at bus device function recovered from a fatal IO error." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 2.4.19.27 PCI2002 : "A fatal IO error detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 2.4.19.
2.4.19.34 PCI3005 : "Device option ROM on mezzanine card was successfully updated." When event is generated, message will have the following substitutions: • = "B1" 2.4.19.35 PCI3006 : "Failed to get Link Tuning or FlexAddress data from iDRAC." 2.4.19.36 PCI3007 : "Link Tuning or FlexAddress data successfully obtained." 2.4.19.37 PCI3008 : "A non-fatal PCIe error detected on a component at bus device function .
• = "1" 2.4.19.44 PCI3015 : "The component at slot recovered from a non-fatal PCIe error." When event is generated, message will have the following substitutions: • = "1" 2.4.19.45 PCI3016 : "Device option ROM on mezzanine card failed to support Link Tuning or FlexAddress." 2.4.19.46 PCI3017 : "Device option ROM on mezzanine card was successfully updated." 2.4.19.47 PCI3018 : "New PCI card(s) have been detected in the system.
• = "" 2.4.19.54 PCI5008 : "The Chassis Management Controller (CMC) is unable to communicate with the PCIe switch board." 2.4.20 Subcategory= Physical Disk [MessageID prefix =PDR] 2.4.20.1 PDR1000 : "Drive is installed in disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 2.4.20.2 PDR1001 : "Fault detected on drive in disk drive bay .
• = "0" 2.4.20.8 PDR1007 : "Rebuild is in progress for drive in disk drive bay ." When event is generated, message will have the following substitutions: • • = "1" = "0" 2.4.20.9 PDR1008 : "Rebuild was aborted for drive in disk drive bay ." When event is generated, message will have the following substitutions: • • = "1" = "0" 2.4.20.10 PDR1016 : "Drive is removed from disk drive bay .
• = "1" • = "0" 2.4.20.16 PDR1023 : "Rebuild completed for drive in disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 2.4.20.17 PDR1024 : "Drive mismatch detected for drive in disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 2.4.20.18 PDR1025 : "Drive mismatch corrected for drive in disk drive bay .
• = "1" 2.4.20.25 PDR1106 : "Drive is in the failed array." When event is generated, message will have the following substitutions: • = "1" 2.4.20.26 PDR1107 : "Rebuild is in progress for drive ." When event is generated, message will have the following substitutions: • = "1" 2.4.20.27 PDR1108 : "Rebuild was aborted for drive ." When event is generated, message will have the following substitutions: • = "1" 2.4.20.
• = "1" 2.4.21 Subcategory= System Performance Event [MessageID prefix =PFM] 2.4.21.1 PFM0001 : "The value of is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "CPU Usage" 2.4.21.2 PFM0002 : "The value of is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "CPU Usage" 2.4.21.
2.4.22 Subcategory= BIOS POST [MessageID prefix =PST] 2.4.22.1 PST0000 : "Unrecognized Post Code." 2.4.22.2 PST0001 : "System Power On." 2.4.22.3 PST0002 : "CPU Microcode load." 2.4.22.4 PST0003 : "Chipset Initialization." 2.4.22.5 PST0004 : "Memory Configuration." 2.4.22.6 PST0005 : "Shadow BIOS." 2.4.22.7 PST0006 : "Multiprocessor Initialization." 2.4.22.8 PST0007 : "POST processing start." 2.4.22.9 PST0008 : "System Management Mode (SMM)initialization." 2.4.22.
• = "1" 2.4.23.2 PSU0001 : "Power supply failed." When event is generated, message will have the following substitutions: • = "1" 2.4.23.3 PSU0002 : "A predictive failure detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 2.4.23.4 PSU0003 : "The power input for power supply is lost." When event is generated, message will have the following substitutions: • = "1" 2.4.23.
2.4.23.11 PSU0022 : "Power supply is correctly configured." When event is generated, message will have the following substitutions: • = "1" 2.4.23.12 PSU0023 : "Power supply operating at 110 volts has been acknowledged by user." When event is generated, message will have the following substitutions: • = "1" 2.4.23.13 PSU0031 : "Cannot communicate with power supply ." When event is generated, message will have the following substitutions: • = "1" 2.
• = "1" 2.4.23.21 PSU0039 : "An under current fault detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 2.4.23.22 PSU0040 : "An output under voltage fault detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 2.4.23.23 PSU0041 : "An output over voltage fault detected on power supply .
2.4.23.30 PSU0077 : "Power supply vendor type mismatch detected." When event is generated, message will have the following substitutions: • = "1" 2.4.23.31 PSU0078 : "Power supply revision mismatch detected." When event is generated, message will have the following substitutions: • = "1" 2.4.23.32 PSU0080 : "Power supply voltage rating does not match the systems requirements.
2.4.23.39 PSU500 : "Unable to get the current server power status." 2.4.23.40 PSU501 : "Server is already powered ON." 2.4.23.41 PSU502 : "Server is already powered OFF." 2.4.23.42 PSU503 : "Server power status: " When event is generated, message will have the following substitutions: • = "ON" 2.4.23.43 PSU504 : "Server power operation successful" 2.4.23.
• = "1" 2.4.23.51 PSU0904 : "Could not power down 240VA on power unit ." When event is generated, message will have the following substitutions: • = "1" 2.4.23.52 PSU0906 : "An interlock power down error detected on power unit ." When event is generated, message will have the following substitutions: • = "1" 2.4.23.53 PSU0907 : "An interlock power down error was corrected for power unit .
• = "1" 2.4.24 Subcategory= PSU Absent [MessageID prefix =PSUA] 2.4.24.1 PSUA0016 : "Power supply is absent." When event is generated, message will have the following substitutions: • = "1" 2.4.25 Subcategory= Power Usage [MessageID prefix =PWR] 2.4.25.1 PWR0100 : "The power button was pressed." 2.4.25.2 PWR0101 : "The power button was released." 2.4.25.3 PWR0102 : "The sleep button was pressed." 2.4.25.4 PWR0103 : "The sleep button was released." 2.4.25.
2.4.25.11 PWR200 : "Enabling the Max Power Conservation Mode (MPCM) feature will disable the Extended Power Performance (EPP) feature." 2.4.25.12 PWR201 : "Selecting the Server Based Power Management Mode option sets your power cap to a maximum value, server priorities to a default priority, and then disables the Max Power Conservation Mode. Do you want to continue?" 2.4.25.
• = "" 2.4.25.27 PWR220 : "The Extended Power Performance (EPP) feature cannot be enabled because slot is empty.
2.4.25.28 PWR221 : "The Extended Power Performance (EPP) feature is already disabled." 2.4.25.29 PWR222 : "The Extended Power Performance (EPP) feature is already enabled." 2.4.25.30 PWR223 : "Cannot perform a 110V AC operation because the Extended Power Performance (EPP) feature is enabled." 2.4.25.31 PWR1000 : "The system performance restored." 2.4.25.32 PWR1001 : "The system performance degraded." 2.4.25.33 PWR1002 : "The system performance degraded because of thermal protection." 2.4.25.
maintained." 2.4.25.51 PWR2202 : "The system is sleeping with lost processor context." 2.4.25.52 PWR2203 : "The system is sleeping with system hardware and processor context lost." 2.4.25.53 PWR2204 : "The system is in a non-volatile sleep state." 2.4.25.54 PWR2205 : "The system is in a soft-off state." 2.4.25.55 PWR2207 : "The system is in a mechanical off state." 2.4.25.56 PWR2208 : "The system is in a sleep state." 2.4.25.57 PWR2209 : "The system is in an undermined sleep state." 2.4.25.
2.4.25.67 PWR8557 : "The System Input Power Cap is too low to be enforced using the current Power Supply configuration." 2.4.25.68 PWR8558 : "The System Input Power Cap is being enforced with the current Power Supply configuration." 2.4.26 Subcategory= RAC Event [MessageID prefix =RAC] 2.4.26.1 RAC0560 : "RAC Software Initialization Error" 2.4.26.2 RAC0561 : "iDRAC to CMC communication link is not functioning for agent free monitoring of chassis PCIe slots." 2.4.26.
• = "12v" 2.4.27.20 RDU0031 : "The voltage redundancy is lost." When event is generated, message will have the following substitutions: • = "12v" 2.4.27.21 RDU0032 : "The voltage redundancy is degraded." When event is generated, message will have the following substitutions: • = "12v" 2.4.27.22 RDU0033 : "The voltage is not redundant." When event is generated, message will have the following substitutions: • = "12v" 2.4.
2.4.28.7 RFL2007 : "Internal Dual SD Module is writable." When event is generated, message will have the following substitutions: • = "SD1" 2.4.28.8 RFL2008 : "Internal Dual SD Module is disabled." When event is generated, message will have the following substitutions: • = "SD1" 2.4.28.9 RFL2009 : "Internal Dual SD Module is enabled." When event is generated, message will have the following substitutions: • = "SD2" 2.4.
2.4.30 Subcategory= FlexAddress SD [MessageID prefix =RFM] 2.4.30.1 RFM1018 : "Removable Flash Media is absent." 2.4.30.2 RFM1019 : "Removable Flash Media is present." 2.4.30.3 RFM1020 : "Removable Flash Media is IPMI-function ready." 2.4.30.4 RFM1021 : "Removable Flash Media is not IPMI-function ready." 2.4.30.5 RFM1022 : "Removable Flash Media is ready." 2.4.30.6 RFM1023 : "Removable Flash Media is not ready." 2.4.30.7 RFM1024 : "Removable Flash Media is offline." 2.4.30.
Module." 2.4.32 Subcategory= Security Event [MessageID prefix =SEC] 2.4.32.1 SEC0000 : "The chassis is open." 2.4.32.2 SEC0001 : "The drive bay is open." 2.4.32.3 SEC0002 : "The I/O card area is open." 2.4.32.4 SEC0003 : "The processor area is open." 2.4.32.5 SEC0004 : "The LAN is disconnected." 2.4.32.6 SEC0005 : "Unauthorized docking is detected." 2.4.32.7 SEC0006 : "The fan area is open." 2.4.32.8 SEC0016 : "The chassis is closed." 2.4.32.9 SEC0017 : "The drive bay is closed." 2.4.32.
Technology (TXT) problem at boot." 2.4.32.24 SEC0045 : "Intel Trusted Execution Technology (TXT) is operating correctly." 2.4.32.25 SEC0051 : "Unable to determine the redundancy status of the chassis intrusion sensor." 2.4.32.26 SEC0052 : "Chassis intrusion sensor may have failed." 2.4.32.27 SEC0600 : "A secure mode violation detected." 2.4.32.28 SEC0601 : "A secure mode violation was corrected." 2.4.32.29 SEC0602 : "User password violation detected." 2.4.32.
address>." When event is generated, message will have the following substitutions: • = "root" • = "192.168.1.
2.4.33.11 SEL1200 : "The system was reconfigured." 2.4.33.12 SEL1202 : "OEM system boot." 2.4.33.13 SEL1204 : "An unknown system hardware failure detected." 2.4.33.14 SEL1205 : "The unknown system hardware failure was corrected." 2.4.33.15 SEL1206 : "An entry was added to auxiliary log." 2.4.33.16 SEL1207 : "An entry was removed from auxiliary log." 2.4.33.17 SEL1208 : "A platform event filter action was executed." 2.4.33.18 SEL1209 : "The platform event filter action failed." 2.4.33.
Insufficient resources to maintain normal operations." 2.4.33.40 SEL1506 : "Lost communications with Chassis Group Member ." When event is generated, message will have the following substitutions: • = "1" 2.4.33.41 SEL1507 : "Communications restored with Chassis Group Member ." When event is generated, message will have the following substitutions: • = "1" 2.4.33.42 SEL1508 : "Member could not join the Chassis Group.
• = "1" 2.4.34.4 SWC4005 : "A firmware or software incompatibility was corrected between iDRAC in slot and CMC." When event is generated, message will have the following substitutions: • = "1" 2.4.34.5 SWC4006 : "A firmware or software incompatibility detected between system BIOS in slot and CMC." When event is generated, message will have the following substitutions: • = "1" 2.4.34.
• = " BIOS" • = " in slot 1" 2.4.34.12 SWC4013 : "A firmware or software incompatibility was corrected between and .
2.4.34.16 SWC5003 : "System Controller (SC) has either stopped functioning or is updating a firmware version." 2.4.34.17 SWC5004 : "System Controller (SC) has restarted functioning." 2.4.35 Subcategory= System Info [MessageID prefix =SYS] 2.4.35.1 SYS083 : "Unable to export ePSA Diagnostics results because iDRAC internal storage could not be accessed." 2.4.35.
• = " present" • = " present" 306
2.4.35.14 SYS115 : "The power cord sensor is non-functional." 2.4.35.15 SYS116 : "Unable to determine the status of the power cord." 2.4.35.16 SYS117 : "The input power supply is restored." 2.4.35.17 SYS118 : "The input power supply is not available." 2.4.35.18 SYS119 : "Unable to expose the OS Collector to the server OS." 2.4.35.19 SYS120 : "Unable to complete the operation because the OS Collector is taking too much time. The operation is cancelled." 2.4.35.
Lifecycle Controller is not enabled." 2.4.35.37 SYS138 : "Unable to start the collection of OS and Application Data because the server is turned off." 2.4.35.38 SYS139 : "Unable to start the collection of OS and Application Data because the server is in POST and has not finished startup." 2.4.35.39 SYS140 : "Unable to start the collection of OS and Application Data because the iDRAC Service Module (iSM) is not running in the server OS." 2.4.35.
2.4.35.51 SYS181 : "Unable to collect OS and Application Data because the OS Collector is not installed on the iDRAC." 2.4.35.52 SYS182 : "Unable to collect OS and Application Data because another Lifecycle Controller operation is currently in progress." 2.4.35.53 SYS183 : "Unable to allocate memory because of insufficient storage space in iDRAC." 2.4.35.54 SYS184 : "Unable to compute the checksum because OS Collector files are not readable." 2.4.35.
• = "Inlet" 2.4.36.6 TMP0105 : "The system board temperature is within range." When event is generated, message will have the following substitutions: • = "Inlet" 2.4.36.7 TMP0106 : "The memory module temperature is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "1" 2.4.36.8 TMP0107 : "The memory module temperature is less than the lower critical threshold.
• = "Planer" 2.4.36.15 TMP0114 : "The temperature is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "Planer" 2.4.36.16 TMP0115 : "The temperature is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "Planer" 2.4.36.17 TMP0116 : "The temperature is outside of range.
2.4.36.19 TMP0118 : "The system inlet temperature is less than the lower warning threshold." 2.4.36.20 TMP0119 : "The system inlet temperature is less than the lower critical threshold." 2.4.36.21 TMP0120 : "The system inlet temperature is greater than the upper warning threshold." 2.4.36.22 TMP0121 : "The system inlet temperature is greater than the upper critical threshold." 2.4.36.23 TMP0122 : "The system inlet temperature is outside of range." 2.4.36.
• = "1" 2.4.36.41 TMP0201 : "CPU temperature is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "1" 2.4.36.42 TMP0202 : "CPU temperature is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "1" 2.4.36.43 TMP0203 : "CPU temperature is greater than the upper critical threshold.
2.4.36.51 TMP502 : "The sensor has returned to a normal state with a value of degrees Celsius." When event is generated, message will have the following substitutions: • = "System Board Inlet Temp" • = " 27" 2.4.36.52 TMP503 : "The sensor state has changed to a warning state with a value of degrees Celsius.
2.4.37 Subcategory= Temperature Statistics [MessageID prefix =TMPS] 2.4.37.1 TMPS0100 : "Inlet temperature is above warning level for extended duration." 2.4.37.2 TMPS0101 : "Inlet temperature is above critical level for extended duration." 2.4.37.3 TMPS0102 : "Inlet temperature is above warning level for extended duration." 2.4.37.4 TMPS0103 : "Inlet temperature is above critical level for extended duration." 2.4.38 Subcategory= UEFI Event [MessageID prefix =UEFI] 2.4.38.
in Recovery mode." 2.4.38.19 UEFI0018 : "Lifecycle Controller (LC) is unable to complete a requested task or function and therefore is in Recovery Mode." 2.4.38.20 UEFI0019 : "Lifecycle Controller (LC) is unable to complete a requested task or function and prevented the boot process from completing on multiple attempts. LC is in Recovery Mode." 2.4.38.21 UEFI0022 : "Unable to initialize Management Engine because the Management Engine is not responding." 2.4.38.
2.4.38.29 UEFI0032 : "Unable to initialize the TPM chip because the TPM chip is not functioning." 2.4.38.30 UEFI0034 : "A CMOS battery loss is detected resulting in an invalid BIOS configuration." 2.4.38.31 UEFI0036 : "Unable to initialize the iDRAC Shared Memory Architecture (SMA) interface." 2.4.38.32 UEFI0037 : "Unable to communicate with iDRAC because of an issue in the iDRAC Shared Memory Architecture (SMA) Intelligent Platform Management Interface (IPMI)." 2.4.38.
• = "Bus: 0 Dev: 0 Func: 18" 2.4.38.47 UEFI0067 : "A PCIe link training failure is observed in and device link is disabled." When event is generated, message will have the following substitutions: • = "Bus: 4 Dev: 0 Func: 0" 2.4.38.48 UEFI0069 : "A CMOS checksum error has occurred. CMOS is reinitialized." 2.4.38.49 UEFI0070 : "One or more correctable PCIe errors have occurred." 2.4.38.50 UEFI0076 : "One or more Corrected Machine Check(CMC) errors have occurred.
2.4.38.61 UEFI0106 : "One or more memory correctable training errors have occurred on memory slot: " When event is generated, message will have the following substitutions: • = "A1" 2.4.38.62 UEFI0107 : "One or more memory errors have occurred on memory slot: ." When event is generated, message will have the following substitutions: • = "A2" 2.4.38.63 UEFI0108 : "One or more memory errors have occurred on memory slot: .
2.4.38.68 UEFI0115 : "The Management Engine firmware has recovered from one or more correctable errors." 2.4.38.69 UEFI0116 : "One or more boot drivers have reported issue(s)." 2.4.38.70 UEFI0117 : "Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 1." 2.4.38.71 UEFI0118 : "Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 2." 2.4.38.
Controller (LC) firmware was not accessible." 2.4.38.86 UEFI0142 : "Unable to enter System Service Mode (SSM) because the Lifecycle Controller (LC) firmware was unable to complete a requested task or function." 2.4.38.87 UEFI0144 : "One or more memory errors have occurred on memory slot: ." When event is generated, message will have the following substitutions: • = "A1" 2.4.38.88 UEFI0146 : "Unable to verify the chassis type via iDRAC and CMC.
2.4.40.3 VFL0005 : "No vFlash partitions exist." 2.4.40.4 VFL0007 : "No vFlash SD card is present." 2.4.40.5 VFL0009 : "vFlash media is currently in use by another operation." 2.4.40.6 VFL0010 : "An operation is in progress on the SD card." 2.4.40.7 VFL0011 : "vFlash media is not disabled." 2.4.40.8 VFL0012 : "vFlash media is not enabled." 2.4.40.9 VFL0013 : "The vFlash SD Card is in read-only mode." 2.4.40.10 VFL0014 : "The vFlash SD card is not initialized." 2.4.40.
• = "vFlash" 2.4.40.20 VFL1006 : "Removable Flash Media is offline." When event is generated, message will have the following substitutions: • = "vFlash" 2.4.40.21 VFL1007 : "Removable Flash Media is online." When event is generated, message will have the following substitutions: • = "vFlash" 2.4.40.22 VFL1008 : "Failure detected on Removable Flash Media ." When event is generated, message will have the following substitutions: • = "vFlash" 2.4.40.
• = "vFlash" 2.4.40.30 VFL1016 : "Media not present for Removable Flash Media ." When event is generated, message will have the following substitutions: • = "vFlash" 2.4.40.31 VFL1017 : "Media is present for Removable Flash Media ." When event is generated, message will have the following substitutions: • = "vFlash" 2.4.41 Subcategory= vFlash Absent [MessageID prefix =VFLA] 2.4.41.1 VFLA1000 : "Removable Flash Media is absent.
2.4.42.6 VLT0105 : "Processor module voltage is within range." When event is generated, message will have the following substitutions: • = "3.2" 2.4.42.7 VLT0200 : "The system board voltage is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "VRM" 2.4.42.8 VLT0201 : "The system board voltage is less than the lower critical threshold.
• = "A" • = "VRM" 2.4.42.15 VLT0208 : "The memory module voltage is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "A" • = "VRM" 2.4.42.16 VLT0209 : "The memory module voltage is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "A" • = "VRM" 2.4.42.
2.4.42.22 VLT0215 : "The disk drive bay voltage is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "VRM" 2.4.42.23 VLT0216 : "The disk drive bay voltage is outside of range." When event is generated, message will have the following substitutions: • = "VRM" 2.4.42.24 VLT0217 : "The disk drive bay voltage is within range.
• = "A" 2.4.42.32 VLT0225 : "The memory module voltage is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "A" 2.4.42.33 VLT0226 : "The memory module voltage is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "A" 2.4.42.34 VLT0227 : "The memory module voltage is greater than the upper critical threshold.
• = "VRM" 2.4.42.40 VLT0233 : "The mezzanine card voltage is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "B1" • = "VRM" 2.4.42.41 VLT0234 : "The mezzanine card voltage is outside of range." When event is generated, message will have the following substitutions: • = "B1" • = "VRM" 2.4.42.
2.4.42.47 VLT0304 : "CPU voltage is outside of range." When event is generated, message will have the following substitutions: • = "1" • = "VRM" 2.4.42.48 VLT0305 : "CPU voltage is within range." When event is generated, message will have the following substitutions: • = "1" • = "VRM" 2.4.42.49 VLT400 : "The sensor has failed with a value Volts.
• = " 2" 2.4.43 Subcategory= Virtual Console [MessageID prefix =VRM] 2.4.43.1 VRM0009 : "No Virtual Media devices are currently connected." 2.4.43.2 VRM0010 : "Unable to disconnect Virtual Media devices." 2.4.43.3 VRM0011 : "The Virtual Media image server is not currently connected." 2.4.43.4 VRM0012 : "The Virtual Media image server is already connected." 2.4.43.5 VRM0013 : "Virtual Media services is currently attached to the USB interface.
2.5.1 Subcategory= Job Control [MessageID prefix =JCP] 2.5.1.1 JCP000 : "New" 2.5.2 Subcategory= Lifecycle Contr [MessageID prefix =LC] 2.5.2.1 LC043 : "Work note contains non-printable or reserved characters." 2.5.3 Subcategory= RAC Event [MessageID prefix =RAC] 2.5.3.1 RAC0707 : "Primary Firmware image is invalid. Currently booted from backup image. To restore primary image, update the firmware." 2.5.3.2 RAC0724 : "Quick Sync Firmware is successfully updated." 2.5.3.
was found on the Lifecycle Controller." 2.5.4.21 RED020 : "Feature not supported on current version of USC." 2.5.4.22 RED021 : "The component InstanceID specified is not present on the system." 2.5.4.23 RED022 : "Version compatibility check was not successful." 2.5.4.24 RED023 : "Lifecycle Controller in use. This job will start when Lifecycle Controller is available." 2.5.4.25 RED024 : "The specified job starts when Lifecycle Controller is available." 2.5.4.
• = "Firmware updates available : Enterprise UEFI Diagnostics, 4225A2, 4225.4, OS Drivers Pack, 7.2.0.7, A00, BIOS" 2.5.4.38 RED037 : "All components firmware match with the specified remote repository." 2.5.4.39 RED038 : "A recurring task of type is added." When event is generated, message will have the following substitutions: • = "AutoTask" 2.5.4.40 RED039 : "Settings for a recurring operation of type were cleared.
• = "AutoTask" 2.5.4.47 RED046 : "A recurring operation of type was unable to create a job because the task type is now disabled." When event is generated, message will have the following substitutions: • = "AutoTask" 2.5.4.48 RED047 : "A recurring operation was not created because the operation is already configured." When event is generated, message will have the following substitutions: • = "AutoTask" 2.5.4.
2.5.4.57 RED056 : "An internal error occurred. Unable to complete the specified operation." 2.5.4.58 RED057 : "An internal error occurred. Unable to complete the specified operation." 2.5.4.59 RED058 : "A repository update job was created." When event is generated, message will have the following substitutions: • = "JID" 2.5.4.60 RED059 : "Unable to create an update job for .
2.5.4.70 RED076 : "Unable to create an Automatic Update schedule, because an invalid parameter is entered." 2.5.4.71 RED077 : "Unable to get the Automatic Update schedule information." 2.5.4.72 RED078 : "Unable to delete the Automatic Update schedule." 2.5.4.73 RED079 : "The input value entered for the parameter is invalid." When event is generated, message will have the following substitutions: • = "Param1" 2.5.4.74 RED080 : "The required parameter is not present.
• = "Component" • = "Available" • = "Current" 2.5.4.87 RED093 : "The requested job cannot be scheduled because Lifecycle Controller is not enabled." 2.5.4.88 RED094 : "Updating firmware for from version to version .
2.5.4.89 RED095 : "rSPI update for Diags failed." 2.5.4.90 RED0101 : "Rollback successfull." 2.5.5 Subcategory= FW Update Job [MessageID prefix =SUP] 2.5.5.1 SUP001 : "Insufficient parameters provided." 2.5.5.2 SUP002 : "Job creation failure." 2.5.5.3 SUP003 : "Invalid URI, target or reboot flag." 2.5.5.4 SUP005 : "Invalid reboot value." 2.5.5.5 SUP006 : "Update package downloading - Delete failed." 2.5.5.6 SUP007 : "iDRAC busy - Delete failed." 2.5.5.
• = "Param1" 2.5.5.
2.5.5.23 SUP028 : "The GetRepoBasedUpdateList method did not complete successfully." 2.5.5.24 SUP029 : "Firmware versions on server match catalog, applicable updates are not present in the repository." 2.5.5.25 SUP030 : "Proxy IP and User Credential pare valid only if the ProxySupport parameter is TRUE." 2.5.5.26 SUP0100 : "Firmware update operation failed." 2.5.5.27 SUP0101 : "Unable to get firmware update status." 2.5.5.28 SUP0102 : "Invalid TFTP IP address specified." 2.5.5.
complete]" When event is generated, message will have the following substitutions: • = "50" 342
2.5.5.48 SUP0122 : "Firmware update completed successfully" 2.5.5.49 SUP0123 : "Firmware update completed successfully. The RAC is in the process of \nresetting. Your connection will be lost. Please wait up to a minute before starting a new session." 2.5.5.50 SUP0124 : "Firmware update is not currently in progress" 2.5.5.51 SUP0125 : "Current firmware update status is unknown" 2.5.5.52 SUP0126 : "Firmware update in progress. Please wait..." 2.5.5.53 SUP0127 : "Verifying firmware image" 2.5.5.
• = "Lifecycle Controller" • = "1.1.0.726, X12" 2.5.5.70 SUP0517 : "Unable to update the firmware to version ." When event is generated, message will have the following substitutions: • = "Lifecycle Controller" • = "1.1.0.726, X12" 2.5.5.71 SUP0518 : "Successfully updated the firmware to version .
2.5.5.74 SUP0522 : "Unable to update the BIOS firmware because write protection is enabled." 2.5.5.75 SUP0525 : "Unable to verify the digital signature of the Update Package." 2.5.5.76 SUP0526 : "Unable to continue with firmware update." 2.5.5.77 SUP0527 : "The Update Package is not supported for this system." 2.5.5.78 SUP0528 : "Unable to generate a firmware comparison table." 2.5.5.79 SUP0529 : "Unable to access repository." 2.5.5.80 SUP0530 : "Incorrect repository path location." 2.5.5.
2.5.5.89 SUP0539 : "Update Packages missing in the repository." 2.5.5.90 SUP1901 : "Firmware update initializing." 2.5.5.91 SUP1902 : "Firmware update stopping services." 2.5.5.92 SUP1903 : "Firmware update verify image headers." 2.5.5.93 SUP1904 : "Firmware update checksumming image." 2.5.5.94 SUP1905 : "Firmware update programming flash." 2.5.5.95 SUP1906 : "Firmware update successful." 2.5.5.96 SUP1907 : "Firmware update failed." 2.5.5.97 SUP1908 : "Firmware update failed checksum." 2.5.5.
2.5.7.3 SWU8502 : "A request was submitted to the Lifecycle Controller on server ." When event is generated, message will have the following substitutions: • = "" 2.5.7.4 SWU8503 : "A reinstall/rollback request was submitted to the Lifecycle Controller on server ." When event is generated, message will have the following substitutions: • = "" 2.5.7.
2.5.7.11 SWU8516 : "Unable to update the iDRAC firmware on the server in slot . Transfer is not successful. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 2.5.7.12 SWU8517 : "Unable to update the iDRAC firmware on the server in slot . The Image file is not accessible. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 2.5.7.
2.5.7.19 SWU8524 : "Unable to update the iDRAC on the server in slot firmware: ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 2.5.7.20 SWU8525 : "Unable to update the iDRAC firmware on the server in slot . The firmware update timeout limit is exceeded." When event is generated, message will have the following substitutions: • = "" 2.5.7.
• = "" 2.5.7.31 SWU8536 : "Unable to update the LKVM firmware, because the Image file could not be accessed. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 2.5.7.32 SWU8537 : "Unable to update the LKVM firmware, because the IP address provided is invalid. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 2.5.7.33 SWU8538 : "Unable to update the iKVM firmware.
2.5.7.36 SWU8542 : "Unable to update the Active CMC firmware. The Image file transfer process was not successful." 2.5.7.37 SWU8543 : "Unable to update the Active CMC firmware. The Image file was not accessible." 2.5.7.38 SWU8544 : "Unable to update the Standby CMC firmware because the Standby CMC could not be prepared for firmware update." 2.5.7.39 SWU8545 : "Unable to update the Standby CMC firmware." 2.5.7.40 SWU8546 : "Unable to update the Standby CMC firmware." 2.5.7.
automatically turned off in 5 seconds." 2.6 Category: Work Notes 2.6.1 Subcategory= UEFI Event [MessageID prefix =UEFI] 2.6.1.1 UEFI0050 : "The process of collecting Brand information is started." 2.6.1.2 UEFI0051 : "Brand information is successfully collected. The system is being restarted." 2.6.1.3 UEFI0053 : "The debranding process is started." 2.6.1.4 UEFI0054 : "Debranding process is completed. The system is being restarted." 2.6.2 Subcategory= User Tracking [MessageID prefix =USR] 2.6.2.
3.0 SNMP Trap Event Notification Test Messages 3 3.1 Category: Audit 3.1.1 Subcategory= BIOS Management [MessageID prefix =BIOS] 3.1.1.1 BIOS102 : "A system BIOS update is scheduled that requires a reboot." 3.1.1.2 BIOS103 : "A previously scheduled system BIOS update is canceled." 3.1.2 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 3.1.2.1 CMC8506 : "A command to shut down the CMC was initiated." 3.1.2.
3.1.2.6 CMC8511 : "Unable to synchronize the data in the Extended Storage removable flash media in the primary and secondary CMCs." 3.1.2.7 CMC8512 : "The Extended Storage feature activation timed out. The feature is not active." 3.1.2.8 CMC8513 : "The Extended Storage feature activation on the secondary CMC timed out. The feature is being returned to single CMC mode." 3.1.2.9 CMC8529 : "Unable to perform the requested action on the server-, because of insufficient privileges.
• = "" 3.1.2.17 CMC8542 : "The CMC was restarted because of a manual reset." When event is generated, message will have the following substitutions: • = "" 3.1.2.18 CMC8543 : "The CMC has reset because the thermal threshold was exceeded." When event is generated, message will have the following substitutions: • = "" 3.1.2.19 CMC8545 : "Detected a missing process failover condition detected. Process = .
3.1.2.25 CMC8553 : "An internal error occurred and a failover condition is detected." 3.1.2.26 CMC8554 : "An internal network error occurred." 3.1.2.27 CMC8555 : "An internal memory error has occurred and a failover condition is detected." 3.1.2.28 CMC8557 : "The system health failover is requested. Code ." When event is generated, message will have the following substitutions: • = "" 3.1.2.29 CMC8558 : "The system health is restored." 3.1.2.
• = "" 3.1.2.39 CMC8570 : "The server slot is disabled for DVD drive mapping." When event is generated, message will have the following substitutions: • = "" 3.1.2.40 CMC8571 : "The coin cell battery in the primary CMC is not working." 3.1.2.41 CMC8572 : "The coin cell battery in CMC is not working." When event is generated, message will have the following substitutions: • = "" 3.1.2.42 CMC8573 : "The chassis health is .
• = "admin" 3.1.3.4 DKM0004 : "DKM Error Code : error." When event is generated, message will have the following substitutions: • = "07" • = "Invalid Key format" 3.1.4 Subcategory= Fan Event [MessageID prefix =FAN] 3.1.4.1 FAN8500 : "Enhanced Cooling Mode is Enabled" 3.1.4.2 FAN8501 : "Enhanced Cooling Mode is Disabled" 3.1.4.3 FAN8502 : "The blower is not detected, because it may not be operating optimally.
• = "" 3.1.6 Subcategory= Debug [MessageID prefix =FSD] 3.1.6.1 FSD000 : "Debug authorized by customer; debugcaps: , was authorized by: , at for the period: to ." When event is generated, message will have the following substitutions: • = "DebugCaps" • = "iDRAC User" • = "unblock time" • = "start time" • = " end time" 3.1.6.
3.1.7.2 HWC8001 : "A device was added to the system at this location: . Additional Details: ." When event is generated, message will have the following substitutions: • = "VFlash" • = " NULL" 3.1.7.3 HWC8002 : "The device was removed from the system at this location: . Additional Details: ." When event is generated, message will have the following substitutions: • = "VFlash" • = " NULL" 3.1.7.
• = "USB-NIC" 3.1.10.3 ISM0002 : "The OS to iDRAC Pass-through is disabled. The iDRAC Service Module is currently enabling the OS to iDRAC Pass-through in the USB NIC mode." 3.1.10.4 ISM0003 : "The iDRAC Service Module is unable to discover iDRAC from the operating system of the server." 3.1.10.5 ISM0004 : "The iDRAC Service Module has successfully started communication with iDRAC." 3.1.10.6 ISM0005 : "The iDRAC Service Module has successfully restarted communication with iDRAC." 3.1.10.
3.1.10.16 ISM0015 : "The iDRAC Service Module detected a change in the host name of the server operating system (OS)." 3.1.10.17 ISM0016 : "The BMC watchdog reset time is changed to seconds." When event is generated, message will have the following substitutions: • = "5" 3.1.10.18 ISM0017 : "The BMC watchdog auto-recovery action is changed from to .
3.1.12 Subcategory= Licensing [MessageID prefix =LIC] 3.1.12.1 LIC000 : "The License Manager action succeeded." 3.1.12.2 LIC001 : "The License Manager command parameter used is invalid." 3.1.12.3 LIC002 : "License Manager is unable to allocate the required resources at startup." 3.1.12.4 LIC003 : "License Manager was unable to create and/or allocate the required resources." 3.1.12.5 LIC004 : "An internal system error has occurred." 3.1.12.
operation." 3.1.12.24 LIC201 : "License assigned to device expires in days." When event is generated, message will have the following substitutions: • = "DE00000000825991" • = "iDRAC" • = "5" 3.1.12.25 LIC202 : "A system error was detected during License Manager startup." 3.1.12.26 LIC203 : "The license has encountered an error.
3.1.12.33 LIC210 : "License deleted from device successfully." When event is generated, message will have the following substitutions: • = "DE00000000825991" • = "iDRAC" 3.1.12.34 LIC211 : "The iDRAC feature set has changed." 3.1.12.35 LIC212 : "The CMC features are changed." 3.1.12.36 LIC213 : "A system error was detected during License Manager startup." 3.1.12.37 LIC501 : "A required license is missing or expired." 3.1.12.
3.1.13.6 LOG326 : "The Alert Log was cleared." 3.1.13.7 LOG327 : "An Alert Log backup was created." 3.1.13.8 LOG328 : "The Server Based Management Mode is enabled." 3.1.13.9 LOG329 : "The Server Based Management Mode is disabled." 3.1.14 Subcategory= Memory [MessageID prefix =MEM] 3.1.14.1 MEM8500 : "Low memory condition detected." 3.1.14.2 MEM8501 : "Low memory warning, KB, KB.
• = "" 3.1.17.2 PSU8502 : "The PSU in slot detected 110 VAC input voltage and does not match chassis configuration." When event is generated, message will have the following substitutions: • = "" 3.1.17.3 PSU8503 : "The PSU in slot detected 220 VAC input voltage and does not match chassis configuration." When event is generated, message will have the following substitutions: • = "" 3.1.17.
3.1.17.12 PSU8513 : "Unable to complete the PSU slot firmware update. Error=0x." When event is generated, message will have the following substitutions: • = "" 3.1.17.13 PSU8515 : "Unable to set the Enable Dynamic Power Supply Engagement attribute." 3.1.17.14 PSU8516 : "Unable to set redundancy policy because PSU enumeration is in progress." 3.1.17.15 PSU8517 : "PSU redundancy policy changed." 3.1.17.16 PSU8518 : "Unable to access the PSU FRU data.
3.1.18 Subcategory= Power Usage [MessageID prefix =PWR] 3.1.18.1 PWR2250 : "Unable to turn on the server because the chassis infrastructure not ready." 3.1.18.2 PWR2251 : "Unable to turn on the server because the chassis cover is open." 3.1.18.3 PWR2252 : "Unable to turn on the server because an NDC or Mezzanine card is incompatible with the I/O Module or PCIe subsystem." 3.1.18.4 PWR2253 : "Unable to turn on the server because a PCIe card or Mezzanine card is not installed." 3.1.18.
3.1.18.12 PWR2262 : "The Intel Management Engine has reported an internal system error." 3.1.18.13 PWR2263 : "User ignored Power Supply Oversubscription Warning." 3.1.18.14 PWR2404 : "Power supply capacity alert disabled." 3.1.18.15 PWR8500 : "Chassis power state updated to from ." When event is generated, message will have the following substitutions: • = "" 3.1.18.
3.1.18.23 PWR8509 : "Unable to change the server power priority because Server Based Power Management mode is enabled." 3.1.18.24 PWR8510 : "Unable to set chassis power property .
3.1.18.25 PWR8511 : "Unable to set the CHASSIS_POWER_button_disable chassis power property." 3.1.18.26 PWR8512 : "CMC rebooted, because the power configuration data could not be accessed." 3.1.18.27 PWR8514 : "Unable to perform chassis power action due to insufficient privileges." 3.1.18.28 PWR8515 : "Unable to perform the chassis power action because the chassis is not turned on." 3.1.18.29 PWR8516 : "Unable to perform the chassis power action requested.." 3.1.18.
AC." When event is generated, message will have the following substitutions: • = "" 3.1.18.47 PWR8534 : "Unable to set Server Based Power Management Mode to enable." 3.1.18.48 PWR8535 : "Unable to set Server Based Power Management Mode to disable." 3.1.18.49 PWR8536 : "Server Performance Over Power Redundancy is enabled." 3.1.18.50 PWR8537 : "Server Performance Over Power Redundancy is disabled." 3.1.18.51 PWR8538 : "Power Remote Logging is enabled." 3.1.18.
3.1.18.59 PWR8546 : "Chassis shutdown already in progress." 3.1.18.60 PWR8547 : "Chassis is already powered off." 3.1.18.61 PWR8548 : "Chassis shutdown operation initiated." 3.1.18.62 PWR8549 : "Chassis shutdown did not complete successfully." 3.1.18.63 PWR8550 : "Chassis shutdown completed." 3.1.18.64 PWR8551 : "Successfully set Virtual Infrastructure Device power to DC Watt." When event is generated, message will have the following substitutions: • = "" 3.1.18.
• = "" 3.1.18.71 PWR8561 : "Unable to power on server because of iDRAC communication issue." When event is generated, message will have the following substitutions: • = "" 3.1.18.72 PWR8562 : "Unable to power on the server before power on timer expired." When event is generated, message will have the following substitutions: • = "" 3.1.18.
3.1.18.79 PWR8569 : "Unable to power cycle the server because the server is off." When event is generated, message will have the following substitutions: • = "" 3.1.18.80 PWR8570 : "Unable to communicate to the iDRAC, when trying to power cycle the server ." When event is generated, message will have the following substitutions: • = "" 3.1.18.
• = "" 3.1.18.88 PWR8578 : "Chassis Management Controller is unable to turn on the iDRAC on server- because power required is less than available power." When event is generated, message will have the following substitutions: • = "" 3.1.18.89 PWR8579 : "Request to reset the CMC is initiated." When event is generated, message will have the following substitutions: • = "" 3.1.18.
3.1.18.96 PWR8586 : "Chassis Management Controller is unable to turn on server- because it is not supported in the VRTX chassis." When event is generated, message will have the following substitutions: • = "" 3.1.18.97 PWR8587 : "Chassis Management Controller is unable to turn on server- because the chassis enclosure is open." When event is generated, message will have the following substitutions: • = "" 3.1.18.
• = "" 3.1.18.106 PWR8596 : "Chassis Management Controller is unable to turn on server- because PSU redundancy is lost and the available power is insufficient." When event is generated, message will have the following substitutions: • = "" 3.1.18.107 PWR8597 : "The Power Supply Unit (PSU) is turned off because it is not supported by the Chassis." When event is generated, message will have the following substitutions: • = "" 3.1.18.
3.1.18.113 PWR8666 : "iKVM power cycle initiated." 3.1.18.114 PWR8667 : "Resetting iKVM to default settings." 3.1.18.115 PWR8668 : "iKVM reset initiated." 3.1.18.116 PWR8669 : "Unable to turn on the server because of an inconsistency between the chassis components and mezzanine card." When event is generated, message will have the following substitutions: • = "" 3.1.18.
3.1.19 Subcategory= RAC Event [MessageID prefix =RAC] 3.1.19.1 RAC0100 : "The Smart Card is removed. Further communication is not possible." 3.1.19.2 RAC0101 : "The inserted Smart Card is not valid or the Smart Card reader is not supported." 3.1.19.3 RAC0102 : "The Smart Card Logon plug-in is not installed. Install the plug-in from the iDRAC Web GUI to log in using Smart Card." 3.1.19.4 RAC0103 : "This browser does not support Smart Card logon on iDRAC. Use Internet Explorer version 7.
partition." 3.1.19.30 RAC0138 : "A valid certificate is not loaded." 3.1.19.31 RAC0140 : "Firmware update has failed." 3.1.19.32 RAC0141 : "Firmware update verification failed: The update status is unknown." 3.1.19.33 RAC0142 : "File is not valid for iDRAC firmware update." 3.1.19.34 RAC0146 : "Firmware rollback has failed." 3.1.19.35 RAC0147 : "Rollback firmware is not available." 3.1.19.36 RAC0148 : "Unable to retrieve the batteries information. The system is powered off." 3.1.19.
characters." 3.1.19.65 RAC0222 : "The Destination E-mail Address is invalid." 3.1.19.66 RAC0223 : "Enter an alphanumeric value or a valid symbol for the following (see the online help for more information):" 3.1.19.67 RAC0224 : "Invalid e-mail description." 3.1.19.68 RAC0225 : "Sending the test mail failed." 3.1.19.69 RAC0226 : "Send Failed: Request processing failed." 3.1.19.70 RAC0227 : "SD card is not detected: Insert an SD Card of size greater than 256MB." 3.1.19.
3.1.19.81 RAC0242 : "The selected partition does not exist." 3.1.19.82 RAC0243 : "Partition failed: A partitioning conflict has occurred with another session." 3.1.19.83 RAC0244 : "The partition label must be unique." 3.1.19.84 RAC0245 : "The partition is in-use by another process." 3.1.19.85 RAC0246 : "Partition is read-only." 3.1.19.86 RAC0247 : "The partition is currently attached." 3.1.19.87 RAC0248 : "This operation deletes the partition permanently. Do you want to continue?" 3.1.19.
remotely through Web GUI, Remote Racadm, Ssh, and Telnet. Local Racadm and serial interface will continue to work." 3.1.19.110 RAC0273 : "iDRAC access will be limited to running the Racadm utility on the local server or using the serial interface." 3.1.19.111 RAC0274 : "See the iDRAC user documentation for more information on using the Racadm utility or the serial interface." 3.1.19.112 RAC0275 : "Click OK to disable the NIC. Click Cancel to keep the setting unchanged." 3.1.19.
Authority (CA) certificate must be uploaded. The CA certificate is used to verify the directory server SSL certificate." 3.1.19.130 RAC0294 : "The Character Accumulate Interval value is invalid. Expected range: 1-255." 3.1.19.131 RAC0295 : "The Character Send Threshold value is invalid. Expected range: 1-255." 3.1.19.132 RAC0297 : "Specify a Domain Controller Address must be configured." 3.1.19.133 RAC0298 : "Root Domain Name must be configured." 3.1.19.
3.1.19.144 RAC0701 : "Requested system powerup." 3.1.19.145 RAC0702 : "Requested system powercycle." 3.1.19.146 RAC0703 : "Requested system hardreset." 3.1.19.147 RAC0704 : "Requested system powerdown." 3.1.19.148 RAC0705 : "Requested system graceful shutdown." 3.1.19.149 RAC0706 : "Requested system NMI." 3.1.19.150 RAC0708 : "Previous reboot was due to a firmware watchdog timeout." 3.1.19.151 RAC0709 : "Unknown server inserted into chassis." 3.1.19.152 RAC0710 : "Server link tuning error." 3.1.19.
3.1.19.164 RAC0722 : "Failed to program the Chassis assigned MAC address for the NIC.Integrated.." When event is generated, message will have the following substitutions: • = "1" 3.1.19.165 RAC0723 : "The firmware version of the Chassis Management Controller is earlier than the required version ." When event is generated, message will have the following substitutions: • = "3.0" • = "4.0" 3.1.19.
3.1.20.6 RDU8508 : "CMC: cannot failover since the other CMC is nonfunctional." When event is generated, message will have the following substitutions: • = "" 3.1.20.7 RDU8509 : "CMC: cannot failover, chassis is in non-redundant state" When event is generated, message will have the following substitutions: • = "" 3.1.20.
• = "" 3.1.20.15 RDU8517 : "CMC: no action allowed while firmware update is in progress" When event is generated, message will have the following substitutions: • = "" 3.1.20.16 RDU8518 : "CMC: active CMC requests Standby CMC to go active state." When event is generated, message will have the following substitutions: • = "" 3.1.20.17 RDU8519 : "Unable to communicate with peer CMC .
3.1.21 Subcategory= Software Config [MessageID prefix =SWC] 3.1.21.1 SWC1916 : "Network Time Protocol server configuration has changed." 3.1.21.2 SWC1920 : "The Chassis Management at Server Mode is enabled." 3.1.21.3 SWC1921 : "The Chassis Management at Server Mode is disabled." 3.1.21.4 SWC1923 : "Unable to modify the server configuration by using Quick Sync because invalid credentials are entered." 3.1.21.5 SWC1924 : "Unable to modify the server configuration by using Quick Sync." 3.1.21.
• = "" 3.1.21.14 SWC8508 : "Unable to capture Profile from server in slot " When event is generated, message will have the following substitutions: • = "" 3.1.21.15 SWC8509 : "Unable to apply Profile to server in slot " When event is generated, message will have the following substitutions: • = "" 3.1.21.
• = "" 3.1.21.24 SWC8518 : "Unable to modify password of User : -" When event is generated, message will have the following substitutions: • = "" 3.1.21.25 SWC8519 : "Successfully modified user name from to ." When event is generated, message will have the following substitutions: • = "" 3.1.21.
3.1.21.32 SWC8526 : "Unable to delete Chassis Group member ()" When event is generated, message will have the following substitutions: • = "" 3.1.21.33 SWC8527 : "Chassis Management Controller is unable to update the iDRAC user name to "root"." 3.1.21.34 SWC8528 : "Chassis Management Controller is unable to update the iDRAC root password." 3.1.21.35 SWC8529 : "Chassis Management Controller unable to enable the iDRAC root user." 3.1.21.
3.1.21.44 SWC8538 : "Unable to delete key for slot of service account, due to problem saving key file." When event is generated, message will have the following substitutions: • = "" 3.1.21.45 SWC8539 : "The key delete operation successfully completed for slot of service account." When event is generated, message will have the following substitutions: • = "" 3.1.21.
• = "" 3.1.21.53 SWC8604 : "Quick Deploy Profile: Server does not support configuration using profiles." When event is generated, message will have the following substitutions: • = "" 3.1.21.54 SWC8605 : "Quick Deploy Profile: Server generation information is not recognized." When event is generated, message will have the following substitutions: • = "" 3.1.21.
• = "" 3.1.21.61 SWC8612 : "Unable to fully extract boot device information from profile: ." When event is generated, message will have the following substitutions: • = "" 3.1.21.62 SWC8613 : "Unable to fully extract boot list settings from the profile." When event is generated, message will have the following substitutions: • = "" 3.1.21.63 SWC8614 : "Legacy profile setting: is not recognized.
• = "" 398
3.1.22.2 SWU8557 : "Invalid firmware: The uploaded firmware image does not contain a verification signature." 3.1.22.3 SWU8558 : "Invalid firmware: The uploaded firmware image validation was unsuccessful." 3.1.22.4 SWU8559 : "The firmware downgrade operation is unsuccessful. A downgrade to the firmware version uploaded is not supported." 3.1.22.5 SWU8560 : "The firmware update process of Active CMC and Standby CMC was not successful because of a unrecognized image error." 3.1.
" When event is generated, message will have the following substitutions: • = "" 3.1.24 Subcategory= Temperature [MessageID prefix =TMP] 3.1.24.1 TMP8500 : "I/O Module temperature exceeded operating range." When event is generated, message will have the following substitutions: • = "" 3.1.24.2 TMP8501 : "Unable to read planar board temperature sensors. The cooling has been increased to safeguard the system." 3.1.24.
3.1.25.4 USR0008 : "The Default Login Warning feature is disabled." 3.1.25.5 USR0013 : "Insufficient user privileges to perform operation." 3.1.25.6 USR0014 : "The current user session is invalid." 3.1.25.7 USR0015 : "The specified user does not exist." 3.1.25.8 USR0016 : "Unable to get session info from the RAC." 3.1.25.9 USR0017 : "No active sessions currently exist for the specified user." 3.1.25.10 USR0018 : "No active sessions currently exist." 3.1.25.11 USR0019 : "Specified user name is too long." 3.
• = "GUI" 3.1.25.19 USR0033 : "Login for from using was incomplete." When event is generated, message will have the following substitutions: • = "root" • = "192.168.1.1" • = "GUI" 3.1.25.20 USR0034 : "Login attempt alert for from using , IP will be blocked for seconds.
3.1.25.25 USR0152 : "Unable to connect the remote VNC session, beacause an incorrect VNC password was entered from the IP ." When event is generated, message will have the following substitutions: • = "192.168.1.1" 3.1.25.26 USR0153 : "Logging off the remote VNC session from the IP address , because the session timed out." When event is generated, message will have the following substitutions: • = "192.168.1.1" 3.1.25.
3.1.25.30 USR0173 : "The Front Panel USB port switched automatically from iDRAC to operating system." 3.1.25.31 USR0174 : "The Front Panel USB device is removed from the operating system." 3.1.25.32 USR0175 : "The Front Panel USB Port Over Current is detected for the attached device on Disk.USBFront.." When event is generated, message will have the following substitutions: • = "Port" 3.1.25.
• = "" 3.1.25.43 USR8502 : "Successfully closed Session: pid= sid=" When event is generated, message will have the following substitutions: • = "" 3.1.25.44 USR8503 : "Domain user authentication was not successful. Reason code = " When event is generated, message will have the following substitutions: • = "" 3.1.25.45 USR8504 : "The IP address specified is out of range." 3.1.25.
3.1.25.52 USR8511 : "Login was successful from (username=, type=, sid=)" When event is generated, message will have the following substitutions: • = "" 3.1.25.53 USR8512 : " login was not successful (username=, reason=)" When event is generated, message will have the following substitutions: • = "" 3.1.25.
3.2.1 Subcategory= Backup/Restore [MessageID prefix =BAR] 3.2.1.1 BAR001 : "Export System Profile requested." 3.2.1.2 BAR002 : "Validating vFlash Backup partition." 3.2.1.3 BAR003 : "Preparing vFlash Backup partition." 3.2.1.4 BAR004 : "Collecting Hardware Inventory information." 3.2.1.5 BAR005 : "Collecting Lifecycle Controller data." 3.2.1.6 BAR006 : "Finalizing Backup file." 3.2.1.7 BAR007 : "Export System Profile completed." 3.2.1.8 BAR008 : "Invalid Backup file passphrase provided." 3.2.1.
Host System." 3.2.1.29 BAR029 : "Restoring Integrated Remote Access Controller firmware." 3.2.1.30 BAR030 : "Import System Profile Complete, restarting Integrated Remote Access Controller." 3.2.1.31 BAR031 : "RESERVED" 3.2.1.32 BAR032 : "Invalid system profile Backup file." 3.2.1.33 BAR033 : "Unable to Restore Lifecycle Controller data." 3.2.1.34 BAR034 : "Unable to Restore Integrated Remote Access Controller firmware." 3.2.1.35 BAR035 : "Unable to Restore Integrated Remote Access Controller configuration.
• = "PERC H310 Mini" 3.2.1.51 BAR051 : "Performing Component Configuration Restore for Device : " When event is generated, message will have the following substitutions: • = "NIC.Slot.1-1-1" 3.2.1.52 BAR052 : "Firmware update cannot be performed for Device: " When event is generated, message will have the following substitutions: • = "PERC H310 Mini" 3.2.1.
3.2.1.58 BAR058 : "Validating NFS destination access." 3.2.1.59 BAR059 : "Validating CIFS destination access." 3.2.1.60 BAR060 : "Collecting firmware inventory information." 3.2.1.61 BAR061 : "Collecting System Information." 3.2.1.62 BAR062 : "Collecting Lifecycle Controller Configuration database." 3.2.1.63 BAR063 : "Collecting Lifecycle Controller Firmware images." 3.2.1.64 BAR064 : "Collecting Integrated Remote Access Controller firmware." 3.2.1.
information." 3.2.1.84 BAR084 : "Host System Service Tag does not match the Backup file Service Tag." 3.2.1.85 BAR085 : "Unable to collect System Information for Import Backup file validation." 3.2.1.86 BAR086 : "Unable to Restore The Lifecycle Controller Configuration database." 3.2.1.87 BAR087 : "Unable to Restore the Lifecycle Controller Firmware images." 3.2.1.88 BAR088 : "No partitions available on vFlash media." 3.2.1.89 BAR089 : "Lifecycle Controller needs to be updated." 3.2.1.
processing." 3.2.1.111 BAR111 : "Server Profile operation timed out." 3.2.1.112 BAR112 : "The system identifier in the Server Profile file does not match the target system." 3.2.1.113 BAR113 : "Unable to create an Automatic Backup job." 3.2.1.114 BAR114 : "An Automatic Backup job is created." When event is generated, message will have the following substitutions: • = "JobID" 3.2.1.115 BAR115 : "The number of Automatic Server Profile backup files has reached the specified limit.
3.2.2.5 BIOS005 : "Mismatch in AttributeName and AttributeValue count" 3.2.2.6 BIOS006 : "Configuration job already created, cannot set attribute on specified target until existing job is completed or is cancelled" 3.2.2.7 BIOS007 : "Configuration job already created, cannot create another configuration job on specified target until existing job is completed or is cancelled" 3.2.2.8 BIOS008 : "No pending data present to create a Configuration job" 3.2.2.9 BIOS009 : "Lifecycle Controller is currently in use.
3.2.2.17 BIOS017 : "Unable to delete vFlash pending one-time boot configuration" 3.2.2.18 BIOS018 : "Invalid BIOS Password." 3.2.2.19 BIOS021 : "Cannot authenticate BIOS password." 3.2.2.20 BIOS022 : "Cannot set the BIOS password. Password is disabled due to a jumper setting on the motherboard." 3.2.2.21 BIOS023 : "Cannot perform the operation due to an unknown error in iDRAC." 3.2.2.22 BIOS024 : "The set operation did not complete successfully as the attribute is readonly." 3.2.2.
3.2.2.26 BIOS028 : "Unable to change the BIOS password using plain text because the password is currently being configured using a hash." 3.2.2.27 BIOS029 : "Unable to change the BIOS password because an Export Server Profile operation is already running." 3.2.2.28 BIOS030 : "Unable to change the BIOS password because an Import Server Profile operation is already running." 3.2.2.29 BIOS101 : "Unable to read or change any of the system BIOS configuration settings." 3.2.
• = "" 3.2.4 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 3.2.4.1 CMC001 : "The command was successful." 3.2.4.2 CMC002 : "General failure." 3.2.4.3 CMC003 : "Missing required parameter ." When event is generated, message will have the following substitutions: • = "parameter" 3.2.4.4 CMC004 : "Invalid parameter value for .
3.2.5 Subcategory= Cert Mgmt [MessageID prefix =DH] 3.2.5.1 DH001 : "Resource needed to perform the operation is unavailable." 3.2.5.2 DH002 : "Internal I/O failure" 3.2.5.3 DH003 : "Service tag could not be read" 3.2.5.4 DH004 : "iDRAC does not have sufficient free resources to generate keys" 3.2.5.5 DH005 : "CA Cert is corrupted, expired, or does not have signing privileges." 3.2.5.6 DH006 : "Not the right passphrase for the private key (need to re-write)." 3.2.5.
• = "Unknown" • = "Unknown" 3.2.6.9 DIS009 : "Notification of iDRAC IP address changed to sent to Provisioning Server." When event is generated, message will have the following substitutions: • = "Unknown" 3.2.6.
3.2.6.11 DIS011 : "Auto Discovery client using customer signed client certificate." 3.2.6.12 DIS012 : "Auto Discovery client using factory signed client certificate." 3.2.6.13 DIS013 : "Auto Discovery client using default client certificate." 3.2.6.14 DIS014 : "Auto Discovery client using customer provided CA certificate to authenticate Provisioning Server." 3.2.6.15 DIS015 : "Auto Discovery client using default CA certificate to authenticate Provisioning Server." 3.2.6.
not available." 3.2.7.4 FAN903 : "Cannot enable the Enhanced Cooling Mode because an unsupported fan is inserted in the Chassis." 3.2.7.5 FAN904 : "Cannot enable the Enhanced Cooling Mode because the Maximum Power Conservation Mode is enabled." 3.2.7.6 FAN905 : "Applying fan configuration settings. This may take several seconds." 3.2.7.7 FAN906 : "Changes are not made to the current settings." 3.2.7.8 FAN907 : "The Enhanced Cooling Mode feature is already enabled." 3.2.7.
3.2.8.5 FC005 : "The number of AttributeName array elements does not match the AttributeValue array element count." 3.2.8.6 FC006 : "Configuration job already created, cannot set attribute on specified target until existing job is completed or is cancelled." 3.2.8.7 FC007 : "A configuration job already exists. Unable to create another configuration job on specified target until existing job is completed or is cancelled." 3.2.8.8 FC008 : "No pending data present to create a Configuration job." 3.2.8.
3.2.8.17 FC017 : "Unable to perform the operation due to an internal error in iDRAC." 3.2.9 Subcategory= Hardware Config [MessageID prefix =HWC] 3.2.9.1 HWC0001 : "Unable to complete the operation as there is no response from iDRAC." 3.2.9.2 HWC0002 : "Unable to detect vFlash SD card." 3.2.9.3 HWC0003 : "Successfully initialized vFlash SD card." 3.2.9.4 HWC0004 : "Unable to initialize vFlash SD card." 3.2.9.5 HWC0005 : "Internal error while retrieving update information." 3.2.9.
3.2.10.4 IOID004 : "Virtual Address Persistence Policy setting for Non-Auxiliary powered devices is changed to ." When event is generated, message will have the following substitutions: • = "AC Cycle and Cold Boot and Warm Boot" 3.2.10.5 IOID005 : "Storage Initiator Persistence Policy setting is changed to ." When event is generated, message will have the following substitutions: • = "AC Cycle and Cold Boot and Warm Boot" 3.2.10.
• = " 1" 3.2.10.12 IOID115 : "Unable to configure the target settings properties of the NIC Port .
3.2.10.13 IOID116 : "Applying I/O Identity settings based on current persistence policy settings." 3.2.10.14 IOID117 : "The operation to apply I/O Identity settings based on current persistence policy settings has completed successfully." 3.2.10.15 IOID118 : "Unable to configure some or all I/O Identity settings based on current persistence policy settings." 3.2.10.16 IOID119 : "FlexAddress is enabled on all NIC and FC HBA devices." 3.2.11 Subcategory= IO Virtualization [MessageID prefix =IOV] 3.2.11.
• = "" 3.2.11.16 IOV102 : "A PCIe adapter is removed from ." When event is generated, message will have the following substitutions: • = "" 3.2.11.17 IOV103 : "A PCIe adapter in is replaced by PCIe adapter ." When event is generated, message will have the following substitutions: • = "" 3.2.11.
3.2.11.25 IOV123 : "<"PCIE Slot" or "PERC VA"> is unassigned/ unmapped from extended server slot ." When event is generated, message will have the following substitutions: • <"PCIE Slot" or "PERC VA"> = "" 3.2.11.26 IOV1001 : "The requested operation was successfully executed." 3.2.11.27 IOV1002 : "The operation was not successful." 3.2.11.28 IOV1003 : "Missing required parameter .
• = "" 3.2.12 Subcategory= DRAC IP Address [MessageID prefix =IPA] 3.2.12.1 IPA0100 : "The iDRAC IP Address changed from to ." When event is generated, message will have the following substitutions: • = "192.168.1.100" • = "192.168.2.100" 3.2.13 Subcategory= Job Control [MessageID prefix =JCP] 3.2.13.1 JCP001 : "Task successfully scheduled." 3.2.13.2 JCP002 : "Unable to schedule the job." 3.2.13.3 JCP003 : "Job failed.
3.2.13.14 JCP014 : "Maximum jobs per queue exceeded." 3.2.13.15 JCP015 : "A running job cannot be deleted." 3.2.13.16 JCP016 : "Invalid UntilTime value. A minimum of 12 minutes is required." 3.2.13.17 JCP017 : "Job creation request unsuccessful. Maximum number of jobs reached." 3.2.13.18 JCP018 : "Cannot create new jobs until the existing Export job is completed or the job is cancelled." 3.2.13.19 JCP019 : "Cannot create new jobs until the existing Import System Profile job is completed or cancelled." 3.2.
3.2.13.25 JCP024 : "Lifecycle Controller is in use. This job starts when Lifecycle Controller is available." 3.2.13.26 JCP025 : "Lifecycle Controller is not enabled." 3.2.13.27 JCP026 : "Update packages are being downloaded. This job resumes when the downloads are completed." 3.2.13.28 JCP027 : "Job created successfully." 3.2.13.29 JCP028 : "Job status updated." 3.2.13.30 JCP030 : "Unable to schedule jobs while an iDRAC firmware update or configuration job is running." 3.2.13.
• = "parameter" 3.2.14.17 LC017 : "Invalid value for the parameter, .
3.2.14.18 LC018 : "Server certificate successfully modified. iDRAC will now restart and be unavailable during restart." 3.2.14.19 LC019 : "Base64 decode of PKCS12 content was not successful." 3.2.14.20 LC020 : "PKCS12 decrypt of the certificate could not complete." 3.2.14.21 LC021 : "PKCS12 decrypt of private key could not complete." 3.2.14.22 LC022 : "Lifecycle Controller Log Export was successful." 3.2.14.23 LC023 : "Cannot access network share." 3.2.14.
running." 3.2.14.44 LC045 : "An instance of CreateConfigJob is already running." 3.2.14.45 LC046 : "An instance of DownloadServerPublicKey is already running." 3.2.14.46 LC047 : "An instance of DownloadClientCerts is already running." 3.2.14.47 LC048 : "Invalid input value for IPChangeNotifyPS." 3.2.14.48 LC049 : "Invalid value for VirtualAddressManagement." 3.2.14.49 LC050 : "Invalid value for SystemServicesState." 3.2.14.50 LC051 : "Cannot create multiple Server Profile Export jobs." 3.2.14.
3.2.14.59 LC060 : "Lifecycle controller is currently not ready to take provisioning requests" 3.2.14.60 LC061 : "Lifecycle controller is ready to take provisioning requests" 3.2.14.61 LC062 : "Export or Import server profile operation is already running." 3.2.14.62 LC063 : "Cannot create new jobs until the existing running jobs are completed or deleted." 3.2.14.63 LC064 : "The value exceeds the maximum length of characters for .
3.2.14.65 LC066 : "The Export Certificate operation is currently running." 3.2.14.66 LC067 : "Successfully exported SSL Certificate." 3.2.14.67 LC068 : "Unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress." 3.2.14.68 LC069 : "Certificate does not exist." 3.2.14.69 LC070 : "Unable to find the configuration XML import file." 3.2.14.
• = "parameters" 3.2.15.5 LIC904 : "Could not connect to network share." 3.2.15.6 LIC905 : "The LicenseName value cannot exceed 64 characters." 3.2.15.7 LIC906 : "License file is not accessible on the network share." 3.2.15.8 LIC907 : "Unable to perform the operation due to an unknown error in iDRAC." 3.2.16 Subcategory= Log event [MessageID prefix =LOG] 3.2.16.1 LOG001 : "Missing required InstanceID or JobID parameter." 3.2.16.2 LOG002 : "Invalid parameter value for InstanceID." 3.2.16.
3.2.16.16 LOG504 : "Chassis Log Export was successful." 3.2.16.17 LOG505 : "Cannot access network share." 3.2.16.18 LOG506 : "An instance of ExportChassisLog is already running." 3.2.16.19 LOG507 : "Resource allocation failure." 3.2.16.20 LOG508 : "Unable to write to the network share." 3.2.16.21 LOG509 : "The value exceeds the maximum length of characters for .
3.2.17.5 NIC005 : "Mismatch in AttributeName and AttributeValue count" 3.2.17.6 NIC006 : "A configuration job already exists, Cannot set attribute on specified target until existing job is completed or is cancelled" 3.2.17.7 NIC007 : "A configuration job already exists, Cannot create another configuration job on specified target until existing job is completed or is cancelled" 3.2.17.8 NIC008 : "No pending data present to create a Configuration job" 3.2.17.
3.2.17.17 NIC017 : "Unable to delete vFlash pending one-time boot configuration" 3.2.17.18 NIC018 : "Invalid BIOS password." 3.2.17.19 NIC021 : "Cannot authenticate specified BIOS password." 3.2.17.20 NIC022 : "Unable to set the BIOS password because of a jumper setting on the motherboard." 3.2.17.21 NIC023 : "Cannot perform the operation due to an unknown error in iDRAC." 3.2.17.22 NIC024 : "The set operation did not complete successfully as the attribute is readonly." 3.2.
system." 3.2.18.21 OSD21 : "Unable to boot to ISO image." 3.2.18.22 OSD22 : "Unable to detach ISO image from the host." 3.2.18.23 OSD23 : "Unable to continue with DetachISOImage - another command is in the process of exposing the ISO Image and booting to it." 3.2.18.24 OSD24 : "Unable to continue with DetachDrivers - UnPackAndAttach is in progress." 3.2.18.25 OSD25 : "Unable to detach USB device containing operating system drivers." 3.2.18.
and is in progress." 3.2.18.63 OSD063 : "The process of installing an operating system or hypervisor is successfully completed." 3.2.18.64 OSD064 : "The process of installing an operating system or hypervisor is abruptly stopped either by the user or the installation infrastructure." 3.2.18.65 OSD065 : "Operating System/Hypervisor Installation did not complete successfully." 3.2.19 Subcategory= PCI Device [MessageID prefix =PCI] 3.2.19.
• = "device name" 3.2.20.5 PR5 : "The configuration values stored for the previous device could not be applied to device: " When event is generated, message will have the following substitutions: • = "device name" 3.2.20.6 PR6 : "Configuration changes successfully applied to device: " When event is generated, message will have the following substitutions: • = "device name" 3.2.20.
3.2.20.16 PR16 : "Some of the configuration values could not be applied to device: " When event is generated, message will have the following substitutions: • = "device name" 3.2.20.17 PR17 : "Some of the configuration values stored for the previous device could not be applied to device: " When event is generated, message will have the following substitutions: • = "device name" 3.2.20.
• = "JID_432156780987" 3.2.20.35 PR35 : "Power Supply slot firmware update will be performed during next system reboot." When event is generated, message will have the following substitutions: • = "1" 3.2.20.36 PR36 : "Version change detected for firmware.
3.2.22.5 RAC005 : "Mismatch in AttributeName and AttributeValue count." 3.2.22.6 RAC006 : "AttributeValue cannot be changed for ReadOnly Attribute Name" 3.2.22.7 RAC007 : "Input out of Range" 3.2.22.8 RAC008 : "Invalid boolean Value" 3.2.22.9 RAC009 : "String exceeds maximum length." 3.2.22.10 RAC010 : "Invalid character value." 3.2.22.11 RAC011 : "Job already exists, cannot process more set operations." 3.2.22.12 RAC012 : "User is not authorized to perform this operation." 3.2.22.13 RAC013 : "Invalid FQDD.
3.2.22.16 RAC016 : "Invalid AttributeName." 3.2.22.17 RAC017 : "Job created to apply the attribute value." 3.2.22.18 RAC018 : "Job completed with Errors." 3.2.22.19 RAC019 : "Job did not complete successfully." 3.2.22.20 RAC020 : "Completed" 3.2.22.21 RAC021 : "Unable to set static values for IPAddress Net mask or Gateway because DHCP is Enabled." 3.2.22.22 RAC022 : "Unable to set values for User Password, IPMILan, IPMISerial or User Admin Privilege because the User Name is not configured." 3.2.22.
• = "parameter" 3.2.22.40 RAC040 : "Missing parameters ." When event is generated, message will have the following substitutions: • = "parameters" 3.2.22.41 RAC041 : "The set operation on the event filters failed." 3.2.22.42 RAC042 : "Invalid number of input parameters." 3.2.22.43 RAC043 : "Unable to update some event filter settings." 3.2.22.44 RAC044 : "Unable to update some event filter settings." 3.2.22.
3.2.22.57 RAC057 : "Unable to set Privacy Protocol to an enabled state because the Authentication Protocol attribute is set to None for the user ID: " When event is generated, message will have the following substitutions: • = "user ID" 3.2.22.58 RAC058 : "AttributeValue is not unique for AttributeName ." When event is generated, message will have the following substitutions: • = "attribute name" 3.2.22.
3.2.22.64 RAC064 : "iDRAC was successfully reset." 3.2.22.65 RAC065 : "iDRAC reset operation was not successful." 3.2.22.66 RAC066 : "iDRAC is successfully reset to factory-default properties." 3.2.22.67 RAC067 : "iDRAC reset to factory defaults operation was not successful." 3.2.22.68 RAC068 : "SHA256Password and Plain Password cannot be imported together." 3.2.22.69 RAC069 : "String Less than Min Supported Length" 3.2.22.
job queue." When event is generated, message will have the following substitutions: • = "123456789" 3.2.22.85 RAC0610 : "The passphrase and confirm passphrase values entered do not match." 3.2.22.86 RAC0612 : "Cancelling the firmware update operation will delete all the uploaded firmware files. Do you want to continue?" 3.2.22.87 RAC0613 : "The uploaded file is invalid." 3.2.22.88 RAC0614 : "Incorrect password for PKCS#12 file." 3.2.22.89 RAC0615 : "Invalid PKCS#12 file." 3.2.22.
3.2.22.101 RAC0661 : "Storage configuration operation - #(operation) is pending on the selected #{devicetype} : #{devicename}." 3.2.22.102 RAC0901 : "Invalid syntax. The -t option value must set to 1." 3.2.22.103 RAC0902 : "The -f option requires -d to also be specifed." 3.2.22.104 RAC0903 : "The -d option cannot be used with any other options." 3.2.22.105 RAC0904 : "The remote file location is not accessible or reachable." 3.2.22.106 RAC0905 : "Failed to get the USC version details." 3.2.22.
invoked by the ." When event is generated, message will have the following substitutions: • = "root" 3.2.22.133 RAC938 : "Successfully initiated configuration XML file export operation invoked by the .
3.2.22.134 RAC939 : "Unable to start the system configuration profile export or import operation." 3.2.22.135 RAC940 : "Unable to start the system configuration profile export or import operation." 3.2.22.136 RAC941 : "Successfully initiated the export operation. This operation may take several minutes to complete." 3.2.22.137 RAC942 : "Successfully initiated the import operation.
in recovery state," 3.2.22.158 RAC963 : "Unable to retrieve the status of Lifecycle Controller." 3.2.22.159 RAC964 : "Unable to perform the operation." 3.2.22.160 RAC965 : "The -l option must be specified if -u and -p are used." 3.2.22.161 RAC966 : "Unable to continue with the opearion because the user name or password is not specified." 3.2.22.162 RAC967 : "Exporting the configuration XML file to a local share is not supported when using Firmware RACADM." 3.2.22.
(PKCS12) file." 3.2.22.179 RAC985 : "Unable to configure the cfgServerBootOnce object." 3.2.22.180 RAC986 : "The "vmkey" sub-command is deprecated." 3.2.22.181 RAC987 : "Firmware update job for is initiated." When event is generated, message will have the following substitutions: • = "firmimg.d7" 3.2.22.182 RAC988 : "Unable to initiate the firmware update." When event is generated, message will have the following substitutions: • = "firmimg.d7" 3.2.22.
3.2.22.188 RAC994 : "Unable to run the "jobqueue delete --all" command." 3.2.22.189 RAC995 : "Unable to retrieve the hardware inventory." 3.2.22.190 RAC996 : "Unable to set the object value because the DNS RAC Name object is not configured." 3.2.22.191 RAC997 : "The object DNSDomainFromDHCP cannot be enabled." 3.2.22.192 RAC998 : "IPv6 cannot be enabled." 3.2.22.193 RAC999 : "The object DNSFromDHCP6 cannot be enabled." 3.2.22.194 RAC1000 : "Unable to set the object value for iDRAC IPv6 address or gateway.
3.2.22.202 RAC1008 : "The Active Directory object DCLookupByUserDomain cannot be disabled." 3.2.22.203 RAC1009 : "The Active Directory objects DCLookupEnable or GCLookupEnable cannot be enabled." 3.2.22.204 RAC1010 : "Unable to set the power cap value." 3.2.22.205 RAC1011 : "The OS to iDRAC pass-through cannot be enabled." 3.2.22.206 RAC1012 : "Unable to change the auto-negotiation state for the current NIC selection mode." 3.2.22.
• = "123456789" 3.2.22.225 RAC1033 : "Unable to retrieve the server component software inventory." 3.2.22.226 RAC1035 : "There are no pending values to be cleared." 3.2.22.227 RAC1036 : "Successfully cleared pending attribute(s) for the group specified." 3.2.22.228 RAC1037 : "Unable to clear pending attribute(s)." 3.2.22.229 RAC1038 : "Unable to clear pending values for the specified component." 3.2.22.230 RAC1039 : "The subcommand entered is not supported on the specified server." 3.2.22.
3.2.22.235 RAC1044 : "The Automatic Update (autoupdate) feature is not enabled." 3.2.22.236 RAC1045 : "Specifying ftp.dell.com as the catalog source for the Automatic Update feaure may result in frequent system firmware updates because the catalog on ftp.dell.com changes often." 3.2.22.237 RAC1046 : "Unable to view the Automatic Update (autoupdate) feature settings because the feature has not been configured." 3.2.22.238 RAC1047 : "Successfully cleared the Automatic Update (autoupdate) feature settings." 3.
3.2.22.243 RAC1052 : "The Automatic Backup (autobackup) feature is not enabled." 3.2.22.244 RAC1053 : "Unable to view the Automatic Backup (autobackup) feature settings because the feature has not been configured." 3.2.22.245 RAC1054 : "Successfully cleared the Automatic Backup (autobackup) feature settings." 3.2.22.246 RAC1055 : "Unable to clear the Automatic Backup (autobackup) feature settings because there is currently no configuration." 3.2.22.247 RAC1056 : "Rollback operation initiated successfully.
3.2.22.258 RAC1068 : "Unable to set minimum non critical threshold value of , because the value entered is greater than, or equal to the maximum non critical threshold value." When event is generated, message will have the following substitutions: • = "InletTemp" 3.2.22.259 RAC1069 : "Unable to set minimum non critical threshold value of , because the value entered is greater than, or equal to the maximum critical threshold value.
3.2.22.264 RAC1109 : "Unable to run the command, because an incorrect Share type is entered." 3.2.22.265 RAC1110 : "Unable to run the command, because an incorrect Proxy port number was entered." 3.2.22.266 RAC1111 : "Unable to delete the pending values or operations of the specified device." 3.2.22.267 RAC1112 : "Unable to delete the pending values for the specified device because the iDRAC internal storage is in use by a currently running job." 3.2.22.
3.2.22.270 RAC1115 : "Unable to run the command, because of insufficient user privileges." 3.2.22.271 RAC1116 : "Unable to run the command, because the restart flag entered is incorrect." 3.2.22.272 RAC1117 : "Unable to run the command." 3.2.22.273 RAC1118 : "Successfully initiated the update operation specified in the command." 3.2.22.274 RAC1119 : "Unable to generate a comparison report for the specified repository." 3.2.22.
to a remote share." 3.2.22.292 RAC1141 : "The iDRAC firmware rollback operation was initiated." 3.2.22.293 RAC1142 : "Unable to start the Remote Diagnostics operation because the Expiration Time entered (difference between Start Time and Expiration Time) is less than five minutes." 3.2.22.294 RAC1143 : "Configuration results are not applicable for the job type for Job: ." When event is generated, message will have the following substitutions: • = "JobID" 3.2.22.
3.2.22.296 RAC1145 : "The entered log type is invalid." 3.2.22.297 RAC1146 : "Unable to set the SNMPv3 username because SNMPv3 is not enabled for the specified user on iDRAC." 3.2.22.298 RAC1147 : "Unable to set the SNMPv3 username entered in the command because the username is not present or enabled on iDRAC." 3.2.22.299 RAC1150 : "Unable to complete the export operation." 3.2.22.300 RAC1151 : "The export operation is unsuccessful." 3.2.22.301 RAC1152 : "The export operation completed successfully." 3.2.
3.2.22.313 RAC1164 : "A remote diagnostics operation is currently running and not completed." 3.2.22.314 RAC1165 : "Unable to configure the port number that is entered for either http or https ports of the iDRAC Web server, because the port number is already in use." 3.2.22.315 RAC1166 : "Successfully initiated Configuration XML file preview operation that was invoked by .
3.2.22.316 RAC1168 : "The RACADM "getconfig" command will be deprecated in a future version of iDRAC firmware." 3.2.22.317 RAC1169 : "The RACADM "config" command will be deprecated in a future version of iDRAC firmware." 3.2.22.318 RAC1170 : "Unable to find the SSL library in the default path." 3.2.22.319 RAC1175 : "Unable to change the user configuration because modifying the user configuration at index 1 is not allowed." 3.2.22.
• = "Param1" 468
3.2.23.5 RED074 : "A required parameter is not present." 3.2.23.6 RED075 : "An Automatic Backup schedule already exists." 3.2.24 Subcategory= Remote Service [MessageID prefix =RSI] 3.2.24.1 RSI0001 : "The Lifecycle Controller Remote Services is available." 3.2.24.2 RSI0002 : "The remote service is currently not available" 3.2.24.3 RSI0003 : "The remote service is reloading data" 3.2.24.4 RSI0004 : "The remote service is unavailable" 3.2.25 Subcategory= Security Event [MessageID prefix =SEC] 3.2.25.
job for the device already exists." 3.2.26.19 STOR024 : "Unable to create a configuration job because a configuration job for the device already exists." 3.2.26.20 STOR025 : "Unable to delete any pending configuration because the configuration job is already scheduled." 3.2.26.21 STOR026 : "A configuration job was not created because there are no pending configuration changes." 3.2.26.22 STOR027 : "Virtual Disk name is not supported." 3.2.26.23 STOR028 : "Virtual disk not found." 3.2.26.
• = "DiskCachePolicy" 3.2.26.35 STOR042 : "Unsupported value for AttributeName " When event is generated, message will have the following substitutions: • = "DiskCachePolicy" 3.2.26.36 STOR043 : "One or more selected physical disk drives are part of virtual disk that is not Secondary RAID Level 0." 3.2.26.37 STOR044 : "All physical disks specified are not part of the same disk group." 3.2.26.
3.2.26.41 STOR048 : "Controller is not Dell Key Management capable." 3.2.26.42 STOR049 : "Controller is in Local Key Management mode." 3.2.26.43 STOR050 : "Controller is in Dell Key Management mode." 3.2.26.44 STOR051 : "StartingLBA and Size value combination is greater than allowed by the physical disk size." 3.2.26.45 STOR052 : "Attempt to exceed the number of supported of virtual disks on a controller or disk group." 3.2.26.46 STOR053 : "The controller key is not present.
Lifecycle Controller version on the server does not have the necessary capabilities." 3.2.26.62 STOR069 : "Unable to run the method, because the number of elements entered for VDPropNameArry and VDPropValueArray is unequal." When event is generated, message will have the following substitutions: • = "Param1" 3.2.26.63 STOR070 : "Unable to run the WS-MAN method , because an invalid parameter is entered.
3.2.26.65 STOR072 : "iDRAC Service Module (ISM) is either not present or not running on the server OS." 3.2.26.66 STOR073 : "The iDRAC Service Module version present on the server OS does not support the requested PCIe SSD (NVMe) device operation." 3.2.26.67 STOR074 : "The requested RAID configuration operation is not allowed because the controller is currently in Non-RAID mode." 3.2.26.
present on the controller. Delete the preserved cache and retry the operation." 3.2.26.83 STOR0701 : "Storage objects are unavailable in the current system configuration." 3.2.26.
3.2.26.85 STOR034 : "Invalid parameter value for RebootJobType." 3.2.27 Subcategory= Software Config [MessageID prefix =SWC] 3.2.27.1 SWC0001 : "Unable to save the network settings." 3.2.27.2 SWC0002 : "Unable to set Part Replacement policies." 3.2.27.3 SWC0003 : "Unable to display the Lifecycle log." 3.2.27.4 SWC0004 : "Unable to add a work note to the Lifecycle Log." 3.2.27.5 SWC0005 : "Unable to display the current hardware inventory." 3.2.27.
Controller GUI." 3.2.27.23 SWC0028 : "The backup Server Profile operation did not successfully complete." 3.2.27.24 SWC0029 : "Unable to retrieve status of backup Server Profile operation." 3.2.27.25 SWC0030 : "Unable to complete the backup Server Profile backup operation." 3.2.27.26 SWC0031 : "Unable to initiate the backup Server Profile backup operation." 3.2.27.27 SWC0032 : "Successfully exported the Server Configuration Profile image file to the USB drive." 3.2.27.
share folder." 3.2.27.67 SWC0072 : "Unable to export the Tech Support Report to destination folder." 3.2.27.68 SWC0073 : "Unable to start operation with the current iDRAC version." 3.2.27.69 SWC0074 : "Unable to start operation with the current iDRAC version." 3.2.27.70 SWC0075 : "Unable to perform RAID operations because the selected controller is in HBA mode." 3.2.27.
3.2.27.72 SWC0077 : "Unable to initiate the Repurpose or Retire System operation." 3.2.27.73 SWC0101 : "Unable to read available log records." 3.2.27.74 SWC0102 : "The -m option is not supported by the interface being used." 3.2.27.75 SWC0103 : "The -E option is not valid for the specified log." 3.2.27.76 SWC0104 : "The -R option is not valid for the specified log." 3.2.27.77 SWC0105 : "Invalid -m option. Try --more or refer help for proper usage" 3.2.27.
configured before a CSR can be generated." 3.2.27.101 SWC0129 : "Unable to send test email. Please make sure that your email alerts \nhave been configured correctly and connectivity to \nthe SMTP server exists." 3.2.27.102 SWC0130 : "Trap at specified index is not currently enabled." 3.2.27.103 SWC0131 : "Trap destination address must be configured." 3.2.27.104 SWC0132 : "Unable to send test trap.
3.2.27.112 SWC0140 : "RAC reset operation initiated successfully. It may take up to a minute \nfor the RAC to come back online again." 3.2.27.113 SWC0141 : "Certificate successfully downloaded from the RAC" 3.2.27.114 SWC0143 : "SSL key successfully uploaded to the RAC." 3.2.27.115 SWC0144 : "Certificate successfully uploaded to the RAC. The RAC will now reset \nto enable the new certificate and may be offline temporarily." 3.2.27.116 SWC0145 : "A CSR was generated successfully" 3.2.27.
know Remote File Share is ENABLED or DISABLED." 3.2.27.148 SWC0216 : "The -c option requires -l to also be specifed." 3.2.27.149 SWC0217 : "The -c option requires -u to also be specifed." 3.2.27.150 SWC0218 : "The -c option requires -p to also be specifed." 3.2.27.151 SWC0219 : "The -p option requires -c to also be specifed." 3.2.27.152 SWC0220 : "The -u option requires -c to also be specifed." 3.2.27.153 SWC0221 : "The -l option requires -c to also be specifed." 3.2.27.154 SWC0222 : "Invalid syntax.
AutoConfig is enabled." 3.2.27.172 SWC0240 : "The IPv6 DNS Server IP address is not allowed to be configured if IPv6 DNS Server DHCP (cfgIPv6DNSServersFromDHCP6) is enabled" 3.2.27.173 SWC0241 : "Power Cap Enable not set. Unable to modify this property" 3.2.27.174 SWC0242 : "A required license is missing or expired. Obtain an appropriate license and try again, or contact your service provider for additional details." 3.2.27.175 SWC0243 : "Certificate regenerated successfully and webserver restarted" 3.2.27.
3.2.27.184 SWC0252 : "No options were specified. The subcommand requires options to be used." 3.2.27.185 SWC0253 : "Unable to allocate memory needed to perform operation." 3.2.27.186 SWC0254 : "Unable to perform requested operation. \nIf the operation attempted was to configure DRAC, possible reason may be that \nLocal Configuration using RACADM is disabled." 3.2.27.187 SWC0255 : "Unable to open file." 3.2.27.188 SWC0256 : "Unable to read file." 3.2.27.189 SWC0257 : "Invalid syntax.
• = "1" 3.2.27.213 SWC0281 : "The specified object is READ ONLY and cannot be modified." 3.2.27.214 SWC0282 : "The specified object is READ ONLY for this index and cannot be modified." 3.2.27.215 SWC0283 : "The specified object value is not valid." 3.2.27.216 SWC0284 : "Failed to set the object value. \nPossible reason may be that Local Configuration using RACADM is disabled." 3.2.27.217 SWC0285 : "Object value is invalid." 3.2.27.
• = "1" 486
3.2.27.225 SWC0293 : "The specified object is not recognized by iDRAC." 3.2.27.226 SWC0294 : "Invalid group name specified." 3.2.27.227 SWC0295 : "Invalid object name specified." 3.2.27.228 SWC0296 : "The specified value is not allowed to be configured if the user name \nor password is blank." 3.2.27.229 SWC0297 : "Unable to remove passwords because file could not be saved." 3.2.27.
in read-only mode." 3.2.27.261 SWC0722 : "Error occurred while resetting to defaults. The reset command was not accepted." 3.2.27.262 SWC0723 : "Error occurred while Resetting to defaults. The Reset status is not available." 3.2.27.263 SWC0724 : "Error occurred while Resetting to defaults due to a timeout." 3.2.27.264 SW0725 : "iDRAC7 communication failure." 3.2.27.265 SWC1903 : "RAC SSL Certificate has been changed." 3.2.27.266 SWC1905 : "RAC Virtual Console configuration has been changed." 3.2.27.
• = "UserName" 3.2.27.277 SWC1925 : "The iDRAC Quick Sync access feature is set to the Disabled mode." 3.2.27.278 SWC1926 : "The iDRAC Quick Sync interface is enabled." 3.2.27.279 SWC1927 : "The iDRAC Quick Sync access feature is set to the read-only mode." 3.2.27.280 SWC1928 : "The iDRAC Quick Sync access feature is set to the read-write mode." 3.2.27.281 SWC1929 : "The iDRAC Quick Sync inactivity timeout value is set to .
3.2.28 Subcategory= System Info [MessageID prefix =SYS] 3.2.28.1 SYS001 : "The operation was successful." 3.2.28.2 SYS002 : "Unable to perform the operation due to an unknown error in iDRAC." 3.2.28.3 SYS003 : "Missing parameters: ." When event is generated, message will have the following substitutions: • = "parameter name" 3.2.28.4 SYS004 : "Invalid parameter value for .
3.2.28.11 SYS011 : "Pending configuration values are already committed, unable to perform another set operation." 3.2.28.12 SYS012 : "User privileges are not sufficient to perform operation." 3.2.28.13 SYS013 : "Invalid attribute name: ." When event is generated, message will have the following substitutions: • = "attribute name" 3.2.28.
3.2.28.27 SYS030 : "Collecting component configuration information." 3.2.28.28 SYS031 : "Updating component configuration." 3.2.28.29 SYS032 : "Staged component configuration is complete." 3.2.28.30 SYS033 : "Staged component configuration completed with errors." 3.2.28.31 SYS034 : "Performing component configuration for: " When event is generated, message will have the following substitutions: • = "NIC.Integrated.1-1.1" 3.2.28.
• = " linenumber" 3.2.28.46 SYS050 : "The system configuration XML file for import configuration is not compliant with schema nesting checks." 3.2.28.47 SYS051 : "The system could not be shut down within the specified time." 3.2.28.48 SYS052 : "Analyzing iDRAC, System, or Lifecycle Controller configuration for changes to be applied." 3.2.28.49 SYS053 : "Successfully imported and applied system configuration XML file." 3.2.28.
3.2.28.61 SYS065 : "Input file for import configuration operation cannot be found or opened." 3.2.28.62 SYS066 : "No changes detected for iDRAC, System, or Lifecycle Controller configuration." 3.2.28.63 SYS067 : "Unable to complete application of configuration XML file values." 3.2.28.64 SYS068 : "Configuration changes that require system reboot were not applied." 3.2.28.65 SYS069 : "No changes were applied since the current component configuration matched the requested configuration." 3.2.28.
imported to the system." 3.2.28.80 SYS088 : "Estimated time for applying configuration changes is seconds." When event is generated, message will have the following substitutions: • = "seconds" 3.2.28.81 SYS089 : "Preview of system configuration XML file is complete." 3.2.28.82 SYS090 : "The configuration XML input file contains unsupported DOCTYPE tags." 3.2.28.83 SYS091 : "Unable to complete the operation because the method is not supported." 3.2.28.
• = "JID_123456789098" 3.2.28.97 SYS152 : "Erase operations for some System Erase tasks did not complete successfully." 3.2.28.98 SYS153 : "Deleting hardware cache data for controller: ." When event is generated, message will have the following substitutions: • = "RAID.Integrated.1-1" 3.2.28.99 SYS154 : "Initiating secure erase operation on secure erase-capable drives for controller: .
3.2.28.101 SYS156 : "Erase operations for System Erase tasks successfully completed." 3.2.28.102 SYS157 : "Unable to successfully complete requested System Erase tasks." 3.2.28.103 SYS158 : "Hardware cache erase is unsuccessful." 3.2.28.104 SYS159 : "vFlash SD Card erase unsuccessful." 3.2.28.105 SYS160 : "The Lifecycle Controller logs are cleared." 3.2.28.106 SYS161 : "Tech Support Report related non-volitale storage deleted." 3.2.28.107 SYS162 : "Turning on the server to perform System Erase tasks." 3.2.
3.2.29.5 TST104 : "SNMP traps not configured." 3.2.29.6 TST105 : "Invalid parameter value for ." When event is generated, message will have the following substitutions: • = "parameter name" 3.2.29.7 TST106 : "Email alert destination address not configured." 3.2.30 Subcategory= UEFI Event [MessageID prefix =UEFI] 3.2.30.1 UEFI0027 : "The system must be restarted for the new license to become effective." 3.2.30.2 UEFI0030 : "A keyboard device is not connected to the system.
3.2.30.14 UEFI0073 : "Unable to boot because of the Secure Boot policy." When event is generated, message will have the following substitutions: • = "Disk connected to USB Front Port 1: Datastick Pro" 3.2.30.15 UEFI0074 : "The Secure Boot policy has been modified since the last time the system was started." 3.2.30.16 UEFI0075 : "Network Daughter Card 1 is not detected." 3.2.30.17 UEFI0081 : "Memory size has changed from the last time the system was started." 3.2.30.
• = "B2" 3.2.30.24 UEFI0092 : "The number of DIMM ranks has exceeded the maximum allowed ranks per channel limit." 3.2.30.25 UEFI0093 : "The DIMM installed on the memory slot: does not meet the minimum supported frequency." When event is generated, message will have the following substitutions: • = "B2" 3.2.30.26 UEFI0094 : "Unsupported Non-ECC memory module is installed on memory slot: .
3.2.30.35 UEFI0105 : "Unable to enable the Cluster on Die (COD) feature because of an unsupported memory configuration." 3.2.30.36 UEFI0113 : "Unable to enable the Fault Resilient Memory (FRM) feature because the current DIMM population or hardware configuration does not support the feature." 3.2.30.37 UEFI0114 : "Unable to enable the Fault Resilient Memory (FRM) operating mode because of mismatches in DIMM channel configurations." 3.2.30.
• = "parameter name" 3.2.31.4 USR103 : "Missing parameters ." When event is generated, message will have the following substitutions: • = "PARAM1" 3.2.31.5 USR104 : "Unable to perform the operation due to an unknown error in iDRAC." 3.2.31.6 USR105 : "The account is not configured." 3.2.32 Subcategory= vFlash Media [MessageID prefix =VF] 3.2.32.1 VF001 : "Command successful." 3.2.32.2 VF002 : "General failure" 3.2.32.
3.2.32.5 VF005 : "Empty partition creation successful" 3.2.32.6 VF006 : "Empty partition creation failed" 3.2.32.7 VF007 : "Image partition creation successful" 3.2.32.8 VF008 : "Image partition creation did not complete successfully." 3.2.32.9 VF009 : "Partition formatting successful" 3.2.32.10 VF010 : "Partition formatting did not complete successfully." 3.2.32.11 VF011 : "Wrong password" 3.2.32.12 VF012 : "SD card not present" 3.2.32.13 VF013 : "SD card locked" 3.2.32.14 VF014 : "vFlash not disabled" 3.
could not be initialized." 3.2.33.13 VFL0713 : "One or more partitions are currently attached; the SD card could not be initialized." 3.2.33.14 VFL0714 : "SD card is not ready and could not be initialized." 3.2.33.15 VFL0715 : "Error occurred while initializing the SD Card due to insufficient permission." 3.2.33.16 VFL0716 : "SD Card is not a vFlash SD Card; the SD card could not be initialized." 3.2.33.17 VFL0719 : "One or more partitions are in use; the SD card could not be initialized." 3.2.33.
3.3.1.4 BAT1003 : "The battery on learn cycle has completed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.5 BAT1004 : "The battery on learn cycle has timed out." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.6 BAT1005 : "The battery on learn cycle has been postponed.
• = "RAID Controller in Slot 5" 3.3.1.13 BAT1012 : "The battery temperature is above normal." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.14 BAT1013 : "Recharge count has exceeded the maximum limit for battery on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.
3.3.1.22 BAT1021 : "The charge level for the battery on is below the normal threshold." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.23 BAT1022 : " battery recondition is completed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.
3.3.1.31 BAT1030 : "The battery charge level is normal." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.32 BAT1031 : "The battery temperature on is above normal." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.1.33 BAT1032 : "The battery temperature on is normal.
3.3.3 Subcategory= Storage Contr [MessageID prefix =CTL] 3.3.3.1 CTL1 : "Controller event log: " When event is generated, message will have the following substitutions: • = "A foreign configuration was detected on RAID Controller in Slot 2" 3.3.3.2 CTL2 : " rebuild rate has changed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.3 CTL3 : " alarm is enabled.
• = "RAID Controller in Slot 5" 3.3.3.11 CTL11 : "Configuration on was reset." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.12 CTL12 : "An invalid SAS configuration has been detected on .
• = "RAID Controller in Slot 5" 3.3.3.20 CTL21 : "Abort CC on Error and Load Balance has changed for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.21 CTL22 : "Load Balance has changed for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.
3.3.3.29 CTL30 : "The Check Consistency rate has changed for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.30 CTL31 : "Copyback is modified for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.31 CTL32 : "Abort CC on Error is modified for .
• = "RAID Controller in Slot 5" 3.3.3.39 CTL40 : "Multi-bit ECC error on DIMM." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.40 CTL41 : "Single-bit ECC error on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.
3.3.3.48 CTL49 : "The NVRAM has corrupted data on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.49 CTL50 : "The NVRAM has corrupt data." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.
3.3.3.57 CTL58 : " SAS SMP communications error " When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" • = " not implemented" 3.3.3.58 CTL59 : " SAS expander error: " When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" • = " not implemented" 3.3.3.
• = " RAID Controller in Slot 5" 3.3.3.65 CTL66 : "Attempted to import Unsupported Virtual Disk type RAID on ." When event is generated, message will have the following substitutions: • = "not implemented" • = " RAID Controller in Slot 5" 3.3.3.66 CTL67 : "Attempted to import Virtual Disk with missing span on .
• = "RAID Controller in Slot 5" 3.3.3.74 CTL75 : "Preserved cache discarded on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.75 CTL76 : "A configuration command could not be committed to disk on " When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.
• = "RAID Controller in Slot 5" 3.3.3.83 CTL84 : " is running an unsupported firmware version." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.84 CTL85 : " is operating at less than optimal bandwidth." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.
• = "RAID Controller in Slot 6" 3.3.3.92 CTL93 : " has been successfully changed to operate in Fault Tolerant mode." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.93 CTL94 : " has been successfully changed to operate in single controller mode." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.
• = "RAID Controller in Slot 5" 3.3.3.101 CTL102 : "The is enabled." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.3.102 CTL200 : "The current firmware version is older than the required version for ." When event is generated, message will have the following substitutions: • = "5.1.10.10" • = "5.1.10.
• = "Controller 1 (PERC H800 Adapter)" 3.3.3.108 CTL206 : "Abort Check Consistency on Error and Auto Copyback on Predictive Failure values are changed for ." When event is generated, message will have the following substitutions: • = "Controller 1 (PERC H800 Adapter)" 3.3.3.109 CTL207 : "Unable to import the Virtual Disk because the supported limit is exceeded on .
• = "Controller 1 (PERC H800 Adapter)" 3.3.3.117 CTL215 : "Redundant path disconnected on ." When event is generated, message will have the following substitutions: • = "Controller 1 (PERC H800 Adapter)" 3.3.3.118 CTL216 : "Redundant path connection is restored on ." When event is generated, message will have the following substitutions: • = "Controller 1 (PERC H800 Adapter)" 3.3.3.
3.3.4.6 DIAG0146 : "Hard Drive - S/N , self test log contains previous error(s)." When event is generated, message will have the following substitutions: • = "0" • = "B363P5B000HM" 3.3.4.7 DIAG0147 : "Optical Drive - Self test: ." When event is generated, message will have the following substitutions: • = "0" • = "DRAM test failed" 3.3.4.
• <80000000000000??> = "800000000018" • = "" 3.3.4.14 DIAG0155 : "Hard Drive - Not installed." 3.3.4.15 DIAG8154 : "Tape Drive - S/N , ULTRIUM media found but drive requires ULTRIUM for ." When event is generated, message will have the following substitutions: • = "0" • = "3" • = "4, 5, or 6" • = "6" • = "writes" 3.3.4.
3.3.4.20 DIAG8160 : "PERC Battery - incorrect status = <80000000000000??>\n." When event is generated, message will have the following substitutions: • = "0" • <80000000000000??> = "8000000000000000" • = "Battery missing or disconnected" 3.3.4.21 DIAG8166 : "OS - Suspect corrupt MBR, verify MBR with Anti-Virus Application." 3.3.5 Subcategory= Storage Enclosr [MessageID prefix =ENC] 3.3.5.
3.3.5.8 ENC8 : "The alarm was disabled." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.5.9 ENC9 : "The asset tag was changed." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.5.10 ENC10 : "The asset name was changed.
• = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.5.17 ENC17 : "An Enclosure Management Module (EMM) has been discovered on ." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.5.18 ENC18 : "Communication with was lost.
• = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.5.26 ENC27 : "SAS or SATA mixing of physical disks is not supported within the ." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.5.27 ENC28 : "Enclosure Management Module (EMM) firmware version mismatch detected in . .
• = "Enclosure 0:0 on Controller 1 at Connector 0" 3.3.6 Subcategory= Fan Event [MessageID prefix =FAN] 3.3.6.1 FAN1000 : " was removed." When event is generated, message will have the following substitutions: • = "Fan 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.6.2 FAN1001 : " has been inserted.
3.3.7.6 FLDC1007 : "The cache device with WWN = and path = is removed." When event is generated, message will have the following substitutions: • = "" 3.3.7.7 FLDC1008 : "The cache device with WWN = and path = is being removed." When event is generated, message will have the following substitutions: • = "" 3.3.7.
3.3.7.14 FLDC1016 : "A valid permanent license is installed for Fluid Cache." 3.3.7.15 FLDC1017 : "A license has been installed for Fluid Cache." 3.3.7.16 FLDC1018 : "A license has been removed for Fluid Cache." 3.3.7.17 FLDC1019 : "All cache devices have been found and registered for Fluid Cache." 3.3.7.18 FLDC1020 : "The storage device with WWN = and path = is in unknown state." When event is generated, message will have the following substitutions: • = "" 3.3.7.
3.3.7.22 FLDC1024 : "Caching was enabled in write-back mode, but it is currently operating in write-through mode." 3.3.7.23 FLDC1025 : "Caching was enabled in write-back or write-through mode, it is currently operating in pass-through mode." 3.3.7.24 FLDC1026 : "Caching is no longer degraded to write-through mode and is now operating in write-back mode for Fluid Cache." 3.3.7.25 FLDC1027 : "Caching is no longer degraded to pass-through mode and is now operating in its configured mode for Fluid Cache." 3.3.
3.3.7.35 FLDC1037 : "Configuration changes are disabled, because Fluid cache is running on an expired or invalid license." 3.3.7.36 FLDC1038 : "There is not enough memory capacity to run necessary services for Fluid Cache." 3.3.7.37 FLDC1039 : "One or more cache devices are missing, resulting in Fluid Cache to be unresponsive." 3.3.8 Subcategory= Physical Disk [MessageID prefix =PDR] 3.3.8.1 PDR1 : " copyback stopped for rebuild.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.9 PDR9 : "Initialization has started on ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.10 PDR10 : " rebuild has started.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.19 PDR19 : "SMART FPT exceeded for ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.20 PDR20 : "SMART configuration change for ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.29 PDR29 : "Rebuild on completed with error(s)." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.30 PDR30 : "A global hot spare failed.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.39 PDR39 : "A blink operation has initiated on ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.40 PDR40 : "The blink operation has ceased on .
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.49 PDR50 : "Insufficient space on the global hot spare ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.50 PDR51 : "Hot spare SMART polling has failed.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.59 PDR60 : "Error occurred on : ." When event is generated, message will have the following substitutions: • • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" = " Error 123" 3.3.8.60 PDR61 : "The rebuild of failed due to errors on the source physical disk.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.69 PDR70 : "Copyback started from to ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" • = " Disk 6 in Enclosure 0 on Coonnector 0 of RAID Controller in Slot 5" 3.3.8.70 PDR71 : "Copyback completed from to .
3.3.8.78 PDR79 : "A user terminated Copyback from to ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" • = " Disk 6 in Enclosure 0 on Coonnector 0 of RAID Controller in Slot 5" 3.3.8.79 PDR81 : "Microcode update started on .
3.3.8.87 PDR93 : "Microcode update on has completed." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.88 PDR94 : "Microcode update on has timed out." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.
3.3.8.97 PDR104 : "The has turned off because the critical temperature threshold is exceeded." When event is generated, message will have the following substitutions: • = "Param1" 3.3.8.98 PDR105 : " is assigned as dedicated hot-spare." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.8.
• = "PCIe Solid-State Drive in Slot 9 in Bay 1" 3.3.8.106 PDR114 : "The is approaching read-only mode." When event is generated, message will have the following substitutions: • = "PCIe Solid-State Drive in Slot 9 in Bay 1" 3.3.8.107 PDR115 : "The is in read-only mode.
• = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 3.3.8.115 PDR211 : " has encountered storage medium error." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 3.3.8.116 PDR212 : "The state of changed from Ready to Non-RAID.
3.3.9.4 PSU1003 : " is switched OFF." When event is generated, message will have the following substitutions: • = "PSU 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.9.5 PSU1004 : "Power supply cable has been inserted into ." When event is generated, message will have the following substitutions: • = "PSU 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.9.
3.3.10 Subcategory= RAC Event [MessageID prefix =RAC] 3.3.10.1 RAC0500 : "There are no batteries to be displayed." 3.3.10.2 RAC0501 : "There are no physical disks to be displayed." 3.3.10.3 RAC0502 : "There are no virtual disks to be displayed." 3.3.10.4 RAC0503 : "There are no out-of-band capable controllers to be displayed." 3.3.10.5 RAC0504 : "There are no enclosures to be displayed." 3.3.10.6 RAC0505 : "There are no devices to be displayed." 3.3.10.
3.3.11.4 SSD1004 : "Exported the log file." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 3.3.11.5 SSD1005 : "Successfully initialized ." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 3.3.11.
• = "CDB:xyz, Sense:abc" 3.3.12.3 STOR3 : "CEM Storage Management has lost communication with the ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 3.3.12.4 STOR4 : "CEM Storage Management encountered internal error." 3.3.12.5 STOR5 : "Redundancy lost.
3.3.12.6 STOR6 : "CEM Storage Management detected inventory change(s) after host reboot." 3.3.12.7 STOR7 : "The storage management instrumentation is performing an inventory refresh operation." 3.3.12.8 STOR8 : "Detected two RAID controllers in integrated slots. This configuration is not currently supported and the second controller will not be powered on." 3.3.12.9 STOR9 : "No RAID controllers have been detected. Access to shared storage will not be available." 3.3.12.
3.3.12.22 STOR0101 : "No RAID controller is displayed." 3.3.12.23 STOR0102 : "No batteries are displayed." 3.3.12.24 STOR0103 : "No physical disks are displayed." 3.3.12.25 STOR0104 : "No virtual disks are displayed." 3.3.12.26 STOR0105 : "No enclosures are displayed." 3.3.12.27 STOR0106 : "Fans are not connected to enclosures or data about fans is unavailable." 3.3.12.28 STOR0107 : "EMMs are not connected to enclosures or data about EMMs is unavailable." 3.3.12.
3.3.12.36 STOR0203 : "The current operating system kernel version and the non-RAID SCSI driver version are older than the minimum required versions." 3.3.12.37 STOR0204 : "The non-RAID SCSI driver version is older than the minimum required version." 3.3.12.38 STOR0205 : "Global rescan initiated for all storage components in the system." 3.3.12.39 STOR0206 : "Smart thermal shutdown feature is enabled." 3.3.12.40 STOR0207 : "Smart thermal shutdown feature is disabled." 3.3.12.
3.3.12.46 STOR0501 : "Unable to configure RAID." 3.3.12.47 STOR0502 : "Unable to launch RAID Configuration wizard." 3.3.12.48 STOR0503 : "Successfully erased RAID configuration." 3.3.12.49 STOR0504 : "Successfully completed RAID operation." 3.3.12.50 STOR0505 : "Unable to delete virtual disks." 3.3.12.51 STOR0506 : "Unable to create virtual disk." 3.3.12.52 STOR0507 : "Insufficient physical disk space on selected RAID controller." 3.3.12.
3.3.14.3 TMP7 : " has failed." When event is generated, message will have the following substitutions: • = "Temperature Sensor 0 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.14.4 TMP1000 : " exceeded the maximum warning threshold." When event is generated, message will have the following substitutions: • = "Temperature Sensor 0 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 3.3.14.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.4 VDR4 : " was created." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.5 VDR5 : " was deleted." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.6 VDR6 : " configuration has changed.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.14 VDR14 : "The consistency check on was cancelled." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.15 VDR15 : "Initialization of was cancelled." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.24 VDR24 : "Reconfiguration of has completed." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.25 VDR25 : " rebuild is completed." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.35 VDR35 : "Background initialization has completed for ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.36 VDR36 : " initialization is in-progress .
3.3.15.44 VDR44 : " disk cache policy has changed." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.45 VDR45 : " blink has been initiated." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.46 VDR46 : " blink has ceased.
3.3.15.53 VDR53 : "The consistency check logging of inconsistent parity data is disabled for ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.54 VDR54 : " initialization is terminated." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.55 VDR55 : " initialization has failed.
3.3.15.62 VDR93 : " bad block medium error is cleared." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.63 VDR94 : "Controller preserved cache was recovered for ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 3.3.15.64 VDR95 : "Unable to log block .Bad block table on is full.
• = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 3.3.15.71 VDR101 : "Virtual Adapter mapping reported for . Virtual Adapter 1 is now . Virtual Adapter 2 is now . Virtual Adapter 3 is now .
• = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 3.3.15.79 VDR109 : "Successfully deleted Controller Enhanced cache ()." When event is generated, message will have the following substitutions: • = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 3.3.15.80 VDR110 : "Unrecoverable storage medium error detected on .
3.4.1.4 AMP0303 : "The system board current is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "fail-safe" 3.4.1.5 AMP0304 : "The system board current is outside of range." When event is generated, message will have the following substitutions: • = "fail-safe" 3.4.1.6 AMP0305 : "The system board current is within range.
3.4.1.13 AMP0312 : "System level current is less than the lower warning threshold." 3.4.1.14 AMP0313 : "System level current is less than the lower critical threshold." 3.4.1.15 AMP0314 : "System level current is greater than the upper warning threshold." 3.4.1.16 AMP0315 : "System level current is greater than the upper critical threshold." 3.4.1.17 AMP0316 : "System level current is outside of range." 3.4.1.18 AMP0317 : "System level current is within range." 3.4.1.
• = " 100.000" 3.4.1.29 AMP404 : "The sensor detected an error with a value of A." When event is generated, message will have the following substitutions: • = "System Board Pwr Consumption" • = " 658" 3.4.1.30 AMP405 : "The sensor state has changed to a failed state with a value of A.
• = "Tue Jan 08 10:56:54 2013" 3.4.2.17 ASR201 : "The watchdog timer restarted the system at ." When event is generated, message will have the following substitutions: • = "Tue Jan 08 10:56:54 2013" 3.4.2.18 ASR202 : "The watchdog timer turned off the system at .
3.4.3.12 BAT0011 : "The storage battery for disk drive bay is operating normally." When event is generated, message will have the following substitutions: • = "1" 3.4.3.13 BAT0012 : "The storage battery for disk drive bay has failed." When event is generated, message will have the following substitutions: • = "1" 3.4.3.14 BAT0013 : "The storage battery for disk drive bay is present." When event is generated, message will have the following substitutions: • = "1" 3.
3.4.3.21 BAT0030 : "The system board battery is reading low." 3.4.3.22 BAT0031 : "The system board battery status is unknown." 3.4.4 Subcategory= Cable [MessageID prefix =CBL] 3.4.4.1 CBL0001 : "Backplane power cable disconnected." When event is generated, message will have the following substitutions: • = "1" 3.4.4.2 CBL0002 : "Backplane signal cable disconnected." When event is generated, message will have the following substitutions: • = "1" 3.4.4.
• = "PERC SAS B0" • = "2" • = "PCIe C" 3.4.5 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 3.4.5.1 CMC8502 : "Unable to access the IPv6 information of the server." 3.4.5.2 CMC8503 : "Unable to access the IPv4 information of the server." 3.4.5.3 CMC8504 : "Unable to access server: , because the NIC is disabled on the identified server." When event is generated, message will have the following substitutions: • = "" 3.4.
• = "" 3.4.5.10 CMC8520 : "The FRU on server is not functioning." When event is generated, message will have the following substitutions: • = "" 3.4.5.11 CMC8521 : "The Mezz card 1 FRU for the server is not functioning." When event is generated, message will have the following substitutions: • = "" 3.4.5.12 CMC8522 : "The Mezz card 2 FRU for the server is not functioning.
3.4.5.19 CMC8534 : "Unable to turn on the server because the power requirement request exceeds the power cap value." When event is generated, message will have the following substitutions: • = "" 3.4.6 Subcategory= Processor [MessageID prefix =CPU] 3.4.6.1 CPU0000 : "CPU has an internal error (IERR)." When event is generated, message will have the following substitutions: • = "1" 3.4.6.2 CPU0001 : "CPU has a thermal trip (over-temperature) event.
3.4.6.9 CPU0008 : "CPU is disabled." When event is generated, message will have the following substitutions: • = "1" 3.4.6.10 CPU0009 : "CPU terminator is present." When event is generated, message will have the following substitutions: • = "1" 3.4.6.11 CPU0010 : "CPU is throttled." When event is generated, message will have the following substitutions: • = "1" 3.4.6.12 CPU0011 : "Uncorrectable Machine Check Exception detected on CPU .
• = "1" 3.4.6.19 CPU0701 : "CPU protocol error detected." When event is generated, message will have the following substitutions: • = "1" 3.4.6.20 CPU0702 : "CPU bus parity error detected." 3.4.6.21 CPU0703 : "CPU bus initialization error detected." 3.4.6.22 CPU0704 : "CPU machine check error detected." When event is generated, message will have the following substitutions: • = "1" 3.4.6.23 CPU0800 : "CPU voltage regulator module is present.
3.4.6.29 CPU0806 : "CPU voltage regulator module is incorrectly configure." When event is generated, message will have the following substitutions: • = "1" 3.4.6.30 CPU0816 : "CPU voltage regulator module is absent." When event is generated, message will have the following substitutions: • = "1" 3.4.6.31 CPU0817 : "CPU voltage regulator module is operating normally." When event is generated, message will have the following substitutions: • = "1" 3.
• = "0" 3.4.8.4 DIAG0114 : "Cache integrity test discrepancy " When event is generated, message will have the following substitutions: • = "Unable to start application processor(s)." 3.4.8.5 DIAG0115 : "CPU Stress Thermal condition. Limit C, Actual C." When event is generated, message will have the following substitutions: • = "60" • = "73" 3.4.8.6 DIAG0121 : "Memory errors detected, but successfully resolved." 3.4.8.
3.4.8.16 DIAG0213 : "System board - CMOS battery failure detected." 3.4.8.17 DIAG0221 : "System board - Interval timer not functional." 3.4.8.18 DIAG0232 : "RTC - did not generate periodic ticks." 3.4.8.19 DIAG0233 : "System board - RTC seconds count is not updating." 3.4.8.20 DIAG0234 : "System board - HPET <1>, incorrect time period. Expected = , Found = ." When event is generated, message will have the following substitutions: • <1> = "1" • = "1" • = "0" 3.4.8.
• = "CPU1" • = "78" 3.4.8.30 DIAG0315 : "Sensor: The () reading C) is lower than expected." When event is generated, message will have the following substitutions: • = "CPU1" • = "0" 3.4.8.31 DIAG0321 : "LCD EDID - Unable to access EDID EEPROM." 3.4.8.32 DIAG0322 : "LCD panel - Unable to modify brightness." 3.4.8.33 DIAG0323 : "Unable to detect inverter lamp status." 3.4.8.
3.4.8.46 DIAG 0414 : "Cables - not detected." When event is generated, message will have the following substitutions: • = "Inverter cable" 3.4.8.47 DIAG0415 : "Cables - Check the following cable, jumper, connection, or sensor: ." When event is generated, message will have the following substitutions: • = "Intrusion" 3.4.8.48 DIAG0511 : "Fan - The () fan failed to respond correctly.
• = "CPU Thermistor" • = "7" • = "8" 3.4.8.54 DIAG8003 : "Fan - Unable to set Manufacturing Mode." 3.4.8.55 DIAG8004 : "Fan - Unable to determine fan speeds." 3.4.8.56 DIAG8005 : "LCD BIST not supported. or Fan - Fan speed failure. Expected at least , observed ." When event is generated, message will have the following substitutions: • = "3500" • = "2600" 3.4.8.57 DIAG8006 : "Fan - Unable to set fans to speed.
• = "1" 3.4.8.64 DIAG8013 : "LCD doesnt support test commands." When event is generated, message will have the following substitutions: • = "LCD" 3.4.8.65 DIAG8014 : "ADDF module () device () failed with error code , number . No EPSA beep code mapped." When event is generated, message will have the following substitutions: • = "8008" • = "2" 3.4.8.66 DIAG8015 : "Unable to stop all APs. The system may be unstable and should be rebooted." 3.
3.4.8.74 DIAG8171 : "PCIe - PCI device in physical Slot , PciTag , is present but not responding" When event is generated, message will have the following substitutions: • = "1" • = "300" 3.4.8.75 DIAG8611 : "User reported not hearing speaker tone" 3.4.8.76 DIAG800B : "Retrieve vendor ID function error." 3.4.8.77 DIAG800C : "Get/Set inverter mode function error. Vendor: Revision: .
3.4.9 Subcategory= Dell Key Mngr [MessageID prefix =DKM] 3.4.9.1 DKM1000 : "A network problem detected. Cannot contact key management server." 3.4.9.2 DKM1001 : "The key management service is operating correctly." 3.4.9.3 DKM1002 : "Key management server certificate problem detected." 3.4.9.4 DKM1004 : "The key management server received a bad request." 3.4.9.5 DKM1006 : "Key management server error detected." 3.4.10 Subcategory= Fan Event [MessageID prefix =FAN] 3.4.10.
3.4.10.8 FAN0007 : "Fan was inserted." When event is generated, message will have the following substitutions: • = "1" 3.4.10.9 FAN0008 : "Fan is present." When event is generated, message will have the following substitutions: • = "1" 3.4.10.10 FAN0009 : "Fan is absent." When event is generated, message will have the following substitutions: • = "1" 3.4.10.11 FAN0010 : "Fan is disabled.
• = "Blower" 3.4.10.18 FAN0017 : " RPM is within normal operating range." When event is generated, message will have the following substitutions: • = "Blower" 3.4.10.19 FAN0018 : "Enhanced Cooling Mode is not supported for fan ." When event is generated, message will have the following substitutions: • = "1" 3.4.10.20 FAN0019 : "An incompatibility between operating mode and fan type was corrected for fan .
3.4.10.26 FAN0026 : "The sensor detected an error with a value of RPM." When event is generated, message will have the following substitutions: • • = "Fan 1" = " 1" 3.4.10.27 FAN0027 : "The sensor has failed with a value of RPM." When event is generated, message will have the following substitutions: • • = "Fan 1" = " 1" 3.4.10.28 FAN0023 : "Unable to read the sensor value.
• = "KVM" 3.4.12.4 HWC1003 : "The is enabled." When event is generated, message will have the following substitutions: • = "KVM" 3.4.12.5 HWC1004 : "The storage adapter is present." 3.4.12.6 HWC1005 : "The storage adapter is absent." 3.4.12.7 HWC1006 : "The storage adapter is disabled." 3.4.12.8 HWC1007 : "The storage adapter is enabled." 3.4.12.9 HWC1008 : "The backplane is present." 3.4.12.10 HWC1009 : "The backplane is absent." 3.4.12.11 HWC1010 : "The backplane is disabled." 3.
3.4.12.19 HWC1200 : "The sled is inserted in slot ." When event is generated, message will have the following substitutions: • = "VGA" • = "1" 3.4.12.20 HWC1201 : "The sled is removed from slot ." When event is generated, message will have the following substitutions: • = "VGA" • = "1" 3.4.12.21 HWC2000 : "The cable or interconnect is connected.
• = "DRAC" 3.4.12.28 HWC2007 : "The is installed correctly." When event is generated, message will have the following substitutions: • = "DRAC" 3.4.12.29 HWC2008 : "A fabric mismatch detected for mezzanine card ." When event is generated, message will have the following substitutions: • = "B1" 3.4.12.30 HWC2009 : "Mezzanine card is installed correctly." When event is generated, message will have the following substitutions: • = "B1" 3.4.12.
• = "IOM" 3.4.12.38 HWC3001 : "The is inserted." When event is generated, message will have the following substitutions: • = "IOM" 3.4.12.39 HWC3002 : "Server is removed." When event is generated, message will have the following substitutions: • = "1" 3.4.12.40 HWC3003 : "Server was inserted." When event is generated, message will have the following substitutions: • = "1" 3.4.12.41 HWC3004 : "IO module is removed.
3.4.12.49 HWC4011 : "Hardware unsuccessfully updated for mezzanine card ." When event is generated, message will have the following substitutions: • = "C2" 3.4.12.50 HWC4012 : "Hardware successfully updated for embedded NIC." 3.4.12.51 HWC4013 : "Hardware unsuccessfully updated for embedded NIC." 3.4.12.52 HWC4014 : "Link Tuning data successfully updated." 3.4.12.53 HWC4015 : "Link Tuning error detected." 3.4.12.54 HWC4016 : "Hardware incompatibility detected with mezzanine card .
3.4.12.59 HWC5002 : "A fabric mismatch detected on ." When event is generated, message will have the following substitutions: • = "IOM" 3.4.12.60 HWC5003 : " is operating correctly." When event is generated, message will have the following substitutions: • = "iDRAC" 3.4.12.61 HWC5004 : "A link tuning failure detected on ." When event is generated, message will have the following substitutions: • = "IOM" 3.4.12.62 HWC5006 : "A failure is detected on .
• = "A1" 3.4.12.69 HWC5032 : "A fabric mismatch detected on IO module ." When event is generated, message will have the following substitutions: • = "A1" 3.4.12.70 HWC5033 : "IO module is operating correctly." When event is generated, message will have the following substitutions: • = "A1" 3.4.12.71 HWC5034 : "A link tuning failure detected on IO module ." When event is generated, message will have the following substitutions: • = "A1" 3.
• = "LCD" 3.4.12.79 HWC6004 : "Cannot communicate with controller." When event is generated, message will have the following substitutions: • = "IOM" 3.4.12.80 HWC6005 : "Communications restored for controller." When event is generated, message will have the following substitutions: • = "IOM" 3.4.12.81 HWC7000 : "Server health changed to a normal state." When event is generated, message will have the following substitutions: • = "1" 3.4.12.
• = "1" 3.4.12.88 HWC8004 : "The SD card device sensor has failed. SD card location: , SD card device type: , SD card state: ." When event is generated, message will have the following substitutions: • = "Main System Chassis" • = " vFlash" • = " NULL" 3.4.12.89 HWC8005 : "The SD card device has returned to normal state. SD card location: , SD card device type: , SD card state: .
• = " NULL" 3.4.12.94 HWC8501 : "Unable to complete the operation because of an issue with the I/O panel cable." 3.4.12.95 HWC8502 : "The I/O panel cable is connected." 3.4.12.96 HWC8503 : "Communication to the control panel has been restored." 3.4.12.97 HWC8504 : "The Chassis Management Controller (CMC) cannot communicate with the control panel." 3.4.12.98 HWC8506 : "Unable to synchronize control panel firmware due to internal error." 3.4.12.
3.4.13.5 IOV108 : "Power fault detected on PCIE adapter in ." When event is generated, message will have the following substitutions: • = "" 3.4.13.6 IOV109 : "An error condition associated with the PCIe slot is cleared." 3.4.13.7 IOV110 : "Successfully updated Chassis Infrastructure firmware." 3.4.13.8 IOV111 : "Unable to update Chassis Infrastructure firmware." 3.4.13.9 IOV112 : "Chassis Infrastructure firmware is not valid." 3.4.13.
• = "" 3.4.13.17 IOV2008 : "The Chassis Management Controller (CMC) is unable to communicate with the PCIe subsystem." 3.4.14 Subcategory= Link Status [MessageID prefix =LNK] 3.4.14.1 LNK0001 : "Network share name unavailable." 3.4.14.2 LNK0002 : "Unable to resolve host name." 3.4.14.3 LNK0003 : "Unable to connect to the DNS server." 3.4.14.4 LNK0004 : "Unable to connect to FTP server." 3.4.14.5 LNK0005 : "Unable to connect to DHCP server." 3.4.14.
• = "Command" 3.4.15.3 LOG323 : "The log size is near maximum capacity. Log type: ." When event is generated, message will have the following substitutions: • = "Command" 3.4.15.4 LOG324 : "The log size has reached its maximum capacity. Log type: ." When event is generated, message will have the following substitutions: • = "Command" 3.4.15.5 LOG325 : "Unable to receive any log entries. Log type: .
3.4.16.6 MEM0005 : "Persistent correctable memory error limit reached for a memory device at location(s) ." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.7 MEM0006 : "Memory device at location is present." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.8 MEM0007 : "Unsupported memory configuration; check memory device at location .
3.4.16.15 MEM0022 : "Memory device at location is absent." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.16 MEM0024 : "Memory device at location is no longer spare memory." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.17 MEM0600 : "Memory device was added at location .
• = "DIMM1" 3.4.16.25 MEM1003 : "Memory device at location failed to transition to in test." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.26 MEM1004 : "Memory device at location is powered off." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.27 MEM1005 : "Memory device at location failed to power off.
• = "DIMM1" 3.4.16.35 MEM1013 : "Memory device at location is in a full state." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.36 MEM1014 : "Memory device at location is in a power save state." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.37 MEM1015 : "Memory device at location is in a power active state.
• = "DIMM1" 3.4.16.46 MEM1206 : "Memory mirror redundancy is degraded. Check memory device at location ." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.47 MEM1207 : "Memory spare is redundant." 3.4.16.48 MEM1208 : "Memory spare redundancy is lost. Check memory device at location ." When event is generated, message will have the following substitutions: • = "DIMM1" 3.4.16.
3.4.16.57 MEM6004 : "Memory device status is critical. Memory device location: , Possible memory module event cause: ." When event is generated, message will have the following substitutions: • = "DIMM_A1" • = " Single bit error logging disabled" 3.4.16.58 MEM6005 : "Memory device has failed. Memory device location: , Possible memory module event cause: .
• = "1" 3.4.16.68 MEM9005 : "Intel SMI 2 Memory interconnect has degraded." When event is generated, message will have the following substitutions: • = "1" 3.4.16.69 MEM9006 : "Intel QPI interconnect has a non-recoverable issue." When event is generated, message will have the following substitutions: • = "1" 3.4.16.70 MEM9007 : "Intel SMI 2 Memory interconnect has a nonrecoverable issue.
3.4.17.3 NIC500 : "The requested object is not allowed to be configured if DHCP \nis enabled." 3.4.17.4 NIC501 : "The requested object is not allowed to be configured if Auto Config \nis enabled." 3.4.17.5 NIC502 : "DHCP is required to be enabled on the NIC before DHCP can be \nenabled for DNS server or domain name objects." 3.4.17.6 NIC503 : "The DNS server IP address is not allowed to be configured \nif DNS server DHCP (cfgDNSServersFromDHCP) is enabled." 3.4.17.
function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 3.4.19.3 PCI1304 : "An I/O channel check error was detected." 3.4.19.4 PCI1306 : "A software error was detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 3.4.19.
• = "1" • = "1" • = "1" 3.4.19.10 PCI1318 : "A fatal error was detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 3.4.19.11 PCI1319 : "A high-severity issue is detected in the SSD bay , Slot ." When event is generated, message will have the following substitutions: • = "1" • = "1" 3.4.19.
3.4.19.16 PCI1344 : "An I/O channel check error was detected." 3.4.19.17 PCI1346 : "A software error was detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 3.4.19.18 PCI1348 : "A PCI parity error was detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 3.4.19.19 PCI1350 : "A PCI system error was detected on a component at slot .
• = "1" • = "1" 3.4.19.26 PCI2001 : "The component at bus device function recovered from a fatal IO error." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 3.4.19.27 PCI2002 : "A fatal IO error detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 3.4.19.
3.4.19.34 PCI3005 : "Device option ROM on mezzanine card was successfully updated." When event is generated, message will have the following substitutions: • = "B1" 3.4.19.35 PCI3006 : "Failed to get Link Tuning or FlexAddress data from iDRAC." 3.4.19.36 PCI3007 : "Link Tuning or FlexAddress data successfully obtained." 3.4.19.37 PCI3008 : "A non-fatal PCIe error detected on a component at bus device function .
• = "1" 3.4.19.44 PCI3015 : "The component at slot recovered from a non-fatal PCIe error." When event is generated, message will have the following substitutions: • = "1" 3.4.19.45 PCI3016 : "Device option ROM on mezzanine card failed to support Link Tuning or FlexAddress." 3.4.19.46 PCI3017 : "Device option ROM on mezzanine card was successfully updated." 3.4.19.47 PCI3018 : "New PCI card(s) have been detected in the system.
• = "" 3.4.19.54 PCI5008 : "The Chassis Management Controller (CMC) is unable to communicate with the PCIe switch board." 3.4.20 Subcategory= Physical Disk [MessageID prefix =PDR] 3.4.20.1 PDR1000 : "Drive is installed in disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 3.4.20.2 PDR1001 : "Fault detected on drive in disk drive bay .
• = "0" 3.4.20.8 PDR1007 : "Rebuild is in progress for drive in disk drive bay ." When event is generated, message will have the following substitutions: • • = "1" = "0" 3.4.20.9 PDR1008 : "Rebuild was aborted for drive in disk drive bay ." When event is generated, message will have the following substitutions: • • = "1" = "0" 3.4.20.10 PDR1016 : "Drive is removed from disk drive bay .
• = "1" • = "0" 3.4.20.16 PDR1023 : "Rebuild completed for drive in disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 3.4.20.17 PDR1024 : "Drive mismatch detected for drive in disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 3.4.20.18 PDR1025 : "Drive mismatch corrected for drive in disk drive bay .
• = "1" 3.4.20.25 PDR1106 : "Drive is in the failed array." When event is generated, message will have the following substitutions: • = "1" 3.4.20.26 PDR1107 : "Rebuild is in progress for drive ." When event is generated, message will have the following substitutions: • = "1" 3.4.20.27 PDR1108 : "Rebuild was aborted for drive ." When event is generated, message will have the following substitutions: • = "1" 3.4.20.
• = "1" 3.4.21 Subcategory= System Performance Event [MessageID prefix =PFM] 3.4.21.1 PFM0001 : "The value of is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "CPU Usage" 3.4.21.2 PFM0002 : "The value of is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "CPU Usage" 3.4.21.
3.4.22 Subcategory= BIOS POST [MessageID prefix =PST] 3.4.22.1 PST0000 : "Unrecognized Post Code." 3.4.22.2 PST0001 : "System Power On." 3.4.22.3 PST0002 : "CPU Microcode load." 3.4.22.4 PST0003 : "Chipset Initialization." 3.4.22.5 PST0004 : "Memory Configuration." 3.4.22.6 PST0005 : "Shadow BIOS." 3.4.22.7 PST0006 : "Multiprocessor Initialization." 3.4.22.8 PST0007 : "POST processing start." 3.4.22.9 PST0008 : "System Management Mode (SMM)initialization." 3.4.22.
• = "1" 3.4.23.2 PSU0001 : "Power supply failed." When event is generated, message will have the following substitutions: • = "1" 3.4.23.3 PSU0002 : "A predictive failure detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 3.4.23.4 PSU0003 : "The power input for power supply is lost." When event is generated, message will have the following substitutions: • = "1" 3.4.23.
3.4.23.11 PSU0022 : "Power supply is correctly configured." When event is generated, message will have the following substitutions: • = "1" 3.4.23.12 PSU0023 : "Power supply operating at 110 volts has been acknowledged by user." When event is generated, message will have the following substitutions: • = "1" 3.4.23.13 PSU0031 : "Cannot communicate with power supply ." When event is generated, message will have the following substitutions: • = "1" 3.
• = "1" 3.4.23.21 PSU0039 : "An under current fault detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 3.4.23.22 PSU0040 : "An output under voltage fault detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 3.4.23.23 PSU0041 : "An output over voltage fault detected on power supply .
3.4.23.30 PSU0077 : "Power supply vendor type mismatch detected." When event is generated, message will have the following substitutions: • = "1" 3.4.23.31 PSU0078 : "Power supply revision mismatch detected." When event is generated, message will have the following substitutions: • = "1" 3.4.23.32 PSU0080 : "Power supply voltage rating does not match the systems requirements.
3.4.23.39 PSU500 : "Unable to get the current server power status." 3.4.23.40 PSU501 : "Server is already powered ON." 3.4.23.41 PSU502 : "Server is already powered OFF." 3.4.23.42 PSU503 : "Server power status: " When event is generated, message will have the following substitutions: • = "ON" 3.4.23.43 PSU504 : "Server power operation successful" 3.4.23.
• = "1" 3.4.23.51 PSU0904 : "Could not power down 240VA on power unit ." When event is generated, message will have the following substitutions: • = "1" 3.4.23.52 PSU0906 : "An interlock power down error detected on power unit ." When event is generated, message will have the following substitutions: • = "1" 3.4.23.53 PSU0907 : "An interlock power down error was corrected for power unit .
• = "1" 3.4.24 Subcategory= PSU Absent [MessageID prefix =PSUA] 3.4.24.1 PSUA0016 : "Power supply is absent." When event is generated, message will have the following substitutions: • = "1" 3.4.25 Subcategory= Power Usage [MessageID prefix =PWR] 3.4.25.1 PWR0100 : "The power button was pressed." 3.4.25.2 PWR0101 : "The power button was released." 3.4.25.3 PWR0102 : "The sleep button was pressed." 3.4.25.4 PWR0103 : "The sleep button was released." 3.4.25.
3.4.25.11 PWR200 : "Enabling the Max Power Conservation Mode (MPCM) feature will disable the Extended Power Performance (EPP) feature." 3.4.25.12 PWR201 : "Selecting the Server Based Power Management Mode option sets your power cap to a maximum value, server priorities to a default priority, and then disables the Max Power Conservation Mode. Do you want to continue?" 3.4.25.
• = "" 3.4.25.27 PWR220 : "The Extended Power Performance (EPP) feature cannot be enabled because slot is empty.
3.4.25.28 PWR221 : "The Extended Power Performance (EPP) feature is already disabled." 3.4.25.29 PWR222 : "The Extended Power Performance (EPP) feature is already enabled." 3.4.25.30 PWR223 : "Cannot perform a 110V AC operation because the Extended Power Performance (EPP) feature is enabled." 3.4.25.31 PWR1000 : "The system performance restored." 3.4.25.32 PWR1001 : "The system performance degraded." 3.4.25.33 PWR1002 : "The system performance degraded because of thermal protection." 3.4.25.
maintained." 3.4.25.51 PWR2202 : "The system is sleeping with lost processor context." 3.4.25.52 PWR2203 : "The system is sleeping with system hardware and processor context lost." 3.4.25.53 PWR2204 : "The system is in a non-volatile sleep state." 3.4.25.54 PWR2205 : "The system is in a soft-off state." 3.4.25.55 PWR2207 : "The system is in a mechanical off state." 3.4.25.56 PWR2208 : "The system is in a sleep state." 3.4.25.57 PWR2209 : "The system is in an undermined sleep state." 3.4.25.
3.4.25.67 PWR8557 : "The System Input Power Cap is too low to be enforced using the current Power Supply configuration." 3.4.25.68 PWR8558 : "The System Input Power Cap is being enforced with the current Power Supply configuration." 3.4.26 Subcategory= RAC Event [MessageID prefix =RAC] 3.4.26.1 RAC0560 : "RAC Software Initialization Error" 3.4.26.2 RAC0561 : "iDRAC to CMC communication link is not functioning for agent free monitoring of chassis PCIe slots." 3.4.26.
• = "12v" 3.4.27.20 RDU0031 : "The voltage redundancy is lost." When event is generated, message will have the following substitutions: • = "12v" 3.4.27.21 RDU0032 : "The voltage redundancy is degraded." When event is generated, message will have the following substitutions: • = "12v" 3.4.27.22 RDU0033 : "The voltage is not redundant." When event is generated, message will have the following substitutions: • = "12v" 3.4.
3.4.28.7 RFL2007 : "Internal Dual SD Module is writable." When event is generated, message will have the following substitutions: • = "SD1" 3.4.28.8 RFL2008 : "Internal Dual SD Module is disabled." When event is generated, message will have the following substitutions: • = "SD1" 3.4.28.9 RFL2009 : "Internal Dual SD Module is enabled." When event is generated, message will have the following substitutions: • = "SD2" 3.4.
3.4.30 Subcategory= FlexAddress SD [MessageID prefix =RFM] 3.4.30.1 RFM1018 : "Removable Flash Media is absent." 3.4.30.2 RFM1019 : "Removable Flash Media is present." 3.4.30.3 RFM1020 : "Removable Flash Media is IPMI-function ready." 3.4.30.4 RFM1021 : "Removable Flash Media is not IPMI-function ready." 3.4.30.5 RFM1022 : "Removable Flash Media is ready." 3.4.30.6 RFM1023 : "Removable Flash Media is not ready." 3.4.30.7 RFM1024 : "Removable Flash Media is offline." 3.4.30.
Module." 3.4.32 Subcategory= Security Event [MessageID prefix =SEC] 3.4.32.1 SEC0000 : "The chassis is open." 3.4.32.2 SEC0001 : "The drive bay is open." 3.4.32.3 SEC0002 : "The I/O card area is open." 3.4.32.4 SEC0003 : "The processor area is open." 3.4.32.5 SEC0004 : "The LAN is disconnected." 3.4.32.6 SEC0005 : "Unauthorized docking is detected." 3.4.32.7 SEC0006 : "The fan area is open." 3.4.32.8 SEC0016 : "The chassis is closed." 3.4.32.9 SEC0017 : "The drive bay is closed." 3.4.32.
Technology (TXT) problem at boot." 3.4.32.24 SEC0045 : "Intel Trusted Execution Technology (TXT) is operating correctly." 3.4.32.25 SEC0051 : "Unable to determine the redundancy status of the chassis intrusion sensor." 3.4.32.26 SEC0052 : "Chassis intrusion sensor may have failed." 3.4.32.27 SEC0600 : "A secure mode violation detected." 3.4.32.28 SEC0601 : "A secure mode violation was corrected." 3.4.32.29 SEC0602 : "User password violation detected." 3.4.32.
address>." When event is generated, message will have the following substitutions: • = "root" • = "192.168.1.
3.4.33.11 SEL1200 : "The system was reconfigured." 3.4.33.12 SEL1202 : "OEM system boot." 3.4.33.13 SEL1204 : "An unknown system hardware failure detected." 3.4.33.14 SEL1205 : "The unknown system hardware failure was corrected." 3.4.33.15 SEL1206 : "An entry was added to auxiliary log." 3.4.33.16 SEL1207 : "An entry was removed from auxiliary log." 3.4.33.17 SEL1208 : "A platform event filter action was executed." 3.4.33.18 SEL1209 : "The platform event filter action failed." 3.4.33.
Insufficient resources to maintain normal operations." 3.4.33.40 SEL1506 : "Lost communications with Chassis Group Member ." When event is generated, message will have the following substitutions: • = "1" 3.4.33.41 SEL1507 : "Communications restored with Chassis Group Member ." When event is generated, message will have the following substitutions: • = "1" 3.4.33.42 SEL1508 : "Member could not join the Chassis Group.
• = "1" 3.4.34.4 SWC4005 : "A firmware or software incompatibility was corrected between iDRAC in slot and CMC." When event is generated, message will have the following substitutions: • = "1" 3.4.34.5 SWC4006 : "A firmware or software incompatibility detected between system BIOS in slot and CMC." When event is generated, message will have the following substitutions: • = "1" 3.4.34.
• = " BIOS" • = " in slot 1" 3.4.34.12 SWC4013 : "A firmware or software incompatibility was corrected between and .
3.4.34.16 SWC5003 : "System Controller (SC) has either stopped functioning or is updating a firmware version." 3.4.34.17 SWC5004 : "System Controller (SC) has restarted functioning." 3.4.35 Subcategory= System Info [MessageID prefix =SYS] 3.4.35.1 SYS083 : "Unable to export ePSA Diagnostics results because iDRAC internal storage could not be accessed." 3.4.35.
• = " present" • = " present" 643
3.4.35.14 SYS115 : "The power cord sensor is non-functional." 3.4.35.15 SYS116 : "Unable to determine the status of the power cord." 3.4.35.16 SYS117 : "The input power supply is restored." 3.4.35.17 SYS118 : "The input power supply is not available." 3.4.35.18 SYS119 : "Unable to expose the OS Collector to the server OS." 3.4.35.19 SYS120 : "Unable to complete the operation because the OS Collector is taking too much time. The operation is cancelled." 3.4.35.
Lifecycle Controller is not enabled." 3.4.35.37 SYS138 : "Unable to start the collection of OS and Application Data because the server is turned off." 3.4.35.38 SYS139 : "Unable to start the collection of OS and Application Data because the server is in POST and has not finished startup." 3.4.35.39 SYS140 : "Unable to start the collection of OS and Application Data because the iDRAC Service Module (iSM) is not running in the server OS." 3.4.35.
3.4.35.51 SYS181 : "Unable to collect OS and Application Data because the OS Collector is not installed on the iDRAC." 3.4.35.52 SYS182 : "Unable to collect OS and Application Data because another Lifecycle Controller operation is currently in progress." 3.4.35.53 SYS183 : "Unable to allocate memory because of insufficient storage space in iDRAC." 3.4.35.54 SYS184 : "Unable to compute the checksum because OS Collector files are not readable." 3.4.35.
• = "Inlet" 3.4.36.6 TMP0105 : "The system board temperature is within range." When event is generated, message will have the following substitutions: • = "Inlet" 3.4.36.7 TMP0106 : "The memory module temperature is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "1" 3.4.36.8 TMP0107 : "The memory module temperature is less than the lower critical threshold.
• = "Planer" 3.4.36.15 TMP0114 : "The temperature is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "Planer" 3.4.36.16 TMP0115 : "The temperature is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "Planer" 3.4.36.17 TMP0116 : "The temperature is outside of range.
3.4.36.19 TMP0118 : "The system inlet temperature is less than the lower warning threshold." 3.4.36.20 TMP0119 : "The system inlet temperature is less than the lower critical threshold." 3.4.36.21 TMP0120 : "The system inlet temperature is greater than the upper warning threshold." 3.4.36.22 TMP0121 : "The system inlet temperature is greater than the upper critical threshold." 3.4.36.23 TMP0122 : "The system inlet temperature is outside of range." 3.4.36.
• = "1" 3.4.36.41 TMP0201 : "CPU temperature is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "1" 3.4.36.42 TMP0202 : "CPU temperature is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "1" 3.4.36.43 TMP0203 : "CPU temperature is greater than the upper critical threshold.
3.4.36.51 TMP502 : "The sensor has returned to a normal state with a value of degrees Celsius." When event is generated, message will have the following substitutions: • = "System Board Inlet Temp" • = " 27" 3.4.36.52 TMP503 : "The sensor state has changed to a warning state with a value of degrees Celsius.
3.4.37 Subcategory= Temperature Statistics [MessageID prefix =TMPS] 3.4.37.1 TMPS0100 : "Inlet temperature is above warning level for extended duration." 3.4.37.2 TMPS0101 : "Inlet temperature is above critical level for extended duration." 3.4.37.3 TMPS0102 : "Inlet temperature is above warning level for extended duration." 3.4.37.4 TMPS0103 : "Inlet temperature is above critical level for extended duration." 3.4.38 Subcategory= UEFI Event [MessageID prefix =UEFI] 3.4.38.
in Recovery mode." 3.4.38.19 UEFI0018 : "Lifecycle Controller (LC) is unable to complete a requested task or function and therefore is in Recovery Mode." 3.4.38.20 UEFI0019 : "Lifecycle Controller (LC) is unable to complete a requested task or function and prevented the boot process from completing on multiple attempts. LC is in Recovery Mode." 3.4.38.21 UEFI0022 : "Unable to initialize Management Engine because the Management Engine is not responding." 3.4.38.
3.4.38.29 UEFI0032 : "Unable to initialize the TPM chip because the TPM chip is not functioning." 3.4.38.30 UEFI0034 : "A CMOS battery loss is detected resulting in an invalid BIOS configuration." 3.4.38.31 UEFI0036 : "Unable to initialize the iDRAC Shared Memory Architecture (SMA) interface." 3.4.38.32 UEFI0037 : "Unable to communicate with iDRAC because of an issue in the iDRAC Shared Memory Architecture (SMA) Intelligent Platform Management Interface (IPMI)." 3.4.38.
• = "Bus: 0 Dev: 0 Func: 18" 3.4.38.47 UEFI0067 : "A PCIe link training failure is observed in and device link is disabled." When event is generated, message will have the following substitutions: • = "Bus: 4 Dev: 0 Func: 0" 3.4.38.48 UEFI0069 : "A CMOS checksum error has occurred. CMOS is reinitialized." 3.4.38.49 UEFI0070 : "One or more correctable PCIe errors have occurred." 3.4.38.50 UEFI0076 : "One or more Corrected Machine Check(CMC) errors have occurred.
3.4.38.61 UEFI0106 : "One or more memory correctable training errors have occurred on memory slot: " When event is generated, message will have the following substitutions: • = "A1" 3.4.38.62 UEFI0107 : "One or more memory errors have occurred on memory slot: ." When event is generated, message will have the following substitutions: • = "A2" 3.4.38.63 UEFI0108 : "One or more memory errors have occurred on memory slot: .
3.4.38.68 UEFI0115 : "The Management Engine firmware has recovered from one or more correctable errors." 3.4.38.69 UEFI0116 : "One or more boot drivers have reported issue(s)." 3.4.38.70 UEFI0117 : "Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 1." 3.4.38.71 UEFI0118 : "Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 2." 3.4.38.
Controller (LC) firmware was not accessible." 3.4.38.86 UEFI0142 : "Unable to enter System Service Mode (SSM) because the Lifecycle Controller (LC) firmware was unable to complete a requested task or function." 3.4.38.87 UEFI0144 : "One or more memory errors have occurred on memory slot: ." When event is generated, message will have the following substitutions: • = "A1" 3.4.38.88 UEFI0146 : "Unable to verify the chassis type via iDRAC and CMC.
3.4.40.3 VFL0005 : "No vFlash partitions exist." 3.4.40.4 VFL0007 : "No vFlash SD card is present." 3.4.40.5 VFL0009 : "vFlash media is currently in use by another operation." 3.4.40.6 VFL0010 : "An operation is in progress on the SD card." 3.4.40.7 VFL0011 : "vFlash media is not disabled." 3.4.40.8 VFL0012 : "vFlash media is not enabled." 3.4.40.9 VFL0013 : "The vFlash SD Card is in read-only mode." 3.4.40.10 VFL0014 : "The vFlash SD card is not initialized." 3.4.40.
• = "vFlash" 3.4.40.20 VFL1006 : "Removable Flash Media is offline." When event is generated, message will have the following substitutions: • = "vFlash" 3.4.40.21 VFL1007 : "Removable Flash Media is online." When event is generated, message will have the following substitutions: • = "vFlash" 3.4.40.22 VFL1008 : "Failure detected on Removable Flash Media ." When event is generated, message will have the following substitutions: • = "vFlash" 3.4.40.
• = "vFlash" 3.4.40.30 VFL1016 : "Media not present for Removable Flash Media ." When event is generated, message will have the following substitutions: • = "vFlash" 3.4.40.31 VFL1017 : "Media is present for Removable Flash Media ." When event is generated, message will have the following substitutions: • = "vFlash" 3.4.41 Subcategory= vFlash Absent [MessageID prefix =VFLA] 3.4.41.1 VFLA1000 : "Removable Flash Media is absent.
3.4.42.6 VLT0105 : "Processor module voltage is within range." When event is generated, message will have the following substitutions: • = "3.2" 3.4.42.7 VLT0200 : "The system board voltage is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "VRM" 3.4.42.8 VLT0201 : "The system board voltage is less than the lower critical threshold.
• = "A" • = "VRM" 3.4.42.15 VLT0208 : "The memory module voltage is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "A" • = "VRM" 3.4.42.16 VLT0209 : "The memory module voltage is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "A" • = "VRM" 3.4.42.
3.4.42.22 VLT0215 : "The disk drive bay voltage is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "VRM" 3.4.42.23 VLT0216 : "The disk drive bay voltage is outside of range." When event is generated, message will have the following substitutions: • = "VRM" 3.4.42.24 VLT0217 : "The disk drive bay voltage is within range.
• = "A" 3.4.42.32 VLT0225 : "The memory module voltage is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "A" 3.4.42.33 VLT0226 : "The memory module voltage is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "A" 3.4.42.34 VLT0227 : "The memory module voltage is greater than the upper critical threshold.
• = "VRM" 3.4.42.40 VLT0233 : "The mezzanine card voltage is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "B1" • = "VRM" 3.4.42.41 VLT0234 : "The mezzanine card voltage is outside of range." When event is generated, message will have the following substitutions: • = "B1" • = "VRM" 3.4.42.
3.4.42.47 VLT0304 : "CPU voltage is outside of range." When event is generated, message will have the following substitutions: • = "1" • = "VRM" 3.4.42.48 VLT0305 : "CPU voltage is within range." When event is generated, message will have the following substitutions: • = "1" • = "VRM" 3.4.42.49 VLT400 : "The sensor has failed with a value Volts.
• = " 2" 3.4.43 Subcategory= Virtual Console [MessageID prefix =VRM] 3.4.43.1 VRM0009 : "No Virtual Media devices are currently connected." 3.4.43.2 VRM0010 : "Unable to disconnect Virtual Media devices." 3.4.43.3 VRM0011 : "The Virtual Media image server is not currently connected." 3.4.43.4 VRM0012 : "The Virtual Media image server is already connected." 3.4.43.5 VRM0013 : "Virtual Media services is currently attached to the USB interface.
3.5.1 Subcategory= Job Control [MessageID prefix =JCP] 3.5.1.1 JCP000 : "New" 3.5.2 Subcategory= Lifecycle Contr [MessageID prefix =LC] 3.5.2.1 LC043 : "Work note contains non-printable or reserved characters." 3.5.3 Subcategory= RAC Event [MessageID prefix =RAC] 3.5.3.1 RAC0707 : "Primary Firmware image is invalid. Currently booted from backup image. To restore primary image, update the firmware." 3.5.3.2 RAC0724 : "Quick Sync Firmware is successfully updated." 3.5.3.
was found on the Lifecycle Controller." 3.5.4.21 RED020 : "Feature not supported on current version of USC." 3.5.4.22 RED021 : "The component InstanceID specified is not present on the system." 3.5.4.23 RED022 : "Version compatibility check was not successful." 3.5.4.24 RED023 : "Lifecycle Controller in use. This job will start when Lifecycle Controller is available." 3.5.4.25 RED024 : "The specified job starts when Lifecycle Controller is available." 3.5.4.
• = "Firmware updates available : Enterprise UEFI Diagnostics, 4225A2, 4225.4, OS Drivers Pack, 7.2.0.7, A00, BIOS" 3.5.4.38 RED037 : "All components firmware match with the specified remote repository." 3.5.4.39 RED038 : "A recurring task of type is added." When event is generated, message will have the following substitutions: • = "AutoTask" 3.5.4.40 RED039 : "Settings for a recurring operation of type were cleared.
• = "AutoTask" 3.5.4.47 RED046 : "A recurring operation of type was unable to create a job because the task type is now disabled." When event is generated, message will have the following substitutions: • = "AutoTask" 3.5.4.48 RED047 : "A recurring operation was not created because the operation is already configured." When event is generated, message will have the following substitutions: • = "AutoTask" 3.5.4.
3.5.4.57 RED056 : "An internal error occurred. Unable to complete the specified operation." 3.5.4.58 RED057 : "An internal error occurred. Unable to complete the specified operation." 3.5.4.59 RED058 : "A repository update job was created." When event is generated, message will have the following substitutions: • = "JID" 3.5.4.60 RED059 : "Unable to create an update job for .
3.5.4.70 RED076 : "Unable to create an Automatic Update schedule, because an invalid parameter is entered." 3.5.4.71 RED077 : "Unable to get the Automatic Update schedule information." 3.5.4.72 RED078 : "Unable to delete the Automatic Update schedule." 3.5.4.73 RED079 : "The input value entered for the parameter is invalid." When event is generated, message will have the following substitutions: • = "Param1" 3.5.4.74 RED080 : "The required parameter is not present.
• = "Component" • = "Available" • = "Current" 3.5.4.87 RED093 : "The requested job cannot be scheduled because Lifecycle Controller is not enabled." 3.5.4.88 RED094 : "Updating firmware for from version to version .
3.5.4.89 RED095 : "rSPI update for Diags failed." 3.5.4.90 RED0101 : "Rollback successfull." 3.5.5 Subcategory= FW Update Job [MessageID prefix =SUP] 3.5.5.1 SUP001 : "Insufficient parameters provided." 3.5.5.2 SUP002 : "Job creation failure." 3.5.5.3 SUP003 : "Invalid URI, target or reboot flag." 3.5.5.4 SUP005 : "Invalid reboot value." 3.5.5.5 SUP006 : "Update package downloading - Delete failed." 3.5.5.6 SUP007 : "iDRAC busy - Delete failed." 3.5.5.
• = "Param1" 3.5.5.
3.5.5.23 SUP028 : "The GetRepoBasedUpdateList method did not complete successfully." 3.5.5.24 SUP029 : "Firmware versions on server match catalog, applicable updates are not present in the repository." 3.5.5.25 SUP030 : "Proxy IP and User Credential pare valid only if the ProxySupport parameter is TRUE." 3.5.5.26 SUP0100 : "Firmware update operation failed." 3.5.5.27 SUP0101 : "Unable to get firmware update status." 3.5.5.28 SUP0102 : "Invalid TFTP IP address specified." 3.5.5.
complete]" When event is generated, message will have the following substitutions: • = "50" 679
3.5.5.48 SUP0122 : "Firmware update completed successfully" 3.5.5.49 SUP0123 : "Firmware update completed successfully. The RAC is in the process of \nresetting. Your connection will be lost. Please wait up to a minute before starting a new session." 3.5.5.50 SUP0124 : "Firmware update is not currently in progress" 3.5.5.51 SUP0125 : "Current firmware update status is unknown" 3.5.5.52 SUP0126 : "Firmware update in progress. Please wait..." 3.5.5.53 SUP0127 : "Verifying firmware image" 3.5.5.
• = "Lifecycle Controller" • = "1.1.0.726, X12" 3.5.5.70 SUP0517 : "Unable to update the firmware to version ." When event is generated, message will have the following substitutions: • = "Lifecycle Controller" • = "1.1.0.726, X12" 3.5.5.71 SUP0518 : "Successfully updated the firmware to version .
3.5.5.74 SUP0522 : "Unable to update the BIOS firmware because write protection is enabled." 3.5.5.75 SUP0525 : "Unable to verify the digital signature of the Update Package." 3.5.5.76 SUP0526 : "Unable to continue with firmware update." 3.5.5.77 SUP0527 : "The Update Package is not supported for this system." 3.5.5.78 SUP0528 : "Unable to generate a firmware comparison table." 3.5.5.79 SUP0529 : "Unable to access repository." 3.5.5.80 SUP0530 : "Incorrect repository path location." 3.5.5.
3.5.5.89 SUP0539 : "Update Packages missing in the repository." 3.5.5.90 SUP1901 : "Firmware update initializing." 3.5.5.91 SUP1902 : "Firmware update stopping services." 3.5.5.92 SUP1903 : "Firmware update verify image headers." 3.5.5.93 SUP1904 : "Firmware update checksumming image." 3.5.5.94 SUP1905 : "Firmware update programming flash." 3.5.5.95 SUP1906 : "Firmware update successful." 3.5.5.96 SUP1907 : "Firmware update failed." 3.5.5.97 SUP1908 : "Firmware update failed checksum." 3.5.5.
3.5.7.3 SWU8502 : "A request was submitted to the Lifecycle Controller on server ." When event is generated, message will have the following substitutions: • = "" 3.5.7.4 SWU8503 : "A reinstall/rollback request was submitted to the Lifecycle Controller on server ." When event is generated, message will have the following substitutions: • = "" 3.5.7.
3.5.7.11 SWU8516 : "Unable to update the iDRAC firmware on the server in slot . Transfer is not successful. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 3.5.7.12 SWU8517 : "Unable to update the iDRAC firmware on the server in slot . The Image file is not accessible. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 3.5.7.
3.5.7.19 SWU8524 : "Unable to update the iDRAC on the server in slot firmware: ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 3.5.7.20 SWU8525 : "Unable to update the iDRAC firmware on the server in slot . The firmware update timeout limit is exceeded." When event is generated, message will have the following substitutions: • = "" 3.5.7.
• = "" 3.5.7.31 SWU8536 : "Unable to update the LKVM firmware, because the Image file could not be accessed. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 3.5.7.32 SWU8537 : "Unable to update the LKVM firmware, because the IP address provided is invalid. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 3.5.7.33 SWU8538 : "Unable to update the iKVM firmware.
3.5.7.36 SWU8542 : "Unable to update the Active CMC firmware. The Image file transfer process was not successful." 3.5.7.37 SWU8543 : "Unable to update the Active CMC firmware. The Image file was not accessible." 3.5.7.38 SWU8544 : "Unable to update the Standby CMC firmware because the Standby CMC could not be prepared for firmware update." 3.5.7.39 SWU8545 : "Unable to update the Standby CMC firmware." 3.5.7.40 SWU8546 : "Unable to update the Standby CMC firmware." 3.5.7.
automatically turned off in 5 seconds." 3.6 Category: Work Notes 3.6.1 Subcategory= UEFI Event [MessageID prefix =UEFI] 3.6.1.1 UEFI0050 : "The process of collecting Brand information is started." 3.6.1.2 UEFI0051 : "Brand information is successfully collected. The system is being restarted." 3.6.1.3 UEFI0053 : "The debranding process is started." 3.6.1.4 UEFI0054 : "Debranding process is completed. The system is being restarted." 3.6.2 Subcategory= User Tracking [MessageID prefix =USR] 3.6.2.
4.0 SysLog Event Notification Test Messages 4 4.1 Category: Audit 4.1.1 Subcategory= BIOS Management [MessageID prefix =BIOS] 4.1.1.1 BIOS102 : "A system BIOS update is scheduled that requires a reboot." 4.1.1.2 BIOS103 : "A previously scheduled system BIOS update is canceled." 4.1.2 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 4.1.2.1 CMC8506 : "A command to shut down the CMC was initiated." 4.1.2.
4.1.2.6 CMC8511 : "Unable to synchronize the data in the Extended Storage removable flash media in the primary and secondary CMCs." 4.1.2.7 CMC8512 : "The Extended Storage feature activation timed out. The feature is not active." 4.1.2.8 CMC8513 : "The Extended Storage feature activation on the secondary CMC timed out. The feature is being returned to single CMC mode." 4.1.2.9 CMC8529 : "Unable to perform the requested action on the server-, because of insufficient privileges.
• = "" 4.1.2.17 CMC8542 : "The CMC was restarted because of a manual reset." When event is generated, message will have the following substitutions: • = "" 4.1.2.18 CMC8543 : "The CMC has reset because the thermal threshold was exceeded." When event is generated, message will have the following substitutions: • = "" 4.1.2.19 CMC8545 : "Detected a missing process failover condition detected. Process = .
4.1.2.25 CMC8553 : "An internal error occurred and a failover condition is detected." 4.1.2.26 CMC8554 : "An internal network error occurred." 4.1.2.27 CMC8555 : "An internal memory error has occurred and a failover condition is detected." 4.1.2.28 CMC8557 : "The system health failover is requested. Code ." When event is generated, message will have the following substitutions: • = "" 4.1.2.29 CMC8558 : "The system health is restored." 4.1.2.
• = "" 4.1.2.39 CMC8570 : "The server slot is disabled for DVD drive mapping." When event is generated, message will have the following substitutions: • = "" 4.1.2.40 CMC8571 : "The coin cell battery in the primary CMC is not working." 4.1.2.41 CMC8572 : "The coin cell battery in CMC is not working." When event is generated, message will have the following substitutions: • = "" 4.1.2.42 CMC8573 : "The chassis health is .
• = "" 4.1.4.3 FCD8503 : "The feature is activated in the chassis: " When event is generated, message will have the following substitutions: • = "" 4.1.4.4 FCD8504 : "The feature was previously activated on another chassis." 4.1.4.5 FCD8505 : "The features cannot be deactivated when the chassis is turned on." 4.1.4.6 FCD8531 : "Unable to activate the . The chassis service tag is unavailable.
4.1.6 Subcategory= IO Virtualization [MessageID prefix =IOV] 4.1.6.1 IOV2009 : "The PCIe adapter in the PCIe slot was removed from the slot while the server was turned-on." When event is generated, message will have the following substitutions: • = "" 4.1.7 Subcategory= iDRAC Service Module [MessageID prefix =ISM] 4.1.7.1 ISM0000 : "The iDRAC Service Module is started on the operating system (OS) of server." 4.1.7.
• = "iDRAC" 4.1.7.12 ISM0011 : "The server operating system (OS) is unable to start the iDRAC Service Module, because it is set to "disabled" in iDRAC." 4.1.7.13 ISM0012 : "The IDRAC Service Module is successfully ended on the server operating system (OS)." 4.1.7.14 ISM0013 : "The feature is enabled." When event is generated, message will have the following substitutions: • = "Operating System Information" 4.1.7.
4.1.7.19 ISM0018 : "The OS Collector application is successfully started on the server operating system (OS)." 4.1.7.20 ISM0019 : "The OS Collector application did not start successfully on the server operating system (OS) because checksum verification did not succeed for some files." 4.1.7.21 ISM0020 : "The OS Collector application did not start successfully on the server operating system (OS) because the iDRAC emulated USB device with the OS Collector application was not found." 4.1.7.
4.1.9.5 LIC204 : "The License Manager database restore operation failed." 4.1.9.6 LIC205 : "License Manager database lock timeout has been exceeded." 4.1.9.7 LIC206 : "EULA warning: Importing license may violate the End-User License Agreement." When event is generated, message will have the following substitutions: • = "DE00000000825991" 4.1.9.8 LIC207 : "License on device has expired.
4.1.10.2 LOG007 : "The previous log entry was repeated times." When event is generated, message will have the following substitutions: • = "0" 4.1.10.3 LOG008 : "The complete Lifecycle Log export was successful." 4.1.10.4 LOG203 : "Lifecycle Log archived up to Log Sequence number ." When event is generated, message will have the following substitutions: • = "0" 4.1.10.5 LOG320 : "Log monitoring is disabled. Log type: .
4.1.13 Subcategory= Power Usage [MessageID prefix =POW] 4.1.13.1 POW000 : "Power on permission error, chassis infrastructure not ready." 4.1.13.2 POW001 : "Power on permission error, chassis cover open." 4.1.13.3 POW002 : "Power on permission error, unknown component installed in Fabric1/ Fabric2." 4.1.13.4 POW003 : "Power on permission error, no PCI/Mezz card installed in Fabric1/ Fabric2" 4.1.13.5 POW004 : "Power on permission error, unacknowledge use of 110V." 4.1.13.
4.1.14.8 PSU8508 : ", PSU firmware update is in progress." When event is generated, message will have the following substitutions: • = "" 4.1.14.9 PSU8510 : "PSU in slot FW updated successfully to version " When event is generated, message will have the following substitutions: • = "" 4.1.14.10 PSU8511 : "Successfully updated the firmware for the PSU in slot .
• = "" 4.1.15 Subcategory= Power Usage [MessageID prefix =PWR] 4.1.15.1 PWR2250 : "Unable to turn on the server because the chassis infrastructure not ready." 4.1.15.2 PWR2251 : "Unable to turn on the server because the chassis cover is open." 4.1.15.3 PWR2252 : "Unable to turn on the server because an NDC or Mezzanine card is incompatible with the I/O Module or PCIe subsystem." 4.1.15.4 PWR2253 : "Unable to turn on the server because a PCIe card or Mezzanine card is not installed." 4.1.15.
4.1.15.12 PWR2262 : "The Intel Management Engine has reported an internal system error." 4.1.15.13 PWR2263 : "User ignored Power Supply Oversubscription Warning." 4.1.15.14 PWR2404 : "Power supply capacity alert disabled." 4.1.15.15 PWR8500 : "Chassis power state updated to from ." When event is generated, message will have the following substitutions: • = "" 4.1.15.
4.1.15.23 PWR8509 : "Unable to change the server power priority because Server Based Power Management mode is enabled." 4.1.15.24 PWR8510 : "Unable to set chassis power property .
4.1.15.25 PWR8511 : "Unable to set the CHASSIS_POWER_button_disable chassis power property." 4.1.15.26 PWR8512 : "CMC rebooted, because the power configuration data could not be accessed." 4.1.15.27 PWR8514 : "Unable to perform chassis power action due to insufficient privileges." 4.1.15.28 PWR8515 : "Unable to perform the chassis power action because the chassis is not turned on." 4.1.15.29 PWR8516 : "Unable to perform the chassis power action requested.." 4.1.15.
AC." When event is generated, message will have the following substitutions: • = "" 4.1.15.47 PWR8534 : "Unable to set Server Based Power Management Mode to enable." 4.1.15.48 PWR8535 : "Unable to set Server Based Power Management Mode to disable." 4.1.15.49 PWR8536 : "Server Performance Over Power Redundancy is enabled." 4.1.15.50 PWR8537 : "Server Performance Over Power Redundancy is disabled." 4.1.15.51 PWR8538 : "Power Remote Logging is enabled." 4.1.15.
4.1.15.59 PWR8546 : "Chassis shutdown already in progress." 4.1.15.60 PWR8547 : "Chassis is already powered off." 4.1.15.61 PWR8548 : "Chassis shutdown operation initiated." 4.1.15.62 PWR8549 : "Chassis shutdown did not complete successfully." 4.1.15.63 PWR8550 : "Chassis shutdown completed." 4.1.15.64 PWR8551 : "Successfully set Virtual Infrastructure Device power to DC Watt." When event is generated, message will have the following substitutions: • = "" 4.1.15.
• = "" 4.1.15.71 PWR8561 : "Unable to power on server because of iDRAC communication issue." When event is generated, message will have the following substitutions: • = "" 4.1.15.72 PWR8562 : "Unable to power on the server before power on timer expired." When event is generated, message will have the following substitutions: • = "" 4.1.15.
4.1.15.79 PWR8569 : "Unable to power cycle the server because the server is off." When event is generated, message will have the following substitutions: • = "" 4.1.15.80 PWR8570 : "Unable to communicate to the iDRAC, when trying to power cycle the server ." When event is generated, message will have the following substitutions: • = "" 4.1.15.
• = "" 4.1.15.88 PWR8578 : "Chassis Management Controller is unable to turn on the iDRAC on server- because power required is less than available power." When event is generated, message will have the following substitutions: • = "" 4.1.15.89 PWR8579 : "Request to reset the CMC is initiated." When event is generated, message will have the following substitutions: • = "" 4.1.15.
4.1.15.96 PWR8586 : "Chassis Management Controller is unable to turn on server- because it is not supported in the VRTX chassis." When event is generated, message will have the following substitutions: • = "" 4.1.15.97 PWR8587 : "Chassis Management Controller is unable to turn on server- because the chassis enclosure is open." When event is generated, message will have the following substitutions: • = "" 4.1.15.
• = "" 4.1.15.106 PWR8596 : "Chassis Management Controller is unable to turn on server- because PSU redundancy is lost and the available power is insufficient." When event is generated, message will have the following substitutions: • = "" 4.1.15.107 PWR8597 : "The Power Supply Unit (PSU) is turned off because it is not supported by the Chassis." When event is generated, message will have the following substitutions: • = "" 4.1.15.
4.1.15.113 PWR8666 : "iKVM power cycle initiated." 4.1.15.114 PWR8667 : "Resetting iKVM to default settings." 4.1.15.115 PWR8668 : "iKVM reset initiated." 4.1.15.116 PWR8669 : "Unable to turn on the server because of an inconsistency between the chassis components and mezzanine card." When event is generated, message will have the following substitutions: • = "" 4.1.15.
4.1.16.7 RAC0723 : "The firmware version of the Chassis Management Controller is earlier than the required version ." When event is generated, message will have the following substitutions: • = "3.0" • = "4.0" 4.1.16.8 RAC0726 : "Auto-throttling is disabled for the server." 4.1.16.9 RAC0727 : "Auto-throttling is enabled for the server." 4.1.16.10 RAC0801 : "iDRAC is being reset." 4.1.16.
4.1.17.7 RDU8509 : "CMC: cannot failover, chassis is in non-redundant state" When event is generated, message will have the following substitutions: • = "" 4.1.17.8 RDU8510 : "CMC: cannot failover, CMC firmware versions are different" When event is generated, message will have the following substitutions: • = "" 4.1.17.9 RDU8511 : "Unable to failover, CMC in unknown state.
• = "" 4.1.17.16 RDU8518 : "CMC: active CMC requests Standby CMC to go active state." When event is generated, message will have the following substitutions: • = "" 4.1.17.17 RDU8519 : "Unable to communicate with peer CMC ." When event is generated, message will have the following substitutions: • = "" 4.1.17.
4.1.18 Subcategory= Software Config [MessageID prefix =SWC] 4.1.18.1 SWC1916 : "Network Time Protocol server configuration has changed." 4.1.18.2 SWC1920 : "The Chassis Management at Server Mode is enabled." 4.1.18.3 SWC1921 : "The Chassis Management at Server Mode is disabled." 4.1.18.4 SWC1923 : "Unable to modify the server configuration by using Quick Sync because invalid credentials are entered." 4.1.18.5 SWC1924 : "Unable to modify the server configuration by using Quick Sync." 4.1.18.
• = "" 4.1.18.14 SWC8508 : "Unable to capture Profile from server in slot " When event is generated, message will have the following substitutions: • = "" 4.1.18.15 SWC8509 : "Unable to apply Profile to server in slot " When event is generated, message will have the following substitutions: • = "" 4.1.18.
• = "" 4.1.18.24 SWC8518 : "Unable to modify password of User : -" When event is generated, message will have the following substitutions: • = "" 4.1.18.25 SWC8519 : "Successfully modified user name from to ." When event is generated, message will have the following substitutions: • = "" 4.1.18.
4.1.18.32 SWC8526 : "Unable to delete Chassis Group member ()" When event is generated, message will have the following substitutions: • = "" 4.1.18.33 SWC8527 : "Chassis Management Controller is unable to update the iDRAC user name to "root"." 4.1.18.34 SWC8528 : "Chassis Management Controller is unable to update the iDRAC root password." 4.1.18.35 SWC8529 : "Chassis Management Controller unable to enable the iDRAC root user." 4.1.18.
4.1.18.44 SWC8538 : "Unable to delete key for slot of service account, due to problem saving key file." When event is generated, message will have the following substitutions: • = "" 4.1.18.45 SWC8539 : "The key delete operation successfully completed for slot of service account." When event is generated, message will have the following substitutions: • = "" 4.1.18.
• = "" 4.1.18.53 SWC8604 : "Quick Deploy Profile: Server does not support configuration using profiles." When event is generated, message will have the following substitutions: • = "" 4.1.18.54 SWC8605 : "Quick Deploy Profile: Server generation information is not recognized." When event is generated, message will have the following substitutions: • = "" 4.1.18.
• = "" 4.1.18.61 SWC8612 : "Unable to fully extract boot device information from profile: ." When event is generated, message will have the following substitutions: • = "" 4.1.18.62 SWC8613 : "Unable to fully extract boot list settings from the profile." When event is generated, message will have the following substitutions: • = "" 4.1.18.63 SWC8614 : "Legacy profile setting: is not recognized.
• = "" 4.1.19.2 SWU8557 : "Invalid firmware: The uploaded firmware image does not contain a verification signature." 4.1.19.3 SWU8558 : "Invalid firmware: The uploaded firmware image validation was unsuccessful." 4.1.19.4 SWU8559 : "The firmware downgrade operation is unsuccessful. A downgrade to the firmware version uploaded is not supported." 4.1.19.5 SWU8560 : "The firmware update process of Active CMC and Standby CMC was not successful because of a unrecognized image error." 4.1.
4.1.21 Subcategory= Temperature [MessageID prefix =TMP] 4.1.21.1 TMP8500 : "I/O Module temperature exceeded operating range." When event is generated, message will have the following substitutions: • = "" 4.1.21.2 TMP8501 : "Unable to read planar board temperature sensors. The cooling has been increased to safeguard the system." 4.1.21.3 TMP8502 : "Able to read planar board temperature sensors. Cooling set for normal chassis operation." 4.1.
4.1.22.6 USR0033 : "Login for from using was incomplete." When event is generated, message will have the following substitutions: • = "root" • = "192.168.1.1" • = "GUI" 4.1.22.7 USR0034 : "Login attempt alert for from using , IP will be blocked for seconds.
• = "Vendor" • = "Man" • = "Prod" • = "Name" • = "Serial" 4.1.22.13 USR0171 : "The Front Panel USB port is detached from the iDRAC Disk.USBFront.. Device Details: Device Class , Vendor ID , Product ID ." When event is generated, message will have the following substitutions: • = "Port" • = "Class" • = "Vendor" • = "Product" 4.1.22.
4.1.22.19 USR0177 : "Configuring the Front Panel USB Port Mode to Automatic because the iDRAC is unable to retrieve the Front Panel USB Port Mode." 4.1.22.20 USR0180 : "The Quick Sync feature is enabled because the activate button on the bezel was pressed." 4.1.22.21 USR0181 : "The Quick Sync feature is deactivated because the inactivity timeout limit was reached." 4.1.22.22 USR0182 : "Server information has been accessed by using the iDRAC Quick Sync feature." 4.1.22.
• = "" 4.1.22.32 USR8506 : "Successfully closed Session: sid=" When event is generated, message will have the following substitutions: • = "" 4.1.22.33 USR8507 : " login was not successful (username=, ip=, error=0x)" When event is generated, message will have the following substitutions: • = "" 4.1.22.
4.2 Category: Configuration 4.2.1 Subcategory= Backup/Restore [MessageID prefix =BAR] 4.2.1.1 BAR054 : "System Reset or Lifecycle Controller Actions Canceled, System Profile Failure Recovery unsuccessful." 4.2.1.2 BAR113 : "Unable to create an Automatic Backup job." 4.2.1.3 BAR114 : "An Automatic Backup job is created." When event is generated, message will have the following substitutions: • = "JobID" 4.2.1.
4.2.4 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 4.2.4.1 CMC001 : "The command was successful." 4.2.4.2 CMC002 : "General failure." 4.2.4.3 CMC003 : "Missing required parameter ." When event is generated, message will have the following substitutions: • = "parameter" 4.2.4.4 CMC004 : "Invalid parameter value for ." When event is generated, message will have the following substitutions: • = "parameter" 4.2.4.
4.2.5 Subcategory= Cert Mgmt [MessageID prefix =DH] 4.2.5.1 DH010 : "Reset iDRAC to apply new certificate. Until iDRAC is reset, the old certificate will be active." 4.2.6 Subcategory= Auto-Discovery [MessageID prefix =DIS] 4.2.6.1 DIS100 : "The AutoConfig operation is successful." 4.2.6.2 DIS101 : "The execution of AutoConfig operation is started." 4.2.6.3 DIS102 : "Unable to start the AutoConfig import operation, because the AutoConfig import file is not available." 4.2.6.
not available." 4.2.7.4 FAN903 : "Cannot enable the Enhanced Cooling Mode because an unsupported fan is inserted in the Chassis." 4.2.7.5 FAN904 : "Cannot enable the Enhanced Cooling Mode because the Maximum Power Conservation Mode is enabled." 4.2.7.6 FAN905 : "Applying fan configuration settings. This may take several seconds." 4.2.7.7 FAN906 : "Changes are not made to the current settings." 4.2.7.8 FAN907 : "The Enhanced Cooling Mode feature is already enabled." 4.2.7.
4.2.8.5 FC005 : "The number of AttributeName array elements does not match the AttributeValue array element count." 4.2.8.6 FC006 : "Configuration job already created, cannot set attribute on specified target until existing job is completed or is cancelled." 4.2.8.7 FC007 : "A configuration job already exists. Unable to create another configuration job on specified target until existing job is completed or is cancelled." 4.2.8.8 FC008 : "No pending data present to create a Configuration job." 4.2.8.
4.2.8.17 FC017 : "Unable to perform the operation due to an internal error in iDRAC." 4.2.9 Subcategory= Hardware Config [MessageID prefix =HWC] 4.2.9.1 HWC0001 : "Unable to complete the operation as there is no response from iDRAC." 4.2.9.2 HWC0002 : "Unable to detect vFlash SD card." 4.2.9.3 HWC0003 : "Successfully initialized vFlash SD card." 4.2.9.4 HWC0004 : "Unable to initialize vFlash SD card." 4.2.9.5 HWC0005 : "Internal error while retrieving update information." 4.2.9.
4.2.10.4 IOID004 : "Virtual Address Persistence Policy setting for Non-Auxiliary powered devices is changed to ." When event is generated, message will have the following substitutions: • = "AC Cycle and Cold Boot and Warm Boot" 4.2.10.5 IOID005 : "Storage Initiator Persistence Policy setting is changed to ." When event is generated, message will have the following substitutions: • = "AC Cycle and Cold Boot and Warm Boot" 4.2.10.
• = " 1" 4.2.10.12 IOID115 : "Unable to configure the target settings properties of the NIC Port .
4.2.10.13 IOID116 : "Applying I/O Identity settings based on current persistence policy settings." 4.2.10.14 IOID117 : "The operation to apply I/O Identity settings based on current persistence policy settings has completed successfully." 4.2.10.15 IOID118 : "Unable to configure some or all I/O Identity settings based on current persistence policy settings." 4.2.10.16 IOID119 : "FlexAddress is enabled on all NIC and FC HBA devices." 4.2.11 Subcategory= IO Virtualization [MessageID prefix =IOV] 4.2.11.
• = "" 4.2.11.16 IOV102 : "A PCIe adapter is removed from ." When event is generated, message will have the following substitutions: • = "" 4.2.11.17 IOV103 : "A PCIe adapter in is replaced by PCIe adapter ." When event is generated, message will have the following substitutions: • = "" 4.2.11.
4.2.11.25 IOV123 : "<"PCIE Slot" or "PERC VA"> is unassigned/ unmapped from extended server slot ." When event is generated, message will have the following substitutions: • <"PCIE Slot" or "PERC VA"> = "" 4.2.11.26 IOV1001 : "The requested operation was successfully executed." 4.2.11.27 IOV1002 : "The operation was not successful." 4.2.11.28 IOV1003 : "Missing required parameter .
• = "" 4.2.12 Subcategory= DRAC IP Address [MessageID prefix =IPA] 4.2.12.1 IPA0100 : "The iDRAC IP Address changed from to ." When event is generated, message will have the following substitutions: • = "192.168.1.100" • = "192.168.2.100" 4.2.13 Subcategory= Job Control [MessageID prefix =JCP] 4.2.13.1 JCP002 : "Unable to schedule the job." 4.2.13.2 JCP032 : "Unable to create a job because conflicting options are entered.
4.2.14.5 LC066 : "The Export Certificate operation is currently running." 4.2.14.6 LC067 : "Successfully exported SSL Certificate." 4.2.14.7 LC068 : "Unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress." 4.2.14.8 LC069 : "Certificate does not exist." 4.2.14.9 LC070 : "Unable to find the configuration XML import file." 4.2.14.
4.2.15.8 LOG503 : "Invalid value for the parameter, ." When event is generated, message will have the following substitutions: • = "parameter" 4.2.15.9 LOG504 : "Chassis Log Export was successful." 4.2.15.10 LOG505 : "Cannot access network share." 4.2.15.11 LOG506 : "An instance of ExportChassisLog is already running." 4.2.15.12 LOG507 : "Resource allocation failure." 4.2.15.13 LOG508 : "Unable to write to the network share." 4.2.15.
4.2.17.2 PCI5002 : "A PCIe card carrier that does not contain a PCIe card is inserted in the PCIe slot ." When event is generated, message will have the following substitutions: • = "" 4.2.17.3 PCI5003 : "A PCIe card carrier is removed from the PCIe slot ." When event is generated, message will have the following substitutions: • = "" 4.2.18 Subcategory= Part Exchange [MessageID prefix =PR] 4.2.18.
4.2.20.3 RAC052 : "Unable to create a configuration job because an existing configuration job is already in progress." 4.2.20.4 RAC053 : "OS to iDRAC pass-through is disabled." 4.2.20.5 RAC054 : "User account attributes cannot be reset to default values due to an internal error." 4.2.20.6 RAC055 : "User name cannot be cleared because the user account is enabled in the input configuration XML file." 4.2.20.
4.2.20.15 RAC064 : "iDRAC was successfully reset." 4.2.20.16 RAC065 : "iDRAC reset operation was not successful." 4.2.20.17 RAC066 : "iDRAC is successfully reset to factory-default properties." 4.2.20.18 RAC067 : "iDRAC reset to factory defaults operation was not successful." 4.2.20.19 RAC068 : "SHA256Password and Plain Password cannot be imported together." 4.2.20.20 RAC069 : "String Less than Min Supported Length" 4.2.20.
4.2.20.33 RAC0610 : "The passphrase and confirm passphrase values entered do not match." 4.2.20.34 RAC0612 : "Cancelling the firmware update operation will delete all the uploaded firmware files. Do you want to continue?" 4.2.20.35 RAC0613 : "The uploaded file is invalid." 4.2.20.36 RAC0614 : "Incorrect password for PKCS#12 file." 4.2.20.37 RAC0615 : "Invalid PKCS#12 file." 4.2.20.38 RAC0616 : "Error while extracting custom signing certificate and private key from the PKCS#12 file." 4.2.20.
4.2.20.49 RAC0661 : "Storage configuration operation - #(operation) is pending on the selected #{devicetype} : #{devicename}." 4.2.20.50 RAC936 : "Unable to change the hot spare property for the PSU." 4.2.20.51 RAC937 : "Successfully initiated configuration XML file import operation that was invoked by the ." When event is generated, message will have the following substitutions: • = "root" 4.2.20.
4.2.20.53 RAC939 : "Unable to start the system configuration profile export or import operation." 4.2.20.54 RAC940 : "Unable to start the system configuration profile export or import operation." 4.2.20.55 RAC941 : "Successfully initiated the export operation. This operation may take several minutes to complete." 4.2.20.56 RAC942 : "Successfully initiated the import operation.
recovery state," 4.2.20.77 RAC963 : "Unable to retrieve the status of Lifecycle Controller." 4.2.20.78 RAC964 : "Unable to perform the operation." 4.2.20.79 RAC965 : "The -l option must be specified if -u and -p are used." 4.2.20.80 RAC966 : "Unable to continue with the opearion because the user name or password is not specified." 4.2.20.81 RAC967 : "Exporting the configuration XML file to a local share is not supported when using Firmware RACADM." 4.2.20.
(PKCS12) file." 4.2.20.98 RAC985 : "Unable to configure the cfgServerBootOnce object." 4.2.20.99 RAC986 : "The "vmkey" sub-command is deprecated." 4.2.20.100 RAC987 : "Firmware update job for is initiated." When event is generated, message will have the following substitutions: • = "firmimg.d7" 4.2.20.101 RAC988 : "Unable to initiate the firmware update." When event is generated, message will have the following substitutions: • = "firmimg.d7" 4.2.20.
4.2.20.107 RAC994 : "Unable to run the "jobqueue delete --all" command." 4.2.20.108 RAC995 : "Unable to retrieve the hardware inventory." 4.2.20.109 RAC996 : "Unable to set the object value because the DNS RAC Name object is not configured." 4.2.20.110 RAC997 : "The object DNSDomainFromDHCP cannot be enabled." 4.2.20.111 RAC998 : "IPv6 cannot be enabled." 4.2.20.112 RAC999 : "The object DNSFromDHCP6 cannot be enabled." 4.2.20.113 RAC1000 : "Unable to set the object value for iDRAC IPv6 address or gateway.
4.2.20.121 RAC1008 : "The Active Directory object DCLookupByUserDomain cannot be disabled." 4.2.20.122 RAC1009 : "The Active Directory objects DCLookupEnable or GCLookupEnable cannot be enabled." 4.2.20.123 RAC1010 : "Unable to set the power cap value." 4.2.20.124 RAC1011 : "The OS to iDRAC pass-through cannot be enabled." 4.2.20.125 RAC1012 : "Unable to change the auto-negotiation state for the current NIC selection mode." 4.2.20.
• = "123456789" 4.2.20.144 RAC1033 : "Unable to retrieve the server component software inventory." 4.2.20.145 RAC1035 : "There are no pending values to be cleared." 4.2.20.146 RAC1036 : "Successfully cleared pending attribute(s) for the group specified." 4.2.20.147 RAC1037 : "Unable to clear pending attribute(s)." 4.2.20.148 RAC1038 : "Unable to clear pending values for the specified component." 4.2.20.149 RAC1039 : "The subcommand entered is not supported on the specified server." 4.2.20.
4.2.20.154 RAC1044 : "The Automatic Update (autoupdate) feature is not enabled." 4.2.20.155 RAC1045 : "Specifying ftp.dell.com as the catalog source for the Automatic Update feaure may result in frequent system firmware updates because the catalog on ftp.dell.com changes often." 4.2.20.156 RAC1046 : "Unable to view the Automatic Update (autoupdate) feature settings because the feature has not been configured." 4.2.20.157 RAC1047 : "Successfully cleared the Automatic Update (autoupdate) feature settings." 4.
4.2.20.162 RAC1052 : "The Automatic Backup (autobackup) feature is not enabled." 4.2.20.163 RAC1053 : "Unable to view the Automatic Backup (autobackup) feature settings because the feature has not been configured." 4.2.20.164 RAC1054 : "Successfully cleared the Automatic Backup (autobackup) feature settings." 4.2.20.165 RAC1055 : "Unable to clear the Automatic Backup (autobackup) feature settings because there is currently no configuration." 4.2.20.166 RAC1056 : "Rollback operation initiated successfully.
4.2.20.177 RAC1068 : "Unable to set minimum non critical threshold value of , because the value entered is greater than, or equal to the maximum non critical threshold value." When event is generated, message will have the following substitutions: • = "InletTemp" 4.2.20.178 RAC1069 : "Unable to set minimum non critical threshold value of , because the value entered is greater than, or equal to the maximum critical threshold value.
4.2.20.183 RAC1109 : "Unable to run the command, because an incorrect Share type is entered." 4.2.20.184 RAC1110 : "Unable to run the command, because an incorrect Proxy port number was entered." 4.2.20.185 RAC1111 : "Unable to delete the pending values or operations of the specified device." 4.2.20.186 RAC1112 : "Unable to delete the pending values for the specified device because the iDRAC internal storage is in use by a currently running job." 4.2.20.
4.2.20.189 RAC1115 : "Unable to run the command, because of insufficient user privileges." 4.2.20.190 RAC1116 : "Unable to run the command, because the restart flag entered is incorrect." 4.2.20.191 RAC1117 : "Unable to run the command." 4.2.20.192 RAC1118 : "Successfully initiated the update operation specified in the command." 4.2.20.193 RAC1119 : "Unable to generate a comparison report for the specified repository." 4.2.20.
(TSR) to a remote share." 4.2.20.211 RAC1141 : "The iDRAC firmware rollback operation was initiated." 4.2.20.212 RAC1142 : "Unable to start the Remote Diagnostics operation because the Expiration Time entered (difference between Start Time and Expiration Time) is less than five minutes." 4.2.20.213 RAC1143 : "Configuration results are not applicable for the job type for Job: ." When event is generated, message will have the following substitutions: • = "JobID" 4.2.20.
4.2.20.215 RAC1145 : "The entered log type is invalid." 4.2.20.216 RAC1146 : "Unable to set the SNMPv3 username because SNMPv3 is not enabled for the specified user on iDRAC." 4.2.20.217 RAC1147 : "Unable to set the SNMPv3 username entered in the command because the username is not present or enabled on iDRAC." 4.2.20.218 RAC1150 : "Unable to complete the export operation." 4.2.20.219 RAC1151 : "The export operation is unsuccessful." 4.2.20.220 RAC1152 : "The export operation completed successfully." 4.2.
4.2.20.232 RAC1164 : "A remote diagnostics operation is currently running and not completed." 4.2.20.233 RAC1165 : "Unable to configure the port number that is entered for either http or https ports of the iDRAC Web server, because the port number is already in use." 4.2.20.234 RAC1166 : "Successfully initiated Configuration XML file preview operation that was invoked by .
4.2.20.235 RAC1168 : "The RACADM "getconfig" command will be deprecated in a future version of iDRAC firmware." 4.2.20.236 RAC1169 : "The RACADM "config" command will be deprecated in a future version of iDRAC firmware." 4.2.20.237 RAC1170 : "Unable to find the SSL library in the default path." 4.2.20.238 RAC1175 : "Unable to change the user configuration because modifying the user configuration at index 1 is not allowed." 4.2.20.
• = "Param1" 4.2.21.5 RED074 : "A required parameter is not present." 4.2.21.6 RED075 : "An Automatic Backup schedule already exists." 4.2.22 Subcategory= Security Event [MessageID prefix =SEC] 4.2.22.1 SEC0700 : "Warning: Default username and password are currently in use. It is strongly recommended to change the default password before configuring the propery. Else, it causes a severe security risk for iDRAC." 4.2.22.2 SEC0701 : "Warning: Default username and password are currently in use.
4.2.23.12 STOR070 : "Unable to run the WS-MAN method , because an invalid parameter is entered." When event is generated, message will have the following substitutions: • = "Method" • = "Param" 4.2.23.13 STOR071 : "The specified Span Count is not valid for creating a RAID 10.
4.2.23.14 STOR072 : "iDRAC Service Module (ISM) is either not present or not running on the server OS." 4.2.23.15 STOR073 : "The iDRAC Service Module version present on the server OS does not support the requested PCIe SSD (NVMe) device operation." 4.2.23.16 STOR074 : "The requested RAID configuration operation is not allowed because the controller is currently in Non-RAID mode." 4.2.23.
present on the controller. Delete the preserved cache and retry the operation." 4.2.23.32 STOR0701 : "Storage objects are unavailable in the current system configuration." 4.2.23.
4.2.24 Subcategory= Software Config [MessageID prefix =SWC] 4.2.24.1 SWC0027 : "Successfully backed up a Server Profile by using the Lifecycle Controller GUI." 4.2.24.2 SWC0034 : "Unable to export the file to the network share." 4.2.24.3 SWC0035 : "Unable to initialize backup Server Profile operation." 4.2.24.4 SWC0036 : "Unable to launch hardware diagnostics." 4.2.24.5 SWC0037 : "Unable to export the file to the network share." 4.2.24.6 SWC0038 : "Unable to export the file to the network share." 4.2.24.
share folder." 4.2.24.39 SWC0072 : "Unable to export the Tech Support Report to destination folder." 4.2.24.40 SWC0073 : "Unable to start operation with the current iDRAC version." 4.2.24.41 SWC0074 : "Unable to start operation with the current iDRAC version." 4.2.24.42 SWC0075 : "Unable to perform RAID operations because the selected controller is in HBA mode." 4.2.24.
4.2.24.56 SWC1930 : "The iDRAC Quick Sync inactivity timeout feature is enabled." 4.2.24.57 SWC1931 : "The iDRAC Quick Sync inactivity timeout configuration is disabled." 4.2.24.58 SWC8619 : "The Chassis Management Controller is unable to process data from the server in slot ." When event is generated, message will have the following substitutions: • = "" 4.2.24.59 SWC8620 : "The Chassis Management Controller is unable to communicate with the iDRAC in server slot .
4.2.25.7 SYS050 : "The system configuration XML file for import configuration is not compliant with schema nesting checks." 4.2.25.8 SYS051 : "The system could not be shut down within the specified time." 4.2.25.9 SYS052 : "Analyzing iDRAC, System, or Lifecycle Controller configuration for changes to be applied." 4.2.25.10 SYS053 : "Successfully imported and applied system configuration XML file." 4.2.25.11 SYS054 : "No configuration changes requiring a system restart need to be applied." 4.2.25.
4.2.25.22 SYS065 : "Input file for import configuration operation cannot be found or opened." 4.2.25.23 SYS066 : "No changes detected for iDRAC, System, or Lifecycle Controller configuration." 4.2.25.24 SYS067 : "Unable to complete application of configuration XML file values." 4.2.25.25 SYS068 : "Configuration changes that require system reboot were not applied." 4.2.25.26 SYS069 : "No changes were applied since the current component configuration matched the requested configuration." 4.2.25.
imported to the system." 4.2.25.41 SYS088 : "Estimated time for applying configuration changes is seconds." When event is generated, message will have the following substitutions: • = "seconds" 4.2.25.42 SYS089 : "Preview of system configuration XML file is complete." 4.2.25.43 SYS090 : "The configuration XML input file contains unsupported DOCTYPE tags." 4.2.25.44 SYS091 : "Unable to complete the operation because the method is not supported." 4.2.25.
• = "JID_123456789098" 4.2.25.58 SYS152 : "Erase operations for some System Erase tasks did not complete successfully." 4.2.25.59 SYS153 : "Deleting hardware cache data for controller: ." When event is generated, message will have the following substitutions: • = "RAID.Integrated.1-1" 4.2.25.60 SYS154 : "Initiating secure erase operation on secure erase-capable drives for controller: .
4.2.25.62 SYS156 : "Erase operations for System Erase tasks successfully completed." 4.2.25.63 SYS157 : "Unable to successfully complete requested System Erase tasks." 4.2.25.64 SYS158 : "Hardware cache erase is unsuccessful." 4.2.25.65 SYS159 : "vFlash SD Card erase unsuccessful." 4.2.25.66 SYS160 : "The Lifecycle Controller logs are cleared." 4.2.25.67 SYS161 : "Tech Support Report related non-volitale storage deleted." 4.2.25.68 SYS162 : "Turning on the server to perform System Erase tasks." 4.2.25.
does not support TXT." 4.2.26.8 UEFI0045 : "Unable to enable the TXT feature because a TPM chip is not present." 4.2.26.9 UEFI0059 : "The Power Supply Units (PSUs) in the system do not match." 4.2.26.10 UEFI0060 : "Power required by the system exceeds the power supplied by the Power Supply Units (PSUs)." 4.2.26.11 UEFI0068 : "The mezzanine card configuration used is not supported on this Chassis." 4.2.26.12 UEFI0071 : "One or more UEFI network interfaces is not available.
• = "B2" 4.2.26.21 UEFI0089 : "Incompatible x16 data bus width DIMM is installed on memory slot: ." When event is generated, message will have the following substitutions: • = "A1" 4.2.26.22 UEFI0090 : "A DIMM with an incompatible number of ranks is installed on memory slot: ." When event is generated, message will have the following substitutions: • = "A6" 4.2.26.
4.2.26.28 UEFI0096 : "Unable to enable the Advanced ECC memory operating mode because the current DIMM population or system configuration does not support Advanced ECC mode." 4.2.26.29 UEFI0097 : "Unable to enable the Advanced ECC memory operating mode because of mismatches in the DIMM channel configurations." 4.2.26.30 UEFI0099 : "Unable to enable the Memory Mirroring feature because the current DIMM population or hardware configuration does not support the feature." 4.2.26.
4.2.26.35 UEFI0105 : "Unable to enable the Cluster on Die (COD) feature because of an unsupported memory configuration." 4.2.26.36 UEFI0113 : "Unable to enable the Fault Resilient Memory (FRM) feature because the current DIMM population or hardware configuration does not support the feature." 4.2.26.37 UEFI0114 : "Unable to enable the Fault Resilient Memory (FRM) operating mode because of mismatches in DIMM channel configurations." 4.2.26.
• = "RAID Controller in Slot 5" 4.3.1.2 BAT1001 : "Battery on was replaced." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.1.3 BAT1002 : "The battery on learn cycle has started." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.1.
4.3.1.11 BAT1023 : "The charge level for the battery on is within normal limits." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.1.12 BAT1024 : "Errors detected with battery on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.1.
4.3.1.20 BAT1033 : "The battery on was removed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.1.21 BAT1034 : "The battery properties for have changed." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.1.22 BAT1035 : "The battery temperature on is above the normal operating temperature.
• = "RAID Controller in Slot 5" 4.3.3.4 CTL12 : "An invalid SAS configuration has been detected on . Details: " When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" • = "SAS topology error: SMP function failed" 4.3.3.5 CTL13 : "The cache has been discarded.
4.3.3.13 CTL37 : "A Patrol Read operation started for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.14 CTL38 : "The Patrol Read operation completed for ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.15 CTL39 : "The reconstruct rate has changed.
• = "RAID Controller in Slot 5" 4.3.3.23 CTL48 : "A foreign configuration was detected on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.24 CTL49 : "The NVRAM has corrupted data on ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.25 CTL50 : "The NVRAM has corrupt data.
• = "RAID Controller in Slot 5" 4.3.3.32 CTL62 : " on has missing drives and will go offline at boot." When event is generated, message will have the following substitutions: • • = "not implemented" = " RAID Controller in Slot 5" 4.3.3.33 CTL63 : "Previous configuration was found completely missing during time boot on .
• = "RAID Controller in Slot 5" 4.3.3.41 CTL80 : " experienced the following warning during startup: ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" • = " PERC Controller Message" 4.3.3.42 CTL81 : "Security key assigned to is modified.
4.3.3.50 CTL89 : " is no longer fault tolerant because the peer controller is not available." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.51 CTL90 : " is not operating in Fault Tolerant Mode because of an incomptible peer controller." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.
• = "RAID Controller in Slot 5" • = " HBA" 4.3.3.59 CTL98 : "Security key assigned to ." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.60 CTL99 : "Security key assigned to is deleted." When event is generated, message will have the following substitutions: • = "RAID Controller in Slot 5" 4.3.3.
4.3.3.66 CTL202 : "Unable to open the firmware and driver configuration file of ." When event is generated, message will have the following substitutions: • = "lsiver.cfg" • = "Controller 1 (PERC H800 Adapter)" 4.3.3.67 CTL203 : "Abort Check Consistency on Error, Copyback or Auto Copyback on Predictive Failure, and Load Balance values are changed for .
4.3.3.74 CTL210 : "Disabled persistent hot spare on ." When event is generated, message will have the following substitutions: • = "Controller 1 (PERC H800 Adapter)" 4.3.3.75 CTL211 : "The property changed on through Manage Physical Disk Power option." When event is generated, message will have the following substitutions: • = "timeinterval" • = " Controller 1 (PERC H800 Adapter)" 4.3.3.
4.3.4 Subcategory= Diagnostic [MessageID prefix =DIAG] 4.3.4.1 DIAG0141 : "Hard Drive - No Hard Drive detected." 4.3.4.2 DIAG0142 : "Hard Drive - S/N , self test unsuccessful ." When event is generated, message will have the following substitutions: • = "0-0-0" • = " WD-WMAT16606510" • = "DST Long" • = ", terminated" 4.3.4.
• = "0x44" • = "Uncorrectable data error" 4.3.4.9 DIAG0149 : "Optical Drive - no drive detected." 4.3.4.10 DIAG0150 : "Hard Drive - No Hard Drive detected, or disk controller not supported." 4.3.4.11 DIAG0151 : "Hard Drive - S/N , incorrect status = <80000000000000??>\n.
• = "0" • = "1013000398" 4.3.4.17 DIAG8156 : "Tape Drive - S/N , no media, cannot test drive." When event is generated, message will have the following substitutions: • = "0" • = "1013000398" 4.3.4.18 DIAG8157 : " Drive - S/N , drive is not a supported drive.
• = "EMM 0 in Enclosure 0 on Connector 1 of RAID Controller in Slot 2" 4.3.5.3 ENC3 : " is shutdown." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.5.4 ENC12 : "Communication resumed on .
• = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.5.12 ENC26 : " is not responding." When event is generated, message will have the following substitutions: • = "Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.5.13 ENC28 : "Enclosure Management Module (EMM) firmware version mismatch detected in . .
• = "Fan 4 in Enclosure 0 on Connector 1 of RAID Controller in Slot 2" 4.3.7 Subcategory= Unknown [MessageID prefix =FLDC] 4.3.7.1 FLDC1001 : "The journal mirror at path = is available." When event is generated, message will have the following substitutions: • = "" 4.3.7.2 FLDC1002 : "The following journal mirror is being replaced: File Path Name = .
• = "" 4.3.7.9 FLDC1010 : "Caching is enabled on the with wwn = and path = ." When event is generated, message will have the following substitutions: • = "" 4.3.7.10 FLDC1012 : "Caching is disabled for the with WWN = and path = ." When event is generated, message will have the following substitutions: • = "" 4.3.7.
• = "" 4.3.7.20 FLDC1022 : "The associated server of the Cache Device with WWN = is not configured." When event is generated, message will have the following substitutions: • = "" 4.3.7.21 FLDC1023 : "Fluid Cache is running on an evaluation license and the evaluation license expires in days." When event is generated, message will have the following substitutions: • = "" 4.3.7.
4.3.7.32 FLDC1034 : "A valid license is not installed for Fluid Cache." 4.3.7.33 FLDC1035 : "Configuration changes are not allowed, because Fluid cache is running on an expired evaluation licesnse (Expired days: )." When event is generated, message will have the following substitutions: • = "" 4.3.7.34 FLDC1036 : "Caching functionality is disabled because Fluid cache is running on an expired evaluation license (Expired days: ).
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.6 PDR6 : " is offline." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.7 PDR8 : " is inserted." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.16 PDR41 : "The clear operation on was cancelled." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.17 PDR43 : "The clear operation on has completed.
4.3.8.25 PDR52 : "A redundant path is broken." 4.3.8.26 PDR53 : "A redundant path has been restored for ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.27 PDR54 : "A disk media error on was corrected during recovery.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.35 PDR63 : "A bad disk block on cannot be reassigned during a write operation." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.36 PDR64 : "An unrecoverable disk media error occurred on .
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.44 PDR79 : "A user terminated Copyback from to ." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" • = " Disk 6 in Enclosure 0 on Coonnector 0 of RAID Controller in Slot 5" 4.3.8.45 PDR81 : "Microcode update started on .
• = "Spun Down" 4.3.8.53 PDR93 : "Microcode update on has completed." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.54 PDR94 : "Microcode update on has timed out." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.
• = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.63 PDR106 : " is unassigned as dedicated hot-spare." When event is generated, message will have the following substitutions: • = "Disk 5 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.8.64 PDR107 : " is assigned as global hot-spare.
• = "PCIe Solid-State Drive in Slot 9 in Bay 1" 4.3.8.72 PDR116 : "Predictive failure reported for " When event is generated, message will have the following substitutions: • = "PCIe Solid-State Drive in Slot 9 in Bay 1" 4.3.8.73 PDR117 : "The has turned off because the critical temperature threshold is exceeded.
• = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 4.3.8.81 PDR213 : "The state of changed from Non-RAID to Ready." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 4.3.8.82 PDR214 : "The is not supported because it is not supplied by an authroized hardware provider.
4.3.9.6 PSU1005 : " is switched on." When event is generated, message will have the following substitutions: • = "PSU 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.9.7 PSU1006 : " was inserted." When event is generated, message will have the following substitutions: • = "PSU 1 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.9.8 PSU1007 : " has failed.
4.3.11.5 SSD1005 : "Successfully initialized ." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" 4.3.11.6 SSD1006 : "The has reached of warranted device wear-out limit." When event is generated, message will have the following substitutions: • = "Physical Disk 1:0:5 on Controller 0 at Connector 1" • = " 90%" 4.
4.3.12.3 STOR7 : "The storage management instrumentation is performing an inventory refresh operation." 4.3.12.4 STOR8 : "Detected two RAID controllers in integrated slots. This configuration is not currently supported and the second controller will not be powered on." 4.3.12.5 STOR9 : "No RAID controllers have been detected. Access to shared storage will not be available." 4.3.12.6 STOR10 : "Access to shared storage will not be available, because the RAID controller is unable to turn on." 4.3.12.
4.3.12.18 STOR0200 : "Array Manager is installed on the system." 4.3.12.19 STOR0201 : "Unable to determine whether the system has the minimum required versions of the RAID controller drivers and firmware." 4.3.12.20 STOR0202 : "The configuration file (Path: ) that contains firmware and driver information for is not updated or is incorrectly formatted to complete the comparison.
4.3.12.31 STOR0506 : "Unable to create virtual disk." 4.3.12.32 STOR0507 : "Insufficient physical disk space on selected RAID controller." 4.3.12.33 STOR0508 : "No supported controllers present for RAID configuration." 4.3.12.34 STOR0509 : "No RAID levels are supported." 4.3.12.35 STOR0510 : "Encryption configuration failed." 4.3.12.36 STOR0511 : "Unable to change the encryption key." 4.3.12.37 STOR0512 : "Unable to apply the encryption key." 4.3.12.38 STOR0513 : "Unable to encrypt virtual disks." 4.3.12.
4.3.14.5 TMP1003 : " has crossed the minimum failure threshold." When event is generated, message will have the following substitutions: • = "Temperature Sensor 0 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.14.6 TMP1004 : " has returned to normal." When event is generated, message will have the following substitutions: • = "Temperature Sensor 0 in Enclosure 0 on Connector 0 of RAID Controller in Slot 5" 4.3.
4.3.15.8 VDR12 : " reconfiguration has started." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.9 VDR14 : "The consistency check on was cancelled." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.10 VDR15 : "Initialization of was cancelled.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.18 VDR31 : "Controller cache is preserved for missing or offline ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.19 VDR32 : "Background initialization has started for .
• = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.28 VDR48 : " has inconsistent data." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.29 VDR50 : "Background Initialization (BGI) completed with uncorrectable errors on ." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 4.
• = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.37 VDR91 : "Consistency check for has detected multiple uncorrectable medium errors." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.38 VDR92 : "Consistency check for has completed with uncorrectable errors.
4.3.15.45 VDR100 : " is unavailable because of incompatibilities with the current controller." When event is generated, message will have the following substitutions: • = "Virtual Disk 0 on Integrated RAID Controller 1" 4.3.15.46 VDR101 : "Hot Spare Protection policy deviation with severity set at Informational level occured for .
• = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 4.3.15.53 VDR107 : "Successfully resized Controller Enhanced cache ()." When event is generated, message will have the following substitutions: • = "Virtual Disk 1 (Virtual Disk 1) on Controller 0 (PERC 5/i Integrated)" 4.3.15.54 VDR108 : "Successfully created Controller Enhanced cache ().
• = "fail-safe" 4.4.1.3 AMP0302 : "The system board current is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "fail-safe" 4.4.1.4 AMP0303 : "The system board current is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "fail-safe" 4.4.1.5 AMP0304 : "The system board current is outside of range.
• = "fail-safe" 4.4.1.12 AMP0311 : "Disk drive bay current is within range." When event is generated, message will have the following substitutions: • = "fail-safe" 4.4.1.13 AMP0312 : "System level current is less than the lower warning threshold." 4.4.1.14 AMP0313 : "System level current is less than the lower critical threshold." 4.4.1.15 AMP0314 : "System level current is greater than the upper warning threshold." 4.4.1.
• = " 100.000" 4.4.1.26 AMP404 : "The sensor detected an error with a value of A." When event is generated, message will have the following substitutions: • = "System Board Pwr Consumption" • = " 658" 4.4.1.27 AMP405 : "The sensor state has changed to a failed state with a value of A.
4.4.2.15 ASR201 : "The watchdog timer restarted the system at ." When event is generated, message will have the following substitutions: • = "Tue Jan 08 10:56:54 2013" 4.4.2.16 ASR202 : "The watchdog timer turned off the system at ." When event is generated, message will have the following substitutions: • = "Tue Jan 08 10:56:54 2013" 4.4.2.
• = "1" 4.4.3.13 BAT0012 : "The storage battery for disk drive bay has failed." When event is generated, message will have the following substitutions: • = "1" 4.4.3.14 BAT0013 : "The storage battery for disk drive bay is present." When event is generated, message will have the following substitutions: • = "1" 4.4.3.15 BAT0014 : "The storage battery for disk drive bay is absent.
4.4.3.21 BAT0030 : "The system board battery is reading low." 4.4.3.22 BAT0031 : "The system board battery status is unknown." 4.4.4 Subcategory= Chassis Management Controller [MessageID prefix =CMC] 4.4.4.1 CMC8502 : "Unable to access the IPv6 information of the server." 4.4.4.2 CMC8503 : "Unable to access the IPv4 information of the server." 4.4.4.3 CMC8504 : "Unable to access server: , because the NIC is disabled on the identified server.
• = "" 4.4.4.10 CMC8520 : "The FRU on server is not functioning." When event is generated, message will have the following substitutions: • = "" 4.4.4.11 CMC8521 : "The Mezz card 1 FRU for the server is not functioning." When event is generated, message will have the following substitutions: • = "" 4.4.4.12 CMC8522 : "The Mezz card 2 FRU for the server is not functioning.
4.4.4.19 CMC8534 : "Unable to turn on the server because the power requirement request exceeds the power cap value." When event is generated, message will have the following substitutions: • = "" 4.4.5 Subcategory= Processor [MessageID prefix =CPU] 4.4.5.1 CPU0000 : "CPU has an internal error (IERR)." When event is generated, message will have the following substitutions: • = "1" 4.4.5.2 CPU0001 : "CPU has a thermal trip (over-temperature) event.
4.4.5.9 CPU0008 : "CPU is disabled." When event is generated, message will have the following substitutions: • = "1" 4.4.5.10 CPU0009 : "CPU terminator is present." When event is generated, message will have the following substitutions: • = "1" 4.4.5.11 CPU0010 : "CPU is throttled." When event is generated, message will have the following substitutions: • = "1" 4.4.5.12 CPU0011 : "Uncorrectable Machine Check Exception detected on CPU .
• = "1" 4.4.5.19 CPU0701 : "CPU protocol error detected." When event is generated, message will have the following substitutions: • = "1" 4.4.5.20 CPU0702 : "CPU bus parity error detected." 4.4.5.21 CPU0703 : "CPU bus initialization error detected." 4.4.5.22 CPU0704 : "CPU machine check error detected." When event is generated, message will have the following substitutions: • = "1" 4.4.5.23 CPU0800 : "CPU voltage regulator module is present.
4.4.5.29 CPU0806 : "CPU voltage regulator module is incorrectly configure." When event is generated, message will have the following substitutions: • = "1" 4.4.5.30 CPU0816 : "CPU voltage regulator module is absent." When event is generated, message will have the following substitutions: • = "1" 4.4.5.31 CPU0817 : "CPU voltage regulator module is operating normally." When event is generated, message will have the following substitutions: • = "1" 4.
4.4.7.4 DIAG0114 : "Cache integrity test discrepancy " When event is generated, message will have the following substitutions: • = "Unable to start application processor(s)." 4.4.7.5 DIAG0115 : "CPU Stress Thermal condition. Limit C, Actual C." When event is generated, message will have the following substitutions: • = "60" • = "73" 4.4.7.6 DIAG0121 : "Memory errors detected, but successfully resolved." 4.4.7.
4.4.7.16 DIAG0213 : "System board - CMOS battery failure detected." 4.4.7.17 DIAG0221 : "System board - Interval timer not functional." 4.4.7.18 DIAG0232 : "RTC - did not generate periodic ticks." 4.4.7.19 DIAG0233 : "System board - RTC seconds count is not updating." 4.4.7.20 DIAG0234 : "System board - HPET <1>, incorrect time period. Expected = , Found = ." When event is generated, message will have the following substitutions: • <1> = "1" • = "1" • = "0" 4.4.7.
• = "CPU1" • = "78" 4.4.7.30 DIAG0315 : "Sensor: The () reading C) is lower than expected." When event is generated, message will have the following substitutions: • = "CPU1" • = "0" 4.4.7.31 DIAG0321 : "LCD EDID - Unable to access EDID EEPROM." 4.4.7.32 DIAG0322 : "LCD panel - Unable to modify brightness." 4.4.7.33 DIAG0323 : "Unable to detect inverter lamp status." 4.4.7.
4.4.7.46 DIAG 0414 : "Cables - not detected." When event is generated, message will have the following substitutions: • = "Inverter cable" 4.4.7.47 DIAG0415 : "Cables - Check the following cable, jumper, connection, or sensor: ." When event is generated, message will have the following substitutions: • = "Intrusion" 4.4.7.48 DIAG0511 : "Fan - The () fan failed to respond correctly.
• = "CPU Thermistor" • = "7" • = "8" 4.4.7.54 DIAG8003 : "Fan - Unable to set Manufacturing Mode." 4.4.7.55 DIAG8004 : "Fan - Unable to determine fan speeds." 4.4.7.56 DIAG8005 : "LCD BIST not supported. or Fan - Fan speed failure. Expected at least , observed ." When event is generated, message will have the following substitutions: • = "3500" • = "2600" 4.4.7.57 DIAG8006 : "Fan - Unable to set fans to speed.
• = "1" 4.4.7.64 DIAG8013 : "LCD doesnt support test commands." When event is generated, message will have the following substitutions: • = "LCD" 4.4.7.65 DIAG8014 : "ADDF module () device () failed with error code , number . No EPSA beep code mapped." When event is generated, message will have the following substitutions: • = "8008" • = "2" 4.4.7.66 DIAG8015 : "Unable to stop all APs. The system may be unstable and should be rebooted." 4.
4.4.7.74 DIAG8171 : "PCIe - PCI device in physical Slot , PciTag , is present but not responding" When event is generated, message will have the following substitutions: • = "1" • = "300" 4.4.7.75 DIAG8611 : "User reported not hearing speaker tone" 4.4.7.76 DIAG800B : "Retrieve vendor ID function error." 4.4.7.77 DIAG800C : "Get/Set inverter mode function error. Vendor: Revision: .
4.4.8.3 FAN0002 : "Fan RPM is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "1" 4.4.8.4 FAN0003 : "Fan RPM is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "1" 4.4.8.5 FAN0004 : "Fan RPM is outside of range." When event is generated, message will have the following substitutions: • = "1" 4.4.8.
• = "1" 4.4.8.13 FAN0012 : " RPM is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "Blower" 4.4.8.14 FAN0013 : " RPM is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "Blower" 4.4.8.15 FAN0014 : " RPM is greater than the upper warning threshold.
• = "Fan 1" 4.4.8.23 FAN0022 : "The sensor has failed, and the last recorded value by the sensor was RPM." When event is generated, message will have the following substitutions: • = "Fan 1" • = " 1" 4.4.8.24 FAN0024 : "The sensor returned to a normal state with a value of RPM." When event is generated, message will have the following substitutions: • = "Fan 1" • = " 1" 4.4.8.
• = " 1" 4.4.9.2 FC103 : "The FC port network connection is successfully started." When event is generated, message will have the following substitutions: • = "Slot 4" • = " 1" 4.4.10 Subcategory= Hardware Config [MessageID prefix =HWC] 4.4.10.1 HWC1000 : "The is present." When event is generated, message will have the following substitutions: • = "KVM" 4.4.10.2 HWC1001 : "The is absent.
4.4.10.12 HWC1201 : "The sled is removed from slot ." When event is generated, message will have the following substitutions: • = "VGA" • = "1" 4.4.10.13 HWC2000 : "The cable or interconnect is connected." When event is generated, message will have the following substitutions: • = "LCD" 4.4.10.14 HWC2001 : "The cable or interconnect is not connected or is improperly connected.
4.4.10.21 HWC2008 : "A fabric mismatch detected for mezzanine card ." When event is generated, message will have the following substitutions: • = "B1" 4.4.10.22 HWC2009 : "Mezzanine card is installed correctly." When event is generated, message will have the following substitutions: • = "B1" 4.4.10.23 HWC2010 : "The riser board cable or interconnect is connected." 4.4.10.24 HWC2011 : "The riser board cable or interconnect is not connected, or is improperly connected.
4.4.10.31 HWC3006 : "Unable to QuickDeploy server in slot ." When event is generated, message will have the following substitutions: • = "1" 4.4.10.32 HWC4000 : "A hardware incompatibility detected between BMC/iDRAC firmware and CPU." 4.4.10.33 HWC4001 : "A hardware incompatibility was corrected between BMC/iDRAC firmware and CPU." 4.4.10.34 HWC4002 : "A hardware incompatibility detected between BMC/iDRAC firmware and other hardware." 4.4.10.
4.4.10.42 HWC4018 : "A hardware incompatibility was corrected between and ." When event is generated, message will have the following substitutions: • = "Server" • = " in slot 1" • = " PSU" • = " in slot 1" 4.4.10.
• = "Main System Chassis" • = " vFlash" • = " NULL" 4.4.10.49 HWC8008 : "The SD card has failed. SD card location: , SD card device type: , SD card state: ." When event is generated, message will have the following substitutions: • = "Main System Chassis" • = " vFlash" • = " NULL" 4.4.10.50 HWC8009 : "SD card device sensor value unknown. SD card location: , SD card device type: , SD card state: .
4.4.11.2 IOV105 : "Unable to manage PCIE adapter located in ." When event is generated, message will have the following substitutions: • = "" 4.4.11.3 IOV106 : "Unable to power on PCIe adapter in ." When event is generated, message will have the following substitutions: • = "" 4.4.11.4 IOV107 : "PCIe adapter in slot was removed while powered on.
• = "" 4.4.11.14 IOV2005 : "The Chassis Management Controller (CMC) detected an issue in the 3.3 Volt Regulator of the PCIe module present in PCIe slot ." When event is generated, message will have the following substitutions: • = "" 4.4.11.15 IOV2006 : "The power-related issue of the PCIe device in slot is resolved." When event is generated, message will have the following substitutions: • = "" 4.4.11.16 IOV2007 : "The 3.
• = "Command" 4.4.13.2 LOG322 : "The log size is no longer near the maximum capacity. Log type: ." When event is generated, message will have the following substitutions: • = "Command" 4.4.13.3 LOG323 : "The log size is near maximum capacity. Log type: ." When event is generated, message will have the following substitutions: • = "Command" 4.4.13.4 LOG324 : "The log size has reached its maximum capacity. Log type: .
4.4.14.5 MEM0004 : "Memory device at location is disabled." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.6 MEM0005 : "Persistent correctable memory error limit reached for a memory device at location(s) ." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.7 MEM0006 : "Memory device at location is present.
4.4.14.14 MEM0021 : "Persistent correctable memory error limit reset for a memory device at location ." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.15 MEM0022 : "Memory device at location is absent." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.16 MEM0024 : "Memory device at location is no longer spare memory.
4.4.14.23 MEM1001 : "Memory device at location failed to transition to a running state." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.24 MEM1002 : "Memory device at location is in test." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.25 MEM1003 : "Memory device at location failed to transition to in test.
• = "DIMM1" 4.4.14.33 MEM1011 : "Memory device at location is on-duty." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.34 MEM1012 : "Memory device at location is in a degraded state." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.35 MEM1013 : "Memory device at location is in a full state.
• = "DIMM1" 4.4.14.43 MEM1203 : "Memory is not redundant." 4.4.14.44 MEM1204 : "Memory mirror is redundant." 4.4.14.45 MEM1205 : "Memory mirror redundancy is lost. Check memory device at location(s) ." When event is generated, message will have the following substitutions: • = "DIMM1" 4.4.14.46 MEM1206 : "Memory mirror redundancy is degraded. Check memory device at location .
• = "DIMM_A1" 4.4.14.56 MEM6003 : "Memory device status is non-critical. Memory device location: , Possible memory module event cause: ." When event is generated, message will have the following substitutions: • = "DIMM_A1" • = " Single bit error logging disabled" 4.4.14.57 MEM6004 : "Memory device status is critical. Memory device location: , Possible memory module event cause: .
4.4.14.66 MEM9003 : "Intel SMI 2 Memory interconnect has a correctable error." When event is generated, message will have the following substitutions: • = "1" 4.4.14.67 MEM9004 : "Intel QPI interconnect has degraded." When event is generated, message will have the following substitutions: • = "1" 4.4.14.68 MEM9005 : "Intel SMI 2 Memory interconnect has degraded.
4.4.16 Subcategory= OS Event [MessageID prefix =OSE] 4.4.16.1 OSE0000 : "A critical stop occurred during OS load." 4.4.16.2 OSE0001 : "A runtime critical stop occurred." 4.4.16.3 OSE0002 : "An OS graceful stop occurred." 4.4.16.4 OSE0003 : "An OS graceful shut-down occurred." 4.4.16.5 OSE0004 : "A soft shut-down initiated by platform event filter." 4.4.16.6 OSE0005 : "Agent is not responding." 4.4.16.7 OSE1000 : "A: boot completed." 4.4.16.8 OSE1001 : "Failed to boot from A." 4.4.16.
4.4.17.4 PCI1308 : "A PCI parity error was detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 4.4.17.5 PCI1310 : "A PCI system error was detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 4.4.17.
4.4.17.10 PCI1320 : "A bus fatal error was detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 4.4.17.11 PCI1321 : "A high-severity issue is detected in a component of the bus , device 0, function ." When event is generated, message will have the following substitutions: • = "1" • = "1" 4.4.17.
• = "1" 4.4.17.19 PCI1356 : "A bus uncorrectable error was detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 4.4.17.20 PCI1358 : "A fatal error was detected on a component at slot ." When event is generated, message will have the following substitutions: • = "1" 4.4.17.21 PCI1360 : "A bus fatal error was detected on a component at slot .
4.4.17.27 PCI3000 : "Device option ROM on embedded NIC failed to support Link Tuning or FlexAddress." 4.4.17.28 PCI3001 : "Device option ROM on embedded NIC was successfully updated." 4.4.17.29 PCI3002 : "Failed to program virtual MAC address on a component at bus device function ." When event is generated, message will have the following substitutions: • • • = "1" = "1" = "1" 4.4.17.
• = "1" • = "1" • = "1" 4.4.17.37 PCI3010 : "A non-fatal IO error detected on a component at bus device function ." When event is generated, message will have the following substitutions: • = "1" • = "1" • = "1" 4.4.17.38 PCI3011 : "The component at bus device function recovered from a non-fatal IO error.
4.4.17.47 PCI3020 : "A low-severity issue is detected in a component of the bus , device 0, function ." When event is generated, message will have the following substitutions: • = "1" • = "1" 4.4.17.48 PCI5004 : "A power fault issue is detected in the PCIe adapter that was turned on in PCIe slot." When event is generated, message will have the following substitutions: • = "" 4.4.17.
4.4.18.3 PDR1002 : "A predictive failure detected on drive in disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 4.4.18.4 PDR1016 : "Drive is removed from disk drive bay ." When event is generated, message will have the following substitutions: • = "1" • = "0" 4.4.18.5 PDR1017 : "Drive in disk drive bay is operating normally.
• = "1" 4.4.18.12 PDR1117 : "Drive is operating normally." When event is generated, message will have the following substitutions: • = "1" 4.4.19 Subcategory= System Performance Event [MessageID prefix =PFM] 4.4.19.1 PFM0001 : "The value of is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "CPU Usage" 4.4.19.
4.4.20 Subcategory= BIOS POST [MessageID prefix =PST] 4.4.20.1 PST0000 : "Unrecognized Post Code." 4.4.20.2 PST0001 : "System Power On." 4.4.20.3 PST0002 : "CPU Microcode load." 4.4.20.4 PST0003 : "Chipset Initialization." 4.4.20.5 PST0004 : "Memory Configuration." 4.4.20.6 PST0005 : "Shadow BIOS." 4.4.20.7 PST0006 : "Multiprocessor Initialization." 4.4.20.8 PST0007 : "POST processing start." 4.4.20.9 PST0008 : "System Management Mode (SMM)initialization." 4.4.20.
• = "1" 4.4.21.2 PSU0001 : "Power supply failed." When event is generated, message will have the following substitutions: • = "1" 4.4.21.3 PSU0002 : "A predictive failure detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 4.4.21.4 PSU0003 : "The power input for power supply is lost." When event is generated, message will have the following substitutions: • = "1" 4.4.21.
• = "1" 4.4.21.12 PSU0032 : "The temperature for power supply is in a warning range." When event is generated, message will have the following substitutions: • = "1" 4.4.21.13 PSU0033 : "The temperature for power supply is outside of range." When event is generated, message will have the following substitutions: • = "1" 4.4.21.14 PSU0034 : "An under voltage fault detected on power supply .
• = "1" 4.4.21.22 PSU0042 : "An output over current fault detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 4.4.21.23 PSU0043 : "An output under current fault detected on power supply ." When event is generated, message will have the following substitutions: • = "1" 4.4.21.24 PSU0044 : "Cannot obtain status information from power supply .
4.4.21.31 PSU0090 : "Power supply wattage mismatch corrected." When event is generated, message will have the following substitutions: • = "1" 4.4.21.32 PSU0091 : "Power supply unit rating exceeds the system power distribution limits." When event is generated, message will have the following substitutions: • = "1" 4.4.21.33 PSU0092 : "Power supply unit rating is appropriate for the system power distribution limits.
4.4.23 Subcategory= Power Usage [MessageID prefix =PWR] 4.4.23.1 PWR200 : "Enabling the Max Power Conservation Mode (MPCM) feature will disable the Extended Power Performance (EPP) feature." 4.4.23.2 PWR201 : "Selecting the Server Based Power Management Mode option sets your power cap to a maximum value, server priorities to a default priority, and then disables the Max Power Conservation Mode. Do you want to continue?" 4.4.23.
because the PSU in slot is not a 3000 W PSU." When event is generated, message will have the following substitutions: • = "" 4.4.23.17 PWR220 : "The Extended Power Performance (EPP) feature cannot be enabled because slot is empty.
4.4.23.18 PWR221 : "The Extended Power Performance (EPP) feature is already disabled." 4.4.23.19 PWR222 : "The Extended Power Performance (EPP) feature is already enabled." 4.4.23.20 PWR223 : "Cannot perform a 110V AC operation because the Extended Power Performance (EPP) feature is enabled." 4.4.23.21 PWR1000 : "The system performance restored." 4.4.23.22 PWR1001 : "The system performance degraded." 4.4.23.23 PWR1002 : "The system performance degraded because of thermal protection." 4.4.23.
4.4.23.37 PWR8557 : "The System Input Power Cap is too low to be enforced using the current Power Supply configuration." 4.4.23.38 PWR8558 : "The System Input Power Cap is being enforced with the current Power Supply configuration." 4.4.24 Subcategory= RAC Event [MessageID prefix =RAC] 4.4.24.1 RAC0560 : "RAC Software Initialization Error" 4.4.24.2 RAC0561 : "iDRAC to CMC communication link is not functioning for agent free monitoring of chassis PCIe slots." 4.4.24.
• = "12v" 4.4.25.20 RDU0031 : "The voltage redundancy is lost." When event is generated, message will have the following substitutions: • = "12v" 4.4.25.21 RDU0032 : "The voltage redundancy is degraded." When event is generated, message will have the following substitutions: • = "12v" 4.4.25.22 RDU0033 : "The voltage is not redundant." When event is generated, message will have the following substitutions: • = "12v" 4.4.
4.4.26.7 RFL2007 : "Internal Dual SD Module is writable." When event is generated, message will have the following substitutions: • = "SD1" 4.4.26.8 RFL2008 : "Internal Dual SD Module is disabled." When event is generated, message will have the following substitutions: • = "SD1" 4.4.26.9 RFL2009 : "Internal Dual SD Module is enabled." When event is generated, message will have the following substitutions: • = "SD2" 4.4.
4.4.28 Subcategory= IDSDM Redundancy [MessageID prefix =RRDU] 4.4.28.1 RRDU0001 : "Internal Dual SD Module is redundant." 4.4.28.2 RRDU0002 : "Internal Dual SD Module redundancy is lost." 4.4.28.3 RRDU0003 : "Internal Dual SD Module redundancy is degraded." 4.4.28.4 RRDU0004 : "Internal Dual SD Module is not redundant." 4.4.28.5 RRDU0006 : "Internal Dual SD Module rebuild initiated." 4.4.28.6 RRDU0007 : "Internal Dual SD Module rebuild completed successfully." 4.4.28.
sensor." 4.4.29.14 SEC0052 : "Chassis intrusion sensor may have failed." 4.4.29.15 SEC0612 : "The default username and password is currently in use. It is recommended to immediately change the default credentials." 4.4.29.16 SEC0613 : "The default username and password is changed." 4.4.30 Subcategory= Sys Event Log [MessageID prefix =SEL] 4.4.30.1 SEL0004 : "Log cleared." 4.4.30.2 SEL0006 : "All event logging is disabled." 4.4.30.3 SEL0008 : "System event log (SEL) is full." 4.4.30.
• = " A1" • = " 1" 4.4.31.3 SWC4012 : "A firmware or software incompatibility is detected between and ." When event is generated, message will have the following substitutions: • = "iDRAC" • = " in slot 1" • = " BIOS" • = " in slot 1" 4.4.31.
4.4.31.5 SWC5003 : "System Controller (SC) has either stopped functioning or is updating a firmware version." 4.4.31.6 SWC5004 : "System Controller (SC) has restarted functioning." 4.4.32 Subcategory= System Info [MessageID prefix =SYS] 4.4.32.1 SYS083 : "Unable to export ePSA Diagnostics results because iDRAC internal storage could not be accessed." 4.4.32.
• = " present" • = " present" 884
4.4.32.14 SYS115 : "The power cord sensor is non-functional." 4.4.32.15 SYS116 : "Unable to determine the status of the power cord." 4.4.32.16 SYS117 : "The input power supply is restored." 4.4.32.17 SYS118 : "The input power supply is not available." 4.4.32.18 SYS119 : "Unable to expose the OS Collector to the server OS." 4.4.32.19 SYS120 : "Unable to complete the operation because the OS Collector is taking too much time. The operation is cancelled." 4.4.32.
Lifecycle Controller is not enabled." 4.4.32.37 SYS138 : "Unable to start the collection of OS and Application Data because the server is turned off." 4.4.32.38 SYS139 : "Unable to start the collection of OS and Application Data because the server is in POST and has not finished startup." 4.4.32.39 SYS140 : "Unable to start the collection of OS and Application Data because the iDRAC Service Module (iSM) is not running in the server OS." 4.4.32.
4.4.32.51 SYS181 : "Unable to collect OS and Application Data because the OS Collector is not installed on the iDRAC." 4.4.32.52 SYS182 : "Unable to collect OS and Application Data because another Lifecycle Controller operation is currently in progress." 4.4.32.53 SYS183 : "Unable to allocate memory because of insufficient storage space in iDRAC." 4.4.32.54 SYS184 : "Unable to compute the checksum because OS Collector files are not readable." 4.4.32.
• = "Inlet" 4.4.33.6 TMP0105 : "The system board temperature is within range." When event is generated, message will have the following substitutions: • = "Inlet" 4.4.33.7 TMP0106 : "The memory module temperature is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "1" 4.4.33.8 TMP0107 : "The memory module temperature is less than the lower critical threshold.
• = "Planer" 4.4.33.15 TMP0114 : "The temperature is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "Planer" 4.4.33.16 TMP0115 : "The temperature is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "Planer" 4.4.33.17 TMP0116 : "The temperature is outside of range.
4.4.33.19 TMP0118 : "The system inlet temperature is less than the lower warning threshold." 4.4.33.20 TMP0119 : "The system inlet temperature is less than the lower critical threshold." 4.4.33.21 TMP0120 : "The system inlet temperature is greater than the upper warning threshold." 4.4.33.22 TMP0121 : "The system inlet temperature is greater than the upper critical threshold." 4.4.33.23 TMP0122 : "The system inlet temperature is outside of range." 4.4.33.
• = "1" 4.4.33.41 TMP0201 : "CPU temperature is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "1" 4.4.33.42 TMP0202 : "CPU temperature is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "1" 4.4.33.43 TMP0203 : "CPU temperature is greater than the upper critical threshold.
4.4.33.51 TMP502 : "The sensor has returned to a normal state with a value of degrees Celsius." When event is generated, message will have the following substitutions: • = "System Board Inlet Temp" • = " 27" 4.4.33.52 TMP503 : "The sensor state has changed to a warning state with a value of degrees Celsius.
4.4.34 Subcategory= Temperature Statistics [MessageID prefix =TMPS] 4.4.34.1 TMPS0100 : "Inlet temperature is above warning level for extended duration." 4.4.34.2 TMPS0101 : "Inlet temperature is above critical level for extended duration." 4.4.34.3 TMPS0102 : "Inlet temperature is above warning level for extended duration." 4.4.34.4 TMPS0103 : "Inlet temperature is above critical level for extended duration." 4.4.35 Subcategory= UEFI Event [MessageID prefix =UEFI] 4.4.35.
in Recovery mode." 4.4.35.19 UEFI0018 : "Lifecycle Controller (LC) is unable to complete a requested task or function and therefore is in Recovery Mode." 4.4.35.20 UEFI0019 : "Lifecycle Controller (LC) is unable to complete a requested task or function and prevented the boot process from completing on multiple attempts. LC is in Recovery Mode." 4.4.35.21 UEFI0022 : "Unable to initialize Management Engine because the Management Engine is not responding." 4.4.35.
4.4.35.29 UEFI0032 : "Unable to initialize the TPM chip because the TPM chip is not functioning." 4.4.35.30 UEFI0034 : "A CMOS battery loss is detected resulting in an invalid BIOS configuration." 4.4.35.31 UEFI0036 : "Unable to initialize the iDRAC Shared Memory Architecture (SMA) interface." 4.4.35.32 UEFI0037 : "Unable to communicate with iDRAC because of an issue in the iDRAC Shared Memory Architecture (SMA) Intelligent Platform Management Interface (IPMI)." 4.4.35.
• = "Bus: 0 Dev: 0 Func: 18" 4.4.35.47 UEFI0067 : "A PCIe link training failure is observed in and device link is disabled." When event is generated, message will have the following substitutions: • = "Bus: 4 Dev: 0 Func: 0" 4.4.35.48 UEFI0069 : "A CMOS checksum error has occurred. CMOS is reinitialized." 4.4.35.49 UEFI0070 : "One or more correctable PCIe errors have occurred." 4.4.35.50 UEFI0076 : "One or more Corrected Machine Check(CMC) errors have occurred.
4.4.35.61 UEFI0106 : "One or more memory correctable training errors have occurred on memory slot: " When event is generated, message will have the following substitutions: • = "A1" 4.4.35.62 UEFI0107 : "One or more memory errors have occurred on memory slot: ." When event is generated, message will have the following substitutions: • = "A2" 4.4.35.63 UEFI0108 : "One or more memory errors have occurred on memory slot: .
4.4.35.68 UEFI0115 : "The Management Engine firmware has recovered from one or more correctable errors." 4.4.35.69 UEFI0116 : "One or more boot drivers have reported issue(s)." 4.4.35.70 UEFI0117 : "Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 1." 4.4.35.71 UEFI0118 : "Card identification signature is not present on Internal Dual Secure Digital Module (IDSDM) SD card 2." 4.4.35.
Controller (LC) firmware was not accessible." 4.4.35.86 UEFI0142 : "Unable to enter System Service Mode (SSM) because the Lifecycle Controller (LC) firmware was unable to complete a requested task or function." 4.4.35.87 UEFI0144 : "One or more memory errors have occurred on memory slot: ." When event is generated, message will have the following substitutions: • = "A1" 4.4.35.88 UEFI0146 : "Unable to verify the chassis type via iDRAC and CMC.
4.4.36.8 VFL1015 : "Removable Flash Media is writable." When event is generated, message will have the following substitutions: • = "vFlash" 4.4.37 Subcategory= vFlash Absent [MessageID prefix =VFLA] 4.4.37.1 VFLA1000 : "Removable Flash Media is absent." When event is generated, message will have the following substitutions: • = "vFlash" 4.4.38 Subcategory= Voltage [MessageID prefix =VLT] 4.4.38.1 VLT0104 : "Processor module voltage is outside of range.
4.4.38.7 VLT0204 : "The system board voltage is outside of range." When event is generated, message will have the following substitutions: • = "VRM" 4.4.38.8 VLT0205 : "The system board voltage is within range." When event is generated, message will have the following substitutions: • = "12" 4.4.38.9 VLT0206 : "The memory module voltage is less than the lower warning threshold.
• = "VRM" 4.4.38.15 VLT0212 : "The disk drive bay voltage is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "VRM" 4.4.38.16 VLT0213 : "The disk drive bay voltage is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "VRM" 4.4.38.17 VLT0214 : "The disk drive bay voltage is greater than the upper warning threshold.
• = "VRM" 4.4.38.24 VLT0221 : "The voltage is greater than the upper critical threshold." When event is generated, message will have the following substitutions: • = "VRM" 4.4.38.25 VLT0222 : "The voltage is outside of range." When event is generated, message will have the following substitutions: • = "VRM" 4.4.38.26 VLT0223 : "The voltage is within range." When event is generated, message will have the following substitutions: • = "VRM" 4.4.38.
• = "A" 4.4.38.33 VLT0230 : "The mezzanine card voltage is less than the lower warning threshold." When event is generated, message will have the following substitutions: • = "B1" • = "VRM" 4.4.38.34 VLT0231 : "The mezzanine card voltage is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "B1" • = "VRM" 4.4.38.
4.4.38.40 VLT0301 : "CPU voltage is less than the lower critical threshold." When event is generated, message will have the following substitutions: • = "1" • = "VRM" 4.4.38.41 VLT0302 : "CPU voltage is greater than the upper warning threshold." When event is generated, message will have the following substitutions: • = "1" • = "VRM" 4.4.38.42 VLT0303 : "CPU voltage is greater than the upper critical threshold.
• = "System Board 1.5V PG" • = " 1.4" 4.4.38.48 VLT403 : "The sensor state has changed to a warning state with a value of Volts." When event is generated, message will have the following substitutions: • = "System Board 1.5V PG" • = " 2" 4.4.38.49 VLT404 : "The sensor detected an error with a value of Volts.
4.5.3.2 RED026 : "An internal error occurred while processing updates." 4.5.3.3 RED027 : "Insufficient space to upload the requested file." 4.5.3.4 RED028 : "Update files were not selected." 4.5.3.5 RED029 : "A reboot is pending." 4.5.3.6 RED030 : "Reboot is complete." 4.5.3.7 RED031 : "Approaching maximum size limit allowed for storing firmware images." 4.5.3.8 RED032 : "Reached maximum size limit allowed for storing firmware images. Deleted all rollback firmware images." 4.5.3.
• = "JID" 4.5.3.17 RED041 : "A recurring operation of type was not created because the required license is not available." When event is generated, message will have the following substitutions: • = "AutoTask" 4.5.3.18 RED042 : "A recurring operation of type was not created because the necessary user access rights are not available." When event is generated, message will have the following substitutions: • = "AutoTask" 4.5.3.
• = "AutoTask" 4.5.3.25 RED049 : "The job is deleted because the recurring operation is currently not enabled." When event is generated, message will have the following substitutions: • = "JID" • = "AutoTask" 4.5.3.26 RED050 : "The specified user credentials necessary for downloading an update package were not correct." 4.5.3.27 RED051 : "The network file transfer of an update package was not successful." 4.5.3.
4.5.3.36 RED060 : "The specified repository catalog is not supported." 4.5.3.37 RED061 : "The job is successfully scheduled." 4.5.3.38 RED062 : "Unable to successfully authenticate user credentials to the specified repository." 4.5.3.39 RED063 : "The iDRAC firmware updated successfully.
4.5.3.50 RED081 : "The Automatic Update schedule already exists." 4.5.3.51 RED082 : "The requested job cannot be scheduled, because job schedule type such as Automatic Backup or Automatic Update is not enabled." 4.5.3.52 RED083 : "The Chassis firmware is not updated because the version currently on the Chassis is same as the requested version." 4.5.3.53 RED084 : "Unable to update the Chassis firmware. There is a comm. issue between iDRAC and Chassis Management Controller (CMC)." 4.5.3.
4.5.3.64 RED095 : "rSPI update for Diags failed." 4.5.4 Subcategory= FW Update Job [MessageID prefix =SUP] 4.5.4.1 SUP026 : "The input value entered for the parameter is invalid." When event is generated, message will have the following substitutions: • = "Param1" 4.5.4.2 SUP027 : "Missing required parameter " When event is generated, message will have the following substitutions: • = "Param1" 4.5.4.
4.5.4.10 SUP0525 : "Unable to verify the digital signature of the Update Package." 4.5.4.11 SUP0526 : "Unable to continue with firmware update." 4.5.4.12 SUP0527 : "The Update Package is not supported for this system." 4.5.4.13 SUP0528 : "Unable to generate a firmware comparison table." 4.5.4.14 SUP0529 : "Unable to access repository." 4.5.4.15 SUP0530 : "Incorrect repository path location." 4.5.4.16 SUP0531 : "Unable to install the Update Packages." 4.5.4.
4.5.4.24 SUP0539 : "Update Packages missing in the repository." 4.5.5 Subcategory= Software Config [MessageID prefix =SWC] 4.5.5.1 SWC5005 : "Unable to update the System Controller (SC) firmware" 4.5.5.2 SWC5006 : "System Controller (SC) Firmware Update Successful" 4.5.6 Subcategory= Software Change [MessageID prefix =SWU] 4.5.6.1 SWU8500 : "The request to Lifecycle Controller on server was not successful.
• = "" 4.5.6.8 SWU8513 : "Successfully updated the IOM infrastructure firmware of slot ." When event is generated, message will have the following substitutions: • = "" 4.5.6.9 SWU8514 : "Unable to update the IOM infrastructure firmware of slot . ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 4.5.6.10 SWU8515 : "Unable to update the IOM firmware.
4.5.6.16 SWU8521 : "The firmware update operation of the iDRAC on the server in slot was stopped. The selected Image file is not compatible with the server hardware." When event is generated, message will have the following substitutions: • = "" 4.5.6.17 SWU8522 : "Unable to update the iDRAC on the server in firmware: ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 4.5.6.
4.5.6.22 SWU8527 : "Successfully completed the iKVM firmware update." 4.5.6.23 SWU8528 : "Unable to update the iKVM firmware, because of a checksum error." 4.5.6.24 SWU8529 : "Unable to update the iKVM firmware, because the Image file was not transferred to the iKVM target." 4.5.6.25 SWU8530 : "Unable to update the iKVM firmware." 4.5.6.26 SWU8531 : "Unable to update the iKVM firmware. The firmware update timeout limit is exceeded." 4.5.6.
4.5.6.34 SWU8540 : "Unable to update the PSU firmware, because the transfer of Image file is not successful. ErrorCode=0x." When event is generated, message will have the following substitutions: • = "" 4.5.6.35 SWU8541 : "Unable to update the PSU firmware, because the Image file is not accessible. ErrorCode=0x.
4.5.6.36 SWU8542 : "Unable to update the Active CMC firmware. The Image file transfer process was not successful." 4.5.6.37 SWU8543 : "Unable to update the Active CMC firmware. The Image file was not accessible." 4.5.6.38 SWU8544 : "Unable to update the Standby CMC firmware because the Standby CMC could not be prepared for firmware update." 4.5.6.39 SWU8545 : "Unable to update the Standby CMC firmware." 4.5.6.40 SWU8546 : "Unable to update the Standby CMC firmware." 4.5.6.
automatically turned off in 5 seconds." 4.6 Category: Work Notes 4.6.1 Subcategory= UEFI Event [MessageID prefix =UEFI] 4.6.1.1 UEFI0050 : "The process of collecting Brand information is started." 4.6.1.2 UEFI0051 : "Brand information is successfully collected. The system is being restarted." 4.6.1.3 UEFI0053 : "The debranding process is started." 4.6.1.4 UEFI0054 : "Debranding process is completed. The system is being restarted." 4.6.2 Subcategory= User Tracking [MessageID prefix =USR] 4.6.2.
