NMIS9 Timestamps and their meanings

Introduction

NMIS is a complete management system which collects fault, performance and basic inventory/configuration data from routers, switches, servers, firewalls, facilities (UPS, AC/CRACK, Sensors), and anything which has an SNMP agent.  NMIS is highly extensible, using device models to define what is collected from devices, and how events are handled.

In summary, NMIS supports any device which supports SNMP with "Default" models, this is called standard support, this includes Default models for SNMPv1 only devices and newer SNMP agents which support the High Capacity agent.  Standard support includes performance and fault collection and alerting of interface statistics and IP packet activity.  Device support NMIS has been extended for various vendors and products, this includes performance and fault collection, alerting and thresholding on additional information like CPU, memory, disk, services, storage, sessions, packets, temperature, and many other things.

To accomplish this, several timestamps are collected and saved to document and manage the current device status, and the success and/or failure of the collection process.  Timestamps can be updated through polling, or by incoming events.

Timestamps used by NMIS

 

Below are the important timestamps used by NMIS and their meanings.

Contact FirstWave for information on support for any timestamps of interest which you do not understand.


TimestampPurposeWhen set
catchall.last_pollTo document the last successful poll without regard to the polling method

Following a successful query without regard to the polling method

NB in versions of NMIS prior to NMIS 9.4.4 this was only for collect polls.

catchall.last_poll_attemptTo document the last attempted poll without regard to the polling methodFollowing an attempted query whether it was successful or not and without regard to the polling method
catchall.last_updateTo document the last successful update of a NodeFollowing an update, either via the scheduled (usually daily) update, or through a detected change made in the configuration, or through a user command
catchall.last_update_attemptTo document the last attempted update of a NodeFollowing an attempted update whether it ws successful or not
catchall.last_poll_snmpTo document the last successful SNMP queryFollowing a successful SNMP query
catchall.last_poll_snmp_attemptTo document the last attempted SNMP queryFollowing an attempted SNMP query whether it was successful or not
catchall.last_poll_wmi_attemptTo document the last successful WMI queryFollowing a successful WMI query
catchall.last_poll_wmi_attemptTo document the last attempted WMI queryFollowing an attempted WMI query whether it was successful or not
catchall.last_node_config_updateTo document the last configuration update of a NodeUpdated any time the Node has been saved through an update, or a collection
catchall.ping_successfulTo document the last successful pingFollowing a successful ping
catchall.status_updatedTo document an update in the status of the deviceFollowing an update in the status of the device, whether through an event, a poll, or a ping