Hi ,
As per HCL Gen 7 servers are not compatible with vsphere 6.5 .
Attached the list ,
you can use 6.0 U2/U3 then do normal patching with latest versions
↧
Re: ESXi 6.5 HP OEM Purple Screen in HP 380 G7 Server
↧
Re: ESXi 6.5 HP OEM Purple Screen in HP 380 G7 Server
As per HCL Gen 7 servers are not compatible with vsphere 6.5 .
hi I think we are all aware of this. But this is normal cause HPE does only certify there current model. If you look a little bit deeper into the HCL
you can see that all major parts from an G7 are supported. The Hardware runs without any problem with 6.5. The only issue is if you installed the
HPE tools (hp-smx) for harwdare monitoring it will end up in an PSOD, cause HPE has fucked up there own tools.
Even if the hardware is not supported I should never end up in an PSOD!!!
↧
↧
Re: After Restarting, ESXi Host becomes Disconnected. After Connect, VMs become orphaned !!!
Please refer to link Understanding the difference between Not Responding and Disconnected ESXi hosts in VMware vCenter Server (2121031) | VMw…
if you are able to access host via dcui or ssh then check if hostd and vpxa agents are running or not. Vpxa agent is responsible for Vcenter and esxi communicatio. Verify it with commands:
/etc/init.d/hostd status
/etc/init.d/vpxa status
if stopped then replace 'status' with START. If running then try RESTART once and then reconnect host from vCenter.
if it doest work then restart all services with command /sbin/services.sh restart.
Then check by reconnecting host from vCenter side.
↧
Re: ESXi 6.5 HP OEM Purple Screen in HP 380 G7 Server
Hi ,
Major parts may supported but if you open case with vmware and there is chance they say this is not supported .
Also if all the parts supporting then only we use this in production else its risk for infra .
↧
Re: Install ESXi 6.5 on R730 with Intel X710
the PSOD could be this ? ESXi host that uses Intel Corporation Ethernet Controller X710 for 10GbE SFP+ NIC fails with PSOD
Disabling TSO TSO6 LRO
esxcli system settings advanced set -o /Net/UseHwTSO -i 0
esxcli system settings advanced set -o /Net/UseHwTSO6 -i 0
esxcli system settings advanced set -o /Net/TcpipDefLROEnabled -i 0
↧
↧
Re: ESXi 6.5 HP OEM Purple Screen in HP 380 G7 Server
hi,
yes I hope that we not talk here about critical production systems. We for example use the G7 in our testlab and non critical workload.
But I think you knwo how the certification on vmware works. Not Vmware certify the system the vendor does and trigger it.
No vendor has the interest in certify old hardware....
If the G7 would be a whitelabel box all the hardware like CPU / network/ storage/ chipset ) is supported. You can install it
with the normal 6.5 media without any problem. Ony if you wish to use the deeper hardware monitoring and try to install
the hpe tools for that it breaks...
So for my point of view it is not an vmware problem it is an HPE problem, that they have no interest that customer can run an G7 and deliver
high quality software to their customers with fine error handleing.
↧
ESX 6.0 - Firewall with Dynamic IP (Dynamic DNS)
Hi all,
is it possible im vmware esx 6.0 to point the firewall to a hostname instead an ip?
At home I have a dynamic IP and i use my own DynDNS-Service, making myself reachable via DNS (every 5min the ip will be checked).
Is it possible to tell the esx firewall to update it's ruleset once my IP changes? or let it point to DNS instead ip?
The Server is hosted in a Colocation with static ip - directly connected to WAN. It can only be accesses from certain IP's currently - however i also want to be able to manage it from home.
Regards
Chris
↧
Re: Downgraded from 6.5 to 6.0 Datastores are now missing
continuum is right. If the datastores were formatted with the new VMFS6 version, then you need ESXi 6.5 (or recreate the datastores, and restore the VMs from your backup).
Unless you are sure, either watch the VMkernel log via "Alt-F12" while booting the host, or run:
grep -i mismatch /var/log/vmkernel.log
after the host is up.
You'll should find s.th. like:
2017-08-07T ... LVM major version mismatch (device 6, current 5)
for each VMFS6 partition.
André
↧
Re: Windows Server 2016 Really slow on ESXI 6.5
Can confirm that patched to latest 6.5.0 has improved speeds from 20-30mb/s read to 250mb/s read. Just updated via ISO and bootable media for easy life.
Thanks for all the help of those who re-assured it was just something that needed patching.
↧
↧
Re: Windows Server 2016 Really slow on ESXI 6.5
patch to esxi 6.5d or 6.5 update 1?
↧
Re: Windows Server 2016 Really slow on ESXI 6.5
Sorry Colin,
VMware-VMvisor-Installer-6.5.0.update01-5969303.x86_64.iso
So update 1.
↧
Re: Windows Server 2016 Really slow on ESXI 6.5
I have the same problem. Windows Server 2016 is very very slow on esxi 6.5d. Hope it's been fixed by 6.5 update1.
↧
Re: VM problem blue screen VMware ESXi 6.5.0 ???
Thanks bluefirestorm.
I applied the line to my vmx file and it appears to have resolved the panic issue. The vmware.log is still flooded with "Too many channels opened.", and "wrong cookie, discarding message." messages, but the VM is not crashing at least.
Also, I just realized I had not upgraded my ESXi hosts to U1 from 6.5d yet. I downloaded the ISOs last week but haven't upgraded, my mistake!
↧
↧
Re: patching esxi using CLI
Old thread but received this error today & noticed a syntax issue myself.
correct syntax.... must use full path even if you reside in the proper directory
esxcli software vib update -d=/vmfs/volumes/{Your Local Datastore}/ESXi600-xxxxxxxxx.zip
↧
Re: ESXi Host configuration backup fails
unsichtbare,
I've tested this on one the problem systems and it resolved my issue.
The downloads directory is now persistent across reboots.
If you are not using Emulex drivers, remove ima-be2escsi and scsi-be2iscsi drivers.
See this link:
VMware vSphere 6 on Dell EMC PowerEdge Servers Release Notes
esxcli software vib remove -n scsi-be2iscsi -n ima-be2iscsi
I plan on rolling this out sometime this week to the other Dell host using Dell 6.0 update 3 image.
↧
ESXi 5.5 Datastore Corruption...
Hello,
Looking for some guidance here. It appears my RAID controller experienced a fatal error and reset itself multiple times over the weekend. Today, all the VMs on my ESXi 5.5 host are now inaccessible. The latest log file and the -flat.vmdk files are missing for each VM. I dismounted the datastore and ran a VOMA analysis, which is reporting extensive corruption. I'd attach the file, but it is over 56MB in size and is too large to attach to the post. Below are a few segments of the analysis file showing the corruption. Just wondering if you think there is any point of purchasing and opening a case with VMware Support, or am I beating a dead horse at this point?
Checking if device is actively used by other hosts
Running VMFS Checker version 1.0 in default mode
Initializing LVM metadata, Basic Checks will be done
Phase 1: Checking VMFS header and resource files
Detected VMFS file system (labeled:'datastore1') with UUID:556f14b7-d3bb20db-fb8d-40f2e9af86b8, Version 5:60
Phase 2: Checking VMFS heartbeat region
ON-DISK ERROR: Invalid HB address <18446743491834347520>
Phase 3: Checking all file descriptors.
Found stale lock [type 10c00001 offset 173344768 v 129, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 134
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173350912 v 23, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 190
num 0 gblnum 0 gblgen 0 gblbrk 0]
ON-DISK ERROR: <FD c376 r4> corrupted address <PB c698 r288>
ON-DISK ERROR: <FD c376 r4> : invalid FD type 0x700
Found stale lock [type 10c00001 offset 173365248 v 33, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 192
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173369344 v 162, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 253
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173375488 v 50, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 799
num 0 gblnum 0 gblgen 0 gblbrk 0]
ON-DISK ERROR: <FD c376 r16> corrupted address <INVALID c32293 r931>
ON-DISK ERROR: <FD c376 r16> : invalid FD type 0x9066c389
Found stale lock [type 10c00001 offset 173389824 v 57, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 804
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173436928 v 82, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 120
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173438976 v 83, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 132
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173441024 v 84, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 143
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173443072 v 85, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 155
num 0 gblnum 0 gblgen 0 gblbrk 0]
ON-DISK ERROR: <FD c376 r49> corrupted address <INVALID c1027 r0>
ON-DISK ERROR: <FD c376 r49> : invalid FD type 0x85028b00
Found stale lock [type 10c00001 offset 173445120 v 86, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 167
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173447168 v 88, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 236
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173449216 v 89, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 251
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173451264 v 90, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 262
num 0 gblnum 0 gblgen 0 gblbrk 0]
Found stale lock [type 10c00001 offset 173453312 v 91, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 274
num 0 gblnum 0 gblgen 0 gblbrk 0]
ON-DISK ERROR: <FD c376 r54> corrupted address <INVALID c0 r0>
ON-DISK ERROR: <FD c376 r54> invalid generation 0
ON-DISK ERROR: <FD c376 r54> : invalid FD type 0x0
Found stale lock [type 10c00001 offset 173455360 v 92, hb offset 3231744
gen 43, mode 1, owner 58e8cca8-1a667fdb-38d7-40f2e9af86b8 mtime 286
num 0 gblnum 0 gblgen 0 gblbrk 0]
Phase 4: Checking pathname and connectivity.
ON-DISK ERROR: Invalid direntry <BBT File Server-flat.vmdk, 376, 16>
ON-DISK ERROR: Invalid direntry <vmware.log, 376, 54>
ON-DISK ERROR: Invalid direntry <vSphere Management Assistant-flat.vmdk, 376, 4>
ON-DISK ERROR: Invalid direntry <vmware.log, 376, 49>
Phase 5: Checking resource reference counts.
ON-DISK ERROR: PB inconsistency found: (608,0) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,1) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,2) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,4) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,5) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,6) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,7) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,8) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,9) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,10) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,11) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,12) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,13) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,14) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (608,15) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (609,0) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (609,1) allocated in bitmap, but never used
ON-DISK ERROR: PB inconsistency found: (609,2) allocated in bitmap, but never used
....thousands of these errors.
Total Errors Found: 669343
↧
Re: ESXi 5.5 Datastore Corruption...
Hello
I may be able to help.
Please read my instructions : Create a VMFS-Header-dump using an ESXi-Host in production | VM-Sickbay
Create a dump like I described in that link - upload it somewhere and provide a download link.
Then call me via skype - see my signature.
Do NOT try anything else before I have seen the dump.
Ulli
↧
↧
Setting up two sites for SRM
Hello,
In ESXI 6.0, I have two cluster-sites at separate data centers and I wanted to get some guidance on how to properly set them up for SRM. Right now both sites are being managed by 1 vCenter Server with Embedded Platform Service controller. Each site has 4 hosts.
Here is what I was thinking of doing but I was unsure if it was the correct way to go:
1. Separate the Embedded Platform Service controller to its own VM.
2. Create 2 VMs for vCenter and platform service controller for the second site.
3. Join the SSO domain created by PSC from site1 with the site 2 PSC and create a new site
4. Add vCenter server to the second PSC
5. Migrate the second site cluster to the new vCenter server ( by removing the hosts/cluster from the first vCenter server and then adding it to the second?)
Now I would have 2 sites, each with their own vCenter Server and PSC. From here I would be then install SRM on both sites.
I would greatly appreciate any and all feedback regarding this.
Thank you,
↧
Re: 3ware 9650SE - not supported in ESXi 6?
Hey,
I tried to uninstall 3ware drivers from 6.0U3 and run a upgrading to 6.5U1.
Upgrade completed, but not able to install 3ware drivers back to host.
Looks like, time to say goodbye to 3ware 9650SE or stay on 6.0U3
↧
problem with changing virtual machine network name.
hello,
I have problem with changing virtual machine name.
when I change vm name, It's ok,
but in esxcli network vm list, it showes me pervious name and It doesn't change without restart virtual machine.
How can I change vm network name without restart virtual machine?
↧