HPE Nimble Storage Solution Specialists

NWT - Group Registration - Group Credentials Error

 
UngyCMH
Occasional Visitor

NWT - Group Registration - Group Credentials Error

I'm attempting to upgrade NWT v5 to v7 on a Windows Client, via NWT upgrade GUI and in this new version the toolkit requires registering with Nimble Storage in order to create VSS-based application snapshots.  I created a new local user account with admin rights. Under Nimble Group Registration, I enter the correct Group IP and new username/password and hit register.  The error I receive is "Specified user credentials cannot be verified. Please check the group management IP or the credentials provided as input. "   The NWT upgrade admin guide states:  "In NWT 7.0.0 and later, provide the username/password credentials that are used by the HPE Nimble
Storage array. You must register at least one group. The array user should have Power User or above
credentials."   

I must be missing something, it mentions registering at least "one group."  Does that mean Active Directory group or user account under Nimble Storage Group?   

 

 

 

5 REPLIES 5
MaruthiKumar
New Member

Re: NWT - Group Registration - Group Credentials Error

Nimble Array should be registered using the local credentials of the Array or an AD User of the Array. (i.e credentials that you use to login to the Array)
You should not use the Windows/Host User credentials.
Please try and let us know if it solves your issue.

UngyCMH
Occasional Visitor

Re: NWT - Group Registration - Group Credentials Error

Sorry for the late reply.  I used a local account setup on the Nimble.  Received the error message again. In addition, I tried my admin account that I use to logon to this same Nimble as well and got the same error message.  "Specified user credentials cannot be verified. Please check the group management IP or the credentials provided as input."  I verifed the password was correct for the local service account by retyping it in the Nimble and it would not allow me to update it as that password was already in use.  

I tried this with the Windows firewall disabled and same issue.  This Windows Server is located on another subnet from the Nimble.  Are there any network firewall ports that need to be opened for the connection to work and authenticate the username and password on this toolkit upgrade to version 7?  

Thank you all for your help!

Michael

Doesitmatter
New Member

Re: NWT - Group Registration - Group Credentials Error

Same issue - any fix ever get figured out?

_Nathan
Occasional Visitor

Re: NWT - Group Registration - Group Credentials Error

I had this issue as well. I opened a case with Nimble and the issue was resolved by removing the caret, ^, from the password.

HBTRon
Occasional Visitor

Re: NWT - Group Registration - Group Credentials Error

We experienced this same issue as well on a small subset of our servers and worked with HPE Nimble Support.  The troubleshooting was long, but in the end, it turned out to be an easy fix.
Using the Nimble PowerShell cmdlet:
Set-NWTConfiguration -GroupMgmtIP x.x.x.x -CredentialObj (Get-Credential)
will give you the "C:\ProgramData\Nimble Storage\Logs\NimblePowerShell.log" file that you can use for troubleshooting.  In our case, we received this log message when the cmdlet failed with the same error that UngyCMH received:
"05-05-2021 09:56:34.938 7548 19152 Warning Login failed with exception Resource:https://10.X.X.X:5392/v1/tokens, Error:The request was aborted: Could not create SSL/TLS secure channel.. Re-attempting login."  (10.X.X.X was our Group IP).
You can see that it's trying to communicate on port 5392.  This was not our problem however as it still happened after specifically creating a new Firewall rule to open port 5392. 

We looked at the later part of that message referring to the SSL/TLS failure.  The Nimble Supprt tech enlisted the help of their software devs to find out that the Group Registration specifically uses the TLS Cipher "TLS_RSA_WITH_AES_256_CBC_SHA256".  Using the cmdlet "Get-TlsCipherSuite | Format-Table -Property Name" it turned out that our servers did not have that particular Cipher enabled.  This was then easily fixed using "Enable-TlsCipherSuite -Name TLS_RSA_WITH_AES_256_CBC_SHA256"