Skip to content

Alarm Types

G-Core Alarm Types

GCore Connectivity

Alarm Type Code: 1001

Description:

This Alarm indicates that the G-Health Client installed on the NVR cannot connect to the G-Core Service. This is a critical alarm as it likely means the G-Core Service is not running.

Recommended Action:

Log on to the NVR and check the GCoreService is running. Contact your support representative if the issue persists.

GCore Invalid Credentials

Alarm Type Code: 1002

Description: This alarm indicates that the G-Health client service installed on the NVR cannot connect to the G-Core Service due to invalid credentials.

Recommended Action: Log onto the NVR and connect the client to the G-Core service.|

GCore Camera Tamper / CPA

Alarm Type Code: 1003

Description: This alarm indicates that a camera may have been tampered with or its view obstructed or obstructed. The source for this could be the Scene Validation service or in some cases it could come from the camera itself.

Recommended Action: Check the camera to see if the image is obstructed or altered.

GCore Camera Sync

Alarm Type Code: 1004

Description: This Alarm indicates that the video signal/stream from the camera is not working. It may indicate that the camera is offline or unreachable.

Recommended Action: Check the camera to see if it is working at all. If it is not displaying in G-View or G-SIM try and log onto the camera's web interface.

GCore Intermittent Camera Sync

Alarm Type Code: 1005

Description: This alarm indicates some persistent problems with a camera such that its signal or stream continues to drop in and out. This may indicate a network issue or in the case of analogue cameras on encoders it may indicate an issue with the analogue signal.

Recommended Action: Check the camera and network.

GCore Archive

Alarm Type Code: 1006

Description: This alarm indicates that the oldest video in the NVR's video archive is less than the desired retention setting. This alarm is simple in that it just checks the oldest footage in the video database. It is not suitable for more complex scenarios with variable retention periods.

Recommended Action: Check the video, if the video does not meet your desired retention setting you may need to adjust your camera settings such that the storage size is not so high or you may need additional storage.

GCore Recording Throughput

Alarm Type Code: 1007

Description: This alarm indicates that the recording throughput from all cameras has fallen beneath the set threshold value. If cameras are configure on the NVR it may indicate a serious network issue and that no cameras are recording.

Recommended Action: Check the NVR and network and that all cameras are streaming.

GCore Configuration Changed

Alarm Type Code: 1009

Description: This alarm is just a notification that the G-Core Configuration has been modified.

Recommended Action: None

GCore System Error

Alarm Type Code: 1010

Description: This alarm is a notification that the GCore System Error Action has occurred in a situation that is not otherwise handled. Since this is just a notification and the source of the problem is not tracked this alarm does not have an active or resolved state.

Recommended Action: Consult your support representation regarding the content of the error message.

GCore Redundant Power Failure

Alarm Type Code: 1011

Description: This alarm indicates on supported systems that GCore has been alerted to the failure of power from one of the redundant power supply units (PSUs) on the NVR. This action is only supported on select G-Scopes with dual redundant PSU and requires that the PSU is wired internally to the MIO module.

Recommended Action: Check the PSU unit on the NVR it may need replacing.

GCore Dongle Missing

Alarm Type Code: 1012

Description: This alarm indicates that the G-Core license dongle has been removed or failed (in the case of a physical dongle) or that it has failed (in the case of a soft dongle). In the case of a remote dongle this could be due to a network outage or due to the Remote SAM server being offline. If the system has dongle cache enabled then the G-Core will continue to run for a period of time before ceasing operation.

Recommended Action: Urgently investigate the cause of the dongle failure.

GCore Analytic Host

Alarm Type Code: 1013

Description: This alarm is triggered when a G-Tect Analytic Host service is configured in G-Core but no G-Tect Live Check action is being received. This likely indicates a failure in the G-Tect service or that the G-Tect service is stopped.

Recommended Action: Investigate why the service may be stopped or not working.

GCore Action Overdue

Alarm Type Code: 1014

Description: This is a bespoke alarm that can be used to monitor when expected G-Core actions are no longer being received. This can be used to alert when an external system that sends these actions is failing to send them. For example a logistic warehouse might expect a consistent flow of Barcode actions, or an LPR system would expect to be seeing regular traffic and LPR or NPR actions.

Configuration

The configuration for this alarm takes place in the appsettings.json file for the G-Health Client. This is found on the client NVR in the install folder for the G-Health Client (usually C:\Program Files\G-Health\G-Health Client ).

  1. Open to edit the appsettings.json file.
  2. Add a section for GCoreOptions like below. Where ActionCode specifies the action code number of the action you want to monitor and OverdueTimeMins specifies the number of minutes without this action before an alarm will be raised.
  3. Restart the G-Health Client Service after changes to the appsettings.json have been saved.
   "GCoreOptions": {
      "ActionMonitors": [
         {
            "ActionCode": 2140,
            "OverdueTimeMins": 7
         },
         {
            "ActionCode": 1365,
            "OverdueTimeMins": 1
         }
      ]
   }

A list of G-Core actions can be found here.

Storage Alarms

HardDriveArrayDegraded

Alarm Type Code: 2001

Description: This alarm indicates that a Hard Drive RAID Array has entered the degraded state. This typically indicates a Hard Drive failure.

Recommended Action: Identify and replace the failed drive before the RAID array fails completely and data is lost.

HardDriveMissing

Alarm Type Code: 2002

Description: This alarm indicates that a disk that was connected to the system is no longer detected. This could mean that the disk has failed.

Recommended Action: Check the disks attached to the NVR system. Replace any that have failed. Once any failed disks have been replaced use the Clear Missing Disks button on the tools tab of the G-Health Client to remove the Client's memory of this disk and stop the alarm.

HardDriveSmart

Alarm Type Code: 2003

Description: This alarm indicates a S.M.A.R.T status error from a drive in the system. This could indicate that a drive is starting to fail.

Recommended Action: Use disk maintenance tools, preferably those from the drive manufacturer to test the disks for errors and consider pre-emptively replacing any with issues.

HardDriveTemperature

Alarm Type Code: 2004

Description: This alarm indicates that the temperature of a drive in the system is running above the set tolerance level in the alarm's rule. If a hard drive runs at too hot a temperature it can be prone to failure.

Recommended Action: Check the environment that the NVR is installed in. It may be that and air conditioning system has failed or that the NVR is just installed in too hot a location. If the environment is not too hot then it may be that a fan in the NVR Server has failed. Check these or contact your support representatives for guidance.

HardDriveArrayFailed

Alarm Type Code: 2005

Description: This alarm indicates that a RAID array in the NVR has failed and data has probably been lost. It is likely in this case that there is more than one failed disk that will need to be replaced.

System Alarms

System Drive Space

Alarm Type Code: 5001

Description: This alarm indicates that the amount of free space on the NVR's Operating System drive has dropped below a certain percentage. This is a critical alarm as if the free space drops too much then the G-Health Client will not be able to operate correctly and will not be able to report on other issues. Other software applications such as G-Core may fail to operate in such circumstances.

Recommended Action: Log on to the NVR and immediately free up some space and try to determine why the space has dropped so low.

System Memory

Alarm Type Code: 5002

Description: This alarm indicates that the NVR's system memory usage is very high and above the alarm threshold.

Recommended Action: Check what processes are utilizing the memory. You may need to stop non essential services or adjust your configuration to be less memory intensive.

System Processor Utilisation

Alarm Type Code: 5003

Description: This alarm indicates high CPU usage above the alarm threshold.

Recommended Action: Check what processes are utilizing the CPU. You may need to stop non essential services or adjust your configuration to be less CPU intensive. Discuss with your support personnel if required.

System Restarted

Alarm Type Code: 5004

Description: This is a notification that the NVR has under gone a reboot.

Recommended Action: If the reboot is unexpected you may wish to investigate the cause. Sometimes this can be due to automatic updates or a power outage.

Time Sync

Alarm Type Code: 5005

Description: This alarm indicates that the NVR's time differs from the set NTP server by more than the allowed amount.

Recommended Action: This is not such an issue if the time drift is small and the NVR is stand alone on its site, but if it differs from other NVRs on the same site or if it is a significant time difference this should be rectified immediately. Check your NTP configuration. If this alarm occurs frequently and resolves itself frequently there may be a problem with your system's clock or the CMOS battery on the NVRs mainboard may need to be replaced.

Client Alarm Types

Client Overdue

Alarm Type Code: 6001

Description: This alarm indicates that the NVR has not been connected to the G-Health server for more than the allowed time. This could be due to a network outage or it could be due to a dead NVR or some software problem on the NVR.

Recommended Action: It should be established promptly whether the NVR is still powered on and active. Any network issues should be investigated.