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. All Rights Reserved.
Contents 1 Introduction................................................................................................................7 What Is New In This Release................................................................................................................. 7 Key Features.......................................................................................................................................... 8 Supported Devices..............................................................
Your Hardware Environment: Hosts.............................................................................................36 Your Hardware Environment: Enclosures.................................................................................... 37 Your Hardware Environment: Management & Monitoring Software..........................................38 Your Hardware Environment: Wireless Controllers.....................................................................39 Device Collection...................
Manually Collecting Data For SCVMM 2008 and 2012..................................................................... 63 Manually Collecting Data For PowerConnect Controller................................................................. 64 6 Collecting Data Using CLI.................................................................................... 65 Collecting For Single Device Using CLI............................................................................................. 66 7 Troubleshooting.
Dell Software Copyright .................................................................................................................... 98 GNU GENERAL PUBLIC ..................................................................................................................... 98 Preamble.............................................................................................................................................
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.
• Support for in CLI collection. • Enhancement for output messaging format. Key Features The key features are: • Collect, parse, and view the SAN configuration report for the following devices: – FluidFS NAS storage model FS8600 – SFP attribute on EqualLogic Array – RHEL version 5.9 – Linux Hitkit version 1.2 – NIC binding order on all windows Operating System – Force 10 MXL 10/40/GbE swtich • Collect and parse vSphere 5.1 SAN configurations report.
• Run Lasso under System Context user. • View SAN Configuration report for Brocade 300 and 5300.
• Option to provide the Delta Service Request number and Project Manager ID and include in the XML and HTML reports. • Parser support for the following devices: – EqualLogic FS7500 – Force 10 S50/S60/S4810 switches – Xen server – PowerVault NX3500 • Solution for error 904 (Collection of EQL Details Failed) for the EqualLogic Array. • Parser support for MaxRequestHoldtime for all the Windows hosts in EqualLogic and MDSeries SAN.
• Raw data collection and limited parsing for PowerVault NX3500 and EqualLogic FS7500. • Display the iSCSI network for different subnet masks. • Collect the applicable attributes for vSphere Hosts for all possible path selection policies. • Parse the attributes related to Port Channel for Power Connect and Cisco Switches. • Option to choose SSH or Telnet protocol in case of Ethernet Switches. • Report the updated version for vSphere host by Lasso.
Storage Device Types of Devices • ML6000 • • • • • • • • • • • • • • • • • • • • • • • Dell PowerConnect 5424/5448 Dell PowerConnect 6224/6248 Dell PowerConnect 7024/7024F/7048 Dell PowerConnect M6220 Dell PowerConnect 8024/8024F Dell PowerConnect M8024/M8024K Dell PowerConnect M6348 Dell PowerConnect M8428K Dell PowerConnect B-Series 8000 Dell PowerConnect 8132/8132f Dell PowerConnect 8164/8164f Dell PowerConnect 5524/5548 Dell PowerConnect 2824/2848 Dell PowerConnect 3524/3524P/3548 Cisco 2960 Cisco
Storage Device Types of Devices NOTE: The SSH and Telnet must be enabled on the controller for Lasso to collect the data. Supported Server Operating Systems For Attached Hosts The following table provides the supported server operating systems for attached hosts: Operating System Operating System Name Windows Systems • • Windows Server 2003 (RTM, SP1, SP2) and Windows 2008 (RTM, SP1, SP2).
Operating System Operating System Name • VMware systems establish SSH session, and root password is required to run the commands as root. For adequate disk space to store a copy of all logs and system data to be collected, see the Readme 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 ESX 3.
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.
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.
4. Click Next. The Destination Folder window is displayed. 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 reentering configuration and security details.
Repairing Lasso Installation You can also reinstall the corrupt files, registry keys, and shortcuts to the Lasso application. 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.
From the Application Maintenance Window To uninstall Lasso from the Application Maintenance window: 1. Double-click the installed .msi file. The Application Maintenance window is displayed. 2. Select the Remove option and click Next. The Lasso Uninstall window is displayed. 3. Click Next. The Updating System window is displayed. 4. Click Finish on the Lasso has been successfully uninstalled window.
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 NOTE: From EqualLogic array, SNMP should be enabled with public access for inventory collection. 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).
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.
NOTE: The community string is case- sensitive. • For System Center Virtual Machine Manager (SCVMM), powershell must be enabled in target Windows VMM host. • For Broadcom 57810 CNA collection, Broadcom Advanced Server Program (BASP) Broadcom Advanced Control Suite (BACS) management application must be installed on the remote windows host. NOTE: For Brocade collection, Brocade Command Line Utility (BCU) must be installed on the remote windows host.
5. Select the devices (one or multiple devices depending on your requirement and SAN) for which Lasso must collect data and click Continue. The device-specific Your Hardware Environment windows are displayed. 6. For each device, enter the required information. Click Continue until you complete providing information for each selected device. The Device Collection window is displayed. 7.
NOTE: Lasso does not support Tape Libraries in this release. Use Existing Configuration Before using this option, make sure that a configuration is saved in the Lasso installation directory. NOTE: Loading configuration files from Lasso 3.8 and earlier may result in loss of some device authentication information. To use an existing configuration: 1. Click Start → Programs (or All Programs) → Dell → Lasso and click Lasso. The Welcome to Lasso window is displayed. 2. Select Use an existing configuration.
4. Select the Upload full collection option to upload the collection to Dell Technical Support site. Click Browse to select the report to be uploaded. For more information on the report formats, see Generated File Formats. 5. Select Authenticated Proxy option to upload the report using proxy. Enter the following details: – IP/Hostname — Enter the IP address or hostname of the proxy server (optional). – Port — Enter the port number. Default port is 80. – Username — Enter the user name (optional).
Field Description Start with a new configuration Select this option to start with a new configuration. Before saving the configuration, if you navigate back to select this option, then the configuration is lost. Use an existing configuration Select this option to use the configuration file saved in the Lasso installation directory. From the drop-down menu, select the required configuration file.
NOTE: If this option is selected, only Company Name is mandatory. Click the Learn More link to display the list of sensitive data that is filtered. Company Information Field Description Company Name Enter your company information. Installation Address Enter SAN location address. City Enter the name of the city where the company is located. Postal Code Enter the postal code of the city where the company is located.
Edit Contact Information Field Description Name Enter the company contact name. Title Enter the designation of the contact. Email Address Enter the E-mail address of the contact. Primary Phone Number Enter the primary phone number of the contact. Select the type of phone number entered from the drop down list. Secondary Phone Number Enter the secondary phone number of the contact. Select the type of phone number entered from the drop down list.
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. Your Hardware Environment: Storage Arrays In this page, select the type of storage array(s) in your SAN environment, enter the details, and click Continue. Storage Arrays in your environment Clicking the image next to the Storage Array provides the validation status.
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.
Your Hardware Environment: Fibre Channel Switches In this page, select the type of fiber channel switch(es) in your SAN environment, enter the details, and click Continue. Switches in your environment Clicking the image next to the switch provides the validation status. If validation is successful, image is displayed. Else, 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.
Switches in your environment Clicking the successful, image next to the Ethernet Switch provides the validation status. If validation is image is displayed. Else, image is displayed. 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.
Your Hardware Environment: Tape Libraries NOTE: Lasso does not support Tape Libraries in this release. In this page, select the type of Tape Library in your SAN environment, enter the details, and click Continue. Tape Libraries in your environment Clicking the image next to the Tape Library provides the validation status. If validation is successful, image is displayed. Else, image is displayed. To edit the selected Tape Library, click Edit available next to the Tape Library.
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, is displayed. Else, image image is displayed. To edit the selected host operating system, click Edit available next to the host. Update the required fields and click Update Host to save the updates. Else, click Cancel.
Field Description 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. Enter the domain information.
Field Description • VRTX 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.
Field Description Password Enter the password. Use this as the default software type Select this option to save the selected software type as the default. Collect ASM/VE logs Select this option to collect the ASM/VE logs for VMware. Domain This field is displayed when the selected type of Software is SAN HQ and SCVMM. Enter the domain information.
Field Description Enable Password Enter the password. Save as the default Username & Password for additional Wireless Controllers Select this option to save the user name and password authentication as default for additional Wireless Controllers. NOTE: The Username, Password, and Enable Password credentials are optional for type of Wireless Controllers. Click Previous to display the Your Hardware Environment page. Device Collection This page displays all the selected types of devices.
Options Description IP/Hostname Enter the IP address or hostname. Port number Enter the port information. Username Enter the user name. Password Enter the password. Select Yes in the “Would you like to automatically upload the collection package to Dell?” to automatically upload the file to Dell Technical Support site. Else, select No. In the “Lasso can save your usernames and passwords in an encrypted password vault for future re-use.
• XML and HTML files — Lasso parses the data collected into XML and HTML files. The XML files are: – An XML output file with an .xml extension. – An encrypted XML output file with a .gpg extension. The HTML files are: – A HTML output file called SANconfiguration.html. To access the XML and HTML files, go to USERPROFILE%\Dell\Lasso\results directory.
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.
To collect Celerra device information manually: 1. Using SSH, login to Celerra device as a root user. 2. Run the following command: /nas/tools/collect_support_materials The server and event log collection file (support_materials*.zip) is generated in the /nas/var/ emcsupport/ directory. 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.
3. Check the progress of SPcollect using the following command: – For releases 19 and later: naviseccli -user -password SPAIPAddress/SPBIPAddress managefiles -list -scope 0 -h – For releases 6 to 18: navicli -h SPAIPAddress/SPBIPAddress managefiles -list This command lists *data.zip files, where * is the current system date on the array. The command spcollect initially creates *_runlog.txt file, that gets listed when this command is executed.
3. Run the following command: SMcli -c "show storagearray profile;" > \Results\Hostname.txt The Hostname.txt file is generated at \Results\ location. NOTE: When the validation or collection operation of a Storage Array times out, go to the DasArray.properties file in the InstallDir and change or increase the timeout value. Example: – mdseries.timeout.value.collection = 200000 which is 120000 by default – mdseries.timeout.value.
4. Enter the password when prompted. The contents of the ftp site is displayed. You can access the collection file (*.tar.gz) in the diagnostics/archive/results__diagnostic. GeneralSystemDiagnostic _XXXX (timestamp) directory. Example of a collection file: diagnostic.GeneralSystemDiagnostic.25_07_2011-06_42_09.tar.gz NOTE: On SAN consisting of many devices, you may need to increase the time out value. By default, time out value for this device is 15 minutes. You can modify the value nas.timeout.
Collecting Storage Device Information From Windows OS For EqualLogic SAN 1. Log in as administrator to the target Windows system. NOTE: For 32–bit and 64–bit operating systems use DellCollector.exe. Before running Dellcollector.exe, make sure that the Windows Management Instrumentation (WMI) service is running. 2. Copy the DellCollector folder and ICSharpCode.SharpZipLib.dll from the \bin\ folder to the target Windows system. Place the ICSharpCode.SharpZipLib.
Manually Collecting Data For Tape Library Device NOTE: Lasso does not support Tape Libraries in this release. You can collect information for the following tape library devices using Lasso: • • • • • PV136T PV132T TL2000 TL4000 ML6000 Manually Collecting Data For PV136T, PV132T, TL2000, And TL4000 Tape Library Device NOTE: Lasso does not support Tape Libraries in this release. 1. Connect to the tape library using: telnet -f Lasso\Results\hostname.
4. Run the command supportDump. Logs collected using the option Capture Snapshot gathers log files from the library are a super set of the logs obtained by running the command supportDump. From this super set, to locate the supportDumpinformation, save the super set to the local folder. Extract the log files and the snap.gz file located in \var\ log\ < vendor_name>\ < IO_Module_name> \ . Locate the file snap. This file contains the same information as the one when you run the command supportDump.
Manually Collecting Data For Cisco Ethernet Device To collect for Cisco Ethernet manually: 1. Log in to Cisco Ethernet switch through SSH/Telnet. 2. Run the following command to enter the required mode: – Exec — enable – Configuration — config 3.
To collect manually: 1. Login to Cisco Nexus switch through SSH/Telnet 2. Run the command config.
3.
– show system internal ethpm info all – show spanning-tree mst – show lldp neighbors detail – show lldp tlv-select – show vsan – show zone – show flogi database 4. For CEE information, run the command show tech-support 5. Capture the console output NOTE: On SAN having many Cisco Nexus switches, you may need to increase the time out value. By default, the time out value for these switches is five minutes (in milliseconds). This value (ciscofcoe.timeout) can be modified in the file ESC.
3. To display CEE information, run the command show tech-support.
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 SSH/Telnet. 2. Run the command show tech-support to display CEE information.
– show interfaces traffic-class-group – show interfaces priority-flow-control – show interfaces tengigabitethernet priority-flow-control – show interfaces counters tengigabitethernet – show lldp tlv-select interface tengigabitethernet – show lldp interface tengigabitethernet – show lldp dcbx interface tengigabitethernet detail 3.
Manually Collecting Data For Force 10 Switches To collect information for Force 10 switches manually: 1. Log in to Force 10 switch through SSH/Telnet. 2.
– – – – – – – – – – – – – – – – – – – – show show show show show show show show show show show show show show show show show show show show interfaces pfc summary interfaces configured inventory media alarms alarms threshold processes cpu memory mac learning-limit ip route all ip route summary ip ospf ip traffic ip rip database cam-profile cam-l2acl cam-usage cam-ipv4flow ntp status ntp association interface port-channel brief Manually Collecting Data For Switches To collect information, connect to the s
4. In the displayed prompt, enter the login credentials to the switch. If you are using Telnet to connect, then go to telnet -f %USERPROFILE%\Dell\Lasso \results\hostname.txt hostname. Enter the commands relevant to the type of switch. NOTE: On Windows 2000, use HyperTerminal and manually capture your telnet session.
3. Capture the console output Manually Collecting Data For McData Device The following sub-commands are included in the show all command. In some older switch firmware, the show all command may not work.
• show config switch • show config zoning • show fabric • show topology • show switch • show domains Manually Collecting Data For Enclosures — M1000e To collect the data, connect to the VRTX using SSH or Telnet. To collect manually: 1. Start putty and enter the hostname or IP address. 2. Enter the login credentials to the M1000e at the prompt. 3. Run the command: racdump. 4. Capture the console output.
Manually Collecting Data For SAN HQ DEVICE To connect manually: 1. Log in as administrator to the target Windows system. NOTE: For 32–bit and 64–bit operating systems, use SANHQCollector.exe. Before running SANHQcollector.exe, make sure that the Windows Management Instrumentation (WMI) service is running. 2. Copy the ICSharpCode.SharpZipLib.dll and SANHQCollector.exe config files from the \bin\ folder to the target Windows system.
Manually Collecting Data For PowerConnect Controller To collect manually: 1. Log in to PowerConnect Controller through SSH/Telnet . 2.
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.
• -PP — proxy server's password. • -RD- — customize the results directory path. • -NU — disable the report upload. • -NA — report not archived. • -CS — community string. • -CN — company name. NOTE: All options are case-insensitive. NOTE: -UZ argument cannot be used when -Secured option is used. While running Lasso in CLI mode, the -p argument in the command is optional.
NOTE: • -OF argument is optional in the command. • If password is not entered in the command, then the input stream is prompted to enter the password. • —RD argument is mandatory when running Lasso using System account.
Devices Ethernet & FCoE Switches Device Types Parameters Required Cisco -IP , -UN , -PD , DT Cisco CiscoEthernet -IP , -UN , -PD , DT CiscoEthernet, -EP CiscoNexus -IP , -UN , -PD , DT CiscoNexus or CiscoFCoE PowerConnect -DT PowerConnect, -IP , -UN, PD, -EP Force10 -OF -IP , -UN , PD
Devices Device Types Parameters Required PD , -DT Windows, D Linux -ST , -IP , -UN , PD , -DT Linux, -RP , -SU Solaris -ST , -IP , -UN , PD , -DT Solaris HP-UX -ST , -IP , -UN , PD , -DT HP-UX AIX -ST , -IP , -UN , PD , -DT AIX VMware -ST
Devices Wireless Controllers Device Types Parameters Required SCVMM -DT SCVMM, -IP, -UN, PD, -D PowerConnectController -DT PowerConnectController, IP, CS, UN, -PD, -EP The following examples provide the command for single device collection for various devices. • lasso.cmd -Q -IP -DT -ST -UN -PD -CN • lasso.
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.
upgraded, then upgrade the MD Storage Manager software. Else, there may not be access to the storage array. 1. Run the command SMcli -c “show storagearray profile;” < IPAddress of MD Array> The command output is generated in the Hostname.txt file in the USERPROFILE Dir\Results\ location. 2. Run the command SMcli -c "save storageArray SupportData file=\"USERPROFILE Dir\Results \Hostname.zip\";" < IPAddress of MD Array> The command output is generated in the Hostname.
Storage Processor Collection 1. Use http://hostname_or_ipaddress/ to connect to SP through Navisphere Manager. 2. Right click SPA or SPB to check the SP event logs. 3. Clear all the old SP collection using File Transfer Manager. 4. Clear all listed Privileged Users to open access to all users. NOTE: This is the default for CX arrays. 5. Add the entry for the system running Lasso to the array. This will limit access to only the listed users. AX arrays have one entry by default.
To add a user (newuser) to the authentication database using the CLI, run the following commands at the prompt: 1. config security authentication user add newuser web cli 2. config security authentication user role newuser Administrator 3.
• If validation or collection fails for Lasso, error messages are displayed. • If error is displayed on validation or collection, try running the Lasso commands. To test the command: 1. From Start menu open the command prompt window. 2. At the prompt, change to the bin directory where Lasso is installed. To do this, enter:cd c: \Program Files\Dell\Lasso\bin\. 3.
For more information, see Manual EqualLogic FluidFS NAS Collection Troubleshooting Celerra Collection To troubleshoot: • Use http://hostname_or_ipaddress/ to connect to the Celerra control station. • If you are not using root credentials, then verify that the user name has the State enabled, primary group is nasadmin (operator), and groups are fullnas (nasadmin). Troubleshooting VMware Collection To display the error messaged received during collection, try to run the Lasso commands.
8 Error Codes The following table provides the error codes and the messages. Error Code Error Message 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.
Error Code Error Message 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.
Error Code Error Message security to verify if the settings are preventing Lasso from running automated scripts. 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.
Error Code Error Message 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.
Error Code Error Message Lasso. If the error persists, contact Dell at US_Lasso_Support@Dell.com . 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.
Error Code Error Message Make sure that root has SSH access, SSH is running and the firewall allows SSH. 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.
Error Code Error Message 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.
Error Code Error Message 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. 419 Timed out during validation. 420 Collection was not successful.
Error Code Error Message 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.
Error Code Error Message Make sure that HITKIT is available, credentials are correct, and does not have an active SSH console open. 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.
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: 2. * PowerConnect Ethernet Switch — IP address, Username, and Password.
8. In the Your Hardware Environment: Ethernet Switches page, from the Type of Ethernet Switch drop down list, select PowerConnect switch, enter the following information and click Save New Ethernet Switch to validate and save the device: – IP/Hostname — 10.94.XXX.YY – Username — testuser – Password — testpassword – Enable Password — enablepassword If validation fails, edit the information for the device and update to re-validate the device. Click Continue. 9.
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? – 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.
• 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.
* Email to US_Lasso_Support@Dell.com NOTE: Dell employees can view the online training modules and videos on Lasso. • 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.
• Why should UNIX Root password be used? – The collection script emcgrab requires root level system access to obtain information about the system. See the directory ftp://ftp.emc.com/pub/emcgrab/Unixfor more information. • What are the other options instead of using UNIX Root password? – 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.
• Why is the collection against a VMware ESX 3.0 server failing? – To troubleshoot, see VMware Root Access • 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.
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.
Dell Software Copyright EACH ONE OF THE FILES (AS DEFINED IN THE "DISCLAIMER" SUBSECTION ABOVE) IS THE COPYRIGHTED WORK OF EITHER DELL OR OF THE THIRD-PARTY VENDOR SUPPLYING THE DOWNLOADABLE FILE. USE OF THE FILES IS 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.
GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 1. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License.
4. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a. Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. one line to give the program's name and a brief idea of what it does.
