OME RACADM CLI "Invalid Username or Password" errors

Hi Marco, 

Problem with this would be that I'm trying to run this via the OME RACADM CLI function across multiple iDRACs at once - meaning that I can't specify the host IP Address. 

I could potentially try the -u and -p flags, but unless I'm mistaken that would require that I specify the IP.

Hello,

did you try to specify user and passwd? Like

racadm -r $Server.HostIP -u $user -p $passwd set iDRAC.LDAP.BindPassword $bindpass

Thanks

Hello,

you cannot use racadm only with one command at conce for all iDRACs.

You have to select one by one, can you try with the user password flag? And also with host iP?

Thanks

Respectfully, I can and have - in our test environment, I was able to modify the LDAP Bind Password using this method across ~10 iDRACs at once using the OME RACADM CLI process. This was suggested as a method to perform this update by our contacts at Dell. 

To clarify, this is being done via OME > Devices tab > selecting multiple devices > More Actions dropdown > RACADM CLI > enter commands > Finish. 

Again, I know this works as I have a completed job in our Test environment where "set iDRAC.LDAP.BindPassword" was run against 5 and then 10 devices using one Job. 

Zwoodcock,

I can confirm the process your trying is supported. 

As far as the invalid user/pass issue, there are only a couple of things I can think of that may cause that error, so lets see if either fit your situation. So the first would be that there is not an LDAP Account specified to need the password you're setting. The second would be that the password you are trying to use has an unsupported character in it. 

Let me know if you see either are the case. 

Thanks Chris! I believe our Password Management is set to only use supported characters. The only special characters I'm seeing in the generated PW are:

[

]

_

-

(

)

For the other note, what exactly are you referring to? By "there is not an LDAP Account specified to need the password you're setting," are you suggesting that the LDAP Bind Account isn't set for the iDRAC(s) in question? 

If so, I can confirm that the iDRAC LDAP settings are correct . I am able to log in using my Directory account to the two iDRACs I updated manually after the failed batch process. 

If iDRAC LDAP settings are ok, can you try to use a password without special characters? If I'm not work the characters ( and ) are not allowed.

Thanks

Sorry; I've been swamped and just now got back around to checking this - I can try. I've resorted to manually updating the bind password on the iDRACs, but I'll leave the last couple of devices and try to use a test Password. 

I can confirm that characters don't appear to make a difference - I attempted with a fake password of "password," and received the same errors. 

I would also like to expand on the error - the exact error message I'm getting is:

ERROR: Login failed - invalid username or password
Exited with error

ERROR: ERROR: 12

Hello @zwoodcock,

Have you considered a network configuration that might being preventing this command issues all over your production environment?

I mean, if you already tried this in test environment and the exact same command is not working on production. Maybe it's because there is something different in the Network configuration.

Regards.