ASUSTOR - Website Management

Date:

Topic_id:

Subject:

Description:

content:

<h4>COURSE OBJECTIVES</h4>
Upon completion of this course you should be able to:
<ol>
<li>Know the basics of ASUSTOR NAS SNMP MIB files.</li>
<li>Use PRTG to monitor ASUSTOR NAS status.</li>
</ol>
 
<h4>PREREQUISITES</h4>
Course Prerequisites:
None
Students are expected to have a working knowledge of:
SNMP, NMS
 
<h4>OUTLINE</h4>
<a href="#mib1">1. Introduction</a>
<a href="#mib2">2. Requirements</a>
<a href="#mib3">3. Supported MIB files</a>
<a href="#mib4">4. ASUSTOR MIB files</a>
<a href="#mib41">4.1 ASUSTOR SYSTEM MIB</a>
<a href="#mib42">4.2 ASUSTOR DISK MIB</a>
<a href="#mib43">4.3 ASUSTOR UPS MIB</a>
<a href="#mib5">5. Monitor specific OIDs</a>
<a href="#mib51">5.1 Import MIB file</a>
<a href="#mib52">5.2 Setup the NMS</a>
 <hr /> 
<h4><a name="mib1"></a>1. Introduction</h4>
ASUSTOR Data Master (ADM) supports SNMP (Simple Network Management Protocol). Network administrators can use any SNMP-based NMS (Network Management System) to monitor the status of ASUSTOR NAS. With SNMP trap capability provided, ASUSTOR NAS can send notification to NMS actively when the pre-defined levels of events occur.
A SNMP MIB (Management Information Base) is a hierarchy of information used to define managed objects in a network device. This document introduces the supported MIB files on ASUSTOR ADM, while also describing how OIDs (Object Identifiers) in ASUSTOR MIBs are used. Users are encouraged to have experience and knowledge of NMS and SNMP prior to consulting this document.
 
<h4><a name="mib2"></a>2. Requirements</h4>
<ul>
<li>ASUSTOR NAS with ADM 3.5.0 or later</li>
<li>A SNMP-based NMS</li>
</ul>
 
<h4><a name="mib3"></a>3. Supported MIB files</h4>
There are two types of MIB files supported on ASUSTOR ADM: standard and ASUSTOR-specific. The table below shows all the MIBs supported by ASUSTOR ADM.
 
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="width: 36%; background: SteelBlue; color: white;">Standard MIB</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>DISMAN-EVENT-MIB</td>
<td>For defining event triggers and actions for network management purposes</td>
</tr>
<tr>
<td>DISMAN-SCHEDULE-MIB</td>
<td>For scheduling SNMP set operations periodically or at specific points in time</td>
</tr>
<tr>
<td>HOST-RESOURCES-MIB</td>
<td>For use in managing host systems</td>
</tr>
<tr>
<td>IF-MIB</td>
<td>For describing network interface sub-layers</td>
</tr>
<tr>
<td>IP-FORWARD-MIB</td>
<td>For the management of CIDR multipath IP Routes</td>
</tr>
<tr>
<td>IP-MIB</td>
<td>For IP and ICMP management objects</td>
</tr>
<tr>
<td>IPV6-ICMP-MIB</td>
<td>For entities implementing the ICMPv6</td>
</tr>
<tr>
<td>IPV6-MIB</td>
<td>For entities implementing the IPv6 protocol</td>
</tr>
<tr>
<td>IPV6-TCP-MIB</td>
<td>For entities implementing TCP over IPv6</td>
</tr>
<tr>
<td>IPV6-UDP-MIB</td>
<td>For entities implementing UDP over IPv6</td>
</tr>
<tr>
<td>NET-SNMP-AGENT-MIB</td>
<td>For monitoring structures for the Net-SNMP agent</td>
</tr>
<tr>
<td>NET-SNMP-EXTEND-MIB</td>
<td>For scripted extensions for the Net-SNMP agent</td>
</tr>
<tr>
<td>NET-SNMP-VACM-MIB</td>
<td>Defines Net-SNMP extensions to the standard VACM view table</td>
</tr>
<tr>
<td>NOTIFICATION-LOG-MIB</td>
<td>For logging SNMP Notifications</td>
</tr>
<tr>
<td>SNMP-COMMUNITY-MIB</td>
<td>To help support coexistence between SNMPv1, SNMPv2c, and SNMPv3</td>
</tr>
<tr>
<td>SNMP-FRAMEWORK-MIB</td>
<td>The SNMP Management Architecture MIB</td>
</tr>
<tr>
<td>SNMP-MPD-MIB</td>
<td>For Message Processing and Dispatching</td>
</tr>
<tr>
<td>SNMP-USER-BASED-SM-MIB</td>
<td>For the SNMP User-based Security Model</td>
</tr>
<tr>
<td>SNMP-VIEW-BASED-ACM-MIB</td>
<td>For the View-based Access Control Model for SNMP</td>
</tr>
<tr>
<td>SNMPv2-MIB</td>
<td>For SNMP entities</td>
</tr>
<tr>
<td>TCP-MIB</td>
<td>For managing TCP implementations</td>
</tr>
<tr>
<td>UCD-DISKIO-MIB</td>
<td>For disk IO statistics</td>
</tr>
<tr>
<td>UCD-DLMOD-MIB</td>
<td>For dynamic loadable MIB modules</td>
</tr>
<tr>
<td>UCD-SNMP-MIB</td>
<td>For private UCD SNMP MIB extensions</td>
</tr>
<tr>
<td>UDP-MIB</td>
<td>For managing UDP implementations</td>
</tr>
<tr>
<th style="width: 36%; background: SteelBlue; color: white;">ASUSTOR-specific MIB</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>ASUSTOR-SYSTEM-MIB</td>
<td>For ASUSTOR system information</td>
</tr>
<tr>
<td>ASUSTOR-DISK-MIB</td>
<td>For ASUSTOR disk information</td>
</tr>
<tr>
<td>ASUSTOR-UPS-MIB</td>
<td>For ASUSTOR UPS information</td>
</tr>
</tbody>
</table>
 
Depending on the vendor, many standard MIBs are delivered with the NMS software. You can also download the standard MIBs from the IETF website, <a href="http://www.ietf.org/" target="_blank" rel="noopener">www.ietf.org</a>, and compile them into your NMS, if necessary. The OIDs of standard SNMP MIB files will not be explained in this document.
 
<h4><a name="mib4"></a>4. ASUSTOR MIB files</h4>
ASUSTOR MIB files can provide specific data about a ASUSTOR NAS's system, disks, and connected UPS. To obtain the ASUSTOR MIB files, please go to ADM [Services] [SNMP] and click on the hyperlink to download.
 
<img src="https://www.asustor.com/images/tinymce/upload_img_20220715141255_ADM_service_SNMP.png" alt="" title="" align="" width="880" height="528" />
 
ADM provides 3 ASUSTOR MIB files. Please check table below for details:
 
<table class="table table-striped" border="1" style="width: 80%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="width: 30%; background: SteelBlue; color: white;">File Name</th>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Group</th>
</tr>
<tr>
<td rowspan="3">ASUSTOR-SYSTEM-MIB</td>
<td>.1.3.6.1.4.1.44738.1</td>
<td>ASUSTOR system</td>
</tr>
<tr>
<td>.1.3.6.1.4.1.44738.2</td>
<td>ASUSTOR hardware</td>
</tr>
<tr>
<td>.1.3.6.1.4.1.44738.3</td>
<td>net</td>
</tr>
<tr>
<td rowspan="2">ASUSTOR-DISK-MIB</td>
<td>.1.3.6.1.4.1.44738.4</td>
<td>disk</td>
</tr>
<tr>
<td>.1.3.6.1.4.1.44738.5</td>
<td>volume</td>
</tr>
<tr>
<td>ASUSTOR-UPS-MIB</td>
<td>.1.3.6.1.4.1.44738.6</td>
<td>ASUSTOR ups</td>
</tr>
</tbody>
</table>
 
These MIB files are the child-nodes of OID 1.3.6.1.4.44738. Please note that the MIB files are mutually dependent. You have to import all of them together to your NMS first, and then you can monitor any of the items on NMS.
 
<a name="mib41"></a>4.1 ASUSTOR SYSTEM MIB
The ASUSTOR System MIB displays all system statuses, including CPU, fan, and network status. Users can monitor this MIB for system operation. The tables below show information provided in the System MIB.
<ul>
<li>The child-nodes of ASUSTOR system group (.1.3.6.1.4.1.44738.1)</li>
</ul>
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Name</th>
<th style="background: SteelBlue; color: white;">Type</th>
<th style="background: SteelBlue; color: white;">Status</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>.1.0</td>
<td>sysSerialNumber</td>
<td>String</td>
<td>-</td>
<td>The serial number of this NAS</td>
</tr>
<tr>
<td>.2.0</td>
<td>sysADMVersion</td>
<td>String</td>
<td>-</td>
<td>The ADM version of this NAS</td>
</tr>
<tr>
<td>.3.0</td>
<td>sysBiosVersion</td>
<td>String</td>
<td>-</td>
<td>The BIOS version of this NAS</td>
</tr>
<tr>
<td>.4.0</td>
<td>sysUptime</td>
<td>String</td>
<td>-</td>
<td>The uptime of this NAS</td>
</tr>
<tr>
<td>.5.0</td>
<td>sysTime</td>
<td>String</td>
<td>-</td>
<td>The current time of this NAS</td>
</tr>
<tr>
<td>.6.0</td>
<td>sysTimeZone</td>
<td>String</td>
<td>-</td>
<td>The time zone of this NAS</td>
</tr>
<tr>
<td>.7.0</td>
<td>sysUpgradeAvailable</td>
<td>String</td>
<td>Available Unavailable</td>
<td>Checks whether there is a newer ADM for upgrade</td>
</tr>
<tr>
<td>.8.0</td>
<td>sysAsustorID</td>
<td>String</td>
<td>-</td>
<td>The ASUSTOR ID of this NAS</td>
</tr>
</tbody>
</table>
 
<ul>
<li>The child-nodes of ASUSTOR hardware group (.1.3.6.1.4.1.44738.2)</li>
</ul>
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Name</th>
<th style="background: SteelBlue; color: white;">Type</th>
<th style="background: SteelBlue; color: white;">Status</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>.1.0</td>
<td>hwModelName</td>
<td>String</td>
<td>-</td>
<td>The model name of this NAS</td>
</tr>
<tr>
<td>.2.0</td>
<td>hwProcessor</td>
<td>String</td>
<td>-</td>
<td>The model name of the CPU</td>
</tr>
<tr>
<td>.5.0</td>
<td>hwCPUTemperature</td>
<td>Integer</td>
<td>-</td>
<td>The CPU temperature in Celsius degree</td>
</tr>
<tr>
<td>.6.0</td>
<td>hwSysTemperature</td>
<td>Integer</td>
<td>-</td>
<td>The system temperature in Celsius degree</td>
</tr>
<tr>
<td>.7.0</td>
<td>hwTotalMem</td>
<td>Integer</td>
<td>-</td>
<td>The system total memory capacity in megabyte (MB)</td>
</tr>
<tr>
<td>.8.0</td>
<td>hwFreeMem</td>
<td>Integer</td>
<td>-</td>
<td>The system free memory capacity in megabyte (MB)</td>
</tr>
<tr>
<td>.9.0</td>
<td>hwFreeMemPercentage</td>
<td>Integer</td>
<td>-</td>
<td>The percentage of the system free memory</td>
</tr>
<tr>
<td>.3.1.1</td>
<td>cpuIndex</td>
<td>Integer</td>
<td>-</td>
<td>Used internally for SNMP table and non-accessible</td>
</tr>
<tr>
<td>.3.1.2</td>
<td>cpuUsage</td>
<td>Integer</td>
<td>-</td>
<td>The percentage of CPU usage</td>
</tr>
<tr>
<td>.4.1.1</td>
<td>fanIndex</td>
<td>Integer</td>
<td>-</td>
<td>Used internally for SNMP table and non-accessible</td>
</tr>
<tr>
<td>.4.1.2</td>
<td>fanSpeed</td>
<td>Integer</td>
<td>-</td>
<td>The fan speed in RPM</td>
</tr>
</tbody>
</table>
 
<ul>
<li>The child-nodes of net group (.1.3.6.1.4.1.44738.3)</li>
</ul>
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Name</th>
<th style="background: SteelBlue; color: white;">Type</th>
<th style="background: SteelBlue; color: white;">Status</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>.1.1.1</td>
<td>netIndex</td>
<td>Integer</td>
<td>-</td>
<td>Used internally for SNMP table and non-accessible</td>
</tr>
<tr>
<td>.1.1.2</td>
<td>netInterface</td>
<td>Integer</td>
<td>-</td>
<td>The network interface</td>
</tr>
<tr>
<td>.1.1.3</td>
<td>netMacAddress</td>
<td>String</td>
<td>-</td>
<td>The MAC address of the network interface</td>
</tr>
<tr>
<td>.1.1.4</td>
<td>netIPv4Address</td>
<td>String</td>
<td>-</td>
<td>The IPv4 address of the network interface</td>
</tr>
<tr>
<td>.1.1.5</td>
<td>netIPv6Address</td>
<td>String</td>
<td>-</td>
<td>The IPv6 address of the network interface</td>
</tr>
<tr>
<td>.1.1.6</td>
<td>netPacketSent</td>
<td>Integer</td>
<td>-</td>
<td>The outgoing packets in kilobyte (KB)</td>
</tr>
<tr>
<td>.1.1.7</td>
<td>netPacketReceived</td>
<td>Integer</td>
<td>-</td>
<td>The incoming packets in kilobyte (KB)</td>
</tr>
</tbody>
</table>
 
<a name="mib42"></a>4.2 ASUSTOR DISK MIB
The ASUSTOR Disk MIB contains two tables for disk and volume respectively. As such, the tables can increase or decrease in size when disks or volumes are added or removed. For example, if a disk is inserted, an additional row containing relevant information will emerge. The OIDs DiskIndex and VolumeIndex are reserved for indexes of table rows and cannot be accessed. The tables below describe information provided in the Disk MIB.
 
<ul>
<li>The child-nodes of disk group (.1.3.6.1.4.1.44738.4)</li>
</ul>
ADM 5.1.0:
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Name</th>
<th style="background: SteelBlue; color: white;">Type</th>
<th style="background: SteelBlue; color: white;">Status</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>.1.1.1</td>
<td>diskIndex</td>
<td>Integer</td>
<td>-</td>
<td>Used internally for SNMP table and non-accessible</td>
</tr>
<tr>
<td>.1.1.2</td>
<td>diskID</td>
<td>String</td>
<td>-</td>
<td>The ID of the disk bay</td>
</tr>
<tr>
<td>.1.1.3</td>
<td>diskModel</td>
<td>String</td>
<td>-</td>
<td>The disk model name</td>
</tr>
<tr>
<td>.1.1.4</td>
<td>diskType</td>
<td>String</td>
<td>SATA M.2</td>
<td>The disk type</td>
</tr>
<tr>
<td>.1.1.5</td>
<td>diskStatus</td>
<td>String</td>
<td>Good Idle Abnormal</td>
<td>The status of the disk</td>
</tr>
<tr>
<td>.1.1.6</td>
<td>diskSmartStatus</td>
<td>String</td>
<td>Healthy Normal Risky Dangerous Bad</td>
<td>The S.M.A.R.T status of the disk</td>
</tr>
<tr>
<td>.1.1.7</td>
<td>diskTemperature</td>
<td>Integer</td>
<td>-</td>
<td>The disk temperature in Celsius degree</td>
</tr>
<tr>
<td>.1.1.8</td>
<td>diskSize</td>
<td>Integer</td>
<td>-</td>
<td>The disk size in gigabyte (GB)</td>
</tr>
</tbody>
</table>
 
<div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
<div class="panel panel-default">
<div class="panel-heading" role="tab" id="heading1">
<h4 class="panel-title"><a role="button" data-toggle="collapse" data-parent="#accordion" href="#collapse1" aria-expanded="true" aria-controls="collapse1"> ADM 4.0 ~ ADM 5.0:</a></h4>
</div>
<div id="collapse1" class="panel-collapse collapse" role="tabpanel" aria-labelledby="heading1">
<div class="panel-body">
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Name</th>
<th style="background: SteelBlue; color: white;">Type</th>
<th style="background: SteelBlue; color: white;">Status</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>.1.1.1</td>
<td>diskIndex</td>
<td>Integer</td>
<td>-</td>
<td>Used internally for SNMP table and non-accessible</td>
</tr>
<tr>
<td>.1.1.2</td>
<td>diskID</td>
<td>String</td>
<td>-</td>
<td>The ID of the disk bay</td>
</tr>
<tr>
<td>.1.1.3</td>
<td>diskModel</td>
<td>String</td>
<td>-</td>
<td>The disk model name</td>
</tr>
<tr>
<td>.1.1.4</td>
<td>diskType</td>
<td>String</td>
<td>SATA M.2</td>
<td>The disk type</td>
</tr>
<tr>
<td>.1.1.5</td>
<td>diskStatus</td>
<td>String</td>
<td>Good Idle Abnormal</td>
<td>The status of the disk</td>
</tr>
<tr>
<td>.1.1.6</td>
<td>diskTemperature</td>
<td>Integer</td>
<td>-</td>
<td>The disk temperature in Celsius degree</td>
</tr>
<tr>
<td>.1.1.7</td>
<td>diskSize</td>
<td>Integer</td>
<td>-</td>
<td>The disk size in gigabyte (GB)</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
 
<ul>
<li>The child-nodes of volume group (.1.3.6.1.4.1.44738.5)</li>
</ul>
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Name</th>
<th style="background: SteelBlue; color: white;">Type</th>
<th style="background: SteelBlue; color: white;">Status</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>.1.1.1</td>
<td>volumeIndex</td>
<td>Integer</td>
<td>-</td>
<td>Used internally for SNMP table and non-accessible</td>
</tr>
<tr>
<td>.1.1.2</td>
<td>volumeName</td>
<td>String</td>
<td>-</td>
<td>The volume name</td>
</tr>
<tr>
<td>.1.1.3</td>
<td>volumeLevel</td>
<td>String</td>
<td>Single Linear Raid0 Raid1 Raid10 Raid5 Raid6 Raid50 Raid60</td>
<td>The volume level</td>
</tr>
<tr>
<td>.1.1.4</td>
<td>volumeStatus</td>
<td>String</td>
<td>Healthy Clean Active Resyncing Recovering Reshaping Appending Migrating fsExpanding fsIniting checking Degraded Failed Inactive</td>
<td>The volume status</td>
</tr>
<tr>
<td>.1.1.5</td>
<td>volumeFileSystem</td>
<td>String</td>
<td>-</td>
<td>The volume file system type</td>
</tr>
<tr>
<td>.1.1.6</td>
<td>volumeTotalSize</td>
<td>Integer</td>
<td>-</td>
<td>The volume total size in gigabyte (GB)</td>
</tr>
<tr>
<td>.1.1.7</td>
<td>volumeFreeSize</td>
<td>Integer</td>
<td>-</td>
<td>The volume free size in gigabyte (GB)</td>
</tr>
</tbody>
</table>
 
<a name="mib43"></a>4.3 ASUSTOR UPS MIB
ASUSTOR UPS MIB provides the ability to monitor the status of a UPS device connected to the ASUSTOR NAS. Please note that 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. The table below describes partial information provided in the UPS MIB. If you are interested in all OIDs, please refer to the MIB file ASUSTOR-UPS-MIB.txt.
 
<ul>
<li>The partial child-nodes of ASUSTOR ups group (.1.3.6.1.4.1.44738.6)</li>
</ul>
<table class="table table-striped" border="1" style="width: 90%; border: solid #e0e8f1;">
<tbody>
<tr>
<th style="background: SteelBlue; color: white;">OID</th>
<th style="background: SteelBlue; color: white;">Name</th>
<th style="background: SteelBlue; color: white;">Type</th>
<th style="background: SteelBlue; color: white;">Status</th>
<th style="background: SteelBlue; color: white;">Explanation</th>
</tr>
<tr>
<td>.1.1.1</td>
<td>upsIndex</td>
<td>Integer</td>
<td>-</td>
<td>Used internally for SNMP table and non-accessible</td>
</tr>
<tr>
<td>.1.1.2</td>
<td>upsManufacturer</td>
<td>String</td>
<td>-</td>
<td>The UPS manufacturer</td>
</tr>
<tr>
<td>.1.1.3</td>
<td>upsModel</td>
<td>String</td>
<td>-</td>
<td>The UPS model name</td>
</tr>
<tr>
<td>.1.1.4</td>
<td>upsVendorId</td>
<td>String</td>
<td>-</td>
<td>The UPS vendor ID</td>
</tr>
<tr>
<td>.1.1.5</td>
<td>upsProductId</td>
<td>String</td>
<td>-</td>
<td>The UPS product ID</td>
</tr>
<tr>
<td>.1.1.6</td>
<td>upsBatteryRemainSecond</td>
<td>Integer</td>
<td>-</td>
<td>The UPS battery remaining usable time in seconds</td>
</tr>
<tr>
<td>.1.1.7</td>
<td>upsBatteryChargePercent</td>
<td>Integer</td>
<td>-</td>
<td>The battery charged percentage</td>
</tr>
</tbody>
</table>
 
<h4><a name="mib5"></a>5. Monitor specific OIDs</h4>
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 means of operating different kinds of NMS vary, the process of OID monitoring is similar. The overall procedure is as follows.
<ol>
<li>Import MIB file into NMS.</li>
<li>Setup the NMS to monitor specific OIDs.</li>
</ol>
The following guide demonstrates the use of PRTG (a type of NMS) including how to import MIB files and setup monitoring for the OIDs provided. For further help regarding PRTG, please consult PRTG documentation, as the following is only intended to be a brief description of OID monitoring.
 
<a name="mib51"></a>5.1 Import MIB file
As PRTG cannot import MIB files directly, Paessler MIB Importer is required to convert MIB files into the PRTG format:
<ul>
<li>Download and Install Paessler MIB Importer. Download from <a href="https://www.paessler.com/tools/mibimporter" target="_blank" rel="noopener">https://www.paessler.com/tools/mibimporter</a>, and install on your computer.</li>
<li>Go to File Import MIB File</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20160413/20160413143559_10951.jpg" alt="" title="" align="" width="860" height="647" />
 
<ul>
<li>Choose all the ASUSTOR MIB file together and click Open File</li>
</ul>
The three MIB files: ASUSTOR-SYSTEM-MIB.txt, ASUSTOR-DISK-MIB.txt and ASUSTOR-UPS-MIB.txt, must be import together as they are mutually dependent and Paessler MIB Importer cannot load them individually. If the import is successful, a window should appear as shown below.
 
<img src="http://www.asustor.com/images/kindeditor/image/20160413/20160413143559_33539.jpg" alt="" />
 
Detailed information is shown as below.
<img src="https://www.asustor.com/images/kindeditor/image/20160413/20160413143601_86088.jpg" alt="" title="" align="" width="860" height="647" />
 
<ul>
<li>Go to File Save Complete OIDLib as… to export the MIB files to the PRTG supported format.</li>
</ul>
<img src="https://www.asustor.com/images/kindeditor/image/20160413/20160413143604_30536.jpg" alt="" title="" align="" width="860" height="647" />
A PRTG-supported library containing the MIB information will then be generated.
 
<a name="mib52"></a>5.2 Setup the NMS
When PRTG is installed, it will create a folder "PRTG Network Monitor" for storing all the required files. The PRTG-supported library containing the MIB files in question should be placed into the subfolder "snmplibs" in folder "PRTG Network Monitor". Once this has been done, specific OIDs can be set up for monitoring in PRTG. This guide assumes that ASUSTOR NAS have already been added to the devices list and focuses only on how to add OIDs for monitoring.
<ul>
<li>Open the PRTG Network Monitor</li>
<li>Go to Sensors Add Sensor</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022161137_PRTG_Add_Sensors_S1.png" alt="" title="" align="" width="900" height="506" />
 
<ul>
<li>Click Add sensor to a device, choose an ASUSTOR NAS from the list, click Continue</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022161313_PRTG_Add_Sensors_S2.png" alt="" width="900" height="506" />
 
<ul>
<li>Select Custom Sensors SNMP Library</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022162016_PRTG_Add_Sensors_S3-1.png" alt="" title="" align="" width="900" height="506" />
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022162058_PRTG_Add_Sensors_S3-2.png" alt="" title="" align="" width="900" height="506" />
 
<ul>
<li>Select the previously exported ASUSTOR library file and click OK</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022162118_PRTG_Add_Sensors_S4.png" alt="" width="500" height="332" />
 
<ul>
<li>Choose items for monitoring</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022162201_PRTG_Add_Sensors_S5.png" alt="" width="900" height="506" />
 
<ul>
<li>You can start monitoring the ASUSTOR NAS status on NMS now!</li>
</ul>
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022162219_PRTG_Add_Sensors_S6-1.png" alt="" title="" align="" width="900" height="506" />
<img src="https://www.asustor.com/images/tinymce/upload_img_20241022162231_PRTG_Add_Sensors_S6-2.png" alt="" title="" align="" width="900" height="506" />

Publish: