|
|
Cisco IOS Release 11.2(10)P provides software support for the Cisco AS5300 access server. This feature chapter describes how to configure modem pooling and E1 R2 signaling. It also provides new command reference pages for new and changed Cisco IOS commands.
This section describes how to setup modem pools and configure E1 R2 register signaling:
Modem pooling allows service providers to define, select, and use separate pools of modems within a single access server or router to provide different dial-in services. Modem allocation is based on the dialed number identification service (DNIS) and a predetermined number of modem ports based on DNIS.
There are a number of applications for using the call set up information, including DNIS/ANI, processing incoming call requests with CallerID, and selecting services to setup "automatically" for specified calls. These uses generally fall into two categories, those requiring allocation of a specific number of modems for a specific service, and those requiring allocation of specific physical modems.
Some wholesale service providers need to allocate a minimum (guaranteed) number of ports per customer and provide some level of extra (overflow) ports. Some service providers use different dial-in numbers for different wholesale customer service offerings. This is one way of differentiating between customers for port allocation. (For example, see Table 1 and the following description.)
| DNIS or Called Number | Minimum Number of Ports | Service |
|---|---|---|
| 555-4444 | X | Wholesale customer A guaranteed ports |
| 555-3333 | Y | Wholesale customer B guaranteed ports |
| 555-5555 | Z | Retail service port allocation and/or overflow for wholesale service A |
| Any other | Remaining | Default pool, used for other purposes |
Total ports = X + Y + Z + remaining
The goal of the configuration is to guarantee all customers a minimum number of connections. After customers reach their minimum number of guaranteed connections, they get a busy signal. For example, suppose all X customers dial in to 555-4444 and gain access. When the X +1 customer dials in to 555-4444, that customer receives a busy signal, providing the DNIS 555-4444 is mapped to a pool of modems with a fixed range of modems. However, not all the ports in the access server are actually in use. A different wholesale customer Y successfully dials in to 555-3333 and gains access, because the called number 555-3333 also has its own private range of modems.
Figure 1 illustrates how you can setup two modem pools for four customers. This is an E1 example configuration for the Cisco AS5300, which can be loaded with 120 digital MICA modems.
To create a modem pool for a specific customer or dial-in service, perform the tasks in the following table beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Create or specify a modem pool. | modem-pool name |
| Step 2 Assign a range of modems to the modem pool. | pool-range number-number |
| Step 3 Assign a called party number, which is based on DNIS, to the modem pool. | called-number number [max-conn number] |
| Step 4 Return to EXEC mode. | Ctrl Z |
| Step 5 (Optional) Display the modem pool you just configured. Replace the name argument with the modem pool name you specified in Step 1. | show modem-pool [name] |
For a modem pool configuration example, see the section "Modem Pool Example."
There are 3 types of E1 R2 signalling that you can configure with the cas-group command: compelled, semi-compelled, and non-compelled. However, each country has its own E1 R2 specifications, which might follow the ITU-T Q.400-Q.490 recommendation for R2 signalling. Unique E1 R2 signaling parameters for specific countries are set by issuing the cas-custom channel command followed by the country name command.
To provide support for E1 R2 signaling, perform the tasks in the following table beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify the E1 controller that corresponds with the E1 interface you want to configure. | controller e1 number |
| Step 2 Configure channel associated signaling on the E1 controller. For a complete description of the command syntax, see the cas-group (controller e1) command reference page. | cas-group channel timeslots range type signal |
| Step 3 (Optional) Enter cas-custom mode, which enables you to customize some of the E1 R2 signaling parameters such as specific country settings. See Step 4. | cas-custom channel |
| Step 4 Customize E1 R2 signaling parameters according to your E1 networking environment.
See the cas-custom command reference page for more information about each signaling command. | The following signaling commands are available:
|
For an E1 R2 configuration example, see the section "E1 R2 Register Signaling Example."
This section provides examples for configuring modem pools and E1 R2 register signaling on a Cisco AS5300.
The following example creates a new modem pool called accounts1. There are 21 modems assigned to this pool. There are a total of 120 MICA modems in the system, which is a Cisco AS5300 setup for an E1 network configuration.
Step 1 From global configuration mode, create a new modem pool using the modem-pool name command. In this example, the modem pool is named accounts1.
configure terminal
modem-pool accounts1
Step 2 Assign a range of modems to the modem pool with the pool-range number-number command. The numbers you specify map to the TTY line number values assigned to each modem.
pool-range 30-50
Step 3 Assign a called number, which is based on DNIS, to the modem pool using the called-number number [max-conn number] command:
called-number 2000 max-conn 21
In this example, the customers dialing the number 2000 are guaranteed access to 21 modems. The 22nd client to dial in is refused connectivity, because the maximum allowable connections (21) was exceeded. However, if 2000 is the only called number in the modem pool, then there is no need to configure the max-conn option because the maximum connections allowed for the called number automatically default to the maximum number of modems in the pool. Additionally, the same called party number cannot be configured in multiple modem pools. Each called number must be assigned only to one modem pool.
Step 4 Return to EXEC mode by pressing CTRL Z:
^Z
Step 5 Using the show modem-pool EXEC command, display the modem pool you just created. All modems that you did not intentional assign to a modem pool (for example, accounts1) are automatically assigned to the system default pool.
show modem-pool
In most cases, you will configure the same channel associated signaling on each E1 controller in your Cisco AS5300. The following example configures signaling and customizes E1 R2 parameters on controller E1 2 using the cas-group and cas-custom controller configuration commands.
The actual channel associated signaling is configured on the 16th timeslot, which is the reason why the timeslot does not come up in the following output.
Step 1 Enter global configuration mode with the configure terminal command:
configure terminal
Step 2 Specify the E1 controller that you want to configure using the controller e1 number global configuration command. A controller informs the access server how to distribute or provision individual timeslots for a connected E1 line. You must configure one E1 controller for each E1 line.
controller e1 2
Step 3 Configure channel associated signaling with the cas-group channel timeslots range type signal command. This example specifies R2 ITU Q421 digital line signaling, which is the most common signaling configuration. This example also specifies R2 compelled register signalling and provisions the ANI addr option.
cas-group 1 timeslots 1 type r2-digital r2-compelled ani
The Cisco AS5300 supports many different signaling types. Choose the option for your specific networking environment.
cas-group 1 timeslots 1-30 type ?
Step 4 (Optional) Customize some of the E1 R2 signaling parameters with the cas-custom channel controller configuration command. This example customizes the signaling for channel group 1 to collect 3 digits before it requests ANI or CallerID information for analog calls in Argentina.
cas-custom 1
?
caller-digits 3
country argentina use-defaults
exit
end
The following commands are new:
The following existing commands were changed:
To assign a called party number to a particular modem pool, use the called-number modem pool configuration command.
called-number number [max-conn number]| number | Called number for a specified 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.
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.
The called party number, which is configured with the called-number command, is based on the dialed number identification service (DNIS). You can also configure multiple called numbers or DNIS for a single modem pool, as shown in the "Examples" section.
Use the max-conn option if you want to specify a maximum number of modems that a called party number can use. For example, if you create one modem pool to serve two or more customers, this option sets limits on how many guaranteed connections each customer will have in to the modem pool. In this way, one customer cannot occupy or monopolize an entire modem pool. Essentially, this feature provides overflow protection and sets dial-in limits for individual customers.
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 mapped to the same modem pool. The x variable is a place holder for the digits 1 through 9.
In the following example, the pool-range command assigns modems 1 to 59 to the modem pool named accounts1. The called-number 4085551212 max-conn 30 command assigns the called number 2000 to the accounts1 modem pool, and it limits the total simultaneous connections for this number to 30. The called-number 4084441212 max-conn 30 command assigns the called number 3000, which is for a different customer, to the same accounts2 modem pool. The total simultaneous connections for this called number is also set to 30. This configuration guarantees a maximum of 30 modems to each customer and protects each customer from unwanted modem calls overflowing in to their respective pools.
router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#modem-pool accounts1router(config-modem-pool)#pool-range 1-59router(config-modem-pool)#called-number 4085551212 max-conn 30router(config-modem-pool)#called-number 4084441212 max-conn 30router(config-modem-pool)#exitrouter(config)#
clear modempool-counters
modem-pool
pool-range
show modem-pool
To customize some of the E1 R2 signaling parameters for a particular E1 channel group on a channelized E1 line, use the cas-custom controller configuration command. Use the no form of this command to disable channel associated signaling for one or more timeslots.
cas-custom channel| channel | Specifies a single channel group number, which can be between 0 and 30. This channel group number must match the channel number specified in the cas-group command. |
No channel associated signaling is configured on the controller.
Controller configuration
This command first appeared in Cisco IOS Release 11.2 P.
The customization parameters set by the cas-custom channel command are applied to the same channel group number used in the cas-group channel timeslots range type signal command. These channel group numbers must match. Otherwise, the customized features specified in by the cas-custom command will not be applied to the cas-group command's configuration. The signaling customization will not take effect.
However, you will not need to configure or set more than one channel group number per E1 line in most cases. Although rarely used, it is possible to split a single E1 (has timeslots 1 to 31) into two groups (for example, 1 to 15 on group 1 and timeslots 17 to 31 in group 2).
After you issue the cas-custom channel command, the system software enters cas-custom mode. At this point, the router prompt changes from router(config-controller)# to router(config-ctrl-cas)#. From here, many signaling parameters can be set.Table 1 (Table 2.)
| CAS Custom Command | Purpose |
|---|---|
| answer-signal {group-a | group-b} number | Answer signal to be used. You can specify the group A signal or the group B signal. The signal number can be 1 to 15. |
| caller-digits number | Specifies the number of digits the access server needs to collect before it requests ANI or CallerID information. You can specify from 1 to 10. |
| category number | Specifies the type of incoming call, which is mapped to a group signal number. Signal numbers from 1 to 15 are available. |
| country name | Specifies the country to be supported. Replace the name argument with one of the following supported countries. Be sure to include the use-defaults option after your country name.
|
|
default | Sets a command to its default setting. |
| dnis-digits number | Expected number of DNIS digits. You can specify 1 to 64 digits. |
| exit | Takes you out of cas custom mode. |
| invert-abcd | Inverts the ABCD bits before tx and after rx. Disabled by default. |
| ka number | Specifies the KA signal code. You can choose 1 to 15. |
| kd number | Specifies the KD signal code. You can choose 1 to 15. |
| metering | Specifies sending a metering pulse when the access server is making an outgoing call. Metering is disabled by default. |
| nc-congestion | Specifies the non-compelled congestion signal. This signal is sent to the central office when the access server is congested and cannot accept the call. Default is B4, which automatically sends the congestion signal when the system is congested. |
| no | Negates a command or sets its defaults. |
| unused-abcd value | Specifies unused ABCD bit values, which can have a 0 or 1 bit value. |
The following example displays the available signaling parameters that you can set after you enter cas-custom mode on a Cisco AS5300:
router(config-ctrl-cas)# ?
CAS custom commands:
answer-signal Answer signal to be used
caller-digits Digits to be collected before requesting CallerID
category Category signal
country Country Name
default Set a command to its defaults
dnis-digits Expected number of DNIS digits
exit Exit from cas custom mode
invert-abcd invert the ABCD bits before tx and after rx
ka KA Signal
kd KD Signal
metering R2 network is sending metering signal
nc-congestion Non Compelled Congestion signal
no Negate a command or set its defaults
unused-abcd Unused ABCD bit values
You can localize your configuration for any of the following countries.
router(config-ctrl-cas)# country ?
argentina Argentina
brazil Brazil
china China
colombia Colombia
costarica Costa Rica
indonesia Indonesia
israel Israel
malaysia Malaysia
philipines Philippines
singapore Singapore
telemex Telemex
telnor Telnor
thailand Thailand
venez Venez
The following example customizes the signaling for channel group 1 to collect 3 digits before it requests ANI or CallerID information for analog calls in Argentina. This configuration is entered on a Cisco AS5300.
router(config-controller)#cas-custom 1router(config-ctrl-cas)#caller-digits 3router(config-ctrl-cas)#country argentina use-defaultsrouter(config-controller)#exitrouter(config)#end
cas-group (controller E1)
To configure the channel associated signaling on an E1 controller, use the cas-group controller configuration command. Use the no form of this command to disable channel associated signaling for one or more timeslots.
cas-group channel timeslots range type signal| channel | Specifies a single channel group number, which can be between 0 and 30. |
| timeslots range | Specifies a timeslot range of values from 1 to 31. You can specify timeslot ranges (for example, 1-31), individual timeslots separated by commas (for example 1, 3, 5), or a combination of the two (for example 1-3, 8, 17-31). The 16th time slot is not specified in the command line, because it is reserved for transmitting the channel signaling. |
| type signal | Specifies the type of channel associated signaling. Configure the signal type that your central office uses. Supported signal types are described in the following bulleted list:
· e&m-fgb [dtmf][mf [dnis]]--Specifies ear and mouth channel signaling with feature group B support. The following two tone signaling options are also supported: dtmf--DTMF tone signalling. mf [dnis]--MF tone signaling with the option of configuring DNIS provisioning. · e&m-fgd--Specifies ear and mouth channel signaling with feature group D support. · e&m-immediate-start--Specifies ear and mouth channel signaling with immediate start support. · fxs-groundstart--Specifies foreign exchange system ground start signaling support. · fxs-loopstart-- Specifies foreign exchange system loopstart signaling support. · p7-- Specifies the P7 switch type. |
| · [r2-analog | r2-digital | r2-pulse] [dtmf | r2-compelled [ani] | r2-non-compelled [ani] | r2-semi-compelled [ani]]
r2-analog--Specifies R2 ITU Q411 analog line signaling, which reflects the on/off switching of a tone in frequency division multiplexing circuits (before TDM circuits were created). r2-digital--Specifies R2 ITU Q421 digital line signaling, which is the most common signaling configuration. r2-pulse--Specifies R2 ITU supplement 7 pulse line signaling, which is a transmitted pulse that indicates a change in the line state. dtmf--Specifies the DTMF tone signaling. r2-compelled [ani]--Specifies R2 compelled register signaling. You can also specify provisioning the ANI addr option. r2-non-compelled [ani]--Specifies R2 non compelled register signaling. r2-semi-compelled [ani]--Specifies R2 semi compelled register signaling. | |
| · sas-groundstart--Specifies specific access station ground start signaling support.
· sas-loopstart--Specifies specific access station loopstart signaling support. |
No channel associated signaling is configured on the controller.
Controller configuration
This command first appeared in Cisco IOS Release 11.2 P.
Use this command to configure support for incoming and outgoing call signals (such as on-hook and off-hook) on each E1 controller.
If you specify the timeslot range 1-31 at the router prompt, the system software automatically uses the 16th timeslot to transmit the channel associated signaling.
Be sure to configure the same line signaling that your central office uses. For example, if your central office uses R2 analog signaling then you must configure the E1 timeslots with the r2-analog signal type. All R2 signaling options include DNIS support by default.
To customize some of the R2 signaling parameters, refer to the cas-custom controller configuration command. When you enable the cas-group command, the cas-custom command is automatically setup and polled for configuration information. However, unless you enable or turn on specific features with the cas-custom command, the cas-custom feature has an empty set of signaling parameters.
If you want to use the modem pooling feature with R2 tone signaling, then DNIS information is automatically collected by the system. You do not need to specify the collection of DNIS information with the cas-group command.
However, if you are using non-R2 tone signalling, the system must be manually configured to collect DNIS information. For non-R2 cas signalling, DNIS collection is done only for E&M-fgb. To collect DTMF DNIS for E&M-fgb under a controller T1 configuration, use the cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnis command. To collect MF DNIS for E&M-fgb, issue the cas-group 0 timeslots 1-24 type e&m-fgb mf dnis command.
In most cases, you will configure the same channel associated signaling on each E1 controller in your Cisco AS5300. There are four E1 controllers on the Cisco AS5300. The following example configures signaling and customized parameters on controller E1 2 using the cas-group and cas-custom controller configuration commands.
The actual channel associated signaling is configured on the 16th timeslot, which is the reason why the timeslot does not come up in the following output.
router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#controller e1 2router(config-controller)#cas-group 1 timeslots 1 type r2-digital r2-compelled anirouter(config-controller)# %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 1 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 2 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 3 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 4 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 5 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 6 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 7 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 8 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 9 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 10 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 11 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 12 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 13 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 14 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 15 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 17 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 18 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 19 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 20 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 21 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 22 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 23 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 24 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 25 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 26 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 27 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 28 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 29 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 30 is up %DSX0-5-RBSLINEUP: RBS of controller 0 timeslot 31 is up
The following example shows all the supported E1 signaling types on the Cisco AS5300. For additional information about each configuration option, see the previous syntax description.
router(config-controller)#cas-group 1 timeslots 1-30 type ?e&m-fgb E & M Type II FGB e&m-fgd E & M Type II FGD e&m-immediate-start E & M Immediate Start fxs-ground-start FXS Ground Start fxs-loop-start FXS Loop Start p7 P7 Switch r2-analog R2 ITU Q411 r2-digital R2 ITU Q421 r2-pulse R2 ITU Supplement 7 sas-ground-start SAS Ground Start sas-loop-start SAS Loop Start router(config-controller)#cas-group 1 timeslots 1-30 type r2-analog ?dtmf DTMF tone signalling r2-compelled R2 Compelled Register Signalling r2-non-compelled R2 Non Compelled Register Signalling r2-semi-compelled R2 Semi Compelled Register Signalling <cr>
You can customize some of the R2 signaling parameters with the cas-custom controller configuration command:
router(config-controller)#cas-custom 1router(config-ctrl-cas)#?CAS custom commands: bxfree Bx-Free signal caller-digits Digits to be collected before requesting CallerID category Category signal country Country Name default Set a command to its defaults exit Exit from cas custom mode invert-abcd invert the ABCD bits before tx and after rx metering R2 network is sending metering signal nc-congestion Non Compelled Congestion signal no Negate a command or set its defaults
To configure channelized T1 timeslots with channel associated signaling (also known as robbed bit signaling), which enables an integrated modem to receive and transmit analog calls, use the cas-group controller configuration command. Use the no form of this command to disable channel associated signaling for one or more timeslots.
cas-group channel timeslots range type signal| channel | Specifies a single channel group number, which can be between 0 and 23. |
| timeslots range | Specifies a timeslot range of values from 1 to 24. |
| type signal | Specifies the type of channel associated signaling. Choose one of the following signal types to configure:
· e&m-fgb--Specifies ear and mouth channel signaling with feature group b support. You can further customize this feature by specifying one of these two options:
· e&m-fgd--Specifies ear and mouth channel signaling with feature group d support. · fxs-loopstart-- Specifies foreign exchange system loopstart signaling support. · fxs-groundstart--Specifies foreign exchange system ground start signaling support. · sas-loopstart--Specifies specific access station loopstart signaling support. · sas-groundstart--Specifies specific access station ground start signaling support. |
No channelized T1 robbed bit signaling is configured.
Controller configuration
This command first appeared in Cisco IOS Release 11.2.
Use this command to enable an integrated modem to receive and transmit incoming and outgoing call signaling (such as on-hook and off-hook) through each T1 controller that is configured for a channelized T1 line.
If you want to collect DNIS information using non-R2 tone signalling, the system must be manually configured. For non-R2 cas signalling, DNIS collection is done only for E&M-fgb. To collect DTMF DNIS for E&M-fgb under a controller T1 configuration, use the cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnis command. To collect MF DNIS for E&M-fgb, issue the cas-group 0 timeslots 1-24 type e&m-fgb mf dnis command.
Switched 56 digital calls are not supported in this feature.
The following example configures all 24 channels with ear and mouth channel signaling with feature group B support:
router(config)#controller T1 0router(config-controller)#cas-group 1 timeslots 1-24 type e&m-fgbrouter(config-controller)# %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 1 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 2 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 3 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 4 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 5 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 6 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 7 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 8 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 9 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 10 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 11 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 12 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 13 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 14 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 15 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 16 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 17 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 18 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 19 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 20 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 21 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 22 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 23 is up %DSX0-5-RBSLINEUP: RBS of controller 1 timeslot 24 is up
The following example configures the required signaling to support modem pooling and the digital number identification service (DNIS) over channelized T1 lines on a Cisco AS5300. The only supported signaling and tone types for incoming analog calls are E&M feature group b, DTMF tones, and MF tones. By configuring DNIS as part of the cas-group command, the system can collect DNIS digits for incoming calls, which can be redirected to specific modem pools setup for different customers or uses. Additionally, you must be running MICA modems in the system and have at least 10% of your total modems in the default modem pool. Free modems are needed in the default pool to detect the incoming called number or DNIS before handing the call off to the appropriate modem pool. Therefore, a second modem is actually needed to handle each incoming call.
router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#controller t1 0router(config-controller)#cas-group 0 timeslots 1-24 type e&m-fgb mf dnisrouter(config-controller)#cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnisrouter(config-controller)#exitrouter(config)#
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
User 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#exitrouter>show lineTty 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
called-number
modem-pool
pool-range
show modem-pool
To clear the active or running counters associated with one or more modem pools, use the clear modempool-counters EXEC command. This command can be used only with MICA digital modems.
clear modempool-counters [name]| name | (Optional) Name of the specified modem pool. |
Disabled
User EXEC
This command first appeared in 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.
The clear modempool-counters command clears the counters as displayed in the show modem-pool command:
router# show modem-pool
modem-pool: System-def-Mpool
modems in pool: 20 active conn: 0
0 no free modems in pool
modem-pool: accounts1
modems in pool: 50 active conn: 0
0 no free modems in pool
called_party_number: 1000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
called_party_number: 2000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
modem-pool: accounts2
modems in pool: 50 active conn: 0
0 no free modems in pool
called_party_number: 3000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
called_party_number: 4000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
The following example clears the modem pool and called party number counters:
router# clear modempool-counters
called-number
modem-pool
pool-range
show modem-pool
To copy bundled modem firmware from a Cisco IOS system image loaded in system Flash memory, use the copy ios-bundled modem EXEC command.
copy ios-bundled modemThis command has no additional keywords or arguments.
Disabled
EXEC
This command first appeared in Release 11.2 P.
If you already have a version of modem code in the Flash memory on your access server, and you upgrade to a Cisco IOS release that includes newer modem firmware, only the modems that are mapped to the bundled Cisco IOS version are updated. In order to set the modem firmware mapping to the firmware version bundled with Cisco IOS software, enter the copy ios-bundled modem command.
This command does not affect any existing modem code that resides in system Flash memory in case you later want to revert to it. If you decide to delete the code from system Flash memory, remember that all files in system Flash memory will be deleted, therefore save and restore any important files (for example, the Cisco IOS software image).
As a result of the copy ios-bundled modem command, future Cisco IOS upgrades will potentially result in the mapping of new Cisco IOS bundled firmware to the modems. (If the new Cisco IOS image contains the same modem code as the old one, no new code will be downloaded to the modems.)
The following example downloads modem firmware that is bundled with the local Cisco IOS system image to the internal modems 1/0 to 1/23.
Step 1 Enter the copy ios-bundled modem EXEC command:
copy ios-bundled modem
Step 2 Specify the modem or range of modems that you want the firmware copied to. This example copies the firmware to modems 1/0 through 1/23.
1/0-1/23
Step 3 Specify whether you want the update to occur during the current session or the next system reload. The busyout option downloads the firmware as soon as the modem(s) becomes available. If the modem is idle when the command is executed, the firmware is downloaded immediately. The reboot option stores instructions in the NVRAM table and downloads the firmware from the Cisco IOS system image during the next system reload.
busyout
Step 4 Confirm that you want to copy the firmware:
yes
The following example updates modem firmware at the next system reload:
router#copy ios-bundled modemModem Numbers (<slot>/<port> | group <number> | all)?1/0-1/23Type of service [busyout/reboot]rebootCopy bundled firmware from IOS image to modems? [yes/no]yesMica Portware download will take effect after reboot
show modem
To configure the duplex mode on a Fast Ethernet interface, use the duplex interface configuration command. Use the no form of this command to return the system to half duplex mode, which is the system default.
duplex {full | half | auto}| full | Specifies full duplex configuration. |
| half | Specifies half duplex configuration. |
| auto | Specifies the auto negotiation capability. The interface automatically operates at half or full duplex, depending on environmental factors, such as the type of media and transmission speeds for the peer routers, hubs, and switches used in the network configuration. |
Half duplex mode
Interface configuration
This command first appeared in Cisco IOS Release 11.2 P.
The auto negotiation capability is turned on for the Fast Ethernet interface by either configuring the speed auto interface configuration command or the duplex auto interface configuration command.
Table 3 describes the system's performance for different configuration combinations of the duplex plus the speed command. Reading one row at a time, the specified duplex command configured with the specified speed command produces the resulting system action.
| Duplex Command | Speed Command | Resulting System Action |
|---|---|---|
| duplex auto | speed auto | Auto negotiates both speed and duplex modes. |
| duplex auto | speed 100 or speed 10 | Auto negotiates both speed and duplex modes. |
| duplex half or duplex full | speed auto | Auto negotiates both speed and duplex modes. |
| duplex half | speed 10 | Forces 10 Mbps and half duplex. |
| duplex full | speed 10 | Forces 10 Mbps and full duplex. |
| duplex half | speed 100 | Forces 100 Mbps and half duplex. |
| duplex full | speed 100 | Forces 100 Mbps and full duplex. |
For the Cisco AS5300, the duplex {full | half | auto} command syntax replaces the following two earlier duplex commands:
You will get the following error messages if you try to use these commands on a Cisco AS5300:
router(config)#interface fastethernet 0router(config-if)#full-duplexPlease use duplex command to configure duplex mode router(config-if)# router(config-if)#half-duplexPlease use duplex command to configure duplex mode
The following example shows the different duplex configuration options you can configure on a Cisco AS5300:
router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#interface fastethernet 0router(config-if)#duplex ?auto Enable AUTO duplex configuration full Force full duplex operation half Force half-duplex operation
speed
interface fastethernet
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
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 · 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 following example shows the different duplex configuration options you can configure on a Cisco AS5300:
router(config)# modem country microcom_hdms ?
argentina Agrentia
australia Australia
austria Austria
belgium Belgium
canada Canada
chile Chile
china China
columbia Columbia
czech-republic Czech/Slovak Republic
denmark Denmark
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
To create or specify a modem pool, use the modem-pool global configuration command.
modem-pool name| name | Specifies the name for a particular modem pool. |
All modems are configured to be part of one system default modem pool. If you have 120 MICA modems loaded in your system, then 120 modems are in the default modem pool.
Global configuration
This command was first introduced in Cisco IOS Release 11.2 P.
Modem pooling allows service providers to define, select, and use separate pools of modems within a single access server or router to enable different dial-in services for different customers. The primary application is to allocate specific modems based on the dialed number identification service (DNIS) and a predetermined number of modem ports based on DNIS.
There are a many applications for using the call set up information, including DNIS/ANI, in processing incoming call requests with CallerID, and selecting services to setup "automatically" for that call. These uses generally fall into two categories, those requiring allocation of a specific number of modems for a specific service, and those requiring allocation of specific physical modems.
Some wholesale service providers need to be able to allocate a minimum (guaranteed) number of ports per customer, and also provide for some level of extra (overflow) ports. Some service providers use different dial numbers for different wholesale customer service offerings. This is one way of differentiating between services or customers when allocating ports. (For example, see Table 4 and the following description.)
| DNIS or Called Number | Minimum Number of Ports | Service |
|---|---|---|
| 555-4444 | X | Wholesale customer A, guaranteed ports, 56K modems |
| 555-3333 | Y | Wholesale customer B, guaranteed ports, Fax modems |
| 555-5555 | Z | Retail service port allocation and/or overflow for wholesale service A |
| Any other | Remaining | Default pool, used for other purposes |
Total ports = X + Y + Z + remaining
The goal of the configuration is to guarantee all customers a minimum number of connections. After customers reach their minimum number of guaranteed connections, they get a busy signal. For example, suppose all X customers dial in to 555-4444 and gain access. When the X +1 customer dials in to 555-4444, that customer receives a busy signal, providing the DNIS 555-4444 is mapped to a pool of modems with a fixed range of modems. However, not all the ports in the access server are actually in use. A different wholesale customer Y successfully dials in to 555-3333 and gains access, because the called number 555-3333 also has its own private range of modems.
You can view the actual configuration information for Figure 2 by entering the show modem-pool command:
router# show modem-pool
modem-pool: System-def-Mpool
modems in pool: 20 active conn: 0
0 no free modems in pool
modem-pool: accounts1
modems in pool: 50 active conn: 0
0 no free modems in pool
called_party_number: 1000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
called_party_number: 2000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
modem-pool: accounts2
modems in pool: 50 active conn: 0
0 no free modems in pool
called_party_number: 3000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
called_party_number: 4000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
The following example creates a new modem pool called accounts1. After you specify the modem pool name, your system software automatically takes you to modem pool configuration mode. Notice that the router prompt changes from router(config)# to router(config-modem-pool)#.
router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#modem-pool accounts1router(config-modem-pool)#
The next example assigns modem TTY line numbers 30 to 50 to the modem pool accounts1. The modem pool's called number is set to 2000. The customers dialing the number 2000 are guaranteed access to 21 modems. The 22nd client to dial in will be refused connectivity because the maximum allowable connections was exceeded. However, if 2000 is the only called number in the modem pool, then there is no need to configure the max-conn option because the maximum connections allowed for the called number automatically default to the maximum number of modems in the pool. Additionally, the same called party number cannot be configured in multiple modem pools. Each called number must be assigned only to one modem pool.
router(config-modem-pool)#pool-range 30-50router(config-modem-pool)#called-number 2000 max-conn 21router(config-modem-pool)#exitrouter(config)#
The following configuration rejects the pool-range 30 command because modem TTY line 30 is already a member of the modem pool accounts1, which we configured in the previous example.
router(config)#modem-pool accounts2router(config-modem-pool)#pool-range 30% TTY 30 is already in another pool.
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| number-number | Specifies a range of modems to be used for a particular 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 or router 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 argument 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 modems 1/0 through 1/23 in a pool range, its TTY line numbers would be 1 to 24. To determine the exact modem number to TTY line mapping scheme for your access sever or router, use the show modem slot/port command.
The following example assigns modem TTY lines 30 to 50 to the modem pool called accounts1. The modem pool's called number is set to 2000. The customers dialing the number 2000 are guaranteed access to 21 modems. The 22nd client to dial in will be refused connectivity because the maximum allowable connections was exceeded. However, if 2000 is the only called number in the modem pool, then there is no real need to configure the max-conn option because the maximum connections allowed for the called number automatically default to the maximum number of modems in the pool.
router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. router(config)#modem-pool accounts1router(config-modem-pool)#pool-range 30-50router(config-modem-pool)#called-number 2000 max-conn 21router(config-modem-pool)#exit
Modems cannot be assigned to more than one modem pool. The following example rejects the pool-range 30 command because modem TTY line 30 is already a member of another modem pool.
router(config)#modem-pool customer2router(config-modem-pool)#pool-range 30% TTY 30 is already in another pool.
called-number
clear modempool-counters
modem-pool
show modem-pool
To display the configuration for a Fast Ethernet interface, use the show interface fastethernet EXEC command.
show interface fastethernet {number}| number | Interface number for the Fast Ethernet interface you want displayed. |
Disabled
EXEC
The following is sample display output for the show interface fastethernet EXEC command on a Cisco AS5300:
router# show interface fastethernet 0
FastEthernet0 is up, line protocol is up
Hardware is DEC21140AD, address is 00e0.1e3e.c179 (bia 00e0.1e3e.c179)
Internet address is 1.17.30.4/16
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
Half-duplex, 10Mb/s, 100BaseTX/FX
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:03, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/120, 8 drops
5 minute input rate 2000 bits/sec, 3 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
158773 packets input, 17362631 bytes, 4 no buffer
Received 158781 broadcasts, 0 runts, 0 giants, 7 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 watchdog, 0 multicast
0 input packets with dribble condition detected
6299 packets output, 622530 bytes, 0 underruns
1 output errors, 0 collisions, 3 interface resets
0 babbles, 0 late collision, 0 deferred
1 lost carrier, 1 no carrier
0 output buffer failures, 0 output buffers swapped out
To display the controllers for the Fast Ethernet interfaces, use the show controller fastethernet EXEC command.
show controller fastethernet {number}| number | Interface number for the controller you want displayed. |
EXEC
The following example displays sample output for the show controller fastethernet command on a Cisco AS5300.
router# show controller fastethernet 0
DEC21140
Setup Frame
(0 ) 00e0.1e3e.c179
(1 ) 0100.0ccc.cccc
(2 ) 0900.2b00.000f
(3 ) 0900.2b02.0104
(4 ) 0300.0000.0001
dec21140_ds=0x60BD33B8, registers=0x3C210000, ib=0x4002F75C, ring entries=32
rxring=0x4002F844, rxr shadow=0x60F14B58, rx_head=6, rx_tail=6
txring=0x4002FA6C, txr shadow=0x60F14BF8, tx_head=10, tx_tail=10, tx_count=0
tx_size=32, rx_size=32
PHY link up
DEC21140 Registers:
CSR0=0xFE024480, CSR3=0x4002F844, CSR4=0x4002FA6C, CSR5=0xFC660000
CSR6=0x322C2002, CSR7=0xFFFFA241, CSR8=0xE0000000, CSR9=0xFFFDC3FF
CSR11=0xFFFE0000, CSR12=0xFFFFFF09, CSR15=0xFFFFFEC8
DEC21140 PCI registers:
bus_no=2, device_no=0
CFID=0x00091011, CFCS=0x82800005, CFRV=0x02000021, CFLT=0x0000FF00
CBIO=0x3C210001, CBMA=0x00000000, CFIT=0x28140100, CFDA=0x00000000
MII registers:
Register 0x00: 0000 784D 2000 5C01 0001 0000 0000 0000
Register 0x08: 0000 0000 0000 0000 0000 0000 0000 0000
Register 0x10: 0000 0000 0000 0000 0000 0001 8060
Register 0x18: 8020 0840 0000 3000 A3B9
throttled=7, enabled=7
rx_fifo_overflow=0, rx_no_enp=0, late_collision=0
rx_watchdog=0, rx_process_stopped=0, rx_buffer_unavailable=0
tx_jabber_timeout=0, tx_carrier_loss=1, tx_deferred=0
tx_no_carrier=1, tx_late_collision=0, tx_excess_coll=0
tx_process_stopped=0, fatal_tx_err=0
overflow_resets=0
0 missed datagrams, 0 overruns
0 transmitter underruns, 0 excessive collisions
0 single collisions, 0 multiple collisions
0 dma memory errors, 0 CRC errors
0 alignment errors, 0 runts, 0 giants
To display the local disconnect reasons for all modems inside the system, 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. |
User and Privileged EXEC
This command first appeared in Cisco IOS Release 11.2 P.
Use this command to find out why a local 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 occured on a specific modem is displayed (see the # column in the next example). 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.
See Table 5 for descriptions of the fields and end-connection events in the following sample display, which applies to MICA and Microcom modems.
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 5 represents a combination of all the local disconnect reasons for MICA and Microcom modems; therefore, each type of modem will not generate all the following disconnect conditions.
| Field | Description |
|---|---|
| dial-in/dial-out call statistics | This category of disconnect reasons can happen only in dial-in or dial-out scenarios. |
|
Watchdog timeout. An obscure firmware problem occurred. This is a rare disconnect reason that occurs only on Microcom modems. |
|
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. This disconnect reason applies to MICA and Microcom modems. |
|
Retrain failure. A connection was lost and not re-established after three attempts. This disconnect reason applies to MICA and Microcom modems. For MICA modems only, too many consecutive retrains or speed shifts occurred. |
|
Inactivity timeout. The time specified in the AT/T command has expired. No modem data transfers were detected during that period. This disconnect reason applies to MICA and Microcom modems. For MICA modems only, received LD, but the partner's inactivity timer expired. Inactivity timeout occurred. LD inactivity was sent. |
|
Link failure. The protocol level link failed while using MNP-10 or LAPM in reliable mode. This disconnect reason applies only to Microcom modems. |
|
Modulation error. An error was detected at the DSP chip level, which caused a disconnect. This disconnect reason applies only to Microcom modems. |
|
MNP10 protocol error. An uncorrectable error occurred during a MNP-10 connection. This disconnect reason applies to MICA and Microcom modems. The following causes pertain only to MICA modems. Modem did not receive a LR frame during negotiation. The received LR frame is incompatible with local settings (second speaker). Too many consecutive retransmissions occurred. A protocol catch-all error occurred. A XID frame was not received during negotiation. The received XID is incompatible with the local settings (second speaker). Received a DM. Received a bad sequence number/ACK#. Received a SABME frame in steady state. Received XID in steady state. Received LR in steady state. Received unknown command code. Received FRMR with reason xx (bit mapped). Received FRMR bad command. Received FRMR data field or incorrect length (U frames). Received FRMR bad N(R). Received LD, but partner never received our LR. Received LD, but the LR has bad parameter #1. Received LD, but the LR was incompatible with partner's configuration. Received LD, but a MNP protocol error occurred. |
|
LAPM protocol error. An uncorrectable error occurred during a LAPM connection. This disconnect reason applies to MICA and Microcom modems. The following causes pertain only to MICA modems. Modem did not receive a LR frame during negotiation. The received LR frame is incompatible with local settings (second speaker). Too many consecutive retransmissions occurred. A protocol catch-all error occurred. A XID frame was not received during negotiation. The received XID is incompatible with the local settings (second speaker). Received a DM. Received a bad sequence number/ACK#. Received a SABME frame in steady state. Received XID in steady state. Received LR in steady state. Received unknown command code. Received FRMR with reason xx (bit mapped). Received FRMR bad command. Received FRMR data field or incorrect length (U frames). Received FRMR bad N(R). Received LD, but partner never received our LR. Received LD, but the LR has bad parameter #1. Received LD, but the LR was incompatible with partner's configuration. Received LD, but a MNP protocol error occurred. |
|
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. This disconnect reason applies to MICA and Microcom modems. For MICA modems only, carrier lost (DSP). |
|
DTR drop. The modem disconnected because the DTR signal from the host became inactive. This disconnect reason applies to MICA and Microcom modems. For MICA modems only, a virtual DTR dropped. This status is reflected from the I/O port redirector, which is currently using the modem. |
|
User hang up. The modem disconnected because a command such as ATH was detected. This disconnect reason applies to MICA and Microcom modems. |
|
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). This disconnect reason applies to MICA and Microcom modems. For MICA modems only, received a DISC frame with normal LAPM termination. |
|
Terminate. A password security error occurred in the Microcom HDMS. This error occurs only with Microcom modems. This disconnect reason applies only to Microcom modems. |
|
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. This disconnect reason applies only to Microcom modems. |
|
A failure was detected while the modem was training up. This disconnect reason applies only to MICA modems. |
|
A host issued a software_reset command. No host reason is available. The dialed number did not answer. The ATH command was detected by the host. This disconnect reason applies only to MICA modems. |
|
No EC fallback protocol was available. This disconnect reason applies only to MICA modems. |
|
Received LD, but the partner saw too many consecutive retransmissions. This disconnect reason applies only to MICA modems. |
| dial-out call statistics | This category of disconnect reasons can happen only in a dial-out scenario. |
|
No carrier. The called number answered, but no answer tone was detected after the appropriate wait. This disconnect reason applies to MICA and Microcom modems. For MICA modems only, no answer back tone was detected. A problem detecting end of answer back tone may have also occurred. A failure was detected while the modem was training up. Carrier lost (DSP). The connection took too long to complete. |
|
No dialtone. No dial tone was detected after the modem went off hook. This disconnect reason applies to MICA and Microcom modems. For MICA modems only, the host could not access the network. |
|
A busy signal was detected while the local modem was attempting to dial. This disconnect reason applies to MICA and Microcom modems. |
|
A character was received from the remote host after the dial command was issued and before a connection was established. This disconnect reason applies to MICA and Microcom modems. For MICA modems only, an AT mode "any key" abort occurred. |
|
Dialstring error. An invalid character was detected in the dial string, which forced the dial attempt to terminate. This disconnect reason applies only to Microcom modems. |
|
Autologon error. An autologon sequence did not successfully complete. This disconnect reason applies only to Microcom modems. |
|
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. This disconnect reason applies only to Microcom modems. |
|
Remote hangup. The modem disconnected because the remote modem disconnected the call and dropped DTR. For MICA modems only, the ATH command was detected by the modem. |
|
Blacklist. In a country that supports blacklisting, an attempt was made to go off hook with a null dial string (ATD). This disconnect reason applies only to Microcom modems. |
|
CCP not seen. The credit card prompt (also known as Bong) was not detected. This disconnect reason applies only to Microcom modems. |
|
FAX class 2 error. An abnormal termination to a fax transmission was detected. This disconnect reason applies only to Microcom modems. |
|
Total number of times the disconnect reason occurred among all the modems in the system. |
To display connection speed statistics for all the modems running in the system, 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.
User and Privileged EXEC
This command first appeared in Cisco IOS Release 11.2 P.
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 6 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.
See Table 7 for descriptions of the fields shown in the following displays.
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 statisitics 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
| 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 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. |
User and Privileged 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 8 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 Hangup After Carrier Loss: | Lost carrier to hang-up delay. |
show modem operational-status
show 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. |
User and Privileged 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 9 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 9 describes the most useful fields in the previous MICA 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 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:
|
|
Static event: | Current static event of the MICA modem, which can be any of the following:
|
|
Dynamic event: | Current dynamic event of the MICA modem, which can be any of the following:
|
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 10 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 10 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. |
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. |
User 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 11.
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 11.
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 11.
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.
| 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. |
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. |
User and Privileged 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.
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). |
To display information about a modem pool, use the show modem-pool EXEC command.
show modem-pool [name]| name | (Optional) Name of the specified modem pool. |
User EXEC
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.
The following example displays sample output for the show modem-pool command. Two modem pools are setup, each containing two called party numbers. Fifty modems are assigned to each modem pool. Each called party number has a maximum of 25 connections. There are 20 modems in the system default pool, which is the pool that includes all the modems that were not assigned to a particular modem pool (for example, accounts1).
router# show modem-pool
modem-pool: System-def-Mpool
modems in pool: 20 active conn: 0
0 no free modems in pool
modem-pool: accounts1
modems in pool: 50 active conn: 0
0 no free modems in pool
called_party_number: 1000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
called_party_number: 2000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
modem-pool: accounts2
modems in pool: 50 active conn: 0
0 no free modems in pool
called_party_number: 3000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
called_party_number: 4000
max conn allowed: 25, active conn: 0
0 max-conn exceeded, 0 no free modems in pool
Table 13 describes the display fields in the previous example:
| Field | Description |
|---|---|
| modem-pool: | Name of the specified modem pool. In the previous example, there are three modem pools configured: System-def-Mpool, accounts1, and accounts2.
All modems that you did not intentional assign to a modem pool (for example, accounts1) are automatically assigned to the system default pool (displayed as System-def-Mpool). |
| modems in pool: | Number of modems that are a member of the specified modem pool. In this example, 20 modems are in System-def-Mpool, 50 modems are in accounts1, and 50 modems are in accounts2. |
| modem-pool: active conn: | Number of simultaneous active connections for the specified pool. |
| 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. |
| test num of modems: | Number of modems tested in the modem pool. |
| called_party_number: | Specified called party number. This is the number that the remote clients are using to dial in to the access server or router. You can have more than one call party number per modem pool. |
| called_party_number: active conn: | Number of simultaneous active connections for the specified called party number. |
| max conn allowed: | Maximum number of modems that a called party number can use. For example, if you create one modem pool to serve two or more customers, this option sets limits on how many guaranteed connections each customer will have in to the modem pool. In this way, one customer cannot occupy or monopolize an entire modem pool. Essentially, this feature provides overflow protection and sets dial-in limits for individual customers. To configure this option, see the called-number command. |
| max-conn exceeded | Number of times an incoming call using this called party number was rejected because the max-conn number parameter specified by the called-number command was exceeded. |
called-number
clear modempool-counters
modem-pool
pool-range
To configure the speed for a Fast Ethernet interface, use the speed interface configuration command. Use the no form of this command to disable a speed setting.
speed {10 | 100 | auto}| 10 | Configures the interface to transmit at 10 Mbps. |
| 100 | Configures the interface to transmit at 100 Mbps. |
| auto | Turns on the Fast Ethernet auto-negotiation capability. The interface automatically operates at 10 or 100 Mbps depending on environmental factors, such as the type of media and transmission speeds for the peer routers, hubs, and switches used in the network configuration. |
100 Mbps
Interface configuration
This command first appeared in Cisco IOS Release 11.2 P.
The auto negotiation capability is turned for the Fast Ethernet interface by either configuring the speed auto interface configuration command or the duplex auto interface configuration command.
Table 14 describes the system's performance for different configuration combinations of the duplex plus the speed command. Reading one row at a time, the specified duplex command configured with the specified speed command produces the resulting system action.
| Duplex Command | Speed Command | Resulting System Action |
|---|---|---|
| duplex auto | speed auto | Auto negotiates both speed and duplex modes. |
| duplex auto | speed 100 or speed 10 | Auto negotiates both speed and duplex modes. |
| duplex half or duplex full | speed auto | Auto negotiates both speed and duplex modes. |
| duplex half | speed 10 | Forces 10 Mbps and half duplex. |
| duplex full | speed 10 | Forces 10 Mbps and full duplex. |
| duplex half | speed 100 | Forces 100 Mbps and half duplex. |
| duplex full | speed 100 | Forces 100 Mbps and full duplex. |
The following example shows the configuration options for the speed command:
router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. router(config)# interface fastethernet 0 router(config-if)# speed ? 10 Force 10 Mbps operation 100 Force 100 Mbps operation auto Enable AUTO speed configuration
|
|