Problems with installation of ISE 3.x on 2019 Hyper-V

[james.king14]

Having issue with installing ISE 3.x on 2019 Hyper-V server.  I get an error that the processor is not large enough.  Even though I have twice the size required.

[ahollifield]

What version of ISE?  3.0?  3.1? 3.2? Also the installer is reporting the speed of the processor is too slow.  What speed in ghz is your CPU in your host?

[james.king14]

The version is 3.1.x and the processor is at 3.2GHZ but it is a windows 2022 box.  I just found that out today.  we had a 2019 but the sysadmin upgraded.  

[ahollifield]

https://www.cisco.com/c/en/us/td/docs/security/ise/3-1/compatibility_doc/b_ise_sdt_31.html

Lists Microsoft Hyper-V on Microsoft Windows Server 2012 R2 and later.  If your CPU/memory reservations are up to spec, I would say TAC would be your next step.

[james.king14]

I have the document on the specs for the Hyper-V installation.  I also have verified that Hyper-V will work on most Windows systems.  I am trying to open a TAC case, but I cannot get into the ISE CLI, since it will not load.

[ahollifield]

Is this a Gen2 Hyper-V VM?  There is a known issue on 3.1 with Gen2 VMs.  Cisco TAC has a hot patch or you can redeploy on a Gen1 VM.

[ajc]

Hi everyone, having the same issue. Deploying ISE 3.3 from scratch using ISO / Hyper-V VM. Generation 1 VM's and getting similar error. Our host has enough Memory 512 GB, CPU 2.0 GHZ, disk (over 5 TB) for those Hyper-V VM's.

[DAVIES604]

Hi ajc. I know this was from some time ago but did you ever find a solution? I am seeing the exact same issue as in your screenshot trying to build 3.3 on Hyper-V. Thanks

UPDATE: I managed to get around this issue by enabling CPU compatibility mode, however don't have the issue on another Hyper-V node, same hardware, so still interested if you found another solution.

[ajc]

Hi Davies, I forgot to post my solution. For bigger Hyper-V VM's, I used Generation 2 and problem solved. I read somewhere that they are also recommending install from PATCH 1 on ISE 3.3 or 3.2 instead of going directly to the latest patch on that version due to some identified issue I do not recall. So basically I am installing to be safe patch 1 and patch 2 on version 3.3.

Also I did not install any hot patch because I do not like it and I had really bad experience with that kind of approach back in the days when running ISE 2.2

[BruceLevenbergGlobal]

I also got this to work for 3.3 ISE-PIC by enabling compatibility mode. 
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/dynamic-processor-compatibility-mode?tabs=hyper-v-manager
I was running into CSCwm59777 with our internal domain, so had to install 3.3 instead. Xeon gold 2.2 Ghz HyperV host reporting under 1 Ghz in the installer for 3.3. 

VM settings:
Gen 2
32 GB RAM 
16 vCPU
60 GB HDD
1 NIC, set appropriate VLAN ID. 
Disabled secure boot
also disabled snapshots
 

[james.king14 · Accepted solution]

How can you tell which is which?  Thanks you have been very helpful.