Logging Raidcom Command - Hitachi VSP F1500 User And Reference Manual

Logging raidcom command

The history of performing raidcom command can be stored in syslog server
by outputting it to the syslog file. Since the information of what command
was performed by who and when are recorded on the syslog file, this is
available to use for audit log.
Output the syslog file by using syslog service on the host OS. For details,
refer to the host OS manual.
Caution:
• The packet loss occurs on the syslog because the syslog uses UDP
communication. The log is also lost when the server to be received the
syslog is down because the server does not have a function to store the
data until it recovered. If you want to record the same log at the client
side by considering the lost of syslog at the syslog server, refer to the
output setting of the syslog file.
• This syslog files are not deleted automatically. Delete unnecessary files
accordingly, or make run the log rotation by installing such as the
logrotate service separately.
The conditions to support the output of syslog file
The conditions to support this function are explained in the following:
Supported OS
This function is supported only when the OS of the host is one of the
following (Windows is out of support):
• Solaris 2.5
• Solaris 10/x86
• HP-UX 10.20/11.0/11.2x
• AIX 4.3
• Red Hat Linux 6.0, 7.0, 8.0 AS/ES 2.1, 3.0, 4.0, 5.0
• AS/ES 2.1, 3.0 Update2, 4.0, 5.0 on EM64T / IA641
Target command
The following shows the raidcom command that is target to be output on the
syslog file.
• Setting commands
• raidcom get command status
• Authentication commands (performing the authentication command at the
prompt also becomes the target.)
However, if the command is not issued to the DKC by detecting the raidcom
command execution error beforehand, the command becomes out of target
even if it falls under the above items.
2-46
CCI software environment
Command Control Interface User and Reference Guide