Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Software Development Kit (SDK) and API Discussions

Calling ZAPI “file-assign-qos” results high CPU utilization


The information is as below and you can also find case in attached link


Case Number: 2005519142

Company Name: SoFu

Case Priority: P3

Customer Region (State/Country/Timezone): Korea

Problem description:

The customer is using ZAPI file-assign-qos to configure QoS policy on this CDOT system(FAS8060 with full SSD).

They observed that calling ZAPI file-assign-qos results high CPU utilization only in the node1(Node2 is working well).

 The following perfstat captured above behavior.



NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner