Synology DiskStation

MIB Guide

1
 Table of
Contents

Introduction  01

Supported MIB files  03

Synology MIB files  05

Synology System MIB
Synology Disk MIB
Synology RAID MIB
Synology UPS MIB
Synology Smart MIB
Synology Services MIB
Synology StorageIO MIB
Synology SpaceIO MIB
Synology FlashCache MIB
Synology iSCSI LUN MIB
Synology Ebox MIB
Synology SHA MIB
Synology NFS MIB
Synology GPUInfo MIB
Synology Port MIB
Synology iSCSI Target MIB

Useful OIDs  20

Monitor Specific OIDs  23

Import MIB Files
Set up the NMS

Document Revision History  27

THIS DOCUMENT CONTAINS PROPRIETARY TECHNICAL
INFORMATION WHICH IS THE PROPERTY OF SYNOLOGY
INCORPORATED AND SHALL NOT BE REPRODUCED, COPIED, Copyright and Disclaimer Notices  28
OR USED AS THE BASIS FOR DESIGN, MANUFACTURING, OR
SALE OF APPARATUS WITHOUT WRITTEN PERMISSION OF
SYNOLOGY INCORPORATED
 Introduction

Introduction

Synology DiskStation Manager (DSM) allows users to monitor the status of their Synology
servers through Network Management Systems (NMS) via Simple Network Management
Protocol (SNMP). However, Synology DSM does not provide SNMP trap capability.

This document introduces Management Information Base (MIB) files of Synology servers. It
focuses on which MIB files are supported by DSM, while also describes how Object Identifiers
(OIDs) in Synology MIBs are used with your preferred NMS software. Users are encouraged to
have experience and knowledge of NMS and SNMP before consulting this document.

01
 Supported MIB files

Supported MIB files

DSM and SRM supports numerous MIB files that can help users monitor different information
on their Synology NAS/IP SAN (hereinafter referred to as Synology servers). Table 2-1 shows
the MIBs supported by DSM and SRM.

These MIB files can be separated into two types: general SNMP MIB and Synology MIB. General
SNMP MIB files are equipped on NMS clients natively.

Synology MIB files can provide specific data about a Synology server system, disks, RAID, and
connected UPS devices. Please see the “Synology MIB Files” section below for more Synology
MIB information.

You can download the Synology MIB file here.

Note: For all tables in this document, unless otherwise noted, DSM denotes that this OID
is compatible with DSM 6.2.4 and above, and DSM UC denotes that this OID is compatible
with DSM UC 3.0.

Table 2-1 General MIB Files Supported by DSM

MIB Explanation
DISMAN-EVENT-MIB For defining event triggers and actions for network
management purposes
DISMAN-SCHEDULE-MIB For scheduling SNMP set operations periodically or at
specific points in time
HOST-RESOURCES-MIB For use in managing host systems
IF-MIB For describing network interface sub-layers
IP-FORWARD-MIB For the management of CIDR multipath IP Routes
IP-MIB For IP and ICMP management objects
IPV6-ICMP-MIB For entities implementing the ICMPv6
IPV6-MIB For entities implementing the IPv6 protocol
IPV6-TCP-MIB For entities implementing TCP over IPv6
IPV6-UDP-MIB For entities implementing UDP over IPv6
NET-SNMP-AGENT-MIB For monitoring structures for the Net-SNMP agent
NET-SNMP-EXTEND-MIB For scripted extensions for the Net-SNMP agent
NET-SNMP-VACM-MIB Defines Net-SNMP extensions to the standard VACM view
table
NOTIFICATION-LOG-MIB For logging SNMP Notifications
SNMP-COMMUNITY-MIB To help support coexistence between SNMPv1, SNMPv2c,
and SNMPv3
SNMP-FRAMEWORK-MIB The SNMP Management Architecture MIB
SNMP-MPD-MIB For Message Processing and Dispatching
SNMP-USER-BASED-SM-MIB For the SNMP User-based Security Model
SNMP-VIEW-BASED-ACM- For the View-based Access Control Model for SNMP
MIB
SNMPv2-MIB For SNMP entities
SYNOLOGY-DISK-MIB For Synology disk information (Synology only)
SYNOLOGY-EBOX-MIB For Synology ebox information (Synology only)

03
 Supported MIB files

SYNOLOGY-FLASHCACHE- For Synology FlashCache information (Synology only)

MIB
SYNOLOGY-GPUINFO-MIB For Synology GpuIO information (Synology only)
SYNOLOGY-ISCSILUN-MIB For Synology iSCSI LUN information (Synology only)
SYNOLOGY-ISCSITarget- For Synology iSCSI Target information (Synology only)
MIB
SYNOLOGY-NFS-MIB For Synology NFS information (Synology only)
SYNOLOGY-PORT-MIB.txt For Synology Ethernet Port information (Synology only)
SYNOLOGY-RAID-MIB For Synology RAID information (Synology only)
SYNOLOGY-SERVICES-MIB For Synology services information (Synology only)
SYNOLOGY-SHA-MIB For Synology High-Availability information (Synology only)
SYNOLOGY-SMART-MIB For Synology smart information (Synology only)
SYNOLOGY-SPACEIO-MIB For Synology SpaceIO information (Synology only)
SYNOLOGY-STORAGEIO-MIB For Synology StorageIO information (Synology only)
SYNOLOGY-SYSTEM-MIB For Synology system information (Synology only)
SYNOLOGY-UPS-MIB For Synology UPS information (Synology only)
TCP-MIB For managing TCP implementations
UCD-DISKIO-MIB For disk IO statistics
UCD-DLMOD-MIB For dynamic loadable MIB modules
UCD-SNMP-MIB For private UCD SNMP MIB extensions
UDP-MIB For managing UDP implementations

04
 Synology MIB files

Synology MIB files

The following Synology MIB files are provided in DSM. These MIB files are the child-nodes of
OID (Object Identifier) 1.3.6.1.4.1.6574. Table 3-1 shows the exact OID of each MIB. Please
note that the MIB files are mutually dependent. Before your NMS can monitor any of the items
in these MIB files, please make sure that all of them have been imported together and use
SNMPv2c to obtain the complete Synology OID information.

Table 3-1 OID of Synology MIBs

Last
OID Name File Name updated
version
.1.3.6.1.4.1.6574.1 synoSystem SYNOLOGY-SYSTEM-MIB.txt DSM 6.0.2
.1.3.6.1.4.1.6574.2 synoDisk SYNOLOGY-DISK-MIB.txt DSM 7.1
.1.3.6.1.4.1.6574.3 synoRaid SYNOLOGY-RAID-MIB.txt DSM 7.0
.1.3.6.1.4.1.6574.4 synoUPS SYNOLOGY-UPS-MIB.txt DSM 6.0.1
.1.3.6.1.4.1.6574.5 synologyDiskSMART SYNOLOGY-SMART-MIB.txt DSM 6.0.1
.1.3.6.1.4.1.6574.6 synologyService SYNOLOGY-SERVICES-MIB. DSM 6.2.1
txt
.1.3.6.1.4.1.6574.101 storageIO SYNOLOGY-STORAGEIO-MIB. DSM 6.1.7
txt
.1.3.6.1.4.1.6574.102 spaceIO SYNOLOGY-SPACEIO-MIB.txt DSM 6.0.1
.1.3.6.1.4.1.6574.103 flashCache SYNOLOGY-FLASHCACHE- DSM 6.2.2
MIB.txt
.1.3.6.1.4.1.6574.104 synologyiSCSILUN SYNOLOGY-ISCSILUN-MIB.txt DSM 6.1.7
.1.3.6.1.4.1.6574.105 synologyEbox SYNOLOGY-EBOX-MIB DSM 6.2.1
.1.3.6.1.4.1.6574.106 synologyHA SYNOLOGY-SHA-MIB DSM 6.2.2
.1.3.6.1.4.1.6574.107 NFS SYNOLOGY-NFS-MIB.txt DSM 7.0
.1.3.6.1.4.1.6574.108 GpuInfo SYNOLOGY-GPUINFO-MIB. DSM 6.2.2
txt
.1.3.6.1.4.1.6574.109 synoEthPort SYNOLOGY-PORT-MIB.txt SRM 1.2.5
.1.3.6.1.4.1.6574.110 synologyiSCSITarget SYNOLOGY-ISCSITarget-MIB DSM 7.0

05
 Synology MIB files

Synology System MIB (OID: .1.3.6.1.4.1.6574.1)

The Synology System MIB displays all system statuses, including temperature and fan status.
Users can monitor this MIB for system functionality. Table 3-2 shows information provided in
the System MIB.

Table 3-2 System MIB

Supported
OID Name Type Status Type Explanation
OS
.1 systemStatus Integer Normal(1) System partition DSM, DSM
Failed(2) status UC
.2 temperature Integer - Temperature of this DSM, DSM
NAS UC
.3 powerStatus Integer Normal(1) Returns error if DSM, DSM
Failed(2) power supplies fail UC

.4.1 systemFanStatus Integer Normal(1) Returns error if DSM, DSM

Failed(2) system fan fails UC
.4.2 cpuFanStatus Integer Normal(1) Returns error if CPU DSM, DSM
Failed(2) fan fails UC
.5.1 modelName String - Model name of this DSM, DSM
NAS UC
.5.2 serialNumber String - Model serial DSM, DSM
number UC
.5.3 version String - The version of DSM DSM, DSM
UC
.5.4 upgradeAvailable Integer Available(1) Checks whether DSM, DSM
Unavailable(2) a new version or UC
Connecting(3) update of DSM is
Disconnected(4) available
Others(5)
.6 controllerNumber Integer Controller A(0) The controller DSM UC
Controller B(1) number

Synology Disk MIB (OID: .1.3.6.1.4.1.6574.2)

The Synology Disk MIB contains several types of information regarding hard drives, including
ID, type and so on, as listed in Table 3-3. This MIB is a table in SNMP. As such, it can increase
or decrease in size when disks are inserted or removed. For example, if a disk is inserted, an
additional row containing relevant information will emerge. The OID DiskIndex (.1) is reserved
for an index of table rows and cannot be accessed. Table 3-4 describes the contents of each
DiskStatus in detail.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.2.1.1" as a prefix since
this MIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.2.1.1.3"
can be used to get the disk model.

06
 Synology MIB files

Table 3-3 Disk MIB

OID Name Type Status Explanation Supported

Type OS
.1 diskIndex Integer - Used internally for SNMP DSM, DSM
table and not accessible UC
.2 diskID String - Disk name in DSM DSM, DSM
UC
.3 diskModel String - Disk model DSM, DSM
UC
.4 diskType String - Disk type, e.g. SATA, SSD DSM, DSM
UC
.5 diskStatus Integer Normal(1)* Current disk status DSM, DSM
UC
.6 diskTemperature Integer - Disk temperature DSM, DSM
UC
.7 diskRole String data * The role of the disk in DSM 7.0
system and above
.8 diskRetry Integer - The count of each disk DSM 7.0
connection retries and above
.9 diskBadSector Integer - The count of each disk I/ DSM 7.0
O bad sector and above
.10 diskIdentifyFail Integer - The count of each disk DSM 7.0
identify fails and above
.11 diskRemainLife Integer - The estimate remain life DSM 7.0
of each disk and above
.12 diskName String - Disk name which will DSM 7.0
keep the same value in and above
different DSM version
.13 diskHealthStatus Integer Normal(1)* Current disk health status DSM 7.1
and above

* For diskStatus details, please Table 3-4

* For diskRole details, please see Table 3-5

* For diskHealthStatus details, please see Table 3-6

Table 3-4 DiskStatus Explanation

Status Explanation Supported OS
Normal(1) The disk is functioning normally DSM, DSM UC
Initialized(2) The disk has system partitions but no DSM, DSM UC
data
NotInitialized(3) The disk is not partitioned DSM, DSM UC
SystemPartitionFailed(4) Partitions on the disk are damaged DSM, DSM UC
Crashed(5) The disk is damaged DSM, DSM UC

Table 3-5 DiskRole Explanation

Status Explanation Supported OS
data Used by storage pool DSM 7.0 and
above
hotspare Assigned as a hot spare disk DSM 7.0 and
above
ssd_cache Used by SSD Cache DSM 7.0 and
above
none Not used by storage pool, nor hot spare, DSM 7.0 and
nor SSD Cache above
unknown Some error occurred DSM 7.0 and
above

07
 Synology MIB files

Table 3-6 diskHealthStatus Explanation

Status Explanation Supported OS
Normal(1) The disk health status is DSM 7.1 and above
normal.
Warning(2) The disk health status is DSM 7.1 and above
warning.
Critical(3) The disk health status is DSM 7.1 and above
critical.
Failing(4) The disk health status is DSM 7.1 and above
failing.

Synology RAID MIB (OID: .1.3.6.1.4.1.6574.3)

In addition to the disk MIB, Synology also provides an MIB for monitoring RAID status. This
MIB is similar to the disk MIB in that rows will appear or disappear to reflect RAID creation and
deletion. Table 3-7 lists the contents of the RAID MIB. Table 3-8 describes each RAID status in
detail.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.3.1.1" as a prefix since
this MIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.3.1.1.3"
can be used to get the RAID status.

Table 3-7 RAID MIB

OID Name Type Status Explanation Supported
Type OS
.1 raidIndex Integer - Used internally for DSM, DSM UC
SNMP table and not
accessible
.2 raidName String - The name of each DSM, DSM UC
RAID in DSM
.3 raidStatus Integer Normal(1)* It shows the RAID DSM, DSM UC
status right now
.4 raidFreeSize Counter64 - The free size of DSM, DSM UC
volume / disk group
.5 raidTotalSize Counter64 - The total size of DSM, DSM UC
volume / disk group
.6 raidHotspareCnt Integer - Total hotspare DSM 7.0 and
disks count which above
can protected raid
(smaller than 0 means
something wrong)

* For RAID status details, please Table 3-8

08
 Synology MIB files

Table 3-8 RAID Status Explanation

Status Explanation
Normal(1) RAID is functioning normally
Repairing(2)

Migrating(3)

Expanding(4)

Deleting(5)

Creating(6) These statuses are shown when RAID is created or

deleted
RaidSyncing(7)

RaidParityChecking(8)

RaidAssembling(9)

Canceling(10)
Degrade(11) Degrade is shown when a tolerable failure of disk(s)
occurs
Crashed(12) RAID has crashed and is now read-only
DataScrubbing (13) RAID is DataScrubbing
RaidDeploying (14) RAID is deploying Single volume on pool
RaidUnDeploying (15) RAID is not deploying Single volume on pool
RaidMountCache (16) RAID is mounting SSD cache
RaidUnmountCache (17) RAID is not mounting SSD cache
RaidExpandingUnfinishedSHR RAID continue expanding SHR if interrupted
(18)
RaidConvertSHRToPool (19) RAID is converting Single volume on SHR to multiple
volume on SHR
RaidMigrateSHR1ToSHR2 (20) RAID is migrating SHR1 to SHR2
RaidUnknownStatus (21) RAID status is not included in the status above

Synology UPS MIB (OID: .1.3.6.1.4.1.6574.4)

The Synology UPS MIB provides the ability to monitor the status of a UPS device connected
to the Synology servers. Please note that the available OIDs of the UPS MIB depend on what
information is provided by the UPS device. If a UPS device does not provide data for a certain
OID, that OID will not appear in the NMS software. Table 3-9 shows a partial UPS MIB table
only. If you are interested in all OIDs, please refer to the MIB file SYNOLOGY-UPS-MIB.txt.

Table 3-9 Partial UPS MIB

OID Name Type Status Explanation Supported
Type OS
.1.1 upsDeviceModel String - UPS device DSM, DSM UC
model
.1.2 upsDeviceManufacturer String - UPS device DSM, DSM UC
manufacturer
.1.3 upsDeviceSerial String - UPS device serial DSM, DSM UC
number
.2.1 upsInfoStatus String - UPS device status DSM, DSM UC
.2.6.2 upsInfoMfrDate String - UPS device DSM, DSM UC
manufacturing
date
.2.12.1 upsInfoLoadValue Float - Load on UPS DSM, DSM UC
device (percent)
.3.1.1 upsBatteryChargeValue Float - Battery charge DSM, DSM UC

09
 Synology MIB files

OID Name Type Status Explanation Supported

Type OS
.3.1.4 upsBatteryChargeWarning Float - Battery level DSM, DSM UC
at which UPS
switches to
Warning state
(percent)
.3.12 upsBatteryType Float - Battery chemistry DSM, DSM UC

Synology Smart MIB (OID: .1.3.6.1.4.1.6574.5)

The Synology SMART MIB provides the SMART information of each disk same as Storage
Manager does. Because every disk may have different SMART attributes, one OID records one
SMART attribute and has diskSMARTInfoDevName to indicate which disk it belongs to.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.5.1.1" as a prefix since
this MIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.5.1.1.3"
can be used to get the SMART attribute name.

Table 3-10 SMART MIB

OID Name Type Status Explanation Supported
Type OS
.1 diskSMARTInfoIndex Integer - Used internally for DSM
SNMP table and
not accessible
.2 diskSMARTInfoDevName String - Describes the DSM
disk to which
this SMART info
belongs to
.3 diskSMARTAttrName String - The name of DSM
the SMART info
attribute, e.g. Raw_
Read_Error_Rate
.4 diskSMARTAttrId Integer - SMART attribute ID DSM
number
.5 diskSMARTAttrCurrent Integer - SMART attribute DSM
current value
.6 diskSMARTAttrWorst Integer - SMART attribute DSM
worst value
.7 diskSMARTAttrThreshold Integer - SMART attribute DSM
threshold value
.8 diskSMARTAttrRaw Integer - SMART attribute DSM
raw value
.9 diskSMARTAttrStatus String - Status of this DSM
SMART info
.10 diskSMARTAttrRaw64 Counter64 - SMART attribute DSM
raw value (64 bit
VER.)

10
 Synology MIB files

Synology Services MIB (OID: .1.3.6.1.4.1.6574.6)

The Synology Services MIB monitors the number of users logging in via HTTP, CIFS, AFP, NFS,
FTP, SFTP, TELNET, and SSH.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.6.1.1" as a prefix since
this MIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.6.1.1.2"
can be used to get the service name.

Table 3-11 Services MIB

OID Name Type Status Explanation
Type
.1 serviceInfoIndex Integer - Used internally for services table and not
accessible
.2 serviceName String - The name of the service
.3 serviceUsers Integer - The number of users using this service

Synology StorageIO MIB (OID: .1.3.6.1.4.1.6574.101)

The Synology StorageIO MIB has I/O information of disks.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.101.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.101.1.1.2" can be used to get the name of the device that we are counting/
checking.

Table 3-12 StorageIO MIB

OID Name Type Status Explanation Supported
Type OS
.1 storageIOIndex Integer - Used internally for DSM, DSM
storageio table and UC
not accessible
.2 storageIODevice String - The name of the DSM, DSM
device we are UC
counting/checking
.3 storageIONRead Counter32 - The number of DSM, DSM
bytes read from this UC
device since boot

(32 bit VER.)

.4 storageIONWritten Counter32 - The number of DSM, DSM
bytes written to this UC
device since boot

(32 bit VER.)

.5 storageIOReads Counter32 - The number of read DSM, DSM
accesses from this UC
device since boot
.6 storageIOWrites Counter32 - The number of DSM, DSM
write accesses to UC
this device since
boot
.8 storageIOLA Integer - The load of disk (%) DSM, DSM
UC
.9 storageIOLA1 Integer - The 1-minute DSM, DSM
average load of disk UC
(%)

11
 Synology MIB files

OID Name Type Status Explanation Supported

Type OS
.10 storageIOLA5 Integer - The 5-minute DSM, DSM
average load of disk UC
(%)
.11 storageIOLA15 Integer - The-15 minute DSM, DSM
average load of disk UC
(%)
.12 storageIONReadX Counter64 - The number of DSM, DSM
bytes read from this UC
device since boot

(64 bit VER.)

.13 storageIONWrittenX Counter64 - The number of DSM, DSM
bytes written to this UC
device since boot

(64 bit VER.)

.14 storageIODeviceSerial String The serial number DSM UC
of this device

Synology SpaceIO MIB (OID: .1.3.6.1.4.1.6574.102)

The Synology SpaceIO MIB has I/O information of volumes.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.102.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.102.1.1.2" can be used to get the name of the device where this volume is
mounted.

Table 3-13 SpaceIO MIB

OID Name Type Status Explanation Supported
Type OS
.1 spaceIOIndex Integer - Used internally for spaceIO DSM, DSM
table and not accessible UC
.2 spaceIODevice String - The name of the device DSM, DSM
this volume mounted on UC
.3 spaceIONRead Counter32 - The number of bytes read DSM, DSM
from this volume since UC
boot

(32 bit VER.)

.4 spaceIONWritten Counter32 - The number of bytes DSM, DSM
written to this volume UC
since boot

(32 bit VER.)

.5 spaceIOReads Counter32 - The number of read DSM, DSM
accesses from this volume UC
since boot
.6 spaceIOWrites Counter32 - The number of write DSM, DSM
accesses to this volume UC
since boot
.8 spaceIOLA Integer - The load of disk in the DSM, DSM
volume (%) UC
.9 spaceIOLA1 Integer - The 1 minute average load DSM, DSM
of disk in the volume (%) UC
.10 spaceIOLA5 Integer - The 5 minute average load DSM, DSM
of disk in the volume (%) UC

12
 Synology MIB files

OID Name Type Status Explanation Supported

Type OS
.11 spaceIOLA15 Integer - The 15 minute average DSM, DSM
load of disk in the volume UC
(%)
.12 spaceIONReadX Counter64 - The number of bytes read DSM, DSM
from this volume since UC
boot

(64 bit VER.)

.13 spaceIONWrittenX Counter64 - The number of bytes DSM, DSM
written to this volume UC
since boot

(64 bit VER.)

.14 spaceUUID String - The UUID of this volume DSM UC

Synology FlashCache MIB (OID: .1.3.6.1.4.1.6574.103)

The Synology FlashCache MIB monitors the resource usage of SSD cache. The collection
frequency is 5 seconds.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.103.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.103.1.1.2" can be used to get the name of the SSD on the flashcache that we
are counting/checking.

Note: The MIB is only suitable for the model which support SSD cache. Otherwise, it will
return zero value for each OID path.

Table 3-14 FlashCache MIB

OID Name Type Status Explanation Supported
Type OS
.1 flashCacheIndex Integer - Reference index DSM, DSM
for each observed UC
device
.2 flashCacheSSDDev String - The SSD device DSM, DSM
name on flashcache UC
we are counting/
checking
.3 flashCacheSpaceDev String - The space device DSM, DSM
name on flashcache UC
we are counting/
checking
.4 flashCacheReadHits Counter64 - The number of DSM, DSM
reads on flashcache UC
.5 flashCacheWriteHits Counter64 - The number of DSM, DSM
writes on flashcache UC
.6 flashCacheDiskRead Counter64 - The number of DSM, DSM
reads on disk UC
.7 flashCacheDiskWrite Counter64 - The number of DSM, DSM
writes on disk UC
.8 flashCacheTotalRead Counter64 - The number of DSM, DSM
reads on volume UC
with flashcache

13
 Synology MIB files

OID Name Type Status Explanation Supported

Type OS
.9 flashCacheTotalWrite Counter64 - The number of DSM, DSM
writes on volume UC
with flashcache
.10 flashCacheReadHitRate Integer - The read hit rate of DSM, DSM
flashcache (%) UC
.11 flashCacheWriteHitRate Integer - The write hit rate of DSM, DSM
flashcache (%) UC
.12 flashCacheReadSeqSkip Counter64 - The number of DSM, DSM
skipped sequential UC
reads on flashcache
.13 flashCacheWriteSeqSkip Counter64 - The number of DSM, DSM
skipped sequential UC
writes on flashcache
.14 flashCacheWriteMissSsd Counter64 - The number of data DSM, DSM
writes to SSD for the UC
first time
.15 flashCacheSsdUuid String - The SSD UUID on DSM, DSM
flashcache we are UC
counting/checking

Synology iSCSI LUN MIB (OID: .1.3.6.1.4.1.6574.104)

The Synology iSCSI LUN MIB can list all the loaded LUNs and show their running information. If
a LUN has been created but not loaded (e.g. when linked to a target), it will not appear in this
list. The throughput is 64-bit and composed of two 32-bit integers. For example, the iSCSi LUN
read throughput is composed of higher 32-bit and lower 32-bit throughput.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.104.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.104.1.1.2" can be used to get the iSCSI LUN uuid.

Table 3-15 iSCSI LUN MIB

OID Name Type Status Explanation Supported
Type OS
.1 iSCSILUNInfoIndex Integer - Used DSM, DSM
internally for UC
iSCSI LUN
table and not
accessible
.2 iSCSILUNUUID String - LUN uuid DSM, DSM
UC
.3 iSCSILUNName String - LUN name DSM, DSM
UC
.4 iSCSILUNThroughputReadHigh Integer - The higher DSM, DSM
32 bit of read UC
throughput
.5 iSCSILUNThroughputReadLow Integer - The lower 32 DSM, DSM
bit of read UC
throughput
.6 iSCSILUNThroughputWriteHigh Integer - The higher 32 DSM, DSM
bit of write UC
throughput

14
 Synology MIB files

OID Name Type Status Explanation Supported

Type OS
.7 iSCSILUNThroughputWriteLow Integer - The lower 32 DSM, DSM
bit of write UC
throughput
.8 iSCSILUNIopsRead Integer - LUN read DSM, DSM
iops UC
.9 iSCSILUNIopsWrite Integer - LUN write DSM, DSM
iops UC
.10 iSCSILUNDiskLatencyRead Integer - LUN read DSM, DSM
disk latency UC
.11 iSCSILUNDiskLatencyWrite Integer - LUN write DSM, DSM
disk latency UC
.12 iSCSILUNNetworkLatencyTx Integer - LUN network DSM, DSM
tx latency UC
.13 iSCSILUNNetworkLatencyRx Integer - LUN network DSM, DSM
rx latency UC
.14 iSCSILUNIoSizeRead Integer - LUN read DSM, DSM
average i/o UC
size
.15 iSCSILUNIoSizeWrite Integer - LUN write DSM, DSM
average i/o UC
size
.16 iSCSILUNQueueDepth Integer - Number DSM, DSM
of iSCSI UC
commands in
LUN queue
.17 iSCSILUNType String - LUN type DSM, DSM
(advanced UC
lun, block lun,
etc.)
.18 iSCSILUNDiskLatencyAvg Integer - Average DSM 7.0
latency of and above
LUN disk
.19 iSCSILUNThinProvisionVolFreeMBs Integer - Free DSM 7.0
space(MB) and above
of thin
provisioning
lun's volume

Synology Ebox MIB (OID: .1.3.6.1.4.1.6574.105)

The Synology Ebox MIB provides the power status of expansion unit connected to Synology
servers. Table 3-16 shows the information provided in ebox MIB. Table 3-17 describes the
content of each eboxPower and eboxRedundantPower status in detail.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.105.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.105.1.1.2" can be used to get the expansion unit model.

Table 3-16 Ebox MIB

OID Name Type Status Explanation
Type
.1 eboxIndex Integer - Expansion unit Index
.2 eboxModel String - Expansion unit model

15
 Synology MIB files

OID Name Type Status Explanation

Type
.3 eboxPower Integer Normal (1)* Power status of expansion unit
.4 eboxRedundantPower Integer Normal (1)* Redundant power status of
expansion unit (if the ebox has no
redundant power interface, this OID
will not appear)

* For eboxPower and eboxRedundantPower details, please see Table 3-17.

Table 3-17 Ebox Power and Redundant Power Status Explanation

Status Explanation
Normal (1) The power supplies well
Poor (2) The power supplies badly
Disconnection (3) The power is not connected

Synology SHA MIB (OID: .1.3.6.1.4.1.6574.106)

The Synology SHA MIB provides basic cluster information and monitors cluster status and
heartbeat status.

Table 3-18 SHA MIB

OID Name Type Status Explanation Supported
Type OS
.1 activeNodeName String - Hostname of active server DSM
.2 passiveNodeName String - Hostname of passive server DSM
.3 clusterAutoFailover Integer true (1) Whether cluster can failover DSM
once something went wrong
false (2)
.4 clusterName String - Hostname of High-Availability DSM
cluster
.5 clusterStatus Integer * Status of High-Availability DSM
cluster
.6 heartbeatStatus Integer * Status of heartbeat connection DSM
.7 heartbeatTxRate Integer - Transfer speed of heartbeat in DSM
kilo-byte-per-second
.8 heartbeatLatency Integer - Heartbeat latency in DSM
microseconds (10^-6 seconds)

* For clusterStatus details, please see Table 3-19.

* For heartbeatStatus details, please see Table 3-20.

Table 3-19 Cluster Status Explanation

Status Explanation Supported
OS
normal (0) The High-Availability cluster is healthy DSM
warning (1) The High-Availability cluster has something went wrong. DSM
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 DSM
resolved as soon as possible.

Please refer to High-Availability Manager for more

details.
upgrading The High-Availability cluster is upgrading. DSM
(3)
processing The High-Availability cluster is undergoing some operation. DSM
(4)

Table 3-20 Heartbeat Status Explanation

16
 Synology MIB files

Status Explanation Supported

OS
normal (0) The heartbeat connection is normal. DSM
abnormal (1) Some information about heartbeat is not available. DSM
disconnected The High-Availability cluster loses connection to passive DSM
(2) server through heartbeat interface, or it is currently in
split-brain mode.
empty (3) The High-Availability cluster has no passive server. DSM

Synology NFS MIB (OID: .1.3.6.1.4.1.6574.107)

The Synology NFS MIB monitors the maximum latency and operations of NFS. Every value will
be cached for 3 seconds. Therefore, if you access a value twice within 3 seconds, you will get
the same value. The maximum latency will always clear the cache and recount the value once
the value has been updated.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.107.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.107.1.1.2" can be used to get the name of NFS.

Table 3-21 NFS MIB

OID Name Type Status Explanation Supported
Type OS
.1 nfsIndex Integer - Used internally for NFS DSM 7.0
table and not accessible and above
.2 nfsName String - The name of NFS DSM 7.0
and above
.3 nfsTotalMaxLatency Integer - Maximum latency of all the DSM 7.0
NFS operations and above
.4 nfsReadMaxLatency Integer - Maximum latency of the DSM 7.0
NFS read operations and above
.5 nfsWriteMaxLatency Integer - Maximum latency of the DSM 7.0
NFS write operations and above
.6 nfsTotalOPS Counter64 - Accumulated counts of all DSM 7.0
the NFS operations and above
.7 nfsReadOPS Counter64 - Accumulated counts of the DSM 7.0
NFS read operations and above
.8 nfsWriteOPS Counter64 - Accumulated counts of the DSM 7.0
NFS write operations and above

17
 Synology MIB files

Synology GPUInfo MIB (OID: .1.3.6.1.4.1.6574.108)

The Synology GPUInfo MIB monitors the resource usage of GPU card. The collection frequency
is 5 seconds.

Note: The MIB is only available on models which supports GPU card such as the DVA3221.
Otherwise, it will return zero value for each OID path.

Table 3-22 GPUInfo MIB

OID Name Type Status Type Explanation Supported
OS
.1 gpuInfoSupported Integer Supported Supported GPU DSM
(0)
Unsupported
(1)
.2 gpuUtilization Integer - The percentage of DSM
GPU time spent
on processing
user space in last
1 second
.3 gpuMemoryUtilization Integer - The percentage DSM
of GPU memory
usage in last 1
second
.4 gpuMemoryFree Integer - The amount of DSM
currently free GPU
memory in kb
.5 gpuMemoryUsed Integer - The amount of DSM
currently used
GPU memory in
kb
.6 gpuMemoryTotal Integer - The total physical DSM
GPU memory size

Synology Port MIB (OID: .1.3.6.1.4.1.6574.109)

The Synology Port MIB defines the status of each Ethernet port, such as link status and link
speed, as listed in Table 3-23. The cache interval is 5 seconds.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.109.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.109.1.1.2" can be used to get the link status of the Ethernet port.

Note: The MIB is only available on models running SRM, such as RT2600ac.

18
 Synology MIB files

Table 3-23 Port MIB

OID Name Type Status Type Explanation Supported
OS
.1 ethPortIndex Integer32 - Used internally for SNMP SRM 1.2.5
table and not accessible and above
.2 ethPortStatus Integer unknown(1) The link status of the SRM 1.2.5
up(2) Ethernet port and above
down(3)
.3 ethPortSpeed Gauge32 - The link speed of the SRM 1.2.5
Ethernet port in units of and above
1,000,000 bits per second

Synology iSCSI Target MIB (OID: .1.3.6.1.4.1.6574.110)

The Synology iSCSI Target MIB can list all iSCSI targets and show their basic information, such
as target name, IQN and connection status.

In order to directly access a specific OID, you must use ".1.3.6.1.4.1.6574.110.1.1" as

a prefix since this MIB contains the relative table and entry number. For example,
".1.3.6.1.4.1.6574.110.1.1.2" can be used to get the iSCSI target name.

Table 3-24 iSCSI Target MIB

OID Name Type Status Explanation Supported
Type OS
.1 iSCSITargetInfoIndex Integer32 - Used DSM 7.0
internally for and above
SNMP table
and not
accessible
.2 iSCSITargetName String - Name of the DSM 7.0
iSCSI target and above
.3 iSCSITargetIQN String - IQN of the DSM 7.0
iSCSI target and above
.4 iSCSITargetConnectionStatus String - Connection DSM 7.0
status of the and above
iSCSI target

19
 Useful OIDs

Useful OIDs

Although there are many native MIB files supported by Synology, user may be interested in
specific information about the Synology servers, such as CPU, memory and so on. The tables
below list the native OIDs related to load, CPU, memory, network and disk for gathering useful
device’s data easily.

Table 4-1 CPU-Related OID

OID Name Explanation Supported
OS
.1.3.6.1.4.1.2021.10.1.5.1 laLoadInt.1 System load average within DSM, DSM
the last 1 minute UC
.1.3.6.1.4.1.2021.10.1.5.2 laLoadInt.2 System load average within DSM, DSM
the last 5 minutes UC
.1.3.6.1.4.1.2021.10.1.5.3 laLoadInt.3 System load average within DSM, DSM
the last 15 minutes UC
.1.3.6.1.4.1.2021.11.9.0 ssCpuUser The percentage of CPU time DSM, DSM
spent processing user-level UC
code
.1.3.6.1.4.1.2021.11.10.0 ssCpuSystem The percentage of CPU time DSM, DSM
spent processing system- UC
level code, calculated over
the last minute
.1.3.6.1.4.1.2021.11.11.0 ssCpuIdle The percentage of DSM, DSM
processor time spent idle, UC
calculated over the last
minute

Table 4-2 Memory-Related OID

OID Name Explanation Supported
OS
.1.3.6.1.4.1.2021.4.3.0 memTotalSwap The total amount of swap DSM, DSM
space configured for this UC
host
.1.3.6.1.4.1.2021.4.4.0 memAvailSwap The amount of swap DSM, DSM
space currently unused or UC
available
.1.3.6.1.4.1.2021.4.5.0 memTotalReal The total amount of real/ DSM, DSM
physical memory UC
.1.3.6.1.4.1.2021.4.6.0 memAvailReal The amount of real/physical DSM, DSM
memory currently unused UC
or available
.1.3.6.1.4.1.2021.4.11.0 memTotalFree The total amount of DSM, DSM
memory free or available UC
for use on this host (This
value typically covers both
real memory and swap
space or virtual memory.)

20
 Useful OIDs

OID Name Explanation Supported

OS
.1.3.6.1.4.1.2021.4.13.0 memShared The total amount of real or DSM, DSM
virtual memory currently UC
allocated for use as shared
memory
.1.3.6.1.4.1.2021.4.14.0 memBuffer The total amount of real or DSM, DSM
virtual memory currently UC
allocated for use as
memory buffers
.1.3.6.1.4.1.2021.4.15.0 memCached The total amount of real or DSM, DSM
virtual memory currently UC
allocated for use as cached
memory

Table 4-3 Network-Related OID

OID Name Explanation Supported
OS
.1.3.6.1.2.1.31.1.1.1.1 ifName The textual name of the DSM, DSM
interface UC
.1.3.6.1.2.1.31.1.1.1.6 ifHCInOctets The total number of DSM, DSM
octets received on the UC
interface
.1.3.6.1.2.1.31.1.1.1.10 ifHCOutOctets The total number of DSM, DSM
octets transmitted out of UC
the interface

Table 4-4 Disk-Related OID

OID Name Explanation Supported
OS
.1.3.6.1.2.1.25.2.3.1.3 hrStorageDescr A description of the DSM, DSM
type and instance of the UC
storage described by this
entry
.1.3.6.1.2.1.25.2.3.1.4 hrStorageAllocationUnits The size, in bytes, of the DSM, DSM
data objects allocated UC
from this pool
.1.3.6.1.2.1.25.2.3.1.5 hrStorageSize The size of the storage DSM, DSM
represented by this UC
entry, in units of
hrStorageAllocationUnits
.1.3.6.1.2.1.25.2.3.1.6 hrStorageUsed The amount of the DSM, DSM
storage represented by UC
this entry
.1.3.6.1.4.1.2021.13.15.1.1.2 diskIODevice The name of the device DSM, DSM
we are counting/checking UC
.1.3.6.1.4.1.2021.13.15.1.1.12 diskIONReadX The number of bytes DSM, DSM
read from this device UC
since boot
.1.3.6.1.4.1.2021.13.15.1.1.13 diskIONWrittenX The number of bytes DSM, DSM
written to this device UC
since boot
.1.3.6.1.4.1.6574.2 synoDisk For Synology disk DSM, DSM
information (Synology UC
only)

21
 Useful OIDs

Table 4-5 System-Related OID

OID Name Explanation Suported OS
.1.3.6.1.4.1.6574.1 synoSystem For Synology system DSM, DSM UC
information (Synology only)

Table 4-6 RAID-Related OID

OID Name Explanation Suported OS
.1.3.6.1.4.1.6574.3 synoRaid For Synology RAID DSM, DSM UC
information (Synology only)

Table 4-7 UPS-Related OID

OID Name Explanation Suported OS
.1.3.6.1.4.1.6574.4 synoUPS For Synology UPS information DSM, DSM UC
(Synology only)

22
 Monitor Specific OIDs

Monitor Specific OIDs

In any NMS, particular MIB files are needed in order to capture data through SNMP. Users
need to import all MIB files to ensure that the NMS can resolve specific OIDs. Once imported,
data can be captured by setting up the NMS. Although the means of operating different kinds
of NMS may vary, the process of OID monitoring is similar. The overall procedure is as follows.

1. Import MIB file into NMS.

2. Set up the NMS to monitor specific OIDs.

The following guide demonstrates the usage of PRTG (a type of NMS) including how to import
MIB files and set up monitoring for the provided OIDs. For further help regarding PRTG, please
consult PRTG documentation, as the following is only intended to be a brief description of OID
monitoring.

Import MIB Files

As PRTG cannot import MIB files directly, Paessler MIB Importer is required to convert MIB files
into the PRTG format:

1. Download Paessler MIB Importer from http://www.paessler.com/tools/mibimporter and

install it on your computer.

2. Go to Import > MIB Files.

3. Choose all the Synology MIB file together and click Open File.

All MIB files (cf. Table 2-1) must be imported together as they are mutually dependent and
Paessler MIB Importer cannot load them individually. If the import is successful, a window as
shown in Figure 1 should appear. Detailed information is shown in Figure 2.

23
 Monitor Specific OIDs

Figure 1. Import MIB: Successful

Figure 2. Detailed Information on MIB

4. Go to File > Save As to export to the PRTG-supported format.

A PRTG-supported library containing the MIB information will then be generated.

24
 Monitor Specific OIDs

Set up the NMS

The PRTG-supported library containing the MIB files in question should be placed into the
folder: “snmplibs”. Once this has been done, specific OIDs can be set up for monitoring in
PRTG. This guide assumes that your Synology servers has already been added to the devices
list and focuses only on how to add OIDs for monitoring.

1. Enter the PRTG Network Monitor.

2. Go to Sensors > Add Sensor.

3. Click Add sensor to an existing device and choose a device.

25
 Monitor Specific OIDs

4. Choose SNMP Library and the library exported in the previous section.

5. Select items for monitoring.

26
 Document Revision History

Document Revision History

This table describes the revisions made to Synology servers MIB Guide.

Table 6-1 Document Revision History

Date Note
2012-07-19 Document created
2013-10-29 Modified OID name and added UPS MIB
2013-11-04 Added more MIBs and useful OID
2016-10-31 Added more MIBs
2018-06-30 Added Ebox MIB

Added useful OIDs in RAID MIB

2018-12-18 Added GPUInfo MIB

Added FlashCache MIB

2018-12-24 Added SHA MIB
2020-01-10 Added information for Synology Unified Controller and eGPU
MIB
2021-02-23 Added PORT MIB for SRM
2021-05-25 Added NFS MIB and iSCSI Target MIB
2022-04-19 Added useful OIDs in Disk MIB

27
 Copyright and Disclaimer Notices

Copyright and Disclaimer Notices

Synology Inc.
© 2015-2022 Synology Inc.
All rights reserved.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted,

in any form or by any means, mechanical, electronic, photocopying, recording, or otherwise,
without prior written permission of Synology Inc., with the following exceptions: Any person
is hereby authorized to store documentation on a single computer for personal use only and
to print copies of documentation for personal use provided that the documentation contains
Synology’s copyright notice.

The Synology logo is a trademark of Synology Inc.

No licenses, express or implied, are granted with respect to any of the technology described in
this document. Synology retains all intellectual property rights associated with the technology
described in this document. This document is intended to assist application developers to
develop applications only for Synology-labelled computers.

Every effort has been made to ensure that the information in this document is accurate.
Synology is not responsible for typographical errors.

Synology Inc.
9F., No.1. Yuandong Rd., Banqiao Dist., New Taipei City 220, Taiwann

Synology and the Synology logo are trademarks of Synology Inc., registered in the United
States and other countries.

Marvell is registered trademarks of Marvell Semiconductor, Inc. or its subsidiaries in the United
States and other countries.

Freescale is registered trademarks of Freescale Semiconductor, Inc. or its subsidiaries in the

United States and other countries.

Other products and company names mentioned herein are trademarks of their respective
holders.

28
 Copyright and Disclaimer Notices

Even though Synology has reviewed this document, SYNOLOGY MAKES NO WARRANTY OR
REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS DOCUMENT, ITS
QUALITY, ACCURACY, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. AS A
RESULT, THIS DOCUMENT IS PROVIDED “AS IS,” AND YOU, THE READER, ARE ASSUMING THE
ENTIRE RISK AS TO ITS QUALITY AND ACCURACY. IN NO EVENT WILL SYNOLOGY BE LIABLE FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES RESULTING FROM
ANY DEFECT OR INACCURACY IN THIS DOCUMENT, even if advised of the possibility of such
damages.

THE WARRANTY AND REMEDIES SET FORTH ABOVE ARE EXCLUSIVE AND IN LIEU OF ALL
OTHERS, ORAL OR WRITTEN, EXPRESS OR IMPLIED. No Synology dealer, agent, or employee is
authorized to make any modification, extension, or addition to this warranty.

Some states do not allow the exclusion or limitation of implied warranties or liability for
incidental or consequential damages, so the above limitation or exclusion may not apply to
you. This warranty gives you specific legal rights, and you may also have other rights which
vary from state to state.

29
 Copyright and Disclaimer Notices

SYNOLOGY
INC.
9F, No. 1, Yuandong Rd.
Banqiao Dist., New Taipei City 220545
Taiwan
Tel: +886 2 2955 1814

SYNOLOGY
AMERICA CORP.
3535 Factoria Blvd SE, Suite #200,
Bellevue, WA 98006
USA
Tel: +1 425 818 1587

SYNOLOGY
UK LTD.
Unit 5 Danbury Court, Linford Wood,
Milton Keynes, MK14 6PL
United Kingdom
Tel.: +44 (0)1908048029

SYNOLOGY
FRANCE
102 Terrasse Boieldieu (TOUR W)
92800 Puteaux
France
Tel: +33 147 176288

SYNOLOGY
GMBH
Grafenberger Allee 295
40237 Düsseldorf
Deutschland
Tel: +49 211 9666 9666

SYNOLOGY
SHANGHAI
200070, Room 201,
No. 511 Tianmu W. Rd.,

synology.com Jingan Dist., Shanghai,

China

SYNOLOGY
Synology may make changes to specifications and product descriptions at any time, without notice. Copyright
JAPAN CO., LTD.
© 2022 Synology Inc. All rights reserved. ® Synology and other names of Synology Products are proprietary 4F, No. 3-1-2, Higashikanda,
marks or registered trademarks of Synology Inc. Other products and company names mentioned herein are Chiyoda-ku, Tokyo, 101-0031
trademarks of their respective holders. Japan

30