NetApp Manageability SDK 5.2 includes the following known issues:
Problem:If you try to save two custom workflows with the same name and in the same path, ZEDI stops working.
Workaround:Create unique names for the custom workflows.
Problem:If you add a new API to a node by using the Workflow tab, the new API name is not displayed in the node. However, the new API is added to the XML request and in the Added API tab. The Workflow tab does not show the asterisk (*) in the unsaved workflow name.
Workaround:Save the workflow at regular interval to let the new API nameappear in the node.
Problem:ZEDI stops working or complete XML output is not displayed when the application runs out of maximum allocated heap memory of 1 GB.
Workaround:
Scenario 1: If you have enabled the “Enable iterator comprehension” option, and if you have used *-iter-start APIs in the workflow, then increase the “Iterator Fetch Size” to a very high value, such as 10000, and reexecute the workflow.
Note: This is applicable for Data ONTAP 7-Mode APIs and OnCommand Unified Manager APIs.
Scenario 2: If you were running zexplore.jar, rerun it and enter the following command to increase the maximum heap size from the allocated 1 GB:
java –Xmx<memory_size> -jar zexplore.jar
Example: java –Xmx1536M -jar zexplore.jar
Scenario 3: If the workflow contains APIs that results in large data, split the workflow into smaller units and run them individually.
Scenario 4: If none of the above scenarios is applicable, exit and execute the workflow again.