Hi Scot and thanks for the question.

mmmm....I'm not sure I have any good ideas on this one.  We do have a new CLI interface that provides a few limited capabilities.  There is a whitepaper on www.delltechcenter.com/ome on this (CLI).  It can do things like add discovery ranges, groups, etc.

But I think you are saying that you actually want to import the devices and not do a discovery of these.  Is that correct?  This probably won't work because in OME we require a certain set of data that we pick up in our discovery range so we can properly discover and classify the system.  Sometimes this gets complex if we are trying to correlate idrac to server, etc.  So we don't have a simple "device import".  Just a range import.

Hope this helps,

Rob

en.community.dell.com/.../20218169.aspx

I thought about this, we have the same situation in many NMS systems.

I think our best option is importing a "range" that is a single IP/Netmask.

This is what I successfully  did using the device csv import but like I said. I'd like to manage this

process device by device so our lifecycle automation tasks could hook into OME.

If you can import a single IP/Netmask via csv we should be able to easily automate this.

Would it be possible to simply add the device by calling Procedure

Discovery_AddDiscoveryConfiguration .

I know all the data required from the NMS.

Scot,

let me check on the procedure you mention.

But can you review the whitepaper I reference?  You can do this with the CLI I'm pretty sure (by single IP).

Rob

Just double checked.  Direct use of the Stored Proc is discouraged.   But I think the CLI wp should give you a way to do this.

Thanks much,

Rob

Does the Dell OME PS Module support PS 3.0 ?

To use the PS CLI I also need to communicate with the JSON Service on the NMS using Invoke-RestMethod

technet.microsoft.com/.../hh849971.aspx

Thanks for the update.

Can you give me kind of a step by step scenario of what you consider a best-case feature?

That will help as I provide feature request details to the product team.

Regards,

Rob

Appears to work with 3.0. Moving forward although running this from the Dell OME server is less than desirable. My best option appears to be to run a schedule task on the Dell OME server to pull all Servers from the NMS that have discovered OpenManage. Then apply logic to selectively add or remove devices from the OME Device pool.

Rob,

 I think the CLI is a great start to but would be a better service to customers as an API that could be

called remotely. Web service or whatever.Then begin to build features into it.

• update firmware
• get compliance status
• update bios etc..

Thanks, this is helpful detail.  I'll send it over to the product team so they can review these requests.

Best regards,

Rob