I have quite a few devices that now have theier syslogs going into the Unexpected Device report, after working fine for a while. Turning on Debugging, it seems to find the device DCR id but then has a SQLException occurredjava.sql.SQLException: JZ0C0: Connection is already closed. error, if I'm reading it right.
I've restart CiscoWorks a few times. It also moves around devices that device is now working again, but others are not - same error in the logs. The messages are from a RSAC if that makes a difference. All Solaris.
I have fixed some other database connection issues in recent releases, and this may be covered by that. However, I will have to investigate this particular code path. In the meantime, restarting SyslogAnalyzer alone should work around the problem.
While the bug was opened due to a problem in the BugToolkit report in RME, the same patch should fix this problem for you. If you contact TAC, and request the patch for CSCso14160, this problem should be fixed.
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...