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 >
