Skip to main content

How FPolicy works

Before you plan and create your FPolicy configuration, you should understand the basics of how FPolicy works.

  • What the two parts of the FPolicy solution are
    There are two parts to an FPolicy solution. The ONTAP FPolicy framework manages activities on the cluster and sends notifications to external FPolicy servers. External FPolicy servers process notifications sent by ONTAP FPolicy.
  • What synchronous and asynchronous notifications are
    FPolicy sends notifications to external FPolicy servers via the FPolicy interface. The notifications are sent either in synchronous or asynchronous mode. The notification mode determines what ONTAP does after sending notifications to FPolicy servers.
  • Roles that cluster components play with FPolicy implementation
    The cluster, the contained storage virtual machines (SVMs), and data LIFs all play a role in an FPolicy implementation.
  • How FPolicy works with external FPolicy servers
    After FPolicy is configured and enabled on the storage virtual machine (SVM), FPolicy runs on every node on which the SVM participates. FPolicy is responsible for establishing and maintaining connections with external FPolicy servers (FPolicy servers), for notification processing, and for managing notification messages to and from FPolicy servers.
  • What the node-to-external FPolicy server communication process is
    To properly plan your FPolicy configuration, you should understand what the node-to-external FPolicy server communication process is.
  • How FPolicy services work across SVM namespaces
    ONTAP provides a unified storage virtual machine (SVM) namespace. Volumes across the cluster are joined together by junctions to provide a single, logical file system. The FPolicy server is aware of the namespace topology and provides FPolicy services across the namespace.