Exist AFF-A800 IP Metrocluster with Juniper switches as cluster network. Why Juniper? Because Cisco switches aren't available in next couple months.
The metrocluster has problem: When write-traffic periodically increase - latency dramatically jump. Our network engineers can't exactly translate settings for Cisco switches to settings for Juniper switches because they have a different set of settings for traffic priority.
I suppose that we can chance to find root of problem if we collect traffic dump for investigation. Question: How I can collect tcpdump on ip metrocluster fabric interfaces (e0b, e1b)? These interfaces are hidden in ONTAP.
It may be possible from the BSD layer, but I would recommend opening a case with Support. Make sure you tag this as a Metrocluster issue. If you mention slowness it will go to us in the Perf team and we will have to engage MCC folks. At the very least we could see if we could run tcpdump for those interfaces.
I am unable to find any documentation that we have tested the specific model switch Juniper QFX5120 for any of our configurations. We are more strict as to which switch vendors and models are capable and supported for Cluster communication compared to client-access switches.
Please continue to work this issue through the Support case and/or your Account Team as those are the correct avenues to get the Juniper QFX5120 working.