F5 Viprion and Cisco vPC design

Hello,

Thanks for this document. However it does not seem to contain any information on how he Viprion is set up on the N9K.

What supposed to be the MTU size between the devices etc. I did notice that 1 viprion chassis in Active and the other one is in Standby. In our design both chassis are active active and the VCMP's are spread across the 2 chassis's.

Also we have no lldp enabled on the ports towards the F5 from the nexus.

I noticed in the CLI that the physical interface of the F5 towards the Nexus has an MTU of 9198. The Nexus has an MTU of 1500 configured on the LACP port-channel, however the vlan's that are configured on the Viprion are also 1500.

A portion of our DMZ setup is also connected with 40Gig to the Viprion with a Cisco Cat 6500 and there are no issues. It really looks like a vPC specific towards the Viprion

Please clarify some things, 1. VCMPs: Is your chassis serving as an hypervisor for multiple VCMP guests? 2. Active active: are the boxes standalone or in sync in an active-active HA scenario?

make the MTUs match on the devices. nexus support Jumbo MTUs(above 9000).

Hello,

YEs the F5 are hosting multiple VCMP's, in short we host VCMP's for our corporate environment and we host VCMP's for our DMZ environment.

They had a wonderful idea to have the VCMP's on the corp to be active on 1 chassis and the VCMP's of the DMZ to be active on another chassis.

This leads me to question nr2

IF you login into the viprion, you can directly note that they are standalone mode. I think they have done for the above reason, however i am not sure why and if that will work.