Limiting the Impact of IP Helper Addresses
Problem
After configuring your router to use IP helper addresses, you suffer from high link utilization or high CPU utilization on the DHCP server.
Solution
The ip helper-address command implicitly enables forwarding several different kinds of UDP broadcasts. You can prevent the router from forwarding the unwanted types of broadcasts with the no ip forward-protocol udp configuration command:
Router1#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router1(config)#no ip forward-protocol udp tftpRouter1(config)#no ip forward-protocol udp nameserverRouter1(config)#no ip forward-protocol udp domainRouter1(config)#no ip forward-protocol udp timeRouter1(config)#no ip forward-protocol udp netbios-nsRouter1(config)#no ip forward-protocol udp netbios-dgmRouter1(config)#no ip forward-protocol udp tacacsRouter1(config)#endRouter1#
Discussion
As mentioned in Recipe 20.1, if the DHCP client and server are on different network segments, the router on the client’s segment must be configured with a helper address for DHCP to work. However, the helper address configuration forwards a variety of different UDP broadcasts, not just DHCP packets. This can cause network loading problems, as well as CPU loading problems on the DHCP server.
By default, when you configure the ip helper-address command on an interface, the router will automatically forward UDP broadcasts for all of the protocols shown in Table 20-1.
Table 20-1. Default ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access