Building network automation solutions

9 module online course

Start now!

6 comments:

  1. Ivan:
    We've run across what seems an odd anomaly. When configuring an interface address as DHCP, the address, mask, and DNS options operate correctly but the route table updates only after the initial zero crossing of the 'next timer fires after' value. Occasionally, this timer starts at values of more than 30 minutes.

    Have you seen this situation?
    Replies
    1. I just experienced the same with a Cisco 1900 with IOS 15.3.3M1. When the router would boot up the default gateway would either not be set or set to 0.0.0.0.
  2. Looks like a bug to me. Try your luck with bug navigator, maybe you'll get a hit; otherwise you should open a case with Cisco TAC.
  3. it seems that the track option can't be configured when configuring a static route for a DHCP next hop. i.e. can't do "ip route 0.0.0.0 0.0.0.0 fas0/1 dhcp track 123". Using a 2811 with IOS 12.4.11 advancedIP... does it exist in any IOS?
  4. I fought this trying to use a static route. I got it working with a floating route in the interface.

    interface FastEthernet0
    ip dhcp client route track 101
    ip address dhcp client-id FastEthernet0
    ip virtual-reassembly
    ....

    interface FastEthernet1
    ip dhcp client route track 102
    ip address dhcp client-id FastEthernet1
    ip virtual-reassembly
    ....
  5. To setup the route for tracking with dhcp use this:

    conf t
    int fastethernet 0
    ip dhcp client route track 101
    ...
    int fastethernet 1
    ip dhcp client route track 102
    ...
Add comment
Sidebar