Database Reference
In-Depth Information
[root@oevm1 ~]#
grep IPADDR /etc/sysconfig/network-scripts/ifcfg-eth0
IPADDR=10.177.0.63
[root@oevm1 ~]#
vi /etc/sysconfig/network-scripts/ifcfg-eth0
[root@oevm1 ~]#
grep IPADDR /etc/sysconfig/network-scripts/ifcfg-eth0
IPADDR=10.177.0.64
[root@oevm1 ~]#
reboot
8.
You also want to mount the
/cloudfs
from the other Virtual IP on the new VM, so you
need to adjust your
/etc/fstab
file and remount the ACFS file system on oevm2.
For example:
[root@oevm2 ~]#
grep cloudfs /etc/fstab
s1-vip:/cloudfs /cloudfs nfs rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,
nfsvers=3,tcp,nolock,acregmin=0,acregmax=0 0 0
[root@oevm2 ~]#
vi /etc/fstab
[root@oevm2 ~]#
grep cloudfs /etc/fstab
s2-vip:/cloudfs /cloudfs nfs rw,intr,bg,hard,timeo=600,wsize=32768,rsize=32768,
nfsvers=3,tcp,nolock,acregmin=0,acregmax=0 0 0
[root@oevm2 ~]#
umount /cloudfs
[root@oevm2 ~]#
mount /cloudfs
9.
Lastly, you can start the first VM too because the conflicting configuration has been
removed. (See the following example). Once started, you should check that the virtual IP
(10.177.0.60 in this example is configured on oevm2) is managed and started on one of the
VMs. You can also test how
keepalived
manages the virtual IP by stopping and starting its
service (use
service keepalived stop
and
service keepalived start
to do it) on the
hosts. The IP will always be allocated to one of the VMs the
keepalived
is running on.
[root@s1 ~]#
oakcli start vm oevm1
Started VM : oevm1
[root@s1 ~]#
oakcli show vm
NAME MEMORY VCPU STATE REPOSITORY
oevm1 12288 4 ONLINE odarepo1
oevm2 12288 4 ONLINE odarepo2
[root@oevm1 ~]#
ip addr list dev eth0 | grep "inet "
inet 10.177.0.63/16 brd 10.177.255.255 scope global eth0
[root@oevm2 ~]#
ip addr list dev eth0 | grep "inet "
inet 10.177.0.64/16 brd 10.177.255.255 scope global eth0
inet 10.177.0.60/32 scope global eth0
You have two-application tier VMs now, but only one of them is configured with e-Business Suite. The final step
to complete the e-Business Suite application tier configuration on ODA is to enable the services on the second VM.
This is covered in the next section.
