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 © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction................................................................................................................7 What Is New In Lasso 4.6 Release.........................................................................................................7 Key Features.......................................................................................................................................... 8 Support Matrix.....................................................................
Your Company Contacts.............................................................................................................. 36 Your Hardware Environment........................................................................................................ 37 Your Hardware Environment: Storage Arrays.............................................................................. 38 Your Hardware Environment: Fibre Channel Switches...............................................................
Manually Collecting Data For Brocade Device............................................................................. 71 Manually Collecting Data For Cisco Device................................................................................. 71 Manually Collecting Data For McData Device..............................................................................72 Manually Collecting Data For McDataBlade Device....................................................................
Troubleshooting Lasso Run As System Account............................................................................... 93 8 Error Codes.............................................................................................................. 95 9 Use Case Scenario................................................................................................ 107 10 Frequently Asked Questions............................................................................109 FAQ — About Lasso............
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, Storage Arrays, Fibre Channel switches, Ethernet and FCoE Switches, Attached Hosts, Enclosures, Management and Monitoring Software, and Wireless Controllers. 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. The collected data is saved as a .
• Support for: – EqualLogic FS7500, FS7600, and FS7610. – Oracle Linux 6.4 Operating system – SAN HQ 3.0 – CML FS8600 • Support to collect host data without specifying attached storage array. • Support to parse and view SAN configuration report for non-iSCSI NIC for hosts. • Support to collect and parse Device ID, Vendor ID, Subdevice ID, and Subvendor ID for NIC and HBA cards for Linux and VMware hosts..
– PowerConnect B8000 model switches – Brocade 8000 models • View SAS HBA card information in the SAN configurations report for MD-series storage connected to Windows 2012 host. – Collect and parse diagnostic information and logs from Windows 2012 server with or without Hyper-V enabled. • View PowerConnect switches front port stacking information for 7000, M6348, and 8000 series in SAN configurations report. • Collect, parse , and view the SAN configurations report for PowerConnect firmware version 4.
• Collect, parse, and view Force 10 switch model S4810 with firmware version Kaveri version 8.3.12.0. • Lasso support for the latest EMC Reports/Grabs (ESX — 1.3.1, Unix — AIX 4.5.0, HP Unix 4.5.0, Linux 4.5.0, Windows Version 41). • View Windows HIT Kit version 4.5 information in SAN configuration report. • View PS Array Group information for Windows Hit Kit in SAN configuration report.
• Option to re-validate the devices when imported from an existing configuration. • 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.
Operating System Collection Protocol Port Used Latest Supported Version Windows Server 2003 SP2 WMI 135 - Windows Server 2003 R2 SP2 WMI 135 - Windows Server 2008 SP2 WMI 135 - Windows Server 2008 R2 SP2 WMI 135 - Windows Server 2012 WMI 135 - Windows Server 2012 R2 WMI 135 - RedHat Enterprise Linux 6.4 SSH2 22 - SLES 11 SP3 SSH2 22 - Cent 6.
NOTE: • WMI protocol uses multiple ports along with 135 to connect to the remote system. • For Windows 2008 (R2), if the correct account (Administrator) is not specified during collection, the registry on that remote host should be edited. Use the Windows 2008 configuration registry script, or manually add the DWORD value in LocalAccountTokenFilterPolicy and set the data to 1 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system \key , then reboot.
Adapter Models SAS HBA SAS 5E SAS HBA SAS 6E FC HBA LPE11000 FC HBA LPE12000 NIC Pro1000 NIC X520 iSCSI HBA QLA4050C iSCSI HBA QLA4052C iSCSI HBA QLE4060C iSCSI HBA QLA4062C FC HBA QLE2460, QLE2462 FC HBA QLE2560, QLE2562 Emulex Intel QLogic Supported Enclosures This section lists the supported enclosures. Table 3. Supported Enclosures Enclosures Collection Protocol Port Used Latest Supported Version M1000e SSH2 22 4.5 VRTX SSH2 22 1.
Management and Monitoring Software Collection Protocol Port Used Latest Supported Version SCVMM 2008 R2 WMI 135 2.0 SCVMM 2012 SP1 WMI 135 3.1 NOTE: WMI protocol uses multiple ports along with 135 to connect to the remote system. Supported Switches This section lists the supported switches. Table 5. Supported Switches Switches Models Collection Protocol Port Used Latest Supported Version N4032F (Limited Support) SSH2/Telnet 22/23 6.0 2848, 2824, 2816 SSH2/Telnet 22/23 2.
Switches Models Collection Protocol Port Used Latest Supported Version W-651 SSH2/Telnet, SNMPv2 22/23, 161 6.3 W-3200 SSH2/Telnet, SNMPv2 22/23, 161 6.3 W-3400 SSH2/Telnet, SNMPv2 22/23, 161 6.3 W-7210, W-7220, W-7240 SSH2/Telnet, SNMPv2 22/23, 161 6.3 W-3600 SSH2/Telnet, SNMPv2 22/23, 161 6.3 C150 SSH2/Telnet 22/23 8.4 C300 SSH2/Telnet 22/23 8.4 S25N, S25P SSH2/Telnet 22/23 8.3 S50 SSH2/Telnet 22/23 8.3 S55 SSH2/Telnet 22/23 8.3 S60 SSH2/Telnet 22/23 8.
Switches SilkWorm McData Blade Models Collection Protocol Port Used Latest Supported Version 6505 SSH2/Telnet 22/23 7.0 6520 SSH2/Telnet 22/23 7.0 4424 SSH2/Telnet 22/23 5.3 200E SSH2/Telnet 22/23 6.2 4416 SSH2/Telnet 22/23 5.2 2960 SSH2/Telnet 22/23 - 3750G SSH2/Telnet 22/23 - 3750E SSH2/Telnet 22/23 12.2 4948 SSH2/Telnet 22/23 - 5010 SSH2/Telnet 22/23 5.0 5020 SSH2/Telnet 22/23 5.0 5448 SSH2/Telnet 22/23 5.0 9124 SSH2/Telnet 22/23 3.
Storage Arrays PowerVault Models Collection Protocol Port Used Latest Supported Version PS5000 SNMPv2, SSH2/ Telnet, FTP 161, 22/23, 21 - PS6000 SNMPv2, SSH2/ Telnet, FTP 161, 22/23, 21 - PS6100 SNMPv2, SSH2/ Telnet, FTP 161, 22/23, 21 - PS6110 SNMPv2, SSH2/ Telnet, FTP 161, 22/23, 21 - PS6210 SNMPv2, SSH2/ Telnet, FTP 161, 22/23, 21 - PS6500 SNMPv2, SSH2/ Telnet, FTP 161, 22/23, 21 - MD3600f SMCLI Utility - 07.80.41.60 MD3000i SMCLI Utility - 07.80.41.
Storage Arrays Celerra Storage devices (NAS) Models Collection Protocol Port Used Latest Supported Version CX4–240 NaviSphere CLI Utility - - CX4–480 NaviSphere CLI Utility - - CX4–960 NaviSphere CLI Utility - - NX4 SSH2 22 - NS 120 SSH2 22 - NS 240 SSH2 22 - NS 480 SSH2 22 - 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: • • • • • • • • • • • • • • • 20 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 Wireless Controllers Device Collection Upload Collection Confirmation
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 dell.com/support 2. Select your support category. 3.
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.
Installing Lasso Using GUI To install Lasso: 1. Double click the .msi file. The Welcome to the Dell Lasso Installation Wizard is displayed. 2. Click Next. If you already have an earlier version of Lasso, then the message “A previous version of Lasso was detected on your system. Continuing the installation will upgrade Lasso to Lasso . Upgrading to the latest version of Lasso provides several benefits. Would you like to proceed with the upgrade?“ window is displayed.
NOTE: If msiexec is not recognized as an internal or external command, include %SystemDrive%: \Windows\System32 (x86 bit operating system) or %SystemDrive%\Windows\SysWOW64 (x64 bit operating system) to the path variable. Modifying Lasso Installation After installing Lasso, you can modify the components that are installed. To modify the components: 1. Double-click on the .msi file. The Application Maintenance window is displayed. 2. Select Modify and click Next.
From Start Menu To uninstall Lasso from the Start Menu: 1. Click Start → Programs (or All Programs) → Dell → Lasso → Uninstall. The Are you sure you want to uninstall this product prompt is displayed. 2. Click Yes to uninstall Lasso. From Windows Add Or Remove Programs Wizard To uninstall Lasso from the Windows Add or Remove Programs wizard on Windows operating systems: 1. Click Start → Control Panel → Add or Remove Programs. NOTE: This option differs based on the operating system. 2.
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: When retrieving the completed collection from the Storage Processor (SP) on Windows 2003, Windows 2008, and Windows Vista, the firewalls display the prompt to allow this connection. EqualLogic collection SNMP default port 161 (SNMP messages) and port 162 (SNMP traps) NOTE: From EqualLogic array, SNMP should be enabled with public access for inventory collection.
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.
3. Select Enable Report Filtering to exclude Customer Identification Information (CII) in the report. Click Yes in the confirmation message displayed to exclude the information. Else, click No. Click Learn More link to display the window with the information about the data that is filtered. The data that is filtered are: • Network configuration information such as IP address, Gateway, Subnet Mask, and Domain. • Host identification information such as host names.
• 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 • Wireless Controllers • Device Collection • Upload Collection • Confirmation NOTE: Lasso does not support Tape Libraries in this release.
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. Edit the information or add new information. Perform the steps from 4 to step 11 mentioned in the Starting New Configuration section.
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). • Password — Enter the password (optional). NOTE: IP/Hostname information is mandatory, if the port used is other than the default. 6. Click Continue. 7.
Field Description 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. Load a configuration file Select this option to use the configuration file saved in a location other than the Lasso user profile directory. Click Browse to load the configuration file.
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. 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.
To remove a contact, click Delete available next to the contact. Click Yes in the “Do you wish to delete the Customer Contact information for ?” to remove. Else, click No. 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.
To collect more details, the required device page is displayed for each selected device. 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.
Field Description Compellent FluidFS NAS Enter the details for the following fields: • • • CLARiiON Enter the details for the following fields: • • • • • EqualLogic 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 o
Field Description 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. To display Celerra and CLARiiON in Select from the following type of Storage Array(s) do the following: Downloading and Displaying Celerra and CLARiiON Storage Arrays To download and display Celerra and CLARiiON storage arrays, do the following: 1.
Field Description • McDataBlade IP/Hostname Enter the IP address or host name of the selected type of switch. Username Enter the user name . Password Enter the password . Use this as the default switch type Select this option to make the selected type of switch as the default. 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.
Field Description • • • • Cisco Nexus PowerConnect — Select this for all types of PowerConnect Ethernet, B8000, and M8428K switches. Brocade Ethernet — Select this for the Brocade B-Series switches. Force10 IP/hostname Enter the IP address or the host name of the switch. Username Enter the user name. Password Enter the password. Enable Password Enter the password. Use this as the default Ethernet switch type Select this option to make the selected type of Ethernet switch as the default.
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. Click Save New Tape Library to save, display the information in the Tape Libraries in your environment section, and start validation of the Tape Library. Else, click Cancel.
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 Enter the root password if the Sudo user is set for target password. Collect advance logs The option is displayed when the host type VMware and the storage array type EqualLogic, MD Series, or Compellent is selected. Select this option to collect additional log information. NOTE: Type of Storage Array is optional. Click Previous to display the Your Hardware Environment page.
Field Description 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. Your Hardware Environment: Enclosure Modules Enclosure Modules page is displayed only when the servers are discovered through VRTX.
Management & Monitoring Software in your environment Clicking the image next to the software provides the validation status. If validation is successful, image is displayed. Else, 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).
Your Hardware Environment: Wireless Controllers In this page, select the type of Wireless Controllers in your SAN environment, enter the details, and click Continue. Wireless Controllers in your environment Clicking the successful, image next to the Wireless Controllers provides the validation status. If validation is image is displayed. Else, image is displayed. To edit the selected Wireless Controller, click Edit available next to the Wireless Controller.
Device Collection This page displays all the selected types of devices. The validated device has name. The devices that failed validation has validate these devices or remove from the list. image next to the device image next to the device name. You can either re- 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. Click the status.
In the “Lasso can save your usernames and passwords in an encrypted password vault for future re-use. If the password vault is not used, no usernames or passwords will be saved and will require re-entry to run the Lasso 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.
To access the XML and HTML files, go to USERPROFILE%\Dell\Lasso\results directory. Viewing Reports To view the report, perform any of the following: • 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.
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: 4. • mdseries.timeout.value.collection = 200000 which is 120000 by default • mdseries.timeout.value.
Manually Collecting Data For PowerVault Or EqualLogic Or Compellent FluidFS NAS Device To collect information for PowerVault or EqualLogic FluidFS NAS device manually: 1. For PowerVault FluidFS NAS device, log in to PV FluidFS NAS and for EqualLogic FluidFS NAS device, log in to EQL FluidFS NAS using root privilege through SSH. 2. Run the command: • diag start GeneralSystemDiagnostic for versions earlier than 2.0. • system internal diagnostics run-general-diagnostic for version 3.0.
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.
Collecting Storage Device Information From Unix OS For EMC SAN Using any secure ftp client (example: scp): 1. Copy the appropriate EMCGrab file from the %ALLUSERSPROFILE%\Dell\Lasso\Packages\EMCAddon \Grabs_Reports directory to the target Unix system. The EMCGrab file can be seen only if you install EMC Plugin from Add-ons option. 2. Log in to the target Unix system by using the root privilege through SSH. NOTE: Use dual mode authentication if SSH is not enabled for root. 3.
3. Copy the output file to the local system using any secure ftp client. NOTE: When the collection operation of host times out, go to the UnixHC.properties file in the InstallDir and change or increase the time out value. Example: hc.timeout.value = 3600000 which is 1800000 by default. Manually Collecting Data For Tape Library Device NOTE: Lasso does not support Tape Libraries in this release.
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.
Manually Collecting Data For Ethernet and FCoE Switches To collect information for switches: 1. Connect to the switch using Telnet: telnet -f %USERPROFILE%\Dell\Lasso\results\hostname.txt hostname NOTE: On Windows 2000, use HyperTerminal and manually capture the telnet session. 2. After logging in, enter the command relevant to the type of switch.
3.
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. If the command fails, in the case of older switch firmware, then run the following commands: 4.
Manually Collecting Data For PowerConnect Ethernet Switches 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.
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 Fibre Channel Switches To collect information, co
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. The commands to collect the data for the types of switches are: • Brocade: – supportShow • McData: – show all – If this command fails, see List of commands • McDataBlade: • Cisco: – If the show allcommand fails.
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 zoning • show fabric • show topology • show switch • show domains Manually Collecting Data For Enclosures — M1000e To collect the data, connect to the M1000e 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.
• -RD- — customize the results directory path. • -NU — disable the report upload. • -NA — report not archived. • -CS — community string. • -CN — company name. • -IMPORT — to import the excel sheet. • -VALIDATE — to validate the device type. • -SP — to display data collection progress in CLI NOTE: All options are case-insensitive. NOTE: -UZ argument cannot be used when -Secured option is used.
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 Device Types Parameters Required Ethernet & FCoE Switches CiscoEthernet -IP , -UN , -PD , DT CiscoEthernet, -EP CiscoNexus -IP , -UN , -PD , DT CiscoNexus or CiscoFCoE PowerConnect -IP , UN, PD, -EP , -DT PowerConnect Force10 -IP , -UN , -PD , DT Force10, -EP, -OF BrocadeEthernet -IP
Devices Device Types Parameters Required Attached Hosts Windows -IP , -UN , -PD , DT Windows, -D , -ST Linux -IP , -UN , -PD , DT Linux, -RP , SU, -ST Solaris -IP , -UN , -PD , DT Solaris, -ST HP-UX -IP , -UN , -PD , DT HP-UX, -ST AIX -IP , -UN
Devices Management and Monitoring Software Management and Monitoring Software Device Types Parameters Required VRTX -IP, UN, PD, -DT VRTX HIT Kit for VMware -IP, UN, PD, -A or -B, -DT HITKITVM SANHQ -IP, UN, PD, -D, DT SANHQ VCenter -IP, UN, PD, -DT VCENTER SCVMM -IP, UN, PD, -D, DT SCVMM PowerConnectController -I
• lasso.cmd -Q -DT -IP -UN -PD -A • lasso.cmd -Q -DT -IP -UN -PD -B • lasso.cmd -Q -DT -IP -UN -PD -RD c:\LassoReports\ • lasso.cmd -Q -IP -DT -CS -PI NOTE: The default proxy port number that is used is 80. • 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.
2. 3. a. Click Start → Run type cmd, press Enter. b. Type ftp . Make sure that ftp server is available and running: a. Using the browser, enter the ftp://ftp.dell.com/serviceability url. b. Check for LassoCatalog.cab file. If the ftp server is not available: a. Ping ftp server. b. If the server is accessible, check the firewall settings to unblock the ftp port (port 20 and 21).
b. If the server is accessible, check the firewall settings to unblock the ftp port (port 20 and 21). 4. Make sure that proxy server is reachable with port mentioned. 5. If the server is reachable, make sure that user name and password are valid. 6. If the checksum validation is unsuccessful, retry package download. Troubleshooting Unsuccessful EMC Package Installation To troubleshoot unsuccessful EMC package installation: 1.
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. This default behavior prevents Lasso from executing the command through SSH remotely if root credentials are used. For more information, see Prerequisites For Data Collection.
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.
7. Copy the collection to %USERPROFILE%\Dell\Lasso\results\ While troubleshooting collectio, to edit privilege user on: • CX array, see Edit Privilege User on CX array. • AX Array, see Edit Privilege User on AX Array. 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.
Troubleshooting Ethernet Switch To reproduce the steps Lasso performs when automating Ethernet Switch validation 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. 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.
3. For collection, copy from mkdir \\Device_Hostname\c$\temp\Dell\Lasso\EMCReports\ the appropriate EMCReport to the remote system using the command copy EMCRPTS_*_V30.EXE \\ Device_Hostname \c$\ temp\ Dell\ Lasso\ EMCReports\. The output should be the hostname of the system you are connecting to and the original prompt should be displayed. If errors are displayed, then the system cannot connect to the remote device.
Troubleshooting VMware Collection To display the error messaged received during collection, try to run the Lasso commands. Lasso collection uses the provided user name and password to make a remote connection to the target device and execute a command. If collection fails in Lasso, test the command using the following steps: 1. Use a secure telnet client like putty to login to vmware system using root privilege. For steps to allow root access, see Allowing Root Access To Unix Server.
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 Certificate authentication failed. Ensure that the client certificate is valid and able to authenticate to the server. 24 UPLOAD_CHUNK_ERROR 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.
Error Code Error Message 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. Lasso is unable to copy the script from the remote system and the script may be suspended. Try to reboot the remote host.
Error Code Error Message 119 Host collection execution failed during HyperV Recognition. Lasso is unable to copy the script from the remote system and the script may be suspended. Try to 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.
Error Code Error Message 157 DSET validation is not successful. Validating Dell System E-Support Tool is not successful because of an unknown error code. 187 Unable to validate the device. Make sure that the connection to the device is available through FTP and then retry the operation. 188 Unable to validate the device. Make sure that MDSM Software has valid permissions and then retry the operation. 189 Unable to validate the device.
Error Code Error Message 200 plink.exe not found. 201 pscp.exe not found. 202 Lasso_grab.sh not found. The error occurs when the package is either corrupt or not installed correctly. Try to reinstall Lasso. 203 EMC executable not found. The error occurs when the package is either corrupt or not installed correctly. Try to reinstall Lasso. 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.
Error Code Error Message 223 SAN HQ server version not found. 295 Compellent Storage Client exe is not found. Make sure that the Compellent Storage Client exe is available in the bin folder. 297 Failed to get Service Tag Information. Refer to Manual UNIX collection and Linux Service Tag Collection. 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.
Error Code Error Message 308 SP collection timed out. Try the collection again. If the error persists, make sure that you have the latest Navisphere CLI. To verify this, run the installer. Also, try to collect the SP Manually. Finally, 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.
Error Code Error Message 411 Switch collection was complete, but collection file not found! You may try to collect switch data manually. 412 Tape Library collection was complete, but collection file not found! You may try to collect tape library data manually. NOTE: Lasso does not support Tape Libraries in this release. 413 Switch collection file not moved properly! You may try to collect switch manually.
Error Code Error Message • 501 Manual Collection Unable to bind to the Controller specified. Verify the IP Address. 601 Vault password is incorrect. 602 Connection failed! Make sure that the IP/device is valid and reachable. 700 Failed to copy Dell Collector to remote host. 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.
Error Code Error Message 805 Collection has failed for Enclosure due to incorrect IP/hostname and credentials. 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: – 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.
• How can the time out value for validating automatically discovered 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.
– Lasso creates a single .zip file that is 2048-bit encrypted (unless this option is disabled, or Lasso is running in a non-exportable country). Only an authorized Dell representative with a valid Wrangler processing utility can load the file and decrypt the contents. Lasso uploads the file to the Dell's ftp site and provides high level of privacy protection and security. This site has "write-only" access to Lasso and the public, and has no read access.
• Why should Lasso be used when the time taken to troubleshoot problems is longer than manually collecting the data with Lasso? – Lasso automates the collection process. The data collected remotely is dependent on the network configuration of the environment . If the access to the system running Lasso to the target devices is blocked, then the scripts can not complete the collection. If all the devices are unavailable, then run the collection scripts manually.
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.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow.
this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all.
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
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.
