Easy Setup Wizard Failure; Cli Command Problems - IBM Storwize V7000 Unified Series Problem Determination Manual

Easy Setup Wizard failure

DNS errors can cause Easy Setup Wizard to fail with no clear error messages.
The Easy Setup Wizard process can fail if there are issues with the DNS
information entered into the system. Entering the incorrect information is a
common problem, particularly in step 5. This step requires that you fill in the
following fields:
v Domain name
v Domain Admin user ID
v Domain Admin user password
v DNS servers
Entering the incorrect information may result in messages such as domain name
not found or wrong user or password. However, a failure can also occur when
connecting or verifying the DNS server, which is the last entry in this step. In this
case, an error message does not appear, but the step fails or hangs.
One known cause of this type of failure occurs when the DNS server Address
Resolution Protocol (ARP) table shows the IP address entered was previously
configured in the ARP table. In this case the DNS server does not allow the
connection. An unused IP address needs to be entered or the address from the
ARP table needs to be removed before restarting the Easy Setup Wizard. Exit out
20
Storwize V7000 Unified: Problem Determination Guide Version
Table 7. CLI command problems
CLI Command
mkfs
Symptom/Message
SG0002C Command
exception found : Disk
<arrayname> might still
belong to file system
<filesystemname>.
Action
This message indicates that the
arrays listed in the error message
appear to already be part of a file
system.
1. Check the list of array names
that you specified in the mkfs
command. If the mkfs command
has been used to create multiple
file systems, you might have
used the same array name in
more than one file system. If
this is the case, correct the list of
array names.
2. If you are certain there is no
data on the system, this
problem might have been
caused by an error during the
manufacturing cleanup process
before the machine was
shipped. In this case, you can
work around the problem by
appending the --noverify
parameter to the mkfs
command. Never use the
--noverify parameter on a
system with customer data
unless directed to do so by
support personnel; improper
use can cause unrecoverable
data loss.