Cisco MCS-7825-H3-IPC1, Руководство по обслуживанию

Страница: 236 / 974

6-2
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability Alarms and CiscoLog Messages
Cisco Unified Serviceability alarms provide information on runtime status and the state of the system,
so you can troubleshoot problems that are associated with your system. The alarm or error message
information includes the application name, machine name, and recommended action and other critical
information to help you troubleshoot.
You configure the alarm interface to send alarm information to multiple locations, and each location can
have its own alarm event level (from debug to emergency). You can direct alarms to the Syslog Viewer
(local syslog), SNMP traps, Syslog file (remote syslog), SDI trace log file, SDL trace log file (for Cisco
Unified CM and CTIManager services only), or to all destinations.
You use the Trace and Log Central option in the Cisco Unified Real-Time Monitoring Tool (RTMT) to
collect alarms that get sent to an SDI or SDL trace log file. To view the alarm information sent to the
local syslog, use the SysLog Viewer in RTMT.
Note All the alarms are logged based on their severity and settings of alarm event level. For information on
viewing the alarm configuration settings, refer to the
Cisco Unified Serviceability Administration Guide .
CiscoLog Format
CiscoLog, a specification for unified logging in Cisco software applications, gets used in the Cisco
Unified RTMT. It defines the message format when messages are logged into file or by using the syslog
protocol. The output that is provided by Cisco software applications gets used for auditing,
fault-management, and troubleshooting of the services that are provided by these applications.
Be aware that CiscoLog message format is compatible with one of the message formats that is produced
by Cisco IOS Release 12.3 by using the syslog protocol when Cisco IOS Software is configured with the
following commands:
•
service sequence-numbers —A default sequence number that is produced by Cisco IOS. An
additional sequence number can also be enabled with this command. This command forces sequence
numbers to be shown in terminal output, but results in two sequence numbers in the syslog output.
CiscoLog standardizes on a format with just one sequence number. Thus, the compliant Cisco IOS
Software configuration occurs when the second number is disabled by using the
no service
sequence-numbers command.
•
logging origin-id hostname —The CiscoLog HOST field remains consistent with that produced by
the Cisco IOS Release 12.3 when configured with this command. This command does not get
documented in the Cisco IOS Software documentation but is available in Cisco IOS Release 12.3.
CiscoLog stays compatible with the results that Cisco IOS Software produces in this field.
•
service timestamps log datetime localtime msec show-timezone year —The CiscoLog
TIMESTAMP field remains consistent with the timestamp format produced by Cisco IOS Release
12.3 when configured with this command.
Note
CiscoLog uses the same field delimiters as Cisco IOS Software Release 12.3.
The following topics are described in this section:
•
Log File and Syslog Outputs, page 6-3
•
Standard Syslog Server Implementations, page 6-4