7 Posts

June 13th, 2012 06:00

Have just ran Troubleshooting and WS-Man is showing Ok. But the ESXi servers are still not showing properly.

Also tried disabling SNMP discovery from the range, as soon as SNMP was unticked the ESX servers moved from

"VMware ESX Servers" to "Unknown" container.

3 Apprentice

 • 

2.8K Posts

June 13th, 2012 08:00

Hi vMaster1,

Can you tell me a bit about how you filled in the discovery wizard page that is used for the wsman protocol? (secure mode, etc.)

thanks,

Rob

7 Posts

June 13th, 2012 08:00

Hi Rob,

Here you go:

3 Apprentice

 • 

2.8K Posts

June 13th, 2012 08:00

Can you try to bump the timeout value to 10 and see if that helps?

Rob

7 Posts

June 13th, 2012 08:00

Thanks Rob, that did the trick.

I understand it is because of the OMSA response time. Any way to improve this?

The hardware log is not showing: Could not connect to device to obtain logs" is it an expected behaviour?

7 Posts

June 13th, 2012 09:00

Thanks Rob,

Sorry, just to clarify: No hardware log is available for ESXi servers at the moment at they use WS-MAN and not SNMP, is that correct?

If yes, any ETA on the SNMP support for ESXi?

Thanks,

3 Apprentice

 • 

2.8K Posts

June 13th, 2012 09:00

No way to improve it at the moment....workin' on it though on our side :)

Pretty sure we just get h/w logs via SNMP in  1.0.1.  If you have any servers discovered via SNMP, you might do a sanity check to see that you are seeing these logs.

thx

Rob

Community Manager

 • 

711 Posts

June 14th, 2012 21:00

Hi,

It is difficult to specify the exact release date. As Rob mentioned in his post, we are looking at supporting hardware logs from ESXi for the next release. Currently it is planned for Q3/Q4 this year.

Regards

Abhijit

No Events found!

Top