BareMetal Edge Nodes Troubleshooting
- If selection ofESC_BareMetal_Profilein the target node PXE boot Menu is not happening, it could be due to port conflict issue. Access http://localhost on the host node, it should display the files as below.If the files are not displayed as mentioned in the above image, it could be due to some other service running on port 8080. In that case, remove the other service on 8080 and restart the container esp_web_1 on host machine.If the files are hosted and you are still not able to select the profile in PXE boot menu, then it could be because Hostname resolution to IP address is not working. In case of Dual Ethernet, you can restart the dnsmasq container by executing the below command on the host device.sudo docker restart esp_dnsmasq_1
- If you encounter an error stating "An active template not found," this implies that the BareMetal configuration is not done and, hence, it needs to be configured from the UI side.If the below error occurs, please verify that the BareMetal Provisioning Configuration is enabled in theSettingstab present inDeploy > Connect to Edge node.
- In Single Ethernet mode, if the Edge Node frequently loses internet connectivity it could be because its DHCP lease has expired. In this case, configure the router with a longer DHCP lease time.
- If provisioning status of the BareMetal edge node is stuck at “Agent Installation” for more than 20 minutes, then execute the below commands to onboard the edge node manually.Execute the below commands on the edge node.cd /etc/esm/ sudo chmod 775 onboarding.sh sudo ./onboarding.shDuring onboarding of edge node with Dual Ethernet network mode, if the Hostname resolution to IP address is not working on the edge node or you are getting an error like “name or service unknown” then you can restart the dnsmasq container by executing the below command on the host device.sudo docker restart esp_dnsmasq_1After executing the above command, restart the edge node.