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.

If it doesn't, you should see a blue "Copy Source" selectbox allowing to choose an existing definition from the same vendor

The reloads the existing .def

Here's some useful information on Sysobjids: Cisco

Type Icons

Class Description
s2,s3,sm,sk,sf Switches: Layer2, Layer3, Modular, Stack, Fiberchannel
rt Router
wc,wa,wb Wireless: Controller, AP, Bridge
fw Firewall
lb Loadbalancer
cp Computer
st Storage
pr Print
ph Phone
up UPS
cl Cloud (usually manually added)
va,vc Video: Camera, Conference

Device Mode

Either an OID, where the device mode can be read from (e.g. Cisco VTP-Mode) or a number representing the actual mode. The following table shows all modes known to NeDi (they're automatically set for non-SNMP devices):
Number Description
0 Generic SNMP device
1 VTP-client
2 VTP-server
3 VTP-transparent
4 VTP-inactive
5 VTP-error
6 Bridge (regular switch)
7 Printer
9 User added device
10 SSH device added by NoDi
11 WMI device added by NoDi
19 NeDi agent added by master deamon
20 Non-SNMP Wlan AP not assigned to a controller
21 Non-SNMP Wlan bridge
25 Wlan AP managed by a controller
30 VoIP phone
31 VoIP (ATA) box
40 Video device (Webcam)
41 Video conference system
50 Generic non-SNMP device
51 Virtual Bridge/Switch

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: