IBM Storwize V7000 Unified Problem Determination Manual page 35
Hide thumbs
Also See for Storwize V7000 Unified:
- Introduction and implementation manual (670 pages) ,
- Problem determination manual (474 pages) ,
- Troubleshooting and maintenance manual (189 pages)
Table of Contents
Advertisement
– Product Family: Disk Systems
– Product: IBM Storwize V7000 Unified
– Release: All
– Platform: All
Before loading the USB flash drive verify it has a FAT32 formatted file system.
Plug the USB flash drive into the laptop. Go to Start (my computer), right-click the
USB drive. The general tab next to File system should say FAT32.
v If the USB flash drive is not formatted as FAT32, format it. To format, right-click
it, select format, under filesystem. Select FAT32 and then click Start. Continue as
prompted.
InitTool.exe is not loaded on the USB key, or fails to launch:
v Install the latest InitTool.exe (or reinstall if tool is not launching). Go to
http://www-933.ibm.com/support/fixcentral/options and select the following
options to locate the tool. The options are listed under the Select product tab, at
the bottom of the page:
– Product Group: Storage Systems
– Product Family: Disk Systems
– Product: IBM Storwize V7000 Unified
– Release: All
– Platform: All
Amber LED on node canister does not stop flashing during install:
Allow at least 15 minutes for the LED to stop flashing. If flashing continues
beyond 15 minutes, remove the USB flash drive and insert in your laptop.
Navigate to the satask_results.html file and scan for errors and follow the service
action recommendation. Take that action and retry installation.
An error is posted in the satask_results html:
Take the recommended service action given by sainfo lsservicerecommendation in
the satask_results html file, reboot the node, and restart the initial setup procedure.
If satask_results.html contains node error code 835 or node error code 550 then this
can indicate that the node canisters were not able to communicate with each other
at some time during the creation of the block cluster. This can occur because the
PCIe link between the node canisters is temporarily broken when the nodes are
restarted, as part of the create cluster process. This can generate node error codes
835 and 550. These are transitional errors that can be ignored if the nodes are now
in active state with no errors. Follow this procedure to check that the errors are
gone, using the USB flash drive:
v Save a copy of satask.txt and satask_results.html.
v Make sure that there is no satask.txt file on the USB flash drive before you plug
it into the control enclosure. Plug the USB flash drive into the control enclosure.
The orange fault light should go on for a short time only (such as a slow blink
for a few seconds). Wait for the orange fault light to go out then unplug the USB
flash drive and plug it into another computer so that you can look at the
contents of the satask_results.html file on the USB flash drive. The
satask_results.html will contain the output from a number of sainfo commands.
v Check the following:
Chapter 3. Getting started troubleshooting
11
Advertisement
Table of Contents
Troubleshooting
