APC 78-10169-02 User Manual

CHAPTER

Monitoring the System

This chapter explains how to monitor the Cisco ICS 7750. The chapter is organized as follows:

• Alarms, page 2-2

• Logging, page 2-3

• SNMP Basics, page 2-10

• Monitoring with ICS System Manager, page 2-16

• Monitoring with CiscoWorks2000, page 2-17

• Monitoring with Cisco IOS Software, page 2-18

• Monitoring a UPS, page 2-21

78-10169-02 Rev. B0

Cisco ICS 7750 Administration and Troubleshooting Guide

2-1

Alarms

Chapter 2 Monitoring the System

This section describesalarms, which indicateproblems on theCisco ICS 7750 or on systems with which it is communicating.

Alarms are associated with the following:

• Events—Physical problems, such as system overheating or loss of power,

detected by the SAP card and reported to the ICS System Manager software. Events are associated with the following system components:

–

Chassis/backplane

–

Fans

–

Power supply modules

• Traps—Problems,such as a trunk outage,thatare detected by MRP cards and

transmitted in the form of a Simple Network Management Protocol (SNMP) message.

Note For more information about SNMP messages, see “SNMP Basics” on

page 2-10. To find out how to identify and solve system problems, see Chapter 4, “System Troubleshooting Guidelines,” and Appendix A, “Error Message Summary.”

Alarm Notification

The system issues notifications of alarms in any of the following ways:

• ICS System Manager is notified of an event and takes the appropriate action;

for example, it changes the state of one or more LEDs on the system and generates an error message, which you then see.

• An SNMP agent generates a trap that is collected by ICS ICS System

Manager or another SNMP management application, which processes the trap and takes the appropriate action.

• You have an open communications session with the Cisco ICS 7750 and

retrieve log messages associated with any alarms.

Cisco ICS 7750 Administration and Troubleshooting Guide

2-2

78-10169-02 Rev. B0

Chapter 2 Monitoring the System

Alarm Levels

The system has the following two alarm levels:

Logging

• Major alarm (amber LED)—Any state that indicates a system malfunction

that can immediately result in a service outage or that indicates a system problem that can seriously degrade service. Examples include:

–

System overheating because of high ambient air temperature, an air intake or exhaust blockage, or fan failure

–

A power supply module outage

–

SPE memory parity or disk read/write errors

–

Loss of an Ethernet interface because of an equipment or Ethernet facility failure

–

Loss of signal or errors on a T1 or higher trunk because of a local or remote equipment failure

• Minor alarm (yellow LED)—Any state that indicates a system abnormality

that does not seriously degrade service, but that may affect the network or equipment, such as a port that is disabled or otherwise out of service.

Logging

This section provides the following information about logging:

• How to Access Log Messages

• How to Read Log Messages

• How to Change the Log Configuration

How to Access Log Messages

You can access log messages in any of the following ways:

• Handling Log Messages with ICS System Manager

• Saving Log Messages to a Syslog Server

Cisco ICS 7750 Administration and Troubleshooting Guide

78-10169-02 Rev. B0

2-3

Logging

Handling Log Messages with ICS System Manager

ICS System Manager provides several options for handling the log messages directed to it. By default, the system sends log messages to the SPE, where they are stored on disk.

ICS System Manager includes an Event Manager that enables you to view system events (messages) and define policies (a set of rules) that specify how you want the system to respond to a particular type of message. For example, for certain types of log messages, you might want to configure the system to automatically generate an e-mail message or send a page.

For additional information about using ICS System Manager for event handling, refer to the ICS System Manager online help.

Saving Log Messages to a Syslog Server

The system saves syslog messages to an internal buffer. You can configure the system to read messages from the buffer and send them to a specified syslog server.

Chapter 2 Monitoring the System

Note For instructions on how to view and change the log configuration, see “How

to Change the Log Configuration” on page 2-7.

How to Read Log Messages

When viewed on a log server,the mandatory portion of a log message begins with a percent sign (%) and can contain up to 80 characters. The message fields that precede the percent sign (received and sent dates and times) are optional.

Table 2-1 describes the elements of log messages as displayed in Event Manager.

Cisco ICS 7750 Administration and Troubleshooting Guide

2-4

78-10169-02 Rev. B0

Chapter 2 Monitoring the System

Table 2-1 Log Message Elements

Element Example Format Description

Received date and time

Sent date and time

FACILITY

1999 Nov 21 11:55:00

%LPR

yyyy mmm dd hh:mm:ss

The date and time when the message was received.

The date and time when the message was sent.

STRING Two or more uppercase letters

that indicate the facility to which the message refers (see

Table 2-2).

From

192.31.7.19

n.n.n.n The IP address of the device

sending the message.

Message

CISCO FACILITY (optional)

System temperature OK

CDP

string A description of the event.

STRING Two or more uppercase letters

that indicate the facility to which the message refers. Facilities include hardware devices, protocols, and system software modules.

CISCO SUBFACILITY (optional)

CIP

STRING Two or more uppercase letters

that indicate the subfacility for Channel Interface Processor (CIP) messages. CIP messages have a Cisco subfacility code of

CIP.

Cisco Severity (optional)

0–7 A single-digit code from 0 to 7

that indicates the severity of the message (see Table 2-3). The lower the number, the more serious the situation.

CISCO MNEMONIC (optional)

XMIT_ERR

STRING A code that uniquely identifies

the message.

Logging

78-10169-02 Rev. B0

Cisco ICS 7750 Administration and Troubleshooting Guide

2-5

Logging

Facilities

Chapter 2 Monitoring the System

Table 2-2 describes the facility types supported by log messages.

Table 2-2 Log Facility Type Keywords

Keyword Description

auth Authorization system cron Cron facility daemon System daemon kern Kernel local0-7 Reserved for user-defined messages (eight

types, from local0 through local7, are

available) lpr Line printer system mail Mail system news USENET news syslog System log uucp UNIX-to-UNIX copy system

Severity Levels

Cisco ICS 7750 Administration and Troubleshooting Guide

2-6

Table 2-3 describes log message severity levels.

Table 2-3 Log Message Severity Level Keywords

Keyword Level Description Syslog Definition

emergency 0 System unusable LOG_EMERG alert 1 Immediate action

LOG_ALERT

required critical 2 Critical condition LOG_CRIT error 3 Error condition LOG_ERR warning 4 Warning condition LOG_WARNING

78-10169-02 Rev. B0

Chapter 2 Monitoring the System

Table 2-3 Log Message Severity Level Keywords (continued)

Keyword Level Description Syslog Definition

notification 5 Normal butsignificant

informational 6 Information—no

debugging 7 Debugging message LOG_DEBUG

Note Not all messages indicate problems. Some messages are informational. Others

may help diagnose problems with communications lines, internal hardware, or system software. To findout how to use system messages to identify and solve problems, see Chapter 4, “System Troubleshooting Guidelines,” and

Appendix A, “Error Message Summary.”

Logging

LOG_NOTICE

condition

LOG_INFO

action required

How to Change the Log Configuration

The system sends log messages to ICS System Manager by default. You can redirect these messages to other destinations such as buffers and UNIX hosts running a syslog server.

This section provides the following information about log configurations:

• Default Log Configuration

• Configuring the Syslog Daemon on UNIX Syslog Servers

• Changing Syslog Server Logging

Cisco ICS 7750 Administration and Troubleshooting Guide

78-10169-02 Rev. B0

2-7

Logging

Default Log Configuration

System IOS components (ASI cards, MRP cards, and the SSP card) ship with the default logging configuration shown in Table 2-4.

Table 2-4 Default Logging Conﬁguration

Configuration Parameters Default Setting

System message logging to the console Disabled System message logging to Telnet sessions Disabled Log server Disabled Syslog server IP address None configured Server facility LOCAL7 Server severity Warnings (4) Logging buffer size 500 Logging history size 1 Timestamp option Disabled

Chapter 2 Monitoring the System

Tip To view the state of syslog error and event logging, including host addresses

and whether console logging is enabled, enter the IOS show logging command.

Configuring the Syslog Daemon on UNIX Syslog Servers

Before you can send log messages to a UNIX syslog server, you must configure the syslog daemon on the UNIX server. Toconfigure the syslog daemon, log in as root and include a line such as the following in the file syslog.conf:

facility.level/syslog path/myfile.log

where

• facility is the log facility keyword (see Table 2-2)

• level is the severity level (see Table 2-3)

Cisco ICS 7750 Administration and Troubleshooting Guide

2-8

78-10169-02 Rev. B0

Chapter 2 Monitoring the System

• syslog path is the path to syslog.conf

• myfile.log is the name of your log file

The syslog daemon (syslogd) sends messages at the level specifiedinsyslog.conf, provided that the file exists, and provided that syslogd has permission to write to it.

Changing Syslog Server Logging

To change syslog server logging behavior, use the global configuration commands shown in Table 2-5.

Table 2-5 Syslog Server Logging Behavior Commands

Task Command

Configure an IOS device to log messages to a syslog server,wherehost is the name or IP address of the target syslog server.

Remove a host from the list of syslog servers. no logging host Configure an IOS device to limit the log messages it

sends to the syslog server(s) based on the severity level, where level is one of the log message severity keywords listed in Table 2-3.

Disable logging to the syslog server(s). no logging trap

Logging

logging host

logging trap level

Note For more information about IOS commands related to logging, refer to the

78-10169-02 Rev. B0

Configuration Fundamentals Command Reference publication.

Cisco ICS 7750 Administration and Troubleshooting Guide

2-9

+ 19 hidden pages