You are on page 1of 7

The following is a Primus(R) eServer solution: ID: emc161922 Domain: EMC1 Solution Class: 3.

X Compatibility Goal Gathering Navisphere Analyzer .NAR files and configuration information for a CLARiiON or VNX performance case Goal Information and data files that must be obtained for a Performance Analysis on all types of CLARiiON arrays Goal How to gather the necessary information for a CLARiiON or VNX performance analysis Goal What logs do I collect for CLARiiON or VNX performance issues? Goal What logs to collect for CLARiiON or VNX performance troubleshooting? Goal What data to collect for CLARiiON or VNX performance troubleshooting? Goal What do I need to submit a performance problem? Fact Product: CLARiiON Fact Product: VNX Series Fact EMC SW: Navisphere Analyzer Fact EMC SW: Unisphere Analyzer Fact Product: Celerra NS Network Server Fact Product: EMC Disk Library (EDL) Symptom Poor read and write performance and high response times for connected hosts. Symptom Performance problems on a CLARiiON array configuration requiring performance analysis Change Response times for host applications have increased or are unacceptably high. Cause 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.  See Navisphere (or Unisphere) Help article "Generating and transferring SP log files" or:    See EMC Knowledgebase article emc60493 for instructions on how to obtain SPcollects on a CLARiiON running Navisphere. or the storage array being at its maximum utilization.  . See EMC Knowledgebase article emc253191 for instructions on how to obtain SPcollects on a VNX or CLARiiON running Unisphere.NAR or . which cover a total period of approximately 24 hours:  NAR and NAZ files contain the same data. include NAR / NAZ files. 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. which were run after the problem occurred (so that their logs would include the time of the incident). but usually a performance analysis will concentrate on a single NAR file which contains the most relevent data.NAZ files. to assist with break/fix performance diagnostics. Performance issues can have a number of causes including hardware faults. If the CLARiiON has an Analyzer license ('-NavisphereAnalyzer' in the software list) then NAR files will be produced. Uploading more NAR files than are needed can allow support to get more background information to an issue and see if it has been going on for some time. 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. Navisphere (or Unisphere) Analyzer . Fix For each event. NAZ files are for use by EMC support only. but only NAR files can be opened in Navisphere / Unisphere Analyzer. If the problem occurs throughout the day. 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. otherwise data logging produces NAZ files. The server names or CLARiiON Storage Groups that own the LUNs. Customer Support Services investigate performance cases to identify issues that are affecting customer sites. which cover the whole period when the problem was occurring. forced flushing (caused by write cache being 100% full). head contention (several busy LUNs sharing the same drives).

highlight the Monitoring Tab and select Analyzer. use the following command: naviseccli ~ analyzer -set -narinterval 120 (where ~ would be where the arguments -h <IP address>. in which case the interval would need to be set to a higher interval. such as 240 seconds. To change the archive interval in Unisphere for a CX4. may need to included) The archive interval should be set to 120 or 60 seconds. the folders under the taskbar at the top should be listed as: This_VNX > System > Monitoring and Alerts > Statistics for Block Click on the 'Performance Data Logging' link. However. performance problems which only lasted a few minutes. Before starting the data logging. These can later be merged together. in order the produce a detailed record of performance. Therefore if the archive polling interval was set at 600 seconds. -user <username> etc. in the Navisphere Analyzer menu. To change the archive interval in Navisphere. if the archive polling interval was 120 seconds. large configurations may take longer than 60 or even 120 seconds to poll. it will be closed and a new one started. Click on Monitoring and Alerts Statistics for Block In other words. Therefore. To change the archive interval in Unisphere for a VNX:     After selecting the VNX system.      To change the archive interval using the CLI. in order to produce graphs covering a longer period. Click on the 'Performance Data Logging' link. there would be 5 hours and 10 minutes of data in each file. the archive interval should be set appropriately:  A typical NAR (or NAZ) file will contain 155 polling intervals of data. The results recorded will be averages of the performance over archive intervals. would be hard to diagnose For Flare release 22 and earlier. go to the Data Logging window. Once each file is full. click on the System Tab. you will need to be in Engineering Mode to change the Archive Interval (see emc255033)     To start data logging: .

From this drop-down menu. select Tools -> Analyzer -> Data Logging. select the correct VNX then go to > System > Monitoring and Alerts > Statistics for Block. If the archive interval needs changing.   In Navisphere Manager.  Therefore the list of NAR files will only include the files which have been completed (which normally happens when there are 155 polling intervals contained in them). Make sure the correct CLARiiON is selected (in the 'Target' box). Alternatively the following CLI command will start a new NAR file and make the latest NAR file available to download (although you may need to wait for a minute or so for it to be closed):  naviseccli ~ analyzer -archive -new (where ~ would include the SP IP address and the Navisphere login)    To retrieve the completed archives (after they have had time to gather sufficient information and the performance issues were occurring during this period):  In Unisphere (Release 30 and above):   Click on the CLARiiON which is to be monitored from the Unisphere Dashboard. select Analyzer. Highlight the 'Monitoring' box and a drop-down menu will appear. In CX4 Unisphere. . Click on the 'Performance Data Logging' link. change the value. for Flare release 22 and earlier. then click on the start button (this is for Flare release 24 and higher. Click on the 'Performance Data Logging' link. you start analyzer by enabling "Statistics Logging") Alternatively use the following CLI command: naviseccli ~ analyzer -start (where ~ would include the SP IP address and the Navisphere login)     A NAR (or NAZ) file will not be available to download while it is still open for data logging. which will close the current NAR file and then start a new one. the data logging can be stopped and then started again. For a VNX. click on the stop button. then click on start. To obtain the latest data. not the latest file. highlight the Monitoring Tab and select Analyzer.

the archive file which is currently being logged to will not be shown. In Navisphere Manager (Release 24 to 29):      Select Tools -> Analyzer -> Archive -> Retrieve Make sure the correct CLARiiON is selected. stop and then start the data logging (allow each file to run for at least ten times the logging period). then the NAR/NAZ files can be transferred directly from C:\EMC\Archives folder. Select the relevant archives and click Retrieve. Repeat for SP B.    Select SP A. Upload files to Powerlink in the same form that they were produced on the SP. It is important to stress that the Navisphere files have to be for the period when the problems were actually occurring.   Alternatively use the following CLI command to retrieve all the archives from one SP: naviseccli -h <SP IP> analyzer -archive -all If you have remote access to the SP. To close the current file and start and new one. Do not merge NAR files and do not decrypt NAZ files.    Do not use the 'naviseccli ~ analyzer -archiveretrieve' in Release 24 or higher. followed by 'Analyzing storage-system performance using Analyzer'    . For Release 22 and below. see article emc227465. Select SP A. Select the relevant archives and click Retrieve.see emc240526 The NAR/NAZ file title contains the date and time (in GMT) of the last data point logged. Any changes to the files can introduce errors. via EMC Remote or Remotely Anywhere. Select 'Help topics'. A guide to running Navisphere Analyzer can be found by going to 'Help' in Navisphere. For Flare release 24 and higher. Instead use 'naviseccli ~ analyzer -archive <-all or -file filenames> . so it is important that the original files are supplied. Repeat for SP B. (Flare release 24 and higher) See article emc255033 for further information on using Navisphere / Unisphere to collect NAR/NAZ files.

Follow the README file to run the utility for the host operating system chosen.) Note If no recent NAR or NAZ files have been produced and the CLARiiON is running Release 24 or higher core software.emc. . Release 24 does not require an enabler to gather performance information. The enabler will appear as the following in Navisphere (right-clicking the CLARiiON array -> Properties -> Software): -NavisphereAnalyzer For an intermittent problem in FLARE pre-Release 24. especially if the performance problem only exists on certain paths. these grabs can be downloaded from ftp://ftp. To start Data Logging: Go to the Analyzer menu bar in Navisphere and select Data Logging. titled: 'EMC® Navisphere® Analyzer Command Line Interface (CLI)'.NAZ) if the latest enabler is not present. then the data logging has not been started. until you find your operating system utility. Select Next.  Select this link to Powerlink and then follow this path to the emcgrab/EMCREPORTS host utility downloads: Home > Support > Product and Diagnostic Tools > Grab Utilities. it is possible to script the archive retrieval to store the archives. Arrays running any Release of FLARE from 14 to 22 will need a Navisphere Analyzer Enabler loaded. Therefore. Please refer to the following EMC knowledgebase articles based on the model switch being used:    McDATA: emc92923 or emc86536 Brocade: emc42373 Cisco: emc97851 or emc102214 Note Release 24 and later stores the old archives but encrypts them (. (See solution emc148982.com/pub/emcgrab/    Switch logs may be needed. Alternatively.  Host Grab (or EMC Report) output files from the affected hosts. Download the utility and the README file. A guide to using Naviseccli for retrieving NAR files can be found on Powerlink.

we will still take the next step and attempt to identify the cause. By Default this will run for 7 days before automatically stopping again. we do not produce detailed performance reports in these cases. (This is the "Stop Automatically After" parameter. If the cause is determined to be configuration related (such as spindle overload or an under provisioned raid group). rather than putting all the data into a single file. 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. then Professional Services can be engaged. If we find that the hardware and software is operating as designed (health check) and we can find nothing broken. If you require help with resolving the configuration issue(s).) Click Start to begin the data logging. and the logging will keep running for 7 days (unless it is manually stopped again):  naviseccli -h <SP A IP> analyzer -start Note CLARiiON Support has a break/fix charter and we approach each performance case from that perspective. (This will create files every few hours. .) Alternatively. In this case. the performance logging can be prepared with the following naviseccli commands for both SP: 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. but making configuration recommendations or performance tuning would be outside of our charter. we will attempt to identify what the possible causes are. So while we can check over the logs to look for evidence of a fault or mis-configuration. and if not enable it.Check that Periodic Archiving is enabled.