I also tried to start the IPMProcess (the attached daemons1.log.gz taken before the attempt and the daemons2.log.gz after) and it started out fine:
bash-3.00# /opt/CSCOpx/bin/pdshow IPMProcess Process= IPMProcess State = Program started - No mgt msgs received Pid = 12414 RC = 0 Signo = 0 Start = 01/07/10 10:02:16 Stop = Not applicable Core = Not applicable Info = Application started by administrator request.
In the daemons.log I noticed some messages for the ipmDB with the warning on the DB indexes, maybe the DB was being checked that long (3Gb) and until it finished it would not open its TCP port?
Yep, the IPM database is corrupt. If you have a good backup of LMS, you can restore it, and hopefully that will provide you with a good IPM DB. If not, you will need to reinitialize the IPM database with the following command:
No, there is no limit. The problem here is not the size per se. It's the fact that the database became corrupt, and is now larger than the engine expects it to be. It is perfectly normal to see multiple gigabyte databases if a lot of data retention is done.
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...