Inhaltszusammenfassung zur Seite Nr. 1
CHAPTER 2
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
Cisco ICS 7750 Administration and Troubleshooting Guide
78-10169-02 Rev. B0
2-1
Inhaltszusammenfassung zur Seite Nr. 2
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
Inhaltszusammenfassung zur Seite Nr. 3
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 erro
Inhaltszusammenfassung zur Seite Nr. 4
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 cert
Inhaltszusammenfassung zur Seite Nr. 5
Chapter 2 Monitoring the System Logging Table 2-1 Log Message Elements Element Example Format Description 1999 Nov 21 Received date and time yyyy mmm dd The date and time when the 11:55:00 hh:mm:ss message was received. 1999 Nov 21 Sent date and time yyyy mmm dd The date and time when the 11:55:00 hh:mm:ss message was sent. %LPR FACILITY STRING Two or more uppercase letters that indicate the facility to which the message refers (see Table 2-2). 192.31.7.19 From n.n.n.n The IP address of the
Inhaltszusammenfassung zur Seite Nr. 6
Chapter 2 Monitoring the System Logging Facilities 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 Table 2-3 describes
Inhaltszusammenfassung zur Seite Nr. 7
Chapter 2 Monitoring the System Logging Table 2-3 Log Message Severity Level Keywords (continued) Keyword Level Description Syslog Definition notification 5 Normal but significant LOG_NOTICE condition informational 6 Information—no LOG_INFO action required 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 find out how to use s
Inhaltszusammenfassung zur Seite Nr. 8
Chapter 2 Monitoring the System 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 Configuration 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 buf
Inhaltszusammenfassung zur Seite Nr. 9
Chapter 2 Monitoring the System Logging • 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 specified in syslog.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 Configur
Inhaltszusammenfassung zur Seite Nr. 10
Chapter 2 Monitoring the System SNMP Basics SNMP Basics The Simple Network Management Protocol (SNMP) facilitates the exchange of management information among network devices. SNMP is part of the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol suite. SNMP enables you to manage network performance, find and solve network problems, and plan for network growth. SNMP Components An SNMP-managed network consists of three key components: managed devices, agents, and network manag
Inhaltszusammenfassung zur Seite Nr. 11
Chapter 2 Monitoring the System SNMP Basics • An SNMP management application, together with the computer it runs on, is called a network management system (NMS). An NMS executes applications that monitor and control managed devices. NMSs provide the bulk of the processing and memory resources required for network management. The Cisco ICS 7750 is compatible with the following NMSs: – ICS System Manager – CiscoWorks2000 – HP OpenView Figure 2-1 shows the relationships between the managed dev
Inhaltszusammenfassung zur Seite Nr. 12
Chapter 2 Monitoring the System SNMP Basics The following system components, though not SNMP-managed devices, receive SNMP support through ICS System Manager: • System alarm processor (SAP) card • Power supply modules • Fans • Chassis SNMP Management Information Base A Management Information Base (MIB) is a collection of information that is organized hierarchically. MIBs are accessed using a network management protocol such as SNMP. They comprise managed objects, which are identified by obj
Inhaltszusammenfassung zur Seite Nr. 13
Chapter 2 Monitoring the System SNMP Basics On the Cisco ICS 7750, the ICS System Manager software (the NMS) typically sends SNMP requests to a single IP address to access the SNMP MIBs of any system component. The SNMP agent can then respond to MIB-related queries being sent by the NMS. Similarly, if CiscoWorks2000 is the NMS, it uses the MIB variables to set device variables and poll devices on the network. You can then display the data that CiscoWorks2000 collects as a graph and analyze
Inhaltszusammenfassung zur Seite Nr. 14
Chapter 2 Monitoring the System SNMP Basics Supported MIBs The Cisco ICS 7750 supports the following MIBs: • CISCO-C2900-MIB—Supports the SSP card. • CISCO-CCM-MIB—Enables the system to get provisioning and statistical information about Cisco CallManager, devices associated with Cisco CallManager (such as Cisco IP phones and gateways), and the Cisco CallManager configuration. • CISCO-CDP-MIB—Enables Cisco CallManager to advertise itself to other Cisco devices on the network, allowing discov
Inhaltszusammenfassung zur Seite Nr. 15
Chapter 2 Monitoring the System SNMP Basics Cisco ICS 7750 Traps Cisco ICS 7750 ASI cards, MRP cards, and the SSP card can generate traps such as the following: • coldStart—Indicates power-up reset of a card. • warmStart—Indicates that software running on a card has been upgraded or that the card has been reset. • linkDown—Indicates that a port changed to a suspended or disabled state due to a secure address violation (mismatch or duplication), network connection error (such as a loss of Li
Inhaltszusammenfassung zur Seite Nr. 16
Chapter 2 Monitoring the System Monitoring with ICS System Manager • Number represents the target physical slot number (slots 1 through 8) of the SNMP request. Note All SNMP requests with a composite community string of @SLOT9 or higher are directed to the SSP, which determines the proper SNMP message destination. For example, assuming that a particular SNMP request needs to reach an MRP card in slot 3, the following composite community string could be used: ICS7750@SLOT3 where ICS7750 repr
Inhaltszusammenfassung zur Seite Nr. 17
Chapter 2 Monitoring the System Monitoring with CiscoWorks2000 Monitoring with CiscoWorks2000 CiscoWorks2000 uses SNMP to monitor and control system devices. You can integrate CiscoWorks2000 applications with other NMSs, such as HP OpenView. CiscoWorks2000 Applications CiscoWorks2000 applications extend industry-standard network management systems to facilitate checking the status of Cisco devices, maintaining device configurations and inventories, and troubleshooting device problems. Cisco
Inhaltszusammenfassung zur Seite Nr. 18
Chapter 2 Monitoring the System Monitoring with Cisco IOS Software SNMP and the CiscoWorks2000 Interface Using SNMP, CiscoWorks2000 retrieves CDP information by polling Cisco CallManager. After the discovery process is completed, a topology map reveals all the Cisco CallManager installations in the network. CiscoWorks2000 also polls other MIB tables in the CISCO-CCM-MIB to gather information required by other components, such as User Tracking (refer to the CiscoWorks2000 Campus Manager onli
Inhaltszusammenfassung zur Seite Nr. 19
Chapter 2 Monitoring the System Monitoring with Cisco IOS Software Evaluating Reachability and Response Times Polling remote parts of the network enables you to test reachability and measure response times. Response-time measurements consist of sending a ping (packet internet groper) packet and measuring the round-trip time (RTT) that it takes to send the packet and receive a response. The ping packet is sent and received as an ICMP echo packet. Note For information about ping command usage
Inhaltszusammenfassung zur Seite Nr. 20
Chapter 2 Monitoring the System Monitoring with Cisco IOS Software With in-band monitoring, network management data is sent over the same paths as user traffic. This means that any problems on the network will be more difficult to solve because collecting troubleshooting data will take longer. Using management tools is beneficial even when the internetwork is congested, failing, or under a security attack. With out-of-band monitoring, network management data travels on different paths than
