F5 Viprion and Cisco vPC design
Hello,
We are facing an issue it seems with our data center design. The design is really simple and straight forward.
We have 2 F5 Viprion chassis connected to the access layer in the data center. The access layer is hosted on N9K. The core is N7K.
Added drawing
So chassis 1 forms a vPC with the N9K1 and N9K2, chassis 2 forms a vPC with the N9K3 and N9K4. This connection is fully LACP.
interface port-channel141
description F5 Viprion 1 - 4*10G - vPC channel
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 310,312,410-415
spanning-tree port type edge trunk
spanning-tree bpduguard disable
spanning-tree guard root
spanning-tree bpdufilter disable
logging event port link-status
logging event port trunk-status
storm-control broadcast level 80.00
storm-control multicast level 80.00
lacp mode delay
vpc 141
This is an example on how the port-channel towards the F5 is configured. It uses LACP mode delay so it will await the LACP negotiation from the viprion i suppose.
The problem is that when we access an application that is hosted on the F5, the throughput is really low. So for example: A remote desktop application will only achieve 5Mbps when pushed throught the F5, a remote desktop application straight to the server will achieve 70Mbps. Please note that the server is also behind another 9K ToR setup. So the problem only occurs when we push traffic through the F5. It also has an issue with a sharepoint server that is connected and only gets 40KBps of download speed.
We also see that traffic entering the physical interfaces on the F5 is experiencing some drops. Screenshot included.
My guess is that there is a problem between the F5 and the Nexus, is there documentation on how this is setup the best way? F5 only has this: https://support.f5.com/csp/article/K13142
The configuration on the trunk towards the nexus is :
LACP Enabled LACP Mode Active LACP Timeout set to log Link selection policy bandwidth Frame Distribution Hash Source/Destination IP address port
An engineer from F5 is tasked to look at the F5 but is not finding anything.