Welcome, Guest. Please login or register.

Author Topic: Same sysobjid used by different vendors  (Read 398 times)

keloko

  • Newbie
  • *
  • Posts: 2
    • View Profile
Same sysobjid used by different vendors
« on: November 14, 2018, 06:01:49 PM »
Has anyone come up with a workaround to separate devices from different vendors using the same sysobjid ?

For example, sysobjid 1.3.6.1.4.1.8072.3.2.10 (Linux) is used for some Checkpoint and Denyall devices and the vendors have no intention to change this apparently. Would it be reasonable, as a workaround, to add a condition somewhere to force/modify the sysobjid for selected devices during discovery process, so that we can apply different .def files for each actual device type ? Or is there a better idea out there on how to approach this issue ?

Thanks in advance for your suggestions and comments.

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2697
    • View Profile
    • NeDi
Re: Same sysobjid used by different vendors
« Reply #1 on: November 26, 2018, 02:58:47 PM »
You can try the Typeoid, which could read the exact type from the device instead mapping to the sysobjid. This works well, if such an OID is avaiable. I've also added a feature in NeDi 1.8 to derive unknown vendors from the first interface MAC address...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

keloko

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Same sysobjid used by different vendors
« Reply #2 on: November 28, 2018, 05:35:43 PM »
Thanks for the hints Remo. I've managed to use Typeoid for some of these devices and will modify the DB directly after discovery for the other exceptions, until I can use version 1.8 (using the MAC vendor sounds like a good solution indeed).