Updating the Configuration file
You can specify the IBM® Serviceable Event Provider to continuously report a problem according to the configuration file settings.
About this task
- Location of syslog file
- Size of activity log
- Maximum count of activity log
- Location of activity log
- Location of Product Engineering (PE) log
- Size of PE log
- Maximum count of Product Engineering (PE) log files
To view or edit the configuration file properties, follow these steps:
Procedure
Results
IBM Serviceable
Event Provider on
KVM monitors and sends traps even without any update / entry in the
configuration file. If no value or invalid value is associated to
any or all of the parameters that are mentioned in configuration file,
the respective properties are set to the following default values:
- Location of syslog file:/var/log/messages
- Max size of activity log: 2MB
- Max count of activity log: 2
- Location of activity log: /var/seprovider/logs
- Location of PE log: /var/seprovider/logs
- Max size of PE log: 2MB
- Max count of PE log files: 2
Example
##########################################################################
## Inorder to reflect the changes in config file, seprovider need to be resarted ##
##########################################################################
#sys log
[SYS_LOG]
#sys log file path
SYS_LOG=/var/log/messages
#activity log
[ACTIVITY_LOG]
#activity log file path
ACTIVITY_LOG=/var/seprovider/logs/activity.log
#log file max size(byte)
MAXSIZE=2048000
#activity log file count
MAXCOUNT=3
#PE log
[TRACE_LOG]
#log file path
TRACE_LOG=/var/seprovider/logs/trace.log
#PE log file max size(byte)
MAXSIZE=2048000
#PE log file count
MAXCOUNT=3
#SNMP trap command path
[NET_SNMP_BIN]
#trap command of SNMP
CMD_STRAP=snmptrap