Maxhawk Posted March 23, 2018 Share #1 Posted March 23, 2018 I'm trying to install a second instance of DSM by using DDSM in Docker in an ESXi environment. The reason I can't spin up another XPE VM instance is because all 12 of my drive bays on the backplane are being passed through by an H310 controller (flashed IT mode=HBA). The issue I'm having with the ESXi VM instance is I can't get network connectivity on the DDSM. I've tried DDSM on a separate bare metal installation and it worked fine set up the same way. The only significant difference is one is bare metal while the other one is ESXi. On ESXi I've presented XPE with 2 virtual network cards on different subnets. DSM gets an IP address from both subnets but DDSM can talk to neither of them. This is an ESXi issue, but I can't exactly go asking on a Synology forum about use with ESXi. I was just hoping that someone here may have done it so I know it's possible. Everything looks right as configured in ESXi. Thanks for reading. Quote Link to comment Share on other sites More sharing options...
haydibe Posted March 29, 2018 Share #2 Posted March 29, 2018 (edited) Been there, done that and had the same result. The issue is more of a ESXi user issue, rather then an ESXi issue Make sure your vSwtich has following settings in the security policy it uses: Allow promiscuous mode -> Yes Allow forged transmits -> Yes Allow MAC changes -> Yes Though, be aware that transfer speeds will drop slightly and won't be as stable as they are without these settings. When i was tinkering around with docker and the macvlan network mode, people in the syno forums could get it up and running and i couldn't. That made me dig into the ESXi vSwtich settings. After the settings have been made, it worked flowless. Edited March 29, 2018 by haydibe 1 Quote Link to comment Share on other sites More sharing options...
Maxhawk Posted March 30, 2018 Author Share #3 Posted March 30, 2018 7 hours ago, haydibe said: Make sure your vSwtich has following settings in the security policy it uses: Allow promiscuous mode -> Yes Allow forged transmits -> Yes Allow MAC changes -> Yes Thanks this worked! I know I tried one of those to Yes but not all three. Also it turns out you don't have to turn these on for the entire vSwitch. I did it only on the port group where I specified the VLAN ID and DDSM got an IP address first try. Quote Link to comment Share on other sites More sharing options...
c_c_b Posted March 30, 2018 Share #4 Posted March 30, 2018 Mind sharing some screenshots? I tried going the port group route as you mentioned but still get a 169.254.... address. Works great if I make the changes at the vSwitch. Quote Link to comment Share on other sites More sharing options...
Maxhawk Posted March 30, 2018 Author Share #5 Posted March 30, 2018 7 hours ago, c_c_b said: Mind sharing some screenshots? I tried going the port group route as you mentioned but still get a 169.254.... address. Works great if I make the changes at the vSwitch. The DDSM network is called Nick-Synology. The only other changes I made to the default was to change NIC teaming to Route based on IP hash which should not affect this. I cant remember if I made changes to the security policy of the default vSwitch0 for the managment network, but I see that it's not all set to No FWIW. This switch is on a separate NIC port from vSwitch Intel. Quote Link to comment Share on other sites More sharing options...
leonoxo Posted August 13, 2020 Share #6 Posted August 13, 2020 Is there a way to use DDSM on another Docker? How to solve the network failure after starting another Docker? The reverse check of the DDSM Container startup command is as follows: docker run --name=DDSM --hostname=DDSM --volume=/volume1/DDSM/@synology_dockerdsm_conf/Infostore/:/usr/syno/ddsm/:rw --volume=/volume1/DDSM/Datastore/:/volume1:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/etc:/etc/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/var:/var/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/usr.syno.etc:/usr/syno/etc/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/usr.local:/usr/local:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/root.ssh:/root/.ssh:rw --cap-add=ALL --cap-drop=AUDIT_CONTROL --cap-drop=AUDIT_WRITE --cap-drop=MAC_ADMIN --cap-drop=MAC_OVERRIDE --cap-drop=DAC_READ_SEARCH --cap-drop=LINUX_IMMUTABLE --cap-drop=SYS_ADMIN --cap-drop=SYS_TIME --cap-drop=SYS_BOOT --cap-drop=SYS_MODULE --cap-drop=SYS_RAWIO --cap-drop=SYS_TTY_CONFIG --network=none --label IsSynologyDSM="yes" --log-driver=db --detach=true SynologyDSM:6.1-15284 /sbin/init --network=none Why is it still connected? Quote Link to comment Share on other sites More sharing options...
Bobwin Posted September 4, 2021 Share #7 Posted September 4, 2021 On 8/13/2020 at 8:44 AM, leonoxo said: Is there a way to use DDSM on another Docker? How to solve the network failure after starting another Docker? The reverse check of the DDSM Container startup command is as follows: docker run --name=DDSM --hostname=DDSM --volume=/volume1/DDSM/@synology_dockerdsm_conf/Infostore/:/usr/syno/ddsm/:rw --volume=/volume1/DDSM/Datastore/:/volume1:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/etc:/etc/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/var:/var/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/usr.syno.etc:/usr/syno/etc/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/usr.local:/usr/local:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/root.ssh:/root/.ssh:rw --cap-add=ALL --cap-drop=AUDIT_CONTROL --cap-drop=AUDIT_WRITE --cap-drop=MAC_ADMIN --cap-drop=MAC_OVERRIDE --cap-drop=DAC_READ_SEARCH --cap-drop=LINUX_IMMUTABLE --cap-drop=SYS_ADMIN --cap-drop=SYS_TIME --cap-drop=SYS_BOOT --cap-drop=SYS_MODULE --cap-drop=SYS_RAWIO --cap-drop=SYS_TTY_CONFIG --network=none --label IsSynologyDSM="yes" --log-driver=db --detach=true SynologyDSM:6.1-15284 /sbin/init --network=none Why is it still connected? Did you find out if it was possible to install DDSM on another Docker? I’m running DDSM on Synology docker, but I would also like to have a version of DDSM running on docker on my Debian VM. Anyone know if this is possible and how do a do that? TIA Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.