Differences

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

--- devicemanagement [2011/04/07 18:29] – [Device History] faltin
+++ devicemanagement [2011/04/07 18:32] (current) – faltin
@@ Line 16: / Line 16: @@
 ===== Device History =====
-:!: Device History for an IP Device is reachable as a link from IP Device Center!
+:!: Device History for an IP Device is reachable as a link from IP Device Info
 Device History gives an overview of all recorded event for an IP device or module. You select either by entering:
    * Entering the serial number in the Quick search box
-   * Enter the ip address or host name (or part of the host name) in the Quick search box
+   * Enter the IP address or host name (or part of the host name) in the Quick search box
    * Select location, then room and then choose a box or a subsequent module
@@ Line 39: / Line 39: @@
    * Manually recorded error events (see below)
-Note: Seeing the whole history for a room or location does not work.
@@ Line 46: / Line 45: @@
 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
@@ Line 52: / Line 51: @@
 ===== Delete Module =====
-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.
+The purpose of "Delete Module" 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,
-the point is to remove the module from its IP device (in NAV 3.5 we will simplify "Module Delete").