Device Definition Editor
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 by clicking on 
, if they're 100% working and I'll include them in the distribution.
You'd usually click on a sysobjid column of an unknown device in Devices-List or 
in Devices-Status.
This will add an IP address and SNMP community along with the sysobjid you wish to take care of.
In case a .def file exists already, it's values will be filled into the form.
Click on 
to set the current sysobjid as source for an undefined device. Then navigate to the undefined device
and click on 
to copy the definition to this one.
The 
reloads the existing .def
In case a .def exists with it's last sysobjid digit within -+10 of the chosen one, it'll be added to a list of potential source .defs, which can be copied as template.
Here's some useful information on Sysobjids: Cisco
It's also recommended to watch the DefGen Tutorial!
- 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 the same as the interface indexes.
- If MAU type (1.3.6.1.2.1.26.2.1.1.11) is used, no actual duplex values are required.
- Use modifiers to multiply/divide temperature and memory if necessary. The latter also accepts % if the value reflects percentage of available memory or -% in the case of used memory.
- Add an "N" to an OID, if of the last number can vary for CPU or temperature.
- Add 1-x to bootimage, if the info is spread across several OIDs (e.g. Zyxel, ESXi)
- Use a negative custom threshold to alert if result is less than threshold
- Once you start editing the text area, the input fields above will be locked to prevent accidental input.
Modules
Without a Class OID the Class Value is assigned to all modules found.
When used with the Entity-MIB it should be a regexp like "6|9|10" to classify the items properly:
- other(1),
- unknown(2),
- chassis(3),
- backplane(4),
- container(5), -- e.g., chassis slot or daughter-card holder
- powerSupply(6),
- fan(7),
- sensor(8),
- module(9), -- e.g., plug-in card or daughter-card
- port(10),
- stack(11), -- e.g., stack of multiple chassis entities
- cpu(12),
- energyObject(13),
- battery(14),
- storageDrive(15)
NeDi Help