Hi Murali, Thanks for reply. I have F5 appliance which is absolutely empty, there are only one account, two interfaces 1.1 and 1.2, no vlans. CS can login to it successfully using admin credentials. After that i created network offering with shared LB, created users network using that offering (for some reason i can't specify CIDR for external LB, and CS cut default /20 network for it, that is not clear - why i can't control CIDR, at this point there is no differences - software router or standalone LB). When i started to create VM vlan was assigned to my network, and F5 was provisioned with that clan (i can see it in F5 ui and ifconfig shows it as well), but from my understanding CS is trying to create vlan second time (the log says about it explicitly):
2012-05-28 07:23:17,503 DEBUG [network.resource.F5BigIpResource] (DirectAgent-66:null) Creating a guest VLAN with tag 801 2012-05-28 07:23:17,556 ERROR [network.resource.F5BigIpResource] (DirectAgent-66:null) Exception caught in Networking::urn:iControl:Networking/VLAN::create() Exception: Common::OperationFailed primary_error_code : 16908390 (0x01020066) secondary_error_code : 0 error_string : 01020066:3: The requested VLAN (/Common/vlan-801) already exists in partition Common. 2012-05-28 07:23:17,556 ERROR [network.resource.F5BigIpResource] (DirectAgent-66:null) Failed to execute IPAssocCommand due to com.cloud.utils.exception.ExecutionException: Exception caught in Networking::urn:iControl:Networking/VLAN::create() Exception: Common::OperationFailed primary_error_code : 16908390 (0x01020066) secondary_error_code : 0 error_string : 01020066:3: The requested VLAN (/Common/vlan-801) already exists in partition Common. 2012-05-28 07:23:17,638 ERROR [network.resource.F5BigIpResource] (DirectAgent-66:null) Retrying IpAssocCommand. Number of retries remaining: 0 2012-05-28 07:23:17,779 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-80:null) Ping from 23 2012-05-28 07:23:17,848 DEBUG [network.resource.F5BigIpResource] (DirectAgent-66:null) Creating a guest VLAN with tag 801 2012-05-28 07:23:17,866 ERROR [network.resource.F5BigIpResource] (DirectAgent-66:null) Exception caught in Networking::urn:iControl:Networking/VLAN::create() Exception: Common::OperationFailed primary_error_code : 16908390 (0x01020066) secondary_error_code : 0 error_string : 01020066:3: The requested VLAN (/Common/vlan-801) already exists in partition Common. 2012-05-28 07:23:17,867 ERROR [network.resource.F5BigIpResource] (DirectAgent-66:null) Failed to execute IPAssocCommand due to com.cloud.utils.exception.ExecutionException: Exception caught in Networking::urn:iControl:Networking/VLAN::create() and F5 doesn't like it causing full rollback. Process didn't get that spot when IP will be assigned. In case of shared F5 (again absolutely empty appliance, no vlans, no networks) - I'm getting error that there is no F5 with requested capacity, but default capacity is 50. > On 26/05/12 10:55 AM, "d...@soleks.com" <d...@soleks.com> wrote: > >> >> >> Hi All, >> >> I have BIG-IP F5 VE (virtual edition), was able to added it to >> Cloudstack, created network offering using F5 LB, after that i had bunch >> of problems, that i can't resolve. >> >> 1) I created not dedicated LB, can't create instance, logs shows: >> >> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] >> is unreachable: There are no F5 load balancer devices >> with the free capacity for implementing this network >> at >> com.cloud.network.element.F5ExternalLoadBalancerElement.implement(F5Extern >> alLoadBalancerElement.java:135) >> at >> com.cloud.network.NetworkManagerImpl.implementNetworkElementsAndResources( >> NetworkManagerImpl.java:1769) >> at >> com.cloud.network.NetworkManagerImpl.implementNetwork(NetworkManagerImpl.j >> ava:1722) >> at >> com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:30) >> at >> com.cloud.network.NetworkManagerImpl.prepare(NetworkManagerImpl.java:1842) >> at >> com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerI >> mpl.java:741) >> at >> com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.jav >> a:461) >> at >> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java: >> 2580) >> at >> com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java: >> 2517) >> at >> com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:32) >> at com.cloud.api.commands.DeployVMCmd.execute(DeployVMCmd.java:317) >> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:132) >> at >> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:427) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >> at >> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >> at java.util.concurrent.FutureTask.run(FutureTask.java:166) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: >> 1110) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java >> :603) >> at java.lang.Thread.run(Thread.java:679) >> >> but i don't have any networks there yet, default capacity is 50. Why it >> happened > > There might be a mismatch between resource guaranteed (to provide a > dedicated or shared load balancer) by a network offering and what load > balancer resources are provisioned in to the deployment. Please refer to > [1], section titled 'device allocation logic' might help to understand > whats going wrong. > >> >> 2) I created dedicated LB, trying to create VM instance, failed, log >> shows the following: >> >> 2012-05-25 12:43:01,530 ERROR [network.resource.F5BigIpResource] >> (DirectAgent-39:null) Exception caught in Networking::urn:iCont >> rol:Networking/VLAN::create() >> Exception: Common::OperationFailed >> primary_error_code : 16908390 (0x01020066) >> secondary_error_code : 0 >> error_string : 01020066:3: The requested VLAN >> (/Common/vlan-608) already exists in partition Common. >> 2012-05-25 12:43:01,530 ERROR [network.resource.F5BigIpResource] >> (DirectAgent-39:null) Failed to execute IPAssocCommand due to c >> om.cloud.utils.exception.ExecutionException: Exception caught in >> Networking::urn:iControl:Networking/VLAN::create() >> Exception: Common::OperationFailed >> primary_error_code : 16908390 (0x01020066) >> secondary_error_code : 0 >> error_string : 01020066:3: The requested VLAN >> (/Common/vlan-608) already exists in partition Common. >> 2012-05-25 12:43:01,615 ERROR [network.resource.F5BigIpResource] >> (DirectAgent-39:null) Retrying IpAssocCommand. Number of retrie >> s remaining: 0 >> 2012-05-25 12:43:01,819 DEBUG [network.resource.F5BigIpResource] >> (DirectAgent-39:null) Creating a guest VLAN with tag 608 >> 2012-05-25 12:43:01,847 ERROR [network.resource.F5BigIpResource] >> (DirectAgent-39:null) Exception caught in Networking::urn:iCont >> rol:Networking/VLAN::create() >> Exception: Common::OperationFailed >> primary_error_code : 16908390 (0x01020066) >> secondary_error_code : 0 >> error_string : 01020066:3: The requested VLAN >> (/Common/vlan-608) already exists in partition Common. >> 2012-05-25 12:43:01,847 ERROR [network.resource.F5BigIpResource] >> (DirectAgent-39:null) Failed to execute IPAssocCommand due to c >> om.cloud.utils.exception.ExecutionException: Exception caught in >> Networking::urn:iControl:Networking/VLAN::create() >> Exception: Common::OperationFailed >> primary_error_code : 16908390 (0x01020066) >> secondary_error_code : 0 >> error_string : 01020066:3: The requested VLAN >> (/Common/vlan-608) already exists in partition Common. >> >> seems like CS is trying to create it twice and failed. Actual vlan was >> created on the LB, but no IP assigned. >> >> 3) Now i'm trying to clean-up CS, removing all F5 LBs, failed again, CS >> is saying that there are network which still uses that loadbalancer. > > Looks like F5 is not programmed completeley with guest vlan and guest > networks subnet IP. After Vlan is configured was there any error while > assigning subnet IP on to F5? > >> >> Is F5 support phased out ? If not what is the support status for it ? >> Will you continue to support it ? > > No, F5 support is not phased out. In fact CloudStack 3.0 network offering > feature is enhanced to support F5 as well, so that brings in addition use > cases (multiple F5 load balancers per zone, ability to assign a dedicated > F5 device to a tenant etc) with F5. > > [1]. http://wiki.cloudstack.org/pages/viewpage.action?pageId=1344581 > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
