How to install and commission all A2E 8.0 elements on a demo laptop

This document explains how to install and commission all A2E elements (SM,AM,SESM,IPCM,PROV,MAS,RTP) on a demo laptop computer. SM,AM,SESM,IPCM, PROV and MAS can be deployed in same operational system (not supported, lab use only), however RTP should be installed in different operational systems. To make this possible you need to install VMware server which is going to run as A2E RTP Platform for RTP (ple3).

Recommended Hardware Requirements

1. 2 Core CPU
2. 4G Memory

1) Installing A2E platform on laptop

Boot your laptop from A2E platform CD. Type “install-kvm LabMachine” for starting installation. LabMachine parameter is necessary for skipping hardware compatibility check in installer. Most laptops have only one ethernet interface even they have 4G of memory and 2 Core CPU. No worries second interface won’t be necessary.

Please proceed with installer guide to finish platform installation.

Please apply platform patches if there is one.

2) Installing MCP and Oracle

• Place Oracle installer load in /var/mcp/media directory with ntappadm.

• Place MCP load in /var/mcp/loads directory with ntappadm

• Extract your MCP_14.0.0.0_X.zip which located in /var/mcp/loads

• Copy all files in /var/mcp/loads/MCP_14.0.0.0_X/install_scripts/bin to /var/mcp/install directory

• Copy installprops.txt, Staging_A2E-Demo_Small.tags and Staging_A2E-Demo_Small.xml in /var/mcp/loads/MCP_14.0.0.0_X/install_scripts/data to /var/mcp/install directory

• Populate installprops.txt by hand or with script populateInstallpropsFile.pl

• Populate Staging_A2E-Demo_Small.tags by hand or script populateTagsFile.pl

• Execute ./oracleInstall.pl it will install Oracle software to demo laptop

• After oracle install run ./mcpInstall.pl –p installprops.txt –i Staging_A2E-Demo_Small.xml –t Staging_A2E-Demo_Small.tags, this will install MCP in your laptop.

3) Installing MAS on A2E Platform

• Place Setup_linux_platform_14.0.0.30_2009.12.01.bin load in /var/mcp/loads directory with root rights
• chmod 777 Setup_linux_platform_14.0.0.30_2009.12.01.bin for execute right
• ./ Setup_linux_platform_14.0.0.30_2009.12.01.bin
• Accept license agreement and wait till installer ends its job
• Hit Enter to finalize the setup
• After that you need to install other bin files like Setup_linux_Crbt_14[1].0.0.30_2009.12.01.bin etc. with the same method above.

On A2E system, MAS and MCP cannot have the same IP address. Demo laptop has only one ethernet interface. You need to add second IP address to this interface so MAS can use that.

To do that,

# ifconfig eth0:0 192.168.54.17 netmask 255.255.254.0 up

# vim /etc/sysconfig/network-scripts/ifcfg-eth0:0

Add following lines in this script to make this eth0:0 permanent (hey, remember these are my IPs, you should use yours instead)

DEVICE=eth0:0

BOOTPROTO=static

BROADCAST=192.168.55.255

IPADDR=192.168.54.17

NETMASK=255.255.254.0

NETWORK=192.168.54.0

ONBOOT=yes

4) Installing VMware Server on A2E Platform

Standart A2E platform has many rpm files and tools installed, however some basic tools and packets do not exist which are available in other Red Hat release by default. So we need to add some rpm packets by hand. You need to get following 2 packets for installing VMware server.

· make-3.81-1.1.x86_64.rpm

· VMware-server-2.0.1-156745.x86_64.rpm

Then, install them

# rpm -ivh make-3.81-1.1.x86_64.rpm
# rpm -ivh VMware-server-2.0.1-156745.x86_64.rpm

If all rpm installations were successful then we can configure vmware server settings. To do that execute,

# /usr/bin/vmware-config.pl

Follow directions to complete configuration. You need to pay attention 2 major thing in here. First you need to change installation directories and make them in /var/mcp partition (cause default values are small disk size in A2E disk layout). Second, you need to select a main ethernet interface for all bridge connections (it should be eth0)

After configuration is done, you can access vmware server gui via your browser. https://192.168.54.16:8333

You can login with your root/password. After this point you can resume with PLE3 installation

5) Installing A2E BCP Platform on VMware Server

A2E BCP platform requires 40GB of disk space and 2 NICS. You need to create your VM with this specs to avoid any interuption during installation procedure. 40GB of disk space quite large if you use a laptop but remember this not a dedicated space, it is the largest, so no harm to set disk space in 40GB in VMware server menu.

After boot from iso, you can follow OS installation guide and finish the installation. Remember RTP needs different IP than MCP and MAS platforms.

L2/L3 Emulation with WANem

How to Emulate a Long Distance Network Cloud with WANem

WANem is a very useful and strong open source network emulator if you'd like to emulate WAN environment in your LAN.

Download from http://wanem.sourceforge.net/ . It's live CD so need to install, just boot and go.

There is 2 type of emulation that i need to create. L3 (pure ip network emulation) and L2 (pure ethernet network emulation)

L3 emulation is quite easy to configure, you need a server/laptop that has at least 2 NICs. We will put this server/laptop between your source and destination and you will define WANem's IP as default GW for this 2 servers.

L2 emulation needs a special handling, cause remember this is pure L2, so you need to set you NICs as bridge.

To do that,

From the Console execute “exit2shell”

Make all interfaces up with,

ifconfig eth0 0.0.0.0 up
ifconfig eth1 0.0.0.0 up
ifconfig eth2 0.0.0.0 up
ifconfig eth3 0.0.0.0 up

Create a bridge-group interface:

brctl addbr br0

Add each interface to the bridge-group br0

brctl addif br0 eth0
brctl addif br0 eth1
brctl addif br0 eth2
brctl addif br0 eth3

Assigned an ip address to the bridge-group br0 for management

ifconfig br0 192.168.1.2 netmask 255.255.255.0

Add default route so you can manage the WANem box from another network

route add default gw 192.168.1.1

Start the tool again with the command “wanem”

I hope you find is useful

Typhoon Master

ESXi 3.5 on HS20 8678 with IDE Controller

How to Install VMWare ESXi 3.5 on IBM HS20 8678 Blade with IDE Controller

I was trying to install VMWare 3.5 on one of the 32bit servers of mine for Virtulization. As you know ESXi 4.0 is for 64bit CPUs and if you want to install VMware Hypervisor, you must use ESXi 3.5 or ESX 3.0 which is not free.

If you look at Hardware Compatibility List for 8678, you will find out ESXi 3.5 is not offically supported. That's correct, you cannot install ESXi 3.5 if you have IDE controller (if you have SCSI controller, you cannot install it but it is still be unsupported configuration).

I googled it in couple of websites, and i can say the solution that find is workin successfully.

Problem occurs when ESXi 3.5 OS try to find your Hard Drive Controller. It is giving an error that setup cannot find any hard drive controller.

The exact error is,

Installation operation Failed!

The installation operation has encountered a fatal error: Unable to find a supported device to write the VMware ESX Server 3i 3.5.0 image to.

Ok if you have this error, following workaround maybe a solution for you as well.

You need to reach ESXi's console by hitting ALT-F1 during that error screen. You need to access ESXi's console so you change some pre installation scripts by hand and make the problem gone.

You'll be prompted for a login, type root, just hit enter for password.

lspci for determinate what type of controller that you have

Mine is CSB5 IDE Controller, now you need figure that out that this soulution is solving your problem or not. To figure that out,

fdisk -l

If any outputs, you're ready for the next step, otherwise you might have one the unsupported controller types.

i.e. CSB6 RAID/IDE Controller (i couldn't make it work)

The next step is changing /usr/lib/vmware/installer/Core/TargetFilter.py file with vi

You need to search for def IDEFilter(lun) and change

return interface.GetInterfaceType() == ScsiInterface.SCSI_IFACE_TYPE_IDE

to

return interface.GetInterfaceType() == ScsiInterface.SCSI_IFACE_TYPE_ISCSI

:wq

After that you should install command by typing "install" in console. It will bring you ALT-F2, you need to ALT-F1 again to access console again. You will see (Enter Install) screen, press Enter then F11 for license confirmation. If everything is ok, you should see your driver in screen Select a Disk, Select your disk and Enter for continue.

That's it.

I hope you find it useful. For further info, check this site http://vm-help.com/esx/esx3i/ESXi_install_to_IDE_drive/ESXi_install_to_IDE_drive.php

Typhoon Master

Basic virt-install command for installing Paravirtual DomU with KS file

Basic virt-install command for installing Paravirtual DomU with KS file

#This is basic virt-install command for installing Paravirtual DomU with KS file, this command is very picky so just c/p don't mess around

virt-install --paravirt --name vFC6-3 --ram 512 --file /var/lib/xen/images/vFC6-3.img --file-size 10 --nographics --location ftp://192.168.1.13/xen --extra-args="console=xvc0

ip=192.168.1.215 netmask=255.255.255.128 gateway=192.168.1.129

dns=192.165.149.1 ks=http://192.168.1.13/catt_fc6.ks.cfg"

Basic Paravirtual Virtual DomU XML Configuration

Basic ParaVirtual DomU XML Configuration

#This is a basic Paravirtual DomU XML
<domain type='xen'>
<name>vA2E-0</name>
<uuid>a6469aa9-c50c-339a-f68d-3888cbc54ebc</uuid>
<memory>4188160</memory>
<currentMemory>4188160</currentMemory>
<vcpu>2</vcpu>
<bootloader>/usr/bin/pygrub</bootloader>
<os>
<type arch='x86_64' machine='xenpv'>linux</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<disk type='file' device='disk'>
<driver name='tap' type='aio'/>
<source file='/var/lib/xen/images/vA2E-0.img'/>
<target dev='xvda' bus='xen'/>
</disk>
<interface type='bridge'>
<mac address='00:16:36:4b:07:d3'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
</interface>
<console type='pty'>
<target port='0'/>
</console>
<input type='mouse' bus='xen'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
</devices>
</domain>

Basic Full Virtual DomU XML Configuration

This is a Full Virtual DomU XML Configuration file


#This is a Full Virtual DomU XML

<domain type='xen'>

<name>vA2E-0</name>

<uuid>971402c5-6275-0005-c2a2-fb9142f7adf9</uuid>

<memory>4188160</memory>

<currentMemory>4188160</currentMemory>

<vcpu>2</vcpu>

<os>

<type arch='x86_64' machine='xenfv'>hvm</type>

<loader>/usr/lib/xen/boot/hvmloader</loader>

<boot dev='hd'/>

</os>

<features>

<acpi/>

<apic/>

<pae/>

</features>

<clock offset='utc'/>

<on_poweroff>destroy</on_poweroff>

<on_reboot>restart</on_reboot>

<on_crash>restart</on_crash>

<devices>

<emulator>/usr/lib64/xen/bin/qemu-dm</emulator>

<disk type='file' device='disk'>

<driver name='file'/>

<source file='/var/lib/xen/images/vA2E-0.img'/>

<target dev='hda' bus='ide'/>

</disk>

<disk type='block' device='cdrom'>

<driver name='phy'/>

<target dev='hdc' bus='ide'/>

<readonly/>

</disk>

<interface type='bridge'>

<mac address='00:16:36:0c:7a:c2'/>

<source bridge='xenbr0'/>

<script path='vif-bridge'/>

</interface>

<serial type='pty'>

<target port='0'/>

</serial>

<console type='pty'>

<target port='0'/>

</console>

<input type='mouse' bus='ps2'/>

<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>

</devices>

</domain>


Basic virt-p2v Configuration

After a successful P2V conversion with virt-p2v Live CD, you might need to re-define your new Virtual Machine, to do that, copy one of the XML config file below and define your img with "virsh define config.cfg"


#virt-p2v quiet usefull program but its cfg file needs to be fixed

#This is for Physical to Full Virtualization

<domain type='xen' id='5'>

<name>Deneme1</name>

<uuid>78f732b0-320a-b9bd-749d-053b37968512</uuid>

<memory>1048576</memory>

<currentMemory>1048576</currentMemory>

<vcpu>1</vcpu>

<os>

<type>hvm</type>

<loader>/usr/lib/xen/boot/hvmloader</loader>

<boot dev='hd'/>

</os>

<features>

<acpi/>

<apic/>

<pae/>

</features>

<clock offset='utc'/>

<on_poweroff>destroy</on_poweroff>

<on_reboot>restart</on_reboot>

<on_crash>restart</on_crash>

<devices>

<emulator>/usr/lib64/xen/bin/qemu-dm</emulator>

<disk type='file' device='disk'>

<driver name='file'/>

<source file='/var/lib/xen/images/p2v-localhost_localdomain-200909291050-hda.img'/>

<target dev='hda' bus='ide'/>

</disk>

<disk type='file' device='cdrom'>

<target dev='hdc' bus='ide'/>

<readonly/>

</disk>

<interface type='bridge'>

<mac address='00:16:3e:80:bd:48'/>

<source bridge='xenbr0'/>

<script path='vif-bridge'/>

<target dev='vif5.0'/>

</interface>

<serial type='pty'>

<source path='/dev/pts/1'/>

<target port='0'/>

</serial>

<console type='pty' tty='/dev/pts/3'>

<source path='/dev/pts/3'/>

<target port='0'/>

</console>

<input type='mouse' bus='ps2'/>

<graphics type='vnc' port='5905' autoport='yes' keymap='en-us'/>

</devices>

</domain>

#This is for Physical to ParaVirtualization, Physical server should be set as Xen Kernel-ed before convertion

<domain type='xen'>

<name>vA2E-0</name>

<uuid>99f969f4-1023-e1ee-8d0f-0b016fd2b166</uuid>

<memory>4194304</memory>

<currentMemory>4194304</currentMemory>

<vcpu>2</vcpu>

<bootloader>/usr/bin/pygrub</bootloader>

<os>

<type arch='x86_64' machine='xenpv'>linux</type>

<kernel>/var/lib/xen/boot_kernel.CpFtTy</kernel>

<initrd>/var/lib/xen/boot_ramdisk.QOTH_r</initrd>

<cmdline>ro root=/dev/VolGroup00/LogVol00 console=xvc0 rhgb quiet</cmdline>

</os>

<clock offset='utc'/>

<on_poweroff>destroy</on_poweroff>

<on_reboot>restart</on_reboot>

<on_crash>restart</on_crash>

<devices>

<disk type='file' device='disk'>

<driver name='tap' type='aio'/>

<source file='/var/lib/xen/images/vA2E-0.img'/>

<target dev='xvda' bus='xen'/>

</disk>

<interface type='bridge'>

<mac address='00:16:36:4b:d5:d0'/>

<source bridge='xenbr0'/>

<script path='vif-bridge'/>

<target dev='vif49.0'/>

</interface>

<serial type='pty'>

<source path='/dev/pts/1'/>

<target port='0'/>

</serial>

<console type='pty'>

<target port='0'/>

</console>

<input type='mouse' bus='ps2'/>

<graphics type='vnc' port='5905' autoport='yes' keymap='en-us'/>

</devices>

</domain>


I hope you find it useful

Typhoon Master

Xen on RHEL 5.4

XEN on RHEL

When i was messing with Virtualization with Xen Kernel on RHEL 5.4, i took some notes myself, i'd like to share with you maybe it will be useful for you as well. I've googled thousands of webpages to get answers for my questions and i bind them all in couple of scripts.

Here you go,

#Installing Xen kernel in a non-Xen-awared OS, OS can be operated as Hypervisor/Dom0 after this step
yum install xen kernel-xen
#Install recommended virtualization packages (you need a GUI for VMM, so if you have one, please install with yum groupinstall "X Window System" "GNOME Desktop Environment")
yum install virt-manager libvirt libvirt-python python-virtinst
#You need to edit grub.conf for making Xen Kernel the default kernel
vim /etc/grub.conf
#Reboot with new Xen Kernel
reboot
#Ok we need Vnc access so, edit xstartup file and add "gnome-session &"
vim /root/.vnc/xstartup


#Other "need to know" stuff here
#Your local FTP directory should be like D:\ftp\xen\xen\images, ISO should be exracted in D:\ftp\xen\xen\ directory, you need to set all permissions in you FTP Server
#You need to point your FTP Server as ftp://192.168.1.13/xen
#VMM is a good GUI program but what if you don't want to use GUI, so virt-install and virsh will be the best option for you
#Some basic command examples,
#virt-install --prompt |for basic installation, if VMM stuck and doesn't install your OS, try this one
#virt-install \
--paravirt \
--name demo \
--ram 500 \
--file /var/lib/xen/images/demo.img \
--file-size 6 \
--nographics \
--location ftp://192.168.1.13/xen
#This is basic virt-install command for installing Paravirtual DomU with KS file
virt-install \
--paravirt \
--name demo \
--ram 512 \
--file /var/lib/xen/images/demo.img \
--file-size 6 \
--nographics \
--location ftp://192.168.1.13/xen \
--extra-args="console=xvc0 ip=192.168.1.215 netmask=255.255.255.128 gateway=192.168.1.129 dns=192.165.149.1 ks=ftp://192.168.1.13/catt_fc6.ks.cfg"
#virsh list
#virsh console DomU
#virsh autostart DomU
#virsh define DomUXML.cfg
#Basic Full Virtual DomU XML
<domain type='xen'>
<name>vA2E-0</name>
<uuid>971402c5-6275-0005-c2a2-fb9142f7adf9</uuid>
<memory>4188160</memory>
<currentMemory>4188160</currentMemory>
<vcpu>2</vcpu>
<os>
<type arch='x86_64' machine='xenfv'>hvm</type>
<loader>/usr/lib/xen/boot/hvmloader</loader>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
<disk type='file' device='disk'>
<driver name='file'/>
<source file='/var/lib/xen/images/vA2E-0.img'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='block' device='cdrom'>
<driver name='phy'/>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='00:16:36:0c:7a:c2'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
</devices>
</domain>
#Basic Paravirtual DomU XML
<domain type='xen'>
<name>vA2E-0</name>
<uuid>a6469aa9-c50c-339a-f68d-3888cbc54ebc</uuid>
<memory>4188160</memory>
<currentMemory>4188160</currentMemory>
<vcpu>2</vcpu>
<bootloader>/usr/bin/pygrub</bootloader>
<os>
<type arch='x86_64' machine='xenpv'>linux</type>
</os>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<disk type='file' device='disk'>
<driver name='tap' type='aio'/>
<source file='/var/lib/xen/images/vA2E-0.img'/>
<target dev='xvda' bus='xen'/>
</disk>
<interface type='bridge'>
<mac address='00:16:36:4b:07:d3'/>
<source bridge='xenbr0'/>
<script path='vif-bridge'/>
</interface>
<console type='pty'>
<target port='0'/>
</console>
<input type='mouse' bus='xen'/>
<graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/>
</devices>
</domain>

I hope you find it usefull

Typhoon

How to install Samba Server on Debian

NFS could be the best solution for file transfering and disk mounting between Unix and Windows systems. However it has special protocol and because of that it needs extra program installation in Windows side.

Samba does not require any special attention, it uses very common protocol which called Netbios (this is the main difference between Samba and NFS, NFS uses it own protocol) which used by Windows systems for file and print sharing (it support dozens of protocols but it is out of our scope right now)

Samba installation and commissioning is easy like NFS and other programs on Debian based system (that's why i like Debian distro so much)

Just follow step for a basic Samba server installation,

1) apt-get install samba smbfs

Ok it's done, installed, now we need to creat a samba password (you can also create a special username for samba, but no harm if you use your exisiting users)

2) smbpassword

Set you samba password as you desired, then we should make some changes in config file for accessing correct path and security.

3) vi /etc/samba/smb.conf

First you can limit access to your Samba server with "hosts allow = 192.168.1.3 ". It means only 192.168.1.3 can access Samaba server. You should put this line under "Networking" section.

And add your home directory as,

[sharename] comment = Insert a comment here path = /home/share/ valid users = tfox carole public = no writable = yes printable = no create mask = 0765

Finally you need to restart samba service for commiting setting above.

"/etc/init.d/samba restart"

If everything is ok you can access to your /home/share in Linux machine from you Windows machine using Start-Run-

"\\192.168.1.100"

It will ask you about authentication info, write your username and password (samba password) to login and access directories that you allowed to browse.

That's all, I hope it will work for you too.

Cheers

Typhoon Master

How to install a NFS server on Debian

How to install a NFS server on Debian

NFS (Network File System) is must if you'd like to share your storage capacity through IP network. It's easy to build easy to configure. Just follow the steps below.

1) Run apt-get install nfs-kernel-server nfs-common portmap

2) Then edit /etc/exports as following

# /etc/exports: the access control list for filesystems which may be exported

# to NFS clients. See exports(5).

#

# Example for NFSv2 and NFSv3:

# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)

#

# Example for NFSv4:

# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)

# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)

/media/sdb 192.168.1.10(rw,sync,no_root_squash)

Line in red indicates your NFS server's share point directory, access granted IP and permissions. wq exports file.

3) You need to commit your changes with following command

exportfs -a

That's all you can mount your NFS client to your new NFS server.

Cheers

Typhoon Master

How to clone your disk with G4L

How to clone your disk with G4L

In this tutorial i'm going to explain 2 different methods for clonning your disk with using G4L. Actually this is quite simple and powerful tool to use, maybe you think this tutorial is unnecessary.

1) Entire disk clone with FTP

2) Entire disk clone to a local disk

1) Cloning your disk to a FTP server

Cloning your disk to a network disk is absolutely necessary if you don't any usb storage or a second disk in your server. It takes time due your network connection speed and hardware you have. If you're using SCSI disks like me speed should satisfy your needs. Cause SCSI disks is not large as IDE, SATA or SAS disks and it effects transfering time as you imagine.

I found only one trick so just gonna explain that one,

When i put static IP from GUI that G4L provide, i couldn't access to my network b/c it doesn't ask my netmask or gw info, so i give this info to G4L from shell with following commands

# ifconfig eth0 192.168.1.10 netmask 255.255.255.0

#route add default gw 192.168.1.1

After that you can your connectivity via ping you default gw and different subnet that routed. If you pings are successful you ready to go to G4L GUI

# g4l

You're gonna need to select raw mode for clonning everthing, GUI will ask you about IP address of your FTP server, FTP directory, FTP Server authentication username and password info. After fill all this up, you need to seleck backup and then proceed. Other options can be stay as default.

2) Cloning your disk to a Local Disk

It is easiest and probably the fastest way to clone your disk. You don't need to set your network connection like FTP example above you just go to raw mode and sleect click n clone. It will ask you which disk is going to be cloned to which disk after setting this you ready to go. It doesn't matter disk sizes and speed are different.

I hope you find it useful

Cheers

Typhoon Master

Installing ESXi/vCenter/vSphere Client on /x32x64 Server/WinXP

First of all, i gotta warn you this is not tutorial about how to install VMWare components but it is about its architecture.

I have couple of x32 Xeon based servers sitting in my Lab, i'd like them to turn into something more handy and powerful. That's because i started to research about how to combine and bind them in a Virtual machine like a Cloud Computing environment.

VMware offers what i'm looking for but there is some problems with my x32 based CPUs. VMware only supports 32bit servers with ESXi 3.5 without a license, however my servers are not supported that version of ESXi, my servers supported by ESX 3.x.x which are license required, so i had to give up and go with VMware Server 2.0 and it fits well nad i gotta say my RHEL5 OS can compute with ESXi's memory comsumption with a good way.

Then i tried out ESXi 4.0 in a x64 server, actually i created a cluster with 2 servers and put a vCenter one of my Windows XP PCs, it worked as charmed. You can manage your servers one by one via vSphere Client, or as i've done, you install a vCenter and connect it via vSphere Client and manage all the host server from there.

I'll update this post

Typhoon Master

How to install VMware Server 2.0 on RHEL5

VMware products are very well documented and easy to use, cause of this i'm not going to explain all the installation that i've done but share some tricks with you.

- My RHEL5 server has dual NICs and it has bond0 as a network interface, after installing vmware server wit rpm -ivh VMware-server-2.0.1-156745.i386.rpm , you're going to need to configure it with vmware-config.pl and this perl scripts guide to configure host server system. I didn't realize it offered mt eth0 as primary NIC and i had some trouble with accessing network from guest OS, then i realize i didn't pick the correct NIC, so please remember you need to select bond0 as your primary host NIC if you have more than 1 NIC on your server.

In additionally,

I had an idea that about installing VMware Server to my Sun N240 server which has Debian Sparc on it. Unfortunatly VMware server does not support Sparc CPU as virtulizer. However i installed the server but couldn't achieve start it because of the CPU. Keep that mind, VMware Server doesn't support Sparc or Power CPU architectures as virtualizer.

Cheers

Typhoon Master

How to install Bind9 as ENUM Server

How to install BIND9 as ENUM Server on Ubuntu

Why do you need an ENUM server?

ENUM server works like DNS server but it matches Phone number with SIP URI instead of IP and URL. Some IMS Core systems use this kind of resolutions.

Installing BIND9

I'm going to explain this for Ubuntu Server, it is quite easy to install but tricky to configure at the begining.

1) apt-get install bind9

2) After installation succefully completed, go to /etc/bind/ directory. You need to edit following files only.

named.conf

named.conf.options

named.conf.enum (actually we will create it in next step)

db.e164.arpa (actually we will create it in next step)

3) named.conf

add following line

include "/etc/bind/named.conf.enum";

4) named.conf.enum

add following line

zone "e164.arpa" {

type master;

file "/etc/bind/db.e164.arpa";

};

5) db.e164.arpa

$TTL 86400

e164.arpa. IN SOA ns.e164.arpa. root.e164.arpa. (

2004011522 ; Serial no., based on date

21600 ; Refresh after 6 hours

3600 ; Retry after 1 hour

604800 ; Expire after 7 days

3600 ; Minimum TTL of 1 hour

)

e164.arpa. 43200 IN NS ns.e164.arpa.

;

ns.e164.arpa. 43200 IN A 192.168.1.2

0.9.8.7.6.5.4.3.2.1.e164.arpa. NAPTR 10 100 "u" "E2U+sip" "!^.*$!sip:info@example.com!".

0.9.8.7.6.5.4.3.2.1.e164.arpa. NAPTR 10 101 "u" "E2U+h323" "!^.*$!h323:info@example.com!".

0.9.8.7.6.5.4.3.2.1.e164.arpa. NAPTR 10 102 "u" "E2U+msg" "!^.*$!mailto:info@example.com!".

8.1.2.7.5.9.3.3.1.6.1.e164.arpa. NAPTR 100 10 "U" "SIP+E2U" "!^.*$!sip:16133957218@example.com!".

6) named.conf.options

#logging {

# channel query-log {

# file "/var/log/query-log" versions 2 size 10m;

# print-time yes;

# print-category yes;

# };

# category queries { query-log; } ;

#};

#

#options {

# directory "/var/cache/bind";

// If there is a firewall between you and nameservers you want

// to talk to, you might need to uncomment the query-source

// directive below. Previous versions of BIND always asked

// questions using port 53, but BIND 8.1 and later use an unprivileged

// port by default.

// query-source address * port 53;

// If your ISP provided one or more IP addresses for stable

// nameservers, you probably want to use them as forwarders.

// Uncomment the following block, and insert the addresses replacing

// the all-0's placeholder.

// forwarders {

// 0.0.0.0;

// };

# auth-nxdomain no; # conform to RFC1035

#

#};

7) You need to restart bind service

/etc/init.d/bind9 restart

8) Now you can query your request with dig tool

dig @ 8.1.2.7.5.9.3.3.1.6.1.e164.arpa -t NAPTR

You suppose to get following answer

;; ANSWER SECTION:

8.1.2.7.5.9.3.3.1.6.1.e164.arpa. 86400 IN NAPTR 100 10 "U" "SIP+E2U" "!^.*$!sip:16133957218@example.com!" .

I hope you find it useful

Typhoon Master