SolarWinds SCP-NPM Dumps

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

 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

According to the SolarWinds NPM Administrator Guide, custom charts are created using the Orion Web Console and are not compatible with Excel file formats. Therefore, the only option to export a report with custom charts is to use a PDF format. Other report formats, such as HTML, CSV, or TXT, are supported for reports without custom charts. References: SolarWinds NPM Administrator Guide, page 171; Export reports to Excel - Forum, reply by ElisabethZakes; How to Export NPM Report Writer Data to Excel (xls or csv)??? - Forum, reply by borgan.

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

 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

 Account limitations are a way of restricting the access of Orion user accounts to specific network objects, such as nodes, interfaces, groups, maps, or alerts. You can use account limitations to prevent a user from seeing or working with select monitored entities through the SolarWinds server. For example, you can limit a user to see only the nodesin a certain group, or only the maps that they have created. You can apply account limitations to individual users or user groups, and you can choose from predefined limitations or create custom limitations based on custom properties. The other options are not effective ways of limiting user access to monitored entities, as they either affect the monitoring status of the entities (unmanage), the permissions of the entities themselves (configure permissions), or the alerting scope of the entities (configure alert limitations). References:

• Limit user access to network areas with account limitations
• Predefined Orion Platform account limitations
• Create custom account limitations

The Action Manager is a feature of the Orion Platform that allows you to create, edit, and delete actions for scheduled reports1. Actions are the tasks that are performed when a report is generated, such as sending an email, saving a file, or printing a report2. You can use the Action Manager to edit the email address for each action on each report schedule, without affecting the report content or schedule3. References: 1: Network Performance Monitor Administrator Guide - Use the Action Manager 2: Network Performance Monitor Administrator Guide - Schedule a report 3: SolarWinds Certified Professional Program - Reporting Exam Study Guide - Use the Action Manager

Account limitations are a way of restricting the access of Orion user accounts to specific network objects, such as nodes, interfaces, groups, maps, or alerts. You can use account limitations to limit a user to only monitor Windows servers and not be able to view other devices that NPM monitors. For example, you can create a custom limitation based on the node property Operating System, and select only Windows as the value. Then, you can apply this limitation to the user account or user group that you want to restrict. The other options are not effective ways of limiting user access to specific devices, as they either affect the visibility of the entire view (view permissions), the layout of the view (account views), or the scope of the alerts (alert limitations). References:

• Limit user access to network areas with account limitations
• Create custom account limitations

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

Response time is the amount of time it takes for a service request to return a response. It is a critical SLA performance metric for a hosted data center service, as it directly affects the user experience and satisfaction. High response time can indicate network congestion, server overload, or other performance issues that can degrade the quality of the service. By tracking response time, you can monitor the availability and reliability of the service, identify and troubleshoot potential problems, and ensure that the service meets the SLA expectations and standards. References: How to measure your SLA: 5 Metrics you should be Monitoring and Reporting, Data Center SLA Frequently Offer a 100% Uptime Guarantee, How To Measure SLA Performance in 4 Steps (With Tips).

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

 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]

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

 Device Studio Poller is a feature that allows users to create custom pollers for devices or technologies that are not supported by default in NPM. It can poll multiple OIDs for a given technology, perform logical operations or transformations on the polled data, and display the polled values in existing resources. However, it does not collect data from Orion Failover Engine or Hot Standby Engines, which are features of Orion High Availability that ensure continuous monitoring in case of primary server failure12. References: 1: Create pollers in Device Studio for NPM3, 2: When Good OIDs Go Bad: Customizing Device Pollers, 3: Manage Pollers (AKA Device Studio) question

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

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.

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

 By default, Orion NPM retains Syslog messages in the database for seven days before discarding them. This means that any Syslog messages older than seven days are deleted from the database and cannot be viewed or searched in the web console. To change the default Syslog retention period, you need to modify the Database Settings on the Orion Polling Settings page in the web console. You can also use the Database Manager tool to manually delete or archive Syslog messages from the database. References: SolarWinds SCP Study Aid - NPM, page 19; NPM Administrator Guide, page 111.

Orion Maps 2.0 supports displaying Palo Alto firewalls as network devices, along with their interfaces, zones, policies, and traffic data. You can also view the firewall status, alerts, and events on the map. To add a Palo Alto firewall to an Orion Map, you need to have Network Insight for Palo Alto enabled in NPM, and discover the firewall using SNMP and API polling. References: Orion Maps 2.0, New Alerting, and Palo Alto Networks Monitoring - SolarWinds Lab Episode #77, SolarWinds Lab Episode 77: Orion Maps 2.0, New Alerting, and Palo Alto Networks Monitoring - Orange Matter, Network Insight for Palo Alto Networks in NPM

 Web Console maps are interactive and dynamic maps that you can create and customize using the Orion Maps feature in the SolarWinds Platform Web Console. You can display various items on the maps, such as monitored nodes, interfaces and volumes, SAM applications and components, and network links. You can also add custom labels, annotations, and images to themaps. Web Console maps can help you visualize the relationships and dependencies among your network devices and applications, as well as troubleshoot issues and identify root causes. References: Orion Maps, Create and customize maps in the Orion Platform, Orion Maps 2.0, New Alerting, and Palo Alto Networks Monitoring - SolarWinds Lab Episode #77.

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