So I found a test scenario document that helps with the sizing. Now I'm trying to find something around best practices on remote locations. And if I do install multiple OME servers can they be centralized?

Schroer, Multiple OME servers cannot be centralized. However  the alerts received by different OME servers can be forwarded to one OME console through 'Alert forward' action.

For you question on discovery of OS and Drac.

You can setup discovery of OS and DRAC on the same schedules.

Also, the install whitepaper on www.delltechcenter.com/ome has a bit of info in there that might be useful to you.

Thanks,

Rob

mmmm....not sure I can find that data, I will try.

How many devices are you looking to monitor across your WAN?

Thx

Rob

One location has less than 25 at this time the second will have probably close to 100, the third and 4th have about 300 each.

Rob, I couldn't find anything talking about monitoring multiple locations with OME. As far as alerts I plan on doing what Lakshmi has recommended. We will be forwarding all alerts to a central MS SCOM. So I'm looking for any ideas to how to manage multiple locations. I have 4 locations across the world. How much traffic will the systems generate and can I just have them all report back to one central OME install or do I need to have OME installed at each location with alerts sent to our SCOM install but as far a hardware management I would have to go to 4 separate installs at each location?

Looking for something like typical system monitoring generates X amount of network traffic or Discovery and Inventory traffic amount. That way I can calculate the affect it would have on our WAN.

Yeah, this is a bit tricky.

Normally, a single OME instance would be just fine for this number of devices.  If you have the opportunity to try it out as a pilot and see how it looks, that would be good.

But, unless the connections to your various DCs are rock-solid and response times to pings are repeatedly sub-second, you may end up needed separate OMEs. Traffic depends on several variables (OME version, server generation, server options, protocol used, etc.).  Maybe you should use a packet capture tool to estimate amount of data…start/end capture before/after each (discovery/inventory/status) poll.

We have a lot of whitepapers published already, but a sizing whitepaper would be a good one to add, so I'll take note.

Best regards,

Rob

Another question on sizing of the server. I see the 3 different sizes in the document but once the SQL server is broke off how large does it need to be? So for a large deployment I need a server with 8 GB RAM and 8 cores with only 10 GB data partition. Is SQL the same? How large will the SQL DB get?

I have a test system with 150 devices and < 100 alerts and the db is only 22 MB.  But the sizing depends on features you leverage.  More system updates will take more filesystem.  More alerts will take more database.

If you are managing more than 500 servers on a single instance on a WAN of 10 mbps you can reliably do disc, inventory and health monitoring, but patch may be bandwidth challenged.

Even you do a remote db, it should be 8GB/8core etc.

Thanks,

Rob