Configuring AdminServer for HA

 

1. Check the current Network Configuration

[root@test1 u01]# ifconfig -a
ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.131.200 netmask 255.255.255.0 broadcast 192.168.131.255
inet6 fe80::250:56ff:feab:e4e prefixlen 64 scopeid 0x20<link>
ether 00:50:56:ab:0e:4e txqueuelen 1000 (Ethernet)
RX packets 56594631 bytes 22936153585 (21.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 36468224 bytes 17952810300 (16.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 14801297 bytes 19196705914 (17.8 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14801297 bytes 19196705914 (17.8 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:0a:f0:7c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)

 

 

2. Below is the IP that will be used for VIP

============================
192.168.131.203 will be used for VIP
============================

 

3. Go to the Interfaces and create a duplicate interface and change the necessary settings

[root@test1 u01]# cd /etc/sysconfig/network-scripts/
[root@test1 network-scripts]# cp ifcfg-ens34 ifcfg-ens34:1

vi ifcfg-ens34:1

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=eui64
NAME=ens34:1 —> Modified
UUID=de6258be-0a59-44c1-aaaa-1425f31455ce
DEVICE=ens34:1 —> Modified
ONBOOT=yes
IPADDR=192.168.131.203 —> Modified
PREFIX=24
GATEWAY=192.168.131.254
DNS1=192.168.1.10
IPV6_PEERDNS=no
IPV6_PEERROUTES=no
PEERDNS=no

 

4. Start the newly created Interface

[root@test1 network-scripts]# ifup ifcfg-ens34:1
WARN : [ifup] You are using ‘ifup’ script provided by ‘network-scripts’, which are now deprecated.
WARN : [ifup] ‘network-scripts’ will be removed in one of the next major releases of RHEL.
WARN : [ifup] It is advised to switch to ‘NetworkManager’ instead – it provides ‘ifup/ifdown’ scripts as well.

 

5. Check the Network Configuration again you will find the Virtual Interface

[root@test1 network-scripts]# ifconfig -a
ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.131.200 netmask 255.255.255.0 broadcast 192.168.131.255
inet6 fe80::250:56ff:feab:e4e prefixlen 64 scopeid 0x20<link>
ether 00:50:56:ab:0e:4e txqueuelen 1000 (Ethernet)
RX packets 56596251 bytes 22936260848 (21.3 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 36468470 bytes 17952847128 (16.7 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens34:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.131.203 netmask 255.255.255.0 broadcast 192.168.131.255
ether 00:50:56:ab:0e:4e txqueuelen 1000 (Ethernet)

 

 

6. Do the same on Node 2 but move the files on /root folder to not start it up on the server boot

[root@test2 ~]# cd /etc/sysconfig/network-scripts/
[root@test2 network-scripts]# ls -l ifcfg-ens34
-rw-r–r–. 1 root root 358 Oct 28 11:12 ifcfg-ens34
[root@test2 network-scripts]# cp ifcfg-ens34 ifcfg-ens34:1
[root@test2 network-scripts]# vi ifcfg-ens34:1
[root@test2 network-scripts]# mv ifcfg-ens34:1 /root/

 

7. Configuring AdminServer for using the virtual IP Address

In the next step we will configure the AdminServer to be able to use the virtual ip address already configured in the previous steps: 192.168.131.203

We can execute these steps either in the AdminConsole or via editing the File $DOMAIN_HOME/config/config.xml. The second way is not supported by Oracle. We will try this via AdminConsole:

a. Connect to the AdminConsole http://192.168.131.200:7001/console and change to the Domain Tree, then to Servers and AdminServer.
b. Lock and Edit
c. Change the Listen Address to 192.168.131.203 (VIP)
d. Save the configuration, press Button “Activate Changes”

 

 

8. Restart the AdminServer.

The AdminServer is now configured to use the virtual IP Address 192.168.131.203.

 

 

9. Access the AdminConsole now via the virtual IP.

http:// 192.168.131.203:7001/console