Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 

In this Document

Purpose

Scope

Details

Overview

Log Bundle Filenames

Log Bundle Contents

Where to look for Log Bundles

References

Applies to:

Purpose

This document explains how to identify specific log bundles based on information about date/time and events contained in the log bundle filename as well as what data is collected based on options selected.

Scope

With the details of this document, customers and Oracle support personnel will be able to quickly find log bundles that are pertinent to a specific issue as well as select what options are needed to gather the proper internal logs.

Details

Overview

Log bundles are a collection of various internal logs and diagnostic information from the individual components (Pilot, Controller or Drive Enclosure) within the FS1-2.  To avoid using up the disk space on the Pilots, the FS1-2 is designed to minimize the size of these internal logs and diagnostic data.  To accomplish this, once an internal log or diagnostic data is gathered as part of a log bundle, it is deleted from the system. As of R6.2.11 and higher, after an Event driven log is created, the system will not create another Event driven log bundle for 15 minutes.

For complex issues Oracle Support may request multiple log bundles covering a period of time.  Performance related issues may also require that performance statistics and or trace logs.  As such, identifying the proper log bundles is crucial to getting the necessary information to Oracle support for a quick resolution.

Log Bundle Filenames

Using the name of the log bundle it is possible to distill critical information about its contents.  The log bundle filename consists of:

1. The FS1-2 System Serial number
2. A timestamp (YYMMDDHHMMSS) marking the date/time on how far back the logs were gathered in this log bundle.
3. A timestamp (YYMMDDHHMMSS) marking the date/time on the end of the logs in this log bundle.
4. A description on what prompted the log bundle to be gathered.
5. Collection type:
   • e = Event driven, the FS1-2 experienced an event
   • p = Periodic driven, logs collected on a regular interval
   • m = Manual driven, logs collected in response to a manual request
   • t = Test driven, logs collected for testing the Call-Home function
      
6. Number in a sequence for this incident.

An example of a log bundle filename is A001365XXX-180221003140-180221004307-ENCLOSURE_DRIVE_STATE_CHANGE-e-02-02.tar. The information in this filename is as follows:

• A001365XXX = FS System serial number
• 18 02 21 00 31 40 = this log bundle will have logs dating back to February 21, 2018 at 12:31:40 am
• 18 02 21 00 43 07 = this log bundle will have logs up to February 21, 2018 at 12:43:07 am
• ENCLOSURE_DRIVE_STATE_CHANGE = the reason this log bundle was gathered was due to an
• e = this log bundle was event driven
• 02-02 = this is the second in the sequence (01-02 is of little use as it does not contain any internal logs)

Log Bundle Contents

What the contents of a Log bundle contain depends a lot on the Collection type. 

• There are certain options that can be configured for Event and Periodic collections:
  
  • The Flash Storage Command Line Interface (fscli) has the following options:
    
    fscli call_home -modify
        Updates the Call-Home settings.
    
    SYNOPSIS
         call_home -modify
            [{-enableEventTrigger |-disableEventTrigger}]
            [{-enableLargeFile | -disableLargeFile}]
            [{-enableStandardPeriodic | -disableStandardPeriodic}]
            [{-enableLargerPeriodic | -disableLargerPeriodic}]
            [-numberOfEvents number-of-events-to-include]
            [{ -callHomeDestination https-server_ip_or_dns
                  [{-proxy
                     -proxyIp proxy_ip
                     -proxyPort proxy_port
                     -proxyConnection {http | socks4 | socks5}
                     [{-enableAuthentication -proxyUsername proxy-username
                      | -noEnableAuthentication}]
                  | -noProxy}]
             | -localDestination local_server_ip_or_dns
               -directory local_directory
               -userName user_name
            }]
            [ -schedulePeriodic {standard | large}
              -interval { daily | weekly | monthly}
              -frequency interval_frequency
              -startTime date-time
            ]
    
            [{-sessionKey | -u admin-user -oracleFS oracle-fs-system}]
            [{-outputformat | -o} { text | xml }]
            [{-timeout timeout-in-seconds | -verify | -usage | -example | -help}]
    
     
  • Using the Oracle FS System Manager GUI, under System tab, Global Settings, Networking, Actions -> Modify, a pop-up window will appear.  Selecting the Notifications tab provides the following options:
    
     
    
    • Enable event triggered Call-Home will send Event driven log bundle collections with diagnostic information to Oracle's Call-Home server.
    • Enable Standard periodic Call-Home will send Periodic log bundles to the Call-Home server based on the options below it.  Log bundles will contain general configuration information but no internal logs from components.
    • Enable large periodic Call-Home will send do the same as standard but will also include trace logs and performance statistics.
    • Enable large file transfers (include log files in Call-Home) will send trace logs and performance statistics with any Event driven log bundle sent to the Call-Home server.
       
• When a Manual log bundle is gathered, the contents are determined by the options selected. 
  
  NOTE: Manual logs only have one number in their sequence (1-1)
  
   
  
  • When using the Command Line Interface (fscli) various options can be used to gather specific data:
    
    fscli system_log -collect
           { -all
            |[-eventLog]
             [-statistics]
             [-systemConfig]
             [-pilot]
             [-sanhostLogs]
             [-controllerBackup]
             [-controllerInMemory]
             [-controllerLogs]
             [-replicationAppliance]
             [-client]
             [-enclosureLogs]
         }
           [-controller controller-id-or-fqn [, controller-id-or-fqn ]... ]
           [-enclosure enclosure-id-or-fqn [, enclosure-id-or-fqn]... ]
           [-sanhost sanhost-id-or-fqn [, sanhost-id-or-fqn]... ]
           [-sendToCallHome
                 [{ -logBundle log-bundle-id-or-fqn [,log-bundle-id-or-fqn]...
                 | -previousBundles time-frame {minutes | hours | days}
                 }]
           ]
           [-withinLastHours number-of-hours ]
           [-collectionReason reason-description ]
           [-uploadClientLogsFirst]
    
        [{-sessionKey | -u admin-user -oracleFS oracle-fs-system}]
        [{-outputformat | -o} { text | xml }]
        [{-timeout timeout-in-seconds | -verify | -usage | -example | -help}]
    
     
  • If gathering a log bundle using the GUI (Support tab, System Logs, Actions -> Create), a pop-up window appears to select what data is gathered:
     
     
    • Component or Item allows the selection of what internal logs etc will be gathered.
    • There are also options to Send to Call-Home server when the collection is completed or download it locally. 
    • The Collection Period has two options: 
      • Restrict the internal log collection period in hours or days.  Selecting a longer period will NOT
      • All internal logs since the previous log collection.
        
        NOTE: selecting a longer time period will NOT collect internal logs that were gathered in previous log bundles.  That data will only be found in the log bundle in which it was gathered at that time.
        
          
    • SAN Host Log Selection allows for the collection of Flash Storage Path Manager (FSPM) logs from up to 10 SAN hosts.  FSPM must be installed to gather this information.
    • The Notes box can be used to attach a manually gathered log bundle to a Service Request (SR).  See KM Document 1943289.1 FS System: How to Gather and Attach a Manual Log Bundle to an Existing MOS Service Request for more information.

Where to look for Log Bundles

In the Oracle FS System Manager GUI log bundles can be found under the Support tab and System Logs:

The fscli command line can generate a similar list:

For Oracle Support engineers

As of R6.2.11, a list of log bundles can be found at the end of the *chsh.xml file in a log bundle by searching on "GetLogBundlesResponse":

References

This solution has no attachment