| 1 | <?xml version="1.0" encoding="utf-8"?> |
|---|
| 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" |
|---|
| 3 | "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
|---|
| 4 | <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> |
|---|
| 5 | <head> |
|---|
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
|---|
| 7 | <meta name="generator" content="pandoc" /> |
|---|
| 8 | <link rel="stylesheet" type="text/css" media="screen, projection, print" |
|---|
| 9 | href="http://www.w3.org/Talks/Tools/Slidy2/styles/slidy.css" /> |
|---|
| 10 | <script src="http://www.w3.org/Talks/Tools/Slidy2/scripts/slidy.js.gz" |
|---|
| 11 | charset="utf-8" type="text/javascript"></script> |
|---|
| 12 | </head> |
|---|
| 13 | <body> |
|---|
| 14 | <div class="slide titlepage"> |
|---|
| 15 | <h1 class="title">Understanding Netdot</h1> |
|---|
| 16 | <p class="author"> |
|---|
| 17 | |
|---|
| 18 | </p> |
|---|
| 19 | </div> |
|---|
| 20 | <div class="slide"> |
|---|
| 21 | <h1 id="installation">Installation</h1> |
|---|
| 22 | <ul> |
|---|
| 23 | <li>Option 1: install the prebuilt VM image</li> |
|---|
| 24 | <li>Option 2: install under Ubuntu 10.04 (LTS): <a href="https://osl.uoregon.edu/redmine/projects/netdot/wiki/Installing_Under_Ubuntu_10041_Server"><code class="url">https://osl.uoregon.edu/redmine/projects/netdot/wiki/Installing_Under_Ubuntu_10041_Server</code></a> |
|---|
| 25 | <ul> |
|---|
| 26 | <li>Quite a few steps and dependencies. Read carefully.</li> |
|---|
| 27 | <li>Get help from the netdot-users mailing list!</li> |
|---|
| 28 | </ul></li> |
|---|
| 29 | <li>I recommend you set your timezone, and restart mysqld if already installed |
|---|
| 30 | <ul> |
|---|
| 31 | <li><code>sudo dpkg-reconfigure tzdata</code></li> |
|---|
| 32 | </ul></li> |
|---|
| 33 | </ul> |
|---|
| 34 | </div> |
|---|
| 35 | <div class="slide"> |
|---|
| 36 | <h1 id="netdot-device">Netdot "Device"</h1> |
|---|
| 37 | <ul> |
|---|
| 38 | <li>Represents a piece of <em>infrastructure</em> which you manage via SNMP |
|---|
| 39 | <ul> |
|---|
| 40 | <li>e.g. switch, router, AP, server</li> |
|---|
| 41 | </ul></li> |
|---|
| 42 | <li>Can add individual devices manually via the GUI (SNMP or not)</li> |
|---|
| 43 | <li>Add SNMP devices via command line |
|---|
| 44 | <ul> |
|---|
| 45 | <li><code>updatedevices.pl -H 10.10.0.254 -I -c NetManage</code></li> |
|---|
| 46 | </ul></li> |
|---|
| 47 | <li>Can sweep a subnet for SNMP devices |
|---|
| 48 | <ul> |
|---|
| 49 | <li><code>updatedevices.pl -B 10.10.0.0/24 -I -c NetManage</code></li> |
|---|
| 50 | <li>Warning: everyone will see your community string!</li> |
|---|
| 51 | <li>And you might want to use the loopback address anyway</li> |
|---|
| 52 | </ul></li> |
|---|
| 53 | <li>Or add a list of devices from a text file (see manual)</li> |
|---|
| 54 | </ul> |
|---|
| 55 | </div> |
|---|
| 56 | <div class="slide"> |
|---|
| 57 | <h1 id="naming-of-devices">Naming of devices</h1> |
|---|
| 58 | <ul> |
|---|
| 59 | <li>Each device must have a primary IP and name</li> |
|---|
| 60 | <li>Several sources, in configurable order, e.g. |
|---|
| 61 | <ul> |
|---|
| 62 | <li>resolve SNMP sysName</li> |
|---|
| 63 | <li>reverse DNS of the snmp target</li> |
|---|
| 64 | </ul></li> |
|---|
| 65 | <li>Unfortunately doesn't work well unless your DNS is already working |
|---|
| 66 | <ul> |
|---|
| 67 | <li>Not good if you are planning to use Netdot to fix your DNS!</li> |
|---|
| 68 | </ul></li> |
|---|
| 69 | <li>The device name is a key in Netdot's DNS tables, but may not be associated with an A record (RR) |
|---|
| 70 | <ul> |
|---|
| 71 | <li>This is confusing</li> |
|---|
| 72 | </ul></li> |
|---|
| 73 | <li>Device serial numbers are checked, but you only get a warning if they overlap |
|---|
| 74 | <ul> |
|---|
| 75 | <li>Sometimes we see the same serial number more than once, e.g. with emulated hardware (dynamips) or faulty equipment</li> |
|---|
| 76 | </ul></li> |
|---|
| 77 | </ul> |
|---|
| 78 | </div> |
|---|
| 79 | <div class="slide"> |
|---|
| 80 | <h1 id="end-user-pcs-are-not-devices">End user PCs are not "Devices"</h1> |
|---|
| 81 | <ul> |
|---|
| 82 | <li>They are auto-detected from ARP tables and forwarding tables</li> |
|---|
| 83 | <li>You can search for them by IP or MAC address</li> |
|---|
| 84 | <li>You can see which switch port they were last plugged into</li> |
|---|
| 85 | <li>You can see when the IP was last active</li> |
|---|
| 86 | </ul> |
|---|
| 87 | </div> |
|---|
| 88 | <div class="slide"> |
|---|
| 89 | <h1 id="polling-of-devices">Polling of devices</h1> |
|---|
| 90 | <ul> |
|---|
| 91 | <li>A cron job polls your devices periodically (say) every hour |
|---|
| 92 | <ul> |
|---|
| 93 | <li>Don't forget to <code>cp netdot.cron /etc/cron.d/netdot</code></li> |
|---|
| 94 | </ul></li> |
|---|
| 95 | <li><code>updatedevices.pl -DIFAT</code> |
|---|
| 96 | <ul> |
|---|
| 97 | <li>Poll only devices in databases</li> |
|---|
| 98 | <li>Refresh basic information (sysName, sysLocation etc)</li> |
|---|
| 99 | <li>Read forwarding tables from switches</li> |
|---|
| 100 | <li>Read ARP tables from routers</li> |
|---|
| 101 | <li>Read CDP/LLDP topology</li> |
|---|
| 102 | </ul></li> |
|---|
| 103 | </ul> |
|---|
| 104 | </div> |
|---|
| 105 | <div class="slide"> |
|---|
| 106 | <h1 id="address-a.k.a.-ipblock">"Address" (a.k.a. "ipblock")</h1> |
|---|
| 107 | <ul> |
|---|
| 108 | <li>Represents a single IP, or a prefix</li> |
|---|
| 109 | <li>Prefix can be "container" or "subnet" |
|---|
| 110 | <ul> |
|---|
| 111 | <li>A "subnet" is something actually seen on a router interface</li> |
|---|
| 112 | <li>A "container" can contain subnets or other containers (recursively)</li> |
|---|
| 113 | <li>A "subnet" <em>cannot</em> contain subnets or containers</li> |
|---|
| 114 | <li>A "container" will be turned into a "subnet" if it's seen on a router interface</li> |
|---|
| 115 | </ul></li> |
|---|
| 116 | <li>Single IPs have different states |
|---|
| 117 | <ul> |
|---|
| 118 | <li>Static - belongs to a device interface, or manually set to static</li> |
|---|
| 119 | <li>Discovered - seen in ARP table</li> |
|---|
| 120 | <li>Dynamic - defined as part of a DHCP pool</li> |
|---|
| 121 | <li>Reserved - should not be assigned</li> |
|---|
| 122 | </ul></li> |
|---|
| 123 | </ul> |
|---|
| 124 | </div> |
|---|
| 125 | <div class="slide"> |
|---|
| 126 | <h1 id="vlans">VLANS</h1> |
|---|
| 127 | <ul> |
|---|
| 128 | <li>Discovered from switches/routers</li> |
|---|
| 129 | <li>Right now, a dot1q tag must be unique across your network</li> |
|---|
| 130 | </ul> |
|---|
| 131 | </div> |
|---|
| 132 | <div class="slide"> |
|---|
| 133 | <h1 id="dns">DNS</h1> |
|---|
| 134 | <ul> |
|---|
| 135 | <li>Must create a DNS zone first, then the records</li> |
|---|
| 136 | <li>Create reverse DNS zones, or you won't get PTR records created</li> |
|---|
| 137 | <li>Netdot can create unique DNS names for each device interface, based on e.g. interface type and number |
|---|
| 138 | <ul> |
|---|
| 139 | <li>This is configurable, and you can write a module for your own naming convention if you wish</li> |
|---|
| 140 | </ul></li> |
|---|
| 141 | </ul> |
|---|
| 142 | </div> |
|---|
| 143 | <div class="slide"> |
|---|
| 144 | <h1 id="dhcp">DHCP</h1> |
|---|
| 145 | <ul> |
|---|
| 146 | <li>Can create config files for ISC DHCP server, e.g. to give static IPs to particular hosts</li> |
|---|
| 147 | <li>Create a DHCP "scope"</li> |
|---|
| 148 | <li>Then you mark a row individual IPs as "dynamic", using the bulk update facility |
|---|
| 149 | <ul> |
|---|
| 150 | <li>So that the DHCP range doesn't have to fall on subnet boundary</li> |
|---|
| 151 | <li>Probably won't scale to v6 :-)</li> |
|---|
| 152 | </ul></li> |
|---|
| 153 | </ul> |
|---|
| 154 | </div> |
|---|
| 155 | <div class="slide"> |
|---|
| 156 | <h1 id="not-convered-in-this-presentation">Not convered in this presentation</h1> |
|---|
| 157 | <ul> |
|---|
| 158 | <li>Cable plant</li> |
|---|
| 159 | <li>Contacts and People</li> |
|---|
| 160 | <li>Reports</li> |
|---|
| 161 | <li>Exporting</li> |
|---|
| 162 | </ul> |
|---|
| 163 | </div> |
|---|
| 164 | <div class="slide"> |
|---|
| 165 | <h1 id="documentation">Documentation</h1> |
|---|
| 166 | <ul> |
|---|
| 167 | <li>Finding stuff can be difficult |
|---|
| 168 | <ul> |
|---|
| 169 | <li>"I know that Netdot can show my network topology, but where was it again?"</li> |
|---|
| 170 | </ul></li> |
|---|
| 171 | <li>It's open source, you can contribute to the documentation |
|---|
| 172 | <ul> |
|---|
| 173 | <li>The manual</li> |
|---|
| 174 | <li>wiki</li> |
|---|
| 175 | </ul></li> |
|---|
| 176 | </ul> |
|---|
| 177 | </div> |
|---|
| 178 | <div class="slide"> |
|---|
| 179 | <h1 id="platform">Platform</h1> |
|---|
| 180 | <ul> |
|---|
| 181 | <li>apache + mod_perl</li> |
|---|
| 182 | <li>mysql</li> |
|---|
| 183 | <li>rrdtool</li> |
|---|
| 184 | <li>graphviz</li> |
|---|
| 185 | <li>...lots of perl dependencies</li> |
|---|
| 186 | </ul> |
|---|
| 187 | </div> |
|---|
| 188 | <div class="slide"> |
|---|
| 189 | <h1 id="database-structure">Database structure</h1> |
|---|
| 190 | <ul> |
|---|
| 191 | <li>DB schema diagram: linked from <a href="https://osl.uoregon.edu/redmine/projects/netdot/wiki/Documentation"><code class="url">https://osl.uoregon.edu/redmine/projects/netdot/wiki/Documentation</code></a></li> |
|---|
| 192 | <li>Traditional SQL design</li> |
|---|
| 193 | <li>Most important tables: device, ipblock</li> |
|---|
| 194 | </ul> |
|---|
| 195 | </div> |
|---|
| 196 | </body> |
|---|
| 197 | </html> |
|---|