SevOne NMS System Administration Guide
This manual describes workflows for users assigned to administrative roles that grant permission to system administration workflows. For the purposes of this document, system administration workflows include the typical initial application implementation settings, cluster level settings, settings that affect the application functionality holistically, and settings that affect all groups of things such as device types, user roles, system level passwords, etc. When you are assigned to a role that does not permit you to use a workflow, that workflow does not appear for you.
Important: As of SevOne NMS 7.0.0, SevOne is distributed using the container
technology, allowing a more confident deployment of the software. To run administrative commands on
a SevOne appliance, the administrator must now execute commands in the context of the
intended container. While the product is distributed across many containers, the one that contains
the administrative commands used in this guide is the container named nms-nms-nms for
<pod-name>-<namespace>-<container-name>.
Configuration of the appliance is largely centralized to the /config directory. This directory is shared between the host and the container and can be used directly from either place to perform the configuration tasks as directed in this manual.
By default, the container deployment of SevOne is set to be read-only. Certain directories continue to allow writing in the case of support information gathering and custom code deployment. i.e., /var/support, /var/custom, /www/custom, in addition to /config as described above.
For details on how to connect IBM SevOne NMS appliance to the Command Line Interface where SevOne NMS software runs in podman containers, please refer to SevOne NMS Connect Appliance using Command Line Interface.
Configuration of the appliance is largely centralized to the /config directory. This directory is shared between the host and the container and can be used directly from either place to perform the configuration tasks as directed in this manual.
By default, the container deployment of SevOne is set to be read-only. Certain directories continue to allow writing in the case of support information gathering and custom code deployment. i.e., /var/support, /var/custom, /www/custom, in addition to /config as described above.
For details on how to connect IBM SevOne NMS appliance to the Command Line Interface where SevOne NMS software runs in podman containers, please refer to SevOne NMS Connect Appliance using Command Line Interface.
Important: Starting SevOne NMS 6.7.0, MySQL has moved to MariaDB 10.6.12.
Note: Terminology usage...
In this guide if there is,
And, if there is any reference to slave or worker, it means follower or agent.
In this guide if there is,
- [any reference to master] OR
- [[if a CLI command (for NMS or Kubernetes or Redis) contains master] AND/OR
- [its output contains master]],
And, if there is any reference to slave or worker, it means follower or agent.