Table Of Contents
show modem
show modem at-mode
show modem bundled-firmware
show modem call-stats
show modem calltracker
show modem configuration
show modem connect-speeds
show modem cookie
show modem csm
show modem log
show modem mapping
show modem mica
show modem operational-status
show modem-pool
show modem summary
show modem test
show modem version
show modemcap
show nbf cache
show nbf sessions
show modem
To display a high-level performance report for all the modems or a single modem inside Cisco access servers, use the show modem command in EXEC mode.
show modem [slot/port | group number]
Syntax Description
slot/port
|
(Optional) Location of a slot and modem port. Remember to include the forward slash (/) when entering this variable.
|
group number
|
(Optional) Assigns the group to which a specified modem belongs. The group number range is from 1 to 200.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.1(5)T
|
This command was enhanced to display information about modems on the Cisco 3600 series routers that support the V.110 standard.
|
12.2(11)YT
|
This command was enhanced to display information about digital modems on the Cisco 3600 and 3700 series routers that support the V.92 and V.44 standards.
|
12.2(15)T
|
The Cisco IOS Release 12.2(11)YT enhancements were integrated into Cisco IOS Release 12.2(15)T.
|
Examples
The following is sample output from the show modem command for two V.34 modem cards inserted in a Cisco 3600 router:
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 is sample output from the show modem command for two V.110 modem cards inserted in a Cisco 3600 router:
Inc calls Out calls Busied Failed No Succ
Mdm Usage Succ Fail Succ Fail Out Dial Answer Pct.
The following is sample output from the show modem command for a Cisco 3600 series router:
* - Modem has an active call
B - Modem is marked bad and cannot be used for taking calls
b - Modem is either busied out or shut-down
Avg Hold Inc calls Out calls Busied Failed No Succ
Mdm Time Succ Fail Succ Fail Out Dial Answer Pct.
* 0/0 00:21:01 132 0 0 0 0 0 0 100%
* 0/1 2d01h 1 0 0 0 0 0 0 100%
0/2 00:00:34 130 0 0 0 0 0 0 100%
* 0/3 00:21:53 126 1 0 0 0 0 0 99%
* 0/4 2d01h 1 0 0 0 0 0 0 100%
0/5 00:00:33 131 0 0 0 0 0 0 100%
* 0/6 00:21:12 131 0 0 0 0 0 0 100%
0/7 00:00:34 131 0 0 0 0 0 0 100%
b 0/8 00:00:00 0 0 0 0 0 0 0 0%
b 0/9 00:00:00 0 0 0 0 0 0 0 0%
b 0/29 00:00:00 0 0 0 0 0 0 0 0%
Total: 00:18:25 783 1 0 0 0 0 0 99%
Table 66 describes the significant fields shown in the previous displays of the show modem command.
Table 66 show modem Field Descriptions
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 Digital Signal Processor (DSP) code, which supports K56flex, is not configured. The modem will revert to transmitting at 33.6 kbps.
• D—Modem is 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 in to 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 3600 router. 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 67 for a description of the fields displayed by the show modem command with slot and port designators.
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 is sample output for a basic V.34 modem module. Notice that unavailable fields are marked with dashes (-):
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, C3600 Non-Manageable Modem
Firmware (Boot) Rev: 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 is sample output from the show modem slot/port command for V.110 modem cards:
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 - - - - - -
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 67 for a description of the fields displayed by this modem card.
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
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 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
The following is sample output from the show modem slot/port command for digital modems on a Cisco 3600 series router that supports the V.92 and V.44 modem standards:
Mdm Typ Status Tx/Rx G Duration TX RX RTS CTS DSR DCD DTR
3/0 V90/92 Idle 46666/31200 1 00:01:30 - - x
Modem 3/0 [line 97], Async97, TTY97
MICA-6DM Firmware: CP ver 2910 - 7/13/2001, SP ver 2910 - 7/13/2001.
Modem config: Incoming and Outgoing
Protocol: LAPM, Compression: V44
Last clearing of "show modem" counters: never
1 incoming completes, 1 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
0 TDM errors, 0 speed shifts (up/dn - 0/0), 0 retrains (hi/lo - 0/0)
Table 67 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.
Table 67 show modem slot/port Field Descriptions
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, K56Flx, and V90/92.
|
Status
|
Current status of the modem. Possible values are as follows:
• Conn—Modem is connected to a remote host.
• B—Inoperable state, which is configured by the modem bad command.
• B*—Inoperable state, which is configured by the modem startup-test command during initial power-up testing.
• b—Modem is busied out. This can be manually configured by the modem busyout line configuration command.
• 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.
|
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 (in hours: minutes: seconds) of the current 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 device transmits data to the DCE device.
• RX—Receive Data. The DCE device receives data from the DTE device.
• RTS—Request To Send. The DTE device signals to the DCE device that the DTE device accepts data into its buffers.
• CTS—Clear To Send. The DCE device signals to the DTE device that the DCE device accepts data into its buffers.
• DSR—Data Set Ready. The modem is ready to start communication.
• DCD—Data Carrier Detect. The DCE device indicates to the DTE device that a call is present and established with a remote modem. Dropping the DCD function terminates the session.
• DTR—Data Terminal Ready. The DTE device indicates to the DCE device that it accepts calls.
|
Firmware
|
Installed modem firmware.
|
Modem config
|
Current modem configuration, which includes the fields Incoming, Outgoing, Incoming and Outgoing, Unknown, Protocol, and Compression.
|
Protocol
|
Protocol the modem is running such as Normal, Direct, reliable/Microcom Network Protocol (MNP)4, and reliable/LAPM (Link Access Procedure for Modems).
|
Compression
|
Compression algorithm running on the modem, such as None, V42bis, V.44, 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.
• Incoming completes and failures—Total number of incoming connection requests that the modem answered and successfully or unsuccessfully connected with the remote DCE device.
• Outgoing completes and failures—Total number of outgoing connection requests that the modem dialed and successfully or unsuccessfully connected with the remote DCE device.
• Failed dial attempts—Number of times the modem attempted to dial out but the call failed to leave the modem.
• Ring no answers—Number of times the integrated modem detected ringing but did not answer the incoming call.
• Busied outs—Number of times the integrated modem was intentionally taken out of service (for example, the modem busyout command was enabled on the modem).
• No dial tones—Number of times the dial-out attempt failed because the modem failed to detect a dial tone.
• Dial timeouts—Number of times the modem has timed out while attempting to dial.
• Watchdog timeouts—Number of times the modem internal watchdog timer has expired.
• No carriers—Number of times the modem disconnected because no carrier was present.
• Link failures—Number of times the modem has detected a link failure.
• Resets—Number of times the modem has been reset.
• Recover oob—Number of times the out-of-band feature has been cleared and reinitialized.
• Protocol timeouts and errors—Number of times the modem protocol failed to make a call connection.
• Lost events—Number of incomplete modem events performed by the modem.
• MOH—Indicates V.92 Modem on Hold (MOH), which allows suspending a modem session to answer an incoming voice call or to place an outgoing call while engaged in a modem session.
|
Modulation type
|
Modulation type, which can be any of the following values: Bel103, Bel212, V21, V22, V22bis, V23, V32, V32bis, VFC, V34, V17, V27, V33, K56Flx, and V90/92.
|
Protocol type
|
Protocol the modem is running such as Normal, Direct, reliable/MNP4, and reliable/LAPM.
|
Transmit Speed Counters:
|
List of connection speeds that were sent by the modem.
|
Receive Speed Counters:
|
List of connection speeds that were received by the modem.
|
Connection Speeds # of connections
|
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 56000 bits per second (bps). The number of successful connections is displayed directly beneath the connection speed identifier. For example, the following output shows that three connections were made at 56 kbps:
Connection Speeds 56000 # of connections 3
|
The following example shows the output for modem group 1, which comprises modem 1/0 through modem 1/23. The report is self explanatory.
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
Related Commands
Command
|
Description
|
show modem version
|
Displays version information about the modem firmware, controller and DSP code (for 56-kbps modems only), and boot code.
|
show modem at-mode
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 command in EXEC mode.
show modem at-mode
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Examples
The report from the show modem at-mode command is self-explanatory. 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:
show modem bundled-firmware
To display a a list of available modem firmware running in a Cisco AS5800 access server, use the show modem bundled-firmware command in EXEC mode.
show modem bundled-firmware
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3(5)AA
|
This command was introduced.
|
Usage Guidelines
Use this command instead of the the show modem mapping command on the Cisco AS5800 access servers. The show modem bundled-firmware command is useful for displaying a list of available modem firmware running in the access server.
Examples
The report from the show modem bundled-firmware command is self-explanatory. The following sample output shows firmware images by slot number:
Router# show modem bundled-firmware
List of bundled modem firmware images by slot
Related Commands
Command
|
Description
|
copy
|
Copies any file from a source to a destination, including a source or destination URL for a TFTP network server, or for Flash memory.
|
copy modem
|
Copies modem firmware to integrated modems in an access server.
|
show modem mapping
|
Displays a snapshot of all the firmware versions running on all the modems in access servers besides the AS5800.
|
show modem call-stats
To display the local disconnect reasons for all modems inside an access server or router, use the show modem call-stats command in EXEC mode.
show modem call-stats [slot]
Syntax Description
slot
|
(Optional) Slot number, which limits the display output to a particular range of modems in the system.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
12.2(11)YT
|
This command was enhanced to display information about digital modems on the Cisco 3600 and 3700 series routers that support the V.92 and V.44 standards.
|
12.2(15)T
|
This enhanced command was integrated into Cisco IOS Release 12.2(15)T.
|
Usage Guidelines
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
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 that the lostCarr error occurred on all the modems in the system, the lostCarr error occurred 2 percent 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 a 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, use the clear modem counters command.
Note
Remote disconnect reasons are not described by this command.
Examples
The following example shows call statistics for the show modem call-stats command. Because of 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
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
The following is sample output from the show modem call-stats command for digital modems on a Cisco 3600 series router that supports the V.92 modem standard (see the "mohTrmnt" column for data about the V.92 Modem on Hold [MOH] function):
Router# show modem call-stats
* - Modem has an active call
B - Modem is marked bad and cannot be used for taking calls
b - Modem is either busied out or shut-down
dial-in/dial-out call statistics
mohTrmnt wdogTimr compress retrain inacTout linkFail moduFail mnpProto
Mdm # % # % # % # % # % # % # % # %
3/0 1 100 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 3/1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
noCarr noDitone busy abort dialStrg autoLgon dialTout rmtHgup
Mdm # % # % # % # % # % # % # % # %
3/0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
* 3/1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3/11 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Table 68 describes the significant fields shown in the display.
Table 68 show modem call-stats Field Descriptions
Field
|
Description
|
dial-in/dial-out call statistics
|
This category of disconnect reasons can happen only in dial-in or dial-out scenarios.
|
mohTrmnt
|
The number of times that a modem is disconnected because Modem on Hold (MOH) terminates. MOH will terminate for two reasons:
• MOH clear down by the modem (MICA_DR_MOH_CLEAR_DOWN)
• MOH time out (MICA_DR_MOH_TIMEOUT)
|
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 reestablished 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 (Link Access Procedure for Modems) in reliable mode.
|
moduFail
|
Modulation error. An error was detected at the Digital Signal Processor (DSP) chip level, which caused a disconnect.
|
mnpProto
|
MNP10 protocol error. An uncorrectable error occurred during an 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 High Density Management System (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
|
Dial string 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 character 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.
|
show modem calltracker
To display all information stored within the Call Tracker active or history database for the latest call assigned to a specified modem, use the show modem calltracker command in privileged EXEC mode.
show modem calltracker [slot/port]
Syntax Description
slot/port
|
(Optional) Location of a slot and modem port. Remember to include the slash mark when entering this argument.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Usage Guidelines
This command allows you to display all Call Tracker data for a given modem when you do not have the call handle readily available and do not want to search the Call Tracker database.
Examples
Router# show modem calltracker 1/1
-------------------------- call handle=0000000058 --------------------------
status=Active, service=PPP, origin=Answer, category=Modem
DS0 slot/cntr/chan=0/0/22, called=71071, calling=6669999
userid=router5200, ip=172.19.4.2, mask=255.255.255.0
setup=10/16/1999 18:29:20, conn=0.10, phys=17.00, service=24.71, authen=24.71
init rx/tx b-rate=28800/33600, rx/tx chars=0/0
resource slot/port=1/1, mp bundle=0, charged units=0, account id=75
idb handle=0x6185B968, tty handle=0x612F8598, tcb handle=0x0
----------------------------------------------------------------------------
protocol: last=LAP-M, attempted=LAP-M
compression: last=V.42bis-Both, supported= V.42bis-RX V.42bis-TX
standard: last=V.34+, attempted=V.34+, initial=V.34+
snr=35 dB, sq=3, rx/tx level=-16/-15 dBm
phase jitter: freq=0 Hz, level=0 degrees
far end echo level=-83 dBm, freq offset=0 Hz
phase roll=-99 degrees, round-trip delay=1 msecs
digital pad=None dB, digital pad comp=0
rbs pattern=0, constellation=16 point
rx/tx: symbol rate=3429/3429, carrier freq=1959/1959
rx/tx: trellis code=0/0, preemphasis index=6/0
rx/tx: constellation shape=Off/On, nonlinear encode=Off/On
rx/tx: precode=Off/On, xmit level reduct=2/2 dBm
rx/tx: chars=0/0, general info=0x0
rx/tx: link layer chars=0/0, NAKs=0/0
error corrected: rx/tx=0/0, rx bad=0
ec retransmissions=0, retransmitted frames=0
rx/tx ppp slip=0/0, bad ppp slip=0
rx/tx b-rate: last=28800/33600, lowest=28800/33600, highest=28800/33600
phase 2 projected max rx b-rate: client=19200, host=24000
phase 4 desired rx/tx b-rate: client=28800/33600, host=28800/33600
retrains: local=0, remote=0, failed=0
speedshift: local up/down=0/0, remote up/down=0/0, failed=0
v110: rx good=0, rx bad=0, tx=0, sync lost=0
v90: status=No Attempt, client=(n/a), failure=None
rx/tx: max neg I frame=128/128, neg window=15/15
v42bis size: dictionary=1024, string=64
T401 timeouts=0, tx window closures=0, rx overruns=0
test err=0, reset=0, v0 synch loss=0
duration(sec)=16, disc reason=0x0