11-15-2002 10:54 AM - edited 03-02-2019 02:55 AM
I have a handfull of devices that are having the Sysname changed by CW2K without being told to.
I change the sysname and a few days later it is changed back. I could understand CW2K archiving configs after they are changed but to actually change the syslog name back to what it was before, without me directiing it to is hard to track. The logs on the device do not show snmp "sets" so I cannot track down the exact time it occurs. It appears to happen at least once a week, or if I restart the server it does it then, and it is only a dozen or so devices, and the same ones everytime. No pattern of device type etc can be determined.
11-15-2002 10:59 AM
Is this RME 3.4?. If so, then take a look at CSCdx73755 via CCO Bug Toolkit. It seems close.
11-15-2002 11:06 AM
That looks like it could be it. What is the quickest way to get the 3.4.3 upgrade?
11-15-2002 11:15 AM
There is no such version as 3.4.3 currently. 3.4 is the latest right now.
11-15-2002 12:00 PM
So is there a bug fix in place for this problem?
11-15-2002 12:11 PM
You should contact TAC to find out if there's fix available or not assuming that the bug matches 100% with your problem symptoms.
11-15-2002 01:59 PM
This has been fixed in the RME 3.4 IDU 2.0 according to the README file for the IDU: http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-rme
11-15-2002 01:41 PM
We faced this same bug in our setup. The TAC claimed the bug was fixed in RME 3.4 IDU 1.0, though it wasn't listed in the notes for the IDU. The Engineer I was working with finally sent me the patches themselves.
I can e-mail them to you if you so wish.
Scott
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