About anthony.goethals

It's the same with the PMRuA --- several of the questions lack context, so it's hard to know what the answer should be (e.g. "How are users monitored?")   Hard to differentiate when a questions is about Panorama managed or Cloud managed Prisma. At least 2-3 questions are just wrong, either the way the question is asked or the answers provided. Some questions can only be answered if you've used the prodiuct --- there is no detail or information in any of the required Beacon training material. ... View more

@hfregoso wrote: Whats the stae of your phase 1 ? Is the issue with phase 2?   One recommendation is to use proxy ids with Azure, I know proxy ids ar eonly for cisco devices but this is one exception to the rule.      I have cli access from the PA220 so I've been running the initial vpn test from there, but I don't have CLI access from the cloud side, yet, so I have not initiated anything from that side, yet.  The system logs on either side don't show me anything related to the VPN, so that might be my problem.   The proxy IDs is something I have not tried yet, and I was just reading about that yesterday.  I will give that a try.   I mostly wanted to make sure that, with the VM300 in the Azure cloud, I was treating this setup properly and not overlooking some issue related to the particular environment.  The PA220 is coming off a working cable modem connection we use for lab setups, and as far as I know, if I allow access through the public facing interface on the Azure side, there's nothing else I have to do in Azure spcifically.   Other than that, on both sides I have the ethernet interfaces with static IP addresses added to virtual routers that allow public facing access, as well as their own security zones. The IPsec tunnels are also in the same securty zones, and both tunnels are in 192.168.100.x/24 subnets with .1 as the IP on one side and .10 as the IP on the other.  The peer addresses are correct on each side of the tunnel, and the IKE Gateways have the correct local and peer addresses.  I'm using the default IKE Crypto and IPSec crypto on both sides.   The one thing I want to try is the proxy IP addressing, so I'll give that a try, but wanted to make sure I wasn't overlooking something special.  Thanks in advance for the advice.             ... View more

@OtakarKlier wrote: Hello, What are you seeing in the logs, traffic and system? The system logs show the VPN connections. Also not sure about Azure, but Google and AWS have load balancers in front of the hosted VM's, may want to double check and see if those ACL's are open?   Regards,   From the PA220 I can test the vpn and I see it initiate but I can't find anything in the VM300 logs indicating failed connection attempts.  We might not have a policy setup yet to show the connection attempts.  Our Azure fabric is in production and used for a great many other things at this time --- not just for the Palo.   I did make sure in the Azure fabric to allow ipsec connectiivty through the public facing interface with a inbound port rule, but not sure if I did enough to allow connectivity.  I've approached this mostly as a Palo-to-Palo tunnel peer connection setup, so not sure if I've done my homework on the Azure side. ... View more

Thanks for getting back, but yeah, I did find it in the BIOS.  It was just hidden where I least expected it.   I had found the hyerthreading option and thought that was it, but until I went deep into the Security option in the BIOS, I didn't find the hyper-v settings.  It's all good now, though, thanks!     ... View more