Orb Agent doesnt match right module types

[tomkeuper]

I have imported some module types from NDX but when i let my Orb agent discover the modules it created other module types. I can easily change the existing modules but it would be better if it could still link them the the NDX Standard.

when i do an snmpwalk I seems to return the value netbox puts in the module name but NDX puts "Aruba" in front. Maybe it could first check the Partnumber itself?

SNMPv2-SMI::mib-2.47.1.1.1.1.13.1 = STRING: "J9850A"
SNMPv2-SMI::mib-2.47.1.1.1.1.13.2 = STRING: "J9850A"
SNMPv2-SMI::mib-2.47.1.1.1.1.13.3 = ""
...
SNMPv2-SMI::mib-2.47.1.1.1.1.13.41 = ""
SNMPv2-SMI::mib-2.47.1.1.1.1.13.42 = ""
SNMPv2-SMI::mib-2.47.1.1.1.1.13.43 = ""
SNMPv2-SMI::mib-2.47.1.1.1.1.13.44 = ""
SNMPv2-SMI::mib-2.47.1.1.1.1.13.69 = STRING: "J9827A"
SNMPv2-SMI::mib-2.47.1.1.1.1.13.74 = STRING: "J9990A"
SNMPv2-SMI::mib-2.47.1.1.1.1.13.75 = STRING: "J9986A"

[leoparente]

Hi @tomkeuper thanks for the ticket. We are investigating yet the best way to solve differences between what agent discovers and what NDX expects. This may be a Diode server side solution. We are not sure yet, but I will keep this ticket and you posted about it.