Juniper vMX 14.10 intermittent boot up issue on Eve-ng
Posted: Sun Jan 06, 2019 3:36 am
Hi All
Does anybody have any idea for the following issue I have below ?
when setup a topology with many juniper vmx routers(vmx-14.1R1.10), sometimes one router can boot up , sometimes not, even I boot up them one by one.
Hardware : My Laptop Thinkpad P52 config - CPU - 8th Generation Intel® Core™ i7-8850H 6 Core Processor with vPro™, 32GB single Chanel RAM, 512G HDD, one 1000 Base T interface and WIFI
EVE-NG Running on - Vmware workstation 15 with Windows 10 Pro , Using community version latest EVE-NG, assigned 26 G RAM on Vmware workstaion, and number of processors is 1 , number os cores per processor is 6.
VT-X - Enabled ( on both laptop BIOS and Vmware workstation)
Before posting the Problem : ( I have checked below steps Example)
My Node note starting. ( some node can bootup and some are not when using the same image, so should not the image issue)
1. check the path of the image ( good )
2. I fixed permission(/opt/unetlab/wrappers/unl_wrapper -a fixpermissions)
3. file name format matches against EVE-NG requirement mentioned in the site.
4. Check the logs /opt/unetlab/data/Logs/ see attachment
root@eve-ng:/opt/unetlab/data/Logs# ls
access.txt api.txt error.txt unl_wrapper.txt
Does anybody have any idea for the following issue I have below ?
when setup a topology with many juniper vmx routers(vmx-14.1R1.10), sometimes one router can boot up , sometimes not, even I boot up them one by one.
Hardware : My Laptop Thinkpad P52 config - CPU - 8th Generation Intel® Core™ i7-8850H 6 Core Processor with vPro™, 32GB single Chanel RAM, 512G HDD, one 1000 Base T interface and WIFI
EVE-NG Running on - Vmware workstation 15 with Windows 10 Pro , Using community version latest EVE-NG, assigned 26 G RAM on Vmware workstaion, and number of processors is 1 , number os cores per processor is 6.
VT-X - Enabled ( on both laptop BIOS and Vmware workstation)
Before posting the Problem : ( I have checked below steps Example)
My Node note starting. ( some node can bootup and some are not when using the same image, so should not the image issue)
1. check the path of the image ( good )
2. I fixed permission(/opt/unetlab/wrappers/unl_wrapper -a fixpermissions)
3. file name format matches against EVE-NG requirement mentioned in the site.
4. Check the logs /opt/unetlab/data/Logs/ see attachment
root@eve-ng:/opt/unetlab/data/Logs# ls
access.txt api.txt error.txt unl_wrapper.txt