Today we encountered a degraded policy in EMC PowerPath disk on one of our SUN/Oracle Solaris boxes. We found out that the license for our PowerPath was not properly installed on the system. With this current issue – our disks is only running on Basic Failover policy which is not recommended for CLARiiON disks. To mitigate the issue, we need to install the license and set the policy back to CLARiiON Optimization Policy.
There are times that we really rely on the manual (man) pages when it comes to getting the right options for a certain command under UNIX boxes. But when it comes to Sun/Oracle Advanced Lights Out Manager (ALOM) we can count on with the help command. Here are the commands that you can have with Sun/Oracle Advanced Lights Out Manager.
It has been a while that I’m gone but the wait is over. Expect more relevant posts and (hopefully) frequent updates from your friendly UNIX SysAdmin from UNIX Note.
I will also try to find other SysAdmins that would like to write for our little site.
As UNIX Systems Administrators, we want our systems up and running – 24 hours a day, 7 days a week. Though this could be achievable with the UNIX Operating Systems, we cannot set aside the fact that our hardware equipment are prone to wear and tear. One notable point of failure if our root or boot disks. Once it dies out – our only way is thru our backup and restore it. But there is another way that we could prevent this – if we have a spare identical disk as our root disk. We can have a redundant machine by having our root disks mirrored and make our system much reliable and omit this point of failure. Here are the step-by-step how to guide in mirroring our root/boot disk using the Solaris Volume Manager (SVM).
Our server had panic and don’t have any space left on you /var partition, worry no more, there is still a way to generate the core files with the help of savecore and make Sun Support don’t wait for another panic to happen before they get their core files.
We had a hardware failure and we cannot seem to boot to our system. Our only option is to restore from our backup. The good thing is that we have foreseen this incident and took the liberty to have a backup of our OS. We will now use ufsrestore to bring our server up and running.
As a good old saying says – An Apple a Day keeps the Doctor away – is also applicable on having good OS backup that will always keep headaches lesser when the hard times come. Now comes ufsdump, a usefull command to help us backup our Solaris Operating System.
Our root (/) partition is nearing 100% utilization and upon further investigation the wtmpx file is the main culprit. We need to trim or flush this file but we need to have a backup of this file for audit purposes.
We have a very large core file and we need this to send to our vendor for analysis. The gzip’d file of the core is 20GB and the FTP server of the vendor does not like that. Therefore we need to split our very large file to smaller chunks that the FTP server would accept.