IBM Support

PowerVM/VIOS How to fix "The RMC has a status code of busy. One reason for this can be the incorrect sizing of the VIOS."

How To


Summary

Fixing RMC busy status in PowerVC and PowerVM/VIOS environments.

Objective

Fixing RMC busy status in PowerVC and PowerVM/VIOS environments.

Environment

PowerVC
PowerVM/VIOS

Steps

The following steps are only to be followed after checking;

To refresh cmdb, run the following commands as oem, no reboot is required;

# /usr/bin/stopsrc -s vio_daemon
#lssrc -a |grep vio_daemon --> make sure it is inoperative
# /usr/sbin/slibclean
# rm -rf /home/ios/CM
# /usr/bin/startsrc -s vio_daemon -a '-d 4'
#lssrc -a |grep vio_daemon --> make sure it is Active and note down the PID
Then we need to execute a kill -1 vio_daemon's PID to start the populate of the DB

  • If the issue persists after checking the above, then we need to reset and cleanup the CM, the following steps do not require downtime but it is recommended to run them during a quiet window, as there might be a brief temporary loss of manageability, also please make sure other VIO servers are up and running while working on this VIOS;

  • 1. Prepare log directory

rm -R /tmp/CMreset 2>/dev/null

mkdir /tmp/CMreset

echo "Saving logs in: /tmp/CMreset/CMcleanup.history.log" >> /tmp/CMreset/CMcleanup.history.log

  • 2. Log hostname and current CM processes

echo "====== locate hostname ======" >> /tmp/CMreset/CMcleanup.history.log

host `hostname` >> /tmp/CMreset/CMcleanup.history.log

echo "======" >> /tmp/CMreset/CMcleanup.history.log

date >> /tmp/CMreset/CMcleanup.history.log

echo "====== ps -ef of CM before cleanup starting ======" >> /tmp/CMreset/CMcleanup.history.log

ps -ef | grep CM >> /tmp/CMreset/CMcleanup.history.log

  • 3. Restart inetd

stopsrc -s inetd

startsrc -s inetd

sleep 10

  • 4. Stop vio_daemon

stopsrc -s vio_daemon

  • 5. Force kill vio_daemon if still running

pid=$(ps -ef | grep -v grep | grep vio_daemon | awk '{print $2}')

if [ -n "$pid" ]; then

    kill -9 $pid

fi

  • 6. Remove CMDB directories

rm -R /var/vio/CM 2>/dev/null

rm -R /home/ios/CM 2>/dev/null

  • 7. Clear library cache

slibclean

  • 8. Restart vio_daemon

startsrc -s vio_daemon

sleep 60

  • 9. Log post-cleanup info

echo "======" >> /tmp/CMreset/CMcleanup.history.log

date >> /tmp/CMreset/CMcleanup.history.log

echo "======  ps -ef of CM after cleanup completed ======" >> /tmp/CMreset/CMcleanup.history.log

ps -ef | grep CM >> /tmp/CMreset/CMcleanup.history.log

echo "====== listing files in /home/ios/CM/DB after cleanup ======" >> /tmp/CMreset/CMcleanup.history.log

ls -ltrb /home/ios/CM/DB >> /tmp/CMreset/CMcleanup.history.log

sleep 180

echo "====== listing files in /home/ios/CM/DB after 180 seconds ======" >> /tmp/CMreset/CMcleanup.history.log

ls -ltrb /home/ios/CM/DB >> /tmp/CMreset/CMcleanup.history.log

echo "====== Last few lines from viod_CM.log after cleanup ======" >> /tmp/CMreset/CMcleanup.history.log

tail -n 60 /home/ios/logs/viod_CM.log >> /tmp/CMreset/CMcleanup.history.log

  • 10. Signal vio_daemon to reload

pid=$(ps -ef | grep -v grep | grep vio_daemon | awk '{print $2}')

if [ -n "$pid" ]; then

    kill -1 $pid

fi

Additional Information

SUPPORT

If you require more assistance, use the following step-by-step instructions to contact IBM to open a case for software with an active and valid support contract.  

1. Document (or collect screen captures of) all symptoms, errors, and messages related to your issue.

2. Capture any logs or data relevant to the situation.

3. Contact IBM to open a case:

   -For electronic support, see the IBM Support Community:
     https://www.ibm.com/mysupport
   -If you require telephone support, see the web page:
      https://www.ibm.com/planetwide/

4. Provide a clear, concise description of the issue.

 - For more information, see: Working with IBM AIX Support: Describing the problem.

5. If the system is accessible, collect a system snap, and upload all of the details and data for your case.

 - For more information, see: Working with IBM AIX Support: Collecting snap data

Click here to submit feedback for this document.
 
Author: Ahmed Deif

Document Location

Worldwide

Operating System

Power:All operating systems listed

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSPHKW","label":"PowerVM Virtual I\/O Server"},"ARM Category":[{"code":"a8m0z0000001gwZAAQ","label":"OTHER-\u003EPowerVC"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.1.0;1.2.0;1.3.0;1.4.0;1.5.0;3.1.0;3.1.1;3.1.2;3.1.3;3.1.4;4.1.0;4.1.1"}]

Product Synonym

PowerVC; PowerVM; PowerVM/VIOS; VIOS; Virtual Input Output Server; IBM® Power® Virtualization Center; Power Virtualization Center; HMC; Hardware Management Console

Document Information

Modified date:
25 September 2025

UID

ibm17243645