5.02021-11-21T21:57:07ZZshareZshare Synology ClusterZshare Synology Cluster## Description
Template to monitor Synology HA Solution
## Overview
Template is based on [Synology MIB Guide](https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/All/enu/Synology_DiskStation_MIB_Guide.pdf) and monitor only an Synology HA Cluster
Is based on snmp v2 data from section Synology SHA MIB
Installation notes
1. Don't forget to set the right community name in template Macros section
2. Before add to host set/add in Zabbix-> Administration -> General -> Value mapping
1. Synology Cluster Status
0 ⇒ normal
1 ⇒ warning
2 ⇒ critical
3 ⇒ upgrading
4 ⇒ processing
2. Synology Heartbeat Status
0 ⇒ normal
1 ⇒ abnormal
2 ⇒ disconnected
3 ⇒ empty
3. Synology AutoFailover
1 ⇒ True
2 ⇒ False
### Features
1. Items are explained in details
2. Triggers are explained and contain tags to show the problem details depending on received value
### Environment
Created and tested with:
* Synology DSM 6.2-24922on following models:
+ RS820RP+
* Zabbix version 4.0.0
### Note(s)
You can write questions also to [tudorticau@mail.ru](mailto:tudorticau@mail.ru)
Nice to read when will deploy Synology HA environment this [Synology HA White Paper](https://global.download.synology.com/download/Document/Software/WhitePaper/Package/HighAvailability/All/enu/Synology_SHA_White_Paper.pdf "Synology HA White Paper")
## Author
Tudor Ticau
ZshareCluster- Active Server NameSNMP_AGENT.1.3.6.1.4.1.6574.106.1.0activeNodeName600CHARHostname of active server/NASClusterPOST
- Cluster AutoFailoverSNMP_AGENT.1.3.6.1.4.1.6574.106.3.0clusterAutoFailover60Whether cluster can failover once something went wrong
true (1)
false (2)ClusterSynology AutoFailoverPOST{last()}=2{HOST.NAME} AutoFailover is not enabledHIGHCluster can't do failover by itself. This can lead to big downtimeYESState{ITEM.VALUE}
- Cluster NameSNMP_AGENT.1.3.6.1.4.1.6574.106.4.0clusterName600CHARHostname of High-Availability clusterCluster
- Cluster StatusSNMP_AGENT.1.3.6.1.4.1.6574.106.5.0clusterStatus60Status of High-Availability cluster
Possible values:
normal (0) - The High-Availability cluster is healthy
warning (1) - The High-Availability cluster has something went wrong. Action should be taken to resume High-Availability feature. Please refer to High-Availability Manager for more details.
critical (2) - The High-Availability cluster is in danger, and should be resolved as soon as possible.Please refer to High-Availability Manager for more details.
upgrading (3) - The High-Availability cluster is upgrading.
processing (4) - The High-Availability cluster is undergoing some operation.ClusterSynology Cluster StatusPOST{last()}<>0{HOST.NAME} Cluster in Failed stateDISASTERThe High-Availability cluster has something went wrong. Action should be taken to resume High-Availability feature.
Possible values:
normal (0) - The High-Availability cluster is healthy
warning (1) - The High-Availability cluster has something went wrong. Action should be taken to resume High-Availability feature. Please refer to High-Availability Manager for more details.
critical (2) - The High-Availability cluster is in danger, and should be resolved as soon as possible.Please refer to High-Availability Manager for more details.
upgrading (3) - The High-Availability cluster is upgrading.
processing (4) - The High-Availability cluster is undergoing some operation.YESCluster State{{ITEM.VALUE}.regsub([0], Healthy)}Cluster State{{ITEM.VALUE}.regsub([1], Warning)}Cluster State{{ITEM.VALUE}.regsub([2], Critical)}Cluster State{{ITEM.VALUE}.regsub([3], Upgrading)}Cluster State{{ITEM.VALUE}.regsub([4], Processing)}
- Heartbeat LatencySNMP_AGENT.1.3.6.1.4.1.6574.106.8.0heartbeatLatency60FLOATsHeartbeat latency in microseconds (10^-6 seconds)ClusterMULTIPLIER0.000001{min(#5)}>10s{HOST.NAME} Heartbeat Latency is over 10 secDISASTERHeartbeat Latency is over 10 sec on {HOST.NAME}. Check network between the NAS or maybe you have high trafficYESValue{ITEM.VALUE}
- Heartbeat StatusSNMP_AGENT.1.3.6.1.4.1.6574.106.6.0heartbeatStatus60Status of heartbeat connection
Possible values:
normal (0) - The heartbeat connection is normal
abnormal (1) - Some information about heartbeat is not available
disconnected (2) - The High-Availability cluster loses connection to passive server through heartbeat interface, or it is currently in split-brain mode
empty (3) - The High-Availability cluster has no passive server.ClusterSynology Heartbeat Status{last()}<>0{HOST.NAME} Heartbeat FailedDISASTERPossible values:
normal (0) - The heartbeat connection is normal
abnormal (1) - Some information about heartbeat is not available
disconnected (2) - The High-Availability cluster loses connection to passive server through heartbeat interface, or it is currently in split-brain mode
empty (3) - The High-Availability cluster has no passive server.YES{HOST.NAME} Cluster in Failed state{Zshare Synology Cluster:clusterStatus.last()}<>0Heartbeat State{{ITEM.VALUE}.regsub([0], "Normal")}Heartbeat State{{ITEM.VALUE}.regsub([1], Abnormal)}Heartbeat State{{ITEM.VALUE}.regsub([2], "Disconnected - no connection to passive server")}Heartbeat State{{ITEM.VALUE}.regsub([3], "Empty - no passive server")}
- Heartbeat Transfer SpeedSNMP_AGENT.1.3.6.1.4.1.6574.106.7.0heartbeatTxRate60BpsTransfer speed of heartbeat in kilo-byte-per-secondClusterMULTIPLIER1000
- Passive Server NameSNMP_AGENT.1.3.6.1.4.1.6574.106.2.0passiveNodeName600CHARHostname of passive serverCluster
{$SNMP_COMMUNITY}publicHeartbeat Latency1A7C11- Zshare Synology ClusterheartbeatLatency
Synology AutoFailover1True2FalseSynology Cluster Status0normal1warning2critical3upgrading4processingSynology Heartbeat Status0normal1abnormal2disconnected3empty