|
0
|
Operation completed normally. |
|
1
|
Unable to complete operation. Check the log file. |
|
2
|
Undefined device subtype. Check the log file.
|
|
3
|
Undefined device type. Check the log file. |
|
4
|
Operation in progress. |
|
5
|
One or more collection failed.
This
is applicable only in case of multiple device collection and not for
single device collection. When you invoke Lasso in quiet mode (CLI)
with a customer configuration file, and if any one of the device collection
fails, Lasso will exit with this error.
|
|
6
|
Collection and upload failed.
If
the collection failed and also the upload, Lasso will exit with this
error code.
|
|
7
|
Upload unsuccessful.
|
|
9
|
Unknown option. Check the log file. |
|
10
|
Parameter is already specified for the session.
Check the log file.
|
|
11
|
Operation timed-out.
|
|
20
|
UPLOAD_UNKNOWN_ERROR
Unknown error
while uploading.
|
|
21
|
UPLOAD_OPTION_ERROR
Upload option
provided is not found. Check the option provided to upload the file.
|
|
22
|
UPLOAD_FILE_SIZE_ERROR
File size
is large. Ensure that the file size does not exceed the expected limit.
|
|
23
|
UPLOAD_CERTIFICATE_ERROR
Certificate
authentication failed. Ensure that the client certificate is valid
and able to authenticate to the server.
|
|
24
|
UPLOAD_CHUNK_ERROR
Not able to split
the file into chunks. Ensure that the file size is not equivalent
to zero KB.
|
|
25
|
UPLOAD_SERVER_ERROR
Not able to
receive acknowledgement for the chunk sent. Ensure that the server
is responding to the client's requests.
|
|
26
|
UPLOAD_INVALID_FILE_ERROR
File
not found. Ensure that the file is available to upload.
|
|
27
|
UPLOAD_TIMEOUT_ERROR
The upload
has timed out. Check the network connection.
|
|
28
|
UPLOAD_MODULE_INIT_FAILED
Failed
during the module initialization.
|
|
29
|
UPLOAD_MODULE_PROXY_ERROR
Unable
to reach Proxy server. Check the proxy settings in the browser.
|
|
30
|
UPLOAD_MODULE_PROXY_UNSUPPORTED_AUTH_SCHEME
Unsupported type of authentication scheme.
|
|
31
|
AUTHENTICATION_FAILED
Authentication
for proxy has failed.
|
|
32
|
UPLOAD_MODULE_RETRY_SEND_CODE
Retry
upload after the certificates are installed.
|
|
101
|
%emcExecutable% not found.
The package is either corrupt or not installed correctly. Try to reinstall
Lasso.
|
|
102
|
%dsetExecutable% not found.
The package is either corrupt or not installed correctly. Try to reinstall
Lasso.
|
|
103
|
Failed to determine remote system drive and remote
system root.
|
|
104
|
Failed to create temporary directory on remote
host.
|
|
105
|
Failed to retrieve completed collection from remote
system.
Lasso is unable to copy the completed collection
from the remote system. Make sure that dot net version 2.0 or later
is installed on the remote system to run
Dell Collector and create the collection file. Try to run Lasso again.
|
|
106
|
Failed to copy EMC Reports to remote host.
Lasso is unable to copy the script from the remote system
and the script may be suspended. Try to reboot the remote host. If
rebooting failed, try to navigate to
Task Manager on the remote host and find an
EMCReport process and terminate
it.
|
|
107
|
Host collection execution failed.
Lasso is unable to copy the script from the remote system and the
script may be suspended. Try to reboot the remote host. If reboot
failed, try to navigate to
Task Manager on
the remote host and find the
EMCReport process and terminate
it.
|
|
108
|
Failed to retrieve completed collection from
remote host.
Lasso is unable to copy the completed
collection from the remote system. Try to run Lasso again. If this
error persists, check the
%SystemRoot%\EMCReports\collection\zip\ directory for a
.zip file in the remote host
system.
|
|
109
|
Another collection process may already be running
on the host.
Wait for the process to complete. If
the error persists, then the remote script may be suspended. Try to
reboot the remote host system. If rebooting failed, try to terminate
the
EMCReport.exe/DellCollector.exe or
emcgrab.sh/dellcollector.sh process by navigating to
Task Manager in Windows or
ps -elf in the remote host system.
|
|
110
|
WMIC service currently unavailable.
|
|
111
|
Execution of a process or a command
on the remote machine is unsuccessful.
|
|
113
|
Unable to access the remote folder.
|
|
114
|
Copying file to remote host was
unsuccessful.
|
|
115
|
Cluster IP cannot be provided for windows host
collection. Please provide the node IP and retry the collection.
|
|
118
|
Copying HyperVRecognize.exe to
remote host was unsuccessful.
|
|
119
|
Host collection execution failed during HyperV
Recognition.
Lasso is unable to copy the script from
the remote system and the script may be suspended. Try to reboot the
remote host. If rebooting failed, try to navigate to
Task
Manager
on the remote host and find the
HyperVRecognize process and terminate it.
|
|
120
|
Failed to retrieve completed collection from
remote host.
Lasso is unable to copy the completed
collection from the remote system. Try to run Lasso again. If the
error persists, check for the
.txt file in the
%SystemRoot%\temp\Dell\Lasso\HyperV\ sub directories on
the remote host system.
|
|
121
|
Failed to find debug log file in remote host.
Lasso is unable to find the debug log file in the remote
host. Try to run Lasso again. If the error persists, check the
%SystemRoot%\temp\Dell\Lasso\DellCollector\ sub directories
for a
.txt file.
|
|
122
|
Failed to retrieve debug log file from remote
host.
Lasso is unable to copy the debug log file from
the remote system. Try to run Lasso again. If the error persists,
check the
%SystemRoot%\temp\Dell\Lasso\DellCollector\ sub directories for a
.txt file in the remote
host.
|
|
150
|
Unable to determine the switch
model details.
|
|
151
|
DSET validation is not successful. Dell System
E-Support Tool is unable to connect to the system using any of the
supported protocols.
|
|
152
|
DSET validation is not successful. Unable to gather
Chassis or Storage data. Make sure that credentials and namespace
are correct.
|
|
153
|
DSET validation is not successful. DSET application
must be run with administrator or root privileges.
|
|
154
|
DSET validation is not successful. Exiting report
collection because of an internal error.
|
|
155
|
DSET validation is not successful. Unable to gather
Software or Logs data. Make sure that user name and password are correct,
and then retry.
|
|
156
|
DSET validation timeout. |
|
157
|
DSET validation is not successful. Validating Dell
System E-Support Tool is not successful because of an unknown error
code.
|
|
187
|
Unable to validate the device. Make sure that
the connection to the device is available through FTP and then retry
the operation.
|
|
188
|
Unable to validate the device. Make sure that
MDSM Software has valid permissions and then retry the operation.
|
|
189
|
Unable to validate the device. Make sure that MD
Storage Manager version is supported for the device and then retry
the operation.
|
|
190
|
Unable to validate the device. Make sure that you
login as administrator and then retry the operation.
|
|
191
|
Unable to validate the device. Timed out during
validation.
|
|
192
|
Unable to validate the device. Make sure that the
IP address or hostname are correct and then retry the operation.
|
|
193
|
Unable to validate the device. Make sure that
the connection to the device is available through SSH and does not
have active SSH console open, and then retry the operation.
|
|
194
|
Unable to validate the device. Make sure that
you have provided CLI credentials and then retry the operation.
|
|
195
|
Unable to validate the device. Make sure that
the connection to the device is available through SNMP, IP address
or hostname and community string are correct and then retry the operation.
|
|
196
|
Unable to validate the device. Make sure that it
is a valid Group or Member or Network Management IP address and then
retry the operation.
|
|
197
|
Unable to validate the device. Make sure that
the firmware version is 4.3.0 or later.
|
|
198
|
Unable to validate the device. Make sure that
the connection to the device is available through SSH or Telnet and
does not have active SSH or Telnet console is open, and then retry
the operation.
|
|
199
|
Unable to validate the device. Make sure that the
IP address or hostname, user name, and password are correct, and then
retry the operation.
|
|
200
|
plink.exe not found.
|
|
201
|
pscp.exe not found.
|
|
202
|
Lasso_grab.sh not found.
The error occurs when the package is either corrupt or
not installed correctly. Try to reinstall Lasso.
|
|
203
|
EMC executable not found.
The error
occurs when the package is either corrupt or not installed correctly.
Try to reinstall Lasso.
|
|
204
|
VMware support logs not collected.
|
|
205
|
VMware execution failed.
The command
vm-support failed for reason such as the collection
may have timed out. Try to collect again or try to collect manually.
|
|
206
|
Failed to retrieve completed collection.
Check the remote host at the
/tmp/Dell/Lasso/[timestamp] location for the collection.
|
|
207
|
Failed to copy
Dell Collector executable to remote host.
The error could because
of insufficient space or insufficient privileges. Check the space
and the permissions in the /tmp folder.
|
|
208
|
Failed to copy
Lasso_grab.sh to remote host.
Check the validation and run the
collection again or collect manually.
|
|
209
|
Failed to execute
Lasso_grab.sh remotely.
The error occurs when the collection has
timed out. Check the validation and run the collection again or collect
manually.
|
|
210
|
Failed to determine name of collection file to
retrieve.
Check
/tmp/Dell/Lasso/[timestamp] location for the collection results.
|
|
221
|
Unable to copy Service Tag exe to the remote system. |
|
222
|
Dependent Exe's and DLL's not
found.
|
|
224
|
Enclosure module host collection
is not successful.
|
|
223
|
SAN HQ server version not found.
|
|
295
|
Compellent Storage Client exe
is not found.
Make sure that the Compellent Storage Client exe
is available in the bin folder.
|
|
297
|
Failed to get Service Tag Information.
Refer to Manual UNIX collection and Linux Service Tag
Collection.
|
|
300
|
NaviCLI.exe was not found.
The file should be in the
C:\Program Files\EMC\Navisphere
CLI
location by default. If file is not found, run the
installer again.
|
|
301
|
NaviCli version could not be determined.
Make sure that Navisphere CLI is installed. Run the installer
again. The installer will check and install.
|
|
302
|
Navisphere CLI command failed trying to retrieve
Agent Revision.
Verify that SP is accessible on the
network, and the firewalls are not blocking the access. See the Troubleshooting
section for more details.
|
|
303
|
Failed to retrieve completed SP Collect from SP.
Connect to SP through Navisphere Manager and use the
File Manager to get the SP Collect.
|
|
304
|
Failed to collect
getall.
Make sure that the SP is available and running. Also,
connect to Navisphere Manager setup page and restart the management
server.
|
|
305
|
Failed to collect
getlog.
Make sure that the SP is available and running. Also,
connect to
Navisphere Manager setup page and restart the management
server.
|
|
306
|
NaviCLI
getagent failed.
Make sure that the SP is available and running. Also,
connect to
Navisphere Manager setup page and restart the management
server.
|
|
307
|
Failed to create
.zip file
out of
getall and
getlog.
Manually, you may need to compress the
getall and
getlog into a
.zip file.
|
|
308
|
SP collection timed out.
Try the
collection again. If the error persists, make sure that you have the
latest Navisphere CLI. To verify this, run the installer. Also, try
to collect the SP Manually. Finally, make sure that the firewall is
not blocking Navisphere from retrieving the collection. For more
information, see Network Ports.
|
|
309
|
Non-supported SP version found. |
|
310
|
NaviSECCli.exe was not found.
The
.exe should be in
C:\Program Files\EMC\Navisphere
CLI
by default. If it is not found in this location, try
to run the installer again.
|
|
311
|
No LUNs found on Storage Array.
Configure at least 1 LUN or Hot Spare. Else Dell cannot parse the
SPCollect.
|
|
312
|
Not a Valid SPA or SPB Identifier.
The IP address entered may not be the Storage Processor A in an EMC
array. Verify that the IP address is SPA (and not SPB).
|
|
313
|
Export command is not supported. |
|
314
|
Navisphere CLI command failed to determine whether
EMC Array is having Navisphere Express or Navisphere Manager.
|
|
315
|
Upgrade of Celerra is in progress. |
|
316
|
EMC Add-on upgrade is in progress. Unable to run
NaviCLI.exe.
|
|
397
|
One or more commands that were run as part of device
collection failed.
|
|
398
|
SPCollect could not be automated. However,
getall/
getlog was collected. You may need
to manually connect to Navisphere Manager and collect an SPCollect.
|
|
401
|
Unable to collect storage management
information on RAID controller module.
The storage management software
in use is not compatible with the firmware on the RAID controller
modules in the Storage Array.
|
|
411
|
Switch collection was complete, but collection
file not found!
You may try to collect switch data
manually.
|
|
413
|
Switch collection file not moved properly!
You may try to collect switch manually.
|
|
415
|
Could not open connection to the Specified IP
Address!
|
|
416
|
Manually telnet to the device to make sure it is
responsive.
|
|
417
|
Collection timed out.
Try to run
the collection when the system is not loaded.
|
|
418
|
Switch collection failed.
You
may try to collect switch manually.
|
|
420
|
Collection was not successful. Cannot start SCVMM
collector in the remote host.
|
|
422
|
Failed to retrieve diagnostic files from FTP Site. |
|
423
|
Remote VMM script was not run because the user
cancelled the collection process.
|
|
424
|
Cannot run script as PSD file path not found. |
|
450
|
Malformed URL found!
Error in connection
or invalid host name.
|
|
489
|
I/O module does not have any IP that is used for
telnet session to be established.
|
|
498
|
Maximum SSH/Telnet remote sessions
are active. Close the active sessions and try to validate again
|
|
499
|
Authentication validation failed!
Try validation again, and check username and password.
|
|
500
|
For information, see
|
|
501
|
Unable to bind to the Controller specified.
Verify the IP Address.
|
|
601
|
Vault password is incorrect. |
|
602
|
Connection failed!
Make sure that
the IP/device is valid and reachable.
|
|
700
|
Failed to copy
Dell Collector to remote host.
The remote host may be preventing
the copy of the script. Lasso has tried to copy the script and it
is possible that the remote script is suspended. You may need to reboot
the remote host. If rebooting fails, try to use the
Task
Manager
on the remote host and try to terminate the
DellCollector process.
|
|
701
|
Failed to copy dependant DLL which are used for
zipping the collection files on the remote host.
|
|
702
|
Host collection execution failed.
The remote host may be preventing the execution of the script. Lasso
has tried to copy the script and it is possible that the remote script
is suspended. You may need to reboot the remote host. If rebooting
fails, try to use the
Task Manager on the remote
host and try to terminate the
DellCollector process.
|
|
703
|
Failed to rename Collection File name on the
remote host.
|
|
704
|
Failed to move the Collection File from temp directory
to
%System%\DellCollector directory on the remote
host.
|
|
705
|
Failed to delete the temporary folder from the
remote host.
|
|
706
|
Unable to find
DellCollector.exe on the Management Station.
Verify if this file is
available after the installation of Lasso in the Management Station
|
|
707
|
Host collection timed out. |
|
708
|
QLogic SANSurferCLI is not found. |
|
802
|
Another collection process may already be running
on the host.
|
|
803
|
Collection timed out for enclosure collection. |
|
805
|
Collection has failed for Enclosure due to incorrect
IP/hostname and credentials.
|
|
807
|
Another collection process may already be running
on the host
|
|
808
|
HitKit for VMware collection has timed out. |
|
809
|
The IP/hostname and credentials provided for the
HITKIT type are not valid.
|
|
810
|
Collection has failed for the HITKIT type due
to wrong IP/hostname and credentials.
|
|
811
|
Unable to retrieve the collection files as the
.zip file does not exist.
|
|
812
|
Collection is not successful. |
|
901
|
Overall host Validation was not successful. |
|
902
|
Invalid operation requested. |
|
903
|
Collection of one or more EqualLogic details failed. |
|
904
|
Collection of EqualLogic details failed. |
|
905
|
Unable to perform ping test. Access to Management
Network is restricted.
|
|
906
|
Compellent collection timed out
Compellent collection timed out because of no response from array
or the port to communicate to array is not open.
|
|
907
|
Compellent log collection timed
out
Incomplete Compellent collection. Time out occurred while gathering
logs from Compellent Array.
|
|
908
|
Compellent collection timed out
due to delay in response
|
|
909
|
Unable to resolve the specified hostname. Make
sure that the hostname is correct, and then retry the operation.
|
