An AAA profile is a set of characteristics that act as a pattern that you can assign to domain names. Once you create an AAA profile, you can map it between a PPP client’s domain name and certain AAA services on given interfaces. Using AAA profiles, you can:
An AAA profile contains a set of commands to control access for the incoming PPP subscriber. If no AAA profile is used, AAA continues as normal. The user’s name and domain name are not changed as a result of an AAA profile mapping.
![]() |
Note: There are two domain names with special meaning. The domain name none indicates that there is no domain name present in the subscriber’s name. For more information about none, see the section Mapping User Requests Without a Valid Domain Name. The domain name default indicates that no other match occurs. For more information about default, see the section Mapping User Requests Without a Configured Domain Name. |
You can control a PPP subscriber’s access to certain domains on given interfaces. As the administrator, you can use the deny command to prevent PPP subscribers from using unauthorized domain names. Using the allow command, you can allow PPP subscribers to use authorized domain names.
In this example, the administrator wants to restrict access of a PPP interface to the specific domain abc.com.
- host1(config)#aaa profile restrictToABC
- host1(config-aaa-profile)#allow abc.com
- host1(config-aaa-profile)#deny default
- host1(config-if)#ppp aaa-profile restrictToABC
When configured as such, the following is a likely scenario:
You can translate an original domain name to a new domain name via the translate command. The command allows you to create domain name aliases; that is, the grouping of multiple domain names into a single domain name. You can partition PPP subscribers with the same domain into separate domains, based on the PPP interface.
![]() |
Note: Partitioning subscribers does not cause modification of a user’s name or domain. |
When you use aliases, you greatly simplify the configuration process. When there are a large number of domains and you use aliases, it reduces the configuration volume, thus requiring less NVS and memory usage.
Example 1
In this example, an administrator wants to associate all subscribers of a PPP interface with a specific domain name.
- host1(config)#aaa profile forwardToXyz
- host1(config-aaa-profile)#translate default
xyz.com
- host1(config-if)#ppp aaa-profile forwardToXyz
When configured as such, the following scenario is typical:
![]() |
Note: If there is no matching entry in the AAA profile for the user’s domain name or for the domain name default, then AAA continues processing as if there were no AAA profile. If the user’s name does not contain a domain name, then AAA attempts to match to the domain name none in the AAA profile. If there is no entry for none, then AAA attempts to match for the domain name default in the AAA profile. If there is no entry for either none or default, then AAA continues processing as if there were no AAA profile. |
Example 2
In this example, an administrator wants to use aliases; that is, to associate multiple domain names with a specific domain name and not allow other domain names.
- host1(config)#aaa profile toAbc
- host1(config-aaa-profile)#translate abc1.com
abc.com
- host1(config-aaa-profile)#translate abc2.com
abc.com
- host1(config-aaa-profile)#translate abc3.com
abc.com
- host1(config-aaa-profile)#deny default
- host1(config-if)#ppp aaa-profile toAbc
When configured as such, the following scenario is typical:
![]() |
Note: If there is no matching entry in the AAA profile for the user’s domain name or for the domain name default, then AAA continues processing as if there were no AAA profile. If the user’s name does not contain a domain name, then AAA attempts to match to the domain name none in the AAA profile. If there is no entry for none, then AAA attempts to match for the domain name default in the AAA profile. If there is no entry for either none or default, then AAA continues processing as if there were no AAA profile. |
aaa profile
- host1(config)#aaa profile boston123
allow
- host1(config-aaa-profile)#allow xyz.com
deny
- host1(config-aaa-profile)#deny xyz.com
ppp aaa-profile
![]() |
Note: Although an AAA profile and an interface profile have similar functionality, they are not related and should be treated differently. |
- host1(config-if)#ppp aaa-profile westford24
translate
- host1(config-aaa-profile)#translate abc.com
xyz.com
You can manually configure the NAS-Port-Type RADIUS attribute (attribute 61) in AAA profiles for ATM and Ethernet interfaces. Doing so allows AAA profiles to determine the NAS port type for a given connection.
To set the NAS-Port-Type attribute for ATM or Ethernet interfaces:
- host1(config)#aaa profile nasPortType
- host1(config-aaa-profile)#nas-port-type atm
wireless-80211
- host1(config-aaa-profile)#nas-port-type ethernet
wireless-cable
aaa profile
- host1(config)#aaa profile nasPortType
nas-port-type atm
- host1(config-aaa-profile)#nas-port-type atm
wireless-80211
nas-port-type ethernet
- host1(config-aaa-profile)#nas-port-type ethernet
wireless-80211
You can specify a service description that will be associated with an AAA profile. The description can then be exported through RADIUS by the Service-Description attribute (RADIUS attribute 26-53) in AAA profiles.
To set the Service-Description attribute:
- host1(config)#aaa profile xyzCorpPro2
- host1(config-aaa-profile)#service-description
bos-xyzcorp
aaa profile
- host1(config)#aaa profile xyzCorpPro2
service-description
- host1(config-aaa-profile)#service-description
service11