Have been trying to install HA on Synology NAS via Virtual Machine Manager and using OVA file. All goes ok following various guides on Youtube etc but I fail to get an Ip address (just the 172. etc ones).
I have been through a raft of threads on here and elsewhere trying to solve the issue without any joy and now getting to the point of giving up.
Network wise - I use Pfsense as the router / firewall and am installing on a DS1621+. The NAS sits in its own VLAN (192.168.20.X) and is accessible from other VLANs where necessary via the firewall rules. This all works.
So I connected to a cable from a spare RJ45 port (LAN1) on the NAS to the local edge switch and configured the port on the switch to the IOT VLAN (192.168.50.X). I can ping the NAS on both VLANS (20 & 50) from the laptop which sits on the main VLAN (192.168.0.X) fine.
The HA install goes fine but just do not get the IP address and cannot get my head around why. I have deleted and re-installed the virtual machine numerous times but get the same issue.
I use a HA Synology VM setup for years without any problems. Maybe this can help you. I checked my settings and I use these settings, FYI:
1 - I’m not using any network bond settings.
2 - At my HA VMnetwork settings there is a gear-icon where you change options, this is what I use:
2a - MAC Address (doesn’t mind except when using an already used one).
2b - SR-IOV, disabled.
2c - Model: e1000 (NOT the virtio, which I suspect could be the problem?)
They are the settings I originally used. Changed the e1000 out of desperation but have now put it back - no change.
Might have to disable the bond but I really don’t want to and the VM is using a completely different port anyway so not sure if it would make a difference but could try it.
Just to be sure, remember you have to restart the HA VM to get the settings active. It’s not changed on the fly.
BTW, beware when booted is takes some time to get access to the HA Web-UI, even when the HA CLI has started.
What is your HA CLI mention the connection address is (Accessed by DSM VM Connection)?
EDIT: you get more network info by using the HA-CLI command network info.
EDIT2: If you get a valid IP-address you could check the observer by making use of your webbrowser and use http:// and port 4357 instead of https 8123.
Bear in mind, that by default DSM is using the first configured in Control Panel interface for any outgoing traffic, so if you use other one it might not be so obvious to be configured. Also what is configuration of your VM network:
Setting on screenshot above links VM network to one configured as you shown on your screenshot.
Addresses in range of 172.x.x.x are docker subnets and are used by differenct HA containers to communicate internally.
Have you tried to set IP for HA to static on proper VLAN:
Pfsense is providing the DHCP service for all the VLANs and has been confirmed as working i.e. other devices get their IP address as does the NAS port that I wish to run HA via.
FYI, I added a separate DSM VM network for every DSM LAN interface (where I use VM’s). The one using HA I have got SR-IOV support enabled.
Maybe that’s why your gear-icon is greyed-out and you can not select a none virtual network card?
EDIT: If I remember correctly you had to do this in older DSM versions by Synology CLI interface. I did that in the past to get that working, but maybe I mistaking because it was a long time ago…
Just to be clear, to me it looks like the Syno VM has the Internal Virtual Network selected for your HA VM network card.
That’s why you need to select a none Syno VM network interface card, and that is preventing to get the VM network interface to be in ‘bridge’-mode, which is needed to get access to your LAN network.
FYI, I was looking at your image and compared it with my running HA instance. The info beneath the docker: is the same but the host_internet: false is different, mine is set to true.
For this kind of problems I use a separate VM, with the same network settings, with just an ISO to boot, and boot with a LinuxMint ISO to see if the problem is similar.
Just a thought…
EDIT: Watching your image again I noticed the interfaces: is enabled and connected to the enp0s3 (this looks allright). So to me it looks like it can not connect to your VLAN (DHCP) properly.
Do you have a second router/gateway (old/simple one?) to connect it to your DSM (LAN) and connect it, to check if the old router/gateway provides a proper IP/GW/DNS to the HA VM?
The gear action is greyed out I think because the VM is running. Once the VM is shutdown I can access it but only have the same ‘Default VM Network’ or ‘Not Connected’ available but no matter what I select I cannot enable SR-IOV.
I think you’re right in what you say regarding non Syno VM card but how I do it, no idea.
LinuxMint and ISO boot - I’ll have to spend some time on that one!
I do have other routers but it won’t be simple as PFsense is running everything, connected to a core switch and then 6 edge switches along with 2 Synology NAS and 13 APs. Everything is in VLANs as well. This means the whole house will go off and I will be hunted down like a rabid dog!
I think you should try to make another VM network, just to try if those options are available? What do you have to loose…
EDIT: You’r absolutly right! the VM must be shutdown before you can use the Gear-icon options.
It’s quite simple IMHO:
1 - Download the LinuxMint Mate ISO.
2 - Go to your Syno VM Manager → Image → add it
3 - Create a new VM with 4 GB RAM, vga, PC, select your desired network, select the LinuxMint ISO, Legacy Bios, USB controller disabled, no need to add HDD.
4 - Boot it and connect (with the SYNO VM manager option) to it, and it will show a GUI (after a while) where you can use your mouse/keyboard to do your thing.
5 - To show your network connected in LinuxMint, open a terminal and enter command: ifconfig -a (it’s does the same like command ipconfig in M$ Windows)
You could even browse, open files, and many more without using a HDD or what so ever!
EDIT: These steps could also be used by, for example, Virtual Box to create Virtual computers.
EDIT2: A lot of Linux distro’s will work this way!
The only thing you could check if a (old) router/gateway will assign a IP/GW/DNS.
You connect the (spare) Syno LAN (configured to listen to DHCP) and the LAN (no WAN) on the router/gateway, don´t connect anything else to it i.e. one network cable will only be needded.
If the (old) router/gateway doesn´t do what you want, just restore it to factory default. Normally factory settings on the majority of (old) router/gateway should be sufficient.
If you have questions, I will try to help you, but be aware I’m not an IT expert, just an enthusiast who had to discover all by trial and error…
Haven’t got around to the Linux one yet but connected a Draytek router to the spare port (set for DHCP) and the port gets an IP, DNS & gateway as it does if I connect it to the Pfsense.
I’m not a Mint user, but it looks like the ethernet connection is up, didn’t receive an IPv4 or IPv6 address, is trying to send packets (TX packets 82), but not receiving anything whatsoever (RX packets 0).
Really dumb question - is the Synology’s firewall enabled and configured to allow TCP/UDP/ICMP/DHCP traffic to the VM???
