NeDi Help

System NeDi

1. By default the help is displayed, which reveals options and the output legend
2. Discover will actually find devices
3. Services relate to nodes (in general)
4. List all available .def files (definitions based on SNMP Sysobjid)
5. Reset can be used for database initialisation or updates

Discover

1. Just check "Protocol" and click execute to discovers the default gateway of the NeDi host and any neighbors via CDP or LLDP
2. Select "Address" from the Seed-selectbox, enter a single IP, a range like 1.2.3,6,8.10-15 or a CIDR notation (uses fping, no need for -Px)
3. Click to select all devices in the DB
4. You can also substitute "all" with a query to only discover a subset and use crontab to parallelize the discoveries this way (Devices-List let's links here with a filter set)
5. Use a static seedlist, which can be useful to map names, locations or contacts (but using the -A option is easier to manage)
6. To find more "exotic" devices, add the vendor strings to ouidev in nedi.conf and check "OUI". Discover a router connected to those devices and they'll be queued
7. You can use route tables as layer3 discovery by checking "Routes"

• Select Ping (1-3s timeout) to test reachability prior SNMP
• Select a Configuration option to back up device configurations to DB and the config folder
• Click to skip interface info, to avoid graphs or to ignore nodes (any combination is possible, to speed up the discovery)
• When you skip Vlans (v) on Cisco switches without a ssh-user set, the MAC address table will be skipped as well due to their SNMP Vlan indexing!
• Select "Version" to force using an SNMP version (only tested upon first discovery and the first one working is stored in DB)
• Check "Read" to re-test SNMP read access (useful to rediscover an existing device in conjunction with -V)
• Check "Write" to re-test SNMP write community strings (only tested upon first discovery, can be turned of via snmpwrite in nedi.conf)
• NeDi relies on unique device names. Check DevIP to use their IP addresses instead
• Select a command file from CLI-Send selectbox to have it executed on each discovered device (see System-Files for creating them)

• Click then "Execute" to backup all devices
• Select "Database & File" to get additional configuration backup files (in conf/ folder)
• Select "File (No Change)" to force file creation, even if config hasn't changed. Add 's' to the skip options to override config status check on supported (e.g. Cisco) devices
• Select "File (Flash Comparison)" to read both, running and startup configs and check for differences

Services

• Click to identify all nodes with IP addresses (use with care as it performs a portscan)
• Select Ping (1-3s timeout) to test reachability prior scan
• Select Nodes and enter a query like oui ~ 'intel' or a CIDR notation (matches ARP entries)
• Or select Address from the Seed-selectbox, enter a single IP, a range like 1.2.3,6,8.10-15 or a CIDR notation (uses fping, no need for -Px)
• Check verbose to follow the progress of the host identification
• The 'id' option uses ssh, sendmail, http, https and netbios for host identification
• Additional ports can be checked by appending e.g. id,3128,5900 (without "id" only specified ports are checked for connectivibty)

• Click then "Execute" to update all node names
• Select Nodes and enter a query like oui ~ 'intel' or a CIDR notation (matches ARP entries)
• Or select Address from the Seed-selectbox, enter a single IP, a range like 1.2.3,6,8.10-15 or a CIDR notation (uses fping)
• The Network Population report in Reports-Networks leverages this information to show unused DNS records for example

• Click to update node vendors using local OUI.csv files (available from ieee.org)

Reset

• Leave "updatedb" as username and click "Execute" to update the DB scheme to the current version
• Enter "nodrop" as username and click "Execute" to erase the existing DB (you'll lose all data!)
• Enter credentials of DB admin and click "Execute" to drop and recreate the DB (you'll lose all data!)