Users Guide

○ Do not change the value on the server—the existing configuration of the component is retained.
● Part configuration update—restores or upgrades the component configuration based on the selection made.
○ Disabled—the part configuration update is disabled and the saved configuration of the old component is not applied
on the replaced component.
○ Apply always—the part configuration update is enabled and the saved configuration of the old component is applied
on the replaced component.
○ Apply only if firmware matches—the saved configuration of the old component is applied on the replaced
component, only if their firmware versions match.
○ Do not change the value on the server—the existing configuration is retained.
Collect LC Logs for servers
LC logs provide records of past activities in a managed server. These log files are useful for server administrators since they
provide detailed information about recommended actions and some other technical information that is useful for troubleshooting
purpose. The various types of information available in LC logs are alerts-related, configuration changes on the system hardware
components, firmware changes due to an upgrade or downgrade, replaced parts, temperature warnings, detailed timestamps
of when the activity has started, severity of the activity, and so on. The exported LC log file is saved in a folder and the
folder is named after the server's service tag. LC logs are saved in the format: <YYYYMMDDHHMMSSSSS>.<file format>.
For example, 201607201030010597.xml.gz is the LC file name, which includes the date and time of the file when it was
created. There are two options to collect LC logs:
● Complete LC logs—exports active and archived LC log files. They are large in size, and hence compressed to .gz format
and exported to the specified location on a CIFS network share.
● Active LC logs—exports recent LC log files immediately or schedule a job to export the log files at regular intervals. View,
search, and export these log files to OMIMSSC Appliance. In addition, you can save a backup of log files in a network share.
To collect LC logs, perform the following steps:
1. In OMIMSSC, click Maintenance Center. Select a server or a group of servers, click LC Logs drop-down menu and then
click Collect LC Logs.
2. Select the servers’ whose logs you want to export, and then click LC Logs drop-down menu and then click Collect LC
Logs.
3. In LC Log Collection, select one of the following options, and click Finish:
● Export Complete LC Logs (.gz)—select to export complete LC logs to a CIFS network share by providing Windows
credentials.
● Export Active Logs (Run now)—select to export the active logs immediately to OMIMSSC Appliance.
○ (Optional) Select the Back up LC logs on the network share check box to save a backup of the LC logs on CIFS
network share by providing the Windows credentials.
● Schedule LC Log Collection—select select to export the active logs at regular intervals.
In Schedule LC Log Collection, select a date and time to export the log files.
Select a radio button depending on how frequently the files have to be exported. The available options for scheduling
frequency to determine how often you want to collect the LC logs are:
○ Never—this option is selected by default. Select to export the LC logs only once at the scheduled time.
○ Daily—select to export the LC logs daily at the scheduled time.
○ Once a week—select to export the LC logs on a weekly basis at the scheduled time.
○ Once every 4 weeks—select to export the LC logs in every four weeks at the scheduled time.
○ (Optional) Select the Back up LC logs on the network share check box to save a backup of the LC logs on CIFS
network share by providing the Windows credentials.
NOTE: Provide a share folder with sufficient storage space, since the exported files are large in size.
To track this job, the Go to the Job List option is selected by default.
View LC Logs
View all the active LC logs, search for detailed description, and download the logs in CSV format.
Add OMIMSSC Appliance in Local Intranet site .
Manage devices using OMIMSSC
87