SCP-NPM Exam Dumps - SolarWinds Certified Professional Questions and Answers

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

The Orion platform supports agent-based monitoring for Windows, Linux/Unix, and AIX systems. An Orion agent is software that provides a communication channel between the Orion server and the target system, as an alternative to WMI or SNMP. Agent-based monitoring can offer better performance, security, and reliability than agentless monitoring, especially for remote or cloud-based systems. The Orion platform does not support agent-based monitoring for Sun Solaris or IBM systems, as they are not compatible with the agent software. References: Monitor with SolarWinds Platform agents in SAM, SolarWinds Platform Agent requirements, Orion Platform | SolarWinds

By default, NPM uses the global critical CPU threshold for node statuses, which is 90%. However, you can override this threshold for individual nodes by editing their properties and specifying a custom value for the critical CPU threshold. This way, you can adjust the threshold according to the specific characteristics and performance of each node. Changing the critical CPU threshold on the node will affect how the node status is calculated and displayed in the web console, as well as how the alerts are triggered based on the CPU utilization. References: Thresholds in the SolarWinds Platform; CPU Critical Threshold - Forum - Network Performance Monitor (NPM) - THWACK

 When you configure a report in the SolarWinds Platform Web Console, you can limit access to specific users by assigning a report limitation category to the report and to the user account. A report limitation category is a custom label that defines which reports a user can see. For example, you can create a “finance” category and assign it to the reports and users related to the finance department. Users with the “finance” category can only access the reports with the same category, and not the reports with other categories, such as “marketing” or “IT”. You can also prevent users from accessing any reports by applying the “No Reports” limitation to their account, or allow administrators to see all reports by applying the “No Limitation” category to their account. References: Restrict who can access reports in the SolarWinds Platform, Define what users can access and do in the SolarWinds Platform.

NetPath is a feature of SolarWinds NPM that helps you identify network problems faster by automatically creating a map of the problem area, with a wide variety of supporting information. NetPath displays the performance details of devices inside and outside of your network. You can use NetPath to see the node-by-node network path from a probe at remote site A to the accounting server at the headquarters, and isolate the node or connection that is decreasing end-to-end performance. If the issue is external, NetPath identifies the name of the company that owns the node and displays their contact information. If the issue is internal, NetPath incorporates data from NPM, NCM, and NTA about your on-premises gear. The other options are not as effective as NetPath in finding the source of the issue, as they do not provide the same level of visibility and analysis of the network path. References:

• NetPath - Easy Visual Network Path Analysis
• Discover your network paths in NPM
• View a network path in NPM

NPM can monitor the virtualization host hardware health, VM sprawl, and virtualization host and VM performance metrics using the Virtualization Manager Integration feature1. However,NPM cannot display the virtualization environment tree, which shows the hierarchical relationship between the virtualization hosts, clusters, datastores, and VMs. This feature is only available in Virtualization Manager2, a separate product that can be integrated with NPM. References: 1: Network Performance Monitor Administrator Guide - Monitor virtual infrastructure 2: Virtualization Manager Getting Started Guide - View the virtualization environment tree

 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]

One possible reason for not being able to show the polled results as charts on the Orion Web Console is that you did not set the poller to collect historical statistics. Historical statistics are required for displaying charts and gauges in the web console, as they provide the data points for plotting the trends and values over time. If you only set the poller to collect current statistics, you will only be able to view the polled results as tables or lists in the web console. To set the poller to collect historical statistics, you need to edit the poller and select the Keep Historical Data option in the Poller Properties page. You can also specify the retention settings for the historical data, such as the frequency and duration of data collection and storage1. References: Create a custom poller

 According to the SolarWinds NPM Administrator Guide, you can edit the node properties of any device and change the polling method to suit your needs. The polling method determines what data is collected and displayed for the node. The “Most Devices: SNMP and ICMP” polling method collects and displays the most comprehensive data, including CPU load, memory utilization, interface statistics, and more. The “Status Only: ICMP” polling method only collects and displays the node status, average response time, and packet loss. If you want to monitor the other statistics on switch A, you should change the polling method to “Most Devices: SNMP and ICMP”. This will not affect the historical data that has already been collected for switch A, as it will be stored in the database. However, deleting switch A and adding it again, or adding switch A again without deleting it first, will result in losing the historical data or creating duplicate nodes. References: SolarWinds NPM Administrator Guide, page 78-79; Polling methods used by Orion

 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