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.
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.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...