This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devicemanagement [2007/10/06 06:23] faltin |
devicemanagement [2011/04/07 18:28] faltin |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Device Management ====== | + | ====== Device History ====== |
- | {{tools:devman.png|}} The device management tool lets you view device history, register error events, delete outdated modules and more. It also has a ordering system, but... | + | {{tools:devman.png|}} The device history tool lets you view device history, register error events and delete outdated modules. |
- | ===== Ignore the ordering system - it is leaving NAV ===== | ||
- | The device management tool consists of six tabs, where we recommend that you ignore three of them. | ||
- | |||
- | Ignore these tabs: | ||
- | * Order devices | ||
- | * Register serial numbers | ||
- | * Register RMA | ||
- | |||
- | In a later version of NAV (3.5 we assume) these tabs will be removed from NAV. The tabs are in essence the ordering system that was meant to be a supplement to those of you who wanted to keep track of your network devices prior to operation, i.e. ordering and arrival on cite, and in potential RMA periods. | ||
- | |||
- | We find this way outside the focus area of NAV and recommend that you use other system to keep track of orders. | ||
- | |||
- | The following Tabs will remain in Device Management and will be explained in the following: | ||
- | |||
- | * Device history | ||
- | * Register error event | ||
- | * Module delete | ||
Line 62: | Line 45: | ||
- | ===== Module Delete ===== | + | ===== Delete Module ===== |
- | The purpose of "Module Delete" is to clear out modules that NAV has recorded as down and that you now will never come up again, simply because they are physically removed from the chassis or stack in question. We have found it necessary to design NAV in this manner, as there is no way for the module monitor to know if a module is temporary down or permanently removed. | + | The purpose of "Module Delete" is to clear out modules that NAV has recorded as down and that you know will never come up again, simply because they are physically removed from the chassis or stack in question. We have found it necessary to design NAV in this manner, as there is no way for the module monitor to know if a module is temporary down or permanently removed. |
When you remove a module using "Module Delete" you are given the choice of putting the module in "inventory state" or "inactive". This functionality relates to the part we will remove from NAV (see above). Choose whatever you like, does not matter, | When you remove a module using "Module Delete" you are given the choice of putting the module in "inventory state" or "inactive". This functionality relates to the part we will remove from NAV (see above). Choose whatever you like, does not matter, |