![]() But now I get to the following point when I try and enter the CLI: This time when I created the vSRX in the lab, I gave it 4 x CPU and 8192 RAM. Created vMX-Control-Plane and Forwarding-Plane and they work fine. Bridged interface as easier and also statically assigned the MAC on the router to ensure same address always applied. Re-installed the eve-ng.ova and created the VM. Purchased a new machine, re-installed VMware Workstation 12 Pro. The html portal shows the vSRX as being available though.Īny ideas as to why this is happening please? I only have access to the qcow2 image and have configured that as per the eve-ng vSRX documentation. It just keeps getting to this point and power cycling. This is continuous and I cannot get the vSRX to actually go to the CLI. > Press a key on the console to reboot,Īll this allows me to do is reboot the vSRX. Mode = 0100644, inum = 6910, fs = /.mountĪutomatic reboot in 15 seconds - press a key on the console to abort Trying to mount root from cd9660:/dev/md0.uzip. Kernel thread "wkupdaemon" (pid 43) exited prematurely. Md0: Preloaded image 8897024 bytes at 0xffffffff824e41c0 Registering tcp_platform_dependent = tcp_handle_special_ports When I power on the vSRX I get to the following point: ![]() I have eve-ng running fine with 2 x vMX currently (CP and FP) and have installed a vSRX (as I need to test some VPN/NAT configurations).
0 Comments
Leave a Reply. |