SolarWinds SCP-NPM Dumps

You can make bulk changes to nodes in NPM using the Manage Nodes feature. This allows you to select multiple nodes and edit their properties, such as the polling method, the polling frequency, the SNMP credentials, the custom properties, and more. You can also use the Edit Nodes feature to assign or unassign pollers to nodes, such as the Universal Device Poller (UnDP), the Hardware Health Poller, the Wireless Poller, and more12. References: 1: Change the polling method for a node3, 2: Manage pollers using Device Studio4

 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

To show the connection between two devices on an Orion map, you need to meet the following requirements1:

• The devices must be monitored by NPM.
• The devices must support topology and be interconnected.
• The devices must have the corresponding interfaces monitored and identified as full or half duplex.
• The Orion Maps feature must be enabled and configured.

If you do not see the connection between two devices on an Orion map, you should first verify that you are monitoring Layer 2 and 3 topologies for the devices. You can do this by checking the NPM Network Topology widget on the device details page. This widget will reflect what connections will be automatically drawn in Orion Maps2. If the widget does not show the expected connection, you may need to enable topology polling for the devices or check the SNMP credentials and configuration3.

If you are monitoring the correct topologies and still do not see the connection, you can build a custom connection between the devices using the Orion Maps feature. In the Map Editor, you can add the two devices to the canvas, select them, and click the Connect Objects button. Here you can specify the interface on either side and choose to add the manual connection to the database2.

Building a new Orion map and adding the related entities instead of the nodes will not resolve the issue, as the related entities are based on the same topology data as the nodes. Changing the monitoring method from SNMP to CLI will not resolve the issue, as CLI is not supported for topology polling3.

References: Orion Maps; Orion Map Devices not connect - Forum; Polling methods used by Orion.

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

High Traffic Utilization alerts are triggered when the interface’s received or transmitted percent utilization exceeds a specified threshold. However, this may not reflect the actual network congestion, as traffic spikes can occur momentarily and then subside. To avoid false alerts, you can configure the alert to trigger only when the traffic utilization remains high for a sustained period, such as 5 minutes or more. This way, you can filter out the transient traffic peaks and focus on the persistent issues that affect the network performance. References:

• How do I create a high transmit percent utilization alert to monitor interface bandwidth
• Trouble with High receive percent utilization alert
• How alerts work

 Device Studio is a feature in the SolarWinds Platform Web Console that allows you to create custom pollers for devices or technologies that are not supported by default in NPM. You can use Device Studio to create pollers for CPU and memory, as well as other metrics, by defining the object identifiers (OIDs) and formulas that you want to poll. Device Studio currently supports SNMP and WMI polling technologies, and you can test, assign, and edit your custom pollers from the Manage Pollers page. References: Create pollers in Device Studio for NPM, Device Studio, Device Studio Poller.

The best way to reduce false alerts for high traffic utilization is to configure the alert trigger condition to be more specific and accurate. By setting the alert to trigger only when traffic utilization remains high for a sustained period, you can avoid getting alerted for short-lived spikes that are not a cause for concern. You can use the Time of Day and Trigger Condition options in the alert configuration wizard to define the duration and threshold of the high traffic utilization condition. For example, you can set the alert to trigger only when traffic utilization is greater than 80% for more than 10 minutes during business hours. References:

• How do I create a high transmit percent utilization alert to monitor interface bandwidth - Forum - Network Performance Monitor (NPM) - THWACK Products
• How alerts work - SolarWinds
• SCP Study Aid - SolarWinds (page 8)

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

 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

 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.

One possible reason why you have not received any emails for the high CPU load alert is that the alerts are muted on the devices. Muting alerts means that the alert conditions are still evaluated, but the alert actions are not executed. This can be useful when you want to temporarily suppress notifications for planned maintenance or testing. You can mute alerts for individual nodes, groups, or applications, or for all alerts in the Orion Platform. To check if the alerts are muted on the devices, you can go to the Manage Nodes page and look for the Muted column. You can also use the Mute Alerts widget on the Orion homepage to see the status of alert muting. To unmute alerts, you can either use the same widget or the Unmute Alerts option in the node, group, or application details page. References: Mute alerts, Manage nodes, Mute Alerts widget

 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]

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

 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

 NetPath is a feature of 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. NetPath can analyze paths to any network segment, whether it is on-premise, cloud, or hybrid. NetPath uses distributed monitoring and path analysis to discover how applications are delivered through the network to your users. You can deploy agents on Windows computers that act as synthetic users and use advanced probing to discover and test the network path that traffic takes to any network endpoint, such as your local file print server, your website, or external websites. NetPath can also incorporate data from NPM, NCM, and NTA about your on-premises gear, as well as data from the Internet nodes and providers12. References: 1: Discover your network paths in NPM3, 2: NetPath - Easy Visual Network Path Analysis | SolarWinds4

NPM provides a default report called Top 25 Interfaces by Percent Utilization that shows the interfaces with the highest average utilization over the selected time period1. This report can be easily edited to change the number of interfaces displayed, the time period, the sorting order, the layout, and the filters2. To create a report that shows the top 50 interfaces by percent utilization, you can simply edit this report and change the Limit option from 25 to 503. This is the most time-efficient way to create the report, as it does not require creating a new report from scratch, writing a SQL query, or running the report multiple times for different timeframes. References: 1: Network Performance Monitor Administrator Guide - Top 25 Interfaces by Percent Utilization 2: Network Performance Monitor Administrator Guide - Edit a report 3: Network Performance Monitor Getting Started Guide - Customize a report

 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

NPM provides several default reports that can be used as templates for creating custom reports. One of them is the Top 100 Interfaces by Percent Utilization report, which shows the average and peak utilization of the most used interfaces in the network. To create a report that shows only the top 50 interfaces, you can copy this report and edit it to change the number of rows displayed. You can also modify other parameters such as the time period, the grouping, the sorting, and the filtering criteria. To copy and edit a default report, follow these steps1:

• Click Reports > All Reports > Manage Reports.
• Find the Top 100 Interfaces by Percent Utilization report and click Duplicate & Edit.
• On the Layout Builder panel, click Edit Table.
• On the Edit Resource panel, change the Maximum Number of Rows to 50.
• Optionally, change other settings such as the Time Period, the Group By, the Sort By, and the Filter Results.
• Click Submit.
• Optionally, change the Report Name, the Report Description, and the Report Category.
• Click Next and then Save.

You can now run or schedule the report to show the top 50 interfaces by percent utilization. References: 1: Create a custom report for NPM showing availability of devices in the last 30 days

Orion Maps can automatically display the connections between the devices that are monitored by NPM, based on topology data, manual dependencies, or application dependency mapping. However, if some of the devices are not monitored by NPM, or the connections are not detected by any of these methods, you can manually configure the connections between them in Orion Maps. To do this, you need to drag and drop the desired devices from the Entity Library to the map canvas, and then use the Connect tool to draw lines between them. You can also edit the connection properties, such as name, type, and status, to customize the appearance and behavior of the connections. References: Create and edit Intelligent Maps, Connect objects on maps manually, Intelligent Maps for SolarWinds Platform products

Sometimes, the Orion Platform may not be able to automatically map the connection between your cloud server and on premise router, even if layer 2 and layer 3 topologies are being polled on the devices. This may happen if the devices are separated by a firewall, a VPN, or a NAT device that prevents the Orion Platform from discovering the link information. In such cases, you can manually create a custom connection between the cloud node and the on premise node on the Orion Map. You can also edit the properties of the custom connection, such as the name, the status, the bandwidth, and the utilization. By creating a custom connection, you can visualize and monitor the connection between your cloud server and on premise router on the Orion Map12. References:

• Create custom connections on Orion Maps - SolarWinds
• SCP Study Aid - SolarWinds (page 10)

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

 Bandwidth usage is the amount of data transferred over a network connection in a given time period. It is an indicator of how much traffic is flowing through a network device or link. Peak network traffic is the highest level of bandwidth usage that occurs during a specific time interval, such as an hour, a day, or a week. Monitoring peak network traffic can help you identify potential bottlenecks, plan for capacity, and optimize network performance. NPM can monitor bandwidth usage on nodes and interfaces using SNMP, WMI, or NetFlow protocols. You can view bandwidth usage charts and reports in the web console, as well as set alerts and thresholds for bandwidth utilization. References: Monitor bandwidth usage in NPM; SCP Study Aid - NPM, page 11.