snIPL (simple network IPL) V.3.0.0
Back to snIPL Overview
2016-12-01 snIPL V.3.0.0 (Development stream)
This snIPL V.3.0.0 replaces all previous versions of snIPL.
Note: Default behavior and command line parameters have changed. The default is now to encrypt the connection. Also, the default password has been removed. See changes below, consult the man page, and check that existing scripts still work as expected.
Before you download any software from this web site, read the Warranty Disclaimer and Limitation of Liabilities.
This version supersedes all previous snIPL versions.
This version contains the following snIPL changes compared to snIPL V.2.3.3:
- Remove default password from snipl
- Enable SNMPv3 encrypted communication with HMC and SE
- Enable OpenSSL encrypted communication with SMAPI servers
The snIPL package contains two commands, snipl and sncap.
snIPL - simple network IPL is a command line tool that remotely controls Linux images using basic Support Element (SE) functions or basic z/VM system management functions. In particular, you can use snIPL to activate and deactivate virtual z Systems hardware.
With snIPL in LPAR mode you can load (IPL) an LPAR from a disk device, send commands to the operating system and retrieve operating system messages; or reset, activate, or deactivate an LPAR for I/O fencing purposes.
With snIPL in z/VM mode you can log on, reset, or log off a z/VM guest virtual machine.
snIPL can access the systems management API through a z/VM SMAPI request server available as of z/VM 5.3.
For z/VM 4.4 to z/VM 5.4, snIPL can access the systems management API through a VSMSERVE service machine on your z/VM system.
For setup information, see the README.snipl file.
For further details, see z/VM Systems Management Application Programming (SC24-6234) or z/VM V5R4.0 Systems Management Application Programming (SC24-6122-02) (or equivalent documentation from the z/VM website: http://www.vm.ibm.com)
snIPL for STONITH provides a STONITH plug-in. The STONITH implementation is part of Cluster Glue. Cluster Glue is a set of libraries, tools, and utilities for the Heartbeat and Pacemaker cluster stack of the High Availability Project. STONITH is usually used as part of this framework but can also be used independently.
For a general description of the STONITH technique, see: http://linux-ha.org/wiki/STONITH
For a general description of Cluster Glue, see: http://linux-ha.org/wiki/Cluster_Glue
The latest STONITH release can be downloaded from http://linux-ha.org/wiki/Downloads.
With snIPL for STONITH you can activate, deactivate, and reset Linux instances in LPAR mode or running as z/VM guests.
snIPL for Stonith supports the remote image operations activate, deactivate, and reset, exploiting basic z Systems Hardware Management Console (HMC) and Support Element (SE) functions for Linux running in an LPAR and of basic z/VM System Management Functions for Linux running under control of z/VM.
To compile and use the STONITH plugin lic_vps, you require two header files
/usr/include/pils/plugin.h and /usr/include/stonith/stonith.h.
You can find these header files in the Cluster Glue package of the Linux High Availability project
Note: As of version 2.1.3, snIPL supports STONITH version 2 only. Older snIPL versions support STONITH version 1 only.
sncap - simple network capacity management is a command line tool which allows to dynamically change Central Processing Complex (CPC) processing unit capacity from Linux environment using Support Element (SE) functions. In particular, you can use sncap to activate or deactivate temporary capacity records and query the temporary capacity record or CPC state information.
Note: For sncap, the SE must be version 2.10.0 or later.
snIPL in LPAR mode and sncap use the management application programming interfaces (APIs) provided by the HMC or SE. To communicate with the HMC or SE, snIPL and sncap establish an SNMP network connection to send and retrieve data. The HMC or SE has to be configured to allow the Linux instance where snIPL or sncap runs to access the API. If your network is firewall-protected, you must open UDP-port 161 and TCP-port 3161 between the Linux instance that invokes snIPL or sncap, and the HMC or SE.
To compile and run snIPL in LPAR mode or sncap, they must be linked to the management library hwmcaapi.
For further details, see 'z Systems Application Programming Interfaces", SB10-7164, which is available for every z Systems generation.
Both the hwmcaapi library and the publication can be downloaded from IBM Resource Link.
For more details about the snipl and sncap tools, refer to the README.snipl file and the manpages in the tarball.