In my case I had to clean up vCenter server Database as per the below KB article:
↧
Re: VMware vSphere Web Client - migrate option greyed out
↧
Re: To power on the Vm by comparing the hard disk file Name in excel
Hi,
Am getting below error
Get-HardDisk : Cannot validate argument on parameter 'VM'. The argument is
null. Provide a valid value for the argument, and then try running the command
again.
At C:\users\test\Desktop\test.ps1:11 char:25
+ if((Get-HardDisk -VM $_ | %{$hdNames -contains $_.FileName}) -notc ...
+ ~~
+ CategoryInfo : InvalidData: (:) [Get-HardDisk], ParameterBindin
gValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,VMware.VimAutom
ation.ViCore.Cmdlets.Commands.VirtualDevice.GetHardDisk
↧
↧
Re: To power on the Vm by comparing the hard disk file Name in excel
That should have said $vm instead of $_.
I corrected the code above.
↧
Re: Enhanced Linked Mode vcenter 6.5 - Vmotion
hi GayathriS
your statements make sense to me. The only thing that I want to highlight is that, I've already been through the first link taht you provided but I don't see any statement about Cross vC Migration alongside CPU/HW requirements.
So, correct me if I'm wrong, I can achieve cross vcenter migration but, unless EVC it is configured, VMs needs to be shutted down during the proceess.
↧
Re: To power on the Vm by comparing the hard disk file Name in excel
thanks... this works
↧
↧
NSX DLR Control VM Upgrade impact
From this KB Operational Impacts of NSX Upgrades
"Packet forwarding is temporarily interrupted" but is this also true for DLR Edge? AFAIK the VM does not participate in packet forwarding, so... is this statement also true for DLR Edges?
We have some DLR that only does L2 Bridges... what about upgrade impact impact of those?
↧
Re: Powercli error while updating tools
apologies for late response
my powercli version is 4.0, i have attached the vmwarelog as well.
↧
upgrade sequence for vsphere version 6.0(to 6.5 or 6.7)?
i have an infrastructure which has only an ESXi host running several services including vCenter(embedded PSC) and NSX.
both the esxi and vcsa using version 6.0, quite old; and the nsx is version 6.3.2.
( there's no additional hosts to use yet.)
this infrastructure is getting unstable and i'm considering two upgrade path: either upgrade to version 6.5 or upgrade to version 6.7, directly
for both upgrading to 6.5 or 6.7:
is it correct that the upgrade sequence is NSX -> vCenter -> ESXi according to article VMware Knowledge Base and VMware Knowledge Base ???
or maybe these two knowledge bases do not match my demand?
sorry for the dumb question.
↧
Re: ESXi 6.7.0 (бесплатный)_как отключать сам хост по расписанию
Добрый день!
Выключать можно как угодно, хоть подключаясь по SSH и выполняя команду на выключение.
Как его вы включать будете? по кнопке?
↧
↧
Re: Powercli error while updating tools
Looks like you might be having an issue with the CD on that VM.
If possible remove the CD from the Settings, then add a new CD to the VM.
Now try the VMware Tools upgrade again.
You might also try to power off/power on the VM (not the guest OS), before doing the above.
PS: you are running a very old version of PowerCLI.
Any particular reason why you can't upgrade?
↧
Re: ESXi 6.7.0 (бесплатный)_как отключать сам хост по расписанию
Finikiez, добрый)
Подключаться по ssh и выполнить команду на выключение - это не проблема, вопрос в том, как настроить автовыключение esxi-хоста по расписанию (как я написал в шапке =))?
Включать через биос, все проверил - работает отлично, сам стартует + все нужные мне виртуалки)
↧
Add new node in old cluster with new license
I have a cluster of Vsphere 5.5 enterprise edition with four nodes , want to add a fifth nodes , now only 6.5 or 6.7 standard or enterprise plus is available , how to get enterprise and downgrade and what to buy
↧
Re: Strange result when attempting to verify the VIB Acceptance Levels
Here the result with your new script:
The output looks better, but it still shows one line with "PartnerSupported" which is normally excluded by the script (-ne"PartnerSupported"...).
↧
↧
Re: vSwitch and Portgroup Security settings
Completely correct, All rules should be applied in VSS Level and then override whatever you want in PG level
↧
Re: ESXi 6.7.0 (бесплатный)_как отключать сам хост по расписанию
Вам нужен какой-либо внешний хост, который по расписанию будет подключаться по SSH к гипервизору и выполнять команду poweroff VMware Knowledge Base
Cron в ESXi с каждой перезагрузкой загружается пустой. API к бесплатному ESXi закрыт.
↧
Ubuntu 18 host Workstation Player 14 Windows 7 guest crashing 8-8-2018
System:
HP EliteDesk 800 G1 SFF
Intel i7 4790
16 GB RAM
500 GB SSD
Nvidia p600
Workstation Player:
14.1.2 build-8497320
Host:
Xubuntu 18.04
2 GB swap
Guest:
Windows 7
2 core
4 GB RAM
125 GB
minimum recommended swap 2 GB
Run in RAM enabled through /etc/vmware/config
Disabled 3d acceleration
vtx enabled
bridged network
Problem:
guest lock ups, sometimes host lock ups when running Windows 7 update, shutdown and restart.
Host lock ups seemed to cease after setting Run in RAM.
Windows system restore generally recovers.
Windows perpetually tries to install certain updates on shut down.
Windows Update installs:
2017-12 security monthly quality rollup kb4054518: blue screen
2018-07 security rollup kb43440556: OK
office security updates 10 kb's: OK
2018-07 security rollup kb4338818: Blue screen after restart
office updates 6 kb's: OK
optional updates for win 7 5 kb's: OK
office updates 10 kb's: OK
.NET 4.7.2: OK
After installing successful updates:
retry 2017-12 kb-4518 through Windows update instead of Shutdown and install: Failed, reboot ok
retry 2018-07 kb-8818 through shutdown and install: Failed but no bsod
2018-07 preview of monthly quality rollup kb4338821: OK
retry 2017-12 kb-4518 through Windows update instead of Shutdown and install: OK
retry 2018-07 kb-8818 through Windows update instead of Shutdown and install: OK
Resolution:
Set Run in RAM to prevent host lock ups.
2017-12 security monthly quality rollup kb4054518 and 2018-07 security rollup kb43440556 have an issue causing bsod in Win 7 guest in vmware. I don't believe the issue exists in bare metal build, I just rebuilt a Win 7 pc with patches and didn't have any issues. The 2018-07 preview of monthly quality rollup kb4338821 installs correctly and presumably supercedes the failing updates allowing them to clear from the update queue.
Rechecking Windows Update and installing subsequent kb's: OK
↧
Re: Error: VMRC - Failed to initialize SSL session to remote host
Having the same issue here, Mac with High Sierra, VMRC gives the same error, but I am able to use the web console just fine (using Chrome).
Here are parts of the vmware-vmrc.log that are likely relevant:
2018-08-08T16:12:35.497-08:00| VMware Remote Console| I125: VMClient_ConnectMksClientEx
2018-08-08T16:12:35.497-08:00| VMware Remote Console| I125: VMClient_ConnectMksClientEx - trying remote socket connection to x.x.x.x:902 /vmfs/volumes/5fe78593-952d52e9/VMname.vmx
2018-08-08T16:12:35.497-08:00| VMware Remote Console| I125: VMClientConnectSocketEx
2018-08-08T16:12:35.790-08:00| VMware Remote Console| I125: SSLVerifyCertAgainstExternalStore: certificate verification requires confirmation: 5
2018-08-08T16:12:36.177-08:00| VMware Remote Console| I125: VMClient_ConnectMksClientEx - connecting the MKS client
2018-08-08T16:12:36.178-08:00| VMware Remote Console| I125: VMClientConnectMKSClientEx
2018-08-08T16:12:36.191-08:00| VMware Remote Console| I125: VmdbAddConnection: cnxPath=/db/connection/#4/, cnxIx=1
2018-08-08T16:12:36.247-08:00| VMware Remote Console| I125: VmdbCnxControlCb: registered SUBSCRIBE completion callback, cnx = /db/connection/#4/
2018-08-08T16:12:36.356-08:00| VMware Remote Console| I125: SOCKET creating new socket, connecting to /tmp/vmware-username/rmksctrl/mksctrl-0000045598-000-2cd57aff
2018-08-08T16:14:29.704-08:00| VMware Remote Console| I125: BasicHTTP: Request 7F9FF13046A0 in state 1 timed out after 123.966 seconds having sent 0/578 and received 0/-1 bytes. Cancelling request.
2018-08-08T16:14:29.706-08:00| VMware Remote Console| I125: BasicHttpOnSent: xmlReadMemory (NULL == xmlDoc) errorCode 51 responseCode 0 message
2018-08-08T16:16:33.135-08:00| VMware Remote Console| I125: BasicHTTP: Request 7F9FF0C31AC0 in state 1 timed out after 123.428 seconds having sent 0/578 and received 0/-1 bytes. Cancelling request.
2018-08-08T16:16:33.138-08:00| VMware Remote Console| I125: BasicHttpOnSent: xmlReadMemory (NULL == xmlDoc) errorCode 51 responseCode 0 message
2018-08-08T16:16:44.739-08:00| VMware Remote Console| I125: VmdbPipeStreamsOvlError Couldn't read: OVL_STATUS_EOF (remote disconnect)
2018-08-08T16:16:44.739-08:00| VMware Remote Console| I125: VmdbCnxDisconnect: Disconnect: closed pipe for sub cnx '/db/connection/#4/' (-14)
2018-08-08T16:16:44.739-08:00| VMware Remote Console| I125: Internal VMDB error: Pipe connection has been broken (-14)
2018-08-08T16:16:44.740-08:00| VMware Remote Console| I125: Internal VMDB error: Pipe connection has been broken (-14)
2018-08-08T16:16:44.740-08:00| VMware Remote Console| I125: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#4/'
↧
↧
Distributed Switch Versus Standard Switch
So I need to add an Air gapped network to my VM environment. I got the physical network completed and now I am working on bringing the VMware to the Cisco UCS. I can ping the network from my Cisco box.
So for the last few hours, I have been working on adding Virtual Switches and networks and adapters and... and ... All the network configuration has been done on the individual ESX server 5. So I go to the Windows VM Server and try and add the NIC card and it fails. So I have gone through this a few.... dozen times., now I am embarrassed to admit but the VM is not seeing the changes. I then start wondering what is the difference between a distributed switch and a standard switch. The I get struck by lightning and look at the VM server and it currently is hosted on ESX Server 7.
So my question is this; So if I am configuring a Datacenter that I want VM's to move from Chassis 1 to Chassie 7 one way is to individually configure each Chassie with standard switch, but if I want to be more efficient at what I am doing, I go to the Data Center level and configure a Distributed Switch. When this is configured as a distributed switch it shares the configuration with all the Chassis.
Am I correct with the difference?
Thanks in advance
~Sean
↧
A faster way to show VM, VM-Folder, and PowerState
I came across this by LucD and found it extremely usefull
http://www.lucd.info/2016/06/03/get-inventoryplus-inventory-all-vsphere-objects/
I have a following 1 liner, it works OK, but its really slow due to secondary "Get-VM" lookup for powerstate
PS /Documents/vmware/powershell> Get-InventoryPlus | where {$_.Type -eq 'VirtualMachine'} | Select Name,BluePath,@{N="PowerState";E={Get-VM -Name $_.Name | Select PowerState}}
Name BluePath PowerState
---- -------- ----------
goblin-pktbot-16 /morgany-sqa/moria/Block3/goblin-pktbot-16 @{PowerState=PoweredOff}
goblin-pktbot-14 /morgany-sqa/moria/Block3/goblin-pktbot-14 @{PowerState=PoweredOff}
goblin-pktbot-13 /morgany-sqa/moria/Block3/goblin-pktbot-13 @{PowerState=PoweredOff}
goblin-pktbot-12 /morgany-sqa/moria/Block2/goblin-pktbot-12 @{PowerState=PoweredOff}
goblin-pktbot-15 /morgany-sqa/moria/Block3/goblin-pktbot-15 @{PowerState=PoweredOff}
goblin-pktbot-11 /morgany-sqa/moria/Block2/goblin-pktbot-11 @{PowerState=PoweredOff}
goblin-pktbot-10 /morgany-sqa/moria/Block2/goblin-pktbot-10 @{PowerState=PoweredOff}
goblin-pktbot-8 /morgany-sqa/moria/Block1/goblin-pktbot-8 @{PowerState=PoweredOff}
goblin-pktbot-7 /morgany-sqa/moria/Block1/goblin-pktbot-7 @{PowerState=PoweredOff}
goblin-pktbot-9 /morgany-sqa/moria/Block2/goblin-pktbot-9 @{PowerState=PoweredOff}
goblin-pktbot-6 /morgany-sqa/moria/Block1/goblin-pktbot-6 @{PowerState=PoweredOff}
goblin-pktbot-5 /morgany-sqa/moria/Block1/goblin-pktbot-5 @{PowerState=PoweredOff}
goblin-pktbot-4 /morgany-sqa/moria/Block0/goblin-pktbot-4 @{PowerState=PoweredOff}
goblin-pktbot-3 /morgany-sqa/moria/Block0/goblin-pktbot-3 @{PowerState=PoweredOff}
goblin-pktbot-2 /morgany-sqa/moria/Block0/goblin-pktbot-2 @{PowerState=PoweredOff}
goblin-pktbot-1 /morgany-sqa/moria/Block0/goblin-pktbot-1 @{PowerState=PoweredOff}
Also, I'm not sure why the data for "PowerState" is returned as "@{PowerState=PoweredOff}" vs just "PoweredOff"
↧
Re: ESXi v6.7 can't attach Serial port to VM
If possible, try to test the serial port and cable by redirecting the esxi direct console to it.
Attach a vt100 terminal.
Boot esxi and press shift-O
Append the following boot options
"gdbPort=none logPort=none tty2Port=com1";
↧