Server Management - Systems Insight Manager
1826499 Members
1649 Online
109692 Solutions
New Discussion

SIM on non HP platforms???

 
Kadir_2
Occasional Contributor

SIM on non HP platforms???

Hello,
Is it a necessity that all managed systems are an HP product, that is could we monitor an IBM server through CMS?. In some papers it is said that they should be either HP IA-32 or HP IA-36, in some other papers it is said that they can be non HP platforms and can be managed via SNMP or WMI. I am really confused. The same question holds also for CMS. Please help...
2 REPLIES 2
David Claypool
Honored Contributor

Re: SIM on non HP platforms???

IA-36? I thing you might mean IA-64 since I don't believe Intel ever made a 36-bit processor (though I believe there were some 34-bit Control Data systems years ago)...

HP software is technically licensed for use on HP systems. However, there is no functional reason why you cannot host HP SIM on a non-HP platform, but if working through a problem with HP Support, you may be told they can't diagnose any further because of being hosted on a non-HP system.

HP SIM can manage non-HP hardware to the extent that the system embraces industry standards such as SNMP and WBEM/WMI as you mention above. We have not tested or documented any procedures regarding this (although Dell has written a paper on managing their systems with HP SIM--apparently an admission on their part that Dell users are likely to use HP SIM instead of their own tool), but in general, HP SIM can do its best job when the following is true:

- SNMP is configured on the system
- WMI/WBEM requires HP SIM to have a suitable set of credentials for the system and in the case of WMI, the HP SIM server needs the WMI Mapper installed and operating
- An HTTP interface is available on the target as a UI to that system's agent and HP SIM has the port it resides on listed in the AdditionalWSdiscs.props file so it can be discovered.
Kadir_2
Occasional Contributor

Re: SIM on non HP platforms???

Thank u very much... (IA 36 was a type error)