Timeline for Adding encrypted password on Cisco 3560-CG switch
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 1, 2019 at 12:00 | comment | added | palvarez | I got the same issue in 15.2(2)E5 and it was because of the salt length. | |
| Mar 15, 2017 at 18:25 | vote | accept | ams264s | ||
| Mar 15, 2017 at 18:25 | comment | added | ams264s | Yeah I'm guessing a bug. I've checked and double checked trailing spaces, plus the command originally failed from a script which would have failed for all the devices were it trying to push out a malformed hash. Oddly enough, after doing the config replace, the MD5's are working from the CLI again. I'll go ahead and mark your answer as correct since the problem seems to be resolved for now. Thanks for your help. | |
| Mar 15, 2017 at 17:33 | comment | added | TDurden | Glad the workaround works. Best guess is that there could have been trailing spaces or you might be running into a bug. bst.cloudapps.cisco.com/bugsearch/bug/CSCsy24510 has something similar but there is not much information. | |
| Mar 15, 2017 at 16:20 | comment | added | ams264s | TDurden, thanks for the info. What we're using is definitely an MD5 hash. It is structured as you've showed above, and it also works as type 5 on other devices. I was able to force it by copying the config to ftp, adding the enable secret and username/pw manually, and then doing a config replace. Everything works as expected after that, so the issue is sort of "fixed" but the question of why the process doesn't work from the CLI remains. | |
| Mar 15, 2017 at 15:00 | history | answered | TDurden | CC BY-SA 3.0 |