hansis
Contributor
Contributor

Network error

Hello!

I have to virtual centers!

If I connect with "connect-viserver VCENTER1" I don't have any problems.

But If I want to connect to VCENTER2 I get following error:

Connect-VIServer : 23.02.2012 12:06:06    Connect-VIServer        Network conne
ctivity error occured. Please verify that the network address and port are corr
ect.
Bei Zeile:1 Zeichen:17
+ connect-viserver <<<<  172.18.65.200
+ CategoryInfo          : ObjectNotFound: (:) [Connect-VIServer], ViServer
ConnectionException
+ FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_BadNe
tworkConnection,VMware.VimAutomation.ViCore.Cmdlets.Commands.ConnectVIServ
er

What is the problem?

thx

hansi

0 Kudos
11 Replies
RvdNieuwendijk
Leadership
Leadership

Hi Hansi,

can you connect to VCENTER2 using the vSphere client?

Regards, Robert

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
0 Kudos
hansis
Contributor
Contributor

Yes I can.

Now I get an error if I want to open the vCenter-Server-Properties:

Aufruf von "PropertyCollector.RetrieveContents" für Objekt "propertyCollector" auf vCenter Server "ATVCENTER3.nv.at" ist fehlgeschlagen.

Call of "PropertyCollector.RetrieveContents" für Objekt "propertyCollector" at vCenter Server "ATVCENTER3.nv.at" failed.

0 Kudos
LucD
Leadership
Leadership

You connect with the IP address ? Is there no name resolution in place ?

Can you try to connect to vCenter 2 with the FQDN ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
hansis
Contributor
Contributor

I can't connect with FQDN. Always the same error.

0 Kudos
LucD
Leadership
Leadership

And the hostname of vCenter2 can be resolved from the station where you run the Connect-VIServer ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
hansis
Contributor
Contributor

Yes.

another question. On VCenter-Server I do not have to install anything for PowerCLI, isn'it?

0 Kudos
RvdNieuwendijk
Leadership
Leadership

That is correct. On the vCenter Server you do not have to install anything for PowerCLI.

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
0 Kudos
LucD
Leadership
Leadership

The error message you got typically comes when one or more of the services on the vCenter are not running (or in a funny state).

You said you can connect with the vSphere client, but it seems you get an error mesage when you try to do something in the vSphere client. Correct ?

Have a look if everything is running on vCenter2. And eventually reboot vCenter2.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
hansis
Contributor
Contributor

nothing changed

Maybe I have forgotten some special settings on vCenter-Server?

0 Kudos
hansis
Contributor
Contributor

it seems to be a network problem.

with ping Vcenter2 -t  I periodical get an timeout.

could that be the reason?

0 Kudos
LucD
Leadership
Leadership

That could indeed explain what you are seeing.

It's definitely worth fixing that connectivity problem first.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos