/
Installation

Installation

NMS Prime can be run in the cloud or on-premises. Both paths use the same Rocky Linux / RHEL 9 stack and RPM packages from the NMS Prime package repository (repo9.nmsprime.com).

The OSS core is open source and installs without a license. To install Prime / Enterprise apps (CRM, BSS, billing, workforce, and further commercial modules), request a license file and your curated package list via contact.nmsprime.com before you run yum install for Prime packages.

Please provide a valid phone number that is reachable from Germany when you contact us via contact.nmsprime.com. Our team will call you within the first 24–48 hours. We typically call two or three times if you are not reachable. We usually call with our number visible — feel free to call back.

Structured onboarding: Start with On Boarding Steps (Prime Platform) for deployment, cloud/hosting, domain & TLS decisions — then continue with per-app onboarding pages.

1. Documentation map

Page

Purpose

Page

Purpose

On Boarding Steps (Prime Platform)

Start here for go-live — cloud/on-prem, hosting, domain & TLS, app onboarding index

Hardware Requirements

OS, CPU, RAM, disk sizing & Rocky 9 partition layout (cloud & on-prem)

Cloud

High-level cloud installation (managed or self-hosted VPS)

On-Prem

High-level on-premises installation (community & enterprise)

2. Cloud vs On-Prem at a glance

 

Cloud

On-Prem

 

Cloud

On-Prem

Remote access

✅ (1)

✅

Full functionality

✅

✅

Automatic backup (7)

✅

✅ (for SLA only)

Ready to start

✅ <15 min (managed)

✅ <30 min (fresh VM)

Required Linux knowledge

✅ low (managed) / medium (self-hosted)

❌ medium

High availability

✅ >99,99% (2)

❌ (3)

Adaptive CPU / RAM / disk

✅ (4)

❌ (4)

Data storage region

✅ EU (5)

your location

3. How installation works

Regardless of cloud or on-prem, NMS Prime is installed on Rocky Linux 9 or RHEL 9 using RPM packages from repo9.nmsprime.com. Public bootstrap script: scripts/INSTALL-REPO.sh. Review Hardware Requirements (sizing and Rocky 9 disk layout) before provisioning your host.

Choose the path that matches your edition:

3.1. Community (OSS core)

No license required.

  1. Provision host — fresh Rocky 9 / RHEL 9 per Hardware Requirements

  2. Bootstrap repos —
    curl -vsL https://github.com/cablelabs/os-provisioning/raw/dev/scripts/INSTALL-REPO.sh | bash

  3. Install packages — yum install -y nmsprime-*

  4. Configure & log in — follow Login and Configuration

3.2. Enterprise (Prime platform)

Before you install: request package selection, repo access, and license files via contact.nmsprime.com. Do not run yum install for Prime packages until you have received your delivery.

  1. Request access — contact.nmsprime.com for package selection, repo credentials, and license files

  2. Provision host — fresh Rocky 9 / RHEL 9 per Hardware Requirements

  3. Place license files in /etc/nmsprime/licenses/

  4. Bootstrap repos — curl … INSTALL-REPO.sh | bash (or install-nmsprime-ci.sh for CI branches)

  5. Install packages — curated yum install command provided with your delivery (typically not nmsprime-*)

  6. Configure & log in — follow Login and Configuration

Managed cloud instances are provisioned by the NMS Prime team — see Cloud.

3.3. Notes

(1) See Cloud for managed access and Login via SSH.

(2) Cloud infrastructure (e.g. AWS EC2) provides the HA baseline.

(3) On-prem HA is your responsibility. See Failover Architecture. SLA customers: contact us for architecture review.

(4) Capacity planning is your task on-prem; cloud providers scale resources on demand.

(5) Default EU region (Frankfurt). Other regions on request via contact.nmsprime.com.

(6) Regional backup infrastructure prevents a single-region loss from affecting your data (managed cloud / SLA).