![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1565651.1 : Unable To Load IB Bonding Interfaces; Getting Error "ib_ipoib: Unknown symbol icmpv6_send"
In this Document
Created from <SR 3-7449085991> Applies to:Exalogic Elastic Cloud X3-2 Hardware - Version All Versions to All Versions [Release All Releases]Linux OS - Version Oracle Linux 5.0 to Oracle Linux 6.4 with Unbreakable Enterprise Kernel [2.6.39] [Release OL5 to OL6U4] Information in this document applies to any platform. SymptomsYou are unable to load IB bonding interfaces getting errors while loading bonding modules. The same behavior is experienced on OL 5.8 when the entry for ipv6 (install ipv6 /bin/true) is inserted in file modprobe.conf: ##$-> cat /etc/modprobe.conf
alias scsi_hostadapter shpchp alias eth0 ixgbe alias eth1 ixgbe alias eth2 ixgbe alias eth3 ixgbe alias scsi_hostadapter1 megaraid_sas alias scsi_hostadapter2 ahci alias net-pf-27 ib_sdp options ib_ipoib lro=Y options ib_sdp sdp_zcopy_thresh=0 recv_poll=0 options mlx4_vnic tx_rings_num=8 rx_rings_num=8 eport_state_enforce=1 options mlx4_core log_mtts_per_seg=5 alias bond0 bonding options bonding max_bonds=3 install usb-storage : install ipv6 /bin/true ##$->
Executing the command "modprobe ib_ipoib" shows the below error in dmesg. [mlx4_vnic] Added fip discovery mlx4_0 port 1 PKEY 0xffff
[mlx4_vnic] Added fip discovery mlx4_0 port 2 PKEY 0xffff ib_ipoib: Unknown symbol icmpv6_send [mlx4_vnic] Received event 0x11 (device mlx4_0 port 1) [mlx4_vnic] Received event 0xb (device mlx4_0 port 1) ChangesThere are no changes on the node related to HW or SW. CauseIPV6 parameter defined under modprobe.conf is causing the failure of loading bonding driver. This causes the IB_IPOIB fail to start. The same will be experienced on OL 5.x and 6.x versions too when the system goes for a reboot. Bond devices will not be working because of the entry as modules do not get loaded. SolutionComment he line for IPV6 and restart the network service. This should fix the issue. Attachments This solution has no attachment |
||||||||||||||||||
|