Cisco UCS Manager generates system log, or syslog messages to record the
following incidents that take place in the
Cisco UCS Manager system:
There are three kinds
of syslog entries: Fault, Event, and Audit.
Each syslog message
Cisco UCS Manager process that generated the message and provides a brief
description of the operation or error that occurred. The syslog is useful both
in routine troubleshooting, incident handling, and management.
Cisco UCS Manager collects and logs syslog messages internally. You can send
them to external syslog servers running a syslog daemon. Logging to a central
syslog server helps in aggregation of logs and alerts. Some syslog messages to
monitor include, DIMM problems, equipment failures, thermal problems, voltage
problems, power problems, high availability (HA) cluster problems, and link
contain an event code and fault code. To monitor syslog messages, you can
define syslog message filters. These filters can parse the syslog messages
based on the criteria you choose. You can use the following criteria to define
By event or fault
codes: Define a filter with a parsing rule to include only the specific codes
that you intend to monitor. Messages that do not match these criteria are
By severity level:
Define a filter with a parsing rule to monitor syslog messages with specific
severity levels. You can set syslog severity levels individually for OS
functions, to facilitate logging and display of messages ranging from brief
summaries to detailed information for debugging.
Cisco devices can send
their log messages to a Unix-style syslog service. A syslog service simply
accepts messages, then stores them in files or prints them according to a
simple configuration file. This form of logging is the best available for Cisco
devices because it can provide protected long-term storage of logs.