User's Manual

• How does Lasso operate?
– Lasso initiates scripts against all defined devices. The scripts collect specific information about the
devices. Lasso then captures the output of individual process separately for each device. This helps
to simultaneously complete the collection. If the time taken for manual login, copy collection
(example:EMCReports) for a host is 5minutes, Lasso can collect data against 10 hosts for the same
time.
NOTE: The limit for simultaneous processes is 10. The limit can be modified in the
LassoConfig.xml file.
• What is the time taken by Lasso to run?
– The time taken is approximately 30 minutes for a normal run. Many factors can modify the
estimated time. The approximate time is determined by adding the following:
* Time taken to input profile and environment information (dependent on the user).
* Time taken to copy EMCReports/emcgrab to the remote device (less than 2MB file size. It is
fast on a LAN but slow if remote).
* Time taken by the longest device. It is 5-10 for hosts, but may be over 20 minutes on a busy
host. For SPCollects, the time taken is approximately 10 minutes, but on a busy SP it is 30
minutes or higher. For switches, less than 5 minutes, but on large switches with error logs, may
be 20 minutes or higher.
* Time taken to copy the collection data from the remote device (may be fast on a LAN but slow
if remote).
* Time taken to zip and encrypt the data (may be less than a few minutes).
* Time taken to upload the data to Dell's FTP site (may be the longest time depending on the size
of the environment and the speed of the Internet connection).
Using the above guidelines, assuming that the profile and environment information is already
entered, all devices are on a LAN, the longest device takes 15 minutes, a few minutes to zip/
encrypt, and the Internet connection is fast, the entire collection should be completed in less than
30 minutes.
If there are environment specific settings that prevent remote execution of some of the scripts,
then troubleshooting may take more time.
• What is Navisphere CLI and where is it available?
– Lasso uses EMC's Navisphere CLI to initiate commands to CX and AX Storage Processors. Among
these commands are SPCollect, getall, and getlog. Navisphere CLI is available at http://
powerlink.emc.com and also provided with the Lasso package.
• What types of devices are supported by Lasso?
– For the list of supported types of devices and operating systems, see Support Matrix.
• What are the system requirements to run Lasso?
– For information on the system requirements to run Lasso, see Prerequisites For Data Collection.
• How can the timeout value for FC Switches be modified?
– On a SAN having many Brocade and McData switches, increase the timeout value. By default,
timeout value for the switch is 3 minutes (in milliseconds). This value can be modified in the file
FCSC.properties available in the Lasso install directory.
• How can the timeout value for Unix hosts be modified?
– On a SAN having Linux, Solaris, HP-UX, and AIX hosts, the collection process may exceed the
default timeout value of 30 minutes (in milliseconds). Therefore, increase the timeout value in
UnixHC.properties file, available in the Lasso install directory.
110