Overview
NetOp's SNMP integration allows monitoring of network devices that don't have a native API integration (firewalls, routers, switches from any vendor). The SNMP agent is deployed as a lightweight collector on a server within your network.
Architecture
NetOp Platform (Cloud)
|
v
SNMP Collector Agent
(deployed on your server)
|
v SNMP v2c/v3
Network Devices
(routers, switches, firewalls)
Prerequisites
- A Linux or Windows server with network access to all target subnets
- SNMP enabled on target devices
- Community string (SNMP v2c) or credentials (SNMP v3) for each device
Deployment Steps
1. Deploy the SNMP Agent
Download and install the NetOp SNMP collector agent on your designated server. Contact NetOp support for the agent package and installation instructions.
2. Configure in NetOp
- Go to Settings → SNMP
- Locate the agent by its Agent Name and Collector ID
- Under Subnets, click + to add a new subnet entry:
- Enter the subnet range (e.g., 192.168.10.0/24)
- Assign a Site Name — all devices discovered in this subnet will be placed in this site
- Click Save
3. Configure SNMP Credentials
Under SNMP V2 Credentials, add the community string:
- Click +
- Enter the community string
- Click Save
The platform will begin scanning the configured subnets and associating discovered devices with the correct sites.
Mapping Suggestions
NetOp provides Mapping Suggestions — automatically detected devices that could be added to the inventory. Review and accept suggestions to populate your asset list.
What SNMP Monitors
Once configured, NetOp collects the following metrics via SNMP:
- CPU utilization
- Memory utilization
- Interface traffic (in/out)
- Interface errors
- Device uptime
- Port status (up/down)
Troubleshooting
No devices discovered
- Verify the SNMP community string matches the device configuration
- Confirm the agent server has network access to the subnet
- Check agent status in Settings → SNMP
Devices in wrong site
- Update the subnet-to-site mapping in Settings → SNMP → Subnets
Partial discovery
- Some devices may use different community strings — add multiple entries
Best Practices
- Use a dedicated read-only SNMP community string for NetOp.
- Segment subnets by site to ensure accurate site assignment.
- Enable Periodic Sync to keep device discovery current.
Comments
0 comments
Please sign in to leave a comment.