seedessentials
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
seedessentials [2011/04/08 12:16] faltin [Patch] |
seedessentials [2013/08/16 13:36] bredal [Subcategory] |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| If you stick with these minimum requirements it will mean NAV has no information of where the equipment is located, nor what | If you stick with these minimum requirements it will mean NAV has no information of where the equipment is located, nor what | ||
| - | organizations are involved. Further, since you have not yet adopted the recommended [[subnetsandvlans#guide_lines_for_configuring_router_interface_descriptions|NAV guidelines for configuring router interface description]], you will have no information on the ownership and usage of the various subnets/vlans. It is of course possible to improve these things at a later stage when you are ready to get better organized. | + | organizations are involved. Further, since you have not yet adopted the recommended [[subnetsandvlans#guide_lines_for_configuring_router_interface_descriptions|NAV guidelines for configuring router interface description]], you will have no information on the ownership and usage of the various subnets/vlans. It is of course possible to improve these things at a later stage when you are ready to get better organized (see the [[#the_move_selected_option|'Move selected' option]]). |
| You may of course use bulk import with the minimum requirements to be even more efficient. You only need to bulk the IP devices. | You may of course use bulk import with the minimum requirements to be even more efficient. You only need to bulk the IP devices. | ||
| Line 172: | Line 172: | ||
| * NAV will also derive the serial number from the equipment. If this fails, or if you for some reason want to register something else here, you can do this manually. Registering serial number is not a requirement, but recommended. The serial number is the key parameter to recognize the physical device. Device History bases its track record of physical devices on serial number. | * NAV will also derive the serial number from the equipment. If this fails, or if you for some reason want to register something else here, you can do this manually. Registering serial number is not a requirement, but recommended. The serial number is the key parameter to recognize the physical device. Device History bases its track record of physical devices on serial number. | ||
| * You may register a text string, function, that describes the IP device further. You may find this most relevant for SRV and OTHER. | * You may register a text string, function, that describes the IP device further. You may find this most relevant for SRV and OTHER. | ||
| - | * The subcategory field can be used to classify a device within the category. An example is to classify the servers (category SRV) into the subcategories MAIL and DNS. An IP device be a member of one or several subcategories. The subcategory will only appear as an option if there are registered subcategories for the category. | + | * The subcategory field can be used to classify a device within the category. An example is to classify the servers (category SRV) into the subcategories MAIL and DNS. An IP device be a member of one or several subcategories. The subcategory will only appear as an option if there are registered subcategories for the category. **NB: Subcategories are to be replaced with 'netbox groups'.** A network group can be compared to a tag, and is independent of categories. A netbox group can be used to filter equipment in reports, creating alert profiles and more. If you have already created subcategories, they will automatically be transformed to groups. |
| After an IP device is successfully added to NAV, the collection system will collect data from the device. | After an IP device is successfully added to NAV, the collection system will collect data from the device. | ||
| Line 260: | Line 260: | ||
| ==== Subcategory ==== | ==== Subcategory ==== | ||
| - | You may define subcategories within the predefines categories in NAV, see [[CategoriesAndTypes]] for more. IP devices may in turn belong to one or more subcategories. | + | You may define subcategories within the predefines categories in NAV, see [[CategoriesAndTypes]] for more. IP devices may in turn belong to one or more subcategories. |
| + | <note important>Subcategories are to be replaced with netbox groups. See note in [[CategoriesAndTypes]] for more information.</note> | ||
| ==== Prefix ==== | ==== Prefix ==== | ||
| Line 298: | Line 298: | ||
| You will notice that it is not possible to edit the room, location or organization values directly when in edit mode. | You will notice that it is not possible to edit the room, location or organization values directly when in edit mode. | ||
| - | You may however obtain the same effect using the 'Move selected' option available from the 'List' tab. | + | You may however obtain the same effect using the 'Move selected' option available from the 'List' tab! |
| - | For the IP device list you may | + | From the IP device list you may: |
| - select one or more IP devices (as many as you like) | - select one or more IP devices (as many as you like) | ||
| - click move selected | - click move selected | ||
| Line 310: | Line 310: | ||
| The same operation can be done for: | The same operation can be done for: | ||
| * moving one/more room(s) to another location | * moving one/more room(s) to another location | ||
| - | * giving an oganization a new parent organization | + | * giving an organization a new parent organization |
seedessentials.txt · Last modified: 2014/03/27 10:31 by morten
Page Tools
