HP XP RAID Manager Software - Manual (Page 46)

•
Examples for execution
/HORCM/log* directory
[root@raidmanager log9]# ls l
total 16
drwxr-xr-x 3 root root 4096 Oct 27 17:33 curlog
-rw-r--r-- 1 root root 3936 Oct 27 17:36 horcc_raidmanager.log
-rw-r--r-- 1 root root 2097452 Oct 27 17:29 horcc_raidmanager.oldlog
-rw-r--r-- 1 root root 46 Oct 27 17:19 horcc_raidmanager.conf
drwxr-xr-x 3 root root 4096 Oct 27 17:19 tmplog
/HORCM/log*/horcc_HOST.log file
COMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005
CMDLINE : pairvolchk ss g URA
12:21:54-2d27f-10090- [pairvolchk][exit(32)]
COMMAND NORMAL : EUserId for HORC : root (0) Thu Oct 27 17:36:32 2005
CMDLINE : raidqry l
17:36:32-3d83c-17539- [raidqry][exit(0)]
COMMAND ERROR : EUserId for HORC : root (0) Thu Oct 27 17:31:28 2005
CMDLINE : pairdisplay g UR
17:31:28-9a206-17514- ERROR:cm_sndrcv[rc < 0 from HORCM]
17:31:28-9b0a3-17514- [pairdisplay][exit(239)]
[EX_ENOGRP] No such group
[Cause ]:The group name which was designated or the device name
doesn't exist in the configuration file, or the network address
for remote communication doesn't exist.
[Action]:Please confirm if the group name exists in the
configuration file of the local and remote host
/HORCM/log*/horcc_HOST.conf file
# For Example
HORCC_LOGSZ=2048
#The masking variable
#This variable is used to disable the logging by the command and exit
code.
#For masking below log pairvolchk returned '32'(status is SVOL_COPY)
#COMMAND NORMAL : EUserId for HORC : root (0) Tue Nov 1 12:21:53 2005
#CMDLINE : pairvolchk ss g URA
#12:21:54-2d27f-10090- [pairvolchk][exit(32)]
pairvolchk=32
pairvolchk=22
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.
46 RAID Manager software environment