Server Management - Systems Insight Manager
1849467 Members
6147 Online
104044 Solutions
New Discussion

HP SIM > 1000 servers

 
fishman_1
New Member

HP SIM > 1000 servers

Is anyone sanely managing this many systems with this product? I'm currently taking SIM training from HP and it proving to be as clunky and finicky as ever. How can you possibly manage all of the security layers, configuration, repository care and feeding without dedicating 1 or more people just to the task?
I know it is a huge task by anything, but this product still needs a lot of work (Better AD integration for security simplication etc) to get there.

fishman
6 REPLIES 6
NEETI TOLIA
Frequent Advisor

Re: HP SIM > 1000 servers

SIM can manage upto 5000 nodes. HP IT itself manages more than 1000 nodes using SIM. There is HP video regarding this somewhere on HP site.
fishmn
Regular Advisor

Re: HP SIM > 1000 servers

I'd love to meet the poor sole who would dare use this to manage 5000 nodes.. he'd be committed to an insane asylum after a few months!
Bill Slobodnik
Frequent Advisor

Re: HP SIM > 1000 servers

I'm running with about 2300 servers without problems (so far), but only for monitoring and reporting. We do not use HPSIM for repository, or any kind of HP software pushes.
Neal Bowman
Respected Contributor

Re: HP SIM > 1000 servers

We use it to manage 2500+ servers. We are a little short on installed RAM, so queries and initial startup is a little slow, but it is acceptable.
fishmn
Regular Advisor

Re: HP SIM > 1000 servers

Those are impressive numbers of servers! I assume you've installed openssh on all your windows boxes? You have them all setup under version control, SNMP alerting?

How does SIM 5.X handle (version control) your older hardware like G1/G2 360/380's?

Do you run your SIM database (SQL?) locally or remotely?

Thanks for replying!
Neal Bowman
Respected Contributor

Re: HP SIM > 1000 servers

For now,we have not installed OpenSSH. We just recently upgraded from CIM7 to CIM5, and are now beginning to see some of the capabilities that are possible. We are under powered as far as memory is concerned, and wind up rebooting our CMS server weekly.