IP address not assigned to BlueBox via DHCP

When configuring a BlueBox device to obtain an IP address via DHCP, the IP address may not be assigned even though:

• Option Obtain IP address automatically (DHCP) is selected in Hardware | Hardware Type | System Configuration. 
• The DHCP server exists on the same VLAN as the BlueBox, or a firewall relay is correctly configured to forward DHCP messages.

Network traffic inspection reveals that the BlueBox is periodically transmitting DHCP discover packets and the DHCP server is responding with DHCP offers, but then the communication between them is stopped.

This issue has been observed on the following products:

• iC5000
• iC5700
• iC6000
• Other older BlueBox products

BlueBox devices expect all DHCP messages from the server to have a payload size larger than 300 bytes. If the DHCP server sends smaller packets, the BlueBox terminates the communication before completing the lease process.

Solution

BlueBox expects that all DHCP messages from the server have a payload size larger than 300 bytes. If the payload is smaller than 300 bytes, configure the DHCP server to add extra fields to the DHCP packets, so the payload size will be increased to more than 300 bytes (e.g., DHCP Option 43 (vendor-specific) with some empty fields will suffice).

More resources in winIDEA Help

• Set up and configure BlueBox Hardware