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.
In order to make sure you know what error code is returned from the controller at that point of time and eliminate any memory related problems, you could try performing the following steps:
1) Enable xml logging ----> dfm options set xmllogenabled=yes 2) Run a dfm host discover against the controller. 3) Check for the 'xml' trace.log for that controller, check for the 'perf-object-get-instances-iter-start' zapi and verify for the response from the controller.
You would need to run these steps when you hit the issue. So that you can correlate the logs with the timestamp the zapi was issued.
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.