I need to remove protection from a number of VMs in HCX. There is no connection to our cloud DC, for now.
Is there a manual way to do this via CLI? I can't use vSphere to do this because it is relying on the tunnel to be up.
In the mean time, I can't expand any VM (HCX Protected) disks.
Thanks
Not sure exactly how we got in this situation, but I've been searching all over and have not found a solution.
I have an ESXi host with a couple datastores. One datastore is an NFS datastore that has a few archived VMs, about 20 TB worth. The datastore shows inactive in vCenter, but I cannot see it with esxcli storage nfs list
I can however add it back using CLI: esxcli storage nfs add -H <host-IP> -s /nfs/<share-name> -v <datastore-name>
Instead of the datastore name it pre-pends (1) after, so it's datastore-name (1). In the UI I then have the inactive datastore as well as the newly created "duplicate" datastore.
I've tried various things such as restarting services, disconnect/reconnect host from vCenter as well as the typical steps shown in other similar articles here and elsewhere on the web.
Some additional details:
NFS 4.1
NFS server is a Nasuni Filer which is online and files are readable.
The Filer then has a back end Object Storage system behind so the data is there, I just can't seem to get vCenter to recognize it anymore.
All archived VMs are powered off but listed as inaccessible at the moment.
Anyone have any other ideas or things I can check?
Thanks
Hello,
last August, I've updated our (Free) Esxi 5.5 to version 6.0.
First, everything seems to be working fine.
But after a while, I found out that configuration changes were not preserved after a reboot of the host.
Configuration changes are very rare in our company, for that it took a while to notice the problem, so I am not 100% sure, that this problem stems from the update.
Hardware Information:
ProLiant ML350p Gen8
iLO Self-Test Results:
Supported host
Power Management Controller Version 3.3
....
Embedded Flash/SD-CARD Controller firmware revision 2.10.00 /8 GB SD-CARD in internal slot
CPLD - PAL1 ProLiant ML350p Gen8 SAS Programmable Logic Device version 0x0C
CPLD - PAL0 ProLiant ML350p Gen8 System Programmable Logic Device version 0x4D
....
software information:
vmware -vl
VMware ESXi 6.0.0 build-9313334
VMware ESXi 6.0.0 Update 3
esxcfg-info -e
boot type: visor-usb
After doing some reading in the vmware kb I found out:
[root@esxi-hit:~] ls -la /*boot*
lrwxrwxrwx 1 root root 4 Apr 23 13:19 /bootbank -> /tmp
-r--r--r-- 1 root root 332055 Jul 27 2018 /bootpart.gz
[root@esxi-hit:/etc/rc.local.d] vmkfstools -P /altbootbank
Could not open /altbootbank
Error: No such file or directory
[root@esxi-hit:/etc/rc.local.d] grep bootbank /var/log/esxupdate.log
2019-04-23T06:44:12Z esxupdate: HostImage: INFO: Installer <class 'vmware.esximage.Installer.BootBankInstaller.BootBankInstaller'> was not initiated - reason: altbootbank is invalid: Error in loading boot.cfg from bootbank /bootbank: Error parsing bootbank boot.cfg file /bootbank/boot.cfg: [Errno 2] No such file or directory: '/bootbank/boot.cfg'
So, it seems that there is something wrong with the "Embedded Flash/SD-CARD"
What can I do to get rid of the problem?
Thanks in advance.
best regards from germany
Siegfried
Hello ESXI experts,
As a home project, I have installed ESXI 6.5 on a Dell optiplex 7010, Success.
I have not chosen any VLAN as it is a home router.
The management IP came as 0.0.0.0 and after a reboot changed to 169.x.x.x.x. I have manually entered a 192.168.0.x IP subnet and default gateway but from another windows pc from the same network ( obviously), I am unable to ping the ESXi management ip. Could anyone help me on this please.
hi all
I want to try to update my esxi 6.7 to update 2. For this i run this commands
esxcli network firewall ruleset set -e true -r httpClient
esxcli software sources profile list --depot=https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
but i became this error
[MetadataDownloadError]
Could not download from depot at https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml, skipping (('https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml', '', '<urlopen error [Errno -2] Name or service not known>'))
url = https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
anybody that can helps me to solve this? i don't find any about this issue
One of ESXI host 6.0 is not responding status. we have tried to reconnect the esxi host but it was failed.
KVM console is hung status , not allowing to do any changes using F2 keys.
The VMs running inside are reachable over network and the status is unknown in Vcenter server.
the esxi host is pinging but From KVM console also I am unable to enable/disable anything .
Can we migrate the unknown state VMs to another host using powerCLI command.
Hello all,
I got an issue with ESXi 5.5.0, I get this old server from a school who switch from old support to us, old support don't gave root password and any other password to the school before leave it.
I have search on the net and I have find a way to try to start ESXi w/out root password (delete password into shadow file) but it didn't work, so I have try to "upgrade" ESXi using the same iso of 5.5.0 but after updating it ask for root password, so I have try a fresh install of ESXi on another server and try to change file shadow, after that the old ESXi stop working, so I have reinstall it overwriting the old installation, ESXi start, it see the old datastore but I have no VM configured, in datastore i have all the old VM.
How can I restore all the old VM on the fresh installation of ESXi 5.5.0?
Thanks,
Alessandro
I was taking a look at the prettyPrint.sh script as a means to examining what the cluster settings being pushed down to the hosts from vCenter.
On a v5.5 host I was able to experiment with it, and on v6.7. However my v6.5 test rig (VMware ESXi 6.5.0 build-5310538) the command fails with a syntax error in xmlpp.py at line 23. It is clear when looking at the script is in Python 2 syntax, i.e. no parentheses around the parameters for the 'print' command, whereas the version of Python installed is 3.5.3.
Is this just because the test rig is behind on 6.5 patches?
I have problem with my LENOVO System x3650 M5, It showed error "Memory Device 4 DIMM 4 0: Correctable ECC logging limit reached - Assert" in hardware health status. And it show alert yellow on the front of my server.
I have two Poweredge 2850 connected to a MD3000i SAN. There are only two virtual servers running a File Server and Exchagne 2003 server. We have the file server running on one ESX host and the exchange server running on the other.
I am using the internal Broadcom nics, one going to the storage network and one going to the production network. I am plugging those into a Dell Poweredge 2724 switch. Last night I enabled jumbo framing on the ESX hosts, Switch and MD3000, but we are still having the issue. I am running ESXi 4 Essentials.
For the past two weeks people's access to the file servers has been freezing. Initially I thought it was the exchange 2003 server causing this issue becuase the problem started happening 4 -5 days after we virtualized exchange.
I have narrowed down the issue to where when a user with a large PST file > 5gb tries to open the file or run a repair on the file, the file server locks up. The VM becomes unresponsive, as best as I can tell Exchange is working okay, but it seems like that server becomes slow.
Any ideas or methods to troubleshoot would be great.
Hello! Constantly falling off a virtual machine on ESXi 5.5 with a MONITOR PANIC error: vcpu-0: VMM fault 14: src = MONITOR rip = 0xfffffffffc2aba4b regs = 0xfffffffffc008610
Got 2 HP servers with one 2-port FC and one 1-port FC HBA and ESXi shows incorrect WWNs in web GUI.
Same as here: VMware: Fiber Channel HBA Reports Wrong WWN? | PeteNetLive
Why is that?
6.7.0 Update 2 (Build 13006603)
esxcli storage core adapter list
HBA Name Driver Link State UID Capabilities Description
-------- ---------- ---------- ------------------------------------ ------------------- -----------------------------------------------------------------------------
vmhba1 qlnativefc link-up fc.5001438028551b81:5001438028551b80 Second Level Lun ID (0000:11:00.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
esxcli storage core adapter list
| vmhba2 | lpfc | link-up | fc.20000000c9aa0b7a:10000000c9aa0b7a Second Level Lun ID (0000:08:00.0) Emulex Corporation Emulex LPe12000 8Gb PCIe Fibre Channel Adapter |
| vmhba3 | lpfc | link-up | fc.20000000c9aa0b7b:10000000c9aa0b7b Second Level Lun ID (0000:08:00.1) Emulex Corporation Emulex LPe12000 8Gb PCIe Fibre Channel Adapter |
Hi all,
I have some BL460c blades in a C7000 enclosure running ESXi 6.5 U2 all managed by a VCSA 6.5.
I have a strange and seemingly random (i.e. not easily repeatable) issue with some of the hosts connecting to storage processors on a VNX storage array.
The blades are all configured the same way (via Host Profile) and all the presentation is the same for all the blades in the cluster on the VNX (all blades should be able to see all 10 iSCSI LUNs as set in permissions on the array. The switches between the C7000 and the storage (HP 10GB blade interconnects x 2 and Aruba 10GB switches) are also all configured the same for all ports (storage vLANs tagged the same on all interconnect ports, trunks all tagged the same way etc. All the blades are patched to the same VUM baseline too.
The strange issue is that of the 8 blades in the cluster, 2 of them can only see LUNs presented on one of the 2 storage controllers. Of the visible LUNs they can see, they can interact, access VMs fine. But, these 2 blades will not see the other storage controller - either by Dynamic or Static presentation. Even if I manually add the missing storage controller they still do not see it or the LUNs.
All very strange. When configured, I have confirmed no connectivity using vmkping in a variety of forms to test outbound connectivity from the various ESXi connections configured on each blade. Most it works for, 2 it doesn't, and currently, they sit in Maintenance Mode taunting me.......!
Anyone else come across this? I raised a call with GSS and they had a quick look (started me on the vmkping route) then dismissed it as a networking issue then closed the case. I have gone through the network config with a fine toothcomb and all looks fine and consistent across all the blades, uplinks, trunks, and switches.
All very strange - would appreciate some thoughts if anyone else has come across this?
Many thanks in advance.
Cheers.
Jeremy.
hola
Ten mi servidor con ESXI 6.7 y quisiera bajarle la compatibilidad hasta Esxi 6.0 .
Alguna idea de como solucionarlo.
Hello
Have my server with ESXI 6.7 and I would like to lower the compatibility to Esxi 6.0.
Any idea how to fix it.
Alright, I will try to make as much sense out of this as I can. I have a VXRail with 4 Nodes, tons of space, power, etc. From vSphere Web Client, I have a VM named "Ticketsystem" , I can move it between nodes all day without any issues. However, anytime I move around or do any work on any other VM, it will sometimes cause Ticketsystem to become unresponsive. Sometimes I can console in and do a proper reboot, other times I have to Reset the VM from vSphere. I cannot find an answer for this happening, nor a fix that seems to take. No other VM I have seems to be affected by this, the TicketSystem VM is the only one having this issue.
Ticketsystem Specs: Win Server 2012r2 - 8 Sockets, 8 Cores per Socket. 16GB Ram & 275GB HD. (Started with CPU 4/2 & memory 8GB, gave it more power a couple months ago hoping that would help)
I'm sure there is a ton of more info I should have put, let me know what else can help, and thank you!
I have a power Edge R520 server installed with Dell-ESXi-5.5U2-2068190-A00
I have uploaded the ESX 6.5U1 ISO image (not the custom Dell one)
Update manager returns:
The upgrade contains the following set of conflicting VIBs:
LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560
LSI_bootbank_scsi-mpt3sas_04.00.00.00.1vmw-1OEM.500.0.0.472560
Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again.
After checking VMWare documentation I found the following article:
Scsi-mpt3sas This is a driver VIB provides ‘mpt3sas’ driver which enables support for AVAGO MPT Fusion based SAS3 (SAS 12.0 Gb/s) Controller(s). Dell don’t support this device and hence this driver can be safely removed.
I try to remove it but cannot find the correct VIB name
~ # esxcli software vib list|grep LSI
scsi-megaraid-perc9 6.901.55.00-1OEM.550.0.0.1331820 LSI VMwareCertified 2014-08-27
scsi-mpt2sas 18.00.00.00.1vmw-1OEM.550.0.0.1198610 LSI VMwareCertified 2014-08-27
scsi-mpt3sas 04.00.00.00.1vmw-1OEM.500.0.0.472560 LSI VMwareCertified 2014-08-27
~ # esxcli software vib remove --vibname scsi-mpt3sas
[NoMatchError]
No VIB matching VIB search specification 'scsi-mpt3sas'. Please refer to the log file for more details.Looking for help with the following issue:
Issue: When I team two or more physical nics on my ESXi 5.5 U1 host on the vswitch containing the management vmk and ping the host management vmk IP address from other devices it will drop packets.
Here is some information that I believe may be helpful to others in diagnosing my issue:
- The packet drop rate seems to be between 5-10% when pinging the mgmt vmk from another device on the network.
- When I ping from the ESXi host out to other network devices I get NO packet loss in my outbound pings.
- As soon as I remove the teamed NIC from the vSwitch and go back to using just one physical NIC the problem disappears.
- I am using "Route based on the originating virtual port ID" for my load balancing algorithm on the vSwitch and vmk port itself. No specific configuration settings have been done at the switch level in relationship to this.
- All the host's physical NICs are connected to a stack of 6 Dell PowerConnect M8024k switches. All 6 physical switches are cabled together and configured as one logical switch stack. M8024k switches are all I/O modules in the back of blade chassis.
- All physical NICs are dual-port Broadcom 57810 CNAs. There are total of 6 ports for each host spread across 3 CNAs.
- Al physical NICs are running NPAR to split each physical NIC port out into 4 virtual NICs. This results in a total of 24 vmnics for the host. (6 ports * 4 NPAR functions per port = 24)
- All NIC ports have a native untagged VLAN that the mgmt vmk uses and also carry additional tagged VLANs. Connecting ports on the M8024k switches run in General (hybrid) mode with the mgmt vmk vlan as the untagged vlan.
- Server hardware is Dell PowerEdge M620 Blade server.
Any help would be greatly appreciated. Have seen this issue on multiple hosts running off this particular blade chassis. On other hosts the problem seemed to magically disappear at some point but I cant seem to pin down what configuration change I made on them that resolved the issue for the other hosts.
Thanks,
Mike
Hello,
I'm currently trying to update from 6.7 (Build 10176752) to 6.7 U1 (Build 10302608) via command line.
[root@esxi:~] esxcli software vib update -d /vmfs/volumes/datastore1/update-from-esxi6.7-6.7_update01.zip
[DependencyError]
VIB VMware_bootbank_esx-base_6.7.0-1.28.10302608 requires esx-update >= 6.7.0-1.28, but the requirement cannot be satisfied within the ImageProfile.
VIB VMware_bootbank_esx-base_6.7.0-1.28.10302608 requires esx-update << 6.7.0-1.29, but the requirement cannot be satisfied within the ImageProfile.
Please refer to the log file for more details.
I don't know why there should be a dependency error because there is no patch/update between build 10176752 and 10302608 as described here https://kb.vmware.com/s/article/2143832.
Btw: I also tried to update via online depot but get an "No space left on device" error. I also activated swap usage for the datastore. Without success.
Can anybody help me?
Regards
SeSchi
Hello;
We have an old IBM x3650 M2 with a built-in usb port for booting as a built-in hypervisor (esxi).
The question is; how to create the bootable USB ?
I am currently running ESXI 6.7 and have 3 VMs all running on default VM Network port group which is attached to the default vSwitch0.
What I am wanting to do is create 2 additional port groups and vSwitches. Each port group (3 total) would then have their own respective vSwitch (3 total). I am able to enter the settings of one of the VMs and connect it to the new port group, but once the connection is complete and I boot the VM I am unable to access any of the network resources that I was able to before. I was toying around with resolving the issue and ran the Windows network troubleshooting tool and it states that the default gateway is unreachable. None of the network settings have been change on the Windows side of things. The only changes that have taken place is the port group move. I'm not overly familiar with VMware so it's possible the solution is right in front of me and I'm missing it.