Dell Lasso Version 4.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2012 Dell Inc. All Rights Reserved.
Introduction 1 Lasso is a Windows-based client and server utility that automates the collection of hardware, software, and storage logs and configuration from servers, disk arrays (EqualLogic, PowerVault MD-Series, and EMC), Fibre Channel switches (Brocade, McData, and Cisco), tape libraries, Ethernet, and FCoE Switches. After Lasso collects the data, it parses the data into XML and HTML formats that is packaged along with the collected data and encrypted. The collected data is saved as a .
– AFW_Delayed_ACK – Large_Frames • Support to collect VMware support logs in case of EqualLogic SAN using advanced mode. • The "Secure Site (Removes Customer Identification Information (CII)) option is renamed to "Enable Report Filtering". The "Learn More" link option provides information about the feature when selected. • Time and speed used to perform the “Ping test” to test the connectivity between the EqualLogic devices is the same as used by Putty.
• Support for Array ping test between the members within an EqualLogic Group. • Collect and parse the Qlogic iSCSI adapter information from Windows, Linux, and VMware hosts attached to Compellent. • Collect Emulex information from Windows, Linux, and VMware hosts attached to Compellent. • Collect and parse SAS HBA information from Windows and Linux (32-bit only) hosts attached to PowerVault MD Series and Compellent. • Validate user input for Ethernet Switch type in the related GUI pages.
Storage Device Storage Arrays Types of Devices • Dell EMC Storage processors – • • • • • Fibre Channel Switches CX3 series— Tackhammer (CX3–10), Jackhammer (CX3–20), Sledgehammer (CX3–40), and Mallet (CX3–80) – CX4 (Fleet) series— Nautilus (CX4–120), Ironclad (CX4–240), Trident (CX4–480), and Dreadnought (CX4–960) – AX series — Mamba (AX4–5F, AX4–5i, and AX4–5FX) PowerVault MD Series arrays — MD3000, MD3000i, MD3200, MD3220, MD3200i, MD3220i, and MD3600i EqualLogic PS series Dell EMC Celerra Storage dev
Supported Server Operating Systems For Attached Hosts The following table provides the supported server operating systems for attached hosts: Operating System Windows Systems Operating System Name • • Windows Server 2003 (RTM, SP1, SP2) and Windows 2008 (RTM, SP1, SP2). For Windows 2008 (R2), if the correct account (Administrator) is not specified during collection, the registry on that remote host should be edited.
Operating System Operating System Name file available at ftp://ftp.emc.com/pub/emcgrab/ Unix. In case of ESX, see the Readme file available at ftp://ftp.emc.com/pub/emcgrab/ESX/ VMware systems VMware ESX 3.0 server and later See also: Prerequisites For Data Collection Work Flow The following figure provides the steps to run Lasso, create and upload the report to Dell Technical Support site, and save the configuration for later use.
See Also: • • • • • • • • • • • • • • • Prerequisites For Data Collection Running Lasso Starting New Configuration Your Company Information and Your Company Contacts Your Hardware Environment Supported Storage Devices and Operating Systems Storage Arrays Fibre Channel Switches Ethernet Switches Tape Libraries Attached Hosts Enclosures Management and Monitoring Software Device Collection Upload Collection 9
Contacting Dell NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer service issues: 1. Visit support.dell.com. 2. Select your support category. 3. If you are not a U.S.
Installing And Uninstalling Lasso 2 This section provides information to install, modify, repair, and uninstall Lasso. Lasso can be installed using GUI or CLI mode. Prerequisites Before installing Lasso, make sure that the following prerequisites are met: • The user account has Administrator privileges.
6. Select one of the following options and click Next: – – – – Save Environment, Username, and Password — Saves all SAN configuration details, user name, and password. It is recommended to use this option to run Lasso multiple times and avoid re-entering configuration and security details. Save Environment and Username only — Saves all SAN configuration details and the user name. The password is not saved. Save Environment only — Saves all SAN configuration details.
The Application Maintenance window is displayed. Select Repair and click Next. 2. The Ready to Repair the Application window is displayed. 3. Click Next. The Updating System window is displayed. Click Finish to exit Lasso. 4. Uninstalling Lasso Lasso can be uninstalled using the GUI or the CLI option.
Using CLI To uninstall, at the command prompt, set the directory to LassoInstDir and run the command: msiexec /qn /x Lasso.msi/log Uninstall.txt NOTE: Before running the .msi file, make sure that the file is available in the directory.
3 Security Lasso is designed to automate data collections from remote systems and depends on network access to these systems. You can run Lasso from a local system that is on the same subnet as the target remote systems. For the successful remote data collection, make sure that there are no firewalls, group policies, security enhanced Linux policies, or other security issues.
Scripts Network Port Windows Collection (UDP ports) 137/138 (NetBIOS), TCP ports 139 (NetBIOS) and 445 (SMB) EqualLogic FluidFS NAS collection SSH (Port 22), FTP (Port 44421) PowerVault FluidFS NAS Collection SSH (Port 22), FTP (Port 44421) Windows uses the utility xCmd. The xCmd uses standard Windows file sharing (UDP ports 137/138 (NetBIOS), TCP ports 139 (NetBIOS) and 445 (SMB). For more information on Windows Port usage, see Microsoft support site.
Using Lasso 4 Lasso compiles information for all the devices in the SAN. It also includes company and site contact information. You can save this information as a configuration file (.xml format) for later use. Lasso collects data for the selected devices and generates a report that can be uploaded to Dell Technical Support site. This section provides information to use Lasso to collect data from the various storage devices in your SAN.
Starting New Configuration Use this option to create a new configuration and generate a report. To collect data using GUI: 1. Click Start → Programs (or All Programs) → Dell → Lasso and click Lasso. The Welcome to Lasso window is displayed. 2. Select Start with a new configuration and click Continue. The Your Company Information window is displayed. 3. Select Enable Report Filtering to exclude Customer Identification Information (CII) in the report.
– If you have selected Yes to upload the report, the collection uploads to Dell Technical Support site. – If you have selected No, the Save Lasso Configuration dialog box is displayed. Click Browse and save the file in the required location with the password. The Confirmation window is displayed. 11. To see the SAN configuration, select View Your SAN Configuration and click Finish. Lasso tool is closed and the report is opened in the internet browser.
NOTE: Loading configuration files from Lasso 3.8 and earlier may result in loss of some device authentication information. To load an existing configuration: 1. Click Start → Programs (or All Programs) → Dell → Lasso and click Lasso. The Welcome to Lasso window is displayed. 2. Select Load a configuration file and click Browse. Specify the file and click Continue. A dialog box displays indicating that background validation is in progress. The Your Company Information window is displayed. 3.
• • • • • • • • • • Storage Arrays Fibre Channel Switches Ethernet Switches Tape Libraries Attached Hosts Enclosures Management and Monitoring Software Device Collection Upload Collection Confirmation Welcome to Lasso Use Lasso to collect configuration and diagnostics data for the storage devices in the SAN and upload the report to Dell Technical Support site. Select one of the following options and click Continue.
Field Description • Password NOTE: IP/Hostname is mandatory, if the port used is other than default. Your Company Information In this page, provide your company information, Dell Technical Support information, and click Continue. NOTE: Fields with an asterisk are mandatory. Select the Enable Sensitive Data Filtering option to exclude Customer Identification Information (CII) from the report. NOTE: If this option is selected, only Company Name is mandatory.
Your Company Contacts In this page, provide the company contact details, edit the contact details, and click Continue. NOTE: Fields with an asterisk are mandatory. Your Company Contacts To edit the information of the company contact, click Edit available next to the contact. Update the required fields and click Update Contact to save the updates. Else, click Cancel. To remove a contact, click Delete available next to the contact.
If previous configuration of Lasso is used and you want to add a specific device, then select the required device option. If you remove an already selected device, then “ The option you have selected will result in all being removed from the configuration. Do you wish to continue?” message is displayed. Click Yes to remove the device. Else, click No. Click Previous to display the Your Company Contacts page.
Field Description • EqualLogic Enter the details for the following fields: • • • • • EQL FluidFS NAS RAID Ctrl Mgmt 0 IP RAID Ctrl Mgmt 1 IP Enter the details for the following fields: • • • Save as the default Username & Password for additional arrays Management IP Username Password Enter the details for the following fields: • • PV FluidFS NAS Group/Mgmt IP Community String Username Password Gather Diagnostic Data — Select this option to gather diagnostic data.
Switches in your environment Clicking the displayed. Else, image next to the switch provides the validation status. If validation is successful, image is image is displayed. To edit the selected Fibre Channel Switch, click Edit available next to the switch. Update the required fields and click Update Switch to save the updates. Else, click Cancel. To delete a Fibre Channel Switch, click Delete available next to the switch(es).
To edit the selected Ethernet Switch, click Edit available next to the Ethernet Switch. Update the required fields and click Update Switch to save the updates. Else, click Cancel. To delete a Ethernet Switch, click Delete available next to the Ethernet Switch. To verify Ethernet Switch(es) from the existing user configuration, select the required switch(es), and click Revalidate Selected Ethernet Switches.
To delete a Tape Library, click Delete available next to the tape library. To verify the tape devices from the existing user configuration, select the tape device and select Revalidate Selected Tape Libraries option. Add/Modify Tape Library Information To add or modify Tape Library information, select the type of Tape Library from the drop down list and enter the data in the required fields.
Add/Modify Host information To add or modify host information, select the type of host operating system from the drop down list and enter the data in the required fields. Click Save New Host to save, display the information in the Hosts in your environment section, and start validation of the host. Else, click Cancel.
Field Description Compellent is selected. Select this option to collect additional log information. Click Previous to display the Your Hardware Environment page. Your Hardware Environment: Enclosures In this page, enter the details for the selected type of Enclosure in your SAN environment and click Continue. Enclosures in your environment Clicking the is displayed. Else, image next to the enclosure provides the validation status. If validation is successful, image image is displayed.
To edit the selected software, click Edit available next to the software. Update the required fields and click Update Software to save the updates. Else, click Cancel. To delete a software, click Delete available next to the software(s). To verify the software(s) from the existing user configuration, select the required software(s) and click Revalidate Selected Management & Monitoring Software.
Upload Use this page to upload the collected files to Dell Technical Support site. To upload the collected files, the options are: Options Description Open Location Click to open the location where the collected files are saved. Upload Full Collection Select this option to automatically upload the collection files to Dell Technical Support site. NOTE: If this option is selected, the zip.gpg file is uploaded.
The collection log file ___validate.log is available at %USERPROFILE%\Dell\Lasso \logs\ location. The device log file for Lasso is available at %USERPROFILE%\Dell\Lasso\logs\ location and the Lasso user interface log file is available at %USERPROFILE%\ Dell\ Lasso\ lasso.log location. Generated File Formats Lasso generates raw data files, TXT, XML, and HTML files: • Raw Data Files — Lasso generates two types of raw data files: – Raw data file with a .zip extension.
Manual Collection 5 If you are not able to collect data using Lasso GUI, then you can manually collect the data. To perform manual collection, login to the required device and run the device specific commands.
The raid group, volume access, host LUNs, storage groups and SP ports collection file (SPCOLLECT.zip) is generated in the /nas/var/log/ directory. 4. Run the following command: /nas/sbin/log_config -d The collection file (log_config*.gz) is generated in the /nas/var/log/ directory. The file includes array related additional information and used for troubleshooting purposes. NOTE: The log_config -d command is functional only if you log in as root user to the Celerra device.
– 4. For releases 6 to 18: navicli -h SPAIPAddress/SPBIPAddress managefiles -retrieve -file <*data.zip> Capture resume data using the following command: – For releases 19 and later: naviseccli -user -password -scope 0 -h SPAIPAddress/SPBIPAddress getresume > ./SPIPAddress.resume.txt – For releases 6 to 18: navicli -h SPAIPAddress/SPBIPAddress getresume > ./ SPIPAddress.resume.txt This command copies the *resume.txt file to current working directory.
– show - Provides high level information for the members, groups, volumes, pools, replication , and so on for the array. This information is required to run the following commands: * member show – Lists the number of members in the array group, their version, status, and so on. * member select show – Lists network information for the respective member. * member select show controllers – Lists controller information for the respective member.
• • • • MDSeries CLARiiON Celerra Compellent NOTE: You can configure time out for Windows attached hosts using winhc.properties file. The default property value is 15 minutes. Set the property for the following types of devices as: • • Compellent, MD Series, and EqualLogic — whc.eql.timeout.value = 1800000 CLARiiON and Celerra — whc.emc.timeout.value = 900000 Collecting Storage Device Information From Windows OS For EMC SAN 1. Copy the appropriate EMCReport.
3. Log in to the remote system to collect the service tag with sysreport | grep Service Tag and include it in the %USERPROFILE%\Dell\Lasso\results\[timestamp]\Host_Linux_IPAddress.svctag.txt file. Collecting Storage Device Information For VMware (ESX/ESXi OS) 1. Log in to the VMware server using root privilege through SSH 2. Run the following command: vm-support -n The output file is saved in the /root/ directory. 3. Copy the output file to the local system using any secure ftp client.
Collecting Logs Manually For ML6000 Device To manually collect logs: 1. Connect to the Service port IP address of ML6000 using SSH (putty), and providing the credentials ilinkacc for user name and password for password. 2. Run the command cat/proc/net/arp and get the I/O mode IP address (The IP other than default gateway). 3. Add Telnet to one of the I.O.Module IP addresses by running the command "telnet" 4. Run the command supportDump.
* To run the sub-commands, see List Of Commands For Cisco FCoE Manually Collecting Data For Cisco Ethernet Device To collect for Cisco Ethernet manually: 1. Log in to Cisco Ethernet switch through telnet. 2. Run the following command to enter the required mode: . – Exec — enable – Configuration — config 3. For CEE information, run the command do show tech-support . 4.
– show interface fex-fabric – show interface transceiver – show interface flowcontrol – show interface priority-flow-control – show interface switchport – show interface trunk – show interface description – show interface status – show inventory – show lldp neighbors – show mac-list – show mac-address-table – show class-map – show license usage – show lacp neighbor – show lacp port-channel – show port-channel capacity – show port-channel load-balance – show port-channel
4.
3. – show system flowcontrol – show version – show switch – show arp – show bridge address-table – show mac address-table – show port-aggregator vlan summary – show port-aggregator port summary – show switch stack-ports Capture the console output NOTE: On SAN having many PowerConnect Ethernet switches, you may need to increase the time out value. By default, time out value for these switches is 3 minutes (in milliseconds). This value (powerconnectethernet.
Manually Collecting Data For Brocade Device To collect manually: 1. Log in to Brocade Fibre channel switch through SSH 2. Run the command supportShow. 3. Capture the console output NOTE: On SAN having many Brocade switches, you need to increase the default time out value of 3 minutes (in milliseconds). This value (brocade.timeout) can be modified in the FCSC.properties file located in the Lasso install directory. Manually Collecting Data For Cisco Device To collect manually: 1.
• show fabric topology • show fabric nodes Manually Collecting Data For McDataBlade Device The following sub-commands are included in the show all command. In some older switch firmware, the show all command may not work. In this case Lasso attempts a manual collection using these commands.
1. Login to the HITKIT VM using root privilege through SSH. 2. Select the Diagnostics option in the Hitkit VMware List of items is displayed. 3. Select Gather support Information from the list of items. The output file is saved in the CIFS share — \\\database\ file. 4. Run the command: net use \\\database\USER:\ to connect to the appliance from the local system. 5. Run the command: CMD /C MOVE /Y\\\database\
Collecting Data Using CLI 6 Lasso is normally run from the shortcut that calls a batch file. This batch file launches the Java UI. Once the environment is configured and validated, then Lasso Java UI calls individual scripts to automate the collections. The Java UI process can be automated with Java CLI options. To start Lasso using CLI, it requires JRE 1.6 or later installed in the system. Create the configuration file using the GUI, before running Lasso using CLI.
• -PI — proxy server's IP address or hostname • -PN — proxy server's port number • -PU — proxy server's user name • -PP — proxy server's password NOTE: -UZ argument cannot be used when -Securedoption is used. While running Lasso in CLI mode, the -p argument in the command is optional. When this argument is not entered, the “Please enter the device password:” message is displayed.
Devices Fibre Switches Ethernet & FCoE Switches Device Types Parameters Required PVFluidFSNAS -IP , -UN , -PD , -DT Brocade -IP , -UN , -PD , -DT McData -IP , -UN , -PD , -DT McDataBlade -IP , -UN , -PD , -DT Cisco -IP , -UN , -PD , -DT CiscoEthernet -IP , -UN <
Devices Device Types Parameters Required , -DT, -D Linux -ST , -IP , -UN , -PD , -DT, -RP , -SU Solaris -ST , -IP , -UN , -PD , -DT HP-UX -ST , -IP , -UN , -PD , -DT AIX -ST , -IP , -UN , -PD , -DT
• java -jar lasso.jar -Q -IP 10.10.78.132 -DT Linux -ST equallogic -UN lasso -PD $ervices1 -SU • java -jar lasso.jar -Q -IP 10.10.78.132 -DT Linux -ST equallogic -UN root -PD $ervices1 -deltaSR 1234567890 -PMMail US_Lasso_Support@dell.com • java -jar lasso.jar -Q -DT M1000e -IP 10.94.217.100 -UN root -PD calvin • Java –jar Lasso.jar –Q –DT PowerConnect –IP 10.94.100.10 –UN root –PD password –EP password • Java –Jar Lasso.jar –Q –DT PowerConnect -IP 10.94.100.
Troubleshooting 7 Lasso may receive errors when trying to automate validation and collection. When a collection fails, click the Error Found icon and review the log. The error code and the description are available at the end of the log. Try to run the collection again. For this, select the required device and click Start Collection. If the problem persists, try to run one of the commands related to the device type. To only collect the data and not troubleshoot, see Manual Collection.
Allowing Root Access Using Multi User Interface (MUI) On VMware The Multi User Interface (MUI) on VMware ESX 3.0/4.0 can also be used to allow root access. When using the MUI, do the following: 1. Select the ESX server in the VI Client 2. Select Configuration 3. Select Security Profile 4. Choose Properties 5. Select SSH Server and place a check in the box 6. Retry Lasso against this host NOTE: In few UNIX systems including VMware ESX 3.0, SSH is disabled as root by default.
To view the collection status, click Collected or Error Found. Troubleshooting EqualLogic For successful validation or collection, make sure that SNMP is enabled on the EqualLogic. To enable, connect to the array using a browser and provide the . To troubleshoot: 1. In the EqualLogic Array UI, click Group Configuration. 2. Navigate to SNMP tab and add a SNMP community string. NOTE: The string is case sensitive.
Edit Privilege User On CX Array To edit privileged users on CX array: 1. Use http://ip.address.of.sp to login to the setup of the array. 2. Expand the Array tree 3. Right-click on the SP and choose Properties. 4. Select the required Agent. 5. Clear any entry in the list. The access is now available to all or you can add the system that is running Lasso in the form of username@host . Example: samus_aran@some.system Edit Privilege User On AX Array To edit privileged user on AX array: 1.
2. Enter the execute mode to make sure that the enabled password is available. Troubleshooting Tape Library To reproduce the steps Lasso performs when automating Tape Library validations or collections: 1. Add Telnet to each switch to make sure that username/password credentials are correct and the prompt such as password change request is not displayed. 2. Test the actual command Lasso runs. For the commands, see Manual Collection for Tape Libraries.
• Telnet or SSH to each Enclosure to make sure that user name/password credentials are correct Troubleshooting HITKIT Collection To complete the Hitkit software collection, Lasso uses SSH. The root credentials are required for SSH connection. Lasso uses this to connect to the system through SSH protocol. Troubleshooting PowerVault FluidFS NAS Collection If validation fails when the Management IP of the array is provided for validation, make sure that the provided IP is correct and available.
8 Error Codes The following table provides the error codes and the messages. Error Code Error Message -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.
Error Code Error Message 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.
Error Code Error Message 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.
Error Code Error Message the %SystemRoot%\temp\Dell\Lasso\DellCollector\ sub directories for a .txt file in the remote host. 197 Authentication validation failed for HitKit appliance. Make sure that the HitKit password entered is correct. 198 xCmd.exe not found. Check for the xCmd.exe file in the bin folder in Lasso installation directory. If the file is not found, then reinstall Lasso. 199 Authentication validation failed! Check user name and password again.
Error Code Error Message 297 Failed to get Service Tag Information. Refer to Manual UNIX collection and Linux Service Tag Collection. 298 Connection was refused! The remote host did not respond to the connection attempt. 299 Authentication validation failed! Try to validate and check the user name and password. Try to connect manually and verify. Make sure that root has SSH access, SSH is running and the firewall allows SSH. 300 NaviCLI.exe was not found.
Error Code Error Message 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.
Error Code Error Message 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. 419 Timed out during validation. 420 Collection Failed. 421 Make sure that MDSM software has valid permissions. 422 Failed to retrieve diagnostic files from FTP Site. 489 I/O module does not have any IP that is used for telnet session to be established.
Error Code Error Message 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 Windows host collection timed out! 801 Authentication validation failed. Make sure that: • • Dell M1000e of Enclosure is available and credentials are correct. Switch does not have an active SSH and telnet console open. 802 Another collection process may already be running on the host.
Error Code Error Message 905 QLogic SANSurferCLI.exe is not found. 999 Demo Mode Failure. Lasso is running in DEMO mode. Remove command line parameter -DEMO to run in live mode.
9 Use Case Scenario Using Lasso GUI, collect data for devices such as PowerConnect switches, CLARiiON and EqualLogic storage arrays in your SAN environment and upload the collection to Dell Technical Support. To do this: 1. Before running Lasso, make sure: – You have the following details for each device: * PowerConnect Ethernet Switch — IP address, Username, and Password.
– Password — testpassword – Enable Password — enablepassword If validation fails, edit the information for the device and update to re-validate the device. Click Continue. 9. In the Device Collection page, all the selected devices are displayed. If there are devices that have failed validation, edit and re-validate the devices or remove them from the list. For more details see Device Collection. 10. Click Start Collection to start the data collection. 11.
Frequently Asked Questions 10 This section has the following types of frequently asked questions: • FAQ — About Lasso • FAQ — Passwords and Security • FAQ — Dealing with errors FAQ — About Lasso • What is Lasso? – • What is Wrangler? – • Lasso is a stand alone collection utility that automates the collection of all pertinent hardware and software configuration details from the target SAN attached servers, Dell Storage Arrays, Fibre Channel, Ethernet and FCoE Switches, and Tape Libraries.
– 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.
• How can the timeout value for FC Switches be modified? – • How can the timeout value for Unix hosts be modified? – • On a SAN having many attached hosts, increase the timeout value for the successful completion of automatic validation in: * SAC.properties— while automatically discovering hosts attached to arrays. * WinHC.properties— while validating already discovered hosts in the background. This happens when the customer configuration file is open.
• What are the other options instead of using UNIX Root password? – • How does Lasso provide security and privacy protection? – • Enter a blank password, when prompted by the SSH session, before Lasso prompts this authentication. The password may be entered several times for each UNIX host in the spawned windows. Add a new user with root access, or change the password temporarily for the Lasso run. It is not recommended to use central authentication scheme.
• What is error code 398 and why is it only a warning? – • 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.
License 11 Various programs are used throughout Lasso, and may have different licenses. Dell: Export Compliance Disclaimer By downloading from Dell's Web site, you are agreeing that you will not use or otherwise export or reexport, directly or indirectly, this Software and/or Technology except as authorized by U.S. law and the laws of the jurisdiction in which the Software and/or Technology was obtained. The Software and/or Technology may not be exported or reexported (i) to any U.S.
SUBJECT TO COPYRIGHT LAWS OF THE UNITED STATES. USE OF ANY OF THE FILES IN ANY MANNER THAT WOULD VIOLATE THE COPYRIGHT LAWS OF THE UNITED STATES IS EXPRESSLY FORBIDDEN. EMCGrab: ftp://ftp.emc.com/pub/emcgrab/Unix/Readme_EMCGrab_v3.8.txt EMCReport: ftp://ftp.emc.com/pub/emcgrab/Windows/EMCRPTS_V28_README.TXT GNU GENERAL PUBLIC Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc.
and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program).
associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. 12. NO WARRANTY BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this License.
