01-22-2009 01:00 AM
I have a few FWSM contexts (Version 3.2(7)) which always appear in the Startup and Running Out-Of-Sync report.
The obvious reason is, that the "show running-config" command on the FWSM hides "asdm" commands, while "show startup" does include them.
IMHO, hiding commands from "show runn" is an insane idea in the first place. But I don't think I have a chance to get this fixed.
RME should cope with this problem, anyway.
The obviuos workaround would be to use "show running-config all" to archive the uncrippled running config.
Solved! Go to Solution.
01-28-2009 08:43 AM
I saw the internal discussion. There is apparently a lot of history on this, but a bug has been filed (CSCsx31925).
01-22-2009 07:13 AM
You could also add the asdm commands to the list of excluded commands under RME > Admin > Config Mgmt. This should get your report working for the time being.
01-22-2009 07:20 AM
Yes, thanks. I know that it would make the symptom disappear. But I'd rather see my config
archived completely.
Are you going to have that problem fixed?
01-22-2009 07:25 AM
I'm unable to completely evaluate such a fix, as I don't have any FWSMs. I suggest you open a TAC Service request so a bug can be filed.
01-23-2009 05:20 AM
Ok, I've opened SR 610551953.
01-28-2009 04:12 AM
My SE has completely missed the point. :-(
I'm trying to get a more seasoned engineer...
01-28-2009 08:43 AM
I saw the internal discussion. There is apparently a lot of history on this, but a bug has been filed (CSCsx31925).
01-30-2009 01:56 AM
Fixing the FWSM is a better solution than I dared to expect. Many thanks to Ramses who got that bug filed.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide