|
|
The Cisco AS5200 universal access server now supports 56K digital modem cards.
56K modems are used for making high-speed connections across digital networks. Ultimately, this means that files transmitted up to 56 kbps arrive at the desktop at nearly twice the speed of standard V.34 (28.8-kbps) connections. The wait for information is reduced by nearly 50 percent.
56K modems are ideal for serious Internet users who want to quickly dial in to corporate LANs or download web pages containing sound, video, graphics, and other large files over digital networks using standard telephone lines.
Traditional modems assume that both ends of a modem conversation use an analog connection over the public switched telephone network. Data signals are converted from digital to analog and back again to digital, limiting transmission speeds to 33.6 kbps. 56K modems however, assume that one end of the modem conversation has a pure digital connection to the phone network and takes advantage of that high-speed digital connection. This is a new technique where the network is viewed as a digital transmission medium and the data is encoded for transmission over an end user's telephone line, which is also known as the local loop. The downstream data is digitally encoded instead of being modulated. Upstream analog-to-digital communication at the local loop can transmit up to 33.6 kbps. Downstream digital to analog communication at the local loop can transmit up to 56 kbps. To maximize channel bandwidth for 56 kbps connections, the ISDN PRI interface must be used. (See Figure 11.)
DSP--Digital signal processor. Special DSP software must be copied to the 56K modems, to enable speeds up to 56 kbps. This file is posted on Cisco System's FTP server. Download instructions are provided later in this document. See the section "Configuration Tasks."
The following prerequisites apply to this feature:
You must run specific compatible versions of 56K modem firmware and DSP software to experience K56flex modulation. These files are not included in the 56K modem cards. This section describes how to download these software files from Cisco System's FTP server (called CCO) to your 56K modems. (See Figure 12.)
Before 56K modems were introduced, modem firmware was upgraded with a single firmware file stored in the modem's Flash memory. The file remained in the modem's Flash memory. However with 56K modems, the modem's Flash memory is not large enough to retain the necessary software to transmit at 56 kbps. Therefore the software is divided in to two parts--56K modem firmware and DSP software. The firmware resides in the modem's Flash memory. The DSP software, which is the core intelligence of K56flex technology, runs from the access server's RAM. Because the DSP software is not retained across reloads or power cycles, the image is stored in the access server's boot Flash memory. (See Figure 13.)
Take the following steps to enable 56K modems to transmit at speeds up to 56 kbps:
For instructions on how to install 56K modem cards, refer to the publication Installing 56K Modem Cards in Cisco AS5200 Universal Access Servers. This document came with your 56K modem card.
Table 27 describes the firmware and DSP software posted to Cisco System's FTP server, which is called CCO. You must download these files to a TFTP server on your LAN then copy the files to the 56K modems installed in the access server.
| File Type | File Posted to Cisco's FTP Server | File Destination |
|---|---|---|
| 56K modem firmware | mcom-modem-fw-3.1.30-1.1.0.bin | Flash memory on the 56K modems |
| 56K DSP software | mcom-modem-dsp-3.1.30-1.1.0.bin | boot Flash memory on the Cisco AS5200 |
Choose a method to download these files from Cisco Systems:
Log in to Cisco's Software Center at the following URL to download both 56K files. You must log in as a Cisco registered user. After the files are downloaded to your desktop computer, you must transfer them to a TFTP server on your network using a FTP application.
http://www.cisco.com/cgi-bin/as5200.pl
Take the following steps to download both 56K files from Cisco's FTP server using an FTP client application.
Step 1 Log in to Cisco System's CCO FTP server, which is called cco.cisco.com:
ftp cco.cisco.com
Step 2 Enter your CCO registered username and password (for example, harry and letmein):
harry
letmein
Step 3 Specify the directory that holds the modem firmware and DSP software files, which is /cisco/access/5200/56k:
cd /cisco/access/5200/56k
Step 4 View the contents of the directory with the ls command:
ls
Step 5 Specify a binary image transfer:
binary
Step 6 Copy the modem firmware and DSP software files from the server to your local environment with the get command. Copy the following two files:
The following example downloads the DSP software file:
get mcom-modem-dsp-3.1.30-1.1.0.bin
The following example downloads the modem firmware file:
get mcom-modem-fw-3.1.30-1.1.0.bin
Step 7 Quit your terminal session:
quit
Step 8 Verify that you successfully transferred the files to your local directory:
ls -al
pwd
If you haven't already done so, you must now transfer these files to a local TFTP server that your Cisco AS5200 can access.
The procedure for copying the 56K modem firmware from a local TFTP server to the 56K modem's Flash memory is described in this section:
Before you back up your boot Flash image with the copy bootflash tftp command, you must create an empty destination file on your local TFTP server:
Step 1 Log on to the Cisco AS5200 and find out the name of the boot image file in boot Flash memory with the show bootflash command:
enable
letmein
show bootflash
Step 2 Go to your TFTP server and create an empty file using your boot image's filename, then change its permissions to be world writable:
touch c5200-is-l.112-6.4
chmod 666 c5200-is-l.112-6.4
ls -l c5200-is-l.112-6.4
The placeholder or destination file is now created and prepared for the backup copy operation. Proceed to the next section "Step 2Back Up the Boot Flash Image and Disable Modem Autoconfigure."
Perform the following steps on the Cisco AS5200:
Step 1 Back up your Boot Flash image to a local TFTP server on your network with the copy bootflash tftp command. This provides a recovery mechanism for you in case you accidentally erase or damage your Boot Flash image in one of the later steps.
copy bootflash tftp
Step 2 Enter global configuration mode and disable the modem autoconfigure command on the TTY lines that correspond with the 56K modems. Ignore this step if this command is not enabled in your system configuration. In the following example, one 12-port 56K modem card is installed in slot 2:
configure terminal
line 13 24
no modem autoconfigure
exit
exit
The boot image is now backed up and modem autoconfigure is disabled. Proceed to the next section "Step 3Upgrade to the Latest 56K Modem Firmware."
Perform the following steps:
Step 1 Log in to the Cisco AS5200 and copy the new modem firmware file from your TFTP server directly to the installed 56K modems using the copy tftp modem Privileged EXEC command:
copy tftp modem
Step 2 Specify the range of 56K modems that you want to upgrade. This example shows the range of modems to be 2/12 through 2/23:
2/12-2/23
Step 3 Specify the name or address of the TFTP server holding the new modem firmware. Press the Return key to accept the default name or IP address enclosed in the brackets []. Also specify the source path/filename of the firmware.
tftp-server
mcom-modem-fw-3.1.30-1.1.0.bin
The 56K modems are now upgraded to the latest version of modem firmware. Proceed to the next section "Copy the RAM-Based DSP Software to the 56K Modems."
The procedure for copying the DSP software from to a local file server to the access server's boot Flash memory is described in this section:
These two steps are performed only once. Although the DSP software runs from RAM, the Cisco IOS software automatically copies the DSP code from boot Flash memory to the 56K modems each time the access server power cycles in the future. After you copy the DSP software in to boot Flash memory for the first time, you should not have to perform these steps again.
Step 1 Copy the DSP software file from your TFTP server to the access server's boot Flash memory using the copy tftp bootflash command. The Cisco IOS software prompts you with a sequence of questions such as name/address of the TFTP server and the DSP filename to be copied. Answer all of the questions accordingly.
copy tftp bootflash
Step 2 Specify the address or name of the server that currently holds the DSP software. You must also specify the source path/filename of the DSP software and the destination filename. The system software proposes a destination filename for you, which is enclosed in square brackets []. Press the Return key to accept the default destination name.
tftp-server
mcom-modem-dsp-3.1.30-1.1.0.bin
Step 3 
When the system asks to confirm erasing the Flash memory device before copying the DSP file, enter no. You will now see a warning message appear that says the DSP file cannot be executed on the system (unlike a feature set or system image). Ignore this message.
no
Step 4 Initiate the copy operation by entering y then pressing the Return key at the [confirm] prompt:
y
Step 5 Continue with the copy operation by entering yes and pressing the Return key:
yes
Now the DSP software is in the access server's boot Flash memory. Proceed to the next section, "Step 2Copy the RAM-Based DSP Software from Boot Flash Memory to the 56K Modems" for step-by-step instructions on how to transfer the DSP image to the 56K modems.
Step 1 Copy the DSP software to the 56K modems by entering the copy flash modem Privileged EXEC command. After you enter this command, specify the range of 56K modems that you want to target with the DSP software. In this example, only one 12-port 56K modem board is installed in the Cisco AS5200.
copy flash modem
2/12-2/23
Step 2 Specify the filename of the DSP software and press the Return key. Note that the filename must be preceded by bootflash:, which is necessary to address the file that is stored in boot Flash memory.
bootflash:mcom-modem-dsp-3.1.30-1.1.0.bin
Step 3 Proceed with the DSP download by entering y and pressing the Return key:
y
Step 4 Verify that the DSP software copied to the 56K modems with the show modem version command. In this example, modems 2/12 through 2/23 are loaded with the new DSP software:
show modem version
During the DSP download process, you may receive an error message if the download fails. Use Table 27 to troubleshoot the reason for failure.
| Error Message | Description | Recommended Action |
|---|---|---|
| %%ERROR: Modem <slot/port>, Modem Firmware file is not valid for modem type. | The specified modem firmware is not compatible with the target modem. For example, V.34 modems cannot be upgraded with 56K firmware. If you have a bank of non-56K modems in the access server and specify the all option in the copy tftp modem command, this error message will appear and not download 56K firmware where appropriate. | Verify that you are copying 56K modem firmware to 56K modems. Also use the show modem command to verify that you specified the correct slot/port or range. |
| %%ERROR: Modem <slot/port> currently being downloaded. | The DSP software is currently downloading to the 56K modems. | The download process is temporarily delayed or performed twice, which is acceptable. The download is not interrupted or damaged. Simply wait until the download is finished. |
| %%ERROR: DSP file not found in system Flash. | The system software cannot find the 56K DSP file in Flash memory. | Copy the DSP file from your local file server to boot Flash memory using the copy tftp bootflash command. |
| %%ERROR: Get NVRAM download DSP file/modem list failed. | An internal system error occurred with NVRAM. | Try power cycling the router to fix the problem. |
| %%ERROR: DSP Firmware file header is not valid. | The specified file is not intended for the 56K DSP download operation. | Verify that you are copying the correct DSP file, which is mcom-modem-dsp-3.1.30-1.1.0.bin. |
| %%ERROR: Modem <slot/port>, download functions not initialized. | The DSP code can not be downloaded to the specified modem. | Use the show modem command to verify that you are downloading to a supported 56K modem. |
| %%ERROR: Modem <slot/port>, download not done. | The DSP software is currently downloading to the 56K modems. | The download process will be temporarily delayed. Wait until the download is complete. |
| %%ERROR: Modem <slot/port> is held in reset. | The specified modem is held in reset mode. The DSP software will not download to this modem. | Take the modem out of reset mode then copy the DSP software again. |
| %%ERROR: NVRAM write for DSP download filename entry failed. | There is a NVRAM table problem. | Reissue the copy tftp bootflash command and copy the DSP file again. |
| %%ERROR: NVRAM table is bad. Use Copy command to set DSP filename. | There is a NVRAM table problem. | Reissue the copy tftp bootflash command and copy the DSP file again. |
| %%ERROR: NVRAM is bad, Report this as a problem. | The NVRAM is not functioning properly. | Try power cycling the router to fix the problem. |
| %%ERROR: Ran out of Memory, Install more memory. | The system software needs more memory to complete the copy operation. | Install additional memory. |
The boot Flash memory in your Cisco AS5200 may not have the available space to accept the additional 56K images or files. If you experience this, you must erase the entire boot Flash memory followed by restoring the boot image before performing the necessary 56K copy operations. Because the Cisco AS5200's Flash file system does not allow individual files to be erased from boot Flash memory, you must erase the entire contents of boot Flash memory at one time. To do this, refer to the following table.
| Warning Do not proceed with erasing your boot Flash memory unless you have a back up of your boot image on your TFTP server. |
| Task | Command |
|---|---|
| Step 1 If you haven't already done so, upload your current boot image to a local TFTP server. The contents of the boot Flash memory is displayed and the system software prompts you for the source filename to be copied. | copy bootflash tftp |
| Step 2 Erase the entire contents of the boot Flash memory. | erase bootflash |
| Step 3 Copy the boot image from your local file server to the Cisco AS5200's boot Flash memory. Specify the destination filename that was copied in Step 1. | copy tftp bootflash |
| Step 4 Copy the 56K modem firmware and DSP software files as described in the section "Copy the RAM-Based DSP Software to the 56K Modems." |
This section provides command reference documentation for the show modem command, which is modified to support the 56K modem technology.
To display modem performance statistics on a Cisco AS5200, use the show modem EXEC command.
show modem [csm][log][slot/modem-port][group number][version][summary][at-mode]| csm | (Optional) Shows the internal status of the call switching module. |
| log | (Optional) Shows the modem history event status performed on a manageable modem or group of modems. |
| slot/modem-port | (Optional) Specifies the location of a slot and modem port. If this number is not specified, statistics for all connected modems are displayed. Remember to include the forward slash (/) when entering this variable. |
| group number | (Optional) Specifies the location of a specific group of modems. If this number is not specified, statistics for all modems in the access server are displayed. |
| version | (Optional) Displays information for modem firmware version, controller and DSP code version (for 56K modem port modules only), and boot code version. |
| summary | (Optional) Displays a cumulative statistics report for all manageable modems dialing into and out of the network. |
| at-mode | (Optional) Displays all AT sessions connected to manageable modems. |
User and Privileged EXEC
The keywords log, summary, and at-mode apply only to manageable modems only.
The number of events that you can record and view with the show modem log command is defined using the modem buffer-size command. The events stored in the buffer wrap around the event queue. You cannot clear the modem event queue.
Use the clear modem counters command to reset modem counters and clear the modem summary report of modem statistics.
The following display shows output information for the show modem command for a V.34 modem port module:
AS5200# show modem
Inc calls Out calls Busied Failed No Succ
Mdm Usage Succ Fail Succ Fail Out Dial Answer Pct.
1/0 0% 0 0 0 0 0 0 0 0%
1/1 0% 0 0 0 0 0 0 0 0%
1/2 0% 0 0 0 0 0 0 0 0%
1/3 0% 0 0 0 0 0 0 0 0%
1/4 0% 0 0 0 0 0 0 0 0%
1/5 0% 0 0 0 0 0 0 0 0%
1/6 0% 0 0 0 0 0 0 0 0%
1/7 0% 0 0 0 0 0 0 0 0%
1/8 0% 0 0 0 0 0 0 0 0%
1/9 0% 0 0 0 0 0 0 0 0%
1/10 0% 0 0 0 0 0 0 0 0%
1/11 0% 0 0 0 0 0 0 0 0%
1/12 0% 0 0 0 0 0 0 0 0%
1/13 0% 0 0 0 0 0 0 0 0%
1/14 0% 0 0 0 0 0 0 0 0%
1/15 0% 0 0 0 0 0 0 0 0%
1/16 0% 0 0 0 0 0 0 0 0%
1/17 0% 0 0 0 0 0 0 0 0%
1/18 0% 0 0 0 0 0 0 0 0%
1/19 0% 0 0 0 0 0 0 0 0%
1/20 0% 0 0 0 0 0 0 0 0%
1/21 0% 0 0 0 0 0 0 0 0%
1/22 0% 0 0 0 0 0 0 0 0%
1/23 0% 0 0 0 0 0 0 0 0%
The following display shows output information for the show modem command for V.110 modem port modules:
Router# show modem
Inc calls Out calls Busied Failed No Succ
Mdm Usage Succ Fail Succ Fail Out Dial Answer Pct.
0/0 0% - - - - 0 0 0 -
0/1 0% - - - - 0 0 0 -
0/2 0% - - - - 0 0 0 -
0/3 0% - - - - 0 0 0 -
0/4 0% - - - - 0 0 0 -
0/5 0% - - - - 0 0 0 -
0/6 0% - - - - 0 0 0 -
0/7 0% - - - - 0 0 0 -
0/8 0% - - - - 0 0 0 -
0/9 0% - - - - 0 0 0 -
0/10 0% - - - - 0 0 0 -
0/11 0% - - - - 0 0 0 -
1/0 0% - - - - 0 0 0 -
1/1 0% - - - - 0 0 0 -
1/2 0% - - - - 0 0 0 -
1/3 0% - - - - 0 0 0 -
1/4 0% - - - - 0 0 0 -
1/5 0% - - - - 0 0 0 -
1/6 0% - - - - 0 0 0 -
1/7 0% - - - - 0 0 0 -
1/8 0% - - - - 0 0 0 -
1/9 0% - - - - 0 0 0 -
1/10 0% - - - - 0 0 0 -
1/11 0% - - - - 0 0 0 -
Table 29 describes the fields in the previous display.
| Field | Description |
|---|---|
| Mdm | Slot and modem port number. Also, the following modem states can appear to the left of a slot/modem port number:
b--Modem was removed from service with the modem shutdown command or the modem busyout command. B--Modem is Bad*, Bad, or the downloaded firmware has failed. d--The RAM based DSP code, which supports K56flex, is not configured. The modem will revert to transmitting at 33.6 kbps. D--Modem is currently downloading firmware. R--Modem is held and isolated in a suspended state by the modem hold-reset command. T--Modem is conducting a back-to-back test with another modem. *--Modem is connected or dialing. |
| Usage | Percentage of the total system uptime that all modems are in use. |
| Inc calls | Number of incoming calls that successfully and unsuccessfully connected to an available Cisco AS5200 integrated modem. |
| Out calls | Number of outgoing calls that successfully and unsuccessfully dialed out from an available Cisco AS5200 integrated modem. |
| Busied Out | Number of modems that have been manually removed from service. |
| Failed Dial | Number of modems that attempted to dial into the network but failed to make a connection. |
| No Answer | Number of modems that detected an incoming ring but failed to answer the call. |
| Succ Pct. | Successful connection percentage of total available modems. |
The following example shows the statistics and current configurations for the manageable modem 2/10, which exists on a V.34 modem board in a Cisco AS5200. A dash (-) indicates a field that is not available on nonmanageable modems. An x indicates a field that is available and active on manageable modems. See Table 30 for a description of the fields displayed by the show modem command.
Router> show modem 2/10
Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR
2/10 V34 Idle 33600/33600 1 00:00:00 x x x x
Modem 2/10, Microcom MNP10 V34 Modem (Select), Async35, TTY35
Firmware (Boot) Rev: 2.1(9) (1.0(5))
Modem config: Incoming and Outgoing
Protocol: reliable/MNP, Compression: V42bis
Management port config: Status polling and AT session
Management port status: Status polling and AT session
TX signals: 0 dBm, RX signals: 0 dBm
Last clearing of "show modem" counters never
0 incoming completes, 0 incoming failures
0 outgoing completes, 0 outgoing failures
0 failed dial attempts, 0 ring no answers, 0 busied outs
0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
0 no carriers, 0 link failures, 0 resets 0 recover oob
0 protocol timeouts, 0 protocol errors, 0 lost events
Connection Speeds 75 300 600 1200 2400 4800
# of connections 0 0 0 0 0 0
Connection Speeds 7200 9600 12000 14400 16800 19200
# of connections 0 0 0 0 0 0
Connection Speeds 21600 24000 26400 28800 31200 33600
# of connections 0 0 0 0 0 1
The following example displays example output for a nonmanageable V.34 modem module. Notice that unavailable fields are marked with dashes (-):
AS5200# show modem 1/1
Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR
1/1 - Idle 19200/19200 0 00:01:05 - - - - - - -
Modem 1/1, AS5200 Non-Manageable Modem
Firmware (Boot) Rev: Unknown
Modem config: Unknown
Management config: Not Manageable Modem
Last clearing of "show modem" counters never
- incoming completes, - incoming failures
- outgoing completes, - outgoing failures,
0 failed dial attempts, 0 ring no answers, 0 busied outs
0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
- no carriers, - link failures, 0 resets
- protocol timeouts, - protocol errors, - lost events
Connection Speeds 75 300 600 1200 2400 4800
# of connections 0 0 0 0 0 0
Connection Speeds 7200 9600 12000 14400 16800 19200
# of connections 0 0 0 0 0 0
Connection Speeds 21600 24000 26400 28800 31200 33600
# of connections 0 0 0 0 0 0
The type of display output generated from the show modem slot/modem-port command depends on the version of Cisco IOS software running on the router or access server. For example, the following shows example output for a 56K modem card, that carries digital modems that transmit at 56 kbps. (In truth, 56K modems do not modulate or demodulate data. A pure digital-to-digital connection is made.) See Table 29 for a description of the new fields displayed for this modem card.
Router# show modem 0/0
Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR
0/0 Idle 0/0 0 00:00:00 x x x x
Modem 0/0, Microcom MNP10 K56 Modem (Select), TTY1
Firmware (Boot) Rev: 3.1(16) (3.0(4))
DSP Controller (SPX) Rev: 1.1(0) (1.1(0))
Modem config: Incoming and Outgoing
Protocol: Normal, Compression: None
Management port config: Status polling and AT session
Management port status: Status polling and AT session
TX signals: 0 dBm, RX signals: 0 dBm
Last clearing of "show modem" counters never
0 incoming completes, 0 incoming failures
0 outgoing completes, 0 outgoing failures
0 failed dial attempts, 0 ring no answers, 0 busied outs
0 no dial tones, 0 dial timeouts, 0 watchdog timeouts
0 no carriers, 0 link failures, 1 resets 0 recover oob
0 protocol timeouts, 0 protocol errors, 0 lost events
Transmit Speed Counters:
Connection Speeds 75 300 600 1200 2400 4800
# of connections 0 0 0 0 0 0
Connection Speeds 7200 9600 12000 14400 16800 19200
# of connections 0 0 0 0 0 0
Connection Speeds 21600 24000 26400 28800 31200 32000
# of connections 0 0 0 0 0 0
Connection Speeds 33600 34000 36000 38000 40000 42000
# of connections 0 0 0 0 0 0
Connection Speeds 44000 46000 48000 50000 52000 54000
# of connections 0 0 0 0 0 0
Connection Speeds 56000
# of connections 0
Receive Speed Counters:
Connection Speeds 75 300 600 1200 2400 4800
# of connections 0 0 0 0 0 0
Connection Speeds 7200 9600 12000 14400 16800 19200
# of connections 0 0 0 0 0 0
Connection Speeds 21600 24000 26400 28800 31200 32000
# of connections 0 0 0 0 0 0
Connection Speeds 33600 34000 36000 38000 40000 42000
# of connections 0 0 0 0 0 0
Connection Speeds 44000 46000 48000 50000 52000 54000
# of connections 0 0 0 0 0 0
Connection Speeds 56000
# of connections 0
The following display shows output information for the show modem slot/modem-port command for V.110 modem port modules:
Router# show modem 0/1
Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR
0/1 Idle -/- 1 00:00:00 - - - - - - -
Modem 0/1, V.110 Terminal Adaptor (Unmanaged), Async2, TTY2
Firmware (Boot) Rev: Unmanaged (Unmanaged)
Modem config: Incoming and Outgoing
Management config: Unmanaged
Last clearing of "show modem" counters never
- incoming completes, - incoming failures
- outgoing completes, - outgoing failures
0 failed dial attempts, 0 ring no answers, 0 busied outs
- no dial tones, - dial timeouts, 0 watchdog timeouts
- no carriers, - link failures, 0 resets, - recover oob
- protocol timeouts, - protocol errors, - lost events
Connection Speeds 75 300 600 1200 2400 4800
# of connections - - - - - -
Connection Speeds 7200 9600 12000 14400 16800 19200
# of connections - - - - - -
Connection Speeds 21600 24000 26400 28800 31200 32000
# of connections - - - - - -
Connection Speeds 33600 34000 36000 38000 40000 42000
# of connections - - - - - -
Connection Speeds 44000 46000 48000 50000 52000 54000
# of connections - - - - - -
Connection Speeds 56000
# of connections -
Table 30 describes the fields in the previous displays, which were created using the show modem slot/modem-port command. This table applies to all modem module types.
| Field | Description |
|---|---|
| Mdm | Slot and modem number. |
| Typ | Modulation type, which can be any of the following values:
|
|
Status | Current status of the modem. Possible values include:
|
|
Tx/Rx | Transmission and receiving speed for the most recently connected call. |
| G | Modem group number assigned to the modem. The group number 0 means the modem is not part of any group. |
| Duration | Time duration of the current call or the last call. |
| Modem functions | The following modem functions are displayed on manageable modems. A field that is available and turned on is marked with an x. An unavailable field is marked with a dash (-).
TX--Transmit Data. The DTE transmits data to the DCE. RX--Receive Data. The DCE receives data from the DTE. RTS--Request To Send. The DTE signals to the DCE that the DTE accepts data into its buffers. CTS--Clear To Send. The DCE signals to the DTE that the DCE accepts data into its buffers. DSR--Data Set Ready. The modem is ready to start communication. DCD--Data Carrier Detect. The DCE indicates to the DTE that a call is present and established with a remote modem. Dropping the DCD function terminates the session. DTR--Data Terminal Ready. The DTE indicates to the DCE that it accepts calls. |
| Firmware | Installed modem firmware. |
| Modem config | Current modem configuration, which includes the fields Incoming, Outgoing, Incoming and Outgoing, and Unknown. |
| Protocol | Protocol the modem is running such as Normal, Direct, reliable/MNP4, and reliable/LAPM (Link Access Procedure for Modems). |
| Compression | Compression algorithm running on the modem, such as None, V42bis, and MNP5. |
| Management config | Indicates if the modem is configured for out-of-band port polling. |
| TX signals | Transmit signal levels. For modulations that do not support signal to noise calculations, the ratio is 0. |
| RX signals | Transmit signal levels. |
| Last clearing of "show modem" counters | Last time the modem's counters were cleared using the clear modem counters command. A summary of modem events also appears.
|
|
Connection Speeds | A complete summary of possible connection speeds and the actual number of connections that occurred at those speeds. Depending on which modem port module and version of software you are running, possible connection speeds range from 75 to 56,000 bps. The number of successful connections are displayed directly beneath the connection speed identifier. For example, the following output shows that three connections were made at 56 kbps.
Connection Speeds 56000 |
The following example displays the call switching module information for modem 1/2:
AS5200# show modem csm 1/2
MODEM_INFO: slot 1, port 2, unit 130, modem_mask=0x0004, modem_port_offset=0
tty_hwidb=0x00000000, modem_tty=0x004370A8, mgmt_tty=0x004370A8, modem_pool=0x0041D99C
csm_status(0): CSM_STATUS_UNLOCKED
csm_state(0x00000000)=CSM_OC_STATE, csm_event_proc=0x0005B448
invalid_event_count=0, wdt_timeout_count=0
wdt_timestamp_started is not activated
wait_for_dialing:False, wait_for_bchan:False
pri_chnl=TDM_ISDN_STREAM(s0, c0), modem_chnl=TDM_ISDN_STREAM(s0, c0)
dchan_idb_start_index=0, dchan_idb_index=0, call_id=0x0000, bchan_num=0
csm_event=CSM_EVENT_NONE, cause=0x0000, phone_num=
ring_indicator=0, oh_state=0, oh_int_enable=0, modem_reset=0
ring_no_answer=0, ic_failure=0, ic_complete=0
dial_failure=0, oc_failure=0, oc_complete=0
oc_busy=0, oc_no_dial_tone=0, oc_dial_timeout=0
remote_link_disc=0, busyout=0, modem_reset=0
call_duration_started=00:00:00, call_duration_ended=00:00:00, total_call_duration=00:00:00
The calling party phone number = 4082968388
The called party phone number = 4085267406
Table 31 describes the most useful fields in the previous display.
| Field | Description |
|---|---|
| MODEM_INFO | Displays internal data structure information. |
| csm_status | Displays the status of the call switching module. Possible displays include unlocked, active call, busyout req, shutdown, bad modem, modem hold, back-to-back, file downloading, and reset. |
| csm_state | Displays the current state of the call switching module. Possible states include idle and connected. Incoming calls are marked IC and outgoing calls are marked OC. |
| Modem counters | Counters for different modem events. |
| The calling party phone number The called party phone number | Phone numbers for the dialing integrated modem and the remote modem. |
The following example shows the event log status for a manageable modem and identifies the time elapsed since each modem event was performed (for example, 01:02:41 means the modem event occurred 1 hour, 2 minutes, and 41 seconds ago):
AS5200# show modem log 0/0
Modem 0/0 Events Log:
01:03:03: Startup Response: Microcom MNP10 K56 Modem (Select)
Modem (boot) firmware = 3.1(16) (3.0(4))
DSP Controller (SPX) rev = 204.173(0) (143.191(0))
01:03:03: Control Reply: 0xFF1F
01:03:03: RS232 event: RTS noDTR* CTS* DSR* noDCD* noRI noTST
01:03:03: RS232 event: RTS noDTR CTS DSR noDCD noRI noTST
01:03:03: Modem State event: Idle
01:03:03: End connection event: Retransmits for MNP block (TX/RX) = 0/0
Duration = 0:00:00, Number of TX/RX char = 0/0
Local Disc Reason = Lost Carrier
Remote Disc Reason = Unknown
01:03:04: Phone number event:
01:02:51: DTR event: DTR On
01:02:51: RS232 event: RTS DTR* CTS DSR noDCD noRI noTST
00:39:52: Startup Response: Microcom MNP10 K56 Modem (Select)
Modem (boot) firmware = 3.1(16) (3.0(4))
DSP Controller (SPX) rev = 1.1(0) (1.1(0))
00:39:52: Control Reply: 0xFF1F
00:39:52: RS232 event: RTS noDTR* CTS* DSR* noDCD* noRI noTST
00:39:52: RS232 event: RTS noDTR CTS DSR noDCD noRI noTST
00:39:53: Modem State event: Idle
00:39:53: End connection event: Retransmits for MNP block (TX/RX) = 0/0
Duration = 0:00:00, Number of TX/RX char = 0/0
Local Disc Reason = Lost Carrier
Remote Disc Reason = Unknown
00:39:53: Phone number event:
00:39:32: DTR event: DTR On
00:39:32: RS232 event: RTS DTR* CTS DSR noDCD noRI noTST
Table 32 describes the most useful fields in the previous display.
| Field | Description |
|---|---|
| Modem <slot/port> Events Log: | The modem for which log events are currently displayed. |
| Startup Response: | List of information describing the modem type, modem firmware, and DSP controller version (for 56K modems only). |
| Control Reply | Indicates the events the modem will be monitoring. |
| RS232 event | Detected modem signaling. |
| Modem State event | Current state of the modem, which can be any of the following:
|
|
End connection event | Descriptions or reasons why a connection was terminated:
|
|
Phone number event | Descriptive information about the last dialed or current phone number. |
The following example shows the cumulative system statistics for all manageable modems on the Cisco AS5200:
AS5200# show modem summary
Incoming calls Outgoing calls Busied Failed No Succ
Usage Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
5% 2 0 12 0 0 0 0 0 0 100%
Table 33 describes the fields in the previous display.
| Fields | Descriptions |
|---|---|
| Incoming and Outgoing calls | Calls dialing into and out of the modem.
|
|
Busied Out | Total number of times the modems were taken out of service with the modem busy command or the modem shutdown command. |
| Failed Dial | Total number of attempts the modems did not hang up or there was no dial tone. |
| No Ans | Total number of times call ringing was detected, but the calls were not answered by a modem. |
| Succ Pct. | Successful connection percentage of total available modems. |
The following example shows the sample display for modem group 1, which is composed of modem 1/0 through modem 1/23:
AS5200# show modem group 1
Incoming calls Outgoing calls Busied Failed No Succ
Grp Usage Succ Fail Avail Succ Fail Avail Out Dial Ans Pct.
1 0% 0 0 24 0 0 24 0 0 0 0%
Modem Group 1: 1/0, 1/1, 1/2, 1/3, 1/4, 1/5, 1/6, 1/7, 1/8, 1/9, 1/10, 1/11, 1/12, 1/13, 1/14, 1/15, 1/16, 1/17, 1/18, 1/19, 1/20, 1/21, 1/22, 1/23
The following example displays information for modem firmware, which includes modem firmware version, boot code version, controller and DSP code version (56K modem modules only), modem board hardware version, and carrier card information. This particular example displays information for 56K modem cards installed on a Cisco AS5200.
If the version number is displayed as 0.0.0, make sure that out-of-band port status polling is functioning.
Router# show modem version
Modem module Firmware Boot DSP
Mdm Number Rev Rev Rev
0/0 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/1 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/2 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/3 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/4 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/5 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/6 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/7 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/8 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/9 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/10 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/11 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
0/12 1 2.2(8) 1.0(5)
0/13 1 2.2(8) 1.0(5)
0/14 1 2.2(8) 1.0(5)
0/15 1 2.2(8) 1.0(5)
0/16 1 2.2(8) 1.0(5)
0/17 1 2.2(8) 1.0(5)
0/18 1 2.2(8) 1.0(5)
0/19 1 2.2(8) 1.0(5)
0/20 1 2.2(8) 1.0(5)
0/21 1 2.2(8) 1.0(5)
0/22 1 2.2(8) 1.0(5)
0/23 1 2.2(8) 1.0(5)
2/0 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/1 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/2 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/3 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/4 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/5 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/6 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/7 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/8 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/9 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/10 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/11 0 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/12 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/13 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/14 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/15 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/16 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/17 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/18 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/19 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/20 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/21 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/22 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
2/23 1 3.1(21) 3.0(4) 1.1(0)/1.1(0)
Modem board HW version info:
Slot 0:
Carrier card:
hw version= 8, number_of_ports= 24, max_modules= 2, max_oob_ports= 2
Modem Module 0:
number_of_modems= 12, option_bits= 1,
rev_num= 02.00, vendor_model_number= 02,
vendor_banner= Microcom MNP10 K56 Modem
Modem Module 1:
number_of_modems= 12, option_bits= 1,
rev_num= 03.00, vendor_model_number= 01,
vendor_banner= Microcom MNP10 V34 Modem
Slot 2:
Carrier card:
hw version= 7, number_of_ports= 24, max_modules= 2, max_oob_ports= 2
Modem Module 0:
number_of_modems= 12, option_bits= 1,
rev_num= 02.00, vendor_model_number= 02,
vendor_banner= Microcom MNP10 K56 Modem
Modem Module 1:
number_of_modems= 12, option_bits= 1,
rev_num= 02.00, vendor_model_number= 02,
vendor_banner= Microcom MNP10 K56 Modem
The next example displays modem version information for V.110 modem port modules for unmanaged modems:
Router# show modem version
Modem module Firmware Boot
Mdm Number Rev Rev
0/0 0 Unmanaged Unmanaged
0/1 0 Unmanaged Unmanaged
0/2 0 Unmanaged Unmanaged
0/3 0 Unmanaged Unmanaged
0/4 0 Unmanaged Unmanaged
0/5 0 Unmanaged Unmanaged
0/6 0 Unmanaged Unmanaged
0/7 0 Unmanaged Unmanaged
0/8 0 Unmanaged Unmanaged
0/9 0 Unmanaged Unmanaged
0/10 0 Unmanaged Unmanaged
0/11 0 Unmanaged Unmanaged
1/0 0 Unmanaged Unmanaged
1/1 0 Unmanaged Unmanaged
1/2 0 Unmanaged Unmanaged
1/3 0 Unmanaged Unmanaged
1/4 0 Unmanaged Unmanaged
1/5 0 Unmanaged Unmanaged
1/6 0 Unmanaged Unmanaged
1/7 0 Unmanaged Unmanaged
1/8 0 Unmanaged Unmanaged
1/9 0 Unmanaged Unmanaged
1/10 0 Unmanaged Unmanaged
1/11 0 Unmanaged Unmanaged
1/12 1 Unmanaged Unmanaged
1/13 1 Unmanaged Unmanaged
1/14 1 Unmanaged Unmanaged
1/15 1 Unmanaged Unmanaged
1/16 1 Unmanaged Unmanaged
1/17 1 Unmanaged Unmanaged
1/18 1 Unmanaged Unmanaged
1/19 1 Unmanaged Unmanaged
1/20 1 Unmanaged Unmanaged
1/21 1 Unmanaged Unmanaged
1/22 1 Unmanaged Unmanaged
1/23 1 Unmanaged Unmanaged
2/0 0 Unmanaged Unmanaged
2/1 0 Unmanaged Unmanaged
2/2 0 Unmanaged Unmanaged
2/3 0 Unmanaged Unmanaged
2/4 0 Unmanaged Unmanaged
2/5 0 Unmanaged Unmanaged
2/6 0 Unmanaged Unmanaged
2/7 0 Unmanaged Unmanaged
2/8 0 Unmanaged Unmanaged
2/9 0 Unmanaged Unmanaged
2/10 0 Unmanaged Unmanaged
2/11 0 Unmanaged Unmanaged
2/12 1 Unmanaged Unmanaged
2/13 1 Unmanaged Unmanaged
2/14 1 Unmanaged Unmanaged
2/15 1 Unmanaged Unmanaged
2/16 1 Unmanaged Unmanaged
2/17 1 Unmanaged Unmanaged
2/18 1 Unmanaged Unmanaged
2/19 1 Unmanaged Unmanaged
2/20 1 Unmanaged Unmanaged
2/21 1 Unmanaged Unmanaged
2/22 1 Unmanaged Unmanaged
2/23 1 Unmanaged Unmanaged
Modem board HW version info:
Slot 0:
Carrier card:
hw version= 3, number_of_ports= 12, max_modules= 1, max_oob_ports= 1
Modem Module 0:
number_of_modems= 12, option_bits= 1,
rev_num= 03.01, vendor_model_number= 01,
vendor_banner= V.110 Terminal Adaptor
Slot 1:
Carrier card:
hw version= 8, number_of_ports= 24, max_modules= 2, max_oob_ports= 2
Modem Module 0:
number_of_modems= 12, option_bits= 1,
rev_num= 03.01, vendor_model_number= 01,
vendor_banner= V.110 Terminal Adaptor
Modem Module 1:
number_of_modems= 12, option_bits= 1,
rev_num= 03.01, vendor_model_number= 01,
vendor_banner= V.110 Terminal Adaptor
Slot 2:
Carrier card:
hw version= 8, number_of_ports= 24, max_modules= 2, max_oob_ports= 2
Modem Module 0:
number_of_modems= 12, option_bits= 1,
rev_num= 03.00, vendor_model_number= 01,
vendor_banner= V.110 Terminal Adaptor
Modem Module 1:
number_of_modems= 12, option_bits= 1,
rev_num= 03.00, vendor_model_number= 01,
vendor_banner= V.110 Terminal Adaptor
Table 34 describes the fields shown in the previous displays of the show modem version command.
| Fields | Descriptions |
|---|---|
| Mdm | Slot and port number for the specified modem. |
| Modem card number | card number associated with the carrier card. |
| Firmware Rev | Modem firmware version, or one of the following:
|
|
Boot Rev | Modem boot version, or one of the following:
|
|
DSP Rev | Controller and DSP version, which is displayed for the 56K modems only. The first column of numbers correspond to the controller version. The second column of numbers, which begin with a forward slash (/), correspond to the DSP version. |
| Modem board HW version info: | Modem hardware board information. |
| Slot | Slot number used for the carrier card. |
| Carrier card | Modem carrier card. |
| Hw version | Modem carrier card hardware version. |
| number_of_ports | Maximum number of modem ports that can be installed in the carrier card. |
| max_modules | Maximum number of modem cards that can be installed in a carrier card. |
| max_oob_ports | Maximum out-of-band ports used in the carrier card. |
| Modem Module | Modem card. |
| number_of_modems | Number of modems installed in the modem card. |
| option_bits | Signal level of the modem A-law and the U-law. |
| rev_num | Modem card version number. |
| vendor_model_number | Vendor modem model number. |
| vendor_banner | Type of banner displayed by the modem vendor. |
The following example shows all the directly connected sessions currently using the internal out-of-band ports on the integrated manageable modems:
AS5200# show modem at-mode
Active AT-MODE management sessions:
Modem User's Terminal
1/1 0 cty 0
The following example shows all the directly connected sessions currently using the internal out-of-band ports on the integrated manageable modems:
AS5200# show modem at-mode
Active AT-MODE management sessions:
Modem User's Terminal
For instructions on how to install a 56K modem card in a Cisco AS5200, refer to the Installing 56K Modem Cards in Cisco AS5200 Universal Access Servers publication.
|
|