13 Responses

  1. Gary Heron
    Gary Heron at |

    Hi Chris,

    My vLab in a HP DL380 – http://vheron.co.uk/?p=18

    Reply
  2. Mike
    Mike at |

    My lab is very similar. Pair of v1910-24gs connected via a LACP trunk, 3 VMware hosts each with 2 dedicated iSCSI ports on standard vSwitches, 3 links in VDS using LBT handle Mgmt, 2x VMotion vmkernels, NFS, FT, and VM traffic.

    How do you like the v1910-24g? I like it but on the latest firmware trying to change Flow Control settings simply makes the switch reboot and the changes are lost which is obnoxious.

    Reply
  3. Wahl Network « HGW XX/7
    Wahl Network « HGW XX/7 at |
  4. Dmitry
    Dmitry at |

    Hi Chris,

    I don’t understand how you get iSCSI in another vlan that NFS on synology?

    You route iSCSI traffic, right?

    Reply
  5. Nick
    Nick at |

    Hello, i ran into your post when doing some research on vmware related stuff and noticed what you said about synology devices not being able to live on multiple vlans. That’s not exactly true. Officially, sure, but unofficially, you can treat them like linux devices – albiet without all of the features.

    I was able to get my synology ds1812+ to listen/function on two vlans, but when i tried more than that, it didn’t work, and i’m not sure if it is because of my switch (cisco sg300-10), because i chose to bond my 2x1gb connections to it via LACP, or because of something else, but it worked. I had the network settings in the DSM control panel go to my vlan3, which i chose for iscsi, network 10.10.3.x/24. When you log into the device via ssh, if you do ifconfig, you can see the bond0 device and then the device you set your ip on, bond0.3 (or .whatever vlan). If you then issue this command –

    ifconfig bond0:.1 192.168.2.4 netmask 255.255.255.0 mtu 9000

    you will then create an ethernet alias that will share your bond and be on vlan 1 or whatever you set it to with the IP settings you chose. You will have to have proper routes in place upstream, but it definitely works.

    You will also need to set your startup scripts on the synology to re-establish your aliased ethernet device as well, and be prepared to have to recreate your settings when upgrading DSM firmware, but ya. Useful!

    Reply
  6. John P.
    John P. at |

    You use vDS in this article but mention “Note: The management host uses a single vSwitch.”

    So you’re using a vSwitch for the management interface and vDS for everything else? Or are you using vDS for everything, including management, with no vSwitches?

    If you use vDS only, will there be any issues if vCenter is shutdown or loses connection?

    Reply

Share your point of view!