We also got really annoyed by that.
We have several scripts that login to various routers several times a
day, and now we see these messages increasing as we are upgrading our
equipment to some new release.
We opened a case 3 months ago (which was closed yesterday!) and it took
the tac engineer 2 months in order to understand what these messages are.
The 1st answer was "nobody else has this issue, please upgrade" (this is
the 2nd most famous tac phrase after "please send a sh tech"),
Then we found this issue on another router which was running the latest
version. The new answer was "it's not possible to recreate internally".
(this is the 4th most famous phrase)
So we did a webex session and the final verdict was "Cosmetic issue. No
impact to network." :-!
Also, the message is a bit misleading because it says "EXIT_CONFIG", but
noone has actually exited config.
PS: For those who are wondering, the 3rd most famous tac phrase is "this
is expected behavior". :-D
--
Tassos
Jared Mauch wrote on 26/08/2010 23:37:
On Aug 26, 2010, at 4:11 PM, Dominik Bay wrote:
On Thu, 26 Aug 2010 15:50:48 -0400
Jared Mauch<[email protected]> wrote:
We complained to cisco about this as well, but they seemingly are
unaware and uncaring of this impact to customers as it magically
showed up "in a code sync". This is obnoxious if you have an
automated process (eg: rancid) login hourly to send you diffs from
the device.
I don't know why you want diffs from sh log anyway ... and most
syslog-Viewer can suppress those messages.
I added some filters to suppress script usernames showing up in my
syslog but I don't care about this feature/bug that much ;-)
Dominik,
It's more about the culture at Cisco of "we can introduce undocumented changes at
our own whim and not give you knobs to disable them".
Then trying to chase down the developer that made the change, got it past code
review, etc.. and impacts you at a later date is the problem. Basically, cisco
is unaccountable for many items, like the misguided 'java' downloader they
introduced to help people that breaks downloads for another swath of users.
This was likely some well-intentioned item added for audit compliance, but it
showing up randomly in code without a knob to turn it off and no release note
is the real 'crime against their userbase'.
- jared
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
