How to Update Openfiler iSCSI Storage Appliance

openfilerThis quick post will show you two method to update the Openfiler appliance. On the previous post, i have describes in details on how to setup and configure Openfiler iSCSI Storage. Openfiler is an Open Source Network Attached Storage and Storage Area Network Solution.

1. First method to update the Openfiler is from terminal or ssh session. Login as a root to Openfiler iSCSI Storage Appliance. If Internet access is available: Test connectivity to the Internet by pinging conary.rpath.com (the online source for Openfiler updates) as below :

[root@storage01 ~]# ping conary.rpath.com
PING conary.rpath.com (208.82.215.41) 56(84) bytes of data.
64 bytes from conary.rpath.com (208.82.215.41): icmp_seq=0 ttl=52 time=395 ms
64 bytes from conary.rpath.com (208.82.215.41): icmp_seq=1 ttl=52 time=402 ms
64 bytes from conary.rpath.com (208.82.215.41): icmp_seq=2 ttl=52 time=403 ms
64 bytes from conary.rpath.com (208.82.215.41): icmp_seq=3 ttl=52 time=408 ms
64 bytes from conary.rpath.com (208.82.215.41): icmp_seq=4 ttl=52 time=405 ms
64 bytes from conary.rpath.com (208.82.215.41): icmp_seq=5 ttl=52 time=409 ms
64 bytes from conary.rpath.com (208.82.215.41): icmp_seq=6 ttl=52 time=408 ms

If Internet access is available: Update the Openfiler installation by typing conary updateall and pressing Enter.

Note: It will take quite a few minutes for the updates to be downloaded and applied.

[root@storage01 ~]# conary updateall

Examples :

[root@storage01 ~]# conary updateall
Resolving dependencies...Performing critical system updates, will then restart update.
Applying update job 1 of 2:
    Update  conary:data (2.0.35-0.1-1 -> 2.1.9-0.1-1)
Applying update job 2 of 2:
    Update  conary:python (2.0.35-0.1-1 -> 2.1.9-0.1-1)
    Update  conary:runtime (2.0.35-0.1-1 -> 2.1.9-0.1-1)
Critical update completed, rerunning command...
Applying update job 1 of 24:
    Install info-vcsa(:user)=1-1-0.1
Applying update job 2 of 24:
    Install info-nagios(:user)=0-1-0.1
Applying update job 3 of 24:
    Update  acl(:doc :lib :locale :runtime) (2.2.47_1-0.1-1 -> 2.2.47_1-0.2-1)
    Update  aoe6(:doc :runtime) (64-1-1 -> 64-2-1)
    Install arecacli(:runtime)=v1.82_81103-1-3
    Update  attr(:doc :lib :locale :runtime) (2.4.41_1-0.1-1 -> 2.4.43_1-0.1-1)
Applying update job 4 of 24:
    Update  binutils(:doc :lib :locale :runtime) (2.17.50.0.6-7-0.0.1 -> 2.17.50.0.6-7-0.0.2)
    Update  conary (2.0.35-0.1-1 -> 2.1.9-0.1-1)
    Update  curl(:doc:lib:runtime) (7.15.3-1.1-1 -> 7.15.3-1.4-1)
    Update  cyrus-sasl(:lib) (2.1.21-5.2-1 -> 2.1.21-5.3-1)
    Install ddless(:doc :runtime)=1.3-1-1
Applying update job 5 of 24:
    Update  dhclient(:lib :runtime) (3.0.2-2.2-1 -> 3.0.7-0.4-1)
    Update  e2fsprogs(:data :doc :lib :locale :runtime) (1.40.8-0.2-1 -> 1.41.8-0.1-1)
    Update  ethtool(:doc :runtime) (/conary.rpath.com@rpl:devel//1/3-2-0.1 -> /conary.rpath.com@rpl:devel//2//openfiler.rpath.org@ofns:2/6-0.0.1-1)
    Update  gzip(:runtime) (1.3.5-4-0.1 -> 1.3.5-4.1-1)
Applying update job 6 of 24:
    Update  hwdata(:data :doc) (0.217-1.0.2-1 -> 0.225-0.0.2-1)
    Install hwdata:runtime=0.225-0.0.2-1
    Update  icu(:data :lib) (3.4-5.1-1 -> 3.4-5.2-1)
    Update  initscripts(:doc :locale :runtime) (8.12-8.18.4-1 -> 8.12-8.18.5-1)
    Install iperf(:doc :runtime)=2.0.4-1-0.1
Applying update job 7 of 24:
    Install iscsi-scst(:doc :runtime)=r1462-2-1
    Update  iscsi_trgt(:doc :runtime) (0.4.17-1-1 -> 1.4.19-2-1)
    Install kernel(:build-tree :configs :runtime :vmware)=2.6.29.6-0.24-1[~!kernel.pae,~kernel.smp]
Applying update job 8 of 24:
    Update  krb5(:config :data :doc :lib :runtime) (1.4.1-7.9-1 -> 1.4.1-7.10-1)
    Update  krb5-server(:config :doc :runtime) (1.4.1-7.9-1 -> 1.4.1-7.10-1)
    Update  krb5-services(:config :doc :runtime) (1.4.1-7.9-1 -> 1.4.1-7.10-1)
Applying update job 9 of 24:
    Update  krb5-workstation(:doc :runtime) (1.4.1-7.9-1 -> 1.4.1-7.10-1)
    Update  kudzu(:python :runtime) (1.1.116.2-3.6-1 -> 1.1.116.2-3.6-2)
    Update  lighttpd(:doc :lib :runtime) (1.4.20-0.1-1 -> 1.4.20-0.3-1)
    Update  lshw(:data :doc :runtime) (02.07-1.0.2-1 -> 02.14-0.0.1-1)
Applying update job 10 of 24:
    Install lsof(:doc :runtime)=4.75-3-0.1
    Update  module-init-tools(:doc :runtime) (/conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/3.1-5.3.1-2 -> /conary.rpath.com@rpl:devel//2//openfiler.rpath.org@ofns:2/3.4-2.0.2-1)
    Update  myri-firmware(:doc :lib :runtime) (v1.4.29-1-1[is: x86] -> 1.4.48b-1-1)
Applying update job 11 of 24:
    Update  net-snmp(:data :doc :lib :perl :runtime) (5.4.1-5.0.2-1 -> 5.4.1-5.3.1-1)
    Update  net-snmp-client(:data :doc :lib :runtime) (5.4.1-5.0.2-1 -> 5.4.1-5.3.1-1)
    Update  net-snmp-server(:data :doc :runtime) (5.4.1-5.0.2-1 -> 5.4.1-5.3.1-1)
Applying update job 12 of 24:
    Update  nfs-client(:doc :runtime) (1.0.10-4.6-1 -> 1.1.4-2.4-1)
    Update  nfs-server(:doc :lib :runtime) (1.0.10-4.6-1 -> 1.1.4-2.4-1)
    Update  nfs-utils(:doc :runtime) (1.0.10-4.6-1 -> 1.1.4-2.4-1)
    Update  open-iscsi(:doc :runtime) (/conary.rpath.com@rpl:devel//1/2.0_865-1.1-1 -> /conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/2.0_871-0.0.1-1)
    Update  openssh(:runtime) (4.9p1-0.1-1 -> 5.3p1-0.3-1)
Applying update job 13 of 24:
    Update  openssh-client(:doc :runtime) (4.9p1-0.1-1 -> 5.3p1-0.3-1)
    Update  openssh-server(:doc :runtime) (4.9p1-0.1-1 -> 5.3p1-0.3-1)
    Update  openssl(:config :data :lib :runtime) (0.9.7f-10.13-1[is: x86(~!i686)] -> 0.9.7f-10.16-1[is: x86(~!i686)])
Applying update job 14 of 24:
    Update  parted(:doc :lib :locale :runtime) (1.6.22-4.1.5-1 -> 1.6.22-4.1.6-1)
    Update  pciutils(:doc :runtime) (2.1.99-12-0.1 -> 2.2.3-7.1-1)
    Update  python(:lib :runtime) (2.4.1-20.17-1 -> 2.4.1-20.18-1)
    Update  qla-firmware(:lib :runtime) (/conary.rpath.com@rpl:devel//1/20070416-4-0.1[is: x86] -> /conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/2010205-0.0.1-1)
    Install qla-firmware:doc=2010205-0.0.1-1
Applying update job 15 of 24:
    Update  samba(:data :lib :runtime) (3.2.7-0.0.1-3 -> 3.4.5-0.0.1-1)
    Update  samba-client(:lib :runtime) (3.2.7-0.0.1-3 -> 3.4.5-0.0.1-1)
    Update  samba-server(:runtime) (3.2.7-0.0.1-3 -> 3.4.5-0.0.1-1)
    Update  scstadmin(:doc :perl :runtime) (1.0.0.x-5-1 -> r1411-1-1)
Applying update job 16 of 24:
    Update  sendmail(:doc :lib :runtime) (8.13.7-0.3-1[sasl] -> 8.13.7-0.4-1[sasl])
    Update  strace(:doc :perl :runtime) (4.5.12-2-0.1 -> 4.5.18-0.1-1)
    Install traceroute(:doc :runtime)=1.4a12-4-0.1
    Install userspace-kernel-firmware(:runtime)=2.6.29.6-0.24-1[~!kernel.pae,~kernel.smp]
Applying update job 17 of 24:
    Install autodir(:doc :lib :runtime)=0.99.9-2-1
    Install xfsdump(:doc :runtime)=3.0.1-0.0.1-1
    Update  xfsprogs(:doc :lib :runtime) (/conary.rpath.com@rpl:devel//1/2.6.25-4-0.1 -> /conary.rpath.com@rpl:devel//2//openfiler.rpath.org@ofns:2/3.0.1-0.0.2-1)
    Install xfsprogs:locale=3.0.1-0.0.2-1
Applying update job 18 of 24:
    Install autofs(:doc :lib :runtime)=4.1.4-5-0.1
    Update  bind(:lib) (9.3.4_P1-0.7-1[ipv6,~!pie,ssl] -> 9.4.3_P5-1.1-1)
    Update  bind-utils(:doc :runtime) (9.3.4_P1-0.7-1[ipv6,~!pie,ssl] -> 9.4.3_P5-1.1-1)
    Erase   device-mapper:doc=1.02.24-2-1
    Erase   device-mapper:runtime=1.02.24-2-1
    Update  lvm2:doc (2.02.34-1-1 -> 2.02.47-1-1)
Applying update job 19 of 24:
    Install device-mapper-multipath:lib=0.4.8-0.3-1
    Update  drbd(:doc :lib :runtime) (8.2.7-2-1[~!xen] -> 8.3.7-1-1)
    Install drbd:data=8.3.7-1-1
    Install drbdlinks(:doc :lib :runtime)=1.18-3-1
    Install libaio(:lib)=0.3.106-3-0.1
    Update  lvm2:lib (2.02.34-1-1 -> 2.02.47-1-1)
Applying update job 20 of 24:
    Erase   device-mapper(:lib)=1.02.24-2-1
    Update  device-mapper-multipath(:doc :runtime) (0.4.7-1.1-1 -> 0.4.8-0.3-1)
    Update  lvm2(:runtime) (2.02.34-1-1 -> 2.02.47-1-1)
    Install man:lib=1.6-5.1.1-1
    Erase   man:locale=1.6-5-0.1
    Update  nut(:data :doc :runtime) (2.2.0-5-1 -> 2.2.2-5-1)
    Install nut:lib=2.2.2-5-1
[initscript] Stopping clvm:[FAILED]

Applying update job 21 of 24:
    Install nagios-plugins(:runtime)=1.4.10-1.1-1
    Install nrpe(:doc :runtime)=2.12-4.1-1
    Install postgresql(:lib)=8.1.19-0.1-1
    Install udev:lib=116-4.2.6-1
    Install util-linux-ng:data=2.16-0.0.3-1
Applying update job 22 of 24:
    Update  man(:doc :runtime) (/conary.rpath.com@rpl:devel//1/1.6-5-0.1 -> /conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/1.6-5.1.1-1)
    Update  mkinitrd(:doc :runtime) (4.2.15-16.13.6-2 -> 4.2.15-16.13.9-1)
    Update  ntp(:runtime) (4.2.4p6-1.1-1 -> 4.2.4p7-0.1-1)
    Update  openfiler:runtime (r1584-3-1 -> r1653-1-1)
    Update  shadow:runtime (/conary.rpath.com@rpl:devel//1/4.0.7-14.3-1 -> /conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/4.0.7-14.3.1-1)
    Update  udev:runtime (/conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/069-5.4.1-1[~!selinux] -> /conary.rpath.com@rpl:devel//2-devel//openfiler.rpath.org@ofns:2/116-4.2.6-1)
    Install util-linux-ng-extras:runtime=2.16-0.0.3-1
    Install util-linux-ng:config=2.16-0.0.3-1
    Install util-linux-ng:runtime=2.16-0.0.3-1
    Erase   util-linux:runtime=2.12r-1.6-1
[openfiler] changing group /etc/shadow

[openfiler] Stopping openfiler: [  OK  ]

[openfiler] Starting openfiler: [  OK  ]

[openfiler] enabling / starting default services

[openfiler]

[openfiler] Shutting down Winbind services: [FAILED]

[openfiler] Starting Winbind services: [  OK  ]

[openfiler] Stopping portmapper: [  OK  ]

[openfiler] Starting portmapper: [  OK  ]

[openfiler] Stopping NFS statd: [  OK  ]

[openfiler] Starting NFS statd: [  OK  ]

[openfiler] Stopping atd: [  OK  ]

[openfiler] Starting atd: [  OK  ]

[openfiler] disabling nscd service

[openfiler] Stopping nscd: [FAILED]

Applying update job 23 of 24:
    Update  openfiler(:doc) (r1584-3-1 -> r1653-1-1)
    Update  shadow (/conary.rpath.com@rpl:devel//1/4.0.7-14.3-1 -> /conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/4.0.7-14.3.1-1)
    Install shadow:doc=4.0.7-14.3.1-1
    Install shadow:locale=4.0.7-14.3.1-1
    Update  udev(:data :doc) (/conary.rpath.com@rpl:devel//1//openfiler.rpath.org@ofns:2/069-5.4.1-1[~!selinux] -> /conary.rpath.com@rpl:devel//2-devel//openfiler.rpath.org@ofns:2/116-4.2.6-1)
    Erase   util-linux(:data)=2.12r-1.6-1
    Install util-linux-ng=2.16-0.0.3-1
    Install util-linux-ng-extras(:doc :supdoc)=2.16-0.0.3-1
Applying update job 24 of 24:
    Update  group-core (2.3-16-4[~!kernel.pae,~kernel.smp,~proftpd.auth_pam,~proftpd.ifsession,~proftpd.ipv6,~proftpd.rewrite,~proftpd.tls,sasl is: x86(~!sse2)] -> 2.3-36-3[~!kernel.pae,~kernel.smp,~proftpd.auth_pam,~proftpd.ifsession,~proftpd.ipv6,~proftpd.rewrite,~proftpd.tls,sasl is: x86(~!sse2)])
    Update  group-openfiler (2.3-16-4[~!kernel.pae,~kernel.smp,~proftpd.auth_pam,~proftpd.ifsession,~proftpd.ipv6,~proftpd.rewrite,~proftpd.tls,sasl is: x86(~!sse2)] -> 2.3-36-3[~!kernel.pae,~kernel.smp,~proftpd.auth_pam,~proftpd.ifsession,~proftpd.ipv6,~proftpd.rewrite,~proftpd.tls,sasl is: x86(~!sse2)])

Reboot the Openfiler appliance :

[root@storage01 ~]# shutdown -r now

2. You also can do update from Openfiler GUI as below :

Login to Openfiler GUI –> Select the System tab –> Click System Update –> Finally click Launch system update.
openfiler16

How to Setup and Configure Openfiler iSCSI Storage on VMware

This post describes on how to setup and configure hosted Openfiler iSCSI storage target on a VMware ESX/ESXi or VMware server 1.x or 2.x host using the freely available Openfiler appliance. However this configuration and setting not a suitable solution for a production environment as it does not include any iSCSI CHAP authentication or datastore multipathing. But it’s good for troubleshooting and learning. Openfiler is an Open Source Network Attached Storage and Storage Area Network Solution.

Pre-Requisites :

  • a. VMware ESX/ESXi/Server 2.0/Vmware workstations/VMware player as a host with a minimum of 5GB of free space on the local datastore.
  • b.Addional Space for extra logical volume on Openfiler iSCSI Storage (e.g dev/sdb)
  • c.Openfiler appliance source file. (e.g openfiler-2.3-x86_64.vmware.tar.gz) You may download at this URL :
    http://www.openfiler.com/community/download/
  • Disk /dev/sdb (30GB) has been added as below :
[root@storage01 ~]# fdisk -l

Disk /dev/sda: 2355 MB, 2355978240 bytes
16 heads, 63 sectors/track, 4565 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        4565     2300696   83  Linux

Disk /dev/sdb: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3917    31457279+  ee  EFI GPT

TCP/IP Configuration :

The procedure detailed below is based on the following configuration. Openfiler appliance assigned the hostname and TCP/IP configuration details:

HOSTNAME=storage01
IPADDR=192.168.1.56
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
nameserver 202.188.0.133
nameserver 202.188.1.5

Steps and Procedure on How to Setup and Configure Openfiler iSCSI Storage :

1. Extract the contents of the downloaded Openfiler tar.gz file (one .vmx file and two .vmdk files) into a directory, the name of which reflects the hostname you wish to use for the Openfiler appliance (example: storage01).

2. Login to ESXi/ESX/VMware Server/Vmware Workstation console, add extracted Openfiler tar.gz file to inventory.

3. Skipped this step on VMware Server 1.x, VMware Server 2.x and VMware Workstation. In ESXi/ESX server edit the Openfiler appliance settings and add a second disk of the size determined.(example: 30GB).

4. Modify the vCPU and Memory setting to meet your requirement.

5. Power on the Openfiler appliance. By default, the Openfiler appliance will attempt to obtain an IP address via DHCP, but best practice is to assign a static Ip address and this such configuration is typically done via the Openfiler web interface. On the Screen capture, hostname and static ip address has been assigned as below :

HOSTNAME=storage01
IPADDR=192.168.1.56

openfiler1

6. Logon to the console as root. By default, no root password is set so you will not be prompted. Set a root password by entering the command passwd, pressing Enter and following the prompts.

Note: A password must be set in order to permit a remote root login from a SSH client.

[root@dhcp01 ~]# passwd
Changing password for user root.
New UNIX password:

7. Browse to https:/DHCP_IP_Address:446, or to the IP address if not using DNS, and ignore the certificate warning. Logon to the Openfiler web interface with the default administrator. Username openfiler and default Password password.

Note: The default administrative port number is 446.

openfiler2

8. To Change to static IP, Select the System tab then scroll down to the “Network Interface Configuration” click “Configure“. On the Network Interface Configuration”, change default Boot Protocol, DHCP to Static for eth0. Then Enter the IP Address, Netmask and leave default for MTU.

openfiler3

9. To configure network range allowed, select the System tab and scroll down to the “Network Access Configuration” section. Define the allowed networks that accept connections from Openfiler appliance. You also can specify individual host IP addresses and ranges. Click Update after entering each set of details.

openfiler4

10. To add the the new logical disk select the Volumes tab and click the Block Devices link. Confirm the presence of disk /dev/sdb.

Please note that the isk /dev/sda is the disk that Openfiler is running on; /dev/sdb is the second disk that was added and that will be provisioned as iSCSI storage.

openfiler7

Click the /dev/sdb link and scroll down to the Create a partition in /dev/sdb section. By default, a partition will be created that fills the entire disk. Accept the defaults and click Create.

Openfiler8

11. To add volume Group,select the Volumes tab. Click the Volume Groups link and enter a Volume Group name “datagroup” (the name is not critical), select /dev/sdb1 (30GB) and click Add volume group.
openfiler9

12. To Create a volume in “datagroup“, select the Volumes tab. Click the Add Volume link. The only existing volume group of volumegroup (datagroup) will be selected by default. Scroll down to the Create a volume in “volumegroup” section. Enter a Volume Name of volume (the name is not critical), a Volume Description of vmware (the description is not critical), adjust the required Space slider up to the maximum, select a Filesystem/Volume type of iSCSI and click Create.
openfiler10

13. This steps is to enable iSCSI target and disable iSCSI initiator. Select the Services tab. Click the Enable link adjacent to iSCSI target server. Click the Disable link adjacent to iSCSI initiator.

openfiler11

14. To Add new iSCSI target, select the Volumes tab and click the iSCSI Targets link from the Volumes Section menu. Modify the auto-generated Target IQN to include the Openfiler name (iqn.2012.openfilerlab1.local in this example) and click Add.

openfile12

Then select the LUN Mapping sub-tab and click Map to map the previous defined volume as a LUN to the newly created iSCSI target (accepting all the defaults).

openfiler13

Finally, select the Network ACL sub-tab and change the Access from Deny to Allow. Click Update.

openfiler14

15. Congratulation!! Now the iSCSI target is accessible to any iSCSI requester on the permitted network/s or IP addresses.

How to Check or Test Reverse DNS on Linux and Windows

dnsReverse Domain Name System (DNS) lookup (also known as rDNS) is a process to determine the hostname associated with a given IP address. It is part of the behavior of the DNS. Its main function is to translate the numeric addresses(IP addresses)of the websites to domain or host names, as opposed to the Forward DNS process. Reverse DNS is separate from forward DNS. Many internet mail servers use reverse DNS to confirm that the server trying to deliver mail to them is genuine, this can help to reduce amount of spam that comes in to their network. Follow the following steps to check or test reverse DNS on linux and Windows operating system.

1. To Check or Test Reverse DNS on Linux operating system :

host <IP Address>

Example :

[root@centos63 ~]# host 184.173.214.97
97.214.173.184.in-addr.arpa domain name pointer 184.173.214.97-static.reverse.softlayer.com.

2. To Check or Test Reverse DNS on Windows Operating system :

C:\>nslookup <IP Address>
C:\>nslookup 184.173.214.97
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    184.173.214.97-static.reverse.softlayer.com
Address:  184.173.214.97

How to Enable IMAP on Gmail account

Gmail is one of the best free webmail service. It’s also possible to access Gmail inbox using IMAP and POP. If proper configured, you will be able to retrieve your Gmail messages with a client like Mozilla Thunderbird and Microsoft Outlook. This post will shows you the steps to enable IMAP in Gmail account :
Gmail

Steps to enable IMAP on Gmail account:

1. Sign in to your Gmail account.
2. Click on the gear icon in the upper right, then select Settings. This will bring you to configuration screen.
3. Click Forwarding and POP/IMAP.
4. By default IMAP is not enabled. Select Enable IMAP.
5. Configure your IMAP client and click Save Changes.

  • You can configure what is the next action when I mark a message in IMAP as deleted.
  • You also can configure what is the next action when a message is marked as deleted and expunged from the last visible IMAP folder.

6. Follow the “Configuration instructions” to configure your mail client such as Mozilla Thunderbird, Android and iPhone.

You can use the following information to configure IMAP with many mail clients :

Incoming Mail (IMAP) Server – requires SSL:

imap.gmail.com
Use SSL: Yes
Port: 993

Outgoing Mail (SMTP) Server – requires TLS :

smtp.gmail.com (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587

How to Download FastStone Image Viewer 4.6

FastStone Image ViewerFastStone Image Viewer is a freware tool for image converter and editor. The current updated version for FastStone Image Viewer are 4.6. It’s very fast, stable, user-friendly image browser, converter and editor. It has a nice array of features that include image viewing, management, comparison, red-eye removal, emailing, resizing, cropping, retouching and color adjustments.

Its innovative but intuitive full-screen mode provides quick access to EXIF information, thumbnail browser and major functionalities via hidden toolbars that pop up when your mouse touches the four edges of the screen. Other features include a high quality magnifier and a musical slideshow with 150+ transitional effects, as well as lossless JPEG transitions, drop shadow effects, image annotation, scanner support, histogram and much more. It supports all major graphic formats (BMP, JPEG, JPEG 2000, animated GIF, PNG, PCX, PSD, EPS, TIFF, WMF, ICO and TGA) and popular digital camera RAW formats (CRW, CR2, NEF, PEF, RAF, MRW, ORF, SRF, ARW, SR2, RW2 and DNG).

Change Log of FastStone Image Viewer 4.6

* Improved the “Acquire Images from Scanner” tool
* Other minor improvements and bug fixes

Download FastStone Image Viewer 4.6

How to Download Format Factory Software

Format FactoryFormat Factory is a multifunctional media converter that available for free. It provides a lot of useful functions as below :
1. Convert all Format to MP4/3GP/MPG/AVI/WMV/FLV/SWF.
2. Convert all Format to MP3/WMA/AMR/OGG/AAC/WAV.
3. Convert all Format to JPG/BMP/PNG/TIF/ICO/GIF/TGA.
4. Convert Rip DVD to video file , Rip Music CD to audio file.
5. MP4 files support iPod/iPhone/PSP/BlackBerry format.
6. Supports RMVB,Watermark, AV Mux.

Furthermore, Format Factory has this Features :
1.It support converting all popular video,audio,picture formats to others.
2 It can repair damaged video and audio file.
3 It can reduce Multimedia file size.
4 It support iphone,ipod multimedia file formats.
5 Picture converting supports Zoom,Rotate/Flip,tags.
6 DVD Ripper.
7 Supports 60 languages

OS requirements: All Windows OS

To download Format Factory, click this link :Download Format Factory

How to Check and Verify Integrity MD5 Checksum on Windows 7

In this i will show the quick steps how to verify MD5 using MD5sums on Windows 7. This steps may working on other Windows operating system such as Windows 2000, Windows XP, Windows 2003 server and Windows 2008 server. MD5sums calculates the MD5 message digest for one or more files. MD5 is a message digest algorithm that takes a message of arbitrary length and produces a 128-bits digital signature of the message.

1. Assumed that you have downloaded the FreeBSD-9.0 iso file and CHECKSUM verifier file together :
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/FreeBSD-9.0-RELEASE-i386-dvd1.iso
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/CHECKSUM.MD5

2. Download and Save the md5sums.exe to C:\ as md5sum.exe :
Download: md5sums-1.2.zip [28 K]

3. Open command prompt and enter the following command :

C:\>md5sums target_file

Example :

C:\>md5sums Z:\Download\FreeBSD-9.0-RELEASE-i386-dvd1.iso

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[Z:\Download\]
FreeBSD-9.0-RELEASE-i386-dvd1.iso         100% fee32ba2041285b971daf7ea429e36e4

4. Compare the MD5 with the following CHECKSUM.MD5 file below :

MD5 (FreeBSD-9.0-RELEASE-i386-bootonly.iso) = 70b4b0dd42c309da79ce63ba2789cfe3
MD5 (FreeBSD-9.0-RELEASE-i386-disc1.iso) = 5bf615f286ee6eeb3ecce45bd8d1622c
MD5 (FreeBSD-9.0-RELEASE-i386-dvd1.iso) = fee32ba2041285b971daf7ea429e36e4
MD5 (FreeBSD-9.0-RELEASE-i386-memstick.img) = 79ddd8f3422e209ae9bd11fee4e399eb

5. If the MD5 key is the same above, the downloaded iso should be ok.

How to Obtain Diagnostic Information for VMware ESXi 5.0 hosts using the vSphere Client

When you lodged a support request to VMware Technical Support, they routinely requests the diagnostic information from you. This diagnostic information contains product specific logs and configuration files from the host on which the product is run or from the host that may have issues and need further troubleshooting. This information is gathered using a specific script or tool within the product. Collecting diagnostic information is the same as collecting or gathering log files. This post will provides procedures for obtaining diagnostic information for ESXi 5.0.

VMware Official Knowledge Base

ESXi 5.0 host diagnostic information can be gathered using the vSphere Client connected to the ESXi host or to vCenter Server.

To gather diagnostic data using the VMware vSphere Client:

1.  Open the vSphere Client and connect to vCenter Server or directly to an ESXi 5.0 host.
2.  Log in using an account with administrative privileges or with the Global.Diagnostics permission.
3.  Select an ESXi host, cluster, or datacenter in the inventory.
4.  Click the File > Export > Export System Logs.
5.  If a group of ESXi hosts are available in the selected context, select the host or group of hosts from the Source list.
6.  Click Next.
7.  In the System Logs pane, select the components for which the diagnostic information must be obtained. To collect diagnostic information for all the components, click Select All.
8.  If required, select the Gather performance data option and specify a duration and interval.

VMware
9.  Click Next.
10.  In the Download Location pane, click Browse and select a location on the client’s disk where you want to to save the support bundle.
11.  Click Next.
12.  In the Ready to Complete pane, review the summary and click Finish. The Downloading System Logs Bundles dialog appears and provides progress status for the creation and downloading of the support bundle from each source. A Generate system logs bundles task is created.
13. When complete, upload the logs to the FTP site. For more information, see Uploading diagnostic information to VMware (1008525).

How to Download VMware vSphere Command-Line Interface (vSphere CLI)

The vSphere Command-Line Interface (vSphere CLI) command set allows you to run common system administration commands against ESX/ESXi systems from any machine with network access to those systems. vSphere CLI provides a set of commands that you use to manage, configure, and automate administrative activities for ESXi and your vSphere virtual environment. It’s includes the ESXCLI command set, vicfg- commands, and some other commands. This are the current version of the vSphere CLI at the time this post is written.

Version: 5.0
Release Date: 8/24/2011
Target Platform: ESXi 5.0, ESX 4.x, vCenter 4.x and later, VMware Infrastructure 3.5 u2 and later

To install vSphere CLI version 5.0 on your workstation, please follow the steps :

1. Browse to ESXi 5.0 server’s ip address. As example, http://192.168.1.50,
Under For Administrator –> vSphere Remote Command Line, Click “Download Windows Installer(exe)“. This vSphere CLI installer is for windows operating system platform such as Windows 7 and Windows XP :
vmware

2. Click Download to proceed :
vmware

3. If you have registered to vmware.com, please login, otherwise register it for free :
vmware

4. Please select download option either using Download manager or use web browser. Recommended way is to use Download manager as i may faster than usual. By the way, I have use web browser :
vmware

5. Wait for downloading.
vmware

How to Install VMware Tools on a Solaris Guest

It is recommended to install VMware Tools in the guest operating system. Although the guest operating system can run without VMware Tools, you lose important functionality, convenience and performance improvement.

When you install VMware Tools, you install the following components:

a) The VMware Tools service (vmtoolsd.exe on Windows guests or vmtoolsd on Linux and Solaris guests). This service synchronizes the time in the guest operating system with the time in the host operating system. On Windows guests, it also controls grabbing and releasing the mouse cursor.

b) A set of VMware device drivers, including an SVGA display driver, the vmxnet networking driver for some guest operating systems, the BusLogic SCSI driver for some guest operating systems, the memory control driver for efficient memory allocation between virtual machines, the sync driver to quiesce I/O for Consolidated Backup, and the VMware mouse driver.

c) The VMware Tools control panel, which lets you modify settings, shrink virtual disks, and connect and disconnect virtual devices.

d) You can also use the command-line interface of the VMware Tools configuration utility in the guest operating system to perform these tasks. See the VMware Tools Configuration Utility User’s Guide.

e) A set of scripts that helps you to automate guest operating system operations. The scripts run when the virtual machine’s power state changes if you configure them to do so.

f) The VMware user process (VMwareUser.exe on Windows guests or vmware-user on Linux and Solaris guests), which enables you to copy and paste text between the guest and managed host operating systems.

To install VMware Tools in a Solaris guest operating system, follow the following steps :

1. Ensure that your Solaris virtual machine is powered on. In the vSphere Client inventory, right-click the virtual machine and select Power > Power On.

2. Click VM in the virtual machine menu, then click Guest > Install/Upgrade VMware Tools and click OK.

3. Copy vmware-solaris-tools.tar.gz from /cdrom/vmwaretools to a temporary directory (/tmp/).

[root@solaris ~]# cp /cdrom/vmwaretools/vmware-solaris-tools.tar.gz /tmp
[root@solaris ~]# cd /tmp

4. Decompress the file using gunzip command.

[root@solaris tmp]# gunzip vmware-solaris-tools.tar.gz

5. Extract the contents of the tar file with the command:

[root@solaris tmp]# tar xvf vmware-solaris-tools.tar

6. Change directory using the command:

[root@solaris tmp]# cd vmware-tools-distrib

7. To install VMware Tools, run this command from the directory vmware-tools-distrib :

[root@solaris vmware-tools-distrib]# ./vmware-install.pl

Important Note :It is recommended to respond to the configuration questions and press “Enter” to accept all of the default values. Reboot the virtual machine for changes to take effect.

8. Check if VMware tools service is running with the command:

[root@solaris ~]# /etc/init.d/vmware-tools status

The output is similar to:

vmware-guestd is running
vmware-memctld is running

How to use Process Explorer 15.13 to Monitor the Process on Windows

On February 17, 2012, Microsoft Sysinternals has released a new version of its excellent system monitoring tool which is Process Explorer 15.13. Process Explorer is an advanced process management utility that picks up where Task Manager leaves off. It will show you detailed information about a process including its icon, command-line, full image path, memory statistics, user account, security attributes, and more. Process Explorer can shows you the information about which handles and DLLs processes have opened or loaded. The Process Explorer display consists of two sub-windows. The top window always shows a list of the currently active processes, including the names of their owning accounts, whereas the information displayed in the bottom window depends on the mode that Process Explorer is in: if it is in handle mode you’ll see the handles that the process selected in the top window has opened; if Process Explorer is in DLL mode you’ll see the DLLs and memory-mapped files that the process has loaded. Process Explorer also has a powerful search capability that will quickly show you which processes have particular handles opened or DLLs loaded. The unique capabilities of Process Explorer make it useful for tracking down DLL-version problems or handle leaks, and provide insight into the way Windows and applications work.

1. To download Process Explorer 15.13, you can get it from FileHippo

2. After downloaded the file, extract it and open ProcessExplorer folder. Double click procexp.

3. Click Agree to proceed :

4. Start to monitor your process using Process Explorer :

How to Check MX Record Using nslookup Command on Windows

nslookup is a command-line tool for network administrator and system administrator that available in many computer operating systems such as linux and windows for querying the Domain Name System (DNS). nslookup can obtain domain name or IP address or for any other specific DNS record. In this post, i will share how nslookup command will useful to check MX record on windows command prompt.

Open windows command prompt and enter “nslookup” command :

C:\>nslookup
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> set type=mx

or
Alternatively, you can run “set q=mx” which will return you the same result with “set type=mx” command :

C:\>nslookup
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> set q=mx

After entering “set typ=mx” or “set q=mx”, you can proceed to enter the domain name that you want to check it’s mx records. In this example, i will share the mx records for gmail.com, yahoo.com and bloggermy.com.

Check MX records for gmail.com

> gmail.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
gmail.com       MX preference = 30, mail exchanger = alt3.gmail-smtp-in.l.google.com
gmail.com       MX preference = 5, mail exchanger = gmail-smtp-in.l.google.com
gmail.com       MX preference = 40, mail exchanger = alt4.gmail-smtp-in.l.google.com
gmail.com       MX preference = 20, mail exchanger = alt2.gmail-smtp-in.l.google.com
gmail.com       MX preference = 10, mail exchanger = alt1.gmail-smtp-in.l.google.com

Check MX records for yahoo.com

> yahoo.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
yahoo.com       MX preference = 1, mail exchanger = mta5.am0.yahoodns.net
yahoo.com       MX preference = 1, mail exchanger = mta6.am0.yahoodns.net
yahoo.com       MX preference = 1, mail exchanger = mta7.am0.yahoodns.net

Check MX records for bloggermy.com

> bloggermy.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
bloggermy.com   MX preference = 5, mail exchanger = ALT1.ASPMX.L.GOOGLE.com
bloggermy.com   MX preference = 5, mail exchanger = ALT2.ASPMX.L.GOOGLE.com
bloggermy.com   MX preference = 10, mail exchanger = ASPMX2.GOOGLEMAIL.com
bloggermy.com   MX preference = 10, mail exchanger = ASPMX3.GOOGLEMAIL.com
bloggermy.com   MX preference = 0, mail exchanger = bloggermy.com
bloggermy.com   MX preference = 1, mail exchanger = ASPMX.L.GOOGLE.com