Posts: 76
Threads: 69
Joined: Jan 2023
Reputation:
0
exhibit show that R1 is attempting to connect to 10.221.10.10 and reveals a connect error
fixing the diagram will show that a static route out e 0/1 will fix the problem
Posts: 95
Threads: 0
Joined: Jan 2023
Reputation:
0
The question has been corrected. Thank you!
Posts: 1
Threads: 0
Joined: May 2019
Reputation:
0
Looking at the debug output, second to the last line, the log suggests that it is attempting to use server x.x.10.10 when the diagram specifies that the server is actually x.x.10.11.
This would require the tacacs group to be modified to use the correct server:
`tacacs server prod`
`address ipv4 x.x.10.1
Last option is the correct one.
Posts: 398
Threads: 11
Joined: Jan 2001
Reputation:
22
Thank you for your feedback. The correct answer indeed is:
tacacs server prod
address ipv4 10.221.10.11
exit
The answer and explanation have been updated.