HP SIM for NonStop Manageability

Linux CMS Requirements
For HP SIM plug-ins that support using a Linux-based CMS, HP SIM and the plug-in's client
component can be installed on any Linux CMS that meets these minimum requirements:
• Any HP IA-32 or IA-64 AMD64 or EM64T system running one of the following Linux versions:
Red Hat Enterprise Linux 5, Update 4 (32 bit)◦
◦ Red Hat Enterprise Linux 5, Update 5 (32 bit)
◦ Red Hat Enterprise Linux 6 (32 bit)
◦ Red Hat Enterprise Linux 4, Update 8 (64 bit)
◦ Red Hat Enterprise Linux 5, Update 4 (64 bit)
◦ Red Hat Enterprise Linux 5, Update 5 (64 bit)
• At least a 1.5-GHz processor and 4 GB RAM; 2.4-GHz processor and 8 GB RAM is
recommended.
• Network connectivity – to a secure operations LAN.
• Software: HP SIM 6.3 or later. HP SIM 6.3 can be installed from the HP SIM DVD that shipped
with NonStop System Console DVD, Update 15 and later. For Update 17, the DVD that ships
along with the NSC DVD was retitled the HP Insight Control for NonStop DVD; it now contains
the NonStop Software Essentials client component for both Windows and Linux in addition
to HP SIM. You can also download HP SIM at:
http://www.hp.com/go/hpsim/download
The Linux CMS (as with a Windows CMS) can be a physical server running Linux (or Windows)
directly on the bare metal, or a virtual server running Linux (or Windows) on a VM with the
hypervisor being VMWare ESX 3.5 (and later) or ESXi 4.1 (and later).
OSM Configuration Requirements
You must configure OSM on each NonStop system that will be monitored by HP SIM. If not already
present, for HP Integrity NonStop NS-series or HP NonStop S-series systems, add the UseSSL=ON
parameter in your OSMCONF configuration file. The OSMCONF file is located on a NonStop system
at $SYSTEM.ZSERVICE.OSMCONF. For information on creating and using an OSMCONF file, see
the OSM Configuration Guide.
If the CMS used to discover and manage the NonStop system is outside of the dedicated
maintenance LAN, you must specify stack parameter(s) for OSM in your OSMCONF file as follows:
stack = <TCPIP process name>
For example:
stack = $ZTC00
stack = $ZTC01
After modifying the OSMCONF file, you must stop and restart the OSM processes in order for the
change to take effect, as follows:
scf abort process $zzkrn.#osm*
scf start process $zzkrn.#osm*
14 Requirements