Hi Folks,
We need to apply a Windows patch to a file server that our Mirage server uses as its storage Volume.
Is stopping the Mirage services all we need to do before rebooting it?
Hi Folks,
We need to apply a Windows patch to a file server that our Mirage server uses as its storage Volume.
Is stopping the Mirage services all we need to do before rebooting it?
This definitely looks like a bug, I suggest to open a SR for this.
Hello,
This is due to DRS being a requirement to have resource pools in the first place.
You can of course snapshot and revert them to avoid their loss, disabling DRS in Web Client will prompt you to do this when attempting to disable:
kb.vmware.com/kb/2032893
Bob
-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-
That seems to indicate that your copy of the script had an issue.
You can remove the Write-Host lines from the 2nd part of the script, and export the $newReport array to a CSV file.
Then it should be working.
Yeah I already have one open, but it's been slow to get traction. I'll escalate it to see if it gets moving.
Thanks, Ilian Ilievfor the detailed explanation and possible options!
I am curious about the options one can think of in case of using the "share a unique session" mode option i.e. the service account for the vCenter Server while adding in vRO. Any suggestions when vRO workflows run as part of the vRO Scheduler?
SRM requires a vCenter at both sites as well. Really, from a DR perspective, if you use vCenter at one site now, you will want a vCenter at your recovery site as well. It usually doesn't make sense to make vCenter a part of the failover so a second vCenter will often make sense.
At the end of the day though it really comes down to your requirements and constraints.
You can retain the resource pool from webclient when disabling DRS
If you found this or any other answer helpful, please consider the use of the Helpful to award points.
Best Regards,
Deepak Koshal
CNE|CLA|CWMA|VCP4|VCP5|CCAH
I tracked down the reason it is not working for me. The NFS datastores I am mounting from our net app appliance do not have a value for .ExtensionData.Info.vmfs.uuid. Can anyone shed light on why this is so?
VMware called me today.
Appantly I am running version 6.0 U3 and you cannot upgrade to 6.5 from that version. The patch to do so is not supposed to be out until late July. I am going to uninstall everything and try restoring a DB from my 5.5 version and then upgrade from there. Fingers crossed.
Thanks for the replies.
Cheston
Dario,
Thank you!
I was using the vicfg-user.pl when I thought I could update Roles. But, as you told me, their no Roles when you have a Standalone ESXi Host. Roles are used when you have vCenter and the ESXi host is controlled by vCenter.
Using the vicfg-cfgbackup.pl --server=x.x.x.x --username=username -l filename command backup the ESXi host to the Windows 10 PC!
I really appreciate all your help!
T.J.
So it's not possible to use the vSphere client on the recovery site to avoid another vCenter license? These VMs are very low maintenance; once they're running we won't need access.
Hi All,
today we had the same issue as described above.
To remember:
Could not connect to one or more vCenter Server systems:
On VCSA Shell:
service-control --status vmware-vpxd shows "stopped"
service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
We contacted VMware Support and they analyzed the core dump logs (/var/core) and could figure out a problem with a single VM in our environment.
There was a problem with a network adapter on that VM (DB entry NULL)
Solution that worked for us:
Find VM
/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres (Login to postgres)
select v.id, v.local_file_name, h.IP_ADDRESS FROM VPX_VM v, VPX_NIC n, VPX_HOST h WHERE v.id=n.entity_id and v.host_id=h.id and n.network_name=''; (get affected VM)
select * from vpx_entity where id = '<YOURID>'; (get affected VM Name)
Fix VM / vpxd (for our specific issue with database issue)
Remove Network Adapter, save config, readd Network Adapter
service-control --start vmware-vpxd
You should now be able to login to your vCenter.
So the NULL Value in the database seem to be a really rare issue. In case of "Could not connect to.....:" just Find VM unregister it from vCenter and Reregister.
Hope this helps somebody!
Regards,
Gabriel
Are you using the administrator@vsphere.local account? If so, the password for that account is set to expire after 90 days, by default.
If that's the case, perhaps this article can help you reset the SSO password for that account: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID-06FF691C-16EC-4AEF-BCE8-2438B51DE693.html
Maybe something like this.
Add host names to the vmhosts.nfs file. Run the following.
Connect-VIServer -Server vcenter01 $hosts = Import-CSV vmhosts.nfs foreach ($vmhost in $hosts){ write-host Doing $vmhost.vmHost $x = Get-VMHost -Name $vmhost.vmHost | New-VIPermission -Role Admin -Principal domain\group write-host $x }
To resume :
ESXI 6.5
I have a guest with two network card.
One with E1000 on Vswitch1 with nic0 (mtu 1500)
One with VMXNet3 on Vswitch2 with nic1 (mtu 9000)
The MTU is OK on the each nic and vswitch.
[root@ESXI2:~] esxcfg-vswitch -l
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0 1536 5 128 1500 vmnic0
PortGroup Name VLAN ID Used Ports Uplinks
VM Network 0 1 vmnic0
Management Network 0 1 vmnic0
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
HA 1536 4 1024 9000 vmnic1
PortGroup Name VLAN ID Used Ports Uplinks
HA 0 1 vmnic1
[root@ESXI2:~] esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vmnic0 0000:03:00.0 tg3 Up 1000Mbps Full a0:b3:cc:df:1c:9f 1500 Broadcom Corporation NetXtreme BCM5723 Gigabit Ethernet
vmnic1 0000:02:00.0 r8168 Up 1000Mbps Full 00:e0:4c:80:1a:50 9000 Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
[root@ESXI2:~]
My guest is working with these setting, but jumbo frames are not enabled. Ping working fine on each IP.
So i want to enable on the second card, because MTU 9000 is set.
When i set MTU 9000 on this card on the guest, the guest reboot, and the setting is not kept.
I lose ping because guest reboot, and ping is OK after reboot finished....
So i would like to know why when i change MTU, the guest reboot ? It's a bug ?
I don't use the good way ?
my Broadcom doesnt support MTU 9000, i know. But Realtek is ok. I have same card on another machine not with ESXI and no problem.
PS: I disabled ipV6 too on vswitch.
I have some doubt about my vmkernel :
[root@ESXI2:~] esxcfg-vmknic -l
Interface Port Group/DVPort/Opaque Network IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type NetStack
vmk0 Management Network IPv4 192.168.0.151 255.255.255.0 192.168.0.255 00:e0:4c:80:1a:50 1500 65535 true STATIC defaultTcpipStack
[root@ESXI2:~]
Logs from ESXI when i change MTU on guest :
2017-06-23T20:35:15.284Z cpu1:88725)Vmxnet3: 17265: Disable Rx queuing; queue size 256 is larger than Vmxnet3RxQueueLimit limit of 64.
2017-06-23T20:35:15.284Z cpu1:88725)Vmxnet3: 17623: Using default queue delivery for vmxnet3 for port 0x3000007
2017-06-23T20:35:15.284Z cpu1:88725)NetPort: 1660: enabled port 0x3000007 with mac 00:0c:29:44:93:21
2017-06-23T20:35:18.218Z cpu0:66070)Uplink: 4622: vmnic0: Non TSO L2 payload size exceeds uplink MTU. FrameLen: 9014, L3 header offset: 14
Like I said previously, VR and SRM require a vCenter at the recovery site. If you don't want a vCenter then more than likely your option would be looking at a backup solution. You could also look at a solution like Veeam or RecoverPoint For VMs. I don't know if either or both of them require a vCenter at the recovery site.
Hi Luc
the requirement are
once a folder/office has been selected,
new-vm needs these
datastore name from esxhost - which is local-esxhostname
highest level of vm hardware version
windows 2012 (64bit) OS
prompt for vcpus
prompt for mem
prompt for network
use paravirtual
choose existing disk in local-esxhost datastore
Try like this, that should also work for NFS datastores
$dsName='MyDS'
$uArgs= @{
volumelabel =$dsName
nopersist =$true
}
Get-VMHost-Datastore$dsName|%{
$esxcli=Get-EsxCli-VMHost$_-V2
$esxcli.storage.filesystem.unmount.Invoke($uArgs)
}
No, We didn't restart as all the VMs are in Prod. We keep getting request for RDM expansion and it is very difficult to get the size from powercli reports as it shows old size.