Lifecycle Controller log replication into operating system
Lifecycle Controller log replication replicates the Lifecycle Controller (LC) log files to the operating system log files. All events that have the operating system log option as the target in the Alerts page or in the equivalent RACADM or WS-Man interfaces are replicated in the operating system log files. This process is similar to the system event log (SEL) replication performed by OpenManage Server Administrator.
The default set of log files to be included in the operating system log files are the same as the logs configured for SNMP traps or alerts. However, the events logged in the Lifecycle Controller log file after the iSM is installed are replicated to the operating system log file. If OpenManage Server Administrator is installed, this monitoring feature is disabled to avoid duplicate SEL entries in the operating system log file.
In iSM, you can customize the location to replicate the Lifecycle Controller log files. By default, the Lifecycle Controller log files are replicated in the
System group of the
Windows logs folder in the Windows
Event Viewer. You can replicate the Lifecycle Controller logs to an existing group or create a folder in the
Application and Services Logs folder in the Windows
Event Viewer. When iSM is already installed and if the host operating system undergoes a reboot or iSM is restarted, and iDRAC has some Lifecycle Controller log files that are generated during this period of host downtime, then iSM log files these Lifecycle Controller log files as past events in the operating system log file when the service starts.
NOTE You can choose the location to replicate the Lifecycle Controller log files only during iSM custom installation or iSM modification.
NOTE The source name of the iSM Lifecycle Controller log files has been changed from
iDRAC Service Module to
Lifecycle Controller Log.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\