Dell Lasso Version 4.
Lasso is a Java-based utility that automates the collection of logs and configuration from servers, disk arrays (EqualLogic, PowerVault MD-Series and EMC), Fibre Channel switches (Brocade, McData, and Cisco), Tape Libraries, and Ethernet and FCoE switches. After the collection, Lasso parses the data into an XML file, which is packaged with the original collection and encrypted. The encrypted file is uploaded to Dell for review.
- Dell PowerConnect M8024/M8024K - Dell PowerConnect M6348 - Dell PowerConnect B-Series 8000 - Cisco 2960 - Cisco 4948 - Cisco 3750E/3750X - Cisco CBS 3130 - Cisco CBS 3030 - Cisco Catalyst 3750E - Nexus 5020 - Force10 S50N/S481 What’s New Providing enhanced user interface in compliance with Dell's lucidity usability requirement. Ensuring that Lasso validates the PC Ethernet Switch, when configured with only username.
Prerequisites Make sure IP connectivity is available to all defined devices. .NET framework 2.0 and SP v1.0 or above. NOTE: In the case of EqualLogic and MD series SAN, the presence of the .Net framework 2.0 or above on the remote Windows host is mandatory for successful Windows host collection. To collect from EMC, use a computer that is not a Fibre Channel attached host. To collect from EqualLogic, install Lasso on one of the iSCSI hosts.
A modified timeout value, as the default timeout value of 15 minutes may not be sufficient for collection from PowerVault NX3500 and EqualLogic FS7500 devices to take place. The timeout value (nas.timeout.value) needs to be modified in the NAS.properties file present in the Lasso Install directory. NOTE: The timeout value is in milliseconds. NOTE: This timeout mechanism is applicable to all the devices. For collection to be successful, change or update the corresponding device properties file.
Issue 5: For a Linux host attached to an EqualLogic Array, values for the attributes - Manufacturer of NIC and Model Name are displayed as Unknown. Issue 6: When multiple collections are run on an ESX 5.0 host, Lasso fails to delete the Dell Collector folder from the temporary directory. Issue 7: For stacked Cisco Ethernet Switches, the value of the serial number gets interchanged between the Master and Member Switches.
Issue 20: Telnet must be enabled on all McData switches for Lasso to collect from them. Issue 21: Lasso's "auto-discover" feature only works with EMC CLARiiON arrays, not for hosts attached to Celerra, EqualLogic, and PowerVault MD Arrays. Resolution: For those arrays, enter in the name or IP address of each attached host.
DF500088: Lasso is not parsing the Cisco 2960 switch. Description: Lasso is not parsing any information for Cisco 2960 switch. DF504839: When the PowerConnect Ethernet switch is configured with just the username, Lasso fails to validate the switch. Description: When the PowerConnect Ethernet switch is configured with just the username and no password, Lasso fails to validate the switch and displays the Error 499: Authentication validation failed! Try validation again, and check username and password.
Description: If there are dead paths configured between VMware hosts and MD Series and EqualLogic Arrays, Lasso fails to parse the LUN information gathered from these dead paths. CR518655: Lasso needs to support MemKit for vSphere version 5.0. Description: Lasso should gather all the MemKit attributes for vSphere version 5.0 host which is attached to the EqualLogic array. DF519120: Lasso should display valid values for Member Sessions in MemKit tab for vSphere.
DF504866: For ESX 3.5 host, the attribute VMFSUUID under the section VMFS iSCSI displays incomplete value in HTML. Description: For the ESX 3.5 host, the attribute VMFSUUID, under the section VMFS iSCSI, displays incomplete values. DF519938: For Windows 2008 R2 Virtual Machine host, iSCSI NICs are not parsed and displayed in the output HTML file.
