Configuring Network Access Servers

This chapter describes how to configure network access servers (NASes) to communicate with Cisco Resource Pool Manager Server (Cisco RPMS).

Cisco RPMS and NASes communicate via the Resource Management Protocol (RMP). RMP is a TACACS+ based meta-protocol that defines exchanged resource management information.

Figure B-1: Components of Cisco RPMS

Backup customer profiles are designed to ensure that selected customers do not lose access to the NASes if communication between the NASes and the Cisco RPMS fails. Although a backup customer profile contains the elements of a standard customer profile, when the connection between the NASes and the Cisco RPMS fails, session counting does not occur and session limits do not apply.

Configuring the NAS to Communicate with Cisco RPMS

To communicate with Cisco RPMS, each NAS must be properly configured. This section describes how to configure a NAS to communicate with Cisco RPMS.

Step	Command	Purpose
1	Router# configure terminal Enter configuration commands, one per line. End with Ctrl-z.	Enter global configuration mode.
2	Router(config)# resource-pool enable	Turn on Resource Pool Management.
3	router(config)# resource-pool group resource name	Create one or more physical resource groups.
4	router(config-resource-group)# range {limit number \| port range} router(config-resource-group)# exit	Identify a range of resources to use inside the resource group. Modems are specified by ports. ISDN B channels are specified by channel limits.
5	Router(config)# aaa new-model	Initiate the AAA access control system.
6	router(config)# tacacs-server host address	Enter the RPMS server's IP address. This address must match the IP address specified in Step 7 via the host address command.
7	Router(config)# aaa group server tacacs+ name	Create a TACACS+ server group.¹
8	Router(config-sg-tacacs+)# host address Router(config-sg-tacacs+)# exit	Add the RPMS server's IP address to the server group.² Resource pool manager will look here and contact these hosts.
9	router(config)# resource-pool aaa protocol group name	Associate the TACACS+ server group to the resource pool management functions. You must use the same name specified in Step 6.³
10	router (config)# vpdn enable	Turn on VPDN support.

Table B-1: Configuring a NAS to Communicate with Cisco RPMS

Step Command Purpose

1

Router# configure terminal
Enter configuration commands, one per line. End with Ctrl-z.

Enter global configuration mode.

2

Router(config)# resource-pool enable

Turn on Resource Pool Management.

3

router(config)# resource-pool group resource name

Create one or more physical resource groups.

4

router(config-resource-group)# range {limit number | port range}
router(config-resource-group)# exit

Identify a range of resources to use inside the resource group. Modems are specified by ports. ISDN B channels are specified by channel limits.

5

Router(config)# aaa new-model

Initiate the AAA access control system.

6

router(config)# tacacs-server host address

Enter the RPMS server's IP address. This address must match the IP address specified in Step 7 via the host address command.

7

Router(config)# aaa group server tacacs+ name

Create a TACACS+ server group.¹

8

Router(config-sg-tacacs+)# host address

Router(config-sg-tacacs+)# exit

Add the RPMS server's IP address to the server group.² Resource pool manager will look here and contact these hosts.

9

router(config)# resource-pool aaa protocol group name

Associate the TACACS+ server group to the resource pool management functions. You must use the same name specified in Step 6.³

10

router (config)# vpdn enable

Turn on VPDN support.

¹Steps 6 through 9 configure the AAA authorization and accounting start/stop records needed to work with the RPMS server.
²You can specify one or more hosts with this command. Additional entries act as backups. Enter the command for each host entry.
³To include enhanced start/stop resource manager records to PPP accounting, enter the resource-pool aaa accounting ppp global configuration command. Cisco recommends that you thoroughly understand how these new start/stop records will affect your current accouting structure before you use this command.

Note For more information on these commands, refer to the Cisco Resource Pool Manager Feature Module.

Configuring Backup Profiles

This information is not currently available in this document. For more information, see the Cisco Resource Pool Manager Feature Module.

Table of Contents