|
|
Cisco Resource Pool Manager Server (Cisco RPMS) enables telephone companies and Internet service providers (ISPs) to count, control, manage, and provides accounting data for shared resources for wholesale VIrtual Private Dial-up Network (VPDN) and retail dial network services across one or more network access server (NAS) stacks.This chapter describes the network architectures you can use with Cisco RPMS.
Cisco RPMS can be easily integrated into existing dial service networks and infrastructures. Cisco RPMS utilizes the following architectures:
When a local AAA server is present in a Cisco RPMS network architecture, Cisco RPMS can provide both wholesale (VPDN) dial services and retail dial services. Wholesale (VPDN) dial services rely on VPDN data specified in the local AAA server or the Cisco RPMS VPDN group. Cisco RPMS uses the VPDN session limit, VPDN session overflow limit, maximum MLP bundles, and maximum links per bundle specified in the VPDN group to manage the tunnel availability. Retail dial services use the local AAA server for user authentication and authorization. Cisco RPMS customer profile and default customer settings provide the session management for retail dial services.
Cisco RPMS uss the Resource Management Protocol (RMP) to communicate with Cisco NASes.
Cisco RPMS has the following system requirements:
A local AAA server can be used for local user authentication, authorization, and accounting records in a Cisco RPMS network architecture.
Cisco RPMS can use RADIUS or TACACS+ to communicate with the local AAA server. Cisco RPMS uses Resource Management Protocol (RMP) to communicate with the Cisco NASes. One TACACS connection is required to enable RMP for the NAS to communicate with Cisco RPMS.
When a local AAA server is present, Cisco RPMS accounting data can be generated in the following ways:
Also, a local AAA server can be used to provide VPDN data. This data can also be specified in the Cisco RPMS VPDN group. Cisco RPMS uses the VPDN session limit, VPDN session overflow limit, maximum MLP bundles, and maximum links per bundle specified in the VPDN group to manage the tunnel availability.
Cisco RPMS provides dial service management for Cisco AS5200, AS5300, and AS5800 NASes. Other non-Cisco NASes are currently not supported.
For more detailed configuration and VPDN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
Cisco 3600 series routers, AS5300 access servers, or 7200 series routers can be implemented as home gateways. The device to use as a home gateway may vary depending on your Cisco RPMS network architecture and network capacity.
More than one home gateway can be configured so Cisco RPMS VPDN sessions are automatically distributed among the home gateways. Cisco RPMS uses a load balancing algorithm to ensure efficient use of home gateway resources. Also, if a connection fails, VPDN sessions are automatically distributed among the remaining home gateways. If these home gateways will receive MLP connections, you must configure Stack Group Bidding Protocol (SGBP).
For more detailed configuration and VPDN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
Cisco RPMS uses an Oracle database to store and retrieve system data. Cisco recommends that you install the Oracle database on a machine separate from the Cisco RPMS server.
The Oracle Database Replication Manager and the Cisco RPMS DBServer component can be used for database replication. All configuration data are replicated among primary and backup Cisco RPMS servers. Configuration changes are automatically updated to peer Cisco RPMS servers through replication and the DBServer cache update mechanism.
Cisco RPMS can be easily integrated into existing VPDN dial service offerings. To convert existing VPDN users to Cisco RPMS, configure Cisco RPMS for the required user configurations using DNIS groups, customer profiles, resource groups, and other Cisco RPMS configuration settings.
When a local AAA server is not present in a Cisco RPMS network architecture, Cisco RPMS provide only wholesale (VPDN) dial services and does not support retail service. Wholesale (VPDN) dial services rely on VPDN data specified in the Cisco RPMS VPDN group.
Cisco RPMS utilizes Resource Management Protocol (RMP) to communicate with the Cisco NASes. One tacacs connection is required to enable RMP for the NAS to communicate with Cisco RPMS.
When a local AAA server is not present, Cisco RPMS accounting data can be generated using Cisco RPMS call detail records. Call detail records are enabled through the Cisco RPMS Administration>Server command.
Cisco RPMS provides dial service management for Cisco AS5200, AS5300, and AS5800 NASes. Other non-Cisco NASes are currently not supported.
For more detailed configuration and VPDN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
Cisco 3600 series routers, AS5300 access servers, or 7200 series routers can be implemented as home gateways. The device to use as a home gateway may vary depending on your Cisco RPMS network architecture and network capacity.
To configure SGBP on multiple home gateways, ensure the necessary configurations are added to the home gateway configuration files for the NAS, designated off-load router, and other home gateways.
For more detailed configuration and VPDN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
Cisco RPMS uses an Oracle database to store and retrieve system data. It is recommended to install the Oracle database on a machine separate from the Cisco RPMS server.
The Oracle Database Replication Manager and the Cisco RPMS DBServer component can be used for database replication. All configuration data are replicated among primary and backup Cisco RPMS servers. Configuration changes are automatically updated to peer Cisco RPMS servers through replication and the DBServer cache update mechanism.
Cisco RPMS can be easily integrated into existing VPDN dial service offerings. To convert existing VPDN users to Cisco RPMS, configure Cisco RPMS for the required user configurations using DNIS groups, customer profiles, resource groups, and other Cisco RPMS configuration settings.
For busy-hour call handling with 20 minute hold times, each Cisco RPMS server can process 14 calls per second over 16,000 ports. For 30 minute hold times, each Cisco RPMS server can process 14 calls per second over 25,000 ports.
Aggregated session counting and session management can be implemented by creating identical configurations on multiple Cisco RPMS servers. A common Cisco RPMS server can be used for displaying cumulative report data and can also be the backup server for the primary Cisco RPMS servers. Figure 2-3 shows an example Cisco RPMS network architecture with a centralized and backup Cisco RPMS.
In this example, the following point of presence (POP) distribution could be used to implement a regional dial service network supporting 76,000 ports:
Multiple Cisco RPMS servers can be configured through a network to support geographically dispersed POPs and dial services. Use the following data to estimate the number of Cisco RPMS servers to implement:
Use the NAS capacity examples Table 2-1 to further understand this data and estimate the needs for your network.
| Calls Per Hour Per NAS | Calls Per Second Per NAS | Number of NASes Supported By 1 Cisco RPMS Server | Number of Ports Supported by 1 Cisco RPMS Server |
|---|---|---|---|
1440 AS5800 ports | 4320 calls per hour | 14 calls per second | 11 Cisco AS5800 NASes |
|
|
|
|
240 AS5300 ports | 720 calls per hour | 14 calls per second | 70 Cisco AS5300 NASes |
|
|
|
|
48 AS5200 ports | 144 calls per hour | 14 calls per second | 350 Cisco AS5200 NASes |
Table 2-2 shows call capacity for 30-minute call hold times (2 calls per hour).
| Calls Per Hour Per NAS | Calls Per Second Per NAS | Number of NASes Supported By 1 Cisco RPMS Server | Number of Ports Supported by 1 Cisco RPMS Server |
|---|---|---|---|
1440 AS5800 ports | 2880 calls per hour | 14 calls per second | 17.5 Cisco AS5800 NASes |
|
|
|
|
240 AS5300 ports | 480 calls per hour | 14 calls per second | 105 Cisco AS5300 NASes |
|
|
|
|
48 AS5200 ports | 96 calls per hour | 14 calls per second | 525 Cisco AS5200 NASes |
Figure 2-4 illustration shows a 13,000 port dial service network using a combination of POPs and single Cisco NASes with one Cisco RPMS for primary operation and one backup Cisco RPMS for fault tolerance and redundancy:
Cisco RPMS provides fault tolerance and resiliency through NAS configurations, primary/backup servers, and a centralized network of multiple Cisco RPMS servers. The following fault tolerance and resiliency options are available:
Cisco RPMS can run standalone or with a backup Cisco RPMS server. Each Cisco RPMS backup server can support multiple primary Cisco RPMS servers. The Cisco RPMS backup server requires Oracle replication and provides a backup configuration and counters in case the primary Cisco RPMS server(s) becomes unavailable. Identical configuration settings (customer profiles, DNIS groups, resource groups, VPDN groups, and others) must be configured on the primary and backup Cisco RPMS servers.
As calls are received, the primary Cisco RPMS server locally checks its session counts to perform session management. Periodically, these local counts are sent to the backup Cisco RPMS server for synchronization. When the session counts get close to a session limit, the primary Cisco RPMS server changes to get the session count from the backup server for each call to ensure an accurate session count is maintained in the primary and backup servers. When the session counts return to a lower level, Cisco RPMS goes back to local session counts to perform session management.
When a primary Cisco RPMS becomes unavailable, call handling is switched to the backup Cisco RPMS and any current calls are reconstructed. Session and resource counts are maintained and restored to the primary Cisco RPMS when it becomes available.
When the backup Cisco RPMS becomes unavailable, the following occurs:
While the backup Cisco RPMS is unavailable and until all calls that were active at the time the backup became unavailable are closed, it is possible that session and resource counts may be under-reported. This can cause oversubscription.
When the backup Cisco RPMS becomes available, the local counts on each primary Cisco RPMS are transmitted to the backup Cisco RPMS, DSM is enabled, and aggregated counts can be maintained for the entire system.
Database replication is accomplished using the Oracle Database Replication Manager and the Cisco RPMS DBServer component. All configuration is replicated among primary and backup RPMS servers. Configuration changes are automatically updated to peer Cisco RPMS servers through replication and the DBServer cache update mechanism.
Oracle replication ensures all Cisco RPMS databases are synchronized. However, because database replication is asynchronous, it does not maintain session counts. To ensure the backup Cisco RPMS knows the current session counts, the Distributed Session Manager (DSM) authority is maintained on the backup server.
The backup customer profile can contain all of the elements defined in a standard customer profile, including base-size or overflow parameters. However, when the connection between the Cisco NAS and Cisco RPMS is unavailable, session counting and session limits are not applied to incoming calls. Also, after the connection is reestablished, there is no synchronization of call counters between the Cisco NAS and Cisco RPMS.
If identical configurations are used across multiple primary Cisco RPMS servers and the servers use the same backup Cisco RPMS server, Distributed Session Management (DSM) technology can be used to aggregate the resource and session counts on the backup Cisco RPMS server.
Posted: Thu May 20 13:27:30 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.