- Notes, Cautions, and Warnings
- Introduction
- AMP Event Messages
- ASR Event Messages
- BAR Event Messages
- BAT Event Messages
- BIOS Event Messages
- BOOT Event Messages
- CBL Event Messages
- CMC Event Messages
- CPU Event Messages
- CPUA Event Messages
- CTL Event Messages
- DH Event Messages
- DIAG Event Messages
- DIS Event Messages
- DKM Event Messages
- ECM Event Messages
- ENC Event Messages
- EPP Event Messages
- FAN Event Messages
- FC Event Messages
- FCD Event Messages
- FLDC Event Messages
- FSD Event Messages
- HWC Event Messages
- IOID Event Messages
- IOV Event Messages
- IPA Event Messages
- ISM Event Messages
- JCP Event Messages
- LC Event Messages
- LIC Event Messages
- LNK Event Messages
- LOG Event Messages
- MEM Event Messages
- NIC Event Messages
- OSD Event Messages
- OSE Event Messages
- PCI Event Messages
- PDR Event Messages
- PFM Event Messages
- POW Event Messages
- PR Event Messages
- PST Event Messages
- PSU Event Messages
- PSUA Event Messages
- PWR Event Messages
- RAC Event Messages
- RDU Event Messages
- RED Event Messages
- RFL Event Messages
- RFLA Event Messages
- RFM Event Messages
- RRDU Event Messages
- RSI Event Messages
- SEC Event Messages
- SEL Event Messages
- SSD Event Messages
- STOR Event Messages
- SUP Event Messages
- SWC Event Messages
- SWU Event Messages
- SYS Event Messages
- TMP Event Messages
- TMPS Event Messages
- TST Event Messages
- UEFI Event Messages
- USR Event Messages
- VDR Event Messages
- VF Event Messages
- VFL Event Messages
- VFLA Event Messages
- VLT Event Messages
- VME Event Messages
- VRM Event Messages
Event and Error Message Reference Guide for 13th Generation Dell PowerEdge ServersVersion 1.2
LOG Event Messages
LOG001
- Message
- Missing required InstanceID or JobID parameter.
- Detailed Description
- One or more required parameters needed for the method invoked in the operation are missing.
- Recommended Response Action
- To provide the correct value for the specified parameter, see Lifecycle Controller-Remote Services documentation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG002
- Message
- Invalid parameter value for InstanceID.
- Detailed Description
- The value provided for the specified parameter is invalid.
- Recommended Response Action
- To provide the correct value for the specified parameter, see Lifecycle Controller-Remote Services documentation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG003
- Message
- ConfigResults not available for log entry specified.
- Detailed Description
- The log entry with the specified InstanceID does not have any associated configuration results.
- Recommended Response Action
- Verify the ConfigResults availability for the InstanceID through enumeration of the LogEntry class and retry the operation. Refer to the Lifecycle Controller-Remote Services documentation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG004
- Message
- Resource allocation failure.
- Detailed Description
- The operation did not complete successfully because of lack of memory or file space in iDRAC firmware.
- Recommended Response Action
- Reset iDRAC and retry the operation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
LOG005
- Message
- Cannot perform the operation due to an unknown error in iDRAC.
- Detailed Description
- The operation did not complete successfully because of an unknown error in iDRAC.
- Recommended Response Action
- Retry the operation. If the issue persists, reset the iDRAC.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG006
- Message
- Test event generated for message ID arg1 .
- Arguments
- arg1 = message ID
- Detailed Description
- This message is generated while performing a Test Event action. Performing a Test Event action logs an event in the Lifecycle Log with the user specified message ID. It may also generate events through SNMP, email, or other event notification sources if they are enabled. The test event does not indicate that there is a hardware or software problem. It provides a mechanism for users to test their event processing applications.
- Recommended Response Action
- No response action is required.
- Category
- Audit (LOG = Log event)
- Severity
- Severity 3 (Informational)
LOG007
- Message
- The previous log entry was repeated arg1 times.
- Arguments
- arg1 = log entry count
- Detailed Description
- This message is generated after a series of sequential duplicate events. Log entry count is the number of times the previous message was repeated.
- Recommended Response Action
- No response action is required.
- Category
- Audit (LOG = Log event)
- Severity
- Severity 3 (Informational)
LOG201
- Message
- Recovered from Lifecycle Controller Log corruption.
- Detailed Description
- Lifecycle Controller Log corruption was detected during iDRAC boot. The Lifecycle Controller Log was truncated at the point of corruption.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
LOG202
- Message
- Recovered from Lifecycle Controller Log comments file corruption.
- Detailed Description
- Unable to access part of Lifecycle Controller Log comments file during iDRAC boot. The file was truncated at the point of corruption.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
LOG203
- Message
- Lifecycle Log archived up to Log Sequence number arg1 .
- Arguments
- arg1 = seq num
- Detailed Description
- This message is generated while archiving Lifecycle Log. All the older messages are archived and can be retrieved using the export Lifecycle Log feature.
- Recommended Response Action
- No response action is required.
- Category
- Audit (LOG = Log event)
- Severity
- Severity 3 (Informational)
LOG204
- Message
- Lifecycle Log archive operation did not complete.
- Detailed Description
- The archive operation did not complete. 10% of the events from the cache will be dropped to make space for new events.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
LOG300
- Message
- The system recovered from Chassis Log file corruption.
- Detailed Description
- The system recovered from Chassis Log file corruption. Some log entries may not be recovered.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
LOG302
- Message
- The Chassis Log file header is corrupted.
- Detailed Description
- The Chassis Log file header is corrupted. The Chassis Log will be recreated and all current log entries will not be preserved.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
LOG303
- Message
- Unable to archive the Chassis Log file.
- Detailed Description
- Unable to rename current Chassis Log file during archive operation. Some log entries may be lost.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
LOG305
- Message
- The Chassis Log file was cleared.
- Detailed Description
- The Chassis Log file was cleared as a result of clear log operation.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
LOG320
- Message
- Log monitoring is disabled. Log type: arg1 .
- Arguments
- arg1 = log type
- Detailed Description
- The hardware log in the system is disabled. The log type information is provided.
- Recommended Response Action
- No response action is required.
- Category
- Audit (LOG = Log event)
- Severity
- Severity 2 (Warning)
- OMSA Event ID
- 5550
LOG321
- Message
- The log status is unknown. Log type: arg1 .
- Arguments
- arg1 = log type
- Detailed Description
- The hardware log may not be up-to-date. The log type information is provided.
- Recommended Response Action
- Make sure that iDRAC is functioning correctly.
- Category
- System Health (LOG = Log event)
- Severity
- Severity 3 (Informational)
- OMSA Event ID
- 5551
LOG322
- Message
- The log size is no longer near the maximum capacity. Log type: arg1 .
- Arguments
- arg1 = log type
- Detailed Description
- The hardware log in the system is no longer near its maximum capacity. The log type information is provided.
- Recommended Response Action
- No response action is required.
- Category
- System Health (LOG = Log event)
- Severity
- Severity 3 (Informational)
- OMSA Event ID
- 5552
- OMSA Trap ID
- 5552
LOG323
- Message
- The log size is near maximum capacity. Log type: arg1 .
- Arguments
- arg1 = log type
- Detailed Description
- The size of a hardware log in the system is near its maximum capacity. The log type information is provided.
- Recommended Response Action
- Clear the log to make sure new entries are recorded.
- Category
- System Health (LOG = Log event)
- Severity
- Severity 2 (Warning)
- OMSA Event ID
- 5553
- OMSA Trap ID
- 5553
LOG324
- Message
- The log size has reached its maximum capacity. Log type: arg1 .
- Arguments
- arg1 = log type
- Detailed Description
- The size of a hardware log in the system has reached its maximum capacity. The log type information is provided.
- Recommended Response Action
- Clear the log to make sure new entries are recorded.
- Category
- System Health (LOG = Log event)
- Severity
- Severity 1 (Critical)
- OMSA Event ID
- 5554
- OMSA Trap ID
- 5554
LOG325
- Message
- Unable to receive any log entries. Log type: arg1 .
- Arguments
- arg1 = log type
- Detailed Description
- Unable to receive any log entries, and therefore log status cannot be monitored. The log type information is provided.
- Recommended Response Action
- Make sure that iDRAC is functioning correctly.
- Category
- System Health (LOG = Log event)
- Severity
- Severity 1 (Critical)
- OMSA Event ID
- 5555
LOG328
- Message
- The Server Based Management Mode is enabled.
- Detailed Description
- The Server Based Management Mode is enabled. Chassis based PSUs, fans, and sensor information can be displayed from server based system management tools.
- Recommended Response Action
- No response action is required.
- Category
- Audit (LOG = Log event)
- Severity
- Severity 3 (Informational)
LOG329
- Message
- The Server Based Management Mode is disabled.
- Detailed Description
- The Server Based Management Mode is disabled. Chassis based PSUs, fans, and sensor information will not be displayed from server based system management tools.
- Recommended Response Action
- No response action is required.
- Category
- Audit (LOG = Log event)
- Severity
- Severity 3 (Informational)
LOG501
- Message
- Unable to run the command because of a general issue.
- Detailed Description
- The command cannot be run because a general issue occurred.
- Recommended Response Action
- Retry the operation. If the issue persists, reset the CMC, and then retry the operation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
LOG502
- Message
- Unable to run the command because the method parameter arg1 is missing.
- Arguments
- arg1 = parameter
- Detailed Description
- The command cannot be run because the method parameter identified in the message is missing.
- Recommended Response Action
- Enter all the parameters required in the command, and then retry the operation. For more information, see the Chassis Record Log Profile.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG503
- Message
- Unable to run the method because the parameter arg1 is not valid.
- Arguments
- arg1 = parameter
- Detailed Description
- The command cannot be run because the value of the parameter identified in the message is not valid.
- Recommended Response Action
- Enter all the parameters required in the command as per the enumeration, and then retry the operation. For more information, see the Chassis Record Log Profile.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG504
- Message
- Chassis Log Export was successful.
- Detailed Description
- The Chassis Log was successfully exported to the destination specified.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
LOG505
- Message
- Unable to access the network share.
- Detailed Description
- The network share access cannot be accessed.
- Recommended Response Action
- Make sure that correct network share access credentials are entered (such as IP address, username, password, and share type). For more information, see the Chassis Record Log Profile.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG506
- Message
- Unable to start the requested operation because the ExportChassisLog operation is already running.
- Detailed Description
- The requested operation cannot be started because the ExportChassisLog operation is already running.
- Recommended Response Action
- Wait for the current ExportChassisLog operation to complete and then retry the operation. If the issue persists, contact your service provider.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG507
- Message
- Unable to allocated required CMC resources.
- Detailed Description
- The operation did not complete successfully because of lack of memory or file space in the CMC.
- Recommended Response Action
- Reset the CMC and retry the operation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 1 (Critical)
- No alerts are applicable for this message
LOG508
- Message
- Unable to write to the network share.
- Detailed Description
- The network share may be read-only or it may not have sufficient space for the export operation.
- Recommended Response Action
- Verify the network share is not read-only and has sufficient space for exporting, then retry the operation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG509
- Message
- Unable to run the command because the parameter value of arg1 exceeds the maximum allowed number of arg2 characters.
- Arguments
- arg1 = parameter name, arg2 = max parameter length
- Detailed Description
- The command cannot be run because the value of the parameter identified in the message exceeds the maximum length identified in the message.
- Recommended Response Action
- Enter a value for the parameter identified in the message that is equal to or less than the maximum allowed characters.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
LOG510
- Message
- Unable to complete the operation because of an unknown issue in the CMC.
- Detailed Description
- The operation cannot be completed because of an unknown issue.
- Recommended Response Action
- Retry the operation. If the issue persists, reset CMC and then retry the operation.
- Category
- Configuration (LOG = Log event)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
평점(별 1~5개)을 매겨주십시오.
평점(별 1~5개)을 매겨주십시오.
평점(별 1~5개)을 매겨주십시오.
문서가 도움이 되었는지 여부를 선택하십시오.
의견에는 <>()\와 같은 특수 문자를 사용할 수 없습니다.