Oliver Boehmer (oboehmer) wrote:
I think the config doesn't honor TTL, so the implementation is rather "basic"..
Would that be basic as in it only resolves the FQDN once when the config is entered, once per boot, or possibly on a schedule later on in the lifecycle of the router?
I noticed other changes between 24T1 and 24T2 that bit me this weekend when I upgraded 2 routers that are my NTP servers. First off all the NTP config that was moved way up in the config in an earlier release suddenly got moved back to where it was. Not a big deal but it makes RANCID unhappy. Second, and this is a bad problem, it removed my "ntp source <int>" command from the config. I didn't notice until today that my NTP servers weren't syncing up right. Reviewing the RANCID diff pointed out the problem.
This happened on both of the routers that I upgraded from 24T1 to 24T2. I haven't rebooted either router to see if the problem will happen after every 24T2 reboot or if it's tied to the moving around of the config between 24T1 and 24T2. My guess would be the latter, at least I hope that's the case. I've contacted TAC to report this bug.
Justin _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
