Modem Management Operations

Term	Description
MICA module	MICA modem card containing 6 (HMM) or 12 (DMM) modems.
Portware	MICA modem code.
Firmware	Microcom modem code.
SPE	Service Processing Element (SPE). A SPE unit is defined as the smallest software downloadable unit. For Microcom, an SPE is an individual modem. For MICA, a SPE is either 6 or 12 modems, depending on whether the MICA module is single or double density.
ucode	Short for microcode. Microcode in a Cisco NAS is code that gets loaded into a card, and it is typically bundled with the Cisco IOS image. (In general, Cisco does not refer to modem code microcode.)
DSP	Digital Signal Processor (DSP). The processor that does the modulating and demodulating. The modem modulation protocols, such as V.34 and V.90, that run in the DSP.

The following documents are related to m odem management operations:

Dial Solutions Configuration Guide, Managing Modems, Release 12.0

: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/
dial_c/dcmodmgt.htm

Dial Solutions Command Reference, Modem Management Commands, Release 12.0

: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/
dial_r/drprt1/drmodmgt.htm

Firmware and Portware Information

: http://www.cisco.com/univercd/cc/td/doc/product/access/fwpwinfo/index.htm

Task 1. Managing Modem Firmware

Inspecting and upgrading modem firmware is a fundamental part of commissioning a NAS. Cisco posts new firmware versions on CCO for you to download via FTP. For more information, go to the Cisco Software Center at the following URL:

http://www.cisco.com/kobayashi/sw-center/sw-access.shtml

A specific architecture surrounds integrated modem technology. Integrated modems get their modem firmware from a file that is stored in one of three places:

Bundled into the Cisco IOS software
Stored in Flash memory
Stored in bootFlash memory

The modem looks first for its firmware inside the bundled Cisco IOS image. The modem will not look outside the bundled image unless you manually change the configuration settings by using the copy source modem command or spe command.

1.1 Inspecting Modem Firmware

Before you upgrade modem firmware for MICA or Microcom modems, perform the following tasks:

Determine the version of firmware that is currently loaded in each modem
(for example, 2.6.2.0).

5300-NAS#show modem version
 
          Modem module     Firmware   Boot          DSP
  Mdm     Number           Rev        Rev           Rev
  1/0               0       2.6.2.0        
  1/1               0       2.6.2.0        
  1/2               0       2.6.2.0        
  1/3               0       2.6.2.0        
  1/4               0       2.6.2.0        
  1/5               0       2.6.2.0        
  1/6               1       2.6.2.0        
  1/7               1       2.6.2.0        
  1/8               1       2.6.2.0        
  1/9               1       2.6.2.0        
  1/10              1       2.6.2.0        
  1/11              1       2.6.2.0        
  1/12              2       2.6.2.0        
  1/13              2       2.6.2.0        
  1/14              2       2.6.2.0        
  1/15              2       2.6.2.0        
  1/16              2       2.6.2.0        
  1/17              2       2.6.2.0

Note

Find the version of firmware that is bundled with the Cisco IOS. The show modem map command displays the region of NVRAM that identifies where the modems get their firmware from at bootup.

: The field "IOS-Default" indicates that the modem gets its firmware from the bundled IOS image. At the end of the display, you see the versions of firmware that the Cisco IOS found and where they are stored. Bundled firmware is stored in the directory system:/ucode.
: The following example shows that MICA portware 2.6.2.0 is mapped to the modems and bundled with the Cisco IOS software:

5300-NAS#show modem map
 
Slot 1 has Mica Carrier card.
 
 
        Modem      Firmware   Firmware
Module  Numbers    Rev        Filename
  0   1/0  - 1/5   2.6.2.0    IOS-Default  
  1   1/6  - 1/11  2.6.2.0    IOS-Default  
  2   1/12 - 1/17  2.6.2.0    IOS-Default  
  3   1/18 - 1/23  2.6.2.0    IOS-Default  
  4   1/24 - 1/29  2.6.2.0    IOS-Default  
  5   1/30 - 1/35  2.6.2.0    IOS-Default  
  6   1/36 - 1/41  2.6.2.0    IOS-Default  
  7   1/42 - 1/47  2.6.2.0    IOS-Default  
 
Slot 2 has Mica Carrier card.
 
 
        Modem      Firmware   Firmware
Module  Numbers    Rev        Filename
  0   2/0  - 2/5   2.6.2.0    IOS-Default  
  1   2/6  - 2/11  2.6.2.0    IOS-Default  
  2   2/12 - 2/17  2.6.2.0    IOS-Default  
  3   2/18 - 2/23  2.6.2.0    IOS-Default  
  4   2/24 - 2/29  2.6.2.0    IOS-Default  
  5   2/30 - 2/35  2.6.2.0    IOS-Default  
  6   2/36 - 2/41  2.6.2.0    IOS-Default  
  7   2/42 - 2/47  2.6.2.0    IOS-Default  
 
 
Firmware-file                                     Version  Firmware-Type
=============                                     =======  =============
system:/ucode/mica_board_firmware                 2.0.2.0  Mica Boardware
system:/ucode/mica_port_firmware                  2.6.2.0  Mica Portware
system:/ucode/microcom_firmware                   5.1.20   Microcom F/W and DSP
5300-NAS#

: The Cisco AS5800 does not support the show modem map command. Use show modem bundled-firmware command instead:

as5800-RS-1#show modem bundled-firmware
List of bundled modem firmware images by slot
  Slot 4
    2.6.2.0
  Slot 5
    2.6.2.0
  Slot 6
    2.6.2.0
  Slot 7
    2.6.2.0
  Slot 8
    2.6.2.0

Inspect the directory that stores the bundled firmware files. The files are loaded into the system main memory through the ucode directory.

: In the following example, two versions of fimware are found: mica_port_firmware and microcom_firmware. The file mica_board_firmware is not user upgradeable.

5300-NAS#dir system:ucode 
Directory of system:/ucode/
 
 14  -r--      516060              <no date>  mica_board_firmware
 15  -r--      375525              <no date>  mica_port_firmware
 16  -r--      381284              <no date>  microcom_firmware
 
No space information available

Look at the existing contents of Flash or boot Flash for the following reasons:
- Determine what firmware versions you already have.
- Determine if your Flash or boot Flash is read-only or read/write.
- Determine if you have enough free space.

Note

The commands show flash and show bootflash are supported in all versions of Cisco IOS. The commands dir flash: and dir bootflash: are supported in Release 12.0T.

AS5300-1#show flash
 
System flash directory:
File  Length   Name/status
  1   6436752  c5300-is-mz.120-5.5.T
  2   392241   mica-modem-pw.2.7.1.0.bin
[6829124 bytes used, 9948092 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
 
AS5300-1#show bootflash
 
Boot flash directory:
File  Length   Name/status
  1   1220196  c5300-boot-mz.120-3.bin
  2   375525   mica-modem-pw.2.6.1.0.bin
  3   381540   mica-modem-pw.2.6.2.0.bin
[1977456 bytes used, 2216848 available, 4194304 total]
4096K bytes of processor board Boot flash (Read/Write)
 
AS5200-2#show flash
 
System flash directory:
File  Length   Name/status
  1   6721924  c5200-is-l.113-7.T.bin
[6721988 bytes used, 10055228 available, 16777216 total]
16384K bytes of processor board System flash (Read ONLY)
 
AS5200-2#show bootflash
 
Boot flash directory:
File  Length   Name/status
  1   3414112  c5200-boot-l.112-11.P2.bin
  2   374826   pw2514.ios
  3   378153   pw2515.ios
  4   381540   pw2615.ios
  5   381540   pw2617.ios
  6   381540   mica-modem-pw.2.6.2.0.bin
[5312100 bytes used, 3076508 available, 8388608 total]
8192K bytes of processor board Boot flash (Read/Write)

Filenames are arbitrary and are not necessarily indicative of their contents. If there is not enough free space on Flash or bootFlash to store the desired file, then you need to:

1. Copy the existing files that you want to keep onto a TFTP server.

2. Erase the Flash.

3. Copy the desired files into Flash.

1.2 Upgrading Modem Firmware

Cisco regularly enhances modem DSP code to improve modem performance. To obtain the latest DSP code, upgrade the NAS modem firmware.

Figure 6-1 summarizes the firmware upgrade procedure.

Figure 6-1: Modem Firmware Download Operation Example

Step 1 Read the latest modem release notes about modem and firmware information on CCO. Understand the latest enhancements and bug fixes before you download code. Refer to the following URL for the latest release notes:

http://www.cisco.com/univercd/cc/td/doc/product/access/fwpwinfo/index.htm

Step 2 Download the latest firmware from CCO to the NAS Flash or bootFlash memory. Depending on which Cisco IOS you are running, there are two ways you can get the latest firmware from CCO into the NAS Flash or bootFlash. Table 6-2 describes these two methods.

Table 6-2: Firmware Copy Commands

Cisco IOS Command Purpose

12.0T and later

copy ftp
Copy a file directly from CCO into Flash, without staging it at a local TFTP server.

11.3 and later

copy tftp: {flash: | bootflash:}

Copy from a TFTP server.

The following example uses the copy ftp command. The file mica-modem-pw.2.7.1.0.bin is copied from ftp.cisco.com to the bootFlash. Be sure to specify your own CCO username and password in the command line (as indicated in the example).

5300-NAS#ping ftp.cisco.com
 
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.31.7.171, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
5300-NAS#
5300-NAS#copy ftp://CCOUSERNAME:CCOPASSWORD@ftp.cisco.com/cisco/access/modems/mica/
mica-modem-pw.2.7.1.0.bin bootflash:
Destination filename [mica-modem-pw.2.7.1.0.bin]? <cr>
Accessing ftp:// CCOUSERNAME:CCOPASSWORD@ftp.cisco.com/cisco/access/modems/mica/mica-modem-pw.2.7.1.0.bin...Translating "ftp.cisco.com"...domain
 server (171.70.24.56) [OK]
 
Erase bootflash: before copying? [confirm]n
Loading cisco/access/modems/mica/mica-modem-pw.2.7.1.0.bin !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!
[OK - 392241/1024 bytes]
 
Verifying checksum...  OK (0x6638)
392241 bytes copied in 5.940 secs (78448 bytes/sec)
5300-NAS#

Step 3 Verify that the new firmware is in Flash or bootFlash. In this example, the unbundled firmware file is mica-modem-pw.2.7.1.0.bin.

5300-NAS#dir flash:
Directory of flash:/
 
  1  -rw-     4583276              <no date>  C5300-IS-MZ.113-9_AA
  2  -rw-     4675992              <no date>  c5300-js-mz.112-18.P.bin
  3  -rw-      392241              <no date>  mica-modem-pw.2.7.1.0.bin
  4  -rw-     5947548              <no date>  c5300-is-mz.120-4.XI1
  5  -rw-        4339              <no date>  startup-config.12.0(4)XI1
 
16777216 bytes total (1173496 bytes free)

Step 4 (Optional) Enable the debug modem maintenance command to watch the modem mapping operation take place:

5300-NAS#debug modem maintenance
Modem Maintenance debugging is on
5300-NAS#show debug
Modem Management:
  Modem Maintenance debugging is on
5300-NAS#terminal monitor

Step 5 Map the new firmware to the modems.

For MICA modems, firmware is mapped to entire modem modules (6 or 12 modem-module boundaries; not individual modems). For Microcom modems, firmware is mapped to one or more individual modems. The rule requiring that all modems in a MICA module run the same code is an architectural requirement.

Depending on which Cisco IOS Release is loaded in the NAS, there are two commands that you can use. Table 6-3 describes these two commands.

Table 6-3: Modem Mapping Commands

Cisco IOS Command Notes

12.0(5)T and later

spe

An SPE unit is defined as the smallest software downloadable unit. For Microcom, an SPE is an individual modem.

For MICA, an SPE is either 6 or 12 modems, depending on whether the MICA module is single or double density.

Before Release 12.0(5)T

copy source modem

Replace the variable source with the keyword flash or bootflash.

Cisco IOS	Command	Notes
12.0(5)T and later	spe	An SPE unit is defined as the smallest software downloadable unit. For Microcom, an SPE is an individual modem. For MICA, an SPE is either 6 or 12 modems, depending on whether the MICA module is single or double density.
Before Release 12.0(5)T	copy source modem	Replace the variable source with the keyword flash or bootflash.

The following MICA example uses the spe command. The numbers 1/0 1/7 refer to modem module numbers 0 through 7 in slot 1. These numbers do not refer to specific modem numbers (for example, slot/port for Microcom modems). In this example, 48 modems are upgraded (8 SPE x 6 modems per module = 48 modems).

5300-NAS#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
5300-NAS(config)#spe 1/0 1/7                                      
5300-NAS(config-spe)#firmware location flash:mica-modem-pw.2.7.1.0.bin
5300-NAS(config-spe)#
*Jan 23 11:14:48.702: %MODEM-5-DL_START: Modem (1/0) started firmware download
*Jan 23 11:14:48.702: %MODEM-5-DL_START: Modem (1/1) started firmware download
*Jan 23 11:14:48.702: %MODEM-5-DL_START: Modem (1/2) started firmware download
*Jan 23 11:14:48.702: %MODEM-5-DL_START: Modem (1/3) started firmware download
*Jan 23 11:14:48.702: %MODEM-5-DL_START: Modem (1/4) started firmware download
*Jan 23 11:14:48.702: %MODEM-5-DL_START: Modem (1/5) started firmware download
*Jan 23 11:15:03.042: %MODEM-5-DL_GOOD: Modem (1/0) completed firmware download:
*Jan 23 11:15:03.042: %MODEM-5-DL_GOOD: Modem (1/1) completed firmware download:
*Jan 23 11:15:03.042: %MODEM-5-DL_GOOD: Modem (1/2) completed firmware download:
*Jan 23 11:15:03.042: %MODEM-5-DL_GOOD: Modem (1/3) completed firmware download:
*Jan 23 11:15:03.042: %MODEM-5-DL_GOOD: Modem (1/4) completed firmware download:
*Jan 23 11:15:03.042: %MODEM-5-DL_GOOD: Modem (1/5) completed firmware download:
*Jan 23 11:15:03.046: %MODEM-5-DL_START: Modem (1/6) started firmware download
*Jan 23 11:15:03.046: %MODEM-5-DL_START: Modem (1/7) started firmware download
*Jan 23 11:15:03.046: %MODEM-5-DL_START: Modem (1/8) started firmware download
*Jan 23 11:15:03.050: %MODEM-5-DL_START: Modem (1/9) started firmware download
*Jan 23 11:15:03.050: %MODEM-5-DL_START: Modem (1/10) started firmware download
*Jan 23 11:15:03.050: %MODEM-5-DL_START: Modem (1/11) started firmware download
*Jan 23 11:15:17.394: %MODEM-5-DL_GOOD: Modem (1/6) completed firmware download:
*Jan 23 11:15:17.394: %MODEM-5-DL_GOOD: Modem (1/7) completed firmware download:
*Jan 23 11:15:17.394: %MODEM-5-DL_GOOD: Modem (1/8) completed firmware download:
*Jan 23 11:15:17.394: %MODEM-5-DL_GOOD: Modem (1/9) completed firmware download:
*Jan 23 11:15:17.394: %MODEM-5-DL_GOOD: Modem (1/10) completed firmware download
*Jan 23 11:15:17.394: %MODEM-5-DL_GOOD: Modem (1/11) completed firmware download
.
.
.
*Jan 23 11:16:43.482: %MODEM-5-DL_GOOD: Modem (1/47) completed firmware download

In the previous example, the specified SPE range gets updated with new firmware in batches of six modems at a time. If double density modems were installed, batches of 12 modems would be updated.

Note below that the SPE range 1/0 to 1/7 is mapped to firmware 2.7.1.0. However, SPE range 2/0 through 2/7 is still mapped to the firmware that is bundled with the Cisco IOS.

!
spe 1/0 1/7
 firmware location flash:mica-modem-pw.2.7.1.0.bin
spe 2/0 2/7
 firmware location system:/ucode/mica_port_firmware
!

The following MICA example is for the copy source modem command. Unlike the spe command, the numbers 1/0-1/5 refer to specific modem numbers (slot/port). The busyout keyword will gracefully busy out the modems if the modems are off hook.

cisco#copy bootflash modem
Source filename []? mica-modem-pw.2.6.2.0.bin
Modem Numbers (<slot>/<port> | group <number> | all)? 1/0-1/5
Type of service [busyout/reboot/recovery] busyout
Allow copy of "bootflash:mica-modem-pw.2.6.2.0.bin" to modems? [yes/no]yes
cisco#
2d05h: %MODEM-5-DL_START: Modem (1/0) started firmware download
2d05h: %MODEM-5-DL_START: Modem (1/1) started firmware download
2d05h: %MODEM-5-DL_START: Modem (1/2) started firmware download
2d05h: %MODEM-5-DL_START: Modem (1/3) started firmware download
2d05h: %MODEM-5-DL_START: Modem (1/4) started firmware download
2d05h: %MODEM-5-DL_START: Modem (1/5) started firmware download
2d05h: %MODEM-5-DL_GOOD: Modem (1/0) completed firmware download:
2d05h: %MODEM-5-DL_GOOD: Modem (1/1) completed firmware download:
2d05h: %MODEM-5-DL_GOOD: Modem (1/2) completed firmware download:
2d05h: %MODEM-5-DL_GOOD: Modem (1/3) completed firmware download:
2d05h: %MODEM-5-DL_GOOD: Modem (1/4) completed firmware download:
2d05h: %MODEM-5-DL_GOOD: Modem (1/5) completed firmware download:

Step 6 Verify that the new firmware was successfully mapped to the modems.

In the following example:

SPE 1/0 applies to modems 1/0 through 1/5.
SPE 1/1 applies to modem 1/6 through 1/11, and so on.
The MICA modules 0 through 7 in slot 1 are running version 2.7.1.0 (not 2.6.2.0).
All the modems in slot 2 are still running version 2.6.2.0, which is bundled into the Cisco IOS image (see the field IOS-Default).

5300-NAS#show modem map
 
Slot 1 has Mica Carrier card.
 
 
        Modem      Firmware   Firmware
Module  Numbers    Rev        Filename
  0   1/0  - 1/5   2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
  1   1/6  - 1/11  2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
  2   1/12 - 1/17  2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
  3   1/18 - 1/23  2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
  4   1/24 - 1/29  2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
  5   1/30 - 1/35  2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
  6   1/36 - 1/41  2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
  7   1/42 - 1/47  2.7.1.0    flash:mica-modem-pw.2.7.1.0.bin  
 
Slot 2 has Mica Carrier card.
 
 
        Modem      Firmware   Firmware
Module  Numbers    Rev        Filename
  0   2/0  - 2/5   2.6.2.0    IOS-Default  
  1   2/6  - 2/11  2.6.2.0    IOS-Default  
  2   2/12 - 2/17  2.6.2.0    IOS-Default  
  3   2/18 - 2/23  2.6.2.0    IOS-Default  
  4   2/24 - 2/29  2.6.2.0    IOS-Default  
  5   2/30 - 2/35  2.6.2.0    IOS-Default  
  6   2/36 - 2/41  2.6.2.0    IOS-Default  
  7   2/42 - 2/47  2.6.2.0    IOS-Default  
 
 
Firmware-file                                     Version  Firmware-Type
=============                                     =======  =============
system:/ucode/mica_board_firmware                 2.0.2.0  Mica Boardware
system:/ucode/mica_port_firmware                  2.6.2.0  Mica Portware
system:/ucode/microcom_firmware                   5.1.20   Microcom F/W and DSP
bootflash:mica-modem-pw.2.6.2.0.bin               2.6.2.0  Mica Portware
flash:mica-modem-pw.2.7.1.0.bin                   2.7.1.0  Mica Portware
5300-NAS#

Task 2. Configuring Modems Using Modem Autoconfigure

This section describes how to apply a new modem capability (modemcap) to an integrated modem. A modemcap is a database of setup strings that is used by the modem autoconfigure function to change a modem's default settings.

Modemcaps have many applications:

A modem's default settings are not optimal. For example, a modem function that you want is not enabled by default.
Two separate modem pools need to be set up in the NAS to perform two different tasks. For example, one pool supports V.90. The other pool has a maximum speed set at 26400 bps to support older modems.
A specialized application is required. For example, a NAS supporting a point-of-sale (POS) application such as a charge card reader. A modemcap is required that will tune the modem for a fast trainup time at the expense of having a slower connect speed.

Always use a modemcap (even if you only want the modem's default settings). To display the modemcaps that are built into the Cisco IOS, enter the show modemcap command. Modemcaps are configured on a per modem basis. They are not configured on a per modem module or service processing element (SPE) basis.

2.1 Basic Rules for Modem Autoconfigure

The following list describes the basic rules:

1. Never use the modem autoconfigure discovery command. Applying specific modemcaps reduces the risk of error.

2. Always use the modem autoconfigure type modem-name command. This command improves your modem's performance. See CSCdk15302 for an explanation.

: The modem autoconfigure type mica command can be used to reset any integrated modem (not only MICA), back to its factory defaults. The keyword mica is a built-in modemcap that only functions as &F (return to defaults).

3. When you use the modem autoconfigure command, be sure that any script reset function is removed. A script reset is redundant and possibly harmful.

: A script reset is a chat script that is applied to a line when the line resets. The modem autoconfigure function is applied when the system starts up, not just when the line resets.

4. When creating a modemcap, ignore all the strange and confusing fields. Put your modem init string into the MSC (Miscellaneous) field:

Always start your init string with &F (or, for non-cisco modems, with the preferred &F1, &F2, etc.)

Never put an &W into an init string. An &W can wear out the EPROM on modems where this is not a no op (that is, a statement or operation that does nothing).
For MICA modems, always be sure that &D2 (not &D3) is in effect. See CSCdk15260 and CSCdk15302 for an explanation.

2.2 Modem Autoconfigure K56Flex Example

The following modem-autoconfigure string disables V.8bis/K56Flex. The string &F&D2s53=0 is applied to two MICA modems. Disabling V.8bis reduces trainup time by about two seconds, and it prevents trainup problems with older client modems.

Step 1 Watch the modem autoconfigure function run, so you can see if there are any typos in the modem string:

5300-NAS#debug confmodem
Modem Configuration Database debugging is on
5300-NAS#show debug
Modem Autoconfig:
  Modem Configuration Database debugging is on
5300-NAS#terminal monitor

Step 2 Remove any previous modem autoconfigure entry:

5300-NAS#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
5300-NAS(config)#no modemcap entry mica-noKflex
% Modemcap entry 'mica-noKflex' does not exist

Step 3 Add the new entry:

5300-NAS(config)#modemcap edit mica-noKflex misc &F&D2s53=0

Note The MICA and Microcom AT command references are posted at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/mod_info/at/index.htm

Step 4 Apply the new entry to the specified lines. Re-enter the modem autoconfigure command each time you change a modemcap. Modem-autoconfigure strings are not applied to busy modems. Modem strings are applied after modems disconnect.

5300-NAS(config)#line 1 2
5300-NAS(config-line)#modem autoconfigure type mica-noKflex
5300-NAS(config-line)#
Oct 25 19:46:06.960 PDT: TTY1: detection speed (115200) response ---OK---
Oct 25 19:46:06.960 PDT: TTY1: Modem command:  --AT&F&D2s53=0--
Oct 25 19:46:06.960 PDT: TTY2: detection speed (115200) response ---OK---
Oct 25 19:46:06.960 PDT: TTY2: Modem command:  --AT&F&D2s53=0--
Oct 25 19:46:09.520 PDT: TTY1: Modem configuration succeeded
Oct 25 19:46:09.520 PDT: TTY1: Detected modem speed 115200
Oct 25 19:46:09.520 PDT: TTY1: Done with modem configuration
Oct 25 19:46:09.520 PDT: TTY2: Modem configuration succeeded
Oct 25 19:46:09.520 PDT: TTY
5300-NAS(config-line)#

If you want to reset the modem to its factory defaults, do not simply remove the modem autoconfigure command. Rather, replace it with another modem autoconfigure type name command where name is a modemcap whose only action is &F. (In recent Cisco IOS releases, the built-in mica modemcap entry will do this.)

Task 3. Gathering and Viewing Call Statistics

Making sure that your modems are connecting at the correct connections speeds is an important aspect of managing modems. This section details the following methods for gathering and viewing modem performance statistics:

Note If you detect low connection speeds across all the modems, you may have a faulty channelized T1/E1 or ISDN PRI line connection.

3.1 Using the Cisco IOS EXEC (CLI)

The Cisco IOS command line interface (CLI) contains many modem management show commands. Use these commands to gather and view modem statistics. This section provides a bulleted list detailing some of the most useful commands.

Here is a list of the show modem command options:

5300-NAS#show modem ?
  <0-2>               Slot/Port number (i.e. 1/1)
  at-mode             AT session connections
  call-stats          Calling statistics for all system modems
  configuration       Modem configuration
  connect-speeds      Connection speeds for all system modems
  cookie              Hex dump of all modem cookies
  csm                 CSM modem information
  group               Modem group information
  log                 Modem event log
  mapping             Show modem firmware mapping
  mica                Modem exec commands
  operational-status  Modem operational status
  summary             Summary statistics for all system modems
  test                Modem test log
  version             Version information for all system modems
  |                   Output modifiers
  <cr>

Display a summary of the modem call statistics:

5300-NAS#show modem summary
         Incoming calls       Outgoing calls      Busied   Failed   No    Succ
Usage  Succ   Fail  Avail   Succ   Fail  Avail    Out      Dial     Ans   Pct.
  43% 60005   4678     25      3     11      0        0       13     8     92%

The following table describes some of the significant fields in the previous example.
Table 6-4: Show Modem Summary Field Descriptions

Field Description

Succ 60005
60,005 calls successfully trained up. The Cisco IOS saw "DSR" go high (still does not mean that PPP negotiated successfully).

Fail 4678
4,678 calls came into the modem, the modem went offhook, but the modem did not train up.

Succ Pct. 92%
The overall success percentage is 92%.

No Ans 8
Eight calls came into the modem but the modem did not go offhook (CPU was too busy). Unless you misconfigured the NAS, this counter should be very low (under 1% of the total calls).

Field	Description
Succ 60005	60,005 calls successfully trained up. The Cisco IOS saw "DSR" go high (still does not mean that PPP negotiated successfully).
Fail 4678	4,678 calls came into the modem, the modem went offhook, but the modem did not train up.
Succ Pct. 92%	The overall success percentage is 92%.
No Ans 8	Eight calls came into the modem but the modem did not go offhook (CPU was too busy). Unless you misconfigured the NAS, this counter should be very low (under 1% of the total calls).

Display the disconnect reasons for the modems that trained up:

5300-NAS#show modem call-stats 0
 
  dial-in/dial-out call statistics
 
       compress  retrain lostCarr userHgup  rmtLink  trainup hostDrop wdogTimr
  Mdm     #   %    #   %    #   %    #   %    #   %    #   %    #   %    #   %
 Total  237      916      413      124     9999     1064     8496        0    
 
  dial-out call statistics
 
         noCarr noDitone     busy    abort dialStrg autoLgon dialTout  rmtHgup
  Mdm     #   %    #   %    #   %    #   %    #   %    #   %    #   %    #   %
 Total 1715        0        0        0        0        0        0        0

Table 6-5 describes some of the significant fields in the previous example.

Table 6-5: Show Modem Call-Status Field Descriptions

Field Description

rmtLink 9999
RmtLink is the most common disconnect reason. RmtLink means that the modem trained up, error correction was negotiated, and the client DTE decided to hang up. All the call-stat counters do not go higher than 9999.

hostDrop
HostDrop (or dtrDrop) means the Cisco IOS (DTE) informed the modem to terminate the call. For example:

Idle timeouts

Absolute timeouts

Authentication failures

PPP negotiation failures

The Cisco IOS learns from the telephone switch that the DS0 was disconnected.

Field	Description
rmtLink 9999	RmtLink is the most common disconnect reason. RmtLink means that the modem trained up, error correction was negotiated, and the client DTE decided to hang up. All the call-stat counters do not go higher than 9999.
hostDrop	HostDrop (or dtrDrop) means the Cisco IOS (DTE) informed the modem to terminate the call. For example: Idle timeouts Absolute timeouts Authentication failures PPP negotiation failures The Cisco IOS learns from the telephone switch that the DS0 was disconnected.

Besides the "hostDrop" message, all other disconnect reasons are not good. If the call trained up without EC, then the peer modem will probably not communicate an orderly disconnect with the Cisco IOS. For example, the messages "lostCarr" or "retrain" might be displayed even though the peer DTE voluntarily disconnected. The collective total of disconnect reasons should be less than 10% of the total number of calls.

Look at detailed disconnect reasons for individual modems:

5300-NAS#show modem call-stats  
 
  dial-in/dial-out call statistics
 
       compress  retrain lostCarr userHgup  rmtLink  trainup hostDrop wdogTimr
  Mdm     #   %    #   %    #   %    #   %    #   %    #   %    #   %    #   %
  1/0     5   2   23   2    7   1    2   1  971   2   20   1  176   2    0   0
* 1/1     8   3   18   1   12   2    6   4  949   2   29   2  167   1    0   0
  1/2     3   1   14   1    8   1    2   1  954   2   26   2  180   2    0   0
* 1/3     4   1   19   2    9   2    1   0  927   2   21   1  202   2    0   0
* 1/4     1   0   20   2   10   2    2   1  961   2   23   2  192   2    0   0
  1/5     2   0   19   2   10   2    4   3  893   1   30   2  182   2    0   0
  1/6     4   1   20   2   10   2    3   2  778   1   21   1  140   1    0   0
* 1/7     6   2   21   2    7   1    1   0  915   2   25   2  176   2    0   0
* 1/8     5   2   21   2    7   1    2   1 1019   2   28   2  159   1    0   0
  1/9     3   1   10   1    8   1    2   1  939   2   22   2  191   2    0   0
  1/10    1   0   29   3    9   2    1   0  918   2   28   2  194   2    0   0
  1/11    2   0   27   2    9   2    4   3  981   2   27   2  174   2    0   0
* 1/12    7   2   21   2   10   2    5   4  966   2   24   2  182   2    0   0
  1/13    6   2   21   2   10   2    1   0  977   2   32   3  168   1    0   0

Display a summary of the range of connect speeds. Specify the top speed of interest followed by a 0. This example displays the initial connect speeds in each direction (transmit and receive) for the range of speeds that go up to 56K. No connections happened at 56000 bps. The transmit speed with the highest hit counter is 48K (9161 hits). The receive-connect speeds are all zeros because V.90 is a transmit only speed.

5300-NAS#show modem connect-speeds 56000 0
 
  transmit connect speeds
 
  Mdm   48000  49333  50000  50667  52000  53333  54000  54667  56000 TotCnt
 Tot     9161   5047   1454   3291    813   1427      0     25      0  60012
 Tot %     15      8      2      5      1      2      0      0      0
 
  receive connect speeds
 
  Mdm   48000  49333  50000  50667  52000  53333  54000  54667  56000 TotCnt
 Tot        0      0      0      0      0      0      0      0      0  60012
 Tot %      0      0      0      0      0      0      0      0      0

Inspect the range of speeds below 56000 bps (38667 to 46667). This is the distribution of speeds of PCM users (KFlex users and V.90 users). Compare this output with the previous example. The peak speed is at 48K, which had 9,161 hits---15% of all callers.

5300-NAS#show modem connect-speeds 46666 0
 
  transmit connect speeds
 
  Mdm   38667  40000  41333  42000  42667  44000  45333  46000  46667 TotCnt
 Tot      349    192    700    221    780   2188   1123    804    693  60011
 Tot %      0      0      1      0      1      3      1      1      1
 
  receive connect speeds
 
  Mdm   38667  40000  41333  42000  42667  44000  45333  46000  46667 TotCnt
 Tot        0      0      0      0      0      0      0      0      0  60011
 Tot %      0      0      0      0      0      0      0      0      0

Examine the DS0 timeslots on each T1 that are used to carry the modem calls. The following example shows that the telco is distributing calls into this hunt group evenly across the T1s. There are a total of 29 (20+9) DS0s currently active.

: The high water mark reports the highest number of DS0s that were in use at one time. However, be sure to inspect the entire dial pool. Entire T1s have been known to remain idle in some hunt groups.

5300-NAS#show controllers t1 call-counters 
T1 0:
  DS0's Active: 20
  DS0's Active High Water Mark: 23
  TimeSlot   Type   TotalCalls   TotalDuration
      1       pri        6536       3w1d
      2       pri        6701       2w3d
      3       pri        5789       2w0d
      4       pri        5498       1w2d
      5       pri        5497       3d02h
      6       pri        5126       7w0d
      7       pri        4525       6w1d
      8       pri        4401       5w3d
      9       pri        4096       4w4d
     10       pri        3961       3w3d
     11       pri        3320       3w0d
     12       pri        3138       1w3d
     13       pri        2912       4d05h
     14       pri        2486       6w4d
     15       pri        2042       5w5d
     16       pri        1644       4w5d
     17       pri        1413       4w1d
     18       pri        1071       3w3d
     19       pri         884       2w4d
     20       pri         675       2w0d
     21       pri         507       1w3d
     22       pri         380       1w1d
     23       pri         263       5d17h
T1 1:
  DS0's Active: 9
  DS0's Active High Water Mark: 23
  TimeSlot   Type   TotalCalls   TotalDuration
      1       pri        8985       3w2d
      2       pri        8650       2w4d
      3       pri        8594       1w3d
      4       pri        7813       4d03h
      5       pri        7671       6w3d
      6       pri        6955       5w5d
      7       pri        6492       4w3d
      8       pri        6343       3w4d
      9       pri        5668       2w3d
     10       pri        5398       6d09h
     11       pri        4842       6w6d
     12       pri        4413       5w3d
     13       pri        4050       4w1d
     14       pri        3339       2w6d
     15       pri        3019       1w2d
     16       pri        2493       1d14h
     17       pri        2104       6w0d
     18       pri        1664       5w1d
     19       pri        1395       3w6d
     20       pri        1094       3w3d
     21       pri         811       2w6d
     22       pri         688       2w0d
     23       pri         482       1w3d
 
Total DS0's Active High Water Mark: 46

Note

3.2 Using Modem Call-Record Terse

Starting with Cisco IOS Releases 11.3AA and 12.0T, modem call records can be sent to syslog and examined to perform statistical analysis.

For example, you can monitor:

Modulation trends such as V.90 verses V.34
Call time durations (consistent short connection times on a modem, regular Lost Carrier counts)
Unavailable user IDs
PPP negotiation or authentication failures

The following example enables modem call-records and sends the logs to wherever your syslog output goes, for example:

To the console---if you do not have the no logging console command enabled.
To the terminal line---if you have the terminal monitor command enabled.
To a syslog host---if you have one configured.

5300-NAS#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
5300-NAS(config)#modem call-record terse
 
*Jan  1 04:19:50.262: %CALLRECORD-3-MICA_TERSE_CALL_REC: DS0 slot/contr/chan=0/0
/0, slot/port=2/0, call_id=18, userid=(n/a), ip=0.0.0.0, calling=4082329440, cal
led=5710945, std=V.34+, prot=LAP-M, comp=V.42bis both, init-rx/tx b-rate=26400/2
6400, finl-rx/tx b-rate=26400/26400, rbs=0, d-pad=None, retr=2, sq=3, snr=25, rx
/tx chars=79/94701, bad=0, rx/tx ec=60/204, bad=521, time=698, finl-state=Steady
, disc(radius)=(n/a)/(n/a), disc(modem)=A220 Rx (line to host) data flushing - n
ot OK/EC condition - locally detected/received DISC frame -- normal LAPM termina
tion

3.3 Using SNMP

Modem connect speeds can be graphed using SNMP MIBs. The graph shown in Figure 6-2 was created with Cisco Access Manager (CAM). The graph describes the modem connect-speed performance activity of one NAS for one month. The following connect speeds are transmitted by the NAS and received by the client modem. Most of the calls performed between 28000 and 31200 bps. This NAS is one member of an access stack.

Figure 6-2: Graphed Modem-Connect Speeds for One Month

What to do Next

Perform the tasks in the section "Enabling Management Protocols: NTP, SNMP, and Syslog."

Cisco IOS	Command	Purpose
12.0T and later	copy ftp	Copy a file directly from CCO into Flash, without staging it at a local TFTP server.
11.3 and later	copy tftp: `{`flash: `\|` bootflash:`}`	Copy from a TFTP server.

Table of Contents

Modem Management Operations