<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Synology | Breek Een Been</title>
    <link>https://blog.breekeenbeen.nl/tag/synology/</link>
      <atom:link href="https://blog.breekeenbeen.nl/tag/synology/index.xml" rel="self" type="application/rss+xml" />
    <description>Synology</description>
    <generator>Source Themes Academic (https://sourcethemes.com/academic/)</generator><language>en-us</language><copyright>Rob Maas</copyright><lastBuildDate>Thu, 04 Dec 2014 09:12:53 +0200</lastBuildDate>
    <image>
      <url>https://blog.breekeenbeen.nl/images/icon_hue0c3a5851739ca8a2afc787728ee763e_182872_512x512_fill_lanczos_center_3.png</url>
      <title>Synology</title>
      <link>https://blog.breekeenbeen.nl/tag/synology/</link>
    </image>
    
    <item>
      <title>Enable Nfs Vaai on a Synology X10</title>
      <link>https://blog.breekeenbeen.nl/post/enable-nfs-vaai-on-a-synology-x10/</link>
      <pubDate>Thu, 04 Dec 2014 09:12:53 +0200</pubDate>
      <guid>https://blog.breekeenbeen.nl/post/enable-nfs-vaai-on-a-synology-x10/</guid>
      <description>&lt;p&gt;I was really trilled when Synology announced also releasing DSM 5.1 for their x10 series. Why? This because DSM 5.1 has a great feature called NFS for VAAI. In simple words, hardware acceleration on your NAS. For everyone using a Synology with at least DSM 5.1 or later and have VMware vSphere connected to it, I really would recommend enabling this feature. How you can do this, is explained below. First check your vSphere storage configuration, without VAAI you will see, that hardware acceleration is not supported.&lt;/p&gt;















&lt;figure id=&#34;figure-nfs-vaai-not-supported&#34;&gt;


  &lt;a data-fancybox=&#34;&#34; href=&#34;nfs_vaai_syn_esxi_notsupp.png&#34; data-caption=&#34;NFS VAAI not supported&#34;&gt;


  &lt;img src=&#34;nfs_vaai_syn_esxi_notsupp.png&#34; alt=&#34;&#34;  &gt;
&lt;/a&gt;


  
  
  &lt;figcaption&gt;
    NFS VAAI not supported
  &lt;/figcaption&gt;


&lt;/figure&gt;

&lt;p&gt;Now first download the VAAI plugin, cause VMware needs to know how it can offload the storage tasks to the Synology NAS. The plugin can be found 
&lt;a href=&#34;http://download.synology.com/ftp/Tools/VAAINFSPlugin/SYN-ESX-5.5.0-NasVAAIPlugin-1.0-offline_bundle-2092790.zip&#34; title=&#34;Synology NFS VAAI Plugin VIB&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;here&lt;/a&gt;. When the download is finished, save the file somewhere on the NAS where VMware can also access it, for me it is a folder named __Management under the NFS share.&lt;/p&gt;





  
  











&lt;figure &gt;


  &lt;a data-fancybox=&#34;&#34; href=&#34;https://blog.breekeenbeen.nl/post/enable-nfs-vaai-on-a-synology-x10/nfs_vaai_syn_esxi_copy2nas_hu282ba091f309865bf30d8919aa707916_10710_2000x2000_fit_lanczos_3.png&#34; &gt;


  &lt;img data-src=&#34;https://blog.breekeenbeen.nl/post/enable-nfs-vaai-on-a-synology-x10/nfs_vaai_syn_esxi_copy2nas_hu282ba091f309865bf30d8919aa707916_10710_2000x2000_fit_lanczos_3.png&#34; class=&#34;lazyload&#34; alt=&#34;&#34; width=&#34;725&#34; height=&#34;124&#34;&gt;
&lt;/a&gt;



&lt;/figure&gt;

&lt;p&gt;Connect to your vSphere host using SSH, make sure you have enabled SSH. (host - configuration - security profile, enabled &amp;amp; start SSH) When you are logged in, you can install the plugin with the following command.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;esxcli software vib install -d /vmfs/volumes/Gimli\ \\(1\\)/\_\_Management/Updates/SYN-ESX-5.5.0-NasVAAIPlugin-1.0-offline\_bundle-2092790.zip
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Wait a few seconds, it can take a few minutes, if everything went fine, you should see the following message.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed: Synology\_bootbank\_esx-nfsplugin_1.0-1
   VIBs Removed:
   VIBs Skipped:
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;You can reboot the system from here, simply with the command &amp;ldquo;reboot&amp;rdquo; or from the client. After the reboot the configuration page should say hardware acceleration: supported.&lt;/p&gt;





  
  











&lt;figure id=&#34;figure-nfs-vaai-supported&#34;&gt;


  &lt;a data-fancybox=&#34;&#34; href=&#34;https://blog.breekeenbeen.nl/post/enable-nfs-vaai-on-a-synology-x10/featured_hu337c6523f24fe086c772713f5817f35f_13958_2000x2000_fit_lanczos_3.png&#34; data-caption=&#34;NFS VAAI supported&#34;&gt;


  &lt;img data-src=&#34;https://blog.breekeenbeen.nl/post/enable-nfs-vaai-on-a-synology-x10/featured_hu337c6523f24fe086c772713f5817f35f_13958_2000x2000_fit_lanczos_3.png&#34; class=&#34;lazyload&#34; alt=&#34;&#34; width=&#34;1076&#34; height=&#34;162&#34;&gt;
&lt;/a&gt;


  
  
  &lt;figcaption&gt;
    NFS VAAI supported
  &lt;/figcaption&gt;


&lt;/figure&gt;

</description>
    </item>
    
    <item>
      <title>Monitoring Your X86 Synology With Monit</title>
      <link>https://blog.breekeenbeen.nl/post/monitoring-your-x86-synology-with-monit/</link>
      <pubDate>Thu, 03 Jan 2013 19:29:13 +0200</pubDate>
      <guid>https://blog.breekeenbeen.nl/post/monitoring-your-x86-synology-with-monit/</guid>
      <description>&lt;p&gt;First of all, I’m not very familiar with 
&lt;a href=&#34;http://mmonit.com/monit/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Monit&lt;/a&gt; at all, but I was looking for a simple monitoring solution which monitors, alerts and eventually can restart a service if it fails. So today I stumble upon Monit which was exactly I was looking for. It generates a simple dashboard and does exactly what I wanted it to do. After messing around with it for a couple of minutes I had a working dashboard on a Debian system which monitored a couple of services.&lt;/p&gt;
&lt;p&gt;I also have Synology NAS which runs a couple of services, which should be up 24/7, unfortunately sometimes a service fails and it is possible I noticed it a little late, i.e. after a couple of hours.&lt;/p&gt;
&lt;p&gt;So I thought why not install Monit on the Synology, I have a DS1010+, which has a plain old x86 Intel CPU, so compiling and running it shouldn’t be that hard even better it turns out they have a lots of compiled versions at their 
&lt;a href=&#34;http://mmonit.com/monit/download&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;website&lt;/a&gt; for download.&lt;/p&gt;
&lt;p&gt;So let’s start.&lt;/p&gt;
&lt;p&gt;First of all download the right version (Linux x86) of the website and unpack it.
Now we have to copy te content to the different locations, Linux users can use SCP, for Windows users, the easiest way is to put the unpacked folder on a share of the Synology. I putted on “\mynasUploads”.&lt;/p&gt;
&lt;p&gt;Start an SSH session (
&lt;a href=&#34;http://www.putty.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Putty&lt;/a&gt;) and login with root and your password.&lt;/p&gt;
&lt;p&gt;First let’s copy the binary to “/usr/local/bin” and copy the default config file to /etc/monitrc.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; cp /volume1/Uploads/monit-5.5/bin/monit /usr/local/bin
&amp;gt;
&amp;gt; cp /volume1/Uploads/monit-5.5/conf/monitrc /etc/monitrc
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Now we have to edit the monitrc so we can access the dashboard and make a directory the default directory for configuration files, I like to keep them seperated.&lt;/p&gt;
&lt;p&gt;You can edit monitrc on Windows with notepad++ and then copy it again or use vi on the Synology.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;vi /etc/monitrc
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Press “ins” to enter insert mode and seek and change the following lines.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; set httpd port 2812 and
&amp;gt;     use address localhost    # only accept connection from localhost
&amp;gt;     allow localhost               # allow localhost to connect to the server and
&amp;gt;     allow admin:monit         # require user &#39;admin&#39; with password &#39;monit&#39;
&amp;gt;     allow @monit                 # allow users of group &#39;monit&#39; to connect (rw)
&amp;gt;     allow @users readonly  # allow users of group &#39;users&#39; to connect readonly
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;and change them, don’t forget to change the subnet if you use another range then 10.0.0.0/8.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; set httpd port 2812 and
&amp;gt;     allow 10.0.0.0/8
&amp;gt;     allow admin:hardpassword
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Quit “vi” bij pressing escape and type &amp;ldquo;:wq”, which stands for write and quit.&lt;/p&gt;
&lt;p&gt;Change the permissions of the monitrc file&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; chmod 0700 /etc/monitrc
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;and finally start monit&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; /usr/local/bin/monit
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Go to your webbrowser and go the url 
&lt;a href=&#34;http://yournas:2812&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;http://yournas:2812&lt;/a&gt; and login, you should see something like the picture below.&lt;/p&gt;





  
  











&lt;figure &gt;


  &lt;a data-fancybox=&#34;&#34; href=&#34;https://blog.breekeenbeen.nl/post/monitoring-your-x86-synology-with-monit/featured_hu341334b6d0ce923b3cd19d573e40e4f1_16056_2000x2000_fit_lanczos_3.png&#34; &gt;


  &lt;img data-src=&#34;https://blog.breekeenbeen.nl/post/monitoring-your-x86-synology-with-monit/featured_hu341334b6d0ce923b3cd19d573e40e4f1_16056_2000x2000_fit_lanczos_3.png&#34; class=&#34;lazyload&#34; alt=&#34;&#34; width=&#34;941&#34; height=&#34;497&#34;&gt;
&lt;/a&gt;



&lt;/figure&gt;

&lt;p&gt;If this works, we can make it more interesting by adding the services or filesystem information.&lt;/p&gt;
&lt;p&gt;Let’s make a directory for the config files and add this directory to the monitrc file.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; mkdir /etc/monit
&amp;gt;
&amp;gt; echo “include /etc/monit/*” &amp;gt;&amp;gt; /etc/monitrc
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Now we only need something to monitor, for example Cloudstation.&lt;/p&gt;
&lt;p&gt;Start vi.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; vi /etc/monit/cloudstation
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;and add the following lines.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; check process cloudstation with pidfile /var/run/synosyncfolder.pid
&amp;gt;         start program = &amp;quot;/var/packages/CloudStation/scripts/start-stop-status start&amp;quot;
&amp;gt;         stop program = &amp;quot;/var/packages/CloudStation/scripts/start-stop-status stop&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This will check if Cloudstation is running and if it isn’t, it will automatically restart the service.&lt;/p&gt;
&lt;p&gt;To load the new config file, restart monit.&lt;/p&gt;
&lt;pre&gt;&lt;code class=&#34;language-bash&#34;&gt;&amp;gt; killall monit
&amp;gt;
&amp;gt; /usr/local/bin/monit
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Monit has a lot more possibilities and the 
&lt;a href=&#34;http://mmonit.com/monit/documentation/monit.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;documentation&lt;/a&gt; is good, so I would say knock yourself out.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;This post was just to get you started, there are still somethings on my todo list, like create an init script and maybe create a package for it.&lt;/em&gt;&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
