tag:blogger.com,1999:blog-23021255.post6421045053538234915..comments2008-04-02T10:12:13.063+02:00Comments on Cisco IOS hints and tricks: Track the DHCP default routeIvan Pepelnjakhttp://www.blogger.com/profile/13457151406311272386noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-23021255.post-47349142447639011772008-04-02T10:12:00.000+02:002008-04-02T10:12:00.000+02:002008-04-02T10:12:00.000+02:00Looks like a bug to me. Try your luck with bug nav...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.Ivan Pepelnjakhttp://www.blogger.com/profile/13457151406311272386noreply@blogger.comtag:blogger.com,1999:blog-23021255.post-47825096679648059992008-03-31T21:44:00.000+02:002008-03-31T21:44:00.000+02:002008-03-31T21:44:00.000+02:00Ivan:We've run across what seems an odd anomaly. W...Ivan:<BR/>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.<BR/><BR/>Have you seen this situation?Anonymousnoreply@blogger.com