ACI Integration with F5-LTM

subashchandran · ‎09-23-2015

Hi All,

I am planning to integrate ACI with F5 LTM(virtual appliance)

L3---------(vip)F5(Real IP,s)---------Servers

Go to mode LB

Can you please share the deployment guide or configuration guide.

I couldn't find good document in web.

Netscaler document i got it from Citrix website.

subashchandran · ‎09-27-2015

Any Updates...

mikriple · ‎09-28-2015

Hey Subash,

Please see the following:

http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-735490.pdf

I'm not sure if these specifically mention L3 out as the Consumer but the configuration is the same. If you are running an older version of code you may need to create a Bridge Domain with a Subnet within the same subnet as your VIP and point a Static Route from the F5 at the Bridge Domain Subnet that is associated with the L3 Out.

Mike Ripley

subashchandran · ‎09-29-2015

Hi Mike,

Thanks for your reply.

I had created L4-L7 devices in the tenant tab and getting error:-

CONFIGURATION STATE

Configuration Issues:

Devices State:

init

This device state is not changing to stable

Attached topology diagram for your reference.

Please refer the below steps :-

++ Create new BD for (External F5 ) and advertise this subnet to public--5.5.5.0

++Will create new service template.

++ Configured self IPs in F5 (Internal ,external and Management)

++Client will access the VIP IP 5.5.5.100 and load balanced to back end webservers.

subashchandran · ‎09-29-2015

Hi team,

Any one faced the below connectivity issues---l4-L7 F5 ltm integration...

PROPERTIES

Severity:

cleared

Last Transition:

2015-09-29T21:59:20.788+00:00

Lifecycle:

Retaining

Affected Object:

uni/tn-TENANT-WT-COE/lDevVip-F5-LTM-VE/lIf-external

Description:

LIf configuration external for L4-L7 Devices F5-LTM-VE for tenant TENANT-WT-COE is invalid. Reason: LIf has an invalid MifLbl

Explanation:
This fault occurs when a Logical Interface configuration is invalid.The config issues the exact reason for the error.

Recommended Action:
If you see this fault, please modify configuration to resolve the cause of fault.

subashchandran · ‎10-01-2015

Hi All,

Now the communication is fine.. APIC to F5 LTM.

I am not able to display Apic name in the F5 partition tab.

Do i need to configure self IP's manually in the F5 or driven the policy from APIC. Please confirm

mikriple · ‎10-01-2015

Hey Subash,

You will need to configure a Service Graph between EPGs with the appropriate configuration parameters in ACI that will get pushed to the F5. Once you do this, you will see configuration pushed over to the F5 as well as a new partition that gets created on the F5 with the configuration from the APIC. All configuration should be done from the APIC.

You can find a quick how to that is for the Physical F5 but will also work for the virtual F5 below:

https://www.youtube.com/watch?v=GcMBbUYFRKI

Also, if you deploy the service graph, verify that you see it under Deployed Devices and there are no faults as well as under Deployed Graph Instances and Devices Selection Policies. These can be found under Tenant>TenantName>L4-L7 Services

Mike Ripley

subashchandran · ‎10-01-2015

Hi Mike ,

I had created service graph and applied template , still not showing in the f5 partion tab.

Attached doc---following CPOC lab demo.

Also, if you deploy the service graph, verify that you see it under Deployed Devices and there are no faults as well as under Deployed Graph Instances and Devices Selection Policies. These can be found under Tenant>TenantName>L4-L7 Services

Attached xml file for your reference.

PROPERTIES

Severity:

minor

Last Transition:

2015-10-01T02:50:45.776+00:00

Lifecycle:

Raised

Affected Object:

uni/tn-TENANT-WT-COE/GraphInst_C-[uni/tn-TENANT-WT-COE/brc-F5-allow-all]-G-[uni/tn-TENANT-WT-COE/AbsGraph-F5-LTM-Service-Graph]-S-[uni/tn-TENANT-WT-COE/ctx-PN-WT-PROD]/NodeInst-ADC

Description:

Service graph for tenant TENANT-WT-COE could not be instantiated. Function node ADC configuration is invalid. Reason: No device context found for LDev

Explanation:
This fault occurs when a service graph could not be instantiated.

Recommended Action:
If you see this fault, please modify graph configuration to resolve cause of fault.

<?xml version="1.0" encoding="UTF-8"?><imdata totalCount="1"><faultInst ack="no" cause="graph-rendering-failure" changeSet="configIssues:missing-ldev-ctx, configSt:failed-to-apply, encap:unknown, funcType:GoTo, name:ADC, shareEncap:no, unkMacUcastAct:proxy" childAction="" code="F0759" created="2015-10-01T02:48:40.515+00:00" descr="Service graph for tenant TENANT-WT-COE could not be instantiated. Function node ADC configuration is invalid. Reason: No device context found for LDev" dn="uni/tn-TENANT-WT-COE/GraphInst_C-[uni/tn-TENANT-WT-COE/brc-F5-allow-all]-G-[uni/tn-TENANT-WT-COE/AbsGraph-F5-LTM-Service-Graph]-S-[uni/tn-TENANT-WT-COE/ctx-PN-WT-PROD]/NodeInst-ADC/fault-F0759" domain="tenant" highestSeverity="minor" lastTransition="2015-10-01T02:50:45.776+00:00" lc="raised" occur="1" origSeverity="minor" prevSeverity="minor" rule="vns-node-inst-node-rendering-failed" severity="minor" status="" subject="management" type="config"/></imdata>

subashchandran · ‎10-01-2015

One more question.

Do i need to change adjacency type from L2 to L3.