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. © 2013 Dell Inc.
Contents Notes, Cautions, and Warnings...................................................................................................2 1 Introduction..................................................................................................................................7 What's New In This Release....................................................................................................................................7 Key Features.......................................................
Your Hardware Environment: Fibre Channel Switches....................................................................................30 Your Hardware Environment: Ethernet Switches.............................................................................................31 Your Hardware Environment: Tape Libraries...................................................................................................32 Your Hardware Environment: Hosts.............................................................
6 Collecting Data Using CLI........................................................................................................55 Collecting For Single Device Using CLI...................................................................................................................56 7 Troubleshooting.........................................................................................................................61 Troubleshooting Unix Host Collection............................................
GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION.......................................................................................................................................................88 END OF TERMS AND CONDITIONS........................................................................................................................
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), Ethernet, and FCoE Switches (Power Connect Cisco, Brocade, and Force 10). After Lasso collects the data, it parses the data into XML and HTML formats. The data is then packaged along with the collected data and encrypted.
– Slot Information – Spanning Tree Active – LLDP TLV – LLDP Remote • Support to view the SAN configuration report for DV Switches Information and DV Switch Port Information in the VMware Hosts section. • Support to view SAN Configuration report for PowerVault MD3600F, MD3620F, and MD3660F models. • Support to run Lasso under System context user. • Support to view SAN Configuration report for Brocade 300 and 5300.
• Support to view PS Array Group information for Windows Hit Kit in SAN configuration report. • Support to view firmware versions for both Chassis Management Controller cards on M1000e appliance in SAN Configuration report. Key Features The key features are: • Collect and parse Qlogic FC HBA information for Windows and Linux hosts attached to Compellent. • Optional user name and password credentials when PowerConnect ethernet switch is configured. • Raw data collection support for Enclosures.
• Use of Forced multi-threaded mode of execution for enhanced Lasso performance. • Solution to parse EqualLogic Array if the EqualLogic IP Address last octet is single digit issue. • Secure Site option in the Your Company Information window of the Lasso GUI to remove Customer Identification Information (CII) from XML format of the collection.
Storage Device Fibre Channel Switches Types of Devices • Compellent FluidFS NAS • McData and Blade switches except director class switches Cisco 9124 Brocade 200E/4424/300/5100/5300 • • NOTE: Telnet must be enabled on all McData switches for Lasso to collect the data.
Operating System Operating System Name \system\key , then reboot. It is recommended to use the Administrator account to prevent the modification and reboot. NOTE: – • • UNIX systems • • • • • • VMware systems For adequate disk space to store a copy of all event logs and other system data, see ftp:// ftp.emc.com/pub/emcgrab/ Windowsdirectory for more information. – admin$ and c$ share must be enabled for remote commands to execute the program embedded in Lasso. xCmd.
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 Attached Hosts Enclosures Management and Monitoring Software Device Collection Upload Collection 13
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.
5. Click Next to accept the default directory path or click Browse to specify another location, and click Next. The Security Level window is displayed. 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.
To repair Lasso: 1. Double-click the .msi file. The Application Maintenance window is displayed. 2. Select Repair and click Next. The Ready to Repair the Application window is displayed. 3. Click Next. The Updating System window is displayed. 4. Click Finish to exit Lasso. Uninstalling Lasso Lasso can be uninstalled using the GUI or the CLI option.
The Updating System window is displayed. 4. Click Finish on the Lasso has been successfully uninstalled window. Using CLI To uninstall, at the command prompt, set the directory to LassoInstDir and run the command: • Using Lasso msi: msiexec /qn /x Lasso.msi/log Uninstall.txt NOTE: Before running the .msi file, make sure that the file is available in the directory. • Using product code: \UninstallLasso.cmd No {CF07A03B-765B-46CB-BEF2-7AD19DB4FA9C} /log uninstall.
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.
– Single Device Collection 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.
Loading Configuration File Use this option if the configuration file is located in a directory other than the Lasso user profile directory. 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.
• Welcome To Lasso • Your Company Information • Your Company Contacts • Your Hardware Environment • Storage Arrays • Fibre Channel Switches • Ethernet Switches • Tape Libraries • Attached Hosts • Enclosures • Management and Monitoring Software • Device Collection • Upload Collection • Confirmation NOTE: Lasso does not support Tape Libraries in this release.
Field Description Select Upload full collection option to upload the collection to Dell Technical Support site. Click Browse to select the report to be uploaded. Select Authenticated Proxy option to upload the collection using proxy. Specify the following proxy details: • • • • IP/ hostname Port number Username Password NOTE: IP/Hostname is mandatory, if the port used is other than default.
Dell Technical Support Information Field Description Case Number Enter service request number. This is optional Dell PM Mail ID Enter Dell PM email ID. This is optional. Click Previous to display the Welcome to Lasso page. 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.
Field Description Ethernet & FCoE Switches Select this option to collect data for the ethernet and FCoE switches. Tape Libraries Select this option to collect data for the tape libraries. Attached Hosts Select this option to collect data for the attached hosts. Enclosures Select this option to collect data for the enclosure(s). Management & Monitoring Software Select this option to collect data for the management and monitoring software.
Field Description • • Celerra Enter the details for the following fields: • • • CLARiiON 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. If this option is selected, then login credentials are required.
Field Description Save as the default Username & Password for additional arrays Select this option to save the user name and password authentication information as default for the included arrays. NOTE: This option is disabled when MD Series type is selected. Use this as the default storage array type Select this option for the selected storage array to be the default type. Click Previous to display the Your Hardware Environment page.
Field Description Save as the default Username & Password for additional switches Select this option to save the user name and password authentication information as default for all the switches of the same type. Click Previous to display the Your Hardware Environment page. Your Hardware Environment: Ethernet Switches In this page, select the type of Ethernet Switches in your SAN environment, enter the details, and click Continue.
Field Description Save as the default Username & Password for additional Ethernet switches Select this option to save the user name and password authentication as default for additional ethernet switches. NOTE: Username, Password, and Enable Password credentials are optional for Cisco Ethernet type of Ethernet Switches. Click Previous to display the Your Hardware Environment page. Your Hardware Environment: Tape Libraries NOTE: Lasso does not support Tape Libraries in this release.
NOTE: Only IP address or host name is required for TL2000 and TL 4000. NOTE: Only IP address or host name and password required for ML6000. Click Previous to display the Your Hardware Environment page. Your Hardware Environment: Hosts In this page, select the type of host operating system in your SAN environment, enter the details, and click Continue. Hosts in your environment Clicking the image next to the host provides the validation status. If validation is successful, image is displayed.
Field Description • Compellent When a storage array is selected, then the array information related to the selected host OS is collected. Use this as the default host type Select this option to save the selected host type as the default. All of the hosts on my SAN can be accessed with this Username & Password Select this option if the user name and password is the same for all the hosts in your SAN environment. Domain This field is displayed when the selected type of host OS is Windows.
Field Description Type of Enclosure M1000e — This type of enclosure is selected by default. IP/Hostname Enter the IP address or host name of the selected type of enclosure. Username Enter the user name. Password Enter the password. Save as the default Username & Password for additional Enclosures Select this option to save the user name and password authentication information for all the enclosures. Click Previous to display the Your Hardware Environment page.
Device Collection This page displays all the selected types of devices. The validated device has The devices that failed validation has remove from the list. image next to the device name. image next to the device name. You can either re-validate these devices or NOTE: Validation of device is necessary for collection to be completed. To validate the device before collection, click Edit next to the device. In the displayed device page, edit the details and re-validate the device.
collection again. Would you like to save it?”, select Yes to save. Else, select No. If saved, the vault is secured as a local file in the %USERPROFILE%\Dell\Lasso directory. NOTE: The extent of information saved depends on the security level selected during the installation of Lasso. Click Continue to upload the file. The Confirmation page is displayed. Confirmation This page displays the status of the file upload. If No is selected in the Upload page, instructions to upload the collection is displayed.
• After Lasso collects the information, on the Confirmation page select View Your SAN Configuration option and click Finish. Lasso tool is closed and the report is opened in the internet browser. • Open the files that are saved at the default location c:\Users\\Dell\Lasso\results\ or in the specified location. For information about the file formats, see Generated File Formats.
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. You can manually collect data for the following devices: • Storage Arrays • Fibre Channel Switches • Ethernet and FCoE Switches • Tape Libraries • Attached Hosts • Enclosures • Management and Monitoring Software NOTE: Lasso does not support Tape Libraries in this release.
3. Run the following command: /nas/tools/.get_spcollect 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.
4. – For releases 19 and later: naviseccli -user -password -scope 0 -h SPAIPAddress/SPBIPAddress managefiles -retrieve -file <*data.zip> – 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.
1. Open a SSH session on the array. 2. Capture the output for each of the following commands to a .txt file. – 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.
• EMC SAN • EqualLogic SAN • 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.
Automating Service Tag Collection On Linux OS 1. Copy the sysreport utility to the remote system. 2. Change the file access permission to r-x (read and executable) for root. 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.
1. Navigate to GUI panel of ML6000 library. 2. Log in to the web client. Enter the credentials admin for username and password for password. 3. In the home page, click the setup tab available in the tool bar. 4. Select the Network Management option. 5. Select the IP version 4 and click Next. If the tape library is already assigned to a IP, the IP address is displayed. If not, assign a static or DHCP IP to the tape library. The displayed IP address is called the Service Port IP.
– – – Cisco Ethernet: * terminal length 0 * To run the commands, see List Of Commands For Cisco Ethernet Cisco FCoE: * terminal length 0 * show startup-config * To run the sub-commands, see List Of Commands For Cisco FCoE Force 10 Switches * To run the commands, see List Of Commands For Force 10 Switches. Manually Collecting Data For Cisco Ethernet Device To collect for Cisco Ethernet manually: 1. Log in to Cisco Ethernet switch through telnet. 2.
– show vpc – show vlan – show clock – show feature – show fex – show fex detail – show hardware internal cpu-mac mgmt stats – show interface – show interface brief – 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-tab
Manually Collecting Data For PowerConnect, Brocade B-Series, And M8428K Devices To collect data for PowerConnect B-Series manually: 1. Log in to Power Connect B-Series FCoE switch through telnet 2. Run the command supportShow to display FC information. 3. To display CEE information, run the command show tech-support. If the command fails, in the case of older switch firmware, then run the following commands: 4.
Manually Collecting Data For PowerConnect Ethernet And M8428K Device To collect information for PowerConnect Ethernet manually: 1. Log in to Power Connect Ethernet switch through Telnet. 2. Run the command show tech-support to display CEE information.
3.
– show interfaces ets summary – show interfaces pfc summary – show interfaces configured Manually Collecting Data For Switches To collect information, connect to the switch using SSH or Telnet. If you are using SSH, then: 1. Start putty and enter the hostname or IP address. 2. Enter Port as 22. 3. Select the protocol option as SSH and click Open. 4. In the displayed prompt, enter the login credentials to the switch.
Manually Collecting Data For Cisco Device To collect manually: 1. Log in to Cisco Fibre channel switch through SSH 2. Run the commands 3. – do show running-config – do show flogi database – do show startup-config – do show inventory – do show vsan – do show zone – do show version – do show interface brief Capture the console output Manually Collecting Data For McData Device The following sub-commands are included in the show all command.
• show about • show chassis • show donor • show interface • show mem • show perf • show setup mfg • show setup radius • show setup services • show setup snmp • show setup system • show version • show config port • show config switch • show config zoning • show fabric • show topology • show switch • show domains Manually Collecting Data For Enclosures — M1000e Connect to the M1000e using SSH or Telnet to collect the data. To collect manually: 1.
6. 54 Run the command net use \\\database /d to disconnect the appliance from the local system.
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 host name or IP address • -PN — proxy server's port number • -PU — proxy server's user name • -PP — proxy server's password • -RD- — customize the results directory path • -NU — disable the report upload • -NA — report not archived NOTE: -UZ argument cannot be used when -Securedoption is used. While running Lasso in CLI mode, the -p argument in the command is optional.
Devices Device Types Parameters Required Storage Arrays CLARiiON -IP , -UN , -PD , -DT EqualLogic -IP , Community String, -DT Celerra -IP , -UN , -PD , DT MDSeries -IP , -DT EQLFluidFSNAS -IP , -UN , -PD , -DT PVFluidFSNAS -IP , -UN , -PD , -DT CompellentFluidFSNAS -I
Devices Device Types Parameters Required NOTE: -EP is not required for PowerConnect B-Series and and M8428K. Tape Libraries PV132T -IP , -UN , -PD , -DT PV136T -IP , -UN , -PD , -DT TL2000 -IP , -DT TL4000 -IP , -DT ML6000 -IP , -PD , -DT NOTE: Lasso does not support Tape Libraries in this release.
Devices Device Types Parameters Required Management and Monitoring Software HIT Kit for VMware -Q -DT HITKITVM IP -UN PD -A or -B The following examples provide the command for single device collection for various devices. • java -jar lasso.jar -Q -OF OutPutFileName -IP 10.94.26.217 -DT Windows -ST CLARiiON -UN admin -PD password • java -jar lasso.jar -Q -IP 10.94.216.158,10.94.216.159 -DT CLARiiON -UN admin -PD password • java -jar lasso.jar -Q -IP 10.
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 NOTE: Lasso does not support Tape Libraries in this release. 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.
Troubleshooting Enclosures To reproduce the steps Lasso performs when automating Enclosures validation or collection: • 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 Lasso Run As System Account When Lasso is run using the system account, the report is not saved in the default location. To troubleshoot this: 1. Install PSExec. 2. Run CMD as Administrator. 3. Navigate to PSExec. 4. Enter the command psexec -I -s cmd.exe. 5. In the new console window that appears, run the command with -RD parameter.
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 297 Error Message 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 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. 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.
Error Code Error Message 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 Windows host collection timed out! 801 Authentication validation failed.
Error Code Error Message 902 Invalid operation requested. 903 Collection of one or more EqualLogic details failed. 904 Collection of EqualLogic details failed. 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, and Ethernet and FCoE Switches.
– 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.
