Pillar Axiom 300 Storage System
 
Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 

A couple of known bugs (Bug13755776  & Bug 13751405) with fsck logs for NAS Slammers can create a condition where it is not possible to gather meaningful logs from the Axiom array.

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Customer's will not know about this problem unless Support tells them the log bundles are not complete.
Created from <SR 3-6929740691>

Applies to:

Goal

Provide a workaround for Oracle support personnel to get a complete log bundle.

Solution

There are three possible solutions to this problem:

1. Use the clearlogs utility to clear the fsck logs from the slammer.  This option requires a Windows platform at the customer site to run the utility.
2. Download and use the supporttool utility to clear the fsck logs.
3. Use remote access (WebEx) to clear the problem manually.

Solution #1:

1. Download the latest version of the utility here.
2. Give the utility to the customer (preferred method is to attach it to My Oracle Support).
3. After unzipping the file, execute the utility with no options.
4. When prompted, enter the shared IP address of the Axiom pilots.
5. If applicable, have the customer gather and upload a new log bundle.

Solution #2:

1. Obtain a copy of the supporttool utility - see Pillar Axiom: How to download the SupportTool, AxiomCLI and pdscli command line utilities [ID 1510401.1].
2. Create an On Site FS task to have a Field Engineer go on site.
3. From a Windows platform, have him execute the supporttool utility as follows:
   
   C:\supporttool_040606.exe submit -H <shared IP address of Axiom> -u administrator -p pillar PerformClearLogs
   
   
4. If applicable, have the customer gather and upload a new log bundle.

Solution #3:

1. Establish WebEx session with customer and have the customer give you access to their desktop.
2. Using Pillar Axiom: How to Enable SSH Access on the Pilot(s) [ID 1431693.1], generate an SSH key and establish a connection to one of the pilots.
3. Determine the IP address of either of the NAS Slammer CUs:
   1. Run the ver command to display the IP addresses
   2. Run cat /etc/nodenames to see the association between the Slammer port WWN and the IP addresses.
   3. Compare the WWNs of the NAS Slammer from a log bundle to determine the proper IP addresses of the NAS Slammer.
4. ssh to either of the IP addresses of the NAS Slammer.
5. Change directory to the fscklog directory:  cd /mfs/255/pds/fscklogdir
   
   
   Note: depending on the history of this Axiom, the 255 directory may be a different number.
6. Running the command 'ls' in that directory and you should see a directory that is the WWN of this Slammer's CU.
7. Recursively remote the contents of that directory by running: rm -rf
8. Type exit twice to end the session.
9. If applicable, have the customer gather and upload a new log bundle.
   
   
   

References

This solution has no attachment