Volume high latency caused by misconfigured FPolicy

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 393

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: perf

Last Updated:

Applies to

ONTAP 9
FPolicy

Issue

High latency is seen via AIQUM and CLI

AIQUM display volume latency is high.

CLI display high latency from Network

::> qos statistics volume latency show
Workload            ID    Latency    Network    Cluster       Data       Disk        QoS      NVRAM      Cloud  FlexCache    SM Sync
--------------- ------ ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------
-total-              -   367.00ms   355.00ms     3.00us   161.00us        0ms        0ms     0.00us        0ms        0ms        0ms
volum-wid30897   30897   372.00ms   360.00ms        0ms   152.00us        0ms        0ms     0.00us        0ms        0ms        0ms
-total-              -   363.00ms   353.00ms     5.00us   151.00us     8.00us        0ms     0.00us        0ms        0ms        0ms
volum-wid30897   30897   351.00ms   350.00ms        0ms   149.00us     8.00us        0ms     0.00us        0ms        0ms        0ms

EMS event for fpolicy.server.connectError stating that the TCP Connection to the FPolicy server failed:

Wed Dec 01 13:37:32 +0800 [cluster_n01: fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server "xx.xx.xx.xx" (reason: "TCP Connection to FPolicy server failed.").

Disabling the Fpolicy the latency is back to expected values.