IBM TotalStorage SAN Storage Data Gathering
Abstract This TIP discusses IBM TotalStorage SAN Storage data gathering.
Contents SAN event data gathering tips
The purpose of this TIP is to outline the basic information that needs to be collected to assist in resolving SAN storage device related problems. You might find it daunting to go through several steps to gather all the data requested, but the most common cause of delays in problem resolution is a lack of data. You should never assume that the root cause of any problem is in the most obvious place. By gathering logs from all parts of the SAN, you give yourself the greatest chance of getting a fast and effective resolution to the problem. The second most common cause of delays in problem resolution is providing data that has been collected some hours or even days after the problem occurred. Often in this case, there is no longer evidence of the original problem. Timely and complete data collection will aid in problems being resolved quickly. Collection of timely and detailed information for IBM TotalStorage devices are outlined in the following sections. The collection of log information is critical to understanding the cause of an event in a SAN environment, and to aid support in analyzing the collected logs. It is also useful to provide the time offsets for individual equipment. As some hardware may have never had its real time clock set to the local time, it can become very difficult to match events from one piece of equipment to the other. Another important piece of information to aid in timely error analysis is a physical diagram of the SAN topology. This diagram should be kept up to date, and include all hosts, switches, directors, and storage devices within the SAN. This document can save countless hours of reconstructing the original picture by piecing together log information.
IBM TotalStorage DS Family disk subsystem
Time difference Time is usually synchronized with the Storage Manager PC. To display and alter the time from the Storage Manager GUI go to Storage Subsystem —> Set Controller Clock. The time displayed is the current IBM TotalStorage DS Family (formerly FAStT) controller time. Take a note of that time delta before altering it. Note: Storage Manager 8.4 has enhancements to better manage the Controller Clock. Log collection This procedure will save what is known as the MEL logs. Start the Storage Manager software and connect to the IBM TotalStorage DS Family (formerly FAStT) controller. From the Subsystem Management window of each IBM TotalStorage DS Family (formerly FAStT) involved, click on the second icon from the left that looks like an open book. This event log view may also be accessed by clicking the View —> View Event Log in the Subsystem Management window. From the Event Log window select the Save All sections button, navigate to the appropriate path, type filename and then Save. Save as many events as possible. Hardware configuration collection To provide support and understanding of the physical layout of the IBM TotalStorage DS Family (formerly FAStT), we want to collect what is known as a Profile. Open the FAStT Storage Manager Client. Double-click the target storage subsystem in the right pane to launch the "Storage subsystem" window. Select View —> Storage Subsystem Profile Select the Save As button to open the dialog box for a location and filename to save the profile to a file. Attention: If the choice to save All sections is offered — do so; navigate to the appropriate path, type a filename and then Save.
IBM TotalStorage Enterprise Storage Server
When an IBM TotalStorage Enterprise Storage Server™ is involved in the SAN configuration that experienced problems, a service call to IBM should be placed to allow remote technical support, or an onsite service representative to collect the relevant logs and statesaves as soon as possible after the event occurred.
3583 Tape Library and SAN Data Gateway Module (SDGM)
Time difference 3583 Library The libraries date and time may be viewed and set from the front panel. Refer to the 3583 Setup and Operator Guide for Multi-Path Libraries. 3583 SDGM If your 3583 tape library has an embedded SAN Data Gateway Module (SDGM) installed, connect to the SDGM serial port and issue the date command to display the date and time. Most SDGMs have never been set to the local time as it does not affect operation. We suggest, while connected, to follow this procedure to set it correctly: Use the rtcDateSet command to manually set the Real Time Clock (RTC) using the following Syntax : rtcDateSet [year],[month],[dayofmonth],[dayofweek],[hour],[minute],[second] This is how to set the date and time to Friday 26th of January 2004 at 9:30 AM SN60023 > rtcDateSet 2004,1,26,5,9,30,00 Note: The time is in 24 hour format. Then use the dateSetFromRTC command to set the gateways RTC as the source of date display: SN60023 > dateSetFromRTC Then we issue the date command to confirm our setting. SN60023 > date SN60023 > FRI JAN 26 9:30:49 2004 Log Collection 3583 Library The IBM TotalStorage Ultrium Scalable Tape Library 3583 Maintenance Information, SA37-0425 manual contains a section on Methods of Capturing Logs. Follow the procedures and ensure all the boot logs are collected. 3583 SGDM Connect via the serial port to the SDGM and enable session logging on your terminal emulator. Issue the command supportDump. Attention: This command will briefly disrupt data flow through the SDGM, we recommend to wait until there is no tape activity before issuing it.