Update: what follows applies to IOS as well, but apparently I had never tried making the mistake described below until now. Yay me?!
Okay regular readers, don’t freak out, but this post has absolutely nothing to do with voice. Not even a little. But I suggest you go with it because change happens and we love it. (No, we really don’t love it, that’s just more of my charming sarcasm you’ve grown to know and *actually* love…)
So, changing a password on a Nexus 7K, sounds simple enough, right? Not something I’ve had to do before (remember, voice engineer last three years), but not something I expected to give me any push back doing. Yes, well, it seems I was wrong about that.
See, I logged into the shiny N7K and typed:
MYSHINY7K(config)#show run | in sec username
and got back something like:
username AMYENGINEER password 5 MYAWESOMEPASSWORDHASHVALUE role network-admin
Prompting me to type in something like:
MYSHINY7K(config)#username AMYENGINEER password 5 HEREISMYNEWAWESOMEPASSWORD role network-admin
And press Enter. And then I got totally sassed by the switch with a message that looked like this:
%String failed to match token pattern at ‘^’ marker.
Huh? Well, fast forward after a few minutes after firing up Google, and I land on this helpful gem from the Cisco Support Forums. It was just enough information to clue me into the fact that the switch didn’t much care for the 5 after the password in my command string. Oh well, pardon me, let me just try that again Mr. Switch.
MYSHINY7K(config)#username AMYENGINEER password HEREISMYAWESOMEPASSWORD role network-admin
And sure enough, without the 5 in the command string, my syntax was perfectly acceptable. Note that the 5 does show up in the running-config after.
Now for those of you Nexus gurus who already know this and have known it for ages, please feel free to pat yourselves on the back, as for this Nexus newbie, I’ll be over in the corner wondering what hazing fun the switch has planned for me next.