SCP-NPM Questions and Answers

Orion agents are software components that you can install on nodes to collect and send data to the Orion server. Orion agents do not require a separate license, as they are included in the license of the Orion Platform product that you are using, such as NPM. You can install and use as many agents as you need, as long as you do not exceed the number of licensed nodes, interfaces, or volumes for your product. Orion agents can use either agent-initiated or server-initiated communication, depending on your network configuration and security requirements. References: NPM Administrator Guide, page 67; SCP Study Aid - NPM, page 15.

NPM polls static properties, such as interface speed and duplex mode, from the firewall devices using SNMP. NPM also collects traffic statistics, such as bytes in and bytes out, from the firewall interfaces using SNMP or NetFlow. NPM then calculates bandwidth consumption based on the total amount of bytes coming through the firewall over a given time interval. Bandwidth consumption is expressed as a percentage of the interface speed. For example, if a firewall interface has a speed of 100 Mbps and NPM polls 10 MB of bytes in and 10 MB of bytes out in one minute, the bandwidth consumption is 20% [(10 MB + 10 MB) / 100 Mbps * 100%]1. References: Monitor firewalls with NPM, Calculate bandwidth utilization on an interface

According to the SolarWinds Platform Agent requirements, the average resource consumption of an agent is less than 1% CPU, max 1 MB of memory, and 1 MB storage on the target computer. The agent software is designed to be lightweight and efficient, and does not impact the performance of the monitored devices. The other options are incorrect, as they either overestimate or underestimate the resource consumption of the agent, or imply that the agent does not use any local resources at all. References: SolarWinds Platform Agent requirements, section “SolarWinds Platform Agent resource consumption”.

 The best way to monitor an SNMP metric that NPM is not monitoring out-of-the-box is to create a custom poller using the Universal Device Poller (UnDP) tool. A custom poller allows you to monitor specific aspects of your network devices using SNMP, by selecting the OIDs that correspond to the metrics you want to collect. You can then assign the custom poller to the devices you want to monitor, and view the results in the Orion Web Console, as charts, tables, or gauges. You can also use custom pollers to create alerts and reports based on the collected data. References: Monitor custom statistics based on OIDs with Universal Device Pollers in NPM, Create a custom poller, Assign Universal Device Pollers to devices monitored in NPM

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

The Universal Device Poller (UnDP) is a feature of SolarWinds NPM that allows you to create custom monitors for almost any statistic provided by SNMP based on its Management Information Base (MIB) and object identifier (OID). An OID is a unique identifier for a variable that can be polled or set via SNMP. The UnDP retrieves management data in the OID format from the devices that support SNMP. The other formats (WMI, XML, ANSI 1) are not used by the UnDP. References:

• Monitor custom statistics based on OIDs with Universal Device Pollers
• NPM Universal Device Pollers

 Capacity Forecast Charts in NPM show the usage trends and forecasts for nodes, interfaces, and volumes based on historical data. By default, 7 days of data are required to generate these charts1. You can change this setting globally or individually for each object2. Capacity Forecast Charts are available for the following metrics: CPU utilization, memory usage, space usage, receive utilization, and transmit utilization3. References: 1: Monitor capacity usage trends on the network and forecast capacity issues in NPM - Capacity forecasting is available for nodes, interfaces, and volumes that meet the following requirements 2: Change capacity forecasting settings globally in NPM - Change the number of days of historical data required for capacity forecasting 3: Monitor capacity usage trends on the network and forecast capacity issues in NPM - Capacity forecasting is available for the following metrics of monitored nodes, interfaces, and volumes monitored

SNMP (Simple Network Management Protocol) is a protocol that allows network managers to monitor and control network devices using a set of standardized messages and data structures. SNMP uses a client-server model, where the network manager (client) sends requests to the network device (server) and receives responses. The network device has an SNMP agent that collects and reports the data using a MIB (Management Information Base), which is a hierarchical database of variables that describe the device’s status and configuration. Each variable in the MIB has a unique identifier called an OID (Object Identifier), which is a dot-separated sequence of numbers that follows a tree structure12.

To retrieve a single value in SNMP, you can use two types of requests: GET and GET NEXT. A GET request asks for the value of a specific OID, and the SNMP agent responds with the value if it exists, or an error if it does not. A GET NEXT request asks for the value of the next OID in the MIB tree, and the SNMP agent responds with the value and the OID of the next variable, or an error if there is no next variable. A GET NEXT request can be useful for discovering the OIDs and values of a device, or for iterating over a table of values34.

A GET VALUE request is not a valid SNMP request, and a GET TABLE request is not a single request, but a series of GET NEXT requests that retrieve all the values in a table . References: 1: SNMP Basics, 2: SNMP Tutorial Part 1 – Understanding MIBs and OIDs, 3: SNMP Tutorial Part 2 – SNMP Get, GetNext, GetBulk, 4: SNMP Commands, : SNMP Table Operations, : SNMP Table Retrieval

 To monitor tenants in your SDN environment with NPM Cisco ACI monitoring, you need to add an APIC node to NPM and enable API polling on the APIC node. The APIC node is the controller of the ACI system that provides a full view of the SDN environment, including tenants, application profiles, endpoint groups, spine and leaf switches, and their health scores1. By enabling API polling on the APIC node, NPM can collect health and performance data for the ACI entities and display them on the Orion Web Console2. You do not need to enable API polling on all ACI devices, as one APIC node can provide the information for the entire ACI system3. You also do not need to view your SDN environment in Orion Maps, as this is an optional feature that allows you to visualize the relationships and dependencies among the ACI entities4. References: 1: Monitor Cisco ACI devices in NPM - SolarWinds1 2: Monitor Cisco ACI devices in NPM - Add ACI devices and enable ACI polling1 3: Monitor Cisco ACI devices in NPM - Requirements1 4: Monitor Cisco ACI devices in NPM - View ACI environment on SolarWinds Platform Maps1

To allow the finance department to view select reports from NPM without a user account, you can enable the Link only option on the report. This option allows you to generate a direct link to the report that can be shared with anyone who has access to the Orion Web Console URL, even if they do not have a user account or login credentials. The Link only option also bypasses any report limitations or account restrictions that might apply to the report. To enable the Link only option on a report, you need to edit the report and select the Link only option in the Report Properties page. You can then copy the link and send it to the finance department via email or other methods. The finance department can then view the report by clicking the link and opening it in a web browser1. References: Share a web-based report with non-Orion Platform users

An alert limitation is a filter that restricts the scope of an alert to a specific set of objects, such as nodes, interfaces, applications, or groups. You can use an alert limitation to create an alert that only applies to a select set of nodes in your network, and exclude the rest. To set an alert limitation for the nodes to be included in the alert, follow these steps1:

• Click Alerts & Activity > Alerts > Manage Alerts.
• Find the alert that you want to edit or create a new alert.
• On the Trigger Condition tab, define the condition that triggers the alert, such as Percent Loss is greater than or equal to 50.
• On the Scope of Alert tab, select Limit the scope of this alert to a specific subset of objects.
• Choose the method to define the subset of objects, such as Select objects manually, Use a custom SWQL query, or Use a custom SQL query.
• Select or enter the criteria to filter the objects, such as the node name, IP address, group, custom property, or any other attribute.
• Click Add Selected Objects to add the objects to the alert limitation.
• Click Next and complete the rest of the alert configuration.

You can now save and enable the alert, and it will only notify you when packet loss meets or exceeds 50% for the nodes that you have selected in the alert limitation. References: 1: Limit the objects an alert applies to

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

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 trapsfrom 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

PerfStack is a feature of the Orion Platform that allows you to compare and correlate performance data from multiple SolarWinds products and entities in a single view1. You can drag and drop metrics from different sources, such as NPM, SAM, NCM, NTA, and more, and create custom dashboards that help you troubleshoot complex network issues2. PerfStack can also show historical data and baselines for comparison3. References: 1: Network Performance Monitor Administrator Guide - Use PerfStack to troubleshoot issues 2: Network Performance Monitor Getting Started Guide - Troubleshoot your network with PerfStack 3: SolarWinds Certified Professional Program - Diagnostics and Troubleshooting Exam Study Guide - Use PerfStack to troubleshoot issues

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

 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.

 The easiest and fastest way to change the polling method for multiple nodes is to use the Manage Nodes feature in the web console. You can select up to 1000 nodes at a time and edit their properties in bulk. You can choose the polling method from the available options, such as ICMP, SNMP, WMI, or Agent, and provide the required credentials or settings. This will apply the changes to all the selected nodes without affecting their existing data oralerts. References: Choose the polling method to use in the SolarWinds Platform; Polling Intervals - Best Practices; SOLARWINDS NETWORK PERFORMANCE MONITOR