In NPM, normally when the devices are been discovered, all the node details will be captured includes Machine type, system name, Location, Software version, Software image, no of cpu etc..
These details are getting captured for Cisco devices but Software image and software version are not getting captured for Juniper, 3com devices.
Can anyone provide any steps to collect these informations in NPM will be very helpful.
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.
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 |
Hi folks,
I am trying to create a resource that will display Node Notes for Unmanaged nodes.
So far I've tried doing this with a Custom Table and dynamic query builder but I can't find the query for Node Notes.
Only other option it seems is to create a custom swql/sql but I am looking for some help with joining data from NodesData and NodeNotes tables.
I wish to have the following included in the table:
Caption (hyperlinked), StatusLED, Unmanaged From, Unmanaged Until, Node Notes
Any help with this query would be greatly appreciated.
The time has come again for another exciting rundown of some of the improvements and enhancements coming your way in the next major installment of the Orion Platform. For those who may not be familiar, Orion is the foundational component upon which product modules such as Network Performance Monitor (NPM), Server & Application Monitor (SAM), and many others are built atop. Platform capabilities are available to, or can be leveraged by modules which run atop the Orion Platform. In most cases, those enhancements are available regardless of which Orion module(s) you are running, such as PerfStack. In others, it may be something which individual modules can extend to utilize for their own purposes, such as the Orion Agent which has been the basis for delivering amazing new capabilities from NetPath and QoE in NPM, to Application Dependency Mapping (ADM) and IaaS monitoring in SAM.
Several years ago I created a Universal Device Poller (UnDP) for monitoring APC SmartUPS devices, and still to this day it remains amongst one of the most popularly downloaded UnDPs for NPM, if not the most popular. Universal Device Pollers are an incredibly powerful feature of NPM, allowing you to monitor virtually anything about a device which is managed via SNMP. However, there comes a time when certain functionality becomes so ubiquitous that it makes sense to promote it to native functionality of the monitoring solution and not require users to create it themselves. So in this 2018.2 release of the Orion Platform included with NPM 12.3, that's precisely what we set out to do, while also making some improvements along the way.
If you haven't already done so, you'll want to start by adding your APC UPS equipment to Orion. You can do so individually using the 'Add Node Wizard' [Settings > All Settings > Add Node], or in bulk using Sonar Discovery [Settings > All Settings > Discover Network]. If you are adding the devices using the 'Add Node Wizard', you will notice a new option listed for your APC UPS equipment entitled 'UPS'. Checking the box next to this option will enable UPS polling for this device.
| List Resources | Power Control Unit Status Resource | UPS Firmware Version |
|---|---|---|
 |  |  |
Once you've successfully completed the 'Add Node Wizard' and navigate to the 'Node Details' view of your newly added UPS device, you will notice a newly added resource entitled 'Power Control Unit Status'. This resource reflects the most important information about your UPS device, including things such as its overall status, time on battery, and the batteries current charge capacity. This information can, as you would expect, be utilized in Alerts to notify you things such as when the UPS is on Battery, if a battery needs replacing, or if the battery is reaching an unsafe operating temperature. You may also notice that the 'Software Version' field in the "Node Details' resource now accurately reflects the firmware version installed and running on the UPS.
Currently, this new capability is limited exclusively to APC (American Power Conversion) SmartUPS Uninterruptible Power Supplies (UPS) containing Network Management (AKA Web/SNMP) cards. This feature does not support APC's unmanaged BackUPS series, nor does it yet support other UPS vendors, such as Eaton, Tripp Lite, or CyberPower. At least for now, we recommend using the Universal Device Poller to monitor similar metrics for UPS vendors other than APC. We will, however, be keeping a close eye on the NPM feature request forum to gauge interest in native support for other UPS vendors.
In a similar vein to UPS monitoring discussed above, we learned from speaking with our customers over the years, as well as from those participating in the Orion Improvement Program, that monitoring Load Average on Linux and Unix systems ranks among the most popular uses of the Universal Device Poller. In our enduring pursuit to deliver unexpected simplicity to our customers, we realized that collecting these important metrics natively was something which was long overdue.
Beginning in Orion Platform 2018.2, and included with NPM 12.3, Load Average is collected automatically for any node which supports it. This is typically any Linux based operating system, but can also extend to FreeBSD, AIX, and other Unix like OS's. The Load Average metrics are collected for nodes monitored via the Orion Agent, as well as those managed agentlessly via SNMP. There's really no additional steps required if you added your nodes using the default selection. Since Load Average has a direct correlation to CPU utilization, it's intuitively tied to the existing 'CPU & Memory' option shown under 'List Resources'. When selected, Load Average statistics are collected automatically if the node being monitored supports them.
| List Resources - CPU & Memory | Load Average Resource |
|---|---|
 |  |
On the 'Node Details' view of your Linux servers, you will notice a snazzy new resource entitled 'Load Average' which displays the one minute, five minute, and fifteen-minute load average of the machine being monitored. Because Load Average metrics are tightly coupled to the number of CPU cores, we extended Orion's alerting to allow you to combine Load Average statistics with CPU count within your Alert Trigger so you can be notified when your system is under strain.
Load Average has also been added to the default PerfStack metrics for the node, meaning if you click on the 'Performance Analysis' button on the "Management' Resource of the 'Node Details' view for Linux server, you'll be taken to PerfStack where these Load Average statistics are automatically prepopulated. Similarly. if you're already working in PerfStack you can drag the node itself onto the chart area, the Load Average statistics, as well as other default metrics for the node will populate the PerfStack dashboard.
Ever since bshopp introduced us to Orion Groups back in NPM 10.1, we've heard from many ofyou that the manner in which availability is calculated for these groups just didn't jive with how you think about availability in your environment, nor did it provide a valuable measurement for use in your SLAs. Sadly, Group Availability in Orion is calculated binarily. Put simply, the group is either 100% 'Up' or it's 100% 'Down' regardless of the number of members contained within the group. What this usually meant was, so long as at least one member in the group was 'Up', the availability of the group was 100%. That remained true even if there were 99 other things 'down' in that group at that time. I know, it sounds odd when you say it aloud or even when you're writing it down, but that's how it's been for years and somehow we've managed the muddle through. Well in this release of the Orion Platform, no longer will you be forced to just muddle through. Today we heed your cries!
Rather than turn the world on its end, causing lots of confusion and alerts storms in our wake, we left the legacy Group Availability metric in place, untouched. I know that will come as a big relief to those of you which have grown dependant upon this method of calculating availability and have built reports and alerts around this metric. What we chose to do instead is introduce a new Group metric entitled 'Group Members Availability', which as one would expect, properly and accurately calculates the availability of the group based on its members. This includes nested groups as well.
This new 'Group Members Availability' metric appears automatically on the 'Group Details' view upon group creation. We will also start calculating this new metric upon upgrade to Orion Platform 2018.2 if you already have existing groups. So there's really nothing you need to do. We even include a new out-of-the-box report we refer to as 'Members Based Group Availability Report - Last Month' which serves as an example for how easily this metric can be added to your own reports compared to some of the complex SQL queries some had attempted to use in the past. You can even leverage this new Group Members Availability metric in your alerting conditions with no fuss!
There's still plenty more we've managed to jam pack into this release of the Orion Platform that we're particularly excited about and would love to get your feedback on. Stay tuned to learn about some of the mapping improvements jblankjblank has whipped up and the many usability enhancements serena has crammed into this release, such as sexy new hovers, a new PerfStack widget, and additional improvements that we've made to ensure your next upgrade experience is great!
What has your upgrade to NPM 12.3 on Orion Platform 2018.2 looked like? We on the product manager team would like to hear about it all, the good the bad and the ugly! For a starting point here is a quick getting started blog post on upgrading to 2018.2 Orion Platform: Preparing for the Upgrade to 2018.2
We have been using IPmonitor and NPM as well as we transition to NPM completely. Recently we had a issue of high CPU utilization with switches in stack.
Both IPmonitor and NPM did not indicate there was a high CPU issue. Although on logging directly into the switch i can see it running at 99% CPU continuously.
It seems that SNMP value being monitored is of for whole switch stack in this case 8 switches, instead of monitoring SNMP from the main master switch which is acting as the brains for the stack.
Any recommendation into resolving this issue.
Hi there,
I'm attempting to create some custom Pollers for Talari SD-WAN Appliances. When I go through the MIB browser, I see that Talari is listed in there, but whenever I select an OID to use I get an error that the OID is invalid. Can someone help me understand what this means?
I'm completely new to this so sorry if the terminology is totally wrong.
My requirement is to display in Solar Winds the data being managed by our Velocloud network. The problem is that Solarwinds does not see it correctly so going through the Solar winds SDK to grab anything from their database isn't going to give me the correct information. So, I'm trying to find a way to pull the information directly from the Velocloud database.
Velocloud sent me a Python script that will pull the data I need from their database.. We currently have a custom view someone created that is not being used called "Node Details - Custom Tab 8". My thought is that if that view is rendered as a web page that I can edit the html and embed the python script and have it run through CGI (Common Gateway Interface) and display what I need. Will that work?
If there is a better way and I'm totally missing it please let me know. Thanks.
Hi Forum!,
If this has been asked before please could you point me in the right direction, but i couldn't find anything that answered my query.
What i am trying to do is on a Atlas Map, i want to add a cisco switch port object and in the label ideally i would like to add the port number and description, and if that description changed on the switch, i would like that to reflect in the network map.
For example
Node Picture (ie. Green circle if active) - Fa1/1 Portdescription (description referenced in the CLI of the Cisco switch.
Is this possible?
Apologies if this is a dumb newbie question.... but I'm just getting started with this particular product set.
We have a development environment where we are trialling various aspects of the SolarWinds tooling (NPM, NCM, NTA, SAM HA etc).
This gives us a good feel for the product set, and as part of this we are looking to understand how to move some of the configuration into Live operation.
We have stringent operational Quality Control and Change Management procedures in place, so we need to be able to replicate any customisations in our live environment - without copying an entire database or having to re-type the configurations. Essentially we need to be able to export then import various configurations - but not the actual individual device/application settings. As in most commercial organisations our systems (dev & live) are air-gapped, so we want to maximise the control of what appears in Live.
For example the types of things that we would need to be ported through to live would be:
Is there a way to do this, ideally as simple as possible
All suggestions gratefully received - Thanks in advance
Hi folks,
I am trying to create a resource that will display Node Notes for Unmanaged nodes.
So far I've tried doing this with a Custom Table and dynamic query builder but I can't find the query for Node Notes.
Only other option it seems is to create a custom swql/sql but I am looking for some help with joining data from NodesData and NodeNotes tables.
I wish to have the following included in the table:
Caption (hyperlinked), StatusLED, Unmanaged From, Unmanaged Until, Node Notes
Any help with this query would be greatly appreciated.
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,
We are looking NPM & SAM installation on the single server, is it possible? If yes or No, Please describe the reason..
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.
HI All,
hope this finds you well. i am just wondering since NPM 12.3 the release notes mention that solarwinds "Support Orion cloud deployment in Amazon EC2 and Azure VM"
https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/release_notes
i am just wondering again has anyone tried with SQLaaS or PaaS for either SQL database or the front end 'Orion'? i understand VMAN appliance inst support in cloud deployments, this is more for NPM and SQL.
i have configured IaaS in Azure with both SQL and front end with no problems but i would like to see the communities approach to other Azure Services and any gotchas?
thanks in advance,
Dan
