Hi Mikhail,
So, did you find a way for us to do the Webex? In your last reply, you said there were some security issues with that in your company, but they can be overcome. Please let us know when you are ready to have the Webex session, so one of our team's folks will analyse your issue. In the meantime, as we help other people with their similar issues, we'll let this forum know about any common problems and workarounds.
One common problem we have encountered is with HAL daemon running (unnecessarily) inside the VM. This causes /etc/fstab to be automatically modified by HAL, depending on what external automounts, such as CD/DVD drives, are exposed by the ESXi. The issue could also affect VM Server platform.
There is now a build of UCSPE 1.3 that fixes this issue, and we have been distributing it to folks who reported it. We will post this build in the downloads section on this website in a few days.
Serge
Serge, hello,
Sorry for long delay but at last I have some results I can share with you and other forum members.
Due to some connectivity and security difficulties I could not provide you Webex connection to UCSPE running under ESXi as you asked me to do, BUT I found a workaround for the issue and hope this can help to understand the real reason of this problem.
First of all I run the UCSPE using VMPlayer as you suggested and had no problem with it.
So I tried to find differences for UCSPE running on VMPlayer and on ESXi and noticed an interesting thing in addressing.
If I start USCPE using VMPlayer it gets some kind of ip address by default (some 192.168.x.y, the same as Vmnet8 interface has) and I can easily access Cisco UCS Manager.
If I start USCPE on ESXi it shows it failed to assign any IP address. Of cause later I assign IP address manually, and I can access Cisco UCS Manager WEB interface but have this ¿timeout error¿ during login. Rebooting this UCSPE does not help, previously entered IP address remains but there is still this ¿timeout error¿.
But ones when I tried a ¿Factory Reset¿ (option ¿i¿) previously entered IP address remained but this ¿timeout error¿ disappeared. To be sure it works I repeated this workaround twice I it helped for me.
So there is a workaround for this ¿timeout error¿ problem and probably it gives you a clue for understanding a situation. Please share your opinion.
Thank you,
Mikhail