Free SOLARWINDS-NPM Exam Dumps Preview

Universal Device Pollers (UnDPs) are custom pollers that allow you to monitor specific aspects of your network devices using SNMP. You can apply UnDPs to any object type that supports SNMP polling, such as interfaces, nodes, and volumes. You cannot apply UnDPs to applications, because they are not SNMP-based objects. Applications are monitored using Application Performance Monitor (APM), which uses different methods, such as WMI, scripts, or agents, to collect data.
References:
Monitor custom statistics based on OIDs with Universal Device Pollers in NPM, Assign Universal Device Pollers to devices monitored in NPM, Add and assign Universal Device Pollers

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 browser 1.
References:
Share a web-based report with non-Orion Platform users

Orion Maps show you how entities are connected based on the data collected by the Orion Platform products. To display the connections between the nodes in Orion Maps, you need to enable Layer 2 and Layer 3 topology polling on those nodes. This will allow the Orion Platform to discover the network topology using protocols such as CDP, LLDP, or ARP. You can enable topology polling on individual nodes or in bulk using the Manage Nodes feature in the web console. You can also customize the topology polling settings and frequency on the Orion Polling Settings page.
References:
Intelligent Maps for SolarWinds Platform products
Understand connections on Intelligent Maps in the SolarWinds Platform;
Network Mapping Tool ?Automated Network Mapping | SolarWinds

The Universal Device Poller (UnDP) is a feature that allows users to create custom monitors for almost any statistic provided by SNMP based on its Management Information Base (MIB) and object identifier (OID). However, sometimes the OID that the user wants to monitor may not be available in the MIB tree, either because it is not supported by the device or because the MIB database is outdated. In this case, the user needs to update the MIB database to get the latest MIBs from the SolarWinds website or from the device vendor. This will ensure that the UnDP can find the OID in the MIB tree and poll it successfully 12.
References:
1: Update the SolarWinds MIB Database for the SolarWinds Platform3,
2: Monitor custom
statistics based on OIDs with Universal Device Pollers in the SolarWinds Platform

Explanation:

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

If you want to see a statistic that NPM does not support out of the box, you can use the Manage Pollers feature in Device Studio or the Universal Device Pollers (UnDP) feature to collect the statistics you want from the device. Both features allow you to create custom monitors for almost any statistic provided by SNMP based on its Management Information Base (MIB) and object identifier (OID). You can also assign the custom pollers to specific devices, view the polled data in the Orion Web Console, and use the data in alerts and reports. The difference between the two features is that Manage Pollers is a web-based interface that simplifies the creation and management of custom pollers, while UnDP is a standalone application that offers more advanced options and flexibility. Device templates and application monitor templates are not features that can be used to collect custom statistics from devices, as they are predefined sets of monitors for specific device types or applications that NPM supports out of the box.
References:
Define a custom statistic to monitor in the NPM Manage pollers using Device Studio
[Monitor custom statistics based on OIDs with Universal Device Pollers]

Map status thresholds determine how the status of a map is calculated based on the status of its child objects. If you set the map status threshold to above 50%, it means that the map will be up if more than half of its child objects are up, regardless of the severity of the down objects. This can cause a situation where half of your objects in a nested map are down, but the top level map is up, because the top level map only considers the status of the nested maps, not the individual objects within them. To avoid this, you can lower the map status threshold to a value that reflects the desired level of availability for your network, or use custom map status thresholds to specify different values for different maps.
References:
Set map status thresholds in NPM, Create nested maps in NPM, How to map through a deeply nested array of objects?

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

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 scores 1. 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 system 3. 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 entities 4.
References:
1: Monitor Cisco ACI devices in NPM - SolarWinds1
2: Monitor Cisco ACI devices in NPM -
3: Monitor Cisco ACI devices in NPM - Requirements1
4: Monitor Cisco ACI devices in NPM - View ACI environment on SolarWinds Platform Maps1

For any node you monitor, you cannot use Network Discovery to automatically add child volumes or interfaces for monitoring. Network Discovery is a tool that helps you identify and add new devices to your network, but it does not automatically monitor all the components of the discovered devices. You need to manually select the volumes or interfaces you want to monitor from the list of resources on each node.
You can also use the Network Sonar Results Wizard to filter and add the resources you want to monitor after running a discovery job.
References:
Discover your network with NPM - SolarWinds (see the Monitoring Settings panel section)
Network Discovery Tool - Automated Discovery Software | SolarWinds (see the Monitor Devices section)

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 mismatches 1.
References:
Detect and predict duplex mismatches in NPM
Speed and Duplex Mismatch - Forum

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 charts 1. You can change this setting globally or individually for each object 2. Capacity Forecast Charts are available for the following metrics: CPU utilization, memory usage, space usage, receive utilization, and transmit utilization 3.
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