User Tools

Site Tools


devicemanagement

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
devicemanagement [2007/10/04 11:24]
faltin
devicemanagement [2011/04/07 18:29]
faltin [Device History]
Line 1: Line 1:
-====== Device ​Management ​======+====== Device ​History ​======
  
-{{tools:​devman.png|}} The device ​management ​tool lets you view device history, register error eventsdelete outdated modules ​and more. I 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.
  
 +The Device History tool has three tabs:
  
-===== Ignore the ordering system ​it is leaving NAV =====+  ​Device History 
 +  - Register Error Event 
 +  - Delete Module
  
-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 taken out of 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 47: Line 37:
    * Cold/warm starts    * Cold/warm starts
    * Software upgrades    * Software upgrades
-   * Manually recorded error events (ee below)+   * Manually recorded error events (see below)
  
 Note: Seeing the whole history for a room or location does not work. Note: Seeing the whole history for a room or location does not work.
 +
  
 ===== Register Error Event ===== ===== Register Error Event =====
  
-The idea is that if you have repetitive malfunctions with a box you can record this and keep this as a record that follow ​the device and its history. You select a device using the same procedure as in "​Device History"​. When you record error event in the comment ​boks you should include time information.+The idea is that if you have repetitive malfunctions with a box you can record this and keep this as a record that follows ​the device and its history. You select a device using the same procedure as in "​Device History"​. When you record error event in the comment ​box you should include time information ​(should there be an extra field for this?). 
 + 
 +Note: Can we actually see these events in device history??? Bugs??? FIXME
  
-Note: Can we actually see these events in device history??? Bugs??? 
  
  
-===== 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 now way for det module monitor to know if a module is temprary ​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,
-the point is to remove the module from its IP device (in NAV 3.we will simplify "​Module Delete"​).+the point is to remove the module from its IP device (in NAV 3.we will simplify "​Module Delete"​).
  
  
devicemanagement.txt · Last modified: 2011/04/07 18:32 by faltin