cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Product Manager
Product Manager

Tell Us Your Unknown Devices v2.0

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.

What is an 'Unknown' Device anyway?

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.

pastedImage_2.png

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.

What Exactly is a SysObjectID?

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.

Where Can I Locate the SysObjectID?

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 DetailsNET-SNMP
pastedImage_2.png

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.

pastedImage_4.png

My Device Incorrectly Appears Listed as 'NET-SNMP'

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.

Install The Orion Linux Agent

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 HatCitrix XenServer
pastedImage_10.pngpastedImage_9.png

Modify NET-SNMP Configuration

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.

Video Link : 1084

Can't I Just Upload My Vendor's MIB File Here And You figure it Out?

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.

Request additional MIBs to the SNMP MIB browser database - SolarWinds Worldwide, LLC. Help and Suppo...

211 Replies

david.wild  wrote:

1.3.6.1.4.1.476.1.42 Liebert/Vertiv GXT4 are new to our network and not correctly identified yet.

a bit new to this, is this the correct way to add "Unknown"

Regards.

In Orion Platform 2019.2 these devices should be recognized as 'Veritiv/Emerson/Liebert'

0 Kudos
Level 10

cisco9200FixedSwitchStack = .1.3.6.1.4.1.9.1.2694

cisco9200RFixedSwitchStack = .1.3.6.1.4.1.9.1.2695

0 Kudos
Level 10

1.3.6.1.4.1.9.1.1348 - ciscoUCVirtualMachine

0 Kudos

frankmuhlstadt  wrote:

1.3.6.1.4.1.9.1.1348 - ciscoUCVirtualMachine

This SysObjectID should already be included in the latest Orion Platform version 2019.2.

0 Kudos

I just upgraded to 2019.2 HF1. that device is still "Unknown". the MIB.CGF is dated 6/21/2019.  Update to the lates MIBs db created 7/12/2019. Rediscovered the device ... Still in the unknown folder.  Advise?

0 Kudos

frankmuhlstadt  wrote:

I just upgraded to 2019.2 HF1. that device is still "Unknown". the MIB.CGF is dated 6/21/2019.  Update to the lates MIBs db created 7/12/2019. Rediscovered the device ... Still in the unknown folder.  Advise?

Ahh, I see what happened. It appears that SysObjectID was added to our database by another team, outside the purview of my usual tracking methods. You are correct, this is not in Orion Platform 2019.2. We are however tracking this internally under DEM-14302. My apologies for the confusion.

0 Kudos
Product Manager
Product Manager

Orion Platform 2019.2 includes almost all of these submissions as of the time of this posting. For a complete listing, click the link below.

https://documentation.solarwinds.com/archive/pdf/orionplatform/RC_Orion_Platform_2019-2_supported-ve...

Not sure if you were replying to the general audience, but the 3 entries I mentioned were not on that list.

0 Kudos

I'm afraid your submissions came a little too late to be included in the 2019.2 release. That is why I needed to add the caveat 'almost all' to the post.

0 Kudos
Level 8

Cisco ASR9906 - 1.3.6.1.4.1.9.1.2572

Cisco cBR-8 - 1.3.6.1.4.1.9.1.2141

0 Kudos
Level 9

1.3.6.1.4.1.9.12.3.1.3.1955

cevChassisN9KC9336CFX2

1.3.6.1.4.1.9.12.3.1.3.1626

cevChassisN9KC9372PX

1.3.6.1.4.1.9.12.3.1.3.1485

cevChassisISR4431

0 Kudos

OID: 1.3.6.1.2.1.33  CS121 SNMP Card

This is an OEM interface card added to an industrial UPS, ours are badged Piller Power Systems, however, I think same OID is quite generic and is used for other makes.

I created a SAM template a while ago which is here: Piller UPS

Pete.

0 Kudos

pgaryga  wrote:

OID: 1.3.6.1.2.1.33  CS121 SNMP Card

This is an OEM interface card added to an industrial UPS, ours are badged Piller Power Systems, however, I think same OID is quite generic and is used for other makes.

I created a SAM template a while ago which is here: Piller UPS 

Pete.

This is not a SysObjectID. 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.

0 Kudos
Level 7

1.3.6.1.4.1.9.1.2593 = Cisco C9500-40X model switch (only shows up as "Cisco" under machine type)

0 Kudos

jpar345  wrote:

1.3.6.1.4.1.9.1.2593 = Cisco C9500-40X model switch (only shows up as "Cisco" under machine type)

This SysObjectID and most others posted here have been added to Orion Platform 2019.2 included in NPM 12.5, available now from your Customer Portal.

0 Kudos
Level 7

1.3.6.1.4.1.8072.3.2.10 = checkpoint Firewall appliance 1490 (seems to be used for different model numbers?)

0 Kudos

badger_442  wrote:

1.3.6.1.4.1.8072.3.2.10 = checkpoint Firewall appliance 1490 (seems to be used for different model numbers?)

'1.3.6.1.4.1.8072.3.2.10' is a generic SysObjectID for NET-SNMP. To learn more about this, click the link below.

https://thwack.solarwinds.com/thread/116311#jive_content_id_My_Device_Incorrectly_Appears_Listed_as_...

0 Kudos
Level 10

1.3.6.1.4.1.12356.101.1.2010 = Fortigate 201E

0 Kudos

frankmuhlstadt  wrote:

1.3.6.1.4.1.12356.101.1.2010 = Fortigate 201E

Captured under DC-1990

Level 10

1.3.6.1.4.1.12356.101.1.306 = Fortigate 30E

0 Kudos

frankmuhlstadt  wrote:

1.3.6.1.4.1.12356.101.1.306 = Fortigate 30E

Captured under DC-1990