User Tools

Site Tools


devicemanagement

Device History

The device history tool lets you view device history, register error events and delete outdated modules.

The Device History tool has three tabs:

  1. Device History
  2. Register Error Event
  3. Delete Module

Device History

:!: 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
  • Select location, then room and then choose a box or a subsequent module

In any case you need to highlight your choice in the form and submit “View history”. All events for your selection that has occurred the last week will then be shown. Start and end time of each event will be shown, in addition to a description of the event itself.

You can choose another time period than the last week. You may also filter on certain event types (listed in a drop down). Press filter to make your time period or filter changes take effect.

Typically, the kind of events you can expect to see are:

  • Status events
  • Service events
  • Module events
  • Threshold events
  • Maintenance periods
  • Cold/warm starts
  • Software upgrades
  • Manually recorded error events (see below)

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 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?).

Delete Module

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.

devicemanagement.txt · Last modified: 2011/04/07 20:32 by faltin