Table of Contents

HMC Problem determination

No more space

Filesystem / is full

Web services are no more responding

Command to check:

monhmc -r disk

This command can free up space in the following file systems: /var, /var/hsc/log, /dump, /extra, /data, and /.

Remove temporary HMC files which have not been modified during the last day (24 hours) from all file systems:

[hmc@hscroot]~> chhmcfs -o f -d 1

Remove all temporary HMC files from all file systems:

[hmc@hscroot]~> chhmcfs -o f -d 0

Remove temporary HMC files which have not been modified during the last 36 hours from the /var file system:

[hmc@hscroot]~> chhmcfs -o f -h 36 -f /var

Remove temporary HMC files from the /dump file system to free up to 100 MB:

[hmc@hscroot]~> chhmcfs -o f -s 100 -f /dump

Remove an HMC from a Power server

If the HMC is still active, you can right click on the power and remove the connection.

Else if no access to the HMC, go into the ASM web interface

https://<ip_port_hmc1or2_of_power>

Entrer as : admin on left panel –> System Configuration –> Hardware Management Console

Here you can remove an HMC

Power servers partitions corrupt

Save Area Version Mismatch

The FSM and HMC management consoles use a storage area (also called the save area ) on each managed server or node to persist the server configuration; primarily PowerVM settings and partition profiles. As new functions are introduced, the format (or version) of the save area is changed. The format of the file is upward compatible only. If you connect for example an HMC using an older code than the latest connected, you will corrupt the “save area”.

Recovering with Initialize Profile data

The recovery is to perform a profile initialize and re-create or restore the profile configuration.

1. Power off all partitions.

2. Log into Advanced System Manager (ASM).

a. On the Host select Operations > Launch Advanced System Manager (ASM).
b. Log into ASM.

3. Power off the server.

Click Power/Restart Control > Power On/Off System . Click Save Settings and Power off .

4. Set server firmware start policy to Standby.

Click Power/Restart Control > Power On/Off System . Set Server firmware start policy to Standby 
(User-Initiated) . Click Save Settings .

5. Reset the server firmware settings.

Click System Service Aids > Factory Configuration Select Reset the server firmware settings
This operation may take several minutes. When the task completes the node access will change to 
OK and the state to powered off.

6. Power on to standby.

In ASM, click Power/Restart Control > Power On/Off System . Click Save Settings and Power on.

7. Re-create the partitions.

The user can re-create the partition configuration or restore the profile configuration from a 
backup created created prior to the damage. 
To restore an older backup, use the FSM Host task 
System Configuration > Manage Virtual Server Data > Restore 

Or to restore an older backup, use the HMC to reinitialize or restore partitioning backup

Change from HMC to non-HMC

Be patient ! Not too fast else it will failed

Note: Currently, no HMCs are connected but the server is in a partitioned state.

First connect to the ASMI (Advanced System Management Interface), web interface connected to Power HMC port

--> System Information --> Real-time Progress Indicator

To permanently change the state to non-HMC-managed:

1) The server must be powered off.
2) Go to System **Service Aids**, click on **Factory Configuration**, then click on **Reset server firmware** settings option.
3) Go to System Configuration, click on Hardware Management Consoles, then click on Reset the server to a non-HMC managed configuration option (if an HMC is available).

The server will have a default partition defined that owns all the system resources.
The default partition type is defined by the default partition environment setting.

To view this setting, go to Power/Restart Control, click on Power On/Off System, then click on the Default Partition Environment option.