Overview (Prime High Availability)
Overview (Prime High Availability)
NMS Prime is a CRM, BSS and OSS platform for ISPs and Telcos.
What this app does
Prime High Availability (ProvHA) is the HA, failover, and load-balancing package for NMS Prime. It pairs a master (read/write) with a slave (read-only DB, shares provisioning load) so DHCP, TFTP, time, and DNS keep serving when one host fails — using Linux/open-source standards (ISC DHCP failover, Galera, rsync/sshfs, and related services).
It answers:
Who is master? — Role from
provha.envand GUI master/slave IPsDoes provisioning survive a host failure? — DHCP failover peers; TFTP / time / DNS peer lists
How is slave kept in sync? — Periodic slave config rebuild; master→slave file sync
What about monitoring in HA? — Cacti via sshfs/autofs; Icinga in HA scenarios (see install guide)
Who uses it
Role | Work |
|---|---|
DevOps / Linux IT | Cluster install, firewall, Galera, ssh keys |
Provisioning ops | ProvHA GUI (master/slave, load ratio, rebuild interval) |
Delivery | Close enablement with NMS Prime; acceptance failover tests |
Main features
Master / slave ProvHA configuration in the GUI
ISC DHCP failover (primary/secondary peers)
TFTP, time, and DNS peer addressing for HA
Slave config rebuild + master file sync commands
Slave cleanup (move non-needed system jobs)
Integration path for Monitoring (Cacti) and Detect (Icinga) in HA
Handled by neighbouring apps
Capability | App |
|---|---|
Day-to-day provisioning data | |
VoIP provisioning | |
Cable-access monitoring graphs | |
Impairment / Icinga path |
Main stories
Run two NMS Prime hosts as master + slave with Galera
Keep DHCP leases and provisioning alive if one host fails
Sync config files and rebuild slave periodically
Prove failover in a controlled acceptance test
At a glance
|
|
|---|---|
Menu / alias | HA/LB · ProvHA Config |
Package |
|
Needs | Base; ProvBase; fuse-sshfs; autofs |
Related | Deep install: High Availability Installation under Official Documentation |