IBM DS3000, DS4000 and DS5000 Support Data Collection
For the IBM System Storage DS3000 / DS4000 / DS5000 / DCS3000 series (LSI Engenio platform), collect "All Support Data" using the DS Storage Manager installed on the management station. The result is a zip archive (for new firmware, a 7z archive). Menu locations vary depending on controller firmware versions; verify the firmware version before proceeding.
Preparation: Connect to the Management Port
The management station should be able to reach both controllers. The table lists legacy factory-default management addresses; use the configured addresses if they differ. For a direct connection, put the laptop on the relevant subnet with mask 255.255.255.0. The source estimates 2–5 minutes before a ping response may become available.
| Controller | Management Port 1 | Management Port 2 |
|---|---|---|
| Controller A | 192.168.128.101 | 192.168.129.101 |
| Controller B | 192.168.128.102 | 192.168.129.102 |
Verify Controller Firmware Version
In the Array Management window of Storage Manager, select the controller to view its properties (Right-click the controller in Logical/Physical View → Properties, or select the controller in the Physical/Hardware tab and view the Firmware version on the right). For DS3200 / DS3300 / DS3400, the source uses the Support tab procedure regardless of firmware; this is a menu-selection distinction, not a reason to omit firmware information from the case.
Collect Based on Firmware Version
| Controller Firmware | Menu Path |
|---|---|
| 6.x | Advanced → Troubleshooting → Collect All Support Data |
| 7.xx ~ 7.7x | Advanced → Troubleshooting → Support Data → Collect |
| 7.8x ~ 7.84 | Monitor → Health → Collect Support Data |
| 7.86, 8.20 | Monitor → Health → Collect Support Data Manually… (generates *.7z) |
| DS3200 / DS3300 / DS3400 (All Versions) | Support → Gather Support Information (Collect All Support Data) |
Locate the corresponding menu based on the table above. Examples for firmware 6.x and 7.xx:
Firmware 7.8x and later are located under the Monitor menu:
In the pop-up window, click Browse to specify the save path and filename, then click Start. Wait for all items in the Execution summary to complete.
For DS3200 / DS3300 / DS3400, click Gather Support Information in the Support tab, specify the file, and then click Start.
- Send the generated archive to Technical Support.
If you receive the message "Reservation is not granted," another management station is currently collecting support data. Please try again later.
Supplementary Data (Collect as required by Technical Support)
DDC Diagnostic Data
After a specific unexpected reboot of the controller, the Major Event Log (MEL) will display "Diagnostic data is available." In this case, DDC data may need to be saved. Right-click the storage in the Enterprise Management window → Execute Script. In the script window, enter the following (note the semicolon at the end), first Verify Syntax, then Execute Only:
save storageSubsystem diagnosticData file="C:\TEMP\ddcLogs.zip";
When the MEL for models such as DCS3700 / DCS3860 displays "Diagnostic data capture has been captured," you can save it via Monitor → Health → Storage Subsystem Diagnostic → Diagnostic Data Capture → Retrieve, or execute:
save storageSubsystem ddc file="C:\TEMP\ddcLogs.zip";Automatically Saved Support Data
Storage Manager provides automatic support-data collection for critical events when enabled. The source describes this from firmware 6.x and gives C:\Program Files (x86)\IBM_DS\client\data\monitor as the default location on its management station. Check the actual setting under Tools → Legacy Collect Support Data → Automatically...; paths and menu labels vary by installation and release.
Additional Information Required for Performance Issues
- Specific symptoms and business impact of performance issues; overall architecture (Application – Server – SAN – Storage) and application characteristics.
- Which volumes or hosts are experiencing issues, and the logical and physical layout of the volumes (server-to-storage mapping).
- The time when the issue first occurred, any environmental changes at that time, and patterns observed during regular business hours.
- Indicators suggesting the issue originates from storage; whether the business requires high IOPS or high throughput (MB/s).
- Where and how performance is measured, including data demonstrating the issue and reference data from normal operation.
- Criteria for determining that the issue has been resolved.
The firmware/menu table and two DDC script forms above follow the legacy source. Use the form supported by the actual controller and run supplementary DDC collection as directed by support. Keep the ending semicolon and choose an existing writable destination directory.