Use this procedure for MiniCluster systems running v1.2.2 or earlier. To determine your version, see List the MCMU Version (CLI).
Use one of these network interfaces to connect to the client access network:
Through the 10GbE NIC, using the first two ends of the four-ended splitter cable
Through the NET 2 and NET 3 ports
You can now configure additional networks on unused network interface slots for existing VMs, either in the same subnet or on a different subnet.
The network interface slots that are available for you to configure as an additional network depends on how your MiniCluster is connected to the client access network:
If your MiniCluster is connected through the 10GbE NIC, through a QSFP to 4x SFP+ or MPO to 4x LC duplex splitter cable – You have the first two ends of the splitter cable (labeled A and B, or 1 and 2) connected to the client access network through 10GbE switches. The following network interface slots are therefore available on both compute nodes for you to configure as additional networks:
The other two ends of the splitter cable (labeled C and D, or 3 and 4) connected to the 10GbE NIC
The NET 2 and NET 3 ports
If your MiniCluster is connected through the NET 2 and NET 3 ports – You are using those two ports on both compute nodes to connect to the client access network through 10GbE switches. The P 0 port (rightmost port, or port A) on the 10GbE NIC is therefore available for you to configure as additional networks. You can connect a QSFP to 4x SFP and SFP++ or an MPO to 4x LC duplex splitter cable to the P 0 port on the 10GbE NIC, which enables you to connect the four ends of the splitter cable (labeled A through D, or 1 through 4) to the additional network.
Refer to the Oracle MiniCluster S7-2 Installation Guide for more information on the connection options for the client access network.
Make one of the following pairs of connections to the additional network to provide high availability:
From the 10GbE NIC:
The first two ends of the splitter cable (A and B, or 1 and 2), if not already used to connect to the client network
The second two ends of the splitter cable (C and D, or 3 and 4)
From the NET 2 and NET 3 ports, if not already used to connect to the client network
Perform one of these commands:
In this example, the VMgroupID is 1.
% mcmu tenant -G -l Listing DB VM Group... Status : Active Description : VMgroupName : dbzg2 editable : True deletable : True progress : False VMgroupID : 1
In this example, the VMgroupID is 2.
% mcmu tenant -A -l Listing APP VM Group... Status : Active EditStatus : Description : Drama App VM Group - shared - multiple - CIS deletable : True progress : False VMgroupName : avm1 editable : True VMgroupID : 2
% mcmu network -a tenant
Specify the VMgroupID number.
Select ID [1] (1): 1
The VMs available in that VM group are listed:
ID | NAME | GLOBALZONE | HOSTNAME ---+---------------------+------------+----------------------- 1 | mc1dbzg1-vm1-mc1-n1 | mc1-n1 | mc1dbzg1-zone-1-mc1-n1 2 | mc1dbzg1-vm1-mc1-n2 | mc1-n2 | mc1dbzg1-zone-1-mc1-n2
Enter comma separated list of VM ID(s) ID [1,2] : 1,2
The available (unused) network interface pairs are listed:
Select any of the interface pairs to configure a network ID: 1 Interfaces: net4,net5 ID: 2 Interfaces: net6,net7
Select ID [1/2] (1):
These are the network interface pairs that you can choose from:
From the NET 2 and NET 3 ports – net2,net3
From the 10GbE NIC:
The first two ends of the splitter cable (A and B, or 1 and 2) – net4,net5
The second two ends of the splitter cable (C and D, or 3 and 4) – net6,net7
Enter IP addresses for virtual_machine: Enter Netmask in CIDR form (valid range: 8-28): Do you want to input Gateway(Router) address? Enter Y/N (N): Enter Default Gateway Address: Do you want to input DNS Servers and Domain name values? Enter Y/N (N): VLAN ID is optional. Do you want to input this value? Enter Y/N (N): Enter CAN HA type (IPMP/AGGR):
A series of messages appear after you enter all the remaining necessary information for the additional network, providing information on the additional network that is being configured. The following message appears at the conclusion, which confirms that the additional network was configured successfully.
[INFO ] Network successfully configured on all the VM(s)
At this point, you used one of the unused network interface pairs to configure an additional network. Repeat these instructions to configure a second additional network using the remaining unused interface pair, if necessary.