11-22-2024 03:17 AM - edited 11-25-2024 12:22 AM
Hello! I got an issue in term of Cisco ISE 3.3 deployment. The ver. is Cisco-ISE-3.3.0.430.SPA.x86_64.iso We have a public cloud vendor worked on OpenStack\KVM environment. We couldn't install the standard ISE from a full .iso image because the old issue:
Unsupported HW, can't find UDI etc
The cloud's vendor said that they won't change their configs due to our personal problems. In my oppinion it shouldn't look like this as an expensive NAC sollution , but it's my first installation on OpenStack (before I did only on ESXi or AWS and eveything was fine from a box.). Has anyone had the same experience and solution? They also suggested to install it first on some home lab on KVM and then - just copy the disk image. But wtf? Also we have a support contract, but can't raise a TAC ticket because we don't have any UID...perfect. If anyone knows how to fix it - would be great, because we stuck even on the first step.
11-25-2024 04:43 PM
I haven't had the pleasure of using OpenStack - have you tried hacking the smbios parameter to "KVM" ?
11-25-2024 11:45 PM
the OpenStack is painful 100%. Cloud's vendor suggested to apply this CLI command
openstack image set --property hw_machine_type="q35" <image name>
and sad that it's all that they can do, because all other parameters are common for all clients and I have to solve all my issues by myself. After applying the command the ISE installer got 1 step forward but anyway got the screen with the same errors
"unsupported hardware, can't get UDI" etc.
I have ho idea why costomers have to dig in this, the probles has been there since 2.x ver and they can't fix it, or don't want.
Now we are downloading the 12gig ISE .iso back, will try to deploy it in a lab and then upload the disk image back and try again. Perfect.
12-02-2024 05:01 AM
reporting: deployed the image in a proxmox lab , copied the disk image with the state where we could get the web and UDI, tried to run it in the openstack cloud and...nothing , the UDI is empty again. The cloud's vendor told that their common parameters are
<sysinfo type='smbios'>
<system>
<entry name='manufacturer'>Servercore</entry>
<entry name='product'>OpenStack Nova</entry>
<entry name='family'>Virtual Machine</entry>
</system>
</sysinfo>
and they won't change anything due to our single VM but will clarify it with developers. Sad situation, Cisco TAC can't help because we can't get the S\N and cloud support just doesn't want. I will wait for couple of days and will move to onpremise, don't see any options.
12-11-2024 11:25 AM - edited 12-11-2024 11:28 AM
The result is : the vendor agreed with helping and changing the config file once manualy for the VM and took a wish request for the next year. Works yet. Great solution for 2024. Thanks for myself
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide