How To Install Xpenology On Esxi

Xpenology is the same Synology NAS operating organisation, just installed on ordinary computer hardware. Instructions on how to install Xpenology on a regular computer are on the Internet wagon and pocket-sized cart, so I volition non dwell on it.

In this commodity, I want to tell you how to install Xpenology equally a virtual machine on an ESXi server and deploy a video surveillance server on its basis. Of form, since this is primarily a NAS, later installing a virtual machine, you can store files of other virtual machines on it from this and other hosts, simply, for me, this will exist overkill. Although, for experiments, this is quite a working choice.

This article is based in office on Tutorial: Install DSM 6.two on ESXi 6.seven

Get-go of all, you demand to download XPENOLOGY TOOL from the site: https://xpenology.com/forum/topic/12422-xpenology-tool-for-windows-x64/

Select the loader (loader) DS3615XS version 1.03b and DSM half dozen.2 23739

Download two files: "synoboot_3615.zero" and "DSM_DS3615xs_23739.pat"

From the archive "synoboot_3615.zip" we take the file "synoboot.img" and create a new text file "synoboot.vmdk" with the following content:

          # Disk DescriptorFile version=1 CID=6ccf51e5 parentCID=ffffffff isNativeSnapshot="no" createType="vmfs"  # Extent description RW 102400 VMFS "synoboot.img" 0  # The Disk Data Base  #DDB  ddb.adapterType = "lsilogic" ddb.deletable = "true" ddb.encoding = "UTF-8" ddb.longContentID = "7e24a756b77e33e24ac940cc6ccf51e5" ddb.thinProvisioned = "1" ddb.uuid = "60 00 C2 9a ee da ca 33-df 5e 04 3f 80 55 f9 62" ddb.virtualHWVersion = "10"        

Next, we need the OSFMOUNT programme, with which we will mount and set up the bootloader in "synoboot.img"

On the mounted deejay, edit the grub.cfg file:

1) Change the serial number and MAC address (for example, to C7AAN09761 and 0A1B2C3D4E5F); if yous need more than one network, and then add a line with mac2, mac3, etc.

2) Commenting out unnecessary bill of fare lines

3) Salve and unmount.

Create a virtual machine in esxi 6.vii:

1) Nosotros give the car 2 cores and 2 gigabytes of retentiveness

2) Remove the disk, SCSI controller and CD/DVD. If the 3617 bootloader is used, then you lot need to remove the USB controller or change its blazon to USB 3.0.

iii) Change the blazon of network
adapter on the E1000e and requite it a MAC address, the same as nosotros
registered in grub.cfg, in our case 0A:1B:2C:3D:4E:5F

To add a difficult deejay to the created virtual automobile, you lot need to add our 2 files to the folder with the machine files: synoboot.img and synoboot.vmdk

After that, in the properties of the machine, click "Add hard deejay" –> "Existing hard disk drive" and select the added disk.

Select its type SATA, SATA accost (0: 0)

Don't forget to change the boot type to BIOS

We start and come across an invitation to notice this device through the site http://discover.synology.com/. We will exercise so (y'all tin also utilize the Synology Assistant program, simply only versions non older than 6.2-24922, later versions cannot exist plant).

If everything is right, then in a minute it will find the device and offer to connect:

Pay attention to the series number and mac address

Nosotros have the license understanding:

And we see a message that the difficult drive is not institute. In fact, this is how it should exist: the deejay that we added before is only a bootloader. If we did this on a real figurer, and so we would write this paradigm (synoboot.img) to a USB wink drive and boot from it.

We plow off our virtual machine and add another SATA controller and a SATA (1.0) disk to it, this disk must be at least 15Gb and exist of a thick type (Thick provisioned).

Going back to the site http://detect.synology.com/ and looking for our device. Now, later on accepting the license agreement, it prompts to "Install"

After clicking "Install", select "Install manually" and select the previously downloaded file "DSM_DS3615xs_23739.pat"

Click "Install Now" and look for the installation to complete.

Afterwards installation, we again look for the device through the site http://find.synology.com/ and connect. Offset of all, you will need to set up the device name, user and password:

Then nosotros betoken that nosotros but need to exist notified about the availability of updates and uncheck both boxes. We DO Not NEED to update at all, we have everything virtual and SMART is irrelevant for u.s..

We skip the adjacent step, we don't demand QuickConnect.

After that, the initial setup is completed. If yous wish, y'all can climb through the settings, specify a static ip address, disable ipv6, enable SSH access, etc.

Nosotros reply all proposals to update with a decisive refusal!

There is one small step left: since this is a virtual machine, we need to install vm-tools so that the hypervisor can fully manage it. So let's become to the site. https://spk.4sag.ru/?fulllist=true and download "open-vm-tools_x64-6.1_10.ii.0-one.spk" from there, afterwards which nosotros manually install the package through the "Package Centre":

But aught volition work right away, since the arrangement does not withal have partitions on which you tin install anything …

To create partitions, go to "Storage Director" –> "Storage Resource Puddle" –> "Create"

We run across our 15Gb disk (if the disk was smaller, it would not let creating a division on information technology), which nosotros gave to the virtual motorcar (drag it to the right with the mouse). We agree that all information on this deejay will exist destroyed and refuse to check the disk for errors (in one case again: nosotros have everything virtual, but on real hardware this is a necessary thing)

We have created a resource puddle, at present we need a sectionalization on this pool, which they will immediately write to us about (there is a slight confusion with the translation: it suggests going to the "Volume" tab, but in fact the desired tab is called "Section").

Go to "Section" and click "Create".

We set the size of the sectionalisation (I used all the free space) and select the type of file system (Btrfs is an interesting thing, of course, only ext4 is somehow closer).

The partition is ready, now y'all can install something on it (we demand to install vm-tools) or create a shared binder on it (SMB, NFS, FTP …).

We render to the "Package Centre" and manually install "open-vm-tools_x64-6.1_10.2.0-1.spk" (you tin can ignore the fact that the bundle is not digitally signed).

At present the hypervisor tin can fully manage this virtual machine (for example, shut it downwards correctly).

Now we can motility on to what all this was started for: to video surveillance.

From the "Packet Center" you need to install a trial version of "Surveillance Station" on two cameras (On the forums, I met links to a hacked version, without restrictions on the number of connected cameras).

You tin immediately click "Open" and become to the page responsible for video surveillance.

Then everything is simple: cameras are added through the "IP camera", yous need to lookout the recordings through the "Timeline", and "Live Video", as you might guess, to view images from the cameras in existent time.

Adding the first photographic camera; if the photographic camera is not in the list of familiar devices, you can ever utilise the ONVIF or RTSP protocol

Nosotros select the permission for the main and secondary streams and the place where the records will be saved (we still have merely i section of 10Gb).

We set how we will tape – continuously or in movement.

After the camera activation is completed, all settings can be edited again: for example, specify who volition exist responsible for event detection (surveillance station or the camera itself).

When you try to install a third camera, the system will write that the licenses have ended. After that, either pay or await for a bundle with a hacked version.

To manage "Surveillance station", you tin can also download "Synology Surveillance Station Client" from the Synology website (information technology works a piddling faster than through a browser).

Now a pocket-sized digression almost where to shop recordings from video cameras. For me, spending on this precious storage space is also wasteful and the easiest manner is to add together an additional disk of the required size to ESXi. On this disk, you tin make a separate datastore or give the entire disk to a virtual machine via RDM. Of grade, after that, the mobility of this virtual motorcar will exist reduced to zero. If this is a standalone ESXi, so at that place is no problem, but if it is a cluster running vCenter, then the automobile is tightly tied to a specific host.

I prefer to add a disk through RDM, if necessary, it can be easily unlinked from the virtual automobile and rearranged to another server, and the automobile can be migrated, and then reattached to this RDM disk. If desired, such a disk can also be installed in an ordinary calculator with Linux, because there is an ext4 file system.

So let's do it. I installed an boosted 1Tb disk in the host. In earlier versions of ESXi, it was possible to add a physical RDM disk straight from the menu, but then for some reason this option was removed. Therefore, we connect to our host via SSH and find out the name of our new disk:

          ls -l /vmfs/devices/disks        

We run into that the deejay nosotros demand is called:

          t10.ATA_____WDC_WD10EZRX2D00DC0B0_________________________WD2DWMC301654272        

The command that makes a link to an RDM disk looks like this:

          vmkfstools -z /vmfs/devices/disks/diskname /vmfs/volumes/datastorename/vmfolder/vmnamevmdk        

In our example, this is:

          vmkfstools -z /vmfs/devices/disks/t10.ATA_____WDC_WD10EZRX2D00DC0B0_________________________WD2DWMC301654272 /vmfs/voluсmes/esxi04ds1/DS3615XS/rdmdisk1tbvmdk        

Now this disk tin exist added in the backdrop of the virtual auto (Add hard disk –> Existing hard disk):

The drive must be on a second SATA controller (1:1)).

And to unbind the RDM disk, you need to delete it in the automobile properties and delete the link file from the folder (in our instance, the rdmdisk1tb.vmdk file).

Once enabled, the drive volition announced in the Storage Manager:

Based on the new deejay, a new resource pool and a new partition on this pool are created (everything is the same every bit for a 15Gb disk). If you add 2 RDM disks, and then even a RAID can be made on their basis.

At present nosotros have two partitions on ii disks (it is clear that several partitions tin be created on a disk for unlike needs, for example, 1 for file trash, the other for storing photographic camera recordings).

The next step is to get to the control panel of Surveillance Station. There we go to the item "Record" on the tab "Storage", "Add"

Select "Add Shared Folder" and set the name and location:

In the properties of the camera, now nosotros select a new storage location, and afterwards confirmation, all recordings from this photographic camera will be moved to the new storage.

That, in fact, is all. Of course, you can register several users with different rights, ready post rotation rules, and much more, simply you lot tin read about all this in the assist.

Source: https://prog.world/installing-xpenology-on-esxi-and-setting-up-virtual-video-surveillance/

Posted by: flahertybrall1995.blogspot.com

Share this post