- Finding Feature Information
- 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
- Additional References
- Feature Information for Per VRF for TACACS Servers
Per VRF for TACACS Servers
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.
- Finding Feature Information
- 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
- Additional References
- Feature Information for Per VRF for TACACS Servers
Finding Feature Information
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 Table at the end of this document.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Per VRF for TACACS Servers
- TACACS+ server access is required.
- Experience configuring TACACS+, AAA and per VRF AAA, and group servers is necessary.
Restrictions for Per VRF for TACACS Servers
- The VRF instance must be specified before per VRF for a TACACS+ server is configured.
Information About Per VRF for TACACS Servers
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.
How to Configure Per VRF for TACACS Servers
Configuring Per VRF on a TACACS Server
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:
DETAILED STEPS
Verifying Per VRF for TACACS Servers
To verify the per VRF TACACS+ configuration, perform the following steps:
Note |
The debug commands may be used in any order. |
DETAILED STEPS
Configuration Examples for Per VRF for TACACS Servers
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
Additional References
The following sections provide references related to Per VRF for TACACS+ Servers..
Related Documents
Related Topic |
Document Title |
---|---|
Configuring TACACS+ |
Configuring TACACS+ module. |
Per VRF AAA |
Per VRF AAA module. |
Security commands |
Cisco IOS Security Command Reference |
Standards
Standard |
Title |
---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
-- |
MIBs
MIB |
MIBs Link |
---|---|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
RFCs
RFC |
Title |
---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
-- |
Technical Assistance
Description |
Link |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feature Information for Per VRF for TACACS Servers
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 1 | Feature Information for Per VRF for TACACS+ Servers |
Feature Name |
Releases |
Feature Information |
---|---|---|
Per VRF for TACACS+ Servers |
12.3(7)T 12.2(33)SRA1 12.2(33)SXI 12.2(33)SXH4 12.2(54)SG |
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. This feature was introduced in Cisco IOS Release 12.3(7)T. This feature was integrated into Cisco IOS Release 12.2(33)SRA1. This feature was integrated into Cisco IOS Release 12.2(33)SXI. This feature was integrated into Cisco IOS Release 12.2(33)SXH4. The following commands were introduced or modified: ip tacacs source-interface, ip vrf forwarding (server-group), server-private (TACACS+). |
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.