CirrusProblem definition. Tenant A is deployed in Box X, Tenant B is deployed in Box Y. (L2 syncro vlan is done between the two boxes) Tenant A pings Bye and gets a response, while Tenant B pings A and gets an unreachable message. When Box Y is rebooted, everything starts to work normally for a while, but after a while the connection is lost again.
Has anyone ever encountered this problem?
Cirrushello Nikoolayy1, thanks for answer.. I found the issu. it is related with dc switch core configuration issue. wrong alarm!
MVPSo it is the directly connected switch to the F5 appliance ? Still in the future using the appliance tcpdump may show any LACP or interface issues:
Initial Setup of the rSeries Network Layer (f5.com)
MVPYou can run tcpdump on the rSeries and on the tenant to see where is the issue at the appliance or tenant level as on the appliance you will check the appliance log and on the tenant you will check the ltm and tmm logs. Maybe moving the tenant to configured state then to deployed may help as well.
Overview of the tcpdump utility on rSeries systems (f5.com)
For r4800 maybe will not possible to run tcpdump on the appliance level as r4000/2000 use SR-IOV not FPGA to directly attach the interfaces to the tenant vm.
[F5OS-A] running tcpdump in bash shell on rSeries r2000/4000
Nacreousis there any vlan that contains more than 1 interface?
and if havent, use the gui to configure the f5 netowrk etc. to see more relevant config and avoid typos.