Collect diagnostic information from AIX and PowerVM

Utilize the NetApp nSANity tool that comes in one of two formats, a Windows based GUI tool and a command line tool, available for both Windows and BASH command lines. AIX hosts need to have data gathered from any host needing analyzed that has SAN access. If the LPAR is a PowerVM guest partition, the information will need to be gathered from the PowerVM hosts through hwich the LPAR makes connection to the SAN. If the LPAR accesses the SAN through hdisks presented through vSCSI, it is still reccomended to gather LPAR data in addition to the PowerVM hosts. In the GUI tool, you will need to populate each of the fields appropriate toRead More

Guest OS tunings for a VMware vSphere deployment

One of the important considerations for deploying NetApp storage to interoperate effectively with the VMware ESX/ESXi guest operating systems in a SAN/NFS environment is to utilize the NetApp recommended guest OS tunings in the virtual machines. This article describes the guest OS tunings utilized and the settings recommended by NetApp to help improve interoperability. The article also describes the purpose of updating guest OS tunings from the previous settings and provides guidance on adopting the updated guest OS tunings. Why are guest OS tunings required? The following are some reasons why guest OS tunings are required: To help improve error handling and interoperability during storage controller failover events. To improve recoveryRead More

FAS2240, special attention needed

The 2240 controller module has two onboard 6GB SAS ports, 0a and 0b, with the 0b port being on the left of the controller module. This is a change from standard NetApp badging, which follows a left to right naming convention. The SAS cable routing rules require that the square port be located on the left and the circle port be located on the right, with the circle being connected to the top of the storage stack. In the case of the 2240 series, the 0a port functions as an expander for the internal disks and therefore must be connected to the top of the stack, leaving it as the circle port.

Performance Troubleshooting 7-Mode

QoS is not available in Data ONTAP 7-Mode systems; however, you can still collect some CLI data to review your current issue. Before you get into reviewing data, here are some common areas that might be beneficial: My CPU is high – is this bad? For more information, see article 3014056: What does high CPU utilization indicate? Why are my HDDs busy? For more information, see the HDD Latency Troubleshooting article – 1014701: How to assess disk-level response times Some users are seeing slowness accessing shares: FPOLICY Troubleshooting article – 1013400: How to troubleshoot pBlk exhaustion due to Fpolicy Server VSCAN Latency troubleshooting article – 1013401: Data ONTAP 7 or Data ONTAP 8-7 Mode: HowRead More

Performance Troubleshooting Clustered ONTAP

A simple rule of thumb: If a particular system or application is running slower than you expect, or slower than it has historically, it might be a performance issue. However, if a particular system or application is not working at all, it is likely not a performance related issue. The recommended method for monitoring performance in a Cluster Data ONTAP system is to use volume workloads. You can use the commands below to help determine where your issue might reside. The following is a review of the commands above, and a look at how to use/interpret them: Use the preceding command to view overall latency on volume workloads and getRead More