Please help us understand your organization's thinking on this topic by selecting how much you agree or disagree with the following statement:
"My company would never purchase a SaaS-based monitoring tool to monitor our on-premises IT infrastructure."
Please expand on “Other” and why by adding a comment below.
SolarWinds has Product Upgrade Advisor website which helps users to validate compatibility of product versions.https://customerportal.solarwinds.com/support/product-upgrade-advisor
Do you use that prior any product upgrade?
Do you have a need to detect rogue APs connected to your network?
Tell us your biggest pain point when troubleshooting IT issues, e.g. users complaining about slow or broken access to applications.
Select your biggest pain point from this list.
Of course any additional comment to this page would be great (e.g. second biggest, pain point not listed below...)
Hi All, I am trying to test SNOW Integration with NPM 12.3 and Create ServiceNow Incident action not working as expected:
1. I have added SNOW instance as mentioned on the documentation into SolarWinds.
2. I gave in the required details and created an alert for -> Node Status is equal to Unmanage (which is the trigger condition)
3. Under trigger actions I created a action 'Create ServiceNow Incident' assigned the SNOW instance added in NPM
4. Gave the default fields and submitted the same, without proceeding further from that step i tried to simulate it from trigger actions page, clicked on the lightning symbol which is used for simulate and it successfully created a SNOW ticket, so far so good, hence i assumed this should work fine as simulating the action is working fine and creating a ticket in SNOW.
5. Later i went on to Summary step and saved the alert.
6. An alert fired within a minute and i could see it under Active alerts
ISSUE -> A TICKET WASN'T CREATED ON SNOW
What should i look for now ? Which log in SolarWinds would provide some additional info on the same, would MacroParser log help or ?
If someone has faced a similar issue, please do help me with the remediation, thanks in advance.
Hey all,
So we have pollers in various countries and the main poller in Colorado. Our issue ( mostly with SNMPV3 on our unix servers), is that it says the next polling time is in the future. We noticed that they all have the same 2 issues and it is based on where the poller is timezone wise. So basically if a node is in the US, but the poller is in Germany, the UTC time can be 7 hours difference, or if it is in our asian poller 14 hours difference. Our current thought is to set all the clocks on all the pollers, regardless of location to MDT. We have experimented with moving those nodes back to our Colorado poller and boom the time seems to fix itself, but moving them back to the other pollers restarts the issue. Any thoughts that are better than this?
I am wondering why the discussion Solarwinds is now horribly unstable. is locked? For an ongoing issue that we also are experiencing, why would thwack moderators choose to lock the discussion and prevent other customers from weighing in, and asking questions? I am attempting to apply the work around in the post, but I wanted to open another thread since the other one is locked. Hopefuly other customers that have upgraded to 12.3 can communicate on thwack. I found that the memory of the Cortex service was using 24-29GB of the 32GB available on the server of my primary poller, and it causes the web console and polling to not function. I'll reply back to this thread after I apply the proposed work-around on the other thread linked above.
OUR ENVIRONMENT: Primay Poller (HA Primary), 18 Additional Pollers (9 Active / 9 HA), 2 AWS, Physical SQL Server with 32 cores, 148 GB Memory, Raid 10 LUNs on 3 Par with SSD.
Network Elements
| TOTAL COUNT | 81350 |
| NODES | 5264 |
| INTERFACES | 51321 |
| VOLUMES | 24765 |
How to check the vulnerability of solarwinds application in terms of security.
Hi All,
I am curious to know like if the node is down then why we are not getting the message like Node status is now why frequently generating the alert as abcd.com has stopped responding (Request timeout). there should be Node status down.
Node status.
SNOW alert details- Not triggered alert as SNOW ticket, while its already configured.
I'm trying to connect Atlas to Orion Network Atlas but it gets stuck on connecting.
We're running version 12.1 of NPM.
I just finished a build out of NPM 12.3 using fresh Server 2016 VMs. I was testing out some new weather maps for our new main dashboard and I'm getting an error on the Network Atlas when I link to the National Weather Service's radar. I am getting the error "no image could be found at the specified location." It works fine in IE on the server.
Is anyone else getting an error on their environment with this link?
Installed NPM 12 today and found I am only able to make one edit to any alert before the 'Manage Alert's > Alert Manager' display area goes into a refresh loop for about ninety seconds to three minutes and am unable to manage any of the alerts. The 'Action Manager' tab does not exhibit this behavior. Setting a different value on the 'Group By' dropdown seems to shorten the amount of time on the refreshes. We've also found using the search field before making any edits seems to prevent the refreshes from occurring.
How I reproduced it:
1.) Click Settings>Manage Alerts
2.) Select the first alert I see and click the 'Edit Alert' button.
3.) When the Alert wizard finishes loading, click the 'Cancel' button.
4.) Sit back and watch the refreshes fly.
What we did to try and fix it:
Any thoughts or suggestions would be appreciated.
Those that have been part of the Thwack Community a while may be familiar with the long running Tell us your "Unknown" devices! thread which had been active since 2007. That thread had become too unwieldy, and most of the user submissions had been implemented many years ago. I recently reviewed each and every posting in that thread, verified what had been implemented in-product, and which ones had not so they could be included in a forthcoming release. With that done, it was time to lock that thread for good and start anew. This time, providing a bit more guidance along the way to ensure everyone is successful in providing the necessary information required to properly identify these devices.
Orion does its best to automatically identify and classify nodes as they're added to Orion. There are however, new device types and models released all the time. It's entirely possible you might be managing a device right now that Orion is unable to properly identify. You can find these easily by going to [Settings - Manage Nodes], changing the 'Group by:' option to 'Machine Type' and clicking on the 'Unknown' category. It's also helpful to add the 'Polling Method' column to the layout, as this thread pertains exclusively to SNMP managed nodes.
Any SNMP managed nodes listed under the 'Unknown' Machine Type category are prime candidates for submission to this thread. All that's required is that you provide the devices SNMP System Object Identifier (SysObjectID), as well as the Make & Model of the device associated with that SysObjectID. This post is an excellent example of the perfect submission.
I have yet to find a clearer definition for what the SysObjectID (System Object Identifier) is then the following excerpt which can typically be found written in virtually every vendor's MIB file verbatim.
Object Name: sysObjectID Object ID: 1.3.6.1.2.1.1.2.0 Object Syntax: OBJECT IDENTIFIER Object Access: read-only Object Status: mandatory Object Description: The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.
Essentially, it's a string of numbers in dotted notation that is (hopefully) unique to at least the manufacturer, and in most cases, to the specific make and model of the device being monitored. It's how we identify for example, that the device vendor is 'Cisco' and the model is a 'Nexus C7018'. All System Object ID's begin with '1.3.6.1.4.1' followed by a number which uniquely identifies the manufacturer. The numbers which then follow typically identify the specific model of the device.
If the device is already managed as a Node in Orion then you can locate the SysObjectID in the 'Node Details' resource as shown below, when viewing the node in the Orion web interface.
| Node Details | NET-SNMP |
|---|---|
 | Alternatively, you can use NET-SNMP to query the following SNMP OID to return the unique SysObjectID.
1.3.6.1.2.1.1.2.0
Below is an example of the 'snmpget' command line arguments which will return you the SysObjectID for the device.
snmpget -v2c -On -c public 10.199.5.103 1.3.6.1.2.1.1.2.0
The example above is executed against a device with the IP address of '10.199.5.103' using SNMPv2c, with the community string 'public'. Below is a screenshot of the resulting output from that command. The string of numbers and periods highlighted in yellow below is this device's unique SysObjectID.
|
Linux hosts, virtual appliances, and even some network equipment built on Linux, FreeBSD, etc. are often identified as 'NET-SNMP'. This is because the SNMP Daemon running on those hosts is, you guessed it, NET-SNMP. Unfortunately, these vendors for some reason, have chosen not to implement their own unique SysObjectID, and instead kept the default SysObjectID '1.3.6.1.4.1.8072.3.2.10' which is designated for NET-SNMP. If you have a device such as this, fret not. There are a few options available to you if you'd like these devices to be properly identified by their appropriate vendor's make & model within Orion.
The easiest solution would be to install the Orion Linux Agent on the device which is reporting itself to be 'NET-SNMP'. The Linux Agent does not rely upon SNMP to identify the machine type or vendor. Instead, the Agent will report the Vendor as 'Linux' and the 'Machine Type' as the Linux distribution running on the device as depicted in the screenshots below.
| Red Hat | Citrix XenServer |
|---|---|
 |  |
Another approach is to customize NET-SNMP and Orion to properly reflect the Vendor and Machine Type. Simply following the steps outlined by adatole's post entitled No More Net-SNMP Nodes. This method uses a script osname.sh which is executed when a particular OID is is queried. Next, you would create a custom Device Poller to query that newly created OID and populate the Machine Type value in Orion for that device.
If you find it more fun to follow along, you can watch adatole walk you through the entire process in the following video.
While it would be nice if that's how it worked, unfortunately many (or most) vendors don't include this information within their MIB files. MIB files include a listing of all possible OIDs which could be polled across a wide variety of different devices (typically an entire product family), but it doesn't include the values which are returned by the devices (Enums notwithstanding). For that reason we need users, such as yourself, to post the SysObjectID's in this thread, along with the device vendor and model information so it can be included in our database.
If you'd still like your device's MIB file included in the Orion MIB database, for use with Network Performance Monitor's Universal Device Poller, or the Orion Platform's SNMP Trap Receiver, simply follow the steps outlined in KB article at the link below. The latest version of the MIB database, containing your submissions, can always be downloaded from within the Customer Portal.
Hello all,
So far, we have integrated SolarWinds 9.1 with SCOM 2007 SP1 using Orion MP, which was first big step. Our goal was to collect performance metrics such as CPULoad and PercentMemUsed (For Non Microsoft products) from SolarWinds and keep it in SCOM-DW repository for reporting.
It looks like "Collect Device Data from Orion" does the collection of the above mentioned metrics. This rule is targeted against "SolarWinds.Orion.SCOM.Node" and "SolarWinds.Orion.SCOM.Interface" objects. We are only interested in Node metrics. So the format of the perf counter that is collected by the rule to my understanding is "Object\Counter\Instance" as shown below:
- SolarWinds.Orion.SCOM.Node\CPULoad\10.10.10.1- SolarWinds.Orion.SCOM.Node\PercentMemUsed\10.10.10.1
It looks like "Collect Device Data from Orion" rule is supposed to write data in OperationsManager and OperationsManagerDW databases. I verified this by opening the MP where it is clearly evident that the rule is writing to both DB:
<WriteAction ID="WriteToDB" TypeID="SC!Microsoft.SystemCenter.CollectPerformanceData" /><WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishPerformanceData" /> .
I also verified that the CPULoad and PercentMemUsed data are written only to OperationsManager database. However, I don't see the same data in DataWarehouse. Has anyone come across this issue, is there an easy way to verify that the Orion data is written to DW and how do I fix this? Thanks in advance. Dipu
Anyone having this issue after upgrading to 12.3?
| Hardware polling failed: Error 31224 - Crypto Error - Unable to perform the requested algorithm. If FIPS restrictions are enabled, please select a FIPS compliant algorithm. |
I have a ticket in with Solarwinds #00144449 but no one has picked it up yet.
Polling server is Windows Server 2016 Standard
SQL server is Windows Server 2016 Standard running SQL Server 2012
So I'm on day three of what was suposed to be a simple upgrade. I'm taking NPM 12.1 to 12.2 and SAM 6.4 to 6.6 while removing some products where the license has expired or we aren't finding useful at this time. Additionally, I was looking to eval WPM so I added it to the install list. The first problem I ran into was the installer stuck at "Importing Sample Maps". Initially I removed IPAM and tried again with no luck. Then I removed NCM, VNQM, and UDT. This got me past that point but, there were issues with the web site setup. I ended up blowing away the website completely and allowing the Configuration Wizard to rebuild it. That seemed to work. At this point I had a working primary/core. My envinorment has the Primary, 2-2APEs, and one remote APE. I took the provided installer from the Primary and placed them on the APEs. Initally, they complained that my APE licenses, active and due to expire in 3/2019 according to my Customer Portal, where not active. I made multiple failed attempts through the Primary to sync licenses via the portal provided License Manager. Following a link about reseting licenses, I ended up downoading/installing a standalone license manager tool to the APE. This didn't work either. I tried the same on the Primary which also didn't work. Support tells me that this corrupted me so I guess don't do that!. Support walked me through the deactivation of all my product licenses. I'm told this was neccessary because the sync would not work with the EVAL status that WPM was in. For purposes of getting through this I decided to uninstall WPM. Still, none of my licensed product would reactivate. Support got some license expert on thier end who did some license reseting on thier end and using the portal provided License Manager, I was able to reactivate NPM and SAM but, had to manually add the APEs. There was no sign of WPM so I figured we were good. By my way of thinking we have a working Primary with NPM and SAM. I went to each of the APES and placed the provided installer on them. When running the installer it would fail at a point where it was trying to download a file "UpgradeFix.exe" from the main server. Looking at the installer log file, this was a file supposedly at downloads.solarwinds.com. From each of the APEs, I had no issues using IE to go to that wesite and downloading the file. So I have to assume the its actually trying to get the file from the Primary but, that file does not exist anywhere on it, nor could I figure our where I could put the file where the APE upgrade installer would find it. Support tells me that this file is related to WPM and there must still be remanents of WPM on my Primary. So they send me a "Burn" script. Basically this script wipes the server of any and all Solarwinds products completely. So I run this on the working Primary. After a considerable amount of time it completes. You are admentaly warned not to interrupt the process. I reboot after the burn and reinstall selecting only NPM and SAM, fight through some website configuration issues ending up with a working Primary except for the annoying IE security prompt when opening the UI, which I still have but, will resolve later...I hope. So again, back to the APEs, using the SW portal on an APE, I navigate to the Polling Engines setting and download an installer. When I run it, it pases all the checks but, there it is again, WPM. The installer intends to place WPM on the APE even though there is no WPM. I can't get rid of this thing. I have combed through the Primary removing any and all mentions of WPM from the registry. I have no idea where else to look or what else to do. I've listed this as a question in hopes maybe someone else has had a similar issue and was able to resovle it. Support will get back to me around 1pm my time today after reviewing all the diagnotic information I have provided but, I thought I reach out here to see if I could find some more ideas.
2018-05-22 18:36:16,879 [17] DEBUG (null) SolarWinds.Administration.SystemInfoCollector.Detectors.InstalledProductsDetector.InstalledModulesDetector - Modules detected in msi library: ACTIVEDIAGNOSTICS:1.8.0.287, COLLECTOR:2.13.0.292, CORE:2017.3.5320.1819, CORTEX:1.0.0.4329, DPAIM:11.1.0.1191, DPI:2.4.0.182, HA:2017.3.1.851, JOBENGINE:2.11.0.328, MIBS:1.0.43.0, NETPATH:1.1.1.4015, NETWORKATLAS:1.17.0.177, NPM:12.2.5300.1871, ORIONHA:2017.3.1.3303, ORIONIMPROVEMENT:2.8.0.196, RABBITMQ:1.1.40.0, RECOMMENDATIONS:1.4.0.4855, SAM:6.6.0.3735, SQLCE35:3.5.8080.0, SQLNATIVECLIENT2008:10.0.1600.22, SQLSMO2012:11.0.2100.60, SWA:1.3.0.339, SWIS:2017.3.0.710, VIM:8.2.0.7071, WINPCAPSILENT:4.1.3.3024, WPM:2.2.1.0
This is from the AdminstrativeService log on the Primary, which I beleive the APE installer is using to understand what it shold put on the APE.
Hi Team,
I have to rebuild an APE. The platform version is 2017.3 HF3
While reinstalling the APE on a new box, we are getting the error: Algorithm has stuck! Unable to install any product on setup.
Is there any other way to install or I have to choose the legacy version?
Which configurations are required for logging in to Huawei ONT HG8245Q2 through web pages?
