1. Installation and Configuration Guide for Exadata Database Machine
  2. OEDA Command Line Interface
  3. OEDACLI Command Reference
  4. COMPUTE
  5. CLONE COMPUTE

4.3.6.1 CLONE COMPUTE

Use this command to clone an existing physical compute cluster node.

Syntax

CLONE COMPUTE
   { SRCNAME=source_compute_node TGTNAME=target_compute_node | 
     TGTNAMES=target_compute_nodes }
[ WHERE 
     STEPNAME=stepname ]
SET ADMINNET NAME=admin_name IP=admin_ip
SET PRIVNET NAME1=priv_name_1 IP1=priv_ip1 [ NAME2=priv_name_2 IP2=priv_ip2 ]
[ SET INTERCONNECT NAME1=priv_name_1 IP1=priv_ip1 [ NAME2=priv_name_2 IP2=priv_ip2 ] ]
[ SET CLIENTNET NAME=client_name IP=client_ip ]
[ SET VIPNET NAME=vip_name IP=vip_ip ]
[ SET BACKUP NAME=backup_name IP=backup_ip ]
SET ILOMNET NAME=ilom_name IP=ilom_ip
SET RACK NUM=rack_number ULOC=ulocation

Arguments

  • SRCNAME: Specifies the name of an existing compute server from which the compute server is derived.

  • TGTNAME: Specifies the name of the new compute server to add.

  • TGTNAMES: Specifies a comma-separated list of new compute servers to add.

  • STEPNAME: Optionally specifies the deployment step to perform, which is one of the following:

    • CREATE_USERS
    • CELL_CONNECTIVITY
    • ADD_NODE
    • EXTEND_DBHOME
    • ADD_INSTANCE

    If STEPNAME is not specified, then all steps are performed.

You can set the following options for a cloned compute node:

  • ADMINNET : Specifies the DNS name and IP address to use for the administration network. The DNS name may optionally include the domain name.

  • PRIVNET : Specifies the names and IP addresses to use for the first and second private networks. The names may optionally include the domain name.

  • INTERCONNECT: Only required if the compute nodes are configured with Exadata Secure RDMA Fabric Isolation or InfiniBand security (PKEYS). Specifies the names and IP addresses to use for the first and second private networks. The names may optionally include the domain name.

  • CLIENTNET : Specifies the DNS name and IP address to use for the client network. The DNS name may optionally include the domain name. Not required on virtual machine (VM) hosts (Oracle Linux KVM or Oracle VM).

  • VIPNET : Specifies the DNS name and IP address to use for the virtual IP (VIP) network. The DNS name may optionally include the domain name. Not required on virtual machine (VM) hosts (Oracle Linux KVM or Oracle VM).

  • BACKUP : Specifies the DNS name and IP address to use for the backup network. The DNS name may optionally include the domain name. Not required on servers without a backup network.

  • ILOMNET: Specifies the DNS name and IP address to use for the ILOM network. The DNS name may optionally include the domain name.

  • RACK : Specifies the rack number in a multi-rack configuration, where 1 is the first rack, and the physical location (slot number) of the server in the rack.

Usage Notes

  • For configurations with Exadata Secure RDMA Fabric Isolation or InfiniBand security (PKEYS), INTERCONNECT defines the private network that connects the database nodes and PRIVNET defines the private storage network.

  • Use TGTNAMES to clone multiple compute servers simultaneously in the DEPLOY ACTIONS. Use TGTNAMES without additional SET statements. Use SAVE ACTION FORCE prior to using this argument. See the example below.

Example 4-11 Cloning a Compute Node

This example clones the dbadm13 compute server to a new server, dbadm14. 

CLONE COMPUTE srcname=dbadm13 tgtname=dbadm14
SET ADMINNET name=dbadm04 ip=10.128.161.192
SET PRIVNET name1=dbadm04-priv1 ip1=192.168.161.195 name2=dbadm04-priv2 ip2=192.168.161.196
SET CLIENTNET name=dbadm04-client ip=198.51.100.112
SET VIPNET name=dbadm04-vip ip=10.128.177.116
SET ILOMNET name=dbadm04-ilom ip=10.128.161.203
SET RACK num=1 uloc=17

SAVE ACTION
MERGE ACTIONS
DEPLOY ACTIONS

Example 4-12 Cloning Multiple Compute Nodes Using TGTNAMES

This example clones dbadm23 and creates the new compute servers dbadm24 and dbadm25. By using the TGTNAMES argument, both new nodes are deployed at the same time in the final DEPLOY ACTIONS. 

CLONE COMPUTE SRCNAME='dbadm23' TGTNAME='dbadm24'
SET ADMINNET name=dbadm24 ip=10.128.161.192
SET PRIVNET name1=dbadm24-priv1 ip1=192.168.161.195 name2=dbadm24-priv2 ip2=192.168.161.196
...
SAVE ACTION FORCE

CLONE COMPUTE SRCNAME='dbadm23' TGTNAME='dbadm25'
SET ADMINNET name=dbadm25 ip=10.128.161.193
...
SAVE ACTION FORCE

CLONE COMPUTE TGTNAMES='dbadm24,dbadm25'

SAVE ACTION
MERGE ACTIONS
DEPLOY ACTIONS

Example 4-13 Cloning a Compute Node Using Steps

This example clones the dbadm33 compute server to a new server, dbadm34, running individual steps. The example shows only the first three steps and does not show all the steps involved in cloning the compute node. 

CLONE COMPUTE srcname=dbadm33 tgtname=dbadm34 WHERE STEPNAME=CREATE_USERS
SET ADMINNET name=dbadm04 ip=10.128.161.192
SET PRIVNET name1=dbadm04-priv1 ip1=192.168.161.195 name2=dbadm04-priv2 ip2=192.168.161.196
SET CLIENTNET name=dbadm04-client ip=198.51.100.112
SET VIPNET name=dbadm04-vip ip=10.128.177.116
SET ILOMNET name=dbadm04-ilom ip=10.128.161.203
SET RACK num=1 uloc=17

SAVE ACTION
MERGE ACTIONS
DEPLOY ACTIONS

CLONE COMPUTE compute  srcname=dbadm33 tgtname=dbadm34 WHERE STEPNAME=CELL_CONNECTIVITY

SAVE ACTION
MERGE ACTIONS
DEPLOY ACTIONS

CLONE COMPUTE srcname=dbadm33 tgtname=dbadm34 WHERE STEPNAME=ADD_NODE

SAVE ACTION
MERGE ACTIONS
DEPLOY ACTIONS

...

Parent topic: COMPUTE