Copyright (c) 2023, Oracle. All rights reserved. Oracle Confidential.

ODA (Oracle Database Appliance): How To Configure bond1 post deploy on V2/V3/V4 (Doc ID
1616564.1)

In this Document

Goal
Solution
  How To Configure bond1 post deploy manual mode
  1. Backup your current NIC (bond) configurations:
  2. Edit NIC bond configuration file adding your IP informations (IPaddress, Netmask & Gateway)
  3. Activate the new configuration doing
  4. Verify your configuration using the command ifconfig
  How To Configure bond1 post deploy using ODA Configuration Manager
  1. ODA Manager
  2. Custom type configuration
  3. Other Network screen
  4. save the new deploy
  5. check your settings
  6. Run deploy steps 3,1,24
References

APPLIES TO:

Oracle Database Appliance Software - Version 2.5.0.0 and later

Information in this document applies to any platform.

GOAL

You have executed the ODA deploy without setting up the bond1 network interface. Now for several reasons (backup,
middle-ware client connections, application client connections, ...) you need to configure it.
 

SOLUTION

Note: Starting with OAK version 12.1.2.3.0 a new command has been added to configure additional network:

oakcli configure additionalnet

Hence you don't need to follow the steps below anymore.

Note: adding a new "network" the default gateway will be the gateway configured in the latest eth device that come
up. For this reason you could loose connectivity on the previous network setup. In such case you need to take care for
the routing table and you should specify them in "/etc/sysconfig/network-scripts/route-<eth name>" to keep
them permanet after a reboot.

How To Configure bond1 post deploy manual mode

 mkdir -p /etc/sysconfig/network-scripts/ifcfg-backup

-- bond1: eth4/5 - NET2/NET3

cp /etc/sysconfig/network-scripts/ifcfg-bond1 /etc/sysconfig/network-scripts/ifcfg-backup/ifcg-
bond1

2. Edit NIC bond configuration file adding your IP informations (IPaddress, Netmask & Gateway)

bond1: eth4 & eth5

/etc/sysconfig/network-scripts/ifcfg-bond1

DEVICE=bond1
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
TYPE=BOND
IPADDR=10.xxx.10.101
NETMASK=255.xxx.255.0
GATEWAY=10.xxx.10.1

The eth4 & eth5 configuration file are as following (no changes are needed)

# cat /etc/sysconfig/network-scripts/ifcfg-eth4
DEVICE=eth4
USERCTL=no
ONBOOT=yes
MASTER=bond1
SLAVE=yes
BOOTPROTO=none
HWADDR=<MAC ADDRESS>

# cat /etc/sysconfig/network-scripts/ifcfg-eth5
DEVICE=eth5
USERCTL=no
ONBOOT=yes
MASTER=bond1
SLAVE=yes
BOOTPROTO=none
HWADDR=<MAC ADDRESS>

3. Activate the new configuration doing

# ifdown bond1
# ifup bond1

4. Verify your configuration using the command ifconfig

The same actions with different IP address should be done on node 2 (if needed)

How To Configure bond1 post deploy using ODA Configuration Manager

1. ODA Manager

Run the ODA Configuration Manager executing the followings to generate the configuration files

/opt/oracle/oak/bin/oakcli deploy config -conf /opt/oracle/oak/onecmd/onecommand.params

Note: The onecommand.params file is compatible only with the Oracle Appliance Manager Configurator version that
was used to generate it. If you updated oak after the initial deployment then you should generate
 onecommand.params with the corresponding Configurator

2. Custom type configuration

From ODA Configuration Manager choose custom type :

3. Other Network screen

Go to the "Other Network" screen and complete the network addresses for the network interface you need to set up
(bond1)
4. save the new deploy

save the deploy configuration as

/opt/oracle/oak/onecmd/onecommand.params

5. check your settings

You can verify your setting doing:

cat /opt/oracle/oak/onecmd/onecommand.params| grep NET1

i.e.:# cat /opt/oracle/oak/onecmd/onecommand.params| grep NET1

NET1_IPS=(10.xxx.10.101 10.xxx.10.102)
NET1_NETMASK=255.xxx.255.0
NET1_GATEWAY=10.xxx.10.1
NET1_NAME=bond1
NET1_HOSTNAME=(oda11 oda12)

6. Run deploy steps 3,1,24

Run the deploy step 3 (SetupSSHroot), 1 (SetupNetwork), 24 (ResecureMachine) running:

/opt/oracle/oak/onecmd/GridInst.pl -s 3
/opt/oracle/oak/onecmd/GridInst.pl -s 1
/opt/oracle/oak/onecmd/GridInst.pl -s 24

 
 Note1: in some OAK version the step 24 (ResecureMachine) could be 23. Please check the right step number using
/opt/oracle/oak/onecmd/GridInst.pl -l    (if running on BareMetal)
/opt/oracle/oak/onecmd/GridInst.pl -l -o (if running on Virtualized Platform)

Note2: GridInst.pl will setup your network (bond1) on both nodes.

Also in this case, like the command "/opt/oracle/oak/bin/oakcli configure firstnet", will restart the network doing a
"service network restart", then there will be a brief interruption to the current connected users to the system (if the IP
which was being used for connection is not being changed).

REFERENCES
NOTE:1422563.1 - ODA (Oracle Database Appliance): How To Configure xbond,bond1,bond2 on ODA V1 post deploy
NOTE:1500709.1 - ODA (Oracle Database Appliance): Enable 8021.Q VLAN Tagged Interfaces for external client access
networks
NOTE:1501039.1 - ODA (Oracle Database Appliance): HowTo Configure Multiple Public Network on GI (Grid Infrastructure)
11gR2
Didn't find what you are looking for?