I am current using ESXi 6.0.
I have asked my ESXi provider about which SATA controller we are using. Meanwhile, I will be applying the patch mentioned in the issue and see if it helps.
Also, I was wondering if this was causing my ESXi to go down. If yes, then how?
P.S I have noticed that once the down ESXi is manually brought up the VMs running on this ESXi work fine.
Thanks.
Hi All,
I have configured ESXI servers to sync time from trusted NTP servers; i could see sync was happening fine but the time was showing as wrong.
After checking i could see that timezone is showing as UTC; but i am on ETC timezone. Because of this time was showing wrongly at ESXi end.
Is there anyway to change the timezone in ESXi6.5 servers? I was not able to find it in ESXi end or even on Vcenter.
Please help me here ASAP.
Thanks
ESXi does not support changing time zone away from UTC.
First time ever doing this... and I know the server requirements, but nothing is clear cut on if it needs to be a dedicated server or not. I'm at a small business of only 145 users. I installed the UEM manager on my view composer server and was considering just doing the same for the App Volumes manager. I've read several docs that say to have two diff instances of App Volumes managers going. I just didn't think that was necessary in my situation. In summary.. am I safe doing these installs piggyback or a dedicated server for my needs.
Thanks.
Did you re-run the vCloud Director configure script after changing the IP address?
/opt/vmware/vcloud-director/bin/configure is the default location for this script - it will (re)confirm the IP addresses for the web portal and the consoleproxy service and alllow you to change these to reflect the new values.
Hello RSEngineer
"this is why .vswp Objects have Force-Provisioning=1 so that they dynamically create FTT=0 Objects if there are not enough Fault Domains (nodes here) to make FTT=1 Objects and thus allowing VMs to be powered on with only 2/3 nodes online."?'
Not sure what else there is to add: for an FTT=1 Object you need 3 Fault Domains(nodes in a non-stretched cluster) data+data+witness components, .vswp are essentially a reserved space for the VMs assigned memory (minus memory-reservation) in the case that it needs to swap to disk (under contention/usage). These are stored as Objects in vSAN and thus need to be created when a VM is powered on - if you only have 2 nodes available then you can't make an FTT=1 Object then making an FTT=0 Object so the VM can power on is essential (and make it FTT=1 later when the 3rd node becomes available).
"Also, with only 2 out of 3 nodes online, can you create a VM with an FTT=0 during that outage? I know this isn't advisable because there is no protection, but I am just wondering if it's possible."
Yes, of course you can as these only require a single Fault Domain/node for component placements.
"Also, when you mentioned the VMs migrating to the surviving nodes from the failed node, what VMware feature is doing that? is it vSphere HA? Does that automatically come with vSAN or is it an added license?"
Yes, vSphere High Availability - vSphere Essentials Plus or higher licensing is required for this feature .
As Joerg mentioned. having 4 nodes (or more) versus 3 really adds to the in-place resiliency that vSAN can provide - if you have a 3-node and you have a hardware failure that may take a number of days to replace/fix then the data is going to be FTT=0 until that gets resolved. If you have 4 or more nodes (and enough overhead space left free), the data can be rebuilt back to FTT=1 on the remaining available nodes, after which it can of course withstand another node failure with all the data still being available, this in my opinion provides a lot of peace of mind.
Bob
Hello Suhag,
How many inaccessible .vswp Objects are there and have you determined that all other data is healthy and accessible?
If all other data is accessible (e.g. you can register and power on all VMs) then you can use RVC to remove the inaccessible .vswp Object(s) that should have by now been recreated by powering on the VM that the original .vswp belonged to:
> vsan.purge_inaccessible_vswap_objects <pathToCluster>
https://www.virten.net/2017/07/vsan-6-6-rvc-guide-part-6-troubleshooting/#vsan-purge_inaccessible_vswp_objectshttps://www.virten.net/2017/07/vsan-6-6-rvc-guide-part-6-troubleshooting/#vsan-purge_inaccessible_vswp_objects
Do note that this is capable of removing inaccessible non-vswap Objects so if you cannot determine the type and/or use of inaccessible Objects it is assisting with deleting then stop and evaluate what you are deleting as opposed to pressing Y.
Bob
Firstly you should be using "Security Tag" and "Equals To". The recommended method to achieve what you want is to use Entity Belongs To. If you've already configured them, see the following attachment for a method to remediate the configuration.
Now to configure your security group using PowerNSX, try the following:
$tag1 = Get-NsxSecurityTag -name HUB-CLIENT
$tag2 = Get-NsxSecurityTag -name ST-ENV-PROD
$tag3 = Get-NsxSecurityTag -name ROL-ORACLEDB
$Entity1 = New-NsxDynamicCriteriaSpec -Entity $tag3
$Entity2 = New-NsxDynamicCriteriaSpec -Entity $tag2
$Entity3 = New-NsxDynamicCriteriaSpec -Entity $tag1
Get-NsxSecurityGroup -name foo | Add-NsxDynamicMemberSet -SetOperator OR -CriteriaOperator AND -DynamicCriteriaSpec $Entity1,$Entity2,$Entity3
Regards
Dale
Topic Name : 使用 Unity 模式
Publication Name : 使用 VMware Workstation Pro
Product/Version : VMware Workstation Pro/15.0
Question :
在Unity模式建议直接缩小到系统托盘，或者增加开关，现在缩小在任务栏感觉占位置，在Unity模式一般情况也很少回到界面去操作。
Hello Bob,
"How many inaccessible .vswp Objects are there and have you determined that all other data is healthy and accessible"
This .vswp object is inaccessible only for one VM. For the same VM, other disk objects are healthy.
Should i try with rebooting the VM or i can directly remove the inaccessible object.
Thanks,
For the actual conversion, use python and CiscoConfParse (GitHub - mpenning/ciscoconfparse: Parse, Audit, Query, Build, and Modify Cisco IOS-style configurations ) to parse the relevant data from the ASA. Once parsed, you can then convert the parsed data into the relevant XML to be configured in NSX via the API.
A word of warning though. If you just blindly migrate the ASA rules, you MUST also set the relevant Applied To for each rule. This becomes somewhat difficult, as you will need to map the IPs used in the rules to match against the relevant VM objects which then can be used in the Applied To (directly or via Security Group membership) of the rule to scope the rule correctly. Failure to leverage the Applied To field will potentially mean that you could cause performance or memory issues due to an un-optimized ruleset.
Dale
Boa noite.
Verifique se a VM tem algum snapshot, se tiver não vai ser possível expandir o disco.
I have one host system where all of my Windows & VMs started getting BSOD shortly after upgrading from WS Pro 12 to 15, I'm running Win 10 Pro.
It happens with existing VMs and newly created VMs. For a while I thought I was having an issue with my SSD, but then moving VM's to another SSD didn't help, neither did moving them to an external platter drive.
I moved the VMs to my Surface tablet, and they work fine, I've moved by v12 pre upgrade back up version of one of them to my OLD 1st Gen i7 (920) system and it has run fine for days, so there is noting wrong with the Windows install.
I can't find anything telling me if any of my hardware could be causing the issue - any help anyone can give? Also -remember I had no problems on Version 12.
Major Hardware components:
ASUS ROG Strix Z270E
Core i7 - 7700K
Intel Optane Memory (32GB)
32GB RAM
CT525MX300SSD1
Nvidia Geforce GTX 1060 6GB
This issue was so long ago, I forgot about it until you replied.
I DID fix it, below is how:
First, some technical details:
So I had a vCenter instance that was vcenter.domain.local and two hosts svr1.domain.local and svr2.domain.local. So what ends up happening is when you add the host to vcenter and you open a console, it actually uses the FQDN for the KMS connection AND SSL verification.
To get it working you have to split your DNS zones. So on the inside you would see:
vcenter.domain.local --> 10.1.1.2
svr1.domain.local --> 10.1.1.3
svr2.domain.local --> 10.1.1.4
and on the outside:
vcenter.domain.local --> 8.8.8.8
svr1.domain.local --> 8.8.8.9
svr2.domain.local --> 8.8.8.10
So when you use the vcenter on the outside, it will be correct, same on inside. vCenter is not NAT-aware and it breaks if you attempt to do it.
When you add your host, you can not add it by its IP because if it is 1) a NAT'd external IP, it connects fine the first time, then fails or 2) internal IP, which is then useless if you try to make it external.
If you guys need help setting this up, let me know
I copied authorize_keys over via WinSCP thinking it would over write the empty existing file. It actually created a new authorize_keys file (/etc/ssh/keys_root I think) and renamed the original .#authorize_keys - still an empty file.
I could not get SSH via public/private key to work and finally rebooted ESXi. Now SSH works via keys I assume the old file was still being used.
The problem is that i can't delete .#authorize keys. I can change permissions but not add write permission, so i can't delete. I get an operation not permitted message. Is there any way to determine what else my be using this file? Or something other then rm -f to delete it?
VCSA Version is 6.7.0.20000
Type: vCenter Server with an embedded Platform Services Controller
ESXi Version is 6.5.0, 8294253
[root@host3:~] esxcli system version get
Product: VMware ESXi
Version: 6.5.0
Build: Releasebuild-8294253
Update: 2
Patch: 50
At the beginning this ESXi host was added by IP address in vcenter web client. Then the host was removed from inventory and re-added to VC with its FQDN.
(There is a working DNS server(win2012r2) in my environment. )
After host was re-added, no vmkernel interface or VMs located in this host was found by cheching through ESXi host configuration -> network -> virtual switch -> DVS&VSS.
It's weird that VMs can be browered from inventory list from VC web client.
I tried to add this host again to DVS by going through -> DVS -> Add new host -> following all steps to add host and all its uplinks/vmk ports it fails saying --
name: reconfigure
status: unable to complete one or more exsi host vSphere Distributed Switch operation
start time: Nov 30, 2018 8:23:58 AM
finish time: Nov 30, 2018 8:24:00 AM
status: error
vDS operation failed on host <host IP>，Received SOAP response fault from []: invokeHostTransactionCall Received SOAP response fault from []: invokeHostTransactionCall
An error occurred during host configuration. got (vim.fault.PlatformConfigFault) exception
diagnosis: Unable to clear DVS propertycom.vmware.netoverlay.layer0 ; Status(bad0004)= Busy
other task detail:
VC version: 10244857
error type: DvsOperationBulkFault
task ID: Task
description ID: dvs.VmwareDistributedVirtualSwitch.reconfigure
Any help appreciated !
Thanks in advance,
Ming
Considering that the CPU is an unlocked "K" model, if there has been some overclocking applied, try to put it back to run on stock frequency/voltage.
There has been at least one post in the past where running VMware Workstation on overclocked CPU does not end up well.
Dear Team,
Replication is not working its giving below error.
problem
Unable to configure replication for virtual machine 'SRM-Test1' because group 'SRM-Test1' cannot be created. Another virtual machine 'SRM-Test1' that has the same instance UUID '5037f550-d473-1fdc-88b9-dc1285e85615' already exists on protection site 'KHVMVCS01.adlabs.com'.
Cause:- 1) In the month of October our "Point to Point" Lease line network shutdown due ISP's issue.
2) We move to VPN via Intenet with SonicWall firewall NSA 3600 and its blocked our replication by firewall .
Troublshhot:- 1) Recently we came to know this is replication blocking by Firewall DPI-SSL, but before that we do lots of exercise with Production DR site Replication Server. We forcefully disconnect Replication and its cleared "production side but not DR side. Due that the above error is came.
2) We now made replication server in exclude list and but the same error came.
3) New Replication is working fine.
Please find my environment details.
Production Site :- Vsphere 6.5 with Replication 6.5
Dr Site:- Vsphere 6.5 with Replication 6.5
Guys need your support to solve the issue.
Thanks for ypur support
How about lockdown mode?
Hello Guys,
I am stuck with a problem where in either one or both vCenter will shut down at different times. After checking the vCenter VM vmware.log file, i believe it is a soft reboot initiated by VM itself or may be ESXi kernel but not sure what is causing this.
The build number for vcenter is 6.5.0.10000 and ESXi version is VMware ESXi, 6.5.0, 5969303. Vcenter is deployed in HA and reboot test of HA works fine. However when one of the vcenter shuts down on its own, the HA does not work.
For some reason when one of the vcenter shuts down, the passive vcenter is not accessible however if I have vCenter HA in healthy state and I shutdown manually Active node, passive node takes over and becomes HA.
The first problem I want to sort out is why vcenter is shutting down with soft shutdown on its own at random time, then second problem which I am not too much worried at this stage is vcenter HA does not work when unexpected shutdown of active vcenter happens.
Attached are the logs as well.
Appreciate your help here. Many thanks.