Courseiva
DHCPInterface Config

ip helper-address [dhcp-server-ip]

Configures a DHCP relay agent on an interface to forward DHCP broadcast requests to a specific DHCP server IP address.

Definition: ip helper-address [dhcp-server-ip] is a Cisco IOS interface config command. Configures a DHCP relay agent on an interface to forward DHCP broadcast requests to a specific DHCP server IP address.

Overview

The `ip helper-address` command is a critical tool in Cisco IOS for forwarding DHCP broadcast requests across network segments. DHCP relies on broadcast messages (UDP port 67/68) that are typically confined to a single subnet by routers. In enterprise networks, DHCP servers are often centralized for manageability, while clients reside on different VLANs or subnets.

Without a relay agent, clients on remote subnets cannot obtain IP addresses from a distant server. The `ip helper-address` command configures a router interface to listen for DHCP broadcasts (and optionally other UDP broadcasts) and forward them as unicast to a specified DHCP server IP address. The router also relays the server's unicast reply back to the client, preserving the original broadcast behavior transparently.

This command is essential for scaling DHCP in multi-subnet environments without requiring a DHCP server on every subnet. Alternatives include using a dedicated DHCP relay agent (e.g., on a switch or firewall) or implementing DHCP snooping with relay on switches, but the `ip helper-helper` command remains the simplest and most common method on Cisco routers. It fits into a broader network configuration workflow where you first design IP addressing and VLANs, then configure DHCP pools on the server, and finally enable relay on the router interfaces facing client subnets.

Important IOS behaviors: The command is applied per interface and can be repeated to specify multiple DHCP servers (up to 8). It also forwards other UDP broadcasts by default (TFTP, DNS, Time, NetBIOS, etc.) unless restricted with `ip forward-protocol`. The command takes effect immediately and is saved in the running configuration.

Privilege level 15 (enable) is required to configure it. The router must have IP routing enabled and an interface with an IP address in the client subnet to relay properly. Understanding this command is fundamental for CCNA and CCNP candidates as it appears in both exam topics and real-world troubleshooting scenarios.

Syntax·Interface Config
ip helper-address [dhcp-server-ip]

When to Use This Command

  • When DHCP clients and servers are on different subnets, and you need to forward DHCP broadcasts across a router.
  • In a multi-VLAN environment where each VLAN has a DHCP server on a different subnet.
  • When using a centralized DHCP server for multiple remote subnets to avoid deploying a DHCP server per subnet.
  • To forward DHCP requests to a failover or secondary DHCP server for redundancy.

Parameters

ParameterSyntaxDescription
dhcp-server-ipA.B.C.DThe IP address of the DHCP server to which broadcast requests are forwarded. Must be a valid unicast IPv4 address. Common mistakes include using a broadcast or multicast address, or an IP address that is not reachable from the router. Ensure the server is reachable via routing and that UDP port 67 is not blocked by ACLs.

Command Examples

Basic DHCP relay configuration on a VLAN interface

interface Vlan10 ip helper-address 192.168.1.10
Router(config)# interface Vlan10
Router(config-if)# ip helper-address 192.168.1.10
Router(config-if)# end
Router# show ip interface Vlan10 | include Helper
  Helper address is 192.168.1.10

The command configures the VLAN10 interface to forward DHCP broadcasts to the DHCP server at 192.168.1.10. The 'show ip interface' output confirms the helper address is set.

Multiple DHCP relay addresses for redundancy

interface GigabitEthernet0/1 ip helper-address 10.0.0.1 ip helper-address 10.0.0.2
Router(config)# interface GigabitEthernet0/1
Router(config-if)# ip helper-address 10.0.0.1
Router(config-if)# ip helper-address 10.0.0.2
Router(config-if)# end
Router# show ip interface GigabitEthernet0/1 | include Helper
  Helper address is 10.0.0.1 [2]

Two helper addresses are configured for redundancy. The 'show ip interface' output shows the first helper address and the count of additional helpers in brackets. The router forwards DHCP requests to both servers.

Understanding the Output

The 'show ip interface' command displays the configured helper address. The line 'Helper address is <IP> [count]' shows the first helper address and the number of additional helper addresses configured. If no helper address is set, the line will not appear or show 'Helper address is not set'.

A missing helper address means DHCP broadcasts will not be forwarded, causing clients on different subnets to fail to obtain an IP address. Multiple helper addresses are shown with a count in brackets; the router forwards DHCP packets to all listed servers.

Configuration Scenarios

Configure DHCP relay for clients on a remote subnet

A company has a centralized DHCP server at 10.0.1.10 on subnet 10.0.1.0/24. Clients on subnet 192.168.10.0/24 cannot obtain IP addresses because DHCP broadcasts are not routed. The router R1 connects both subnets and must relay DHCP requests.

Topology

DHCP Server (10.0.1.10)---(Gi0/1) R1 (Gi0/0)---(192.168.10.0/24) Clients

Steps

  1. 1.Step 1: Enter global configuration mode: R1# configure terminal
  2. 2.Step 2: Enter interface configuration mode for the client-facing interface: R1(config)# interface GigabitEthernet0/0
  3. 3.Step 3: Configure the DHCP relay address: R1(config-if)# ip helper-address 10.0.1.10
  4. 4.Step 4: Exit and save configuration: R1(config-if)# end; R1# copy running-config startup-config
Configuration
! Full IOS config block
interface GigabitEthernet0/0
 ip address 192.168.10.1 255.255.255.0
 ip helper-address 10.0.1.10
!

Verify: Use 'show ip interface GigabitEthernet0/0' and look for 'Helper address is 10.0.1.10'. Also, from a client, release and renew IP (e.g., ipconfig /renew on Windows) and verify it receives an address from the 192.168.10.0/24 pool.

Watch out: Forgetting to configure an IP address on the interface before applying the helper-address command will cause the relay to fail silently. Always ensure the interface has a valid IP address in the client subnet.

Configure DHCP relay to multiple servers for redundancy

To ensure high availability, DHCP requests from clients on VLAN 100 (192.168.100.0/24) should be forwarded to two DHCP servers at 10.0.1.10 and 10.0.2.10. The router R2 acts as the default gateway for VLAN 100.

Topology

DHCP Server1 (10.0.1.10)---(Gi0/1) R2 (Gi0/0.100)---(192.168.100.0/24) Clients DHCP Server2 (10.0.2.10)---(Gi0/2) R2

Steps

  1. 1.Step 1: Enter global configuration mode: R2# configure terminal
  2. 2.Step 2: Enter subinterface configuration for VLAN 100: R2(config)# interface GigabitEthernet0/0.100
  3. 3.Step 3: Configure encapsulation and IP address: R2(config-subif)# encapsulation dot1Q 100; R2(config-subif)# ip address 192.168.100.1 255.255.255.0
  4. 4.Step 4: Add first DHCP server: R2(config-subif)# ip helper-address 10.0.1.10
  5. 5.Step 5: Add second DHCP server: R2(config-subif)# ip helper-address 10.0.2.10
  6. 6.Step 6: Exit and save: R2(config-subif)# end; R2# copy running-config startup-config
Configuration
! Full IOS config block
interface GigabitEthernet0/0.100
 encapsulation dot1Q 100
 ip address 192.168.100.1 255.255.255.0
 ip helper-address 10.0.1.10
 ip helper-address 10.0.2.10
!

Verify: Use 'show ip interface GigabitEthernet0/0.100' to see both helper addresses listed. Test by shutting down one server and verifying clients still get addresses from the other.

Watch out: The router forwards DHCP requests to all configured helper addresses simultaneously, which can cause duplicate IP assignments if both servers respond. Ensure DHCP servers are configured to coordinate (e.g., split scope or DHCP failover).

Troubleshooting with This Command

When troubleshooting DHCP relay issues, start by verifying the `ip helper-address` configuration is present on the correct interface. Use `show ip interface [interface]` and look for the 'Helper address' line. If missing, the relay is not configured.

Healthy output shows the helper IP address(es) listed. Problem indicators include no helper address or an incorrect IP. Next, ensure the interface has an IP address in the client subnet; without it, the router cannot identify the client's subnet to relay properly.

Use `show ip interface brief` to confirm the interface is up/up and has an IP. Common symptoms: clients fail to obtain an IP address (DHCP discover never reaches server), or clients get an IP from the wrong subnet (server assigns from a different pool). The latter often occurs if the relay agent does not set the 'giaddr' field correctly; check that the router's interface IP is in the same subnet as clients.

Use `debug ip dhcp server packet` on the DHCP server (if accessible) to see if requests arrive with the correct giaddr. On the router, use `debug ip udp` to confirm packets are being forwarded (though this can be noisy). A step-by-step diagnostic flow: 1) Verify `ip helper-address` on the client-facing interface. 2) Check reachability to the DHCP server from the router (ping). 3) Ensure no ACLs block UDP port 67/68 between router and server. 4) On the router, use `show ip sockets` to see if UDP port 67 is listening. 5) Capture packets on the router's interface using `monitor capture` or an external tool to see if DHCP discovers are being forwarded.

Correlate with `show ip dhcp relay information` (if using option 82) to see relay agent info. If the server is on a different VLAN, ensure inter-VLAN routing is enabled. Also, check that the router's IP routing table has a route to the DHCP server.

Finally, remember that `ip helper-address` forwards other UDP broadcasts by default; if you see unexpected traffic, use `no ip forward-protocol udp <port>` to restrict.

CCNA Exam Tips

1.

Remember that 'ip helper-address' forwards UDP broadcasts for DHCP (ports 67/68) by default, but also forwards other UDP services like TFTP, DNS, and NetBIOS unless disabled with 'ip forward-protocol'.

2.

The command is configured in interface configuration mode, not globally. It must be applied to the interface facing the DHCP clients.

3.

CCNA exam may test that the helper address must be reachable from the router; otherwise, DHCP requests are dropped.

4.

Be aware that 'ip helper-address' does not forward broadcasts for all UDP services; only specific ports are forwarded by default.

Common Mistakes

Applying the helper address on the wrong interface (e.g., the interface facing the DHCP server instead of the clients).

Forgetting to configure a default route or ensure reachability to the DHCP server, causing relay failures.

Not realizing that multiple helper addresses cause the router to forward DHCP requests to all servers, which can lead to multiple IP offers and potential conflicts.

ip helper-address [dhcp-server-ip] vs show ip interface

Both 'ip helper-address' and 'show ip interface' relate to IP interfaces on a Cisco router, but they serve fundamentally different purposes: one configures DHCP relay forwarding, while the other displays interface status for verification. They are often considered together when troubleshooting IP connectivity issues involving DHCP.

Aspectip helper-address [dhcp-server-ip]show ip interface
ScopePer-interfaceRouter-wide (all interfaces)
Configuration modeInterface Configuration (config-if)Privileged EXEC (#)
FunctionForwards DHCP broadcasts to a specific serverDisplays interface IP status and statistics
PersistencePersistent (saved in running-config)Non-persistent (show output only)
Typical useConfigure DHCP relay agentVerify interface IP configuration and troubleshoot
OutputNo direct output (silent configuration)Detailed interface information

Use ip helper-address [dhcp-server-ip] when you need to forward DHCP broadcast requests from clients on a subnet to a centralized DHCP server located on a different subnet.

Use show ip interface when verifying the IP address assignment, interface status, or troubleshooting connectivity issues at the IP layer.

Platform Notes

In IOS-XE (e.g., Catalyst 9000 switches), the `ip helper-address` command syntax and behavior are identical to classic IOS. However, on IOS-XE switches, the command is applied to SVIs (interface Vlan) or routed ports. The output of `show ip interface` is similar.

For NX-OS (e.g., Nexus switches), the equivalent command is `ip dhcp relay address <server-ip>` under the interface configuration mode. For example: `interface Vlan100; ip dhcp relay address 10.0.1.10`. NX-OS also requires `feature dhcp` to be enabled globally.

On ASA firewalls, DHCP relay is configured using `dhcprelay server <server-ip> <interface>` and `dhcprelay enable <interface>` in global configuration mode. In IOS-XR (e.g., ASR 9000), the command is `dhcp ipv4 relay helper-address <server-ip> vrf <vrf-name>` under interface configuration, and the relay feature must be enabled with `dhcp ipv4 relay` in global config. Behavior differences across IOS versions: In older IOS 12.x, the command also forwarded broadcasts for ports 69 (TFTP), 53 (DNS), 37 (Time), 137-138 (NetBIOS), and 161 (SNMP).

In IOS 15.x and later, you can selectively disable these with `no ip forward-protocol udp <port>`. The maximum number of helper addresses per interface is 8 in all versions. Always verify the specific platform documentation, as some low-end routers may have limitations.

Related Commands

debug ip dhcp server events

Use this command to monitor DHCP server events in real time, such as address assignments, renewals, and conflicts, for troubleshooting DHCP operation on a Cisco IOS router acting as a DHCP server.

show ip interface

Displays the status and configuration of all IP interfaces on a Cisco router, including IP address, protocol status, and interface statistics, used for verifying interface IP configuration and troubleshooting connectivity issues.

Practice for the CCNA 200-301

Test your knowledge with practice questions covering all CCNA 200-301 exam domains.

Practice CCNA 200-301 Questions