I've changed the IP address of the vCenter (& external PSC) machines. vCenter is fine, but all the hosts keep disconnecing from vCentre. I updated the vCenter servers IP address in the VPXA.CFG (as per article 1001493), but the address keeps on getting reverted back to the old address. I've checked the vCenter's IP address (As per article 1008030) and even restarted vCenter, but still the same: The vCenter server's IP address gets reverted.

What else can I do to try to fix this?

Thank you.

What is the max supported latency between vCenter and remote hosts? We have hosts that are randomly disconnecting at sites with greater than 200ms of latency.

Hello All,

On a newly installed vCenter server 6.7, I installed yum with the command tdnf install yum (as detailedin the PhotonOS documentation). Eveyrhting ran fine, the following packages being installed :

yum-metadata-parser                                          x86_64                 1.1.4-2.ph1                                   57.10 k

yum                                                          noarch                 3.4.3-7.ph1                                    4.18 M

urlgrabber                                                   noarch                 3.10.1-3.ph1                                 504.62 k

python2-libs                                                 x86_64                 2.7.15-8.ph1                                  15.50 M

python2                                                      x86_64                 2.7.15-8.ph1                                   1.87 M

python-xml                                                   x86_64                 2.7.15-8.ph1                                 329.53 k

python-rpm                                                   x86_64                 4.13.0.2-1.ph1                               197.62 k

pycurl                                                       x86_64                 7.21.5-4.ph1                                 143.50 k

After that, I could not log back to the vCenter server :

Traceback (most recent call last):

  File "/usr/lib/applmgmt/base/bin/vherdrunner", line 6, in <module>

    import vherdrunner

  File "/usr/lib/applmgmt/base/bin/vherdrunner.py", line 9, in <module>

    from defusedxml import xmlrpc

ImportError: No module named defusedxml

I then decided to remove Yum and all the above packages. This ran fine. But, now, I don't even have a python interpreter left :

Last login: Wed Jul 10 10:05:25 2019 from 172.31.251.249

/bin/appliancesh: /usr/lib/applmgmt/base/bin/vherdrunner: /usr/bin/python: bad interpreter: No such file or directory

/bin/appliancesh: line 8: /usr/lib/applmgmt/base/bin/vherdrunner: Success

Do you know how I could restore the correct version of sofwares so that everything goes back in order? I'm very surprised that the package system can be so easily broken...

Hi all,

I'd like to know what's the best way to have vCenter in a Horizon 7 environment. Some say you can use VCSA. This means it's a VM. One can do the same with a windows server with vCenter installed also as a VM.

As I started with Vmware 10 years ago one was told to have it as a physical machine beside all the esxi servers. Are there other recommendations nowadays?

This question comes up because we plan an environment with Horizon 7 and about 12 ESXi servers. The network will be splitted in 3 different subnets. VDI should then deliver desktops with different rights to access these subnets.

Any idea would be very appreciated.

Thank you...!

Hey all,

I am having trouble trying to work out the best architecture for 4 sites to be in linked mode...

My client has 4 sites

2 sites in AD domain x

2 sites in AD domain y

Both AD domains are in the same forest and have a 2 way trust

The client wants a vCenter in all sites with linked mode between all of them.

Does this require that all vCenter servers are in the same SSO domain?

Do the sites link in a ring as below or more like a mesh?

We have 3 ESXI 6.5 hosts running a few VM's on them.

Now we wanted to deploy a vcenter to manage our esxi hosts and their machines. We have bought a vcenter licese too.

We are trying to install VMware-VCSA-all-6.7.0 iso on a virtual machine which is setup on one of the virtual machine.

Its not booting up from there. do we need to install something else before we install vcenter ?

When i setup the virtual machine i choose Guest OS family as linux and Guest OS version as Photon.

am i doing this right? or vcenter will be installed on a separate machine ?

Hi,

I have the following problem. Currently, I installed a new Vcenter Server Appliance in version 6.5.0.14000. I can not cope with sending notifications via VCSA that does not work.

My external mail server for sending notifications works fine. Notifications from other devices affect my inbox.

I would also like to emphasize that our mail server (mail.companydomain.com) is open to the IP address and ports of the VCSA server.

Configuration in the VCSA GUI is in the instructions (Vcenter General-> Mail) in the fields are filled in as follows:

• mail server - mail server address (mail.companydomain.com),

• mail sender - (helpdesk@companydomain.com)

When using the VCSA console, the command:

echo "Subject: sendmail test" | sendmail -v my.email@companydomain.com

the mail is forwarded to my mailbox.

This is how my sendmail works in VCSA. Where to look for a problem?  It's need any additional settings?

best wishes,

Hi all,

yesterday I updated my vCenter Appliance via the webinterface to (I guess) vCenter Server Appliance 6.7.0.31100 embedded build 13843380 (got this information out of snmp).

After the last update, I can't really detect which one it is, because I can't login anymore to the Webpage at https://IP_or_dns:5480 as user root with the correct Password.

The unfunny thing is, ssh connection to the IP_or_dns with the given Password works proper and I have Access (and I am root).

What to do, to solve this issue?

Is there anyone out, who can assist me or point me to the issue I haven't seen yet?

thanks

Gerold

Hi VMTN folk,

I have recently merged 2x vCenter Servers with embedded PSCs into the same SSO domain using the 'cmsso-util domain-repoint' utility.  I can now managed both environments from the same pane of glass - mission accomplished!

However,  an issue trying to setup vSphere Replication has lead me to checking the PSC partner status using the

'./vdcrepadmin -f showpartnerstatus -h vc.domain.com -u administrator@vsphere.local'

command.  The partner PSC name is displayed OK, but with a status of "Host Available: No".

Is this to be expected, or are there other tasks to complete, or could this be some other issue?  I've checked another separate environment that was merged with the same utility - same 'Host Available: No status' is displayed.

Thanks in advance

Tony

Hello,

I am trying to convert a Hyper-V VM via the Vmware converter. The VM is shutdown.

Through the conversion wizard i use the local administrator account on the hyper-V node, and it lists all the VM's.

I select the turned off VM and it reports to collect vm information, when i get an error that indicates that it is unable to open the vhd file. The administrator account has full rights to the file of couse.

Agent log:

[Originator@6876 sub=Default] Sysimage::HyperVWMI::ExecuteQuery: Executing : Select * from Msvm_MemorySettingData where instanceID like 'Microsoft:5B74ABF5-30E1-4F65-9A19-B1ED38629BA0%'

2019-06-14T10:18:38.564+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::GetVirtualMemory: Virtual Memory on VM: 4096

2019-06-14T10:18:38.595+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::GetNumVCpus: retrieving number of virtual CPUs.

2019-06-14T10:18:38.595+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::ExecuteQuery: Executing : Select * from Msvm_ProcessorSettingData where instanceID like 'Microsoft:5B74ABF5-30E1-4F65-9A19-B1ED38629BA0%'

2019-06-14T10:18:38.611+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::GetNumVCpus: Num CPUs in VM: 2 * 1 = 2

2019-06-14T10:18:38.642+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::GetVmName: Obtaining VM's name

2019-06-14T10:18:38.642+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::ExecuteQuery: Executing : Select * from MSVM_ComputerSystem where Name = '5B74ABF5-30E1-4F65-9A19-B1ED38629BA0' and Description = 'Microsoft Virtual Machine'

2019-06-14T10:18:38.658+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::ExecuteQuery: Executing : Select * from Msvm_VirtualSystemManagementService

2019-06-14T10:18:38.658+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::ExecuteQuery: Executing : Select * from Msvm_SummaryInformation where Name = '5B74ABF5-30E1-4F65-9A19-B1ED38629BA0' and ElementName != 'SKAXXX'

2019-06-14T10:18:38.658+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::GetGuestOS: Found guest OS for 5B74ABF5-30E1-4F65-9A19-B1ED38629BA0 'Other'

2019-06-14T10:18:38.658+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::GetVmFirmware: Retrieving VM Firmware for:5B74ABF5-30E1-4F65-9A19-B1ED38629BA0

2019-06-14T10:18:38.658+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::ExecuteQuery: Executing : Select * from Msvm_VirtualSystemSettingData where VirtualSystemIdentifier = '5B74ABF5-30E1-4F65-9A19-B1ED38629BA0' and VirtualSystemType = 'Microsoft:Hyper-V:System:Realized'

2019-06-14T10:18:38.705+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimage::HyperVWMI::GetVmFirmware: Retrieved VM InstanceID successfully.

2019-06-14T10:18:38.705+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] [BaseDiskSetComputer::OpenDiskSet] Will use open retries count 3

2019-06-14T10:18:38.736+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'The parameter is incorrect' (error code:5701641)

2019-06-14T10:18:38.736+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Error 5701641 opening disk C:\ClusterStorage\Volume1\XXXXXX\XXXXX_disk_1.vhdx.

2019-06-14T10:18:38.736+02:00 warning vmware-converter-agent[36724] [Originator@6876 sub=Default] ERROR 5701641 opening disk disk-3.

2019-06-14T10:18:38.736+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Attempt to opening disk disk-3 again [rest 2] (sleep for 5 sec).

2019-06-14T10:18:43.783+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'The parameter is incorrect' (error code:5701641)

2019-06-14T10:18:43.783+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Error 5701641 opening disk C:\ClusterStorage\Volume1\XXXXX\XXXX_disk_1.vhdx.

2019-06-14T10:18:43.783+02:00 warning vmware-converter-agent[36724] [Originator@6876 sub=Default] ERROR 5701641 opening disk disk-3.

2019-06-14T10:18:43.783+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Attempt to opening disk disk-3 again [rest 1] (sleep for 10 sec).

2019-06-14T10:18:54.252+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'The parameter is incorrect' (error code:5701641)

2019-06-14T10:18:54.252+02:00 info vmware-converter-agent[36724] [Originator@6876 sub=Default] Error 5701641 opening disk C:\ClusterStorage\Volume1\XXXX\XXXXX_disk_1.vhdx.

2019-06-14T10:18:54.252+02:00 warning vmware-converter-agent[36724] [Originator@6876 sub=Default] ERROR 5701641 opening disk disk-3.

2019-06-14T10:18:54.252+02:00 error vmware-converter-agent[36724] [Originator@6876 sub=Default] [BaseDiskSetComputer::OpenDiskSet] OpenDisks failed, mntapi error: 91226257

2019-06-14T10:18:54.252+02:00 error vmware-converter-agent[36724] [Originator@6876 sub=Default] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 91226257 MNTAPI errorType = 1, errorCode = 5701641

2019-06-14T10:18:54.252+02:00 error vmware-converter-agent[36724] [Originator@6876 sub=Default] AnalyzeErrorAndThrow(): DiskLib error 87

Thanks

Hi,

I just searched for my specific topic and would need some help with my new vsphere and vcenter software.

So far, when I wanted to "backup" or basically clone my VM from host "1" to host "2" ( I have to hosts in my office, in order one host fails or breaks down )

I jumped into that host, into the running VM (windows server 2012 OS) and used the "Vmware Converter Standalone" in Windows. I just moved the running OS as a VM to my other esxi host.

However, with Vcenter, I imagine that there are way better methods to perform that, right?

Clone, migrate whatsoever from one host to another.

The Converter on Windows took about 15 hours to convert the physical machine into a VM on the other host. (and it was a FREE esxi so far.)

Now I purchased the real deal and heard that the licensed Version uses some acceleration features??

The details are in particular:

Host "1" (esxi 6.0) with running VM

Host "2" (esxi 6.7 with additional VCENTER appliance on it)

--> I want the running VM from Host "1" on Host "2".

--> Should I update Host "1" first to esxi 6.7?? Or is that dangerous for my VM on it??

That may be a realy easy question for all of you, but it would be great if you help me with a short answer

Thanks and Cheers

Mario

Hi, Can I install VCSA 6.7 on ESXi 6.5 Host, without any issue?

I have an ESXi host connected to a vCenter. While testing out a couple of VM deployments/undeployments, its observed that whenever a new VM is created via the ESXi WebUI the VM shows up immediately in vCenter, but when it's deleted/unregistered via the ESXi WebUI the VM shows up as orphaned in vCenter.

I was expecting the VM be deleted from the vCenter inventory. I believe, vCenter should detect the delete operation on ESXi host and update it's own inventory automatically. Is that a wrong expectation?

vCenter and ESXi host are running on 6.5.

1 vcsa  and 1 esxi servers running in vmare workstation for lab purposes.

Without a single VM installed or running, my desktop installed RAM is chewed up at the get go.

Does the concept of dynamic memory not apply here?

When i log in with the vsphere web client monitor performance both servers show the exact usage. 1.41GB RAM.
Where does the other 15 Gigabytes go? Is it locked by the vcsa. Not very dynamic like behavior.

Also since the ESXI and the VCSA work towards the same goal of supporting the VMs, does the memory count double.
Like russian dolls. If Esxi host is running a VM needing 2GB, and VCSA manages the ESXI then do we tack on another 2GB to the VCSA as well.

Meaning do we add the VM ram needs to both servers , the vcsa and the esxi?

thanks

Dear Expert,

please help me!

I use HPE_StoreVirtual_VSA_2014 to build one volume named LUNA

on VMware center. two physical servers, two hosts,. Host 01 have two data storage: one is data1 and one is LUNA

                                                                                    Host 02 have two data storage: one is data2 and one is LUNA

check it working well.

I power off both hosts, and after two weeks and power on again.

I found host 02 only have one data storage data 2 there. storage adapter shows on line. when I added new data to host 02. system said name LUNA already there.

I have two question, 01. why power on both host, Could VMs not automatically power on? VMware version is newest 6.5. so I check and can not find power on setup.

                                 02. how to re-mount LUNA to host 02? I have two there VMs in the LUNA, now these three VMs show inaccessible.

brgds

Liu Wei

some one can give me advice?

Recently we faced log files full of storage cause vCenter no longer working. we installed Vsphere management on fleet vessels.

The first two vessel experience this issue. i wonder if Vmware could not clean up old log files, or  not? if system does not clean up automatically. we have to clean up regularly.

It sounds it is not good thing for us.

thanks an  brgds

Liu  Wei

Hello all,

i was trying to post a http request using below command.

"curl -v --insecure --request POST https://x.x.x.x/"

It's reaching upto SSL handshake for 6.5/6.0 where as in 6.7 it fails at hand shake level only.

Below is the out of the same

6.5

==

* About to connect() to 10.126.129.250 port 443

*   Trying 10.126.129.250... connected

* Connected to 10.126.129.250 (10.126.129.250) port 443

* successfully set certificate verify locations:

*   CAfile: /etc/pki/tls/certs/ca-bundle.crt

  CApath: none

* SSLv2, Client hello (1):

SSLv3, TLS handshake, Server hello (2):

SSLv3, TLS handshake, CERT (11):

SSLv3, TLS handshake, Server finished (14):

SSLv3, TLS handshake, Client key exchange (16):

SSLv3, TLS change cipher, Client hello (1):

SSLv3, TLS handshake, Finished (20):

SSLv3, TLS change cipher, Client hello (1):

SSLv3, TLS handshake, Finished (20):

SSL connection using AES256-SHA

* Server certificate:

*        subject: /CN=10.126.129.250/C=US

*        start date: 2019-03-26 22:25:07 GMT

*        expire date: 2029-03-20 22:25:06 GMT

*        subjectAltName: 10.126.129.250 matched

*        issuer: /CN=CA/DC=vsphere/DC=local/C=US/ST=California/O=vc-250.n1kqa.com/OU=VMware Engineering

* SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.

> POST / HTTP/1.1

> User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5

> Host: 10.126.129.250

> Accept: */*

>

< HTTP/1.1 400 Bad Request

< Date: Fri, 12 Apr 2019 10:57:37 GMT

< Connection: close

< Content-Type: text; charset=plain

< X-Frame-Options: DENY

< Content-Length: 0

* Closing connection #0

* SSLv3, TLS alert, Client hello (1):

6.7

==

* About to connect() to 10.126.129.254 port 443

*   Trying 10.126.129.254... connected

* Connected to 10.126.129.254 (10.126.129.254) port 443

* successfully set certificate verify locations:

*   CAfile: /etc/pki/tls/certs/ca-bundle.crt

  CApath: none

* SSLv2, Client hello (1):

Unknown SSL protocol error in connection to 10.126.129.254:443

* Closing connection #0

curl: (35) Unknown SSL protocol error in connection to 10.126.129.254:443

Any idea , what is missing here ?.

Hello All,

i m using Vcenter server version 6.7.0.30000 and trying to add ESXI server with Version 6.7.0.13006603.

The ESXI Server addition keeps failing,  i tried to ping the ESXi server from Vcenter CLI and it was failing as well.  I thought its network reachability issue, but when we enter the ESXi server hostname and credentials, ESXI responses with Cert Fingerprint.

Following the TASK TAB, below is the message: The host may not be available on the network, a network configuration problem may exist, or the management services on this host may not be responding.

while I was reviewing the TASK tab with details, I noticed that it was throwing credential errors, I was using a root user account for integrating Vcenter with ESXi server. I verified by login to ESXi using the root account again.

Using same Vcenter version of Server I m able to add ESXi 6.5 host and it works without issue. But with ESXi 6.7 it seems there is some level of firewall rule that needs to be ticked off.

appreciate your support.

Hi All

trying to upgrade VCSA from 6.7 U1b to 6.7U2 in offline mode .

my current VCSA version is

VCSA 6.7U1b is in ESXi Host Version : ESXi 6.7 U2 13006603

I tried two ways to upgrade VCSA ,

first ,I download the VMware-VCSA-all-6.7.0-13010631.iso  and run the vcsa-ui-installer

once connected to the source and after validated

there is a error messge

Source machine version is 6.7 and this installer is 6.7.

Supported versions for upgrade are equal to or higher than 6.0 and lower than 6.7.

in log

shows

2019-07-12T08:41:09.362Z - info: Login successful to host for source VC, IP: 1.1.5.122:443

2019-07-12T08:41:09.362Z - info: sourceVcService: Source VC Version=6.7, minVersion=6, maxVersion=6.7

2019-07-12T08:41:09.362Z - error: sourceVcService: Source VC version is not supported: vcVersion=6.7.0, minVersion=6

2019-07-12T08:41:09.362Z - error: Source VC version check failed

no idea ,why??

second way

I tried to mount the VMware-VCSA-all-6.7.0-13010631.iso to VM of VCSA in ESXi

and then I log in VAMI ,try to check update from CD -DVD ROM

but nothing happened ... no update resource ..

I log in the vcsa shell ,df -h there is no mounted cd rom ,but  the vm option ,the cd rom is connected and sure that the iso path is correct.

any idea ?

thanks ~~