Camek wrote:
othohin - Your response would be true if you only wanted one VLAN to appear to your ESXi servers. Instead what you need to do is configure the network ports which are being used with the ESXi server running View to support "trunks" and not "access" VLANs. If you wanted to have say VLAN 10,11,12 visable to the ESXi server you would setup the trunk on all the ports used by the servers and allow all 3 vlans. Now in ESXi under "Network" configuration you would add a "Vitrual Machine" for each of the 3 VLAN, one for each of the vlan you setup above. Now when you setup our desktop image for View make sure on it's network configuation that you select the proper Vitural Machine and it and any replicans from that image will now be attached to the selected VLAN. If you want images running on more VLAN than you must have an image for each VLAN.
To avoid this issue what we do is have one VLAN which is dedicated to View then all desktops being use in View have he same VLAN. This helps us too because now we know which user is View user and which one in "local" in the building just base on the IP address.
hi Camek,
If you see the attachment file you will understand the matter. It's not a tranking or VLAN routing issue. It's about differentiate the DHCP server according the VLAN. So no need to trund or VLAN routing!!!!!!!!!!!
