Official Documentation (Prime High Availability)

Official Documentation (Prime High Availability)

Short operator / configuration guides for Prime High Availability.

App hub: Prime High Availability

Configuration sequence index: Module Setups · Cross-app path: Configuration

NEEDS_NATIVE_COPY: Nested install/architecture pages keep their original media, layouts, and attachments on those pages. Do not trim or re-host media across pages. English summary and links are maintained here.

Before you start

  • Role: DevOps / Linux IT with root access on both hosts

  • Two NMS Prime installations; Galera (or agreed SQL cluster) ready

  • Package nmsprime-provha on master and slave

  • Needs: Base, ProvBase, fuse-sshfs, autofs

Guides

#

Guide

For

#

Guide

For

1

First steps (roles & GUI)

DevOps

2

DHCP failover sanity

DevOps

3

Sync & rebuild slave

DevOps

High Availability Installation

Full install (English)

High Availability Architecture

Architecture (NEEDS_NATIVE_COPY)

Typical Tier-1 Architecture

Reference (NEEDS_NATIVE_COPY)

1. First steps (roles & GUI)

  1. Install nmsprime-provha on both hosts (yum install nmsprime-provha)

  2. Set PROVHA__OWN_STATE=master or slave in /etc/nmsprime/env/provha.env; run php artisan config:cache

  3. Open ProvHA Config in the GUI; set master IP, slave IP, DNS update passwords, rebuild interval

  4. Confirm own state set and determined values match (GUI warnings if not)

[Screenshot TBD]

2. DHCP failover sanity

  1. Set addresses in /etc/dhcp-nmsprime/failover.conf (master/peer)

  2. Ensure dhcpd.conf includes the failover file; open peer ports (e.g. 7911/tcp, 647/tcp) in firewalld

  3. Rebuild DHCP config from master; check journalctl -u dhcpd for peer normal / balancing messages

  4. Remember: DHCP may not answer until the peer is reachable during startup

3. Sync & rebuild slave

  1. Establish SSH key access from master to slave

  2. On master: php artisan provha:sync_ha_master_files

  3. Confirm slave rebuild interval; run cleanup on slave as documented (provha:clean_up_slave)

  4. Optional paths: Cacti sshfs/autofs and Icinga HA — follow the nested Installation page

Nested deep-dives (preserve URLs)

Page

Purpose

Page

Purpose

High Availability Installation

Full master/slave install, Galera, rsyslog, Cacti, Icinga

High Availability Architecture

Architecture overview

Typical Tier-1 Architecture

Tier-1 reference


Legacy hub content (videos & media)

 

 

Prime High Availability is the core package for the entire HA-, Failover- and Load-Balancing process in NMS PRIME. It will enable you to run all Applications with several million devices in a highly secure, redundant, and tested manner. For this purpose, we try to stick as close as possible to default Linux and open-source standards.

Pro hint: It is best used with a lot of excellent Linux IT guys, devops, engineers and assisted in a close fashion with our team.


Package name: nmsprime-provha

Forum: General

Content

Feature

State

Details

Start here..

Feature

State

Details

Start here..

General Linux Service

SQL cluster via MariaDB

High Availability Installation

Apache cluster

Filesystem cluster

Syslog

 

 

 

OS Provisioning

OS VoIP Provisioning

 

OS Provisioning / OS VoIP Provisioning and HA

High Availability Installation

ISC-DHCP Failover and HA

TFTP Failover and HA

Time Failover and HA

DNS and BIND failover and HA

CMTS, OLT, DSLAM usage in HA scenario

 

 

 

 

Prime Monitoring


Prime Monitoring itself via Apache

High Availability Installation

Cacti in HA

 

 

Prime Detect

Icinga in HA

 

 

 

 

Requirements