09-24-2021 03:10 PM
It has finally happened and we ran out of IPv4 space on Primary CIDR block for our VPC. We created a new CIDR and associated it to the same VPC. However it appears that I can't associate an ENI in the new CIDR to our Palo Alto in the original CIDR. And we can't use the NAT ENI in the original because it hops to the original then out which AWS doesn't allow.
Has anyone tried this, or aware of how to work around this issue? Thanks, Chad
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!