Cisco N5K-C5010P-BF Troubleshooting Guide - Page 134

No command accounting logs on ACS server when TACACS+ accounting enabled

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 134 highlights

Chapter 6 Troubleshooting Security Issues AAA Send document comments to [email protected]. Perform the following steps for role assignment: • Check which AAA group is being used for authentication with the show running-config aaa and show aaa authentication commands. • For TACACS+, check the VRF association with the AAA group with the show tacacs-server groups and show running-config tacacs+ commands. • For RADIUS, check the VRF association with the AAA group with the show radius-server groups and show running-config radius commands. • If the above commands show that the association is correct, then use the debug tacacs+ all command to enable the trace. • Log in the user again, and collect the debug trace. The trace should contain information for further investigation (as shown in the example). Example: tacacs: process_aaa_tplus_request: Group t1 found. corresponding vrf is management • Use the no debug tacacs+ all command to turn off debug tracing on TACACS+. No command accounting logs on ACS server when TACACS+ accounting enabled When TACACS+ accounting is enabled, the command accounting logs on the ACS server are not found. Possible Cause The ACS server configuration is wrong or incomplete. Solution Perform the following steps: • In the ACS GUI in Network Configuration, go to the AAA Client Setup for any client. Check the checkbox for Log Update/Watchdog Packets from this AAA Client. Click the Submit + Apply button. • Verify CMD Accounting with the following menu path: Reports and Activity > TACACS+ Administration Open the Tacacs+Administration .csv file and verify the cmd and timestamp on each row of the file. PAP authentication does not work for RADIUS PAP authentication works for TACACS+ but not for RADIUS. Possible Cause Starting with Release 4.2(1), NX-OS only supports ASCII (PAP) authentication for TACACS+. Solution In NX-OS, ASCII authentication is equivalent to PAP authentication. By default, both TACACS+ and RADIUS use CHAP. You can switch to PAP authentication with the aaa authentication login ascii-authentication command. Cisco Nexus 5000 Series Troubleshooting Guide 6-6 OL-25300-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
6-6
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 6
Troubleshooting Security Issues
AAA
Perform the following steps for role assignment:
•
Check which AAA group is being used for authentication with the
show running-config aaa
and
show aaa authentication
commands.
•
For TACACS+, check the VRF association with the AAA group with the
show tacacs-server
groups
and
show running-config tacacs+
commands.
•
For RADIUS, check the VRF association with the AAA group with the
show radius-server groups
and
show running-config radius
commands.
•
If the above commands show that the association is correct, then use the
debug tacacs+ all
command to enable the trace.
•
Log in the user again, and collect the debug trace.
The trace should contain information for further investigation (as shown in the example).
Example:
tacacs: process_aaa_tplus_request: Group t1 found. corresponding vrf is management
•
Use the
no debug tacacs+ all
command to turn off debug tracing on TACACS+.
No command accounting logs on ACS server when TACACS+ accounting
enabled
When TACACS+ accounting is enabled, the command accounting logs on the ACS server are not found.
Possible Cause
The ACS server configuration is wrong or incomplete.
Solution
Perform the following steps:
•
In the ACS GUI in Network Configuration, go to the AAA Client Setup for any client. Check the
checkbox for
Log Update/Watchdog Packets from this AAA Client
. Click the
Submit + Apply
button.
•
Verify CMD Accounting with the following menu path:
Reports and Activity > TACACS+ Administration
Open the Tacacs+Administration <active|DATE>.csv file and verify the cmd and timestamp on each
row of the file.
PAP authentication does not work for RADIUS
PAP authentication works for TACACS+ but not for RADIUS.
Possible Cause
Starting with Release 4.2(1), NX-OS only supports ASCII (PAP) authentication for TACACS+.
Solution
In NX-OS, ASCII authentication is equivalent to PAP authentication. By default, both TACACS+ and
RADIUS use CHAP. You can switch to PAP authentication with the
aaa authentication login
ascii-authentication
command.