Está en la página 1de 8

323906703.doc (273.

00 KB)
7/15/2016 2:01 PM
Last saved by Rosslyn Bradley

Test /Acceptance Criteria (TAC) for Implementation (was EIP-2)


.1

cnhck040_R035

Once the array has been completely configured and all servers are connected to it, you can proceed
with the remainder of the TAC Checklist. This process is divided in 3 categories:
The CLARiiON array

P Done

The attached servers


The switches
Requirements (if not already done):
Obtain and install the latest version of the CAP2 program on your laptop. The CAP2 program can
be downloaded from the EMC Services Partner Web via PowerLink
If necessary, download EMCGrab and/or EMCReports from the EMC Services Partner Web via
PowerLink.
NOTE: EMCGrab is for Solaris, Linux, HP-UX, AIX, and Tru64 hosts. EMCReports is for Windows
platforms.
If you will be using the High Availability Validation Tool (HAVT) to verify the high-availability of hosts,
then download the Server Utility for those host operating systems that you will be checking. Notes:
you must use the 6.22.20 or later version of the server utility
the utility has to be installed on each host
6.22.20 and later versions can co-exist with a host agent
Ensure you have a Windows management station or laptop with IP connectivity to both SPs.
Verify connectivity by performing a ping command to both SPs.
Note: If CAP2 experiences difficulty retrieving SP collects, try disabling the firewall protection software,
or any other installed firewall software, before concluding that CAP2, navicli, or SPcollect is failing.
Most firewalls block the ports that CAP2 uses to contact CLARiiON storage processors (SPs), hosts,
and switches. Refer to EMC Knowledgebase article emc115946.
.2

Host High Availability Validation

If you are running HAVT on the hosts, then:


.a Install the Navisphere Server utility on each host.
.b cd into the directory where the utility gets installed:
HP-UX, Solaris, Linux: /opt/Navisphere/bin
AIX:/usr/lpp/HOSTUTIL
Windows:c:\programfiles\emc\navisphereserverutility
.c Run the following command to run the utility and push the resulting file to the array:
HP-UX, Solaris, AIX:
./naviserverutilhavuploadip<SPIPaddress>user<username>password
<password>scope<0or1>(where0=global,1=local)output<directory&
filenameonhostforoutputifrequired>

Linux:
./naviserverutilclihavuploadip<SPIPaddress>user<username>password
<password>scope<0or1>(where0=global,1=local)output<directory&

323906703.doc (273.00 KB)


7/15/2016 2:01 PM
Last saved by Rosslyn Bradley
filenameonhostforoutputifrequired>

Windows CLI:
naviserverutilclihavuploadip<SPIPaddress>user<username>password
<password>scope<0or1>(where0=global,1=local)output<directory&
filenameonhostforoutputifrequired>

The pushed file(s) will be gathered by SPCollect and the data included in the CAP2 review.
.d If you wish to run the utility just to generate a report and view the output, then run the following
command:
HP-UX, Solaris, AIX: ./naviserverutil
Linux: ./naviserverutilcli
Windows CLI: naviserverutilcli
and select option 3.
A summary report is displayed and an xml file generated which can be viewed using a browser.
Windows GUI: naviserverutil
and follow the prompts on the screen.
.3

Running the TAC procedure

.a Start CAP2
.b Select Tools Service Workbench CLARiiON Configuration Review.
.c In the CLARiiON Configuration Review Wizard dialog, perform the following:
Under User Registration, select the appropriate type of engagement from the drop-down
menu.
Enter the engagement number, your name, email address, and company name.
Under Site Registration, enter the site ID and site name.
Select New Install from the Activity Type drop-down menu.
Enter any remarks.
Click Next.
.d The Max Run Time is the approximate time that the wizard will run. The minimum is 10 minutes
because it assumes that SPCollect may run for 10 mins. The remainder (30 - 10) is the amount of
time that FBI monitoring will run (if selected).
.e When SPCollect starts to run it uses the No Progress Timeout to make sure that the CAPTURE
process changes from one stage to the next within this time, or it aborts automatically.
The Check Interval is the time used between checking for progress during the SPCollect capture
process.

Adjust Max Run Time if required.


Adjust No Progress Timeout if required.
Adjust Check Interval if required.
NOTE: It is recommended that you leave these at default.
Change the NaviCLI path if necessary.
Check the Execute FBI process box if you want FBI to run.
Click Next.
On the next dialog, enter the SP A and SP B IP addresses for the array and click Add. The
serial number for those IP addresses will be determined and added to the right-hand panel.

323906703.doc (273.00 KB)


7/15/2016 2:01 PM
Last saved by Rosslyn Bradley
.f Repeat for as many arrays as you need to check.\
.g Select the destination directory for the files. CAP2 automatically creates a folder called capData.
.h It is recommended that you accept the default of c:\capData as shown. If this is done, the default
directory for output files will be
C:\capData\<CSISRorPASnumber>\<arrayserialnumber>_<date_time>

.i Click Next.
.j CAP2 will check for and list any hosts that are attached to the array. If you have another host to be
validated and then enter the IP address and click Add.
.k Repeat for all hosts to be validated.
.l If a host is listed that you do not want to be validated at this time, select the host in the left-hand
panel and use the >> to move the host to the Excluded Hosts panel.
If no hosts are to be validated, then uncheck the Collect Host Data box.
.m Click Next.
.n Enter the IP address of the first switch that is to be checked and click Add.
If no switches are to be validated, then uncheck the Collect Switch Information box.
.o Repeat for all switches to be validated.
.p Click Next.
.4

Host Configuration Review: EMCGrab and EMCReports, HEAT


.a You will be instructed to load EMCGrab and/or EMCReports on hosts that are attached to this array,
run the tool and then copy the output file(s) back to the management station/laptop where you are
running the CAP2 program, to the folder specified in the message.
NOTE: EMCGrab (emc62506) is a host-based utility running on Solaris, Linux, AIX, HP-UX and
Tru64. For Windows platforms this tool is called EMCReports (emc96965).
.b Install and execute the EMCGrab or EMCReports using instructions in the appropriate EMC
Knowledgebase article mentioned above.
Note: It is advisable to have the customer run these reports as they require administrative privileges.
Note: Run this for all hosts that are attached.
.c Once completed, a compressed tar file is created under the EMCGrab/output directory. For
Windows platforms, a zip file is automatically generated under
c:\winnt\EMCReports\COLLECTION\ZIP.
.d All host files collected should be placed in the folder specified by CAP2.
.e Upload the files to HEAT. The HEAT application is a host-based tool that parses the
EMCGrab/EMCReports output files and provides a detailed analysis.
Option 1 - If you are connected to the EMC network: From the main CAP2 screen, select Help
Service Toolbox.
Option 2: If you cannot access the EMC Internal Network: Access to HEAT is available via
Powerlink at Home > Support > Product and Diagnostic Tools > Environment Analysis
Tools. If you require a Powerlink account, please visit http://powerlink.emc.com and complete

323906703.doc (273.00 KB)


7/15/2016 2:01 PM
Last saved by Rosslyn Bradley
the registration form.
This will take you to the Toolbox website from which you can access HEAT
(http://toolbox.isus.emc.com/heat.php). Select Upload and browse to the files you collected earlier
from EMCGrab/EMCReports. Click the Upload button. This may take some time depending on the
file system and your network connectivity.
Once the files have been successfully uploaded, enter your email address (without the @emc.com
extension) to which the HEAT report is to be sent. There is no need to enter a case number for the
install process. Click Continue to generate the HTML report. The report can be viewed online or you
can wait for it to be sent to your inbox.
It is the installing engineers responsibility to go through each HEAT report and correct all discovered
problems. Different colors are used to distinguish entries. Pay careful attention to the red entries,
which identify warnings. HEAT verifies information against the E-Lab Interoperability Navigator (ESM).
HEAT will indicate the versions of software, firmware, and patch levels that should be installed.
Investigate any discrepancies.
It is also important to verify the connectivity to the CLARiiON array. If PowerPath is the failover
software on the host, then a listing of the powermt display dev=all command output is also included in
the report. Verify that each server has the correct number of paths to the array. If another failover
software is used (for example, DMP), then that specific information is also in the report. Additional
details may also be found in the emcgrab output.
If configuration errors appear in the HEAT report, you must implement the changes on the server, then
rerun EMCGrab/EMCReports and upload the new output to HEAT again. Repeat these steps until
your HEAT report displays a clean installation. Only the last HEAT report together with its associated
EMCGrab/EMCReports output files need to be kept for each server.
When the EMCGrabs/EMCReports have been run, the HEAT reports received and all the output files
have been transferred to the management station/laptop to the C:\capData\<CSISRorPAS
number>\<arrayserialnumber>_<date_time> folder, click on OK.
.5

Switch Configuration Review - for SAN configurations only: Data Collection, SWAT
You will be instructed to gather switch information from all switches in the SAN environment to which
the disk array is attached, and then copy the output file(s) back to the folder specified in the message.
For Brocade and/or McData switches, some switch information will be gathered by CAP2 (if you
entered the switch IP addresses). CAP2 does not gather information for Cisco switches.
For all switches, use the following instructions to collect data for later use. You can also refer to EMC
Knowledgebase article emc111717 for additional switch data collection information.
Brocade supportshow data collection:
Start the hyperterminal program by selecting Start Programs Accessories
Communications Hyperterminal.
Make a new connection and select a name and icon for the connection.
A box appears titled Connect to.
Change the Connection using modem to TCP/IP (Winsock) and enter the IP address of the
Brocade switch.
.a Click the OK button.
.b Login into Brocade switch (default user: admin/default password: password) and then start to
capture text. Transfer Capture text File C:\supportshow.wri

323906703.doc (273.00 KB)


7/15/2016 2:01 PM
Last saved by Rosslyn Bradley
.a Run the Brocade command: supportshow.
.b After the command completes, stop the capture text process (Transfer Capture text
Stop).
.c After completing this for all switches in all related fabrics, type quit and close the
hyperterminal session.
Cisco support details:
.a Start the hyperterminal program by selecting Start Programs Accessories
Communications Hyperterminal.
.b Make a new connection and select a name and icon for the connection.
.c A box appears titled Connect to.
Change the Connection using modem to TCP/IP (Winsock) and enter the IP address of the
Cisco switch.
.d Click the OK button.
.e Log into Cisco switch (default user: admin/default password: password) and then start to capture
text. Transfer Capture text File C:\supportshow.wri
.f Run the following commands:
termlen0
showtechsupportdetails

.g After the command completes, stop the capture text process (Transfer Capture text Stop).
.h After completing this for all switches in all related fabrics, type quit and close the hyperterminal
session.
Connectrix McData data collection:
.a Select the IP address of a switch from which you want to retrieve a data collection.
.b Select Maintenance Data Collection.
.c Enter a file name for the file then select Save. Note the folder where the data is saved.
.d Once you select save, data collection takes over and the files are downloaded to the local PC and
stored in the folder specified.
For all switch types: All files collected should be placed in
C:\capData\<CSISRorPASnumber>\<arrayserialnumber>_<date_time>
or the folder that you selected above.
Upload the files to SWAT.
The SWAT application is a host-based tool that parses the switch output files and provides a detailed
analysis.
Option 1 - If you are connected to the EMC network: From the main CAP2 screen, select Help
Service Toolbox.
Option 2: If you cannot access the EMC Internal Network: Access to SWAT is available via
Powerlink at Home > Support > Product and Diagnostic Tools > Environment Analysis Tools. If you
require a Powerlink account, please visit http://powerlink.emc.com and complete the registration
form.
This will take you to the Toolbox website from which you can access SWAT
5

323906703.doc (273.00 KB)


7/15/2016 2:01 PM
Last saved by Rosslyn Bradley
(http://toolbox.isus.emc.com/swat.php).
Select Upload and browse to the file you collected earlier with the switch tools. Click the Upload
button. This may take some time depending on the file system and your network connectivity.
Once the files have been successfully uploaded, enter your email address (without the @emc.com
extension) to which the SWAT report will be sent. There is no need to enter a case number.
It is the installing engineers responsibility to go through each SWAT report and correct all the
discovered problems. Different colors are used to distinguish entries. Pay careful attention to the red
entries, which identify warnings. SWAT verifies information against the E-Lab Interoperability
Navigator (ESM).
It is also important to verify the frame statistics section. The presence of many errors may indicate
connectivity issues. If this is the case, reset the switch statistics and run a new data collection/SWAT
process after a few hours of activity. Note if the error count is the same or increasing.
If configuration errors appear in the SWAT report, you must implement the changes on the switch, then
run a new data collection and upload them to SWAT again. Repeat these steps until your SWAT report
displays a clean installation. Only the last SWAT report together with its associated data collection
output files needs to be kept for each switch.
When the switch data collection has been completed and the files have been placed in the appropriate
location, click OK.
.6

Processing will start for the arrays that were selected.


When asked, enter the username, password, and scope for each array/and or switch and click on OK.

.7

If any HAVT reports were generated after the SPCollects were run, then you can manually load them
onto the station where CAP2 is running. Put them in the HAHosts directory indicated by CAP2.

When the data collection has completed, click on Finish to load the results into CAP
.8

Evaluating CAP2 output:


.a An Issue Summary screen will de displayed.

.b Examine it for any errors.


.c Select the Analysis tab to review the results.
.d The information presented will include a Pass/Fail statement. If the check failed, additional
investigation will need to occur.
.e Use normal troubleshooting methods such to define and repair any issues. See Tools Launch
for options contained within CAP2 (for example, SPLAT).
.f If a Pass statement was returned, go to the Issues tab and review this list for any items which may
impact a successful LUN failover such as single paths, failed paths, etc. Any problems are to be
corrected prior to proceeding with the FCO/Upgrade. Contact EMC Technical Support if assistance
is required.
.g Using the information under the Hosts and Host HA tabs, check on a per host connection that
these are set correctly for the host operating system in use. Refer to the Failover Settings
Reference Table. Verify with the customer that the failover software implied by the Host settings
has been installed.
This document can be obtained using the link below or rerunning the CLARiiON Procedure

323906703.doc (273.00 KB)


7/15/2016 2:01 PM
Last saved by Rosslyn Bradley
Generator and selecting Failover Settings Reference Table from the Reference Materials menu.
View Failover Settings Reference Table
NOTE: For current support for ALUA, please consult the E-Lab Interoperability Navigator. See the
Installation Roadmap for CLARiiON Storage Systems P/N 069001166 for the required
failovermode, initiator type settings etc. for any failover software that is not listed.
NOTE: The Trusted column should be ignored as it applies to legacy arrays only.
.h Using the information under the Switches tab, check that all expected host and array connections
are listed and valid.
.9

Set the default Sniffer values:


Note: This need only be done if the storage system has been installed with a release prior to Release
16.

The Set Sniff Rate utility requires that:


SP collects have been run for the array
A report has been generated from them using CAP2
That report is currently open in CAP2
.a From the CAP2 toolbar, select Tools Service Workbench Apply Default Sniffer Values.
.b Click Yes when prompted to confirm to set the sniffer values.
.c The Sniff rates will be set on all the LUNs on the array. Information will be displayed at the end of
the Analysis report. Settings prior to applying the default sniffer values and the settings after the
update will be listed in a report similar to the one below.
If the Sniff Rate information does not appear at the end of the Analysis report, you will have to
refresh the .xml output. Select File and select the cap_<array_serial _number>_<date_time>.xml
file that you have just created for this array.
.10

Collect the documentation set as follows.


CAP2 will have automatically created a zip file for each array called
<array_serial_number>_<date_time>_Enhanced_Install_Procedure-2.zip
in the c:\capData\<CSI SR or PAS number> folder or the folder that you selected above. The zip file
will consist of:
the last CAP2 files for the array
the last SWAT html report for each switch and its associated data collection output files
the last HEAT html report for each server and its associated EMCGrab/EMCReports output file
NOTE: Do not change the name of the zip file, or submit a file with anything other than this naming
convention, because files are retrieved for analysis based on this expected name structure.
If you were unable to take advantage of the automatic zip function, you can create the zip file
manually, but naming convention has to be strictly observed. You can zip all these files into a file
called <array_serial_number>_<date>_Enhanced_Install_Procedure-2.zip. <date> will be in the
format mm-dd-yyyy, with the date being the date on which the reports were generated. For example,
reports gathered on July 5, 2005 for array serial number APM00033100394 would be called:
APM00033100394_07-05-2005_Enhanced_Install_Procedure-2.zip
This file should be placed in the C:\capData\<CSI SR or PAS number> folder. Use this file wherever
<array_serial_number>_<date_time>_Enhanced_Install_Procedure-2.zip is referenced.

323906703.doc (273.00 KB)


7/15/2016 2:01 PM
Last saved by Rosslyn Bradley
NOTE: It is imperative that you use this naming convention because files are retrieved for analysis
based on this expected name structure.
Leave the collected files on the management station for future reference.
Table of Contents

También podría gustarte