|
|
This chapter describes the commands that manage modems existing inside access servers or routers. Cisco Systems does not consider external modems, which physically connect to an access server or router through an asynchronous cable, to be part of its modem management paradigm.
For configuration information and examples, refer to the "Managing Modems" chapter in the Dial Solutions Configuration Guide.
To assign a called party number to a pool of modems, use the called-number modem pool configuration command. Use the no form of this command to remove a number from a modem pool.
called-number number [max-conn number]
number | Called number for a modem pool. |
max-conn number | (Optional) Maximum number of simultaneous connections allowed for the called party number. |
Disabled
Modem pool configuration
This command first appeared in Cisco IOS Release 11.2 P.
A called party number is a telephone number that is used to reach a remote destination. For example, a mobile laptop dials a called party number to reach an ISP's POP. Some ISPs set up several called party numbers to enable remote clients to dial in, but to the end user, it appears and functions as one unified service.
Cisco's implementation of a called party number is based on the dialed number identification service (DNIS). You can configure multiple DNIS numbers in a single modem pool. However, the same DNIS number cannot be used in multiple modem pools. Each modem pool must be assigned different DNIS numbers.
Use the max-conn option to provide overflow protection, which specifies a maximum number of simultaneous connections that a called party number can consume. For example, if you create one modem pool to serve two or more services or customers, this option guarantees how many modems each service or customer can have access to at any given time.
The Cisco IOS software also includes a feature that simplifies the called number configuration. By using an x variable as the last digit in a called telephone number (for example, issuing the called-number 408555121x command), clients dialing different called numbers such as 4085551214 or 4085551215 will automatically be sent to the same modem pool. The x variable is a floating place holder for digits 1 through 9.
In the following example, the modem pool called v90service is virtually partitioned between two customers using different DNIS numbers. The pool-range command assigns modems 1 to 110 to the shared modem pool. The called-number 5551212 max-conn 55 command assigns the DNIS number 5551212 to the v90service modem pool. The total number of simultaneous connections is limited to 55. The called-number 4441212 max-conn 55 command assigns the DNIS number 4441212, which is for a different customer, to the same v90service modem pool. The total number of simultaneous connections is also set to 55.
as5300# configure terminal Enter configuration commands, one per line. End with CNTL/Z. as5300(config)# modem-pool v90service as5300(config-modem-pool)# pool-range 1-110 as5300(config-modem-pool)# called-number 5551212 max-conn 55 as5300(config-modem-pool)# called-number 4441212 max-conn 55 as5300(config-modem-pool)# exit as5300(config)#
The following configuration rejects the pool-range 30 command because modem TTY line 30 is already a member of the modem pool v90service, which was configured in the previous example. Each modem in the access server is automatically assigned to a unique TTY line. TTY line numbers are assigned according to your shelf, slot, or port hardware configuration.
as5300(config)# modem-pool v34service as5300(config-modem-pool)# pool-range 30 % TTY 30 is already in another pool.
You can use the master indexes or search online to find documentation of related commands.
clear modempool-counters
modem-pool
pool-range
show modem-pool
To clear the counters of a specified asynchronous interface or specified asynchronous interface group, as displayed by the show interface async command, enter the clear counters (async) interface configuration command.
clear counters {async async-interface-number | group-async group-async-interface-number}
async | Clears the counters in a specified asynchronous interface. |
async-interface-number | Required async interface number of the asynchronous interface that has been previously created with this number specification. The range is from 1 through 49. |
group-async | Clears the counters in a specified asynchronous interface group. |
group-async-interface-number | Required group-async interface number that has been previously created with this number specification. The range is from 0 through 49. |
Disabled
EXEC
This command first appeared in Cisco IOS Release 12.0 T.
Before using this command, use the show interface async command to display the asynchronous related counters on the specified asynchronous interface.
The following example uses the show interface async command to display the asynchronous related counters on the asynchronous interface named 1. The example then uses the clear counters group-async command to clear the counters. After the counters are cleared, the configuration file for the interface is displayed.
as5300# show interface async 1
Async1 is down, line protocol is down
modem(slot/port)=1/0, state=IDLE
dsx1(slot/unit/channel)=NONE, status=VDEV_STATUS_UNLOCKED
Hardware is Async Serial
Interface is unnumbered. Using address of Ethernet0 (1.18.31.9)
MTU 1500 bytes, BW 115 Kbit, DLY 100000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive not set
DTR is pulsed for 5 seconds on reset
LCP Closed
Closed: IPCP, CDPCP
Last input never, output never, output hang never
Last clearing of "show interface" counters 00:03:46
Input queue: 0/10/0 (size/max/drops); Total output drops: 0/////
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/0/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
5300#
5300# clear counters group-async 1
Clear "show interface" counters on this interface [confirm]
5300#
*Oct 17 00:42:27.083: %CLEAR-5-COUNTERS: Clear counter on interface Group-Asynce
You can use the master indexes or search online to find documentation of related commands.
show interface async
clear modem counters
To clear line counters, use the clear counters line EXEC command.
clear counters line {type | number}
type | Type of line you want to clear. Replace the type argument with one of the following: aux, console, tty, or vty. |
number | Specifies the first line number to clear, which can be between 0 and 54. |
Disabled
EXEC
This command first appeared in Release 11.2 P.
This command clears the line counters shown by the show line command.
The following example shows the available options under the clear counters line command. When you issue this command, the counters (for example, Uses and Noise) displayed by the show line command are cleared.
router# clear counters line ? <0-54> First Line number aux Auxiliary line console Primary terminal line tty Terminal controller vty Virtual terminal router# exit router> show line Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns * 0 CTY - - - - - 0 4 0/0 A 1 TTY 115200/115200 - inout - - - 1 0 0/0 A 2 TTY 115200/115200 - inout - - - 1 0 0/0 A 3 TTY 115200/115200 - inout - - - 1 0 0/0 * 4 TTY 115200/115200 - inout - - - 0 0 0/0 * 5 TTY 115200/115200 - inout - - - 0 0 0/0 * 6 TTY 115200/115200 - inout - - - 0 0 0/0 * 7 TTY 115200/115200 - inout - - - 0 0 0/0 * 8 TTY 115200/115200 - inout - - - 0 0 0/0 * 9 TTY 115200/115200 - inout - - - 0 0 0/0 * 10 TTY 115200/115200 - inout - - - 0 0 0/0 * 11 TTY 115200/115200 - inout - - - 0 0 0/0 * 12 TTY 115200/115200 - inout - - - 0 0 0/0 * 13 TTY 115200/115200 - inout - - - 0 0 0/0 * 14 TTY 115200/115200 - inout - - - 0 0 0/0 * 15 TTY 115200/115200 - inout - - - 0 0 0/0 A 16 TTY 115200/115200 - inout - - - 1 0 0/0 A 17 TTY 115200/115200 - inout - - - 1 0 0/0 A 18 TTY 115200/115200 - inout - - - 1 0 0/0 A 19 TTY 115200/115200 - inout - - - 1 0 0/0 A 20 TTY 115200/115200 - inout - - - 1 0 0/0 A 21 TTY 115200/115200 - inout - - - 1 0 0/0
You can use the master indexes or search online to find documentation of related commands.
show line
To reset the hardware for one or more manageable modems on an access server or router, use the clear modem EXEC command.
clear modem {slot/port-number | all | group group-number | at-mode slot/port-number |
slot/port-number | Clear the modem at the specified slot and modem port number. Remember to include the forward slash (/) when entering this variable. For example: 1/1. This variable can also be used with the subcommands clear modem at-mode and clear modem counters. |
all | Clear all modems. This command disconnects any active calls. |
group group-number | Clears the modem hardware for a group of modems. The modem group-number is the number of the group you have previously created. |
at-mode slot/port-number | Tears down an AT directly connected session. The variable, slot/port-number, is required. This EXEC command clears an attention (AT) directly connected session to a manageable Microcom modem from a second Telnet session. |
test | Clears the log or test report that is displayed by the show modem test command. If you do not clear the test regularly, eventually the oldest test report will replace the current test report. |
Disabled
EXEC
This command first appeared in Cisco IOS Release 11.2.
The modem hardware is reset for modems that are idle or busied out for long periods of time.
An AT directly connected session is usually initiated and closed from the same Telnet session by using the modem at-mode command and Ctrl-C. However, you can clear an AT directly connected session that was mistakenly left open by enabling the clear modem at-mode command from a second Telnet session in to the access server.
The following example of the clear modem slot/port command resets the hardware for manageable modem 1/1:
as5300# clear modem 1/1
The following example of using the clear modem all command
as5300# clear modem all This command will disconnect any active calls. Clear (reset) all modems? [confirm] Clearing modems................................................ Done as5300#
The following examples of the clear modem group command clear the manageable modems in group 1:
clear modem group 1 clear modem group1
The following example executes the clear modem at-mode command from a Telnet session:
router# modem at-mode 1/1
The following example executes the clear modem at-mode command from a second Telnet session while the first Telnet session is connected to the modem:
router# clear modem at-mode 1/1 clear "modem at-mode" for modem 1/1 [confirm] router#
The following output is displayed in the first Telnet session after the modem is cleared by the second Telnet session:
Direct connect session cleared by vty0 (171.69.1.164)
You can use the master indexes or search online to find documentation or related commands.
clear modem counters
interface group-async
modem at-mode
To clear the statistical counters on one or more manageable modems installed in an access server, use the clear modem counters EXEC command.
clear modem counters [slot/port-number | group [group-number]]
slot/port-number | (Optional) Clear the modem at the specified slot and modem port number. Remember to include the forward slash (/) when entering this variable. For example: 1/1. This variable can also be used with the subcommands clear modem at-mode and clear modem counters. |
group [group-number] | (Optional) Clears the counter for one or all groups of modems. The subcommand, clear modem counters group, without the group-number clears counters in all modem groups. The optional modem group-number is the number of the group you have previously created. The Group number range is 1 through1002. |
Disabled
EXEC
This command first appeared in Cisco IOS Release 11.2.
Entering the clear modem counters command without specifying an optional keyword or argument resets the modem statistics on each modem and the summary statistics displayed in the show modem summary command.
The following example of the clear modem counters slot/port command clears the statistical counters on manageable modem 1/1:
clear modem counters 1/1
The following example of the clear modem counters group command clears the statistical counters on all manageable modem groups:
5300# clear modem counters group Clear "show modem" counters for all modem groups [confirm] 5300# *Oct 17 20:20:24.974: %CLEAR-5-COUNTERS: Clear counter on modems in all groups e 5300#
You can use the master indexes or search online to find documentation or related commands.
show modem summary
clear counters async
clear counters group-async
To clear the active or running counters associated with one or more modem pools, use the clear modempool-counters EXEC command. This command is used only with MICA digital modems.
clear modempool-counters [name]
name | (Optional) Modem pool name. If you do not include this option, all counters for all modem pools will be cleared. |
Disabled
EXEC
This command first appeared in Release 11.2 P.
The clear modempool-counters command clears the counters that are displayed in the show modem-pool command.
This example shows three modem pools set up on the access server: System-def-Mpool, v90service, and v34service. The clear modempool-counters v90service command clears the running counters for the v90services modem pool.
as5300# show modem-pool modem-pool: System-def-Mpool modems in pool: 20 active conn: 15 0 no free modems in pool modem-pool: v90service modems in pool: 50 active conn: 43 3 no free modems in pool called_party_number: 4441000 max conn allowed: 50, active conn: 43 3 max-conn exceeded, 3 no free modems in pool modem-pool: v34service modems in pool: 50 active conn: 30 1 no free modems in pool called_party_number: 4443000 max conn allowed: 50, active conn: 30 0 max-conn exceeded, 0 no free modems in pool as5300# clear modempool-counters v90service as5300# show modem-pool modem-pool: System-def-Mpool modems in pool: 20 active conn: 15 0 no free modems in pool modem-pool: v90service modems in pool: 50 active conn: 0 0 no free modems in pool called_party_number: 4441000 max conn allowed: 50, active conn: 0 0 max-conn exceeded, 0 no free modems in pool modem-pool: v34service modems in pool: 50 active conn: 30 1 no free modems in pool called_party_number: 4443000 max conn allowed: 50, active conn: 30 0 max-conn exceeded, 0 no free modems in pool
You can use the master indexes or search online to find documentation of related commands.
called-number
modem-pool
pool-range
show modem-pool
To copy modem firmware to integrated modems in an access server, use the copy modem EXEC command.
copy {flash | tftp | rcp} modem
flash | Copies firmware from Flash memory to the modems. |
tftp | Copies firmware from a local TFTP server on your network to the modems. |
rcp | Copies firmware from a local rcp server on your network to the modems. |
Disabled
EXEC
This command first appeared in Cisco IOS Release 11.2. For more information on this command, see the online configuration guides and command references for configuration fundamentals.
After you enable this command, you are asked to provide the download destination (a slot/port or all), the remote host name, and the path leading to the source modem firmware.
If a modem that you want to upgrade is busy with a call when the copy modem command is enabled, the upgrade for that modem yields until the active call is dropped. All other idle modems in the upgrade range proceed with the downloading operation.
The following example copies the modem firmware file called modem_upgrade from the TFTP server called Modem_Server to modem 2/0, which is installed in a Cisco AS5200 access server:
router# copy tftp modem Modem Numbers (<slot>/<port>[-<slot>/<port>] | group <number> | all)? 2/0 Address or name of remote host [UNKNOWN]? Modem_Server Source file name? dirt/elem/modem_upgrade Accessing file 'dirt/elem/modem_upgradeonModem_Server... Loading dirt/elem/modem_upgrade.from 223.255.254.254 (via Ethernet0): ! [OK] Loading dirt/elem/modem_upgradefrom 223.255.254.254 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 237503/278528 bytes] router# %MODEM-5-DL_START: Modem (2/0) started firmware download %MODEM-5-DL_GOOD: Modem (2/0) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85
As shown in this example, you might want to upgrade and test one modem's firmware before upgrading the firmware of all the modems on the access server, as shown in the next example.
This example downloads the same modem firmware file from the TFTP server to all the modems in the Cisco AS5200 access server:
router# copy tftp modem Modem Numbers (<slot>/<port>[-<slot>/<port>] | group <number> | all)? all Address or name of remote host [UNKNOWN]? Modem_Server Source file name? dirt/elem/modem_upgrade Accessing file 'dirt/elem/modem_upgradeonModem_Server... Loading dirt/elem/modem_upgrade.from 223.255.254.254 (via Ethernet0): ! [OK] Loading dirt/elem/modem_upgradefrom 223.255.254.254 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 237503/278528 bytes] router# %MODEM-5-DL_START: Modem (2/0) started firmware download %MODEM-5-DL_START: Modem (2/1) started firmware download %MODEM-5-DL_START: Modem (2/2) started firmware download %MODEM-5-DL_START: Modem (2/3) started firmware download %MODEM-5-DL_START: Modem (2/4) started firmware download %MODEM-5-DL_START: Modem (2/5) started firmware download %MODEM-5-DL_START: Modem (2/6) started firmware download %MODEM-5-DL_START: Modem (2/7) started firmware download %MODEM-5-DL_START: Modem (2/8) started firmware download %MODEM-5-DL_START: Modem (2/9) started firmware download %MODEM-5-DL_START: Modem (2/10) started firmware download %MODEM-5-DL_START: Modem (2/11) started firmware download %MODEM-5-DL_START: Modem (2/12) started firmware download %MODEM-5-DL_START: Modem (2/13) started firmware download %MODEM-5-DL_START: Modem (2/14) started firmware download %MODEM-5-DL_START: Modem (2/15) started firmware download %MODEM-5-DL_START: Modem (2/16) started firmware download %MODEM-5-DL_START: Modem (2/17) started firmware download %MODEM-5-DL_START: Modem (2/18) started firmware download %MODEM-5-DL_START: Modem (2/19) started firmware download %MODEM-5-DL_START: Modem (2/20) started firmware download %MODEM-5-DL_START: Modem (2/21) started firmware download %MODEM-5-DL_START: Modem (2/22) started firmware download %MODEM-5-DL_START: Modem (2/23) started firmware download %MODEM-5-DL_GOOD: Modem (2/2) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/10) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/4) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/6) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/7) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/12) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/11) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/13) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/1) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/14) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/19) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/22) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/5) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/8) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/9) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/17) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/0) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/3) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/21) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/16) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/15) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/18) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/20) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85 %MODEM-5-DL_GOOD: Modem (2/23) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85
The following example copies the modem firmware file called STAR.M from Flash memory to the integrated modem 1/2:
router# copy flash modem
Modem Numbers (<slot>/<port> | group <number> | all)? 1/2
System flash directory:
File Length Name/status
1 3539820 as5200-i-m.allcookies
2 239203 STAR.M
3 23072 BOOT.105 [3802288 bytes used, 4586320 available, 8388608 total]
Source file name? STAR.M
router#
%MODEM-5-DL_START: Modem (1/2) started firmware download
%MODEM-5-DL_GOOD: Modem (1/2) completed firmware download: MNPClass10V.34/V.FCModemRev1.0.23/85.23/85
router#
You can use the master indexes or search online to find documentation of related commands.
copy
To set the amount of time that the Cisco IOS software waits for the Clear to Send (CTS) signal after raising the data terminal ready (DTR) signal in response to RING, use the modem answer-timeout line configuration command. Use the no form of this command to revert to the default value.
modem answer-timeout seconds
seconds | Specifies the timeout interval in seconds. |
15 seconds
Line configuration
This command first appeared in Cisco IOS Release 10.0.
This command is useful for modems that take a long time to synchronize to the appropriate line speed.
For more information, see the "Configuring Modem Support and Asynchronous Devices" chapter in the Dial Solutions Configuration Guide.
The following example sets the timeout interval to 20 seconds for the modem connected to lines 3 through 13:
line 3 13
modem answer-timeout 20
You can use the master indexes or search online to find documentation of related commands.
modem callin
modem inout
To open a directly connected session and enter AT command mode, which is used for sending AT commands to Microcom manageable modems, use the modem at-mode EXEC command.
modem at-mode slot/port
slot/port | Slot and modem port number. Remember to include the forward slash (/) when entering this variable. |
Disabled
EXEC
This command first appeared in Cisco IOS Release 11.2.
Manageable modems return "OK" if the AT command you transmit is successfully enabled. Press Ctrl-C after transmitting an AT command to close the directly connected session.
The following example opens a directly connected session on modem 1/1, enters AT command mode on modem 1/1, and transmits the AT command ATH through the out-of-band feature of modem 1/1:
router# modem at-mode 1/1 You are now entering AT command mode on modem (slot 1 / port 1). Please type CTRL-C to exit AT command mode. at%v MNP Class 10 V.34/V.FC Modem Rev 1.0/85 OK at\s IDLE 000:00:00 LAST DIAL NET ADDR: FFFFFFFFFFFF MODEM HW: SA 2W United States 4 RTS 5 CTS 6 DSR - CD 20 DTR - RI MODULATION IDLE MODEM BPS 28800 AT%G0 MODEM FLOW OFF AT\G0 MODEM MODE AUT AT\N3 V.23 OPR. OFF AT%F0 AUTO ANS. ON ATS0=1 SERIAL BPS 115200 AT%U0 BPS ADJUST OFF AT\J0 SPT BPS ADJ. 0 AT\W0 ANSWER MESSGS ON ATQ0 SERIAL FLOW BHW AT\Q3 PASS XON/XOFF OFF AT\X0 PARITY 8N AT
You can use the master indexes or search online to find documentation of related commands.
clear modem at-mode
To permit a Microcom modem to accept a directly connected session, use the modem at-mode-permit line configuration command. The no form of this command disables permission for modems to accept a direct connection.
modem at-mode-permitThis command has no keywords or arguments.
Enabled
Line configuration
This command first appeared in Cisco IOS Release 11.2.
After you enter this command, enter the modem at-mode command to enable a directly connected session on the modem. From AT command mode, you can enter AT commands directly from your terminal session.
For a complete list of supported AT commands, refer to the AT command documentation that came with your access server or router.
The no modem at-mode-permit command disables a modem from accepting a direct connection, which is useful for ensuring modem security.
The following example permits the modem connected to TTY line 1 to accept a directly connected session:
line 1 modem at-mode-permit
You can use the master indexes or search online to find documentation of related commands.
clear modem at-mode
modem at-mode
To configure a line to discover what kind of modem is connected to the router and to configure that modem automatically, use the modem autoconfigure discovery line configuration command. Use the no form of this command to disable this feature.
modem autoconfigure discoveryThis command has no arguments or keywords.
This command has no default.
Line configuration
This command first appeared in Cisco IOS Release 11.1.
The modem is identified each time the line is reset. If a modem cannot be detected, the line continues retrying for 10 seconds. When the modem type is determined, this information remains stored until the modem is recycled or disconnected. Discovery mode is much slower than configuring a line directly.
Each time the modem is reset (every time a chat reset script is executed), a string of commands is sent to the modem, the first one being "return to factory-defaults."
The following example discovers whatever kind of modem is attached to the router or access server:
modem autoconfigure discovery
You can use the master indexes or search online to find documentation of related commands.
To direct a line to attempt to configure the attached modem using the entry for modem-name, use the modem autoconfigure type line configuration command. Use the no form of this command to disable this feature.
modem autoconfigure type modem-name
modem-name | The name of the modem (such as Codex_3260). |
This command has no default.
Line configuration
This command first appeared in Cisco IOS Release 11.1.
The modem is reconfigured each time the line goes down.
The following example automatically configures the attached modem using the codex_3260 modemcap entry:
modem autoconfigure type Codex_3260
You can use the master indexes or search online to find documentation of related commands.
To automatically and periodically perform a modem diagnostics test for modems inside the access server or router, use the modem autotest global configuration command. Use the no form of this command to disable or turn off the modem autotest service.
modem autotest {error threshold | minimum modem | time hh:mm [interval]}
error threshold | Maximum modem error threshold. When the system detects this many errors with the modems, the modem diagnostics test is automatically triggered. Specify a threshold count between 3 and 50. |
minimum modem | Minimum number of modems that will remain untested and available to accept calls during each test cycle. You can specify between 5 and 48 modems. The default is 6 modems. |
time hh:mm | Time you want the modem autotest to begin. You must use the military time convention and a required colon (:) between the hours and minutes variables for this feature. For example, 1:30 a.m. is issued as 01:30. |
interval | (Optional) Long-range time variable used to set the modem autotest more than one day in advance. The range of hours is between 1 hour and 168 hours. For example if you want to run the test once per week, issue 168. There are 168 hours in one week. |
Disabled
Global configuration
This command first appeared in Cisco IOS Release 11.3.
The following example shows how to set the modem autotest to run once per week at 3:00 a.m. Additionally, the autotest will activate if the system detects a modem error count higher than 40 errors.
Step 1 Determine the current time set on the access server with the show clock EXEC command. In this example, the time and date set is 3:00 p.m, Monday, August 25, 1997:
router# show clock *15:00:01.031 EST Aug 25 1997
Step 2 Enter global configuration mode and set the time you want the modem autotest to activate. In this example, the access server is configured to run the modem autotest each ongoing Tuesday at 3:00 a.m:
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# modem autotest time 03:00 168
Step 3 Configure the autotest to activate if the system detects a high modem error count. In this example, the autotest activates if the system detects a modem error count higher than 40 errors. For the list of modem errors that are monitored by the modem autotest command, see the show modem call-stats command.
router(config)# modem autotest error 40 router(config)# exit router# %SYS-5-CONFIG_I: Configured from console by console router#
Step 4 Display the results of the modem autotest once the test has run through a test cycle by issuing the show modem test EXEC command:
router# show modem test Date Time Modem Test Reason State Result 5/15 07:25:17 AM 1/0 Back-To-Back TIME INTERVAL Idle FAIL 5/15 07:25:17 AM 1/1 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/2 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/3 Back-To-Back TIME INTERVAL Idle FAIL 5/15 07:25:17 AM 1/4 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/5 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/6 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/7 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/8 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/9 Back-To-Back TIME INTERVAL Idle PASS ...
Alternatively, you can view which modems were marked bad by the modem autotest by issuing the show modem EXEC command. Bad modems are marked by the letter B. In this example, modems 1/0 and 1/3 are marked bad (identified with a B), which takes them out of commission and unable to participate in dial services:
router# show modem Inc calls Out calls Busied Failed No Succ Mdm Usage Succ Fail Succ Fail Out Dial Answer Pct. B 1/0 0% 0 0 0 0 1 0 0 0% 1/1 0% 0 0 0 0 3 0 0 0% 1/2 0% 0 0 0 0 1 0 0 0% B 1/3 0% 0 0 0 0 1 0 0 0% 1/4 0% 0 0 0 0 1 0 0 0% 1/5 0% 0 0 0 0 1 0 0 0% 1/6 0% 0 0 0 0 1 0 0 0% 1/7 0% 0 0 0 0 1 0 0 0% 1/8 0% 0 0 0 0 1 0 0 0% 1/9 0% 0 0 0 0 1 0 0 0% 1/10 0% 0 0 0 0 1 0 0 0% 1/11 0% 0 0 0 0 1 0 0 0% 1/12 0% 0 0 0 0 1 0 0 0% 1/13 0% 0 0 0 0 1 0 0 0% 1/14 0% 0 0 0 0 1 0 0 0% 1/15 0% 0 0 0 0 1 0 0 0% 1/16 0% 0 0 0 0 1 0 0 0% 1/17 0% 0 0 0 0 1 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%
To remove an integrated modem from service and indicate it as suspected or proven to be inoperable, use the modem bad line configuration command. Use the no form of this command to restore a modem to service.
modem badThis command has no keywords or arguments.
Disabled
Line configuration
This command first appeared in Cisco IOS Release 11.2.
If you mark a modem as inoperable, it appears as Bad---without the asterisk (*)---in the Status column of the show modem command output. A modem marked inoperable by the modem startup-test command appears as Bad* in the show modem command output. Use the no modem bad command to unmark a modem as Bad* or Bad and restore it for dial-up connection services.
The first part of the following example shows a successful connection between modem 2/1 and modem 2/0, which verifies normal operating conditions between these two modems. However, when modem 2/1 is tested against modem 2/3, the back-to-back modem test fails. Therefore, modem 2/3 is suspected or proven to be inoperable. Modem 2/3 is removed from dial-up services through the use of the modem bad command on line 28.
router# test modem back-to-back 2/1 2/0 Repetitions (of 10-byte packets) [1]: 10 router# %MODEM-5-B2BCONNECT: Modems (2/1) and (2/0) connected in back-to-back test: CONN ECT9600/REL-MNP %MODEM-5-B2BMODEMS: Modems (2/0) and (2/1) completed back-to-back test: success/ packets = 20/20 router# test modem back-to-back 2/1 2/3 Repetitions (of 10-byte packets) [1]: 10 router# %MODEM-5-BADMODEMS: Modems (2/3) and (2/1) failed back-to-back test: NOCARRIER router# configure terminal router(config)# line 28 router(config-line)# modem bad router(config-line)# end
You can use the master indexes or search online to find documentation of related commands.
modem startup-test
show modem
test modem back-to-back
To configure the size of the history event queue buffer for integrated modems installed in an access server or router, use the modem buffer-size command.
modem buffer-size number
number | Defined number of modem events that each manageable modem is able to store. |
100 modem events
Global configuration
This command first appeared in Cisco IOS Release 11.2.
A large buffer size uses significant amounts of processing memory. If the processing memory is running low, reduce the modem buffer size.
To view modem events, use the show modem log command.
The following example enables each modem in the access server to store 150 modem events:
modem buffer-size 150
You can use the master indexes or search online to find documentation of related commands.
show modem log
To gracefully disable a modem from dialing or answering calls, use the modem busyout line configuration command. Use the no form of this command to re-enable a modem.
modem busyoutThis command has no keywords or arguments.
Disabled
Line configuration
This command first appeared in Cisco IOS Release 11.2.
The disabling action is not executed until the active modem returns to an idle state. No active connections are interrupted when you enter this command.
If a busyout-threshold is set, this command will be delayed until the DS0 lines to the exchange are taken out of service.
For T3 cards the message, No Controller configured, might appear for unconfigured T1 links in the T3.
The following example disables the modem associated with line 1/0/5 from dialing and answering calls. You do not specify a slot/port number with this command:
router# configure terminal router(config)# line 1/0/5 router(config-line)# modem busyout
The following example busyouts a range of modems:
router# configure terminal router(config)# line 1/0/5 1/0/72 router(config-line)# modem busyout
The following example disables the modem associated with line 1 from dialing and answering calls. You do not specify a slot/port number with this command:
line 1 modem busyout
You can use the master indexes or search online to find documentation of related commands.
busyout
ds0 busyout
modem shutdown
To configure the modem country code for a bank of MICA modems, use the modem country mica global configuration command. Use the no form of this command to remove a country code from service.
modem country mica country
country | Specifies a type of country code. Replace the argument country with one of the following supported country names: · australia · austria · belgium · china · cyprus · czech-republic (Czech/Slovak Republic) · denmark · e1-default (Default E1, A Law) |
| · finland · france · germany · hong-kong · india · ireland · israel · italy · japan · malaysia · netherlands · new-zealand |
| · norway · poland · portugal · russia · singapore · south-africa · spain · sweden · switzerland · t1-default (Default T1, u Law) · taiwan · thailand · turkey · united-kingdom · usa |
Disabled
Global configuration
This command first appeared in Cisco IOS Release 11.2 P.
The following example shows the different duplex configuration options you can configure on a Cisco AS5300:
router(config)# modem country mica ? australia Australia austria Austria belgium Belgium china China cyprus Cyprus czech-republic Czech/Slovak Republic denmark Denmark e1-default Default E1 (A Law) finland Finland france France germany Germany hong-kong Hong Kong india India ireland Ireland israel Israel italy Italy japan Japan malaysia Malaysia netherlands Netherlands new-zealand New Zealand norway Norway poland Poland portugal Portugal russia Russia singapore Singapore south-africa South Africa spain Spain sweden Sweden switzerland Switzerland t1-default Default T1 (u Law) taiwan Taiwan thailand Thailand turkey Turkey united-kingdom United Kingdom usa USA
You can use the master indexes or search online to find documentation of related commands.
modem country microcom_hdms
To configure the modem country code for a bank of Microcom modems, use the modem country microcom_hdms global configuration command. Use the no form of this command to remove a country code from service.
modem country microcom_hdms country
country | Specifies a type of country code. Replace the argument country with one of the following supported country names: · argentina · australia · austria · belgium · brazil · canada · chile · china · columbia · czech-republic (Czech/Slovak Republic) · denmark · europe · finland · france · germany · greece · hong-kong · hungary · india · indonesia |
| · finland · israel · italy · japan · korea · malaysia · mexico · netherlands · new-zealand |
| · norway · peru · philippines · poland · portugal · saudi-arabia · singapore · south-africa · spain · sweden · switzerland · taiwan · thailand · united-kingdom · usa |
No country code enabled.
Global configuration
This command first appeared in Cisco IOS Release 11.2 P. The europe keyword was added in Cisco IOS Release 12.0.
The following example shows the different duplex configuration options you can configure on a Cisco AS5300:
router(config)# modem country microcom_hdms ? argentina Argentina australia Australia austria Austria belgium Belgium canada Canada chile Chile china China columbia Columbia czech-republic Czech/Slovak Republic denmark Denmark europe Europe finland Finland france France germany Germany greece Greece hong-kong Hong Kong india India indonesia Indonesia ireland Ireland israel Israel italy Italy japan Japan korea Korea malaysia Malaysia mexico Mexico netherlands Netherlands new-zealand New Zealand norway Norway peru Peru philippines Philippines poland Poland portugal Portugal saudi-arabia Saudi Arabia singapore Singapore south-africa South Africa spain Spain sweden Sweden switzerland Switzerland taiwan Taiwan thailand Thailand united-kingdom United Kingdom usa USA
You can use the master indexes or search online to find documentation of related commands.
modem country mica
To reset and isolate integrated modems for extensive troubleshooting, use the modem hold-reset line configuration command. Use the no form of this command to restart a modem.
modem hold-resetThis command has no keywords or arguments.
Disabled
Line configuration
This command first appeared in Cisco IOS Release 11.2.
This command is also used to reset a modem that is frozen in a suspended state. Disable the suspended modem with the modem hold-reset command, and then restart initialization with the no modem hold-reset command.
The modem hold-reset command for the V.110 port module resets the processor on board the module only if the command is executed on all 12 ports. If the modem hold-reset command is issued on only a portion of the V.110 ports, the processor will not reset.
The following example disables the suspended modem using tty line 4 and resets the modem's initialization:
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# line 4 router(config-line)# modem hold-reset router(config-line)# no modem hold-reset
The following examples resets a 12-port V.110 port module. You must specify the entire tty line range for the entire bank of ports.
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# line 1 12 router(config-line)# modem hold-reset router(config-line)# no modem hold-reset router(config-line)# exit router(config)#
You can use the master indexes or search online to find documentation of related commands.
To set the maximum number of polling attempts used to retrieve performance statistics from a modem installed in an access server or router, use the modem poll retry global configuration command.
modem poll retry number
number | Maximum number of polling attempts. The configuration range is from 0 to 10 attempts. |
Three polling attempts
Global configuration
This command first appeared in Cisco IOS Release 11.2.
Higher settings cause the software to keep polling one modem for status and to avoid polling other modems, which decreases the amount of statistics that are gathered.
The following example configures the server to attempt to retrieve statistics from a local modem up to five times before discontinuing the polling effort:
modem poll retry 5
You can use the master indexes or search online to find documentation of related commands.
clear modem
modem poll time
modem status-poll
To set the time interval between modem polls, which are used to periodically retrieved and report modem statistics, use the modem poll time global configuration command. To restore the 12-second default setting, use the no form of this command.
modem poll time seconds
seconds | Number of seconds between polls. The configuration range is from 2 to 120 seconds. |
12 seconds
Global configuration
This command first appeared in Cisco IOS Release 11.2.
This command does not apply to basic modems, which do not have out-of-band ports.
The following example sets the time interval between polls to 10 seconds:
modem poll time 10
You can use the master indexes or search online to find documentation of related commands.
modem poll retry
modem status-poll
To specify the modem recovery mode, enter the modem recovery action global configuration command. Enter the no form of this command to turn off this feature.
modem recovery action {disable | download | none}
disable | Mark the modem bad. |
download | Recover by firmware download. Sets the modem into a recovery pending state, thus, stopping the modem from accepting new calls. |
none | Do not try to recover. Ignore the recovery threshold and just keep going. |
The default setting is modem recovery action download.
Global configuration
This command first appeared in Cisco IOS Release 12.0.
MICA portware is downloaded on a modular basis and not on a modem basis. Thus, reloading MICA portware requires all 6 modems (or 12) in a module to be re-loaded.
After a modem has been deemed faulty, the configured action will take place on the modem. The following choices are possible: disable, download, and none.
The following example shows the available options for this command:
Router(config)# modem recovery action ? disable Mark the modem bad download Recover by firmware download none Do not try to recover
You can use the master indexes or search online to find documentation of related commands.
modem recovery maintenance
modem recovery threshold
modem recovery-time
To specify the modem maintenance recovery behavior, enter the modem recovery maintenance global configuration command. Enter the no form of this command to turn off this behavior.
modem recovery maintenance {action {disable | drop-call | reschedule} | max-download number | schedule {immediate | pending} | time hh:mm | window minutes}
action | Mode of recovery. The default is set to reschedule. |
disable | Mark the modem bad. Mark the originally faulty modem as bad and return all other modems back into service. |
drop-call | Force firmware download by dropping holding calls. This forces the recovery by dropping any active calls remaining on modems within the module. |
reschedule | Reschedule firmware download to next maintenance time. Leave the originally faulty modem as needing recovery and return all other modems back into service. Recovery will be attempted again on the following day. The default is set to reschedule. |
max-download number | Maximum simultaneous recovery downloads. You must choose one number between 1 and 30. A range of values is not supported. |
schedule | Scheduling method for modem recovery. Determines if the system should attempt module recovery as soon as a problem is found or wait for the maintenance window. |
immediate | Immediately attempt module recovery. |
pending | Delay recovery until maintenance time. |
time hh:mm | Time of day for scheduled modem recovery. This is the actual time of day when the modem recovery maintenance process wakes up and starts recovering MICA modems. The default time is 3:00 AM. |
window minutes | Amount of time for normal recovery to take place. This is the delay timer in minutes, which is between 0 and 360. |
The default action is set to reschedule. The default is modem recovery maintenance schedule is set to pending. The default time is 3:00 AM.
Global configuration
This command first appeared in Cisco IOS Release 12.0.
MICA portware is downloaded on a modular basis and not on a modem basis. Thus, reloading MICA portware requires all 6 modems (or 12) in a module to be re-loaded.
Every 24 hours, the modem recovery maintenance process will wake up and attempt to recover any modems which are in the pending recovery state.
When a MICA module attempts to reload its portware, it must avoid taking down any modem connections that may exist. As such, the recovery process sets all modems currently not in use to recovery pending state. If any modems on the module are active, the recovery process waits for the calls to terminate normally. To avoid capacity problems from attempting recovery for an excessively long time period, a maintenance window is configured to require the modem recovery to take place within a specific timeframe. Otherwise, a given action is performed on that module when the window expires. The default window is 60 minutes. This behavior is set using the modem recovery maintenance window minutes command.
When the modem recovery maintenance window expires, one of the following actions is performed on the modem module awaiting recovery: disable, reschedule, or drop-call. These options are associated with the modem recovery action command.
When the modem recovery maintenance process starts, it attempts to recover all modems in the recovery pending state. This can potentially be all modules on a given system. Thus, to avoid taking down all modems on a given system, only a maximum of simultaneous module recoveries can take place. The default is dynamically calculated to be 20% of the modules on a given system. This configuration allows that value to be overridden. These options are associated with the modem recovery maintenance max-download number command.
The following example shows the available options for this command:
Router(config)# modem recovery maintenance ? action Mode of recovery max-download Maximum simultaneous recovery downloads schedule Scheduling method for modem recovery time Time of day for scheduled modem recovery window Amount of time for normal recovery to take place Router(config)# modem recovery maintenance action ? disable Mark the modem bad drop-call Force firmware download by dropping holding calls reschedule Reschedule firmware download to next maintenance time Router(config)# modem recovery maintenance max-download ? <1-30> Number of MICA modules which can be simultaneously recovered Router(config)# modem recovery maintenance schedule ? immediate Attempt recovery immediately pending Delay recovery until maintenance time
You can use the master indexes or search online to find documentation of related commands.
modem recovery action
modem recovery threshold
modem recovery-time
To specify the threshold, which starts the modem recovery process, enter the modem recovery threshold global configuration command. Enter the no form of this command to disable the threshold value.
modem recovery threshold number
number | Number of consecutive call attempts, which fail to train up, before the modem is deemed faulty. Choose between 1 and 1000. |
30 call attempts are enabled by default.
Global configuration
This command first appeared in Cisco IOS Release 12.0.
MICA portware is downloaded on a modular basis and not on a modem basis. Thus, reloading MICA portware requires all 6 modems (or 12) in a module to be re-loaded.
The following example shows the variable number for this command:
Router(config)# modem recovery threshold ? <1-10000> Number of failures after which modem recovery is started
You can use the master indexes or search online to find documentation of related commands.
modem recovery action
modem recovery maintenance
modem recovery-time
To set the maximum amount of time the call-switching module waits for a local modem to respond to a request before it is considered locked in a suspended state, use the modem recovery-time global configuration command. The no form of this command sets a 5-minute response time, which is the default setting.
modem recovery-time minutes
minutes | Maximum amount of time local modems wait for a response. |
5 minutes
Global configuration
This command first appeared in Cisco IOS Release 11.2.
After the call-switching module resets a suspended modem, it recovers to a default call switching module state.
The following example configures the call-switching module to wait for 8 minutes:
modem recovery-time 8
You can use the master indexes or search online to find documentation of related commands.
modem recovery action
modem recovery maintenance
modem recovery threshold
To abruptly shut down an active or idle modem installed in an access server or router, use the modem shutdown line configuration command. Use the no form of this command to take the modem out of a shutdown state and place it back in service.
modem shutdownThis command has no keywords or arguments.
Disabled
Line configuration
This command first appeared in Cisco IOS Release 11.2.
Enable the no modem shutdown command to restore to service a modem that has been shut down.
The following example abruptly shuts down the modem associated with line 1/0/6. All active calls on the modem are dropped immediately.
router# configure terminal router(config)# line 1/0/6 router(config-line)# modem shutdown
The following example abruptly shuts down a range of modems.
router# configure terminal router(config)# line 1/0/5 1/0/72 router(config-line)# modem shutdown
The following example abruptly shuts down the modem associated with line 2 on a Cisco AS5300. All active calls on the modem are dropped immediately.
configure terminal line 2 modem shutdown
You can use the master indexes or search online to find documentation of related commands.
busyout
ds0 busyout
modem busyout
To perform diagnostic testing on each integrated modem during the rebooting process, use the modem startup-test global configuration command. Use the no form of this command to disable startup testing.
modem startup-testThis command has no keywords or arguments.
Enabled
Global configuration
This command first appeared in Cisco IOS Release 11.2.
The results of the modem startup test are displayed in the Status column of the show modem command's output. Modems that pass the diagnostic test are marked as Idle, Busy, Downloading, and Reset. Modems that fail the diagnostic test are marked as Bad*. These modems cannot be used for call connections. Depending on how many modems are installed, this diagnostic test may take from 5 to 15 minutes to complete.
Perform additional testing on an inoperative modem by executing the test modem back-to-back command. The no modem startup-test command disables startup testing.
The following example performs a startup test on the integrated Cisco AS5200 modems:
configure terminal modem startup-test
Display the results of the modem startup test after you restart the system by enabling the show modem command.
You can use the master indexes or search online to find documentation of related commands.
modem autotest
show modem
test modem back-to-back
To poll for modem statistics through a modem's out-of-band feature, use the modem status-poll line configuration command. Use the no form of this command to disable status polling through the out-of-band feature for a specified modem.
modem status-pollThis command has no keywords or arguments.
Enabled
Line configuration
This command first appeared in Cisco IOS Release 11.2.
This command applies only to manageable modems that have out-of-band ports.
The following example enables modem status polling through TTY line 1:
configure terminal line 1 modem status-poll
You can use the master indexes or search online to find documentation of related commands.
modem poll retry
modem poll time
To change a modem value that was returned from the show modemcap command, use the modemcap edit global configuration command.
modemcap edit modem-name attribute value
modem-name | Name of the modem whose values are being edited. |
attribute | Modem capability, or attribute, as defined by the show modemcap command. |
value | The AT command equivalent (such as &F). |
This command has no default.
Global configuration
This command first appeared in Cisco IOS Release 11.1.
Modemcaps are printed within the configuration file. You can edit them using this command.
Configure one attribute of one modem at a time. See the modem-capability values defined by show modemcap command.
The following example adds the factory default entry, &F, to the configuration file. This entry, and others like it, are stored in a database that is referenced by the configuration file.
modemcap edit Codex_3250 factory-default &F
You can use the master indexes or search online to find documentation of related commands.
modemcap entry
show modemcap
To store and compress information about the capability of a specified modem, use the modemcap entry global configuration command. Use the no form of this command to disable this feature.
modemcap entry modem-type
modem-type | Type of supported modem as specified in Table 12. |
The capability values that exist in the specified modem at the time that the command is issued.
Global configuration
This command first appeared in Cisco IOS Release 11.1.
This command displays the capability of the specified modem.
Modemcaps are printed within the configuration file and are intended to be edited using the modemcap edit command. The modemcap entry command does not display values that are not set in the modem.
Use modemcap entry with the show modemcap command to interpret the capability of the specified modem. Table 12 lists the modemcap entries for supported modems.
| Modem Type | Output |
|---|---|
hayes_optima | FD=&F:AA=S0=1:DTR=&D2:CD=&C1:TPL=default. |
codex_3260 | FD=&F:AA=S0=1:CD=&C1:DTR=&D2:HFL=*FL3:SPD=*SC1:BER=*SM3:BCP=*DC1:NER=*SM1:NCP=*DC0:NEC=E0:NRS=Q1:CID=&S1. |
usr_courier | HFL=&H1&R2:SPD=&B1:BER=&M4:BCP=&K1:NER=&M0:NCP=&K0:TPL=default. |
usr_sportster | TPL=usr_courier. |
hayes_optima | HFL=&K3:BER=&Q5:BCP=&Q9:NER=&Q0:NCP=&Q0:TPL=default. |
viva | HFL=&K3:BER=&Q5:BCP=%C1:NER=&Q6:NCP=%C0:TPL=default. |
telebit_t3000 | HFL=S58=2:BER=S180=3:BCP=S190=1:NER=S180=0:NCP=S190=0:TPL=default. |
You can use the master indexes or search online to find documentation of related commands.
modem hold-reset
show modemcap
To create a new modem pool or to specify an existing modem pool, use the modem-pool global configuration command. Use the no form of this command to delete a modem pool from the access server's configuration.
modem-pool name
name | Specifies the name of a modem pool. |
All modems are configured to be part of one system default modem pool (displayed as System-def-Mpool by the show modem-pool command.). For example, if you have 120 MICA modems loaded in your access server, then 120 modems are in the default modem pool.
Global configuration
This command was first introduced in Cisco IOS Release 11.2 P.
Modem pools enable you to physically partition or virtually partition your access server for dial-in and dial-out access.
Physical partitioning is makes one access server appear as if it is multiple access servers loaded with different types of modem services (for example, v.34 modems, fax capable modems, and point-of-sale (POS) modems). Each service is part of one modem pool and assigned a unique DNIS number.
Virtual partitioning is creates one large modem pool on the access server, but enables different customers to dial-in and share the modem resources. Each customer is assigned its own DNIS number. Each customer is given overflow protection, which guarantees a certain number of simultaneous connections.
The following example creates a modem pool called v90service. After the modem-pool v90service command is issued, modem pool configuration mode is accessed. The access server's prompt changes from as5300(config)# to as5300(config-modem-pool)#.
as5300# configure terminal Enter configuration commands, one per line. End with CNTL/Z. as5300(config)# modem-pool v90service as5300(config-modem-pool)#
The next example assigns modem TTY line numbers 30 to 50 to a modem pool. The DNIS number is set to 2000. The customers dialing the number 2000 are guaranteed access to 21 modems. The 22nd client to dial in is refused connectivity because the maximum number of allowable connections is exceeded.
as5300(config-modem-pool)# pool-range 30-50 as5300(config-modem-pool)# called-number 2000 max-conn 21 as5300(config-modem-pool)# exit as5300(config)#
You can use the master indexes or search online to find documentation of related commands.
called-number
clear modempool-counters
pool-range
show modem-pool
To assign a range of modems to a modem pool, use the pool-range modem-pool configuration command.
pool-range number-number (Cisco AS5200 and Cisco AS5300)
number-number | Assigns a range of TTY lines, which correspond to ranges of modems, to a modem pool. A dash (-) is required between the two modem numbers. The range of modems you can choose from is equivalent to the number of modems in your access server that are not currently associated with another modem pool. |
Disabled. All modems are configured to be part of the system default modem pool.
Modem pool configuration
This command first appeared in Cisco IOS Release 11.2 P.
For a complete description of modem pools and how they are configured on Cisco access servers, see the command reference page for the modem-pool command.
Replace the number-number variable with the modem TTY line numbers that correspond with the range of modems you want in the modem pool. TTY line numbers start from 1, which map to modem numbers that start from 0. For example, if you want to include modems 1/0 through 1/23 in a pool range, use the TTY line numbers 1 to 24. To verify the modem to TTY line numbering scheme, enter the show modem slot/port command.
The following example assigns modem TTY line numbers 30 to 50 to a modem pool. The DNIS number is set to 2000. The customers dialing 2000 are guaranteed access to 21 modems. The 22nd client to dial in is refused connectivity because the maximum number of allowable connections is exceeded.
as5300(config)# modem-pool v90service as5300(config-modem-pool)# pool-range 30-50 as5300(config-modem-pool)# called-number 2000 max-conn 21 as5300(config-modem-pool)# exit as5300(config)#
The following configuration rejects the pool-range 30 command, because modem TTY line 30 is already a member of the modem pool v90service, which was configured in the previous example. Each modem in the access server is automatically assigned to a unique TTY line. TTY line numbers are assigned according to your shelf, slot, or port hardware configuration.
as5300(config)# modem-pool v34service as5300(config-modem-pool)# pool-range 30 % TTY 30 is already in another pool. as5300(config-modem-pool)#
You can use the master indexes or search online to find documentation of related commands.
called-number
clear modempool-counters
modem-pool
show modem-pool
To display a high-level performance report for all the modems or a single modem inside an access server or router, use the show modem EXEC command.
show modem [slot/port | group number] (Cisco AS5200, CiscoAS5300)
slot/port | (Optional) Specifies the location of a slot and modem port. Remember to include the forward slash (/) when entering this variable. |
group number | (Optional) Specifies a modem group to which a specified modem belongs. The group number range is between 1 and 200. |
EXEC
This command first appeared in Cisco IOS Release 11.2.
The following display shows output information for the show modem command for two V.34 modem cards inserted in a Cisco AS5200:
router# show modem
Inc calls Out calls Busied Failed No Succ
Mdm Usage Succ Fail Succ Fail Out Dial Answer Pct.
* 1/0 17% 74 3 0 0 0 0 0 96%
* 1/1 15% 80 4 0 0 0 1 1 95%
* 1/2 15% 82 0 0 0 0 0 0 100%
1/3 21% 62 1 0 0 0 0 0 98%
1/4 21% 49 5 0 0 0 0 0 90%
* 1/5 18% 65 3 0 0 0 0 0 95%
* 1/6 19% 58 2 0 0 0 0 0 96%
* 1/7 17% 67 5 0 0 0 1 1 93%
* 1/8 20% 68 3 0 0 0 0 0 95%
1/9 16% 67 2 0 0 0 0 0 97%
1/10 18% 56 2 0 0 0 1 1 96%
* 1/11 15% 76 3 0 0 0 0 0 96%
* 1/12 16% 62 1 0 0 0 0 0 98%
1/13 17% 51 4 0 0 0 0 0 92%
1/14 16% 51 5 0 0 0 0 0 91%
1/15 17% 65 0 0 0 0 0 0 100%
1/16 15% 73 3 0 0 0 0 0 96%
1/17 17% 67 2 0 0 0 0 0 97%
1/18 17% 61 2 0 0 0 0 0 96%
* 1/19 17% 74 2 0 0 0 0 0 97%
1/20 16% 65 1 0 0 0 0 0 98%
* 1/21 16% 58 3 0 0 0 0 0 95%
* 1/22 18% 56 4 0 0 0 0 0 93%
* 1/23 20% 60 4 0 0 0 0 0 93%
The following display shows output information for the show modem command for two V.110 modem cards inserted in a Cisco AS5200:
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 13 describes the fields shown in the previous displays of the show modem version command.
| 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 suspected to be inoperable or bad. No calls can be made with this modem. The letter B can also mean that a modem firmware download failed for the specified modem. In this case, try unmarking the modem as bad with the no modem bad command and upgrading the modem firmware again. 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. p--- Firmware download is pending. Typically because one or more modems is active. 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 a modem. |
Out calls | Number of outgoing calls that successfully and unsuccessfully dialed out from an available 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 card in a Cisco AS5200. A dash (-) indicates a field that is not available on basic modems. An x indicates a field that is available and active on manageable modems. See Table 14 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 basic V.34 modem module. Notice that unavailable fields are marked with dashes (-):
router# 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 following display shows output information for the show modem slot/port command for V.110 modem cards:
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 -
The type of display output generated from the show modem slot/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, which 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 14 for a description of the fields displayed by 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
Table 14 describes the fields in the previous four displays, which were created using the show modem slot/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: Bel103, Bel212, V21, V22, V22bis, V23, V32, V32bis, VFC, V34, V17, V27, V33 and K56Flx |
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 feature 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.
|
Transmit Speed Counters: | List of connection speeds that were transmitted by the modem. |
Receive Speed Counters: | List of connection speeds that were received by the modem. |
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 shows the sample display for modem group 1, which is composed of modem 1/0 through modem 1/23:
router# 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
You can use the master indexes or search online to find documentation of related commands.
show mica module
show modem version
To display a list of the manageable Microcom modems that have open AT sessions and a list of users logged in to those sessions, use the show modem at-mode EXEC command.
show modem at-modeThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.2.
The following output shows that modem 1/1 has one open AT directly connected session:
router# show modem at-mode Active AT-MODE management sessions: Modem User's Terminal 1/1 0 cty 0
To display the local disconnect reasons for all modems inside an access server or router, use the show modem call-stats EXEC command.
show modem call-stats [slot]
slot | (Optional) Specifies the slot number, which limits the display output to a particular range of modems in the system. |
EXEC
This command first appeared in Cisco IOS Release 11.3.
Use this command to find out why a modem ended its connection or why a modem is not operating at peak performance.
Local disconnect reasons for a particular modem are listed across the top of the screen display. For example, see lostCarr, dtrDrop, rmtLink, wdogTimr, compress, retrain, inacTout, and linkFail in the following output:
router# show modem call-stats
dial-in/dial-out call statistics
lostCarr dtrDrop rmtLink wdogTimr compress retrain inacTout linkFail
Mdm
* 0/0
* 0/1
In the body of the screen display, the number of times an error occurred on a specific modem is displayed (see the # column). The % column shows the total running percent that a modem was logged for the specified disconnect reason with respect to the entire modem pool. For example, out of all the times the lostCarr error occurred on all the modems in the system, the lostCarr error occurred 2% of the time on modem 0/0.
router# show modem call-stats
dial-in/dial-out call statistics
lostCarr dtrDrop rmtLink wdogTimr compress retrain inacTout linkFail
Mdm # % # % # % # % # % # % # % # %
* 0/0 6 2 2 3 1 0 0 0 0 0 0 0 0 0 0 0
* 0/1 5 2 2 3 2 1 0 0 0 0 0 0 0 0 0 0
Bad or malfunctioning modems are detected by an unusually high number of disconnect counters for a particular disconnect reason. For example, if modem 1/0 had an astronomically high number of compression errors compared to the remaining modems in system, modem 1/0 would probably be bad or inoperable.
To reset the counters displayed by the show modem call-stats command, issue the clear modem counters command.
The following example shows call statistics for the show modem call-stats command. Due to the screen size limitation of most terminal screen displays, all the possible disconnect reasons cannot be displayed at the same time. Only the top eight most frequently experienced disconnect reasons are displayed.
router# show modem call-stats
dial-in/dial-out call statistics
lostCarr dtrDrop rmtLink wdogTimr compress retrain inacTout linkFail
Mdm # % # % # % # % # % # % # % # %
* 0/0 6 2 2 3 1 0 0 0 0 0 0 0 0 0 0 0
* 0/1 5 2 2 3 2 1 0 0 0 0 0 0 0 0 0 0
0/2 5 2 2 3 4 3 0 0 0 0 0 0 0 0 0 0
* 0/3 5 2 2 3 2 1 0 0 0 0 0 0 0 0 0 0
* 0/4 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/5 5 2 2 3 2 1 0 0 0 0 0 0 0 0 0 0
* 0/6 4 1 2 3 2 1 0 0 0 0 0 0 0 0 0 0
* 0/7 4 1 2 3 4 3 0 0 0 0 0 0 0 0 0 0
* 0/8 6 2 1 1 3 2 0 0 0 0 0 0 0 0 0 0
* 0/9 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/10 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 0/11 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
0/12 5 2 2 3 2 1 0 0 0 0 0 0 0 0 0 0
* 0/13 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/14 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/15 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/16 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/17 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 0/18 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 0/19 5 2 1 1 3 2 0 0 0 0 0 0 0 0 0 0
* 0/20 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/21 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 0/22 5 2 1 1 11 10 0 0 0 0 0 0 0 0 0 0
* 0/23 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/0 4 1 2 3 2 1 0 0 0 0 0 0 0 0 0 0
* 2/1 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/2 5 2 2 3 0 0 0 0 0 0 0 0 0 0 0 0
* 2/3 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/4 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/5 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/6 4 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 2/7 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 2/8 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 2/9 4 1 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/10 5 2 1 1 0 0 0 0 0 0 0 0 0 0 0 0
* 2/11 5 2 1 1 5 4 0 0 0 0 0 0 0 0 0 0
* 2/12 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/13 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 2/14 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/15 4 1 1 1 3 2 0 0 0 0 0 0 0 0 0 0
* 2/16 4 1 1 1 3 2 0 0 0 0 0 0 0 0 0 0
* 2/17 5 2 2 3 9 8 0 0 0 0 0 0 0 0 0 0
* 2/18 4 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 2/19 3 1 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/20 7 3 1 1 8 7 0 0 0 0 0 0 0 0 0 0
* 2/21 5 2 1 1 1 0 0 0 0 0 0 0 0 0 0 0
* 2/22 4 1 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/23 5 2 1 1 2 1 0 0 0 0 0 0 0 0 0 0
Total 233 59 110 0 0 0 0 0
dial-out call statistics
noCarr noDitone busy abort dialStrg autoLgon dialTout rmtHgup
Mdm # % # % # % # % # % # % # % # %
* 0/0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0/2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/3 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/4 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/6 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/7 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/9 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/11 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0/12 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/13 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/14 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/15 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/16 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/17 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/18 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/19 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/21 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/22 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 0/23 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/0 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/1 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/5 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/6 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/7 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/8 7 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/9 4 1 1 1 2 1 0 0 0 0 0 0 0 0 0 0
* 2/10 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/11 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/12 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/13 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/14 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/15 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/16 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/17 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/18 5 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/19 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/20 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/21 4 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/22 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 2/23 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Total 84 0 0 0 0 0 0 0
Table 15 describes the show modem call-stats fields.
| Field | Description |
|---|---|
dial-in/dial-out call statistics | This category of disconnect reasons can happen only in dial-in or dial-out scenarios. |
wdogTimr | Watchdog timeout. An obscure firmware problem occurred. This is a rare disconnect reason. |
compress | Compression. An error was detected during decompression, which caused the internal decompression dictionary to overflow. This could be caused by a modem dialing in that is using a slightly different compression algorithm. |
retrain | Retrain failure. A connection was lost and not re-established after three attempts. |
inacTout | Inactivity timeout. The time specified in the AT/T command has expired. No modem data transfers were detected during that period. |
linkFail | Link failure. The protocol level link failed while using MNP-10 or LAPM in reliable mode. |
moduFail | Modulation error. An error was detected at the DSP chip level, which caused a disconnect. |
mnpProto | MNP10 protocol error. An uncorrectable error occurred during a MNP-10 connection. |
lapmProt | LAPM protocol error. An uncorrectable error occurred during a LAPM connection. |
lostCarr | Lost carrier. The modem firmware detected a carrier drop during a connection. The cause for the carrier drop could be the loss of signal from the remote modem or the result of a error detection. |
dtrDrop | DTR drop. The modem disconnected because the DTR signal from the host became inactive. |
userHgup | User hang up. The modem disconnected because a command such as ATH was detected. |
rmtlink | Remote link disconnect. If an MNP-10 reliable link is established, the remote modem sends the disconnect reason across the link before disconnecting. The disconnect reason displayed is LOCAL (remote link disconnect) and REMOTE (the reason the remote modem disconnected). |
trminate | Terminate. A password security error occurred in the Microcom HDMS. This error occurs only with Microcom modems. |
callBkfa | Callback failed. This error applies to leased line connections only. A switched line connection failed and a connection still cannot be made on the leased line. |
dial-out call statistics | This category of disconnect reasons can happen only in a dial-out scenario. |
noCarr | No carrier. The called number answered, but no answer tone was detected after the appropriate wait. |
noDitone | No dial tone. No dial tone was detected after the modem went off hook. |
busy | Busy. A busy signal was detected while the local modem was attempting to dial. |
abort | Abort. A character was received from the remote host after the dial command was issued and before a connection was established. |
dialStrg | Dialstring error. An invalid character was detected in the dial string, which forced the dial attempt to terminate. |
autoLgon | Autologon error. An autologon sequence did not successfully complete. |
dialTout | Dial timeout. When a semicolon is used as a dial modifier, the modem returns to the command state as indicated by an "OK." This allows a continuation of the dial string. If a period of time elapses as specified in the S7 register without the dial string completing, the attempt is aborted with dial timeout as the disconnect reason. |
rmtHgup | Remote hang-up. The modem disconnected because the remote modem disconnected the call and dropped DTR. |
blacklst | Blacklist. In a country that supports blacklisting, an attempt was made to go off hook with a null dial string (ATD). |
ccpNssn | CCP not seen. The credit card prompt (also known as Bong) was not detected. |
faxClasz | FAX class 2 error. An abnormal termination to a fax transmission was detected. |
Total | Total number of times the disconnect reason occurred among all the modems in the system. |
To display the current modem configuration for digital MICA modems loaded inside an access server or router, use the show modem configuration EXEC command.
show modem configuration [slot/port]
slot/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. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The following example uses the show modem configuration command to display the configuration for modem 0/1, which resides in slot 0/1 of a Cisco AS5300:
router> show modem configuration 0/1
Modem(0/1) Configuration Block:
Country Code: 1
Originate/Answer Mode: Answer
Data Bits Selection: 8
Parity Selection: 0
Stop Bits Selection: 1
V.42 ODP generation: Generate ODP sequence when originating a call
Error Correction Autodetect Time-out value: 5000 ms
Protocol Negotiation Time-out value: 10000 ms
Protocol Negotiation Fallback Character:
Protocol Negotiation Retransmission Limit: 12
Error Correction Frame Length: 256 bytes
Data Compression: V.42bis and MNP5
ARA Error Correction: ARA1.0 & ARA2.0 Enabled for Answer only
V.42 Error Correction: V.42(LAP-M) Originate&Answer enabled
MNP Error Correction: MNP Originate&Answer enabled
Link Protocol Fallback: Asynchronous Framing (Start/Stop/Parity)
DSP processor MVIP TDM slice: 0
Calling Tone: Disabled
Guard Tone: Disabled
Modem Standard: V.34bis Automode, with terbo
Max. Connect Rate: 33600 bps
Min. Connect Rate: 300 bps
Signal Quality Threshold: Bit Errors >=1:1000 cause recovery
Fallback/Fallforward Squelch Timer: 500 ms
Fall Forward Timer: 10000 ms
Fall Back Timer: 500 ms
Terminate Time-out: 20 second(s)
Wait For Data Mode Time-out: 40 second(s)
Lost Carrier To Hang-up Delay: 1400 ms
Transmit Level Setting: -13 dBm
Retrain Limit: 4
V.34 Max. Symbol Rate: 3249 Baud
V.34 Min. Symbol Rate: 2400 Baud
V.34 Carrier Frequency: Auto Carrier Selection
V.34 Preemphasis Filter Selection: 11
Tx and RX Signaling Type: NULL signaling
Call Progress Tone Detection: No tone detection
+++ Escape Detection: Enabled-Originate-Mode-Only
AT Command Processor: Enabled
Call Set Up Delay: no delay before link initiation
Automatic Answer: delay 1 second(s)
Escape Detection Character: ASCII 43 ('+')
Carriage Return Character: ASCII 13 (CR)
Line Feed Character: ASCII 10 (LF)
Backspace Character: ASCII 8 (BS)
Pause Before Blind Dialing: 2 second(s)
Wait For Carrier After Dial: 40 second(s)
Comma Dial Modifier Time: 2 second(s)
Bit-mapped Register(S9=0x13D): E1Q2V1&D3X4
Delay For Hangup After Carrier Loss: 1400 ms
Table 16 describes the fields in the previous display:
| Field | Description |
|---|---|
Modem slot/port | Slot and port for the specified modem. |
Country code: | Transmit level limits with respect to the S39 register. Default is 1 (U.S. domestic). |
Originate/Answer Mode: | Answer or originate. Default is answer. |
Data Bits Selection: | 7, 8, or 9 data bits. Default is 8. |
Parity Selection: | 0 = no parity, 1 = even parity, 2 = odd parity. Default is no parity. |
Stop Bits Selection: | 1 or 2 stop bits. Default is 1 stopbit. |
V.42 ODP generation: | Disabled or generate ODP sequence when originating a V.42 call. Default is Generate ODP sequence when originating a V.42 call |
Error Correction Autodetect Time-out value: | Maximum period during which the modem will run an automated detection machine upon the incoming data. Default is 5000 ms. |
Protocol Negotiation Time-out value: | Maximum wait for error correction protocol negotiation before fallback. Default is 10000 ms. |
Protocol Negotiation Fallback Character: | 0 to 127. Default is 13. |
Protocol Negotiation Retransmission Limit: | 0 = Do not disconnect on excessive retransmission; 1 to 255 = number of successive retransmissions to cause disconnect. Default is 12. |
Error Correction Frame Length: | Buffer length; 64 to 1024 octets of data. Default is 256. |
Data Compression: | Disabled, V.42bis, MNP5, or V.42bis or MNP5 (V.42 has precedence). Default is V.42bis or MNP5 (V.42 has precedence). |
ARA Error Correction: | ARA1.0 & ARA2.0 Disabled, Enabled for Answer only, Enabled for Answer originate ARA1.0, and Enabled for Answer originate ARA2.0. Default is Enabled for Answer only. |
V.42 Error Correction: | V.42(LAP-M) Disabled, V.42(LAP-M) Originate & Answer enabled. Default is disabled. |
MNP Error Correction: | MNP Disabled or MNP Originate and Answer enabled. Default is MNP Originate and Answer enabled. |
Link Protocol Fallback: | Asynchronous framing (Start/Stop/Parity), Synchronous framing (Raw 8 bits to DSP), or Disconnect (Hang-up). Default is Asynchronous framing (Start/Stop/Parity). |
DSP processor MVIP TDM slice: | 0 to 15. |
Calling Tone: | Disable or Send calling tone. Default is disable. |
Guard Tone: | Guard tone disabled, Use Guard tone (V.22 & V.22bis only). Default is disabled. |
Modem Standard: | V.34bis Automode with terbo, V.34bis Automode skip terbo, V.32 terbo Automode, V.32bis Automode, V.22bis Automode, or K56Flex 1.1. Default is V.34bis Automode with terbo. |
Max. Connect Rate: | 75 to 56000 bps. |
Min. Connect Rate: | 75 to 56000 bps. |
Signal Quality Threshold: | No action on bit errors, Bit Errors >=1:100 cause recovery, Bit Errors >=1:1000 cause recovery, Bit Errors >=1:10000 cause recovery, Bit Errors >=1:100000 cause recovery, or Bit Errors >=1:1000000 cause recovery. Default is 1:1000. |
Fallback/Fallforward Squelch Timer: | Time to delay after a speed shift before allowing another speed shift. Default is 500 ms. |
Fall Forward Timer: | Elapsed time with continuous good signal quality to cause a fall forward. Default is 10000 ms. |
Fall Back Timer: | Elapsed time with bad signal quality to cause a fallback. Default is 500 ms. |
Terminate Time-out: | Elapsed time after a disconnect request before forcing a link disconnect. During this period, the modem sends buffered data and then clears down the link. Default is 20 seconds. |
Wait for Data Mode Time-out: | Maximum time during link establishment before disconnection. Default is 40; 60 for K56Flex. |
Lost Carrier To Hang-up Delay: | Maximum time without a carrier to cause the link disconnect. Default is 1400 ms. |
Transmit Level Setting: | 6dBm, 7dBm, 8dBm, -20dBm, or -21dBm. Default is 9 dBm. |
Retrain Limit: | Maximum successive failed retrains to cause the link to disconnect. Default is 4. |
V.34 Max. Symbol Rate: | 2400 baud, 2743 baud, 2800 baud, 3000 baud, 3200 baud, or 3429 baud. Default is 3429 baud. |
V.34 Min. Symbol Rate: | 2400 baud, 2743 baud, 2800 baud, 3000 baud, 3200 baud, or 3429 baud. Default is 2400 baud. |
V.34 Carrier Frequency: | Low Carrier, High Carrier, or Auto Carrier Selection. Default is High Carrier. |
V.34 Preemphasis Filter Selection: | 0 to 10 = a selected filter; 11 = Automatic Preemphasis Selection. Default is 11. |
Tx and Rx Signaling Type: | NULL signaling, MF signaling, DTMF signaling, Lower band R2 signaling, Upper band R2 signaling, or R1 signaling. Default is NULL signaling. |
Call Progress Tone Detection: | No tone detection, Dial tone detection, Ring-Back tone detection, or Busy tone detection. Default is no tone detection. |
+++ Escape Detection: | Disabled, Enabled, or Enabled-in-Originate-Mode-Only. Default is Enabled-in-Originate-Mode-Only. |
AT Command Processor: | Disabled or Enabled. Default is disabled. |
Call Set Up Delay: | No delay before link initiation, delay value (1 to 255). Default is no delay. |
Automatic Answer: | Answer immediately, delay value (1 to 255 seconds). default is 1 second. |
Escape Detection Character: | ASCI value (0 to 127). Default is 43. |
Carriage Return Character: | ASCI value (0 to 127). Default is 13. |
Line Feed Character: | ASCI value (0 to 127). Default is 10. |
Backspace Character: | ASCI value (0 to 127). Default is 8. |
Pause Before Blind Dialing: | 2 to 255 seconds. Default is 2. |
Wait For Carrier After Dial: | Wait for data mode timeout. |
Comma Dial Modifier Time: | 2 to 255 seconds. Default is 2. |
Bit-mapped Register(S9=0x13D): | Bit mapped register. |
Delay For Hang-up After Carrier Loss: | Lost carrier to hang-up delay. |
You can use the master indexes or search online to find documentation of related commands.
show modem operational-status
show modem mica
show modem log
To display connection speed statistics for all the modems running in an access server or router, use the show modem connect-speeds EXEC command.
show modem connect-speeds [max-speed [slot]]
max-speed | (Optional) Maximum speed you want displayed in the shifting speed window. You can specify from 12,000 to 56,000 bps. |
slot | (Optional) Specifies the slot number, which limits the display output to a particular range of modems in the system. |
The maximum speed displayed is 12,000 bps.
EXEC
This command first appeared in Cisco IOS Release 11.3.
Because most terminal screens are not wide enough to display the entire range of connection speeds at one time (for example, 75 to 56000 bps), the max-speed variable is used. This variable specifies the contents of a shifting baud-rate window, which provides you with a snap shot of modem connection speeds for your system. If you want to see a snap shot of lower baud rates, specify a lower connection speed. If you want to see a snap shot of higher baud rates, specify a higher connection speed.
The max-speed variable also rounds up to the nearest recognizable baud rate by the software, so you do no need to memorize or enter exact connection speeds. For example, if you enter a maximum baud rate of 22059, the system software automatically rounds the value up to 24000.
To display a complete picture of all the connection speeds and counters on the system, you must enter a series of commands. Each time you issue the show modem connect-speeds max-speed command, only nine baud rate columns can be displayed at the same time.
Table 17 shows a range of commands that you can issue, one at a time, to see a complete picture of the total possible connection speeds on your access server.
| Command | Connect Speed Range Displayed |
|---|---|
show modem connect-speeds 56000 | 40,000 to 56,000 bps |
show modem connect-speeds 38000 | 24,000 to 38,000 bps |
show modem connect-speeds 21600 | 2,400 to 21,600 bps |
show modem connect-speeds 12000 | 75 to 1200 bps |
The show modem connect-speeds command displays a log of connection speed statistics starting from the last time the access servers or router was power cycled or the clear modem counters command was issued. If you want to create a monthly report of the connection speeds achieved by the modems, issue the clear modem counters command at the beginning of the month and issue the show modem connect-speeds command at the end of the month.
The following display shows connection speed statistics up to 28000 bps:
router# show modem connect-speeds 28800 transmit connect speeds Mdm 9600 12000 14400 16800 19200 21600 24000 26400 28800 TotCnt * 1/0 0 0 0 0 3 4 6 37 23 74 * 1/1 0 0 3 1 0 4 9 41 20 80 * 1/2 0 0 2 0 1 3 10 37 26 82 1/3 1 0 0 0 0 3 15 35 7 62 1/4 0 0 0 0 4 2 8 20 13 49 * 1/5 0 0 4 0 1 0 4 38 17 65 * 1/6 0 0 2 1 0 1 9 32 11 57 * 1/7 1 0 2 0 0 5 10 31 18 67 * 1/8 0 0 0 1 1 1 10 42 11 68 1/9 0 0 2 1 2 4 4 30 23 67 1/10 0 0 0 0 0 2 5 26 22 56 * 1/11 0 0 0 0 3 1 16 38 17 76 * 1/12 0 0 0 0 0 3 7 40 12 62 1/13 0 0 0 1 2 3 11 20 14 51 1/14 0 0 2 0 0 2 7 26 12 51 1/15 0 0 1 1 1 2 6 29 25 65 1/16 2 0 2 0 1 5 10 37 15 73 1/17 0 0 0 0 0 2 10 33 22 67 1/18 0 0 2 2 0 2 12 17 25 61 * 1/19 2 0 3 0 1 2 9 35 20 74 1/20 0 0 2 2 2 2 8 28 21 65 * 1/21 0 1 2 0 1 2 5 23 21 58 * 1/22 0 0 1 0 1 1 5 27 21 56 * 1/23 0 0 2 0 0 4 8 30 15 60 Tot 6 1 32 10 24 60 204 752 431 1546 Tot % 0 0 2 0 1 3 13 48 27 receive connect speeds Mdm 9600 12000 14400 16800 19200 21600 24000 26400 28800 TotCnt * 1/0 0 0 1 0 1 2 9 35 25 74 * 1/1 0 0 3 0 1 3 10 42 18 80 * 1/2 0 0 2 0 1 4 8 40 26 82 1/3 1 0 0 0 0 1 10 36 14 62 1/4 0 0 1 0 2 2 8 22 8 49 * 1/5 0 1 4 0 0 0 9 32 17 65 * 1/6 0 0 2 0 0 0 7 33 14 57 * 1/7 0 0 2 1 1 0 6 39 18 67 * 1/8 0 0 0 0 1 0 11 43 12 68 1/9 1 0 3 0 0 0 8 33 22 67 1/10 0 0 0 0 1 1 6 31 17 56 * 1/11 0 0 0 1 1 1 14 43 16 76 * 1/12 0 0 0 0 0 0 5 43 12 62 1/13 0 0 0 0 0 2 10 26 13 51 1/14 0 0 2 1 0 0 5 27 14 51 1/15 0 0 1 0 1 2 3 36 22 65 1/16 1 0 3 1 2 0 8 37 20 73 1/17 0 0 0 0 0 0 8 36 22 67 1/18 0 1 1 0 0 2 4 30 20 61 * 1/19 0 0 3 2 1 1 6 42 18 74 1/20 0 1 2 1 2 1 2 37 18 65 * 1/21 0 0 3 3 1 2 2 28 18 58 * 1/22 0 0 1 0 1 0 5 32 16 56 * 1/23 0 0 2 0 0 1 8 35 13 60 Tot 3 3 36 10 17 25 172 838 413 1546 Tot % 0 0 2 0 1 1 11 54 26
The following display shows connection speed statistics up to 56000 bps:
router# show modem connect-speeds 56000 transmit connect speeds Mdm 40000 42000 44000 46000 48000 50000 52000 54000 56000 TotCnt 1/0 0 0 0 0 0 0 0 0 0 0 1/1 0 0 0 0 0 0 0 0 0 0 1/2 0 0 0 0 0 0 0 0 0 0 1/3 0 0 0 0 0 0 0 0 0 0 1/4 0 0 0 0 0 0 0 0 0 0 1/5 0 0 0 0 0 0 0 0 0 0 1/6 0 0 0 0 0 0 0 0 0 0 1/7 0 0 0 0 0 0 0 0 0 0 1/8 0 0 0 0 0 0 0 0 0 0 1/9 0 0 0 0 0 0 0 0 0 0 1/10 0 0 0 0 0 0 0 0 0 0 1/11 0 0 0 0 0 0 0 0 0 0 1/12 0 0 0 0 0 0 0 0 0 0 1/13 0 0 0 0 0 0 0 0 0 0 1/14 0 0 0 0 0 0 0 0 0 0 1/15 0 0 0 0 0 0 0 0 0 0 1/16 0 0 0 0 0 0 0 0 0 0 1/17 0 0 0 0 0 0 0 0 0 0 1/18 0 0 0 0 0 0 0 0 0 0 1/19 0 0 0 0 0 0 0 0 0 0 1/20 0 0 0 0 0 0 0 0 0 0 1/21 0 0 0 0 0 0 0 0 0 0 1/22 0 0 0 0 0 0 0 0 0 0 1/23 0 0 0 0 0 0 0 0 0 0 Tot 0 0 0 0 0 0 0 0 0 0 Tot % 0 0 0 0 0 0 0 0 0 receive connect speeds Mdm 40000 42000 44000 46000 48000 50000 52000 54000 56000 TotCnt 1/0 0 0 0 0 0 0 0 0 0 0 1/1 0 0 0 0 0 0 0 0 0 0 1/2 0 0 0 0 0 0 0 0 0 0 1/3 0 0 0 0 0 0 0 0 0 0 1/4 0 0 0 0 0 0 0 0 0 0 1/5 0 0 0 0 0 0 0 0 0 0 1/6 0 0 0 0 0 0 0 0 0 0 1/7 0 0 0 0 0 0 0 0 0 0 1/8 0 0 0 0 0 0 0 0 0 0 1/9 0 0 0 0 0 0 0 0 0 0 1/10 0 0 0 0 0 0 0 0 0 0 1/11 0 0 0 0 0 0 0 0 0 0 1/12 0 0 0 0 0 0 0 0 0 0 1/13 0 0 0 0 0 0 0 0 0 0 1/14 0 0 0 0 0 0 0 0 0 0 1/15 0 0 0 0 0 0 0 0 0 0 1/16 0 0 0 0 0 0 0 0 0 0 1/17 0 0 0 0 0 0 0 0 0 0 1/18 0 0 0 0 0 0 0 0 0 0 1/19 0 0 0 0 0 0 0 0 0 0 1/20 0 0 0 0 0 0 0 0 0 0 1/21 0 0 0 0 0 0 0 0 0 0 1/22 0 0 0 0 0 0 0 0 0 0 1/23 0 0 0 0 0 0 0 0 0 0 Tot 0 0 0 0 0 0 0 0 0 0 Tot % 0 0 0 0 0 0 0 0 0 0
Table 18 describes of the fields shown in the previous displays.
| Field | Description |
|---|---|
transmit connect speeds | Connection speeds for calls initiated by the system. |
Mdm slot/port | Specified slot and port number assigned to the modem. |
speed counters | The transmit and receive speed counters are 75, 300, 600, 1200, 2400, 4800, 7200, 9600, 12000, 14400, 16800, 19200, 21600, 24000, 26400, 28800, 31200, 33600, 32000, 34000, 36000, 38000, 40000, 42000, 44000, 46000, 48000, 50000, 52000, 54000, and 56000 bps. |
TotCnt | For the specified modem, the sum of the number of times a connection was initiated or received at one of the specified connection rates (75 to 56,000 bps). |
Tot | For all modems loaded in the system, the total number of times a call was initiated or received at the specified speed. |
Tot % | Percentage of the total number of calls that were initiated or received at the specified speed. |
receive connect speeds | Connection speeds for incoming calls. |
To display information about the modem cookie, use the show modem cookie EXEC command.
show modem cookieThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.2.
The following display shows output information for the show modem cookie command for a V.34 carrier card and two modem cards:
router# show modem cookie
Hex dump of modem board HW version info:
Slot 1:
Carrier card:
0000: 1802 0200 0000 0000 0000 0000 0000 0000
0010: 0000 0000 0000 0000 0000 0000 0000 0000
Modem Module 0:
0000: 0C01 3033 3030 3031 4D69 6372 6F63 6F6D
0010: 204D 4E50 3130 2056 3334 204D 6F64 656D
Modem Module 1:
0000: 0C01 3033 3030 3031 4D69 6372 6F63 6F6D
0010: 204D 4E50 3130 2056 3334 204D 6F64 656D
Table 19 describes significant fields in the previous display.
| Field | Description |
|---|---|
Slot 1: | The slot carrying the carrier and modem card. |
Carrier card: | Carrier card and its cookie parameters. |
Modem Module 0: | Modem card and its cookie parameters. |
To display the internal status of the call switching module for modems inside access servers or routers, use the show modem csm EXEC command.
show modem csm [slot/port | group number]
slot/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. The group number range is between 1 and 200. |
EXEC
This command first appeared in Cisco IOS Release 11.2.
The following example displays the call switching module information for modem 1/2 on a Cisco AS5200:
router# 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 20 describes significant 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 | Phone numbers for the dialing integrated modem and the remote modem. |
To display the modem history event status performed on a manageable modem or group of modems, use the show modem log EXEC command.
show modem log [slot/port | group number]
slot/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. The group number range is between 1 and 200. |
EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is display output for the show modem log command issued on a Cisco AS5300, which is loaded with MICA digital modems. See Table 21 for MICA modem field descriptions.
router# show modem log 1/0
Modem 1/0 Events Log:
01:54:02:Startup event:MICA Hex modem (Select)
Modem firmware = 2.0.0.9
01:54:02:RS232 event:
noRTS, noDTR, CTS, noDCD
01:54:02:RS232 event:
RTS, DTR, CTS, noDCD
01:54:02:RS232 event:
RTS, DTR, CTS, noDCD
01:54:02:RS232 event:
noRTS, DTR, CTS, noDCD
01:54:02:RS232 event:
RTS, DTR, CTS, noDCD
01:54:02:RS232 event:
noRTS, noDTR, CTS, noDCD
01:54:02:RS232 event:
RTS, DTR, CTS, noDCD
01:54:03:RS232 event:
RTS, DTR, CTS, noDCD
00:01:09: ISDN outgoing called number: 1000
00:01:04:RS232 event:
noRTS, DTR, CTS, noDCD
00:01:04:RS232 event:
RTS, DTR, CTS, noDCD
00:01:06:Modem State event:
State: Open
00:01:06:Modem State event:
State: Connect
00:01:06:Modem State event:
State: Link
00:00:54:Modem State event:
State: Training
00:00:32:Modem State event:
State: EC Correction
00:00:32:Modem State event:
State: Steady
00:00:32:RS232 event:
RTS, DTR, CTS, DCD
00:00:32:Static event:
Connect Protocol: LAP-M
Compression: (invalid#3)
Connected Standard: Bell212
TX,RX Symbol Rate: 3429, 3429
TX,RX Carrier Frequency: 1959, 1959
TX,RX Trellis Coding: 16, 16
Frequency Offset: 0 Hz
Round Trip Delay: 1 msecs
TX,RX Bit Rate: 16800, 16800
00:00:33:Dynamic event:
Sq Value: 7
Signal Noise Ratio: 35 dB
Receive Level: -8 dBm
Phase Jitter Frequency: 0 Hz
Phase Jitter Level: 0 degrees
Far End Echo Level: -73 dBm
Phase Roll: -98 degrees
Total Retrains: 0
EC Retransmission Count: 0
Characters received, transmitted: 0, 32
Characters received BAD: 0
PPP/SLIP packets received, transmitted: 0, 0
PPP/SLIP packets received (BAD/ABORTED): 0
EC packets transmitted, received: 0, 0
EC packets (Received BAD/ABORTED): 0
Table 21 describes the most useful fields in the previous MICA modem display.
| Field | Event State | Description |
|---|---|---|
Modem <slot/port> Events Log: |
| The modem for which log events are currently displayed. |
00:00:00: |
| Identifies the time elapsed since each MICA modem event was performed (for example, 01:02:41 means the modem event occurred 1 hour, 2 minutes, and 41 seconds ago). |
Startup event: |
| Type of specified MICA modem. |
Modem firmware: |
| Modem firmware version. |
RS232 event: |
| Detected modem signaling event. |
ISDN outgoing called number: |
| Outgoing ISDN phone number dialed by the specified MICA modem. |
Modem State Event | Current state of the MICA modem, which can be any of the following: | |
| Connect | Modem is connected to a remote host. |
| Open | Open modem event. |
| Link | Link protocol event occurred. |
| Training | Modem retraining event. |
| EC correction | Error correction frames transmitted or received. |
| Steady | Steady modem event. |
| Bad | Inoperable state, which is configured by the modem bad command. |
| Bad* | Inoperable state, which is configured by the modem startup-test command during initial power-up testing. |
| Reset | Modem is in reset mode. |
| D/L | Modem is downloading firmware. |
| Bad FW | Downloaded modem firmware is not operational. |
| Busy | Modem is out of service and not available for calls |
| Idle | Modem is ready for incoming and outgoing calls. |
Static event: | Current static event of the MICA modem, which can be any of the following: | |
| Connect protocol | Connection protocol used for the current session, which can be SYNC mode, ASYNC mode, ARA1.0, ARA2.0, LAP-M, or MNP. |
| Compression | Type of compression used for the current session, which can be None, V.42bis TX, V.42bis RX, V.42bis both, or MNP5 data compression. |
| Connected standard | Standards protocol used to connect, which can be V.21, Bell103, V.22, V.22bis, Bell212, V.23, V.32, V.32bis, V.32terbo, V.34, V.34+, or K56Flex 1.1. |
| TX, RX symbol rate | Symbol rate used to send samples to the line or receive samples off of the line. |
| TX, RX carrier frequency | Carrier frequency used by the remote service provider. |
| TX, RX trellis coding | Trellis coding received and transmitted. |
| Frequency offset | +/-32 in 1/8 Hx steps. |
| Round trip delay | Total round trip propagation delay of the link, which is expressed in milliseconds. |
| TX, RX bit rate | For RX, the bit rate from the remote service provider to the local service provider. For TX, the bit rate from the local service provider to the remote service provider. |
Dynamic event: | Current dynamic event of the MICA modem, which can be any of the following: | |
| Sq value | Signal quality value, which can be between 0 and 7 (0 is the worst possible quality). |
| Signal noise ratio | Expressed in decibels, which can be between 0 and 70 dB steps. |
| Receive level | Expressed in decibels, which can be between 0 and -128 dBm steps. |
| Phase jitter frequency | +/-32 in 1/8 Hz steps. |
| Phase jitter level | 0 to 90 degrees. |
| Far end echo level | 0 to -90 in dBm of far end echo level (that portion of the transmitted analog signal that has bounced off the remote modem's analog front end). |
| Phase roll | +/-32 in 1/8 Hz steps. |
| Total retrains | Count of total retrains. |
| EC retransmission | Count of total error correction retransmissions that occurred during the duration of the link. |
| Characters received, transmitted | Count of total characters received and transmitted. |
| Characters received BAD | A subset of the above total (Characters received, transmitted). Represents the total number of parity error characters. |
| PPP/SLIP packets received, transmitted | Total count of PPP/SLIP packets transmitted and received. This total could include all PPP/SLIP packets, including BAD/ABORTED packets. |
| PPP/SLIP packets received, (BAD/ABORTED) | Total count of the bad or aborted PPP/SLIP packets, which is a subset of the above (PPP/SLIP packets received, transmitted). |
| EC packets transmitted, received | Count of total error correction frames transmitted or received. This total could include all error correction packets, including BAD/ABORTED packets. |
| EC packets (received BAD/ABORTED) | Total count of the bad or aborted error correction packets, which is a subset of the above (EC packets transmitted, received). |
The following example shows the event log status for a V.34 Microcom manageable modem installed in a Cisco AS5200. To escape from the log display mode, press the keys Ctrl-c. See Table 23 for Microcom field descriptions.
router# show modem log 1/0
Modem 1/0 Events Log:
04:58:33: End connection event: Retransmits for EC block (TX/RX) = 86/33
Duration = 0:10:21, Number of TX/RX char = 100183/34307
Local Disc Reason = Remote Link Disc
Remote Disc Reason = Unknown
04:58:33: Modem State event: Idle
04:58:33: DTR event: DTR Off
04:58:33: RS232 event: RTS noDTR* CTS* DSR* noDCD* noRI* noTST*
04:58:21: DTR event: DTR On
04:58:21: RS232 event: RTS* DTR* CTS DSR noDCD noRI noTST
04:56:27: ISDN incoming calling number: 7039687666
04:56:27: ISDN incoming called number: 8366
04:56:21: Modem State event: Dialing/Answering
04:56:21: Modem State event: Incoming ring
04:56:21: Modem State event: Waiting for Carrier
04:56:21: RS232 event: RTS DTR CTS DSR noDCD noRI* noTST
04:56:09: Modem State event: Connected
04:56:09: Connection event: TX/RX Speed = 24000/26400, Modulation = V34
Direction = Answer, Protocol = reliable/LAPM, Compression = V42bis
04:56:09: RS232 event: RTS DTR CTS DSR DCD* noRI noTST
04:55:57: Modem Analog signal event: TX = -13, RX = -17, Signal to noise = 40
04:55:21: Modem State event: Disconnecting
04:55:21: End connection event: Retransmits for EC block (TX/RX) = 0/0
Duration = 0:00:46, Number of TX/RX char = 8911/7732
Local Disc Reason = Remote Link Disc
Remote Disc Reason = Unknown
04:55:23: Modem State event: Idle
04:55:23: DTR event: DTR Off
04:55:23: RS232 event: RTS noDTR* CTS* DSR* noDCD* noRI* noTST*
04:55:11: DTR event: DTR On
04:55:11: RS232 event: RTS DTR* CTS DSR noDCD noRI noTST
04:53:23: ISDN incoming calling number: 8477262725
04:53:23: ISDN incoming called number: 8366
04:53:22: Modem State event: Dialing/Answering
04:53:22: Modem State event: Incoming ring
04:53:22: RS232 event: RTS DTR CTS DSR noDCD noRI* noTST
04:53:10: Modem State event: Waiting for Carrier
04:53:10: RS232 event: RTS DTR CTS DSR noDCD noRI* noTST
04:52:58: Modem State event: Connected
04:52:58: Connection event: TX/RX Speed = 24000/24000, Modulation = V34
Direction = Answer, Protocol = reliable/LAPM, Compression = V42bis
04:52:58: Modem Analog signal event: TX = -13, RX = -19, Signal to noise = 40
04:52:58: RS232 event: RTS DTR CTS DSR DCD* noRI noTST
04:52:46: Modem State event: Retrain Initiated
04:52:34: Connection update event: TX/RX Speed = 24000/24000, Modulation = V34
04:52:34: Modem State event: Connected
04:52:22: Modem Analog signal event: TX = -13, RX = -17, Signal to noise = 40
04:52:12: RS232 event: RTS DTR CTS* DSR DCD noRI noTST
04:49:24: RS232 event: RTS DTR CTS* DSR DCD noRI noTST
04:49:12: RS232 event: RTS DTR CTS* DSR DCD noRI noTST
04:19:14: RS232 event: RTS DTR CTS* DSR DCD noRI noTST
03:46:29: Modem State event: Disconnecting
03:46:29: End connection event: Retransmits for EC block (TX/RX) = 6/8
Duration = 1:06:31, Number of TX/RX char = 114943/29854
Local Disc Reason = Remote Link Disc
Remote Disc Reason = Unknown
03:46:29: Modem State event: Idle
03:46:29: DTR event: DTR Off
03:46:29: DTR event: DTR On
03:46:29: RS232 event: RTS DTR* CTS* DSR* noDCD* noRI* noTST*
03:45:35: ISDN incoming calling number: 5124745911
03:45:35: ISDN incoming called number: 8366
03:45:29: Modem State event: Dialing/Answering
03:45:29: Modem State event: Incoming ring
03:45:29: Modem State event: Waiting for Carrier
Table 22 describes the most useful fields in the previous Microcom modem display.
| Field | Description |
|---|---|
Modem <slot/port> Events Log: | The modem for which log events are currently displayed. |
00:00:00: | Identifies the time elapsed since each Microcom modem event was performed (for example, 01:02:41 means the modem event occurred 1 hour, 2 minutes, and 41 seconds ago). |
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 event log status for a manageable modem. It also 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). To escape from the log display mode, press the keys Ctrl-c.
router# 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 23 describes the most useful fields in the previous example.
| 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. |
You can use the master indexes or search online to find documentation of related commands.
show modem operational-status
show modem configuration
show modem mica
To display a snapshot of all the firmware versions running on all the modems in the access server, use the show modem mapping EXEC command. This command also shows the source location of each version of firmware (for example, running out of Flash, boot Flash, or bundled with Cisco IOS software).
show modem mappingThis command has no additional keywords or arguments.
EXEC
This command first appeared in Cisco IOS Release 11.3 T.
This command is useful for managing and monitoring multiple versions of modem firmware running in an access server.
Modem firmware can reside in the access server's Flash, boot Flash, or bundled with the Cisco IOS software.
Firmware can also be copied from a local TFTP server to the onboard modems. For the Cisco AS5300, issue the copy tftp flash command followed by the copy flash modem command. The Cisco AS5300 stores individual firmware files that are not bundled with the Cisco IOS software in Flash memory. For the Cisco AS5200, issue the copy tftp bootflash command followed by the copy bootflash modem command. The Cisco AS5200 stores individual firmware files not bundled with the Cisco IOS software in boot Flash memory.
All the modems in a single MICA modem module run the same version of firmware (for example, modems 1/0 through 1/5 in module 0). However, different versions of modem firmware can exist between different modem modules (for example, module 0 and module 1).
Individual firmware files cannot be erased from Flash or boot Flash memory. The entire contents of Flash or boot Flash memory must be deleted during the erase operation. If you do this, be sure to backup your Cisco IOS software and running configuration before you erase your system's Flash or boot Flash memory.
The following is sample display output for the show modem mapping EXEC command. This access server is loaded with MICA and Microcom modems. Table 24 describes each field in the display.
router# show modem mapping
Slot 1 has Mica Carrier card.
Modem Firmware Firmware
Module Numbers Rev Filename
0 1/0 - 1/5 2.0.1.7 IOS-Default
1 1/6 - 1/11 2.0.1.7 IOS-Default
2 1/12 - 1/17 2.0.1.7 IOS-Default
3 1/18 - 1/23 2.0.1.7 IOS-Default
4 1/24 - 1/29 2.0.1.7 IOS-Default
5 1/30 - 1/35 2.0.1.7 IOS-Default
6 1/36 - 1/41 2.0.1.7 IOS-Default
7 1/42 - 1/47 2.2.3.0 flash:mica-modem-portware.2.2.3.0.bin
Slot 2 has Microcom Carrier card.
Module Firmware Firmware
Mdm Number Rev Filename
2/0 0 3.2(10) flash:mcom-modem-code-3.2.10.bin
2/1 0 3.1(30) IOS-Default
2/2 0 3.1(30) IOS-Default
2/3 0 3.1(30) IOS-Default
2/4 0 3.1(30) IOS-Default
2/5 0 3.1(30) IOS-Default
2/6 0 3.1(30) IOS-Default
2/7 0 3.1(30) IOS-Default
2/8 0 3.1(30) IOS-Default
2/9 0 3.1(30) IOS-Default
2/10 0 3.1(30) IOS-Default
2/11 0 3.1(30) IOS-Default
2/12 1 3.1(30) IOS-Default
2/13 1 3.1(30) IOS-Default
2/14 1 3.1(30) IOS-Default
2/15 1 3.1(30) IOS-Default
2/16 1 3.1(30) IOS-Default
2/17 1 3.1(30) IOS-Default
2/18 1 3.1(30) IOS-Default
2/19 1 3.1(30) IOS-Default
2/20 1 3.1(30) IOS-Default
2/21 1 3.1(30) IOS-Default
2/22 1 3.1(30) IOS-Default
2/23 1 3.1(30) IOS-Default
IOS Bundled Firmware Information:
Mica Boardware Version : 1.3.4.5
Mica Portware Version : 2.0.1.7
Microcom Firmware Version : 3.1.30
Microcom DSP Software Version : 1.01
Firmware files on Boot Flash:
Firmware-file Version Firmware-Type
============= ======= =============
Firmware files on System Flash:
Firmware-file Version Firmware-Type
============= ======= =============
flash:mcom-modem-code-3.2.10.bin 3.2.10 Microcom F/W and DSP
flash:mica-modem-portware.2.2.3.0.bin 2.2.3.0 Mica Portware
Table 24 describes the most useful fields in the previous example.
| Field | Description |
|---|---|
Slot x has card | Type of modem card inserted in the specified slot. |
Module | Modem module number that corresponds with the specified modem or group of modems. |
Modem numbers | Range of specified modems, which are displayed as slot/port. |
Mdm | Specified modem number, which is displayed as slot/port. |
Firmware Rev | Version of firmware running on the modem or module. Each time the access server reloads, this version of firmware is copied to the specified modem or range of modems. The field display "Unknown" is displayed when a modem is presently upgrading its firmware. |
Firmware Filename | Location or filename of the firmware that is downloaded to the modems. A firmware file located in Flash memory begins as flash:filename. A file located in boot Flash memory begins as bootflash:filename. If the firmware is embedded or bundled in the Cisco IOS image, the field IOS-Default appears. On the Cisco AS5300, firmware files are stored in the system Flash memory. On the Cisco AS5200, firmware files are stored in boot Flash memory. |
IOS Bundled Firmware Information: | List of firmware versions that are bundled with the Cisco IOS software running on the system. If the firmware versions in this section are more current than the firmware running on your modems, you should upgrade the running modem firmware. |
Firmware files on Boot Flash: | List of current firmware located on boot Flash memory. The categories are Firmware-file, Version, and Firmware-Type. |
Firmware files on System Flash: | List of current firmware located on the system Flash memory. The categories are Firmware-file, Version, and Firmware-Type. |
You can use the master indexes or search online to find documentation of related commands.
copy tftp flash
copy flash modem
copy tftp bootflash
copy bootflash modem
To display information about MICA digital modems, use the show modem mica EXEC command.
show modem mica {slot/port | all | slot [number]}
slot/port | Specifies the display for a single modem in a MICA digital modem board. |
all | Displays output for all the MICA modems in the system. |
slot number | Displays output for a particular slot, which is mainly used for debugging purposes. The optional number variable allows you to specify a slot number. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
Each MICA modem has its own data channel port, which is tied to its own TTY line. For example, modem 0/1 is tied to TTY line 2. To display data channel information for a single MICA modem, issue the show modem mica slot/port command.
All the modems on each MICA modem card share three pseudo channels for modem management functions, for example the DC session channel, status polling channel, and controlling channel. To view statistics for each modem management channel, issue the show modem mica all command. The first channel you see displayed is the status polling channel (shown as SLOT/PORT (0/61) TTYNUM=-1 (MM Status Port)). The second displayed channel is the DC session channel (shown as SLOT/PORT (0/60) TTYNUM=-1 (MM DC Port)). The third displayed port is the controlling channel (shown as SLOT/PORT (0/62) TTYNUM=-1 (Control Port)). No TTY lines are associated with the modem management ports, as indicated by the field display TTYNUM=-1. Finally, an extensive list of all the data channels for each MICA modem is displayed.
The following example displays the data port channel for modem 0/1. For a description of the significant fields in this display, see Table 25.
router# show modem mica 0/1 SLOT/PORT (0/1) TTYNUM=2 (Data Port) Modem hardware state: CTS noDSR DTR RTS RX Queue count is 0 TX Queue count is 1 TTY outpak is 0 TX pending FALSE RX pending FALSE RX ring with 4 entries at 0x40093184, (RX_AVAILABLE) rx_count=4 Rx_pak_head=0x6082B030 Rx_BD_head=0x4009318C Rx_BD_base=0x40093184 INPUT count = 12 00 pak=0x60753064 buf=0x40067514 status=8000 pak_size=0 01 pak=0x6082B030 buf=0x4013F948 status=8000 pak_size=0 02 pak=0x60A4323C buf=0x4021A214 status=8000 pak_size=0 03 pak=0x60A32DA0 buf=0x40208E9C status=8800 pak_size=0 TX ring with 4 entries at 0x400943F0, (TX_READY) tx_count = 0 tx_head = 0x400943F0 , head_txp = 0x0 Tx_bd_tail=0x400943F0 , Tx_bd_base=0x400943F0 OUTPUT count = 12 00 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 01 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 02 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 03 pak=0x0000000 buf=0x0000000 status=0800 pak_size=0
The following example displays sample output for the show modem mica all command. For a description of the significant fields in this display, see Table 25.
router# show modem mica all SLOT/PORT (0/60) TTYNUM=-1 (MM DC Port) Modem hardware state: CTS DSR DTR RTS Board is running boardware version 1.3.2.0 Boardware redirect state = DISABLE size=4520 location=0x400968A8 Board INTR ON RX[0]=0x0 RX[1]=0x0 RX[2]=0x0 RX[3]=0x0 TX[0]=0x0 TX[1]=0x0 TX[2]=0x0 TX[3]=0x0 Next Modem service is 0 Throttle count is 0, Throttle state is OFF Data channel no buffer count is 0 Boardware crash count is 0 No crash dump available Board state is RUNNING Modules state are: R R R R R R R R Modules crash count are: 0 0 0 0 0 0 0 0 Interval timer is 16 RX Queue count is 0 TX Queue count is 0 TTY outpak is 0 TX pending FALSE RX pending FALSE RX ring with 4 entries at 0x400938E4, (RX_AVAILABLE) rx_count=4 Rx_pak_head=0x60761CE0 Rx_BD_head=0x400938F4 Rx_BD_base=0x400938E4 INPUT count = 2 00 pak=0x60761920 buf=0x4009025C status=8000 pak_size=0 01 pak=0x60761740 buf=0x4008FBA4 status=8000 pak_size=0 02 pak=0x60761CE0 buf=0x40090FCC status=8000 pak_size=0 03 pak=0x6084311C buf=0x40150608 status=8800 pak_size=0 TX ring with 4 entries at 0x40094B50, (TX_READY) tx_count = 0 tx_head = 0x40094B60 , head_txp = 0x0 Tx_bd_tail=0x40094B60 , Tx_bd_base=0x40094B50 OUTPUT count = 2 00 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 01 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 02 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 03 pak=0x0000000 buf=0x0000000 status=0800 pak_size=0 SLOT/PORT (0/61) TTYNUM=-1 (MM Status Port) Modem hardware state: CTS DSR DTR RTS Board is running boardware version 1.3.2.0 Boardware redirect state = DISABLE size=4520 location=0x400968A8 Board INTR ON RX[0]=0x0 RX[1]=0x0 RX[2]=0x0 RX[3]=0x0 TX[0]=0x0 TX[1]=0x0 TX[2]=0x0 TX[3]=0x0 Next Modem service is 0 Throttle count is 0, Throttle state is OFF Data channel no buffer count is 0 Boardware crash count is 0 No crash dump available Board state is RUNNING Modules state are: R R R R R R R R Modules crash count are: 0 0 0 0 0 0 0 0 Interval timer is 16
The following example displays sample output for the show modem mica slot command. For a description of the significant fields in this display, see Table 25.
router# show modem mica slot SLOT/PORT (0/62) TTYNUM=-1 (Control Port) Modem hardware state: CTS DSR DTR RTS Board is running boardware version 1.3.2.0 Boardware redirect state = DISABLE size=4520 location=0x400968A8 Board INTR ON RX[0]=0x0 RX[1]=0x0 RX[2]=0x0 RX[3]=0x0 TX[0]=0x0 TX[1]=0x0 TX[2]=0x0 TX[3]=0x0 Next Modem service is 0 Throttle count is 0, Throttle state is OFF Data channel no buffer count is 0 Boardware crash count is 0 No crash dump available Board state is RUNNING Modules state are: R R R R R R R R Modules crash count are: 0 0 0 0 0 0 0 0 Interval timer is 16 RX Queue count is 0 TX Queue count is 0 TTY outpak is 0 TX pending FALSE RX pending FALSE RX ring with 4 entries at 0x40093924, (RX_AVAILABLE) rx_count=4 Rx_pak_head=0x6075D4D8 Rx_BD_head=0x40093934 Rx_BD_base=0x40093924 INPUT count = 1366 00 pak=0x6075CD58 buf=0x4008A2BC status=8000 pak_size=0 01 pak=0x6075D6B8 buf=0x4008C454 status=8000 pak_size=0 02 pak=0x6075D4D8 buf=0x4008BD9C status=8000 pak_size=0 03 pak=0x6075D2F8 buf=0x4008B6E4 status=8800 pak_size=0 TX ring with 4 entries at 0x40094B90, (TX_READY) tx_count = 0 tx_head = 0x40094BA0 , head_txp = 0x0 Tx_bd_tail=0x40094BA0 , Tx_bd_base=0x40094B90 OUTPUT count = 1894 00 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 01 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 02 pak=0x0000000 buf=0x0000000 status=0000 pak_size=0 03 pak=0x0000000 buf=0x0000000 status=0800 pak_size=0
The first channel you see displayed is the status polling channel (shown as SLOT/PORT (0/61) TTYNUM=-1 (MM Status Port)). The second displayed channel is the DC session channel (shown as SLOT/PORT (0/60) TTYNUM=-1 (MM DC Port)). The third displayed port is the controlling channel (shown as SLOT/PORT (0/62) TTYNUM=-1 (Control Port)). No TTY lines are associated with the modem management ports, as indicated by the field display TTYNUM=-1. Finally, an extensive list of all the data channels for each individual MICA modem is displayed. Table 25 describes the most useful fields in the previous example.
| Field | Description |
|---|---|
SLOT/PORT (0/61) TTYNUM=-1 (MM Status Port) | Status polling channel. |
SLOT/PORT (0/60) TTYNUM=-1 (MM DC Port) | DC session channel. |
SLOT/PORT (0/62) TTYNUM=-1 (Control Port) | Controlling pseudo channel. |
Modem hardware state: | State of the modem hardware, which can be CTS, DSR, DTR, and RTS. |
Board is running boardware version | Version of boardware. |
Boardware crash count | Number of times the board has crashed since the system was last power cycled. |
Modules state are: | State of the modem modules. R means that the specified modem module is running. |
Modules crash count are: | Number of times each modem module has crashed since the system was last power cycled. |
INPUT count = | Count of packets received since the last power cycle. |
OUTPUT count = | Count of packets transmitted since the last power cycle. |
You can use the master indexes or search online to find documentation of related commands.
show modem operational-status
show modem configuration
show modem log
To display the current modem operational status for MICA digital modems loaded inside an access server or router, use the show modem operational-status EXEC command.
show modem operational-status [slot/port]
slot/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. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The following example uses the show modem operational-status command to display the operational status for the modem 0/1 in a Cisco AS5300. The modem resides in slot 0 and has been assigned to port number 1. For a description of the significant fields in this display, see Table 26.
router> show modem operational-status 0/1
Modem(0/1) Operational-Status:
Parameter #0 Disconnect Reason Info: (0xDF00)
Type (=6 ): Tx (host to line) data flushing, OK
Class (=31): Requested by host
Reason (=0 ): non-specific host disconnect
Parameter #1 Connect Protocol: LAP-M
Parameter #2 Compression: V.42bis both
Parameter #3 EC Retransmission Count: 0
Parameter #4 Self Test Error Count: 0
Parameter #5 Call Timer: 27 secs
Parameter #6 Total Retrains: 0
Parameter #7 Sq Value: 4
Parameter #8 Connected Standard: V.34+
Parameter #9 TX,RX Bit Rate: 31200, 31200
Parameter #11 TX,RX Symbol Rate: 3429, 3429
Parameter #13 TX,RX Carrier Frequency: 1959, 1959
Parameter #15 TX,RX Trellis Coding: 16, 16
Parameter #16 TX,RX Preemphasis Index: 0, 0
Parameter #17 TX,RX Constellation Shaping: Active, Active
Parameter #18 TX,RX Nonlinear Encoding: Active, None
Parameter #19 TX,RX Precoding: Active, Active
Parameter #20 TX,RX Xmit Level Reduction: 0, 0 dBm
Parameter #21 Signal Noise Ratio: 40 dB
Parameter #22 Receive Level: -8 dBm
Parameter #23 Frequency Offset: 0 Hz
Parameter #24 Phase Jitter Frequency: 0 Hz
Parameter #25 Phase Jitter Level: 0 degrees
Parameter #26 Far End Echo Level: -65 dBm
Parameter #27 Phase Roll: 4 degrees
Parameter #28 Round Trip Delay: 1 msecs
Parameter #30 Characters received, transmitted: 8650752, 720896
Parameter #32 Characters received BAD: 3801088
Parameter #33 PPP/SLIP packets received, transmitted: 0, 0
Parameter #35 PPP/SLIP packets received (BAD/ABORTED): 0
Parameter #36 EC packets transmitted, received: 0, 65536
Parameter #38 EC packets (Received BAD/ABORTED): 327680
Line Shape:
| Field | Description |
|---|---|
Modem (slot/port) | Specified modem. |
Parameter #1 Connect Protocol: | Connect protocol for the current session, which can be SYNC mode, ASYNC mode, ARA1.0, ARA2.0, LAP-M, or MNP. |
Parameter #2 Compression: | Compression protocol used for the current connection, which can be None, V.42bis TX, V.42bis RX, V.42bis both, or MNP5 data compression. |
Parameter #3 EC Retransmission Count: | Count of total error correction retransmissions that occurred during the duration of the link. |
Parameter #4 Self Test Error Count: | Total errors generated during a self test run. |
Parameter #5 Call Timer: | In seconds. |
Parameter #6 Total Retrains: | Count of total retrains. |
Parameter #7 Sq Value: | 0 through 7, where 0 is the worst. |
Parameter #8 Connected Standard: | Standard connect protocol, which can be V.21, Bell03, V.22, V.22bis, Bell212, V.23, V.32, V.32bis, V.32terbo, V.34, V.34+, or K56Flex. |
Parameter #9 TX,RX Bit Rate: | For TX, bit rate from the local SP to the remote SP. For RX, bit rate from the remote SP to the local SP. |
Parameter #11 TX,RX Symbol Rate: | For TX, symbol rate used to receive sample off of the line. For RX, symbol rate used to send samples to the line. |
Parameter #13 TX,RX Carrier Frequency: | For TX, carrier frequency used by the local SP. For RX, carrier frequency used by the remote SP. |
Parameter #15 TX,RX Trellis Coding: | 32, 64, or no trellis used. |
Parameter #16 TX,RX Preemphasis Index: | 0 through 10. |
Parameter #17 TX,RX Constellation Shaping: | None or active. |
Parameter #18 TX,RX Nonlinear Encoding: | None or active. |
Parameter #19 TX,RX Precoding: | None or active. |
Parameter #20 TX,RX Xmit Level Reduction: | 0 to 15 in dBm of reduction. |
Parameter #21 Signal Noise Ratio: | 0 to 70 in dB steps. |
Parameter #22 Receive Level: | 0 to -128 in dBm steps. |
Parameter #23 Frequency Offset: | +/-32 in 1/8 Hz steps. |
Parameter #24 Phase Jitter Frequency: | +/-32 in 1/8 Hz steps. |
Parameter #25 Phase Jitter Level: | 0 to 90 degrees. |
Parameter #26 Far End Echo Level: | 0 to -90 in dBm of far end echo level (that portion of the transmitted analog signal which has bounced off of the remote modem's analog front end). |
Parameter #27 Phase Roll: | +/-32 in 1/8 Hz steps. |
Parameter #28 Round Trip Delay: | Total round trip propagation delay of the link. |
Parameter #30 Characters received, transmitted: | Count of total characters received and transmitted. |
Parameter #32 Characters received BAD: | Total number of parity errored characters, which is a subset of parameter #30. |
Parameter #33 PPP/SLIP packets received, transmitted: | Total count of PPP/SLIP packets transmitted and received. This total could include all PPP/SLIP packets, including BAD/ABORTED packets. |
Parameter #35 PPP/SLIP packets received (BAD/ABORTED): | Total count of the bad or aborted PPP/SLIP packets, which is a subset of the above (PPP/SLIP packets received, transmitted). |
Parameter #36 EC packets transmitted, received: | Count of total error correction frames transmitted or received. This total could include all error correction packets, including BAD/ABORTED packets. |
Parameter #38 EC packets (Received BAD/ABORTED): | Total count of the bad or aborted error correction packets, which is a subset of the above (EC packets transmitted, received). |
You can use the master indexes or search online to find documentation of related commands.
show modem configuration
show modem mica
show modem log
To display a high-level report for all manageable modems dialing into and out of the network, use the show modem summary EXEC command.
show modem summaryThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is sample display output for the show modem summary command:
router# show modem summary
Incoming calls Outgoing calls Busied Failed No Succ Usage Succ Fail Avail Succ Fail Avail Out Dial Ans Pct. 17% 1547 64 11 0 0 11 0 3 3 96%
Table 27 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. |
To display the modem test log, use the show modem test EXEC command.
show modem testThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.2.
The modem test log displays the results of the modem diagnostics test, which is issued with the modem autotest global configuration command.
The following display shows output information for the show modem test command for a V.34 modem card:
router# show modem test Date Time Modem Test Reason State Result 5/15 07:25:17 AM 1/0 Back-To-Back TIME INTERVAL Idle FAIL 5/15 07:25:17 AM 1/1 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/2 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/3 Back-To-Back TIME INTERVAL Idle FAIL 5/15 07:25:17 AM 1/4 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/5 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/6 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/7 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/8 Back-To-Back TIME INTERVAL Idle PASS 5/15 07:25:17 AM 1/9 Back-To-Back TIME INTERVAL Idle PASS ...
Table 28 describes the field in the previous display.
| Fields | Descriptions |
|---|---|
Date | Date the back-to-back test occurred for the specified modem. |
Time | Time the test occurred. |
Modem | Specified modem that performed a back-to-back test. |
Test | Operation performed by the specified modem. |
Reason | Reason the modem performed a back-to-back test. |
State | Current operational state of the modem. |
Result | Result of the back-to-back test for the specified modem. |
To display version information about the modem firmware, controller and DSP code (for 56K modems only), and boot code, use the show modem version EXEC command.
show modem versionThis command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.2.
This command is very useful for verifying the version of modem firmware running on the system before or after a modem firmware upgrade.
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 in a Cisco AS5200.
If the version number is displayed as 0.0.0, verify that out-of-band 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 cards for basic 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 29 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 module 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. |
To display the configuration and connection status for one or more modem pools, use the show modem-pool EXEC command.
show modem-pool [name]
name | (Optional) Modem pool name. |
EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The counters display by the show modem-pool command are cleared with the clear counters (async) command.
In the following example, two modem pools are set up: v90service and v34service. Each pool contains one DNIS number: 1234 and 5678. Each DNIS number is allowed a maximum of 48 simultaneous connections. A total of 96 modems are assigned to the modem pools: 48 and 48. Modems that are left unassigned to modem pools are automatically put into the default modem pool (displayed as System-def-Mpool). The default pool is empty in this example.
as5300# show modem-pool modem-pool: System-def-Mpool modems in pool: 0 active conn: 0 0 no free modems in pool modem-pool: v90service modems in pool: 48 active conn: 46 8 no free modems in pool called_party_number: 1234 max conn allowed: 48, active conn: 46 8 max-conn exceeded, 8 no free modems in pool modem-pool: v34service modems in pool: 48 active conn: 35 0 no free modems in pool called_party_number: 5678 max conn allowed: 48, active conn: 35 0 max-conn exceeded, 0 no free modems in pool
Table 30 describes the modem-pool fields.
| Field | Description |
|---|---|
modem-pool | Name of the modem pool. In the previous example, there are three modem pools configured: System-def-Mpool, v34service, and v90service. To set modem pool name, see the clear counters (async) command. All the modems not assigned to a modem pool are automatically assigned to the system default pool (displayed as System-def-Mpool). |
modems in pool | Number of modems assigned to the modem pool. To assign modems to a pool, see the clear counters (async) command. |
active conn | Number of simultaneous active connections for the specified modem pool or called party DNIS number. |
no free modems in pool | Number of times incoming calls were rejected because there were no more free modems in the pool to accept the call. |
called_party_number | Specified called party DNIS number. This is the number that the remote clients use to dial into the access server. You can have more than one DNIS number per modem pool. To set the DNIS number, see the called-number command. |
max conn allowed | Maximum number of modems that a called party DNIS number can use, which is an overflow protection measure. To set this feature, see the called-number command. |
max-conn exceeded | Number of times an incoming call using this called party DNIS number was rejected because the max-conn number parameter specified by the called-number command was exceeded. |
You can use the master indexes or search online to find documentation of related commands.
called-number
clear modempool-counters
modem-pool
pool-range
To diagnose an integrated modem that may not be functioning properly, use the test modem back-to-back EXEC command.
test modem back-to-back first-slot/port second-slot/port
first-slot/port | Slot and modem number of the first test modem. Remember to include the forward slash (/) when entering this variable. |
second-slot/port | Slot and modem number of the second test modem. Remember to include the forward slash (/) when entering this variable. |
Disabled
EXEC
This command first appeared in Cisco IOS Release 11.2.
Use this command to perform back-to-back testing of two modems. You might need to enable this command on several different combinations of modems to determine which one is not functioning properly.
The following example performs a back-to-back modem test between modem 2/0 and modem 2/1 and removes modem 2/1 (which is associated with TTY line 26) from all dial-in and dial-out services:
router# test modem back-to-back 2/0 2/1 back2back 2/0 2/1 Repetitions (of 10-byte packets) [1]: router# %MODEM-5-B2BCONNECT: Modems (2/0) and (2/1) connected in back-to-back test: CONNECT9600/REL-MNPM %MODEM-5-B2BMODEMS: Modems (2/0) and (2/1) completed back-to-back test: success/packets = 2/2
You can use the master indexes or search online to find documentation of related commands.
modem bad
Posted: Thu May 25 10:22:01 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.