Pass the SolarWinds Certified Professional SCP-NPM Questions and answers with ValidTests

 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]

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

NPM can monitor the network bandwidth utilization of your devices, interfaces, and applications using SNMP and NetFlow protocols. Network bandwidth utilization is the amount of data transmitted or received over a network link in a given time period. High network bandwidth utilization can indicate network congestion, packet loss, latency, or other performance issues that can affect the email delivery speed. By looking at the network bandwidth utilization of thedevices and interfaces involved in the email communication, you can identify the possible bottlenecks or sources of network problems that might be causing the email slowness. References: Monitor network bandwidth utilization in NPM, Network Bandwidth Analyzer Pack, How to Monitor Network Bandwidth Using the Command Line.

The Export to Excel button is only displayed if the report contains only custom table resources. Other resources cannot be converted to the Excel format.https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-exporting-reports-sw1547.htm#:~:text=the%20Excel%20format.-,Click%20Reports%20%3E%20All%20Reports%20in%20the%20menu%20bar%2C%20and%20click,Click%20either%20Export%20as%20Excel .

 One possible cause of this issue is that the user account has the No Reports limitation applied to it. This limitation prevents the user from accessing any reports in the Orion Console, regardless of the report group or category. To resolve this issue, you need to edit the user account and change the report limitation to either No Limitation (to allow access to all reports) or a specific report limitation category (to allow access to only the reports with that category). You can also create custom report limitation categories and assign them to the reports and users as needed. References: Restrict who can access reports in the SolarWinds Platform, Define what users can access and do in the SolarWinds Platform.

The Discovery Ignore List is a feature that allows you to specify the IP addresses or hostnames of the devices that you do not want to monitor or discover in the future. You can add devices to the ignore list manually or automatically during the discovery process. Once a device is added to the ignore list, it will be skipped by any subsequent discovery. You can also remove devices from the ignore list if you change your mind and want to monitor them later. References: Add devices to the Discovery Ignore List in NPM, Remove devices from the Discovery Ignore List in NPM, How to View Devices on Your Windows Network and What to Do If You Can’t See Them

 Packet loss is a measure of how many packets are lost or discarded during transmission over a network. Packet loss can cause network performance issues such as slow response time, jitter, and degraded voice quality. NPM can monitor packet loss on nodes and interfaces using ICMP ping or SNMP statistics. You can review the packet loss metrics on the Node Details or Interface Details views, or create a custom chart or report to compare packet loss across multiple nodes or interfaces. By reviewing the packet loss on the nodes on either side of the connection, you can identify which node or interface is experiencing the problem and troubleshoot the root cause. You can also use the Performance Analysis dashboard (PerfStack) to correlate packet loss with other metrics such as response time, CPU load, memory usage, buffer misses, and interface errors123. References:

Monitor packet loss in NPM - SolarWinds

Troubleshoot intermittent network slowdowns with NPM - SolarWinds

SCP Study Aid - SolarWinds (page 9)

https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-configuring-trap-viewer-filters-and-alerts-sw272.htm https://documentation.solarwinds.com/en/success_center/orionplatform/content/lm/la-orion-log-viewer.htm

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

SNMP traps are unsolicited messages sent by SNMP-enabled devices to notify the NPM server of important events or problems, such as device failures, configuration changes, or performance issues. SNMP traps contain information about the device and the event, such as the device name, IP address, timestamp, and OID (Object Identifier). An OID is a unique identifier for a specific variable in a MIB (Management Information Base), which is a hierarchical database of device information that can be accessed by SNMP. However, not all OIDs are recognized by NPM by default, as different devices may use different or custom MIBs and OIDs. Therefore, to ensure NPM correctly interprets SNMP traps from a new router on your network, you need to update the MIB database with the latest MIBs from the router vendor or from the SolarWinds website. This will allow NPM to translate the OIDs in the SNMP traps into meaningful names and values, and display them in the Trap Viewer or use them in alerts12.

To update the MIB database, follow these steps3:

Download the MIB files from the router vendor’s website or from the SolarWinds MIB Database.

Copy the MIB files to the \SolarWinds\Orion\Mibs folder on the NPM server.

Click Settings > All Settings > Manage MIBs.

Click Add New MIB and browse to the MIB file that you want to add.

Click Submit.

Repeat steps 4 and 5 for each MIB file that you want to add.

Click Compile to compile the MIBs and update the MIB database.

You can now view the SNMP traps from the new router in the Trap Viewer or use them in alerts. References: 1: SNMP Traps Explained: How to View SNMP Traps, 2: SNMP Traps in NPM, 3: Update the SolarWinds MIB Database for the SolarWinds Platform, : SolarWinds MIB Database, : 2, : 1, : 3, : 4