bondib0 is not coming up after reboot on Exadata DB node

Asset ID:	1-72-1627826.1
Update Date:	2014-03-11
Keywords:

Solution Type Problem Resolution Sure

Solution 1627826.1 : bondib0 is not coming up after reboot on Exadata DB node

Related Items


Exadata Database Machine V2
 Exadata Database Machine X2-2 Full Rack
 Exadata X3-2 Hardware

Related Categories


PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
 _Old GCS Categories>ST>Server>Engineered Systems>Exadata>Administration and Configuration
 _Old GCS Categories>ST>Server>Engineered Systems>Exadata>Troubleshooting and Debugging

In this Document

Symptoms

Cause

Solution

Created from <SR 3-8593302983>

Applies to:

Exadata X3-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine V2 - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine X2-2 Full Rack - Version All Versions to All Versions [Release All Releases]
Linux x86

Symptoms

bondib0 is not coming up after reboot on Exadata DB node

The effected node dbadm02 lists bondib0 with no link:

[root@bkkdbadm02 network-scripts]# ethtool bondib0
Settings for bondib0:
Link detected: no

Cause

-rwxrwxrwx 1 cores2am staff 317 Dec 9 08:42 ifcfg-bondib0*
-rwxrwxrwx 1 cores2am staff 317 Dec 9 08:41 ifcfg-bondib0.09122013*

You cannot have backups of these files by having an extension appended to the end of the filename. If you want to back them up, you have to prepend something to the beginning of the filename, not the end, or put them in another directory. The scripts will attempt to bring up every interface that starts with ifcfg- in this directory, so both ifcfg-bondib0 and ifcfg-bondib0.09122013 will get started.

Solution

#mv ifcfg-bondib0.09122013 09122013-ifcfg-bondib0

#reboot

Attachments

This solution has no attachment