[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Advanced networking - physical NICs.

Hi Jon,

1. Yes
2. You tell CloudStack what VLAN the public IPs are on, CloudStack will add the VLAN tags
3. CloudStack will do it automatically
4. 'something' like this:


BRIDGE= cloudbr1


DEVICE= cloudbr1

NOTE the public/guest interface (eth1 in this case) will then need to be connected to a trunk interface on your switch which allows all of the VLANs that you need for public and private networks

Kind regards,

Paul Angus

53 Chandos Place, Covent Garden, London  WC2N 4HSUK

-----Original Message-----
From: Jon Marshall <jms.123@xxxxxxxxxxxxx> 
Sent: 03 July 2018 11:55
To: users@xxxxxxxxxxxxxxxxxxxxx
Subject: Advanced networking - physical NICs.

I come from a Cisco background so I understand vlans, tagging and how to configure switches for trunks and I also understand how to configure tagging on CentOS.

The bit that is just not clicking with me is how to configure the NIC with CS using KVM and advanced networking.

The management/storage NIC is easy as I just assign an IP directly the bridge configuration file (cloudbr0) as there is no vlan tagging here.

The second NIC I want to run guest and public traffic across and I am using another bridge - cloudbr1.

Questions -

1) Is it okay to run guest and public traffic on the same NIC ?

2) do the public IPs only live on the VR ie. do I need a cloudbr1.<vlan ID> for the public IP range ?

3) whenever I add a new guest network once setup do I first need to setup the cloudbr1.<vlan ID> for that guest network or does cloudstack do this automatically ?

4) Assuming it is okay to run guest and public on same NIC what would the initial configuration of cloudbr1 look like ?

Apologies for all the questions but I am just getting completely stuck on this