AWS: Dataplane interface not getting IP via DHCP
10335
Created On 03/18/20 11:58 AM - Last Modified 04/06/20 17:42 PM
Symptom
Dataplane interfaces on PA-VM deployed in AWS are configured as DHCP clients to receive IP configuration dynamically. However, one of the interfaces does not get the IP configuration and is stuck in Init state.
- Click on Network > Interface > Ethernet1/x in question and notice interface getting 0.0.0.0 IP address.
-
Review System Logs to understand and verify the failure events.
System Logs:
2020/01/14 10:41:12 critical dhcp ethern if-clear 0 DHCP client cleared IP address on interface:ethernet1/3 due to: Release initiated due to internal error. Please check for duplicate IPs or overlapping Subnets.
2020/01/14 10:41:12 critical dhcp ethern if-clear 0 DHCP client cleared IP address on interface:ethernet1/3 due to: Release initiated due to internal error. Please check for duplicate IPs or overlapping Subnets.
-
Above log snippets indicates ethernet1/3 is getting IP from same subnet in which one of the other dataplane interface within the same virtual router resides
-
Verify the subnets associated with each dataplane interfaces on AWS to identify the overlapping subnet
Environment
- Platform: PA-VM
- PAN-OS / Plugin Version: - 9.0.1 / 1.0.7
- Deployment: AWS
Cause
- More than one dataplane interfaces within the same virtual router are associated with same subnet on AWS. Each interface within a virtual router should belong to different network / subnet.
Resolution
- Change the subnet associated with interface failing DHCP negotiation on AWS