Works fine now. 6 ESXi 5.x servers installed with OME agent.

Shows up as ESX in inventory.

The Timeout seems to be the one that fixed it. (set to 10 sec now)

Thanks Again. FAQ document is updated with this information.

I did.

I use Timeout 10 and Retries 4.
Takes abit longer to do the test but works everytime for me.

In my environment this works too. Thnks all of you.

I seem to be having this same problem and adjusting the timeout value in OME resolved the issue there.  However, ever since updating our ESXi hosts to 5.0 Update 1 and the OMSA 7.0.0 VIB now I can no longer get the OMSA web server to connect to my ESXi hosts... I just get a page cannot be displayed error whether I use IE9 or FireFox 10.  Since prior to the Update 1 release OME worked just fine with a 5 second timeout I'm guessing that something needs to be adjusted in the OMSA web server as well but I can't find any option for this.  Any ideas?

You might be able to get better responses to OMSA questions by posting on the Systems Management Forum.

en.community.dell.com/.../default.aspx

Addilapi, did you get the IE9 to work? if not, try this:  In IE 9, press F12 to bring up debug bar, Click on 'Cache' menu and place a check on  'Always refresh from server'.

question, was open omsa webserver working with IE9 before update 1?

Yes, OMSA web server was able to access our ESXi 5.0 GA hosts running VIB 6.5 and 7.0 just fine until we upgraded to ESX 5.0 Update 1.  I've tried using OMSA web server installed on several systems and from several systems to rule out an installation problem.

I tried the suggestion for F12 / debugging and it had no impact.

Hello,

i also have the same issue. Server unter ESXi apears with unclassified. What a sence makes this OME Tool if it doesn't work`?

Thx Daniel

Ha! Thanks for the post Daniel.

Yes, it works :-)

Can you confirm you've followed the steps in this whitepaper?  ESXi does indeed require a bit more setup than something like SNMP.

Thanks and let me know how it goes.

Rob

wp:

en.community.dell.com/.../20071085.aspx

Sorry, but I think I have done exactly what's described in this whitepaper and it doesn't work. Any ideas what to do?

Thx Daniel

Hi Daniel,

Not sure if you have tried increasing the timeout value to 10 in the WS-MAN page of the discovery wizard. We have seen that responses for WS-MAN commands for ESXi 5 take longer than those for ESXi 4. You can also try running the Troubleshooting tool and run the WS-MAN test. That will validate credentials and connectivity.

Regards

Abhijit

Daniel,

Do you have 'secure mode' checked or unchecked in the disc wizard?

Are there any error messages in the OME application log?  Not sure there _would_ be in this case, but thought we can check.

Thx

Rob

.. no way. Doesn't work and the Test-Tool für WS-Man stats everything is ok. What else can be done?

Thx Daniel