SCP-NPM Reviews Questions

 Traps are unsolicited messages sent by network devices to report events or issues. The Orion Platform can receive and process traps from any device that supports SNMP. To alert on a select message, you can use the Traps in Orion Alerts feature, which allows you to configure the default trap alert to fire on the trap message you select to alert on. You can also customize the alert conditions, actions, and triggers to suit your needs. For example, you can alert on traps thatmatch a specific OID, source, or severity, and send an email, log a ticket, or run a script when the alert is triggered. References: Configure SNMP traps in NPM, Traps in Orion Alerts, Create alerts for SNMP traps

An OID (Object Identifier) is a unique identifier for a specific variable in a MIB (Management Information Base) that can be polled or monitored by SNMP (Simple Network Management Protocol). However, not all OIDs are supported by all devices or SNMP agents, which are software components that collect and report the MIB data. If you select an OID that is not supported by the device or the SNMP agent, you will get an “OID not supported” error when you try to create a custom poller for that device in NPM (Network Performance Monitor). This means that the device or the SNMP agent does not have the information for that OID or does not respond to the SNMP request for that OID12.

To resolve this issue, you can try the following steps34:

• Verify that the device supports the OID that you want to monitor. You can use the MIB Browser or the MIB Walk tool to browse the MIB tree of the device and find the OID. You can also check the device vendor’s documentation or website for the supported OIDs and MIBs.
• Verify that the SNMP agent on the device is configured properly and has the latest version. You may need to update the SNMP agent or enable some features or extensions to support the OID. You can also check the SNMP agent’s logs or status for any errors or warnings.
• Verify that the SNMP credentials and settings are correct and match the device’s configuration. You may need to use a different SNMP version, community string, port, or timeout value to communicate with the device. You can also test the SNMP connectivityusing the SNMP Test tool or the Test button in the UnDP (Universal Device Poller) application.
• Verify that there are no network issues or firewalls that are blocking the SNMP traffic between the NPM server and the device. You may need to allow the SNMP protocol and port on the firewall or router, or use a different network path or interface to reach the device. You can also use the Ping or Traceroute tools to check the network connectivity and latency.

References: 1: What is an OID?5, 2: The OID is not supported, 3: Troubleshoot Unknown Nodes, 4: Troubleshoot SNMP issues

 Account limitations are a way of restricting the access of Orion user accounts to specific network objects, such as nodes, interfaces, groups, maps, or alerts. You can use account limitations to prevent a user from seeing or working with select monitored entities through the SolarWinds server. For example, you can limit a user to see only the nodesin a certain group, or only the maps that they have created. You can apply account limitations to individual users or user groups, and you can choose from predefined limitations or create custom limitations based on custom properties. The other options are not effective ways of limiting user access to monitored entities, as they either affect the monitoring status of the entities (unmanage), the permissions of the entities themselves (configure permissions), or the alerting scope of the entities (configure alert limitations). References:

• Limit user access to network areas with account limitations
• Predefined Orion Platform account limitations
• Create custom account limitations