Hi all, My SRM license capacity shows 500 VMs on bothe vCenters (License tab). After configuring the SRMs and assigning the asset license the capcity (License --> asset --> solution) shows 75. ...
See more...
Hi all, My SRM license capacity shows 500 VMs on bothe vCenters (License tab). After configuring the SRMs and assigning the asset license the capcity (License --> asset --> solution) shows 75. Can i have some directions or to understand why 75 instead of 500? Thanks
Hi all, I am trying to add a new license to my vcenter but it failed with: The created license with serial key XXXXXX cannot be assigned to the chosen asset. I am getting the error while trying...
See more...
Hi all, I am trying to add a new license to my vcenter but it failed with: The created license with serial key XXXXXX cannot be assigned to the chosen asset. I am getting the error while trying to assign the license from : administration --> Licenses --> asset --> vcenter server systems --> choosing my new license vCenter 7.0.3 License for SRM v8.
The problem is not with the storage. on my network, I have two clusters: - One cluster with two ESXi servers. - One cluster with one ESXi server. Only the first cluster is not working. The se...
See more...
The problem is not with the storage. on my network, I have two clusters: - One cluster with two ESXi servers. - One cluster with one ESXi server. Only the first cluster is not working. The second one works perfect
Hi, Even though the PE is accessible, the ESXi server claim that PE is not configured. 2023-05-10T10:02:49.307Z error vvold[2099648] [Originator@6876 sub=Default] VasaOp::IsSuccessful [#18566]: bin...
See more...
Hi, Even though the PE is accessible, the ESXi server claim that PE is not configured. 2023-05-10T10:02:49.307Z error vvold[2099648] [Originator@6876 sub=Default] VasaOp::IsSuccessful [#18566]: bindVirtualVolume transient failure: 22 (STORAGE_FAULT / ESXi host has no PE configured that can reach a VVol / ) [root@esx-gdc-n62:/var/log] esxcli storage vvol protocolendpoint list
Type: SCSI
Accessible: true
Configured: true - VASA provider registered and online. - Certificates installed and all is ok. I know that reboot will solve the problem but is there any solution to avoid rebooting the ESXi server? Thanks
Any help with the following error: 2022-01-11T13:51:10.091Z warning vmware-dr[04439] [SRM@6876 sub=vmomi.soapStub[7] opID=6e76717f:8892] SOAP request returned HTTP failure; <SSL(<io_obj p:0x00000000...
See more...
Any help with the following error: 2022-01-11T13:51:10.091Z warning vmware-dr[04439] [SRM@6876 sub=vmomi.soapStub[7] opID=6e76717f:8892] SOAP request returned HTTP failure; <SSL(<io_obj p:0x0000000001b22fb8, h:21, <TCP 'x.x.x.x : 43302'>, <TCP 'x.x.x.x : 443'>>), /sms/sdk>, method: queryActiveAlarm; code: 500(Internal Server Error)
Hi all, i tried to create a thick hard disk in the storage provider: New-HardDisk -VM vm10 -StorageFormat Thick -CapacityGB 1024 The result is "Thin" provisioning while expected a thick. An...
See more...
Hi all, i tried to create a thick hard disk in the storage provider: New-HardDisk -VM vm10 -StorageFormat Thick -CapacityGB 1024 The result is "Thin" provisioning while expected a thick. Any ideas?
Hi, is there any way to check which LUN ID belongs to the protocol end point? LUN id is not presenting with the following command: esxcli storage vvol protocolendpoint list Thanks
Is there any explanation why "DNS Name" is changed after powering on the VMs (Vms deployed from template ). I am using customization specification manager with a spec that already created with t...
See more...
Is there any explanation why "DNS Name" is changed after powering on the VMs (Vms deployed from template ). I am using customization specification manager with a spec that already created with the following configuration: Name = Linux Template OS type = linux computer name = Test + 'unique suffix' DNS name will be as i mentioned in "computer name" but it changed after powering on the VM. Command used: New-VM -Name $Vm12 -Template $Template_name -VMHost $ESX03 -Datastore $DS_ESX03_1 -OSCustomizationSpec "Linux Template"
