DefendX Fpolicy server is not staying connected
Applies to
- ONTAP 9+
- Superna DefendX
Issue
- Network connection between ONTAP and DefendX server is not staying connected.
- There are indications that connections are occurring successfully but are not remaining connected.
::> vserver fpolicy show-engine
(vserver fpolicy show-engine)
Vserver Policy Name Node FPolicy Server Server Status Server Type
------- ------------- ------------ ----------------- -------------- -----------
vserver
DefendX_Control_QFS
nodea x.x.x.x disconnected primary
vserver
DefendX_Control_QFS
nodeb x.x.x.x disconnected primary
2 entries were displayed.- fpolicy-mlog:
00000014.0036e723 07ea64ab Thu Jan 30 2025 21:17:50 +00:00 [kern_fpolicy:info:7767] Establish TCP connection was successful.[0x0x8066a4400] src/fsm/fsm_external_engine.cc:5077
00000014.0036e724 07ea64ab Thu Jan 30 2025 21:17:50 +00:00 [kern_fpolicy:info:7767] Hand Shake with Version [1.0]. src/fsm/fsm_schemas.cc:1506
00000014.0036e725 07ea64ab Thu Jan 30 2025 21:17:50 +00:00 [kern_fpolicy:warning:7767] Fpolicy server : Handhshake successful for XML format
00000014.0036e726 07ea64ab Thu Jan 30 2025 21:17:50 +00:00 [kern_fpolicy:info:7767] FPolicy handshake was successful.[0x0x8066a4400] src/fsm/fsm_external_engine.cc:5087 - Followed by:
00000014.0036e72a 07ea64ab Thu Jan 30 2025 21:17:51 +00:00 [kern_fpolicy:error:7767] Read returned error with errno[4] [0x0x8066a2f00] src/fsm/fsm_external_engine.cc:1075
00000014.0036e72b 07ea64ab Thu Jan 30 2025 21:17:51 +00:00 [kern_fpolicy:error:7767] readMsg returned error while reading the message length response from FPolicy server [0x0x8066a2f00] src/fsm/fsm_external_engine.cc:6811
00000014.0036e72c 07ea64ab Thu Jan 30 2025 21:17:51 +00:00 [kern_fpolicy:info:7767] [virtual smdb_error fpolicy_appcfg_server_status_db_iterator::notify_imp(smdb_cdb_iterator::operation)] operation: [modify], policy: [76]
00000014.0036e72d 07ea64ab Thu Jan 30 2025 21:17:51 +00:00 [kern_fpolicy:info:7767] updateStatusTable[disconnect]:: Modified entry vs[3] policy[DefendX_Control_QFS] server[x.x.x.x] [0x0x8066a2f00] src/fsm/fsm_external_engine.cc:5012
00000014.0036e72e 07ea64ab Thu Jan 30 2025 21:17:51 +00:00 [kern_fpolicy:info:7767] Server DISCONNECTED with retVal = 9329. [0x0x8066a2f00] src/fsm/fsm_task.cc:2668
00000014.0036efab 07eab91e Thu Jan 30 2025 21:53:51 +00:00 [kern_fpolicy:info:7767] [virtual smdb_error fpolicy_appcfg_server_status_db_iterator::notify_imp(smdb_cdb_iterator::operation)] operation: [modify], policy: [76]
00000014.0036efac 07eab91e Thu Jan 30 2025 21:53:51 +00:00 [kern_fpolicy:info:7767] Server state changed to 5. [0x0x80728a700] src/fsm/fsm_task.cc:466
000000014.0036efad 07eab91e Thu Jan 30 2025 21:53:51 +00:00 [kern_fpolicy:error:7767] connect failed. errno = 61 [0x0x8066a4400] src/fsm/fsm_external_engine.cc:5429 - Audit-mlog:
00000015.02ccf216 07ea32ae Thu Jan 30 2025 21:17:48 +00:00 [kern_audit:info:3528] 8503e8000017cdb6 :: cluster:ontapi :: x.x.x.x:54272 :: vserver:domain\user :: <netapp nmsdk_language="C" nmsdk_platform="Windows Server 2019 Standard AMD64" version="1.15" xmlns="http://www.netapp.com/filer/admin" nmsdk_version="9.8P3" vfiler="vserver"><fpolicy-enable-policy><policy-name>DefendX_Control_QFS</policy-name><sequence-number>10</sequence-number></fpolicy-enable-policy></netapp> :: Pending:
00000015.02ccf219 07ea32ae Thu Jan 30 2025 21:17:48 +00:00 [kern_audit:info:3528] 8503e8000017cdb6 :: cluster:ontapi :: x.x.x.x:54272 :: vserver:domain\user :: fpolicy-enable-policy :: Success:
00000015.02ccf229 07ea32ae Thu Jan 30 2025 21:17:50 +00:00 [kern_audit:info:3528] 8003e8000007e192:8003e8000007e194 :: cluster:ssh :: 30.58.208.207:42612 :: cluster:admin :: Logging out :: Success
00000015.02ccf233 07ea32ae Thu Jan 30 2025 21:17:50 +00:00 [kern_audit:info:3528] 8503e8000017cdbf :: cluster:ontapi :: x.x.x.x:54277 :: vserver:domain\user :: <netapp nmsdk_language="C" nmsdk_platform="Windows Server 2019 Standard AMD64" version="1.15" xmlns="http://www.netapp.com/filer/admin" nmsdk_version="9.8P3" vfiler="vserver"><fpolicy-server-connect><policy-name>DefendX_Control_QFS</policy-name><server>x.x.x.x</server><node>nodea</node></fpolicy-server-connect></netapp> :: Pending:
00000015.02ccf235 07ea32ae Thu Jan 30 2025 21:17:50 +00:00 [kern_audit:info:3528] 8503e8000017cdbf :: cluster:ontapi :: x.x.x.x:54277 :: vserver:domain\user :: fpolicy-server-connect :: Error: The specified server "x.x.x.x" is already connected.
00000015.02ccf238 07ea32ae Thu Jan 30 2025 21:17:50 +00:00 [kern_audit:info:3528] 8503e8000017cdc1 :: cluster:ontapi :: x.x.x.x:54278 :: vserver:domain\user :: <netapp nmsdk_language="C" nmsdk_platform="Windows Server 2019 Standard AMD64" version="1.15" xmlns="http://www.netapp.com/filer/admin" nmsdk_version="9.8P3" vfiler="vserver"><fpolicy-server-connect><policy-name>DefendX_Control_QFS</policy-name><server>x.x.x.x</server><node>nodeb</node></fpolicy-server-connect></netapp> :: Pending:
00000015.02ccf23a 07ea32ae Thu Jan 30 2025 21:17:50 +00:00 [kern_audit:info:3528] 8503e8000017cdc1 :: cluster:ontapi :: x.x.x.x:54278 :: vserver:domain\user :: fpolicy-server-connect :: Error: The specified server "x.x.x.x" is already connected. - Occurs on multiple clusters running the same version of ONTAP as well as the same version of DefendX.
- Does not occur on all Vserver nor does it happen all the time when doing the initial connection