User003's Posts

Apparently no one knows how to solve the problem, and probably the vSan technology is not yet able to go beyond the test lab
Hello, help me please I have big problem with my VM on vSAN One of my vms reports a problem. I have attached screenshots. Is there any way to fix this without data loss or with partial loss? ... See more...
Hello, help me please I have big problem with my VM on vSAN One of my vms reports a problem. I have attached screenshots. Is there any way to fix this without data loss or with partial loss? debag message problem object=c9c8fe60-f035-8dc4-41d4-38d547b03581 owner=597d07eb-09bc-7b19-3714-001b2162ec4b(Health: Healthy) uuid=c9c8fe60-f035-8dc4-41d4-38d547b03581 type=CONFIG_STATUS rev=16 minHostVer=3 [content = (("state" i45) ("CSN" l344) ("SCSN" l363))], errorStr=(null) root@noda4:~] /usr/lib/vmware/osfs/bin/objtool getAttr -u c9c8fe60-f035-8dc4-41d4-38d547b03581 Failed to get object attributes : Input/output error 327684. [root@noda4:~] cmmds-tool find -f json -u c9c8fe60-f035-8dc4-41d4-38d547b03581 { "entries": [ { "uuid": "c9c8fe60-f035-8dc4-41d4-38d547b03581", "owner": "597d07eb-09bc-7b19-3714-001b2162ec4b", "health": "Healthy", "revision": "19", "type": "DOM_OBJECT", "flag": "2", "minHostVersion": "3", "md5sum": "b87f4bf99dbfa9a1b6a7a4855fcee5e2", "valueLen": "2304", "content": {"type": "Configuration", "attributes": {"CSN": 344, "SCSN": 363, "addressSpace": 107374182400, "scrubStartTime": 1666570505387027, "objectVersion": 10, "highestDiskVersion": 10, "muxGroup": 646428584123136, "flags": 1, "groupUuid": "c7c8fe60-fa1b-1f0e-199a-38d547b03581", "raidFact": 300, "compositeUuid": "c9c8fe60-f035-8dc4-41d4-38d547b03581"}, "child-1": {"type": "RAID_1", "attributes": {"pointFixTargets": [4294901762, 4294967295, 65535], "scope": 3}, "child-1": {"type": "Component", "attributes": {"capacity": [0, 107374182400], "addressSpace": 107374182400, "componentState": 9, "componentStateTS": 1680892514, "transient": 1, "faultDomainId": "59b3d368-ab9f-620b-a746-f832e4724aa7", "flags": 327680, "lastScrubbedOffset": 42846650368, "subFaultDomainId": "59b3d368-ab9f-620b-a746-f832e4724aa7"}, "componentUuid": "0cf56863-0cd2-04e1-d01a-ac1f6b11710e", "diskUuid": "5227fb64-d625-0ed9-4eef-86ea169da9d7"}, "child-2": {"type": "Component", "attributes": {"capacity": [107143495680, 107374182400], "addressSpace": 107374182400, "componentState": 6, "componentStateTS": 1680935769, "staleLsn": 18446744073709551615, "faultDomainId": "59977b6c-5cfe-1b55-8013-38d547b03581", "flags": 65536, "nVotes": 2, "subFaultDomainId": "59977b6c-5cfe-1b55-8013-38d547b03581", "rLsn": 18446744073709551614}, "componentUuid": "608e2e64-2025-0e6b-f8e8-ac1f6b447ea4", "diskUuid": "5262ff87-fb4d-9f67-eace-2967f519080a"}, "child-3": {"type": "Component", "attributes": {"capacity": [107143495680, 107374182400], "addressSpace": 107374182400, "componentState": 6, "componentStateTS": 1680934203, "staleLsn": 18446744073709551615, "faultDomainId": "59b3d368-ab9f-620b-a746-f832e4724aa7", "flags": 65536, "nVotes": 2, "subFaultDomainId": "59b3d368-ab9f-620b-a746-f832e4724aa7", "rLsn": 18446744073709551614}, "componentUuid": "36d52f64-e2f9-5d80-12ef-ac1f6b11710e", "diskUuid": "5227fb64-d625-0ed9-4eef-86ea169da9d7"}}, "child-2": {"type": "Witness", "attributes": {"componentState": 5, "componentStateTS": 1680856374, "isWitness": 1, "faultDomainId": "597d07eb-09bc-7b19-3714-001b2162ec4b", "nVotes": 2, "subFaultDomainId": "597d07eb-09bc-7b19-3714-001b2162ec4b"}, "componentUuid": "36d52f64-0a2e-6180-64a6-ac1f6b11710e", "diskUuid": "52475c21-2d12-5566-d831-6221ba95ea12"}}, "errorStr": "(null)" } ,{ "uuid": "c9c8fe60-f035-8dc4-41d4-38d547b03581", "owner": "597d07eb-09bc-7b19-3714-001b2162ec4b", "health": "Healthy", "revision": "16", "type": "CONFIG_STATUS", "flag": "2", "minHostVersion": "3", "md5sum": "378938463897daa20ab2aee98ecf5bda", "valueLen": "96", "content": {"state": 45, "CSN": 344, "SCSN": 363}, "errorStr": "(null)" } ]    
hi, I have a vCenter located behind nat and a group of hosts with a public ip when connecting hosts to vCenter using changes in the file /etc/vmware/vpxa/vpxa. cfg <serverIp>10.0.0.1< / serverIp> to ... See more...
hi, I have a vCenter located behind nat and a group of hosts with a public ip when connecting hosts to vCenter using changes in the file /etc/vmware/vpxa/vpxa. cfg <serverIp>10.0.0.1< / serverIp> to an external IP address <preserveServerIp>true</preserveServerIp> the hosts are visible in vcenter but an error appears in the logs   [2021-09-21 17:53:21:330 'HostUpdateDepotManager' 139669465257728 ERROR] [scanHost20, 371] result for host: **** (entity: host-26900) shows error : -----Result Begin (*****)----- <esxupdate-response> <version>1.50</version> <error errorClass="MetadataDownloadError"> <errorCode>4</errorCode> <errorDesc>Failed to download metadata.</errorDesc> <url>http://192.168.1.10:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip</url> <localfile>None</localfile> <msg>('http://192.168.1.10:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip', '/tmp/tmpfquu19yt', '&lt;urlopen error timed out&gt;')</msg> </error> </esxupdate-response>   it turns out that the host is still trying to access the vcenter on the internal ip, how can this problem be solved?  
localhost:~ # /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name --server-name                                               localhost vCenter.maysun.local ================== Please sel... See more...
localhost:~ # /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name --server-name                                               localhost vCenter.maysun.local ================== Please select: 0. exit 1. Test LDAP connectivity 2. Force start replication cycle 3. Reset account password 4. Set log level and mask 5. Set vmdir state ================== 3   Please enter account UPN : administrator@maysun.local VmDirForceResetPassword failed (9106) ================== Please select: 0. exit 1. Test LDAP connectivity 2. Force start replication cycle 3. Reset account password 4. Set log level and mask 5. Set vmdir state ================== 3   Please enter account UPN : cn=administrator,cn=users,dc=maysun,dc=local     VmDirForceResetPassword failed (9106)
root login has been used
launched with the shell command shell but the pi still reset password does not work ================== Please select: 0. exit 1. Test LDAP connectivity 2. Force start replication cycle 3.... See more...
launched with the shell command shell but the pi still reset password does not work ================== Please select: 0. exit 1. Test LDAP connectivity 2. Force start replication cycle 3. Reset account password 4. Set log level and mask 5. Set vmdir state ================== 3   Please enter account UPN : cn=administrator,cn=users,dc=vSphere,dc=local VmDirForceResetPassword failed (9106) ================== Please select: 0. exit 1. Test LDAP connectivity 2. Force start replication cycle 3. Reset account password 4. Set log level and mask 5. Set vmdir state ================== 3   Please enter account UPN : Administrator@vSphere.local VmDirForceResetPassword failed (9106) vcenter VMware vCenter Server Appliance 6.0.0.20000
I have 1 ssd and 1 hdd in 1 server I want to add 1 more hdd to the server and thus expand the disk group. Is this possible?
Tell me whether I can use vCenter in 1 segment, say 192.168.1.0/24 and a couple of other hosts behind the router say esxi1 192.168.2.0/24 and esxi2 192.168.3.0/24 just 3 branches merged into 1 n... See more...
Tell me whether I can use vCenter in 1 segment, say 192.168.1.0/24 and a couple of other hosts behind the router say esxi1 192.168.2.0/24 and esxi2 192.168.3.0/24 just 3 branches merged into 1 network, through the tunnel, we want each branch to put 1 server and do data replication night in the main data center. Since the channel is narrow to work directly with the data center is problematic, but replication per night will suffice. Tried 1 host to register so he kind of appears and then falling off and why the SP is changed to the host IP of the VPN interface of the segment vCenter esxi 6.0 hosts also on 6.0 I just don't understand this is a routing problem, or indeed between vCenter and esxi go arp or other packets that does not pass the router.
Thank you, I clicked to reapply the VM storage policy and fix it
How to fix this? Restart the vCenter has not solved the problem. This error is only on 1 VM