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

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

6-10
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
HEADER Field
The HEADER field has the following format:
<APPNAME>-<SEVERITY>-<MSGNAME>
A single dash character (ASCII decimal value 45) serves a separator for the three fields.
APPNAME Field
The APPNAME field in the HEADER defines the name of the application producing the message. Cisco
IOS uses FACILITY in place of APPNAME that names the logical component producing the message.
Cisco IOS 12.3 defines approximately 287 facilities for 3950 messages. Example of some easily
TIMEZONE Must consist of at least one, but no more than 7 characters in the
following ASCII decimal value range: 32-126. The value must not
include a combination of colon-space-percent of characters – “: %“
(ASCII decimal values 58, 32, 37) – as this character combination is
reserved as a field delimiter that follows the time stamp.
There is no standard set of acronyms for time zones
1
. A list of common
time zone acronyms and corresponding time offsets from UTC is
provided in the UTC specification.
Uppercase letters are recommended for time zone acronym values.
CiscoLog recommends the use of time offset instead of time zone
identifier in this field. The offset, if provided, must follow the following
format “-hhmm” or “+hhmm” to indicate hour and minute offset from
UTC.
In this format time zone field must always contain 5 characters, with the
last 4 characters being constrained to numbers only. Unlike a textual
time zone identifier, this format provides a specific time offset from
universal standard time.
Cisco IOS Release 12.3 supports any 7-character string as a time zone
identifier, so it can be configured in a way which is compatible with this
recommendation. Multiple messages may and sometimes must be
produced with exactly the same time stamp. This can happen naturally
on a non-preemptive operating system or may need to be deliberately
induced as in the case of multi-part messages. Sequence numbers then
become helpful for establishing message order. Time stamp should
always be accurate to the millisecond unless it can significantly hinder
performance of the application.
In either case, applications must always provide the administrator with
an option to output messages with exact time stamp in milliseconds. If
an application uses time stamp with accuracy to the second (instead of a
millisecond), it must put the last known milliseconds value or 000 in
place of the milliseconds. Whatever convention is chosen by the
application, it should be followed consistently.
1. Neither Cisco IOS nor CiscoLog define a standard set of time zone acronyms because there is no single established standard.
Table 6-1 TIMESTAMP Field Specifications (continued)
Field Specification