Forum Discussion
MvdG
Cirrus
CirrusDirect 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.
The F5 and Cisco APIC integration based on the device package and iWorkflow is End Of Life.
The latest integration is based on the Cisco AppCenter named ‘F5 ACI ServiceCenter’.
Click here to view the Cisco ACI and F5 BIG-IP design guide which discusses the following topics:
- SNAT or no SNAT
- BIG-IP redundancy
- Multi-tenancy
- Tighter integration using F5 ACI ServiceCenter
Visit https://devcentral.f5.com/s/articles/F5-and-Cisco-ACI-Essentials-Design-guide-for-a-single-POD-APIC-cluster to learn how to access a lab for hands on experience using the F5 ACI ServiceCenter
https://f5.com/cisco for updated information on the integration.
