topic Re: Cisco ISE VM move (VMWare Host to Hyper Host) in Network Access Control

Cisco ISE VM move (VMWare Host to Hyper Host)

hainhtetaung — Tue, 15 Jun 2021 07:50:13 GMT

Dear community,

What will be best recommended approach. Will it be effect to the ISE Date Base.

Thank you

Re: Cisco ISE VM move (VMWare Host to Hyper Host)

Mark Elsen — Tue, 15 Jun 2021 09:30:50 GMT

- I don't think you can do that direct, you will have to backup the database, create the VM(s) and initial installation of ISE on hyper v and do a backup-restore. Netapp apparently has a tool : https://library.netapp.com/ecmdocs/ECMLP2413759/html/GUID-DE92ABAB-0DD2-4CB2-9425-A4763E1F2140.html , would not recommend this though even if you have netapp, probably not supported by Cisco neither.

Re: Cisco ISE VM move (VMWare Host to Hyper Host)

symplico3 — Tue, 15 Jun 2021 09:48:38 GMT

when we use for our website this is perfect for us.

Re: Cisco ISE VM move (VMWare Host to Hyper Host)

Marcelo Morais — Tue, 15 Jun 2021 12:27:33 GMT

Hi @hainhtetaung ,

the best approach would be a Backup&Restore after a new installation, please take a look at: Create a Cisco ISE VM on Hyper-V.

Note: take a look at Convert a VMware VM to Hyper-V. and CSCvr16054 Moving ISE to a different Hyper-V Host. before testing on a lab environment.

Hope this helps !!!

Re: Cisco ISE VM move (VMWare Host to Hyper Host)

Damien Miller — Wed, 16 Jun 2021 06:51:30 GMT

I would suggest that the best approach would be to do this one node at a time. Build a new node and join it to the deployment, do this for each node. This would require no backup/restore, and the ability to easily reuse names/address.

Re: Cisco ISE VM move (VMWare Host to Hyper Host)

thomas — Sun, 27 Jun 2021 23:44:21 GMT

Please read the ISE Installation Guide where the topic is documented:

VMware Virtual Machine Requirements

Cisco ISE supports the following VMware servers and clients:

VMware Version 8 (default) for ESXi 5.x (5.1 U2 minimum)
VMware version 11 (default) for ESXi 6.x
VMware Version 13 (default) for ESXi 7.x

Cisco ISE supports the cold VMware vMotion feature that allows you to migrate virtual machine (VM) instances (running any persona) between hosts. For the VMware vMotion feature to be functional, the following condition must be met:

Cisco ISE must be shutdown and powered off: Cisco ISE does not allow to stop or pause the database operations during vMotion. This might lead to data corruption issues. Hence, ensure that Cisco ISE is not running and active during the migration.

Note

Cisco ISE VM does not support Hot vMotion.

Refer to your VMware documentation for more information on VMotion requirements.

Caution

If the Snapshot feature is enabled on the VM, it might corrupt the VM configuration. If this issue occurs, you might have to reimage the VM and disable VM snapshot.

Note

Cisco ISE does not support VMware snapshots for backing up ISE data because a VMware snapshot saves the status of a VM at a given point in time. In a multi-node Cisco ISE deployment, data in all the nodes are continuously synchronized with current database information. Restoring a snapshot might cause database replication and synchronization issues. We recommend that you use the backup functionality included in Cisco ISE for archival and restoration of data. Using VMware snapshots to back up ISE data results in stopping Cisco ISE services. A reboot is required to bring up the ISE node.