Dell Lasso Version 4.7.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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. © 2016 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 this Release.................................................................................................................. 7 Key Features.......................................................................................................................................... 8 Support Matrix....................................................................
Your Company Contacts.............................................................................................................. 38 Your Hardware Environment........................................................................................................ 39 Your Hardware Environment: Storage Arrays.............................................................................. 40 Your Hardware Environment: Fibre Channel Switches...............................................................
Manually Collecting Data For Enclosure — VRTX.............................................................................. 71 Manually Collecting Data For Enclosure — PowerEdge FX2.............................................................72 Manually Collecting Data For HITKIT Appliance Under VRTX........................................................... 73 Manually Collecting Data For SAN HQ DEVICE.................................................................................
9 Use Case Scenario............................................................................................ 104 10 Frequently Asked Questions........................................................................ 106 FAQ — About Lasso.......................................................................................................................... 106 FAQ — Passwords and Security........................................................................................................
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 Extensible Markup Language (XML) and HyperText Markup Language (HTML) formats.
– Spanning Tree PortFast attribute from PowerConnect and Dell Networking switches – Fibre Channel Host Bus Adapter (FCHBA) onboard settings and other sections for Windows, Linux, and VMware ESXi 6.0 and 5.5 – Brocade Fibre Channel switch interconnect fabric – Virtual port information for iSCSI and Fibre Channel I/O cards on Compellent storage arrays – Integration of Dell System E-Support Tool (DSET) version 3.
• Collect and parse Device ID, Vendor ID, Subdevice ID, and Subvendor ID for NIC and HBA cards for Linux and VMware hosts. • Enhancement for output messaging format by displaying the specific error codes and error messages if the device is not reachable, protocols are not enabled, and validation is not successful. • Import devices and credentials information from Microsoft Excel.
• Collect and parse data from devices in SAN environment for Windows 8 Management Station and Windows 2012 Server. • Collect, parse, and view the SAN configuration report for Cisco 5050 and 5548 FCoE models.
* Interface QoS Information * Interface DCB Information * Interface Media Information – Dell Force10 * PFC Summary * ETS Summary * Interfaces Configuration report – Cisco Nexus * PFC Information * Policy Map * LLDP Information * LACP Information • Run multiple instances of Lasso CLI and GUI simultaneously. • Stop default upload of the report in the CLI using -nu option. • 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.
• Support for Array ping test between the members within an EqualLogic Group. • Collect and parse the Qlogic iSCSI adapter information from Windows, Linux, and VMware hosts attached to Compellent. • Collect Emulex information from Windows, Linux, and VMware hosts attached to Compellent. • Collect and parse SAS HBA information from Windows and Linux (32-bit only) hosts attached to PowerVault MD Series and Compellent. • Validate user input for Ethernet Switch type in the related GUI pages.
Support Matrix This chapter lists the supported devices and operating systems for Dell Lasso. Supported Operating Systems The following table lists the supported operating systems. Table 1.
Operating System Collection Protocol Port Used Latest Supported Version Oracle VM Server SSH2 22 - Microsoft Hyper-V Server 2008 R2 WMI 135 - Microsoft Hyper-V Server 2012 R2 WMI 135 - Microsoft Hyper-V Server 2012 WMI 135 - XenServer 6.0 SSH2 22 - XenServer 6.2 SSH2 22 - XenServer 6.5 SSH2 22 - XenServer 7.0 SSH2 22 - VMware ESX 3.5 SSH2 22 - VMware ESX 4.0 SSH2 22 - VMware ESXi 4.0 SSH2 22 - VMware ESXi 4.1 SSH2 22 - VMware ESXi 5.
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 PERC 5E SAS HBA PERC 6E SAS HBA SAS 5E SAS HBA SAS 6E Emulex FC HBA LPE11000 FC HBA LPE12000 Intel NIC Pro1000 NIC X520 QLogic iSCSI HBA QLA4050C iSCSI HBA QLA4052C iSCSI HBA QLE4060C iSCSI HBA QLA4062C FC HBA QLE2460, QLE2462 FC HBA QLE2560, QLE2562 FC HBA QME2462 Broadcom CNA BCM57800 CNA BCM57810 CNA BCM57840 Supported Enclosures The following table lists the supported enclosures. Table 3.
Supported Management and Monitoring Software The following table lists the supported management and monitoring software. Table 4. Supported Management and Monitoring Software Management and Monitoring Software Collection Protocol Port Used Latest Supported Version WMI 135 3.02 HIT KIT for VMware SSH2 22 3.1 vCenter HTTPS 443/9443 5.5 SCVMM 2008 R2 WMI 135 2.0 SCVMM 2012 SP1 WMI 135 3.
Switches Models Collection Protocol Port Used Latest Supported Version NOTE: Lasso supports Dell Networking C1048P (Port Expander) with C9010 switch. Dell PowerConnect PowerConnect 2848, 2824, and 2816 SSH2/Telnet 22/23 2.0 3524, 3524P, and 3548 SSH2/Telnet 22/23 2.0 5424, 5448 SSH2/Telnet 22/23 2.0 5524, 5548 SSH2/Telnet 22/23 4.1 6224, 6248 SSH2/Telnet 22/23 3.3 7024, 7048, and 7024F SSH2/Telnet 22/23 5.1 8024, 8024F SSH2/Telnet 22/23 5.
Switches Models Collection Protocol Port Used Latest Supported Version W-7210, W-7220, and W-7240 SSH2/Telnet, and SNMPv2 22/23, 161 6.3 W-3600 SSH2/Telnet, and 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.3 S4810, S4820T SSH2/Telnet 22/23 9.3 S5000 SSH2/Telnet 22/23 9.3 S6000 SSH2/Telnet 22/23 9.
Switches SilkWorm McData Blade Models Collection Protocol Port Used Latest Supported Version 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 3750X SSH2/Telnet 22/23 - 4948 SSH2/Telnet 22/23 - 5010 SSH2/Telnet 22/23 5.0 5020 SSH2/Telnet 22/23 5.0 5548 SSH2/Telnet 22/23 5.0 7xxx series SSH2/Telnet 22/23 5.0 9124 SSH2/Telnet 22/23 3.
Storage Arrays PowerVault Compellent Models Collection Protocol Port Used Latest Supported Version PS6000 SNMPv2, SSH2/ Telnet, and FTP 161, 22/23, and 21 9.0 PS6100 SNMPv2, SSH2/ Telnet, and FTP 161, 22/23, and 21 9.0 PS6110 SNMPv2, SSH2/ Telnet, and FTP 161, 22/23, and 21 9.0 PS6210 SNMPv2, SSH2/ Telnet, and FTP 161, 22/23, and 21 9.0 PS65X0 SNMPv2, SSH2/ Telnet, and FTP 161, 22/23, and 21 9.0 PS6610 SNMPv2, SSH2/ Telnet, and FTP 161, 22/23, and 21 9.
Storage Arrays Models Collection Protocol Port Used Latest Supported Version FS8600 SSH2, FTP, SSH2 22, 44421, 10022 5.0 FS7500 SSH2, FTP 22, 44421 4.0 FS7600 SSH2, FTP 22, 44421 4.0 FS7610 SSH2, FTP 22, 44421 4.0 NX3500 SSH2, FTP 22, 44421 3.0 NX3600 SSH2, FTP 22, 44421 3.0 NX3610 SSH2, FTP 22, 44421 3.
Table 7.
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. Go to 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 or Upgrading Lasso You can install Lasso: • Using GUI • Using CLI 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 .
The Ready to Install the Application window is displayed. 8. Click Next to continue with the installation. The Lasso has been successfully installed window is displayed. 9. Click Finish to close the installation wizard. Installing Lasso Using CLI To install or upgrade, at the command prompt, set the directory to LassoMSIPath and run the command: msiexec /qn /i /log install.txt The installation messages are logged in the install.txt file.
• Using GUI • Using CLI Using GUI To uninstall Lasso using the GUI, use one of the following options: • Start Menu • Windows Add Or Remove Programs Wizard 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.
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. Compellent Web Service (Port 443) 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.
– SNMP: Port 161. To enable SNMP, in a browser, enter the to connect to the controller. In the Mobility Controller page, go to Configuration → SNMP and add the SNMP community string. NOTE: The community string is case-sensitive. • For System Center Virtual Machine Manager (SCVMM), powershell must be enabled in target Windows VMM host.
– Upload an existing collection • CLI – 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.
Following actions are performed based on the selection: • 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.
NOTE: Loading configuration files from Lasso 3.8 and earlier may result in loss of some device authentication information. To load an existing configuration: 1. Click Start → Programs (or All Programs) → Dell → Lasso and click Lasso. The Welcome to Lasso window is displayed. 2. Select Load a configuration file and click Browse. Specify the file and click Continue. A dialog box displays indicating that background validation is in progress. The Your Company Information window is displayed. 3.
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). • Password — Enter the password (optional). NOTE: IP/Hostname information is mandatory, if the port used is other than the default. 6. Click Continue.
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 Report Filtering option to exclude Customer Identification Information (CII) from the report. NOTE: If this option is selected, only Company Name is mandatory. It is recommended to not select the Enable Report Filtering option, if the Lasso collection is performed for technical support or proactive maintenance support. Click the Learn More link to display the list of sensitive data that is filtered. Company Information Table 10.
Your Company Contacts To edit the information of the company contact, click Edit available next to the contact. Update the required fields and click Update Contact to save the updates. Else, click Cancel. To remove a contact, click Delete available next to the contact. Click Yes in the “Do you wish to delete the Customer Contact information for ?” to remove. Else, click No. Edit Contact Information Table 12. Edit Contact Information Field Description Name Enter the company contact name.
Field Description Management & Monitoring Software Select this option to collect data for the management and monitoring software. Wireless Controllers Select this option to collect data for the wireless controllers. 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.
Field Description • • Celerra Enter the details for the following fields: • • • Compellent MD Series PV FluidFS NAS CS IP/Hostname Username Password Enter the details for the following fields: • • • IP/Hostname Username Password NOTE: In the Select an IP address dialog box, select a web server IP address from the dropdown list. Once the option is selected, the web sever IP address will be used to communicate with all Compellent arrays for that instance of Lasso.
Field Description EQL FluidFS NAS Enter the details for the following fields: • • • MD Series Management IP Username Password Enter the details for the following fields: • • PV 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 Select this option to save the user name and password authentication information as default for the included arrays.
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. Else, click Cancel. To delete a Fibre Channel Switch, click Delete available next to the switch(es).
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.
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.
Field Description • Oracle VM Server IP/hostname Enter the IP address or the host name for the selected type of host operating system. Username Enter the user name. Password Enter the password. Root Password Enter the root password.
Field Description 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. Your Hardware Environment: Enclosures In this page, enter the details for the selected type of Enclosure in your SAN environment and click Continue. Enclosures in your environment Clicking the image next to the enclosure provides the validation status.
Field Description NOTE: To discover the integrated servers, you need to install DSET using the Add-ons option available on the Welcome to Lasso screen. DSET captures the hardware view of the servers. If servers are connected to the SAN storage, each server will have to be added to Lasso via the LAN IP address for individual collection. 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.
Modify Server Information To edit the iDRAC information, enter the data in the required fields for the selected type of iDRAC. Click Update Server to save, display the information in the Enclosures Modules in your environment section, and start validation of the enclosure. Else, click Cancel. Table 19. Modify Server Information Field Description IP/Hostname Enter the IP address or host name of the selected type of enclosure. Username Enter the user name. Password Enter the password.
Field Description • HIT Kit for VMware • SAN HQ • vCenter • SCVMM IP/hostname Enter the IP address or host name of the selected type of software. Username Enter the user name. For ESXi versions later than 5.5, the domain name is required for adding the vCenter to Lasso. The domain name is also required if ESXi 5.5 is configured for Single Sign On (SSO). NOTE: The username for adding a vCenter configured for SSO must include the domain name 'vsphere.local'. For example, vsphere.local\username.
To delete a Wireless Controller, click Delete available next to the Wireless Controller. To verify Wireless Controller(s) from the existing user configuration, select the required Controller(s), and click Revalidate Selected Wireless Controllers. Add/Modify Wireless Controller information To add or modify Wireless Controller information, select the type of Wireless Controller from the drop down list and enter the data in the required fields.
After all the devices are verified and validated, click Start Collection to start the collection. Click the image to check the status of the collection. Click Cancel Collection to cancel the collection. Click Continue to parse the data and generate XML and HTML output. The generated files are added to the original collection .zip file. The data that is uploaded to the Dell Technical Support site is encrypted.
Table 22. Upload Options Description Open Location Click to open the location where the collected files are saved. Upload Full Collection Select this option to automatically upload the collection files to Dell Technical Support site. NOTE: If this option is selected, the zip.gpg file is uploaded. Authenticated Proxy Select this option to upload the collection files to Dell Technical Support site using proxy. IP/Hostname Enter the IP address or hostname. Port number Enter the port information.
The collection log file ___validate.log is available at %USERPROFILE %\Dell\Lasso\logs\ location. The device log file for Lasso is available at %USERPROFILE%\Dell\Lasso\logs\ location and the Lasso user interface log file is available at %USERPROFILE%\ Dell\ Lasso\ lasso.log location. Generated File Formats Lasso generates raw data files, TXT, XML, and HTML files: • Raw Data Files — Lasso generates two types of raw data files: – Raw data file with a .zip extension.
Manual Collection 5 If you are not able to collect data using Lasso GUI, then you can manually collect the data. To perform manual collection, login to the required device and run the device specific commands.
The 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. Run the following command: /nas/sbin/log_config -d The collection file (log_config*.gz) is generated in the /nas/var/log/ directory.
Continue to check the progress of the SPCollect (using this command) until *_runlog.txt is deleted and corresponding *data.zip file is created. Copy the created *data.zip file to the current working directory using one of the following commands: 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.
Manually Collecting Data For EqualLogic Device To collect information for EqualLogic device manually: 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.
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.value (in milliseconds) in the NAS.properties file available in the Lasso install directory.
The output .zip file is generated in \DellCollector\Collection\zip\ directory. Collecting Storage Device Information For UNIX OS Using any secure ftp client (example: scp): 1. Copy the appropriate dellcollector from the LassoInstallDir>\Bin directory to the target Unix system. By default, the Lasso installation directory is \Dell\Lasso\Bin\. 2. Log in to the target Unix system by using the root privilege through SSH.
5. Run the EMCGrab: /dellcollector.sh —autoexec. 6. Accept the license agreement. The output is generated in the /tmp/emcgrab/outputs/ directory and you can copy it to the local system by using the secure ftp client. NOTE: When the collection operation of the host times out, go to the UnixHC.properties file in the installation directory and change or increase the time-out value. Example: hc.timeout.value = 3600000 which is 1800000 by default.
– terminal length 0 – To run the commands, see List Of Commands For Force 10 Switches. • Dell Networking – If the firmware version is 6.0 and above, to run the commands, see List Of Commands For PowerConnect Ethernet – If the firmware version is 9.4 and above, 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 SSH/Telnet. 2.
NOTE: On a SAN consisting of many Cisco Ethernet switches, you may need to increase the time out value. By default, the time out value for these switches is 3 minutes (in milliseconds). This value (ciscoethernet.timeout) can be modified in the file ESC.properties located in the Lasso install directory. Manually Collecting Data For Cisco Nexus Device Lasso provides support to Nexus 5020 and 5548 switches. To collect manually: 1. Login to Cisco Nexus switch through SSH/Telnet 2. Run the command config.
• show mac-list • show mac-address-table • show class-map • show license usage • show lacp neighbor • show lacp port-channel • show port-channel capacity • show port-channel load-balance • show port-channel usage • show port-channel traffic • show queuing interface • 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.
4. • show port-channel • show mac-address-table • show spanning-tree brief • show spanning-tree • show cee maps • show vlan fcoe • show ip interface brief • show interface switchport • show lldp statictics • show port-channel summary • show mac-address-table count • show spanning-tree mst brief • show qos rcv-queue multicast all • show qos interface all • show fcoe-map • fos switchshow • fos cfgshow • fos zoneshow • chassisshow Capture the console output .
3.
Manually Collecting Data For Force 10 and Dell Networking Switches To collect information for Force 10 switches manually: 1. Log in to Force 10 switch through SSH/Telnet. 2. Run the following commands: Table 23.
• • • • • • • • • • • • • • • • • • • • • • show show show show show show show show show show show show show show show show show show show show show show interfaces ets summary 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 interfaces port-channel brief Manually Co
– If this command fails, see List of commands • Cisco: – terminal length 0 – show running-config – show flogi database – show startup-config Manually Collecting Data For Brocade Device To collect manually: 1. Log in to Brocade Fibre channel switch through SSH 2. Run the command supportShow. 3. Capture the console output NOTE: On SAN having many Brocade switches, you need to increase the default time out value of 3 minutes (in milliseconds). This value (brocade.timeout) can be modified in the FCSC.
• show port info • show port technology • show port exit • show loginserver • show feature • show security portbinding • show security switchbinding • show openTrunking config • show thresholdAlerts alerts • show fabric topology • show fabric nodes Manually Collecting Data For McDataBlade Device The following sub-commands are included in the show all command. In some older switch firmware, the show all command may not work.
4.
4.
4.
6. Run the command net use \\\database /d to disconnect the appliance from the local system. 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.
• show version • show license verbose • show license limits • show log all • show tech • show ap active • show aaa profile • show aaa authentication all • show firewall • show keys all • show vlan mapping Manually Collecting Integrated Server Information Within VRTX To manually collect integrated server information within VRTX 1. Run the command prompt as an administrator. 2. Run cscript Integrate_Server_Collector.vbs in the Lasso installation directory. 3.
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. Create the configuration file using the GUI, before running Lasso using CLI. To start collection, run the following command from path: Lasso.
• -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. • -IMPORT — to import the excel sheet. • -VALIDATE — to validate the device type. • -SP — to display data collection progress in CLI • -ENCR— to provide passwords in encrypted format NOTE: All options are case-insensitive.
Collecting For Single Device Using CLI For single device collection, run the command: lasso.cmd -Q -OF -IP -DT -UN —PD -D -Secured —RD 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 Fibre Channel Switches Brocade -IP , -UN , -PD , -DT Brocade McData -IP , -UN , -PD , -DT McData McDataBlade -IP , -UN , -PD , -DT McDataBlade Cisco -IP , -UN , -PD , -DT Cisco CiscoEthernet -IP , -DT CiscoEthernet CiscoNexus -IP , -UN , -PD , -DT CiscoNexus or CiscoFCoE Power
Devices Device Types Parameters Required Optional Parameters NOTE: -EP is optional. If the PowerConnect Ethernet switch is configured, then password is required for Lasso to perform the collection. NOTE: -EP is not required for PowerConnect BSeries and and M8428K.
Devices Device Types Parameters Required Optional Parameters NOTE: To provide the Sudo user credentials in Lasso for collecting data from Linux or VMware, the switch -SU is mandatory. NOTE: -ST is mandatory and can have Celerra, CLARiiON, EqualLogic, MD Series or Compellent types of storage array.
The following examples provide the command for single device collection for various devices. • lasso.cmd -Q -IP -DT -ST -UN -PD -CN • lasso.cmd -Q -OF -IP -DT -UN -PD • lasso.cmd -Q -IP , DT -UN -PD • lasso.cmd -Q -IP -CS -DT • 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.
1. 2. 3. Make sure that local ftp client is running: 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. Make sure that the files and folder permissions are in %allusersprofile%\
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 MD Series To troubleshoot MD Series, make sure that: • MDSM software is installed in the system or you can download this from %SystemDrive%:\Pro
Troubleshooting Compellent Collections for SCOC Versions Prior to 6.6.x For successful validation or collection, make sure that the PhoneHome functionality to the Compellent Co-pilot services is working. To troubleshoot Compellent collections: NOTE: The following troubleshooting steps are applicable only for SCOS versions prior to 6.6.x 1. If multiple IPs are configured on Lasso management station, include the IP address of the same subnet as array in the Compellent.properties file to connect to the array.
4. Ensure Lasso is not running on a Virtual Center Server. 5. Ensure Lasso is not running on an SCVMM Server. 6. Ensure Lasso is not running on an IIS Server or have the IIS Microsoft Service running. 7. Ensure the server where Lasso is running is not actively browsing to https://site.com. 8. If Enterprise Manager Data Collector is installed and running on the server where Lasso is running, close the EM application. 9.
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. Therefore, SPCollects always fail on AX arrays unless the system running Lasso is added as a privileged user. 6. Connect to Navisphere Manager manually and run the SPCollect. 7. Copy the collection to %USERPROFILE%\Dell\Lasso\results\ While troubleshoo
The following table provides the list of user name, interfaces, and the user role: Table 25. Interface: CLI Username Interfaces Role Administrator Web, CLI Administrator newuser Web, CLI Administrator Troubleshooting Ethernet Switch To reproduce the steps Lasso performs when automating Ethernet Switch validation or collections: 1. Add Telnet or SSH to each switch to make sure that username/password credentials are correct and the prompt such as password change request is not displayed. 2.
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.
For steps to allow root access, see Allowing Root Access To Unix Server. NOTE: If root access is not enabled through SSH, use dual mode authentication. 2. Run vm-support-n and use secure ftp client to transfer the collection created in the root user’s home directory. The collection is transferred to the %USERPROFILE\ Dell\ Lasso\ results folder. To collect the data manually and not troubleshoot, see Manual VMware Collection.
8 Error Codes The following table provides the error codes and the messages. Table 26. Error Codes 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 23 UPLOAD_CERTIFICATE_ERROR 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.
Error Code Error Message 104 Failed to create temporary directory on remote host. 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 115 Cluster IP cannot be provided for windows host collection. Please provide the node IP and retry the collection. 118 Copying HyperVRecognize.exe to remote host was unsuccessful. 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.
Error Code Error Message 155 DSET validation is not successful. Unable to gather Software or Logs data. Make sure that user name and password are correct, and then retry. 156 DSET validation timeout. 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.
Error Code Error Message or Telnet and does not have active SSH or Telnet console is open, and then retry the operation. 199 Unable to validate the device. Make sure that the IP address or hostname, user name, and password are correct, and then retry the operation. 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.
Error Code Error Message 221 Unable to copy Service Tag exe to the remote system. 222 Dependent Exe's and DLL's not found. 224 Enclosure module host collection is not successful. 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.
Error Code Error Message Make sure that the SP is available and running. Also, connect to Navisphere Manager setup page and restart the management server. 307 Failed to create .zip file out of getall and getlog. Manually, you may need to compress the getall and getlog into a .zip file. 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.
Error Code Error Message 401 Unable to collect storage management information on RAID controller module. The storage management software in use is not compatible with the firmware on the RAID controller modules in the Storage Array. 411 Switch collection was complete, but collection file not found! You may try to collect switch data manually. 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.
• 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. 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? – Lasso is a stand alone collection utility that automates the collection of all pertinent hardware and software configuration details from the target SAN attached servers, Dell Storage Arrays, Fibre Channel, Ethernet and FCoE Switches.
• 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). 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. • Who can view the uploaded data collection? – From version 2.9.0 and later, a "write-only" ftp site is used and "view" or "read" permission are not available.
– 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. Example: If the "admin$" share is disabled on Windows through a Group Policy, then Lasso can not execute the EMCReports remotely and is a limitation in Lasso.
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.
