Scribd Logo
Upload

Welcome to Scribd!

  • 230 views

    1) Configure AAA

    Uploaded by

    Mirko Sapia

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    1) Configure AAA

    Uploaded by

    Mirko Sapia
    230 views5 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    230 views5 pages

    1) Configure AAA

    Uploaded by

    Mirko Sapia

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 5
    At a glance
    Powered by AI
    The document discusses configuring local and server-based AAA authentication on Cisco routers.

    Local AAA authentication using the local database and server-based AAA authentication using TACACS+ and RADIUS servers are configured.

    The steps include configuring a local username, enabling AAA, configuring AAA authentication to use the local database, and applying the authentication method to login lines.

    Configure AAA Authentication on Cisco Routers

    Instructor Version

    Topology Diagram

    Addressing Table

    Device Interface IP Address Subnet Mask

    Fa0/0 192.168.1.1 255.255.255.0


    R1
    S0/0/0 10.1.1.2 255.255.255.252
    S0/0/0 10.1.1.1 255.255.255.252
    R2 Fa0/0 192.168.2.1 255.255.255.0
    S0/0/1 10.2.2.1 255.255.255.252
    S0/0/1 10.2.2.2 255.255.255.252
    R3
    Fa0/0 192.168.3.1 255.255.255.0
    TACACS+ Server NIC 192.168.2.2 255.255.255.0
    RADIUS Server NIC 192.168.3.2 255.255.255.0
    PC-A NIC 192.168.1.3 255.255.255.0
    PC-B NIC 192.168.2.3 255.255.255.0
    PC-C NIC 192.168.3.3 255.255.255.0

    All contents are Copyright © 1992–2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 5
    CCNA Security

    Learning Objectives
     Configure a local user account on R1 and authenticate on the console and VTY lines using local AAA.
     Verify local AAA authentication from the R1 console and the PC-A client.
     Configure a server-based AAA authentication using TACACS+.
     Verify server-based AAA authentication from PC-B client.
     Configure a server-based AAA authentication using RADIUS.
     Verify server-based AAA authentication from PC-C client.

    Introduction
    The network topology shows routers R1, R2 and R3. Currently all administrative security is based on knowledge
    of the enable secret password. Your task is to configure and test local and server-based AAA solutions.
    You will create a local user account and configure local AAA on router R1 to test the console and VTY logins.
     User account: Admin1 and password admin1pa55
    You will then configure router R2 to support server-based authentication using the TACACS+ protocol. The
    TACACS+ server has been pre-configured with the following:
     Client: R2 using the keyword tacacspa55
     User account: Admin2 and password admin2pa55
    Finally, you will configure router R3 to support server-based authentication using the RADIUS protocol. The
    RADIUS server has been pre-configured with the following:
     Client: R3 using the keyword radiuspa55
     User account: Admin3 and password admin3pa55
    The routers have also been pre-configured with the following:
     Enable secret password: ciscoenpa55
     RIP version 2
    Note: The console and VTY lines have not been pre-configured.

    Task 1: Configure Local AAA Authentication for Console Access on R1

    Step 1. Test connectivity.


     Ping from PC-A to PC-B.
     Ping from PC-A to PC-C.
     Ping from PC-B to PC-C.

    Step 2. Configure a local username on R1.


    Configure a username of Admin1 and secret password of admin1pa55.
    R1(config)# username Admin1 password admin1pa55

    Step 3. Configure local AAA authentication for console access on R1.


    Enable AAA on R1 and configure AAA authentication for console login to use the local database.
    R1(config)# aaa new-model
    R1(config)# aaa authentication login default local

    All contents are Copyright © 1992–2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 5
    CCNA Security

    Step 4. Configure the line console to use the defined AAA authentication method.
    Enable AAA on R1 and configure AAA authentication for console login to use the default method list.
    R1(config)# line console 0
    R1(config-line)# login authentication default

    Step 5. Verify the AAA authentication method.


    Verify the user EXEC login using the local database.
    R1(config-line)# end
    %SYS-5-CONFIG_I: Configured from console by console
    R1# exit

    R1 con0 is now available


    Press RETURN to get started.

    ************ AUTHORIZED ACCESS ONLY *************


    UNAUTHORIZED ACCESS TO THIS DEVICE IS PROHIBITED.

    User Access Verification

    Username: Admin1
    Password: admin1pa55
    R1>

    Task 2: Configure Local AAA Authentication for VTY Lines on R1

    Step 1. Configure a named list AAA authentication method for VTY lines on R1.
    Configure a named list called TELNET-LOGIN to authenticate logins using local AAA.
    R1(config)# aaa authentication login TELNET-LOGIN local

    Step 2. Configure the VTY lines to use the defined AAA authentication method.
    Configure the VTY lines to use the named AAA method.
    R1(config)# line vty 0 4
    R1(config-line)# login authentication TELNET-LOGIN
    R1(config-line)# end

    Step 3. Verify the AAA authentication method.


    Verify the Telnet configuration. From the command prompt of PC-A, Telnet to R1.
    PC> telnet 192.168.1.1

    ************ AUTHORIZED ACCESS ONLY *************


    UNAUTHORIZED ACCESS TO THIS DEVICE IS PROHIBITED.

    User Access Verification

    Username: Admin1
    Password: admin1pa55
    R1>

    All contents are Copyright © 1992–2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 5
    CCNA Security

    Task 3: Configure Server-Based AAA Authentication Using TACACS+ on R2

    Step 1. Configure a backup local database entry called Admin.


    For backup purposes, configure a local username of Admin and secret password of adminpa55.
    R2(config)# username Admin password adminpa55

    Step 2. Verify the TACACS+ Server configuration.


    Select the TACACS+ Server. From the Config tab, click on AAA and notice that there is a Network
    configuration entry for R2 and a User Setup entry for Admin2.

    Step 3. Configure the TACACS+ server specifics on R2.


    Configure the AAA TACACS server IP address and secret key on R2.
    R2(config)# tacacs-server host 192.168.2.2
    R2(config)# tacacs-server key tacacspa55

    Step 4. Configure AAA login authentication for console access on R2.


    Enable AAA on R2 and configure all logins to authenticate using the AAA TACACS+ server and if not
    available, then use the local database.
    R2(config)# aaa new-model
    R2(config)# aaa authentication login default group tacacs+ local

    Step 5. Configure the line console to use the defined AAA authentication method.
    Configure AAA authentication for console login to use the default AAA authentication method.
    R2(config)# line console 0
    R2(config-line)# login authentication default

    Step 6. Verify the AAA authentication method.


    Verify the user EXEC login using the AAA TACACS+ server.
    R2(config-line)# end
    %SYS-5-CONFIG_I: Configured from console by console
    R2# exit

    R2 con0 is now available


    Press RETURN to get started.

    ************ AUTHORIZED ACCESS ONLY *************


    UNAUTHORIZED ACCESS TO THIS DEVICE IS PROHIBITED.

    User Access Verification

    Username: Admin2
    Password: admin2pa55
    R2>

    All contents are Copyright © 1992–2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 5
    CCNA Security

    Task 4: Configure Server-Based AAA Authentication Using RADIUS on R3

    Step 1. Configure a backup local database entry called Admin.


    For backup purposes, configure a local username of Admin and secret password of adminpa55.
    R3(config)# username Admin password adminpa55

    Step 2. Verify the RADIUS Server configuration.


    Select the RADIUS Server. From the Config tab, click on AAA and notice that there is a Network configuration
    entry for R3 and a User Setup entry for Admin3.

    Step 3. Configure the RADIUS server specifics on R3.


    Configure the AAA RADIUS server IP address and secret key on R3.
    R3(config)# radius-server host 192.168.3.2
    R3(config)# radius-server key radiuspa55

    Step 4. Configure AAA login authentication for console access on R3.


    Enable AAA on R3 and configure all logins to authenticate using the AAA RADIUS server and if not available,
    then use the local database.
    R3(config)# aaa new-model
    R3(config)# aaa authentication login default group radius local

    Step 5. Configure the line console to use the defined AAA authentication method.
    Configure AAA authentication for console login to use the default AAA authentication method.
    R3(config)# line console 0
    R3(config-line)# login authentication default

    Step 6. Verify the AAA authentication method.


    Verify the user EXEC login using the AAA TACACS+ server.
    R3(config-line)# end
    %SYS-5-CONFIG_I: Configured from console by console
    R3# exit

    R3 con0 is now available


    Press RETURN to get started.

    ************ AUTHORIZED ACCESS ONLY *************


    UNAUTHORIZED ACCESS TO THIS DEVICE IS PROHIBITED.

    User Access Verification

    Username: Admin3
    Password: admin3pa55
    R3>

    Step 7. Check results.


    Your completion percentage should be 100%. Click Check Results to see feedback and verification of which
    required components have been completed.

    All contents are Copyright © 1992–2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 5

    You might also like