SolarWinds SCP-NPM Based on Real Exam Environment

 SNMP traps are unsolicited messages sent by network devices to report events or issues. If NPM receives too many traps from devices that are not managed by NPM, or traps that are not relevant for monitoring, the performance of the Orion Web Console can be affected. To resolve this issue, you can point the devices to a trap manager, such as Kiwi Syslog Server, and configure it to filter out unwanted traps before forwarding the remaining ones to the Orion Platform. This way, NPM will only process the traps that are important for monitoring and alerting, and reduce the load on the database and web server. References: Configure SNMP traps in NPM, Filter traps in Kiwi Syslog Server, [Forward traps to another host in Kiwi Syslog Server]

To detect duplex mismatches, you need to meet the following requirements1:

• The nodes must be monitored by NPM.
• The nodes must be in the up state during the discovery.
• The nodes must support topology and be interconnected.
• Duplex of both devices must be identified as full or half.
• The Possible Duplex Mismatches widget must be enabled on the node details view.

You do not need to ensure corresponding values for each interface are different, as this is the result of a duplex mismatch, not a requirement for detection. In fact, you should unify the duplex mode configuration on neighboring interfaces to avoid mismatches1.

References: Detect and predict duplex mismatches in NPM; Speed and Duplex Mismatch - Forum

 Device Studio Poller is a feature that allows users to create custom pollers for devices or technologies that are not supported by default in NPM. It can poll multiple OIDs for a given technology, perform logical operations or transformations on the polled data, and display the polled values in existing resources. However, it does not collect data from Orion Failover Engine or Hot Standby Engines, which are features of Orion High Availability that ensure continuous monitoring in case of primary server failure12. References: 1: Create pollers in Device Studio for NPM3, 2: When Good OIDs Go Bad: Customizing Device Pollers, 3: Manage Pollers (AKA Device Studio) question

Capacity planning is available for the following metrics of monitored nodes, interfaces, and volumes: CPU utilization on nodes, memory usage on nodes, space usage on volumes, receive(in) utilization on interfaces, and transmit (out) utilization on interfaces1. Capacity planning allows you to monitor capacity usage trends on the network and forecast capacity issues based on historical data and customizable thresholds. You can view capacity forecasting graphs and tables on the details views of nodes, interfaces, and volumes, or use the Top XX Capacity Problems widget to see a list of objects whose usage trend is rising2. References: Monitor capacity usage trends on the network and forecast capacity issues in NPM, Forecast capacity for nodes, interfaces, or volumes in NPM