NetMaster REST API zFS Setup in Shared zFS Environment

Products

• NetMaster Network Management for TCP/IP

Issue/Introduction

Can the REST API run across multiple LPARs in a plex from one shared directory/ZFS file? 

In addition, if it is possible, are there any cons to be aware of with this deployment type?

In the Install guide it indicates per LPAR install:

NMAPIDEP - JCL member. Deploys the NetMaster API Service to the desired location. Re-run the NMAPIDEP member for each NetMaster LPAR on which the NetMaster API Service is set up.

however, another REST API with a similar setup is configured to utilize the shared ZFS across the plex.

Environment

Netmaster Network Management for TCP/IP

Resolution

The REST API is not designed to use a shared ZFS.

Each NMAPI Server requires a unique .yaml file in the ZFS that allows it to interact with the local Netmaster region, and that NMAPI can also write a log out to the ZFS file, which would not function properly if shared. There are additional .so files that might not be shareable between API services - we have not attempted to do so.

In short, the recommendation is to define separate ZFS files and create unique mountpoints for each LPAR.