cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
150
Views
0
Helpful
1
Replies

Migrating Old iPSK Manager to a New Ubuntu SOE VM & Fresh iPSK Manager

brdly
Level 1
Level 1

Hi all — looking for advice and best-practice steps to migrate an older Cisco iPSK Manager deployment onto a fresh, managed Ubuntu VM while preserving existing endpoint/PSK data.

Current Setup

  • Ubuntu 18.04 LTS (standalone; not joined to AD; limited monitoring/AV)
  • iPSK Manager (circa 2021)
  • 3,000+ endpoints defined in iPSK
  • ISE 3.2 Patch 7 using iPSK as an ODBC identity source (ISE upgrade to 3.4 planned)

Objective

Rebuild on a new Ubuntu SOE VM managed by our infrastructure team, install the latest iPSK Manager, and migrate existing iPSK data.

Absolute minimum is the ability to migrate all the endpoint data to the new instance. I am happy to manually rebuild all the portals, groups, SSL certificates manually. 

Why a Fresh Build

  • Move to a supported SOE with proper monitoring and patching
  • Modernize iPSK Manager and dependencies
  • Reduce technical debt from the legacy one-off server

What I’m Unsure About

  • Best-practice method to migrate iPSK data (endpoints/PSKs, groups/portals) to the new instance. Or if it's even possible. 
    • Should I snapshot the existing VM and attempt a yolo upgrade of the existing iPSK Manager instance then move the data across? 
    • Or dump the data from the iPSK manager on its current version, move it across, then upgrade it using the new instance. 

Proposed High-Level Approach

  1. Provision new Ubuntu LTS SOE VM with all of iPSK's requirements. 
  2. Install the latest iPSK Manager.
  3. Migrate the existing iPSK database to preserve endpoint/PSK data.
  4. Recreate configuration (vhosts/TLS/portals) as needed on the new host.
  5. Test thoroughly, then cut over via DNS with a clear rollback plan.

Advice, lessons learned, or validated steps from anyone who has done this would be greatly appreciated.

P.S

We have a lab that I've run VMs up on and have a copies of the existing production VM and its data. I've been attempting to do the migration, but I've broken it a few times now. So reaching out for any advice. Also! I am able to test any suggestions before trying for real. 

P.P.S

If you have a super obvious and simple suggestion, don't hesitate to let me know. I might not have thought of it or not know about it. 

1 Reply 1

richardcoleofficiall
Community Member

Safest path — export and migrate the iPSK Manager MySQL database rather than the full app. Spin up your new Ubuntu SOE VM, install the same iPSK version as production, then restore the existing DB dump and verify schema alignment. Once confirmed, upgrade iPSK Manager in place to the latest build. This preserves all endpoint/PSK data while avoiding version-jump corruption. Snapshot before upgrade and cut over via DNS once validated.