Introduction
Generate those infamous .def files with the help of this module, to make them as accurate and reliable as possible. Email me the resulting .def files, if they're 100% working and I'll include them in the distribution.
Usage
Preparation
You'd usually click on a sysobjid (type column) of an unknown device in Devices-List. This will add an IP address and SNMP community along with the sysobjid you wish to take care of. Alternatively you can add those values manually and click on the
button to update the form.
In case there's an existing .def file in html/log already, it's values will be filled into the form. This should make it easy for you to improve existing definitions at a later stage. This comes in handy as well, when you copy a .def file from a similar device from sysobj to html/log/ (adjusting the sysobjid) to get your usnupported unit going.
Process
Now you're ready to actually work in the .def file. You find templates to the right of each section, which suggest some OIDs. You can test them by clicking on the
get and
walk button.
- Hover over the input fields, to get hints on what to fill in.
- Find the most official type (there's usually a sticker with a barcode somewhere).
- Select the icon according to the GUI docs on the NeDi Homepage.
- Contact me, if you need a new OS selection.
- Some vendors use vlan community indexing to get Bridge forwarding information on the switches.
- Some vendors use twice the bandwidth to indicate fullduplex. Just use 'doublespeed' as keyword for IF Duplex.
- Only populate the Alias- Duplex- and Vlan- Index fields, if they're not coherent with the interface indexes.
Details
- Add additional comments on top by a leading #
- Once you start editing the text area, the inputs above will be locked to prevent accidental input.