VIC DHCP does not request gateway

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• DHCP assigns IP and does not assign default network.
• The tether.debug log file will show that the gateway for the DHCP response is nil.

INFO DHCP response: IP=192.168.0.4, SubnetMask=ffffff00, Gateway=<nil>, DNS=[4.4.4.4 8.8.8.8], Lease Time=2h0m0s

Note: The tether.debug is located on the VMFS datastore that the VM container's working directory.

• The DHCP discovery will not have "route" as one of the requested options when viewing a data level packet dump.

$ tcpdump -Xvvvnr packet.pcap

reading from file packet.pcap, link-type EN10MB (Ethernet)

17:35:00.999606 IP (tos 0x0, ttl 16, id 36864, offset 0, flags [none], proto UDP (17), length 300)

0.0.0.0.bootpc > 255.255.255.255.bootps: [no cksum] BOOTP/DHCP, Request from 00:50:56:85:62:84, length 272, xid 0x6ed6d800, Flags [Broadcast] (0x8000)

Client-Ethernet-Address 00:50:56:85:62:84

Vendor-rfc1048 Extensions

Magic Cookie 0x63825363

Parameter-Request Option 55, length 2:

Subnet-Mask, Domain-Name-Server

DHCP-Message Option 53, length 1: Discover

Client-ID Option 61, length 19: hardware-type 255, ac:f8:d3:a8:00:02:00:00:1a:dc:cf:a7:27:d8:72:6d:5d:3e

END Option 255, length 0

PAD Option 0, length 0, occurs 3

0x0000: 4500 012c 9000 0000 1011 19c2 0000 0000 E..,............

Environment

VMware vSphere Integrated Containers 1.0.x

Cause

VIC 1.1.1 caches the network scope for dynamic networks causing the DHCP to assume that the default gateway is defined statically.

Resolution

To resolve this issue, upgrade the VIC appliance and then the VCH endpoint VM.

1. Upgrade the VIC Appliance -  Upgrade the vSphere Integrated Containers Appliance
2. Upgrade the VCH endpoint VM - Upgrade Virtual Container Hosts

Additional Information

Containers on Container Networks have no internet connectivity after >2 Containers are started and have obtained IPs