52 Posts

November 29th, 2011 11:00

Oops, I meant WS-MAN, not CIM of course.

52 Posts

November 29th, 2011 11:00

NOTE: For ESXi 5.0, OMSA VIB 6.5 A02 or greater is required.

Okay, you had to know this was coming... when can we expect availability of A02?  Is there any chance OME will work with the A01 that we've already managed to install on ESXi 5.0?

AAlso, can you detail the exact CIM discovery settings (port, options) that we need to use when creating a discovery range?

3 Apprentice

 • 

2.8K Posts

November 29th, 2011 12:00

eh, yeah....sorry 'bout that.  I guess A02 will be out in December (I think).  A01 will work with ESXi 4 ok, but not 5 (as far as OME is concerned).  OME + ESXi 5 needs the A02 fixes.

3 Apprentice

 • 

2.8K Posts

November 29th, 2011 12:00

Oops, I meant WS-MAN, not CIM of course.

Yep, so the 1.0.1 release is targeted for Q1/2012.  We are planning to support upgrades from 1.0 to 1.0.1.

Does that answer that part of the question?  Not sure if I understood the ESXi 5 part totally.

For WS-Man, the Help button on the WS-Man page of the wizard will help give a bit of detail

on the fields.  But for us in our lab, we will use the following:

-enable WSMan -- checked

-user id -- myuserid

- password -- mypw

-- timeout -- 2

-- retries -- 4

-- port -- 443

-- Secure mode -- checked

-- Trusted site -- checked

disclaimer -- some sites may use a certificate file for best security.

Hope this helps.

Rob

52 Posts

November 29th, 2011 12:00

Currently the latest available version of the OMSA VIB is 6.5 A01 which was released in March.  Your instructions reference 6.5 A02 which is not yet available.  When will it be available and will the A01 release work before then?

Here is some additional detail about using the current A01 release on ESXi 5 but it doesn't elaborate if OME will work with it:

en.community.dell.com/.../1977.aspx

16 Posts

December 2nd, 2011 11:00

Even after adding the WS-man setting the ESXi 4.1 server still shows a purple on the hardware health.

3 Apprentice

 • 

2.8K Posts

December 2nd, 2011 12:00

Hi Ben,

I wonder if your discovery range has *both* SNMP and WSMan enabled in the wizard.

If so, you need to delete the device, create a new discovery range with WS-MAN enabled and SNMP disabled.  See if that works.

Rob

3 Apprentice

 • 

2.8K Posts

December 13th, 2011 06:00

ESXi 5.0, OMSA VIB 6.5 A02 now posted here...thx.  Rob

www.dell.com/.../DriverFileFormats

December 16th, 2011 12:00

OK, we have following the instruction from the OME tutorial for the installation of OMSA and such.  I created a unique include range (one IP address)with only WS-MAN enabled with a username and password, unchecked secure mode, with port 443, and nothing is getting discovered.  

I used the troubleshooting tool, and I was able to connect to SNMP successfully and tested successfully with the WS-MAN test.  Any suggestions?

3 Apprentice

 • 

2.8K Posts

December 16th, 2011 13:00

Ignore my prev post dated 3:04pm...I posted to the incorrect thread.  Rob

3 Apprentice

 • 

2.8K Posts

December 16th, 2011 13:00

So I'm not entirely sure I understand what you are seeing here.  A drac with an iSCSI ip? hmm..

Did you discover them both in a single ip range or two discovery ranges.

You might try deleting the device from the tree, then rediscovering just the server with the SNMP protocol.

Then let's see what gets displayed.

You can also use the troubleshooting tool (installed on your desktop) to test the ip addresses of your server and drac to see what gets returned in the test.

Rob

Ignore, posted to wrong thread.

December 16th, 2011 14:00

Version 5

3 Apprentice

 • 

2.8K Posts

December 16th, 2011 14:00

What version of ESXi ?

3 Apprentice

 • 

2.8K Posts

December 16th, 2011 15:00

Did you install A02 ?

December 16th, 2011 15:00

Yes sir. The vm admin followed the instructions explicitly.

No Events found!

Top