When we define a separate storage network for secondary storage (for example on vlan34) on Xenserver 6.2, Cloudstack 4.4.1 creates this new network on Xenserver for SSVM to reach secondary storage with proper vlan and everything BUT since we can no longer issue any IP address with the same vlan (34) directly on Xenserver (for xenserver to mount secondary) just using our bonded interface, we have to create static routing from our router for xenserver to access this secondary storage through its management interface. Are you guys assigning IP directly to Xenserver after waiting for Cloudstack to create this new network on Xenserver (using Cloudstack's newly created network name) and using this network to issue IP address directly on Xenserver, I cant think of any other way, any idea? thanks Sam
