Authentication failed while using Write command

[ankitspatel]

Hello

I have authentication failed error when I try to use write command. it saves the config but still gives this error.

Building configuration...
Compressed configuration from 19375 bytes to 9814 bytes[OK]
Writing CACPC3OXPLRS001-Jul-18-2022-15-11-48.540-1
% Authentication failed.

[Mark Elsen]

 - Could you verify the startup configuration after this and verify if a (real) saving of the running-config was done or not. Also check the logs after that failure , see if you can find more info's from the logs.

 M.

[ankitspatel]

yes, running config is being saved in real. no information in logs.

RS001#show clock
15:56:01.871 UTC Mon Jul 18 2022
RS001#write
Building configuration...
Compressed configuration from 19327 bytes to 9777 bytes[OK]
Writing RS001-Jul-18-2022-15-56-06.282-1
% Authentication failed.

RS001#show startup-config
Using 9777 out of 2097152 bytes, uncompressed size = 19327 bytes
!
! Last configuration change at 15:55:57 UTC Mon Jul 18 2022 by C556
! NVRAM config last updated at 15:56:05 UTC Mon Jul 18 2022 by C556

RS001#dir | i nvram
417794 -rw- 2097152 Jul 18 2022 15:56:11 +00:00 nvram_config
417795 -rw- 2097152 Jul 18 2022 15:56:11 +00:00 nvram_config_bkup

[Mark Elsen]

 - How is the current-administrative user authenticated , if this is not a local admin , does it have sufficient privileges  (like for instance getting admins authenticated through radius) , though it seems the command can be executed indeed , the lack of could then be  minor side effect.

 M.

[Jitendra Kumar]

Looks like you don't have full permission to do that...

If you are using AAA? if yes check the permissions on your user ID.

[salamshina]

This issue is most likely due to bad archive path. When you do show archive and see what the output is, this could be due to bad credentials.

In this case, just do no archive, then wr mem. This should fix the problem. Don't forget to reconfigure the archive path again.

Thanks,

Abdul.