BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot login in VC with personal account after VC firmware update

 
Tom Wolf_3
Valued Contributor

Cannot login in VC with personal account after VC firmware update

Hello all.

We have a BladeSystem c7000 Enclosure G2 where the virtual connect firmware was just updated to 4.75

Prior to the firmware update, I was able to log into the virtual connect with my personal account.

After the update, I keep getting the following error when I try to log into the VC with that account:

Invalid User Name, Password, Role, unknown/improperly
configured Authentication Service, or combination of these.
NOTE: User Name and Password are case sensitive.


I can still log into this VC with the Administrator account.

But I'd rather not use it.

When I look at the VC System log I see these failures for my personal account but no other explanation.

2019-08-11T16:37:22-05:00 VCEX3C411300C3 vcmd: [VCD:GLE-537-24:1012:Warning] VCM user authentication failure

How would I resolve this?

As always, any assistance would be appreciated.

Thank you.

Tom Wolf

2 REPLIES 2
MV3
HPE Pro

Re: Cannot login in VC with personal account after VC firmware update

HI Tom,

Good Day!

A firmware upgrade should not wipe of any user account if added in managing Users tab.

Were you using any LDAP user account in your VCM?

I would advise you to follow the correct procedure to creating a local account in VCM.

Please find the below HPE Virtual Connect for c-Class BladeSystem User Guide.

https://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-a00055965en_us-1.pdf

Refer page 65- 69 (Virtual Connect users and roles)

Accept or Kudo
Tom Wolf_3
Valued Contributor

Re: Cannot login in VC with personal account after VC firmware update

Hello MV3.

Thanks for the info.

Yes, we are using LDAP authentication on all our VCM's.

My personal account works fine on all the other VCM's, just this one that was updated to 4.75 is having issues.

Other VCM's will be update from 4.63 to 4.75 in the weeks to come.

I suspect I'll encounter the same issue on them after the update.

Not sure why LDAP is rejecting my login post firmware update.

I'm trying to get a resource in our organization familiar with LDAP to let me know how this would be addressed but not having much luck.

As noted, I can still login with the Administrator account but I don't like using that.

Is a new LDAP cert needed to fix this?

Thanks again for replying.