Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2335574.1
Update Date:2018-04-23
Keywords:

Solution Type  Problem Resolution Sure

Solution  2335574.1 :   Exadata Compute Node Re-Image Stuck In Network Configuration Loop  


Related Items
  • Exadata X3-2 Hardware
  •  
  • Exadata X4-2 Hardware
  •  
  • Exadata X7-2 Hardware
  •  
  • Exadata X5-2 Hardware
  •  
  • Exadata X6-2 Hardware
  •  
  • Exadata Database Machine X2-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
  •  


During Bare Metal Restore of a compute node, the node reboots as expected but instead of booting normally it boots back to the network configuration again.

Created from <SR 3-16208432831>

Applies to:

Exadata X3-2 Hardware - Version All Versions and later
Exadata X4-2 Hardware - Version All Versions and later
Exadata X5-2 Hardware - Version All Versions and later
Exadata X6-2 Hardware - Version All Versions and later
Exadata X7-2 Hardware - Version All Versions and later
Information in this document applies to any platform.

Symptoms

During Bare Metal Restore (BMR) re-imaging of an Exadata compute node:

  • Network configuration steps as detailed in Task 6 of the Oracle Exadata Database Machine Maintenance Guide (section 2.16.6) have been completed.
  • The node reboots as expected but instead of booting normally it boots back to the network configuration again.
  • None of the network configuration information entered before the reboot has been saved.



Cause

A required service was not started during the network configuration.

 

Solution

1. Complete the interactive network setup again.

2. After answering the question "Do you want to configure basic ILOM settings (y/n) [y]:n", networking will start. Log in to the node as root via ssh, console, etc.

3. Once logged in, start the service that failed to start.

     service preipconf start

4. Ensure the vldrun.pl script was automatically started when step 3 was executed (ps -fe |grep vldrun).

    If the script is running, go to #5.

    If the script is not running, start it manually.

     /opt/oracle.cellos/validations/bin/vldrun.pl -mode first_boot -force -quiet -all

5. Reboot the node.

    The node should reboot normally and you can continue with Task 7 (section 2.16.7) in the maintenance guide.

    If any errors are encountered in the steps above or the node does not reboot normally, open a Service Request with Oracle Support.

 

References

3-16197261356

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback