To configure Internet Protocol over InfiniBand (IPoIB):

1. Edit the /etc/sysconfig/network-scripts/ifcfg-ibN configuration file, where N is the number of the interface. The following example shows the configuration for the interface ib0:

   DEVICE=ib0
   TYPE=InfiniBand
   ONBOOT=yes 
   DHCP_HOSTNAME="myhost.mydom.com"
   BOOTPROTO=static
   IPADDR=192.168.100.1
   NETMASK=255.255.255.0
   IPV4_FAILURE_FATAL=yes
   IPV6INIT=no 
   CONNECTED_MODE=no
   NAME=ib0 

2. Stop the NetworkManager service:

   sudo systemctl stop NetworkManager

3. Start the RDMA service:

   sudo systemctl start rdma

4. Bring up the interface:

   sudo ifup ibN

   (Bug ID 19150870)

The IPoIB driver supports the use of either connected mode or datagram mode with an interface, where datagram mode is the default mode. Changing the mode of an InfiniBand interface by echoing either connected or datagram to /sys/class/net/ibN/mode is not supported. It is also not possible to change the mode of an InfiniBand interface while it is enabled.

To change the IPoIB mode of an InfiniBand interface:

1. Edit the /etc/sysconfig/network-scripts/ifcfg-ibN configuration file, where N is the number of the interface:

   • To configure connected mode, specify CONNECTED_MODE=yes in the file.

   • To configure datagram mode, either specify CONNECTED_MODE=no in the file or do not specify this setting at all (datagram mode is enabled by default).

   Note:

   Before saving your changes, make sure that you have not specified more than one setting for CONNECTED_MODE in the file.

2. To enable the specified mode on the interface, use the following commands to take down the interface and bring it back up:

   sudo ifdown ibN
   sudo ifup ibN

(Bug ID 17479833)

ibwarn: [2696] _do_madrpc: recv failed: Connection timed out
ibwarn: [2696] mad_rpc: _do_madrpc failed; dport (Lid 38)
ibportstate: iberror: failed: smp set portinfo failed

You can safely ignore these warnings. (Bug ID 16248314)

During installation, if you select Encrypt my data on the Installation Destination screen and then perform manual partitioning, the Encrypt check box is not shown as selected on the Manual Partitioning screen. This check box refers to encryption that you can configure on a file system type that supports encryption or on an LVM logical volume that contains the file system. If you click Modify, the Encrypt check box on the Configure Volume screen is shown as selected for the volume, meaning that the encryption will be applied at the level of the underlying block device.

For LVM, selecting Encrypt my data encrypts the LVM physical volume and all the logical volumes that it contains. If you do not select Encrypt my data, you can encrypt the logical volume by selecting the Encrypt check box on the Manual Partitioning screen or encrypt the physical volume by selecting the Encrypt check box on the Configure Volume screen.

For btrfs, encryption can only be applied to the block device that contains the file system, including its subvolumes. For example, enabling encryption for the /home subvolume of a btrfs root file system implicitly enables encryption for the root file system itself. You can only select the Encrypt check box on the Configure Volume screen. As btrfs does not support encryption at the file-system level, you cannot select the Encrypt check box on the Manual Partitioning screen for a btrfs file system.

Do not select the Encrypt check box or a BTRFS, LVM, or LVM Thin Provisioning device type for /boot. The /boot file system must be configured on a standard partition and should be of type ext4 or XFS.

When entering a password in the Disk Encryption Passphrase dialog, press Tab to move between the entry fields. You cannot use the mouse to select the fields.

Attempting to perform a network installation without configuring a network interface to use DHCP to obtain its IP settings or with static IP settings results in the error Error in Installation Source.

For example, if you use a feature such as a remote console or Lights-out management to access a boot ISO, the network configuration of the embedded server manager might not be available when you select the installation location. The workaround is to use the graphical installer to configure the network settings manually before configuring the installation location. (Bug ID 19047736)

Attempting to create an lxc-oracle container on a remote file system mounted using NFS v4 fails. In addition, attempting to mount a remote file system using NFS v4 from within an lxc-oracle container also fails. The workaround is to use NFS v3 instead. (Bug ID 16316266)

You cannot enable or disable the NFS service by using the systemctl command with nfs.service. Specify nfs-server.service instead, for example:

sudo systemctl enable nfs-server

(Bug ID 18437212)

The libcgroup package in Oracle Linux 7 does not include the cgconfig and cgred control group services. To restore these services on an upgraded system, install the libcgroup-tools package. (Bug ID 19177606)

The postupgrade scripts fail if a proxy is required to access Oracle Linux yum server. (Bug ID 19169163)

If you do not run the preupgrade assistant utility preupg, an upgraded system hangs while rebooting with the message starting wait for plymouth boot screen to quit. (Bug ID 18815298)

The old RHCK is not removed during the upgrade. (Bug ID 18767222)

The redhat-upgrade-tool-cli utility does not exit if UEK R3 is not installed. (Bug ID 18900135)

The redhat-upgrade-tool-cli utility requires that you install version 3.2.29-43.0.1 or later of the yum package on the Oracle Linux 6 system that you want to upgrade. If you use an earlier version of the yum package, the upgrade tool fails with dependency errors. (Bug ID 18648783)

A kernel panic can occur with UEK R3 if all the inodes for an XFS file system are used. (Bug ID 19695297)

xfs_copy fails to copy a file system under UEK R3 if the device sector size is greater than 512 bytes. (Bug ID 19267663)