Two different static server pools in the same EPG.
Can I break out two different server pools within the same ACI EPG using static pools and then use two F5 BIG-IP physical appliances in an active-active HA state to load balance both pools at the same time between the two F5s? Here is a break down of what this might look like: EPG-A: BIG-IP 5050(A) -> ServerPoolA BIG-IP 5050(B) -> ServerPoolB ServerPoolA Contains: 10.10.10.10/24 10.10.10.11/24 ServerPoolB Contains: 10.10.10.12/24 10.10.10.13/24
F5 LBaasV1 integration with Openstack Kilo and Cisco ACI
Hello, ¿has anyone tried to run the F5 LBaaSv1 for Openstack Kilo, while using Cisco ACI as SDN solution with the ml2 plugin integration? We are setting up that scenario, with an F5 physical appliance shared between all the Openstack tenants (the "under the cloud" deployment described in F5 docs) , but when trying to create a pool via Horizon GUI we get the following error "ERROR f5.oslbaasv1agent.drivers.bigip.agent_manager [-] Exception: Unsupported network type opflex. Cannot setup network." Opflex is the standard network type for Openstack with ACI, and I am not sure if it's possible to use another network type. We are asking Cisco support but meanwhile any information about a similar setup will be appreciated. Thanks.
Direct Server Return (nPath) and Cisco ACI
Hello, Anyone familiar with a F5 nPath configuration attached to a Cisco ACI environment? In the past, we have configured nPath on a F5 LTM in a traditional Layer 3 network which worked fine. But now the F5 appliance is connected to a Cisco ACI environment and we are seeing strange behavoir within ACI. VS and pool members are on different subnets and VLAN's and we believe that is causing the problem. Cisco ACI is seeing the IP-address of the VS on the VLAN in which the pool members are located. In a traditional network this is no problem, but Cisco ACI does not accept that. Is there a best practice that says VS and pool members must be in the same VLAN when using Cisco ACI and nPath? The F5 knowledge base articles all tell me this is not needed in a traditional network setup. Regards, Martijn.Integration question: Cisco ACI with f5 in unmanaged mode
(knowledge level : rudimentary :: first aci <-> f5 integeration project of my life:: reaching out to the community since everyone seems to be baffled) Need help in getting a stalled project through. trying to reach out the community to identify any direct Cisco ACI + f5 technical material to understand and configure f5 in unmanaged mode. There are quite a few links dealing in more complex vcmp/virtual and other issues. The work done so far: expected target architecture : Use f5 in unmanaged mode with ACI. With ACI expected to act like a regular switch and not be bothered with l4-7 et al. f5 configs: single physical f5 device : Port 2.1 and 2.2 : portchanneled to ACI 9K leaf switches : trunk is green/up! When you talk to Cisco as soon as they here f5 - the immediate jump is to configure l4-7. Q: When f5 is treating ACI as a switch how do i configure so that is it not bothered with l4-7 et al. Any discussion around this to further expand will be highly appreciated. Thanks,In one-arm mode, do my pool member servers have to be in the same network as the vIP/self-IP?
Reading through the LTM Implementation Worksheet and it says: "In a one-arm network, the Virtual IP (VIP) is on the same IP address space as the pool member servers. A one-arm network typically requires the source IP to be SNAT'ed to the floating IP address of the LTM when the packet is sent to the server. In a one-arm configuration, the server's default gateway is a network device such as a switch or router." Is this the only way or can I have my pool members in a different network/subnet as my self-IP and vIP?
