Sun Storage 2540 Array
 
Sun Storage 2510 Array
 
Sun Storage 2540-M2 Array
 
Sun Storage 6780 Array
 
Sun Storage 6180 Array
 
Sun Storage 6130 Array
 
Sun Storage 2530 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage J4400 Array
 
Sun Storage J4500 Array
 
Sun Flash F5100 Array
 
Sun Storage J4200 Array
 
Sun Storage 6140 Array
 
Sun Storage 6540 Array
 
Sun Storage 6580 Array
 

PLA-Support>Sun Systems>DISK>Arrays>SN-DK: 6140_6180
 

In this Document

Goal

Solution

Collect host data, and supportdata for all arrays

Collect host data, and supportdata for a specific array type

Collect host data only, and no supportdata

References

Created from <SR 3-5882838661>

Applies to:

Goal

The Oracle Services Tools Bundle (STB) provides a suite of data gathering utilities for Oracle hardware products. With the release of STB 8.0.4, the Oracle Explorer Data Collector component of STB will now collect a supportdata for all the legacy Sun Storage Arrays. Both an Explorer from the server and a supportdata from all registered arrays can be gathered with just one simple command. This document explains how to use Explorer to collect this information.

Solution

To collect array supportdata when running Explorer, Sun Storage Common Array Manager (CAM) must be installed on the host that is running Explorer.  This is because Explorer uses commands when gathering array supportdata that are only available when CAM is installed. Also, Explorer will only collect supportdata for arrays that are registered in CAM.

While it may be tempting to consider installing CAM on multiple servers, this is not a best practice. The best practice is to identify a single host to serve as the CAM management station. To collect diagnostic data for other hosts attached to Sun Storage Arrays, there are two options. Depending on your configuration and the nature of the problem, one option may be more convenient than the other.

• Run Explorer on the CAM host, which will collect data for that host and also for all registered arrays. Then run Explorer on the host experiencing the problem. This will produce two Explorer files to provide to Oracle technical support.

• On the CAM host, use CAM to collect supportdata for one or more arrays. Then run Explorer on the host experiencing the problem. This will result in a single Explorer for the problem host, and one supportdata file for each array.

When running Explorer on a host configured with CAM, you can:

• Collect host data, and supportdata for all arrays.
• Collect host data, and supportdata for a specific array type.
• Collect host data only, and no supportdata.

Explorer uses the CAM command /opt/SUNWsefms/bin/ras_admin to determine which arrays to collect data for. In this example, there are 12 arrays registered with this installation of CAM.

Note the array Type in the above output. Explorer contains two modules which will collect data for a specific array type. Each module will collect a separate supportdata file for each array associated with the module type. You can specify which module type Explorer should use, but you cannot specify an individual array.

• The st25xx module will collect a supportdata for any array of type 2510, 2540, 2530, 2540m2, 2530m2, j4200, j4400, j4500, and f5100.
  
  
• The se61xx module will collect a supportdata for any array of type 6130, 6140, 6180, 6540, 6580, and 6780.

Collect host data, and supportdata for all arrays

When Explorer is run without any options, all the default modules are run, including st25xx and se61xx. In the case where both server and array data are required, Explorer can collect all data in a single command.

Collect host data, and supportdata for a specific array type

In the example below, supportdata is collected for all arrays whose type is associated with the st25xx module.

 

In this next example, supportdata is collected for all arrays whose type is associated with the se6100 module.

Collect host data only, and no supportdata

In this final example, Explorer is instructed not to collect array information. This can be done when there is a specific problem on the server unrelated to the storage.

References

This solution has no attachment