![IBM Carrier Grade X3650 T User Manual Download Page 55](http://html1.mh-extra.com/html/ibm/carrier-grade-x3650-t/carrier-grade-x3650-t_user-manual_4040617055.webp)
IBM® Carrier Grade Server X3650 T
Revision 3.0
47
12.2.2
SysCon Event Logging and Notification
All SysCon events are logged to the SysCon log (/var/log/syscon) and notification made available to any
process that has registered an event query with the SysCon daemon through the SysCon API.
Depending on policy, each event type may also be logged to the SysCon event log, and/or syslog. In
addition, notification may be sent through SNMP and/or the Telco Alarms Manager (TAM).
A complete list of policies that enable logging and notification appears below. These policies can be
applied to each event type/device type combination. If no notification policy is specified in the XML policy
file, then notification is limited to the SysCon log and to processes that have registered queries with the
SysCon service (daemon).
The SysCon installation configures the Linux LogRotate process to occur once each week; as such,
SysCon Log data is limited to the previous six weeks.
SysCon Event Log Structure:
struct syscon_log_entry {
syscon_log_recid_t log_recid;
size_t log_size;
int log_format;
int log_event_type;
syscon_log_dev_type_t log_dev_type;
syscon_log_severity_t log_severity;
uid_t log_uid;
gid_t log_gid;
pid_t log_pid;
pid_t log_pgrp;
struct timespec *log_time;
unsigned int log_flags;
char log_dev[128];
char log_mntpnt[128];
char log_nodeid[68];
char log_mesg[SYSCONLOG_ENTRY_MAXLEN];
SysCon Event Log file format:
struct syscon_log_entr new
"%d;%d;%d;%d;%d;%d;%d;%d;%d;%d;%d;%d;%s;%s;%s;%s",
new.log_recid, new.log_size, new.log_format, new.log_event_type,
new.log_dev_type, new.log_severity, new.log_uid, new.log_gid,
new.log_pid, new.log_pgrp, new.log_time, new.log_flags,
new.log_dev, new.log_mntpnt, new.log_nodeid, new.log_mesg
Syslog file format:
struct syscon_log_entr new
"PX25;%d;%d;%d;%d;%d;%d;%d;%d;%d;%d;%d;%d;%s;%s;%s;%s",
new.log_recid, new.log_size, new.log_format, new.log_event_type,
new.log_dev_type, new.log_severity, new.log_uid, new.log_gid,
new.log_pid, new.log_pgrp, new.log_time, new.log_flags,
new.log_dev, new.log_mntpnt, new.log_nodeid, new.log_mesg
SEL entry format:
Slot/Connector 00 entries in the SEL are SysCon events. The data fields (enclosed in brackets at
the end of each entry) contain the event-type (00,02,03,04,06,07) in the first byte; the second and
third bytes are the major and minor numbers of the SysCon SCSI device. Examples for the six
event types are as follows:
Summary of Contents for Carrier Grade X3650 T
Page 8: ...IBM Carrier Grade Server X3650 T Revision 3 0 viii This page intentionally left blank...
Page 12: ...IBM Carrier Grade Server X3650 T Revision 3 0 4...
Page 15: ...IBM Carrier Grade Server X3650 T Revision 3 0 7...
Page 17: ...IBM Carrier Grade Server X3650 T Revision 3 0 9...
Page 25: ...IBM Carrier Grade Server X3650 T Revision 3 0 17...
Page 43: ...IBM Carrier Grade Server X3650 T Revision 3 0 35...