cc/td/doc/product/access/solution/asap
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Using Cisco IOS for Operations and Maintenance
 Introduction
 Monitoring Network Performance Using IOS Commands
 Managing Gateways
 Managing Gatekeepers
 Managing Modems
 Using and Managing MIBs
 Cisco IOS References

Using Cisco IOS for Operations and Maintenance

Introduction

This chapter presents operations and maintenance tasks related to the Cisco ASAP Solution and the PSTN gateway solutions that are provided by Cisco IOS commands entered at the command-line interface (CLI).

This chapter presents the following major topics:

Tip See also Task Summary.

Target Platforms

The Cisco IOS CLI manages the following components of the Cisco ASAP Solution and the PSTN gateway solutions: Cisco AS5000 series.

References

See Cisco IOS References.

Task Summary

The tasks in this chapter are listed below, grouped by major category.

Monitoring Network Performance

Managing Gateways

Managing Gatekeepers

Managing Modems

Using MIB Objects

Monitoring Network Performance Using IOS Commands

The performance of a network is directly linked to the operational state of devices within the network. The hardware and software components of a network device also affect its performance. Failed hardware components can cause a complete outage in the network. It is critical to monitor the operating environments of network devices, such as voltage, temperature, and airflow, and ensure that they are operating within specifications. Software components such as buffersand memory can have a significant impact on the protocols running on the device.

A useful performance indicator on the Cisco devices is their CPU utilization. By measuring CPU utilization over time, a trend can be established to determine traffic patterns. Devices running constantly at high utilization levels can affect the overall performance of forwarding and processing packets. CLI commands on the Cisco devices can display the CPU utilization and information on running processes. Information returned on the CPU load can be accessed by means of objects defined in MIB files. For details on using such files, see Using MIB Objects.

Managing Gateways

For a good discussion of a variety of ways to verify basic setups, as well to determine memory and CPU utilization, refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

Consider, in particular, the following topics.

Checking Memory and CPU Utilization

The basic command to see CPU utilization is show processes. The following example displays results of that command:

Router# show processes
CPU utilization for five seconds: 1%/0%; one minute: 1%; five minutes: 1%
PID QTy PC Runtime (ms) Invoked uSecs Stacks TTY Process
1 Mwe 6039CCC8 2203448 9944378 221 7392/9000 0 IP-EIGRP Router
2 Lst 60133594 329612 34288 9613 5760/6000 0 Check heaps
3 Cwe 6011D820 0 1 0 5648/6000 0 Pool Manager
4 Mst 6015FAA8 0 2 0 5608/6000 0 Timers

You can also use a MIB to monitor the output of this command. Table 8-3 provides the MIB objects in the OLD-CISCO-CPU-MIB for monitoring the output of a show processes command.

The amount of main memory left on the processor of a device has a significant impact on performance. Buffers are allocated from memory into different memory pools that are used by a protocol. The following CLI commands are commonly used to monitor the memory and buffer statistics on a device: show memory, show buffers, and show interface.

The following example displays the memory allocation resulting from the the show memory command.

Router# show memory
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 60DB19C0 119858752 1948928 117909824 117765180 117903232
Fast 60D919C0 131072 69560 61512 61512 61468

There is a MIB that allows you to capture the output of this command. Table 8-4 provides the MIB objects in the CISCO-MEMORY-POOL-MIB for monitoring the output of a show memory command.

Note   Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.ht m

Note Chapter 2, "Verifying Basic Setup," and the following sections therein:
Investigating Memory Usage Illustrates the command show memory summary. Inspecting CPU Utilization illustrates the command show process cpu history.

Configuring Call Admission Control Thresholds Using Cisco IOS Commands

Table 8-1 lists the high-level tasks that you need to complete for configuring Call Admission Control (CAC) thresholds.

For step-by-step instructions, refer to the documentation for the following feature modules, at their respective URLs:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xa/122xa_2/ft_pfavb.htm

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/sw_conf/ios_122/dt61294.htm

Table 8-1  

Tasks Description

Configuring Call Spike

Configures the limit for the number of incoming calls in a short period of time.

Configuring Call Threshold

Enables a resource and defines associated parameters. Action is enabled when the resource cost goes beyond the high value and is not disabled until the resource cost drops below the low value.

Configuring Call Threshold Poll-Interval

Enables a polling interval threshold for CPU or memory.

Configuring Call Treatment

Configures how calls should be processed when local resources are unavailable. This indicates whether the call should be disconnected (with cause code), hairpinned, or should play a message or busy tone to the user.

Configuring Call Denial

Enters the Call Denial feature and sets a threshold at which denial of new calls occurs. This CPU load threshold can be set anywhere from 20 to 85%.

Tasks for Configuring Call Admission Control Thresholds

Verifying Call Admission Control Configurations

To verify the Call Admission Control configuration tasks, enter the following commands in privileged EXEC mode.

Command Description

show call spike status

Displays the configured call spike threshold and statistics for incoming calls.

show call threshold

Displays enabled triggers, current values for configured triggers, and number of Application Programming Interface (API) calls that were made to global and interface resources.

show call treatment

Displays the call treatment configuration and the statistics for handling the calls based upon resource availability.

show process

Displays the CPU threshold value configured for call denial.

show running-config

Displays all of the configurations

Verifying Controllers

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 3, "Basic Configuration Using the Command-Line Interface," and the following sections therein:

Refer to the subsection Verify in the above section, which illustrates the commands show interface async 4/0 and show async status.

Refer to the subsection Verify in the above section, which illustrates the command show controller.

Refer to the subsection Verify in the above section, which illustrates the command show controller.

Verifying ISDN PRI

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 3, "Basic Configuration Using the Command-Line Interface," and the following sections therein:

Refer to the subsection Verify in the above section, which illustrates the following commands: show controller t3, show isdn status, show isdn service, and show running-config.

Verifying ISDN D-Channels

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 3, "Basic Configuration Using the Command-Line Interface," and the following sections therein:

Refer to the subsection Verify in the above section, which illustrates the command show interface serial.

Verifying Universal Port Card and Lines

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 3, "Basic Configuration Using the Command-Line Interface," and the following sections therein:

Refer to the subsection Verify in the above section, which illustrates the commands show spe and show line.

Also refer to Chapter 5, "Managing and Troubleshooting the Universal Port Card," in the same document.

Verifying Clocking

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 3, "Basic Configuration Using the Command-Line Interface," and the following sections therein:

This section illustrates the use of the at command atdt and the Cisco IOS command show caller. You can also use the command show user.

Testing Asynchronous Shell Connections

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 3, "Basic Configuration Using the Command-Line Interface," and the following sections therein:

Refer to the subsection Verify in the above section, which illustrates the command show tdm clocks.

Configuring and Verifying Alarms

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 4, "Continuing Configuration Using the Command-Line Interface," and the following section therein:

Caution   By default, facility alarms are off. You must use the command facility-alarm and its options to enable alarms related to interfaces, controllers, modem boards, redundant power supplies, temperature, and fans.

Refer to the subsection Verify in the above section, which illustrates the command show facility-alarm.

Managing and Viewing SPE Performance Statistics

Event logs are automatically enabled and are based on one event queue per SPE (system processing engine). The log contains raw binary data that can be viewed by means of a variety of show spe commands.

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 5, "Managing and Troubleshooting the Universal Port Card," and the following sections therein:

The following command classes, with options, are described: show spe voice, show spe digital, show spe modem, show port, and miscellaneous show spe (log, version, fax).

Managing Ports

In port configuration mode, you can clear ports, remove them from service, or disable them from dial-up service.

Refer to Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/sw_conf/53swcg/index.htm

In the above-referenced guide, refer to Chapter 5, "Managing and Troubleshooting the Universal Port Card," and the following sections therein:

(presents the commands that are available in port configuration mode: busyout and shutdown)

Tip For the details of port management, including a command reference (applicable to both Cisco AS5350 and Cisco AS5400 platforms), refer to Managing Port Services on the Cisco AS5400 Universal Access Server at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/nextport/index.htm

Managing and Troubleshooting SPEs

In SPE configuration mode, you can transfer firmware from flash memory and specify an upgrade method, minimizing the impact on traffic.

In the above-referenced guide, refer to Chapter 5, "Managing and Troubleshooting the Universal Port Dial Feature Card," and the following sections therein:

Presents the SPE management options that are available in SPE configuration mode: firmware location, firmware upgrade, busyout, and shutdown. (See Upgrading SPE Firmware, below.)

Discusses the types of diagnostic tests you can perform on an SPE modem: startup test, auto-test, and back-to-back test.

Presents the spe recovery command and options, for use when an SPE port fails to connect after a certain number of consecutive attempts.

Presents the spe download maintenance command and options, for use in configuring a scheduled recovery of SPEs.

Presents the command clear spe, for use in manually recovering a port that is in a suspended state.

Discusses various ways to upgrade SPE firmware.

Using Cisco Call Tracker to Manage Gateways

Cisco Call Tracker captures detailed statistics on the status and progress of active calls and retains historical data for disconnected call sessions. It collects session information such as call states and resources, traffic statistics, total bytes transmitted and received, user IP address, and disconnect reason. This data is maintained within the Call Tracker database tables, which are accessible through the Simple Network Management Protocol (SNMP), the command line interface, or syslog.

For step-by-step procedures for configuring Call Tracker and verifying configurations on the Cisco AS5300 and Cisco AS5800, refer to Call Tracker plus ISDN and AAA Enhancements for the Cisco AS5300 and Cisco AS5800 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/dt_cltrk.htm

Configuring Call Tracker

To configure Call Tracker, enter calltracker enable command in global configuration mode.

Verifying Call Tracker

To verify the operation of CallTracker, enter the show call calltracker summary command in EXEC mode.

Managing Gatekeepers

Cisco 3640, Cisco 3660, and Cisco 7200 series platforms that are used as gatekeepers (and directory gatekeepers) employ H.323 RAS signaling to perform their function in the network hierarchy. A good discussion of this gatekeeper functionality and how to manage it can be found in Cisco High-Performance Gatekeeper at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121x/121xm/121xm_5/ft_0394.htm

The following topics in that document are of interest with respect to managing and verifying gatekeepers in the solution.

Configuring Load Balancing and Alternate Gatekeepers

In case a gatekeeper fails, you can assign an alternate gatekeeper to continue operation. You can create a local cluster associated with a local zone and define the alternate GK within the cluster. You will also need to configure load balancing, to determine the maximum number of calls, the percentage of CPU utilization, and the maximum percent of memory used per GK.

Configuring Remote Clusters

You can define a group of associated GKs in a remote cluster. Simplifying management responsibilities, you can then address the cluster as you would an individual remote GK.

Configuring Server Triggers

You can configure GKs to connect to a specific back-end server at startup, or listen to any server that wants to connect to it. This is done by configuring server triggers.

Verifying Gatekeeper Configuration

This section provides a useful look at the results of a variety of show gatekeeper commands.

Maintaining and Monitoring Gatekeeper Endpoints

This section lists a variety of show gatekeeper commands that are useful in monitoring and managing gatekeeper endpoints, clusters, and performance.

Managing Modems

Modems can occasionally stop working, but reloading the firmware generally resets the modem and brings it back into service. A modem recovery feature allows the UG to identify modems that have gone out of service and automatically reloads their DSP firmware.

Modem failure and recovery are discussed in detail in the document Configuring Modem Recovery at the following URL:

http://www.cisco.com/warp/public/76/modem-recovery.html

Read the section Modem Failure Overview for some diagnostic tips. This section addresses the earlier MICA modems, but is applicable to NextPort modems, which use the universal port DSP.

Note   The commands of interest to universal port cards are the spe recovery series. These replace the previously used modem recovery series. (SPE stands for Software Port Entity.) To see the series of spe recovery commands available from the command line, enter spe recovery ?. Then look for analogous commands, and their explanations, in the section Configuring Modem Recovery.
Tip Refer also to Comparing NextPort SPE Commands to MICA Modem Commands, at the following URL:
http://www.cisco.com/warp/public/76/nextport_compare.html

For the details of port management, including a command reference (applicable to both Cisco AS5350 and Cisco AS5400 platforms), refer to Managing Port Services on the Cisco AS5400 Universal Access Server at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t3/nextport/index.htm

Using and Managing MIBs

MIBs, or Management Information Bases, are databases of network performance information (the characteristics and parameters of network devices) for use by a variety of management applications. SNMP is a commonly used protocol for defining the information types in a MIB.

Table 8-2 lists some useful Cisco MIBs that support the Cisco ASAP Solution.

Table 8-2   Useful Cisco MIBs that Support the Cisco ASAP Solution

Dial (Modem) MIBs Voice MIBs

DIAL-CONTROL-MIB

CISCO-VOICE-DIAL-CONTROL-MIB

CISCO-DIAL-CONTROL-MIB

CISCO-CAS-IF-MIB

CISCO-POP-MGMT-MIB

CISCO-VOICE-IF-MIB

CISCO-MODEM-MGMT-MIB

CISCO-VOICE-NUMBER-EXPANSION-MIB

 

CISCO-CALL-APPLICATION-MIB

 

CISCO-SIP-UA-MIB

Obtaining MIBs

To obtain Cisco MIBs, as well as application notes related to their use, refer to Cisco MIBs at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To obtain MGC MIBs, as well as application notes related to their use, refer to MGC MIBs at the following URL:

http://cco/univercd/cc/td/doc/product/access/sc/rel9/mgc_mib/index.htm

Using MIB Locator

A convenient tool, MIB Locator, is also available that lets users browse an automated database of MIBS. A component of Cisco Feature Navigator (for which you will need a Cisco account password), MIB Locator provides a wider range of information to help the user maintain and troubleshoot networks. To use MIB Locator, follow the instructions below.

Step 1   Go to the following URL:

http://www.cisco.com/go/fn

Step 2   Enter a Cisco password as requested. The Feature Navigator window appears.

Step 3   In the left-hand frame, click MIB Locator. The MIB Locator window appears.

You can search for MIBs by using the following criteria:

Step 4   Use the criteria you want, then click the Submit button to issue your request.

You will be asked to narrow your search until you find the specific MIB you want. You can both view and download specific MIBs.

Using MIB Objects

The values collected from CLI commands are accessible through SNMP. MIB objects are also useful for monitoring CPU utilization. (See Checking Memory and CPU Utilization. Cisco provides the following MIB files for obtaining the equivalent output from CLI commands: CISCO-MEMORY-POOL-MIB, OLD-CISCO-INTERFACES-MIB, and OLD-CISCO-MEMORY-MIB.

Table 8-3 provides the MIB objects in the OLD-CISCO-CPU-MIB for monitoring the output of a show processes command.

Table 8-3  

Objects Description

busyPer

CPU busy percentage in the last 5 seconds.

AvgBusy1

One-minute moving average of the CPU busy percentage.

AvgBusy5

Five-minute moving average of the CPU busy percentage.

MIB Objects in OLD-CISCO-CPU-MIB for Monitoring CPU Utilization

Table 8-4 provides the MIB objects in the CISCO-MEMORY-POOL-MIB for monitoring the output of a show memory command.

Table 8-4  

Objects Description

CiscoMemoryPoolName

A textual name assigned to the memory pool

CiscoMemoryPoolUsed

Number of bytes from the memory pool that are currently in use

CiscoMemoryPoolFree

Indicates the number of bytes from the memory pool that are currently unused on the managed device

CiscoMemoryPoolLargestFree

Largest number of contiguous bytes from the memory pool that are currently unused

MIB Objects in CISCO-MEMORY-POOL-MIB for Monitoring Show Memory Output

Cisco IOS References

The following are the most current references, and their respective URLs, for Cisco IOS commands, system error messages, and debug commands:

Cisco IOS

For the details of Cisco IOS Release 12.2, refer to Cisco IOS Release 12.2 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/

System Error Messages

The system software sends these error messages to the console (and, optionally, to a logging server on another system) during operation. Not all system error messages indicate problems with your system. Some are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software.

Cisco IOS System Error Messages, Cisco IOS Release 12.2 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122sup/122sems/

Debug Command Reference

For the details of debugging commands, refer to Cisco IOS Debug Command Reference, Cisco IOS Release 12.2 at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122sup/122debug/


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Jan 22 01:56:49 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.