fwsm - ver 3.2(5) in cat 6509-E(12.2 SXI) The last-config-change timestamp in the running-copy of the config reflects the current-time in the following cases:
1) more system:running-config 2) copy running-config to a remote server and open via regular text editor. A sh run in the module has always stripped out the info and I am aware of that behavior but this one is new. I would leave it as a not-quite-so-cosmetic bug but in this case RANCID for obvious reasons, sees the different timestamp and emails the meaningless diffs to me and the PHB's and I have to explain... The startup-config reflects the actual-time a change was made. Wondering if anyone has seen this behavior and knows of a workaround short-of-an-upgrade. There is nothing related to this in cco- release notes/bug reports. Any insight would be appreciated. ./Randy _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
