Use the Abnormal Events - Unit lost incident type to automatically alert operators when there are connectivity issues taking any unit such as access control or video units offline.
Abnormal Events - Unit lost incident type: functionality
- At least one valid email address for notification emails.
- For Genetec Mission
Control™ versions 188.8.131.52, a
macro to initiate a reboot of the unit.
As of Genetec Mission Control™ 184.108.40.206, Reboot unit is available as an automation workflow activity for incident type configuration.
The system automatically closes the incident after the unit comes back online.
For more information on the how the operator can monitor and manage the incident, see the Genetec Mission Control™ User Guide.
Abnormal Events - Unit lost incident type configuration
The incident type is preconfigured with the following:
Abnormal Events - Unit lost incident type: triggers
The incident is configured to be automatically triggered when any unit goes offline.
Based on your setup, you can add, remove or modify triggers as required. For more details, see Modifying incident triggers.
Abnormal Events - Unit lost incident type: automation workflow
After the incident is triggered, the system waits to see if the error resolves itself within 2 minutes. If not, the system runs a dedicated macro that restarts the unit. If the unit comes back online, the system automatically closes the incident without any manual intervention.
- Latest activity log
- Last event
- Incident trigger time
- Incident owner
- Incident sources
- Incident location
For more details, see Modifying incident automation workflow activities.
Abnormal Events - Unit lost incident type: user procedure
The incident is configured with a dynamic procedure, that accepts operator response and directs system action accordingly.
- Verification of event cause: Maintenance, known issue or unknown issue.
- Directives for the operator:
- If the event cause is a maintenance, known hardware or network issue, put the incident on hold and revisit the issue for resolution.
- If the event cause unknown, reboot the unit.
- If the unit does not come back online, create a service request.
For more details, see Modifying incident user procedures.