|
|
Cisco IOS Release 11.2(10)P provides the modem pooling feature to the Cisco AS5200 access server. This feature chapter describes how to configure modem pooling. It also provides new command reference pages for new commands.
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 services or 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, 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.
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 "Configuration Example."
The following example creates a new modem pool called accounts1. There are 21 modems assigned to this pool. There are a total of 48 Microcom modems in the system, which is a Cisco AS5200 setup for a PRI T1 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
The following commands are new:
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 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 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 2 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 1 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 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 3 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
|
|