Tag Archives: Migration

VMware LifeCycle Manager – Migration error “SSH is not enabled or invalid” – LCMMIGRATION15102

During my migration from vRSLCM 2.1 patch 2 to the latest version 8 release, I encountered the following error;

Error Code: LCMMIGRATION15102

vRSLCM Migration Failed with SSH is not enabled or Root credential invalid. Please make sure SSH is enabled or porvide the correct root credential by adding the credential to the home page locker app

Pretty obvious error, however the provided root credentials were correct, and I could use putty to connect to my existing LCM instance.

The fix

I spoke with an internal VMware employee about this, the suggestion was to just create the same authentication details again in the locker and chose them on the retry. However I decided to just go ahead and reset the SSH user on my old environment as a precaution as well.

1. Old LCM Instance > Go to Settings > System Administration

Scroll down find the section to reset the “root” user as below, enter the new password and confirm, then select save.

I would recommend you test connecting to the old LCM instance using ssh and the new creds at this stage.

2. New LCM instance, go to the locker app, and then click for passwords, you will see just icons on the left hand side but you can click the >> to expand the navigation pane.

3. Add your new credentials and save

4. Go back to Requests, find your failed task under “invokemigration” and select to retry.

You will be given an option to select which credentials you want to retry with, select your new credentials object and hit submit!

(This type of feature where you can respecify the variables on a retry is something I’ve asked for a lot!).

5. And fingers crossed you will then see the request complete successfully.

Regards

Dean

VMware vRealize LifeCycle Manager 8 – Migration Process Screenshots

VMware vRealize LifeCycle Manager 8 released earlier this week, 17th October 2019.

Note the official name and abbreviation, its a long one!

  • vRSLCM (vRealize Suite LifeCycle Manager)

You can find the supporting official documentation here;

What's New Blog Link:
What's New Blog Post

Download Link:
Product Download

Release Notes:
Release Notes

Documentation Link:
Resources
Migration Process

The best news about this release is the “easy installer“, which also allows you to migrate from older versions. In this post, I’ve documented the screenshots in steps for you, as I know many of you out there like to see the end to end process before you undergo an update yourself, so you know what to expect.

During this migration process the following will happen;

  1. New LCM virtual appliance deployed
  2. New IDM appliance deployed (unless you select to link to an existing environment)
  3. Existing LCM settings and content will be migrated
Migration Process Screenshots

1. Load up the Easy Installer UI and select the Migrate option

Procedure
1. After you download the file, mount the vra-lcm-installer.iso file.
2. Browse to the folder vrlcm-ui-installer inside the CD-ROM.
3. The folder contains three sub-folder for three operating systems. Based on your operating system, browse to the corresponding operating system folder inside vrlcm-ui-installer folder.
4. Run the executable as per the correct steps for your OS.

2. You’ll get the below introduction page explaining the Migrate option, and some pre-req info.

3. As with every software, there is a EULA to accept.

4. Select the target vCenter environment where you want the LifeCycle Manager and Identity Manager (if needed) appliances to be deployed.

You will be asked to confirm the connection SSL Thumbprint for the vCenter provided.

5. Select the Datacenter or VM folder within your target vCenter that you want to deploy the Virtual Appliances.

6. Select the compute resource within your target vCenter to deploy the Virtual Appliances

7.  Select the storage location for your virtual appliances, at this stage I am unaware if you are able to select different datastores for each Virtual Appliance.

7. Provide details for the Network configuration for the new virtual appliances. For the easy installer it is assumed you will be deploying both to the same network subnet range.

8. Provide the default passwords for both virtual appliances, this password will be used for the following accounts;

  • vRealize LifeCycle Manager
    • Root Password
    • Admin Password
  • VMware Identity Manager
    • Root Password
    • Admin Password
    • sshuser password
    • Default Configuration User Password (You will configure the name of this account later)

9. Configuration of the LifeCycle Appliance deployment

  • Name of VM in vCenter
  • IP address
  • Hostname  (FDQN as in DNS)

10. Next you will provide the details of the existing LifeCycle Manager you are migrating from. The wizard does not seem to do any prechecks of the information provided, like it does when you connect to vCenter at the start.

11.Configuration of the VMware Identity Manager appliance

  • Install a New Identity Manager
    • Name of VM in vCenter
    • IP address
    • Hostname  (FDQN as in DNS)
    • Default Configuration Admin (Provide a name that is not root or admin)
  • Import Existing VMware Identity Manager
    • No configuration necessary, it will be pulled across from the existing LCM environment.

12. The usual Summary page of all the options you have selected/configured.

13. Finally as the process runs, you will get a progress bar with the various stages. And then once complete, a link to the new vRSLCM (vRealize Suite LifeCycle Manager) UI and the request that’s created to migrate the data from the old vRSLCM environment.

So this concludes the post!

Regards

Dean

Upgrading VMware vSphere 5.5 to vSphere 6.5 (VMUG Presentation)

Blog post born from a VMUG Presentation

Mid Feb, one of the London VMUG leaders posted on twitter, looking for someone to present on the subject of “upgrading from vSphere 5.5 to vSphere 6.5”.

So I jumped at the chance, kind of, and offered to present. This blog post covers the content from that presentation.

  • vSphere 5.5 – End of Support
  • vSphere 6.5 – New features
  • OK, so let’s just upgrade then?
  • The plugin’s
  • SSO is gone!
  • Understand your topologies
  • Pre-Upgrade Tasks
  • The Upgrade, the big event
  • Gotcha’s
  • VSAN Considerations
  • vShield Manager is no more! Upgrade to NSX Manager
  • Resources

The presentation is available to download here – http://vexpert.me/London-vmug-dean (case sensitive link)

Or I’ve figured out how to embed it from Slideshare.net below (But animations don’t seem to work);

vSphere 5.5 – End of Support
  • End of General Support for vSphere 5.5 is September 19, 2018
    • Includes vCenter 5.5, ESXi 5.5, VSAN 5.5
    • KB 51491
  • In the event you are unable to upgrade before the End of General Support (EOGS) and are active on Support and Subscription, you have the option to purchase extended support in one year increments for up to two years beyond the EOGS date.
    • Expect this to be more costly than general support.
    • SLA’s are more akin to that of basic support rather than production support
    • Annual security patch. Includes catastrophic/critical security fixes only
    • Ability to create hot patches for Severity 1 issues only
  • Technical Guidance for vSphere 5.5 is available until September 19, 2020 primarily through the self-help portal.
  • During the Technical Guidance phase, VMware does not offer new hardware support, server/client/guest OS updates, new security patches or bug fixes unless otherwise noted.
    • For example, there was no SPECTRE/Meltdown security patches released for vSphere 5.1

It’s not only the core vSphere 5.5 products that are affected, as we can see from the End-of-Support tracking page provided by virten.net. There are other VMware solutions that you have deployed that may also need upgrading.

Continue reading Upgrading VMware vSphere 5.5 to vSphere 6.5 (VMUG Presentation)