Synopsis
mpsetlogsend_omgr |
mpsetlogsend_omgr {-n|-y} |
mpsetlogsend_omgr [{-n|-y}] -f <output file> -k {<number of storage days>|unlimit} |
mpsetlogsend_omgr -d |
Description
This command configures the settings for outputting the audit logs that are output by Systemwalker Operation Manager.
Options
No option specified
Outputs the current settings for audit log output. The following information is output:
LOG NAME : Systemwalker Operation Manager audit log LOG OUTPUT : ON LOG KEEP DAYS : 31 day(s) OUTPUT FILE : /var/opt/FJSVftlo/audit/log/mp_omgr_auditYYMMDD.log
The output content is as follows:
LOG NAME | This item is the name of the target audit log. |
LOG OUTPUT | "ON" is displayed if settings have been made so that audit logs are output, and "OFF" is displayed if such settings have not been made. |
LOG KEEP DAYS | This item displays the number of days for which audit logs that have been output in the past will be stored. Information will be displayed as "unlimited", "1 day(s)", "2 day(s)", ... "999 day(s)" |
OUTPUT FILE | This item displays the output file for audit logs. In the content displayed, the "YYMMDD" part is actually replaced by the date (where "YY" is the last two digits of the year, "MM" is the month and "DD" is the day of the month). |
LOG COLLECTION (*1) | "ON" is displayed if settings have been made so that audit logs are collected by the Systemwalker Centric Manager audit log management function, and "OFF" is displayed if such settings have not been made. |
COLLECTION FILE (*1) | This item outputs the files to be collected by the Systemwalker Centric Manager audit log management function. If log collection settings have never been made, "-" will be output. |
*1: The audit log management function can be used only if Systemwalker Operation Manager coexists with Operation Management Servers, Asset Management Servers, Section Management Servers, Job Servers and Operation Management Clients running Systemwalker Centric Manager V13.2.0 or later.
-f <output file>
Specify the output file for audit logs using the full path specification.
Up to 246 bytes' worth of characters can be specified for the output destination.
Log files will be output with the name specified by the "-f" option plus "YYMMDD.log", where YYMMDD indicates the date.
If "/var/audit/audit_log" has been specified for the "-f" option, the log file that is actually output on May 19, 2006 will be "/var/audit/audit_log060519.log".
-k <number of storage days>
Specify the maximum number of days for which audit logs will be held. After "-k", specify either a number between 1 and 999 (units are "days") or "unlimit". The command will terminate with a parameter error if a value of 1000 or more is specified. If "unlimit" is specified, the audit log files that have been output will not be deleted.
-d
Specify this option to stop outputting audit logs. If this option is specified, Systemwalker Operation Manager audit logs will no longer be output.
At the same time, collection using the Systemwalker Centric Manager audit log management function will also stop. To only stop collection using the audit log management function, use the "-n" option. (*1)
-y (*1)
Specify this option to collect audit log files onto an Operation Management Server using the Systemwalker Centric Manager audit log management function. If this option is specified, audit logs that have been output will be automatically collected on the Operation Management Server.
Collection settings for the files collected by the audit log management function are also updated by this option.
-n (*1)
Specify this option to pause the collection of audit log files on the Operation Management Server using the Systemwalker Centric Manager audit log management function. If this option is specified, audit logs that have been output will stop being collected on the Operation Management Server. To start collecting audit logs again, execute this command again, specifying the "-y" option.
These options can be used only if Systemwalker Operation Manager coexists with Operation Management Servers, Asset Management Servers, Section Management Servers, Job Servers and Operation Management Clients running Systemwalker Centric Manager V13.2.0 or later.
Return Values
Return value | Meaning |
|---|---|
0 | Normal termination |
Value other than 0 | Abnormal termination |
Command Location
Windows | Systemwalker Operation Manager installation directory\mpwalker.jm\bin |
Solaris | /usr/bin |
Privilege Required
This command can be executed by only system administrators (superusers or users belonging to the Administrators group).
Cautions
If log collection settings for the Systemwalker Centric Manager audit log management function have not been updated since the audit log output settings were changed (that is, if this command has been executed without the "-y" option specified), the content of the audit log output destination (OUTPUT FILE) and the content that is actually collected on the Operation Management Server may be different. To resume log collection correctly, execute this command again specifying the "-y" option.
The access rights to the output destination directory for audit logs must be set up again when the output destination directory is changed. Refer to "Define user restrictions" in the Systemwalker Operation Manager Installation Guide for details.
When both Systemwalker Operation Manager and Centric Manager are installed on Linux 64, as shown in the table below, the audit logs of the ACL Manager will be output in two separate files.
Centric Manager | |||
|---|---|---|---|
V13.4.0 or later | V13.4.0 or later | ||
Operation Manager | V13.2.0 - V13.3.1 | No issues. | The audit logs of the ACL Manager will be output in two separate files regardless of the installation order of Centric Manager and Operation Manager. |
V13.8.0 or later | No issues. | If Centric Manager has been installed after Operation Manager, the audit logs of the ACL Manager will be output in two separate files. | |
V13.8.0 or later | If Centric Manager has been installed after Operation Manager, the audit logs of the ACL Manager will be output in two separate files. | No issues. | |
The file name of the output destination is as follows:
The output destination displayed by mpsetlogsend_omgr (audit log setup command)
The file that "_acl" was added to before the date of the above file
(Example: /var/opt/FJSVftlo/audit/log/mp_omgr_audit_aclYYMMDD.log)
The files that "_acl" is added to are not displayed as the execution result of mpsetlogsend_omgr (audit log setup command), however the two files have the same audit log output settings (ON or OFF, storage period and if they are the collection target).
