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-21-2019 08:41 AM
Can somebody tell me this - if Eth0 and E1/1 are showing different IP addresses in teh AWS instance window, than what I have configured, what course should I take. Currently, E1 is a private ENI and Im pretty sure that wont work as my public IP address.
06-21-2019 08:59 AM
I may have missed something but it sounds like you did the following
1. configured your interfaces in PAN-OS statically
2. Didn't set the AWS ipconfiguration to static
If that is the case go back into the VM-Series and change the interfaces to dynamic
For any of the dataplane interfaces only check "add default route" for your untrust interface
06-24-2019 08:03 AM
Thanks for the help. The problem I have now is that even though E1/1 (untrust) is configured as DHCP client, Palo Alto shows N/A for the IP address. Under "dynamic IP int status" everything is all zeros.
06-24-2019 01:49 PM
Went ahead and made it static. Seemed to work. Attribute this as a PANOS bug in 9.0.1
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!