Skip to content

Instantly share code, notes, and snippets.

@changtimwu
Last active June 18, 2016 04:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save changtimwu/316acbca5c9c8ce0e3f10b01dd7a4ede to your computer and use it in GitHub Desktop.
Save changtimwu/316acbca5c9c8ce0e3f10b01dd7a4ede to your computer and use it in GitHub Desktop.
Setup TACACS+ between LANTECH switch and Cisco ACS

References

All are from Cisco official documents:

Basics

  • The security model of Lantech switches is rather simple. Each user falls into either one of the following of permissions.
    • read-only: allow to view current settings but changing settings is disallowed.
    • read-write: both viewing/changing settings are allowed.
  • How permission mapped into TACACS+ privilege level?
    • privilege level 1~8 --> read-only permission
    • privilege level 9~15 --> read-write permission

Cisco ACS configuration

  • Image we're going split users into two groups with different permissions like the following table
group name permission privelege level members
admin-group read-write 15 alex, amy
user-group read-only 1 ufo, upup
@changtimwu
Copy link
Author

Create groups: admin-group and user-group
2016-06-18 11 23 42

@changtimwu
Copy link
Author

Create users under correspondent groups
user_under_groups

@changtimwu
Copy link
Author

changtimwu commented Jun 18, 2016

Create Shell Profiles:
create_profiles

  • roaccess: privilege level = 1

ro_name
ro_priv

  • rwaccess: privilege level =15
    rw_name
    rw_priv

@changtimwu
Copy link
Author

In Access-Services -> Service Selection Rules, create a rule to route all tacas+ access into Default Device Admin service
service_selection_rules
tacacs_to_devadmin

@changtimwu
Copy link
Author

In Access Policies > ... > Access Services > Default Device Admin > Authorization
Create rules to map groups into correspondent shell profiles
devadmin_author_policy
admingrp-rwaccess
usergrp-roaccess

@changtimwu
Copy link
Author

changtimwu commented Jun 18, 2016

When things not work. Let's diagnosis

  • Check how many times the rule has been hit
    hit_counts
    hit_counts_refresh
  • Open monitoring and resports and check the TACACS+ AAA reports
    monitor_report
    favorites
  • Click the Refresh button and check the detail by clicking details
    tacacs_auth_log
  • In side the report, the sections Access Policy and Evaluating Identity Policy provide valuable clues on why ACS allows/denys a login.
    report_anaylysis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment