...
- The individual performing this installation has a small bit of Linux experience
- Root access is available
- Internet access is required for installing any missing but required software packages
- NMIS must be installed on the same server that opHA is being installed on. Here you can read the NMIS installation guide.
- You will need a license for opHA ( CONTACT US for an evaluation license )
- opHA has to be installed onto the Master Primary and each Poller NMIS server
...
opHA needs to be installed in all the servers - Masters and Primaries and pollers - but we will be using the GUI only from the master Primary server.
opHA Set Up
...
Here you can find how to perform the basis to start running opHA.
...
| Info | ||
|---|---|---|
| ||
You MUST set the "opha_url_base" on the POLLER to the https:// url for the poller before doing discovery. In setting opha_url_base you must also set the opha_hostname to match the fqdn. If the opha_url_base is blank the master Primary will connect to the poller but on receipt of the pollers information it will swap the https:// URL for http:// and the discovery will then fail. |
...
Once we have synchronise a peer we will be able to see its data from NMIS or opCharts from the master Primary.
opHA Roles
...
We can assign roles to peers using the configuration menu > Role Mapping:
...
By default, the system creates the next roles:
- Poller
- MasterPrimary
- Local
- Portal
But it is possible to update them though the configuration file.
...
opHA version 3.0.5 brings a new feature to modify the NMIS and omk configuration from the master Primary server. The centralised configuration feature allows to manage easy and quick a large network of multi-servers network.
...
It is important to note that once NMIS is updated from a masterPrimary, cannot be edited from the poller.
...
In the opHA synchronisation, the registry data for each product configured in the server will be send to the masterPrimary.
Each registry has a url property. In the opCharts case, it will be used to see the graphs from the poller.
...
In the following url, http://server/en/omk/opHA/peers/CLUSTERID you can perform several actions about the following peer capabilities:
- Pull Peer Data: The master Primary will request all peer data enabled - except for nodes from version 3.2.1. Since the last synchronisation date. This action is performed periodically (cron job) for all peers.
- Clear Latest Data: Will remove the last synchronisation date, so the next pull will be complete.
- Sync all nodes: From 3.2.1. The master Primary will send all the nodes to the peer. This means, if the peer doesn't have a node, It will be created. If the master Primary does not have a node and the peer does, it will be removed from the peer. You can read more in Centralised node management page.
- Rediscover: From 3.2.1. The master Primary will update the peer data, this is the registry url access, the user and the server name, based on the peer information:
opha_api_user: From opCommon.json config file
opha_url_base: From opCommon.json config file
- server_name: From nmis config file, Config.nmis
...