|
|
This chapter describes the variety of dial service scenarios available with Cisco Resource Pool Manager Server (RPMS). These scenarios include:
This network configuration can be used by serice providers and others to provide wholesale (VPDN) dial service to corporate customers and other ISPs, and retail dial service to end users for Internet/intranet access.
Figure 3-1 shows Cisco RPMS with multiple connections to NASes for both wholesale (VPDN) and retail dial service. The wholesale (VPDN) connections are forwarded to VPDN tunnels using domain names or DNIS numbers. The retail connections use the local AAA server for user authentication before directing calls to the Internet/intranet.
Using Cisco RPMS with a local AAA server provides the following call management and dial service offerings:
The setup and configurations of each call management and dial service offering are described separately. The configurations outlined in this section use the following:
| Call Management | Dial Service | Cisco RPMS Configuration |
|---|---|---|
Before Calls Are Answered | DNIS-Based Wholesale (VPDN) | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>VPDN 5. Configuration>Customer |
Before Calls Are Answered | DNIS-Based Retail | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>Customer |
After Calls Are Answered | DNIS-Based Wholesale (VPDN) | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>VPDN 5. Configuration>Customer |
After Calls Are Answered | Domain Name-Based Wholesale (VPDN) | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>VPDN 5. Configuration>Customer |
After Calls Are Answered | Non-DNIS Retail | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>Customer |
Using this type of call management, before calls are answered, Cisco RPMS subjects incoming calls to the configured DNIS groups/call types matching, enforces the customer profile sessions limits, and allocates resources according to the assigned resource groups. If the matching DNIS group/call type are configured for the call, the session/overflow limits are not exceeded, and resources are available, Cisco RPMS accepts the call and sends a call-accept message to the NAS and call processing continues. If a resource is not available, a channel not available (CNA) or busy call treatment can be used. When the telco group spans multiple NASes, CNA call treatment enables the switch to hunt across NASes for an available resource. If a customer profile is not available, the call treatment can be configured to be either no answer or busy.
To enable DNIS-based wholesale (VPDN) dial service along with applying call management before calls are answered, the following Cisco RPMS configurations are used:
user = dnis:9495555555{
profile_id = 23
profile_cycle = 4
radius=Cisco11.3 {
check_items= {
2=cisco
}
reply_attributes= {
9,1="vpdn:ip-addresses=10.5.5.13"
9,1="vpdn:tunnel-id=isp"
9,1="vpdn:nas-password=cisco"
9,1="vpdn:gw-password=cisco"
Make the following entries in the NAS configuration files:
aaa group server tacacs+ coney server 10.3.15.2 !
aaa group server tacacs+ pagoda server 10.6.8.25 !
aaa authentication login default pagoda //--it uses tacacs server group "pagoda" for telnet authentication--// aaa authentication ppp default pagoda //--it uses tacacs server group "pagoda" for ppp user authentication--//
aaa accounting network default start-stop group pagoda //--it uses tacacs server group "pagoda" for accounting information --//
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30 resource-pool aaa accounting ppp resource-pool aaa protocol group coney
vpdn enable //--to enable vpdn--//
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
The home gateway router serves as the terminating device for the VPDN tunnels used for Cisco RPMS wholesale (VPDN) dial service. Make the following entries in the home gateway configuration files:
aaa new-model aaa authentication login default tacacs+ aaa authentication ppp default tacacs+ aaa authorization network default tacacs+
vpdn enable
vpdn-group 1 accept dialin l2f virtual-template 1 remote isp local name hg ! vpdn-group 2 accept dialin l2tp virtual-template 1 remote isp local name hg
tacacs-server host 10.5.55.47 tacacs-server key cisco
The Cisco RPMS Maximum MLP bundles setting specifies the maximum number of connections that can open multilink connections in this VPDN group. The maximum links per bundle setting specifies the maximum number of links for each bundle. For example, if standard ISDN users will be part of this VPDN group, limit this setting to two links per bundle. If video conferencing will be used, increase this setting to accommodate the necessary bandwidth (usually six links).
For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
When more than one home gateway IP address is configured, sessions are automatically distributed among the IP addresses. If a connection fails, sessions are automatically distributed among the remaining IP addresses. If these home gateways will receive MLP connections, you must configure Stack Group Bidding Protocol (SGBP).
To configure SGBP on multiple home gateways, ensure the following configurations entries are added to the home gateway configuration files. The NAS is called qa5300e. The off-load router is called qa5300g. The second home gateway is called apm7200.
multilink virtual-template 1 ! sgbp group mystack sgbp seed-bid offload sgbp member qa5300e 10.1.0.33 sgbp member qa5300g 10.5.5.31 vpdn enable vpdn multihop
multilink virtual-template 1 ! sgbp group mystack sgbp member apm7200 10.5.5.13 sgbp member qa5300e 10.1.0.33 vpdn enable vpdn multihop
Make the following entries in the NAS configuration files:
aaa group server tacacs+ coney server 10.3.15.2 !
aaa group server tacacs+ pagoda server 10.6.8.25 !
aaa authentication login default pagoda //--it uses tacacs server group "pagoda" for telnet authentication--// aaa authentication ppp default pagoda //--it uses tacacs server group "pagoda" for ppp user authentication--//
aaa accounting network default start-stop group pagoda //--it uses tacacs server group "pagoda" for accounting information --//
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30 resource-pool aaa accounting ppp resource-pool aaa protocol group coney
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
Using this type of call management, Cisco RPMS answers all calls using a default DNIS group/call type, enforces the session/overflow limits defined in a default customer profile, and assigns the available resources from the resource groups assigned to the default customer profile. If the session/overflow limits are not exceeded, and resources are available, Cisco RPMS continues processing the call. If a resource is not available, a channel not available (CNA) or busy call treatment can be used. When the telco group spans multiple NASes, CNA call treatment enables the switch to hunt across NASes for an available resource. If a default customer profile is not available, the call treatment can be configured to be no answer or busy.
The advantages of domain name VPDN dial service are that DNIS numbers are not used and user groups can be easier to manage. In addition, new numbers do not need to be ordered each time a customer is added. However, in order for a user to access the home gateway through domain name wholesale service, the domain name must appear in the user ID. For example, if the username is "jdoe" and the domain name is "company.com," the user ID would be "jdoe@company.com."
To enable domain name-based wholesale (VPDN) dial service along with applying call management after calls are answered, the following Cisco RPMS configurations are used:
user = domain:cisco.com{
profile_id = 23
profile_cycle = 4
radius=Cisco11.3 {
check_items= {
2=cisco
}
reply_attributes= {
9,1="vpdn:ip-addresses=10.5.5.13"
9,1="vpdn:tunnel-id=isp"
9,1="vpdn:nas-password=cisco"
9,1="vpdn:gw-password=cisco"
Make the following entries in the NAS configuration files:
aaa group server tacacs+ coney server 10.3.15.2 !
aaa group server tacacs+ pagoda server 10.6.8.25 !
aaa authentication login default pagoda //--it uses tacacs server group "pagoda" for telnet authentication--// aaa authentication ppp default pagoda //--it uses tacacs server group "pagoda" for ppp user authentication--//
aaa accounting network default start-stop group pagoda //--it uses tacacs server group "pagoda" for accounting information --//
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30 resource-pool aaa accounting ppp resource-pool aaa protocol group coney
vpdn enable //--to enable vpdn--//ns
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
The Cisco RPMS Maximum MLP bundles setting specifies the maximum number of connections that can open multilink connections in this VPDN group. The maximum links per bundle setting specifies the maximum number of links for each bundle. For example, if standard ISDN users will be part of this VPDN group, limit this setting to two links per bundle. If video conferencing will be used, increase this setting to accommodate the necessary bandwidth (usually six links).
For the complete NAS configuration file, see "Configuration Files". For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
The home gateway router serves as the terminating device for the VPDN tunnels used for Cisco RPMS wholesale (VPDN) dial service. Make the following entries in the home gateway configuration files:
aaa new-model aaa authentication login default tacacs+ aaa authentication ppp default tacacs+ aaa authorization network default tacacs+
vpdn enable
vpdn-group 1 accept dialin l2f virtual-template 1 remote isp local name hg ! vpdn-group 2 accept dialin l2tp virtual-template 1 remote isp local name hg
tacacs-server host 10.5.55.47 tacacs-server key cisco
When more than one home gateway IP address is configured, sessions are automatically distributed among the IP addresses. If a connection fails, sessions are automatically distributed among the remaining IP addresses. If these home gateways will receive MLP connections, you must configure Stack Group Bidding Protocol (SGBP).
To configure SGBP on multiple home gateways, ensure the following configurations are added to the home gateway configuration files. The NAS is called qa5300e. The off-load router is called qa5300g. The second home gateway is called apm7200.
multilink virtual-template 1 ! sgbp group mystack sgbp seed-bid offload sgbp member qa5300e 10.1.0.33 sgbp member qa5300g 10.5.5.31 vpdn enable vpdn multihop
multilink virtual-template 1 ! sgbp group mystack sgbp member apm7200 10.5.5.13 sgbp member qa5300e 10.1.0.33 vpdn enable vpdn multihop
To enable DNIS-based wholesale (VPDN) dial service along with applying call management after calls are answered, the following Cisco RPMS configurations are used:
user = dnis:9495555555{
profile_id = 23
profile_cycle = 4
radius=Cisco11.3 {
check_items= {
2=cisco
}
reply_attributes= {
9,1="vpdn:ip-addresses=10.5.5.13"
9,1="vpdn:tunnel-id=isp"
9,1="vpdn:nas-password=cisco"
9,1="vpdn:gw-password=cisco"
Make the following entires in the NAS configuration files:
aaa group server tacacs+ coney server 10.3.15.2 !
aaa group server tacacs+ pagoda server 10.6.8.25 !
aaa authentication login default pagoda //--it uses tacacs server group "pagoda" for telnet authentication--// aaa authentication ppp default pagoda //--it uses tacacs server group "pagoda" for ppp user authentication--//
aaa accounting network default start-stop group pagoda //--it uses tacacs server group "pagoda" for accounting information --//
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30 resource-pool aaa accounting ppp resource-pool aaa protocol group coney
vpdn enable //--to enable vpdn--//ns
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
The home gateway router serves as the terminating device for the VPDN tunnels used for Cisco RPMS wholesale (VPDN) dial service. Make the following entries in the home gateway configuration files:
aaa new-model aaa authentication login default tacacs+ aaa authentication ppp default tacacs+ aaa authorization network default tacacs+
vpdn enable
vpdn-group 1 accept dialin l2f virtual-template 1 remote isp local name hg ! vpdn-group 2 accept dialin l2tp virtual-template 1 remote isp local name hg
tacacs-server host 10.5.55.47 tacacs-server key cisco
The Cisco RPMS Maximum MLP bundles setting specifies the maximum number of connections that can open multilink connections in this VPDN group. The maximum links per bundle setting specifies the maximum number of links for each bundle. For example, if standard ISDN users will be part of this VPDN group, limit this setting to two links per bundle. If video conferencing will be used, increase this setting to accommodate the necessary bandwidth (usually six links).
For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
When more than one home gateway IP address is configured, sessions are automatically distributed among the IP addresses. If a connection fails, sessions are automatically distributed among the remaining IP addresses. If these home gateways will receive MLP connections, you must configure Stack Group Bidding Protocol (SGBP).
To configure SGBP on multiple home gateways, ensure the following configurations are added to the home gateway configuration files. The NAS is called qa5300e. The off-load router is called qa5300g. The second home gateway is called apm7200.
multilink virtual-template 1 ! sgbp group mystack sgbp seed-bid offload sgbp member qa5300e 10.1.0.33 sgbp member qa5300g 10.5.5.31 vpdn enable vpdn multihop
multilink virtual-template 1 ! sgbp group mystack sgbp member apm7200 10.5.5.13 sgbp member qa5300e 10.1.0.33 vpdn enable vpdn multihop
Make the following entries in the NAS configuration files:
aaa group server tacacs+ coney server 10.3.15.2 !
aaa group server tacacs+ pagoda server 10.6.8.25 !
aaa authentication login default pagoda //--it uses tacacs server group "pagoda" for telnet authentication--// aaa authentication ppp default pagoda //--it uses tacacs server group "pagoda" for ppp user authentication--//
aaa accounting network default start-stop group pagoda //--it uses tacacs server group "pagoda" for accounting information --//
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30 resource-pool aaa accounting ppp resource-pool aaa protocol group coney
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
This network configuration is used to provide wholesale (VPDN) dial service to corporate customers and other ISPs when a local AAA server is not present. Without a local AAA server, retail dial service is not available.
Figure 3-2 shows Cisco RPMS with multiple connections to NASes. The wholesale (VPDN) connections are forwarded to VPDN tunnels using domain names or DNIS numbers.
Using Cisco RPMS without a local AAA server provides the following call management and dial service offerings:
The setup and configuration of each call management and dial service offering is described separately. The configurations outlined in this section use a single Cisco RPMS, three Cisco AS5300s without a local AAA server.
| Call Management | Dial Service | Cisco RPMS Configuration |
|---|---|---|
Before Calls Are Answered | DNIS-Based Wholesale (VPDN) | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>VPDN 5. Configuration>Customer |
After Calls Are Answered | DNIS-Based Wholesale (VPDN) | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>VPDN 5. Configuration>Customer |
After Calls Are Answered | Domain Name Based Wholesale (VPDN) | 1. Configuration>Customer 2. Configuration>DNIS 3. Configuration>Resources>Group and 4. Configuration>VPDN 5. Configuration>Customer |
Using this type of call management, before calls are answered, Cisco RPMS subjects incoming calls to the configured DNIS groups/call types matching, enforces the customer profile sessions limits, and allocates resources according to the assigned resource groups. If the matching DNIS group/call type are configured for the call, the session/overflow limits are not exceeded, and resources are available, Cisco RPMS accepts the call and sends a call-accept message to the NAS and call processing continues. If a resource is not available, a channel not available (CNA) or busy call treatment can be used. When the telco group spans multiple NASes, CNA call treatment enables the switch to hunt across NASes for an available resource. If a customer profile is not available, the call treatment can be configured to be no answer or busy.
This type of dial service allows for the sharing of ports among wholesale (VPDN) customers using the DNIS numbers as the means to differentiate customers and service levels. No domain name is used so users do not enter a domain name with their user ID. However, DNIS numbers must be available for each VPDN customer.
To enable wholesale (VPDN) dial service along with applying call management before calls are answered, use the following Cisco RPMS configurations:
Make the following entries in the NAS configuration files:
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30
vpdn enable //--to enable vpdn--//
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
The home gateway router serves as the terminating device for the VPDN tunnels used for Cisco RPMS wholesale (VPDN) dial service. Make the following entries in the home gateway configuration files:
aaa new-model aaa authentication login default tacacs+ aaa authentication ppp default tacacs+ aaa authorization network default tacacs+
vpdn enable
vpdn-group 1 accept dialin l2f virtual-template 1 remote isp local name hg ! vpdn-group 2 accept dialin l2tp virtual-template 1 remote isp local name hg
tacacs-server host 10.5.55.47 tacacs-server key cisco
The Cisco RPMS Maximum MLP bundles setting specifies the maximum number of connections that can open multilink connections in this VPDN group. The maximum links per bundle setting specifies the maximum number of links for each bundle. For example, if standard ISDN users will be part of this VPDN group, limit this setting to two links per bundle. If video conferencing will be used, increase this setting to accommodate the necessary bandwidth (usually six links).
For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
When more than one home gateway IP address is configured, sessions are automatically distributed among the IP addresses. If a connection fails, sessions are automatically distributed among the remaining IP addresses. If these home gateways will receive MLP connections, you must configure Stack Group Bidding Protocol (SGBP).
To configure SGBP on multiple home gateways, ensure the following configuration entries are added to the home gateway configuration files. The NAS is called qa5300e. The off-load router is called qa5300g. The second home gateway is called apm7200.
multilink virtual-template 1 ! sgbp group mystack sgbp seed-bid offload sgbp member qa5300e 10.1.0.33 sgbp member qa5300g 10.5.5.31 vpdn enable vpdn multihop
multilink virtual-template 1 ! sgbp group mystack sgbp member apm7200 10.5.5.13 sgbp member qa5300e 10.1.0.33 vpdn enable vpdn multihop
For the complete home gateway configuration, see "Configuration Files". For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
Using this type of call management, Cisco RPMS answers all calls, using a default DNIS group/call type, enforces the session/overflow limits defined in a default customer profile, and assigns the available resources from the resource groups assigned to the default customer profile. If the session/overflow limits are not exceeded, and resources are available, Cisco RPMS continues processing the call. If a resource is not available, a channel not available (CNA) or busy call treatment can be used. When the telco group spans multiple NASes, CNA call treatment enables the switch to hunt across NASes for an available resource. If a default customer profile is not available, the call treatment can be configured to be no answer or busy.
The advantages of domain name VPDN dial service is that DNIS numbers are not used and user groups can be easier to manage. In addition, new numbers do not need to be ordered each time a customer is added. However, in order for a user to access the home gateway through domain name wholesale service, the domain name must appear in the user ID. For example, if the username is "jdoe" and the domain name is "company.com", the user ID would be "jdoe@company.com".
To enable domain name-based wholesale (VPDN) dial service along with applying call management after calls are answered, use the following Cisco RPMS configurations:
Make the following entries in the NAS configuration files:
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30
vpdn enable //--to enable vpdn--//ns
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
The home gateway router serves as the terminating device for the VPDN tunnels used for Cisco RPMS wholesale (VPDN) dial service. Make the following entires in the home gateway configuration files:
aaa new-model aaa authentication login default tacacs+ aaa authentication ppp default tacacs+ aaa authorization network default tacacs+
vpdn enable vpdn multihop
vpdn-group 1 accept dialin l2f virtual-template 1 remote isp local name hg ! vpdn-group 2 accept dialin l2tp virtual-template 1 remote isp local name hg
tacacs-server host 10.5.55.47 tacacs-server key cisco
The Cisco RPMS Maximum MLP bundles setting specifies the maximum number of connections that can open multilink connections in this VPDN group. The maximum links per bundle setting specifies the maximum number of links for each bundle. For example, if standard ISDN users will be part of this VPDN group, limit this setting to two links per bundle. If video conferencing will be used, increase this setting to accommodate the necessary bandwidth (usually six links).
For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
When more than one home gateway IP address is configured, sessions are automatically distributed among the IP addresses. If a connection fails, sessions are automatically distributed among the remaining IP addresses. If these home gateways will receive MLP connections, you must configure Stack Group Bidding Protocol (SGBP).
To configure SGBP on multiple home gateways, ensure the following configurations are added to the home gateway configuration files. The NAS is called qa5300e. The off-load router is called qa5300g. The second home gateway is called apm7200.
sgbp group mystack sgbp seed-bid offload sgbp member qa5300e 10.1.0.33 sgbp member qa5300g 10.5.5.31 vpdn enable vpdn multihop
multilink virtual-template 1 ! sgbp group mystack sgbp member apm7200 10.5.5.13 sgbp member qa5300e 10.1.0.33 vpdn enable vpdn multihop
For the complete NAS configuration file, see "Configuration Files". For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
Make the following entries in the NAS configuration files:
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30
vpdn enable //--to enable vpdn--//ns
tacacs-server host 10.6.8.25 tacacs-server host 10.3.15.2 tacacs-server key cisco tacacs-server administration
The home gateway router serves as the terminating device for the VPDN tunnels used for Cisco RPMS wholesale (VPDN) dial service. Make the following entries in the home gateway configuration files:
aaa new-model aaa authentication login default tacacs+ aaa authentication ppp default tacacs+ aaa authorization network default tacacs+
vpdn enable vpdn multihop
vpdn-group 1 accept dialin l2f virtual-template 1 remote isp local name hg ! vpdn-group 2 accept dialin l2tp virtual-template 1 remote isp local name hg
tacacs-server host 10.5.55.47 tacacs-server key cisco
The Cisco RPMS Maximum MLP bundles setting specifies the maximum number of connections that can open multilink connections in this VPDN group. The maximum links per bundle setting specifies the maximum number of links for each bundle. For example, if standard ISDN users will be part of this VPDN group, limit this setting to two links per bundle. If video conferencing will be used, increase this setting to accommodate the necessary bandwidth (usually six links).
For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
When more than one home gateway IP address is configured, sessions are automatically distributed among the IP addresses. If a connection fails, sessions are automatically distributed among the remaining IP addresses. If these home gateways will receive MLP connections, you must configure Stack Group Bidding Protocol (SGBP).
To configure SGBP on multiple home gateways, ensure the following configurations are added to the home gateway configuration files. The NAS is called qa5300e. The off-load router is called qa5300g. The second home gateway is called apm7200.
sgbp group mystack sgbp seed-bid offload sgbp member qa5300e 10.1.0.33 sgbp member qa5300g 10.5.5.31 vpdn enable vpdn multihop
multilink virtual-template 1 ! sgbp group mystack sgbp member apm7200 10.5.5.13 sgbp member qa5300e 10.1.0.33 vpdn enable vpdn multihop
For the complete NAS configuration file, see "Configuration Files". For more detailed configuration and VPN information, refer to Cisco Access VPN Solutions Using Tunneling Technology.
Resource pool management offers a call discrimination feature that enables rejection of calls based on a DNIS group and call type filter. When a call arrives at the NAS, the DNIS and call type are matched against a table of disallowed calls. If the DNIS and call type match entries in this table, the call is rejected.
Call discrimination can be used by customers to manage billing of calls to different types of resources. If the service provider has a different billing structure for modem calls and for digital calls, each call type will be assigned a different DNIS. When a user calls the DNIS, the call type must be of the allowed call type or the call is rejected.
Call discrimination in Cisco RPMS subjects calls to DNIS group and call type (bearer capability) restrictions specified in a call discrimination table so calls can be blocked and disconnected before they are assigned to Cisco NAS resources. For example, call discrimination can be used to restrict a specific DNIS group to a only modem calls by creating call discrimination settings for the DNIS group and the other call types (digital, V.110, and V.120). (See Figure 3-3.)
To configure call discrimination in Cisco RPMS:
Figure 3-3 illustrates the Cisco RPMS call discrimination feature.
Data over Voice Bearer Services (DOVBS) is a dial service that uses a customer profile and an assigned resource group of digital resources to direct data calls with a speech call type to HDLC controllers.
To support ISDN DOVBS, use a DNIS group and a configured customer profile to direct the speech call to the appropriate digital resource.
The DNIS group that is assigned to the customer profile should have a call type of speech. The resource group assigned to this customer profile will be digital resources and also have a call type of speech, so the call will terminate on an HDLC controller rather than a modem.
To DOVBS, use the following Cisco RPMS configurations:
Perform any other Cisco RPMS configuration options.
The call information between the Cisco SC2200 and Cisco Resource Pool Manager Server communicates as follows:
Figure 3-4 illustrates Cisco RPMS and SS7.
If a Cisco RPMS is being used to manage the resources in a group of network access servers, the information for the accounting records is forwarded from the Cisco RPMS to the network access server for each call. The NAS then creates the new AAA accounting start and stop records for customer profiles and forwards the records to your local AAA accounting server.
At the same time, the Cisco RPMS creates a call detail record for each call. You will use the call detail record for billing purposes if you are not using local AAA accounting server in your network.
The sample local AAA accounting data shows start and stop records for DNIS-based wholesale (VPDN) using Cisco RPMS.
A typical local AAA accounting start record looks like this:
Tue Mar 23 10:44:19 1999 |
Tue Mar 23 10:44:41 1999 |
Call detail records contain the following data:
Customer | NAS name | Reference number | Tunnel name |
Cisco RPMS offers a fault-tolerant and resilient dial service management solutions.
Figure 3-5 illustrates a fault tolerant architecture using Cisco RPMS.
Cisco RPMS allows you to 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. Although this might affect performance when the customer profile gets close to its session limit, it ensures an accurate session count is maintained in the primary and backup servers, and prevents oversubscription. When the session counts return to a lower level, Cisco RPMS goes back to local session counts to perform session management.
This is accomplished using the Oracle Database Replication Manager and the Cisco RPMS DBServer component. All configuration is 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.
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 Management (DSM) authority is maintained on the backup server.
This mechanism involves the NAS storing an attribute containing pertinent data about a call so that it can be used by the backup in a fail-over situation to rebuild the context of an active call that was opened on the primary RPMS. The rebuilt context ensures that the proper counters can be maintained and that a meaningful Call Detail Record is generated for the call when it closes.
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.
To enable a backup profile:
resource-pool enable resource-pool call treatment resource channel-not-available resource-pool call treatment profile no-answer ! resource-pool group resource digital range limit 10 ! resource-pool group resource async1 range port 1/0 1/10 ! resource-pool group resource async2 range port 1/11 1/20 ! resource-pool group resource async3 range port 1/21 1/30 ! resource-pool aaa protocol group redline local ! tacacs-server host 150.1.1.4 port 49
If identical configurations are used across multiple primary Cisco RPMS servers, Distributed Session Management (DSM) technology can be used to aggregate the resource and session counts on a centralized Cisco RPMS server. This centralized Cisco RPMS server can also be configured as a backup server for multiple primary servers.
Figure 3-6 illustrates a DSM architecture across several Cisco RPMS servers.
This configuration can be used to provide wholesale (VPDN) dial service to corporate customers and retail dial service to end users from a single NAS using Cisco IOS Resource Pool Manager (RPM) without Cisco RPMS server solution.
Figure 3-7 shows multiple connections to a NAS. In this scenario, some connections can be forwarded through VPDN tunnels for wholesale (VPDN) dial service. Others can be authenticated locally for retail dial service.
This configuration does not use Cisco RPMS. If more than one Cisco NAS is used, all configuration must be manually performed on each NAS using Cisco IOS commands, and resource usage information is not shared between NASes.
Posted: Thu May 20 13:27:44 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.