PaloAlto 10.0.4 VM not responding on Managment Interface
Posted: Thu Feb 24, 2022 3:56 pm
AMD Ryzen 9 5950x CPU
32MB Ram
EVE-NG-Pro 4.0.1-65
VMWare Workstation 16.2.2
I opened a previously working lab yesterday, after not using it for a week, and after starting everything up I attempted to log in via HTTPS to the management interface, which has a static IP address, and my connection was denied. I went to a Windows 10 vm I was running in the lab and was able to access the GUI via an internal interface I had put a management profile on which allowed me HTTPS access. Based on the GUI everything looked OK, however I was not getting log entries for the failed HTTPS access through the management interface. Using a Cisco router I had in the lab I was able to ping all my interfaces on both my PaloAlto FW's with no issue, hence there is not a routing/switching issue.
When I opened a new lab and attempted to install a new PaloAlto FW the new installation failed to install a DHCP address, which is SOP for PaloAlto VM's....
I had a PA VM on my VMWare workstation and it loaded, and configured a DHCP address, no problem. I copied all my configurations from my lab.
I deleted the Palo Alto qcow2 from EVE-NG and following the how to's reinstalled a known good, working, VM. Shutdown EVE-NG, shutdown VMWare Workstation 16, shut down my desktop and starting from scratch fired everything up. I was still not able to access the management interface via GUI and, again, when I attempted to install the "new" PA Qcow it too did not configure a DHCP interface.
HALP
32MB Ram
EVE-NG-Pro 4.0.1-65
VMWare Workstation 16.2.2
I opened a previously working lab yesterday, after not using it for a week, and after starting everything up I attempted to log in via HTTPS to the management interface, which has a static IP address, and my connection was denied. I went to a Windows 10 vm I was running in the lab and was able to access the GUI via an internal interface I had put a management profile on which allowed me HTTPS access. Based on the GUI everything looked OK, however I was not getting log entries for the failed HTTPS access through the management interface. Using a Cisco router I had in the lab I was able to ping all my interfaces on both my PaloAlto FW's with no issue, hence there is not a routing/switching issue.
When I opened a new lab and attempted to install a new PaloAlto FW the new installation failed to install a DHCP address, which is SOP for PaloAlto VM's....
I had a PA VM on my VMWare workstation and it loaded, and configured a DHCP address, no problem. I copied all my configurations from my lab.
I deleted the Palo Alto qcow2 from EVE-NG and following the how to's reinstalled a known good, working, VM. Shutdown EVE-NG, shutdown VMWare Workstation 16, shut down my desktop and starting from scratch fired everything up. I was still not able to access the management interface via GUI and, again, when I attempted to install the "new" PA Qcow it too did not configure a DHCP interface.
HALP