Thank you, Geoff. That was precisely the answer I was looking for. I knew I was doing something wrong. I didn't realize the second adapter could be used without an IP address explicitly assigned to it. Yes, this is a basic zone (just an internal project so we don't need any public IP addresses). I was planning to set up an NFS server on the 192.168.101.0/24 network so this is exactly what I was trying to accomplish. Thanks.
On Fri, Jul 25, 2014 at 1:34 AM, Geoff Higginbottom < [email protected]> wrote: > Ian, > > It looks like you are trying to setup a basic zone and have a Management > Server on IP 192.168.101.3 and a Host on IP 192.168.101.4. > > The second interface on the host does not need any IP configuration on the > Host as it will not be used by the Host so remove the 192.168.102.4 > mapping.. This interface will be used by the Guest VMs running on the Host > who will have their own IP schema. > > Your Guest IP range will be in the 192.168.102.0/24 CIDR with a gateway > of 192.168.102.1 > > The Management Serve will talk to the Host via the 1st Interface, and > Guest VMs will use the 2nd. > > You have not mentioned storage, but assuming you are using NFS for Primary > and Secondary, put the NFS Server on the 192.168.101.0/24 network, and > then all storage traffic will also go over the 1st interface. > > Regards > > Geoff Higginbottom > > D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581 > > [email protected] > > -----Original Message----- > From: Daan Hoogland [mailto:[email protected]] > Sent: 25 July 2014 08:47 > To: [email protected] > Subject: Re: dual NIC VLAN configuration > > Ian, I would imagine that guest traffic can't go out to the net this way. > Maybe you should swap them. This is only guessing however. What are you > seeing? > > On Fri, Jul 25, 2014 at 2:00 AM, Ian Young <[email protected]> wrote: > > Here's the less verbose version: My hypervisor has two NICs and I've > > set up a label on each. Traffic to and from cloudbr0 works perfectly. > > Traffic going into cloudbr1 goes out cloudbr0 because that interface > > has a default gateway. Will this pose a problem when I try to set up > > separate management and guest networks in CloudStack? > > > > > > On Thu, Jul 24, 2014 at 10:56 AM, Ian Young <[email protected]> > wrote: > > > >> I am trying to set up a server with two NICs as a hypervisor. I > >> would like to use the two interfaces to separate management and guest > >> traffic, as recommended by the CloudStack installation guide. This > >> server is connected to a managed switch, which is connected to a > >> hardware firewall, both of which are set up with tagged VLANs. Some > >> of the ports on the switch are designated as VLAN 6 and some are VLAN > >> 7. I've confirmed the VLANs are set up correctly by configuring eth0 > >> and eth1 (one at a time) with the appropriate IP address, netmask, and > gateway. > >> > >> However, the difficulty arises when I try to configure both > >> interfaces simultaneously. The return traffic tends to go out > >> whichever interface is associated with the default gateway, a typical > >> issue when using multiple network interfaces. I've followed numerous > >> guides, which all basically say the same thing: Don't set a default > >> gateway; use iproute2 to control the flow of traffic with route-eth0, > >> rule-eth0, and rt_tables. I've tried setting this up numerous times > >> to no avail, probably because the guides I'm reading don't involve > >> VLANs. Add to that the the cloudbr0 and cloudbr1 bridges that > >> CloudStack requires and now I'm really confused as to how to set up > >> the network. I can't be the first person to have set up CloudStack > >> this way; it sounds pretty common. Can someone explain to me the > correct way to configure these interfaces? > >> > >> Here is my network information: > >> > >> VLAN 6 (management) > >> 192.168.101.0/24 > >> gateway: 192.168.101.1 > >> > >> VLAN 7 (guest) > >> 192.168.102.0/24 > >> gateway: 192.168.102.1 > >> > >> current hypervisor settings: > >> eth0: 192.168.101.4 > >> eth1: 192.168.102.4 > >> > >> current management server settings (this is a separate machine): > >> p4p1: 192.168.101.3 > >> > > > > -- > Daan > Find out more about ShapeBlue and our range of CloudStack related services > > IaaS Cloud Design & Build< > http://shapeblue.com/iaas-cloud-design-and-build//> > CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/> > CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/> > CloudStack Infrastructure Support< > http://shapeblue.com/cloudstack-infrastructure-support/> > CloudStack Bootcamp Training Courses< > http://shapeblue.com/cloudstack-training/> > > 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 a > company incorporated in India and is operated under license from Shape Blue > Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil > and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is > a company registered by The Republic of South Africa and is traded under > license from Shape Blue Ltd. ShapeBlue is a registered trademark. >
