Frequent fpolicy disconnection errors seen in EMS logs
Applies to
- Ontap 9
- Fpolicy
Issue
- Frequent fpolicy disconnection & connection errors are reported.
- Below messages observed in EMS logs.
Fri Aug 02 16:51:44 +0000 [node-01: fpolicy: fpolicy.server.maxPendingReq:info]: Maximum outstanding requests for the FPolicy server "10.xx.0.xxx" has reached.
Fri Aug 02 16:52:46 +0000 [node-01: fpolicy: fpolicy.server.disconnect:error]: Connection to the FPolicy server "10.xx.0.xxx" of policy "CVXXX" is broken for Vserver svm_01 ( reason: "Server progress timeout is hit." ).
Fri Aug 02 16:52:58 +0000 [node-01: fpolicy: fpolicy.server.connect:notice]: Control channel with the FPolicy server "10.xx.0.xxx" of policy "CVxxx" is established for Vserver svm_01.
- No changes done on Ontap end.
- The external fpolicy server is not responding in a timely manner and a timeout is triggering, which causes Ontap to disconnect and reconnect.
-
When disconnect occurs, a automatic reconnect is triggered immediately, so from that standpoint the disconnect is not a problem exactly.