New Release SCP-NPM SolarWinds Certified Professional Questions

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

Capacity usage trends are calculated based on historical data. By default, the longest time period taken into account for calculating the capacity forecast is 180 days. The more historical data up to 180 days are available, the more precise is the calculated forecast. Forecast calculation methods include peak calculation and average calculation, which can be set globally or customized for individual objects. Capacity forecasting is available for nodes, interfaces, and volumes that meet certain requirements, such as being managed in NPM and having enough historical data in the database. References: Monitor capacity usage trends on the network and forecast capacity issues in NPM, Forecast capacity for nodes, interfaces, or volumes in NPM, Real-Time Network Monitoring Tool

 Alert suppression is a feature that allows you to create conditions that prevent an alert from being triggered or sent if certain criteria are met. This can help you avoid receiving multiple or unnecessary alerts from a single event or a complex situation. For example, if you have a router that connects your SolarWinds server to a remote site with critical devices, you may not want to receive alerts about those devices if the router is down, as the problem is not with the devices but with the router. In this case, you can configure alert suppression to suppress the alerts for the devices if the router is down. To do this, you need to select the option “Suppress the alert if all of the following apply” and add the conditions “Node Name is equal to ‘target’” and “Node Status is equal to ‘Down’”. This means that the alert will be suppressed only if both conditions are true, i.e., the router with the name ‘target’ is down. If the router is up or has a different name, the alert will not be suppressed. References: Alert suppression - SolarWinds; Alert Suppression - Forum - Network Performance Monitor (NPM) - THWACK

The SNMP trap service is responsible for receiving, decoding, displaying, and storing the SNMP trap messages in the Log Analyzer database. If the service is not running, you will not see the messages in the Orion Web Console. You can verify the status of the service by using the Orion Service Manager or the Windows Services console. You can also restart the service if needed. The other options are not relevant for troubleshooting the cause of missing SNMP trap messages. References:

• Monitor SNMP traps
• Troubleshoot SNMP traps
• Orion Service Manager