CXClear 1.1.

3 User Guide

Data Erasure
for CLARiiON

CXClear version 1.1.3

User Guide

REV 1.1.7

EMC Confidential
Copyright © 2010-2017 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as of its publication date. The
information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION
MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE
INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an
applicable software license.

1
 CXClear 1.1.3 User Guide

Version Control

Date Version Author Description

April 23rd, 2009 0.1 First Draft
May 6th, 2009 0.2 Updates after internal review
May 8th, 2009 0.3 Small updates from John
June 5th, 2009 0.4 Miscellaneous updates
August 13th, 2009 0.5 Reformat using Procedure Generator template
September 10th, 2009 0.6 Updated for CXClear 1.1
October 7th, 2009 0.8 Additional small updates
October 28th, 2009 0.9 Updates following EDL qualification
December 15th, 2009 1.0 Small updates for CXClear 1.1.1
January 26th, 2010 1.1 Small updates for CXClear 1.1.2
May 24th, 2010 1.1.2 Added checksum verification
June 22 2011 1.1.2 Added some updates windows 7
December 07th 2011 1.1.3 LAVA User information added
December 16th 2011 1.1.3 Minor edits
September 24th, 2013 1.1.3 Added McAfee info
October 31st, 2013 1.1.3 Updated download link
November 13, 2013 1.1.4 Updated License Request link
May 11, 2016 1.1.5 GS Tools Added note to uninstall VNXClear before
installing CXClear
March 21, 2017 1.1.6 GS Tools Added 2.9 Check Array Configuration
November 20,2017 1.1.7 GS Tools Updated psapps links lava and elabadvisor

2
 CXClear 1.1.3 User Guide

Table of Content

1. CXClear v1.1 Release .............................................................................................................. 5

1.1. CXClear Overview ..................................................................................................... 5
1.2. Delivered Features .................................................................................................... 5
1.3. Package content ........................................................................................................ 5
1.4. Supported Platforms .................................................................................................. 6
1.5. Execution Time Examples ......................................................................................... 7
1.6. Erasure Steps Overview ............................................................................................ 7
1.7. Important Considerations .......................................................................................... 8
1.8. EMC Disk Library Considerations .............................................................................. 9
2. Pre-Erasure steps ..................................................................................................................... 9
2.1. Download the CXClear installation package ............................................................. 9
2.2. Install and Verify CXClear ......................................................................................... 9
2.3. Check Virus protection settings ...............................................................................11
2.4. Request an erasing license .....................................................................................13
2.5. Get the necessary equipment ..................................................................................16
2.6. Retrieve sp-collect (mandatory step) .......................................................................17
2.7. Retrieve ddbs_info (optional step) ...........................................................................17
2.8. Check array serial number ......................................................................................17
2.9. Check array configuration ........................................................................................17
3. CXClear Installation ................................................................................................................18
3.1. Check whether your installation has expired ...........................................................18
3.2. Get the installation file .............................................................................................18
3.3. Check your Laptop...................................................................................................19
3.4. If necessary, uninstall any previous CXClear installation ........................................19
3.5. Install CXClear on your laptop .................................................................................20
4. PXE Boot Instructions .............................................................................................................23
4.1. Disable your wireless network .................................................................................23
4.2. Set your static IP address ........................................................................................24
4.3. Verify array front-end ports are disconnected .........................................................25
4.4. PXE Boot Array........................................................................................................25
4.5. Different PXE boot methods ....................................................................................25
4.6. TFTPD32 .................................................................................................................26
4.7. PXE boot Steps for CX3 array .................................................................................26
4.8. PXE boot steps for CX array ...................................................................................32
5. CXClear Usage .......................................................................................................................43
5.1. Generalities ..............................................................................................................43
5.2. Starting the CXClear GUI ........................................................................................44
5.3. Deploy and Start the CXClear Server ......................................................................45
5.4. Reconnecting to an already running CXClear server ..............................................46
5.5. Start/Reconnect error messages .............................................................................47
5.6. Stopping the CXClear Server ..................................................................................49

3
 CXClear 1.1.3 User Guide

5.7. FLARE disks ............................................................................................................50

5.8. Start Erasure ............................................................................................................51
5.9. Monitor Erasure Process .........................................................................................57
5.9.1. Header Section ........................................................................................................57
5.9.2. Disk List section .......................................................................................................58
5.9.3. Columns meaning ....................................................................................................60
5.9.4. Right Click Menus ....................................................................................................62
5.10. Retrieve Report and Logs ........................................................................................65
5.10.1. Report ......................................................................................................................66
5.10.2. Report signature ......................................................................................................66
5.10.3. Accepting CXClear signing certificate .....................................................................67
5.10.4. Report statuses ........................................................................................................71
5.10.5. Report details ...........................................................................................................72
6. Reconditioning Array after Erasure ........................................................................................73
7. Troubleshooting ......................................................................................................................75
7.1. Tftpd32.exe automatically deleted ...........................................................................76
7.2. No Network Connectivity between SP and Host .....................................................76
7.2.1. If the PXE booting process didn’t complete successfully ........................................76
7.2.2. If the PXE process successfully completed .............................................................76
7.2.3. If the problem persists, contact support with: ..........................................................76
7.2.4. Adjust Tftpd32 configuration settings ......................................................................77
7.3. Check PXE booting between two laptops ...............................................................78
7.4. Work around Cisco Security Agent ..........................................................................80
7.5. Using the serial port to detect problems ..................................................................81
7.5.1. IRQ conflicts ............................................................................................................83
7.5.2. Drives failing to spin up ...........................................................................................84
7.5.3. Capturing the Serial Port output ..............................................................................85
7.5.4. Forgot your IP address ............................................................................................86
7.6. Some disks or buses not discovered .......................................................................87
7.7. ‘Preserve FLARE’ erasing option greyed out ..........................................................89
7.8. GUI hangs or commands not reaching the array ....................................................90
7.9. Detect Erroneous disks ...........................................................................................90
8. Appendices .............................................................................................................................90
8.1. Install winscp418setup.exe on your laptop ..............................................................90
8.2. Manually Retrieve Log files .....................................................................................96
8.3. PAS TS Task Type and Task Number is CSI Service Request ..............................99
8.4. CSI Service Request – Certificate of Completion Attachment ..............................100
8.5. Generate ddbs_info file using EMCRemote ..........................................................101
8.6. Tftpd32 log sample ................................................................................................105
8.7. SP-Collect Retrieval methods ................................................................................106
8.8. CXClear and Windows 7 .......................................................................................108

4
 CXClear 1.1.3 User Guide

1. CXClear v1.1 Release

1.1. CXClear Overview
The CXClear Data Erasure Solution is a tool that enables EMC Global Services personnel to
perform full frame erasures on CLARiiON CX, CX3, NAS and EDL arrays. The application
executes from the EMC field resource laptop which is used to PXE (Network) boot a Linux image
onto the target CLARiiON SP processor and control the erasing application from a client GUI.
CLARiiON erasures are performed in support of Certified Data Erasure services sold using model
PS-BAS-CXDE or PS-CUS-EMC when erasure is a component of a large project. The erasure
engagement is subject to the deliverables documented in the Certified Data Erasure for
CLARiiON Service Brief located in the TS Kit on Powerlink or documented in the Statement of
Work (SOW) for the project. On order acceptance, the appropriate EMC resource is assigned the
task. A CSI Service Request is opened using Task Type = TS WORK and the PAS number is
entered into the appropriate field in the “Additional Information” pane in CSI. The CLARiiON
Procedure Generator is used to download the latest procedures (this document) and contains the
links to access the CXClear program and required licensing. Following completion of the CXClear
process, any disk drive that does not successfully erase is removed from the array and rendered
to the customer for final disposition. The Completion Report is delivered to the customer and a
copy of the report is attached to the CSI Service Request when the event is closed. Please refer
to the appendix 8.4 for additional information.
Erasures should only be performed on functional arrays that have been decommissioned by the
customer or which are to be repurposed by the customer.

1.2. Delivered Features

 Erasing engine
 Graphical client interface
 Start and stop the erasure
 3, 5 or 7 passes DOD compliant erasures
 Wipe or preserve FLARE disks
 Error recovery algorithm
 Random sample sector verifications
 Digitally signed erasure report in PDF format
 Screen resolution of 1152 x 864 or greater supported on Windows
 All Clariion FC disks
 SATA disks up to 2TB (3 and 4TB are not supported by the application)
 ATA disks

1.3. Package content

The package is made of a CXClear.exe file and this user guide document. The installation utility
will create the following file structure for Windows XP and 32 Bit windows. For Windows 7 64 bIt
the default installation is to `Program Files (x86)’ -> `EMC’ :

5
 CXClear 1.1.3 User Guide

Figure 1 CXClear installation directory structure

 ‘logs’ folder:
The logs folder is empty at installation time but the GUI and server logs will be stored there:
 CXClearClient.log (GUI client log file)
 CXClear_serialnumber_yyyy-mm-dd_hh-mm-ss_xxxxxx.tar.gz (server log, retrieved
using the ‘Retrieve Data’ menu on the GUI or automatically when the ‘Start’ or
‘Stop’ command is invoked).

 ‘Start’ ‘Program’ ‘EMC’ ‘TsgTools’ ‘CXClear’ menu:

 CXClear (main application launcher)
 PuTTY (SSH client)
 TFTPD32 (DHCP/TFTP server)
 Uninstall CXClear (uninstaller)

1.4. Supported Platforms

Note: CX4 and VNX are not supported

Platform Supported
CX3-80 Ok
CX3-40f Ok
CX3-40 Ok
CX3-40c Ok
CX3-20f Ok
CX3-20 Ok
CX3-20c Ok
CX3-10c Ok
CX300 Ok

6
 CXClear 1.1.3 User Guide

CX500 Ok
CX700 Ok
CX400 Ok
CX600 Ok
CX200 Ok
EDL Ok
NAS Celerra Ok

IMPORTANT: EDL products cannot be repurposed. We only provide the option to ‘Preserve
FLARE’ to repurpose the array as a CLARiiON.

1.5. Execution Time Examples

Here are some erasure timings for different disk types:

Disk Type Size Number of passes Duration

ATA 750 GB 7 passes 105 hours
FC 146 GB 7 passes 3 hours
FC 300 GB 7 passes 11 hours
SATA 1 TB 7 passes 40 hours

Note: CXClear carries out the erasure of 120 disks in parallel simultaneously. As selected disks
complete the erasure process, additional selected disks will automatically start until all selected
disks are erased.

Erasure durations are dependent on several factors including the CPU of the machine performing
the erasure as well as the number, size, speed and manufacturer of the disks in the array.
Therefore it is difficult to accurately predict an erasure time for a specific configuration. The
erasure estimates provided in the tool are extremely rough. The Preserve FLARE option incurs
an additional pass where the disks are additionally zeroed.
Set-up time should be less than an hour. Re-installing FLARE if required may take up 2 hours as
there are multiple SP reboots involved. The ‘navicli zeromark’ will also take as much time as
a single pass on the largest disk in the array. Time should also be allowed to upgrade to the latest
FLARE bundle and re-install any software.

1.6. Erasure Steps Overview

The user should carry out the steps below on the identified platforms:
 Prior to going to customer site:
a. Download latest CXClear ProcGen document.
b. Download the latest package (see section 2.1).
c. Install and verify the checksums (see sections 2.2 and 2.3).
d. Request a license file (see sections 0).

7
 CXClear 1.1.3 User Guide

e. Get cables (see section 2.5).

f. Install and configure the CXClear application (see section 0).
 At customer site:

a. Retrieve sp-collect (just before PXE booting the array) (see section 2.6).
b. Retrieve optional ddbs_info (see section 2.7).
c. PXE boot the array (see section 4).
d. Start CXClear GUI and Start the server application (see section 5.2).
e. Visually check that there are no missing or additional disks (red rows in the list of
disks, scroll to the end of the table)
f. Configure and begin an erasure (see section 5.8).
g. Monitor progress (see section 5.9).
h. Retrieve erasure report and log files (see section 5.10).
i. Visually check that the report is correct.
j. Hand back any non erased disks to the customer.
k. If re-installing FLARE - use the backrev procedure and run the ‘navicli zeromark’
before upgrading to the latest FLARE bundle.

1.7. Important Considerations

 The application is fully running in the target CLARiiON memory and if it is rebooted or the
power turned off, then all data is irretrievably lost.
 The user laptop is only running the GUI front end of the application. Once the application has
been successfully deployed and the erasure started the GUI can be terminated and the laptop
disconnected. The user doesn’t have to leave their laptop on site for the duration of the
erasure. When returning to the site to complete the erasure process, the user reconnects to
the configuration via the CXClear application and collects the results.
 CXClear is typically deployed from a laptop connected to the target CLARiiON via a LAN (and
serial) cable but it can be managed from any host that can see its IP address. The GUI front
end application can run on any Windows machine and talk to any successfully PXE booted
CLARiiON. Instructions in this guide explain how to succesfully connect one laptop to one
array at a time, advanced DHCP and IP understanding is required to manage several array
from one host PC.
 If you encounter a problem, the first thing to do is to capture screenshots of the error, retrieve
the log file from the CLARiiON and read through the Troubleshooting recommendations in
section 7.
 If VNXClear is installed, remove it prior to installing CXClear.

WARNING: CLARiiON arrays running FLARE version prior to release 16 have not been
tested and shouldn’t be erased before being upgraded.

8
 CXClear 1.1.3 User Guide

1.8. EMC Disk Library Considerations

 For CXClear erasures performed on EDL platforms, the CLARiiON should be completely
disconnected from the DL configuration. Specifically, cables connected to the AUX ports on
the SPs must be removed prior to initiating the erasure.
 EDL models with spin-down capabilities must verify the disk enclosures power up all drives as
part of the SP and DAE power cycle procedure in the PXE Boot operation.
 If the Disk Library server (i.e. head) requires erasure, the internal hard drives on the server
can be erased using the DBAN utility available in the eRoom.

2. Pre-Erasure steps
2.1. Download the CXClear installation package
The CXClear installation package can be downloaded from the GSTools website. Make sure you
download the latest version from:
 https://elabadvisor.psapps.emc.com/app/licensedtools/list

If access issues are encountered, please send an e-mail to: [email protected]

NOTE:- The latest version of the user guide is available from the GSTools website, the ProcGen
version may be few days late depending on ProcGen release dates.

One file containing the following must be down loaded from the GSTools website:
 CXClear_utility_pwd=emc.zip
 Checksum_CXClear.zip
 CXClear_v1.1.3_User_Guide.pdf

2.2. Install and Verify CXClear

Once the files above have been downloaded into a local folder, unzip
CXClear_utility_pwd=emc.zip (type emc when prompted for a password) and
Checksum_CXClear.zip.

Double click on cxclear_exe_checksum.bat to check the integrity of the downloaded file. If all is
ok you will get the following:

Figure 2 Successful checksum verification

9
 CXClear 1.1.3 User Guide

It has already happened that the EMC virus checker tampered with the downloaded file (i.e.
removing tftpd32.exe), in that case you would get a checksum verification error and the output
would look something like:

Figure 3 Installer checksum error

You can now install the application by double clicking on CXClear.exe.

Again to be safe it is a good idea to verify the checksums of the installed files. Double click on
cxclear_install_checksum.bat. If you didn’t install CXClear in the default directory
(C:\Program Files\EMC\TsgTools\CXClear) then you must enter the installation path,
otherwise just press return. If all is ok you will see the following output:

Figure 4 Installed files checksum verification

10
 CXClear 1.1.3 User Guide

2.3. Check Virus protection settings

It is suggested to disable Anti-virus and Firewall software to prevent issues in preparation for
performing an erasure. Ensure you restart these services when you are finished to keep
your system protected. Known scenarios are described below.

Use of tftp.exe

The McAfee security tool sometimes blocks DHCP and TFT traffic preventing to PXE boot the
CLARiiON. After discussions with IT, it seems that the following checks could prevent the
problem:
 Right click on the McAfee icon and chose ‘VirusScan Console’
 In ‘Access Protection’ ‘Anti-virus Standard Protection’ make sure that ‘Prevent
use of tftp.exe’ is not ticked (untick it if it is).

Figure 5

 In ‘Unwanted Program Policy’ ‘Exclusions…’ make sure that tftpd32.exe is listed. If it

isn’t contact IT to update your excclusion list.

Continued on next page

11
 CXClear 1.1.3 User Guide

McAfee Host Intrusion Prevention Service

 On your PC, navigate to the Control Panel > Administrative Tools > Services icon. You can
also access the Services program from Start > Run: services.msc.
 Open the Services icon and locate the McAfee Host Intrusion Prevention Service.
 Double-click the McAfee service and then select the Stop option to stop the service.
 Retry the initialization process and then complete the system initialization.
 After you have completed system initialization, re-enable the McAfee Host Intrusion
Prevention Service by restarting the service. It is critical that you re-enable the McAfee
Host Intrusion Prevention Service once steps #1-4 above are completed in order to
protect your systems.

12
 CXClear 1.1.3 User Guide

2.4. Request an erasing license

Licensing is done so via the GSSD License Server
(https://lava.psapps.emc.com/userRequest/CXClear) . You will be required to Register CXClear
and obtain a valid license. Users will be required to perform the following steps in order to receive
a valid CXClear Authorization file.
1. Access via the above link the CXCLEAR License request page
If you receive a message saying there is a problem with the sites security certificate you
may continue in this case, as it is an EMC internal site. This is NOT recommended in
other circumstances. See examples below

Figure 6 Certificate warning message (Windows)

13
 CXClear 1.1.3 User Guide

Figure 7 Certificate warning message (Firefox)

2. If you are presented with a EULA you will need to accept this agreement before
proceeding with the remainder of the license registration.

14
 CXClear 1.1.3 User Guide

3. If the user is a new LAVA user they will be presented with New User Registration dialog
shown below. Once this is completed you will be directed to the CxClear Authorization
Request form.

All fields should be automatically

completed, if not the user should
manually complete all fields on this
form with the correct EMC Employee
information as requested.

Figure 8 User Registration

Note: If User is already a LAVA user they will go straight to CxClear Authorization
Request Form.

4. The user will fill out the CxClear Authorization Request page and when satisfied they
will press the Download CxClear Key File button. This will generate the encrypted
authorization file and prompt the user to download it to their file system.
 Make sure that the array serial number is correct as it is verified by CXClear
when the application is deployed onto the target array (e.g. CK200084600889
or APM00023001079).
 Some of the details the license wil appear in the final report presented to the
customer so please ensure they are accurate.
 This file should be kept. It will need to be entered into application when it is
deployed. See section 5.3 figure 47.
 The file is initially named “authcache_Array_serial#.lava” The serial value on
the file is substituted with the serial number entered in on the request.
 The Requester First and Last names, Company and email address should be
reflect your registration details.

15
 CXClear 1.1.3 User Guide

 The “Clear” button can be user to clear the entry fields and enter in another
request
If the user has 3 different data erasures to perform they can enter one,
download the authorization file, click “Clear” and repeat the process for the
next 2.

Complete all fields on this form with

the correct information as requested.
Note: If the information doesn’t match
the exact array SN# the erasure
software will not be licensed and you
will not be able to proceed with the
Figure 9 CxClear License request erasure.

 Although e-mail addresses are required in some fields the file is not
automatically e-mailed. The requester will have to ensure the downloaded
file is distributed accordingly.

NOTE: There is a mandatory check box to indicate completion of the required training for CXClear.

Once you have obtained a valid license, continue with the steps listed below.
2.5. Get the necessary equipment
The following list of equipment is needed:
 The appropriate CLARiiON serial cable for the array. There are three types:
 For the CX3 series arrays use a DB9 to micro-DB9. For the CX series use a DB9 to DB9
(excluding the CX500).
 For the CX500 use a DB9 to DB9 with a DB9 to RJ45 adaptor).
 A cross over network cable to connect directly from the laptop to the array (part number 038-
003-457).
 A cross-head (Phillips) screw driver to assist in removing one Storage Processor from the
chassis.

16
 CXClear 1.1.3 User Guide

2.6. Retrieve sp-collect (mandatory step)

The sp-collect file (serialnumber_SPA_date_data.zip) is required from at least one of the SP’s.
It is recommended that SP-A be used as this is the default SP required for re-imaging.
It is mandatory to provide the sp-collect information to CXClear.
The sp-collect information must be current and must accurately reflect the status of the Array
being erased.

WARNING: No configuration changes should be made to the Array after the sp-collect
is generated.

The sp-collect information may be gathered using different methods, they are explained in section
8.7.

2.7. Retrieve ddbs_info (optional step)

IMPORTANT: This step is critical if the array is going to be reused or repurposed in the customer’s
environment.

The ddbs_info information is used by CXClear to locate the FLARE disks areas that must be left
untouched to allow the array to be re-imaged using the Back-rev procedure. This file is optional
but if it is not provided the ‘Preserve FLARE Disks’ erasure option will not be available. There is a
DIMM’s open to have this information put into the sp-collect file in future versions of FLARE.
Refer to section 8.5 to generate and retrieve a ddbs_info file.

2.8. Check array serial number

Before starting the erasing process, the user must check the array serial number. There are two
stickers beside each other at the back of the array; one shows the WWN seed and the other the
serial number. Ensure that this last number matches the number of the targeted array serial (and
is the one that was provided for the license registration).

2.9. Check array configuration

WARNING:

Do not proceed with the Data Erasure if any host is still connected to this array or if any lun is still
configured.

Request the customer to remove all host connections and remove all luns.

17
 CXClear 1.1.3 User Guide

3. CXClear Installation
To install the CXClear application, follow the steps below:

3.1. Check whether your installation has expired

If you have already installed CXClear, check whether your installation has expired. Every 60 days
the software expires and you must download and install a new version. The ‘Home’ tab of the
application shows the number of remaining days before expiration.

Figure 10 Check CXClear remaining days

3.2. Get the installation file

If not performed previously, retrieve the CXClear.exe installer file from
https://elabadvisor.psapps.emc.com/app/home/index
[Click on Licensed Tools tab to download the required version]

18
 CXClear 1.1.3 User Guide

3.3. Check your Laptop

CXClear has been qualified for Dell Laptops running a standard EMC Windows XP image.
It should run on other recent Windows installations, but be aware that occasional issues have
been found with the anti-virus and firewall applications. In some instances CXClear does not
correctly install (see troubleshooting section 7.1) or fail to PXE boot due to DHCP requests
coming from the array being blocked by the firewall (see troubleshooting section 7.2). If you want
to make sure you won’t encounter these issues on site perform a PXE boot test as explained in
7.3.

3.4. If necessary, uninstall any previous CXClear installation

On Windows XP or 32 bit Windows 7 to uninstall the application run:
C:\Program Files\EMC\TsgTools\CXClear\Uninstall_CXClear\Uninstall CXClear.exe
or click the:
‘Start’ ‘Program’ ‘EMC’ ‘TSGTools’ ‘CXClear’ ‘Uninstall CXClear’ menu.
On 64 bit Windows 7 the application is in C:\Program
Files(X86)\EMC\TsgTools\CXClear\Uninstall_CXClear\Uninstall CXClear.exe

Note: The CXClear\logs folder will be left untouched and your previous log files and reports
will not be deleted. If you want to remove them you must do so manually.

19
 CXClear 1.1.3 User Guide

3.5. Install CXClear on your laptop

Execute the installer and follow the on-screen instructions:
 Click ‘Next’

Figure 11 CXClear installer 1

 Choose the installation location, then click ‘Next’

Unless you have a good reason not to do so, choose the default installation location.

Note: On Windows 7 64 Bit the default is to install to c:/Program_files (X86)/EMC. Please

see appendix 8.8 for additional details on Windows 7. On Windows 7 you will be asked to allow
the application to make changes to your computer – reply yes

20
 CXClear 1.1.3 User Guide

Figure 12 CXClear installer 2

 Click ‘Next’

Figure 13 CXClear installer 3

21
 CXClear 1.1.3 User Guide

 Click ‘Install’

Figure 14 CXClear installer 4

 Click ‘Done’

Figure 15 CXClear installer 5

22
 CXClear 1.1.3 User Guide

 On Windows XP application can now be started from:

C:\Program Files\EMC\TsgTools\CXClear

On Windows & you will need to change the permissions on this file before
proceeding - please see appendix 8.8

This is accessible via the following sequence in Windows:

‘Start’ -> ‘Programs’ -> ‘EMC’ -> ‘TSGTools’ -> ‘CXClear’ menu.

Figure 16 CXClear Start menu

Note that a log file has been created. If you kept the default installation an installation path it is
stored in:
C:\Program Files\EMC\TsgTools\CXClear\CXClear_install.log

4. PXE Boot Instructions

4.1. Disable your wireless network

Figure 17 Disable the wireless network

23
 CXClear 1.1.3 User Guide

4.2. Set your static IP address

To successfully PXE boot the array you need to set a static IP address for the laptop. The laptop
must be running on the same IP network as the CLARiiON, requiring the following configuration:
IP address: 192.168.169.2
Subnet mask: 255.255.255.0
Default gateway: 192.168.169.1

As shown in the screenshots below for Windows XP. For Windows 7 you may have to run
“ipconfig /renew’ and “ipconfig” from the DOS prompt to check the changes have taken affect:

Figure 18 Change laptop network configuration (Windows XP)

24
 CXClear 1.1.3 User Guide

Figure 19 Set Laptop static IP address

Note: The DNS settings can be left untouched

4.3. Verify array front-end ports are disconnected

Once the application loads the SCSI driver it may try to make use of the Fibre front-end ports so
please ensure these are disconnected. Label them for re-insertion later if required.

DANGER: Do not attempt to perform erasures while the array is connected to a host or
switch. Unpredictable results, including permanent DATA LOSS, may occur..

4.4. PXE Boot Array

The steps for PXE booting the array are listed in section 4.8 for the CX series and in
section 4.6 for the CX3 series.

4.5. Different PXE boot methods

Stiletto’s (DAE3P’s and DAE4P’s) operate in 2 modes – local and remote. When using FLARE as
an Operating System the DAE’s are in remote mode and are visible only to the FLARE OS.
Unfortunately the only way to put the DAE’s back into local mode where they are visible to the
CXClear server application via the OS kernel running on the SP is to power-cycle them.

25
 CXClear 1.1.3 User Guide

Once the DAE’s are in local mode and FLARE sees them again they may be returned to remote
mode. This may happen if the PXE boot process times out.
After power-cycling the DAE’s on a CX3 (PXE boot using the ICA sub-menu) when you bring the
disks online all the back-ends may go into remote mode and not be visible - this is circumvented
by PXE booting from the BIOS on boot-up when the disks are in local mode after the power-cycle.
The downside is that if you go too far during the boot to the Engineering menu you may need to
re-power-cycle as the disks have been re-enabled in remote mode.
Unfortunately for the CX series we cannot interrupt the BIOS with the same method. We need to
go to the Engineering ICA menu to bring the disks online. The downside of this on the CX series
is that back-end zero may be re-enabled in remote mode if it is connected to DAE3P’s or
DAE4P’s. Hence you may additionally have to power-cycle the DAE’s on back-end zero once
more after the array has been PXE booted (see trouble shooting section 7.6 for more
information).

4.6. TFTPD32
A few recommendations regarding the use of the TFTPD32 DHCP and TFTP server:
 Do not use it on a corporate network as it will conflict with the existing DHCP server.
 Always make sure the SP is stopped before starting the TFTPD32 application.
 If you do changes to the default configuration (shouldn’t be necessary) make sure that you
save the changes, otherwise they will not be taken into account.
 On Windows 7 you may have to change the permissions on TFTP32.exe. Please see
appendix 8.8 for instructions. You will need to do this if you adjust any settings.

4.7. PXE boot Steps for CX3 array

a. Power down the entire array (including DAE’s) using the standard CLARiiON shutdown
procedure.

CAUTION: Ensure only one Storage Processor is inserted, remove either Storage
Processor A or Storage Processor B prior to PXE booting the array. The recommendation
is to use SP-A.

b. Connect a CLARiiON serial cable between the laptop and the service port on the inserted
Storage Processor and a cross-over network cable to the management network port on the
inserted Storage Processor. See diagrams below for the CX3-20/CX3-40/CX3-80 to help
identify the ports to use:
CX3-20/CX3-40

26
 CXClear 1.1.3 User Guide

Figure 20 CX3-20 and CX3-40 backend

CX3-80

Figure 21 CX3-80 backend

c. Start PuTTY on the laptop (in C:\Program Files\EMC\CX Clear\bin\putty.exe or

C:\Program Files(x86)\EMC\CX Clear\bin\putty.exe for Windows 7 64 bit)

Or use the menu:

Start -> Programs -> EMC -> TsgTools -> CXClear -> Putty

Figure 22 Starting PuTTY

d. Connect it to the serial port then click the ‘Open’ button.

27
 CXClear 1.1.3 User Guide

Figure 23 PuTTY configuration

e. Start TFDPD32 from the menu

‘Start’ -> Programs -> EMC -> TsgTools -> CXClear -> TFTPD32
Please ensure that the laptop IP address has been set to 192.168.169.2 (check it by typing
ipconfig in a DOS box after the LAN cable is connected).

IMPORTANT: If you have previously used Tftpd32 to PXE boot an array, don’t forget to delete any
residual IP addresses as shown below.

28
 CXClear 1.1.3 User Guide

Figure 24 Delete residual Tftpd32 allocated addresses

f. Power up the array again following the standard CLARiiON power up procedure (DAE’s first
followed by the Storage Processor enclosure).
g. Verify all disks/DAE’s are powered up and wait until the disks settle before powering up the
SP.
h. The normal boot-up messages will display in the PuTTY screen. Initially you will see the BIOS
memory test followed by the screen below. Once this screen appears activate the PuTTY
window (click on the title bar) then press the Esc key twice (and only twice) in quick
succession.

IMPORTANT: It is important that if you don’t manage to catch this screen then you must power
down then power up the array as explained above. If you simply restart the SP you will not detect
any disks later on.

29
 CXClear 1.1.3 User Guide

Figure 25 CX3 boot-up screen

i. After a short pause when the menu below appears select the option shown highlighted in
white (option 3) and press Enter.

CAUTION: Please be careful to select this option and only this option!

30
 CXClear 1.1.3 User Guide

Figure 26 CX3 boot menu

j. The array will now attempt to PXE boot and if it is successful. You will see the progress screen
below:

Figure 27 Linux boot image transfer

31
 CXClear 1.1.3 User Guide

And the Tftpd32 ‘Log View’ tab looks like:

Figure 28 Tftpd32 log panel

k. Proceed to the CXClear Usage in section 5.

l. If you timed out on the PXE boot at some stage you will need to unload the drivers and power
cycle the DAEs as explained in section 7.6.

4.8. PXE boot steps for CX array

a. Power down the entire array (including DAE’s) using the standard CLARiiON shutdown
procedure.

CAUTION: Ensure only one Storage Processor is inserted, remove either Storage
Processor A or Storage Processor B prior to PXE booting the array.

b. Connect a CLARiiON serial cable between the laptop and the service port on the inserted
Storage Processor and a cross-over network cable to the management network port on the
inserted Storage Processor. See diagrams below for the CX series to help identify the ports to
use:

32
 CXClear 1.1.3 User Guide

CX700/CX600

Figure 29 CX600 and CX700 backend

CX500

IMPORTANT: Note that the CX500 uses a different type of serial cable to the rest of the CX range.

Figure 30 CX500 backend

CX400/CX300/CX200

33
 CXClear 1.1.3 User Guide

Figure 31 CX200, CX300 and CX400 backend

c. Start PuTTY on the laptop (in C:\Program Files\EMC\TsgTools\X Clear\bin\putty.exe

or C:\Program Files(x86)\EMC\CX Clear\bin\putty.exe for Windows 7 64 bit)
Or use the menu:

‘Start’ -> Programs -> EMC -> TsgTools -> CXClear -> Putty

Figure 32 Starting PuTTY

d. Connect it to the serial port then click the ‘Open’ button

34
 CXClear 1.1.3 User Guide

Figure 33 PuTTY configuration

e. Start TFDPD32 from the menu

‘Start’ -> Programs -> EMC -> TsgTools -> CXClear -> TFTPD32
Please ensure that the laptop IP address has been set to 192.168.169.2 (check it by typing
ipconfig in a DOS box after the LAN cable is connected) and if Windows 7 the permissions
are correct on the file (see appendix 8.8).

IMPORTANT: if you have previously used Tftpd32 to PXE boot an array, don’t forget to delete any
residual IP addresses as shown below:

35
 CXClear 1.1.3 User Guide

Figure 34 Delete residual Tftpd32 allocated addresses

f. Power up the array again following the standard CLARiiON power up procedure (DAE’s first
followed by the Storage Processor enclosure).
g. Verify all disks/DAE’s are powered up and wait until the disks settle before powering up the
SP.
h. The normal boot up messages will display in the PuTTY screen as shown below:

36
 CXClear 1.1.3 User Guide

Figure 35 CX boot-up screen

i. When the following screen appears, activate the PuTTY window (click on the title bar)
then press the Esc key to interrupt the break sequence:

Figure 36 CX boot sequence

j. You will then see the following screen:

37
 CXClear 1.1.3 User Guide

Figure 37 Interrupted CX boot sequence

k. Enter the engineering password ‘GO_sox’ to access the engineering menu:

Figure 38 Interrupted CX boot sequence

38
 CXClear 1.1.3 User Guide

l. The engineering menu will then appear, select the option that says ‘ICA Sub-Menu’. In the
example below this is 38 but this number is different depending on the model of the array:

Figure 39 CX ICA menu

m. In the ICS menu, select option 3 to PXE Boot Enable the drives:

39
 CXClear 1.1.3 User Guide

Figure 40 CX ICA sub-menu

n. Enter 15 for the number of drives to enable regardless of the number of drives physically in
the array:

Figure 41

40
 CXClear 1.1.3 User Guide

o. The following screen will then be displayed:

Figure 42

p. Press any key and then enter option 2 to start the PXE boot process:

Figure 43

41
 CXClear 1.1.3 User Guide

q. The array will now commence PXE booting:

Figure 44 Linux boot image transfer

And the Tftpd32 ‘Log View’ tab looks like:

42
 CXClear 1.1.3 User Guide

Figure 45 Tftpd32 log panel

r. Proceed to the CXClear Usage in section 5.

5. CXClear Usage
We now assume that CXClear is installed on the user laptop, the array is successfully PXE
booted (section 4) and the user has gathered the necessary files: the Erasure license and sp-
collect files and the optional ddbs_info file (section 2).

IMPORTANT: To avoid any discrepancies in the report make sure to run sp-collect
immediately prior to PXE booting the array and start the erasure.

The user must be aware of the array model and serial number.

5.1. Generalities
In the screenshots below the fields followed by an * are mandatory.

43
 CXClear 1.1.3 User Guide

Note for Windows XP and 32 Bit Windows 7 that a GUI log file is generated and stored in, for
Windows 7 ^4 bit it will be in the `programs files (x86)’ directory:
C:\Program Files\EMC\TsgTools\CxClear\logs\CXClearClient.log

5.2. Starting the CXClear GUI

Click the launch icon in the menu:
‘Program’ -> ‘EMC’ -> ‘TsgTools’ -> ‘CXClear’ -> ‘CXClear’

Or execute directly:
C:\Program Files\EMC\TsgTools\CXClear\bin\CXClear.exe

The user is then presented with the screen below:

Figure 46 GUI Home panel

For new erasure events, you are now ready to deploy and start the CXClear server. Please refer
to section 5.3 for the procedures.
If you are returning to monitor or complete an erasure event that was previously started, go to
section 5.4.

44
 CXClear 1.1.3 User Guide

5.3. Deploy and Start the CXClear Server

To deploy and start the CXClear server, use the ‘CXClear Operation’ ‘Start/Reconnect
Server Application’ menu to launch the start wizard:

Figure 47 Start/Reconnect menu option

Fill in your name, the password (f7jDr), the target CLARiiON model and the IP address used
during the PXE boot process. Attach the License, sp-collect, ddbs_info files and click the
‘Start/Reconnect’ button. Note that this operation typically takes around 30 seconds, but on
some system it can takes up to 3 or 4 minutes.

CAUTION: Make sure you select the correct ‘CLARiiON Model’. Selecting an incorrect
model may cause the wrong driver to be loaded, resulting in disks failing to be properly
detected.

Figure 48 Start panel

45
 CXClear 1.1.3 User Guide

If the deployment and checks are successful, you will see the message below:

Figure 49 Succesfully deployed message

5.4. Reconnecting to an already running CXClear server

If the CXClear server application has already been started, then you only need to fill the three first
fields on the Start panel (i.e. the license, sp-collect, model and ddbs_info will be ignored).

Figure 50 Reconnect panel

Click the ‘Start/Reconnect’ button and you will be reconnected to the running application.
Once reconnected the following message is displayed:

46
 CXClear 1.1.3 User Guide

Figure 51 Succesfully reconnected message

or this one if all the fields were filled in:

Figure 52 Succesfully reconnected message

5.5. Start/Reconnect error messages

DANGER: Some checks are carried out on the files provided at Start time, but make sure
the CLARiiON Model is correct or the drives may be incorrectly detected.
A wrong password or IP address will cause one of the following messages to be displayed:

Figure 53 Start with wrong password

Figure 54 Start with incorrect IP

47
 CXClear 1.1.3 User Guide

A file which isn’t a license or a license for the wrong array will trigger the following response:

Figure 55 Start with wrong license

A file which isn’t a license or license file which has been tampered with will trigger the following
response – Lava Authorisation errors are most likely related to Licensing file errors.

Figure 56 Invalid or corrupted license file

If the sp-collect file provided doesn’t match the license data or if a corrupted sp-collect file is
provided, the following message is displayed:

Figure 57 Start with invalid sp-collect

Figure 58 Start with invalid ddbs_info file

Figure 59 No disks detected when starting CXClear

48
 CXClear 1.1.3 User Guide

WARNING: If no disks are detected please go to troubleshooting section 7.6.

Figure 60 No disks detected when starting CXClear

Should the above message occur do not hit o.k. and reconnect to the application. The
application may allow you to continue but it is likely that no checking of the license and
sp_collects has been done – the cause of the deployment failure should be corrected.

5.6. Stopping the CXClear Server

To Stop the CXClear server and cancelled the ongoing erasure, use the ‘CXClear Operation’
‘Stop Server Application’ menu:

Figure 61 Stop menu option

Enter the CXClear password (f7jDr) then press the ‘Stop CXClear’ button:

49
 CXClear 1.1.3 User Guide

Figure 62 Stop Panel

The following message will be displayed after few seconds to one minute:

Figure 63 Succesfully stopped message

5.7. FLARE disks

There are 3 options for handling the erasure of disk drives that contain the FLARE Operating
System. If the array is being returned to EMC or disposed out of the customer’s control, the
‘Erase FLARE disks’ option should be selected. If the array is planned to be redeployed by the
customer, the ‘Preserve FLARE disks’ option must be chosen. The following information
provides more detail on the FLARE options:
 Wipe FLARE disks
If the ‘Erase FLARE Disks’ option is selected the FLARE disks will be wiped exactly like any
other disks.

50
 CXClear 1.1.3 User Guide

Note: If a valid ddbs_info file is provided the boot and utility FLARE partitions will be
erased after the other disks are completed. This gives the user a chance to stop the erasure
before they are irremediably wiped if he realizes he chose the wrong option. If no ddbs_info
file is provided the FLARE disks are erased concurrently with the other disks.

Figure 64 FLARE disks boot and utility partitions waiting to be deleted

 Preserve FLARE disks

When used with ‘Preserve FLARE disks’ erasing option the application leaves the boot
sector and the utility partition on the FLARE disks. All other FLARE information is erased.
These two sections of the FLARE disks are then used to re-image the array, see section 6 for
more information. An additional zero pass will be performed by the application to facilitate the
CLARiiON coming online. When FLARE is re-installed a navicli zeromark command must
be ran to write the zeromark data on all disks to allow fast binding. See section 7.7 for
instances where the ‘Preserve FLARE disks‘ option may not be enabled.
 Leave FLARE disks untouched
If you want the FLARE disks to be left unerased by the application, use the right click ‘Skip
disk’ option on the FLARE disks before starting the erasure. The FLARE disks are on Bus 0,
enclosure 0 and slot 0 to 4. The FLARE disks in slot 4 is always fully erased as it is not
needed for reconditioning the array. The first 4 disks on the GUI may not be BUS 0 by default.
You may want to sort the disk table per Bus and enclosure by clicking on the relevant header.

DANGER: This option must not be used on a customer site as it may leave customer
data on the skipped disks after the erasure is completed.

Figure 65 Manually skip FLARE disks

5.8. Start Erasure

 Once the application is deployed the erasure can be started. Start the Erasure Wizard by
clicking on the ‘Begin Erasure’ menu.

51
 CXClear 1.1.3 User Guide

Figure 66 Erasure menu option

WARNING: A message box will be displayed if you attempt to begin a second

erasure on an array already running an erasure. If you want to restart the erasure
you must use the ‘Stop Server Application’ first.

 First check that the serial number of the targeted array matches the one displayed on the first
wizard panel panel.
 Click ‘Next’.
The discrepancies between sp-collect and the disks detected are listed. First the disks listed in
sp-collect but not detected (a disconnected Bus in the example below). The disks shown in this
screen will not be erased by CXClear

Figure 67 Erasure wizard checks

 Click ‘Next’

52
 CXClear 1.1.3 User Guide

If there are disks listed in sp-collect but not detected by CXClear (disks faulty or removed after
sp-collect was run) the panel below is displayed:

Figure 68 Erasure wizard discrepancies 1

 Click ‘Next’.
If there are disks detected by CXClear but not listed in sp-collect (disks added after sp-collect was
run) the panel below is displayed.

Note: The bus number cannot be accurately determined if a disk is not listed in the sp-collect
but the enclosure and slot should be accurate. The disks shown in this screen will not be erased
by CXClear.

53
 CXClear 1.1.3 User Guide

Figure 69 Erasure wizard discrepancies 2

CAUTION: If you see any of two previous panels, it probably means that the sp-collect file
you provided is out of date and you should Stop the Server application without starting an
erasure and rerun sp-collect.

 Click ‘Next’.
 Then choose the number of passes, then click ‘Next’.

54
 CXClear 1.1.3 User Guide

Figure 70 Erasure wizard number of passes

 Choose whether FLARE disks are preserved or not. The second option will only be available if
a valid ddbs_info files was provided and there is a FLARE disk in either/all of bus 0 enclosure
0 slots 0 to 3 and the version of FLARE is above 2.19. This is not the case in the screenshot
below and the option is disabled.

55
 CXClear 1.1.3 User Guide

Figure 71 Erasure wizard FLARE erasure

 Click ‘Next’.
 Check that the erasure parameters are correct, then click ‘Finish’

56
 CXClear 1.1.3 User Guide

Figure 72 GUI Erasure wizard

When the erasure starts, the disks in the Disk List display will change colour. If after few seconds
you see 120 disks turn yellow and the percentage erased is increasing, you have successfully
started the erasure. At this point the CXClear GUI may be closed and the laptop disconnected
from the SP. If applicable, other CLARiiON erasures may be initiated.
To monitor the ongoing erasures and finish the erasure, the laptop must be reconnected to the
Ethernet port on the SP via the cross-over cable. Once connected, launch the CXClear GUI then
select the ‘Start/Reconnect’ option from the ‘CXClear Operations’ menu.

5.9. Monitor Erasure Process

Once the application is deployed onto the CLARiiON, the status of all disks can be monitored by
clicking on the ‘Disk List’ tab. This panel is made of two sections:
5.9.1. Header Section
The header section displays information about the number of disks and overall status of the
erasure.

57
 CXClear 1.1.3 User Guide

Figure 73 Dsk List panel header

 Total Disks: number of disks detected plus disks found in sp-collect.

 Number of Disks Erased: number of disks fully erased and verified. Shown in green in the
table.
 Number of Disks Erasing: number of disks being erased. Shown in yellow in the table.
 Number of Disks not Started: number of disks waiting to be erased. Shown in black and
white in the table.
 Number of Faulty/Cancelled disks: number of disks found faulty before or during erasure
plus the disks manually cancelled by the user. These disks will be marked Not Erased in the
report and are shown in red in the table.
 Number of Ignored Disks: number of disks moved or not listed in sp-collect. These disks will
be marked Not Erased in the report and are shown in red in the table.
 Number of Processed Sectors: total number of sectors processed so far. This is a sum of all
sector processed for all passes and across all disks.
 Number of Sectors not Yet Processed: total number of sectors remaining to be processed
for all passes and across all disks.
 Number of DOD passes: number of erasing passes requested. It is one of 3, 5 or 7 passes.
 Zero pass: yes/no. Indicates whether a zero pass will be carried out in addition to the
requested DOD ones. Will be set to ‘yes’ if the ‘Preserve FLARE’ erasing option was
selected.
 FLARE Recoverable: Will be ‘no’ if the ‘Preserve FLARE’ erasing option was selected.
 Percentage Erased: overall erasure and verification completion percentage.
 Time Started: date and time the erasure was started including time zone.

5.9.2. Disk List section

The disk list panel displays all the disks involved (disks detected and disks listed in sp-collect).
The rows in red highlight disks that will not be erased for some reason. In the case below bus 0
was disconnected so all these disks where not detected by the OS although they were listed in
sp-collect.

58
 CXClear 1.1.3 User Guide

Figure 74 Disk List sample 1

White rows show disks waiting to be erased.

59
 CXClear 1.1.3 User Guide

Figure 75 Disk List sample 2

Yellow rows indicate disks being processed (zeroing in the example below) while green ones
show disks successfully erased.

Figure 76 Disk List sample 3

Note: Note that the list can be sorted by clicking on a column header. If this is done while the
erasure is on-going the table may flash annoyingly. If this happens clicking on the ID header should
stop the flashing.

5.9.3. Columns meaning

 #: arbitrary disk ID starting at 0 in bus/enclosure/slot order.

60
 CXClear 1.1.3 User Guide

 Bus: bus number extracted from sp-collect.

 Enclosure: enclosure number returned by the hardware.
 Slot: slot number returned by the hardware. This number is followed by an asterisk if the disk
contains the FLARE operating system.
 Percentage Erased: percentage of the erasure and verification completed.
 Est. time Remaining: rough estimation of the time remaining, this number is not always
accurate.
 Passes Done: number of passes fully completed.
 Status: shows the current erasing status of the disk. Possible values are:
 Erasure Not Started
 Erasure in progress
 Zero in progress
 Verification in progress

Note: Due to the specificity of FLARE disks they stay in the ‘Verification in Progress’
state until fully erased. This is normal.

 Erased
 Disk Status: shows the status of the disk. Possible values are:
 Good: disk correctly detected without any faulty sectors so far.
 Not detected: listed in sp-collect but not in the list of disks detected by the OS, listed in
/dev/sgxx.

 Not in sp Collect: detected by OS but not listed in sp-collect.

 Not responding: detected but not responding to SCSI commands.
 Disk moved: serial number listed in sp-collect and detected by OS but slot/enclosure
mismatch.
 User skipped: listed out of the erasing list by the user before the erasure start.
 Cancelled by user: Cancelled by the user after the erasure is started.
 Faulty sector(s): at least one sector repeatedly failed being written. If more that 30 sectors
were repeatedly failing on writing, the application stops erasing this disk.
 Error following write failure: the reading of a sector failed after a write completed so we
were unable to verify that the write was successful. This error may disappear if the
erasure is restarted on this disk.

Note: CXClear makes a best effort at erasing all disks, so the erasure on disks with
the above two statuses will proceed and the row will be amber. If 30 such errors are
found on a disk CXClear gives up erasing it and the row become red. The report will
always mark these disks as ‘Not Erased’.

 Verification read error: at least one sector unreadable at verification time.

 Verification mismatch: at least one sector didn’t match expected data at verification time.
 Type: disk type as returned by the disk.
 Vendor: vendor as returned by the disk.

61
 CXClear 1.1.3 User Guide

 Size (GB): disk size in GB.

 Short Serial Number: 25 rightmost characters of the array serial number (the full serial is
visible in the View Details right click dialog).

5.9.4. Right Click Menus

Right clicking on a disk row will pop a menu of actions that can be carried out on this disk:

Figure 77 Right click menu

 View Details: opens a dialog box with all the disk details.

62
 CXClear 1.1.3 User Guide

Figure 78 Disk Details dialog

 Skip/Unskip disk: cancel the erasure of this disk if it is underway (yellow row) and change its
status to ‘Cancelled by user’. If the erasure is not started (white row) the disk status is
change to ‘User Skipped’. It can take a few seconds to a few minutes for the skip disk
command to register on disks that are erasing slowly.

Note: Note that this action is not reversible after an erasure is started, so be careful
before canceling a disk.

Note: It may take up to a couple of minutes before a disk cancellation is reflected in

the Disk List.

 Flash disk: flash the LED of the current disk for 15 seconds. This operation is not possible
while an erasure is underway.

63
 CXClear 1.1.3 User Guide

Figure 79 Disk LED flashing dialog

 Flash containing bus: flash the LEDs of all the disks on the same bus as the selected disk
for 15 seconds. This operation is not possible while an erasure is underway.

Figure 80 Bus LED flashing dialog

 View Sector Content: retrieve and display the content of a sector (or displays the hash of its
content as it might contain customer data). It can take a few seconds for the command to be
processed.

64
 CXClear 1.1.3 User Guide

Figure 81 Sectort Details dialog

Note: The LBA number is expressed in decimal.

Note: The LED Flashing and Sector content viewing operations are not available while an
erasure is ongoing. A warning message box will be displayed if you attempt to use them.

5.10. Retrieve Report and Logs

To retrieve the server log file, click on the ‘CXClear Operation’ ‘Retrieve Data’ menu

65
 CXClear 1.1.3 User Guide

Figure 82 Retrieve Data menu option

A log file named CXClearServer_arrayserialnumber_yyyy-mm-dd_hh-mm-

ss_retrieve.tar.gz is stored in c:\Program Files\EMC\TsgTools\CXClear\Logs. Or c:\
Program Files(x86) on 64 bit Windows 7.

Figure 83 Log retrieved message box

Note: The log file is automatically retrieved from the array when the ‘Start/Reconnect
Server Application’ and ‘Stop Server application’ menu options are selected. The file has
the same naming convention but ends with _start.tar.gz or _stop.tar.gz.

IMPORTANT: Always provide the Server log along with the client log ( CXClearClient.log file in
the same folder) when contacting Support.

5.10.1. Report
The erasure certificate PDF report is automatically generated after the erasure finishes. It will be
inserted in the .tar.gz file that is retrieved from the server (see section 5.10 above) and is
automatically extracted in the laptop Logs folder with the name pattern CXClearyyyymmdd-
hhmmss.pdf (e.g. CXClear20090909-164604.pdf).

5.10.2. Report signature

The erasure report is digitally signed by the CXClear application. When looking at the PDF report
the top right icon shows the signature status. There are three possible statuses:

66
 CXClear 1.1.3 User Guide

Figure 84 Report title

 Valid: represented by a green check mark. The signature and certificate have been
successfully verified (see section 5.10.3).
 Unknown: represented by a question mark. This usually means that the CXClear signing
certificate (self signed) hasn’t been recognised as a trusted certificate. Accept this certificate
as a trusted one and the icon should become green.
 Invalid: represented by a red cross. The document has been tampered with or more benignly
the certificate has expired.

5.10.3. Accepting CXClear signing certificate

The first time you open a CXClear erasure report the signature will be marked unknown. If you
click on the question mark icon you will see the following:

Figure 85 Report signature validation status

The dialog says that the report has not been tempered with since it has been signed but that the
signer is not known to the system.
So, if you are sure that you have opened a genuine CXClear report, do the following to add the
CXClear signing certificate to the list of trusted certificates:
a. Click on ‘Signature Properties’.
b. Click on ‘Show Certificate…’ from the ‘Summary’ tab.

67
 CXClear 1.1.3 User Guide

Figure 86 Adding CXClear signing certificate to trusted list 1

c. Select the ‘Trust’ tab in the ‘Certificate Viewer’ dialog.

68
 CXClear 1.1.3 User Guide

Figure 87 Adding CXClear signing certificate to trusted list 2

d. Click on ‘Add to Trusted Identities…’.

69
 CXClear 1.1.3 User Guide

Figure 88 Adding CXClear signing certificate to trusted list 3

e. Click ‘OK’ to accept.

70
 CXClear 1.1.3 User Guide

Figure 89 Adding CXClear signing certificate to trusted list 4

f. Close the dialogs.

g. Restart Acrobat Reader and the report will show as below:

Figure 90 Valid report signature

5.10.4. Report statuses

The disks listed in the report can have different statuses, here are the possible values:
 Erased: disk succesfully erased.

71
 CXClear 1.1.3 User Guide

 Not detected: listed in sp-collect but not in the list of disks detected by the OS (in
/dev/sgxx).

 Not in sp Collect: detected by the OS but not in sp-collect.

 Not responding: detected but not responding.
 Disk moved: serial number in sp-collect and detectd by OS but slot/enclosure mismatch.
 User skipped: listed out of the erasing list by the user before the erasure start.
 Erasure failed due to user cancellation: Cancelled by the user after the erasure is started.
 Erasure failed due to faulty sector(s): at least one sector repeatedly failed being written.
 Erasure failed due to error following write failure: a sector write failed and wasn’t
successfully recovered.
 Erasure failed due to verification read error(s): at least one sector unreadable at
verification time.
 Erasure failed due to verification mismatch: at least one sector didn’t match expected data
at verification time.

5.10.5. Report details

The report is made of several sections:

a. The legal disclaimer

b. The Erasure Request Details: show some information contained in the license file.

Figure 91 Report erasure request details

c. The Erasure Results Summary: information about the CLARiiON and the disks erased. The
Serial numbers are from the drive itself and do not reflect the EMC SN# on the front of the
drive.

Figure 92 Report erasure results summary

d. Disk that were not erased or failed the erasure:

72
 CXClear 1.1.3 User Guide

Figure 93 Report failed disk list

e. List of all disks:

Figure 94 Report full disk list

IMPORTANT: Disks that have failed to erase must be removed from the array and rendered to the
customer for final disposition. EMC Serial Numbers for drives removed should be recorded and
sent to the IB Group indicating that they need to be expired from the TLA and the status set to
‘Deinstall - Cust Site’. A softcopy of the Certificate of Completion/Report must be provided
to the customer and a copy be attached to the CSI Service Request when the SR is being closed
out.

6. Reconditioning Array after Erasure

Before re-imaging the array please familiarize yourself with the Back-Rev Procedure (non data-
in-place) for the Array (see below). It is available on the Existing Storage System/Host
procedures on the CLARiiON Procedure Generator. In particular, please note any FLARE
restrictions prior to the erasure.

73
 CXClear 1.1.3 User Guide

Note: CXClear will not preserve any FLARE disks with a version below release 2.19 and the
‘Preserve FLARE’ option will not be displayed on the GUI.

Figure 95

The recovery images are available on Software Download > CX-Series Utility Partitions,
Recovery Images & Conversion Files or CX3 Utility Partitions & Recovery Images section on both
the GS Website and the EMC Partner Services Web via PowerLink. The files are named
‘recovery image xxxxxxxxxx.mif’

These images are very large in size (up to 300 MB) so it might be best to download them before
you start the procedure.
The xxxxxx.pdu for a subsequent FLARE upgrade is smaller but still up to 80 MB in size so
these are best downloaded from Powerlink.
The procedure itself can take quite a long period of time (up to 2 hours) as multiple SP reboots
are required.
After re-imaging the array the user must run the Navisphere CLI zerodisk command to zero out
all the drives erased including the FLARE drives before proceeding with any BIND operations.
This will take as long as a single erasure pass on the largest disk in the array. Primus ETA
emc159191 has a good description of the zeromark command set.
From the command prompt on one of the SPs, type:
> navicli -h <SP_IP_address> zerodisk -messner <disklist>
[start|stop|status|getzeromark]

where:
 Start: Starts zeroing out the specified disks
 Stop: Stops zeroing out the specified disks
 Status: Returns current status of zeroing operation

74
 CXClear 1.1.3 User Guide

 Getzeromark: Returns current zeromark status

The zerodisk operation is complete when ‘getzeromark’ returns ‘0’ and ‘status’ returns
‘not running’.

Figure 96

Figure 97

7. Troubleshooting
Before logging a ticket with Support, please read the sections below that may provide assistance.

75
 CXClear 1.1.3 User Guide

7.1. Tftpd32.exe automatically deleted

We have occasionally noticed that the tftpd32.exe application or the CXClear.exe installer get
deleted at installation time. The issue was tracked down to McAfee and EMC IT security policies
not getting updated locally. IT managed to fix the issue; you may want to call them and refer to
ticket IM4196461.

7.2. No Network Connectivity between SP and Host

There are cases when an IP address is not successfully negotiated by the OS running on the
CLARiiON during PXE booting or is lost afterward. The symptoms are:
 TFTP/IP errors in the tftpd32 LogViewer tab.
 Apparent loss of connectivity during PXE booting (PXE booting may have continued normally
but invisibly).
 ‘Cannot ping the array...’ message when starting the server application.
 Fail to Start or Reconnect after succcesful PXE boot.

7.2.1. If the PXE booting process didn’t complete successfully

 Check network connections are correct (you could be connected to the wrong SP or an iSCSI
port on a CX3 or a CX500 console port).
 Check the IP allocated to the CLARiiON in the tftpd32 LogViewer tab, it should be
192.168.169.5

 Try PXE booting two laptops as explained in 7.3.

 Try using the serial port to the CLARiiON (see 7.3) to run ifconfig command on the array.
 Restart the full PXE boot process as described in section 4.
 Check that CSA isn’t blocking the array DHCP requests. See section 7.4.
 Try the Tftpd32 configuration settings suggested in 7.2.4.
 You may have to powercyle the array again if FLARE has “seen” the DAE’s.
 Ensure you did not remove the network cable before the boot sequence reached the DE login
prompt.

7.2.2. If the PXE process successfully completed

 Check that the LAN and serial cables are still properly connected.
 Make sure that you are Starting the Server Application (or reconnecting) to the correct SP.
(Check array ip with ifconfig and route on serial port as explained in 7.5.4)
 Reboot the array as a last resort. Bear in mind that if an erasure was ongoing it will have to be
restarted from scratch.

7.2.3. If the problem persists, contact support with:

 Screenshots of the PuTTY outputs (see 7.5.3).
 The Tftpd32 log. It is retrieved using the ‘Copy’ button on the ‘Log Viewer’ tab.
 The output of the ipconfig command run from a DOS box on the laptop\

76
 CXClear 1.1.3 User Guide

 The client log file C:\Program Files\EMC\TsgTools\CXClear\logs\CXClearClient.log

 The latest server log if you got the connection working at some point C:\Program
Files\EMC\TsgTools\CXClear\logs\CXClearServer_arrayserial_date_time_xxx.tar.g
z

 The output of the ipconfig and route commands executed on the array via the serial port (if
the OS has successfully started on the array).

7.2.4. Adjust Tftpd32 configuration settings

The Tftpd32 application is acting both as a DHCP and a TFTP server. It will provide the
CLARiiON with an IP address during the PXE booting and when the OS is started on the array. It
is supplied with most options preconfigured however in some cases some settings needed to be
adjusted to suit the local network addressing.
 Run C:\Program Files\EMC\TsgTools\CXClear\clariion-app\tftpd32.exe
 Click on the ‘DHCP Server’ tab.

Check that your laptop IP has

been given the static
192.168.169.2 value. (Will only
be shown when there is network
connectivity with the array)

Laptop gateway address. Value

is set at 0.0.0.0 by default. If
you are experiencing problems
try the value 192.168.169.1.
(the laptop gateway must
always be set to 192.168.169.1)

Then click ‘Save’ if any setting

was changed.

Figure 98 TFTPD32 configuration

 Change the value in the ‘Default router’ field to the IP address of the default router, use
either the value 0.0.0.0 or 192.168.169.1 for troubleshooting.
 Another setting that has helped some users is the ‘Persistent lease’ in the ‘Settings’
panel. By default the ‘Persistent lease’ is on but it can be turned off if there is a problem
allocating an IP to the array.

77
 CXClear 1.1.3 User Guide

Unchecking this setting may

help with the allocation of an IP
to the array.

Click ‘OK’ then click ‘Save’ if

any setting was changed.

Figure 99 Persistant leases setting

 Delete any already allocated IP lines that might be listed in the bottom table.
 Click on the ‘Save’ button.
 Close the window.

7.3. Check PXE booting between two laptops

A very good way to check whether PXE booting will work with your laptop (i.e. CXClear properly
installed and configured and no security application blocking PXE communications) is to PXE
boot a second laptop. The steps are the following:
 Intall and configure CXClear on your laptop (see section 0).
 Set static IP of your laptop to 192.168.169.2, mask 255.255.255.0 and Gateway
192.168.169.1 (see section 4.2).

 Switch off the second laptop.

 Connect the two laptops with the crossed over LAN cable.

78
 CXClear 1.1.3 User Guide

 Start TFTPD32 and delete possible residual IP addresses (see section 8.3e)
 Switch on the second laptop, press F12 to go into the boot menu and choose ‘Onboard NIC’
(on Dells laptops).
 After less than a minute, the TFTPD application should display the allocated IP
(192.168.169.5).

Figure 100 TFTPD32 allocated IP

 The screen of the second laptop will show the IP connection between the two machines and
the uploading of the boot image:

79
 CXClear 1.1.3 User Guide

Figure 101 Second laptop bootup screen

Note: CXClear will deploy in memory so the second laptop will not be affected in anyway and
nothing will be written on its disks.

7.4. Work around Cisco Security Agent

There is no way of knowing whether CSA is blocking communication coming from the array (no
entries in the event viewer) but if everything else fails it is worth trying temporarily disabling the
service:
 Set the static IP settings of your laptop to 192.168.169.2 as explained in section 4.2.
 Go to Settings -> Control Panel -> Administrative Tools -> Services and disable
the Cisco Agent service as shown below:

Note: Some people had to start their laptop in Safe Mode (press F8 at boot time on Dell
computers) to be able to disable CSA.

Note: If disabling the service doesn’t work try setting the service to Manual and reboot the
laptop.

80
 CXClear 1.1.3 User Guide

Figure 102 Temporarily disabling CSA

 Reboot your laptop off the EMC Corporate network.

 If the service succesfully stopped you will see the icon below in the bottom right of your
screen..

Figure 103 Check that CSA is stopped

 You should now be able to PXE boot an array or make a test with a second laptop as
explained in section 7.3.

DANGER: Don’t forget to set the CSA service back to ‘Automatic’ after the PXE booting is
successfully completed and all disks are detected.

7.5. Using the serial port to detect problems

The output of the boot and SCSI driver loading can be seen on the serial port if connected. The
following example is from a system with only seven disks.
Initially you will see the Linux kernel loading. When ‘Start/Reconnect Server Application’
is selected the SCSI drivers are loaded and typically what should be observed is that
 The SCSI subsystem is initialised.

81
 CXClear 1.1.3 User Guide

 The Fibre Channel cards are detected (the message about ‘too many PMC Sierra cards’
can be ignored).
 The disks are detected and assigned a WWN.
 The disks are then configured into the kernel (messages about unsupported sectors sizes can
be ignored)
The order in which the cards are detected bears no relation to the order of buses in the SP.

Figure 104

You may ignore messages about ‘too many PMC cards detected’.
After a pause you will see the disks beginning to be configured into the system.

Figure 105

Until eventually the last drive is loaded – in this case sg6. This may take a few minutes on larger
systems with many disk drives.

82
 CXClear 1.1.3 User Guide

Figure 106

If you get output similar to that beneath then the Fibre channel cards have been detected but no
disks have been found. Please see section 7.6 for a possible explanation.

7.5.1. IRQ conflicts

Occasionally you may see IRQ conflicts when the drivers are being loaded or cables are being
plugged into a PXE-booted SP:
irq 10: nobody cared (try booting with the "irqpoll" option)
[<c0133f82>] __report_bad_irq+0x22/0x80
[<c0134068>] note_interrupt+0x68/0xd0
[<c0133aea>] __do_IRQ+0xba/0xd0
[<c0105168>] do_IRQ+0x38/0x60
[<c010396a>] common_interrupt+0x1a/0x20
[<c011ad31>] __do_softirq+0x31/0xa0
[<c011adc6>] do_softirq+0x26/0x30
[<c010516d>] do_IRQ+0x3d/0x60
[<c010396a>] common_interrupt+0x1a/0x20

83
 CXClear 1.1.3 User Guide

[<f89734b9>] agtiapi_InitCard+0x189/0x2d0 [agtisa]

[<f897263c>] agtiapi_DetectHBA+0x40c/0x540 [agtisa]
[<f8811039>] init_this_scsi_driver+0x39/0xf8 [agtisa]
[<c012efe5>] sys_init_module+0xa5/0x180
[<c010289b>] sysenter_past_esp+0x54/0x79
handlers:
[<c01ff570>] (tg3_interrupt_tagged+0x0/0x170)
[<f8973680>] (agtiapi_IntrHandler+0x0/0x70 [agtisa])
[<f8973680>] (agtiapi_IntrHandler+0x0/0x70 [agtisa])
[<f8973680>] (agtiapi_IntrHandler+0x0/0x70 [agtisa])
[<f8973680>] (agtiapi_IntrHandler+0x0/0x70 [agtisa])
Disabling IRQ #10

The exact cause of the IRQ errors is not known but they are rare and will not normally show when
PXE booting. They are generally not persistent. If they do occur they may be related to a timing
issue. The IRQ errors do not always cause issues, but if they do you can try the following:
 When power-cycling allow some time between power-cycling each DAE individually.
 Unplug the back-end cables before power-cyling the DAE's and plug them back in afterwards.
 Ensure all Front-end ports are disconnected. This should have been done by default.
 It has been reported that empty DAE's may cause IRQ errors. If this is the case cable them
out.
 When you are power-cycling you can normally see the IRQ error occuring when a specific
DAE is being power-cycled. This DAE should be checked to see if there is anything unusual
about it. If not and it is possible recable this DAE to use the alternative LCC's or replace it.
 Try the alternate SP and see if it has the same issue.
 The default process is to ‘Start/Reconnect Server Application’ to start the SCSI
drivers, see if it loaded on the serial port then ‘Stop Server Application’ and powercyle
any missing DAE’s to pick up any drives or buses which may not have been detected initially.
If it is suspected that this is causing the IRQ errors. You may powercycle the DAE’s before
initially loading the SCSI drivers.
Unless the IRQ errors have brought down the network port or buses/drives are missing they can
be ignored.
Always confirm you can still see the network port after loading the drivers by pinging the IP
address you assigned to the SP from your laptop. If the array cannot be pinged then the only
option is to re-PXE boot the array.

7.5.2. Drives failing to spin up

We have occasionally seen SATA or ATA drives not spinning up when deploying onto the server.
The SCSI driver cannot start all disks and gives the impression that the deployment has been
interrupted.
The troublesome disks can be identified on the serial port when you see the kernel attempting to
spin them up. It takes the kernel over 30 seconds before it rejects a disk or spins it up. If there are
a lot of drives in this condition, it may take a long time. Normally they will not have their LED
illuminated. Re-inserting them and re-PXE booting normally corrects the issue.

84
 CXClear 1.1.3 User Guide

Figure 107

7.5.3. Capturing the Serial Port output

The output of the serial port can be captured to file by using the logging screen to capture the
output.

Figure 108

See the following screens for the setting that may need to be enabled:

85
 CXClear 1.1.3 User Guide

Figure 109

7.5.4. Forgot your IP address

If you forgot your IP address, you can get the assigned IP address by logging into the Serial port
as de, password de and using the /sbin/ifconfig and route commands to confirm your
network settings. The inet addr is the IP address you have been assigned. The mask is the mask
assigned and route shows the default gateway assigned.
-bash-3.00$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:60:16:25:E6:72
inet addr:10.64.22.46 Bcast:10.255.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:207133 errors:0 dropped:0 overruns:0 frame:0
TX packets:42980 errors:0 dropped:0 overruns:0 carrier:0
collisions:6801 txqueuelen:1000
RX bytes:33825990 (32.2 MiB) TX bytes:15430831 (14.7 MiB)
Interrupt:10
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:26712 errors:0 dropped:0 overruns:0 frame:0
TX packets:26712 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:9772760 (9.3 MiB) TX bytes:9772760 (9.3 MiB)

-bash-3.00$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.64.22.0 * 255.255.255.0 U 0 0 0 eth0

86
 CXClear 1.1.3 User Guide

default 10.64.22.1 0.0.0.0 UG 0 0 0 eth0

-bash-3.00$

7.6. Some disks or buses not discovered

The specific example of the disks on bus 0 failing to be discovered is detailed below, but a similar
approach can be taken every time all the disks within one or several DAEs are marked as ‘Not
Detected’.

If a full bus or full DAE is shown red on the sorted disk table (see screenshot in section 5.9.2) it
means the driver has failed to discover these drives in the array. This has been seen on several
array types on bus 0 when PXE booting with DAE3P’s and DAE4Ps (Stiletto’s).
It is likely that during the boot process the DAE4P's on bus 0 are being reset back to remote
mode. See section 4.5 for an explanation of the modes the DAE’s may be in.
a. It can easily be seen on the sorted disk list (click on the bus column header to sort the
table) that bus 0 is missing. In the following display, only 175 of 235 disks have been
detected and no disks have been detected on bus zero.

Figure 110 Bus 0 disks not detected

b. Check the back of the array to see if any of the DAE's have a flashing LED on the LCC cards,
see pictures below for location:

87
 CXClear 1.1.3 User Guide

Figure 111

Figure 112

Note: On some arrays it may be normal to have the LEDs flashing on bus 0 and have the
drives correctly detected.

c. Unload the SCSI drivers before manipulating any disks or DAE's. Click ‘CXClear
Operations’ ‘Stop Server Application’.
d. Enter the password (f7jDr) and click the ‘Stop CXClear’ button (see section 5.6 for details).
When the application has stopped hit the OK. button.

88
 CXClear 1.1.3 User Guide

e. Each DAE on the bus with a flashing LED must be power-cycled individually starting from
the highest enclosure to the lowest. Obviously with a DPE the DPE must be left
powered up.
f. After the power cycle the LEDs should not be flashing.
g. Normally start CXClear as explained in section 5.2.
h. All disks expected should now be detected. In the following example the count does not equal
235 as some disks were pulled from the array but are not visible on the screenshot. You can
see that backend bus zero has been detected.

Figure 113

IMPORTANT: If you have DPE and no disks on bus 0 are visible- unplug the Stiletto DAEs at
the DPE, re-PXE boot the array normally, Start the CXClear application, check the DPE disks
are now visible. You can powercycle and re-plug the Stilletto DAEs then follow the procedure
again from step c. to detect the disks in the stilettos. skipping steps d. and e.

7.7. ‘Preserve FLARE’ erasing option greyed out

CXClear doesn’t allow the preservation of the FLARE disks in the following cases:
 ddbs_info file not provided at Start time. In this case Stop then re-Start the server application
from the ‘CXClear Operations’ menu.
 FLARE version older than 2.19.
 FLARE disks not in the system (bus0, enclosure 0, slot 0-4). CXClear will not allow the FLARE
preservation if these slots are empty.
 Disks in bus 0, enclosure 0, slot 0-4 do not match the disks listed in sp-collect.
If you take out the FLARE disks and replace them by other non-FLARE disks. CXClear will
find out they do not match sp-collect and will highlight them in red. The ‘Preserve FLARE’

89
 CXClear 1.1.3 User Guide

option will greyed out. The same will happen if you move disks from other slots into the
FLARE ones, the disks are then marked as moved.

7.8. GUI hangs or commands not reaching the array

It happened occasionally that a GUI freeze is experienced, in this case close the GUI (click on the
top right X) and restart it from the Start -> Programs -> EMC -> TsgTools -> CXClear ->
CXClear. Then use the Start menu option to start the application or reconnect to it if it is already
started. This has no impact on the application running on the array and any on-going erasure.
The same applies if you receive an unexpected error message from the GUI like a network
timeout.

7.9. Detect Erroneous disks

Disks that won’t be erased by CXClear can be split into two categories: disks that will be ignored
because they are seen by the OS and not listed in the sp-collect and those listed in sp-collect but
not seen by the OS. Neither will be marked as erased in the final report. If you have either of
these use cases you may want to remove the disks from the system or check the hardware
configuration.
In either case we need to unload the SCSI drivers and restart the application.
If the PXE booting has enabled a bus:.
a. First sort the disks per bus number on the GUI (click on ‘Bus’ column header). Ideally all
disks should be detected and are online. However disks failing to respond correctly to
SCSI requests or not matching the sp-collect list of drives will be highlighted in red with a
Disk Status of respectively ‘Not Responding’ and ‘Not Detected’.
b. You can locate individual disks by right clicking a specific row and selecting the ‘Flash
disk’ command, the selected disk LED will flash for 15 seconds.

c. You can also flash the LEDs of all disks on a specific bus by right clicking any disk on this
bus and choosing the ‘Flash containing bus’ command.
d. If you wish to remove/add disks, powercyle DAE’s or reload the application select the
‘Stop CXClear Server’ menu command, type in the CXClear password (f7jDr) and
click ‘Stop CXClear’.
e. Make whatever changes you require. If powercycling DAE’s start from the highest
enclosure number to the lowest.
f. Select the ‘Start/Reconnect CXClear Server’ menu command, this may take few
minutes. It will reload the SCSI drivers, rediscover the disks and restart the CXClear
application.

8. Appendices
8.1. Install winscp418setup.exe on your laptop

90
 CXClear 1.1.3 User Guide

This utility shouldn’t be useful anymore with CXClear 1.1. I leave the installation procedure in the
documentation just in case CXClear application finds itself in a deadlock and the user cannot
Stop or Retrieve the logs using the GUI menu operations.

a. Double click the installer located in

C:\Program Files\EMC\TsgTools\CXClear\install\winscp418setup.exe

b. Select the desired language for the install & click OK

Figure 114

c. Click Next

Figure 115

d. Click Next

91
 CXClear 1.1.3 User Guide

Figure 116

e. Click Next

Figure 117

f. Click Next

92
 CXClear 1.1.3 User Guide

Figure 118

g. Click Install

Figure 119

h. Click Finish

93
 CXClear 1.1.3 User Guide

Figure 120

i. When WinSCP starts, the defaults need to be set up to use SCP. In the drop down menu,
select the SCP File protocol.

Figure 121

j. Click the Advanced options tick box.

94
 CXClear 1.1.3 User Guide

Figure 122

k. Click on SCP/Shell & untick the two boxes for “Try to get full timestamp” & “Lookup user
groups”

Figure 123

l. Click on Stored session then click “Set defaults”

95
 CXClear 1.1.3 User Guide

Figure 124

m. Click OK on the pop up dialogue box

n. Click on Close.

8.2. Manually Retrieve Log files

Same comment as above, either the ‘Retrieve Data’ or ‘ Stop Server Application’
menus should be able to retrieve the logs in all cases. If you want to manually retrieve the
CXClear log follow the instructions below.

Note: This can only be done after an IP address has been successfully negotiated between
the laptop and the CLARiiON.

a. Install WinSCP (if you haven’t already done it, see appendix 8.1).
b. Connect to the array using PUTTY:

96
 CXClear 1.1.3 User Guide

Figure 125

c. Log onto the array (login: de, password: de).

d. Type the command:
tar -c /var/log/de/* -f array-10.64.22.40-log.tar

97
 CXClear 1.1.3 User Guide

Figure 126

e. Connect top the array using WinSCP (user: de, password: de) and make sure the protocol is
set to SCP:

Figure 127

98
 CXClear 1.1.3 User Guide

f. Accept the key caching request:

Figure 128

g. Copy the file to the laptop:

Figure 129

8.3. PAS TS Task Type and Task Number is CSI Service Request
When creating the Service Request, the PAS Task Type should be TS Work and the task number
is entered into the defined field as noted in the screenshots below:

99
 CXClear 1.1.3 User Guide

Figure 130

Figure 131

8.4. CSI Service Request – Certificate of Completion Attachment

When closing the CSI Service Request, the Certificate of Completion and erasure report should
be attached to the SR using the attachment option depicted in the screenshot below.

100
 CXClear 1.1.3 User Guide

Figure 132

8.5. Generate ddbs_info file using EMCRemote

a. Log on to CLARiiON SPA or SPB using EMCRemote

Figure 133 EMCRemote screenshot

b. Open a DOS prompt (Start -> Run -> type ‘cmd’)

c. Run the command:

> ddbs_info -ls 0 > ddbs_SN#.txt
Where SN# is the serial number of the array

101
 CXClear 1.1.3 User Guide

Figure 134 Generate ddbs_info file

d. Transfer the file back to your host using file transfer manager noting the location

102
 CXClear 1.1.3 User Guide

Figure 135 Retrieve ddbs_info file 1

Figure 136 Retrieve ddbs_info file 2

e. Delete the file on the array when done

103
 CXClear 1.1.3 User Guide

Figure 137 Delete ddbs_info

Figure 138

f. You are then finished

104
 CXClear 1.1.3 User Guide

Figure 139 Terminate EMCRemote session

8.6. Tftpd32 log sample

Here is a copy of the log produced by Tftpd32 during the successful PXE booting of a CLARiiON
given an IP 10.64.22.76 (we used this value instead of the default 192.168.169.5 to connect to
the array from our desks):
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:60:16:25:90:5F [11/09
14:27:23.008]
DHCP: proposed address 10.64.22.76 [11/09 14:27:23.008]
372 Request 2 not processed [11/09 14:27:23.088]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:60:16:25:90:5F [11/09 14:27:27.074]
Previously allocated address 10.64.22.76 acked [11/09 14:27:27.074]
Connection received from 10.64.22.76 on port 2070 [11/09 14:27:27.104]
Read request for file <pxelinux.0>. Mode octet [11/09 14:27:27.134]
Using local port 1073 [11/09 14:27:27.144]
372 Request 2 not processed [11/09 14:27:27.164]
<pxelinux.0>: sent 22 blks, 11164 bytes in 0 s. 0 blk resent [11/09
14:27:27.354]
Connection received from 10.64.22.76 on port 57089 [11/09 14:27:27.394]
Read request for file <pxelinux.cfg/0A40164C>. Mode octet [11/09 14:27:27.434]
File <pxelinux.cfg\0A40164C> : error 2 in system call CreateFile The system
cannot find the file specified. [11/09 14:27:27.434]
Connection received from 10.64.22.76 on port 56834 [11/09 14:27:27.434]
Read request for file <pxelinux.cfg/0A40164>. Mode octet [11/09 14:27:27.494]
File <pxelinux.cfg\0A40164> : error 2 in system call CreateFile The system
cannot find the file specified. [11/09 14:27:27.514]
Connection received from 10.64.22.76 on port 56579 [11/09 14:27:27.534]

105
 CXClear 1.1.3 User Guide

Read request for file <pxelinux.cfg/0A4016>. Mode octet [11/09 14:27:27.554]

File <pxelinux.cfg\0A4016> : error 2 in system call CreateFile The system cannot
find the file specified. [11/09 14:27:27.574]
Connection received from 10.64.22.76 on port 56324 [11/09 14:27:27.594]
Read request for file <pxelinux.cfg/0A401>. Mode octet [11/09 14:27:27.614]
File <pxelinux.cfg\0A401> : error 2 in system call CreateFile The system cannot
find the file specified. [11/09 14:27:27.644]
Connection received from 10.64.22.76 on port 56069 [11/09 14:27:27.644]
Read request for file <pxelinux.cfg/0A40>. Mode octet [11/09 14:27:27.644]
File <pxelinux.cfg\0A40> : error 2 in system call CreateFile The system cannot
find the file specified. [11/09 14:27:27.644]
Connection received from 10.64.22.76 on port 55814 [11/09 14:27:27.644]
Read request for file <pxelinux.cfg/0A4>. Mode octet [11/09 14:27:27.654]
File <pxelinux.cfg\0A4> : error 2 in system call CreateFile The system cannot
find the file specified. [11/09 14:27:27.654]
Connection received from 10.64.22.76 on port 55559 [11/09 14:27:27.654]
Read request for file <pxelinux.cfg/0A>. Mode octet [11/09 14:27:27.654]
File <pxelinux.cfg\0A> : error 2 in system call CreateFile The system cannot
find the file specified. [11/09 14:27:27.654]
Connection received from 10.64.22.76 on port 55304 [11/09 14:27:27.654]
Read request for file <pxelinux.cfg/0>. Mode octet [11/09 14:27:27.654]
File <pxelinux.cfg\0> : error 2 in system call CreateFile The system cannot find
the file specified. [11/09 14:27:27.654]
Connection received from 10.64.22.76 on port 55049 [11/09 14:27:27.654]
Read request for file <pxelinux.cfg/default>. Mode octet [11/09 14:27:27.654]
OACK: <tsize=190,> [11/09 14:27:27.664]
Using local port 1082 [11/09 14:27:27.664]
<pxelinux.cfg\default>: sent 1 blk, 190 bytes in 0 s. 0 blk resent [11/09
14:27:27.724]
Connection received from 10.64.22.76 on port 55050 [11/09 14:27:27.805]
Read request for file <message>. Mode octet [11/09 14:27:27.805]
File <message> : error 2 in system call CreateFile The system cannot find the
file specified. [11/09 14:27:27.815]
Connection received from 10.64.22.76 on port 54795 [11/09 14:27:27.815]
Read request for file <bzImage>. Mode octet [11/09 14:27:27.815]
OACK: <tsize=1135551,> [11/09 14:27:27.815]
Using local port 1084 [11/09 14:27:27.815]
<bzImage>: sent 2218 blks, 1135551 bytes in 1 s. 0 blk resent [11/09
14:27:28.766]
Connection received from 10.64.22.76 on port 54796 [11/09 14:27:28.766]
Read request for file <initrd-bb.gz>. Mode octet [11/09 14:27:28.776]
OACK: <tsize=42180058,> [11/09 14:27:28.776]
Using local port 1085 [11/09 14:27:28.776]
<initrd-bb.gz>: sent 82383 blks, 42180058 bytes in 36 s. 0 blk resent [11/09
14:28:04.758]

8.7. SP-Collect Retrieval methods

The sp-collect information may be gathered using different methods:
a. Via EMCRemote to the SP, run spcollect.pl from a command prompt and the spcollect zip
file will be created in the c:\dumps folder.

b. Run the commands:

> Naviseccli -h <SP-IP> spcollect -messner
And to retrieve them:
> Naviseccli -h <SP-IP> managefiles -retrieve
Other options are -list and -delete <-o> <-all|-file filenames>

c. Use Navisphere to start the sp-collect

106
 CXClear 1.1.3 User Guide

Figure 140 Generate sp-collect file

And then retrieve the log using the file transfer manager

Figure 141 Retrieve sp-collect file

107
 CXClear 1.1.3 User Guide

Figure 142 Retrieve sp-collect file

Method c. was used during qualification but both other methods should also be applicable.
d. As of CXClear v1.1 SP-Collects generated via the NST (Navisphere Service Taskbar) are also
supported.

Figure 143 NST Connection

8.8. CXClear and Windows 7

108
 CXClear 1.1.3 User Guide

A fundamental step toward increasing the security of Windows® is enabling interactive users to
run with a standard user account, which gives them access to only a limited set of permissions
and privileges. By default, Windows Vista® and Windows Server® 2008 will run every application
as a standard user even if a user logs on as a member of the Administrators group. Conversely,
when users attempt to launch an application that has been marked as requiring administrator
permissions, the system will explicitly ask them to confirm their intention to do so. Only
applications running with Administrator privileges can modify system and global settings and
behavior. This feature of Windows Vista and Windows Server 2008 is User Account Control
(UAC).

CXClear was designed to run under Windows XP and with the default installation procedure
places it’s files in the C:\Program Files\EMC directory .

When installing in Windows 7 the default installation places the files in either the C:\Program
Files\EMC directory by default under 32 bit Windows or C:\Program Files(x86)\EMC under
Windows 7 64bit

By default in Windows 7 the User does not have permission to write to these area’s.

The easiest solution is to either

A) install CXClear in an area where the User has permission to write e.g. C:/Temp.
B) Check that the permission on all the files that are required to run CXClear have
administrative rights to that they can write to the C:\Program Files\EMC directories. The
following files should be checked prior to running them and if necessary changed.

C:\{install dir}\EMC\TsgTools\CXClear\bin\CXClear.exe
C:\{install dir}\EMC\TsgTools\CXClear\bin\putty.exe (if you wish to save files or settings)
C:\{install dir}\EMC\TsgTools\CXClear\ clariion-app\ tftpd32.exe
C:\{install dir}\EMC\TsgTools\CXClear\ install\ winscp418setup.exe (if required)

Simply select the application properties and change the application to run with
Administrative rights See Figure 139/140

It is worth checking these files have the correct permissions should you experience any
problems with the running of CXClear.

109
 CXClear 1.1.3 User Guide

Figure 144 Changing CXClear.exe to run with adminstrative rights

110
 CXClear 1.1.3 User Guide

Figure 145 Changing CXClear.exe to run with adminstrative rights

When running CXclear it is worth checking in the `C:\Program

Files\EMC\TsgTools\CXClear\logs’ directory to make sure that the following files are being
generated:-
“CXClearClient.log” as the GUI starts
“CXClearServer_{Clar_SN) _{date}_start.tar.gz” when the erasure is being started.

If you have ran the program with standard user privileges and used the default install
directories you may find that the no logs have been written to the the C:\Program
Files\EMC\TsgTools\CXClear\logs directory.
The logs have not disappeared Windows 7 redirects any request to write to a system
folder that the user lacks permission to a local folder. Search under C:\Users\<user
name>\ directory to see if you can find the files.

Alternatively it may be possible to see the files if the “Compatibility files” button is enabled on the
drop down in the directory you expected to see the logs in. See Figure 145. This will not be
highlighted if all the applications writing to this area have write permission.

111
 CXClear 1.1.3 User Guide

Figure 146 Compatibilty files

Good documentation on Windows & and application redirection is available on

http://windowsteamblog.com/windows/b/developers/archive/2009/08/04/user-account-control-
data-redirection.aspx

112