IBM Z HMC OS Message Forwarder
The IBM Z HMC OS Message Forwarder connects to the console of operating systems running in LPARs on Z systems and forwards the messages written by the operating systems in the LPARs to remote syslog servers.
The Z systems can be in classic or DPM operational mode.
The forwarder attempts to stay up as much as possible, for example it performs automatic session renewals with the HMC if the logon session expires, and it survives HMC reboots and automatically resumes forwarding again once the HMC come back up, without loosing or duplicating any messages.
Documentation
Supported environments
- Operating systems: Linux, macOS, Windows
- Python versions: 3.9 and higher
- HMC versions: 2.11.1 and higher
Quickstart
-
If not yet available, install the "pipx" command as described in https://pipx.pypa.io/stable/installation/.
-
Without having any virtual Python environment active, install the log forwarder as follows:
$ pipx install zhmc-os-forwarder
That makes the
zhmc_os_forwardercommand available in the PATH, without having to activate any virtual Python environment. -
Provide a config file for use by the forwarder.
The config file tells the forwarder which HMC to use, and for which CPCs and LPARs it should forward to which syslog servers.
Download the Example forwarder config file and edit that copy according to your needs.
For details, see Forwarder config file.
-
Run the forwarder as follows:
$ zhmc_os_forwarder -c config.yaml zhmc_os_forwarder version: 0.2.0 zhmcclient version: 1.10.0 Verbosity level: 0 Opening session with HMC 10.11.12.13 (user: johndoe@us.ibm.com, certificate validation: False) Forwarder is up and running (Press Ctrl-C to shut down)
Limitations
At this point, the forwarder has several limitations. All of them are intended to be resolved in future releases.
- The forwarder does not recover from HMC restart or connection loss
- Restarting the forwarder will send again all OS messages the HMC has buffered
- New and deleted LPARs in DPM mode are not automatically detected.
Reporting issues
If you encounter a problem, please report it as an issue on GitHub.
License
This package is licensed under the Apache 2.0 License.
Release files for zhmc-os-forwarder 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zhmc_os_forwarder-1.2.0.tar.gz | 79.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zhmc_os_forwarder-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 105.2 kB
Release files / zhmc_os_forwarder-1.2.0.tar.gz
| Download URL | zhmc_os_forwarder-1.2.0.tar.gz |
|---|---|
| Size | 79.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1b046bb325753f0c165e8c219573f1158a39569dfcd718f25cc34ed96f420b6
|
|
BLAKE2b-256 checksum How to use checksums |
8184b259462302f66e2d323c15d9ed6bb9e60058b72a87b503c24089a3307eb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logRelease files / zhmc_os_forwarder-1.2.0-py3-none-any.whl
| Download URL | zhmc_os_forwarder-1.2.0-py3-none-any.whl |
|---|---|
| Size | 25.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e9cd7c692b2a79e647061515718b7a70e2235b5884663c1683f2aefc1d271447
|
|
BLAKE2b-256 checksum How to use checksums |
85a98fa1da6e5caa682d592aecfe740ac7ad7c4a11ffe992947cf01df09f9a27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency log