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...

215 Replies
Level 7

Hereby a list of recent HPE Aruba switches I would like to see added. I could see some small overlap with recent posts, but still post the entire list I've found below, to hopefully get consistent descriptions for these product lines:

SysObjectIDDescription
1.3.6.1.4.1.47196.4.1.1.1.1Aruba 8400 8-slot chassis (JL375A)
1.3.6.1.4.1.47196.4.1.1.1.2Aruba 8320 48p 10G SFP/SFP+ and 6p 40G QSFP+ switch (JL479A)
1.3.6.1.4.1.47196.4.1.1.1.3Aruba 8320 32p QSFP+ switch (JL579A)
1.3.6.1.4.1.47196.4.1.1.1.5Aruba 8320 48p 1G/10GBASE-T and 6p 40G QSFP+ switch (JL581A)
1.3.6.1.4.1.47196.4.1.1.1.50Aruba 8325 8325-48Y8C switch (JL635A)
1.3.6.1.4.1.47196.4.1.1.1.70Aruba 8325 8325-32C switch (JL636A)
1.3.6.1.4.1.47196.4.1.1.1.100Aruba 6300M 24SFP+/4SFP56 switch (JL658A)
1.3.6.1.4.1.47196.4.1.1.1.101Aruba 6300M 48SR PoE CL6 /4SFP56 switch (JL659A)
1.3.6.1.4.1.47196.4.1.1.1.102Aruba 6300M 24SR PoE CL6 /4SFP56 switch (JL660A)
1.3.6.1.4.1.47196.4.1.1.1.103Aruba 6300M 48G PoE CL4 /4SFP56 switch (JL661A)
1.3.6.1.4.1.47196.4.1.1.1.104Aruba 6300M 24G PoE CL4 /4SFP56 switch (JL662A)
1.3.6.1.4.1.47196.4.1.1.1.105Aruba 6300M 48G /4SFP56 switch (JL663A)
1.3.6.1.4.1.47196.4.1.1.1.106Aruba 6300M 24G /4SFP56 switch (JL664A)
1.3.6.1.4.1.47196.4.1.1.1.107Aruba 6300F 48G PoE CL4 /4SFP56 switch (JL665A)
1.3.6.1.4.1.47196.4.1.1.1.108Aruba 6300F 24G PoE CL4 /4SFP56 switch (JL666A)
1.3.6.1.4.1.47196.4.1.1.1.109Aruba 6300F 48G /4SFP56 switch (JL667A)
1.3.6.1.4.1.47196.4.1.1.1.110Aruba 6300F 24G /4SFP56 switch (JL668A)
1.3.6.1.4.1.47196.4.1.1.1.111Aruba 6300M 48G /4SFP56 Pwr2Prt switch (JL726A)
1.3.6.1.4.1.47196.4.1.1.1.150Aruba 6405 Chassis (R0X24A)
1.3.6.1.4.1.47196.4.1.1.1.151Aruba 6410 Chassis (R0X25A)
1.3.6.1.4.1.47196.4.1.1.1.300Aruba 6200F 24G 4SFP+ switch (JL724A)
1.3.6.1.4.1.47196.4.1.1.1.301Aruba 6200F 24G CL4 4SFP+ 370W switch (JL725A)
1.3.6.1.4.1.47196.4.1.1.1.302Aruba 6200F 48G 4SFP+ switch (JL726A)
1.3.6.1.4.1.47196.4.1.1.1.303Aruba 6200F 48G CL4 4SFP+ 370W switch (JL727A)
1.3.6.1.4.1.47196.4.1.1.1.304Aruba 6200F 48G CL4 4SFP+ 740W switch (JL728A)

QNAP have changed their SNMP and OID implementation recently.

1.3.6.1.4.1.55062 QNAP (NAS Devices with QTS 4.5.1.1461 build 20201020 or newer)
0 Kudos
Level 7

Please add the following Aruba CX switches

DESCRIPTION Aruba JL661A 6300M 48G CL4 PoE 4SFP56
SYSOBJECTID 1.3.6.1.4.1.47196.4.1.1.1.103

DESCRIPTION Aruba R0X25A 6410
SYSOBJECTID 1.3.6.1.4.1.47196.4.1.1.1.151

DESCRIPTION Aruba JL635A 8325
SYSOBJECTID 1.3.6.1.4.1.47196.4.1.1.1.50

 

 

0 Kudos
Level 8

1.3.6.1.4.1.11.2.3.7.11.181.16.Aruba JL258A 2930F-8G-PoE+-2SFP+
1.3.6.1.4.1.11.2.3.7.11.181.20.Aruba JL255A 2930F-24G-PoE+-4SFP+
1.3.6.1.4.1.11.2.3.7.11.181.21.Aruba JL256A 2930F-48G-PoE+-4SFP+
1.3.6.1.4.1.11.2.3.7.11.182.20.Aruba JL356A 2540-24G-PoE+-4SFP+
1.3.6.1.4.1.11.2.3.7.11.182.21.Aruba JL357A 2540-48G-PoE+-4SFP+
1.3.6.1.4.1.11.2.3.7.11.163.HP J9853A 2530-48G-PoE+-2SFP+
0 Kudos

More HPE Aruba from me:

HPE 2930F-24G-4​SFP+ (L253A)  

SYSOBJECTID 1.3.6.1.4.1.11.2.3.7.8.5.5 

 

 

 

0 Kudos
Level 8

DESCRIPTION Aruba JL665A 6300F 48G CL4 PoE 4SFP56 SWITCH
SYSOBJECTID 1.3.6.1.4.1.47196.4.1.1.1.107

DESCRIPTION Aruba JL635A 8325-48Y8C 48p 25G 8p 100G SWITCH
SYSOBJECTID 1.3.6.1.4.1.47196.4.1.1.1.50

DESCRIPTION Aruba JL581A 8320-4​8Px10GBase​T-6Px40G SWITCH
SYSOBJECTID 1.3.6.1.4.1.47196.4.1.1.1.5

0 Kudos
Level 8

These Aruba CX Network Switches are being labeled as Unknown. Can these be added to the next update?

DESCRIPTION Aruba JL665A 6300F 48G CL4 PoE 4SFP56 Sw
SYSOBJECTID 1.3.6.1.4.1.47196.4.1.1.1.107

0 Kudos
Level 7

<body>

<p>Both of the following OIDs incorrectly resolve to machine type "Cisco". Cisco is the correct vendor for both.

<p>1.3.6.1.4.1.9.1.2688 should be machine type "Catalyst 9500-48Y4C"

<p>1.3.6.1.4.1.9.1.2804 should be machine type "Catalyst 9300L Switch Stack"

 

</body>

 

 

Hi John,

I *think* that 1.3.6.1.4.1.9.1.2688 is: "Cisco Catalyst 9500 Virtual Stack",  not the 9500-48Y4C.

See attached screenshot from SolarWinds MIB Browser.

Thank you,

-Scott

0 Kudos
Level 7

NPM 2019.4
IF IOS is 16.9.X the proper values are shown. but above we MachineType as Cisco.

so for Cisco IOS XE higher then 16.9

1.3.6.1.2.1.47.1.1.1.1.13.1000 C9200-24P
1.3.6.1.2.1.47.1.1.1.1.13.1000 C9500-40X

 

0 Kudos

1.3.6.1.4.1.9.1.2391 = C9800_IOSX​E-K9 - Cisco vWLC

0 Kudos

graham.leiker  wrote:

1.3.6.1.4.1.9.1.2391 = C9800_IOSXE-K9 - Cisco vWLC

Captured under DC-2870

0 Kudos

Hi @aLTeReGo,

Have a couple here to add, they all show as 'Dell Computer Corporation' in 2019.4 HF3.

1.3.6.1.4.1.6027.1.3.32 = DellEMC S5048F-ON
1.3.6.1.4.1.674.11000.5000.100.2.1.20 = DellEMC S5232F-ON
1.3.6.1.4.1.674.11000.5000.100.2.1.21 = DellEMC S5248F-ON
1.3.6.1.4.1.674.11000.5000.100.2.3.2 = DellEMC Z9264F-ON

Thank you for your support!

0 Kudos


@sum_giais wrote:

Hi @aLTeReGo,

Have a couple here to add, they all show as 'Dell Computer Corporation' in 2019.4 HF3.

1.3.6.1.4.1.6027.1.3.32 = DellEMC S5048F-ON
1.3.6.1.4.1.674.11000.5000.100.2.1.20 = DellEMC S5232F-ON
1.3.6.1.4.1.674.11000.5000.100.2.1.21 = DellEMC S5248F-ON
1.3.6.1.4.1.674.11000.5000.100.2.3.2 = DellEMC Z9264F-ON

Thank you for your support!


Tracking internally under DC-3237

Hello aLTeReGo,

I have these unknown device types in NPM:

1.3.6.1.4.1.9.1.2694 = Cisco C9200L-48P-4X

1.3.6.1.4.1.9.1.2695 = Cisco C9200-48P

1.3.6.1.4.1.9.1.2685 = Cisco IE-3300-8T2S

Thank you!

0 Kudos
Level 16

C9300L-48P-4X      1.3.6.1.4.1.9.1.2804

Cisco Catalyst  C9200-48P  1.3.6.1.4.1.9.1.2695

                                  

Macine type  is "Cisco" ...

0 Kudos
Product Manager
Product Manager

sja  wrote:

C9300L-48P-4X      1.3.6.1.4.1.9.1.2804

Cisco Catalyst  C9200-48P  1.3.6.1.4.1.9.1.2695

                                  

Macine type  is "Cisco" ...

Tracking internally under DC-3118

0 Kudos
Level 7

1.3.6.1.4.1.705.1 - Eaton 5PX 2200

0 Kudos

mburns34  wrote:

1.3.6.1.4.1.705.1 - Eaton 5PX 2200

Have you verified this SysObjectID against different modules of Eaton UPSs? The OID you posted is too generic for that specific make & model device. This appears to be a root OID.

0 Kudos

I have a couple of these EATON ups that have that OID number but come up as Merlin Gerin. The rest show the correct company and model but the SYSTEMOID field just shows the model and serial number instead of the OID.

0 Kudos