Discovery: Identical SNMP System OID for 2 Juniper Switches ex4300-48p & ex4300-24p how to classify them if OID classifers can't?

[Cedric Creton]

Dears,

Using Istanbul Discovery to inventory our numerous Juniper Switches

For 2 sub-model of ex4300 Juniper Switches   with different numbers of network interfaces(ex4300-48p & ex4300-24p), discovery retrieves the same SYs OID

Identical SNMP System OID for 2 Juniper Switches ex4300-48p & ex4300-24p: 1.3.6.1.4.1.2636.1.1.1.2.63

"Juniper Networks, Inc. ex4300-48p Ethernet Switch, kernel JUNOS 14.1X53-D45.3, Build date: 2017-07-28 04:37:59 UTC Copyright (c) 1996-2017 Juniper Networks, Inc.

System OID: 1.3.6.1.4.1.2636.1.1.1.2.63"

&

"Juniper Networks, Inc. ex4300-24t Ethernet Switch, kernel JUNOS 13.2X51-D35.3, Build date: 2015-04-09 23:43:21 UTC Copyright (c) 1996-2015 Juniper Networks, Inc.

System OID: 1.3.6.1.4.1.2636.1.1.1.2.63"

So creating an SNMP OID Classifier is not enough to differentiate the 24-port and the 48-port. How to clearly identify the model?

Thank you in advance.

Kind Regards

Cedric

[doug_schulze]

Cedric,

We had that same problem with HP printers back in the day where we created a new exploration probe based on the manufacturer to set the specific model. You can see this probe in the discovery definition > (SNMP Classifier group) > standard printer classifier. All you would have to do is find the oid that Juniper publishes that can tell you the exact model and create your own exploration probe using the printer one as a guide to get what you are looking for...

[Paul-Eric Paum2]

Doug, thank you much for this information!

I faced the same issue with Ricoh printers (and also some other Xerox printers) and was able to fix this.

[doug_schulze]

Great to hear, one of the things I love about probes is being able to use condition scripts from parameters gathered during classification...And can think of a few great ways to use patterns to do the same....

[Cedric Creton]

Hello Doug,

I'm at least coming back to that  issue.

On a device (again a Juniper)... 1.3.6.1.2.1.1.2 - sysObjectID is not returned (it should be 1.3.6.1.4.1.2636.1.1.1.2.63)

But I have the sysDescr 🙂

<sysDescr oid="1.3.6.1.2.1.1.1" type="SnmpOctetString">

Juniper Networks, Inc. ex4300-48t Ethernet Switch, kernel JUNOS 14.1X53-D47.6, Build date: 2018-09-08 05:53:12 UTC Copyright (c) 1996-2018 Juniper Networks, Inc.

</sysDescr>"

You previous example was talking about a new exploration probe.

In present case, the device is used as a switch.... but by default discovery identify that as a router... 

How can I force to discover that as switch if I can catch the sysObjectID fiels ??? Does an identification (too late, no?) probe with a script can do the job, parsing the sysDescr?

Best Regards

Cedric