Raise the debugging level by 1. This gets rather messy above 3 or 4.
Be verbose. This makes sdig print every port instead of just the one that
is the most likely candidate, for example (includes inter-switch ports
with LINKINFO written in sdig.conf).
Fast mode. sdig will not do reverse DNS (in-addr.arpa) or NetBIOS queries
to port 137 when this is enabled.
Use the configuration file config.
Look for this MAC address rather than asking a router about it. You still
can provide an IP address or hostname so that sdig knows which network
A total-network sweep option is when you dont provide the IP, takes longer
to query all switches, so care is taken than each IPxCOMMUNITY is only
An Internet Protocol address to find, i.e. 192.168.1.1.
A DNS or WINS hostname to find. WINS resolution is only available if you
have installed nmblookup from Samba and have added it to your config file.
Parallelized SNMP queries have been added and improved as a feature of
the recent sdig versions. If compiled in, they can be disabled at run time,
or different activities may be done at discretion of future programmers.
"-p" increases the "use parallelism" counter.
"-P" decreases the "use parallelism" counter, but to no less than zero.
You might want to disable this i.e. if it misbehaves on your platform,
or if you have very many switches and spawning many children would exhaust
your file descriptors (network sockets) or process table entries.
Hint: Future versions may add a limit on number of spawned children.
If the "parallelized queries" feature is not compiled in, these "-p/-P"
flags are recognized, but ignored.
You cant track down arbitrary hosts on the Internet. Well, most people cant. You might be able to do this if you convince all the router and switch manufacturers of the world to drop in a SNMP backdoor for your sdig host. US government three letter entities: contact me for details.
This program was developed on just one kind of system (Linux glibc2) so it probably doesnt compile cleanly on others.
NOTE: version 0.45 was developed on Solaris x86/SPARC and also works there.
I (Russell Kroll) first wrote this program to show some local people that you dont need to dump lots of money into a program like 3coms Transcend just to hunt down some lusers on your network. If you dont need to create fancy network diagrams to impress the PHBs, then this program will probably work for you.
It was developed originally on 3com SuperStack 3300s, and continues to be tested both on those and various HP 2324s and 4108s. Other equipment should also work if it provides the same basic OIDs.
Jim Klimov also tested it in a diverse network with HP, Cisco, Avaya, and Allied Telesyn equipment, to name a few.
Russell Kroll <firstname.lastname@example.org> up till sdig-0.40 Russell A. Jackson <email@example.com> sdig-0.41 .. sdig-0.44 Jim Klimov <firstname.lastname@example.org> sdig-0.45
|SDIG (8)||Mon Apr 4 2003|