F5 IPSEC to 3rd party vCloud Air

I am trying to do something unique where I have an inline F5 LB pair that is already listening with virtual servers on multiple public VLANs routing to pool members existing multiple local private VLANs.

 

I want to be able to enable a new private VLAN that exists in vCloud Air and create an IPSEC tunnel between the F5 Big-IP to the remote third party vCloud Air vShield.

 

Attempting to follow the first task of creating Forwarding (IP) VS from IPsec between a BIG-IP system and a third-party device causes an error that the 0.0.0.0 network has already been created.

 

On the local network, IP's are not directly connected to the same network, the F5 is only accessible via public gateway IP.

 

Example:

 

• 10.0.0.0/8 Client network.

   

• |.

   

• 10.1.1.1 Gateway IP to F5.
• |.
• 10.1.1.0/24 F5 listening VS network (10.1.1.5 F5 floating IP).
• |.
• 10.1.?.? or 192.168.?.? (Lost as to what I set up next).
• |.
• 192.168.70.0/24 remote vCloud Network (20.0.0.1 remote 3rd party IP).

I would format this better if the message board worked better.