Quantcast
Channel: VMware Communities : All Content - vSphere Upgrade & Install
Viewing all 3263 articles
Browse latest View live
↧

vCenter 7 unable to use update menus...

June 5, 2020, 2:39 am
$
0
0

Hi,

 

I have now upgraded my older vCenter Essentials 6.7U3 to the

After the complete check I was unable go to the updates menus (baselines, HW Tools, VM Hardware). I have there still the rotating wheel.

So I cant acces the Baselines and set it to upgrade my hosts.

 

I have also I thing with it builded another issues or problems:

 

1.     In LifeCycle manager I have these error: Status 404 - https://x.x.x.x/ui/vum-ui/rest/vcenters/5a8080e2-5dca-434a-87f4-303c3cb3f9b1/compliance

2.     Anny update menu (submenu or settins) end with rotating wheel

3.     By patch Setup menu have unexpected error

 

Please is possible to help me?

 

Thanks.

↧
Search

Datastore lost after 6.7 to 7.0 Upgrade

June 7, 2020, 5:05 pm
$
0
0

Hello dear Community, after upgrading my VMware ESXi from 6.7 to 7.00 with the CLI Online Method, all of my VM's are Unusable because the Datastore is missing. I think it has to do with the lsi megaraid sas 9260-4i Controller that is providing the boot-Drive and the Datastore. I tried to rescan the Devices and looked in the Cli but without luck, I could only see that it was in fact detected by the OS with the "lspci" Command. I could not find anything to the compatibility with 7.0 online, but I hope that somebody here can help me figure this out. Is there any kind of Driver that I can install to detect the Device? We had to Upgrade to 7.0 because our evaluation License ran out on 6.7 and we could only get a free one for 7.0, so we either get the Hardware working with 7.0 or we have to Downgrade, Secure and switch our Hardware. Thanks in advance for the Help, its much appreciated!! Best regards, Andreas

↧
↧

VC Windows upgrade to 6.7 - DNS server on VC

June 9, 2020, 1:33 pm
$
0
0

Hi there,

I need some help to upgrade VC windows based on 6.5 to 6.7 U3. This has the DNS server on the same system , restricting the upgrade. During the upgrade, when VC needs to reboot, the DNS isn't available and fails the process.

How can I perform an upgrade in this case? Suggested was to point to an external VC with a DNS server, but it isn't possible in my case or too much work process. Also, the option is to build fresh VCSA and import all data and objects. However, this cannot be done now. Planes to migrate to VCSA are in the next upgrades to the latest version 7.x.

Any other option?

Your help will be much appreciated.

Cheers,

↧

Issue installing ESXi 6.5

June 11, 2020, 4:21 am
$
0
0

Hello,

 

I have an issue with the installation of ESXi 6.5 on a DELL PowerEdge R440 server on dual SD Card.

 

I've downloaded the DELL customized iso on this page => Support for PowerEdge R440 | Drivers & Downloads | Dell US

 

 

I've created an USB Bootable with this ISO, I can boot on it without issue then the installaiton of ESXi start.

 

When I strart the installation after choosing the dual SD Card, after 5% I have the error message below :

 

esx.jpg

 

For information, I don't know if there is any impact, but at the beggining I've made a mistake I've put the ISO file on one of the SD Card instead of USB Stick.

 

Thanks for your help.

↧

VCSA 6.5-6.7 upgrade: A vCenter Single Sign-On endpoint certificate validation error has occured.

June 11, 2020, 8:33 am
$
0
0

Hi all,

Sorry if this have been discussed before. I couldn't find anything about it and not much at all on the error message on the internet.

 

I'm upgrading a VCSA running 6.5 to 6.7 using the appliance installer, and the pre upgrade stops with this message:

 

Error: A vCenter Single Sign-On endpoint certificate validation error has occured.

Resolution: Ensure that the endpoint service registrations in vmdir match their corrsponding machine SSL certificates in VECS. For more information, see Knowledge Base article KB 2121701.

 

I recently refreshed the machine certificate that was about to expire, which also required me to accept the certificates on all connected applications such as Horizon View and Veeam-servers, but no other strange issues have been noticed.

 

The KB 2121701 didn't really seem to match our environment, but I followed the guide and ran the ls_update_certs.py script according to the instructions. It spat out several pages of output, mostly "INFO" but a few "WARN" which always was " com.vmware.vim.vmomi.client.http.impl.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase - Shutting down the connection monitor." and "com.vmware.vim.vmomi.client.http.impl.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase - Interrupted, no more connection pool cleanups will be performed."

 

Other things I've done is to unregister some old NetApp plugins that we don't use, and also followed the solution in Error when upgrading from VCSA 6.7 to 7.0

 

Nothing has helped though, and I'm still stuck at the validation stage.

 

Certificates always make my head spin, and I'd be grateful with some hints on what to check here. We really need to get the VCSA updated, since we've got other things that depend on us having 6.7.

 

Thanks

↧
↧

VUM upgrade fails - ramdisk (upgradescratch) is full

June 11, 2020, 8:31 am
$
0
0

Hi,

 

I am trying to push an ESXi 6.7 upgrade via VUM but keep getting this log (and fails) in vmkernel and the scratch partition is on a SAN datastore with plenty of free space

 

 

MemSchedAdmit: 471: Admission failure in path: upgradescratch/upgradescratch

MemSchedAdmit: 489: upgradescratch (289688) extraMin/extraFromParent: 1/1, upgradescratch (289687) childEmin/eMinLimit: 92160/92160

WARNING: VisorFSRam: 206: Cannot extend visorfs file /upgrade_scratch/QEDENTV.V00 because its ramdisk (upgradescratch) is full.

 

 

Any suggestions as to which disk/path it is referring to being full?

 

 

Thanks

↧

Is it necessary to upgrade the vDS to a newer version than 6.0.0 before upgrading to vSphere 7? (vCenter and ESXi hosts are running 6.7 U3)

June 12, 2020, 5:20 am
$
0
0

I am now managing a VMware environment that was upgraded from vSphere 6.0 to 6.7 several months ago.  vCenter and the ESXi hosts are now running version 6.7 U3.  The distributed switches were not upgraded however, so those are still on version 6.0.0.  I know that you can only upgrade directly to vSphere 7 if you are currently running vSphere 6.5 or 6.7.  Does this include the distributed switch version as well?

↧

VC 6.7 U3h to 7.0.0b?

June 12, 2020, 1:54 pm
$
0
0

Will there be a VC 7.0.0b release soon? We have scheduled our vCenter 7 upgrade scheduled for June 17th, but we took the 6.7 U3h upgrade to secure our vCenters from an issue that our security team alerted us to. However, according to KB 67077 says that we cannot upgrade from 6.7 U3h to 7.0.0a due to code regression. We would really rather not have to roll back to 6.7 U3f to do the upgrade.

 

Alternatively, is there a way to force the upgrade and acknowledge that we will be going to a version of VC that does not have the security fixes contained in 6.7 U3h?

↧
Search

VMware vSphere 6.5 Install On HPE DL 380 Gen9 install Error：processlookuperror errno 3 no such process

June 13, 2020, 1:49 am
$
0
0

VMware vSphere 6.5 Install On HPE DL 380 Gen9 install Error：processlookuperror errno 3 no such process

 

ISO Image:VMware-ESXi-6.5.0-Update3-15256549-HPE-Gen9plus-650.U3.10.5.5.16-Mar2020.iso

Server:HPE DL380 Gen9 ，Update SPP 2019.12

 

WeChat Image_20200613164246.png

↧
↧

vCenter 7.0 migration questions

June 14, 2020, 12:14 pm
$
0
0

Hi,

 

We have 3 x 6.5u3 vCenters all joined to the same external PSC. Looking to move up to 7.0, converge to an embedded PSC and rename vCenters.

2 vCenters (HQ and DR) can be down during the upgrade, however taking our VDI vCenter could preset a challenge as with it being down new VMs can't be provisioned.

 

Given our setup, should we bother going through the migration or just stand up the new vcenters? I realize that starting from scratch would require recreating all scheduled jobs in vcenter, re-configuring vcenter access for users and touching many 3rd party apps (monitoring / backup) that connect to vCenter. I also realize that renaming vcenters would require going through all 3rd party apps to point them to the new vcenter names.

 

If we go the convergence  / migration path. Should we start with VDI vcenter or leave it for the last?

 

One of the road blocks I already see is we can't rename until we get away from the external PSC.

 

Thanks

↧

Migrate vcenter 5.5 for windows to vcsa 6.5.

June 15, 2020, 4:41 am
$
0
0

When you migrate to a vcsa 6.5 to a new esxi host can you migrate it to an esxi 5.5 host like you have your entire vmware farm or can you migrate to a 6.5 esxi host ?. In theory virtual center 5.5 you can only see or add esxi 5.5 host and not 6.5. I guess the most logical thing is to migrate to an esxi 5.5 host and then update it.

↧

VCSA 6.7 to 7 upgrade fails

June 15, 2020, 8:14 am
$
0
0

Trying to upgrade from a VCSA 6.7 to 7.0.  I was able to deploy the new appliance via step 1.

At step 2 (Upgrade) I'm getting the following error:

 

"Certificate validation failed during pre-upgrade check"

 

I checked the KB VMware Knowledge Base but confused on where I'm supposed to run the commands listed here.

As far as I can tell though, my self-signed cert on the existing 6.7 appliance is still valid.

 

Is there a way to get around/fix this certificate error?

↧

Upgrade PSC fails with vapi.endpoint errors

June 15, 2020, 9:10 am
$
0
0

I'm working on an environment with two Windows PSC's behind a NetScaler load balancer and one Windows vCenter running on a two-node Windows Failover Cluster. Everything is version 6 with an extended support contract :-) At the moment the load balancer only has one PSC active and the other one disabled so we can work on it without disturbing business.

 

I started with the first PSC but whatever I do, the migration to a 6.7 appliance fails with an error related to vapi.endpoint.

 

Is there someone with expertise on how to perform this migration?

 

BTW I also submitted an SR with GSS.

↧
↧

VC 6.7 U3h Upgrade to 7.0a Failure

June 16, 2020, 9:25 am
$
0
0

Hello,

 

I have a vCenter appliance I'm upgrading, I go through the process, everything works fine until after importing the data from the source vCenter instance.  So, stage 1 goes fine, stage 2 goes fine until after the original vCenter is shut down.  The original vCenter is shutting down before it continues past that.  I then get this error.

 

 

Error setting network. Details : 15/06/2020 16:51:38 [ERROR] Cannot run /sbin/ifup eth0 command. Unknown error. Return code : 256 output: Make sure the interface is down or not assigned any IP eth0 is DOWN or not assigned an IP. Bringnig eth0 up... Can not find the manual filename, let us search for the auto filename Performing duplicate address check for IPv4 address 10.193.252.229  [1;31mError: IP already exists in the network [0;39m Unable to set the network parameters

Failed to set network

 

The IP is the source vCenter appliance.  It is shut down while the wizard still says it's shutting down the source.  I'm not sure what's happening.

↧

New VCSA 6.7 with existing Windows vCenter Server 6.5

June 16, 2020, 11:50 pm
$
0
0

Hi,

I'm looking to start using VCSA 6.7 but we have an existing Windows vCenter Server 6.5. I understand that there is no supported migration path for this which is OK as I'd like to build VCSA 6.7 as a "fresh start".

 

I have 4 * ESXi, 6.5.0, 15256549 hosts in a cluster and was planning to disconnect one host. Install ESXi 6.7 U3 on it and the setp VCSA 6.7 as a guest and get things going. Then the plan was to migrate some non-production guest to it and test and then over time do the same to all the other hosts.

 

Is a plausible and supported way of moving forward?

 

regards.

↧
Search

Angry Frustrated Down $$$

June 20, 2020, 1:28 am
$
0
0

I don't feel that way.

 

If had a tier 3 man wasting hours trying to resolve PSOD on change systems I'd be (removed by moderator)

 

If I spent $15k on a storage solution whether that be nas, sas, iscsi or (removed by moderator) usb you should support it!

 

Keep telling us all what we can't do or you won't.

 

I have never met a single engineer that doesn't both love and hate you at the same time... that was easy when you we're the only game in town....that is not the case any more so get your resume together.

 

We all cannot wait for someone to come along and kick your (removed by moderator). When they do you will fall so hard.

 

So Yahoo

 

Another PSOD

 

Thanks for making me work so damn hard for so little.

 

Your programmers suck.

 

I love you, I hate you.

 

Sean

↧

I'm try to upgrade my vCSA from 6.0 to 6.5, using the GUI , however it fails with the error "A problem occurred while getting data from the source vCenter Server."

December 6, 2017, 10:30 pm
$
0
0

I'm getting the errors as attached.

 

VMware VCenter Error.jpg

↧
↧

upgrading vcenter 6.5u2 to 6.7u3 on VXrail 4.5.300-11239489

June 21, 2020, 11:25 pm
$
0
0

Hi All,

 

I'm looking for help for upgrading the vCenter 6.5u2 to 6.7u3 on VxRail. Our vcenter is external vcenter.

 

Any help will be much appreciated.

 

VxRail 4.5.300-11239489

 

Thanks

V

↧

Going From vSphere 5.1 to 6.7 (Maybe 7)

June 22, 2020, 10:15 am
$
0
0

Wow, seems like forever since I have had a need to be here.

 

I have a vSphere 5.1 Enterprise + vCenter Server Standard (running on Windows 2012) environment that is, obviously, out of support.  The required DBs are also out of support on a 2005 SQL Server.  We have recently acquired some active licenses from another department in my organization that is currently using vSphere 6.0 but are retiring that environment and I have confirmed with our VMware reps that me and my department can take possession of that other department's licensing and us those to upgrade our vSphere 5.1 to to 6.7 or maybe even 7.  Going to 7 will depending on our backup vendor and if we want to go to a non-LTS version of their product (allowing us to go to 7) or still with the LTS we are running today meaning we can only go to 6.7U3.

 

Anyway, I have confirmed all of our hardware, host servers, HBAs, 10GB NICs, Storage etc are all on the HCL for both 6.7 & 7. 

 

Further I am not interested in historical data or doing multiple upgrades to get from 5.1 to 6.7 or 7.  So I will be building a brand new vSphere platform from the ground up.

 

Our current setup is mostly older VMs (Windows Server 200x) and running on 2 "Very Beefy" HP Proliant DL380 Gen 9 servers.  We have the capacity to run all VMs on just 1 host.

 

My plan is to put a host into MM and then remove it from the existing cluster.  Wipe it out and install ESXi 6.7 or 7 and install a new vCenter on Windows on that host. Once done and that new host is able to see all of our storage, I will removed all the VMs from inventory on the 5.1 host and add all the VMs to inventory on the new host/vCenter.  Then I will install from scratch 6.7 or 7 on that other host and add it to the new Cluster.  Then I will update all VM Hardware / Tools etc, setup HA, DRS again etc and apply the licensing that I am inheriting from the other department.

 

Does the plan make sense?  Any caveats or pitfalls to watch for?

↧

after upgrade ESXI from 5.1.0 to 6.0.0 1 host out of 3 switches to evaluation mode after I enter the licence key

June 23, 2020, 4:43 am
$
0
0

Hi,

as per title after upgrading ESXI from 5.1.0 to 6.0.0 on 3 hosts I entered the VMware vSphere 6 Essentials licence key but one host keeps switching to evaluation mode which expires this week.

I checked and the licence key is for 3 hosts (Max 2 processors per host) and the problematic host has 2, the others 2 hosts have 3 total.

So what could cause this issue?

Thanks

↧
Viewing all 3263 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>