connect problems

May 26, 2011 at 9:43 AM

hi!

first of all: Thanks for all the IPs :-)

I just tried to get die VMWare IP up and running and have a problem with connecting to my vSphere Server. I installed the vSphere Client and the vSphere PowerCLI. Also did the configuration for the IP in Opalis. When I try to create a simple policy (Custom-Start and Get-Vm or Get-Cluster, Opalis responds:

5/26/2011 11:29:49 AM Get-Cluster  You are not currently connected to any servers. Please connect first using Connect-VIServer or one of its aliases. 

Exception: CmdletInvocationException
Target site: <getCluster>d__0.MoveNext

Stack trace:
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
   at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)

Szenario is: my vSphere Server is scott.prod-td.local, my account for accessing the vSphere-Server is acc@int-td.local (separate AD Domains, fully trusted). Login with the vSphere Client works (using "int-td\acc" for login). To make it a little bit more complicated the Opalis Action/Management Server is in a third Domain (not trusted to any other domain). In a network trace I see a TLS-Session building up between Opalis and vSphere Server, but since it is encrypted...

My configuration settings for VMware IP is as follows:

username: acc
Port: 443
Password: *****
Domain: int-td.local (the domain where the account sits!)
VirtualCenter: scott.prod-td.local

Please help! :-)

Yours, ralf

Coordinator
May 27, 2011 at 7:50 PM
Edited May 27, 2011 at 7:52 PM

Hey Ralf,

The command that is run to connect to your vSphere server is

"Connect-VIServer -Server " + virtualCenter + " -Port " + port + " -User " + domain + "\\" + userName + " -Password " + password + "\n";

can you try running that for me from powershell (on your action server) after loading the vmware vsphere cmdlets (into the powershell session) and see if it successfully connects?  Given your configuration above the line to put into powershell would be

Get-PSSnapin -Registered | Add-PSSnapin

Connect-VIServer -Server scott.prod-td.local -Port 443 -User acc\int-td.local -Password *****

Try it and let me know what you get as a result!

Thanks,

Ryan

May 31, 2011 at 2:08 PM
hi!

thanks for your help. I figured out that it was a problem with the
certificate and that might have slipped through the error handling
within the OIP during the Connect-VIServer. Changed the certificate
and now everything is ok. But I figured out that a Get-VM inside
Opalis brings back a lot more information than a Get-VM inside the
PowerCLI. Why is this and is there a chance to get even more
information like the "dnsname" etc. that is shown in the vSphere
Properties of the VM?

Thanks a lot.

Yours, ralf

2011/5/27 randorfer <notifications@codeplex.com>:
> From: randorfer
>
> Hey Ralf,
>
> The command that is run to connect to your vSphere server is
>
> "Connect-VIServer -Server " + virtualCenter + " -Port " + port + " -User " +
> domain + "\\" + userName + " -Password " + password + "\n";
>
> can you try running that for me from powershell after loading the vmware
> vsphere cmdlets and see if it successfully connects?  Given your
> configuration above the line to put into powershell would be
>
> Connect-VIServer -Server scott.prod-td.local -Port 443 -User
> acc\int-td.local -Password *****
>
> Try it and let me know what you get as a result!
>
> Thanks,
>
> Ryan
>
> Read the full discussion online.
>
> To add a post to this discussion, reply to this email
> ([email removed])
>
> To start a new discussion for this project, email
> [email removed]
>
> You are receiving this email because you subscribed to this discussion on
> CodePlex. You can unsubscribe on CodePlex.com.
>
> Please note: Images and attachments will be removed from emails. Any posts
> to this discussion will also be available online at CodePlex.com