Sun Storage Flexline 280 Array
 
Sun Storage Common Array Manager (CAM)
 
Sun Storage 2540-M2 Array
 
Sun Storage J4400 Array
 
Sun Storage 2510 Array
 
Sun Storage J4500 Array
 
Sun Storage 2540 Array
 
Sun Storage 6140 Array
 
Sun Flash F5100 Array
 
Sun Storage 6180 Array
 
Sun Storage 6780 Array
 
Sun Storage 2530 Array
 
Sun Storage 2530-M2 Array
 
Sun Storage Flexline 380 Array
 
Sun Storage J4200 Array
 
Sun Storage 6540 Array
 
Sun Storage 6130 Array
 
Sun Storage Flexline 240 Array
 
Sun Storage 6580 Array
 

PLA-Support>Sun Systems>DISK>Disk Software>SN-DK: CAM
 
_Old GCS Categories>Sun Microsystems>Storage Software>Modular Disk Device Software
 

Applies to:

Goal

Sun Storage Common Array Manager (CAM) has the ability to collect support-based configuration and logs for Sun Storage 2500, 2500-M2, J4000, F5100, 6000 and Flexline Arrays. This can be performed using the Browser or CLI interface. The purpose of this document is to describe how to collect this information.

If you are using a Sun Storage J4000 JBOD Array as part of a Sun Storage 7000 Unified Storage System, you do not manage the array using CAM. Instead, you use the management software provided with the Unified Storage System. Please refer to J4200/J4400 Array System Overview.

Solution

Before gathering array support data, please confirm the array is not affected by any of the following known Alerts :

• <Document 1019002.1> Collecting Support Data On Certain Arrays May Cause One or Both Array Controllers to Reboot
• <Document 1021045.1> During "supportdata" Collection Sun Storage Arrays May Experience Loss of Data Access
• <Document 1000797.1> "Support Data Collection" Procedure on Certain Sun StorEdge and Sun StorageTek Arrays May Cause SATA Drive Failures
• <Document 1019006.1> Collecting Support Data Using Common Array Manager while Drives are Bypassed May Cause Controllers to Reboot

Using the CAM Browser-based Service Advisor

The Service Advisor is opened via a button in the top right-hand corner.

1. Select an Array in the left pane.

2. Click on the Service Advisor button, which will launch a new window.

Example :



3. Go to the "Array Troubleshooting and Recovery" section in the left pane, and select "Collecting Support Data."

Example :



4. Follow the step-by-step instructions it then displays in the right pane. The first step, "Reserve the tray for maintenance," does not affect data access to the array. It only prevents other administrative actions in CAM from being run simultaneously.

5. The result will be a ZIP or GZ archive on the CAM management host. In the latest CAM releases (6.x) the supportdata file can be downloaded onto the machine where the browser is launched to access CAM, but in previous releases you will have to download it directly from the CAM management host under /tmp.

Collecting Data via CLI

This requires the use of the ras_admin and supportData utilities. Both utilities are located on the management host in the same directory, which is specific to the operating system where the CAM software is installed.

Solaris: /opt/SUNWsefms/bin/
Linux:  /opt/sun/cam/private/fms/bin/
Windows with CAM 5.0.2 or earlier:  C:\Program Files\Sun_Microsystems\StorageTek_Mgmt\Component\fms\bin\
Windows with CAM 5.1 or later:  C:\Program Files\Sun\Common Array Manager\Component\fms\bin\

1.  Get the array detail from ras_admin device_list:

Example :

# ./ras_admin device_list
Monitored On     Device          Type IP Address  Unique Identifier Active ASR
---------------- --------------- ---- ----------- ----------------- ------ ---
camhost          arrayname       6540 <controller IP> <WWN>          Y      Y   
#

2. Use the supportData utility to collect the array data:

supportData -d <identifier> -p <path> -o <filename>

where:

<identifier> is either the:

<deviceKey> for the internal Array Serial Number or
<array-name> for the Name of the Array assigned in Configuration Service or
<ip-number> for the ip address of either the A or B controller or
<ip-name>  for the fully qualified DNS name of either the A or B controller.

<path> is the location where you want the output written, e.g. /tmp.

<filename>is the output file to be created.

Example :

# ./supportData -d arrayname -p /tmp -o myarray.support

 

Do you still have questions?  You can use My Oracle Support Communities.  Communities put you in touch with industry professionals like yourself.  They are monitored by Oracle support engineers, so you can expect reliable and correct answers.  Ask questions and see what others are asking about in the Disk Storage 2000, 3000, 6000 RAID Arrays & JBODs Community.

 

 

References

This solution has no attachment