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-72-2211740.1
Update Date:2018-05-01
Keywords:

Solution Type  Problem Resolution Sure

Solution  2211740.1 :   Failing to add a new host config to SP using ldm add-config command  


Related Items
  • Netra SPARC T4-2 Server
  •  
  • SPARC T4-1
  •  
  • Netra SPARC T4-1 Server
  •  
  • SPARC T3-4
  •  
  • SPARC T8-1
  •  
  • SPARC T7-2
  •  
  • Netra SPARC T3-1B
  •  
  • SPARC T3-1B
  •  
  • Netra SPARC S7-2
  •  
  • SPARC T5-4
  •  
  • SPARC T3-2
  •  
  • SPARC T8-4
  •  
  • SPARC T5-2
  •  
  • SPARC T8-2
  •  
  • SPARC T7-4
  •  
  • SPARC S7-2L
  •  
  • SPARC T5-8
  •  
  • SPARC T7-1
  •  
  • SPARC T3-1
  •  
  • SPARC T4-2
  •  
  • SPARC S7-2
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>CMT>SN-SPARC: T5
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-13728614781>

Applies to:

Netra SPARC T3-1B - Version All Versions to All Versions [Release All Releases]
SPARC T4-1 - Version All Versions to All Versions [Release All Releases]
Netra SPARC T4-1 Server - Version All Versions to All Versions [Release All Releases]
SPARC T4-2 - Version All Versions to All Versions [Release All Releases]
Netra SPARC T4-2 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

LDOM admin not able to save new host config to Service Processor using "ldm add-config" command.

Error message states the System Controller ran out of memory :

root@myhost # ldm add-config myhost_new_config
Error: Operation failed because the system controller
ran out of memory. Before being able to save a new configuration,
one or more of the existing ones must be deleted

 

 

Cause

The process of saving config to SP has run out of space in host data flash (the HFFS on the MB rather than space on the SP). This can occur when storing a large number of Oracle VM profiles, or where using large and complex Oracle VM configurations.

After collecting a snapshot, one can confirm the corresponding warning messages reported by the Guest Manager (GM):


bash$ > egrep md_store_ds.c ./ilom/traces/@coredump@sp_trace@logs@GM.log

GM WARN 2016-11-28 14:42:54.721675 1436 md_store_ds.c:968 Not enough space to save MD set myhost_new_config.
GM 41 2016-11-28 14:42:54.729616 1436 md_store_ds.c:970 Required 5244396 bytes - available 4851761 bytes.
GM WARN 2016-11-29 07:36:11.543126 1436 md_store_ds.c:968 Not enough space to save MD set myhost_new_config.
GM 41 2016-11-29 07:36:11.544209 1436 md_store_ds.c:970 Required 5244400 bytes - available 4851761 bytes.
GM WARN 2016-12-05 14:52:37.346215 1436 md_store_ds.c:968 Not enough space to save MD set myhost_new_config.
GM 41 2016-12-05 14:52:37.349868 1436 md_store_ds.c:970 Required 5237654 bytes - available 4851761 bytes.

 

Solution

In order to resolve/workaround this condition, is to delete previous existing configuration(s) before saving the new spconfig.

List existing configs:

# ldm list-spconfig

Choose one or more previous existing config(s) no longer necessary and remove it/them to make room to new config:

# ldm remove-spconfig <config-name>

Save the new config:

# ldm add-spconfig <config-name>

Notice - for very large LDom configuration environments, a unique spconfig profile may take more than 50% of the available Host Data Flash storage space, triggering the error message. So the LDom admin will have to remove it before creating a new one.

References

<NOTE:1464421.1> - Configuration, Save & Restore Setup and Troubleshooting of Oracle VM Server for SPARC (LDom)

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