Powershell Connect-Ucs Fails

[Lloyd Goddard]

Hi, 

I'm having issues connecting to a UCS cluster via powershell. To test basic access using Cisco UCS PowerTool 1.2.1.0 I enter "Connect-UCS 10.x.x.x" where I am prompted for my username password which authenticates against LDAP. This fails to connect although I can launch Cisco UCS manager 2.1(1f) and login in ok with these credentials. 

Can anyone assist in any troubleshooting steps as I've run out of ideas. Thanks. 

PowerTool C:\> Connect-Ucs https://10.x.x.x -xml

cmdlet Connect-Ucs at command pipeline position 1
Supply values for the following parameters:
Credential
==>https://10.x.x.x:<aaaLogin inName="xxxxxxxx" inPassword="****" />
Connect-Ucs : Connect-Ucs: Connection to https://10.x.x.x Failed.
At line:1 char:12
+ Connect-Ucs <<<<  https://10.x.x.x -xml
    + CategoryInfo          : NotSpecified: (:) [Connect-Ucs], Exception
    + FullyQualifiedErrorId : Cisco.Ucs.Cmdlets.ConnectUcs

PowerTool C:\>

[Walter Dey]

I would try

“connect-ucs x.x.x.x” where x.x.x.x equals the VIP IP address of UCS domain

[Lloyd Goddard]

Thanks for the reply. I have attempted to connect to the UCS VIP address along with the individual IP's of the fabric interconnects with no joy I am afraid. 

[Walter Dey]

Any firewall in the path ? or the host, from where you initiate the session ?

[gmonroy]

Would it be possible for you to get a packet capture on the ldap server of both working and non working instances using the same credentials? That will help us get an idea if perhaps the powertool itself is sending out the authentication details incorrectly, whereas the UCS domain is not.

Also you mention that it fails specifically for ldap, are you able to login with powertool if you used local credentials, perhaps the local admin?

Regards,

-Gabriel