Yes, you can deploy that OVA on any supported hypervisor and server, but OVA allocations still based on 35x5 series. The OVAs are all based on the hardware appliances, so that is the relationship to the 3595. To determine which platform ISE has matched to the VM, you need to find platform property in ‘she tech support’ or under the ISE reports for counters (Under Diagnostics reports).
With OVAs, Customer should not need to know details of how To set reservations or other custom settings.Īs noted, there is a difference between platform detection for sizing services within ISE and the license detect and validation logic. Yes, you have complete control with iso install, but there is always a trade off with simplicity.
Working with Product Management team to get this resolved. The previous 3595 is now shifted down to become the new Medium appliance and the 3515-based VM remains a Small. ISE 2.4 introduces a new Large VM appliance option which is essentially a 3595 VM with 256GB RAM. Please note that a the original large appliance (3595) has been relabeled as a Medium appliance.
Large VM license is currently set to trigger if it detects > 8 CPUs. So it is correct that your 35x5 should be configured to allocate 12 or 16 hyper-threaded CPUs, but the license should not be triggering. That is why the OVAs have been updated for ISE 2.4 but all OVAs for prior releases require update:ĬSCvh71644 - VMware OVA templates for SNS-35xx are not detected correctly With all 35x5 appliances and their VM equivalents, hyperthreading is assumed enabled on the platform such that 6 or 8 physical cores will be presented as 12 or 16 logical processors to the guest VM. The intent is that only appliances configured to match a specific hardware appliance specs should trigger alarm if license is less than platform size detected. This is a recently discovered issue and believe the logic for license requires update.