<< Click to Display Table of Contents >> Navigation:  What to Do in Case of Emergency > Equipment failures

Below is the list of possible failures of equipment used to run Microolap EtherSensor, corrective and recovery actions for the sensor.

Unable to start Microolap EtherSensor services due to incorrect server reboot or stop.

This emergency is indicated by the (Error 1053) system message telling that the service cannot be started.

If any of the Microolap EtherSensor services cannot be started, do the following:

▪Try to start the services again, taking into account that in order for the Microolap EtherSensor services to be started, the EtherSensor Watcher service must be started.

▪If you failed to restart the services, contact support.

There is no free disk space for message interception spools.

The following are the indications of this emergency:

▪OS alerts about the lack of free space on the disk.

▪Records in the OS system log about the lack of free space on the disk.

The system administrator must find out why the system has run out of space. You can use the Disk Management snap-in. If the reason is the spool overflow ([INSTALLDIR]\data directory), delete spool data or move them to a free disk partition. Other possible reasons are:

▪Server that supposed to receive messages sent from sensor is unavailable. If this is the case, troubleshoot communication errors.

▪Too much traffic processed by the sensor: if this is the case, set up additional sensors and distribute the load among them.

Microolap EtherSensor server emergency power shutdown..

After the power is restored and the server on which the Microolap EtherSensor runs is back online, the system administrator must make sure that all the services have been started successfully.

If there are any deviations from the normal startup procedure, inspect service logs. If these logs contain error messages, contact support.

Microolap EtherSensor server network disconnect.

The following are the indications of this emergency:

▪The network card of the server on which the sensor runs alerts about the mechanical loss of integrity of the communications channel.

▪Packets sent over the ICMP protocol to servers for further message processing are not returned or returned partially.

The system administrator must verify and recover the communications channel of the server on which the. Microolap EtherSensor runs. After that, check network settings in the operating system. After the network connection problems are resolved, make sure that all the Microolap EtherSensor services are operational