The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Per VRF for TACACS+ Servers feature allows per virtual route forwarding (per VRF) to be configured for authentication, authorization, and accounting (AAA) on TACACS+ servers.
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Per VRF for TACACS+ Servers" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
•Prerequisites for Per VRF for TACACS+ Servers
•Restrictions for Per VRF for TACACS+ Servers
•Information About Per VRF for TACACS+ Servers
•How to Configure Per VRF for TACACS+ Servers
•Configuration Examples for Per VRF for TACACS+ Servers
•TACACS+ server access is required.
•Experience configuring TACACS+, AAA and per VRF AAA, and group servers is necessary.
•The VRF instance must be specified before per VRF for a TACACS+ server is configured.
To configure the Per VRF for TACACS+ Servers feature, the following concept should be understood:
•Per VRF for TACACS+ Servers Overview
The Per VRF for TACACS+ Servers feature allows per VRF AAA to be configured on TACACS+ servers. Prior to Cisco IOS Release 12.3(7)T, this functionality was available only on RADIUS servers.
This section contains the following procedures:
•Configuring Per VRF on a TACACS+ Server (required)
•Verifying Per VRF for TACACS+ Servers (optional)
The initial steps in this procedure are used to configure AAA and a server group, create a VRF routing table, and configure an interface. Steps 10 through 13 are used to configure the per VRF on a TACACS+ server feature:
1. enable
2. configure terminal
3. ip vrf vrf-name
4. rd route-distinguisher
5. exit
6. interface interface-name
7. ip vrf forwarding vrf-name
8. ip address ip-address mask [secondary]
9. exit
10. aaa group server tacacs+ group-name
11. server-private {ip-address | name} [nat] [single-connection] [port port-number] [timeout seconds] [key [0 | 7] string]
12. ip vrf forwarding vrf-name
13. ip tacacs source-interface subinterface-name
14. exit
To verify the per VRF TACACS+ configuration, perform the following steps:
Note The debug commands may be used in any order.
1. enable
2. debug tacacs authentication
3. debug tacacs authorization
4. debug tacacs accounting
5. debug tacacs packets
This section includes the following configuration example:
•Configuring Per VRF for TACACS+ Servers: Example
The following output example shows that the group server tacacs1 is configured for per VRF AAA services:
aaa group server tacacs+ tacacs1
server-private 10.1.1.1 port 19 key cisco
ip vrf forwarding cisco
ip tacacs source-interface Loopback0
ip vrf cisco
rd 100:1
interface Loopback0
ip address 10.0.0.2 255.0.0.0
ip vrf forwarding cisco
The following sections provide references related to Per VRF for TACACS+ Servers..
|
|
---|---|
Configuring TACACS+ |
"Configuring TACACS+" module. |
Per VRF AAA |
"Per VRF AAA" module. |
Security commands |
|
|
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
|
|
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.