cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amin Pashapour <>
Subject Re: F5 and CloudStack
Date Thu, 13 Mar 2014 22:53:20 GMT
Hi Chandan

Below is what my network offering shows:
Supported Services:UserData, Firewall, Vpn, Dhcp, StaticNat, Lb, Dns, PortForwarding, SourceNat

Service Capabilities: UserData: VirtualRouter, Firewall: VirtualRouter, Vpn: VirtualRouter,
Dhcp: VirtualRouter, StaticNat: VirtualRouter, Lb: F5BigIp, Dns: VirtualRouter, PortForwarding:
VirtualRouter, SourceNat: VirtualRouter


 From: Chandan Purushothama <>
To: "" <> 
Sent: Thursday, March 13, 2014 5:46 PM
Subject: RE: F5 and CloudStack

Hello Amin,

May I know whether you added Port Forwarding Service to your Network Offering,

Thank you,

-----Original Message-----
From: Amin Pashapour [] 
Sent: Wednesday, March 12, 2014 2:21 PM
Subject: Re: F5 and CloudStack

Chandan Purushothama <Chandan.Purushothama@...> writes:

> Hello Amin,
> May I know if you are able to work with a VM deployed in a network 
> created
> "DefaultIsolatedNetworkOfferingWithSourceNatService". This will prove 
> that
your Guest VLAN range
> and Public VLAN are valid,
> Thank you,
> Chandan.
> -----Original Message-----
> From: Amin Pashapour [mailto:jolfa1@...]
> Sent: Wednesday, March 12, 2014 1:09 PM
> To: users@...
> Subject: F5 and CloudStack
> Hi All
> I am trying to add an F5 BigIP (10.1) into my CloudStack (4.2.1)
> This is what I have done:
> 1- Created a network offering with VR to do everything, including 
> Source
and Static NAT, except BL using F5BigIP.
> 2- Created a network based on the offering. Added egress rule for for all protocols.
> 3- Created a VM using Centos template and the network from step 2
> 4- Added a firewall rule to the "public" ip of the network for tcp 
> ports
1- 64000.
> 5- Can't add port forwarding to the public ip.
> I get into the VM's console and the network is up. However, I can't
ping/ssh to any other system.
> No system can ping/ssh my VM.  This is similar to what someone named 
> Anoop
had observed in April of 2013.
> Can someone give me a hint or two on what I am missing?
> Thanks.

Hi Chandan.

Other VM's using DefaultIsolatedNetworkOfferingWithSourceNatService work perfectly fine. I
can ssh with no problems.  Of course, I had to add a port forwarding rule to let port 22

When I try to add a port forwarding rule with the F5 offering network, I get this error:

The IP <public ip> is already used as SourceNAT rather than PortForwarding.

And I can't go any further.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message