netdisco-frontend 1.0-2 / usr / share / netdisco / html / doc / README.html

<%text>

<p><a name="__index__"></a></p>
<!-- INDEX BEGIN -->

<ul>

	<li><a href="#name">NAME</a></li>
	<li><a href="#author">AUTHOR</a></li>
	<li><a href="#description">DESCRIPTION</a></li>
	<li><a href="#features">FEATURES</a></li>
	<ul>

		<li><a href="#switch_ports">Switch Ports</a></li>
		<li><a href="#easy_administration">Easy Administration</a></li>
		<li><a href="#network_administration_and_security">Network Administration and Security</a></li>
		<li><a href="#reporting">Reporting</a></li>
		<li><a href="#inventory_of_network_devices">Inventory of Network Devices</a></li>
		<li><a href="#supported_devices">SUPPORTED DEVICES</a></li>
	</ul>

	<li><a href="#support">SUPPORT</a></li>
	<li><a href="#glossary">GLOSSARY</a></li>
	<li><a href="#install">INSTALL</a></li>
	<li><a href="#using_netdisco">USING NETDISCO</a></li>
	<ul>

		<li><a href="#components">Components</a></li>
		<li><a href="#commandline_options">Command-Line Options</a></li>
		<li><a href="#commandline_commands">Command-Line Commands</a></li>
		<li><a href="#features">Features</a></li>
		<li><a href="#netdisco_maintenance">Netdisco Maintenance</a></li>
		<li><a href="#topology_information">Topology Information</a></li>
		<ul>

			<li><a href="#autodetection_of_uplink_ports">Autodetection of uplink ports</a></li>
			<li><a href="#manual_topology_information">Manual Topology Information</a></li>
		</ul>

		<li><a href="#cron_jobs">Cron Jobs</a></li>
	</ul>

	<li><a href="#config_file">Config File</a></li>
	<ul>

		<li><a href="#general_items">General Items</a></li>
		<li><a href="#database_maintenance">Database Maintenance</a></li>
		<li><a href="#backend_items">Back-End Items</a></li>
		<ul>

			<li><a href="#admin_panel">Admin Panel</a></li>
			<li><a href="#database_settings">Database Settings</a></li>
			<li><a href="#snmp_settings">SNMP Settings</a></li>
		</ul>

		<li><a href="#port_control">Port Control</a></li>
		<li><a href="#web_settings">Web Settings</a></li>
		<ul>

			<li><a href="#ldap_settings">LDAP Settings</a></li>
			<li><a href="#graph_settings">Graph Settings</a></li>
		</ul>

	</ul>

	<li><a href="#design">DESIGN</a></li>
	<ul>

		<li><a href="#design_goals">Design Goals</a></li>
		<li><a href="#backend_components">Back-End Components</a></li>
		<li><a href="#database">Database</a></li>
		<ul>

			<li><a href="#sql_tables">SQL Tables</a></li>
		</ul>

	</ul>

	<li><a href="#thanks">THANKS</a></li>
</ul>
<!-- INDEX END -->

<hr />
<p>
</p>
<h1><a name="name">NAME</a></h1>
<p>Netdisco 1.0 - README</p>
<p>
</p>
<hr />
<h1><a name="author">AUTHOR</a></h1>
<p>Netdisco is maintained by a team of Open Source developers headed by Eric
Miller, Bill Fenner, Oliver Gorwits, and Max Baker.</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>Netdisco is an Open Source web-based network management tool.</p>
<p>Designed for moderate to large networks, configuration information and
connection data for network devices are retrieved and set by SNMP.  With
Netdisco you can locate the switch port of an end-user system by IP or MAC
address.  Data is stored using a SQL database for scalability and speed.</p>
<p>Cisco Discovery Protocol (CDP), Foundry Discovery Protocol (FDP), Link Layer
Discovery Protocol (LLDP), and SynOptics Network Management Protocol (SONMP)
optionally provide automatic discovery of the network topology.</p>
<p>The network is inventoried by both device model and operating system (like
IOS).  Netdisco uses router ARP tables and L2 switch MAC forwarding tables to
locate nodes on physical ports and track them by their IP addresses.</p>
<p>For each node, a time stamped history of the ports it has visited and the IP
addresses it has used is maintained.  Netdisco gets all its data, including 
topology information, with SNMP polls and DNS queries.  It does not use CLI
access and has no need for privilege passwords.  Security features include a
wire-side Wireless Access Point (AP) locator.</p>
<p>Netdisco was created at the University of California, Santa Cruz (UCSC),
Networking and Technology Services (NTS) department.   UCSC continues to
support the development of Netdisco by providing development servers and beer.
The Netdisco project is hosted by Source Forge.</p>
<p>See <a href="http://www.netdisco.org">http://www.netdisco.org</a></p>
<p>
</p>
<hr />
<h1><a name="features">FEATURES</a></h1>
<p>
</p>
<h2><a name="switch_ports">Switch Ports</a></h2>
<p>From the web interface devices connected to switch and router ports are listed by 
MAC address.  A history of which switch ports a MAC address has been seen at is 
kept.  With a click the you can browse a network device connected to an uplink port.
With another click you can disable or enable the switch port, logging the reason, user and
date.</p>
<ul>
<li><strong><a name="item_central_location_to_disable_2fenable_switch_ports_">Central location to disable/enable switch ports.</a></strong>

<p>Network administrators can disable and enable ports without having to know enable or
privilege passwords.  Reasons for switching on/off ports are logged for end-of-the-year 
auditing and reporting.   Non-IOS savvy managers can control port access from a familiar
browser interface.  This feature was designed with a University Residential Networks (ResNet)
in mind.</p>
<p>Only users you specify in Netdisco will have access to switch off a port.  Netdisco
will also not allow people to switch off uplink ports by accident.</p>
</li>
<li><strong><a name="item_indexing">Supports Cisco VLAN Community String indexing (<code>public@101</code>)</a></strong>

<li><strong><a name="item_mac_address_to_switch_port_resolution">MAC Address to switch port resolution</a></strong>

<li><strong><a name="item_ip_address_to_switch_port_resolution">IP Address to switch port resolution</a></strong>

<li><strong><a name="item_find_switch_ports_with_multiple_nodes_attached">Find Switch Ports with multiple nodes attached</a></strong>

<li><strong><a name="item_find_nodes_using_multiple_ip_addresses">Find nodes using multiple IP addresses</a></strong>

<li><strong><a name="item_vendor">Find nodes by vendor (using MAC address OUI)</a></strong>

</ul>
<p>
</p>
<h2><a name="easy_administration">Easy Administration</a></h2>
<ul>
<li><strong><a name="item_interface">Controllable through Web Interface or Command Line Interface (CLI)</a></strong>

<li><strong><a name="item_speed">Database store for scalability and speed (Postgresql)</a></strong>

<li><strong><a name="item_easily_extendible_to_new_network_devices">Easily extendible to new network devices</a></strong>

<li><strong><a name="item_user_system_to_restrict_access_and_features">User system to restrict access and features</a></strong>

</ul>
<p>
</p>
<h2><a name="network_administration_and_security">Network Administration and Security</a></h2>
<ul>
<li><strong><a name="item_automatic_inventory_and_search_of_network_hardware">Automatic inventory and search of network hardware</a></strong>

<li><strong><a name="item_administratively_enable_2fdisable_switch_ports_fro">Administratively enable/disable switch ports from web interface with logging</a></strong>

<li><strong><a name="item_duplex_mismatch_finder">Duplex Mismatch Finder</a></strong>

<li><strong><a name="item_points">Find Wireless Access Points (APs) from wired-side of network</a></strong>

<li><strong><a name="item_layer_two_traceroute">Layer Two Traceroute</a></strong>

</ul>
<p>
</p>
<h2><a name="reporting">Reporting</a></h2>
<ul>
<li><strong><a name="item_graphing_of_network_topology_2e_clickable_image_2d">Graphing of network topology.  Clickable image-map of devices.  Link speed shown</a></strong>

<li><strong><a name="item_statistics_for_number_of_actual_nodes_connected_to">Statistics for number of actual nodes connected to network</a></strong>

</ul>
<p>
</p>
<h2><a name="inventory_of_network_devices">Inventory of Network Devices</a></h2>
<ul>
<li><strong><a name="item_system">by Operating System (IOS,CatOS,HP...)</a></strong>

<li><strong><a name="item_by_model_2c_vendor_2c_osi_layer_2c_dns_name">by Model, Vendor, OSI Layer, DNS Name</a></strong>

<li><strong><a name="item_blocking">Find device ports that are blocking (via Spanning Tree Protocol)</a></strong>

<li><strong><a name="item_find_devices_using_ip_27s_w_2fout_dns_entries">Find devices using IP's w/out DNS entries</a></strong>

</ul>
<p>
</p>
<h2><a name="supported_devices">SUPPORTED DEVICES</a></h2>
<p>Netdisco supports any Network device that talks SNMP and has basic information
available through MIB-II (RFC 1213).   Additional vendor-specific information
is available for a number of devices, but especially for Cisco, Extreme,
Foundry, HP, and Nortel/Bay devices.</p>
<p>Device support is handled through <a href="#item_snmp_3a_3ainfo"><code>SNMP::Info</code></a> -- a Perl module that is
an integral part of Netdisco that handles device-specific code.  See the
<code>Device Matrix</code> at <a href="http://snmp-info.sourceforge.net">http://snmp-info.sourceforge.net</a> for a list of 
devices that have been tested against Netdisco.  SNMP::Info can be extended
for new families of devices relatively easily with a little Perl knowledge.</p>
<p>
</p>
<hr />
<h1><a name="support">SUPPORT</a></h1>
<p>Please use the <code>netdisco-users</code> mailing list for all problems and comments.</p>
<p><a href="http://lists.sourceforge.net/lists/listinfo/netdisco-users">http://lists.sourceforge.net/lists/listinfo/netdisco-users</a></p>
<p>In case of bugs, please use the Bug interface from SourceForge page at:</p>
<p><a href="http://sourceforge.net/projects/netdisco">http://sourceforge.net/projects/netdisco</a></p>
<p>
</p>
<hr />
<h1><a name="glossary">GLOSSARY</a></h1>
<dl>
<dt><strong><a name="item_device">Device</a></strong>

<dd>
<p>Any device connected to the network that contributes to the physical topology.
Devices need to be accessible via SNMP.  A device usually has multiple interfaces
(ports) and can have multiple IP addresses.</p>
</dd>
</li>
<dt><strong><a name="item_node">Node</a></strong>

<dd>
<p>A node is anything connected to a device.   Nodes are uniquely identified by their
MAC addresses.  A node may or may not have IP addresses associated with it.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck">Macsuck</a></strong>

<dd>
<p><strong>Technical Answer</strong> : The process in Netdisco that goes out to all Layer-2 devices and 
gets the Forwarding Tables / CAM Tables.  Each row in the table maps a MAC
address to a switch port.   This process is what makes devices show up on
switch ports.</p>
</dd>
<dd>
<p>Netdisco will attempt to detect uplink ports in case you are missing topology data
during macsuck.  Check the logs of the macsuck / macwalk for notifications of
detected uplink ports, and add that data to your <em>netdisco-topology.txt</em>.</p>
</dd>
<dd>
<p><strong>Fun Answer</strong> - From Douglas M. McKeown :</p>
</dd>
<dd>
<p>``This is where you go to a switch (Layer 2) and find all
the MAC (or Ethernet Hardware) addresses which this device is connected to.
So you plug your Dell into your HP Switch and that HP Switch is uplinked to
your Core switch (not using the word router here.  we're talking simple,
physical network connections, sort of like electrical wires.)  Well your
Dell has a MAC address of let's say ''A``  and amazingly, your HP switch
has a MAC address of ''B`` and your Core switch has an address of ''1``.
Well if you Macsuck your Core switch, it doesn't have your Dell
connected to it, but it does have ''B`` which is another switch.  So you
Macsuck ''B`` and it has MAC addresses for 1, B and A!  You don't really
Macsuck an end device (your Dell).</p>
</dd>
<dd>
<p>So what do we know?</p>
</dd>
<dd>
<pre>
    - Core (1) knows about HP Switch &quot;B&quot;.
    - HP Switch &quot;B&quot; knows about Core (1) and Dell &quot;A&quot;.
    - Dell &quot;A&quot; knows about HP Switch &quot;B&quot;.</pre>
</dd>
<dd>
<p>Does ``1'' know about ``A'' ?  If it's a router it does.  Otherwise it asks
who has ``A'' and switch ``B'' says, I know!  So 1 goes to B which goes to
A.</p>
</dd>
<dd>
<p>Got it?``</p>
</dd>
</li>
<dt><strong><a name="item_arpnip">Arpnip</a></strong>

<dd>
<p>The process in Netdisco that goes out to every Layer-3 device and gets its ARP
cache.  Each entry in the ARP Cache maps a MAC address to an IP address.</p>
</dd>
<dd>
<p>This process is what lets Netdisco map an Ethernet address to an IP address.
Combined with the Macsuck process, Netdisco can ultimately resolve an IP address
to a switch port.</p>
</dd>
<dd>
<p>If you have a small network that only has layer-2 devices on it, and you
use a Linux or BSD box as your router, you will need to install net-snmp
on the machine, and then have netdisco discover that machine.  Otherwise
you will not be able to resolve a MAC address to an IP address.</p>
</dd>
</li>
<dt><strong><a name="item_cdp__2f_fdp__2f_lldp__2f_sonmp">CDP / FDP / LLDP / SONMP</a></strong>

<dd>
<p>Having topology information is crucial for Netdisco to function.  So.
if you network does not support one of the above Layer2 discover protocols,
you <strong>must</strong> put the information in the <em>netdisco-topology.txt</em> file.</p>
</dd>
<dd>
<p>See <a href="#topology_information">Topology Information</a> in this file.</p>
</dd>
<dd>
<p>From Douglas McKeown :</p>
</dd>
<dd>
<p>``CDP is the <strong>Cisco Discovery Protocol</strong>.  Sort of an add-on for when
switches talk to switches about who's connected to whom.  CDP quickly
tells other switches that it has switches connected.  Netdisco really
likes CDP a lot for mapping out the network and automatically
discovering the topology.   If your devices don't use CDP, then you need
to work with the <em>netdisco-topology.txt</em> file to create a layout of your
network.''</p>
</dd>
<dd>
<p>Note that LLDP (IEEE Standard), FDP (Foundry), and SONMP (Nortel/Bay) are
supported, and anywhere you see CDP you can assume we mean LLDP, FDP, and
SONMP too.</p>
</dd>
<dl>
<dt><strong><a name="item_security_warning">Security Warning</a></strong>

<dd>
<p><strong>WARNING</strong>!  There is a potential community string exposure when Netdisco is auto-discovering
network equipment (<code>netdisco</code> <a href="#item__2dr__7c_7c__2d_2ddiscoverall_root_device">-r</a>).  If a malicious host were to implement CDP and Netdisco were
to discover that host, Netdisco would send all read-only community strings to
that device in an attempt to add it to the topology.</p>
</dd>
<dd>
<p>There are two main ways to avoid this exposure:</p>
</dd>
<dl>
<dt><strong><a name="item_list_addresses_of_valid_devices">List addresses of valid devices</a></strong>

<dd>
<p>Use the <a href="#item_discover_only">discover_only</a> and/or <a href="#item_discover_no">discover_no</a> configuration keywords to
control what IP addresses netdisco will be permitted to visit.
<a href="#item_discover_only"><code>discover_only</code></a> is inclusive, and <a href="#item_discover_no"><code>discover_no</code></a> is exclusive;
it's recommended to use <a href="#item_discover_only"><code>discover_only</code></a> if feasible.</p>
</dd>
<dd>
<p>When using this method, check the backend log for devices visible via
CDP but not via SNMP.  These may point out the need to expand the
range that is discoverable, or may be instances of this class of attack.</p>
</dd>
<dd>
<p>Additionaly <a href="#item_discover_no_type"><code>discover_no_type</code></a> can be used to prevent netdisco
from visiting certain devices based on the device_type returned by CDP.</p>
</dd>
</li>
<dt><strong><a name="item_disable_cdp_and_other_discovery_protocols">Disable CDP and other discovery protocols</a></strong>

<dd>
<p>This solution involves disabling CDP and other discovery protocols
from your user-connection ports, and leaving it on on inter-device
ports.  Unfortunately, in some configurations, user-connection
ports <strong>are</strong> inter-device ports, e.g., especially when you want to
keep the ability to easily add a phone to a port that didn't have
one previously.</p>
</dd>
<dd>
<p>Sample <code>IOS</code> Code for above:</p>
</dd>
<dd>
<pre>
 interface range fastethernet1/1-32
  no cdp enable</pre>
</dd>
<dd>
<p>Make sure you don't disable CDP on any ports that are connected to
other pieces of infrastructure.
Also make sure you don't use the global command <code>no cdp run</code>, since that will
disable CDP entirely.</p>
</dd>
</li>
</dl>
</dl>
</dl>
<p>
</p>
<hr />
<h1><a name="install">INSTALL</a></h1>
<p>See the INSTALL document for instructions and requirements to install Netdisco.</p>
<p>
</p>
<hr />
<h1><a name="using_netdisco">USING NETDISCO</a></h1>
<p>
</p>
<h2><a name="components">Components</a></h2>
<p>Netdisco has three components :</p>
<ol>
<li><strong><a name="item_back_2dend">Back-end</a></strong>

<p>The back-end talks to devices via SNMP.  Contained in the back-end is the logic to create the topology,
collect statistics and generate graphs.</p>
<p>Most of the back-end is controlled by cron jobs.</p>
<p>A background daemon is put resident to run maintenance tasks collected from the front-end. This 
keeps these sometimes memory intensive tasks and code out of the httpd processes.</p>
</li>
<li><strong><a name="item_database">Database</a></strong>

<p>Netdisco uses PostgreSQL to store all its information.  Careful abstraction of the database calls
means that Netdisco can be ported to another SQL platform easily.  Hooks to use other databases are
present.</p>
</li>
<li><strong><a name="item_front_2dend">Front-end</a></strong>

<p>The front-end operates on stored data only.  This abstraction is both for speed and security.</p>
<p>Some front-end administration tasks are put in a queue in the database that a daemon running from
the back-end picks up and processes.</p>
<p>The number of people using Netdisco can scale with the web server capacity, and will create no extra load
on the devices.</p>
</li>
</ol>
<p>
</p>
<h2><a name="commandline_options">Command-Line Options</a></h2>
<dl>
<dt><strong><a name="item__2db__7c_7c__2d_2dbatchmode">-b || --batchmode</a></strong>

<dd>
<p>Batch Mode.  Redirect output to log file.  Log file directory set in configuration file 
under <a href="#item_datadir">datadir</a>.</p>
</dd>
</li>
<dt><strong><a name="item__2dc__7c_7c__2d_2dconfigfile_file">-C || --configfile file</a></strong>

<dd>
<p>Set Config file. Default is netdisco.conf.</p>
</dd>
</li>
<dt><strong><a name="item__2dd__7c_7c__2d_2ddebug">-D || --debug</a></strong>

<dd>
<p>DEBUG.  Sends copious information to STDOUT</p>
</dd>
</li>
<dt><strong><a name="item__2dl__7c_7c__2d_2dnologging">-L || --nologging</a></strong>

<dd>
<p>No Log.  This will not add entries to the <a href="#item_log">log</a> table.</p>
</dd>
</li>
<dt><strong><a name="item__2dn__7c_7c__2d_2dnodestoo">-n || --nodestoo</a></strong>

<dd>
<p>Delete Nodes.  Used with --expiredevice only.</p>
</dd>
</li>
<dt><strong><a name="item__2dn__7c_7c__2d_2dnewonly">-N || --newonly</a></strong>

<dd>
<p>New Only.  On a network discovery <a href="#item__2dr__7c_7c__2d_2ddiscoverall_root_device">-r</a>, only discover found devices that aren't in the database.</p>
</dd>
</li>
<dt><strong><a name="item__2dp__7c_7c__2d_2dport_port">-P || --port port</a></strong>

<dd>
<p>Port.  Specify Port for removal of nodes <a href="#item__2de__7c_7c__2d_2dexpirenodes_device">-e</a>.</p>
</dd>
</li>
<dt><strong><a name="item__2ds__7c_7c__2d_2ddumpsql">-S || --dumpsql</a></strong>

<dd>
<p>Debug.  <code>carp()</code> SQL commands.  Sets $netdisco::SQLCARP to 1.</p>
</dd>
</li>
<dt><strong><a name="item__2dv__7c_7c__2d_2darchive">-V || --archive</a></strong>

<dd>
<p>archiVe nodes.  Used with <a href="#item__2de__7c_7c__2d_2dexpirenodes_device">-e</a> only.</p>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="commandline_commands">Command-Line Commands</a></h2>
<dl>
<dt><strong><a name="item__2da__7c_7c__2d_2darpwalk">-a || --arpwalk</a></strong>

<dd>
<p>Arp Walk.  ArpNip each device that has Layer 3 capabilities.</p>
</dd>
</li>
<dt><strong><a name="item__2da__7c_7c__2d_2darpnip_device">-A || --arpnip device</a></strong>

<dd>
<p>ArpNip.  ArpNip's a single device.  See <a href="#item_arpnipper">ArpNipper</a> in Design.</p>
</dd>
<dd>
<p>Devices listed in <a href="#item_arpnip_no"><code>arpnip_no</code></a> in the config file are excluded.
If there is a <a href="#item_arpnip_only"><code>arpnip_only</code></a> entry in the config file, devices
not listed are excluded.
See the entry below.</p>
</dd>
</li>
<dt><strong><a name="item__2db__7c_7c__2d_2dbackup">-B || --backup</a></strong>

<dd>
<p>Backup and Nightly Maintenance.</p>
</dd>
<dl>
<dt><strong><a name="item_removes">Removes</a></strong>

<dd>
<p>Devices and nodes that are old using the <code>expire_*</code> config file directives (see below).</p>
</dd>
</li>
<dt><strong><a name="item_creates">Creates</a></strong>

<dd>
<p>Archive data files for <a href="#item_node">node</a>,<a href="#item_node_ip">node_ip</a>,<a href="#item_device">device</a>, and <a href="#item_device_ip">device_ip</a> tables.</p>
</dd>
</li>
<dt><strong><a name="item_calls">Calls</a></strong>

<dd>
<p>Database cleanup routines (<a href="#item__2dk__7c_7c__2d_2dcleannodes">-K</a>) as well.</p>
</dd>
</li>
<dt><strong><a name="item_exports">Exports</a></strong>

<dd>
<p>NMIS config file if <a href="#item_nmis_dump">nmis_dump</a> is set.</p>
</dd>
</li>
</dl>
<p>This routine should be run nightly.</p>
<p>For a full backup run <em>sql/pg --back</em> to backup the whole database.</p>
<dt><strong><a name="item__2dd__7c_7c__2d_2ddiscover_device">-d || --discover device</a></strong>

<dd>
<p>Discover Device.</p>
</dd>
<dd>
<p>IP addresses and subnets listed in <a href="#item_discover_no"><code>discover_no</code></a> in the config file
are excluded.
If there is a <a href="#item_discover_only"><code>discover_only</code></a> entry in the config file, IP addresses
and subnets not listed are excluded.
See the entry below.</p>
</dd>
</li>
<dt><strong><a name="item__2de__7c_7c__2d_2dexpirenodes_device">-e || --expirenodes device</a></strong>

<dd>
<p>Expire Nodes for given device. Use <a href="#item__2dv__7c_7c__2d_2darchive">-V</a> to archiVe instead of delete.  Specify a 
port with <a href="#item__2dp__7c_7c__2d_2dport_port">-P</a> to delete or archive nodes on a per port basis.</p>
</dd>
</li>
<dt><strong><a name="item__2d_2dexpire_2dnodes_2dsubnet_subnet">--expire-nodes-subnet subnet</a></strong>

<dd>
<p>Finds all devices in given subnet and runs expire nodes on each.   Will 
display devices effected and then ask for confirmation.</p>
</dd>
<dd>
<p>Subnet is specified in CIDR format :</p>
</dd>
<dd>
<pre>
    192.168.0.0/24</pre>
</dd>
</li>
<dt><strong><a name="item__2de__7c_7c__2d_2dexpiredevice_device">-E || --expiredevice device</a></strong>

<dd>
<p>Delete a device. Use <a href="#item__2dn__7c_7c__2d_2dnodestoo">-n</a> to delete nodes as well.</p>
</dd>
</li>
<dt><strong><a name="item__2df__7c_7c__2d_2ddiscoverfile_file">-F || --discoverfile file</a></strong>

<dd>
<p>Discover Device from given File.   Used to restore backed up info from <a href="#item__2db__7c_7c__2d_2dbackup">-B</a>, and to 
discover devices that are not available through topology information.  Use <a href="#item__2dt__7c_7c__2d_2dtopofile">-T</a> to 
only import Topology Information.</p>
</dd>
</li>
<dt><strong><a name="item__2dg__7c_7c__2d_2dgraph">-g || --graph</a></strong>

<dd>
<p>Graph.  Creates graph using GraphViz.  Can create image output (png,gif) or 
vector output (svg).</p>
</dd>
<dd>
<p>NOTE: You can safely ignore all warnings about <code>size too small for label</code>.</p>
</dd>
<dd>
<p>Make sure you have a relatively new version of GraphViz.  You need a newer
version of GraphViz if you get an error similar to:</p>
</dd>
<dd>
<pre>
  Creating CMAP : /usr/local/netdisco/html/netmap.map
    warning, language cmap not recognized, use one of: ps hpgl pcl mif...</pre>
</dd>
</li>
<dt><strong><a name="item__2dh__7c_7c__2d_2dhelp">-h || --help</a></strong>

<dd>
<p>Prints out command line usage.</p>
</dd>
</li>
<dt><strong><a name="item__2di__7c_7c__2d_2dchangeip_old_ip_new_ip">-i || --changeip old_ip new_ip</a></strong>

<dd>
<p>Change IP address of device.  Creates new entry, removes old one and moves nodes
over to the new one.</p>
</dd>
</li>
<dt><strong><a name="item__2di__7c_7c__2d_2dexpireips">-I || --expireips</a></strong>

<dd>
<p>Expire IP Addresses from <a href="#item_node_ip">node_ip</a> table.   This will delete entries from the node_ip table
that are not matching entries (MAC Addresses) found in the node or device_port tables.</p>
</dd>
</li>
<dt><strong><a name="item__2dk__7c_7c__2d_2dcleanalias">-k || --cleanalias</a></strong>

<dd>
<p>alias klean-up.  DANGEROUS.  Deletes from the <em>device</em> table any 
IP address that is found as an alias in the <em>alias</em> table.</p>
</dd>
</li>
<dt><strong><a name="item__2dk__7c_7c__2d_2dcleannodes">-K || --cleannodes</a></strong>

<dd>
<p>Database Node Klean-up. Permanently deletes nodes matching:</p>
</dd>
<ol>
<li><strong><a name="item_mac_addresses_that_are_switch_port_addresses">MAC Addresses that are Switch Port Addresses</a></strong>

<li><strong><a name="item_mac_addresses_that_are_listed_on_non_2dexistent_po">MAC Addresses that are listed on non-existent ports</a></strong>

<li><strong><a name="item_information">MAC Addresses that exist on ports with topology information (uplink ports)</a></strong>

</ol>
<dt><strong><a name="item__2dm__7c_7c__2d_2dmacwalk">-m || --macwalk</a></strong>

<dd>
<p>Mac Suck each device in the database that has Layer 2 capabilities.</p>
</dd>
</li>
<dt><strong><a name="item__2dm__7c_7c__2d_2dmacsuck_device">-M || --macsuck device</a></strong>

<dd>
<p>Mac Suck given device only.</p>
</dd>
<dd>
<p>Devices listed in <a href="#item_macsuck_no"><code>macsuck_no</code></a> in the config file are excluded.
If there is a <a href="#item_macsuck_only"><code>macsuck_only</code></a> entry in the config file, devices
not listed are excluded.
See the entry below.</p>
</dd>
</li>
<dt><strong><a name="item__2do__7c_7c__2d_2doui">-O || --oui</a></strong>

<dd>
<p>Import OUI information from oui.txt</p>
</dd>
</li>
<dt><strong><a name="item__2dp__7c_7c__2d_2ddaemon__5bstart_2cstop_2cstatus_">-p || --daemon [start,stop,status,restart]</a></strong>

<dd>
<p>Control the Admin Daemon.  Takes arguments (start,stop,status,restart).</p>
</dd>
</li>
<dt><strong><a name="item__2dr__7c_7c__2d_2ddiscoverall_root_device_list">-r || --discoverall root_device_list</a></strong>

<dd>
<p>Walk the network with the given (comma-seperated) root(s).
Use <a href="#item__2dn__7c_7c__2d_2dnewonly">-N</a> to discover new devices only.  Given root devices
will always be discovered.</p>
</dd>
</li>
<dt><strong><a name="item__2dr__7c_7c__2d_2drefresh">-R || --refresh</a></strong>

<dd>
<p>Refresh devices.  Will run a discover (<a href="#item__2dd__7c_7c__2d_2ddiscover_device">-d</a>) for each device in the database.</p>
</dd>
</li>
<dt><strong><a name="item__2dt__7c_7c__2d_2dtopofile">-T || --topofile</a></strong>

<dd>
<p>Import Topology Data.  Will import manual topology data stored in file specified by 
configuration option <a href="#item_topofile">topofile</a> . Use <a href="#item__2df__7c_7c__2d_2ddiscoverfile_file">-F</a> to specify a different file from the
command line.</p>
</dd>
<dd>
<p>It is not necessary to do this after every change.  This is only a convenience switch.</p>
</dd>
</li>
<dt><strong><a name="item__2du__7c_7c__2d_2duser__5buser_5d__5bpassword_5d__">-u || --user [user] [password] [port_control?] [admin?] [``full name'']</a></strong>

<dd>
<p>Add or Change a User.  Supply all four arguments (user pw port_control admin) for 
command-line control, or supply less for interactive prompts.</p>
</dd>
<dd>
<p>It's better to use interactive prompts so that the password doesn't get stored in your 
shell history file and exported to the process table.</p>
</dd>
</li>
<dt><strong><a name="item__2dv__7c_7c__2d_2dversion">-v || --version</a></strong>

</dl>
<p>
</p>
<h2><a name="features">Features</a></h2>
<dl>
<dt><strong><a name="item_admin_daemon">Admin Daemon</a></strong>

<dd>
<p>The admin daemon is a copy of <code>netdisco</code> that runs in the background.  From the web <code>Admin Panel</code>,
jobs are put in a queue in the database.  The daemon picks up these jobs and executes them from the 
back-end as user <code>netdisco</code>.  The daemon is restarted daily in a cron job, or can be manually started
as root :</p>
</dd>
<dd>
<pre>
    su - netdisco -c &quot;/usr/local/netdisco -p restart&quot;</pre>
</dd>
</li>
<dt><strong><a name="item_port_info__2f_jack_search">Port Info / Jack Search</a></strong>

<dd>
<p>This feature integrates Netdisco with other databases that have port info.</p>
</dd>
<dd>
<p>Port Info was designed around data coming out of a Pinnacles database at UCSC, and might
prove to be site-specific.   However, see <code>port_info.html</code> for a good example of how to access other
databases using the <a href="#item_netdisco_2epm"><code>netdisco.pm</code></a> SQL routines.</p>
</dd>
<dd>
<p>Enable this feature by setting <a href="#item_port_info"><code>port_info</code></a> to true in <code>netdisco.conf</code></p>
</dd>
</li>
<dt><strong><a name="item_port_control">Port Control</a></strong>

<dd>
<p>Port Control allows a user of Netdisco to administratively turn a port on or off.</p>
</dd>
<dd>
<p>To do this the back-end requires a read-write community string for the device in question. 
The admin daemon must also be enabled.  Netdisco keeps a log for each port holding information 
about why a port was turned on or off.</p>
</dd>
<dd>
<p>A reason for turning switch the port is chosen from a list to provide future audits of admin activity.  
The user and IP address of the request are stored.  To change the default reasons, modify the 
<code>%PORT_CONTROL_REASONS</code> hash in <a href="#item_netdisco_2epm"><code>netdisco.pm</code></a></p>
</dd>
<dd>
<p>Optionally if the <a href="#item_portctl_email"><code>portctl_email</code></a> setting is set in <code>netdisco.conf</code>, an e-mail is sent out with a 
notification of the switching.  Locally at UCSC that e-mail is sent to an administrative mailing list.</p>
</dd>
<dd>
<p>To turn this feature off uncheck the <a href="#item_port_control"><code>Port Control</code></a> checkbox from all users in the <code>Admin Panel</code>.</p>
</dd>
<dd>
<p>By default Netdisco will be allowed to shut off</p>
</dd>
<dd>
<pre>
    - Switch Ports
    - IP Phones
    - Router Ports that are NOT uplinks</pre>
</dd>
<dd>
<p>By setting certain config file directives you can allow Netdisco to shutoff uplink ports and
VLAN interfaces.  But this is <strong>REALLY NOT RECOMMENDED</strong>.  See below for the required
commands.</p>
</dd>
</li>
<dt><strong><a name="item_web_console">Web Console</a></strong>

<dd>
<p>The Web Console allows netdisco to front-end the web interface of a switch or router.  
Traffic can then be routed over https, through Netdisco's web server.  An additional security layer is added
by requiring the user to be logged into Netdisco. The normal security measures used by the 
device's web server are still active.</p>
</dd>
<dd>
<p>The Web console is a reverse proxy that runs on Apache.  You must enable it in <code>netdisco_apache.conf</code> and 
<code>netdisco_apache_dir.conf</code>.   The add devices and models to the configuration lines <a href="#item_web_console_vendors"><code>web_console_vendors</code></a> and
<a href="#item_web_console_models"><code>web_console_models</code></a> in <code>netdisco.conf</code>.</p>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="netdisco_maintenance">Netdisco Maintenance</a></h2>
<dl>
<dt><strong><a name="item_refreshing_a_device">Refreshing a device</a></strong>

<dd>
<p>To refresh or discover a device and its ports, use the <a href="#item__2dd__7c_7c__2d_2ddiscover_device">-d</a> command:</p>
</dd>
<dd>
<pre>
    netdisco -d mydevice</pre>
</dd>
</li>
<dt><strong><a name="item_importing_topology_information">Importing Topology Information</a></strong>

<dd>
<p>It is not necessary to import the topology information after changing <em>netdisco-topology.txt</em>.  You should
however restart the admin daemon.  The topology text file is re-parsed each time you run netdisco.</p>
</dd>
<dd>
<p>As a convenience you can use the topology file to quickly seed Netdisco with devices. 
To import all the topology information at once make sure the topology filename is set in <code>netdisco.conf</code>
and use the <a href="#item__2dt__7c_7c__2d_2dtopofile">-T</a> command:</p>
</dd>
<dd>
<pre>
    netdisco -T</pre>
</dd>
</li>
<dt><strong><a name="item_aborting_a_process_of_netdisco">Aborting a process of Netdisco</a></strong>

<dd>
<p>Hit Ctrl-C if you are running a netdisco process, or send the job the INT signal. 
The job can cleanup after itself, write out its stats and log entries.</p>
</dd>
<dd>
<pre>
    kill -INT jobpid</pre>
</dd>
<dd>
<p>There is currently no way to stop a job inside the Admin daemon.  Send the daemon an INT 
signal and it will terminate after its current job has completed.</p>
</dd>
</li>
<dt><strong><a name="item_changing_the_ip_address_of_a_device">Changing the IP Address of a Device</a></strong>

<dd>
<p>If a device is being replaced with a different device and a different IP, see <a href="#item_deleting_a_device">Deleting a Device</a>
below.</p>
</dd>
<dd>
<pre>
    netdisco -i old-ip-address new-ip-address</pre>
</dd>
<dd>
<p>Changing the IP address of a device will:</p>
</dd>
<ol>
<li><strong><a name="item_discover_the_new_device">Discover the new device</a></strong>

<li><strong><a name="item_remove_old_device_entry_2c_port_2c_and_aliases">Remove Old Device Entry, port, and aliases</a></strong>

<li><strong><a name="item_move_the_old_nodes_to_the_new_device_2e">Move the old nodes to the new device.</a></strong>

</ol>
<dt><strong><a name="item_auto_2ddeleting_old_data_from_the_database">Auto-Deleting Old Data From the Database</a></strong>

<dd>
<p>In order for Netdisco to be self-maintaining data has to be taken out of the 
database as well as put in.   The following config file directives are used to 
auto-prune stuff from the database :</p>
</dd>
<dl>
<dt><strong><a name="item_expire_devices">expire_devices</a></strong>

<dt><strong><a name="item_expire_nodes">expire_nodes</a></strong>

<dt><strong><a name="item_expire_nodes_archive">expire_nodes_archive</a></strong>

</dl>
<p>See each item's entry in the <a href="#config_file">Config File</a> Section below for more details.</p>
<p>The expire data routines are called from the <a href="#item__2db__7c_7c__2d_2dbackup">-B</a>/Backup routine, which should
be running nightly via cron.</p>
<dt><strong><a name="item_deleting_a_device">Deleting a Device</a></strong>

<dd>
<p>To delete a device use the <a href="#item__2de__7c_7c__2d_2dexpiredevice_device">-E</a> command followed by the device name or IP.  Set <a href="#item__2dn__7c_7c__2d_2dnodestoo">-n</a> to 
delete all the nodes seen on that device as well</p>
</dd>
<dd>
<p>This is rather permanent.  Make sure you run <a href="#item__2db__7c_7c__2d_2dbackup">-B</a>ackup before you do this.</p>
</dd>
</li>
<dt><strong><a name="item_deleting_nodes">Deleting Nodes</a></strong>

<dd>
<p>Nodes consist of two components -- the switch port to MAC address mapping in the <a href="#item_node"><code>node</code></a> table, 
and the MAC address to IP mapping in the <a href="#item_node_ip"><code>node_ip</code></a> table.</p>
</dd>
<dd>
<p>To remove nodes from a switch, use the Admin Panel on the web side and choose either
<code>Delete Nodes</code>  or <code>Archive Nodes</code>.   Archiving nodes will set the archive bit so that the 
data will be available, but not always showing.   You can also delete nodes from the command 
line using the <a href="#item__2de__7c_7c__2d_2dexpirenodes_device">-e</a> command with or without the <a href="#item__2dv__7c_7c__2d_2darchive">-V</a> flag.</p>
</dd>
<dd>
<p>Database Cleanup <a href="#item__2dk__7c_7c__2d_2dcleannodes">-K</a> will delete nodes that seem to be extraneous.  See <a href="#item__2dk__7c_7c__2d_2dcleannodes">-K</a> for more details.</p>
</dd>
<dd>
<p>Once you have cleared out nodes from a switch, then run <a href="#item__2di__7c_7c__2d_2dexpireips">-I</a> to remove unused node to IP mappings.</p>
</dd>
<dd>
<p>This is rather permanent.  Make sure you run <a href="#item__2db__7c_7c__2d_2dbackup">-B</a>ackup before you do this.</p>
</dd>
</li>
<dt><strong><a name="item_adding__2f_changing_users">Adding / Changing Users</a></strong>

<dd>
<p>The easiest way to add a user is to use the <code>Add User</code> form in the Admin Panel.  After first installing
Netdisco you need to add an admin user by running <a href="#item__2du__7c_7c__2d_2duser__5buser_5d__5bpassword_5d__">-u</a>.</p>
</dd>
</li>
<dt><strong><a name="item_migrating_the_users_table_to_a_new_host">Migrating the Users table to a new host</a></strong>

<dd>
<p>If you are moving your Netdisco install over to another machine and
you want to keep your users table, here is the process :</p>
</dd>
<dd>
<pre>
    source$ pg_dump -a -d -U netdisco -t users netdisco &gt; user_dump.sql
    source$ scp user_dump.sql dest:</pre>
</dd>
<dd>
<pre>
    dest$ cd /usr/local/netdisco/sql
    dest$ ./pg /path/to/user_dump.sql</pre>
</dd>
</li>
<dt><strong><a name="item_localhost">Localhost (127.0.0.1) is showing up on CDP Links</a></strong>

<dd>
<p>See ``How the Switch Selects the IP Address To Include in Outbound CDP
Packets'' in <a href="ftp://ftp.hp.com/pub/networking/software/59692375_e1.pdf">ftp://ftp.hp.com/pub/networking/software/59692375_e1.pdf</a></p>
</dd>
</li>
<dt><strong><a name="item_device_model_comes_up_as__27products_2e_27">Device Model comes up as 'Products.'</a></strong>

<dd>
<p>The device is probably newer than your Cisco MIBs.  Redownload <a href="ftp://ftp.cisco.com/pub/mibs/v2/v2.tar.gz">ftp://ftp.cisco.com/pub/mibs/v2/v2.tar.gz</a>
and install these newest mibs into <em>/usr/local/share/snmp/mibs</em>.</p>
</dd>
</li>
<dt><strong><a name="item_things_are_getting_really_slow">Things are getting Really slow</a></strong>

<dd>
<p>For some reason over here at UCSC, things get real slow in Postgres after a while.
Even though we are doing frequent VACUUM's on all the data, it seems to be dragging
down after a while.</p>
</dd>
<dd>
<p>This turns out to be an INDEX bloat problem on Postgres versions less than 7.4. 
Recently doing this on a Postgres 7.3 install changed the amount of space that
Netdisco's database was using from 16G to 400M !!!</p>
</dd>
<dd>
<p>In order to fix this we do a <code>VACUUM FULL ANALYZE VERBOSE</code> and <code>REINDEX</code> from <code>pg</code>.
This command locks each table before it does the VACUUM, and therefore can be more thorough.
It's a good idea to take netdisco down temporarily while you do this.  I do this about
once a month, or when I notice it dragging down.  Use <code>Netdisco Statistics</code> as a good metric
of things slowing down.  This may get fixed with changes in VACUUM in Postgres 7.4 and above.</p>
</dd>
<dd>
<p>Procedure for doing a vacuum full (as root):</p>
</dd>
<ol>
<li><strong><a name="item_shutdown_the_admin_daemon">Shutdown the admin daemon</a></strong>

<pre>
    /usr/local/netdisco/bin/netdisco_daemon stop</pre>
<li><strong><a name="item_clear_the_cron_tab_for_user_netdisco">Clear the cron tab for user netdisco</a></strong>

<pre>
    crontab -u netdisco -r</pre>
<li><strong><a name="item_comment_out_the_netdisco_config_file_includes_in_h">Comment out the netdisco config file Includes in httpd.conf</a></strong>

<li><strong><a name="item_restart_apache">Restart Apache</a></strong>

<pre>
    /usr/local/apache/bin/apachectl graceful</pre>
<li><strong><a name="item_check_to_see_if_any_netdisco_jobs_are_running_and_">Check to see if any netdisco jobs are running and wait for them or kill them</a></strong>

<pre>
    ps
    killall netdisco</pre>
<li><strong><a name="item_run_reindex_and_vacuum_full">Run REINDEX and  VACUUM FULL</a></strong>

<p>Before:</p>
<pre>
    df -h
    /usr/local/netdisco/sql/pg
        # before comparison :
        select relname, relpages from pg_class order by relpages desc;</pre>
<pre>
        REINDEX TABLE node;
        REINDEX TABLE node_ip;
        REINDEX TABLE device;
        REINDEX TABLE device_port;
        REINDEX TABLE device_port_log;
        VACUUM FULL ANALYZE VERBOSE;</pre>
<pre>
        # after comparison :
        select relname, relpages from pg_class order by relpages desc;
        \q</pre>
<p>After:</p>
<pre>
    df -h</pre>
</li>
<li><strong><a name="item_postgres">Restart Postgres (just for fun)</a></strong>

<pre>
    /usr/local/etc/rc.d/010.pgsql restart</pre>
<p>OR</p>
<pre>
    /etc/rc.d/init.d/pgsql restart</pre>
<p>OR</p>
<pre>
    /etc/rc.d/pgsql restart</pre>
<li><strong><a name="item_uncomment_lines_in_httpd_2econf">Uncomment lines in httpd.conf</a></strong>

<li><strong>Restart Apache</strong>

<pre>
    /usr/local/apache/bin/apachectl graceful</pre>
<li><strong><a name="item_reload_crontab_for_user_netdisco">Reload crontab for user netdisco</a></strong>

<pre>
    crontab -u netdisco /usr/local/netdisco/netdisco.crontab</pre>
<li><strong><a name="item_restart_admin_daemon">Restart Admin Daemon</a></strong>

<pre>
    /usr/local/netdisco/bin/netdisco_daemon start</pre>
</ol>
<dt><strong><a name="item_clearing_the_admin_queue">Clearing the Admin Queue</a></strong>

<dd>
<p>If your admin queue is just getting too long and you want to clear it
you can do it by just dropping the table and readding it.</p>
</dd>
<dd>
<pre>
    cd sql
    ./pg admin.sql</pre>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="topology_information">Topology Information</a></h2>
<p>Topology information is crucial to Netdisco's performance.  It allows the
application to know which ports are uplink ports and which have connected
nodes.  Ports that are uplink ports that are not marked so in Netdisco will
appear to <strong>steal</strong> MAC address entries from their rightful ports.  So it is
critical to use the topology file and CDP/FDP/SONMP to maintain a topology.</p>
<p>
</p>
<h3><a name="autodetection_of_uplink_ports">Autodetection of uplink ports</a></h3>
<p>During macsuck if Netdisco finds the MAC address of a known device or switch
port, then that port is marked as an uplink.  Nodes will not collect at these
switch ports, and a warning message will be printed.  Check the logs of 
your macsuck and macwalk jobs in order to find and correct autodetected 
uplink ports.  Add these ports to your netdisco-topology.txt file.</p>
<p>
</p>
<h3><a name="manual_topology_information">Manual Topology Information</a></h3>
<p>Netdisco will auto-discover the layer-two topology of a network using CDP.
However, many networks have parts of the topology that are not covered by CDP.</p>
<p>Use the manual topology file <code>netdisco-topology.txt</code> to supply the layout of
the network if your network has devices that don't talk CDP or misreport
information.</p>
<p>The manual topology file only requires one side of the data to be entered.
Both directions of a link will be forced to the given data if one side is
listed.</p>
<p><strong>File Format</strong></p>
<p>The format of the manual topology consists of four types of lines:</p>
<dl>
<dt><strong><a name="item__23comment">#comment</a></strong>

<dd>
<p>Comments are delimited with a <code>#</code> They can happen on any line.  Escape as <code>\#</code> if 
you need to use a literal pound sign.</p>
</dd>
</li>
<dt><strong><a name="item_routername">routername</a></strong>

<dd>
<p>Any line that does not start with <a href="#item_link_3a"><code>link:</code></a> or <a href="#item_alias_3a"><code>alias:</code></a> is assumed to be a the DNS name or 
IP address of a network device.</p>
</dd>
</li>
<dt><strong><a name="item_link_3a">link:</a></strong>

<dd>
<p>Lines that start with <a href="#item_link_3a"><code>link:</code></a> connect two devices together.  The format is</p>
</dd>
<dd>
<pre>
    link:outgoing port,destination device,Destination port</pre>
</dd>
<dd>
<p>The outgoing port belongs to the device listed above the <a href="#item_link_3a"><code>link:</code></a> line.</p>
</dd>
<dd>
<p>The Destination Device and Port tell Netdisco who is on the other end of this link.
The device can be a DNS name or an IP Address.</p>
</dd>
<dd>
<p><strong>NOTE</strong>: The port names must match exactly how Netdisco sees it.  Go to the 
device and check it out.  You might think of it as <code>port 1</code> but Netdisco might
think of it as <code>RMONPort26onunit1</code>.</p>
</dd>
</li>
<dt><strong><a name="item_alias_3a">alias:</a></strong>

<dd>
<p>Not implemented for output.  The backup file will have these lines just for informations'
sake.  Alias IPs on a device are found during discovery.</p>
</dd>
<dd>
<p>Many network devices like routers have multiple IP addresses assigned to them.  If the device
cannot or does not supply this information to Netdisco in a standard way, you can add IP
addresses used here.</p>
</dd>
</li>
</dl>
<p>White space in the file (except for line breaks) is ignored.  Tabbing over before <code>line:</code> lines
makes it easier to read, but is not required.</p>
<p><strong>File Uses</strong></p>
<p>Some reasons the manual topology file is used:</p>
<ol>
<li><strong><a name="item_man_in_the_middle">Man in the Middle</a></strong>

<p>Let's say you have two CDP speaking devices with a non-CDP speaking device in between them</p>
<pre>
    [Cisco] ---&gt; [Bay] ---&gt; [HP]</pre>
<p>The Cisco and HP devices (CDP speakers) find each other and the Bay device never appears. 
You would then have to add these lines to the topology file:</p>
<pre>
    ciscoswitch.my.company
        link:EtherNet0/1,bayswitch.my.company,25
    bayswitch.my.company
        link:26,hpswitch.my.company,J3</pre>
<p>This tells Netdisco that port <code>Ethernet0/1</code> on <code>ciscoswitch</code> is connected to Port <code>25</code> on <code>bayswitch</code>.
Then in turn Port 26 on <code>bayswitch</code> is connected to port <code>J3</code> on <code>hpswitch</code>.</p>
<p>A note about devices that are <em>CDP Aware</em> and that implement CDP:</p>
<p><em>CDP Aware</em> devices are devices that probably do not speak CDP (probably for legal reasons) but 
that are smart enough not to forward CDP packets.  Cisco devices that have CDP disabled are usually
still <em>CDP Aware</em> and will not forward the packets.   Man-in-the-middle situations occur when the device
both does not speak CDP and is not <em>CDP Aware</em>.</p>
</li>
<li><strong><a name="item_isolated_network_segment">Isolated Network Segment</a></strong>

<p>If you have a segment of your network that is not connected directly, or connected through a non physical
link like a VPN, then you might fudge an entry to connect that segment of the network with the main one.</p>
</li>
<li><strong><a name="item_attach_a_non_2dcdp_speaking_device">Attach a non-CDP speaking device</a></strong>

<p>Anywhere a device that does not supply topology information is connected to the network, an entry
must be added in the manual topology file.</p>
</li>
</ol>
<p>
</p>
<h2><a name="cron_jobs">Cron Jobs</a></h2>
<p>Netdisco is controlled via cron jobs.  Jobs are run as user <code>netdisco</code>.
Multiple jobs can be run at once.</p>
<p>The default jobs are :</p>
<ul>
<li><strong><a name="item_macsuck__2d_every_2_hours_macsuck_all_the_devices_">MacSuck - Every 2 hours MacSuck all the devices in the database.</a></strong>

<li><strong><a name="item_arpnip__2d_every_2_hours_arpnip_all_the_devices_in">ArpNip  - Every 2 hours ArpNip  all the devices in the database. (Offset from Macsuck by 1 hours)</a></strong>

<li><strong><a name="item_refresh_devices__2d_once_a_day_refresh_device_info">Refresh Devices - Once a day refresh device information.</a></strong>

<li><strong><a name="item_backup__2d_once_a_day_backup_information_2e">Backup - Once a day backup information.</a></strong>

<li><strong><a name="item_graph__2d_once_a_day_re_2dcreate_the_graph_2e">Graph - Once a day re-create the graph.</a></strong>

<li><strong><a name="item_week">Walk Network - Once a week (Wed @ 14:00) try and discover new devices.</a></strong>

<li><strong><a name="item_restart_admin_daemon__2d_once_a_day_just_for_good_">Restart Admin Daemon - Once a day just for good measure.</a></strong>

</ul>
<p>
</p>
<hr />
<h1><a name="config_file">Config File</a></h1>
<p>The settings in <code>netdisco.conf</code> are used both in the back-end and the front-end.</p>
<p>When you make a change in the config file that is used in the web front end, 
you must reload apache.  The config information is shared between processes for speed
and memory performance.</p>
<pre>
    su - -c &quot;/usr/local/apache/bin/apachectl restart&quot;</pre>
<p>Multiple config files can be used in the back-end by calling Netdisco with the
<code>-C</code> option:</p>
<pre>
    netdisco -C myotherfile.conf</pre>
<p>
</p>
<h2><a name="general_items">General Items</a></h2>
<dl>
<dt><strong><a name="item_domain">domain</a></strong>

<dd>
<p>STRING. Trimmed from all DNS names viewed.  Leave blank to show all domain names.  Add a dot 
in front of your value :</p>
</dd>
<dd>
<pre>
    .ucsc.edu</pre>
</dd>
</li>
<dt><strong><a name="item_home">home</a></strong>

<dd>
<p>PATH.  Full path to where netdisco lives.  Is the root path for all other files and paths.</p>
</dd>
</li>
<dt><strong><a name="item_customer">customer</a></strong>

<dd>
<p>STRING.  Name added to page titles and heading.</p>
</dd>
</li>
<dt><strong><a name="item_customericon">customericon</a></strong>

<dd>
<p>STRING.  URL,width,height - replaces discoball icon with custom logo.</p>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="database_maintenance">Database Maintenance</a></h2>
<p>New in version 0.93 these directives are included to help make
Netdisco more self-maintaining.</p>
<p><strong>Setting these will result in permanent data removal.</strong></p>
<dl>
<dt><strong>expire_devices</strong>

<dd>
<p>DAYS. Devices that have not been refreshed in this number 
of days will be removed.   All nodes connected to this device will be removed 
as well.</p>
</dd>
</li>
<dt><strong>expire_nodes</strong>

<dd>
<p>DAYS.  Nodes that have not been refreshed in this number of days will be removed from
the database.  Archived and non-archived nodes are removed.  This includes SwitchPort/MAC
and MAC/IP mappings.</p>
</dd>
</li>
<dt><strong>expire_nodes_archive</strong>

<dd>
<p>DAYS.  Archived data for switch-port/MAC and MAC/IP mappings older than this number
of days will be removed.</p>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="backend_items">Back-End Items</a></h2>
<dl>
<dt><strong><a name="item_arpnip_no">arpnip_no</a></strong>

<dd>
<p>LIST:string.  Devices that won't be arpnipped.  See <a href="#item_bulkwalk_no"><code>bulkwalk_no</code></a> for syntax.
If you have any layer-3 devices that have been discovered by netdisco
but are using proxy-ARP as a way to get to other devices, place them here.
Alternately, if you have many proxy-ARP clients but one (or a handful of)
central device with all of the proper ARP info, put that in <a href="#item_arpnip_only"><code>arpnip_only</code></a>.</p>
</dd>
</li>
<dt><strong><a name="item_arpnip_only">arpnip_only</a></strong>

<dd>
<p>LIST:string.  If present, only arpnip these devices.  See <a href="#item_bulkwalk_no"><code>bulkwalk_no</code></a> for syntax.</p>
</dd>
</li>
<dt><strong><a name="item_compress">compress</a></strong>

<dd>
<p>EXECUTABLE. Full path and command line arguments to the compression program used in <a href="#item_compresslogs">compresslogs</a></p>
</dd>
</li>
<dt><strong><a name="item_compresslogs">compresslogs</a></strong>

<dd>
<p>BOOLEAN. Compress log files?  See <a href="#item_compress">compress</a> entry above.</p>
</dd>
</li>
<dt><strong><a name="item_datadir">datadir</a></strong>

<dd>
<p>PATH. Full or relative path to the directory that backups and logs will be stored in</p>
</dd>
</li>
<dt><strong><a name="item_discover_no">discover_no</a></strong>

<dd>
<p>LIST:string.  IP addresses in this list will not be visited during discovery.
See <a href="#item_bulkwalk_no">bulkwalk_no</a> for syntax, except that only hostnames, IP addresses
and subnets are valid.</p>
</dd>
</li>
<dt><strong><a name="item_discover_no_type">discover_no_type</a></strong>

<dd>
<p>REGEX:string.  Place a pattern here to exclude the discovery of certain devices
based on the CDP device type information.  Good for excluding a whole device
class like lightweight access points or IP phones that have CDP but don't talk
SNMP.</p>
</dd>
</li>
<dt><strong><a name="item_discover_only">discover_only</a></strong>

<dd>
<p>LIST:string.  If present, discovery will be limited to only IP addresses
in this list.  If you have a management VLAN, put that subnet here
to avoid discovering user devices.
See <a href="#item_bulkwalk_no">bulkwalk_no</a> for syntax, except that only hostnames, IP addresses
and subnets are valid.</p>
</dd>
</li>
<dt><strong><a name="item_ignore_interfaces">ignore_interfaces</a></strong>

<dd>
<p>LIST:STRING  If present, device ports matching any of the items in this list
will be ignored by the discovery process. Note this may have side effects -
connected devices and nodes on those ports will in turn also not be
discovered.</p>
</dd>
<dd>
<p>Each item in the list is separated by a comma and may be a Perl regular
expression. A useful example for this option might be:</p>
</dd>
<dd>
<pre>
 EOBC,unrouted VLAN,StackPort,Control Plane Interface,SPAN (S|R)P Interface,StackSub</pre>
</dd>
</li>
<dt><strong><a name="item_ignore_private_nets">ignore_private_nets</a></strong>

<dd>
<p>Not fully implemented.</p>
</dd>
<dd>
<p>BOOLEAN. Set to true to ignore aliases that are part of private nets:</p>
</dd>
<dd>
<pre>
    10.0.0.0/8 172.16.0.0/16 and 192.168.0.0/24</pre>
</dd>
</li>
<dt><strong><a name="item_logextension">logextension</a></strong>

<dd>
<p>STRING. The extension to add to log files.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck_bleed">macsuck_bleed</a></strong>

<dd>
<p>BOOLEAN. Set to true will let nodes accumulate on uplink ports without topology information.
This is a debug option to help you figure out your topology and generally should not be set.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck_no">macsuck_no</a></strong>

<dd>
<p>LIST:string.  Don't macsuck these devices.  See <a href="#item_bulkwalk_no"><code>bulkwalk_no</code></a> for syntax.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck_only">macsuck_only</a></strong>

<dd>
<p>LIST:string.  If present, only macsuck these devices.  See <a href="#item_bulkwalk_no"><code>bulkwalk_no</code></a> for syntax.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck_no_vlan">macsuck_no_vlan</a></strong>

<dd>
<p>LIST:Strings.  Comma separated list of VLAN names not to visit when MACsucking.</p>
</dd>
<dd>
<p>This option was used to speed up MACsucking on certain Cisco Catalyst family devices
where you have to connect to each VLAN with SNMP to get the forwarding tables.   Certain
default VLANs will not answer to SNMP, and Netdisco has to wait for them to timeout.</p>
</dd>
<dd>
<p>VLANs listed here are overrided regardless of <a href="#item_macsuck_all_vlans">macsuck_all_vlans</a> value.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck_timeout">macsuck_timeout</a></strong>

<dd>
<p>SECONDS. Timeout for devices when mac sucking.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck_all_vlans">macsuck_all_vlans</a></strong>

<dd>
<p>BOOLEAN.  Set to macsuck all VLANs, not just the ones that are being used on ports.</p>
</dd>
<dd>
<p>This is a debug option. Set this if you think that the option of not macsucking VLANs that
aren't in use on device ports is some how interfering.</p>
</dd>
<dd>
<p>Setting this would revert macsuck to the same behavior as 0.93 and before.</p>
</dd>
<dd>
<p>Does not override <a href="#item_macsuck_no_vlan">macsuck_no_vlan</a>.</p>
</dd>
</li>
<dt><strong><a name="item_max_procs">max_procs</a></strong>

<dd>
<p>INTEGER.  The number of simultaneous processes to use when collecting data
from devices.  Using several processes speeds up data collection, but uses
more database resources.  Be careful of using up all of your database
connection handles.  Typical values are 15-25.</p>
</dd>
<dd>
<p>Note that the load average will be quite high with this option, very
nearly the same as the value of max_procs.  However, that's because
each of these processes spends much of its time waiting for responses
from the device, so is ready to run.  The high load average doesn't
affect the usability of the system in the same way that a high load
average caused by cpu-bound jobs would.</p>
</dd>
</li>
<dt><strong><a name="item_nbt_days">nbt_days</a></strong>

<dd>
<p>DAYS.  The maximum age of a node for it to be checked for NetBIOS
information.  Default 7.</p>
</dd>
</li>
<dt><strong><a name="item_nmis_dump">nmis_dump</a></strong>

<dd>
<p>FILENAME.  Set this option to have <code>nightly()</code> (-B) dump an NMIS <a href="http://www.sins.com.au/nmis">http://www.sins.com.au/nmis</a> 
style Config file.  Warning, this file will contain SNMP Community strings.</p>
</dd>
<dd>
<p>Optional Override options are :</p>
</dd>
<dl>
<dt><strong><a name="item_nmis_group">nmis_group</a></strong>

<dd>
<p>STRING.  Group to use with nmis_dump.  Default <code>Network</code></p>
</dd>
</li>
<dt><strong><a name="item_nmis_role">nmis_role</a></strong>

<dd>
<p>STRING.  Role to use with nmis_dump.  Default <code>core</code></p>
</dd>
</li>
<dt><strong><a name="item_nmis_collect">nmis_collect</a></strong>

<dd>
<p>STRING.  Collect option to use with nmis_dump.  Default <code>true</code></p>
</dd>
</li>
<dt><strong><a name="item_nmis_active">nmis_active</a></strong>

<dd>
<p>STRING.  Active option for nmis_dump file. Default <code>true</code></p>
</dd>
</li>
<dt><strong><a name="item_nmis_net">nmis_net</a></strong>

<dd>
<p>STRING.  Net identifier to use.  Default <code>lan</code></p>
</dd>
</li>
<dt><strong><a name="item_nmis_port">nmis_port</a></strong>

<dd>
<p>INT. SNMP Port to list in nmis_dump file.  Default <code>161</code></p>
</dd>
</li>
</dl>
<dt><strong><a name="item_node_monitor_email">node_monitor_email</a></strong>

<dd>
<p>STRING.  If set, consult the node_monitor table for MAC addresses that are being
monitored after every macwalk.  If any of the monitored MAC addresses appear or
move, send an email to the node_monitor_email setting and any cc address listed
in the database.  Note that the node_monitor table must currently be maintained
via raw sql access, there is no admin page for it.</p>
</dd>
</li>
<dt><strong><a name="item_reverse_sysname">reverse_sysname</a></strong>

<dd>
<p>BOOLEAN.  Turn this on to have Netdisco do a reverse lookup of the sysName.0 field to use
as the management IP address for a device.  See bug 810939 and <code>device_root()</code> for more info.
Default <code>false</code></p>
</dd>
</li>
<dt><strong><a name="item_store_modules">store_modules</a></strong>

<dd>
<p>BOOLEAN.  Set to false to skip the module inventory on device discovery.
The module inventory can double the device discovery time so if you
aren't using the information you can skip it.</p>
</dd>
</li>
<dt><strong><a name="item_store_wireless_clients">store_wireless_clients</a></strong>

<dd>
<p>BOOLEAN.  Set to false to skip the wireless client information
gathering.  This is captured at macsuck time, so if you aren't using
the information you can skip it.</p>
</dd>
</li>
<dt><strong><a name="item_topofile">topofile</a></strong>

<dd>
<p>FILE. Full path of the file that contains manual topology information.  Defaults to
<em>netdisco-topology.txt</em></p>
</dd>
</li>
<dt><strong><a name="item_timeout">timeout</a></strong>

<dd>
<p>SECONDS. Timeout for refreshing or discovering a device</p>
</dd>
</li>
</dl>
<p>
</p>
<h3><a name="admin_panel">Admin Panel</a></h3>
<dl>
<dt><strong><a name="item_daemon_bg">daemon_bg</a></strong>

<dd>
<p>BOOLEAN.  Run daemon in the background?</p>
</dd>
</li>
<dt><strong><a name="item_daemon_pid">daemon_pid</a></strong>

<dd>
<p>FILE.  Filename for the pid file used by admin daemon.  Must be writable by
daemon user.</p>
</dd>
</li>
<dt><strong><a name="item_daemon_poll">daemon_poll</a></strong>

<dd>
<p>SECONDS. Time to wait to check for new items in the queue.</p>
</dd>
</li>
</dl>
<p>
</p>
<h3><a name="database_settings">Database Settings</a></h3>
<p>The five database settings are <code>db</code> , <code>db_user</code>, <code>db_pw</code>, <code>db_opts</code>, and <code>db_env</code>.</p>
<p>You can run multiple database types in Netdisco.  See <a href="#item_port_info"><code>port_info</code></a> for an instance of this.</p>
<p>For each of the above settings, the database shortcut name (you choose) is inserted after <code>db</code>.</p>
<p>Postgres is the required first database, and uses the short name <code>Pg</code>.</p>
<p>The following lines must be added :</p>
<dl>
<dt><strong><a name="item_db_pg">db_Pg</a></strong>

<dd>
<p>STRING. Database connect string to give to DBI.</p>
</dd>
<dd>
<p>Default : <code>dbi:Pg:dbname=netdisco</code></p>
</dd>
</li>
<dt><strong><a name="item_db_pg_user">db_Pg_user</a></strong>

<dd>
<p>STRING. Database user</p>
</dd>
</li>
<dt><strong><a name="item_db_pg_pw">db_Pg_pw</a></strong>

<dd>
<p>STRING. Database Password</p>
</dd>
</li>
<dt><strong><a name="item_db_pg_opts">db_Pg_opts</a></strong>

<dd>
<p>HASH.   Options to add to the connect string.</p>
</dd>
<dd>
<p>Default : <code>PrintError =&gt; 1, AutoCommit =&gt; 1</code></p>
</dd>
</li>
<dt><strong><a name="item_db_pg_env">db_Pg_env</a></strong>

<dd>
<p>HASH.  Environment variables to be set before running database calls.
Separate multiple entries with commas.</p>
</dd>
<dd>
<p>Mainly used for Oracle.</p>
</dd>
<dd>
<p>Default : not set.</p>
</dd>
<dd>
<p>Example :</p>
</dd>
<dd>
<pre>
 db_Oracle_env  = ORACLE_HOME =&gt; /usr/local/oracle7, ORACLE_STUFF=&gt;1</pre>
</dd>
</li>
</dl>
<p>
</p>
<h3><a name="snmp_settings">SNMP Settings</a></h3>
<dl>
<dt><strong><a name="item_bulkwalk_off">bulkwalk_off</a></strong>

<dd>
<p>BOOLEAN.  Set to true to use GETNEXT instead of BULKWALK for every device.  
This slows things down, but might be necessary for problem devices.</p>
</dd>
<dd>
<p>Set to false to use BULKWALK even if netdisco thinks you have a buggy
version of Net-SNMP (e.g., because your installation is patched)</p>
</dd>
<dd>
<p>Other solutions include addding <code> sub bulkwalk_off { 1; } </code> to the device
class that is misbehaving in SNMP::Info.  This will turn off bulkwalk for a
class of devices, not all.</p>
</dd>
<dd>
<p>Also see <a href="#item_bulkwalk_no">bulkwalk_no</a> to turn BULKWALK off on a per-device or device class level.</p>
</dd>
<dd>
<p>Default is on.  SNMP::Info 1.0 or higher required.</p>
</dd>
</li>
<dt><strong><a name="item_bulkwalk_no">bulkwalk_no</a></strong>

<dd>
<p>LIST:STRING.   A comma separated list of devices to not bulkwalk</p>
</dd>
<dd>
<p>This list can take five different inputs:</p>
</dd>
<dl>
<dt><strong><a name="item_hostname_or_ip">Hostname or IP</a></strong>

<dd>
<p>Simply put the device's name or IP address in the list.</p>
</dd>
<dd>
<pre>
    switch1, switch2, switch3</pre>
</dd>
</li>
<dt><strong><a name="item_model_3aregex">model:regex</a></strong>

<dd>
<p>Add an entire model type for excluding from bulkwalking.</p>
</dd>
<dd>
<p>This can be a simple string like <code>6500</code> or it could be a regular expression like
<code>(2512|65\d\d)</code>.  The regex must match the whole string (it's anchored).</p>
</dd>
</li>
<dt><strong><a name="item_vendor_3aregex">vendor:regex</a></strong>

<dd>
<p>Add an entire vendor type for excluding form bulkwalking.</p>
</dd>
<dd>
<p>This can be a simple string like <code>hp</code> or it could be a regular expression like
<code>(cisco|hp)</code>. The regex must match the whole string (it's anchored).</p>
</dd>
</li>
<dt><strong><a name="item_subnet">Subnet</a></strong>

<dd>
<p>You can exclude a whole subnet of devices from bulkwalking.  Use CIDR notation.</p>
</dd>
<dd>
<pre>
 128.1.0.0/16</pre>
</dd>
</li>
<dt><strong><a name="item_blanket_wildcard">Blanket Wildcard</a></strong>

<dd>
<p>You can use a single asterix <code>*</code> to specify that all devices not 
be bulkwalked.</p>
</dd>
</li>
</dl>
<dt><strong><a name="item_bulkwalk_repeaters">bulkwalk_repeaters</a></strong>

<dd>
<p>INT.  Sets MaxRepeaters on BULKWALK operations.  See <code>perldoc SNMP</code> for more info.</p>
</dd>
<dd>
<p>Default is 20.  SNMP::Info 1.0 or higher required.</p>
</dd>
</li>
<dt><strong><a name="item_community">community</a></strong>

<dd>
<p>LIST:STRING. A comma separated list of community strings to try on each device.</p>
</dd>
</li>
<dt><strong><a name="item_community_rw">community_rw</a></strong>

<dd>
<p>LIST:STRING.  OPTIONAL. A comma separated list of Read-Write community strings.</p>
</dd>
<dd>
<p>This is only necessary if you turn on the <code>port_control</code> command.</p>
</dd>
</li>
<dt><strong><a name="item_get_community">get_community</a></strong>

<dd>
<p>STRING.  An external program to run to get the community string for a given
device.  This is useful if, for example, you have you devices already configured
in another NMS and you want to use that information instead of configuring
<a href="#item_community"><code>community</code></a> and/or <a href="#item_community_rw"><code>community_rw</code></a> in this file.</p>
</dd>
<dd>
<p>The strings %IP% and %HOST% are replaced by the IP address and the hostname
(or IP address if no hostname is known) of the system being contacted.</p>
</dd>
<dd>
<p>The command must return output in the following form:</p>
</dd>
<dd>
<pre>
    community=&lt;list of readonly-communities&gt;
    setCommunity=&lt;list of write-communities&gt;</pre>
</dd>
<dd>
<p>If the community string is not known for the given system, the command
should return no output and the community strings configured in netdisco
will be used.</p>
</dd>
</li>
<dt><strong><a name="item_mibdirs">mibdirs</a></strong>

<dd>
<p>LIST:STRING.  A comma separated list of directories to search for MIB files.</p>
</dd>
</li>
<dt><strong><a name="item_nonincreasing">nonincreasing</a></strong>

<dd>
<p>BOOLEAN.  Setting this to true will allow the bulkwalk of devices that have
tables with  non-increasing OIDs.  The default is to not allow this behavior to
prevent problem devices from looping indefinitely.   Requires Net-SNMP 5.3 or higher.</p>
</dd>
<dd>
<p>See patch # 1364650 in Net-SNMP or bug # 1176130.</p>
</dd>
</li>
<dt><strong><a name="item_snmpforce_v1">snmpforce_v1</a></strong>

<dd>
<p>LIST:STRING.   A comma separated list of devices.  Forces matching
devices to use SNMPv1</p>
</dd>
<dd>
<p>See <a href="#item_bulkwalk_no">bulkwalk_no</a> for syntax.</p>
</dd>
</li>
<dt><strong><a name="item_snmpforce_v2">snmpforce_v2</a></strong>

<dd>
<p>LIST:STRING.   A comma separated list of devices.  Forces matching
devices to use SNMPv2c</p>
</dd>
<dd>
<p>See <a href="#item_bulkwalk_no">bulkwalk_no</a> for syntax.</p>
</dd>
</li>
<dt><strong><a name="item_snmpforce_v3">snmpforce_v3</a></strong>

<dd>
<p>LIST:STRING.   A comma separated list of devices.  Forces matching
devices to use SNMPv3.</p>
</dd>
<dd>
<p>See <a href="#item_bulkwalk_no">bulkwalk_no</a> for syntax.</p>
</dd>
</li>
<dt><strong><a name="item_snmpver">snmpver</a></strong>

<dd>
<p>INT. Default version of SNMP protocol to connect with.</p>
</dd>
</li>
<dt><strong><a name="item_snmptimeout">snmptimeout</a></strong>

<dd>
<p>INT. Settings for 'Timeout' field passed to SNMP::Session.  Micro-seconds before
retry, Default 1000000 micro-seconds = 1 second.</p>
</dd>
</li>
<dt><strong><a name="item_snmpretries">snmpretries</a></strong>

<dd>
<p>INT. Settings for 'Retries' field passed to SNMP::Session</p>
</dd>
</li>
<dt><strong><a name="item_v3_users">v3_users</a></strong>

<dd>
<p>LIST.  The users to try for SNMPv3 (like <a href="#item_community">community</a> for SNMPv1/SNMPv2)</p>
</dd>
</li>
<dt><strong><a name="item_v3_users_rw">v3_users_rw</a></strong>

<dd>
<p>LIST.  The users to try for SNMPv3 read-write access.</p>
</dd>
</li>
<dt><strong><a name="item_v3_user_string_2e_colon_seperated_values_3a_user_3">v3_user
STRING.  Colon seperated values: user:auth/enc[:authproto:authpass[:privproto:privpass]]</a></strong>

<dd>
<p>user is the SNMPv3 username, as listed in v3_users or v3_users_rw.</p>
</dd>
<dd>
<p>auth/enc specifies what levels of authorization/privacy you are configuring.
The possible values are:</p>
</dd>
<dl>
<dt><strong><a name="item_none">none</a></strong>

<dd>
<p>only use noAuthNoPriv, the user has no authorization or privacy configured.</p>
</dd>
</li>
<dt><strong><a name="item_auth">auth</a></strong>

<dd>
<p>Use authNoPriv - authorization but no privacy.</p>
</dd>
</li>
<dt><strong><a name="item_enc">enc</a></strong>

<dd>
<p>Use authPriv - authorization and privacy for all requests.</p>
</dd>
</li>
<dt><strong><a name="item_auth_2cenc">auth,enc</a></strong>

<dd>
<p>Use authNoPriv for read and authPriv for write.</p>
</dd>
</li>
</dl>
<p>authproto is the authorization protocol, and can be any that the underlying
library supports, e.g., SHA or MD5.</p>
<p>authpass is the authorization pass phrase.</p>
<p>privproto is the privacy proto, e.g., DES or AES.</p>
<p>privpass is the privacy pass phrase.</p>
<p>No support is currently provided for providing hexadecimal keys directly.
Such support might use the prefix ``0x'' to identify a hex key, so be careful
how you choose your pass phrases.</p>
</dl>
<p>
</p>
<h2><a name="port_control">Port Control</a></h2>
<dl>
<dt><strong><a name="item_portctl_email">portctl_email</a></strong>

<dd>
<p>EMAIL.  Address that reports of use of <a href="#item_port_control"><code>Port Control</code></a> are sent to.</p>
</dd>
</li>
<dt><strong><a name="item_portctl_nophones">portctl_nophones</a></strong>

<dd>
<p>BOOLEAN.  Set to True to make sure an IP Phone port never can be turned off/on.  Default false.</p>
</dd>
</li>
<dt><strong><a name="item_portctl_timeout">portctl_timeout</a></strong>

<dd>
<p>SECONDS.  Amount of time to wait for a response from the admin daemon.</p>
</dd>
</li>
<dt><strong><a name="item_portctl_uplinks">portctl_uplinks</a></strong>

<dd>
<p>BOOLEAN. Set to True to allow Netdisco to be able to disable Uplinks. (Router Interfaces too)</p>
</dd>
<dd>
<p>Default False.</p>
</dd>
<dd>
<p><strong>EXTREMELY VERY DANGEROUS</strong> - Turning off uplinks will take out chunks of your 
network.</p>
</dd>
</li>
<dt><strong><a name="item_portctl_vlans">portctl_vlans</a></strong>

<dd>
<p>BOOLEAN. Set to True to allow Netdisco to be able to disable VLAN interfaces.</p>
</dd>
<dd>
<p>Default False.</p>
</dd>
<dd>
<p><strong>EXTREMELY VERY DANGEROUS</strong> - Turning off a VLAN could take out most of your 
network.</p>
</dd>
</li>
<dt><strong><a name="item_vlanctl">vlanctl</a></strong>

<dd>
<p>BOOLEAN. Set to True to allow Netdisco to be able to change the default VLAN on an interface.</p>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="web_settings">Web Settings</a></h2>
<dl>
<dt><strong><a name="item_port_info">port_info</a></strong>

<dd>
<p>BOOLEAN.  Turns on the <code>Port Info</code> and <code>Jack Search</code> features.</p>
</dd>
</li>
<dt><strong><a name="item_secure_server">secure_server</a></strong>

<dd>
<p>BOOLEAN. If a secure server is present.</p>
</dd>
<dd>
<p>Requires web login, password changing and all admin functions to be run in secure space.</p>
</dd>
</li>
<dt><strong><a name="item_traceroute">traceroute</a></strong>

<dd>
<p>BOOLEAN.  If the traceroute button should be present in the top bar.  The
L2 Traceroute function has limits and may be slow on large networks, so the
link to it can be disabled.</p>
</dd>
</li>
<dt><strong><a name="item_web_console_models">web_console_models</a></strong>

<dd>
<p>LIST:STRING.  Comma separated list of models that want to use the Web Console</p>
</dd>
</li>
<dt><strong><a name="item_web_console_vendors">web_console_vendors</a></strong>

<dd>
<p>LIST:STRING.  Comma separated list of vendors that use the Web Console.</p>
</dd>
</li>
<dt><strong><a name="item_webpath">webpath</a></strong>

<dd>
<p>PATH. URL Path added to the beginning of links on the web front-end</p>
</dd>
</li>
<dt><strong><a name="item_websession">websession</a></strong>

<dd>
<p>MINUTES.  Amount of time a session lasts before someone has to login again.</p>
</dd>
</li>
<dt><strong><a name="item_apache_auth">apache_auth</a></strong>

<dd>
<p>BOOLEAN. Whether to use Apache-based authentication.  If this is configured
both here and in netdisco_apache_dir.conf, then logins will trust the
REMOTE_USER set by Apache.  If the user is found in the user database,
then the appropriate privileges are applied; if the user is not found then
they have access but no port control or admin access.  There is another link
on the sidebar, ``Netdisco Login'' to log in using the netdisco user database.</p>
</dd>
</li>
</dl>
<p>
</p>
<h3><a name="ldap_settings">LDAP Settings</a></h3>
<dl>
<dt><strong><a name="item_ldap_server">ldap_server</a></strong>

<dd>
<p>LIST:STRING.  Comma separated list of LDAP servers.  If using Active Directory
these would be domain controllers.</p>
</dd>
</li>
<dt><strong><a name="item_ldap_user_string">ldap_user_string</a></strong>

<dd>
<p>STRING.  String to construct the user portion of the DN.  %USER% is a variable
which will be replaced at runtime with the logon name entered on the logon
page of the application.  Examples:  cn=%USER%, uid=%USER%.  Active
Directory users may use DOMAIN\%USER% and skip all other options except
ldap_server as this notation eliminates the need to construct the full
distinguished name.</p>
</dd>
</li>
<dt><strong><a name="item_ldap_base">ldap_base</a></strong>

<dd>
<p>STRING.  String which indicates where in the hierarchy to begin searches.
If a proxy user is not defined and anonymous binds are not enabled this
value will be appended to the ldap_user_string to construct the distinguished
name for authentication.</p>
</dd>
</li>
<dt><strong><a name="item_ldap_proxy_user">ldap_proxy_user</a></strong>

<dd>
<p>STRING.  User to bind with to perform searches.  If defined as anonymous, then
anonymous binds will be performed and ldap_proxy_pass will be ignored.  For
organizations with users in multiple OU's this option can be used to
search for the user and construct the DN based upon the result.</p>
</dd>
</li>
<dt><strong><a name="item_ldap_proxy_pass">ldap_proxy_pass</a></strong>

<dd>
<p>STRING.  Proxy user password.  Ignored if proxy user defined as anonymous.</p>
</dd>
</li>
<dt><strong><a name="item_ldap_opts">ldap_opts</a></strong>

<dd>
<p>HASH.   Options to add to the connect string.  Normally only needed if server
does not support LDAPv3.</p>
</dd>
</li>
<dt><strong><a name="item_ldap_tls_opts">ldap_tls_opts</a></strong>

<dd>
<p>HASH.   If defined, the connection will use Transport Layer Security (TLS)
which provides an encrypted connection. TLS is the preferred method of
encryption, ldaps (port 636) is not supported.  This is only possible if
using LDAPv3 and the server supports it.  These are the options for the
TLS connection.  See the Net::LDAP documentation under start_tls for options,
but the defaults should work in most cases.</p>
</dd>
</li>
<dt><strong><a name="item_example_configuration_to_use_microsoft_active_dire">Example configuration to use Microsoft Active Directory</a></strong>

<dd>
<pre>
 ldap_server          = AD-Domain-Controller1,AD-Domain-Controller2
 ldap_user_string     = DOMAIN\%USER%</pre>
</dd>
<dd>
<p>Note:  Only one domain is currently supported in this configuration</p>
</dd>
<dt><strong><a name="item_example_configuration_to_use_novell_e_2ddirectory">Example configuration to use Novell E-Directory</a></strong>

<dd>
<pre>
 ldap_server          = LDAP-Server-1,LDAP-Server-2
 ldap_user_string     = cn=%USER%
 ldap_base            = o=MYORGANIZATION
 ldap_proxy_user      = anonymous</pre>
</dd>
<dd>
<p>Note:  This configuration will support users split across multiple containers
as long as the containers exist below MYORGANIZATION</p>
</dd>
</dl>
<p>
</p>
<h3><a name="graph_settings">Graph Settings</a></h3>
<dl>
<dt><strong><a name="item_edge_color">edge_color</a></strong>

<dd>
<p>STRING. Default color for link between devices.</p>
</dd>
</li>
<dt><strong><a name="item_graph">graph</a></strong>

<dd>
<p>FILE. Full path and name to the GIF graph of the network.  Path should be the same
as in the <code>netmap.html</code> component.</p>
</dd>
</li>
<dt><strong><a name="item_graph_bg">graph_bg</a></strong>

<dd>
<p>STRING. Background color for the graph.</p>
</dd>
</li>
<dt><strong><a name="item_graph_color">graph_color</a></strong>

<dd>
<p>STRING. Text color for the graph</p>
</dd>
</li>
<dt><strong><a name="item_graph_default">graph_default</a></strong>

<dd>
<p>STRING. Default type of graph to view in NetMap (svg,gif,png).  Optional,
defaults to <code>svg</code>.</p>
</dd>
</li>
<dt><strong><a name="item_graph_epsilon">graph_epsilon</a></strong>

<dd>
<p>INT. Sets the <code>epsilon</code> attribute in <code>GraphViz</code> used to control the graph solver.
Set to an integer value.  This will improve the mapping and visual quality of
them graph. Each integer step can mean an exponential time increase in the solving
of the graph.</p>
</dd>
</li>
<dt><strong><a name="item_graph_clusters">graph_clusters</a></strong>

<dd>
<p>BOOLEAN.  Creates clusters of nodes based on their location field.
Best with <a href="#item_graph_layout">graph_layout</a> <code>fdp</code>.  Only use if all or most
devices in a given location have the same location string.</p>
</dd>
</li>
<dt><strong><a name="item_graph_layout">graph_layout</a></strong>

<dd>
<p>STRING.  Choose program to render graph with.  Valid options are <code>neato</code>, <code>twopi</code>, <code>circo</code> and <code>fdp</code>.</p>
</dd>
</li>
<dt><strong><a name="item_graph_fontpath">graph_fontpath</a></strong>

<dd>
<p>STRING.  Path for graphviz to find font files to be used for <a href="#item_node_font">node_font</a>.  Defaults to <a href="#item_home">home</a>.</p>
</dd>
</li>
<dt><strong><a name="item_graph_map">graph_map</a></strong>

<dd>
<p>FILE. Set to Full path and name to the ISMAP data for the network.  Path should be the 
same as in the <code>netmap.html</code> component.</p>
</dd>
</li>
<dt><strong><a name="item_graph_nodesep">graph_nodesep</a></strong>

<dd>
<p>FLOAT.  Node Separation (in inches) of nodes in graph.</p>
</dd>
</li>
<dt><strong><a name="item_graph_overlap">graph_overlap</a></strong>

<dd>
<p>BOOLEAN. Parameter passed to <code>GraphViz</code> for the <code>overlap=&quot;&quot;</code> feature.</p>
</dd>
</li>
<dt><strong><a name="item_graph_png">graph_png</a></strong>

<dd>
<p>FILE. Full path and name to the PNG graph of the network.  Path should be the same
as in the <code>netmap.html</code> component.  Use this if you prefer not to use GIF, or if
your graphviz binary doesn't support GIF, reporting an error similar to
<code>Renderer type: &quot;gif&quot; not recognized. Use one of: [...png...]</code>.</p>
</dd>
</li>
<dt><strong><a name="item_graph_ranksep">graph_ranksep</a></strong>

<dd>
<p>FLOAT.  Rank Separation of elements in graph.</p>
</dd>
</li>
<dt><strong><a name="item_graph_ratio">graph_ratio</a></strong>

<dd>
<p>FLOAT or STRING. Graph's aspect ratio, may be a floating point number, or one of
the keywords fill, compress, or auto.</p>
</dd>
</li>
<dt><strong><a name="item_graph_raw">graph_raw</a></strong>

<dd>
<p>FILE.  Set to create the raw (.dot) graph file as well.</p>
</dd>
</li>
<dt><strong><a name="item_graph_splines">graph_splines</a></strong>

<dd>
<p>BOOLEAN.  Turn on GraphViz's spline engine? (Is very processor intensive).</p>
</dd>
</li>
<dt><strong><a name="item_graph_svg">graph_svg</a></strong>

<dd>
<p>FILE.  Set to create an SVG version of the graph.  Requires GraphViz 0.8 or greater.</p>
</dd>
</li>
<dt><strong><a name="item_graph_timeout">graph_timeout</a></strong>

<dd>
<p>MINUTES. Time to allow <code>neato</code> to try and solve the graph.  Default 60min.</p>
</dd>
</li>
<dt><strong><a name="item_graph_x_2c_graph_y">graph_x, graph_y</a></strong>

<dd>
<p>FLOAT. The X and Y dimensions of the graph in inches.   To convert to pixels, times by 
100 (96 actually).  So the default values of 30x30 will give you a graph that is about 3000x3000 pixels wide.</p>
</dd>
</li>
<dt><strong><a name="item_node_fillcolor">node_fillcolor</a></strong>

<dd>
<p>STRING. Default background color for device</p>
</dd>
</li>
<dt><strong><a name="item_node_fixedsize">node_fixedsize</a></strong>

<dd>
<p>BOOLEAN. True keeps the box size small and fixed (for huge graphs); false allows the
box to be sized to fit the text inside.  Default TRUE.</p>
</dd>
</li>
<dt><strong><a name="item_node_font">node_font</a></strong>

<dd>
<p>FILE. Name of the True Type Font used for label of node.
Exclude .ttf in name.</p>
</dd>
</li>
<dt><strong><a name="item_node_fontcolor">node_fontcolor</a></strong>

<dd>
<p>STRING. Color of text</p>
</dd>
</li>
<dt><strong><a name="item_node_fontsize">node_fontsize</a></strong>

<dd>
<p>FLOAT. Size of text in Pixels.  Note that for the graph_overlap=scale option, the font gets scaled down
and so an oversized font is used.</p>
</dd>
</li>
<dt><strong><a name="item_node_map">node_map</a></strong>

<dd>
<p>STRING. Colon separated list of values.  Multiple node_map entries can exist.
Entry is in format:</p>
</dd>
<dd>
<pre>
    Variable:Regular Expression:Attribute:Value:Key String:Key Title</pre>
</dd>
<dd>
<p>Variables that you can use include : label,ip</p>
</dd>
<dd>
<p>Attributes can be any node attribute usable in GraphViz, such as fillcolor and color</p>
</dd>
<dd>
<p>Examples:</p>
</dd>
<dd>
<pre>
    label:cat(?!-g):fillcolor:blue:cat:Blue Box - Catalyst Switch</pre>
</dd>
<dd>
<p>If the label (dns name) matches cat, but not cat-g, make it blue,
with an entry in the key like <code>[cat]  Blue Box - Catalyst Switch</code></p>
</dd>
<dd>
<pre>
    ip:^169\.233:color:yellow:node:Yellow Border - ResNet</pre>
</dd>
<dd>
<p>If the IP address of the device starts with 169.233, then make the border around the 
device yellow, with an entry in the key like <code>[node]  Yellow Border - ResNet</code>.</p>
</dd>
<dd>
<p>You may leave off Key String and Key Title to get no entry in the
key for this color combination.  This can be useful to get only one
key entry when using multiple node_map entries with the same
attribute/value.</p>
</dd>
</li>
<dt><strong><a name="item_node_problem">node_problem</a></strong>

<dd>
<p>STRING. Color to use for devices that are not accessible</p>
</dd>
</li>
<dt><strong><a name="item_node_shape">node_shape</a></strong>

<dd>
<p>STRING. Default shape for device, normally box.</p>
</dd>
</li>
<dt><strong><a name="item_node_style">node_style</a></strong>

<dd>
<p>STRING. Default style of device, normally filled.</p>
</dd>
</li>
<dt><strong><a name="item_root_device">root_device</a></strong>

<dd>
<p>STRING. IP address of a device to be used as the ``center'' of the graph.</p>
</dd>
</li>
</dl>
<p>
</p>
<hr />
<h1><a name="design">DESIGN</a></h1>
<p>
</p>
<h2><a name="design_goals">Design Goals</a></h2>
<ul>
<li><strong><a name="item_use_of_snmp_leaf_names_only_3b_no_oids">Use of SNMP Leaf Names only; No OIDs</a></strong>

<li><strong><a name="item_easily_extendible_to_new_devices_2e_no_device_2dsp">Easily extendible to new devices. No device-specific hacks in logic</a></strong>

<li><strong><a name="item_modular_back_2dend_database_front_2dend_setup">Modular back-end database front-end setup</a></strong>

<li><strong><a name="item_security_2e_front_2dend_abstraction_from_device_ma">Security.  Front-end abstraction from device manipulation means 
sensitive network devices are not exposed to a web interface .</a></strong>

<li><strong><a name="item_data_archiving_2e_data_structures_and_backup_routi">Data Archiving.  Data structures and backup routines to provide
online and offline storage of network structure and usage.</a></strong>

<li><strong><a name="item_highly_configurable_2e_extract_out_all_possible_op">Highly Configurable.  Extract out all possible options to <em>netdisco.conf</em>
and avoid site-specific code.</a></strong>

<li><strong><a name="item_administration_available_on_both_command_line_and_">Administration available on both command line and web interfaces.</a></strong>

</ul>
<p>
</p>
<h2><a name="backend_components">Back-End Components</a></h2>
<dl>
<dt><strong><a name="item_netdisco_2epm">netdisco.pm</a></strong>

<dd>
<p>Perl Module that holds all the SQL interaction routines as well as some
helper routines.  Used by both the back-end and front-end.</p>
</dd>
</li>
<dt><strong><a name="item_snmp_3a_3ainfo">SNMP::Info</a></strong>

<dd>
<p>Perl Modules created for this project that are used to provide the interaction
between the device and Netdisco over SNMP.  All device-specific changes are 
done in these modules.</p>
</dd>
</li>
<dt><strong><a name="item_network_walker">Network Walker</a></strong>

<dd>
<p>Using a device as a starting point (root), the walker then tries to visit every
device directly connected to the starting point.  Neighboring devices are found
with CDP.</p>
</dd>
</li>
<dt><strong><a name="item_arpnipper">ArpNipper</a></strong>

<dd>
<p>The ArpNipper is visits each discovered device with Layer 3 capabilities.
Each device's ARP Cache is read and the IP address to MAC address translation is stored
in the <strong>node_ip</strong> table.</p>
</dd>
<dd>
<p>The original ArpNipper was written by Jim Warner at UCSC.</p>
</dd>
</li>
<dt><strong><a name="item_macsucker">MacSucker</a></strong>

<dd>
<p>The MacSucker visits each device with Layer 2 capabilities.
Each device's Forwarding Table is read.  MAC addresses that are on ports without
a physical mapping (virtual ports) are skipped.  MAC Addresses on ports with a
neighbor recorded are skipped (uplink ports).  MAC Addresses that are actually 
switch ports are skipped.  The remaining MAC addresses are recorded
as nodes in the <strong>nodes</strong> table.</p>
</dd>
<dd>
<p>If the device supports the <code>v_name()</code> call, and has VLANs, then the MacSucker tries to 
connect to each VLAN and <code>macksuck()</code> each VLAN.  This is required for some devices like
the Cisco Catalyst 5000, 3500, 1900, 6500 series.</p>
</dd>
<dd>
<p>A few speedups are implemented for the devices that require each VLAN to visited:</p>
</dd>
<dl>
<dt><strong><a href="#item_macsuck_no_vlan">macsuck_no_vlan</a></strong>

<dd>
<p>This config file directive lists VLANs that exist in every device by default 
but do not ever have MAC addresses attached to them.</p>
</dd>
</li>
<dt><strong><a href="#item_macsuck_no">macsuck_no</a></strong>

<dd>
<p>Use this config file directive to exclude problem devices.</p>
</dd>
</li>
<dt><strong><a name="item_macsuck_only_happens_on_vlans_listed_under_ports">Macsuck only happens on VLANS listed under ports</a></strong>

<dd>
<p>(New 0.94) Many VLANs may be on the device or in the vtpdomain, but only a few of them 
may be in use on device_ports.  Macsuck will not try to visit the VLANs that are
not in use on device ports.  See <a href="#item_macsuck_all_vlans">macsuck_all_vlans</a> to override this.</p>
</dd>
</li>
</dl>
<p>The original MacSucker was written by Mark Boolootian at UCSC.</p>
<dt><strong><a name="item_helper_routines">Helper Routines</a></strong>

<dd>
<p>The 40+ routines for creating backups, logging, etc.</p>
</dd>
<dd>
<p>Browse the source code or check out netdisco-api for more info.</p>
</dd>
</li>
</dl>
<p>
</p>
<h2><a name="database">Database</a></h2>
<p>Netdisco uses PostgreSQL as its database store.  Indexing is used heavily to speed up 
queries and facilitate large data sets.   See the <code>sql/</code> directory and INSTALL
for more information.</p>
<p>
</p>
<h3><a name="sql_tables">SQL Tables</a></h3>
<dl>
<dt><strong><a name="item_admin">admin</a></strong>

<dd>
<p>Queue for admin control panel tasks to be sent back and forth from the front-end.</p>
</dd>
</li>
<dt><strong><a name="item_device">device</a></strong>

<dd>
<p>Holds device information.  Each device is identified by unique IP Address.</p>
</dd>
</li>
<dt><strong><a name="item_device_ip">device_ip</a></strong>

<dd>
<p>Holds alias IP Addresses for devices.  Each device can have multiple IP's stored 
in this table.  The master IP address is either taken from SNMP information or 
from the reverse DNS entry of the device name.  Also used to link a certain alias
to a port.</p>
</dd>
</li>
<dt><strong><a name="item_device_port">device_port</a></strong>

<dd>
<p>Holds the interface (port) information for each device.  One row for each interface
exists with information about the port status.</p>
</dd>
</li>
<dt><strong><a name="item_device_port_log">device_port_log</a></strong>

<dd>
<p>Contains log entries for port_control, tool used for administratively enabling and disabling 
ports.</p>
</dd>
</li>
<dt><strong><a name="item_device_port_ssid">device_port_ssid</a></strong>

<dd>
<p>Holds SSID information for wireless access points.</p>
</dd>
</li>
<dt><strong><a name="item_device_port_wireless">device_port_wireless</a></strong>

<dd>
<p>Holds channel and power information for wireless access points.</p>
</dd>
</li>
<dt><strong><a name="item_log">log</a></strong>

<dd>
<p>Holds log entries for human use.</p>
</dd>
</li>
<dt><strong><a name="item_node">node</a></strong>

<dd>
<p>Holds an entry for each MAC address connected to the network that isn't a device. Tells
on which switch port the node was seen, and when it was seen there.  Also holds the archived
data on node location.  Archived data has the column ''active'' set to false. Data comes from 
<a href="#item_macsucker">MacSucker</a></p>
</dd>
</li>
<dt><strong><a name="item_node_ip">node_ip</a></strong>

<dd>
<p>Maps a MAC Address to an IP address.  Has no notion of where this node was seen.   Keeps
time stamps of when this is from.  Data comes from <a href="#item_arpnipper">ArpNipper</a>.  Archived data is similar
to the <a href="#item_node">node</a> table, where ``active'' is set to false for archived data.</p>
</dd>
</li>
<dt><strong><a name="item_node_monitor">node_monitor</a></strong>

<dd>
<p>Lists MAC addresses that are to be monitored for presence on the network; if one
appears or moves at the end of a macwalk, send email to <a href="#item_node_monitor_email">node_monitor_email</a>
and the CC field in the node_monitor_table, if set.</p>
</dd>
</li>
<dt><strong><a name="item_node_nbt">node_nbt</a></strong>

<dd>
<p>Maps a MAC address to an IP address and its NetBIOS information, including NBT name,
domain, and user.  Archived data is similar
to the <a href="#item_node">node</a> table, where ``active'' is set to false for archived data.</p>
</dd>
</li>
<dt><strong><a name="item_node_wireless">node_wireless</a></strong>

<dd>
<p>Holds information about the a wireless station's radio -- maximum possible rate,
current transmit rate, signal strength and quality, and rx/tx packets and bytes.
This table has no archived data; it only contains the most recent sample for a
given MAC address.</p>
</dd>
</li>
<dt><strong><a name="item_process">process</a></strong>

<dd>
<p>This table is used to coordinate the work of multiple child processes when performing
parallel work.</p>
</dd>
</li>
<dt><strong><a name="item_sessions">sessions</a></strong>

<dd>
<p>Web sessions created by MasonX::Request::WithApacheSessions.  Stores information about
a current session in the global $m-&gt;session hash under mason.</p>
</dd>
</li>
<dt><strong><a name="item_oui">oui</a></strong>

<dd>
<p>Populated with data from oui.txt  Oui.txt contains the Organizationally Unique Identifiers (OUI) that 
map a MAC address to a vendor.  The database is controlled by the IEEE.  See INSTALL for more
information.</p>
</dd>
</li>
<dt><strong><a name="item_users">users</a></strong>

<dd>
<p>User information for web front end.</p>
</dd>
</li>
</dl>
<p>
</p>
<hr />
<h1><a name="thanks">THANKS</a></h1>
<p>I would like to thank the following people for their
contributions to Netdisco :</p>
<p>Mark Boolootian and Jim Warner (Through who's ideas Netdisco was born and
shaped)  (UCSC) , Mike Hunter (UCB), Brian Wilson (NCSU), Bradley Baetz
(bbaetz), David Temkin (sig.com), Edson Manners (FSU), Dmitry Sergienko (Trifle
Co, .ua), Remo Rickli (PSI, Switzerland), Jean-Philippe Luiggi (sagem.com),
A.L.M Buxey (Loughborough University, UK), Kevin Cheek (UMICH), John Bigrow
(bnl.gov), George Pavel (llnl.gov), Charles Goldsmith (wokka.org), Douglas M.
McKeown (saintmarys.edu), Revital Shvarzman (York U, Ontario), Walter Gould
(Auburn U), Lindsay Druet and Colin Palmer (U of Waikato, Hamilton NZ), Dusty
Hall (Auburn U), Jon Monroe (center pointe), Eric Miller (jeneric), Bill
Fenner, Oliver Gorwits (Oxford U), Alexander Barthel
(http://archiv.tu-chemnitz.de/pub/2005/0045/), Bill Anderson, Carlos Vicente (U
Oregon),  Alexander Hartmaier (t-systems.at), Justin Hunter (Arizona State U),
Jethro Binks (U of Strathclyde, Glasgow), Jordi Guijarro (UAB.es), Sam
Stickland (spacething.org),  Stefan Radman (CTBTO.org), Clint Wise, Max
Kosmach, Bernhard Augenstein.</p>
<p>And probably lots of other people I forgot to put in here.   Not to mention the 
authors and communities of all the other software that Netdisco is built upon.</p>

</%text>