<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Interface not accepting DHCP address in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4894786#M386982</link>
    <description>&lt;P&gt;Hello Adam,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;STRONG&gt;Configuration register is 0x2402&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;... et voilà! Here is the culprit!&lt;/PRE&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/50421-config-register-use.html#toc-hId--612512991" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/50421-config-register-use.html#toc-hId--612512991&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Your configuration register value translates to these meanings:&lt;/P&gt;
&lt;PRE&gt;- Boots default ROM software if network boot fails (0x2000)&lt;BR /&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;- IP broadcast with all zeros (0x0400)&lt;/STRONG&gt;&lt;/FONT&gt;&lt;BR /&gt;- Traditional default netboot filename (0x0002)&lt;/PRE&gt;
&lt;P&gt;The correct default setting of your configuration register should be&lt;/P&gt;
&lt;PRE&gt;0x2102&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;Once you get the chance, please change it and reload the router:&lt;/P&gt;
&lt;PRE&gt;configure terminal&lt;BR /&gt;config-register 0x2102&lt;BR /&gt;end&lt;BR /&gt;copy run start&lt;BR /&gt;reload&lt;/PRE&gt;
&lt;P&gt;I have also reviewed your configuration, and you have a few additional problems there that are unrelated to this issue but that would come back and bite you later.&lt;/P&gt;
&lt;P&gt;1) You have Cisco Express Forwarding (CEF) disabled. This will decrease the throughput your router can provide, and increases the CPU load when routing packets. Please enable CEF by&lt;/P&gt;
&lt;PRE&gt;configure terminal&lt;BR /&gt;ip cef&lt;BR /&gt;end&lt;/PRE&gt;
&lt;P&gt;2) Your NAT configuration is partially wrong, partially incomplete.&lt;/P&gt;
&lt;P&gt;What's &lt;EM&gt;incomplete&lt;/EM&gt;: Your interface Vlan25 is marked as inside which is okay, but you don't have an interface marked as outside. This is a must without exceptions. Based on your configuration, I assume that it is&lt;/P&gt;
&lt;PRE&gt;FastEthernet0/0&lt;/PRE&gt;
&lt;P&gt;that should be marked as outside.&lt;/P&gt;
&lt;P&gt;What's &lt;EM&gt;wrong&lt;/EM&gt;: You have used the&lt;/P&gt;
&lt;PRE&gt;ip nat source list NAT interface FastEthernet0/0 overload&lt;/PRE&gt;
&lt;P&gt;command to specify how the packets should be translated. However, you missed the &lt;STRONG&gt;inside&lt;/STRONG&gt; keyword from this command. Without the &lt;STRONG&gt;inside&lt;/STRONG&gt; keyword, this command refers to another method and style of NAT configuration we call the NVI style, and that requires different configuration of the interfaces as well&lt;/P&gt;
&lt;PRE&gt;ip nat enable instead of ip nat inside/outside&lt;/PRE&gt;
&lt;P&gt;With your current configuration, the NAT would not work at all.&lt;/P&gt;
&lt;P&gt;To fix both issues, configure:&lt;/P&gt;
&lt;PRE&gt;configure terminal&lt;BR /&gt;no ip nat source list NAT interface FastEthernet0/0 overload&lt;BR /&gt;ip nat inside source list NAT interface FastEthernet0/0 overload&lt;BR /&gt;interface FastEthernet0/0&lt;BR /&gt;ip nat outside&lt;BR /&gt;end&lt;/PRE&gt;
&lt;P&gt;3) Your&lt;/P&gt;
&lt;PRE&gt;default route&lt;/PRE&gt;
&lt;P&gt;is statically configured out the&lt;/P&gt;
&lt;PRE&gt;Fa0/0&lt;/PRE&gt;
&lt;P&gt;interface without a next hop. Pointing a static route out a multi-access interface such as Ethernet &lt;EM&gt;without&lt;/EM&gt; a next hop address is a &lt;U&gt;strong, resounding no&lt;/U&gt;. It causes an excessive ARP traffic and an excessively large ARP cache, and is completely dependent on your upstream router having Proxy ARP enabled (it is because such route causes the entire internet to be considered as directly connected on your&lt;/P&gt;
&lt;PRE&gt;Fa0/0&lt;/PRE&gt;
&lt;P&gt;and hence ARP-able). We already saw situations where, through this configuration, the ARP cache grew so large that it caused the router to exhaust all memory and crash - only to exhaust it again, ending in neverending repeated crashes.&lt;/P&gt;
&lt;P&gt;I understand you configured it this way because with DHCP, you cannot assume to know the next hop address in advance. However, you do not need to configure any static&lt;/P&gt;
&lt;PRE&gt;default route&lt;/PRE&gt;
&lt;P&gt;if you are using DHCP. If the DHCP assigns you a&lt;/P&gt;
&lt;PRE&gt;default route&lt;/PRE&gt;
&lt;P&gt;it will be put into your routing table automatically without any additional configuration (with an AD of 254). If you still want to configure it statically because you want to give it a better AD, you can do it but you still need to specify the&lt;/P&gt;
&lt;PRE&gt;dhcp&lt;/PRE&gt;
&lt;P&gt;keyword in the static route to avoid the problems specified above.&lt;/P&gt;
&lt;P&gt;To fix this:&lt;/P&gt;
&lt;PRE&gt;configure terminal&lt;BR /&gt;no ip route 0.0.0.0 0.0.0.0 FastEthernet0/0&lt;BR /&gt;&lt;BR /&gt;! ... and if you insist on having it configured statically because you want to lower its AD:&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 FastEthernet0/0 dhcp&lt;BR /&gt;end&lt;/PRE&gt;
&lt;P&gt;Hopefully, this all will make your router work properly.&lt;/P&gt;
&lt;P&gt;Please feel welcome to ask further!&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 07 Aug 2023 06:19:37 GMT</pubDate>
    <dc:creator>Peter Paluch</dc:creator>
    <dc:date>2023-08-07T06:19:37Z</dc:date>
    <item>
      <title>Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893445#M386907</link>
      <description>&lt;P&gt;Have configured an interface on cisco 2811 for DHCP, it is up/up but not accepting an address. I've attached a basic config and DHCP debug. Any advice would be appreciated, any further info can be provided.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 07:10:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893445#M386907</guid>
      <dc:creator>Adam_S</dc:creator>
      <dc:date>2023-07-27T07:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893474#M386908</link>
      <description>&lt;P&gt;Adam,&lt;/P&gt;
&lt;P&gt;There don't seem to be any attachments included with your post. I wonder if they might be getting scrubbed or something. Could you try attaching them again?&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 08:02:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893474#M386908</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2023-07-27T08:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893485#M386909</link>
      <description>&lt;P&gt;ive reattached the file. Hopefully it takes. Below are the contents just in case:&lt;/P&gt;
&lt;PRE&gt;Cisco-2811#show ip int brief&lt;BR /&gt;Interface IP-Address OK? Method Status Protocol&lt;BR /&gt;FastEthernet0/0 unassigned YES DHCP up up&lt;BR /&gt;FastEthernet0/1 192.168.1.2 YES NVRAM up up&lt;BR /&gt;FastEthernet0/1/0 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/1 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/2 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/3 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/4 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/5 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/6 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/7 unassigned YES unset up down&lt;BR /&gt;FastEthernet0/1/8 unassigned YES unset up down&lt;BR /&gt;Serial0/3/0 unassigned YES NVRAM administratively down down&lt;BR /&gt;Vlan1 unassigned YES NVRAM administratively down down&lt;BR /&gt;Vlan25 192.168.25.1 YES NVRAM up down&lt;BR /&gt;NVI0 2.2.2.2 YES unset up up&lt;BR /&gt;Loopback0 2.2.2.2 YES NVRAM up up&lt;BR /&gt;Cisco-2811#show run int&lt;BR /&gt;Cisco-2811#show run interface fa&lt;BR /&gt;Cisco-2811#show run interface fastEthernet 0/0&lt;BR /&gt;Building configuration...&lt;BR /&gt;&lt;BR /&gt;Current configuration : 204 bytes&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/0&lt;BR /&gt;description internet&lt;BR /&gt;ip address dhcp&lt;BR /&gt;ip broadcast-address 0.0.0.0&lt;BR /&gt;no ip redirects&lt;BR /&gt;no ip unreachables&lt;BR /&gt;no ip proxy-arp&lt;BR /&gt;ip virtual-reassembly&lt;BR /&gt;duplex auto&lt;BR /&gt;speed auto&lt;BR /&gt;end&lt;BR /&gt;&lt;BR /&gt;Cisco-2811#show version&lt;BR /&gt;Cisco IOS Software, 2800 Software (C2800NM-ADVIPSERVICESK9-M), Version 12.4(15)T9, RELEASE SOFTWARE (fc5)&lt;BR /&gt;Technical Support: &lt;A href="http://www.cisco.com/techsupport" target="_blank" rel="noopener"&gt;http://www.cisco.com/techsupport&lt;/A&gt;&lt;BR /&gt;Copyright (c) 1986-2009 by Cisco Systems, Inc.&lt;BR /&gt;Compiled Tue 28-Apr-09 13:09 by prod_rel_team&lt;BR /&gt;&lt;BR /&gt;ROM: System Bootstrap, Version 12.4(13r)T5, RELEASE SOFTWARE (fc1)&lt;BR /&gt;&lt;BR /&gt;Cisco-2811 uptime is 57 minutes&lt;BR /&gt;System returned to ROM by power-on&lt;BR /&gt;System image file is "flash:c2800nm-advipservicesk9-mz.124-15.T9.bin"&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;*Nov 26 05:32:14 AEDST: DHCP: QScan: Purging entry&lt;BR /&gt;*Nov 26 05:32:14 AEDST: DHCP: deleting entry 49241A08 0.0.0.0 from list&lt;BR /&gt;*Nov 26 05:32:14 AEDST: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0/0&lt;BR /&gt;*Nov 26 05:32:14 AEDST: Temp sub net mask: 0.0.0.0&lt;BR /&gt;*Nov 26 05:32:14 AEDST: DHCP Lease server: 0.0.0.0, state: 11 Purging&lt;BR /&gt;*Nov 26 05:32:14 AEDST: DHCP transaction id: EB4&lt;BR /&gt;*Nov 26 05:32:14 AEDST: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs&lt;BR /&gt;*Nov 26 05:32:14 AEDST: No timer running&lt;BR /&gt;*Nov 26 05:32:14 AEDST: Retry count: 0 Client-ID: cisco-0015.633b.8ba0-Fa0/0&lt;BR /&gt;*Nov 26 05:32:14 AEDST: Client-ID hex dump: 636973636F2D303031352E363333622E&lt;BR /&gt;*Nov 26 05:32:14 AEDST: 386261302D4661302F30&lt;BR /&gt;*Nov 26 05:32:14 AEDST: Hostname: Cisco-2811&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP: Try 49 to acquire address for FastEthernet0/0&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP: allocate request&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP: new entry. add to queue, interface FastEthernet0/0&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP: SDiscover attempt # 1 for entry:&lt;BR /&gt;*Nov 26 05:32:44 AEDST: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0/0&lt;BR /&gt;*Nov 26 05:32:44 AEDST: Temp sub net mask: 0.0.0.0&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP Lease server: 0.0.0.0, state: 3 Selecting&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP transaction id: EB5&lt;BR /&gt;*Nov 26 05:32:44 AEDST: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs&lt;BR /&gt;*Nov 26 05:32:44 AEDST: Next timer fires after: 00:00:04&lt;BR /&gt;*Nov 26 05:32:44 AEDST: Retry count: 1 Client-ID: cisco-0015.633b.8ba0-Fa0/0&lt;BR /&gt;*Nov 26 05:32:44 AEDST: Client-ID hex dump: 636973636F2D303031352E363333622E&lt;BR /&gt;*Nov 26 05:32:44 AEDST: 386261302D4661302F30&lt;BR /&gt;*Nov 26 05:32:44 AEDST: Hostname: Cisco-2811&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP: SDiscover: sending 299 byte length DHCP packet&lt;BR /&gt;*Nov 26 05:32:44 AEDST: DHCP: SDiscover 299 bytes&lt;BR /&gt;*Nov 26 05:32:44 AEDST: B'cast on FastEthernet0/0 interface from 0.0.0.0&lt;BR /&gt;*Nov 26 05:32:47 AEDST: DHCP: SDiscover attempt # 2 for entry:&lt;BR /&gt;*Nov 26 05:32:47 AEDST: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0/0&lt;BR /&gt;*Nov 26 05:32:47 AEDST: Temp sub net mask: 0.0.0.0&lt;BR /&gt;*Nov 26 05:32:47 AEDST: DHCP Lease server: 0.0.0.0, state: 3 Selecting&lt;BR /&gt;*Nov 26 05:32:47 AEDST: DHCP transaction id: EB5&lt;BR /&gt;*Nov 26 05:32:47 AEDST: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs&lt;BR /&gt;*Nov 26 05:32:47 AEDST: Next timer fires after: 00:00:04&lt;BR /&gt;*Nov 26 05:32:47 AEDST: Retry count: 2 Client-ID: cisco-0015.633b.8ba0-Fa0/0&lt;BR /&gt;*Nov 26 05:32:47 AEDST: Client-ID hex dump: 636973636F2D303031352E363333622E&lt;BR /&gt;*Nov 26 05:32:47 AEDST: 386261302D4661302F30&lt;BR /&gt;*Nov 26 05:32:47 AEDST: Hostname: Cisco-2811&lt;BR /&gt;*Nov 26 05:32:47 AEDST: DHCP: SDiscover: sending 299 byte length DHCP packet&lt;BR /&gt;*Nov 26 05:32:47 AEDST: DHCP: SDiscover 299 bytes&lt;BR /&gt;*Nov 26 05:32:47 AEDST: B'cast on FastEthernet0/0 interface from 0.0.0.0&lt;BR /&gt;*Nov 26 05:32:51 AEDST: DHCP: SDiscover attempt # 3 for entry:&lt;BR /&gt;*Nov 26 05:32:51 AEDST: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0/0&lt;BR /&gt;*Nov 26 05:32:51 AEDST: Temp sub net mask: 0.0.0.0&lt;BR /&gt;*Nov 26 05:32:51 AEDST: DHCP Lease server: 0.0.0.0, state: 3 Selecting&lt;BR /&gt;*Nov 26 05:32:51 AEDST: DHCP transaction id: EB5&lt;BR /&gt;*Nov 26 05:32:51 AEDST: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs&lt;BR /&gt;*Nov 26 05:32:51 AEDST: Next timer fires after: 00:00:04&lt;BR /&gt;*Nov 26 05:32:51 AEDST: Retry count: 3 Client-ID: cisco-0015.633b.8ba0-Fa0/0&lt;BR /&gt;*Nov 26 05:32:51 AEDST: Client-ID hex dump: 636973636F2D303031352E363333622E&lt;BR /&gt;*Nov 26 05:32:51 AEDST: 386261302D4661302F30&lt;/PRE&gt;</description>
      <pubDate>Mon, 07 Aug 2023 05:50:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893485#M386909</guid>
      <dc:creator>Adam_S</dc:creator>
      <dc:date>2023-08-07T05:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893489#M386910</link>
      <description>&lt;P&gt;Hi Adam,&lt;/P&gt;
&lt;P&gt;Can you remove the&lt;/P&gt;
&lt;PRE&gt;ip broadcast-address 0.0.0.0 from your Fa0/0&lt;/PRE&gt;
&lt;P&gt;and try again? This is a configuration for very legacy devices that used the destination IP address of&lt;/P&gt;
&lt;PRE&gt;0.0.0.0 as a broadcast&lt;/PRE&gt;
&lt;P&gt;rather than&lt;/P&gt;
&lt;PRE&gt;255.255.255.255&lt;/PRE&gt;
&lt;P&gt;However, DHCP servers commonly listen to&lt;/P&gt;
&lt;PRE&gt;255.255.255.255&lt;/PRE&gt;
&lt;P&gt;this might be the reason. In fact, all you need on your&lt;/P&gt;
&lt;PRE&gt;Fa0/0 is ip address dhcp  and no shutdown&lt;/PRE&gt;
&lt;P&gt;no other manual configuration is required.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 05:53:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893489#M386910</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2023-08-07T05:53:00Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893491#M386911</link>
      <description>&lt;P&gt;hi,&lt;/P&gt;
&lt;P&gt;can you do this?&lt;/P&gt;
&lt;PRE&gt;&lt;EM&gt;interface FastEthernet0/0&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;no ip address dhcp&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;no ip broadcast-address 0.0.0.0&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;ip address dhcp client-id FastEthernet0/0&lt;/EM&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:31:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893491#M386911</guid>
      <dc:creator>johnlloyd_13</dc:creator>
      <dc:date>2023-08-07T06:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893494#M386912</link>
      <description>&lt;P&gt;Hey John,&lt;/P&gt;
&lt;P&gt;Good eye on the&lt;/P&gt;
&lt;PRE&gt;ip broadcast-address 0.0.0.0&lt;/PRE&gt;
&lt;P&gt;A friendful comment: The&lt;/P&gt;
&lt;PRE&gt;client-id Fa0/0&lt;/PRE&gt;
&lt;P&gt;forces the DHCP client to identify itself by deriving its identity from the MAC address of the&lt;/P&gt;
&lt;PRE&gt;Fa0/0&lt;/PRE&gt;
&lt;P&gt;interface. This is required when the DHCP server is offering a stable IP to the client based on its identification. It is very safe to try this out, but if the DHCP server is not intentionally configured in advance for this identifier, then any should do, in which case the&lt;/P&gt;
&lt;PRE&gt;client-id Fa0/0&lt;/PRE&gt;
&lt;P&gt;is not required.&lt;/P&gt;
&lt;P&gt;Let's see what Adam comes back with.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:34:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893494#M386912</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2023-08-07T06:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893499#M386913</link>
      <description>&lt;P&gt;thanks for the suggestion. I removed the&lt;/P&gt;
&lt;PRE&gt; ip broadcast 0.0.0.0&lt;/PRE&gt;
&lt;P&gt;command, but&lt;BR /&gt;as soon as it tries to broadcast for a DHCP address the router inmediately&lt;BR /&gt;adds the command back to the interface config.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;PRE&gt;##- Please type your reply above this line -#&lt;/PRE&gt;</description>
      <pubDate>Mon, 07 Aug 2023 05:54:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893499#M386913</guid>
      <dc:creator>Adam_S</dc:creator>
      <dc:date>2023-08-07T05:54:36Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893501#M386914</link>
      <description>Thanks. I tried this, no difference.&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Jul 2023 08:39:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893501#M386914</guid>
      <dc:creator>Adam_S</dc:creator>
      <dc:date>2023-07-27T08:39:50Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893507#M386915</link>
      <description>&lt;P&gt;Adam,&lt;/P&gt;
&lt;P&gt;This is getting very weird.&lt;/P&gt;
&lt;P&gt;I would like to ask you to share the &lt;U&gt;full&lt;/U&gt; output of the&lt;/P&gt;
&lt;PRE&gt;show version and show running-config&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;I am particularly interested in seeing the value of your configuration register, and some of the old-style configuration that might for some reason be lurking around (such as&lt;/P&gt;
&lt;PRE&gt;no ip classless no ip routing&lt;/PRE&gt;
&lt;P&gt;etc.).&lt;/P&gt;
&lt;P&gt;The configuration register might be important because I do recall that there was one bit in it that forced the broadcast address to be either all-zeros or all-ones.&lt;/P&gt;
&lt;P&gt;From the debugs, it's clear you are sending out DHCP Discover but never get back an Offer from the server.&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 05:56:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893507#M386915</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2023-08-07T05:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893512#M386916</link>
      <description>&lt;P&gt;You try what ?&lt;/P&gt;
&lt;P&gt;The client ID must be same as what&lt;/P&gt;
&lt;PRE&gt;dhcp server&lt;/PRE&gt;
&lt;P&gt;use you need to contact ISP ask them the clinet ID format they use. Then config your router to send same client ID.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:35:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893512#M386916</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-08-07T06:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893517#M386917</link>
      <description>&lt;P&gt;Hello buddy,&lt;/P&gt;
&lt;P&gt;I touched that topic here already: &lt;A href="https://community.cisco.com/t5/routing/interface-not-accepting-dhcp-address/m-p/4893494/highlight/true#M386912" target="_blank"&gt;https://community.cisco.com/t5/routing/interface-not-accepting-dhcp-address/m-p/4893494/highlight/true#M386912&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Unless we have an evidence that this is even an ISP scenario and not a lab test, and that the ISP is expecting a specific DHCP client ID to allocate IP addresses, we cannot say that Adam "must" do anything. Let's wait for Adam to come back with more information.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 09:08:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893517#M386917</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2023-07-27T09:08:50Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893522#M386918</link>
      <description>&lt;P&gt;Thanks I just clarify point here.&lt;/P&gt;
&lt;P&gt;Have a nice summer&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 09:15:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893522#M386918</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-07-27T09:15:39Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893526#M386919</link>
      <description>Right you are. Sorry i probably should of mentioned that this is indded a&lt;BR /&gt;test lab, connected to a cisco 3845. With the DHCP pool configured. I will&lt;BR /&gt;provide the request config in the next couple of days.&lt;BR /&gt;</description>
      <pubDate>Thu, 27 Jul 2023 09:20:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893526#M386919</guid>
      <dc:creator>Adam_S</dc:creator>
      <dc:date>2023-07-27T09:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893575#M386925</link>
      <description>&lt;P&gt;if it LAB then check&amp;nbsp;&lt;BR /&gt;the interface receive the DHCP discover must be in same subnet of DHCP POOL, check the subnet and subnet MASK&amp;nbsp;&lt;BR /&gt;also if you use excluded&lt;/P&gt;
&lt;PRE&gt;255.255.255.255 or x.x.x.255&lt;/PRE&gt;
&lt;P&gt;remove it.&amp;nbsp;&lt;BR /&gt;and check again.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;have a nice summer&amp;nbsp;&lt;BR /&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:36:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893575#M386925</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-08-07T06:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893672#M386932</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;as mentioned by others, you are running a very old IOS version, which requires the DHCP broadcast to go to&lt;/P&gt;
&lt;PRE&gt;0.0.0.0 instead of 255.255.255.255&lt;/PRE&gt;
&lt;P&gt;I somewhere recall that the global config command&lt;/P&gt;
&lt;PRE&gt;no ip source-route disables ip directed broadcasts&lt;/PRE&gt;
&lt;P&gt;can you try that command&amp;nbsp; and check if the interface still adds&lt;/P&gt;
&lt;PRE&gt;ip directed-broadcast 0.0.0.0&lt;/PRE&gt;
&lt;P&gt;to the interface ?&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:38:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893672#M386932</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2023-08-07T06:38:11Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893685#M386934</link>
      <description>&lt;P&gt;Hi Georg,&lt;/P&gt;
&lt;P&gt;A very humble correction: The IOS on Adam's 2811 router is admittedly old but not tragically so - it's 12.4(15)T9. Back in my days at the university and NetAcad, we'd use even older versions (12.2, 12.3, 12.4) which would already be using&lt;/P&gt;
&lt;PRE&gt;255.255.255.255, not 0.0.0.0, as the default limited-broadcast address&lt;/PRE&gt;
&lt;P&gt;So I am very confident that the IOS version itself isn't the problem.&lt;/P&gt;
&lt;P&gt;As for the&lt;/P&gt;
&lt;PRE&gt;no ip source-route&lt;/PRE&gt;
&lt;P&gt;that would be an interesting although unexpected correlation. Source routing is about the packet's sender explicitly putting the list of transit hops (up to 9) into the packet's header. But the packet still needs to be unicast... so I'm not sure why would that command have any bearing on the limited-broadcast address. But doesn't harm to test anyway, certainly!&lt;/P&gt;
&lt;P&gt;I keep my hopes high about the config register and/or the complete configuration having something odd there.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:40:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893685#M386934</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2023-08-07T06:40:57Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893695#M386937</link>
      <description>&lt;P&gt;Hello Peter,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am probably wrong, and you likely right. I just remembered there was something about the source routing. My very first router was running an 11.x version, there were all kinds of 'weird' things going on.&lt;/P&gt;
&lt;P&gt;Curious to see how this gets resolved...&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jul 2023 12:40:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893695#M386937</guid>
      <dc:creator>Georg Pauwen</dc:creator>
      <dc:date>2023-07-27T12:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893700#M386940</link>
      <description>&lt;P&gt;Hi Georg,&lt;/P&gt;
&lt;P&gt;Oh, yes, there was this&lt;/P&gt;
&lt;PRE&gt;no ip classless&lt;/PRE&gt;
&lt;P&gt;configured by default, and there was the&lt;/P&gt;
&lt;PRE&gt;ip subnet-zero&lt;/PRE&gt;
&lt;P&gt;which allowed or disallowed the use of the first subnet of a major network (for example,&lt;/P&gt;
&lt;PRE&gt;10.0.0.0/24 of 10.0.0.0/8&lt;/PRE&gt;
&lt;P&gt;). Weird classful times indeed! : )&lt;/P&gt;
&lt;P&gt;Best regards,&lt;BR /&gt;Peter&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:43:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893700#M386940</guid>
      <dc:creator>Peter Paluch</dc:creator>
      <dc:date>2023-08-07T06:43:47Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893777#M386943</link>
      <description>&lt;P&gt;Georg, if you do recall something&lt;/P&gt;
&lt;PRE&gt;weird&lt;/PRE&gt;
&lt;P&gt;about source routing, please send me a follow up message.&lt;/P&gt;
&lt;P&gt;Reason I ask, possibly I'm among the few that liked to use source routing while troubleshooting some network issues.&lt;/P&gt;
&lt;P&gt;BTW, I know disabling source routing applied to transit traffic, don't know if it also applies to same device sourced traffic.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Aug 2023 06:47:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4893777#M386943</guid>
      <dc:creator>Joseph W. Doherty</dc:creator>
      <dc:date>2023-08-07T06:47:02Z</dc:date>
    </item>
    <item>
      <title>Re: Interface not accepting DHCP address</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4894131#M386959</link>
      <description>&lt;PRE&gt;Cisco-2811#show run&lt;BR /&gt;Building configuration...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Current configuration : 4851 bytes&lt;BR /&gt;!&lt;BR /&gt;version 12.4&lt;BR /&gt;service timestamps debug datetime localtime show-timezone&lt;BR /&gt;service timestamps log datetime localtime show-timezone&lt;BR /&gt;service password-encryption&lt;BR /&gt;!&lt;BR /&gt;hostname Cisco-2811&lt;BR /&gt;!&lt;BR /&gt;boot-start-marker&lt;BR /&gt;boot system flash:c2800nm-advipservicesk9-mz.124-15.T9.bin&lt;BR /&gt;boot-end-marker&lt;BR /&gt;!&lt;BR /&gt;logging buffered 4096 informational&lt;BR /&gt;enable secret 5 X.X.X&lt;BR /&gt;!&lt;BR /&gt;no aaa new-model&lt;BR /&gt;clock timezone AEST 10&lt;BR /&gt;clock summer-time AEDST recurring 1 Sun Oct 2:00 1 Sun Apr 2:00&lt;BR /&gt;dot11 syslog&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;no ip cef&lt;BR /&gt;no ip dhcp use vrf connected&lt;BR /&gt;ip dhcp excluded-address 192.168.25.1 192.168.25.100&lt;BR /&gt;!&lt;BR /&gt;ip dhcp pool LAN&lt;BR /&gt;network 192.168.25.0 255.255.255.0&lt;BR /&gt;dns-server 1.1.1.1&lt;BR /&gt;default-router 192.168.25.1&lt;BR /&gt;lease 24&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;no ip domain lookup&lt;BR /&gt;!&lt;BR /&gt;multilink bundle-name authenticated&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;voice-card 0&lt;BR /&gt;no dspfarm&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;vtp domain home&lt;BR /&gt;vtp mode transparent&lt;BR /&gt;archive&lt;BR /&gt;log config&lt;BR /&gt;hidekeys&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;vlan 25&lt;BR /&gt;name LAN&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;interface Loopback0&lt;BR /&gt;ip address 2.2.2.2 255.255.255.255&lt;BR /&gt;ip broadcast-address 0.0.0.0&lt;BR /&gt;h323-gateway voip interface&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/0&lt;BR /&gt;description internet&lt;BR /&gt;ip address dhcp client-id FastEthernet0/0&lt;BR /&gt;ip broadcast-address 0.0.0.0&lt;BR /&gt;duplex auto&lt;BR /&gt;speed auto&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1&lt;BR /&gt;ip address 192.168.1.2 255.255.255.252&lt;BR /&gt;ip broadcast-address 0.0.0.0&lt;BR /&gt;duplex full&lt;BR /&gt;speed auto&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/0&lt;BR /&gt;switchport access vlan 25&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/1&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/2&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/3&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/4&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/5&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/6&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/7&lt;BR /&gt;!&lt;BR /&gt;interface FastEthernet0/1/8&lt;BR /&gt;!&lt;BR /&gt;interface Serial0/3/0&lt;BR /&gt;no ip address&lt;BR /&gt;ip broadcast-address 0.0.0.0&lt;BR /&gt;encapsulation frame-relay&lt;BR /&gt;shutdown&lt;BR /&gt;clock rate 2000000&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;no ip address&lt;BR /&gt;ip broadcast-address 0.0.0.0&lt;BR /&gt;shutdown&lt;BR /&gt;!&lt;BR /&gt;interface Vlan25&lt;BR /&gt;description LAN&lt;BR /&gt;ip address 192.168.25.1 255.255.255.0&lt;BR /&gt;ip broadcast-address 0.0.0.0&lt;BR /&gt;ip nat inside&lt;BR /&gt;ip virtual-reassembly&lt;BR /&gt;!&lt;BR /&gt;router ospf 100&lt;BR /&gt;log-adjacency-changes&lt;BR /&gt;network 2.2.2.2 0.0.0.0 area 0&lt;BR /&gt;network 192.168.1.0 0.0.0.3 area 0&lt;BR /&gt;network 193.168.1.0 0.0.0.3 area 0&lt;BR /&gt;!&lt;BR /&gt;no ip forward-protocol nd&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 FastEthernet0/0&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;no ip http server&lt;BR /&gt;no ip http secure-server&lt;BR /&gt;ip nat source list NAT interface FastEthernet0/0 overload&lt;BR /&gt;!&lt;BR /&gt;ip access-list extended NAT&lt;BR /&gt;permit ip 192.168.25.0 0.0.0.255 any&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;tftp-server flash:/c7921/APPS-1.0.4.SBN alias APPS-1.0.4.SBN&lt;BR /&gt;tftp-server flash:/c7921/CP7921G-1.0.4.LOADS alias CP7921G-1.0.4.LOADS&lt;BR /&gt;tftp-server flash:/c7921/GUI-1.0.4.SBN alias GUI-1.0.4.SBN&lt;BR /&gt;tftp-server flash:/c7921/SYS-1.0.4.SBN alias SYS-1.0.4.SBN&lt;BR /&gt;tftp-server flash:/c7921/TNUX-1.0.4.SBN alias TNUX-1.0.4.SBN&lt;BR /&gt;tftp-server flash:/c7921/TNUXR-1.0.4.SBN alias TNUXR-1.0.4.SBN&lt;BR /&gt;tftp-server flash:/c7921/WLAN-1.0.4.SBN alias WLAN-1.0.4.SBN&lt;BR /&gt;tftp-server flash:/c7911new/c7911/apps11.8-3-2-27.sbn alias apps11.8-3-2-27.sbn&lt;BR /&gt;tftp-server flash:/c7911new/c7911/cnu11.8-3-2-27.sbn alias cnu11.8-3-2-27.sbn&lt;BR /&gt;tftp-server flash:/c7911new/c7911/cvm11sccp.8-3-2-27.sbn alias cvm11sccp.8-3-2-27.sbn&lt;BR /&gt;tftp-server flash:/c7911new/c7911/dsp11.8-3-2-27.sbn alias dsp11.8-3-2-27.sbn&lt;BR /&gt;tftp-server flash:/c7911new/c7911/jar11sccp.8-3-2-27.sbn alias jar11sccp.8-3-2-27.sbn&lt;BR /&gt;tftp-server flash:/c7911new/c7911/SCCP11.8-3-3S.loads alias SCCP11.8-3-3S.loads&lt;BR /&gt;tftp-server flash:/c7911new/c7911/term06.default.loads alias term06.default.loads&lt;BR /&gt;tftp-server flash:/c7911new/c7911/term11.default.loads alias term11.default.loads&lt;BR /&gt;!&lt;BR /&gt;control-plane&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;voice-port 0/2/0&lt;BR /&gt;!&lt;BR /&gt;voice-port 0/2/1&lt;BR /&gt;!&lt;BR /&gt;ccm-manager redundant-host 10.12.0.21&lt;BR /&gt;ccm-manager mgcp&lt;BR /&gt;no ccm-manager fax protocol cisco&lt;BR /&gt;ccm-manager music-on-hold bind Loopback0&lt;BR /&gt;ccm-manager config server 10.12.0.21&lt;BR /&gt;ccm-manager config&lt;BR /&gt;!&lt;BR /&gt;mgcp&lt;BR /&gt;mgcp call-agent 10.12.0.25 2427 service-type mgcp version 0.1&lt;BR /&gt;mgcp rtp unreachable timeout 1000 action notify&lt;BR /&gt;mgcp modem passthrough voip mode nse&lt;BR /&gt;mgcp package-capability rtp-package&lt;BR /&gt;mgcp package-capability sst-package&lt;BR /&gt;mgcp package-capability pre-package&lt;BR /&gt;no mgcp package-capability res-package&lt;BR /&gt;no mgcp timer receive-rtcp&lt;BR /&gt;mgcp sdp simple&lt;BR /&gt;mgcp rtp payload-type g726r16 static&lt;BR /&gt;mgcp behavior g729-variants static-pt&lt;BR /&gt;!&lt;BR /&gt;mgcp profile default&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;dial-peer voice 999020 pots&lt;BR /&gt;service mgcpapp&lt;BR /&gt;port 0/2/0&lt;BR /&gt;!&lt;BR /&gt;dial-peer voice 999021 pots&lt;BR /&gt;service mgcpapp&lt;BR /&gt;port 0/2/1&lt;BR /&gt;!&lt;BR /&gt;dial-peer voice 999030 pots&lt;BR /&gt;service mgcpapp&lt;BR /&gt;!&lt;BR /&gt;dial-peer voice 1 voip&lt;BR /&gt;destination-pattern 10924&lt;BR /&gt;session target ipv4:10.255.255.255&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;call-manager-fallback&lt;BR /&gt;max-conferences 8 gain -6&lt;BR /&gt;transfer-system full-consult&lt;BR /&gt;ip source-address 10.255.255.255 port 2000&lt;BR /&gt;max-ephones 5&lt;BR /&gt;max-dn 5&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;line con 0&lt;BR /&gt;line aux 0&lt;BR /&gt;line vty 0 4&lt;BR /&gt;exec-timeout 0 0&lt;BR /&gt;privilege level 15&lt;BR /&gt;password 7 X.X.X&lt;BR /&gt;login&lt;BR /&gt;line vty 5&lt;BR /&gt;exec-timeout 0 0&lt;BR /&gt;password 7 X.X.X&lt;BR /&gt;login&lt;BR /&gt;!&lt;BR /&gt;scheduler allocate 20000 1000&lt;BR /&gt;ntp clock-period 17180114&lt;BR /&gt;ntp update-calendar&lt;BR /&gt;ntp server 216.239.35.4&lt;BR /&gt;sntp broadcast client&lt;BR /&gt;!&lt;BR /&gt;end&lt;/PRE&gt;</description>
      <pubDate>Mon, 07 Aug 2023 05:57:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/interface-not-accepting-dhcp-address/m-p/4894131#M386959</guid>
      <dc:creator>Adam_S</dc:creator>
      <dc:date>2023-08-07T05:57:31Z</dc:date>
    </item>
  </channel>
</rss>

