This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC!
We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.
Hi All,
The install guide highly recommends dedicated VM resources and not to share or oversubscribe resources,
Is this enforced through the OVA or via any other means?
If ISE is run in an oversubscribed manner do we require the customer to vacate other guest on the Esx host if facing issues while trouble shooting through TAC?
Many thanks
Alistair
Solved! Go to Solution.
VMware resource sharing is NOT supported. VMware resource sharing is one of the best ways to guarantee mysterious and intermittent problems with ISE nodes. VMware configuration should be one of the first things a TAC Engineer checks for with certain symptoms because it is so insidious.
The ISE OVAs are explicitly named for their equivalent appliance model and hardware requirements:
ISE-2.1.0.474-virtual-SNS3415.ova
ISE-2.1.0.474-virtual-SNS3495.ova
While the ISE OVAs do enforce the hardware requirements for CPU, RAM and Disk, they have no way of knowing if the resourcing is dedicated or shared within VMware.
VMware resource sharing is NOT supported. VMware resource sharing is one of the best ways to guarantee mysterious and intermittent problems with ISE nodes. VMware configuration should be one of the first things a TAC Engineer checks for with certain symptoms because it is so insidious.
The ISE OVAs are explicitly named for their equivalent appliance model and hardware requirements:
ISE-2.1.0.474-virtual-SNS3415.ova
ISE-2.1.0.474-virtual-SNS3495.ova
While the ISE OVAs do enforce the hardware requirements for CPU, RAM and Disk, they have no way of knowing if the resourcing is dedicated or shared within VMware.