Hi All,
Like the title said, I need to upgrade from vSphere 4.1 to 6.5,
and I was looking for information on the best way to go about
it, as well as any tips or best practices for the upgrade process.
Thanks,
-Matt
Hi All,
Like the title said, I need to upgrade from vSphere 4.1 to 6.5,
and I was looking for information on the best way to go about
it, as well as any tips or best practices for the upgrade process.
Thanks,
-Matt
A PowerEdge 2950 II running VMware ESXi, 6.0.0, 5050593 Image Profile (Updated) ESXi-6.0.0-20170202001-standard has been running without issue for quite some time, and the underlying hardware has had no issues for several years. Recently, an Intel 350T2V2 NIC was installed and configured for use, then a Dell SAS 6 GB HBA External Controller Card 7RJDT was installed. Neither installation had a negative impact on system stability.
Next, upon replacing four (4) Crucial 4GB 240 Pin 512Mx72 DDR2 PC2-5300 CL5 ECC DIMMs with eight (8) A-TECH 8G DDR2 PC2-5300 ECC FULLY BUFFERED DIMMs, the BIOS memory check passed, but seemed to proceed very (very) slowly. ESXi started to boot, but took an extraordinarily (very) long time at the /sb.v00 and /s.v00 steps of the "Loading VMware Hypervisor" stages. Eventually, and a (very) long time later, a message appeared stating "Relocating modules and starting up the kernel...". Again, a significant amount of time transpired. Then, the screen blacked out and this:
VMB: 398: Unexpected exception 2 @0x41800e06957e
VMB: 405: cr0 0x8001003d cr2 0x0 cr3 0x100803000 cr4 0x30
VMB: 407: error code 0x2 rip 0x41800001eee0 cs 0x8
VMB: 409: rflags 0x86 rsp 0x42800001eee0 ss 0x0
VMB: 411: rax 0x12345678 rcx 0x101ffff rdx 0xffff4c000
VMB: 413: rbx 0x0 rbp 0x0 rsi 0x1000
VMB: 415: rdi 0xffff81100004c000 r8 0x2 r9 0x23
VMB: 417: r10 0x8000000000000003 r11 0x0 r12 0xffff4c
VMB: 419: r13 0x420000045221 r14 0xd r15 0x0
VMB: 420: gs 0x10 fs 0x10
VMB: 422: FSbase:0x0 GSase:0x417rce236200 kernelGSbase:0x0
VMB: 139: [0x42800001eee0] 0x41800e06957e
VMB: 139: [0x42800001ef00] 0x41800e06a0ad
VMB: 139: [0x42800001ef900] 0x41800e814c24
VMB: 139: [0x42800001efc0] 0x41800e000fb8
VMB: 85: Halting.
At the same time, the PowerEdge 2950 front panel LCD switch from blue to amber and reported:
E1420 CPU BUS PERR
At this point the system is dead and must be powered off.
The RAC System Event Log shows entries like:
Entry 007 of 007
Severity: Non-Recoverable
Date and Time: Wed May 10 13:48:12 2017
Description:
CPU Bus PERR: Processor sensor, transition to
non-recoverable was asserted.
Dell forums show a flurry of PowerEdge 1950/2950 CPU Bus PERR reports in the Apr-May 2008 time frame, but no conclusive resolutions were spotted, though it seemed apparent Dell acknowledged an issue at some point and RHEL issued a related OS patch at some point. Xeon E5xxx processors were mentioned and this one has Xeon E5345 CPUs. Various posts seemed to suggest the issue might be related to virtualization.
Various BIOS setting changes have been tested per a number of Dell / VMware forum posts to no avail.
The system successfully boots a CentOS 7 1503 Live KDE 64-bit and CentOS 6.5 Live KDE 32-bit DVDs, though one gets an impression that possibly the system is running a slow.
One is led to suspect the new DIMMs triggered this situation, but it seems over hasty to remove a 64GB upgrade and return to a 16GB configuration since 16GB RAM is not going to support VMs planned for this system. To this end, research continues.
That was what I needed! I deleted the audit.log file, rebooted, and the services all started. I also needed to deal with the log disk at 100% capacity. For anyone else who may have this problem I used these articles:
vCenter Appliance root Partition 100% full due to Audit.log files not being rotated (2149278) | VMware KB
/storage/log directory is full in vCenter Server Appliance 6.0 (2143565) | VMware KB
Thanks very much for your help.
My config:
Supermicro X10SDV-7TP4F server bios updated to 1.0b
4 4td nas drives connected to LSI 2116 - P20 firmware recently applied (20.0.7.0).
16GB SATA DOM - esxi 6.5
FreeNAS VM with 32gb datastore on 300 GB SSD -
within esxi I can see the LSI 2116 adapter, then I configure it for passthrough to FreeNAS, however FreeNAS cannot see the controller.
Any ideas, Please????
The system BIOS is 2.0.1, and it appears that a 2.7.0 is available. I have a Dell Server Update Utility (SUU_741_x32_96) DVD issued March, 2014 and found a later SUU published December, 2014 still supports the PowerEdge 2950, so I'm downloading it. The SUUs issued in 2015 seem to have dropped support for the PowerEdge 2950.
Attempts at using the SUU on CentOS 7 1503 64-bit Live KDE DVD fail in a number of ways. The suu utility script bombs out with basic shell errors, and while attempting to use the repository resources directly, the Linux environment seems to have either bogged down and become unusable or has cratered.
Using the CentOS 6.5 i386 Live KDE DVD seems a reasonable next attempt.
what exact tcpdump should i use?
tcpdump -n host x.x.x.x -vv /tmp/filename.pcap
is it udp 902 on the appliance or esxi host?
or it is tcp 443 on the esxi host?
The suu utility runs better in the CentOS 6.5 32-bit Live DVD environment, but bombs when various arguments are used while figuring out how to use it.
The SUU DVD has a repository/PE2950_BIOS_LX_2.7.0.BIN file that contains a BIOS upgrade. Running it gives an error that reports a compat-libstdc.i686 RHEL package is needed to use the utility. There does not appear to be any such package in CentOS, but `yum search libstdc` shows compat-libstdc++-296.i686 and compat-libstdc++-33.i686 packages are available. Having recalled that compat-libstdc++-296-2.96-132.7.2.i386.rpm was once installed on a Mandriva OS when trying to get Dell tools to work on a PowerEdge 4400, this is attempted, but fails.
Upon installing compat-libstdc-33.i686, the BIOS update applies.
At this juncture, VMware ESXi boot does not slow down at /sb.v00 and /s.v00, and in fact starts up without triggering an exception!
By this time, the newer SUU released December, 2014 has finished downloading.
The CentOS 6.5 32-bit Live DVD environment is booted again, and `suu -u` is attempted again. This time, the utility works, albeit with numerous console errors apparently triggered as system component firmwares upgrade.
In the end, most system components seem to have updated: the PERC RAID controller, system baseboard, RAC, RAC Utility, etc.
The system seems to be fine, so attention returns to spinning up VMs... What an adventure!
This conversation has been posted in case it helps someone (me?) in the future, though I'm probably nuts for running this old hardware.
Hi,
Not sure but it is entirely possible that when you connect the USB3 device directly into the VM that either the Windows XP stack or VMware's usb logic gets confused and ends up in a broken state that can only be resolved by rebooting the guest.
FWIW I have never read about anybody who was able to use USB3 within an Windows XP VM successfully. Yes I have seen some claims, but I'm fairly sure that those devices simply negotiated down to USB2.
--
Wil
I have a similar issue and have found a work around that works for me and my environment. I have found that the certificate that is self-generated with the EAP plug-in is getting rejected by Chrome, you can see this if you hit F12 and look at the "Console" and "Security" tabs.
The simple work around is to manually navigate to https://vmware-plugin:8094 (your hosts file is edited as part of the installation) and select "Advanced" and "Proceed to https://vmware-plugin:8094".
This will work as long as the exception is remembered by Chrome. A better solution would be to regenerate the certificate with the appropriate missing information, but VMware is just telling everyone to wait for the next vCenter release.
Honestly, I have no Idea Paul... I no longer keep any vRA 6 environments around. That code was created/tested in vRA 7.2 GA.
how can I make USB3.0 NIC reboot persistent management for ESXi 6.5 running on MAC MINI 6.1 ...
I've installed drivers for usb3.0 ax88179 and plugged a thunderbolt NIC such that I have:
[root@localhost:~] esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
vmnic0 0000:01:00.0 tg3 Up 1000Mbps Full a8:20:66:36:34:5a 1500 Broadcom Corporation NetXtreme BCM57766 Gigabit Ethernet
vmnic1 0000:09:00.0 tg3 Up 1000Mbps Full a8:20:66:06:d8:47 1500 Broadcom Corporation NetXtreme BCM57762 Gigabit Ethernet
vusb0 Pseudo ax88179_178aUp 100Mbps Full 8c:ae:4c:fe:01:94 1500 Unknown Unknown
Since the NIC3.0 interface is very, very weak in performance (number of packets per second), I need to generate traffic across the first two NICs (default/built-in one, and the thunderbolt NIC).
Problem:
Setting the USB3.0 Adaptor w/ cli <esxcli network vswitch standard uplink add -u vusb0 -v vSwitch0> and then removing vmnic0 from vSwitch0 - won't survive reboots.
Thanks for a moment.
I've deployed the vRNI Platform OVA. I have connected its IP address. Results of the page is not very good English, but see screen shot.
So I Please try login in few minutes. Over 24 hours of Please try login in few minutes. I see the console login, but have no credentials to access the shell to troubleshoot.
The simple question is "WHAT??" Am I missing something or is 24 hour startup time for the application to be expected? This is in my home lab. Need some screen shots for an upcoming presentation. Please help.
Thanks, again.
I would also like to know how to do this.
It was easy with vCenter 6 using the old client but the web client doesn't seem to allow it.
Admin Test
Test est test
This is great, Burke! I see now how to properly access values returned by the resourceData. This does exactly what I needed and will be a very helpful example. I appreciate your help with this.
Hi,
If you have PowerCLI installed you can achieve this by executing;
Connect-VIServer "vcenter.tld.com"
Get-VMHost | Select Name,Manufacturer,Model,NumCpu,CpuTotalMhz,ProcessorType,MemoryTotalGB | Export-CSV "C:\_admin\vmhosts.csv" -NoTypeInformation
If you wanted all of the properties of the hosts you can just use:
Get-VMHost | Export-CSV "C:\_admin\vmhosts.csv" -NoTypeInformation
Hope this helps, please mark this as helpful if this resolves your issue,
Kind regards,
Adrian
Hello Rajeev,
This is not a normal logging location that is rotated as dictated by configurations (e.g after x number of days or x number of lines).
This is where vpxd core dumps are directed.
If it is running low on space then you can relocate some of the dumps that are located there (or remove them if they are old and/or you don't need the data contained in them) or you can increase the size allocated to this space.
Example of how to clear ALL .tgz core dump files:
http://blog.migrationking.com/2015/09/how-to-fix-storagecore-filesystem-out.html
(Obviously exercise caution when deleting anything, moving is safer and preferably don't use * wildcard as is done in the above article)
Bob
-o- If you found this comment useful please click the 'Helpful
Hello Matthew,
Looks like you will have to upgrade to ~5.5 U2 and then to 6.5
The Interoperability Matrices are your friend here and will show you what can be upgraded to what for all the main VMware products:
ESXi
https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#upgrade&solution=1
vCenter (Windows-based)
https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#upgrade&solution=2
There may be other variables that need to be accounted for such as the DB-type of your vCenter and whether this can be upgraded:
Another thing to consider that will likely require upgrading is the VMFS datastore versions
https://kb.vmware.com/kb/1005325
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-
Thanks for response Pim,
Issues [note: these are happening randomly with random users] that I am facing are Pinned items on task bar is not persisting and few applications settings are not persisting across sessions.
Thank you,
Vkmr.