Page 1 of 4
EMC Knowledgebase
Knowledgebase Solution Question: Question: Question: Question: Question: Question: Question: Environment: Environment: Environment: Environment: Environment: Environment: Problem: Problem: Change: Gathering Navisphere Analyzer .NAR files and configuration information for a CLARiiON performance case Information and data files that must be obtained for a Performance Analysis on all types of CLARiiON How to gather the necessary information for a CLARiiON performance analysis What logs do I collect for CLARiiON Performance issues? What logs to collect for CLARiiON performance troubleshooting? What data to collect for CLARiiON performance troubleshooting? What do I need to submit a performance problem? Product: CLARiiON Product: VNX Family EMC SW: Navisphere Analyzer EMC SW: Unisphere Analyzer Product: Celerra NS Network Server Product: EMC Disk Library (EDL) Poor read and write performance and high response times for connected hosts. Performance problems on a CLARiiON array configuration requiring performance analysis Response times for host applications have increased or are unacceptably high. Performance Service Requests will not be fully investigated until both the SPCollects and NAR (or NAZ) files are available and a detailed description of the symptoms has been provided. The SPCollects have the configuration and fault information for the CLARiiON and the NAR files have the performance data. The detail of the performance issue symptoms is also needed so that the engineer will know which period needs to be analyzed in detail and the LUNs that had the noticeable performance impact. Without this detail, only the general performance statistics will be analyzed to look at issues affecting all LUNs. Customer Support Services investigate performance cases to identify issues that are affecting customer sites. Performance tuning (to achieve peak performance for a host or application) and reconfiguration is a task for a Storage Administrator or a Solutions Architect so this will not be handled in the Service Request. Performance issues can have a number of causes including hardware faults, forced flushing (caused by write cache being 100% full), head contention (several busy LUNs sharing the same drives), or the storage array being at its maximum utilization. For each event, Technical Support needs to know the following, in the description of the performance problem: The time (with the time zone GMT/UTC difference) and date. The server names or CLARiiON Storage Groups that own the LUNs. The LUNs that the affected application was using at that time. Is it reading or writing performance that is suffering? Obtain the basic diagnostic files that must cover the period when the problems occur: SPcollects for both Storage Processors, which were run after the problem occurred (so that their logs would include the time of the incident). See Navisphere (or Unisphere) Help article "Generating and transferring SP log files" or EMC Knowledgebase solution emc60493 for instructions on how to obtain SPcollects. Navisphere (or Unisphere) Analyzer .NAR or .NAZ files, which cover the whole period when the problem was occurring. If the problem occurs throughout the day, include NAR / NAZ files which cover a total period of at least 24 hours:
Root Cause:
http://knowledgebase.emc.com/emcice/resultDisplay2.do?result=-1&clusterName=DefaultCluster&page=&docType=1006&groupid... 7/27/2011
Page 2 of 4
Fix:
http://knowledgebase.emc.com/emcice/resultDisplay2.do?result=-1&clusterName=DefaultCluster&page=&docType=1006&groupid... 7/27/2011
Page 3 of 4
Notes:
2. 3. 4.
Go to the Analyzer menu bar in Navisphere and select Data Logging. Check that Periodic Archiving is enabled, and if not enable it. (This will create files every few hours, rather than putting all the data into a single file.) Click Start to begin the data logging. By Default this will run for 7 days before automatically stopping again. (This is the "Stop Automatically After" parameter.)
Notes:
Alternatively, the performance logging can be prepared with the following naviseccli commands for both SP:
2. 3. 4. 5.
naviseccli -h <SP A IP> setstats -on naviseccli -h <SP B IP> setstats -on naviseccli -h <SP A IP> analyzer -set -default naviseccli -h <SP A IP> analyzer -set -periodicarchiving 1
The logging can then be started on both SP with the following command, and the logging will keep running for 7 days (unless it is manually stopped again):
naviseccli -h <SP A IP> analyzer -start CLARiiON Support has a break/fix charter and we approach each performance case from that perspective. If we find that the hardware and software is operating as designed (health check) and we can find nothing broken, we will still take the next step and attempt to identify the cause. So while we can check over the logs to look for evidence of a fault or mis-configuration, we do not produce detailed performance reports in these cases. If the cause is determined to be configuration related (such as spindle overload or an under provisioned raid group), we will attempt to identify what the possible causes are, but making configuration recommendations or performance tuning would be outside of our charter. In this case, we will contact your local Account Service Representative (ASR) and copy your EMC District Service Manager to let them know that this particular issue may require additional assistance. If you require help with resolving the configuration issue(s), then Professional Services can be engaged.
Notes:
http://knowledgebase.emc.com/emcice/resultDisplay2.do?result=-1&clusterName=DefaultCluster&page=&docType=1006&groupid... 7/27/2011
Page 4 of 4
http://knowledgebase.emc.com/emcice/resultDisplay2.do?result=-1&clusterName=DefaultCluster&page=&docType=1006&groupid... 7/27/2011