SCP HCO Fundamental Study Guide for 1.2 PDF

7/23/24, 5:42 PM Add a single node for monitoring to the SolarWinds Platform Search SolarWinds Platform Documentation  Add a single node for monitoring to the...

7/23/24, 5:42 PM Add a single node for monitoring to the SolarWinds Platform Search SolarWinds Platform Documentation  Add a single node for monitoring to the SolarWinds Platform This topic applies to all SolarWinds Platform products. See this video: Adding Nodes Manually. As an alternative to using the Network Sonar Discovery wizard, you can add individual nodes for monitoring. Adding a single node offers more detail in monitoring and is recommended for nodes with high latency. Do not include nodes with high latency in a discovery job. As you add a single node for monitoring, you can: Select the statistics and resources to monitor. Add Universal Device Pollers. Specify how often the node status, monitored statistics, or topology details are updated. Add custom properties. Edit alert thresholds. To add a single node for monitoring: 1. Log in to the SolarWinds Platform Web Console as administrator. 2. Click Settings > Manage Nodes, and then click Add a Node. 3. Specify the node, and click Next. a. Provide the host name or IP address. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-adding-devices-for-monitoring-in-the-web-console-sw851.htm 1/3 7/23/24, 5:42 PM Add a single node for monitoring to the SolarWinds Platform b. Select the polling method, and provide credentials. 4. Select the statistics and resources to monitor on the node, and click Next. 5. If you have defined a custom poller and want to monitor the metric on the node, select the poller on the Add Pollers pane, and click Next. 6. Review and adjust the device properties. a. To edit the SNMP settings, change the values, and click Test. b. To edit how often the node status, monitored statistics, or topology details are updated, change the values in the Polling area. For critical nodes, you may need to poll status information or collect statistics more frequently than the default polling intervals. Change the polling intervals if polling the nodes takes too long. c. Enter values for custom properties for the node. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-adding-devices-for-monitoring-in-the-web-console-sw851.htm 2/3 7/23/24, 5:42 PM Add a single node for monitoring to the SolarWinds Platform The Custom Properties area is empty if you have not defined any custom properties for the monitored nodes. See Create a custom property in the SolarWinds Platform. d. To adjust when the status of the node changes to Warning or Critical, edit alerting thresholds for the metric. Select the Override box and set thresholds specific for the node. 7. Click OK, Add Node. The node will be monitored according to the options you set. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-adding-devices-for-monitoring-in-the-web-console-sw851.htm 3/3 7/23/24, 5:42 PM How to delete a node from the Orion Website (https://support.solarwinds.com/) SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy (https://www.solarwinds.com/cookies). Hide this Message Select your Preferred Language from the below list English (US) NETWORK MANAGEMENT (/SUCCESSCENTER/S/TOPIC/0TO2J000… How to delete a node from the Orion Website This article provides information about what happens when a monitored object is deleted from Solarwinds Orion web console. Sep 23, 2021 Success Center FIRST PUBLISHED DATE 10/3/2019 9:46 PM LAST PUBLISHED DATE 9/23/2021 3:45 AM OVERVIEW There comes scenarios where you no longer need to monitor one ore more node(s) in your environment or you have to replace old hardware with new one from new vendor may be. ENVIRONMENT NPM 2022.3;NPM 2022.4;NPM 2023.1;NPM 2023.2;NPM 2023.4 CAUSE Want to delete de-commissioned nodes/devices or replace with new vendor RESOLUTION Delete Nodes in Node Management (Classic View) 1. Log in to the Orion web console. 2. Navigate to Orion Website Administration by clicking on Settings. 3. Click on Manage Nodes under Node & Group Management. https://support.solarwinds.com/SuccessCenter/s/article/How-to-delete-a-node-from-Orion?language=en_US 1/5 7/23/24, 5:42 PM How to delete a node from the Orion Website 4. Search for the node by typing the node name. 5. Select a node by checking the box next to it. Do not click on the node itself because that will take you to the Node Details Summary page. 6. Click on the Delete button in the upper-right corner of the toolbar. 7. You will be prompted with Are you sure you want to delete the selected item?. 8. Click on Yes. Delete Nodes in Manage Entities (Modern Dashboard View) 1. Log in to the Orion Web Console as an administrator. 2. Click Settings > Manage Nodes. 3. On the Manage Entities Pages 4. Select the node or nodes to delete 5. Click on MORE on the Manage Entities menu 6. Next on the MORE menu, Click Delete 7. In the Delete Entities Windows (Are you sure want to delete selected entity?) Click Delete. https://support.solarwinds.com/SuccessCenter/s/article/How-to-delete-a-node-from-Orion?language=en_US 2/5 7/23/24, 5:42 PM How to delete a node from the Orion Website Delete Managed Agent Nodes in Orion platform 1. Log in to the Orion Web Console as an administrator. 2. Click Settings > Manage Agents 3. Search for the agent name and Select the agent and press Delete button 4. Then follow one of the above methods to delete this agent node from Managed Nodes / Manage Entities Note: Once the node is removed - all applications, interfaces and volumes monitored on that node are removed from monitoring. The node and associated objects related to that node will be completely removed from the database during DB maintenance which happens at 2:15 AM by default but it can be run anytime by launching the Database Maintenance application. Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any. Did you know? Solarwinds offers fully functional free trials of all of our products, from network and systems management to IT Security and Database Monitoring https://support.solarwinds.com/SuccessCenter/s/article/How-to-delete-a-node-from-Orion?language=en_US 3/5 7/23/24, 5:42 PM How to delete a node from the Orion Website FREE TRIALS AND DOWNLOADS (HTTPS://WWW.SOLARWINDS.COM/DOWNLOADS? LEC-DFT-CSC-SW_WW_X_PP_X_LD_EN_CSCDYK_X-ORIO- 20200600_ARTICLE_X_X_VIDNO_X-X) Related Articles No related articles yet Articles are related if tend to be read by the same people We'd like to hear from you. Please submit this form to provide feedback to the Success Center team.  We’re Geekbuilt.® Developed by network and systems engineers who know what it takes to manage today's dynamic IT environments, SolarWinds has a deep connection to the IT community. The result? IT management products that are effective, accessible, and easy to use. https://support.solarwinds.com/SuccessCenter/s/article/How-to-delete-a-node-from-Orion?language=en_US 4/5 7/23/24, 5:42 PM How to delete a node from the Orion Website (https://www.facebook.com/SolarWinds) (https://twitter.com/solarwinds) (https://www.youtube.com/user/solarwindsinc) (https://www.linkedin.com/company/solarwinds) COMPANY FOR CUSTOMERS (HTTPS://WWW.SOLARWINDS.COM/COMPANY/H (HTTPS://CUSTOMERPORTAL.SOLARWINDS.COM/ OME) ) INVESTORS FOR GOVERNMENT (HTTPS://INVESTORS.SOLARWINDS.COM/OVERVI (HTTPS://WWW.SOLARWINDS.COM/FEDERAL- EW/DEFAULT.ASPX) GOVERNMENT/IT-MANAGEMENT-SOLUTIONS-FOR- GOVERNMENT) CAREER CENTER (HTTPS://SOLARWINDS.JOBS/) GDPR RESOURCE CENTER RESOURCE CENTER (HTTPS://WWW.SOLARWINDS.COM/GENERAL- (HTTPS://WWW.SOLARWINDS.COM/RESOURCES) DATA-PROTECTION-REGULATION-CORE-IT) EMAIL PREFERENCE CENTER SOLARWINDS TRUST CENTER (HTTPS://LAUNCH.SOLARWINDS.COM/SUBSCRIP (HTTPS://WWW.SOLARWINDS.COM/TRUST- TION-CENTER.HTML) CENTER) Legal Documents (https://www.solarwinds.com/legal/legal-documents) Privacy (https://www.solarwinds.com/legal/privacy) California Privacy Rights (https://www.solarwinds.com/legal/privacy#california-privacy-rights) Security Information (https://www.solarwinds.com/information-security) Documentation & Uninstall Information (https://support.solarwinds.com/SuccessCenter/s/?language=en_US) Sitemap (/sitemap.xml) © 2024 SolarWinds Worldwide, LLC. All rights reserved. https://support.solarwinds.com/SuccessCenter/s/article/How-to-delete-a-node-from-Orion?language=en_US 5/5 7/23/24, 5:42 PM Calculate node status in the SolarWinds Platform Search SolarWinds Platform Documentation  Calculate node status in the SolarWinds Platform This topic applies to all SolarWinds Platform products. By default, node status is detected using ICMP: The SolarWinds Platform sends a ping request. If the SolarWinds Platform does not receive the response, it places the node into the Warning state and fast-polls the device for 120 seconds. If the node still does not respond, the SolarWinds Platform notifies you that the node is Down. ICMP only tells you the SolarWinds Platform did not receive a response for the ping request. The device could be down, but there might also be a routing problem, an intermediary device could be down, or something could have blocked the packet on its way to or from the device. See Get more details about the node in the NPM Getting Started Guide for more details. Status of sub-elements, such as interfaces and volumes, is detected using SNMP. This is more accurate, because the device tells you that the sub-element is Down. SolarWinds Platform status options Icon Status name critical down external unknown unmanaged unreachable up warning https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-calculate-node-status.htm 1/6 7/23/24, 5:42 PM Calculate node status in the SolarWinds Platform Enhanced node status - what does it mean? In Orion Platform 2018.4 and earlier, the node status icon consisted of two circles - the large one reflected whether the node was up or down, the small one provided information about additional metrics. Starting with Orion Platform 2019.2, you can keep using this "classic" method for calculating node status, or switch to the "enhanced" node status calculation where you can select what "contributors" are reflected in the status. A contributor is a status of a metric or feature that can influence the node status, such as the status of an interface, a hardware health sensor, or even a threshold. Based on your settings, the following items might be reflected in node status: Node thresholds: Both global thresholds and thresholds specified for individual nodes are now reflected in the node status. Child objects: The status of interfaces, hardware health, or applications monitored on a node is reflected in the node status. Where can you see a change when you switch to the enhanced node status calculation? Intelligent Maps: The status of mapped objects reflects the status of components used to calculate the node status. Groups: With enhanced status calculation, you can only use nodes to form a group. Status of all child objects associated with them will be reflected in the node status. Alerts: Thresholds and child objects now influence node status so you no longer need alert definitions for individual metrics or child entities. To keep you informed about what went wrong, new macros for root cause were added: ${N=SwisEntity;M=NodeStatusRootCause} ${N=SwisEntity;M=NodeStatusRootCauseWithLinks} If you add these variables to the trigger action message, the notification will include any node thresholds which have been crossed, as well as a list of all child objects in a degraded state associated with the node. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-calculate-node-status.htm 2/6 7/23/24, 5:42 PM Calculate node status in the SolarWinds Platform Node tooltips: If you position your cursor over a node in the critical status in any widget, the child entities causing the problem are listed at the bottom of the tooltip. Configure enhanced mode The enhanced node status calculation is enabled by default on new installations. If you upgraded from a previous SolarWinds Platform version, you might need to configure the feature. Before you enable enhanced status calculation, SolarWinds recommends that you disable alert actions in the Alert Manager. Click Alerts & Activity > Alerts, and click More > Pause actions of all alerts. After you enable the feature, check active alert, tweak the alerts that should not trigger, and re-enable alert actions. 1. Enable the feature. 2. Specify what should influence your node status. This step is optional, as SolarWinds provides with a default combination of enabled contributors. 3. Adjust the status rollup mode for individual nodes. This step is optional. The default option is Mixed status. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-calculate-node-status.htm 3/6 7/23/24, 5:42 PM Calculate node status in the SolarWinds Platform Enable the enhanced node status calculation Starting with Orion Platform 2019.2, this is the default option. 1. Click Settings > All Settings > Polling Settings. 2. Scroll down to Node Status calculation, and select Enhanced. 3. Submit your changes. Specify what should be included in the node status calculation Including a group contributors, such as interfaces, into the node status calculation means that the node status turns to warning when any of the entities on the node is down. 1. Click Settings > All Settings and scroll down to Thresholds & Polling. 2. Click Node Child Status Participation. 3. Review the list of components that can influence the node status. Available items depend on the SolarWinds Platform products you have installed. 4. Enable items to be included in node status calculation. SolarWinds recommends that you keep the default settings. Starting with Orion Platform 2020.2, you can also include volume status into node status calculation. Starting with Orion Platform 2020.2, volume status is enabled in Node status contributors on new installs. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-calculate-node-status.htm 4/6 7/23/24, 5:42 PM Calculate node status in the SolarWinds Platform Exclude specific entities from node status calculation Excluding the status of specific entities, such as interfaces or applications, from node status calculation is not supported. If you do not want a child issue to participate in its parent's status, consider the following options: Remove the entity from monitoring. Unmanage the entity. For details on unmanaging interfaces, see Suspend collecting data for interfaces. Change the parent node's rollup mode not to be affected by this child status. Remove all entities of this type from participating in the node status. Specify how to calculate node status for enhanced calculation You have now defined the components that influence the node status calculation. Decide how to use them in the status calculation. SolarWinds Platform uses status roll-up mode to set how the partial components of node status should be evaluated. Worst The total node status is the worst status among the configured options. Best The total node status is the best status among the configured options. Mixed (default option) The global node status combines all specified contributors. Review the following table: Final Node Status Polled Status Child 1 Status Child 2 Status CRITICAL UP or WARNING UP CRITICAL CRITICAL UP or WARNING DOWN CRITICAL DOWN DOWN ANY ANY WARNING UP or WARNING UP WARNING WARNING UP or WARNING UP DOWN WARNING UP or WARNING UP UNREACHABLE WARNING WARNING UP UNKNOWN WARNING UP or WARNING DOWN WARNING WARNING UP or WARNING DOWN UNKNOWN WARNING UP or WARNING DOWN DOWN WARNING WARNING UNKNOWN UNKNOWN UP UP UP UP https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-calculate-node-status.htm 5/6 7/23/24, 5:42 PM Calculate node status in the SolarWinds Platform Final Node Status Polled Status Child 1 Status Child 2 Status UP UP UP UNKNOWN UP UP UP SHUTDOWN UP UP UNKNOWN UNKNOWN UNMANAGED UNMANAGED ANY ANY UNREACHABLE UNREACHABLE ANY ANY Child status EXTERNAL ANY ANY Change status rollup mode By default, the status rollup mode is set to mixed. To change it, edit it in the settings for individual nodes: 1. Go to the node details page, or select the node on Manage Nodes. 2. Click Edit Node. 3. Select the status rollup mode for the node, and submit your changes. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-calculate-node-status.htm 6/6 7/23/24, 5:43 PM Set general thresholds in the SolarWinds Platform Search SolarWinds Platform Documentation  Set general thresholds in the SolarWinds Platform This SolarWinds Platform topic applies only to the following products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — NAM — NCM — NPM — NTA — SAM — SRM — VMAN — VNQM — WPM Orion general thresholds are used for nodes and volumes in all SolarWinds Platform products. Thresholds set on specific objects are not affected by changes made to general thresholds. 1. Click Settings > All Settings in the menu bar. 2. In the Thresholds and Polling grouping, click Core Thresholds. 3. Enter values for Critical Level or Warning Level for selected thresholds. 4. Click Submit. Monitored thresholds are changed on a global level. To access thresholds for virtual objects, go to Settings, and click Virtualization Thresholds in the Thresholds & Polling grouping. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-setting-orion-general-thresholds-sw2045.htm 1/3 7/23/24, 5:43 PM Set general thresholds in the SolarWinds Platform Disable thresholds Starting with Orion Platform 2019.2, you can disable critical or warning thresholds in your SolarWinds Platform. 1. Click Settings > All Settings in the menu bar. 2. In the Thresholds and Polling grouping, click Core Thresholds. 3. Clear the box for the critical or warning thresholds you want to disable in your system. After the next poll, the disabled thresholds will not be reflected in your SolarWinds Platform. You can override this global setting for individual nodes. Do you want to see a list of General threshold types in the SolarWinds Platform? © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-setting-orion-general-thresholds-sw2045.htm 2/3 7/23/24, 5:43 PM Set general thresholds in the SolarWinds Platform https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-setting-orion-general-thresholds-sw2045.htm 3/3 7/23/24, 5:43 PM Create a dependency between network objects Search SolarWinds Platform Documentation  Create a dependency between network objects This topic applies to all SolarWinds Platform products. 1. Click Settings > All Settings in the menu bar. 2. In the Node & Group Management grouping, click Manage Dependencies. 3. Click Add New Dependency. 4. Select the parent object or group, and click Next. To define a dependency so that the reported states of child objects depend on the status of multiple parent objects, create a group including all parent objects, and select it on this view. 5. Type a Dependency Name, select the child entities, and click Next. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-creating-a-new-dependency-sw1316.htm 1/3 7/23/24, 5:43 PM Create a dependency between network objects To define a dependency so that the reported states of multiple child objects depend on the status of one or more parent objects, create a group including all child objects, and select it on this view. 6. Review the settings for the dependency. If there are active alerts on child objects, they are listed on this view. 7. Click Submit. The dependency appears on the Manage Dependencies page. This dependency can be used to limit an alert, which is then triggered only for the router that goes down, and not when a monitored device is unreachable because the router is down. You can also display the dependency on custom views in the SolarWinds Platform Web Console. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-creating-a-new-dependency-sw1316.htm 2/3 7/23/24, 5:43 PM Create a dependency between network objects https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-creating-a-new-dependency-sw1316.htm 3/3 7/23/24, 5:44 PM Create dependencies between network objects automatically Search SolarWinds Platform Documentation  Create dependencies between network objects automatically This topic applies to all SolarWinds Platform products. You can choose to calculate dependencies automatically using the Auto Dependency feature. Auto Dependency calculates node-to-node dependencies based on topology connections. First it determines the root node of each polling engine or cluster of connected nodes. Then it determines dependencies using the root node as the base. Since the path followed by each polling engine may be different, a unique path is created for each polling engine. When a cluster is polled by multiple polling engines, dependencies are not created between nodes that are polled by different engines even if they are topologically dependent. Manually created dependencies are always used if there is a conflict between an automatically generated dependency. Automatic dependencies are recalculated when topology is recalculated. Ignored dependencies continue to be ignored when your topology is recalculated. Enable automatic dependencies 1. Click Settings > All Settings in the menu bar. 2. Click Polling Settings in the Thresholds & Polling grouping. 3. Select the Enable Auto Dependencies check box in the Calculations & Thresholds section. 4. Click Submit. Once Auto Dependency has been enabled, dependencies are calculated immediately and are displayed within a few minutes. View automatic dependencies Automatic dependencies are shown along with user-defined dependencies in the All Dependencies resource and in the Manage Dependencies page. Auto dependencies are automatically named with an AutoDep- prefix. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-automatic-dependencies-sw1154.htm 1/3 7/23/24, 5:44 PM Create dependencies between network objects automatically Manage automatic dependencies Changes made to an automatic dependency add audit events to your event log. Automatically calculated dependencies cannot be edited or deleted. 1. Click Settings > All Settings in the menu bar. 2. Click Manage Dependencies in the Node & Group Management grouping. 3. If Auto Dependency has been enabled, the Calculate dependencies automatically icon is toggled on. 4. Automatically calculated dependencies display Calculated Automatically in the Origin column. 5. To show only automatically calculated dependencies, select Dependency Origins from the Group by drop-down menu, and click on Calculated Automatically. Ignore an automatically calculated dependency 1. Select the automatically calculated dependency and click Ignore Auto Dependency. 2. Click Yes, to confirm that you want to ignore the dependency. The automatically calculated dependency is removed from the Manage Dependencies tab and displayed on the Manage Ignored Dependencies tab. The ignored dependency does not affect the child's node status. Restore an ignored automatically calculated dependency 1. Click on Manage Ignored Dependencies. 2. Select the dependency, and click Restore Auto Dependency. The automatically calculated dependencies is removed from the Manage Ignored Dependencies tab and displayed on the Manage Dependencies tab. The dependency is then used when calculating node status. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-automatic-dependencies-sw1154.htm 2/3 7/23/24, 5:44 PM Create dependencies between network objects automatically https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-automatic-dependencies-sw1154.htm 3/3 7/23/24, 5:44 PM Customize thresholds for single objects in the SolarWinds Platform Search SolarWinds Platform Documentation  Customize thresholds for single objects in the SolarWinds Platform This SolarWinds Platform topic applies only to the following products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — NAM — NCM — NPM — NTA — SAM — SRM — VMAN — VNQM — WPM Get notified when polled values on critical devices reach different values than on other objects. For example, set warning and critical thresholds for CPU load on critical devices to a lower percentage than the default settings. 1. Click Settings > All Settings in the menu bar. 2. In the Node & Group Management grouping, click Manage Nodes. 3. Find the node or interface for which you want to set custom thresholds. 4. Select the object, and click Edit Properties. 5. Scroll down to Node Thresholds, select the Override Orion General Thresholds check box by the metric, and provide values for Warning and Critical thresholds. Starting with Orion Platform 2019.2, you can use sustained thresholds and specify how long the condition must be true for the threshold to be exceeded. If you want to use dynamic thresholds, click Use Dynamic Baseline Thresholds. The integer values will be replaced with macros for dynamic thresholds (${USE_BASELINE_WARNING}, ${USE_BASELINE_CRITICAL}). When the polled values for the selected metric cross the thresholds on the object, the object will be highlighted, and appropriate alerts triggered. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-customize-thresholds-per-object.htm 1/3 7/23/24, 5:44 PM Customize thresholds for single objects in the SolarWinds Platform To customize thresholds for virtual objects, go to Settings, and click Manage Virtual Devices in the Node & Group Management grouping. Select a VMware object, click Edit Thresholds, and change the thresholds. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-customize-thresholds-per-object.htm 2/3 7/23/24, 5:44 PM Customize thresholds for single objects in the SolarWinds Platform https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-customize-thresholds-per-object.htm 3/3 7/23/24, 5:44 PM Baselines and baseline calculations in the SolarWinds Platform Search SolarWinds Platform Documentation  Baselines and baseline calculations in the SolarWinds Platform This SolarWinds Platform topic applies only to the following products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced NAM — NPM — NTA — SAM — SRM — VMAN — VNQM — WPM With baselines, you can define what is normal for individual monitored objects based on polled data. By default, the baseline calculator uses the last seven days of collected statistic values to determine what is normal for individual monitored objects. The baseline is calculated using mean and standard deviation. You can use baselines to detect deviations from the average polled values and be alerted on the deviations. Baselines can be displayed on some charts in the SolarWinds Platform Web Console. What data is subject to statistical baseline calculation? Nodes Interfaces Volumes CPU Load Received (Incoming) Errors & Discards Percent Disk Usage Percent Memory Used Transmitted (Outgoing) Errors & Discards Response Time Received (Incoming) Percent Utilization Percent Loss Transmitted (Outgoing) Percent Utilization Use mean and standard deviations as thresholds To get notified when polled values for a node or interface are outside the range specified by mean and standard deviations, set dynamic baseline thresholds. If you have a contextual understanding of the metric you are monitoring, consider defining the thresholds manually. Baselines are calculated values and do not know what is crucial for your environment. 1. Click Settings > Manage Nodes. 2. Locate and select the node or interface, and click Edit Properties. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-orion-baseline-data-calculation.htm 1/3 7/23/24, 5:44 PM Baselines and baseline calculations in the SolarWinds Platform 3. Scroll down to Alerting Thresholds, select Override Orion General Thresholds, click Use Dynamic Baseline Thresholds. Before you use calculated deviations as thresholds, click Latest Baseline Details to review the latest baseline statistics. Mean and standard deviations will now be used as alerting thresholds for the node or interface. Customize how the baseline is calculated A baseline is a period when things are operating normally in your environment. Any anomalies that occur during the baseline period will be calculated into the results and skew the recommended values. If you are aware of an anomaly, re-baseline to ensure that the recommended values are accurate. Consider customizing baselines if significant changes happen that influence what is normal in your environment, such as merging a new company, onboarding a large number of users, or making substantive improvements to the infrastructure. By default, baseline calculations are based on data collected during seven days. Node baseline calculations are performed daily, and interface baseline calculations are performed weekly on Sunday. 1. Log in to the SolarWinds Platform Web Console using an account with administrative privileges. 2. Click Settings > All Settings in the menu bar. 3. In Thresholds & Polling, click Polling Settings. 4. Scroll down to Database Settings, and adjust the number of days in the Baseline Data Collection Duration field so that the time does not include a known deviation from the normal status. The Baseline Data Collection Duration cannot exceed the Detailed Statistics Retention configured in the same section. 5. To change the frequency of calculating interface baselines, choose the Interface Baseline Calculation Frequency. You can customize the calculation frequency only for interface baselines. The number of monitored interfaces is usually much larger than the number of nodes. Calculating baselines for nodes usually does not affect performance as much as performing the same calculations for all monitored interfaces. 6. Click Submit. Your settings will now be used for calculating baselines. If baselines are not calculated the way you expect them to be, see Troubleshoot baseline thresholds. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-orion-baseline-data-calculation.htm 2/3 7/23/24, 5:44 PM Baselines and baseline calculations in the SolarWinds Platform https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-orion-baseline-data-calculation.htm 3/3 7/23/24, 5:45 PM Poll devices with SolarWinds Platform Agents Search SolarWinds Platform Documentation  Poll devices with SolarWinds Platform Agents This topic applies only to the following SolarWinds Platform products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — LA — NAM — NPM — SAM — SCM — SRM — VMAN* An agent is software that provides a communication channel between the SolarWinds Platform server and a Windows or Linux/Unix computer. Products install plugins on agents to collect the data that the agents send back. This can be beneficial in situations such as: Polling hosts and applications behind firewall NAT or proxies. Polling nodes and applications across multiple discrete networks that have overlapping IP address space. Secure, encrypted polling over a single port. Support for low bandwidth, high latency connections. Polling nodes across domains where no domain trusts have been established. Full, end-to-end encryption between the monitored host and the main polling engine. You can monitor servers hosted by cloud-based services such as Amazon EC2, Rackspace, Microsoft Azure, and other Infrastructure as a Service (IaaS). After deployment, all communication between the SolarWinds Platform server and the agent occur over a fixed port. This communication is fully encrypted using 3072-bit TLS encryption. The agent protocol supports NAT traversal and passing through proxy servers that require authentication. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-solarwinds-orion-agents-sw467.htm 1/3 7/23/24, 5:45 PM Poll devices with SolarWinds Platform Agents https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-solarwinds-orion-agents-sw467.htm 2/3 7/23/24, 5:45 PM Poll devices with SolarWinds Platform Agents https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-solarwinds-orion-agents-sw467.htm 3/3 7/23/24, 5:45 PM Agent communication modes Search SolarWinds Platform Documentation  Agent communication modes This topic applies only to the following SolarWinds Platform products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — LA — NAM — NPM — SAM — SCM — SRM — VMAN* Communication modes determine how the agent and the SolarWinds Platform server communicate. This is frequently influenced by where the device you want to monitor is on your network. Server-initiated communication This communication method is also known as a passive agent. Any communication between your SolarWinds Platform server or additional polling engines and the agent is initiated by the SolarWinds Platform server itself. To allow communication from the SolarWinds Platform server, the firewall service running on the monitored device or the network firewall must allow incoming connections through port 17790. If the agent is configured to use another port, update the firewall rules to allow incoming connections from the other port. Agent-initiated communication This communication method is also known as an active agent. In active mode, there are no listening ports on the agent. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-communication-modes.htm 1/3 7/23/24, 5:45 PM Agent communication modes Any communication between your SolarWinds Platform server or additional polling engines and the agent service is initiated by the agent service itself. Update your firewall rules to allow outgoing connections through port 17778 to enable communication between the agent and the SolarWinds Platform server. You cannot use agent-initiated communication through a proxy using NTLM authentication if the agent is running on a Linux/Unix-based device. This communication method is most useful when the agent is installed on a network separated from your SolarWinds Platform server by one or more NAT devices, and you have no easy way to connect the two. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-communication-modes.htm 2/3 7/23/24, 5:45 PM Agent communication modes https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-communication-modes.htm 3/3 7/23/24, 5:45 PM View agent connections and status, update agents, or manage agents Search SolarWinds Platform Documentation  View agent connections and status, update agents, or manage agents This topic applies only to the following SolarWinds Platform products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — LA — NAM — NPM — SAM — SCM — SRM — VMAN* Review agent connection and deployment status. The following steps require Administrator rights. 1. Click Settings > All Settings in the menu bar. 2. Under Node & Group Management, click Manage Agents. The icon displayed next to each Agent/Node indicates the status of the node or an agent icon. The agent icon indicates one of the following: A SolarWinds Platform Agent has been deployed to a server not managed as a node A SolarWinds Platform Agent has been deployed to a managed node but the currently used polling method is not the agent Choose a list of resources and statistics to monitor This is only available for agents that are deployed on nodes. For a Single Agent: Select the nodes, click Choose Resources, and choose items on the node you want to monitor. For Multiple Agents: Select the nodes, click Choose Resources. The server uses Network Sonar Discovery to discover available resources on the agents you have selected. You can choose items on the nodes to monitor. Manage the agent as a new node Select the agent and click Manage as Node. The Add Node page opens and is pre-configured with the agent's details. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-managing-agents-sw449.htm 1/4 7/23/24, 5:45 PM View agent connections and status, update agents, or manage agents View installed agents details Click More Actions > Viewed installed agent plug-ins to view the agent status, connection status, plug-in status, and plug-in version. Click More Actions > View installed plug-ins report to view a report of the same information for all agents. Reboot the node the agent is installed on Click More Actions > Reboot Agent Machine. This button is disabled by default. It is enabled when the installation of an agent requires a system reboot. Update the agent manually If you have disabled automatic updates of agents, you can see Update Required in the Agent Status column of the Manage Agents view when an update is available. Update the agent to ensure compatibility with the version of SolarWinds Platform your agent needs to communicate with. Although agents may continue to work in a limited capacity when an upgrade is pending, SolarWinds recommends that you update the agent at the earliest opportunity. To update an agent: 1. Select the agent. 2. Click More Actions > Update. The agent is updated. The Update button is disabled by default. It is enabled when: Automatic updates for the agent are disabled. The selected agent requires an update. Re-establish a connection to an agent using server-initiated communication The server tries to re-establish the connection to the passive agent when the connection is lost and automatic reconnection fails. This can also be used for connecting to an agent that was deleted but not uninstalled. Click More Actions > Reconnect to passive agent. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-managing-agents-sw449.htm 2/4 7/23/24, 5:45 PM View agent connections and status, update agents, or manage agents Manage Agents table columns The table on the Manage Agents page displays information on the status and connection of your agents. Column Description Agent/Node Name or IP address of the listed node. Agent Status Current status of the listed agent. Connected/OK: Everything is working. Unknown: The agent is connected but no communication is received. If the agent is in the Unknown status for a long time, try renewing the communication. Select the agent and click More > Restart Agent Service. Update Available: The agent version is older than the version on the server and should be updated. Update in Progress: The agent is currently being updated. Reboot Required: The agent needs to be rebooted in order to finish the installation of plug-ins. Reboot in Progress: The agent is currently being rebooted. Once reboot is complete, the agent should finish installation of plugins. Reboot Failed: The agent cannot be rebooted. It may be temporarily offline or there may be some other issue. Restarting: The agent is restarting. Plugin Update Pending: A plugin on the agent has an older version than the one that is on the server and should be updated. Connection Status Current connection status of the listed agent. Connected/OK: The agent is connected. Unknown: The agent management service is not running. Service not Responding: The agent management service is running, but the agent is not connected. Deployment Pending: An agent deployment is going to start, but has not started. Deployment in Progress: The agent is being deployed to the target node. Deployment Failed: Agent deployment failed. Invalid Response: The status displayed if the agent responds in an unexpected manner. Waiting for Connection: The agent was approved, but has yet to connect to the SolarWinds Platform server. Registered On Date when the agent was added to the agent management system. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-managing-agents-sw449.htm 3/4 7/23/24, 5:45 PM View agent connections and status, update agents, or manage agents Column Description Mode Agent communication type: Agent-initiated: The agent initiates the connection to the agent management system. Server-initiated: The agent listens on its designated port for connections from the SolarWinds Platform server. Version Version of the agent software. This is helpful in determining which agents should be updated. When viewing Linux/Unix-based nodes monitored by SolarWinds Platform Agents for Linux/Unix, the table includes additional columns. These columns include the following: Column Header Description Agent - Package Displays the distribution name of the installer package. This is the name of the Distro Name common installer for Linux/Unix distributions. For example, suse displays as the common installer for all 64-bit SUSE distributions. Agent - OS Distro Displays the general distribution name of the Operating System. For example, Name opensuse displays for an installed SUSE distribution. Agent - Operating Displays the installed Operating System name and version. This value will differ System from the package installer version. For example, opensuse 42.1 x64 is the installed OS version for this SUSE distribution. Agent - Package Displays the installation package name and version for the distribution. The Operating installer package version may differ from the installed Operating System version. System For example, suse 10.0 x64 is the package version for this SUSE distribution. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-managing-agents-sw449.htm 4/4 7/23/24, 5:46 PM SolarWinds Platform Agent requirements Search SolarWinds Platform Documentation  SolarWinds Platform Agent requirements This topic applies only to the following SolarWinds Platform products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — LA — NAM — NPM — SAM — SCM — SRM — VMAN* Agent software is free. Licensing occurs through your product and is usually based on the number of monitored elements. Windows agents run as a service. Linux/Unix agents run as a service daemon. Before you deploy agents to a target computer, review the following system requirements. System requirements Account privileges Agent port requirements SolarWinds Platform Agent resource consumption SolarWinds Platform Agent scalability FIPS support FAQs about agent requirements https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 1/8 7/23/24, 5:46 PM SolarWinds Platform Agent requirements System requirements Type Windows Linux/Unix Operating System Windows Server 2008 R2 SP1 Amazon Linux 2 / AMI, 64-bit Windows Server 2012 R2 CentOS 6.x, 32-bit Windows Server 2016 CentOS 6.x, 7.x, 8.x, 64-bit Windows Server 2019 IBM AIX 7.1 and 7.2 Windows Server 2022 Oracle Linux 6.x, 7.x, 8.x, 64-bit Windows 7 Red Hat Enterprise Linux 6.x 9.0 Windows 8.x 32-bit MS Windows 10 Red Hat Enterprise Linux 6.x, 7.x, 8.x, 9.0, 64-bit MS Windows 11 SUSE Linux Enterprise Server Only Pro, Enterprise, and Ultimate 11.x - 15.x, 64-bit workstation SUSE Linux Enterprise Server operating systems editions are supported. 11.x, 32-bit Ubuntu 14.x - 22.x, 64-bit Ubuntu 14.x - 16.x, 32-bit Linux distributions not listed above, such as Debian or Fedora, are not supported. In a TLS 1.2 only environment, the target agent operating system must support TLS 1.2. Hard drive space Approximately 100 MB of hard drive space on the target computer. Other software The following software packages are installed by For Linux, you may need to install the the agent installer if necessary: following manually: Microsoft Visual C++ 2013 Redistributable Python Package for 32-bit or 64-bit Starting with Orion.NET Framework support Platform 2019.4, Python 3 is deployed On operating systems that support.NET automatically to Linux Framework 4.8, all Windows Agent Plugins agents. During upgrades, are migrated to.NET 4.8. all Linux Agent plugins Upon upgrade to 2019.4,.NET 4.8 is are migrated to Python 3. deployed automatically to operating systems Orion Platform 2019.2 that support.NET 4.8. and earlier require Starting with SolarWinds Platform 2022.3, Python 2, versions 2.4.3.NET Framework 4.0 and 4.5 are not and later. supported. The bash shell.NET Framework 4.5 is deployed for Windows Server 2012 with no.NET For AIX: Framework installed You don't need to install Python manually. Required packages are distributed and deployed automatically with the agent plug-ins. Bash or korn shell is required. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 2/8 7/23/24, 5:46 PM SolarWinds Platform Agent requirements Type Windows Linux/Unix Security The DigiCert Root Certificate Authority (CA) must After the agent is installed, it runs be current. This is required because the agent under dedicated swiagent account. software is signed using a DigiCert certificate. To Some actions require root access. install a certificate, see Certificates and the agent in the SolarWinds Platform. After the agent is installed, it runs as a Local System account and does not require administrative permissions to function. Account privileges If you want to deploy agents from the SolarWinds Platform server, the following requirements must be met. Windows The account used for remote deployment must have access to the administrative share on the target computer: \\\admin$\temp. User Account Control (UAC) must either be disabled on the target computer, or the built-in Administrator account must be used. You may need to disable UAC remote restrictions. Other remote or mass deployment methods do not have the same requirements. Linux/Unix An account that can connect remotely through SSH. An account that can install software and create a user and group. See Credentials and privileges used on Linux/Unix-based computers for more information. To deploy a Linux/Unix agent via pull deployment, make sure that the following conditions are met: SolarWinds Platform Web Console must be accessible from the target Linux computer. Pull deployment uses wget, curl, or perl to download the installation files from the chosen polling engine. Agent port requirements The following ports need to be open both to deploy and to update SolarWinds Platform Agents: Target computer where the agent is deployed Server hosting the SolarWinds Platform polling engine Local agent ports https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 3/8 7/23/24, 5:46 PM SolarWinds Platform Agent requirements Target computer Service/ Communication Port Protocol Direction Description OS Process method 22 TCP sshd Inbound Used to install Either Linux/Unix the agent on Agent installer Linux/Unix computers through SSH and SFTP or SCP. 135 TCP Agent installer Inbound (DCE/RPC Either Windows Locator service) Microsoft EPMAP. This port must be open on the target computer for remote deployment. WMI is only needed for deploying the agent to a Windows server with the Add Node or Add Agent wizard. If you do not want to open WMI ports required for software deployment, you can use another deployment method for the Agent. WMI also uses any random TCP port greater than 1024. See WMI portocalypse on THWACK. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 4/8 7/23/24, 5:46 PM SolarWinds Platform Agent requirements Service/ Communication Port Protocol Direction Description OS Process method 445 TCP Agent installer Inbound Microsoft-DS Either Windows SMB file sharing. This port must be open on the target computer (inbound) for remote deployment. 17778 TCP SolarWinds Agent Outbound Used Agent-initiated All continuously by the agent to communicate back to theSolarWinds Platform server. Also used to deploy the agent. 17790 TCP SolarWinds Agent Inbound Used to Server-initiated All communicate with the SolarWinds Platform server. Dynamic UDP SolarWinds.ServiceHost.Process.exe Outbound SolarWinds Either Windows Cortex utilizes two dynamic UDP listening ports from dynamic range (assigned by OS) for SNMP polling. One port is for IPv4 and the second one is for IPv6 (if enabled). SolarWinds Platform server Service/ Communication Port Protocol Direction Description OS Process method 22 TCP n/a Outbound Used to install the agent on Either Linux/Unix Linux/Unix computers through SSH and SFTP or SCP. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 5/8 7/23/24, 5:46 PM SolarWinds Platform Agent requirements Service/ Communication Port Protocol Direction Description OS Process method 17778 TCP Orion Module Inbound Used continuously by the Agent-initiated All Engine agent to communicate back to the SolarWinds Platform SolarWinds server. Also used to deploy Agent the agent. 17790 TCP Orion Module Outbound Used to communicate with Server-initiated All Engine the SolarWinds Platform server. SolarWinds Agent Local Agent ports The following ports are required for local communication inside the server or agent. Do not open them in the firewall; they are used only by local services. Port Protocol Direction Description 17775 TCP Inbound RestAPI forwarder for Cortex (on agents) 17798 TCP Inbound Cortex Diagnostics API (on servers) Dynamic TCP Inbound Port used for communication between the JobEngine and its workers. (on agents) SolarWinds Platform Agent resource consumption Agent resource consumption is variable and depends on what information is collected and how often the information is collected. This is the same as when the data is polled agentlessly, because in most cases, Agents use the same methods for collecting data as agentless polling. Some Linux distributions, such as CentOS, log all cron jobs, including jobs that ensure the agent service is still up and responding. The log file can become large quickly. If your distribution logs all cron jobs, ensure that you use a tool such as logrotate to keep your log files to a manageable size. Resource Consumption CPU Under normal operating conditions, SolarWinds Platform Agent monitoring consumes less than 1% more resources than what would be consumed by monitoring the same node agentlessly. Memory 10 - 100 MB, depending on the number and types of jobs. Bandwidth Roughly 20% (on average) of the bandwidth consumed by the WMI protocol for transmission of the same information. For example, agents use approximately 1.3 kB/s versus WMI at 5.3 kB/s. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 6/8 7/23/24, 5:46 PM SolarWinds Platform Agent requirements SolarWinds Platform Agent scalability SolarWinds Platform Agents Scalability Engine Guidelines Scalability options The achievable SolarWinds Platform Agent scalability varies with actual usage and configuration. Up to 1000 Agents with minimal load have been tested. However, SolarWinds recommends not exceeding 500 agents per polling engine. Using Agent features, such as ADM, SCM, or NetPath, might change scalability limits. For details, see scalability details for individual features. Combining Agents with SolarWinds Platform Collectors reduces the total number of SolarWinds Platform Agents supported per polling engine. For each Collector you use, the Agent scalability is reduced by ten SolarWinds Platform Agents (1 Collector = 10 SolarWinds Platform Agents). FIPS support Starting with Orion Platform 2020.2, SolarWinds Platform Agents support FIPS. To run FIPS-compliant SolarWinds Platform Agents, enable FIPS on the target computer. FIPS is configured both on the main polling engine and on the polled agent computer so all communication between them is FIPS-compliant. Remote deployment in FIPS mode is disabled. To run SolarWinds Platform Agents in FIPS-compliant mode, deploy agents manually (Windows or Linux/Unix). FAQs about agent requirements What authentication method is used by the Agent? What are the minimum required cipher suites for TLS 1.2 agent communications? How do we ensure that only the SolarWinds Platform server can initiate communication to the Agent? What authentication method is used by the SolarWinds Platform Agent? The agent retains the SolarWinds Platform server’s public certificate and uses it for validation. The agent is provisioned with its own certificate for regular operation. The server maintains each agent’s certificate and uses it to verify agent identities. What are the minimum required cipher suites for TLS 1.2 agent communications? Agents use the OpenSSL cypher string TLSv1.2+FIPS:kRSA+FIPS:!eNULL:!aNULL which resolves to: TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any Au=any Enc=CHACHA20/POLY1305(256) Mac=AEAD TLS_AES_128_GCM_SHA256 TLSv1.3 Kx=any Au=any Enc=AESGCM(128) Mac=AEAD TLS_AES_128_CCM_SHA256 TLSv1.3 Kx=any Au=any Enc=AESCCM(128) Mac=AEAD ECDHE-ECDSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AESGCM(256) Mac=AEAD ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD DHE-DSS-AES256-GCM-SHA384 TLSv1.2 Kx=DH Au=DSS Enc=AESGCM(256) Mac=AEAD https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 7/8 7/23/24, 5:46 PM SolarWinds Platform Agent requirements DHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(256) Mac=AEAD ECDHE-ECDSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AESGCM(128) Mac=AEAD ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(128) Mac=AEAD DHE-DSS-AES128-GCM-SHA256 TLSv1.2 Kx=DH Au=DSS Enc=AESGCM(128) Mac=AEAD DHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(128) Mac=AEAD ECDHE-ECDSA-AES256-SHA384 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AES(256) Mac=SHA384 ECDHE-RSA-AES256-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AES(256) Mac=SHA384 DHE-RSA-AES256-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(256) Mac=SHA256 DHE-DSS-AES256-SHA256 TLSv1.2 Kx=DH Au=DSS Enc=AES(256) Mac=SHA256 ECDHE-ECDSA-AES128-SHA256 TLSv1.2 Kx=ECDH Au=ECDSA Enc=AES(128) Mac=SHA256 ECDHE-RSA-AES128-SHA256 TLSv1.2 Kx=ECDH Au=RSA Enc=AES(128) Mac=SHA256 DHE-RSA-AES128-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(128) Mac=SHA256 DHE-DSS-AES128-SHA256 TLSv1.2 Kx=DH Au=DSS Enc=AES(128) Mac=SHA256 RSA-PSK-AES256-GCM-SHA384 TLSv1.2 Kx=RSAPSK Au=RSA Enc=AESGCM(256) Mac=AEAD DHE-PSK-AES256-GCM-SHA384 TLSv1.2 Kx=DHEPSK Au=PSK Enc=AESGCM(256) Mac=AEAD AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD PSK-AES256-GCM-SHA384 TLSv1.2 Kx=PSK Au=PSK Enc=AESGCM(256) Mac=AEAD RSA-PSK-AES128-GCM-SHA256 TLSv1.2 Kx=RSAPSK Au=RSA Enc=AESGCM(128) Mac=AEAD DHE-PSK-AES128-GCM-SHA256 TLSv1.2 Kx=DHEPSK Au=PSK Enc=AESGCM(128) Mac=AEAD AES128-GCM-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(128) Mac=AEAD PSK-AES128-GCM-SHA256 TLSv1.2 Kx=PSK Au=PSK Enc=AESGCM(128) Mac=AEAD AES256-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA256 AES128-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA256 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1 DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA How do we ensure that only the SolarWinds Platform server can initiate communication to the SolarWinds Platform Agent? The agent retains a copy of the public Orion certificate obtained during provisioning. Passive mode uses this to authenticate the server. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-agent-requirements-sw476.htm 8/8 7/23/24, 5:46 PM Node polled by WMI showing down but WMI test passed in SolarWinds NPM (https://support.solarwinds.com/) SolarWinds uses cookies on our websites to facilitate and improve your online experience. By continuing to use our website, you consent to our use of cookies. For further details on cookies, please see our cookies policy (https://www.solarwinds.com/cookies). Hide this Message Select your Preferred Language from the below list English (US) NETWORK MANAGEMENT (/SUCCESSCENTER/S/TOPIC/0TO2J000… Node polled by WMI showing down but WMI test passed in SolarWinds NPM Added a WMI node and when testing the WMI credentials the test was successful but when the node is added to SolarWinds NPM, it shows as down.The node status is determined by ICMP. If unable to ping the node then it will show as down even though you can poll it via WMI. Sep 22, 2022 Success Center FIRST PUBLISHED DATE 11/9/2018 8:20 PM LAST PUBLISHED DATE 9/22/2022 5:12 PM OVERVIEW Added a WMI node, and when testing the WMI credentials, the test is successful but the added node shows as down. ENVIRONMENT NPM 12.5 - EOL;SAM 6.9 - EOL;NPM 2019.4 - EOL;SAM 2019.4 - EOL;NPM 2020.2;SAM 2020.2 CAUSE The node status is determined by ICMP. If unable to ping the node then it will show as down even though you can poll it via WMI. RESOLUTION 1. Test that you can ping the Node from the Orion Server. Node status is determined by ICMP. If you cannot ping the device from the Orion server then it will be marked as down. 2. If ICMP is blocked then change the polling method to Agent polling. https://support.solarwinds.com/SuccessCenter/s/article/Node-polled-by-WMI-showing-down-but-WMI-test-passed-in-SolarWinds-NPM?language=… 1/4 7/23/24, 5:46 PM Node polled by WMI showing down but WMI test passed in SolarWinds NPM About Agents An agent is a software that provides a communication channel between the Orion server and a Windows computer. Agents are used to provide packet-level traffic information about key devices and applications that you specify. This can be beneficial in the following situations: Allows for polling host and applications behind firewall NAT or proxies Polling node and applications across multiple discrete networks that have overlapping IP address space Allows for securely encrypted polling over a single port Support for low bandwidth, high latency connections Polling nodes across domains where no domain trusts have been established Full end-to-end encryption between the monitored host and the Orion poller Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any. Did you know? Solarwinds offers fully functional free trials of all of our products, from network and systems management to IT Security and Database Monitoring FREE TRIALS AND DOWNLOADS (HTTPS://WWW.SOLARWINDS.COM/DOWNLOADS? LEC-DFT-CSC-SW_WW_X_PP_X_LD_EN_CSCDYK_X-ORIO- 20200600_ARTICLE_X_X_VIDNO_X-X) Related Articles No related articles yet Articles are related if tend to be read by the same people https://support.solarwinds.com/SuccessCenter/s/article/Node-polled-by-WMI-showing-down-but-WMI-test-passed-in-SolarWinds-NPM?language=… 2/4 7/23/24, 5:46 PM Node polled by WMI showing down but WMI test passed in SolarWinds NPM We'd like to hear from you. Please submit this form to provide feedback to the Success Center team.  We’re Geekbuilt.® Developed by network and systems engineers who know what it takes to manage today's dynamic IT environments, SolarWinds has a deep connection to the IT community. The result? IT management products that are effective, accessible, and easy to use. (https://www.facebook.com/SolarWinds) (https://twitter.com/solarwinds) (https://www.youtube.com/user/solarwindsinc) (https://www.linkedin.com/company/solarwinds) COMPANY FOR CUSTOMERS (HTTPS://WWW.SOLARWINDS.COM/COMPANY/H (HTTPS://CUSTOMERPORTAL.SOLARWINDS.COM/ OME) ) INVESTORS FOR GOVERNMENT (HTTPS://INVESTORS.SOLARWINDS.COM/OVERVI (HTTPS://WWW.SOLARWINDS.COM/FEDERAL- EW/DEFAULT.ASPX) GOVERNMENT/IT-MANAGEMENT-SOLUTIONS-FOR- GOVERNMENT) CAREER CENTER (HTTPS://SOLARWINDS.JOBS/) GDPR RESOURCE CENTER RESOURCE CENTER (HTTPS://WWW.SOLARWINDS.COM/GENERAL- https://support.solarwinds.com/SuccessCenter/s/article/Node-polled-by-WMI-showing-down-but-WMI-test-passed-in-SolarWinds-NPM?language=… 3/4 7/23/24, 5:46 PM Node polled by WMI showing down but WMI test passed in SolarWinds NPM (HTTPS://WWW.SOLARWINDS.COM/RESOURCES) DATA-PROTECTION-REGULATION-CORE-IT) EMAIL PREFERENCE CENTER SOLARWINDS TRUST CENTER (HTTPS://LAUNCH.SOLARWINDS.COM/SUBSCRIP (HTTPS://WWW.SOLARWINDS.COM/TRUST- TION-CENTER.HTML) CENTER) Legal Documents (https://www.solarwinds.com/legal/legal-documents) Privacy (https://www.solarwinds.com/legal/privacy) California Privacy Rights (https://www.solarwinds.com/legal/privacy#california-privacy-rights) Security Information (https://www.solarwinds.com/information-security) Documentation & Uninstall Information (https://support.solarwinds.com/SuccessCenter/s/?language=en_US) Sitemap (/sitemap.xml) © 2024 SolarWinds Worldwide, LLC. All rights reserved. https://support.solarwinds.com/SuccessCenter/s/article/Node-polled-by-WMI-showing-down-but-WMI-test-passed-in-SolarWinds-NPM?language=… 4/4 7/23/24, 5:47 PM Edit agent connection settings or reprovision the agent once deployed Search SolarWinds Platform Documentation  Edit agent connection settings or reprovision the agent once deployed This topic applies only to the following SolarWinds Platform products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — LA — NAM — NPM — SAM — SCM — SRM — VMAN* You can modify settings such as the communication mode or to which polling engine the agent sends information by modifying the agent on the computer. If the agent loses connectivity to the SolarWinds Platform server, is unable to connect after being manually installed, or if the SolarWinds Platform server has migrated, you can configure the agent's settings directly on the computer you are monitoring. This enables the agent to reconnect to the SolarWinds Platform server. Reprovisioning the agent retains historical data for the node including cpu, memory, and application polled data. Windows devices 1. Log in with an administrator account to the computer with the agent installed on it. 2. Open Orion Agent Settings in the Control Panel. If you get an error when opening Agent Settings in the Control Panel: Navigate to the C:\ProgramData\SolarWinds\Agent directory and Permanently Grant Access to the directory for your user when prompted. Navigate to the agent installation directory (by default C:\Program Files (x86)\SolarWinds\Agent) and Permanently Grant Access to the directory for your user when prompted. 3. Select the Agent Communication Mode. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-editing-agent-settings-in-the-control-panel-sw413.htm 1/3 7/23/24, 5:47 PM Edit agent connection settings or reprovision the agent once deployed 4. Edit the Connection Settings. If you select Orion Server Initiated Communication, you can adjust the Agent Shared Secret: The Agent Shared Secret is provided for security. When you install the agent, you must set a shared secret. When the SolarWinds Platform server connects to the agent, it verifies the secret to connect. Don't use double quotes in the Shared Secret. 5. Click OK to save your changes. 6. If the certificate changed since the last time you provisioned the agent, review the used certificate and confirm it if you trust it. When communication between the agent and the SolarWinds Platform server is successful, the agent is listed on the Manage Agents page with the updated communication mode. Linux/Unix-based devices 1. Log in to the computer with the agent installed on it. 2. Open a terminal window. 3. Run the following command as root: /opt/SolarWinds/Agent/bin/swiagentaid.sh init 4. Configure the agent communication mode and polling engine information. 5. Enter 7 to save your changes. When communication between the agent and the SolarWinds Platform server is successful, the agent is listed on the Manage Agents page with the updated communication mode. © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-editing-agent-settings-in-the-control-panel-sw413.htm 2/3 7/23/24, 5:47 PM Edit agent connection settings or reprovision the agent once deployed https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-editing-agent-settings-in-the-control-panel-sw413.htm 3/3 7/23/24, 5:47 PM Deploy agents to nodes Search SolarWinds Platform Documentation  Deploy agents to nodes This topic applies only to the following SolarWinds Platform products: Hybrid Cloud Observability Essentials — Hybrid Cloud Observability Advanced DPAIM — LA — NAM — NPM — SAM — SCM — SRM — VMAN* Agents provide an additional method to poll devices that are part of a separate network or have intermittent connectivity to the network with your SolarWinds Platform server. SolarWinds Platform products support multiple methods of deploying agent software. Deployment to Raspberry Pi devices may take longer. Before you deploy agents, verify your global agent deployment settings. Software deployment - Deploy the agent software from the SolarWinds Platform server to one or more client computers. Deploy an agent with the Add Node wizard Deploy agents to monitored nodes Manual deployment - Manually move the installer to the remote computer and then install and configure it locally. Deploy the agent manually to a Windows computer Deploy SolarWinds Platform Agents manually to a Linux/Unix-based computer Mass deployment - Mass deploy the agent software to multiple computers using a mass deployment technology, such as Group Policies, SolarWinds Patch Manager, or other automation software. Mass deploy an agent on Windows Deploy agents on Linux/Unix-based computers through a repository Deploy with a Gold Master Image Prerequisites for deploying agents on Windows Core Servers Cloud deployment - Deploy the agent to a computer in the cloud. Manually deploy an agent on Amazon Web Services Automatically deploy a Windows agent to established instances on Amazon Web Services Automatically deploy SolarWinds Platform Agent on Azure VMs Windows Core requires specific setup before you can install the agent software. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-deploying-an-agent-sw422.htm 1/4 7/23/24, 5:47 PM Deploy agents to nodes © 2003-2021 SolarWinds Worldwide, LLC. All rights reserved. https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-deploying-an-agent-sw422.htm 2/4 7/23/24, 5:47 PM Deploy agents to nodes https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-deploying-an-agent-sw422.htm 3/4 7/23/24, 5:47 PM Deploy agents to nodes https://documentation.solarwinds.com/en/success_center/orionplatform/content/core-deploying-an-agent-sw422.htm 4/4