|
Wednesday, 23 April 2008 |
|
Since this is my first experience to get PBEagent works inside VMware ESX 3.5, lack of the documentation about how to setup, configure & test PBEagent plus the third party vendor who sold the UPS don't know how to configure it, I don't have any choice except to get all things work as per my customer expectation.
We need to make sure few things before start the UAT :
- PBEagent are running - /etc/init.d/PBEagent status
- APC Port is open - port 3052 for Web Config
- Powerchute "Smart" signal - It won't works when using "simple" signal
- Enable Broadcast messages - This will notify all users before UPS going down
- ESX Virtual Power Shutdown - Guest OS Shutdown when ESX going to shutdown
When all ready I just clicked "initiate shutdown" feature's found inside Powerchute webaccess then monitor the ESX process via SSH & VI Client. Within 5 minutes (depend on configuration) I got a messages "Powerchute Business Edition: Host will shutdown within ....." then "Powerchute Business Edition: Shutdown Process Started". From vi client I also noticed the guest OS will going to shutdown state one by one depending on your ESX confguration before the server going to poweroff.   All process went very smoothly & for sure, it's such a big relieved to me considering all the problems I had during project implementation. Finally I can close this tricky, final & the last UAT & I can concentrate now on my final documentation. ariyossss athlon_crazy 23/4/2008 11:00am |
|
Last Updated ( Wednesday, 23 April 2008 )
|
|
|
Saturday, 12 April 2008 |
|
Just want to share my company dinner at Sheraton Subang recently: |
|
Read more...
|
|
|
Thursday, 10 April 2008 |
|
Some pictures taken during HP Insight Control Environment (ICE) hands-on training at One World Hotel, Bandar Utama last month. The training simply just wan't us to get advantage & familiarize with ICE tools. What I can say, it's pretty cool tools for us to manage HP Blade Server. You will find so many features inside this tools compare with IBM management tools such as you can manage & centralize your license, P2V from HP Proliant server to blade, resource management, generate report, performance monitoring, rapid deployment pack which is you can drag & drop during OS installation & many more. Since this is my first time experience to work with HP Blade, little difficult for me to catch-up & master all this things within one day. The only thing I remember is, ICE daemon installation itself will take around two (2) hours to finished it. But, it's very good tools indeed to manage your HP Blade Server.
|
|
Last Updated ( Thursday, 10 April 2008 )
|
|
Read more...
|
|
|
Monday, 07 April 2008 |
|
This two days I was busy setting up SLES10 vps inside my noguix server just to have scalix mail server running inside for my personal use. After 3 times I did hard testing & resources calculation on my laptop, finally I export SLES10+SCALIX vmware image(.vmx) from my laptop into noguix server. But before that I just add another memory a total 768MB + 800MB(swap) just to make sure noguix have enough resources to run SLES10+SCALIX. It's remind me on Zimbra which their heavy requirements need with atleast 1GB for testing & 2GB for production. After extract the vmware image, then I start the VPS remotely from vmware-server on my laptop. As I expected, SLES10+SCALIX running smoothly without hassle. |
|
Last Updated ( Monday, 07 April 2008 )
|
|
Read more...
|
|
|
Wednesday, 02 April 2008 |
|
I just finished with scalix implementation for my customer mail server recently. The scalix will handle approximately 20-50 premium & standard users account running on SLES10 SP1 with 1GB of ram as a guest OS on top of VMware ESX server. The installation process of scalix went smoothly since SLES10 is one of supported OS by scalix and you must meet their software & technical requirements before do the installation such as:-
|
|
Last Updated ( Wednesday, 02 April 2008 )
|
|
Read more...
|
|
|
Saturday, 22 March 2008 |
|
This is a very good info I want to share with you all. One of my client had problem with their cluster last time. The cluster seems lost connection with their eDirectory and caused the whole groupwise system not working properly. After full investigation, I found that one of their master cluster node had been targeted by intruder. With trial & error method, hundred of username & password had been tried until they find the right combination to get access to the system which resulted their network resources exausted, flooded with the attack & became slow. If unluncky, the network can totally disconnected or unavailable for the connection. When eDirectory unable to connect with the cluster for the specified time given, eDirectory will diclared that the cluster resources is down. The bad thing is, that cluster resource is needed to make sure the whole groupwise system can work properly. A groupwise consist of primary, secondary domain & post office. If one the component failed to operate this will caused a problem to the groupwise. So, we adviced our client to thighten up their network security & firewall to avoid this problem again in the future. |
|
|
|
<< Start < Prev 1 2 3 4 5 6 7 8 Next > End >>
|
| Results 29 - 35 of 56 |
