Ten items, checked at onboarding, prevent the large majority of later "the platform is wrong" escalations. Work through them for every new customer before anyone relies on the data.
Account structure
NetOp nests five levels. An Organization is your top level, and an Organization Admin invited at the root sees every sub-organization and tenant beneath it. A Customer (Tenant) is one end customer, and settings live here — every site under that customer shares the same thresholds. An Integration is the vendor connection that defines the customer's data. Sites sit under an integration and are the level at which you triage. Devices sit under sites, each with its own dashboard.
Create the tenant first, with the name you want, then attach its integration. The alternative — configuring the integration directly and letting NetOp generate the customer — produces a system-generated name you have to rename later.
The checklist
- Tenant created with the customer's real name. A system-generated name follows you into every report.
- Integration connected and discovering. Devices appear under Assets, and Last Sync shows a recent success.
- Periodic sync enabled, daily. Operations › Periodic Sync. Without it the picture ages quietly.
- Sites named the way the customer names them. Settings › Sites. Vendor-generated names mean nothing in a phone call.
- Devices assigned to the right sites. Settings › Site Management. Wrong attribution distorts topology, correlation, and every site-level number.
- WAN bandwidth limits configured. Settings › Network Interfaces. Without them, utilisation cannot be calculated at all.
- Port roles set: ISP, interconnect, or user. Settings › Network Interfaces. The single biggest noise reduction on switch-heavy sites.
- SLA profiles tagged with a traffic type. Settings › QoE. An untagged profile scores against the wrong expectations.
- Thresholds reviewed against this customer. Settings › Anomalies. Defaults are balanced, not tailored.
- Notification recipients and topics agreed. Integrations › Notifications. Decide what is internal and what is external.
Connecting an integration
Integrations › Datasources. Pick the vendor, supply the credentials, and discovery begins.
Have the token, URL, and region ready before you open the form — the session will not wait. Never share a token by email; store it in a password manager.
A note specific to Meraki: one API token can manage several customer organizations, so make sure the admin user that created the token belongs to every Meraki organization you expect to see. After saving the token, click it — available tenants appear under New Tenants, and ticking and saving adds them automatically with no manual sync.
Editing an existing integration lets you change the token, set the region, and enable or disable collection without deleting the connection.
Adding SNMP coverage
SNMP fills the gaps that vendor cloud APIs do not report: printers, servers, UPS units, and storage. Use it where coverage matters more than depth.
The collector runs on a host inside the network, so deploy the agent first — the SNMP tab configures it after deployment, it does not install it. Then define subnets and v2/v3 credentials under Settings › SNMP, and the UI pushes that to the agent, which autodiscovers devices on those subnets.
Two things worth care here. The community string is effectively a device password — treat it as a credential and do not reuse one string across customers. And assign a site name during this step so discovered devices land in the right place automatically, rather than needing correction in Site Management afterwards. The platform proposes subnet-to-site mappings; review them rather than accepting them wholesale.
Connecting a ticketing system
Integrations › Workflows supports ServiceNow and ConnectWise, so incidents flow into one queue rather than two.
Decide early which system is the source of truth for the customer-facing SLA clock. Running two clocks produces two different MTTR numbers and an awkward service review. Requirements differ per platform and per instance, so raise this before committing to a date.
Related articles
- How NetOp collects your network data
- Reducing alert noise
Comments
0 comments
Please sign in to leave a comment.