Oracle FS1-2 Flash Storage System
 

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

Applies to:

Goal

 This document provides the details and required steps to setup Call-Home automatic log collection process for the FS1-2.

Solution

Background

Call-Home is a notification process that will automatically send FS1-2 System Logs to a secure Oracle server for analysis if a problem is detected.

There are four ways System Logs are generated:

• Periodic - gathered at a set interval
• Event - gathered automatically when a system problem is detected.
• Manual - gathered manually
• Test - gathered as part of a Call-Home test

Periodic and Event generated logs can be configured to automatically be sent to Oracle.  In the case of an event, this will reduce the time it takes to resolve an issue.  It may also be combined with Automatic Service Request (ASR) to further speed up the process.  See KM Document 1508403.1 Deactivation/Reactivation of ASR via My Oracle Support for more information.

Network Requirements:

• Switch ports set to auto-negotiation
• All Pilot IP addresses (Pilot1, Pilot2 and Public) must be allowed connections on Ports 53 (Domain Name Server or DNS), 443 (Oracle Call-Home server) and 8083 (FS1 Command Line Interface)
• Firewall(s) between the Pilots and the proxy must allow the TCP ports 53, 443 and 8083 for All Pilot IP addresses (Pilot1, Pilot2 and Public)
• DNS Access is required
• Proxy user/password usage is not supported

For more details about Call-Home process and Call-Home types please check FS System administration manuals at the Oracle Help Center (OHC).

The documentation for your system is also available on FS System web interface "Documentation" tab.

Call-Home Process

The Call-Home server fully qualified hostname is callhome.support.pillardata.com.  This hostname resolves to IP address 129.157.65.45.

The new DNS name will be callhome-pillar.oracle.com however it is not used at the moment. If a customer uses HTTPS and updates to the new DNS name, the transaction would fail as the security certificates are bound to callhome.support.pillardata.com

You can try to ping Call-Home server name on FS System pilot to make sure:

[root@pilot1 bin]# ping Call-Home.support.pillardata.com

If you cannot reach it via ping check DNS server configured correctly in /etc/resolv.conf [DO NOT edit this file]
    
There is no nslookup or host utility available on the pilots. However, you can invoke curl manually to make sure pilot can reach to Call-Home server:

[root@pilot1 ~]# curl -v -4 callhome.support.pillardata.com  

This will try to reach default port 80, but can confirm that it can resolve the Call-Home server host name. To reach port 443 you can try below command:

[root@pilot1 ~]# curl -v -4 callhome.support.pillardata.com:443

If there is proxy in configuration you should also give proxy server IP:

curl -v -x  <Proxy_server_IP:port> callhome.support.pillardata.com:443
Example:
[root@pilot1 ~]# curl -v -x  148.87.67.151:80 callhome.support.pillardata.com:443

Please check curl man page when you need help about curl options.

If there is a need to configure a firewall by IP address, be absolutely certain to check the DNS resolution for callhome.support.pillardata.com, verify that the IP is 129.157.65.45 and that the IP address is authorized on the firewall.

Check each of the DNS servers configured correctly to resolve Call-Home server address on your workstation:

Setup

1. Configure DNS Settings
   You should set the primary and secondary DNS to resolve email server and Call-Home server to the correct IP addresses. The DNS settings allow the FS System to send Call-Home configuration information and event notifications to designated email recipients.
   
   1. Navigate to System -> Global Settings -> Networking
   2. Select Actions -> Modify
      
      
      
      
   3. From the Interfaces tab, enter the Primary DNS Server IP address.
      
      
      
      
   4. Enter the Secondary DNS Server IP address.
   5. Click OK
      
      
2. Configure Call-Home for ASR
   Configure the Call-Home options to ensure that the Oracle FS System sends specific event notifications to My Oracle Support (MOS). MOS then receives these notifications and, if necessary, initiates a Service Request (SR).
1. Navigate to System -> Global Settings -> Networking
2. Select Actions -> Modify
   
   
   
   
3. Click the Notification tab
   
   
   
   
4. Select the Enable event triggered Call-Home option.
5. Select the Enable standard periodic Call-Home option. Accept the default daily periodic interval.
6. Select the Enable larger periodic Call-Home option. Accept the default weekly periodic interval.
7. Verify that the Use Oracle Server option is selected.
8. Accept the default settings for the Use Oracle Server option. Do not alter the server name of the HTTP Server address.
9. (Optional) Select Use Proxy and enter the proxy server address, port number, and protocol type as provided by your proxy administrator. Ensure that the proxy server, if used, resolves the host name of the Oracle server: callhome.support.pillardata.com.
10. Select Enable large file transfers.
11. Accept the default value for the Number of recent events to send in header option.
12. Click OK.
    NOTES:
    • In order for ASR to function properly, you must enable the standard periodic Call-Home option.  This is true no matter what the other options you enable in the Call-Home Triggering section.
    • If you deactivate Enable large file transfer, only the Call-Home header will be sent to Oracle. ASR will still be able to open service requests automatically however no troubleshooting data will be available and you will be required to send us the log files manually.
    • The SCP and local server option should only be used if instructed by Oracle support.
    • Proxies requiring login/password are not supported.
    
    
    
3. Test Call-Home
   To initiate test for Call-Home
   1. Navigate to System -> Global Settings -> Networking
   2. Select Actions -> Test Call-Home.
      
      
      
   3. Confirm that you want to send test Cal-Home information, and click OK
      
      
      The Call-Home test is an ASR activation request in MOS. MOS should receive your request in a few minutes, but no longer than 60 minutes and reply with an email with instructions to complete the process.
      
      
   4. Follow the instructions in that email from MOS to complete the ASR activation process. For more information on how to complete the activation process, refer to KM Document 1329200.1 How to Manage and Approve Pending ASR Assets in My Oracle Support.
      
      NOTE:  An “inactive” state means that MOS has not received the activation request. If you did not receive an email from MOS, or if the ASR asset in MOS is “inactive”, refer to KM Document 1503107.1 How to Troubleshoot ASR Management Software Auto Update Issues.
        
      
      
4. Display the Event Log and Details
   Review the event log to monitor events that have occurred in the Oracle FS System. If too many events display on the screen, you can filter the list of events.
1. Navigate to System -> Alerts and Events -> Event Log.
2. Review the event log details to ensure that the information is what you expect as shown in below figure.
   
   
   
   
5. View Log Bundle
   
   When an Oracle FS System system performs test Call-Home operation, the log bundle named as "test" will be recorded on system logs section. To make sure it is created please check system logs. A log bundle contains a number of system logs and is formatted as a TAR file, which you can download to your workstation. Oracle Customer Support might request that you collect the logs and send them to Oracle for analysis.
   
   Navigate to Support -> System Logs.
   
   
    
   
   
6. Steps via FSCLI for R6
   
   You can use the fscli command to enable and configure the CallHome settings for the types of Call-Home bundles such as a large file, as well as primary and secondary periodic log collections.
   1. Use fscli to Login with an administrator account
      
      $ fscli login -u administrator -oracleFS <FS System name or IP address>
       
   2. Get help about command
      
      $ fscli call_home -help
       
   3. Display a list of all the Call-Home settings and Matrix information that exists on the Oracle FS System.
      
      $ fscli call_home -list
       
   4. If you think it is required then reset the CallHome options to the default values.
      
      $ fscli call_home -reset
       
   5. Enable Call-Home with desired parameters  
      
      $ fscli call_home -modify -callHomeDestination callhome.support.pillardata.com -enableEventTrigger -enableLargeFile -enableStandardPeriodic  -enableLargerPeriodic  -schedulePeriodic standard -interval weekly -frequency 2 -startTime 2015-01-01
       
   6. Check status after setting the values
      
      $ fscli call_home -list
       
   7. Tests the Call-Home feature to verify that Call-Home is correctly configured.
      
      $ fscli call_home -test
       

G. Scripted version of the procedure

The manual procedure displayed above can be performed via the script FS_ASR_check attached to this document:

• Log on the pilot
• scp the script in /var/tmp
• chmod +x FS_ASR_check.sh
• ./FS_ASR_check.sh

The script will go through the steps:

• check the call-home settings
• check if the server can be pinged
• test the connectivity with/without proxy
• send a test call-home.

Any error or failure will be reported in FS_ASR_check.log

References

This solution has no attachment