To gather SP Collect from SP A, run the following commands navicli h xxx.xxx.xxx.

xxx spcollect messner Wait for 5 to 7 mins navicli h xxx.xxx.xxx.xxx managefiles list The name of the SP Collect file will be SerialNumberOfClariion_spa_Date_Time_*.zip navicli h xxx.xxx.xxx.xxx managefiles retrieve where xxx.xxx.xxx.xxx is the IP Address of SP A For SP B, similar process like above, the name of the file you will be looking for is SerialNumberOfClariion_spb_Date_Time_*.zip Where xxx.xxx.xxx.xxx will be the IP Address of SP B Why should I run a SP Collect on my storage? SP Collect information is very important with troubleshooting the disk array and will give the support engineer all the necessary vital data about the storage array (environment) for troubleshooting. The following data that is collected using the SP Collects from both the SPs:

Ktdump Log files iSCSI data FBI data (used to troubleshoot backend issues) Array data (sp log files, migration info, flare code, sniffer, memory, host side data, flare debug data, metalun data, prom data, drive meta data, etc)

PSM data RTP data (mirrors, snaps, clones, sancopy, etc) Event data (windows security, application and system event files) LCC data Nav data (Navisphere related data)