Archive for January, 2010
VMware just released new update for VirtualCenter 2.5 Update 6 (Release Notes)
This new release will improve :
- Customization Improvements
- Support for Firefox 3.x Browsers with VirtualCenter Web Access
- Bug and security fixes
ariyossssComments are off for this post
As promised in my last post regarding SLES11, I chose Samba + Openldap to be the first 2 services I’m going to try for the operational and stability in SLES11. Since we all knew this is trivial job for some system admin to configure both services and make it running well on SLES10 and some Linux Distro.
- To have Samba file sharing and user authentication via LDAP server.
- Samba Version 3.2.7-11.6-2057-SUSE-CODE11
Notes : All software will be installed by default during SLES11 installation. However I still have to install “perl-ldap” before I can run any “smbldap-tools” command.
Samba+Ldap also require “smbldap-tools” for user & group operation. Unfortunately, akin to the previous one, SLES11 also doesn’t come with “smbldap-tools”. I have to download it manually from somewhere which I forgot where Read more2 comments
I will get a chance to conduct my 3rd VMware JumpStart Training for customer but this time the event will be held at Putrajaya on 25-26th January 2010. The training is for 16-20 packs and I’ve been requested to conduct one simple test for participants and among those participants, four(4) will be selected for VMware Certified Professional Training.
Perhaps this is my last show as a Trainer and hopefully my fellow colleagues can take over the responsibility from me starting from 28-29 of January and 4-5 of February.
athlon_crazy 23/01/2010 6:15am
Pictures Update : Just update for the past training with some pictures. Read moreNo comments
Perhaps this could be too late for sharing however, I did some testing with my junior on how we can patch ESX 3.5 U3 to U4 via “esxupdate” command. Though we knew, we can do this via ESX 3.5 U4 CD, I still prefer “esxupdate” method due to it’s success story. Since ESX3.50 U4 patch inclusive of more than twenty(20) .zip files, unzip and patch process could take longer time if we do this manually one by one. Therefore, I create one script (patch-esx350u4.sh) for my junior so that he can do ESX 3.5 U4 upgrade easily for one of my customer next week.
1.First we download the patch ESX350-Update04 (include file dependencies around 1.2GB in size) from VMware site.
2.Download script patch-esx350u4.sh here
3.Upload all zip files to target ESX (Make sure all zip files uploaded specially ESX350-20090903201-UG.zip)
4.Upload patch-esx350u4.sh to target ESX
5.cd to your upload folder —> $cd /root/ESX3U4
6.Make it executable —> $chmod +x patch-esx350u4.sh
7.Run patch script —> $./patch-esx35u4
8.Give your location of .zip files eg:/root/ESX3U4
9.Verify patch status once finished with $esxupdate -l query
10.For unsuccessfull patch, please patch manually or rerun “patch-esx350u4.sh” (read manual-patch.txt)
$esxupdate -n -r file:/root/ESX35U4/ESX350-200909012-UG update
- Make sure all patchs/zip included in $esxupdate -l query (specially ESX350-Update04)
- The patch-esx350u4.sh will unzip and patch ESX one by one without reboot the system until finished
Having some installation test for SLES 11 running on my ESX 3.5 U3 recently. Once we meet adequate SLES 11 hardware requirements, the installation process can be done very fast yet quite confusing on “custom partitioning” part but other than that SLES 11 installation akin to what we did last time on SLES 10. Perhaps you also may had some errors “calling Yast” during root & user account configuration which end up user unable to log-in to this new fresh SLES 11 once installation completed. However, boot into “init 1″ let me to reset my root password.
So, in future I will try to setup few services like, dhcp,dns, ldap, samba & etc on this new SLES specially on iSCSI target & initiator and see whether they(Novell) do vastly changed SLES 11 from SLES10 in term of OS stability, security and etc.
SLES11, 512mb, 10gb, kernel 2.6.27, gnome, esx 3.5 u3, nfs, SLES-11-DVD-x86_64-GM-DVD1.iso
athlon_crazy 21/01/2010 7:04amNo comments
Few months back I gave up with my test “proxy authentication via ldap” in Endian Firewall since there was something in Endian which prevent users from authenticate correctly to my ldap servers. However, last week I found something which can help you all configure your Endian HTTP proxy authentication correctly with any ldap server.
So basically, I found that the culprit is “LDAP config” inside Endian squid.conf as below :
# START AUTHENTICATION (NOX)
# METHOD is LDAP
auth_param basic program /usr/lib/squid/squid_ldap_auth -b “dc=no-x,dc=org” -d -D “cn=yours,dc=no-x,dc=org” -w “password” -f “(&(&(objectClass=person)(uid=%s))(|))” -u uid -v 3 -P xx.xx.xx.xx:389
auth_param basic children 20
auth_param basic realm LOGIN
auth_param basic credentialsttl 60 minutes
Just want to wish, a warm welcome to *** to all my new colleagues (Suhaimi, Fathul and Khairul). Hopefully we can work and learn together toward 2010. Finally God heard our last year wish.. heheheNo comments