<![CDATA[Juniper Product infos are not recognized]]>Product/vendor/serial infos are not recognized by netxms on these juniper swtches:
ex4200 firmware 15.1
ex2200 firmware 12.xxxx
ex4550 firmware 15.1rxxxx

Immagine 2022-10-25 122444.png

This bug leds also to another behaviour.
If a well-recognized switch is phisically substituted with one of the above unrecognized models, the infos are not updated (emptied as i would expect) thus mantaining the old switch productname. I need to do a full poll to delete wrong infos and get the situation of the first image.

Immagine 2022-10-25 123235.png

]]>https://forum.netxms.org/topic/7539/juniper-product-infos-are-not-recognizedRSS for NodeFri, 13 Nov 2026 09:03:06 GMTTue, 25 Oct 2022 10:38:07 GMT60<![CDATA[Reply to Juniper Product infos are not recognized on Tue, 01 Nov 2022 17:15:33 GMT]]>I've updated Juniper driver to use this MIB if available. Changes will be included into next patch release.

Best regards,
Victor

]]>https://forum.netxms.org/post/31982https://forum.netxms.org/post/31982Tue, 01 Nov 2022 17:15:33 GMT<![CDATA[Reply to Juniper Product infos are not recognized on Tue, 01 Nov 2022 14:07:11 GMT]]>Here you can download the official Juniper Networks SNMP MIB packages
And a handy navigator through the SNMP MIB Object hierarchy

Looked deeper, your program is already equipped with the necessary MIBs, but the Product and Serial number are not really displayed.
scr1.jpg
 

In the MIB Explorer:
scr2.jpg

]]>https://forum.netxms.org/post/31976https://forum.netxms.org/post/31976Tue, 01 Nov 2022 14:07:11 GMT<![CDATA[Reply to Juniper Product infos are not recognized on Mon, 31 Oct 2022 15:19:06 GMT]]>Currently NetXMS uses Entity MIB for getting hardware information for Juniper devices. Looks like those models does not support Entity MIB.
Do you know if Juniper priovides model and serial number information via private MIB? If yes, we can update Juniper driver to use it.

As for retaining old hardware information - it is a bug (or rather flawed logic). Existing hardware information kept in place if server cannot read it from the device to avoid erasing it because of read error. I think that best solution will be device replacement detection (likely based on MAC address change and probably also hardware model change) and running full poll if it is detected. Added it as feature in our tracker: https://track.radensolutions.com/issue/NX-2314

]]>https://forum.netxms.org/post/31969https://forum.netxms.org/post/31969Mon, 31 Oct 2022 15:19:06 GMT