Oracle Exalogic Elastic Cloud Owner's Manual page 212

Table of Contents

Advertisement

Create a Partition for EoIB and Associating the pkey with a VNIC and VLAN
c.
Create the interface file for the first VNIC, eth4 in the example, by using a text
20.
editor such as vi.
Save the file in the /etc/sysconfig/network-scripts directory.
Example:
# more /etc/sysconfig/network-scripts/ifcfg-eth331_1
DEVICE=eth331_1
BOOTPROTO=none
ONBOOT=yes
HWADDR=a2:c0:a0:a8:01:01
MASTER=bond1
SLAVE=yes
Create an interface file for the second VNIC, say eth5. Be sure to name the
21.
interface file and specify the DEVICE directive by using a derived interface name
and not the kernel-assigned name, as described earlier. In addition, be sure to
specify the relevant dummy MAC address for the HWADDR directive.
After creating the interface files, create the ifcfg-bond1 file. If the file already
22.
exists, verify its contents.
Example:
# more /etc/sysconfig/network-scripts/ifcfg-bond1
DEVICE=bond1
IPADDR=192.168.48.128
NETMASK=255.255.255.0
16-14 Oracle Exalogic Elastic Cloud Machine Owner's Guide
Example:
e101cn01#mlx4_vnic_info -i eth4 | grep IOA_PORT
IOA_PORT
mlx4_0:1
Note the number after the colon (:) in the IOA_PORT value that is displayed,
in this case 1.
Build the interface file name and device name by using the following
convention:
Interface file name: ifcfg-ethA_B
Device name: ethA_B
A is the EPORT_ID, and B is the number after the colon (:) in the IOA_PORT
value.
Example:
Interface file name: ifcfg-eth331_1
Device name: eth331_1
In this example, 331 is the EPORT_ID, and 1 is the value derived from the
IOA_PORT.
Make sure that the name of the interface file (ifcfg-eth331_1 in the
example) is the name derived in step 19.
For the DEVICE directive, specify the device name (eth331_1 in the
example) derived in step 19.
For the HWADDR directive, specify the dummy MAC address created in step 4.

Advertisement

Table of Contents
loading

Table of Contents