Pillar Axiom: Howto Avoid a Component Requested Callhome generated on fsck completion

Asset ID:	1-72-2060338.1
Update Date:	2018-01-08
Keywords:

Solution Type Problem Resolution Sure

Solution 2060338.1 : Pillar Axiom: Howto Avoid a Component Requested Callhome generated on fsck completion

Applies to:

Pillar Axiom 600 Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

On completion of a file system consistency check (fsck), a callhome of type 'Component Requested Callhome' will be raised and sent to Oracle support.

Cause

This is normal action when the filesystem state changes (back to online) at the completion of the fsck.

Solution

No action is required under normal 'consistent' completion of the fsck , the filesystem returning online.

Event log entries similar to the following will identify if a successful fsck generated a callhome to Oracle.

Example events from performing fsck

From a scanlog'd bundle, the events_summary_all.txt will look similar to the following:-

2015-09-25T16:02:55-07:00 TaskStarted                               INFORMATIONAL
2015-09-25T16:03:03-07:00 FileSystemCheckProgress                   INFORMATIONAL
2015-09-25T16:03:04-07:00 FileSystemCheckProgress                   INFORMATIONAL
2015-09-25T16:03:13-07:00 FileSystemCheckProgress                   INFORMATIONAL
2015-09-25T16:03:39-07:00 FileSystemCheckProgress                   INFORMATIONAL
2015-09-25T16:03:39-07:00 FileSystemCheckProgress                   INFORMATIONAL
2015-09-25T16:03:41-07:00 FileSystemCheckProgress                   INFORMATIONAL
2015-09-25T16:03:43-07:00 FileSystemConsistent                      INFORMATIONAL
2015-09-25T16:03:43-07:00 ComponentRequestedCallhome                ERROR

within events_detail_all.txt we see the fsck result and resulting callhome generation.

2015-09-25T16:03:43-07:00 FileSystemConsistent                      INFORMATIONAL
EventGuid                                                    = ID12345678-1234-1234-1234-123456789abc
InternalEventCode                                            = 0x90008
ReportingControlUnit_SlammerName                             = Slammer1
ReportingControlUnit_SlammerID                               = ID12345678-1234-1234-1234-123456789abc
ReportingControlUnit_SlammerFQN                              = /Slammer1
ReportingControlUnit_ControlUnitNumber                       = 1
ReportingControlUnit_ServiceType                             = NAS
Parameter_ReportingControlUnitWWN                            = 2009000b08012345
Parameter_RawEventContents                                   = 00000000574300000000000000000000000000002079E111
Parameter_FileSystemFQN                                      = /pillar/storage
Parameter_FileSystemID                                       = ID12345678-1234-1234-a329-123456789abc
Parameter_FileSystemName                                     = storix
Parameter_FileServerFQN                                      = /pillar

2015-09-25T16:03:43-07:00 ComponentRequestedCallhome                ERROR
EventGuid                                                    = ID12345678-1234-1234-1234-123456789abd
InternalEventCode                                            = 0x10016
ReportingControlUnit_SlammerName                             = Slammer1
ReportingControlUnit_SlammerID                               = ID12345678-1234-1234-1234-123456789abc
ReportingControlUnit_SlammerFQN                              = /Slammer1
ReportingControlUnit_ControlUnitNumber                       = 1
ReportingControlUnit_ServiceType                             = NAS
Parameter_ReportingControlUnitWWN                            = 2009000b08012345
Parameter_ControlUnitWWN                                     = 2009000b08012345
Parameter_Data                                               = FSCK 12345 completed successfully, status

To eliminate the callhome being sent to Oracle and an auto service request (ASR) being created, callhome can be disabled for the duration of the fsck. Please remember to re-enable when completed if required.

For details of how to temporarily disable callhome please refer to Pillar Axiom: How to Disable Call Home to Prevent Automatic Service Request ASR Generation (Doc ID 1535352.1)

References

<NOTE:1535352.1> - Pillar Axiom: How to Disable Call Home to Prevent Automatic Service Request ASR Generation

Attachments

This solution has no attachment