Stimmen - , Durchschnittliche Bewertung:
(
)
)
Hersteller: APC
Dateigröße: 140.48 kb
Dateiname: monitor.pdf
Unterrichtssprache:
Das Dokument wird geladen, bitte warten
 |
Das Dokument wird geladen, bitte warten
Anleitung Zusammenfassung
B0 Cisco ICS 7750 Administration and Troubleshooting Guide 2-1 Chapter 2 Monitoring the System Alarms Alarms This section describes alarms, which indicate problems on the Cisco 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, that are 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. 2-2 Cisco ICS 7750 Administration and Troubleshooting Guide 78-10169-02 Rev. B0 Chapter 2 Monitoring the System Logging Alarm Levels The system has the following two alarm levels: • 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 Chapter 2 Monitoring the System 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. 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. 2-4 Cisco ICS 7750 Administration and Troubleshooting Guide 78-10169-02 Rev. B0 Chapter 2 Monitoring the System Logging Table 2-1 Log Message Elements Element Example Format Description Received date and time 1999 Nov 21 11:55:00 yyyy mmm dd hh:mm:ss The date and time when the message was received. Sent date and time 1999 Nov 21 11:55:00 yyyy mmm dd hh:mm:ss The date and time when the message was sent. FACILITY %LPR 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 System temperature OK string A description of the event. CISCO FACILITY (op...