|
|
This chapter explains how to maintain and upgrade the Cisco ICS 7750 and is organized as follows:
 |
Note For information on how to replace system hardware, see the Cisco ICS 7750 Hardware Installation Guide. |
You can run diagnostics either remotely over a Telnet or modem connection, or locally from a console connected to the console port on the SAP.
POST diagnostics are available for the following cards:
 |
Caution There is only one SAP and one SSP card in a single chassis. If you take the SAP off-line, the system's ability to detect alarms associated with the operating environment, fans, and power supply modules is degraded until the SAP is on-line. If you take the SSP off-line, the system loses LAN connectivity, and calls being made from or to Cisco IP Phones that are routed through that SSP are disconnected until the SSP is on-line. |
|
Note Depending on your system configuration, taking SPEs or MRPs off-line can adversely affect users connected to the system. For example, if Cisco CallManager is running on only one SPE, taking that SPE off-line disconnects calls to or from the PSTN and prevents the system from processing further PSTN traffic until the SPE is on-line. Similarly, taking an MRP off-line that is in the process of routing voice or WAN traffic prevents that traffic from reaching its destination. |
During POST, some or all of the following events can occur:
|
Note If a card fails diagnostics, see "Solving Hardware Problems." |
Many of the cards in the Cisco ICS 7750 support commands that can help you better understand what is happening in your internetwork. This section describes the basic use of these commands:
To check host reachability and network connectivity, use the ping EXEC or privileged EXEC command. This command enables you to confirm basic network connectivity on many kinds of networks.
For IP connections, the ping command sends ICMP echo messages. If a station receives an ICMP echo message, it sends an ICMP echo reply message back to the source.
The extended command mode of the ping command permits you to specify the supported IP header options, which allows the target device to perform a more extensive range of test options.
It is a good idea to use the ping command when the network is functioning properly to see how the command works under normal conditions and so that you have something to compare it to when troubleshooting.
|
Note For more information about ping command usage, see "System Troubleshooting Guidelines," and "Solving Serial Connection Problems." |
The trace EXEC command discovers the routes that packets follow to their destinations. The trace privileged EXEC command (also referred to as an extended trace) enables you to specify the supported IP header options, allowing the target device to perform a more extensive range of testing.
The trace command uses the error message generated by devices (routers or cards) when a datagram exceeds its time-to-live (TTL) value. Probe datagrams are sent initially with a TTL value of one, which causes the first device to discard the probe datagrams and send back "time exceeded" error messages.
The trace command then sends several probes and displays the round-trip time for each. After every third probe, the TTL is increased by one.
Each outgoing packet can result in one of two error messages. A "time exceeded" error message indicates that an intermediate device has seen and discarded the probe. A "port unreachable" error message indicates that the destination node has received the probe and discarded it because it could not deliver the packet to an application. If the timer goes off before a response comes in, an asterisk (*) is displayed.
The trace operation terminates when the destination responds, when the maximum TTL is exceeded, or when you interrupt the trace with the escape sequence.
As with ping, it is a good idea to use the trace command when the network is functioning properly to see how the command works under normal conditions and so that you have something to compare it to when troubleshooting.
For detailed information on using the trace EXEC and privileged EXEC commands, refer to the "Troubleshooting Commands" chapter in the Cisco IOS Configuration Fundamentals Command Reference publication.
The following system hardware components might require software image upgrades:
You can use the System Manager's Software Manager to upgrade IOS software and Cisco CallManager. The Software Manager automates software image upgrades, including image verification, backing up the running software image (if applicable), updating the device configuration to load the downloaded image, and reloading the device. For additional information, refer to the Cisco ICS 7700 System Manager User Guide.
Failover enables a standby (backup) component to automatically take over if the primary component fails.
A failover configuration provides the following:
If your system has redundant components, one component (such as an SPE) is typically designated as active, and a second component is designated as standby. If your system has two SPEs, the active SPE controls failover processing as long as it remains active. If the active SPE fails, the system software ensures that the standby SPE takes over as the active SPE. When the failed SPE comes back online, it becomes the standby SPE.
|
Note Only one SPE is active at a time. |
In the following example, a Cisco ICS 7750 has three SPEs, which are running the following software:
SPE 1 goes offline. Since the IP phones are no longer receiving keepalive messages from Cisco CallManager on SPE 1, they make contact with the Cisco CallManager instance that is running on SPE 2, which has become the active SPE, enabling normal call processing to continue.
If your Cisco ICS 7750 has redundant SPEs, you can configure the system so that data in the database of the active SPE can be automatically replicated on the standby SPE. Table 3-1 describes the types of data that can be replicated.
| Data Type | Description | Update Frequency | Typical File Size |
|---|---|---|---|
System hardware configuration | A file that records information about cards and other system components | infrequent | small |
User configuration selections | Configuration files that store per-application configuration information | infrequent | small |
MRP, SSP, and Catalyst 3524-PWR XL configurations | Configuration files that store configuration data for individual cards and switches | infrequent | small |
MRP, SAP, SSP, and Catalyst 3524-PWR XL software images | Current versions of Cisco IOS in use on system cards and switches | infrequent | very large (4 MB)1 |
System error log2 | A log file that stores a configurable amount of error and other log data | frequent | large to very large |
System monitoring log | A log file that captures a configurable amount of data for tracking system status | frequent | large to very large |
SNMP configuration | A configuration file that stores information about the community string and MIB II | infrequent | small |
Posted: Mon Oct 2 13:41:20 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.