Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell Lasso Version 4.7.3 User's Guide

PDF

FAQ — Dealing With Errors

  • What is the description of the error code?
    • For information on the error code and descriptions, see Error Codes
  • Why does the Switch password fail each time even though the login to the Switch Web UI is successful?
    • All Switch collections use SSH/Telnet user name and password. For McData switches, if a user name is accepted with the Web UI, it does not automatically work with the CLI.. The access should be granted specifically. To verify that the password enter is valid, telnet into the switch and try the user name/password. To do this, go to Start > Run and enter telnet hostnameor ip address. If SSH interface is used by lasso and fails, connect to the switch using putty and try the user name/password to manually execute the command(s). See the documentation on the Switch for instructions to configure the user name or see troubleshooting section for more information.
  • How to troubleshoot device errors on collection?
    • Make sure to validate the devices. If the devices are already validated and using a saved configuration, then validate them again. The password may have changed. Click Error found icon to view the log of the device. This will include the reason for the device to fail collection. Also see the troubleshooting section for steps to run the collections using the CLI to verify or collect the data manually.
  • Why is the collection against a VMware ESX 3.0 server failing?
  • Does Lasso work on a 64-bit system?
    • Yes, Lasso can collect against a 64-bit system. Lasso version 3.5 and later can be installed and run on a 64-bit system with limited support. For more information, see Readme.
  • What is error code 398 and why is it only a warning?
    • Error code 398 describes that a full SPCollect was not obtained from the Storage Processor. A full getalland getlogis collected. For information on complete SP collect, see Manual Collection For CLARiiON .
  • Why should Lasso be used when the time taken to troubleshoot problems is longer than manually collecting the data with Lasso?
    • Lasso automates the collection process. The data collected remotely is dependent on the network configuration of the environment . If the access to the system running Lasso to the target devices is blocked, then the scripts can not complete the collection. If all the devices are unavailable, then run the collection scripts manually. Example: If the "admin$" share is disabled on Windows through a Group Policy, then Lasso can not execute the EMCReports remotely and is a limitation in Lasso.
  • How to troubleshoot a failed device?
    • If the Lasso full collection is failing, then manually collect the remaining devices. If there are many devices, then modify the security settings to resolve. Also, report the error for more assistance.
  • How to run Lasso against a Meditech host that displayed a blue screen?
    • A Meditech system is not Windows system. EMCReports fails when running on a Meditech system. Lasso automatically runs the EMCReports and the issue can occur if run against a Meditech system. Do not manually or using Lasso, run the EMCReports against a Meditech system. For more details, see the ftp://ftp.emc.com/pub/emcgrab/Windows directory.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\