SNMP MIB Guide

Last updated: Jul 16, 2024

Table of Contents

Introduction
Supported MIB files
Synology MIB files
Synology System MIB (OID: .1.3.6.1.4.1.6574.1)
Synology Disk MIB (OID: .1.3.6.1.4.1.6574.2)
Synology RAID MIB (OID: .1.3.6.1.4.1.6574.3)
Synology UPS MIB (OID: .1.3.6.1.4.1.6574.4)
Synology Smart MIB (OID: .1.3.6.1.4.1.6574.5)
Synology Services MIB (OID: .1.3.6.1.4.1.6574.6)
Synology StorageIO MIB (OID: .1.3.6.1.4.1.6574.101)
Synology SpaceIO MIB (OID: .1.3.6.1.4.1.6574.102)
Synology FlashCache MIB (OID: .1.3.6.1.4.1.6574.103)
Synology iSCSI LUN MIB (OID: .1.3.6.1.4.1.6574.104)
Synology Ebox MIB (OID: .1.3.6.1.4.1.6574.105)
Synology SHA MIB (OID: .1.3.6.1.4.1.6574.106)
Synology NFS MIB (OID: .1.3.6.1.4.1.6574.107)
Synology GPUInfo MIB (OID: .1.3.6.1.4.1.6574.108)
Synology Port MIB (OID: .1.3.6.1.4.1.6574.109)
Synology iSCSI Target MIB (OID: .1.3.6.1.4.1.6574.110)
Synology MailPlus MIB (OID: .1.3.6.1.4.1.6574.201)
Useful OIDs
Monitor Specific OIDs
Import MIB Files
Set up the NMS
Document Revision History
Copyright and Disclaimer Notices

1

2
3
6
7
8
10
12
13
14
15
16
18
19
21
22
24
25
26
27
28
32
36
36
38
40
41

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 tohave experience and knowledge of NMS and SNMP before consulting this document.

2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, andconnected UPS devices. Please see the “Synology MIB Files” section below for more Synology
MIB information.
You can download the Synology MIB file here.

Notes:For all tables in this document, unless otherwise noted, DSM denotes that this OID iscompatible 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 DSMMIBDISMAN-EVENT-MIB
DISMAN-SCHEDULEMIBHOST-RESOURCES-MI
B
IF-MIB
IP-FORWARD-MIB
IP-MIB
IPV6-ICMP-MIB
IPV6-MIB
IPV6-TCP-MIB

3

Explanation
For defining event triggers and actions for network management
purposes
For scheduling SNMP set operations periodically or at specific points
in timeFor use in managing host systems
For describing network interface sub-layers
For the management of CIDR multipath IP Routes
For IP and ICMP management objects
For entities implementing the ICMPv6
For entities implementing the IPv6 protocol
For entities implementing TCP over IPv6

IPV6-UDP-MIB
NET-SNMP-AGENT-MI
B
NET-SNMP-EXTENDMIBNET-SNMP-VACM-MI
B
NOTIFICATION-LOGMIBSNMP-COMMUNITYMIB
SNMP-FRAMEWORKMIB
SNMP-MPD-MIB
SNMP-USER-BASED-S
M-MIB
SNMP-VIEW-BASED-A
CM-MIB
SNMPv2-MIBSYNOLOGY-DISK-MIBSYNOLOGY-EBOX-MI
B
SYNOLOGY-FLASHCA
CHE-MIBSYNOLOGY-GPUINFO-MIBSYNOLOGY-ISCSILUN-MIBSYNOLOGY-ISCSITarg
et-MIBSYNOLOGY-NFS-MIB

4For entities implementing UDP over IPv6
For monitoring structures for the Net-SNMP agent
For scripted extensions for the Net-SNMP agent
Defines Net-SNMP extensions to the standard VACM view table
For logging SNMP Notifications
To help support coexistence between SNMPv1, SNMPv2c, andSNMPv3The SNMP Management Architecture MIB
For Message Processing and Dispatching
For the SNMP User-based Security Model
For the View-based Access Control Model for SNMPFor SNMP entities
For Synology disk information (Synology only)
For Synology ebox information (Synology only)
For Synology FlashCache information (Synology only)
For Synology GpuIO information (Synology only)
For Synology iSCSI LUN information (Synology only)
For Synology iSCSI Target information (Synology only)
For Synology NFS information (Synology only)SYNOLOGY-PORT-MI
B.txt
SYNOLOGY-RAID-MIBSYNOLOGY-SERVICES-MIBSYNOLOGY-SHA-MIBSYNOLOGY-SMART-MIB
SYNOLOGY-SPACEIOMIBSYNOLOGY-STORAGE
IO-MIBSYNOLOGY-SYSTEMMIBSYNOLOGY-UPS-MIBSYNOLOGY-MAILPLU
S-MIB
TCP-MIB
UCD-DISKIO-MIB
UCD-DLMOD-MIB
UCD-SNMP-MIB
UDP-MIB5

For Synology Ethernet Port information (Synology only)
For Synology RAID information (Synology only)
For Synology services information (Synology only)
For Synology High-Availability information (Synology only)
For Synology smart information (Synology only)
For Synology SpaceIO information (Synology only)
For Synology StorageIO information (Synology only)
For Synology system information (Synology only)
For Synology UPS information (Synology only)
For Synology MailPlus Server information (Synology only)
For managing TCP implementations
For disk IO statistics
For dynamic loadable MIB modules
For private UCD SNMP MIB extensions
For managing UDP implementations

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 obtainthe complete Synology OID information.

Table 3-1 OID of Synology MIBs
OID
.1.3.6.1.4.1.6574.1.1.3.6.1.4.1.6574.2.1.3.6.1.4.1.6574.3.1.3.6.1.4.1.6574.4

Name
synoSystem
synoDisk
synoRaid
synoUPS

.1.3.6.1.4.1.6574.5

synologyDiskSMART.1.3.6.1.4.1.6574.6

synologyService.1.3.6.1.4.1.6574.101

storageIO.1.3.6.1.4.1.6574.102

spaceIO.1.3.6.1.4.1.6574.103

flashCache.1.3.6.1.4.1.6574.104

synologyiSCSILUN.1.3.6.1.4.1.6574.105.1.3.6.1.4.1.6574.106.1.3.6.1.4.1.6574.107
6synologyEbox
synologyHA
NFS

File NameSYNOLOGY-SYSTEMMIB.txt
SYNOLOGY-DISK-MIB.txt
SYNOLOGY-RAID-MIB.txt
SYNOLOGY-UPS-MIB.txt
SYNOLOGY-SMARTMIB.txt
SYNOLOGY-SERVICESMIB.
txt
SYNOLOGY-STORAGEIOMIB.txt
SYNOLOGY-SPACEIOMIB.txt
SYNOLOGYFLASHCACHE-MIB.txt
SYNOLOGY-ISCSILUNMIB.txt
SYNOLOGY-EBOX-MIBSYNOLOGY-SHA-MIBSYNOLOGY-NFS-MIB.txt

Last updated
versionDSM 6.0.2
DSM 7.1
DSM 7.0
DSM 6.0.1
DSM 6.0.1
DSM 6.2.1
DSM 6.1.7
DSM 6.0.1
DSM 6.2.2
DSM 6.1.7
DSM 6.2.1
DSM 6.2.2
DSM 7.0

.1.3.6.1.4.1.6574.108

GpuInfo.1.3.6.1.4.1.6574.109

synoEthPort.1.3.6.1.4.1.6574.110

synologyiSCSITarget.1.3.6.1.4.1.6574.201

mailplus

SYNOLOGY-GPUINFOMIB.txt
SYNOLOGY-PORT-MIB.txt
SYNOLOGY-ISCSITargetMIBSYNOLOGY-MAILPLUSMIB.txt

DSM 6.2.2
SRM 1.2.5
DSM 7.0
DSM 7.2

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
OID

Name

.1

systemStat.2

temperatur.3

powerStatu.4.1

systemFan.4.2

cpuFanStat.5.1

modelNam.5.2

serialNumb

us

e

s

.5.3

7

Statususeer
versionType

Status Type
(1)
Integer Normal
Failed (2)String -Explanation
System partition
statusTemperature of thisNAS
Returns error if
power supplies fail
Returns error ifsystem fan fails
Returns error if CPU
fan fails
Model name of thisNAS

String -Model serial number DSM, DSM UC

String -The version of DSM

Integer (1)Integer Normal
Failed (2)(1)
Integer Normal
Failed (2)(1)
Integer Normal
Failed (2)Supported OS
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC

DSM, DSM UC

.5.4

upgradeAv.6controllerN

ailableumber

Available (1)Unavailable (2)(3)
Integer Connecting
Disconnected(4)
Others (5)A (0)Integer Controller
Controller B (1)

Checks whether a
new version or
update of DSM isavailable

DSM, DSM UC

The controller
numberDSM UC

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 thisMIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.2.1.1.3" can beused to get the disk model.

Table 3-3 Disk MIB
OID

diskModel

String String -.4

diskType

String -.5

diskStatus

Integer Normal (1)*Explanation
Used internally for
SNMP table and notaccessible
Disk name in DSM
Disk model
Disk type, e.g. SATA,
SSD
Current disk status

Integer -Disk temperature

.1

Name
diskIndex.2.3

diskID.6

diskTemper
ature

8

Type

Status Type

Integer -Supported OS
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC

.7

diskRole

String data *.8

diskRetry

Integer -.9diskBadSec.10

diskIdentify.11

diskRemain

tor

Fail

Life

.12

diskName.13

diskHealth
StatusInteger Integer Integer String Integer Normal (1)*The role of the disk
in system
The count of eachdisk connection
retries
The count of eachdisk I/O bad sector
The count of eachdisk identify fails
The estimate remain
life of each disk
Disk name which willkeep the same value
in different DSM
versionCurrent disk healthstatusDSM 7.0 andabove
DSM 7.0 andabove
DSM 7.0 andabove
DSM 7.0 andabove
DSM 7.0 andabove
DSM 7.0 andabove
DSM 7.1 andabove

For diskStatus details, see Table 3-4
For diskRole details, see Table 3-5
For diskHealthStatus details, see Table 3-6

Table 3-4 DiskStatus Explanation
StatusNormal (1)Initialized (2)NotInitialized (3)SystemPartitionFailed (4)Crashed (5)Explanation
The disk is functioning normally
The disk has system partitions but nodata
The disk is not partitioned
Partitions on the disk are damaged
The disk is damaged

Table 3-5 DiskRole Explanation9

Supported OS
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC

Statusdata
hotsparessd_cachenone
unknown

Explanation
Used by storage pool
Assigned as a hot spare disk
Used by SSD Cache
Not used by storage pool, nor hot spare,nor SSD Cache
Some error occurredSupported OS
DSM 7.0 and above
DSM 7.0 and above
DSM 7.0 and above
DSM 7.0 and above
DSM 7.0 and above

Table 3-6 diskHealthStatus Explanation
StatusNormal (1)Warning (2)Critical (3)Failing (4)Explanation
The disk health status is normal.
The disk health status is warning.
The disk health status is critical.
The disk health status is failing.

Supported OS
DSM 7.1 and above
DSM 7.1 and above
DSM 7.1 and above
DSM 7.1 and above

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 thisMIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.3.1.1.3" can beused to get the RAID status.

Table 3-7 RAID MIB
OID
.1

Name
raidIndex

10

StatusType

Type
Integer-

Explanation

Supported
OS

Used internally for
SNMP table and notaccessible

DSM, DSMUCThe name of each
RAID in DSM
shows the RAID
.3
Integer
Normal (1)* Itstatus
raidStatusright now
The free size of.4
Counter64 raidFreeSize
volume / disk group
The total size of.5Counter64 raidTotalSize
volume / disk group
Total hotspare disks
count which can.6Integerprotect RAID (smaller
raidHotspareCnt
than 0 means
something wrong)
For RAID status details, see Table 3-8.2

raidName

String-

DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUCDSM 7.0
and above

Table 3-8 RAID Status Explanation
StatusNormal (1)Explanation
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)
Crashed (12)DataScrubbing (13)RaidDeploying (14)RaidUnDeploying (15)RaidMountCache (16)11

Degrade is shown when a tolerable failure of disk(s) occurs
RAID has crashed and is now read-only
RAID is DataScrubbing
RAID is deploying Single volume on pool
RAID is not deploying Single volume on pool
RAID is mounting SSD cacheRAID is not mounting SSD cache

RaidUnmountCache (17)

RAID continue expanding SHR if interrupted

RaidExpandingUnfinishedSHR(18)RAID is converting Single volume on SHR to multiple volume
on SHR
RAID is migrating SHR1 to SHR2
RAID status is not included in the status above

RaidConvertSHRToPool (19)
RaidMigrateSHR1ToSHR2 (20)
RaidUnknownStatus (21)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
.1.1

Name
upsDeviceModel

StatusType

Type

Explanation

String-UPS device model

String-.1.3

upsDeviceSerial

String-UPS device
manufacturer
UPS device serial
number

.2.1

upsInfoStatus

String-UPS device status.2.6.2

upsInfoMfrDate

String

-

Float

-

UPS device
manufacturing date
Load on UPS device(percent)

Float

-

Battery charge.1.2

upsDeviceManuf
acturer.2.12.1

upsInfoLoadValu.3.1.1

upsBatteryCharg

12eeValueSupportedOS
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSM
UC

.3.1.4.3.12

upsBatteryCharg
eWarning

upsBatteryType

Float

-

Battery level atwhich UPS switches
to Warning state(percent)

Float

-

Battery chemistry

DSM, DSMUC
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 thisMIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.5.1.1.3" can beused to get the SMART attribute name.

Table 3-10 SMART MIB
OID

Name

.1

diskSMARTInfoI.2

diskSMARTInfoD.3

diskSMARTAttrN

ndex

evNameame.4

diskSMARTAttrId.5

diskSMARTAttrC.6

diskSMARTAttrW

urrentorst

13

StatusType

Type
Integer-String-String-Integer-

Integer-

Integer-

Explanation
Used internally for
SNMP table and notaccessible
Describes the disk towhich this SMART
info belongs to
The name of the
SMART info attribute,e.g. Raw_
Read_Error_Rate
SMART attribute ID
number
SMART attributecurrent value
SMART attribute
worst value

Supported
OS
DSM
DSM
DSM
DSM
DSM
DSM

.7

diskSMARTAttrT.8

diskSMARTAttrR.9

diskSMARTAttrSt.10

diskSMARTAttrR

hreshold

aw

atus

aw64

Integer-

Integer-String-

SMART attributethreshold value
SMART attribute raw
value
Status of this SMART
info
SMART attributeraw value (64 bit
VER.)

Counter64 -

DSM
DSM
DSM
DSM

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 thisMIB contains the relative table and entry number. For example, ".1.3.6.1.4.1.6574.6.1.1.2" can beused to get the service name.

Table 3-11 Services MIB
OID

Name

Status
Type

Type

.1

serviceInfoIndex

Integer-.2

serviceName

String-.3

serviceUsers

Integer-

Explanation
Used internally for services table
and not accessible
The name of the service
The number of users using thisservice

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" canbe used to get the name of the device that we are counting/checking.
14

Table 3-12 StorageIO MIB
OID

Name

Status
Type

Type

.1

storageIOIndex

Integer-.2

storageIODevice

String-.3

storageIONRead

Counter32 -.4storageIONWrittenCounter32 -.5storageIOReads

Counter32 -.6

storageIOWrites

Counter32 -.7

storageIOLA

Integer-.8

storageIOLA1

Integer-.9

storageIOLA5Integer-.10

storageIOLA15

Integer-

15

Explanation

Supported
OS

Used internally forstorageio table andnot accessible
The name of thedevice we arecounting/checking
The number of bytes
read from this device
since boot (32 bit
VER.)
The number of bytes
written to this device
since boot (32 bit
VER.)
The number of readaccesses from thisdevice since bootThe number of write
accesses to thisdevice since bootDSM, DSMUC

The load of disk (%)

DSM, DSM
UC

The 1-minute
average load of disk(%)
The 5-minute
average load of disk(%)
The-15 minute
average load of disk(%)

DSM, DSMUC

DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC

DSM, DSMUC
DSM, DSM
UC

.11

storageIONRead.12

storageIONWritt.13

storageIODevice

X

enX

SerialThe number of bytes
read from this device
since boot (64 bit
VER.)
The number of bytes
written to this device
since boot (64 bit
VER.)
The serial numberof this device

Counter64 -Counter64 String

DSM, DSMUC
DSM, DSMUCDSM UC

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" canbe used to get the name of the device where this volume is mounted.

Table 3-13 SpaceIO MIB
OID

Name

Status
Type

Type

.1

spaceIOIndex

Integer-.2

spaceIODevice

String-.3

spaceIONRead

Counter32 -.4spaceIONWritten16Counter32 -Explanation

Supported
OS

Used internally forspaceIO table andnot accessible
The name of thedevice this volume
mounted on
The number of bytes
read from thisvolume since boot(32 bit VER.)
The number of bytes
written to thisvolume since boot(32 bit VER.)

DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSM
UC

.5

spaceIOReads

Counter32 -.6

spaceIOWrites

Counter32 -.7

spaceIOLA

Integer-.8

spaceIOLA1

Integer-.9

spaceIOLA5Integer-.10

spaceIOLA15

Integer-.11

spaceIONReadXCounter64 -.12spaceIONWrittenX.13

spaceUUIDCounter64 String-

The number of readaccesses from thisvolume since bootThe number of write
accesses to thisvolume since bootThe load of disk inthe volume (%)
The 1 minute averageload of disk in thevolume (%)
The 5 minute
average load of disk
in the volume (%)
The 15 minute
average load of disk
in the volume (%)
The number of bytes
read from thisvolume since boot(64 bit VER.)
The number of bytes
written to thisvolume since boot(64 bit VER.)
The UUID of thisvolumeDSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUCDSM 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" canbe used to get the name of the SSD on the flashcache that we are counting/checking.
17

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

Table 3-14 FlashCache MIB
OID
.1

Name
flashCacheIndex.2

flashCacheSSDD.3

flashCacheSpace.4

flashCacheRead.5

flashCacheWrite.6

flashCacheDiskR.7

flashCacheDisk.8

flashCacheTotal.9

flashCacheTotal

ev

Dev

Hits

Hits

ead

Write

Read

Write

18

StatusType

Type
Integer-String-String-Counter64 Counter64 Counter64 Counter64 Counter64 Counter64 -Explanation

Supported
OS

Reference index foreach observed
deviceThe SSD devicename on flashcache
we are counting/checking
The space devicename on flashcache
we are counting/checking
The number of reads
on flashcache
The number of writes
on flashcache
The number of reads
on disk
The number of writes
on disk
The number of reads
on volume withflashcache
The number of writes
on volume withflashcache

DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSM
UC.10

flashCacheRead.11

flashCacheWrite.12

flashCacheRead.13

flashCacheWrite.14

flashCacheWrite.15

flashCacheSsdU

HitRate

HitRateSeqSkip

SeqSkip

MissSsd

uid

Integer-

Integer-

The read hit rate of
flashcache (%)
The write hit rate of
flashcache (%)
The number ofskipped sequential
reads on flashcache
The number ofskipped sequential
writes on flashcache
The number of data
writes to SSD for the
first time
The SSD UUID on
flashcache we arecounting/checking

Counter64 Counter64 Counter64 String-

DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSM
UC

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 readthroughput 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" canbe used to get the iSCSI LUN uuid.

Table 3-15 iSCSI LUN MIB
OID
.1

Name
iSCSILUNInfoInd
ex

19

StatusType

Type
Integer-

Explanation

SupportedOS

Used
internally for iSCSI
LUN table and notaccessible

DSM, DSM
UC.2

iSCSILUNUUIDString-

LUN uuid.3

iSCSILUNName

String-

LUN name.4

iSCSILUNThroug.5

iSCSILUNThroug.6

iSCSILUNThroug.7

iSCSILUNThroug.8

iSCSILUNIopsRe.9

iSCSILUNIopsWr.10

iSCSILUNDiskLat.11

iSCSILUNDiskLat.12

iSCSILUNNetwor.13

iSCSILUNNetwor.14

iSCSILUNIoSizeR.15

iSCSILUNIoSize.16

iSCSILUNQueue

hputReadHigh

hputReadLow

hputWriteHigh

hputWriteLow

ad

ite

encyReadencyWrite

kLatencyTx

kLatencyRx

ead

Write

Depth

20

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

Integer-

The higher
32 bit of readthroughput
The lower 32 bit ofread throughput
The higher 32 bit ofwrite throughput
The lower 32 bit ofwrite throughput

DSM, DSMUC
DSM, DSMUC
DSM, DSMUC

DSM, DSMUC
DSM, DSMUC
DSM, DSMUC
DSM, DSM
LUN read iops
UC
DSM, DSM
LUN write iops
UC
LUN read disk
DSM, DSM
latencyUC
LUN write disk
DSM, DSM
latencyUC
LUN network tx
DSM, DSM
latencyUC
LUN network rx
DSM, DSM
latencyUC
LUN read average i/o DSM, DSM
sizeUC
LUN write average DSM, DSM
i/o sizeUC
Number of iSCSI
DSM
commands in LUN DSM,
UC
queue

.17

iSCSILUNType.18

iSCSILUNDiskLat
encyAvg
iSCSILUNThinPr.19

ovisionVolFreeM

String-Integer-

Integer-

LUN type(advanced lun, block
lun, etc.)
Average latency of
LUN disk
Free space(MB) of
thin provisioning
lun's volume

Bs

DSM, DSMUCDSM 7.0
and above
DSM 7.0
and above

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" canbe used to get the expansion unit model.

Table 3-16 Ebox MIB
OID
.1
.2
.3

Name

Type

StatusType

Explanation

Expansion unit Index
Expansion unit model
eboxModel
Normal (1)* Power status of expansion unit
eboxPower
Redundant power status of
expansion unit (if the ebox has no
eboxRedundant.4
Integer
Normal(1)*
redundant power interface, this OID
Powerwill not appear)
For eboxPower and eboxRedundantPower details, see Table 3-17
eboxIndex

IntegerStringIntegerTable 3-17 Ebox Power and Redundant Power Status Explanation
StatusNormal (1)21Explanation
The power supplies well

Poor (2)Disconnection (3)The power supplies badly
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 andheartbeat status.

Table 3-18 SHA MIB
OID

Name

.1

activeNodeNam.2

passiveNodeNa.3clusterAutoFailo

e

me

ver

StatusType

Type
String-String-Integertrue (1)false (2).4clusterName

String-.5clusterStatus

Integer*.6

heartbeatStatus

Integer*.7

heartbeatTxRate

Integer-

Integer-.8heartbeatLatency

For clusterStatus details, see Table 3-19
For heartbeatStatus details, see Table 3-20
22

Explanation
Hostname of active
serverHostname of passive
serverWhether cluster can
failover once
something went
wrong
Hostname of HighAvailability cluster
Status of HighAvailability cluster
Status of heartbeat
connection
Transfer speed ofheartbeat in kilobyte-per-second
Heartbeat latency inmicroseconds (10^-6seconds)

Supported
OS
DSM
DSM
DSM
DSM
DSM
DSM
DSM
DSM

Table 3-19 Cluster Status Explanation
Statusnormal (0)warning (1)critical (2)upgrading (3)processing (4)Explanation
Supported OS
The High-Availability cluster is healthy DSM
The High-Availability cluster has
something went wrong. Action should betaken to resume High-Availability feature. DSM
Please refer to High-Availability Manager
for more details.
The High-Availability cluster is in danger,
and should be resolved as soon as
possible.
DSM
Please refer to High-Availability
Manager for more details.
The High-Availability cluster is
DSM
upgrading.
The High-Availability cluster isDSM
undergoing some operation.

Table 3-20 Heartbeat Status Explanation
Statusnormal (0)abnormal (1)disconnected (2)empty (3)Explanation
The heartbeat connection is normal.
Some information about heartbeat is notavailable.
The High-Availability cluster loses
connection to passive server throughheartbeat interface, or it is currently in
split-brain mode.
The High-Availability cluster has no
passive server.

Supported OS
DSM
DSM
DSM
DSM

Synology NFS MIB (OID: .1.3.6.1.4.1.6574.107)
23

The Synology NFS MIB monitors the maximum latency and operations of NFS. Every value will becached for 3 seconds. Therefore, if you access a value twice within 3 seconds, you will get thesame value. The maximum latency will always clear the cache and recount the value once thevalue 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" canbe used to get the name of NFS.

Table 3-21 NFS MIB
OID

Name

StatusType

Type

Explanation

SupportedOS
DSM 7.0
and above.1

nfsIndex

Integer-

Used internally for
NFS table and notaccessible.2

nfsNameString-

The name of NFS

DSM 7.0
and above

Maximum latency of
all the NFS
operations
Maximum latency of
the NFS read
operations
Maximum latency of
the NFS write
operations
Accumulated countsof all the NFS
operations
Accumulated countsof the NFS read
operations
Accumulated countsof the NFS write
operations

DSM 7.0
and above.3

nfsTotalMaxLate.4

nfsReadMaxLate.5

nfsWriteMaxLat

ncy

ncy

ency

Integer-

Integer-

Integer-.6

nfsTotalOPSCounter64 -.7

nfsReadOPSCounter64 -.8

nfsWriteOPSCounter64 -24

DSM 7.0
and above
DSM 7.0
and above
DSM 7.0
and above
DSM 7.0
and above
DSM 7.0
and above

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.

Notes: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
.1

Name
gpuInfoSupported.2

gpuUtilization.3

gpuMemoryUtili.4

gpuMemoryFre.5

gpuMemoryUse.6

gpuMemoryTot

zation

e

d

al

Type
Integer

Integer

Integer
Integer
Integer
Integer

Status Type

Explanation

Supported(0)
Unsupported Supported GPU(1)
The percentage of
GPU time spent on
processing user
space in last 1
secondThe percentage ofGPU memory usage
in last 1 second
The amount of
currently free GPU
memory in kb
The amount of
currently used GPU
memory in kb
The total physicalGPU memory size

Synology Port MIB (OID: .1.3.6.1.4.1.6574.109)
25

Supported
OS
DSM

DSM

DSM
DSM
DSM
DSM

The Synology Port MIB defines the status of each Ethernet port, such as link status and linkspeed, 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" canbe used to get the link status of the Ethernet port.

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

Table 3-23 Port MIB
OID
.1

Name
ethPortIndex.2

ethPortStatus.3

ethPortSpeed

StatusType

Type

Explanation

SupportedOS
SRM 1.2.5
and above

Integer32-

Used internally for
SNMP table and notaccessible

Integer

unknown(1)
up (2)
down (3)The link status of the SRM 1.2.5
Ethernet port
and above-

The link speed of the
Ethernet port in units SRM 1.2.5
of 1,000,000 bits per and above
secondGauge32

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" canbe used to get the iSCSI target name.

Table 3-24 iSCSI Target MIB
26

OID

Name

.1

iSCSITargetInfoI.2

iSCSITargetNam

ndex

e

.3

iSCSITargetIQN.4iSCSITargetConn
ectionStatus

StatusType

Type
Integer32-

String-String-String-

Explanation

Supported
OS

Used internally for
SNMP table and notaccessible
Name of the iSCSI
targetIQN of the iSCSI
targetConnection status of
the iSCSI target

DSM 7.0
and above
DSM 7.0
and above
DSM 7.0
and above
DSM 7.0
and above

Synology MailPlus MIB (OID: .1.3.6.1.4.1.6574.201)

The Synology MailPlus MIB monitors mail-related information, including mail delivery results,
threat events, mail queue, IMAP, POP3, SMTP connections, and service status. In a MailPlus highavailability (HA) setup, delivery (.1.3.6.1.4.1.6574.201.1) and threat (.1.3.6.1.4.1.6574.201.2) numbers
are taken from the primary server’s transaction log and include data from both servers. By default,
the secondary server does not record transaction logs but relies on log transfers from the primaryserver.
While delivery and threat data reflect activities on both servers, the mail queue, IMAP, POP3,
SMTP connections, and service status (.1.3.6.1.4.1.6574.201.3 - .1.3.6.1.4.1.6574.201.6) numbers are
based solely on the local server’s activities.

Table 3-25 MailPlus MIB
OID

Name

Status
Type

Type

.1.1

deliverySent

Integer-.1.2

deliveryReceived

Integer-

27

Explanation
The number of
emails sent in thepast 10 minutes on
MailPlus Server
The number of
emails received in
the past 10 minutes
on MailPlus Server

SupportedOS
DSM 7.2
and above
DSM 7.2
and above.1.3

deliveryBounce

Integer-.1.4

deliveryDeferred

Integer-.1.5

deliveryExpired

Integer-

Integer-

Integer-

Integer-.1.6

deliveryForward.1.7

deliveryDeletedI.2.1

threatDataProteed

nQueue

ction

.2.2

threatDmarc

Integer-.2.3

threatSpf

Integer-28

The number of
emails bounced in
the past 10 minutes
on MailPlus Server
The number of
emails deferred in
the past 10 minutes
on MailPlus Server
The number of
emails expired in thepast 10 minutes on
MailPlus Server
The number of
emails forwarded in
the past 10 minutes
on MailPlus Server
The number of
emails deleted fromthe queue in the past
10 minutes on
MailPlus Server
The number of MCP(Message Content
Protection) incidents
occurred on MailPlus
Server in the past 10
minutes
The number of
DMARC incidents
occurred on MailPlus
Server in the past 10
minutes
The number of SPF
incidents occurredon MailPlus Server inthe past 10 minutes

DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above

DSM 7.2
and above

DSM 7.2
and above
DSM 7.2
and above.2.4

threatSpam

Integer-.2.5

threatDnsbl

Integer-.2.6

threatDkim

Integer-

Integer-

Integer-.2.7

threatMalicious.2.8

threatAttachme

Content

ntFilter.2.9

threatVirus

Integer-.2.10

threatsBlocklist

Integer-.3.1

queueMaildrop

Integer-.3.2

queueActive

Integer-29

The number of spamincidents occurredon MailPlus Server inthe past 10 minutes
The number of
DNSBL incidents
occurred on MailPlus
Server in the past 10
minutes
The number of DKIM
incidents occurredon MailPlus Server inthe past 10 minutes
The number ofmalicious content
incidents occurredon MailPlus Server inthe past 10 minutes
The number ofattachment filter
incidents occurredon MailPlus Server inthe past 10 minutes
The number of virus
incidents occurredon MailPlus Server inthe past 10 minutes
The number of block
list incidents
occurred on MailPlus
Server in the past 10
minutes
The number of
emails in the
maildrop queue
The number of
emails in the activequeue

DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above

DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above

The number of.3.3 queueIncoming Integer
emails in theincoming queue
The number of.3.4 queueDeferred Integer
emails in thedeferred queue.
The number of.3.5 queueHold
Integeremails in the holdqueue
The number of.4.1
IntegerconnectionImap
connections via IMAPThe number of.4.2 connectionPop3 Integer
connections via
POP3
The number of.5.1
Integer
inbound SMTP
smtpInboundconnections
The number of.5.2 smtpOutbound Integer
outbound SMTP
connections
Running
The status of Postfix.6.1
Integer
servicePostfix(0)*
service
Running
The status of.6.2 serviceDovecot Integer(0)*
Dovecot service
For servicePostfix and serviceDovecot details, see Table 3-26

DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above
DSM 7.2
and above

Table 3-26 Postfix Service and Dovecot Service Status Explanation
StatusRunning (0)Abnormal (1)Dead PID File (2)30Explanation
The service is up and running as expected.
The service is currently inactive and not running.
Although the service is not running, a PID (Process ID) file exists,indicating a possible issue with the service's startup or termination
process.

Port Not Listening (3)Unknown (6)31The service is running, but its utilized ports are not actively listening
for connections.
The status of the service cannot be definitively determined. It may beinactive when it should be running or active when it should be inactive.

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 usefuldevice’s data easily.

Table 4-1 CPU-Related OID
OID

Name

.1.3.6.1.4.1.2021.10.1.5.1

laLoadInt.1.1.3.6.1.4.1.2021.10.1.5.2

laLoadInt.2.1.3.6.1.4.1.2021.10.1.5.3

laLoadInt.3.1.3.6.1.4.1.2021.11.9.0

ssCpuUser.1.3.6.1.4.1.2021.11.10.0

ssCpuSystem.1.3.6.1.4.1.2021.11.11.0

ssCpuIdle

Explanation
System load average
within the last 1 minute
System load average
within the last 5 minutes
System load average
within the last 15 minutes
The percentage of CPU
time spent processinguser-level code
The percentage of CPU
time spent processing
system- level code,
calculated over the lastminuteThe percentage ofprocessor time spent idle,
calculated over the lastminuteSupported OS
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC

DSM, DSM UC

DSM, DSM UC

Table 4-2 Memory-Related OID
OID.1.3.6.1.4.1.2021.4.3.0
32

Name
memTotalSwap

Explanation
Supported OS
The total amount of swap
space configured for this DSM, DSM UC
host.1.3.6.1.4.1.2021.4.4.0

memAvailSwap.1.3.6.1.4.1.2021.4.5.0

memTotalReal.1.3.6.1.4.1.2021.4.6.0

memAvailReal.1.3.6.1.4.1.2021.4.11.0

memTotalFree.1.3.6.1.4.1.2021.4.13.0

memShared.1.3.6.1.4.1.2021.4.14.0

memBuffer.1.3.6.1.4.1.2021.4.15.0

memCached

The amount of swap
space currently unused oravailable
The total amount of real/
physical memory
The amount of
real/physical memory
currently unused oravailable
The total amount ofmemory free or available
for use on this host (Thisvalue typically covers
both real memory andswap space or virtual
memory.)The total amount of realor virtual memory
currently allocated for use
as shared memory
The total amount of realor virtual memory
currently allocated for use
as memory buffers
The total amount of realor virtual memory
currently allocated for use
as cached memory

DSM, DSM UC
DSM, DSM UC
DSM, DSM UC

DSM, DSM UC

DSM, DSM UC

DSM, DSM UC

DSM, DSM UC

Table 4-3 Network-Related OID
OID

Name

.1.3.6.1.2.1.31.1.1.1.1

ifName.1.3.6.1.2.1.31.1.1.1.6

ifHCInOctets

33

Explanation
The textual name of theinterface
The total number ofoctets received on theinterface

Supported OS
DSM, DSM UC
DSM, DSM UC

.1.3.6.1.2.1.31.1.1.1.10

ifHCOutOctets

The total number ofoctets transmitted out of
the interface

DSM, DSM UC

Table 4-4 Disk-Related OID
OID.1.3.6.1.2.1.25.2.3.1.3.1.3.6.1.2.1.25.2.3.1.4

Name
hrStorageDescr

hrStorageAllocatio
nUnits

.1.3.6.1.2.1.25.2.3.1.5

hrStorageSize.1.3.6.1.2.1.25.2.3.1.6

hrStorageUsed.1.3.6.1.4.1.2021.13.15.1.1.2

diskIODevice.1.3.6.1.4.1.2021.13.15.1.1.12

diskIONReadX.1.3.6.1.4.1.2021.13.15.1.1.13

diskIONWrittenX.1.3.6.1.4.1.6574.2

synoDisk

Explanation
A description of the typeand instance of thestorage described by thisentry
The size, in bytes, of thedata objects allocatedfrom this pool
The size of the storage
represented by this entry,
in units of
hrStorageAllocationUnits
The amount of thestorage represented bythis entry
The name of the device
we are counting/checking
The number of bytes readfrom this device sinceboot
The number of bytes
written to this device
since bootFor Synology disk
information (Synology
only)

Supported OS
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC
DSM, DSM UC

Table 4-5 System-Related OID
OID
34

Name

Explanation

Supported OS

.1.3.6.1.4.1.6574.1

synoSystem

For Synology system
information (Synology
only)

DSM, DSM UC

Table 4-6 RAID-Related OID
OID.1.3.6.1.4.1.6574.3

Name
synoRaid

Explanation
For Synology RAID
information (Synology
only)

Supported OS
DSM, DSM UC

Table 4-7 UPS-Related OID
OID.1.3.6.1.4.1.6574.4

35

Name
synoUPS

Explanation
For Synology UPS
information (Synology
only)

Supported OS
DSM, DSM UC

Monitor Specific OIDs
In any NMS, particular MIB files are needed in order to capture data through SNMP. Users need toimport 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 mayvary, 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 FilesAs 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 loadthem individually.

36

a. If the import is successful, a window should appear.

b. Detailed information on MIB is shown as follows.

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.

37

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 andfocuses 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.

38

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

5. Select items for monitoring.

39Document Revision History
This table describes the revisions made to Synology servers MIB Guide.

Table 6-1 Document Revision History
MIB
2012-07-19
2013-10-29
2013-11-04
2016-10-31
2018-06-30
2018-12-18
2018-12-24
2020-01-10
2021-02-23
2021-05-25
2022-04-19
2024-07-16

40

Explanation
Document created
Modified OID name and added UPS MIB
Added more MIBs and useful OID
Added more MIBs
Added Ebox MIB
Added useful OIDs in RAID MIB
Added GPUInfo MIB
Added FlashCache MIB
Added SHA MIB
Added information for Synology Unified Controller and eGPUMIB
Added PORT MIB for SRM
Added NFS MIB and iSCSI Target MIB
Added useful OIDs in Disk MIB
Added Synology MailPlus MIB

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 inthis document. Synology retains all intellectual property rights associated with the technology
described in this document. This document is intended to assist application developers todevelop 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 Statesand other countries.
Marvell is registered trademarks of Marvell Semiconductor, Inc. or its subsidiaries in the UnitedStates 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.
Even though Synology has reviewed this document, SYNOLOGY MAKES NO WARRANTY OR
REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH RESPECT TO THIS DOCUMENT, ITSQUALITY, 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 RESULTINGFROM ANY DEFECT OR INACCURACY IN THIS DOCUMENT, even if advised of the possibility ofsuch damages.
41

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 isauthorized 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.

42