gNBs
Sign in to Connect NMS
Reset your password
Enter your nms2 email. We'll send a link to choose a new password.
Choose a new password
This signs you out everywhere.
| Status | gNB | IP | ID | Core | CPEs | Ping | Uptime | Last drop | Cells / SAS | Alarms | Serial | Updated |
|---|
Live data is read from each gNB over SSH every 2 minutes (read-only key); ping every 30 s. Click a row for details, an IP to open the gNB's web page.
| Status | Device / serial | IP | Site | gNB | Signal | Ping | Last drop | Drops 24 h | Last check-in | Uptime | Last test | Firmware | MAC |
|---|
Every CPE's serial, model, firmware, serving gNB and signal come from WaveNMS's list (every 5 min, via cpe_watch). MDU CR650s are also found in the buildings' routers and pinged every 30 s ("offline" = 3 failed pings in a row); CPEs the NMS can't ping (5G CPEs and the CR650s behind them) use WaveNMS's online status. Devices on the ACS relay also show their own TR-069 check-ins every 60 s. Click a row for details, an IP to open the device's web page.
| Status | Device / serial | MAC | IMSI | Last seen | Where | Firmware | Added from | Notes |
|---|
Every CR650 / CPX60 / CPX80 we own. Units move to Deployed by themselves the moment they show up on our network (check-in, building router, or WaveNMS reports them online), or to Staged if they show up from the staging bench. In stock = never seen working; Idle = seen before, silent 30+ days. Returned / RMA / Retired are set by hand. Units provisioned in WaveNMS but never online are imported here automatically while the WaveNMS link works; new stock can be added from a CSV or by scanning serials, with no WaveNMS needed.
Check an address
Or click the map. Coordinates work too (e.g. 41.4397, -81.7052).
Spec sheet for the installer
The PDF has the heading, a satellite map with the aiming line, distance, likely sector and an on-site checklist. Client details go only into the PDF; nms2 doesn't store them.
| Name | When | Repeat | gNBs | Status | Progress / last run | Set up by |
|---|
At the chosen time nms2 saves an evidence snapshot, then reboots the gNBs one at a time: the next starts only after the last is verified back. If one doesn't come back the batch stops and the rest are left alone. Each gNB needs nms2's reboot key (docs/GNB_REBOOT_KEY.md); one without it is skipped. Google Chat gets a message when the batch starts and when it ends, plus one per gNB; the usual down/up alerts for them are held.
| Name | When | Repeat | CPEs | Status | Progress / last run | Set up by |
|---|
At the chosen time nms2 reboots the CPEs 10 at a time through our ACS (WaveNMS keeps managing them). A CPE that hasn't checked in through the relay in the last 5 minutes is skipped; if one is rebooted but doesn't come back, the batch stops. "Several CPEs offline" alerts for CPEs being rebooted are held. A run more than an hour late (nms2 was down at the time) isn't started late.
Mark what happened (goes on the timeline)
Snapshots (kept after the 90-day metrics expire)
Save one before rebooting anything during a failure. It freezes every chart below for the selected range, plus the timeline and gNB states.
| # | Label | Range | Saved |
|---|
gNBs
Reachability is from the NMS pinging each gNB every 30 s; "unreachable" needs 3 failed pings in a row. Answering ping does not prove a gNB is passing traffic.
| gNB | ID | IP | Core | Ping | Since | RTT |
|---|
| When | Severity | What | Subject | Details |
|---|
| Token | Starts with | Created | Last used |
|---|
Our CRM sends customer records (name, account, service address, phone, email, contacts) to nms2's API with one of these tokens, or nms2 pulls them from the CRM's URL (NMS_CRM_PULL_URL). Records are matched to CPEs by serial or MAC and shown on the CPE pages. The CRM can also read each device's online/offline status. The API is described in docs/CRM_API.md. A token only opens the CRM API, and only its hash is stored.
Health (nms doctor)
| Check | Status | Details |
|---|
Notification channels
| Name | Type | Last success | Last error |
|---|
Add a channel (saved only if a test message goes through)
Delivery log (last 50)
| When | Channel | Subject | Status | Tries | Error |
|---|
My account
Password
Changing the password signs you out everywhere else (other browsers, phones); this browser stays signed in.
Sessions
Signed in somewhere you shouldn't be, or on a shared computer? End every other session; this browser stays signed in.
| Name | Role | Status | Last sign-in |
|---|
admin: everything, including users and integrations · operator: day-to-day CPE work (settings, diagnostics, renames, Open through nms2), inventory, notes; no reboots, firmware, schedules or users ·viewer: read only. Disabling an account or setting a new password ends its sessions straight away. Everything here is in the audit log.