To stop accounting “stop” records for users who fail to authenticate at login or during session negotiation, use the aaa accounting send-stop-record authentication failure command in global configuration mode. To stop generating records for users who fail to authenticate at login or during session negotiation, use the no form of this command.
The following example generates “stop” record for users who fail to authenticate at login or during session negotiation:
aaa accounting send stop-record authentication failure
aaa accounting send stop-record authentication failure
To stop accounting “stop” records for users who fail to authenticate at login or during session negotiation, use the aaa accounting send-stop-record authentication failure command in global configuration mode. To stop generating records for users who fail to authenticate at login or during session negotiation, use the no form of this command.
The following example generates “stop” record for users who fail to authenticate at login or during session negotiation:
aaa accounting send stop-record authentication failure
0
0
http://www.cisco.com/c/en/us/td/docs/ios/12_2/security/command/reference/fsecur_r/srfacct.html
0
0
Correct answers are B and C.
http://www.aiotestking.com/cisco/which-two-accounting-notices-are-used-to-send-a-failed-authentication-attempt-record-to-a-aaa-server/
0
0
The general syntax for accounting is:
Router(config)# aaa accounting {system | network | exec | connection | commands level} {default | list-name} {start-stop | stop-only | none} [method1 [method2…]]
We can account for start and stop or stop only.
http://www.cisco.com/c/en/us/td/docs/ios/12_2/security/configuration/guide/fsecur_c/scfacct.html
0
0
The correct answers are A and C.
4
0