Skip to main content
NetApp Knowledge Base

DR CONFIG REPLICATION FAILED: Data-fpolicy-client cannot be added to service policy

  1. Last updated
  2. Save as PDF
Views:
272
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • 2 Node MetroCluster
  • Automatic Non-Disruptive Upgrade (ANDU)
  • ONTAP 9.8

Issue

After upgrading the first node in a 2 node MetroCluster to ONTAP 9.8+, errors similar to the below are observed:
 
                              Cluster  : ClusterA
                              Vserver  : vs-cifs01
                      Partner Vserver  : vs-cifs01-mc
                  Configuration State  : degraded
                        Stream Status  : processing-task
                            Failed Row : Table Name: vs_service_policies_view, Operation: get, Fields: vs-cifs01-mc 
                                         default-data-blocks data-core data-iscsi data-fpolicy-client - "data-core: 
                                         0.0.0.0/0" "data-iscsi: 0.0.0.0/0" "data-fpolicy-client: 0.0.0.0/0" 7 - true
                         Failed Reason : Apply failed for Object: vs_service_policies_view Method: baseline. Reason: 
                                         Internal error. Failed to update service policy "default-data-blocks". Reason: 
                                         Service "data-fpolicy-client" cannot be added to service policy 
                                         "default-data-blocks" because the service is not known to the cluster. Use 
                                         the "network interface service show" command to review available services. Use 
                                         the "network interface service-policy show" command to review the state of the 
                                         policy. Retry the command, if necessary.
                 Last apply fail time  : 3/29/2020 12:25:41

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.