Full HMC file systems cause serious problems that affect the HMC operations.Monitoring HMC file systems is an easy task,But you have to Enabling the HMC for remote command execution!
Let us start by know how to Enabling the HMC for remote command execution:
Follow this guide to accomplish this task:
http://pic.dhe.ibm.com/infocenter/director/v6r1x/index.jsp?topic=/director.virtual_6./eica7_t_enabling_hmc_7_remote_command_execution.html
Now,you could open SSH session with your HMC.once you logged in (default user name "hscroot" and default password "abc1234"),you get restricted shell.
Although,you log int HMC with restricted shell ,you still have the ability to monitor and Modify the File systems of the HMC!
-To Monitor the file systems
#monhmc -r disk (the default time interval is every 4 sec)
Note: full /var file systems cause a lot of problems!
Additionally ,you can set time count to monitoring your HMC file systems :
#monhmc -r disk -n 10 (every 10 sec)
For the sake of completion,i have to tell you about another command to monitor and check your HMC file systems which is lshmcfs ,thie command gives you much more information!
Let`s see how we can clean up the full file systems:
Freeing up HMC file systems (to be more specific,freeing up the logs),we simply run:
#chhmcfs -o f -d 0
-o inidacate opration and "f" means freeing
-d meaning no. of days and zero means ALL
NOTE: chhmcfs frees up space in Hardware Management Console (HMC) file systems. Space is freed by removing temporary HMC files that are used for HMC and managed system firmware problem analysis from the HMC hard disk.
If for any reason you want to freeing up a specific file systems or do more sophisticated tasks,then you need full access with root privilege to you HMC.To get root access ,give your IBM guy a call to give you a password based on your serial machine(valid for only 24 hours).
This way of accessing the HMC with root is called PESH,Produce Engineering Shell.
The scope of this blog dose not cover the PESH,for more info go to the following link:
http://www-01.ibm.com/support/docview.wss?uid=nas1dba3b86d228b9b6c862570d1008009fd
No comments:
Post a Comment