On Boarding Steps (Prime Monitoring)
On Boarding Steps (Prime Monitoring)
Top customer deliverables (prio 1–5)
Device reachability — management IPs / SNMP communities / ACS access for pilot modems and NetGws
Monitoring Config agreed — spectrum span, realtime interval, DHCP flapping threshold
Grafana dashboards assigned — configfiles used in production point to the right history dashboards
Pilot analysis sign-off — NOC confirms Analysis works for DOCSIS and (if used) TR-069 samples
Detect pairing — impairment board / topography available so Monitoring is not used in isolation
Scopes
Access
|
|
|---|---|
NMS brings | Monitoring package enabled; role templates for Analysis vs config |
Customer brings | Named NOC owners and who may change Monitoring Config |
Decide | Who may run spectrum / iperf in production |
Decisions
|
|
|---|---|
NMS brings | Recommended spectrum spans and flapping defaults |
Customer brings | Plant frequency plan, SNMP/ACS standards, which device types are in scope |
Decide | Pilot CMTS / clusters vs full-plant day one |
Initial data
|
|
|---|---|
NMS brings | Poller / Grafana wiring per deployment model |
Customer brings | Reachable pilot devices, credentials, configfile ↔ dashboard mapping |
Decide | Whether Arris iperf is enabled |
Acceptance
|
|
|---|---|
NMS brings | Unit Test Protocol (Prime Monitoring) run on the tenant |
Customer brings | Sign-off that NOC can diagnose pilot impairments from Analysis |
Decide | Exit criteria vs Detect / Ticket go-live |
Parent hub: Prime Monitoring