![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 2335574.1 : Exadata Compute Node Re-Image Stuck In Network Configuration Loop
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 laterExadata 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. SymptomsDuring Bare Metal Restore (BMR) re-imaging of an Exadata compute node:
CauseA required service was not started during the network configuration.
Solution1. 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.
References3-16197261356Attachments This solution has no attachment |
||||||||||||
|