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.
From our environment it is all the isilon and oplocks that causes this issue. I think you can actually set the locking time down from the default of 2 minutes which helps. There may also be different software code revisions of the actual oplock code on the isilon that you can play with (I'm not the storage guy). I've also had an issue with if you had your desktop or documents redirected and tried to run a batch or command prompt shortcut from that location elevated as administrator it would take like 30 seconds to launch as you are actually trying to open the file as 2 different users of the same user id which causes the oplocking mechanism to go haywire.
LucD, as always you are johnny on the spot.
So I want to try and figure out a few parts of this. First off I was going to create a new datastore cluster and then have SRDS choose which datastore within the new datastore cluster to select. I figured this would be the best way as the system would receptacle load after each svMotion is completed right? The $vmPerHost line is brilliant, does that end up being individually accessible based on each host?
So this looks like the loop will wait will all of the VMs within the first pass are svMotioned before picking up the next VM within the queue, if I am reading this correctly. That would be a single large VM would delay the svMotion of all of the other ones. So that was the trick I was trying to get at having x number of individual queues running in tandem with one VM each svMotioning.
As always many thanks for your help with this.
This error indicates that there is a configuration issue with glance-api. The exact trace or reason can be found at the very top of glance-api logs when it loads the 'vi' store. Can you look for that ?
I don't recall exactly but the trace must contain the words "BadStoreConfiguration" or "Failed to load driver". Sometimes this happens if the datastore got relocated under different datacenter or folder and glance isn't aware of the change.
Switching to 'file' store will store all your images locally on the controllers and doesn't use the VMware configuration. default_store='vi' is the supported store for VIO. If we fix the BadStoreConfiguration then you should see the image gets uploaded to the vSAN datastore.
Hi Team,
Can anyone help me to understand what are the parameters, based on which vROPS gives the value of 'Time Remaining'.
how can we calculate it manually to verify ?
Thanks
Randhir
Hello
Thank you for the advice. I am going to further investigate this however I have a few additional questions.
As we now are using vSAN does the stores still need to be = vi or something else ?
We did change the glance storage from datastoreh1 however now we have two when we added the vsandatastore.
Do we need to create an images folder on the vsandatastore and make that configuration change in the glance-api.conf so that the directory the images are being stored is /images on the vsandatastore ?
I thought it may have to do with the VIO management cluster not having access to the vSAN datastore as this storage is on the Compute Cluster and the Management Cluster does NOT have access to the vSAN storage. Does this matter ?
Ill run some tests later and advise on the glance-api logs.
Hi Team,
Can any one help me that which field i can select to capture disk utilization of VM's in vROPS for windows and Linux.
i am only able to see 'Disk Capacity Remaining %' in the raw data.
Thanks
Randhir
Try creating the pool with provisioning disabled, then change the policy to the correct one, then enabling provisioning.
I'm having some issues that I'm hoping the community can solve. I have a vCSA 5.5 in my environment that I want to upgrade to 6.5. I downloaded the 6.5e ISO and mounted it, ran the installer. The problem is I am stuck at step 3. I input the info for the source appliance (the current vCSA 5.5) with the appropriate info which seems to take. However the info I input for the second section, the ESXi Host or vCenter Server info seems to be the issue. I have used both the direct IP for the host as well as the IP for the vCSA 5.5. Using port 5480 as I can't get further on any other port.
When inputting the info using host IP, I get the error "Failed to get an SSL thumbprint of the source server certificate for [host IP]."
When inputting the info using vCSA IP, I get the certificate warning window, which I press Yes to, but then the error is "Invalid credentials for ESXi host or vCenter Server." I have switched the username to be any of these: root / administrator@vsphere.local / vmadmin (this is our vCenter admin account) / vmadmin@vsphere.local - all come up with the same error. I know that all of these work to log in to the host directly, and that the xxx@vsphere.local accounts work when logging into the vCSA through both the web ui and using the vSphere client.
So what am I doing incorrectly, and why won't it let me upgrade? Should I just cut my losses and make a new vCSA and then remove my hosts from the old one and add them to the new one? Is there something else I should try to do?
Hot off the press -- native AD is now supported in LI 4.5. KB and release notes have been updated. Recommendation is still to move to VIDM, but AD can still be used.
I recently posted about an error message when attempting to power on a DOS program that is held on my flash drive. It worked for a couple of days and then I began to get this error message that is:
VMware Workstation unrecoverable error: (vcpu-0)
vcpu-0:VERIFY vmcore/vmm/main/cpuid.c:386 bugNr=1036521
A log file is available in "C:\Users\Swamp\Documents\Virtual Machines\DOS\vmware.log".
You can request support.
To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
You can also run the "vm-support" script in the Workstation folder directly.
We will respond on the basis of your support entitlement.
I have the Virtualization enabled on the BIOS, my instructor of the class I am taking has placed another copy of the DOS program on the flash drive and deleted the old one. I recently upgraded to 12.7 which did not help. I hope I am offering enough inform@ation to get some help out there. Thanks
I also failed to mention that I am using an HP Envy m7 with a 64bit OS and 16 GB of RAM with i7--7500U CPU @ 2.7GHz 2.9 GHz and Windows 10 Home and a Sacdisk Ultra USB 3.0 Flash Drive 128 GB
Thanks, I did a new thread and hopefully added what I can
I am new to Mirage and have been successful in assigning base layers to multiple machines, however our most recent base layer just seems to get stuck in some sort of loop. Machines will get to 93% Initializing Layer Update, hang there for a while then hit 100%. The machine will get to 40% on Assign base layer, error and start over. The exception listed in the error is "InternalError". I am not 100% sure where to start troubleshooting this. I can go back and use an older base but I would like to know what may have happened to cause this, what logs could help, etc.
Any information would be greatly appreciated!
Thanks,
Brad
Correct, the VM are grouped by ESXi name.
In each of the groups there is a Group property that contains all the VM running on that ESXi node.
Correct, the script will wait till all svMotions are completed before continuing and starting the next batch.
Let me see how I can adapt this to always start a svMotion for each ESXi on which there is none running.
