search

alanrenouf / vCheck-vSphere

vCheck Daily Report for vSphere
MIT License
735 stars 326 forks source link

Can Connect to my vcenter #267

Closed JB1154 closed 10 years ago

JB1154 commented 10 years ago

I ran through the setup once then ran my 1st VCheck reports. I decided to change some parms by restarting with the -config. Now when I run vCheck I'm now getting network connectivity error occurred. Please verify that the network address and port are correct. Our vcenter is using a different port and maybe that is the issue but it ran the first time when I only entered the server name. How do I enter a port number? $Server = "vcenter"

Thank you, JB

monahancj commented 10 years ago

The first time may have worked if you were already connected in the shell session. IIRC, the connect-viserver will fail if you're already connected.

There is a "-port" option, and (not being snarky) "help connect-viserver" has all the info you need. Same info in a web doc- https://www.vmware.com/support/developer/PowerCLI/PowerCLI501/html/Connect-VIServer.html .

JB1154 commented 10 years ago

Thanks Chris, Somehow I was under the impression your script was handling or passing the values to the Vconnect command differently as this is how I have it set up to connect when I start the shell

Thanks!!!

John P Iabone Jr

AKA John Boy

Sneddo commented 10 years ago

Hey, I just edited out your email signature from you reply :)

Not a bad idea to support non-standard ports, would be reasonably easy to implement too- i.e. allow servername:port notation in GlobalVariables, and do a split on connecting to vCenter. Will have a look at this next week unless someone else want to have a go.

JB1154 commented 10 years ago

Thanks I saw my Signature and said “Oh well” but thank you!!

Yea that would be good as I tried different iteration and would receive errors that it could not parse the value and other errors. I ended up ending my powershell session and restarting and it worked just by having the server name.

We plan on doing away with the port # when we go to version 5.5 Thank you, JB

From: Sneddo [mailto:notifications@github.com] Sent: Wednesday, October 15, 2014 10:12 PM To: alanrenouf/vCheck-vSphere Cc: Iabone, John Subject: Re: [vCheck-vSphere] Can Connect to my vcenter (#267)

Hey, I just edited out your email signature from you reply :)

Not a bad idea to support non-standard ports, would be reasonably easy to implement too- i.e. allow servername:port notation in GlobalVariables, and do a split on connecting to vCenter. Will have a look at this next week unless someone else want to have a go.

— Reply to this email directly or view it on GitHubhttps://github.com/alanrenouf/vCheck-vSphere/issues/267#issuecomment-59311908.

alanrenouf commented 10 years ago

Sounds like a reasonable addition, Iy use the port if it's specified though so it still works on default port if not specified.

Sneddo commented 10 years ago

Just added a commit for this. The connection plugin now uses a port if specified, otherwise just uses the default (443).

Just specify your vCenter in servername:port format

JB1154 commented 10 years ago

Thanks everyone!!! JB From: Sneddo [mailto:notifications@github.com] Sent: Thursday, October 16, 2014 9:13 PM To: alanrenouf/vCheck-vSphere Cc: Iabone, John Subject: Re: [vCheck-vSphere] Can Connect to my vcenter (#267)

Just added a commit for this. The connection plugin now uses a port if specified, otherwise just uses the default (443).

Just specify your vCenter in servername:port format

— Reply to this email directly or view it on GitHubhttps://github.com/alanrenouf/vCheck-vSphere/issues/267#issuecomment-59461185.