Alarm and System Message Overview

Transcription

1 CHAPTER 1 The Cisco ACNS Alarms and Error Messages Guide lists and describes the error messages for the Application and Content Networking System (ACNS). The system software sends these error messages to the console (and, optionally, to a logging server on another system) during operation. Not all error messages indicate problems with your system. Some messages are purely informational, while others may help diagnose problems with communications lines, internal hardware, or the system software. This chapter contains the following sections: System Message Structure, page 1-1 System Message Example, page 1-5 Searching for System Messages, page 1-5 Alarm Structure, page 1-6 Sample Alarm, page 1-6 System Message Structure System error messages are structured as follows: FACILITY-SEVERITY-MNEMONIC: Message-text FACILITY code The facility code consists of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. In the ACNS context, the facility code is CE and refers to Content Engine. ACNS error messages also indicate where the system condition occurred. These messages are structured as follows: FACILITY-SOURCE-SEVERITY-MNEMONIC: Message-text Source indicates the location of the condition. Examples of source are ACQ, which indicates that the condition occurred in the Acquisition component, or SYSMON, which indicates that the condition occurred in the System Monitor component. Table 1-1 lists the source codes in ACNS. 1-1

2 System Message Structure Chapter 1 Table 1-1 List of Source Codes in ACNS Code ACL ACQ AUTH AUTHCACHE AUTHMOD AUTOREG BANDWD BMRNG BUFMGR BYPS CACHE CDNFS CIFSSVR CLEAN CLI CMS COMMONEDM CR CSE DDBG DHCP DISK DIST DNS DS FFS FTP FTP_EXPORT FTP_PROXY HTTP ICAP ICP INETD IPTVPM LIBCMN Component Description Access control list Acquisition Authentication Authentication cache Authentication mode Auto Registration Bandwidth Boomerang module Buffer Manager Bypass Cache Content Delivery Network file system Common Internet File System Server Cleanup CLI commands Content Management Service Common EDM Content routing Cisco streaming engine Debug Dynamic Host Configuration Protocol Disk Distribution Domain name server Data server Firewall feature set File Transfer Protocol File Transfer Protocol Export File Transfer Protocol Proxy Hypertext Transfer Protocol Interactive Communicating Application Protocol daemon Internet Cache Protocol Internet daemon IP/TV Program Manager Common library 1-2

3 Chapter 1 System Message Structure Table 1-1 List of Source Codes in ACNS (continued) Code LOGGING LSR MINGETTY MODUTILS NAS NODEMGR NTP PAM PARSER PFS PM POSTGRE PRELD RBCP REALPXY REALSRV RPC RSH RSM RTSP RTSPG RULES SCHED SMARTD SNMP SSHD SSRV STATS STDBY STREAMCACHE SYS SYSMON SYSUTL SYSVINIT TELNET TFTP Component Description Logging Label switch routing Minimal getty Module utilities Network attached storage Node manager Network Time Protocol Port to application mapping Parser PAC file server Preferences module Postgres server Preload Router Blade Configuration Protocol RealProxy RealSubscriber Remote proxy caching Remote Shell Protocol RealServer Manager Real-Time Streaming Protocol Real-Time Streaming Protocol Gateway URL filtering rules Scheduler SMARTD Simple Network Management Protocol Secure Shell Streaming server Statistics Provider application Standby Stream cache Kernel System Monitor System utility System V initialization Telnet Trivial File Transfer Protocol 1-3

4 System Message Structure Chapter 1 Table 1-1 List of Source Codes in ACNS (continued) Code TRNSLG TVOUT UNILOG UPG URLFLT UTILLIN VCRON WCCP WEBSENSESERVER WI WMT Component Description Translog TV Out Unilog Upgrade URL filter Linux utilities Vixie cron Web Cache Communication Protocol Websense server WebServer Windows Media Technologies Severity Level The severity level is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 1-2 lists the message severity levels. Table 1-2 Message Severity Level Severity Level Description 0 - emergency System is unusable 1 - alert Immediate action is required 2 - critical Critical condition 3 - error Error condition 4 - warning Warning condition 5 - notification Normal but significant condition 6 - informational Informational message only 7 - debugging Message that appears during debugging only Mnemonic code The mnemonic code uniquely identifies the error message. Message-text Message-text is a text string that describes the condition. The text string sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because variable fields change from message to message, they are represented here by short strings enclosed in square brackets ([ ]). The variables give you more information about the system condition. A decimal number, for example, is represented as [dec]. Table 1-3 lists a sample of the variable fields that you will find in this publication. 1-4

5 Chapter 1 System Message Example Table 1-3 Representation of Variable Fields in Messages Representation [chars] or [char] [dec] [failure description] [x] or [y] [error] [module] [procedure] [additional information] [cli] [err] Type of Information Character string Decimal Explains the type and nature of system failure Characters Error code Name of the module Name of the procedure Additional information about the error message Command entered at the command line interface Error description System Message Example The following is an example of a system error message: CE-ACQ : Failed to read Channel=[chars], Channel table may have been dropped accidentally. Restarting acquirer to wait for its creation. CE is the facility code. ACQ is the source code. 2 is the severity level is the mnemonic code. Failed to read Channel=[chars], Channel table may have been dropped accidentally. Restarting acquirer to wait for its creation is the message text. Searching for System Messages If you search for the explanation and recommended action of a message that contains a SOURCE, remove the SOURCE from the text first, and then search for the message in the documentation. For example, instead of searching the documentation for the message CE-ACQ , remove the source identifier and search for the message CE When searching for a message in the Error Message Decoder (EMD) also, you must remove the source identifier. The EMD is located here: 1-5

6 Alarm Structure Chapter 1 Alarm Structure Cisco ACNS alarms are structured as follows: MESSAGE_TYPE-SEVERITY-SOURCE-MNEMONIC: Alarm-text MESSAGE_TYPE A three letter code indicating the message is an alarm. SEVERITY An alarm can have the severity levels critical, major, or minor. A critical alarm indicates that a critical problem exists somewhere in the network. Critical alarms cause failover. Critical alarms should be cleared immediately. A major alarm indicates that a serious problem exists that is disrupting service. Major alarms differ from critical alarms in that they do not cause failovers. Major alarms should also be cleared immediately. Minor alarms should be noted and cleared as soon as possible. SOURCE The component from where the alarm originated. MNEMONIC A unique code for identifying the alarm. ALARM TEXT A brief description of the alarm. Sample Alarm Given here is an example of an alarm: /alm/min/acquirer/zerobandwidth: specified content acquisition bandwidth is 0 alm is the message type. min is the severity level. acquirer is the source code. zerobandwidth is the mnemonic. specified content acquisition bandwidth is 0 is the alarm text. 1-6