06-20-2019 11:58 AM
Im doing some testing in AWS with a DEV server on the inside of my vm 100.. I have E1/2 configured as gateway interface with a ENI private IP address we created in AWS. However, after troubleshooting almost the entire day I cant get it to come up. Im using 9.0.1 so this could be a bug but Im not sure. Has anybody every encountered this?
06-20-2019 02:50 PM
I have a better understanding of the problem. In AWS , the way the IP addresses are allocated are very confusing to me. Ive read the PA documentation and I cant find anywhere were it explains how you are supposed to use the Eth0, Eth1, etc and how these map back to the Palo Alto vm's. I have to understand IP addressing in AWS land and I just cant get my head around it. If anybody has a knowledge based article that explains this please send. Also, the vm-series deployment guide IS NOT helpful for this. Yes, I read it
06-20-2019 03:03 PM
AWS ETH0 = PA Management
AWS ETH1 = PA ETH1/1
AWS ETH2 = PA ETH1/2
AWS ETH3 = PA ETH1/3
This assumes you did not perform an interface swap during deployment. If so Management and ETH1/1 would be reversed so that ETH1/1 is the target of an ELB.
06-21-2019 08:03 AM
Thank you. unfortunately, that brings up more questions so I think I will stop here
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!