Skip to content

TACACS Monitoring Destination

Location in GUI: Admin » External Data Collectors » Monitoring Destinations » TACACS

Diagram
NameTypeConstraintMandatoryDefault Value
tacacsList[tacacs]No

NameTypeConstraintMandatoryDefault Value
nameStringRegex: ^[a-zA-Z0-9_.:-]{1,64}$Yes
descriptionStringRegex: ^[a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]{1,128}$No
destinationsList[destinations]No

destinations (apic.fabric_policies.monitoring.tacacs)

Section titled “destinations (apic.fabric_policies.monitoring.tacacs)”
NameTypeConstraintMandatoryDefault Value
hostname_ipAnyString[Regex: ^[a-zA-Z0-9:][a-zA-Z0-9.:-]{1,254}$] or IPYes
portIntegermin: 1, max: 65535No49
protocolChoicepap, chap, mschapNopap
keyStringNo
mgmt_epgChoiceinb, oobNooob

Example-1: This data model creates a TACACS monitoring destination group named tacacs_simple with a single TACACS+ accounting destination at 10.0.0.50 over port 49 using pap authentication. The destination is reached over the oob management EPG. The shared secret key is sensitive and should be supplied via a variable or vault.

apic:
fabric_policies:
monitoring:
tacacs:
- name: tacacs_simple
description: Simple TACACS Accounting Example
destinations:
- hostname_ip: 10.0.0.50
port: 49
protocol: pap
key: "{{ tacacs_key }}"
mgmt_epg: oob

Example-2: This data model creates a TACACS monitoring destination group tacacs_advanced with two destinations (one primary using chap over inb, one secondary using mschap over oob), and wires it into the common monitoring policy as a TACACS source with Switch TACACS Audit enabled.

apic:
fabric_policies:
monitoring:
tacacs:
- name: tacacs_advanced
description: Advanced TACACS Accounting Example
destinations:
- hostname_ip: tac1.example.com
port: 49
protocol: chap
key: "{{ tacacs_key_primary }}"
mgmt_epg: inb
- hostname_ip: tac2.example.com
port: 49
protocol: mschap
key: "{{ tacacs_key_secondary }}"
mgmt_epg: oob
policies:
- name: common
tacacs:
- name: tacacs_src
audit: true
destination_group: tacacs_advanced