In an inline setup we only support F5 & SRX combination. F5 will be behind SRX so F5 does not require any public IP configured. So no need to configure public interface with public vlan and IP address.
-----Original Message----- From: BJO ERN [mailto:[email protected]] Sent: Wednesday, November 13, 2013 1:17 PM To: users Subject: Re: External Loadbalancer Thanks Sanjeev for the Info. How would be the setup on an inline setup ? Public would move to the external firewall right ? On Tue, Nov 12, 2013 at 9:53 PM, Sanjeev Neelarapu < [email protected]> wrote: > Hi Bjoern, > > Public VLAN will not be configured by CS. Admin has to configure > public vlan and assign one IP belongs to that vlan on F5 public interface > manually. > > -Sanjeev > > -----Original Message----- > From: BJO ERN [mailto:[email protected]] > Sent: Wednesday, November 13, 2013 8:22 AM > To: users > Subject: External Loadbalancer > > Hi Guys, > > who did setup a external load balancer in cloudstack ? > I setup a F5 with an assigned network offering and finally got the > guest VLAN/pool provisioning working. > But I noticed that a public VLAN was not created on the F5, so how > would the public traffic reach the device if not inline ? I basically > ended up with a virtual IP (public) which does not belong to an VLAN > on the F5 > > FYI, since we don't have a supported external firewall, I did not add > the firewall feature to the network offering and was hoping we can put > our firewall transparently in place (generally allowing port 80/443 as > example) > > Bjoern >
