For VCF 9.1 and higher:
- Retrieve the affected Org, Project, VPC and Subnet details from the Alarm message.
- Identify the port MAC addresses for which the server has reclaimed the dynamic IP by using
/policy/api/v1/orgs/{org-id}/projects/{project-id}/vpcs/{vpc-id}/subnets/{subnet-id}/state/dhcp-server-managed-ports and looking for ‘ip’_allocation_state’ , ‘mac_address’ and ‘ip_address’ fields. - In the below sample, MAC "00:50:56:##:##:##” is determined as FAILURE (“ip_allocation_state” field) and it’s dynamic IP (“ip_address” field) is released by the server.
{ "ports": [ { "port_path": "/orgs/default/projects/default/vpcs/###/subnets/###/ports/default:########-6aaf-4363-b36f-############", "ip_allocation_state": “FAILURE”, "client_mode": “DHCP”, "mac_address": "00:50:56:#:##:##”, "ip_address": "0.0.0.0", "ip_address_consumed": false }, …. ] }
- On VC, identify VM and the network adapter using the MAC address retrieved from above step.
- Go to VM’s ‘Edit Settings’ page, perform disconnect & reconnect for the affected network adapter.
- For the above network adapter’s MAC, verify SUCCESS for ‘ip_allocation_state’ valid IP address for the MAC is assigned by DHCP server IP using the above API.
{ "ports": [ { "port_path": "/orgs/default/projects/default/vpcs/###/subnets/###/ports/default:########-6aaf-4363-b36f-############", "ip_allocation_state": “SUCCESS”, "client_mode": “DHCP”, "mac_address": "00:50:56:#:##:##”, "ip_address": "10.X.Y.Z”, "ip_address_consumed": false }, …. ] }
- Ensure DHCP client runs on the VM’s interface to acquire the newly allocated IP from the server.