= The error message indicates that the volume my_data_vol is WAFL inconsistent, which means that

there is a discrepancy between the data blocks and the metadata in the file system. This can be

caused by various factors, such as hardware failures, software bugs, power outages, or network

disruptions. The first action to correct this issue is to determine the root cause behind the

inconsistency before attempting any recovery procedure, as recommended by the NetApp

documentation1. This is because some recovery procedures, such as wafliron or storage takeover,

may not work or may cause further damage if the underlying cause is not resolved. For example, if

the inconsistency is due to a faulty disk or shelf, running wafliron may not fix the problem and may

even corrupt more data. Therefore, it is important to identify and isolate the cause of the

inconsistency before taking any further steps. Reference = 1 Volume Showing WAFL Inconsistent -

NetApp Knowledge Base

The error message indicates that the ONTAP Select Deploy VM cannot connect to the vCenter server

due to a network issue1.

One possible cause of this issue is that the IP address of the ONTAP Select Deploy VM is conflicting

with another device on the same network2.

To correct this problem, you need to change the IP address of the ONTAP Select Deploy VM to a

unique and valid address that can reach the vCenter server2.

You can change the IP address of the ONTAP Select Deploy VM by using the Deploy web interface or

the Deploy CLI2.

After changing the IP address, you need to restart the Deploy services and re-add the vCenter server

to the inventory2. Reference:

1: Credential authentication failed with: HostConnectionFailed, NetApp Knowledge Base

2: Changing the IP address of the Deploy VM, ONTAP Select 9 Documentation Center

The wafl.dir.size.max event occurs when a directory has reached its maximum directory size

(maxdirsize) limit, which prevents new file creation in that directory. The maxdirsize is a volume-level

option that can be modified using the volume modify command. To solve this issue, you should

increase the maximum directory size for the volume that contains the CIFS share, as long as it does

not exceed 3% of the physical memory. Alternatively, you can reorganize the directory structure to

avoid having too many files in one directory. Reference =

Max Directory size error - NetApp Knowledge Base

How to identify the target directory of wafl.dir.size.warning - NetApp Knowledge Base

Post about wafl.dir.size.max | Source.kohlerville.com

WAFL Max dirsize | uadmin

A B2B type consistency point (CP) occurs when a new CP is triggered before the previous CP is

completed, due to the second memory buffer reaching a watermark. This can cause write latency to

increase as user write operations are not replied until a write buffer frees up. However, this only

affects the aggregate that is undergoing the B2B processing, and not the other aggregates on the

same node. Therefore, the performance of the client operations on the data aggregates will not be

affected by B2B processing on the root aggregate. Reference = What is the Back-to-Back (B2B)

Consistency Point Scenario?, What are the different Consistency Point types and how are they

measured in ONTAP 9?, What are the different Consistency Point types and how are they measured?

A type B consistency point (CP) is triggered when the NVRAM buffer is full and needs to be flushed to

disk. A type B CP indicates that the write workload is higher than the disk throughput, and the

system is experiencing back pressure1

A switchless cluster is a cluster configuration that does not use external switches for cluster

interconnect and management network. A switchless cluster has lower bandwidth and redundancy

than a switched cluster, and is limited to two nodes2

The exhibit shows the output of the sysstat -x command, which displays the system performance

statistics in extended mode. The output shows that the system has high CPU utilization, high disk

utilization, high NVRAM utilization, and several type B CPs. These are signs of performance issues

and resource contention3

The best corrective action to address these consistency points is to add an additional shelf of twenty-

four 1.8 TB disks. This will increase the disk capacity and throughput, and reduce the disk utilization

and the frequency of type B CPs4

Creating additional data LIFs will not address the consistency points, because the data LIFs are used

for data access protocols, not for NVRAM flushing5

Converting the 2-node switchless cluster to a 2-node switched cluster will not address the

consistency points, because the cluster interconnect and management network are not related to

the disk performance6

Replacing the twenty-four 1.8 TB disks with twelve 4 TB disks will not address the consistency points,

because the disk throughput will not increase, and the disk utilization will remain high7

Reference:

1: Where can I learn more about Consistency Points? - NetApp Knowledge Base 2: ONTAP 9 - Cluster

and SVM Peering Express Guide - The Open Group 3: ONTAP 9 - Commands: Manual Page Reference -

The Open Group 4: ONTAP 9 - Hardware Universe - The Open Group 5: ONTAP 9 - Network

Management Guide - The Open Group 6: ONTAP 9 - Clustered Data ONTAP Concepts Guide - The

Open Group 7: ONTAP 9 - Logical Storage Management Guide - The Open Group