Hi Geoff, Thanks for this.
So does that mean I could only have multiple Primary Storage networks and not multiple Secondary Storage networks? The Physical Network 'storage' maps to a Xenserver network of the same name - My thinking is that if I create a second secondary storage volume on a different vlan, I would have to then add in a Cloudstack Management CIDR on the new network, and then in XenServer, ensure that both of the storage networks have the same name. So, on Xenserver I have: "Cloud-storage" network on Bond0+1 with IP address 192.168.10.1 "Cloud-storage" network on Bond2+3 with IP address 172.27.100.1 In Cloudstack I would have a single Physical Network called "Cloud-storage" With the IP Range: 192.168.10.10-192.168.10.20 172.27.100.10-172.27.100.20 And then based on the IP ranges above, my SSVM would be able to talk to both secondary storage devices in both networks. I also thought that you could not vlan tag a storage network in XenServer, but the Administration Guide for XenServer 6.1 seems to say otherwise: 4.3.3.3. Using VLANs with Dedicated Storage NICs Dedicated storage NICs (also known as IP-enabled NICs or simply management interfaces) can be configured to use native VLAN / access mode ports as described above for management interfaces, or with trunk ports and XenServer VLANs as described above for virtual machines. To configure dedicated storage NICs, see Section 4.4.7, "Configuring a Dedicated Storage NIC" http://support.citrix.com/servlet/KbServlet/download/32307-102-691300/reference.pdf I'll give it a go anyway, and see what happens. Len -----Original Message----- From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com] Sent: 02 July 2013 14:57 To: users@cloudstack.apache.org Subject: RE: Multiple Storage Interfaces Hi Len, What you are trying to do is perfectly possible, however confusingly it has nothing to do with the CloudStack Physical Network 'storage'. The CloudStack Storage Network is only used when accessing Secondary Storage, and is something which causes lots of confusion. (re-writing the official docs in relation to this is on my very long list of things to do) All you need to do is create two networks mapped to two different Bonds on your XenServer (assuming you want to use Bonding) then add a two new IPs, mapped to these networks. As XenServer cannot VLAN TAG the traffic for Storage or Management Networks, you will need to set the Switch Ports to Access Ports and let your switch add the appropriate VLAN Tags. This also highlights the need for dedicated NICs, one for each Storage Network, which is advisable in order to get optimum performance. If you are using Jumbo Frames, remember to set the MTU on the Bond, before mapping an IP to the Network. As longs as these CIDRs are unique, and do not overlap your CloudStack Management CIDR, when you add Primary Storage via CloudStack, your XenServers will simply use the appropriate Bond when they communicate with the Storage. Traffic routing is handled automatically by the XenServers based on the destination IPs. Regards Geoff Higginbottom D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 geoff.higginbot...@shapeblue.com -----Original Message----- From: Len Bellemore [mailto:len.bellem...@controlcircle.com] Sent: 02 July 2013 14:02 To: users@cloudstack.apache.org Subject: Multiple Storage Interfaces Hi Guys, Here's my scenario: I am using XenServer as my hypervisor and I have two separate storage networks set up (in Xenserver) One network set up on vlan 100, one network set up on vlan 200 Each network goes to a separate storage device Is it possible, when I create my Zone (advanced) to have multiple Physical Storage Networks? Through the gui it doesn't seem to let me add multiple storage networks, but maybe through the API? Thanks Len ________________________________ IMPORTANT NOTICE. This electronic message contains information from Control Circle Ltd, which may be privileged or confidential. The information is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this electronic message in error, please notify me by telephone or email (to the number or email address above) immediately. Activity and use of the ControlCircle e-mail system is monitored to secure its effective operation and for other lawful business purposes. Communications using this system will also be monitored and may be recorded to secure effective operation and for other lawful business purposes This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark. ________________________________ IMPORTANT NOTICE. This electronic message contains information from Control Circle Ltd, which may be privileged or confidential. The information is intended for use only by the individual(s) or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this electronic message in error, please notify me by telephone or email (to the number or email address above) immediately. Activity and use of the ControlCircle e-mail system is monitored to secure its effective operation and for other lawful business purposes. Communications using this system will also be monitored and may be recorded to secure effective operation and for other lawful business purposes
