Differences

This shows you the differences between two versions of the page.

--- subnetsandvlans [2007/09/30 15:43] – faltin
+++ subnetsandvlans [2011/04/08 13:58] (current) – [Syntax] faltin
@@ Line 19: / Line 19: @@
 Please note that the vlan information is **not** compulsory in NAV. There are a number of advantages of having this information, however, the most vital components of NAV will operate fine without.
-There are two subsystems in NAV that can fill in vlan information: the background process [[backendprocesses#getdevicedata|getDeviceData]] and the [[seedessentials|tool editDatabase]]. getDeviceData will attempt as far as possible to automatically fill in this information. This is easily achieved if you are using the NAV guidelines for configuring router interface descriptions (again - not a requirement - anyway - more below).
+There are two subsystems in NAV that can fill in vlan information: the background process [[backendprocesses#ipdevpoll|ipdevpoll]] and the [[seedessentials|tool seedDatabase]]. ipdevpoll will attempt as far as possible to automatically fill in this information. This is easily achieved if you are using the NAV guidelines for configuring router interface descriptions (again - not a requirement - anyway - more below).
-:!: [[seedessentials#vlan|the Edit Vlan component of editDatabase]] lets you complete missing information after getDeviceData has done its job.
+:!: [[seedessentials#vlan|the Edit Vlan component of SeedDatabase]] lets you complete missing information after ipdevpoll has done its job. To be precise you can manually edit the organization, usage and vlan values.
 ===== Network types =====
@@ Line 51: / Line 51: @@
 ===== Guide lines for configuring router interface descriptions =====
-NAV has defined guide lines for configuring router interface descriptions (use the description-command in interface config mode on a cisco router). You may follow these guide lines if you like, getDeviceData will then take advantage of this and have an easy task filling in vlan attributes.
+NAV has defined guide lines for configuring router interface descriptions (use the description-command in interface config mode on a cisco router). You may follow these guide lines if you like, ipdevpoll will then take advantage of this and have an easy task filling in vlan attributes.
-The description setting also serves as a sensible documentation in the configs of your running routers.
+The description setting also serves as a sensible documentation in the configurations of your running routers.
 ==== Syntax ====
@@ Line 81: / Line 81: @@
 ^ $comment   | Any further (unstructured) description you may want to add (btw: also a way of distinguishing two math-staff-subnets from one another).                              |
 ^ $vlan      | The vlan number for this broadcast domain. Please note: This information may be derived from the interface name itself, if this is a virtual interface or it may be derived from the connected switch, using CDP. It may also be added (or changed) in editDatabase.                                    |
-^ $to_router | The router that this routerinterface is connected to. Please note: This information is easily derived automatically by getDeviceData and is thus superficial.             |
+^ $to_router | The router that this router interface is connected to. Please note: This information is easily derived automatically by ipdevpoll and is thus superficial.             |
 ^ $to_org    | The organizational unit that this external link is peering with.                      |