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-provhaon master and slaveNeeds: Base, ProvBase, fuse-sshfs, autofs
Guides
# | Guide | For |
|---|---|---|
1 | First steps (roles & GUI) | DevOps |
2 | DHCP failover sanity | DevOps |
3 | Sync & rebuild slave | DevOps |
— | Full install (English) | |
— | Architecture (NEEDS_NATIVE_COPY) | |
— | Reference (NEEDS_NATIVE_COPY) |
1. First steps (roles & GUI)
Install
nmsprime-provhaon both hosts (yum install nmsprime-provha)Set
PROVHA__OWN_STATE=masterorslavein/etc/nmsprime/env/provha.env; runphp artisan config:cacheOpen ProvHA Config in the GUI; set master IP, slave IP, DNS update passwords, rebuild interval
Confirm own state set and determined values match (GUI warnings if not)
[Screenshot TBD]
2. DHCP failover sanity
Set addresses in
/etc/dhcp-nmsprime/failover.conf(master/peer)Ensure
dhcpd.confincludes the failover file; open peer ports (e.g. 7911/tcp, 647/tcp) in firewalldRebuild DHCP config from master; check
journalctl -u dhcpdfor peer normal / balancing messagesRemember: DHCP may not answer until the peer is reachable during startup
3. Sync & rebuild slave
Establish SSH key access from master to slave
On master:
php artisan provha:sync_ha_master_filesConfirm slave rebuild interval; run cleanup on slave as documented (
provha:clean_up_slave)Optional paths: Cacti sshfs/autofs and Icinga HA — follow the nested Installation page
Nested deep-dives (preserve URLs)
Page | Purpose |
|---|---|
Full master/slave install, Galera, rsyslog, Cacti, Icinga | |
Architecture overview | |
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.
Content
Feature | State | Details | Start here.. |
|---|---|---|---|
General Linux Service |
| SQL cluster via MariaDB | |
| Apache cluster | ||
| Filesystem cluster | ||
| Syslog | ||
|
|
| |
|
| OS Provisioning / OS VoIP Provisioning and HA | |
| 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 itself via Apache | ||
| Cacti in HA | ||
|
| ||
| Icinga in HA | ||
|
|
|
|
Requirements