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

How to non-disruptively create a new root aggregate

This article describes the procedure that should be followed to create a new root aggregate non-disruptively and have it host the root volume in clustered Data ONTAP 8.2 and 8.3 and ONTAP 9.0systems. This feature allows the root aggregate to be hosted on a thin partition using disks that are shared for data aggregates. On system initialization, 12-24 disks are divided into a large ‘P1’ partition for data and into a small ‘P2’ partition for the root. Only re-initializing each node (option 4) will place the root aggregate onto shared disks and it is not possible to do this non-disruptively. However, it is possible to non-disruptively move the root volume off ofRead More

How to capture packet traces (PKTT)

It is important to specify -d /etc/crash in the pktt commands so that the traces are saved to disk and in a location that is easy to access.  If you do not specify the -d option, the traces will only be written to disk if you use the pktt dump command. The pktt start all command starts capturing packets on all physical and VLAN ports that are online. Examples: ::> node run -node <node_name> pktt start all -i <ip_addr> -i <ip_addr> -i <ip_addr> -d /etc/crash This will start a packet trace on all interfaces on the node specified, and will capture any packet that has a source or destination of one of the IPs specified withRead More