Overview
SNMP Resource Type Definitions are reusable SNMP identification profiles that map a device sysObjectID and related OIDs to a specific device type, model, OS, and interface attributes for discovery in OpsRamp.
SNMP Device Type Definitions enable Service Providers, Partners, and Clients to independently create and manage SNMP discovery definitions in their scoped environments.
Each definition is a configuration template that tells OpsRamp how to identify a device and collect extra details from it. It includes required fields like Object OID, Make, Device Type, Native Type, and OS, and can also include optional OIDs for serial number, firmware, hardware, software, and interface information.
Why use SNMP Resource Type Definitions?
- Faster onboarding for new SNMP device models.
- More accurate discovery by mapping sysObjectID and OIDs to the correct device profile.
- Better inventory quality with optional serial, firmware, hardware, software, and interface details.
- Definitions are separated by scope, so one team can make changes for its own customers without affecting others.
Available scope levels
SNMP Device Type definitions are available at the following scope levels:
| Scope Level | Description |
|---|---|
| Global | Default SNMP Device Type definitions available to all scopes. |
| Service Provider | Configurations applied at service provider level. |
| Partner | Configurations applied at partner level. |
| Client | Configurations specific to a client. |
Important considerations
- Existing Global SNMP definitions cannot be edited.
- A scoped copy from Global, Client, Partner, or Service Provider is allowed only when the same definition has no discovered resources in the target scope.
- Creating SNMP definitions at Service Provider, Partner, or Client scope is allowed only when the corresponding Global definition has no discovered resources in that scope.
- Editing or deleting a scoped SNMP definition is allowed only if that definition has no discovered resources.
- Copy, edit, and delete operations are blocked when discovered resources exist.
- Only SNMP definitions in the same selected scope can be edited or deleted.
- A Client can clone Partner, Service Provider, and Global definitions one time per definition per scope, only when no discovered SNMP resources exist for that definition.
Note
When the same SNMP Resource Type Definition SysOID exists in multiple scopes, the system uses the definition based on the following priority:Client > Partner > Service Provider > Global
Manage SNMP Resource Type Definitions
You can manage SNMP definitions for your selected scope. You can configure definitions, review existing entries, and copy eligible definitions from higher scopes when needed.
Use the following pages for common tasks: