Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-1929473.1
Update Date:2018-01-16
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1929473.1 :   ILOM-8000-79 - ILOM Filesystem Capacity Limit Exceeded  


Related Items
  • SPARC M7-8
  •  
  • SPARC T7-4
  •  
  • Oracle SuperCluster M7 Hardware
  •  
  • SPARC M8-8
  •  
  • SPARC T7-2
  •  
  • Oracle SuperCluster M8 Hardware
  •  
  • SPARC M7-16
  •  
  • SPARC T7-1
  •  
  • Sun SPARCserver
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
  •  




In this Document
Purpose
Details
References


Applies to:

Sun Microsystems > Servers > x64 Servers
Sun SPARCserver
SPARC M7-8
SPARC M7-16
SPARC T7-1
Information in this document applies to any platform.

Purpose

 Provide additional information for message ID: ILOM-8000-79

Details

ILOM Filesystem Capacity Limit Exceeded

Type

Fault
  defect.ilom.fs.logging-misconfig

Severity

Minor

Description

Message ID: ILOM-8000-79 indicates that the ILOM fault manager has applied diagnosis
to error reports indicating the ILOM filesystem has exceeded capacity limits.

The ILOM health daemon (healthd) monitors the health of the service processor
by checking that required processes are running, filesystems are not exceeding capacity limits,
no memory leaks, no file descriptor leaks, or other SP related issues are occurring.

Tests for proper process behavior include Remtre Procedureal Calls (RPC) to the processes,
opening sockets, and communicating with the processes.
 
The Health Daemon can take the following actions:

 •Remove old files from the /var/log,  if the directory is nearly full.
 •Remove old files from /coredump,  if the directory is nearly full.
 •Reboot the Service processor (SP), if the SP is out of file descriptors.
 •Do a snapshot and reboot the SP, if the SP runs out of memory.
 •Restart a required process, if it's not working correctly.

Actions to take if the Health Daemon is unable to resolve problems.

1. Ensure that the log setting is not set to verbose mode.
2. Reset ILOM to factory defaults.
3. Reload ILOM image.
4. If problem persists, file a bug.

This fault will be automatically cleared when the ILOM filesystem capacity falls below the specified limit.

Automated Response

ILOM will attempt to remove older entries from the filesystem in order to make room for new entries.
The chassis wide service-required LED will be illuminated.

Impact

The service processor may be unable to continue logging incoming events if the filesystem remains near full.

Suggested Action for System Administrator

1. Ensure that the log setting is not set to verbose mode.

2. Reset ILOM to factory defaults.

3. Reload ILOM image.

If problem continues to persist, then contact Oracle Support.

Refer to the following document for the latest procedures for displaying event content in preparation

for submitting a service request and applying any post-repair actions that may be required.
PSH Procedural Article for ILOM-Based Diagnosis (Doc ID 1155200.1)

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback